After I got my nexus 5x, I unlocked bootloader and root, and finally I go back official stock 6.0.1. But the camera didn't work fine(sometimes black screen, and then phone reboot). Have to flash CM13.
Following the guide, I did those steps strictly. Yet failed.
- When I tried to install CM13.zip, the TWRP told me I had to decrypt , and need to enter the default password which I don't know/have.
- I tried another way, flash official recovery.img . Failed again: the official recovery told me "can't mount SDcard", update zip file from sd card failed.
How can I install CM13 now? Or, how can I solved the camera issue?
I feel terrible about this, could you guys help?
thank you
faytuu said:
After I got my nexus 5x, I unlocked bootloader and root, and finally I go back official stock 6.0.1. But the camera didn't work fine(sometimes black screen, and then phone reboot). Have to flash CM13.
Following the guide, I did those steps strictly. Yet failed.
- When I tried to install CM13.zip, the TWRP told me I had to decrypt , and need to enter the default password which I don't know/have.
- I tried another way, flash official recovery.img . Failed again: the official recovery told me "can't mount SDcard", update zip file from sd card failed.
How can I install CM13 now? Or, how can I solved the camera issue?
I feel terrible about this, could you guys help?
thank you
Click to expand...
Click to collapse
Update TWRP to 3.0.0-1
You can't flash anything worth flashing with stock recovery.
Make sure you are using the latest stock version "J" as it has alot of fixes for this like the camera error.
Darke5tShad0w said:
Update TWRP to 3.0.0-1
You can't flash anything worth flashing with stock recovery.
Make sure you are using the latest stock version "J" as it has a lot of fixes for this like the camera error.
Click to expand...
Click to collapse
Thanks for your reply. I will try TWRP 3.0.0.1 for bullhead
Yes, I'm using the MHC19J build. I still got the camera issue, and tired for that (this is the reason why I want flashing CM13). Do I need to format userdata while I always get the red warning at booting ?
SOLVED http://forum.xda-developers.com/nexus-5x/general/learn-using-nexus-5xwith-official-stock-t3342616
Related
Hello,
I am having some trouble reverting back from TWRP to Stock Recovery to do an OTA update to the 5/30 update. Whenever I flash the recovery in TWRP, it fails. Another problem I had was, when I was in stock recovery (before jumping to TWRP), I tried doing the OTA update, but when the phone rebooted to perform the update, it would stop half way and reboot back into the OS and no change would happen (even though it said "Updating ColorOS". Any help is appreciated. Thanks!
azeem40 said:
Hello,
I am having some trouble reverting back from TWRP to Stock Recovery to do an OTA update to the 5/30 update. Whenever I flash the recovery in TWRP, it fails. Another problem I had was, when I was in stock recovery (before jumping to TWRP), I tried doing the OTA update, but when the phone rebooted to perform the update, it would stop half way and reboot back into the OS and no change would happen (even though it said "Updating ColorOS". Any help is appreciated. Thanks!
Click to expand...
Click to collapse
If you don't want to flash recovery via fastboot, use flash tool from play. Then try updating again.
speaking of stock recovery, does anyone know where i can get the recovery.img at? i've been searching...
xBeerdroiDx said:
speaking of stock recovery, does anyone know where i can get the recovery.img at? i've been searching...
Click to expand...
Click to collapse
Here: https://www.dropbox.com/s/nsmi7q86pzymbka/recovery.zip
azeem40 said:
Hello,
I am having some trouble reverting back from TWRP to Stock Recovery to do an OTA update to the 5/30 update. Whenever I flash the recovery in TWRP, it fails. Another problem I had was, when I was in stock recovery (before jumping to TWRP), I tried doing the OTA update, but when the phone rebooted to perform the update, it would stop half way and reboot back into the OS and no change would happen (even though it said "Updating ColorOS". Any help is appreciated. Thanks!
Click to expand...
Click to collapse
You can use my recovery flasher to go back to stock recovery. Here
tantrums said:
You can use my recovery flasher to go back to stock recovery. Here
Click to expand...
Click to collapse
Thanks a lot man! I will surely give it a try tomorrow.
Man, I used your recovery flasher to install the recovery, but it still doesn't let me install the OTA. It boots into recovery and nothing happens. When I reboot the phone, it says updating, but when I check for OTAs, it still says to install the update.
azeem40 said:
Man, I used your recovery flasher to install the recovery, but it still doesn't let me install the OTA. It boots into recovery and nothing happens. When I reboot the phone, it says updating, but when I check for OTAs, it still says to install the update.
Click to expand...
Click to collapse
That's odd. You could try this recovery:
http://forum.xda-developers.com/showpost.php?p=53065486&postcount=84
It's official TWRP except it's modified to report the device as "FIND 7" (just like stock recovery) so it can flash stock ROMs/updates. I doubt the stock recovery uses open recovery script so I doubt you'll be able to initiate the flash via the settings menu. However you could try to install the OTA manually. I think the zip is placed in /sdcard/ota or something like that. I sent my Find 7a in so I can't verify the correct path.
Doc Ames said:
That's odd. You could try this recovery:
http://forum.xda-developers.com/showpost.php?p=53065486&postcount=84
It's official TWRP except it's modified to report the device as "FIND 7" (just like stock recovery) so it can flash stock ROMs/updates. I doubt the stock recovery uses open recovery script so I doubt you'll be able to initiate the flash via the settings menu. However you could try to install the OTA manually. I think the zip is placed in /sdcard/ota or something like that. I sent my Find 7a in so I can't verify the correct path.
Click to expand...
Click to collapse
Even when I use the zip, it gets like 1/4th of the way done and then says "installation failed"... Kind of frustrating.
azeem40 said:
Even when I use the zip, it gets like 1/4th of the way done and then says "installation failed"... Kind of frustrating.
Click to expand...
Click to collapse
Maybe check if the OTA is available for download here or on Oppo Forums with an MD5 so you can verify integrity. If not you could delete the .zip and redownload via software update. If all else fails you could switch to ColorOS 2.0 beta or try Gummy or Omni. I personally hated colorOS however I feel that 2.0 beta is actually more stable with less bugs.
Doc Ames said:
Maybe check if the OTA is available for download here or on Oppo Forums with an MD5 so you can verify integrity. If not you could delete the .zip and redownload via software update. If all else fails you could switch to ColorOS 2.0 beta or try Gummy or Omni. I personally hated colorOS however I feel that 2.0 beta is actually more stable with less bugs.
Click to expand...
Click to collapse
I already tried it, but even that failed.. Color os didn't install either.
So no one has an idea on why I can't install the Ota? Even tried unrooting and trying the Ota that way, but it still failed. Even if I use recovery of color os to flash the Ota without root, it still fails. I don't know what else to do... I want to get Ota in case they update to 4.4 kitkat...
I fixed it.
azeem40 said:
I fixed it.
Click to expand...
Click to collapse
How did you fix it?
Good evening everyone!
I've recently wanted to update my Hercules from 4.1 (I know it's reeealy outdated) to version 6.0 Marshmallow.
So I did a few steps and now I cant' seem to go any further, and I need your help.
So far, I've done the following:
-Installed TWRP 2.8.7.0
-Used Odin to flash the TWRP mentioned above
Now, I know there are a few problems regarding this version of the TWRP on the Hercules, so I tried fixing it by using Odin again and flashing the updated 2.8.7.1 and even the 3.0 version that I found on some threads, but with no sucess.
I haven't even had the chance to install Marshmallow on my phone in the first chance, because I couldn't find any .ZIP folders on the TWRP instalation menu.
I really appreciate your help guys, I'm a noob at this and I'm just starting to figure what is what, I just need my phone updated. It's running so far atleast, so it's not hard bricked I guess.
Did you follow the instructions to flash TWRP using Odin?
olafo73 said:
Did you follow the instructions to flash TWRP using Odin?
Click to expand...
Click to collapse
I'm pretty sure I did everything I was intended to do. I installed Samsung Kies so I could install the drivers on my mobile, and then TWRP through Odin properly with the blue light showing up. After flashing it, it turned green and said PASS or PASSED. So I think I did everything right on that end, I can even access TWRP with no real problems.
I even tried to do a ROOT on my system, but again, I couldn't use ZIP or any other files on the TWRP installation option because they simply do not appear
bump
Watching this thread as I have the same problem.
I can boot to TWRP 2.8.7, but if I try to install, there's no file to install from.
I can go back to TWRP 2.6.0, and then mount the card and see the ROM, but every ROM I try fails. Something about non-virtual partitions if I try 4.4 or better, and error executing updater binary if i try 4.1
aguycalled80 said:
Watching this thread as I have the same problem.
I can boot to TWRP 2.8.7, but if I try to install, there's no file to install from.
I can go back to TWRP 2.6.0, and then mount the card and see the ROM, but every ROM I try fails. Something about non-virtual partitions if I try 4.4 or better, and error executing updater binary if i try 4.1
Click to expand...
Click to collapse
How did you go back to TWRP 2.6.0?
N1ZUW said:
How did you go back to TWRP 2.6.0?
Click to expand...
Click to collapse
With Odin.
I can boot in download mode no problem.
N1ZUW said:
Good evening everyone!
I've recently wanted to update my Hercules from 4.1 (I know it's reeealy outdated) to version 6.0 Marshmallow.
So I did a few steps and now I cant' seem to go any further, and I need your help.
So far, I've done the following:
-Installed TWRP 2.8.7.0
-Used Odin to flash the TWRP mentioned above
Now, I know there are a few problems regarding this version of the TWRP on the Hercules, so I tried fixing it by using Odin again and flashing the updated 2.8.7.1 and even the 3.0 version that I found on some threads, but with no sucess.
I haven't even had the chance to install Marshmallow on my phone in the first chance, because I couldn't find any .ZIP folders on the TWRP instalation menu.
I really appreciate your help guys, I'm a noob at this and I'm just starting to figure what is what, I just need my phone updated. It's running so far atleast, so it's not hard bricked I guess.
Click to expand...
Click to collapse
I don't know of any problems with any of the recoveries. However there are different recoveries for different roms which need to be used in a specific order and in a specific way, the first time that you virtually repartition your phone.
Have you gone through the process of applying the "virtual partition" and installing the modified "virtual partition" recovery? This is required for most of the MM roms on this phone (Hercules). The process is very well documented here http://forum.xda-developers.com/galaxy-s2-tmobile/help/guidance-sgh-t989-updating-issue-t3414641 in the #2nd post.
markusrow said:
I don't know of any problems with any of the recoveries. However there are different recoveries for different roms which need to be used in a specific order and in a specific way, the first time that you virtually repartition your phone.
Have you gone through the process of applying the "virtual partition" and installing the modified "virtual partition" recovery? This is required for most of the MM roms on this phone (Hercules). The process is very well documented here http://forum.xda-developers.com/galaxy-s2-tmobile/help/guidance-sgh-t989-updating-issue-t3414641 in the #2nd post.
Click to expand...
Click to collapse
Hi, thanks for replying
No, I dont' take I have taken that step actually. I'm pretty new to this and I tried following every step correctly, but I know that I failed or skipped something at some extent and I've been trying to figure out what exactly, so I can fix it. I guess I need to Virtual Partition my phone then, could you post me the link do to so? Because I think you posted one that would take back to this post
aguycalled80 said:
With Odin.
I can boot in download mode no problem.
Click to expand...
Click to collapse
How do you go in download mode if you have TWRP installed? Does TWRP work as download mode aswell? Thanks for your help man, hope you can fix your phone too!
N1ZUW said:
How do you go in download mode if you have TWRP installed? Does TWRP work as download mode aswell? Thanks for your help man, hope you can fix your phone too!
Click to expand...
Click to collapse
I shut it down in TWRP then hold volume down and power to go into download mode.
My phone has gone backwards now though - it doesn't matter what I load in Odin now, it won't boot up. The SAMSUNG screen is on, with a progress bar, but it never gets to the end. It stops right near the end and it sits there until I reboot it again.
This is the first time I've ever done this, but I just hated the UI on the Huawei G8 (laggy) and decided to try the xda way. PS: knowing that it's easier to help someone when they tell all the details, I am going to post all of it. So sorry for the long post.
First thing I did was try to update to unofficial marshmallow downloaded from here. But it didn't work saying installation failed ... Did some research and found out the device OS is from Iran (I'm from the middle east), so probably the reason why it didn't allow me to install an EU update.
What I did then was unlock bootloader by getting the unlock code from emui website. And then unlocking it from the adb terminal (adb.exe)
Then I loaded TWRP and did a backup.
I forgot to copy SuperSu to the SD card, and when TWRP asked me to root I accepted. So it got stuck on the Huawei logo while booting.
I then did a recovery from TWRP which worked perfectly
I should've just downloaded a new rom and flashed that , but I was like maybe it might allow me to install that update now the phone is unlocked so I tried installing it from the updater ->local update. And that's when the looping into recovery happened.
So I tried to do another recovery from my backup , but again it loaded into TWRP . Which I don't understand since I guess it should load the backed up System. Or is there something telling the device to reload the update from the SD card causing it to crash again ?
UPDATE: I went into file manager and renamed the dload folder to dloadxxx but that didnt help. Then I downloaded the latest TWRP and flashed that, and recovered the backed up system and THAT worked . The restore took longer than with the older TWRP . I have no clue why it worked like this. But maybe this can help someone in the future.
Thanks
Had the same thing. Exept that this happend during OTA update ....
Get a stock ROM of your choice (tested with xxxB130xxx).
Use update extractor to extract boot.img, system.img recovery.img
Wipe all partitions (except external SD Card) with TWRP. Select remove data and confirm. (you said you have backup). This allows a clean install.
Bring phone into fastboot mode (Vol down + power)
Flash bootlader with fastboot
Make Reset
Flash recovery and system
After reboot phone should start up normal.
Let me know if you got stuck somewhere.
Chilli
Edit: Root cause for the problem seems that Hauwei needs stock recovery for some update actions. -> When ever you want to make OTA or dload update flash back to stock recovery before (better flash completely to stock ).
vlatkozelka said:
This is the first time I've ever done this, but I just hated the UI on the Huawei G8 (laggy) and decided to try the xda way. PS: knowing that it's easier to help someone when they tell all the details, I am going to post all of it. So sorry for the long post.
First thing I did was try to update to unofficial marshmallow downloaded from here. But it didn't work saying installation failed ... Did some research and found out the device OS is from Iran (I'm from the middle east), so probably the reason why it didn't allow me to install an EU update.
What I did then was unlock bootloader by getting the unlock code from emui website. And then unlocking it from the adb terminal (adb.exe)
Then I loaded TWRP and did a backup.
I forgot to copy SuperSu to the SD card, and when TWRP asked me to root I accepted. So it got stuck on the Huawei logo while booting.
I then did a recovery from TWRP which worked perfectly
I should've just downloaded a new rom and flashed that , but I was like maybe it might allow me to install that update now the phone is unlocked so I tried installing it from the updater ->local update. And that's when the looping into recovery happened.
So I tried to do another recovery from my backup , but again it loaded into TWRP . Which I don't understand since I guess it should load the backed up System. Or is there something telling the device to reload the update from the SD card causing it to crash again ?
UPDATE: I went into file manager and renamed the dload folder to dloadxxx but that didnt help. Then I downloaded the latest TWRP and flashed that, and recovered the backed up system and THAT worked . The restore took longer than with the older TWRP . I have no clue why it worked like this. But maybe this can help someone in the future.
Thanks
Click to expand...
Click to collapse
h t t ps://mega.nz/#!P04D2S5Y!Yn2CL5wLC8ISb5AcNR9MTxzhAq3yVH3weG60go5zQCA download this archive, change twrp inside it with the lastest one that surdu_pertu provide.
go twrp wipe all things there
than
using adb "fastboot flash recovery stock.img"
after the first boot phone gonna think a new firmware is being installed just skip it and power off the phone
this will give you a nice start for flashing the Marshmallow from the begining.
Hello Demage,
I would be looking forward to having an Marshmallow image (if it supports my basebands). But Mega says the key is invalid. Can you double check?
Chilli
Thankfully, I managed to fix it.
1- Download Marshmallow G8 stock ROM.
2- Download Huawei update extractor, then extract recovery.img using the previous tool from the stock ROM Update.app file.
3- Go to the bootloader, then flash the extracted recovery.img into recovery.
4- Reboot by the command fastboot reboot.
5- You will get the default loading screen saying the device is reset, then you will be directed to the system welcome screen.
6- You can flash TWRP again, then superSU.
Stuck at "Patching System Image Unconditionally" when flashing CM12.1 via TWRP
Just got a Note 4, proceeding with the usual root and installation CyanogenMod ASAP
Everything was going smoothly until the actual flashing of CyanogenMod, whenever I try to flash it, it just gets stuck on "patching system image unconditionally" and doesn't progress beyond that point
Steps I've taken so far:
1) unboxed phone, was running Android 6.0 (I think, maybe 6.0.1)
2) Rooted with Chainfire's Auto Root
3) Flashed TWRP 3.0.2-0 via Odin 3.09 as per TWRP's instructions
4) Ensured that I could boot both to the stock ROM and TWRP
5) Copied cm12.1 and gapps to Note 4's internal storage (sd card hasn't come in yet, normally I put it onto sd card)
6) Did default factory wipe from TWRP
7) Attempted to flash cm12.1, ran into issue
I didn't make a backup of the stock ROM so now the phone has a recovery but no actual OS, as I had to pull the battery out to get it to do anything beyond being stuck at the patching system image step
I'm redownloading cm12.1 in case maybe there was a problem with the .zip itself, I know it's bad practice but I never check md5 sums
I've found other threads that suggested flashing the stock ROM for some reason, but they were for other phones and I'm not sure if it's related to the Note 4.
I've seen some mention of the bootloader being locked, but I don't know how to tell if the bootloader is locked or not. I see the same exact boot screen that I saw with my Note 3, S4, S3, etc. Could the issue be the bootloader?
I've also found this thread, but I can't get TWRP to mount in Windows, it keeps saying the driver failed to install. MTP transfers worked fine with the stock ROM was still there, but for some reason it doesn't work with the Mount option in TWRP. I'm downloading the Android SDK so I can try using adb
If anyone else has run into this, can you advise me on what to do from here?
EDIT: Nevermind, fixed it. Changed system partition's filesystem to F2FS via TWRP, and this allowed CM and gapps to flash with no issue. Now booted into CM But hopefully this will be helpful if anyone else has this issue
EDIT2: Buuuuut now the WiFi's not working. It just gets stuck at "turn on WiFi" but nothing actually turns on, and the on/off button for WiFi in settings is grayed out. IT NEVER ENDS
CyanogenMod Thread
Reddit Thread
EDIT3:
WiFi and Settings Issue seems to be resolved
I think the problem had something to do with the baseband version
As per Trex's post (http://forum.xda-developers.com/showpost.php?p=69520362&postcount=2), I had to revert back to the OK1 baseband
Now everything seems to work fine
As for TWRP not working and just going to a black screen, I redownloaded it from the TWRP website and it worked fine
So now both TWRP and CM are installed and working, WiFi works, and Settings don't crash.
Now I've encountered an issue where the camera doesn't focus, and I'm wondering if there's still some plastic film on the camera lens, but I've been picking at it and nothing is coming off and I'm afraid of damaging the plastic if I keep trying...
AbuFiraas said:
Just got a Note 4, proceeding with the usual root and installation CyanogenMod ASAP
Everything was going smoothly until the actual flashing of CyanogenMod, whenever I try to flash it, it just gets stuck on "patching system image unconditionally" and doesn't progress beyond that point
Steps I've taken so far:
1) unboxed phone, was running Android 6.0 (I think, maybe 6.0.1)
2) Rooted with Chainfire's Auto Root
3) Flashed TWRP 3.0.2-0 via Odin 3.09 as per TWRP's instructions
4) Ensured that I could boot both to the stock ROM and TWRP
5) Copied cm12.1 and gapps to Note 4's internal storage (sd card hasn't come in yet, normally I put it onto sd card)
6) Did default factory wipe from TWRP
7) Attempted to flash cm12.1, ran into issue
I didn't make a backup of the stock ROM so now the phone has a recovery but no actual OS, as I had to pull the battery out to get it to do anything beyond being stuck at the patching system image step
I'm redownloading cm12.1 in case maybe there was a problem with the .zip itself, I know it's bad practice but I never check md5 sums
I've found other threads that suggested flashing the stock ROM for some reason, but they were for other phones and I'm not sure if it's related to the Note 4.
I've seen some mention of the bootloader being locked, but I don't know how to tell if the bootloader is locked or not. I see the same exact boot screen that I saw with my Note 3, S4, S3, etc. Could the issue be the bootloader?
I've also found this thread, but I can't get TWRP to mount in Windows, it keeps saying the driver failed to install. MTP transfers worked fine with the stock ROM was still there, but for some reason it doesn't work with the Mount option in TWRP. I'm downloading the Android SDK so I can try using adb
If anyone else has run into this, can you advise me on what to do from here?
EDIT: Nevermind, fixed it. Changed system partition's filesystem to F2FS via TWRP, and this allowed CM and gapps to flash with no issue. Now booted into CM But hopefully this will be helpful if anyone else has this issue
EDIT2: Buuuuut now the WiFi's not working. It just gets stuck at "turn on WiFi" but nothing actually turns on, and the on/off button for WiFi in settings is grayed out. IT NEVER ENDS
Click to expand...
Click to collapse
You must flash 5.1.1 ok1 bootloader to get wifi work
I suggest you first flash 5.1.1 firmware in odin
Then flash twrp. Tar file in odin.
Then make full wipe
Flash cm rom + gapps
You will get clean rom install without any errors
Hope this will help
Trex888 said:
You must flash 5.1.1 ok1 bootloader to get wifi work
I suggest you first flash 5.1.1 firmware in odin
Then flash twrp. Tar file in odin.
Then make full wipe
Flash cm rom + gapps
You will get clean rom install without any errors
Hope this will help
Click to expand...
Click to collapse
Okay I'll give that a shot. Are "5.11 ok1 bootloader" and "5.1.1 firmware" the same thing? And do you know where I can find it/them?
Just flashed OK1 via Odin via this thread, but it's just boot looping over and over
EDIT: Did a simple factory wipe and it's working fine now. Currently running unrooted Stock 5.1.1, Baseband N910PVPS4COK1. So I'm basically starting from the beginning, whereas before it was on 6.0 but now it's 5.1.1
Am now rooted but I can't get TWRP installed, I flash it and try to boot to recovery but it just boots to a black screen
Issue seems to be resolved, edited original post
AbuFiraas said:
Okay I'll give that a shot. Are "5.11 ok1 bootloader" and "5.1.1 firmware" the same thing? And do you know where I can find it/them?
Click to expand...
Click to collapse
Go to download mode and check exact model number
Tell me model number and i give you links for bootloader and firmware
Trex888 said:
Go to download mode and check exact model number
Tell me model number and i give you links for bootloader and firmware
Click to expand...
Click to collapse
It's working now, I found another post that had all the various stock firmwares on there. Now the issue I'm having is that my camera doesn't focus at all, but I don't know if it's a hardware or software issue. I never checked the camera before rooting the first time. Gonna try going back to unrooted stock again but if that doesn't change anything, I might have to take it to a Sprint store and get a replacement. Hopefully they don't notice the KNOX trip... lol
Hello please help. So I unlocked bootloader, set up Google and finger scanning password. Flashed SuperSU and that's when everything went wrong. Got stuck on the boot logo. Any suggestions? I've read about using the Qualcomm driver method but I'm unsure if it'll work on a Mac? Any help ? I've used twrp to flash ROM no luck. Used stock recovery but adb doesn't detect my devices I guess I didn't enable USB debugging after unlocking the bootloader.
jasj0410 said:
Hello please help. So I unlocked bootloader, set up Google and finger scanning password. Flashed SuperSU and that's when everything went wrong. Got stuck on the boot logo. Any suggestions? I've read about using the Qualcomm driver method but I'm unsure if it'll work on a Mac? Any help ? I've used twrp to flash ROM no luck. Used stock recovery but adb doesn't detect my devices I guess I didn't enable USB debugging after unlocking the bootloader.
Click to expand...
Click to collapse
Flashing the stock firmware using TWRP should do it for you. Just perform a FULL WIPE (formatting all partitions) before flashing the rom and keep in mind that you need a modified TWRP version to flash Oxygen OS based roms. The official TWRP won't do it.
Can you explain what you mean by "formatting all partitions"?
I have a modified twrp recovery. When I click on wipe there is two options " advance wipe" and "format data" is the 2nd optioption the one your referring too as well? I flashed ROM.zip with the modified twrp without formatting data (I rather wait on your reply to be sure) and instead of getting stuck on the boot logo it is doing a bootloop now. Thanks for your assistance BTW.
jasj0410 said:
Can you explain what you mean by "formatting all partitions"?
I have a modified twrp recovery. When I click on wipe there is two options " advance wipe" and "format data" is the 2nd optioption the one your referring too as well? I flashed ROM.zip with the modified twrp without formatting data (I rather wait on your reply to be sure) and instead of getting stuck on the boot logo it is doing a bootloop now. Thanks for your assistance BTW.
Click to expand...
Click to collapse
Advanced Wipe
--> mark
"ART Cache"
"Cache"
"Data"
"Internal Storage"
"System"
--> swipe to wipe
If you don't get any errors
--> restart TWRP (Or you can't access the storage)
--> flash rom
Did that no luck. I'm trying to flash 3.2.7 anything tricky/specific I should be doing ?
I'm going to flash 3.2.6 tomorrow when I get near Wi-Fi and See what happens.
Should I be downloading "OTA zip" or" oxygenOS 3.2.6 full zip"
jasj0410 said:
Did that no luck. I'm trying to flash 3.2.7 anything tricky/specific I should be doing ?
I'm going to flash 3.2.6 tomorrow when I get near Wi-Fi and See what happens.
Should I be downloading "OTA zip" or" oxygenOS 3.2.6 full zip"
Click to expand...
Click to collapse
OTA = on the air update // for upgrading your android version e.g. OOS 3.2.6 --> 3.2.8 // NOT for solo installation!
You can either use OOS 3.2.6 or the very awesome Open Beta 7 (Don't be irritated because there is "OTA" in the filename, both are complete roms)
These are full roms officially from OnePlus.net and I'm pretty sure that they will work together with TWRP 3.0.2-22.
I suppose you simply used the wrong files. Could you tell me where you downloaded the files?
LS.xD said:
OTA = on the air update // for upgrading your android version e.g. OOS 3.2.6 --> 3.2.8 // NOT for solo installation!
You can either use OOS 3.2.6 or the very awesome Open Beta 7 (Don't be irritated because there is "OTA" in the filename, both are complete roms)
These are full roms officially from OnePlus.net and I'm pretty sure that they will work together with TWRP 3.0.2-22.
I suppose you simply used the wrong files. Could you tell me where you downloaded the files?
Click to expand...
Click to collapse
i literally downloaded those files you linked to me and still no luck. it shouldn't be a problem that I'm using android file manager to transfer the rom over to my phone right? I'm going to wipe everything and go to stock recovery and use adb push to flash stock rom. any other suggestions you got?
Anyone please? I've rooted moto g 1st and 4th grn so it's not the fact that I'm being a complete noob. I've downloaded the modified twrp flashed 3.2.6, beta 7 and cyanogenmod. No luck on anything.
jasj0410 said:
Anyone please? I've rooted moto g 1st and 4th grn so it's not the fact that I'm being a complete noob. I've downloaded the modified twrp flashed 3.2.6, beta 7 and cyanogenmod. No luck on anything.
Click to expand...
Click to collapse
Use this guide and try both methods.
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
tnsmani said:
Use this guide and try both methods.
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Click to expand...
Click to collapse
thanks for your reply. i managed to fix it. the other guy's link for a modified twrp didn't work (the custom recovery not the link) so i downloaded another and ended up installing beta 7 which worked. for future reference the link (mega unbrick) you provided me would that work with a mac?
jasj0410 said:
thanks for your reply. i managed to fix it. the other guy's link for a modified twrp didn't work (the custom recovery not the link) so i downloaded another and ended up installing beta 7 which worked. for future reference the link (mega unbrick) you provided me would that work with a mac?
Click to expand...
Click to collapse
I doubt that though there is no specific info on this .