Related
i'm having bootloop after installing 17/02/2013 CM10.1 rom on my gsm gnex. the issues are:
1. i don't have any previous working cm10 rom saved in phone's sdcard.
2. can't get adb working, maybe because i never enabled usb debugging mode before.
fyi, i have never flashed any other roms, just CM roms. please assist..
Go into recovery and transfer a new Rom download to your phone if you have a computer. There is an option to transfer files inside recovery.
eqjunkie829 said:
Go into recovery and transfer a new Rom download to your phone if you have a computer. There is an option to transfer files inside recovery.
Click to expand...
Click to collapse
that requires adb (adb_sideload- correct me if i'm wrong).. my adb is not working.. can't boot to android.. can't find a way to enable usb debugging mode.. so no adb..
Do you have a custom recovery or experience with fastboot? Boot a recovery image via "fastboot boot recoveryname*.img", and adb is enabled.
bodh said:
Do you have a custom recovery or experience with fastboot? Boot a recovery image via "fastboot boot recoveryname*.img", and adb is enabled.
Click to expand...
Click to collapse
i don't have custom recovery, but i know how to get into fastboot. please explain how to ""Boot a recovery image via "fastboot boot recoveryname*.img"""
[email protected] said:
i don't have custom recovery, but i know how to get into fastboot. please explain how to ""Boot a recovery image via "fastboot boot recoveryname*.img"""
Click to expand...
Click to collapse
Attached is clockworkmod touch recovery for gsm galaxy nexus, maguro. Phone in bootloader mode, open a terminal, cd to directory of fastboot and where you move this file to, type fastboot devices to verify device is connected, then "fastboot boot CWMT6023.img", without the quotes of course. This will temporarily allow you to use clockworkmod recovery, and thus adb, without having it on your device once you have selected "reboot now".
And if that didn't help, try consulting http://forum.xda-developers.com/showthread.php?t=1626895, since i'm thinking you haven't used fastboot in a terminal, but only know it's 'mode', and may need help with drivers.
You also might want to consider just straight out flashing cwm recovery, since YOU NEED TO MAKE BACKUPS!
[email protected] said:
i don't have custom recovery, but i know how to get into fastboot. please explain how to ""Boot a recovery image via "fastboot boot recoveryname*.img"""
Click to expand...
Click to collapse
If u don't have a custom recovery how did u flash cm10?
Sent from my Galaxy Nexus using xda premium
Esteway.619 said:
If u don't have a custom recovery how did u flash cm10?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
sorry, i got cwm. but what does fastboot have to do with cwm? i can't use cwm to restore because files can't be sent from computer to it.
as of fastboot in terminal, it seems the phone not connected to computer. is there anything has to do with my drivers? "fastboot device" command shows <waiting for device>
I gave you that link to set up drivers more than anything else. If you already have cwm, boot to it and now you can adb push a rom.zip to your sdcard and install it, wipe caches and perhaps a factory reset [if you're changing to a different rom], OR, you can first try and wipe cache and advanced, dalvik cache to see if that fixes the bootloop.
1. Why didn't you make a backup?
2. Why didn't you make sure you know how to get out of this situation before flashing new ROMs?
3. Search as there are LOTS of tutorials on how to use adb to side load a new ROM via CWM
EddyOS said:
1. Why didn't you make a backup?
2. Why didn't you make sure you know how to get out of this situation before flashing new ROMs?
3. Search as there are LOTS of tutorials on how to use adb to side load a new ROM via CWM
Click to expand...
Click to collapse
I know how to use the adb to sideload a new ROM, thank you.
But please read my earlier post, in order to use adb, usb debugging mode must be enabled in android settings.
Mine is disabled, and i can't enable it now.
[email protected] said:
I know how to use the adb to sideload a new ROM, thank you.
But please read my earlier post, in order to use adb, usb debugging mode must be enabled in android settings.
Mine is disabled, and i can't enable it now.
Click to expand...
Click to collapse
If you think that then you have no idea on how adb works...
That is ONLY applicable when Android is running. As it's not, it's irrelevant...
[email protected] said:
I know how to use the adb to sideload a new ROM, thank you.
But please read my earlier post, in order to use adb, usb debugging mode must be enabled in android settings.
Mine is disabled, and i can't enable it now.
Click to expand...
Click to collapse
ADB should work in your custom recovery regardless of USB debugging being enabled or disabled.
I can't tell you how many times I have rebooted into recovery, wiped, then realized I forgot to put a file on my sdcard that I wanted to flash. I then use adb to push the file(s) from within the recovery.
Edit: I really need to refresh prior to responding.
so i can't get adb working because of the driver? thats why i got "waiting for device" when pushing file to phone?
edit: i've installed all the required drivers, it's not my 1st time doing it. MAYBE, this computer never connected to my gnex before, as i've formatted it a few days ago. So the gnex driver was not properly installed.. Is it possible?
If that version of cm 10 is for 4.2.2., then i think you may have an issue accessing adb without first getting the rsa verification, even in recovery (but im not sure). Looks like your only other option would be to fastboot flash stock images. And of course it sounds like driver issues, especially if your fastboot is not even working. Again, that link I posted will get you back up and running. http://forum.xda-developers.com/showthread.php?t=1626895
Hi all,
i haven't a Nexus 10 but I want to let you know that Jade Remix OS ROM is now available for flashing on the Nexus 10:
Here is the link to download the ROM: https://drive.google.com/open?id=0B6QbFTXmsda3VDhCMUU3OVg1S2s
Here you'll find screenshots and videos: http://www.jide.com/en/remixos - https://www.youtube.com/channel/UC0U64-AHqJfeAnFJ5vQnM8w/feed
Here is the JIDE forum: https://forum.jide.com/index.php?p=/discussion/601/nexus-10-rom-available-here#Head
This is the greatest "fork" Android base ROM!!
P.S.: I don't want anything, just a Thank You
ROM Installation Instructions
Want to try to flash a Remix OS ROM to other android devices? Yes! We will soon put the Remix OS ROM on the Internet for users to download and flash onto their own device. To start, we will provide the guideline and support to flash the Remix OS ROM on Google Nexus 10.
Disclaimer
Flashing Remix OS ROM on Nexus 10 requires strong android knowledge. Flashing this ROM on Nexus 10 will be at your own risk. You will have to bear responsibility for all the resulting consequences. Jide will NOT be responsible for any damage caused.
Further Note:
Unfortunately, as a startup, we lack the resources to support installation Remix OS ROM on other android devices, thus, we will ONLY provide support for the Nexus 10 device. The Nexus 10 is a touchscreen tablet manufactured by Samsung with direct support from Google. It is the second Nexus tablet. Of course, we will look forward to the support of Remix fans to share with the world about their experience on flashing the ROM on other Android devices.
Installation Instructions
The followings are the steps to install Remix OS ROM: Unlocking the device & Installing image files using fastboot
Unlocking the device
1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging on the device.
3. Connect the device to the computer through USB.
4. From a terminal on a computer, type the following to boot the device into fastboot mode:
- adb reboot bootloader
5. Once the device is in fastboot mode, verify your PC sees the device by typing
- fastboot devices
- If you don't see your device serial number, and instead see "", fastboot is not configured properly on your machine. See fastboot documentation for more info.
- If you see "no permissions fastboot", try running fastboot as root.
6. From the same terminal, type the following command to unlock the bootloader:
fastboot oem unlock
7. A disclaimer will display on the device that must be accepted. Use the volume keys to cycle through the options. Pressing the power button should confirm your selection.
8. If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked. You can confirm this is the case if you see an unlocked icon at the bottom of the Google boot screen during reboots.
9. Since the device resets completely, you will need to re-enable USB debugging on the device to continue.
Installing image files using fastboot
1. Make sure your computer has working fastboot and adb.
2. Download images
- you should have a download link from us in the email. The information of the image zip file:
- Images Zip File Name: images_Nexus_10-5.0.2-B2015070105-signed.zip
- md5: bdb08b6a0508dd1088f177a9e19c2875
- sha1: 9d6df824ef8c32af1a3a9d89e5f870133bcdebf6
3. Unzip the downloaded zip file ( images_Nexus_10-5.0.2-B2015070105-signed.zip ) and go to the folder
4. Connect the Nexus 10 to the computer via USB.
5. Make sure the fastboot binary is in your PATH or that you place the recovery image in the same directory as fastboot.
6. Open a terminal on your PC and reboot the device into fastboot mode by typing
adb reboot bootloader
or by using the hardware key combination for your device while it is powered off.
7. Once the device is in fastboot mode, verify your PC sees the device by typing
fastboot devices
- If you don't see your device serial number, and instead see "", fastboot is not configured properly on your machine. See fastboot documentation for more info.
- If you see "no permissions fastboot", make sure your UDEV rules are setup correctly.
8. Clean the existing data by entering the following command:
- fastboot -w
9. Flash images onto your device by entering the following three commands:
- fastboot flash system system.img
- fastboot flash recovery recovery.img
- fastboot flash boot boot.img
10. Once the flash completes successfully, run the following command to reboot the device into recovery to verify the installation.
- fastboot reboot
Some of the external link of this documents will link to CM website. The installation process is referenced by http://wiki.cyanogenmod.org/w/Install_CM_for_manta
You are the man!
Yea that didn't work for me, no recovery on boot to recovery just blank screen. Also stuck on remix boot logo.
Works for me. You have to fastboot -w to wipe your device, then flash at least the system and boot image through fastboot.
I didn't wipe my device ,didn't wanna lose the sdcard content. I simply did a factory reset from twrp. Question, can it be rooted with cfautoroot like normal android 5.0?
its totally a new dev rom! the best out there! Love this rom!
How to add other languages, for example, russian?
So far I'm loving this rom. The only thing is that I wish there was a way to add widgets.
For some reason i can't hear any media volume whether it be youtube videos, music, or netflix. Any ideas on what might be wrong?
For some odd reason Tapatalk doesn't work on this ROM for me.
How do we root? Anyone know?
I've found this YOUTUBE link, but didn't test yet
EddyTeddy01 said:
For some reason i can't hear any media volume whether it be youtube videos, music, or netflix. Any ideas on what might be wrong?
Click to expand...
Click to collapse
I'm having the same problem, did you ever figure this out?
Corvidd said:
I'm having the same problem, did you ever figure this out?
Click to expand...
Click to collapse
Why is this always a problem with N10 roms?
Sent from my Nexus 5 using Tapatalk
I'm trying to get this ROM off my nexus 10, but I don't have ADB connection for some reason. I don't have TWRP recovery anymore either. Anyone have any tips?
blkhrt13 said:
I'm trying to get this ROM off my nexus 10, but I don't have ADB connection for some reason. I don't have TWRP recovery anymore either. Anyone have any tips?
Click to expand...
Click to collapse
ADB - do you have USB debugging on? is Fastboot not working either? may need to re-install drivers on your PC
TWRP - are you saying it was installed, but you can't access it? unclear on your exact issue.
drewski_1 said:
ADB - do you have USB debugging on? is Fastboot not working either? may need to re-install drivers on your PC
TWRP - are you saying it was installed, but you can't access it? unclear on your exact issue.
Click to expand...
Click to collapse
Okay, I'll power off the tablet, then hold volume up AND down + power and that boots it into.... Recovery I think. When it boots to that, adb and fastboot are connected. I have a Nexus toolkit installed on my pc for flashing etc. Whenever I click flash recovery to reinstall twrp, it reboots the tablet into the OS and that's it. And when it's booted into the OS, there's no adb connection. And USB debugging is on. I finally just gave up.
blkhrt13 said:
Okay, I'll power off the tablet, then hold volume up AND down + power and that boots it into.... Recovery I think. When it boots to that, adb and fastboot are connected. I have a Nexus toolkit installed on my pc for flashing etc. Whenever I click flash recovery to reinstall twrp, it reboots the tablet into the OS and that's it. And when it's booted into the OS, there's no adb connection. And USB debugging is on. I finally just gave up.
Click to expand...
Click to collapse
Power + Vol Up/Down boots to bootloader.
If you have fastboot, then download the TWRP img file to your computer and issue the following command in the bootloader (forget the toolkit)
Code:
fastboot flash recovery <recovery img file name>
then you should be able to get into TWRP by using the Power Up/Down buttons until you see "Recovery" aligned with the Power Button.
press Power and you should be good to go.
blkhrt13 said:
I'm trying to get this ROM off my nexus 10, but I don't have ADB connection for some reason. I don't have TWRP recovery anymore either. Anyone have any tips?
Click to expand...
Click to collapse
I'm in the EXACT same situation. Fastboot and adb not working for this, but all my other android devices are working fine. Luckily I have twrp installed so I'll just flash something else then start over on a diff rom.
Edit: and of course, just like that, I restart one more time and it actually works. very temperamental i guess.
This is a great ROM with fast clean I interface. I used official manta 5.1 from Jide. Unfortunately google device manager now sees my N10 as a Linux device, and google play services will not load properly so I cannot play cloud connected games which is really sad, I will have to back to an android custom ROM..... If you don't need play services give jide a try.. Its a pretty cool concept.
Hi,
I have a unique problem. I cant go into fastboot. Yes, fastboot on my OPT is not a opltion.
I cant instal TWRP. I can't wipe the OS to flash a new one.
My question is this:
Is there a way to wipe the partitions on a android phone via windows or something?
This problem is created by me. Somehow I flash OOS over CM (??)
So when my phone boots (bootloader is unlocked) I will see 2 boot sequences wich prevents me from accesing the fastboot menu.
The solution I see is this: Enter TWRP --> Wipe all but USB-OTG ...
Anyway, I hope there is a android Einstein here because I'm at a loss..
Feel free to ask any questions and pls help me!
Grt TwoChill
TowChill said:
Hi,
I have a unique problem. I cant go into fastboot. Yes, fastboot on my OPT is not a opltion.
I cant instal TWRP. I can't wipe the OS to flash a new one.
My question is this:
Is there a way to wipe the partitions on a android phone via windows or something?
This problem is created by me. Somehow I flash OOS over CM (??)
So when my phone boots (bootloader is unlocked) I will see 2 boot sequences wich prevents me from accesing the fastboot menu.
The solution I see is this: Enter TWRP --> Wipe all but USB-OTG ...
Anyway, I hope there is a android Einstein here because I'm at a loss..
Feel free to ask any questions and pls help me!
Grt TwoChill
Click to expand...
Click to collapse
Here you can find a recovery guide:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I'd recommend methode 2, because it seems more east to do.
Good luck!
TowChill said:
Hi,
I have a unique problem. I cant go into fastboot. Yes, fastboot on my OPT is not a opltion.
I cant instal TWRP. I can't wipe the OS to flash a new one.
My question is this:
Is there a way to wipe the partitions on a android phone via windows or something?
This problem is created by me. Somehow I flash OOS over CM (??)
So when my phone boots (bootloader is unlocked) I will see 2 boot sequences wich prevents me from accesing the fastboot menu.
The solution I see is this: Enter TWRP --> Wipe all but USB-OTG ...
Anyway, I hope there is a android Einstein here because I'm at a loss..
Feel free to ask any questions and pls help me!
Grt TwoChill
Click to expand...
Click to collapse
If you are getting two boot screens, please confirm if this is what you see in your first boot screen:
some text which goes like "Your device cannot be trusted etc etc. fastboot oem lock something something"
If yes, press the volume buttons at this screen, which will take you to an "Options menu"
This will have options to power off, restart, recovery, fastboot, back to previous page.
use volume down buttons to move selection to fastboot and press power button to select fastboot.
This will take you to bootloader.
Alternatively:
Is the device getting identified by your computer when connected?
If yes, and if you have adb tools installed, try this command, after connecting to computer and selecting usb configuration as transfer files
adb devices
The result of this should show your device
then type:
adb reboot bootloader
This should take you to your bootloader screen.
pvramk said:
If you are getting two boot screens, please confirm if this is what you see in your first boot screen:
some text which goes like "Your device cannot be trusted etc etc. fastboot oem lock something something"
If yes, press the volume buttons at this screen, which will take you to an "Options menu"
This will have options to power off, restart, recovery, fastboot, back to previous page.
use volume down buttons to move selection to fastboot and press power button to select fastboot.
This will take you to bootloader.
Alternatively:
Is the device getting identified by your computer when connected?
If yes, and if you have adb tools installed, try this command, after connecting to computer and selecting usb configuration as transfer files
adb devices
The result of this should show your device
then type:
adb reboot bootloader
This should take you to your bootloader screen.
Click to expand...
Click to collapse
Thank you for your replay.
I have done all of this and i do understand how this works.
I have adb drivers installed, my computer does reconizes my phone and everything works even the reboot to bootloader via CMD. (adb devices, it shows, etc)
When my phone then tries to access the bootloader, it will show those messeges " this devices cant be trusted etc etc." afther 5 seconds again I see the the android logo (with a few lines of static on the bottom) (( that clearly is not right )) but it will show me again the same message " this devices cant be trusted etc etc" ... then it will just show me the battery icon and power precentage (this if I choose to boot to bootloader) or else it starts normally..
Clearly the flashing of CM failed. And with a sideload to install OxygenOS I can use it.. But it does prevents me from accessing the fastboot mode..
So Is there an alternative way to install TWRP without using the fastboot mode? Or is there an other way i can try to wipe the partitions inc. the os?
From there I know what to do.
TowChill said:
Thank you for your replay.
I have done all of this and i do understand how this works.
............
So Is there an alternative way to install TWRP without using the fastboot mode? Or is there an other way i can try to wipe the partitions inc. the os?
From there I know what to do.
Click to expand...
Click to collapse
well if you are rooted you can try using an app called flashify or flashfire to install twrp
pvramk said:
well if you are rooted you can try using an app called flashify or flashfire to install twrp
Click to expand...
Click to collapse
Thanks! Unfortunatly my phone isn't rooted anymore ..
I'm screwed right?
TowChill said:
Thanks! Unfortunatly my phone isn't rooted anymore ..
I'm screwed right?
Click to expand...
Click to collapse
When the display shows the battery % check if fastboot devices shows your device?
If not I'm sorry, I would not be of any more help to you my friend.
Hope someone more knowledgeable comes along and clears your problem....
TowChill said:
Thank you for your replay.
I have done all of this and i do understand how this works.
I have adb drivers installed, my computer does reconizes my phone and everything works even the reboot to bootloader via CMD. (adb devices, it shows, etc)
When my phone then tries to access the bootloader, it will show those messeges " this devices cant be trusted etc etc." afther 5 seconds again I see the the android logo (with a few lines of static on the bottom) (( that clearly is not right )) but it will show me again the same message " this devices cant be trusted etc etc" ... then it will just show me the battery icon and power precentage (this if I choose to boot to bootloader) or else it starts normally..
Clearly the flashing of CM failed. And with a sideload to install OxygenOS I can use it.. But it does prevents me from accessing the fastboot mode..
So Is there an alternative way to install TWRP without using the fastboot mode? Or is there an other way i can try to wipe the partitions inc. the os?
From there I know what to do.
Click to expand...
Click to collapse
If nothing works, try method 2 from the Hard Brick guide from Naman Bhalla.
So I tried to flash another rom by flashing TWRP and unlocking the bootloader, which worked and I then had installed Freedom Os. Then I locked the Bootloader to get the Message away, but know when you charge it or turn it on it is in an boot loop which repeats the Oneplus Logo what you normally see, but very short and after that it bobrates turns the screen off and it atart again. Or I can go into fastboot mode, but when I try to go into the recovery, it goes into the Boot Loop again. Is there a way to get the Original OS back? Ive already dopwnloaded it but I cant get in on there. Can you tell me how to fix it on my own?
[GUIDE] Mega Unbrick Guide for A Hard Bricked OnePlus 3 > METHOD 1
If you can access fastboot mode, connect the phone to a PC, then go to ADB and erase recovery using the command " fastboot erase recovery" and install TWRP 3.0.4-1 using the command " <fastboot flash recovery <recovery.zip/img> again.
Once you do that, boot into TWRP, go to wipe and wipe everything. Once you do that, transfer the stock OOS into the internal memory using copy-paste , then go to install , select the transferred file to install the OS or else go to advance setting in TWRP and select adb sideload and use the command "adb sideload <filename.zip>".
This should install the OS on the phone.
If you want to go complete stock, then you also need to install the stock recovery. Search the forum to get the relevent files or else you can download it from the OnePlus website and later on update to latest OS via OTA.
NEVER EVER LOCK THE BOOTLOADER , IF YOU'RE USING ANY ROM OTHER THAN STOCK OS AND STOCK RECOVERY
anup807 said:
If you can access fastboot mode, connect the phone to a PC, then go to ADB and erase recovery using the command " fastboot erase recovery" and install TWRP 3.0.4-1 using the command " <fastboot flash recovery <recovery.zip/img> again.
Once you do that, boot into TWRP, go to wipe and wipe everything. Once you do that, transfer the stock OOS into the internal memory using copy-paste , then go to install , select the transferred file to install the OS or else go to advance setting in TWRP and select adb sideload and use the command "adb sideload <filename.zip>".
This should install the OS on the phone.
If you want to go complete stock, then you also need to install the stock recovery. Search the forum to get the relevent files or else you can download it from the OnePlus website and later on update to latest OS via OTA.
NEVER EVER LOCK THE BOOTLOADER , IF YOU'RE USING ANY ROM OTHER THAN STOCK OS AND STOCK RECOVERY
Click to expand...
Click to collapse
Can you tell me how to go to adb? When doing it while being in fastboot I get the error "remote: Partition erase is not allowed"
revedar said:
Can you tell me how to go to adb? When doing it while being in fastboot I get the error "remote: Partition erase is not allowed"
Click to expand...
Click to collapse
Download Universal ADB software, download the latest version and install it.
TWRP 3.0.4-1
Official Oxygen OS 4.0.3
Official Recovery
Connect your phone to the PC and then navigate to installed folder, right click holding SHIFT key and select "Open command window here"
Inside command window type
adb devices
If all the drivers are installed properly, you should see you're device ID here.
then type
adb reboot bootloader
your phone will enter fastboot mode.
then type
fastboot devices
again you should see you're device ID here.
then follow the instruction , i've given earlier.
anup807 said:
Download Universal ADB software, download the latest version and install it.
TWRP 3.0.4-1
Official Oxygen OS 4.0.3
Official Recovery
Connect your phone to the PC and then navigate to installed folder, right click holding SHIFT key and select "Open command window here"
Inside command window type
adb devices
If all the drivers are installed properly, you should see you're device ID here.
then type
adb reboot bootloader
your phone will enter fastboot mode.
then type
fastboot devices
again you should see you're device ID here.
then follow the instruction , i've given earlier.
Click to expand...
Click to collapse
So i've downloaded the software, installed the driver and typed in cmd adb devices "adb devices List of devices attached" is returned, so it seems like there is going something wrong. Is it because the Driver is installed wrong or because "target reported max download size of 440401920 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.528s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.551s"
This is returned when trying to flash. Do I have to be in fastboot mode or something else to be able to follow your instructions? In Fast Boot is written that the Device State is locked and Secure Boot is enabled. I messaged Oneplus and hope they have a solution which can just unlock the Bootloader when being in fastboot mode, so everything is fine again. I hope you can help me, but I still wanna say thank your for now
Errr... fastboot can unlock the bootloader. fastboot oem unlock
emuandco said:
Errr... fastboot can unlock the bootloader. fastboot oem unlock
Click to expand...
Click to collapse
Thank you, but it dont works because i forgot to re-enable the oem modification and usb debugging in freedom os, maybe there is an option to do this without having this enabled but I didnt found it. So I wait for a helpful answer from somebody here or from Oneplus, I consider sending my smartphone to oneplus to let them repair it if I cant do it. Just saying that modding an S3, Asus transformer pad and nvidia shield is way easier.
never ever relock your bootloader while you in custom OS
oopstairs said:
never ever relock your bootloader while you in custom OS
Click to expand...
Click to collapse
Thank you for not helping me
revedar said:
Thank you for not helping me
Click to expand...
Click to collapse
Yeah I'm sorry I can't help you in your case. I'm just stating the fact. Sorry if I offended you.
Shouldn't it still be possible to reflash the properly signed official updates? TBH I never had such a problem and thus never had to cope with it. Same with recovery: http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img Try flashing this one with fastboot. It's the official one. By flashing this one you might fix your stuff over adb sideloading the official full update zips.
Try the unbrick guide provided in the 2nd post to your query. It should definitely help. Better contact OnePlus tech2 support and they'll flash your phone for you. They're really helpful.
emuandco said:
Shouldn't it still be possible to reflash the properly signed official updates? TBH I never had such a problem and thus never had to cope with it. Same with recovery: http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img Try flashing this one with fastboot. It's the official one. By flashing this one you might fix your stuff over adb sideloading the official full update zips.
Click to expand...
Click to collapse
I already tried to do this, but the console returns something like permission denied.
anup807 said:
Try the unbrick guide provided in the 2nd post to your query. It should definitely help. Better contact OnePlus tech2 support and they'll flash your phone for you. They're really helpful.
Click to expand...
Click to collapse
The MSM Software disconnects the smartphone while the process works
U cannot flash in adb while the bootloader is locked, u can not unlock the bootloader unless u can access ur OS, I am not sure y people was trying to get u to flash via fastboot the answer was provided to u in the 2nd post
^^^ This!
It's pretty much obvious fastboot flash will not work with a locked bootloader.
It's pretty obvious unlocking the bootloader will not work, while one can not access the OS.
Unbrick tool is the only option to bring it back to life, or sending it for RMA. If unbrick tool fails, try using different drivers and make sure it is connected with the stock cable (I've only tried with a Nilkin cable besides the stock one, which always failed at different stages during the process).
Not even sure drivers must be installed manually, I've never done that myself on Windows 10, as they were automatically installed (3 different's PC's, both on x86 and x64).
Which version of stock firmware did you last have? If it was 4.0.1 or earlier, then you can use
Code:
fastboot oem 4F500301
to issue a flash command even without unlocking the bootloader. If you are on that, then use that command and flash stock recovery and then flash stock zip.
rk2612 said:
Which version of stock firmware did you last have? If it was 4.0.1 or earlier, then you can use
Code:
fastboot oem 4F500301
to issue a flash command even without unlocking the bootloader. If you are on that, then use that command and flash stock recovery and then flash stock zip.
Click to expand...
Click to collapse
I had the most recent update installed. Is there a similar command at the moment?
revedar said:
I had the most recent update installed. Is there a similar command at the moment?
Click to expand...
Click to collapse
Don't think so.
I tried ro go back from beta 13 to public 12 and stuck on fastboot. I tried to sideload from recovery the 13 beta or the 12 version but it said error because i didnt opened the usb debugging before i stucked at fastboot(adb devices not recognize the phone) what can i do??? Please helpppp!!
Edit:Fixed!!
@avivasaf
Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)
roirraW edor ehT said:
@avivasaf
Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)
Click to expand...
Click to collapse
I tried it, it said oem unlocking is not checked, go to developer options, which i cant do
@avivasaf There may not be anything you can do to fix it, then. To fool around with Android Betas, you really should unlock the bootloader first so that you have more recovery options. Hopefully, someone else with more experience recovering from such a situation responds with some other ideas.
avivasaf said:
I tried it, it said oem unlocking is not checked, go to developer options, which i cant do
Click to expand...
Click to collapse
Device Unlock DisabledFor security reasons, you need to enable "OEM unlocking" in order to flash your device. See the device preparation instructions for more information.
avivasaf said:
I tried ro go back from beta 13 to public 12 and stuck on fastboot. I tried to sideload from recovery the 13 beta or the 12 version but it said error because i didnt opened the usb debugging before i stucked at fastboot(adb devices not recognize the phone) what can i do??? Please helpppp!!
Click to expand...
Click to collapse
Have you tried going into recovery and then scrolling down to wipe data/factory reset and doing that?
You might be able to sideload the beta again.
get the ota here as some people have claimed USB debugging or OEM unlock is not required to sideload
Boot into recovery (power > volume up > tap volume up when you see the android with an exclamation mark)
Right-click on the downloaded ota.zip and open an terminal in your adb folder (platform tools)
Code:
adb sideload "paste the path here"
It's worth a shot. Good luck
Lughnasadh said:
Have you tried going into recovery and then scrolling down to wipe data/factory reset and doing that?
Click to expand...
Click to collapse
Tried it, didn't help
fil3s said:
You might be able to sideload the beta again.
get the ota here as some people have claimed USB debugging or OEM unlock is not required to sideload
Boot into recovery (power > volume up > tap volume up when you see the android with an exclamation mark)
Right-click on the downloaded ota.zip and open an terminal in your adb folder (platform tools)
Code:
adb sideload "paste the path here"
It's worth a shot. Good luck
Click to expand...
Click to collapse
Its start 0% to sideload and stopped after 1 second"failed", in the phone "success 1"
avivasaf said:
Its start 0% to sideload and stopped after 1 second"failed", in the phone "success 1"
Click to expand...
Click to collapse
I don't understand that one. Sideloading should be possible, you just can't downgrade, should just be able to tap 'apply update from adb' in recovery mode and be good to go.
The first thing one should do when getting an android is enable USB debugging.
fil3s said:
I don't understand that one. Sideloading should be possible, you just can't downgrade, should just be able to tap 'apply update from adb' in recovery mode and be good to go.
The first thing one should do when getting an android is enable USB debugging.
Click to expand...
Click to collapse
I know that, but in my case its to late, any suggestions?
avivasaf said:
I know that, but in my case its to late, any suggestions?
Click to expand...
Click to collapse
I'm sorry mate. It might be a brick. I know its a crappy thing to hear, but it's one of those life lessons learned the hard way I guess.
All I would try to do is remove the device in device manager, install google USB driver in fastboot and try again.
You can try to use Google's flash tool (it's reportedly worked for some with even locked bootloaders) to get a booting device.
Android Flash Tool
flash.android.com
If you can't get your PC to recognize your P6P while it's in bootloader mode, and you're using Google's own USB driver (which is obviously recommended) for Windows, I had this very issue today. I solved it by abandoning the Google driver for clockworkmod's universal adb driver which after installation, allowed my PC to finally recognize my P6P in bootloader mode...
You might have to wait for Official Android 13 to drop with a locked bootlaoder
Fixed!!!
I downloaded the ota file! Not the one that didnt worked from beta program, the ota file could sideload and phone back to life!
After that used android flash tool to return to public Android 12
fil3s said:
You might be able to sideload the beta again.
get the ota here as some people have claimed USB debugging or OEM unlock is not required to sideload
Boot into recovery (power > volume up > tap volume up when you see the android with an exclamation mark)
Right-click on the downloaded ota.zip and open an terminal in your adb folder (platform tools)
Code:
adb sideload "paste the path here"
It's worth a shot. Good luck
Click to expand...
Click to collapse
Your ota file saved me, thanks alot
avivasaf said:
Your ota file saved me, thanks alot
Click to expand...
Click to collapse
I'm kind of confused. That OTA file that was linked to you is the same as the latest official one for A13 Betas. Were you just trying to sideload the wrong OTA file to begin with?
Btw, glad you got it going
Lughnasadh said:
I'm kind of confused. That OTA file that was linked to you is the same as the latest official one for A13 Betas. Were you just trying to sideload the wrong OTA file to begin with?
Btw, glad you got it going
Click to expand...
Click to collapse
There are 2 files the one that call ota is the one that saved me, the other one is the the one from beta program