Hello guys,I cannot flash TWRP. After putting 'fastboot flash recovery twrp.img' command when I select recovery it shows 'error to load recovery' or something like this in red colour. So I select fastboot and 'Start' the phone. Later when I put the phone again in recovery,I get that it is still the stock recovery.
sounds like it doesn't see the file twrp.img.
I usually go with
Flashboot flash recovery "C:\FILE LOCATION"
"C:\FILE LOCATION" being a click and drag to the CMD Prompt, if your TWRP.IMG is in a different folder than your fastboot files.
Michajin said:
sounds like it doesn't see the file twrp.img.
I usually go with
Flashboot flash recovery "C:\FILE LOCATION"
"C:\FILE LOCATION" being a click and drag to the CMD Prompt, if your TWRP.IMG is in a different folder than your fastboot files.
Click to expand...
Click to collapse
My all files are in same folder.
maybe the .img is corrupted? I'm assuming you are bootloader unlocked...
Michajin said:
maybe the .img is corrupted? I'm assuming you are bootloader unlocked...
Click to expand...
Click to collapse
I have download the image from official twrp.me site. And yes I have unlocked the bootloader months ago.
Can you just boot TWRP, not flash it?
fastboot boot TWRP.img
Replace TWRP.img with your actual file.
acejavelin said:
Can you just boot TWRP, not flash it?
fastboot boot TWRP.img
Replace TWRP.img with your actual file.
Click to expand...
Click to collapse
Ok,but after that? Actually sir,months ago u told me to flash it and go to recovery so I was following ur steps. Boot is temporary,so after boot how to flash twrp permanently to replace stock recovery?
Atanu Mukherjee said:
Ok,but after that? Actually sir,months ago u told me to flash it and go to recovery so I was following ur steps. Boot is temporary,so after boot how to flash twrp permanently to replace stock recovery?
Click to expand...
Click to collapse
Yes, but you are saying it doesn't work... So I was asking if you can boot it to verify the image works.
acejavelin said:
Yes, but you are saying it doesn't work... So I was asking if you can boot it to verify the image works.
Click to expand...
Click to collapse
Ok sir. And if work then what to do next? How to flash twrp in simple process?
Atanu Mukherjee said:
Ok sir. And if work then what to do next? How to flash twrp in simple process?
Click to expand...
Click to collapse
If that works than your image file itself is good... Once TWRP is loaded, copy the twrp.img file to the device and flash it with TWRP.
I know it seems counter-intuitive to install TWRP from TWRP, but it is just running in RAM, so you can flash the IMG to the recovery partition with TWRP.
My assumption is something fastboot or drivers is not correct... using this method would bypass those issues, you could also bypass these issues by using Linux as your OS since it does not require drivers like Windows does to talk to an Android device. If you can successfully flash but NOT load recovery, I would assume you have a defective device.
Of course there always the possibility of a bad cable or USB port on the computer though...
acejavelin said:
If that works than your image file itself is good... Once TWRP is loaded, copy the twrp.img file to the device and flash it with TWRP.
I know it seems counter-intuitive to install TWRP from TWRP, but it is just running in RAM, so you can flash the IMG to the recovery partition with TWRP.
My assumption is something fastboot or drivers is not correct... using this method would bypass those issues, you could also bypass these issues by using Linux as your OS since it does not require drivers like Windows does to talk to an Android device. If you can successfully flash but NOT load recovery, I would assume you have a defective device.
Of course there always the possibility of a bad cable or USB port on the computer though...
Click to expand...
Click to collapse
'Flash twrp with twrp' means just flash it like flashing rom? Copy it to sd card,swipe to flash?
When I cheked the drivers were working or not by putting command,those are working as it gave me back ph serial no. And mine is original windows. Upgradeed it to 10. Is there any issue for windows version?
And the cable,yes I dont know is it defective or not. But u know sir,1st time when I put 'adb devices' it could not recognise my device. Then I pull the usb off and put it again then works.
Atanu Mukherjee said:
'Flash twrp with twrp' means just flash it like flashing rom? Copy it to sd card,swipe to flash?
When I cheked the drivers were working or not by putting command,those are working as it gave me back ph serial no. And mine is original windows. Upgradeed it to 10. Is there any issue for windows version?
And the cable,yes I dont know is it defective or not. But u know sir,1st time when I put 'adb devices' it could not recognise my device. Then I pull the usb off and put it again then works.
Click to expand...
Click to collapse
Boot TWRP, then copy the twrp.img file to the device.
From the main menu in TWRP, select Install, change to Images by tapping the button on the bottom-right of screen, and navigate to the twrp.img file then select it and a new menu will open asking you if it is a Recovery Image or Boot Image, select Recovery Image, then swipe to flash. Once complete go to main menu, select Reboot, then Recovery.
I can't really answer your questions specific to Windows... I don't own a Windows PC and my only access to Windows is via a Virtualbox VM. Sorry.
acejavelin said:
Boot TWRP, then copy the twrp.img file to the device.
From the main menu in TWRP, select Install, change to Images by tapping the button on the bottom-right of screen, and navigate to the twrp.img file then select it and a new menu will open asking you if it is a Recovery Image or Boot Image, select Recovery Image, then swipe to flash. Once complete go to main menu, select Reboot, then Recovery.
Click to expand...
Click to collapse
Ok sir.thank u very much. But sir as u know,I may ask u again some silly ques in future regarding these methods.
One more silly ques,if I boot twrp and from there if I flash lineage,will this process work? And what I have to clear before flashing rom?
Atanu Mukherjee said:
Ok sir.thank u very much. But sir as u know,I may ask u again some silly ques in future regarding these methods.
One more silly ques,if I boot twrp and from there if I flash lineage,will this process work? And what I have to clear before flashing rom?
Click to expand...
Click to collapse
Before flashing a new ROM I always wipe user data, system, and caches, then flash ROM and Gapps. Make sure to backup to your SD card first.
acejavelin said:
Before flashing a new ROM I always wipe user data, system, and caches, then flash ROM and Gapps. Make sure to backup to your SD card first.
Click to expand...
Click to collapse
Yes u told me before to make a nandroid backup.
Do I need to download Gapps? I already backed up apps to lptp. Sir,Lineage or AICP which one is better? I get a max 4.10hrs of SOT with wifi now. Its poor I think as I dont play game. In 2g its lower & 3g sucks totally.
Atanu Mukherjee said:
Yes u told me before to make a nandroid backup.
Do I need to download Gapps? I already backed up apps to lptp. Sir,Lineage or AICP which one is better? I get a max 4.10hrs of SOT with wifi now. Its poor I think as I dont play game. In 2g its lower & 3g sucks totally.
Click to expand...
Click to collapse
Do you need Gapps? No, unless you want any Google applications, such as the Play Store. If you don't care about Google apps and services you can skip them and use an alternative.
Honestly... 4hr is pretty good, I never get better than 3.5 hours of SOT over 18 hours off-charger with no gaming.
No third party ROM will give you better battery life than stock. Moto may not be good at a lot of things, but they can optimize a ROM better than anybody. The only way you will get better battery life than stock is to use a third party kernel and scale everything way back, trading off performance significantly.
The Pure/Style's main battery abuser is the screen... it is beautiful, but it sucks battery like nobody's business, and no third party ROM or kernel can really have any effect on that. Your battery usage due to radio connectivity is kind of locked too, no matter the ROM, the radio firmware is the same.
acejavelin said:
Do you need Gapps? No, unless you want any Google applications, such as the Play Store. If you don't care about Google apps and services you can skip them and use an alternative.
Honestly... 4hr is pretty good, I never get better than 3.5 hours of SOT over 18 hours off-charger with no gaming.
No third party ROM will give you better battery life than stock. Moto may not be good at a lot of things, but they can optimize a ROM better than anybody. The only way you will get better battery life than stock is to use a third party kernel and scale everything way back, trading off performance significantly.
The Pure/Style's main battery abuser is the screen... it is beautiful, but it sucks battery like nobody's business, and no third party ROM or kernel can really have any effect on that. Your battery usage due to radio connectivity is kind of locked too, no matter the ROM, the radio firmware is the same.
Click to expand...
Click to collapse
I have already backed up google apps to my sd cards and pc. So i can install them again,what I do after every hard reset.
Actually as N claims more battery saver than M,so I thought if any of those roms gv bttr bttry bckup. Before I got 5hrs with wifi.now it drops to 4.10 with a good off charger time. And if I use continuously with little sleep,thn 4.30hrs with wifi only.not in 3g,2g(though my home is low network coverage area.red 3g signal)
Atanu Mukherjee said:
I have already backed up google apps to my sd cards and pc. So i can install them again,what I do after every hard reset.
Actually as N claims more battery saver than M,so I thought if any of those roms gv bttr bttry bckup. Before I got 5hrs with wifi.now it drops to 4.10 with a good off charger time. And if I use continuously without little sleep,thn 4.30hrs with wifi only.not in 3g,2g(though my home is low network coverage area.red 3g signal)
Click to expand...
Click to collapse
Your call... When I change ROMs I never restore apps, too many issues with conflicts and other stuff. Experience has taught me to reinstall from Play Store every time, maintain online backups for data and settings and other stuff (contacts, photos, etc), and run a lean device.
As far as restoring Google apps, you can restore most of the apps, but you will want to flash the pico or nano Gapps at a minimum in order to get the framework and basic libraries installed into system, or else your backed up Google apps won't work anyway.
acejavelin said:
Your call... When I change ROMs I never restore apps, too many issues with conflicts and other stuff. Experience has taught me to reinstall from Play Store every time, maintain online backups for data and settings and other stuff (contacts, photos, etc), and run a lean device.
As far as restoring Google apps, you can restore most of the apps, but you will want to flash the nano Gapps at a minimum in order to get the framework and basic libraries installed into system, or else your backed up Google apps won't work anyway.
Click to expand...
Click to collapse
Ok then I will download Gapps also. Btw sir is there news when offifial 7 comes for style? I was waiting for long but after that moto USA tweet I feel little sad.its too late.
And one more think which I dont like is the cpu. I checked and get that CPU 0 to CPU 4 all are working but not the CPU 5. The 6th core is sleeping all the time as I dont play any game. Cpu4 also sleeps normal time. So basically for me its a quad core. :crying:
Atanu Mukherjee said:
Ok then I will download Gapps also. Btw sir is there news when offifial 7 comes for style? I was waiting for long but after that moto USA tweet I feel little sad.its too late.
And one more think which I dont like is the cpu. I checked and get that CPU 0 to CPU 4 all are working but not the CPU 5. The 6th core is sleeping all the time as I dont play any game. Cpu4 also sleeps normal time. So basically for me its a quad core. :crying:
Click to expand...
Click to collapse
Cores are throttled or taken off-line based on load and temperature... The BIG cores (one or both) only come online if the threshold of CPU load reaches a certain level, otherwise they pretty much stay offline as they use much more power than the four LITTLE cores do. This is literally called big.LITTLE architecture, read up on it if you want to know more (I am not an ARM/CPU expert), but if you are not using your big cores, it is probably because they are not needed.
As far as when "official" Nougat will be available? No word, last I heard was Moto Germany said it was pushed back to May sometime... TBH, I am kind of think chances are decent that Lenovo to come up with some lame excuse and just cancel the upgrade, so I wouldn't hold my breath for it.
Related
I'm currently running @Danvdh / @ktoonsez Google Play Edition on my S4 (I9505 jfltexx) .. and have been for a while. Since they've just released a new CM based rom I was going to give it a shot. So, first things first I went to reboot into recovery to do a backup of my current ROM.
However, instead of recovery mode I end up in download mode. Figuring I'd pressed the wrong option on the advanced reboot menu I rebooted and tried again. Ended up in DL mode again. It doesn't matter what method I used to try and get to recovery I can't... it constantly goes to DL mode. I used to be able to get to revocery without a problem (TWRP).
My question is, is this a common occurance and would reflashing TWRP (using Nandroid Manager - the way I did it originally) fix my problem.. or is there a more fundamental issue at play here. For what it's worth Nandroid Manager detects that i'm running TWRP 2.7.0.1 already
Just try to reflash it with Odin.
Or you could try entering it from the terminal:
su
reboot recovery
Lennyz1988 said:
Just try to reflash it with Odin.
Click to expand...
Click to collapse
I would but I'm concerned there may be an underlying issue that would potentially brick my device if i tried a reflash. How can it be that it suddenly won't reboot into recovery anymore when previously it did ?
update:
I've just tried your sugestion via terminal emu which has the same result unfortunately. However, I noticed that after entering the su command it returns [email protected] in the command prompt. I would have expected this to be [email protected]jfltexx right? I'm assuming now that flashnig the Google Edition ROM has changed what my device is reporting itself as ? (forgive me me if I'm talking bollocks at this point.. I'm just guessing)
So, now if I flash the twrp that already have (for jfltexx) will this cause a problem ?
If I had to guess, and I'm just shooting in the dark here, but this sounds like an error in the ROM. And I'd bet that changing the rom solves the problem.
What happens if you try to reboot into Download mode? Does it go to Download mode? The only time I've experiences this, download and recovery were reveresed in the ROM I was using. So trying to boot to 1 always gave me the other. So I'd try to reboot into Download mode and see if that puts you in recovery.
If all else fails, use Odin to return to stock. It will not brick your phone because of this.
davey.lad said:
I've just tried your sugestion via terminal emu which has the same result unfortunately. However, I noticed that after entering the su command it returns [email protected] in the command prompt. I would have expected this to be ro[email protected]jfltexx right? I'm assuming now that flashnig the Google Edition ROM has changed what my device is reporting itself as ? (forgive me me if I'm talking bollocks at this point.. I'm just guessing)
So, now if I flash the twrp that already have (for jfltexx) will this cause a problem ?
Click to expand...
Click to collapse
Sounds to me like you are already running a jftexx recovery with a jgedlte ROM. That probably is the source of the problem - Since the rom replaces the entire system, it also replaces the basic stats the device has about itself. If the Google Play edition is different in hardware, I would suspect it would also damage the kernel function (for example by asking an amount of ram the phone does not have).
I would just install a jftexx rom. These things are pretty sensitive when it comes to versions.
NetaA said:
Sounds to me like you are already running a jftexx recovery with a jgedlte ROM. That probably is the source of the problem - Since the rom replaces the entire system, it also replaces the basic stats the device has about itself. If the Google Play edition is different in hardware, I would suspect it would also damage the kernel function (for example by asking an amount of ram the phone does not have).
I would just install a jftexx rom. These things are pretty sensitive when it comes to versions.
Click to expand...
Click to collapse
The google version is the same hardware. Its the same device with a different rom installed. The google rom is totally interchangeable with other s4s. All it is is an aosp rom.
This is not his problem.
Sent from your phone. You should be more careful where you leave that thing.
Skipjacks said:
The google version is the same hardware. Its the same device with a different rom installed. The google rom is totally interchangeable with other s4s. All it is is an aosp rom.
This is not his problem.
Sent from your phone. You should be more careful where you leave that thing.
Click to expand...
Click to collapse
Alright, thanks for the info.
Since I'm not really familiar with the process of getting into recovery mode, the help I can offer is limited.
Good luck
Thanks for the updates guys.. sorry about the delayed reply - been on holiday.
In the end I just used Nandroid Manager to reflash the original twrp.img that I had.
Sorted. Guess I was worried about nothing.
cheers :good:
Hello my fellow XDA Members. I am stuck in a tight spot and after reading and re-reading some things the situation doesn't look very promising. I hope this is the moment that Karma shows up and I can get some help on this. Here it goes.
Specs - LG G2 D801 Variant > TWRP V2.8.3.1 > NO OS Currently
I was running Cloudy G3 Rom smoothly and got bored and decided to flash that new rom that is a 5.0 Rom all variants. Did the usual back ups and flashed it. Something happened when I flashed the rom. It went through the Aroma installer and then said "successful" but stuck in a bootloop. I tried it again and nothing happened. Then I tried to wipe everything again and started getting an E: Cannot mount (data or system I forget which as that error went away after I completely formatted data, wiped everything and reflashed Cloudy Stock. )
> Cloudy stock bootlooped and nothing is happening in TWRP. I Am using the USB OTG method of getting files on the phone and getting it charged but anytime I try to do anything (flash a rom, an older version of TWRP) it just immediately restarts TWRP and thats that. I have No OS at all.
> I tried to use one of the methods to get into download mode and flash a stock KDZ but the phone acts like it is going into DL mode (shows the little blue transition screen) but never gets into the ACTUAL download mode where the PC or flash tool can recognize it.
So in a nutshell > No OS > I can get into TWRP but it does nothing > No Download Mode > Don't want a new phone > Don't want to take it apart and try to short circuit anything if possible. LOL.
I am totally stuck here. I am done alot of work and even helped friends and family out with their devices over the years. I am just not sure if I need to consider it a done deal and get a new phone or maybe one of you guys know of something easy and obvious (please let it be the latter) I am missing. Thanks for any help you can offer. I Will be standing by.
Have you tried to reflash bootloader? If not, do that and reflash cloudy right away
wisefreakz said:
Have you tried to reflash bootloader? If not, do that and reflash cloudy right away
Click to expand...
Click to collapse
I haven't thought about flashing a bootloader. How would I flash the bootloader if I can not the phone into either DL mode and or TWRP doesn't do anything either? Is a bootloader file just a flashable file like any other .zip file?
jcnbama said:
I haven't thought about flashing a bootloader. How would I flash the bootloader if I can not the phone into either DL mode and or TWRP doesn't do anything either? Is a bootloader file just a flashable file like any other .zip file?
Click to expand...
Click to collapse
@jcnbama
Have you tried this or this?
euphoria360 said:
@jcnbama
Have you tried this or this?
Click to expand...
Click to collapse
The first one I can not do as I do not have any knowledge at all of Ubuntu, Linux, or any of that. It would take forever to get a working knowledge of that software in order to get things going again. I would probably just have to either take it to a cellphone repair shop or get another phone before I could do the first link.
I have not tried the second one but it is a viable option. I was looking at it online and trying to talk myself down from having to do that. I would reallllllllly rather not have to take my phone apart if I can keep from so that's kind of what this post is all about. Just trying to see if anyone knows of ANYTHING else before I go taking apart my phone.
Can you describe more about "twrp doesnt do anything"?
Does twrp boot up?
Can u see/wipe partitions?
Can u install any rom in twrp? Does it finish?
euphoria360 said:
Can you describe more about "twrp doesnt do anything"?
Does twrp boot up?
Can u see/wipe partitions?
Can u install any rom in twrp? Does it finish?
Click to expand...
Click to collapse
TWRP boots and I can go into wipe, advanced wipe, and format data and it says it's successful. I can use file manager and move items back and forth from USB OTG. If I try to flash anything it just reboots TWRP immediately so I can't install any .zip files at all.
My guess is that your bootloader is damaged.
The only option i can see for you is that Ubuntu thing i shared with you. So, lets stop acting lazy and do what needs to be done. Dont scare since there is nothing to loose. LG G2 is unbrikable
Booting up ubuntu or any other linux os is so easy. And there is nothing much to learn. Trust me.
Go to ubuntu website and download their newest iso file. Burn it on dvd and boot it up. You dont have to install it, just choose "live mode" and it boots up. Just like that. Then yiu can proceed with tutorial mentioned above and it shouldnt take more than an hour from you. Its all typing some commands in terminal (remember CMD in windows!).
Just make sure to download the files mentioned in that tutorial before proceeding.
euphoria360 said:
My guess is that your bootloader is damaged.
The only option i can see for you is that Ubuntu thing i shared with you. So, lets stop acting lazy and do what needs to be done. Dont scare since there is nothing to loose. LG G2 is unbrikable
Booting up ubuntu or any other linux os is so easy. And there is nothing much to learn. Trust me.
Go to ubuntu website and download their newest iso file. Burn it on dvd and boot it up. You dont have to install it, just choose "live mode" and it boots up. Just like that. Then yiu can proceed with tutorial mentioned above and it shouldnt take more than an hour from you. Its all typing some commands in terminal (remember CMD in windows!).
Just make sure to download the files mentioned in that tutorial before proceeding.
Click to expand...
Click to collapse
First of all calling people lazy is not nice. I'm not lazy I am trying to play it safe. I wouldn't want to brick it to the point to where I don't even have recovery and it can not even be charged any longer. I have Ubuntu on my desktop upstairs. I have used it a little. It's not that I am completely ignorant to Ubuntu I am just a total novice. Also the issue described in that post doesn't exactly match my situation. I am not in a black screen. It's more like a bootloop that I can not get out of because TWRP is not doing what it needs to do and I can not flash TWRP a ROM or get into DL mode at all. Also that post says,
"VERY IMPORTANT!!!!!!! You must use the img files that correspond to the ROM you have installed before getting the problem to avoid breaking your phone."
I don't have a rom on my phone soooo...
You didn't answer my question well. If on TWRP you can finish installing rom without any error, and you keep coming to twrp after restarts, that's another situation. Try this:
http://forum.xda-developers.com/showthread.php?t=2451696
But if you cant even finish install in twrp (twrp gives you errors or just restarts before giving you "successful", either you have problem in rom you try to flash or you need to build everything up from start.
That lazy thing was for encouraging you to do it.
And you cant brick your device. There is always a way on G2.
For img files: find them from last stock rom that was working on your phone.
Deleted
This method here seemed pretty straightforward to upgrade to Nougat: https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
I was already unlocked so I figured I just need to flash the "Full" package then the "TWRP" package. TWRP is working, the bootloader still shows as unlocked in fastboot mode, but trying to boot just shows a Linux penguin and nothing else!
I just cleared everything in TWRP to see if that was somehow the issue then reboot, and TWRP says no OS installed! HOW?!
All this happened because I'm unclear on everything, and instead of a yes/no answer I get mocked. Someone please help.
Can you Boot in Fastboot?
When yes . load a Original Firmware update.zip and extract recovery.img from this . Do the recovery.img in Minimal adb and fastboot , open a command windows .
Type: fastboot flash recovery recovery.img ,before this boot the phone in fastboot mode.
After the flash recovery ,boot the phone in the recovery with Volume down (tick them 1 or two times ) reboot ist with power.
Put a SD Card in the Phone with the update zip in root folder of the SD Card.
In recovery tick with Volume down to the Point update via SD Card and wait the Process ist finished.
tester2017 said:
Can you Boot in Fastboot?
When yes . load a Original Firmware update.zip and extract recovery.img from this . Do the recovery.img in Minimal adb and fastboot , open a command windows .
Type: fastboot flash recovery recovery.img ,before this boot the phone in fastboot mode.
After the flash recovery ,boot the phone in the recovery with Volume down (tick them 1 or two times ) reboot ist with power.
Put a SD Card in the Phone with the update zip in root folder of the SD Card.
In recovery tick with Volume down to the Point update via SD Card and wait the Process ist finished.
Click to expand...
Click to collapse
I have access to fastboot mode. However I'm still confused as to what is going on.
At least I've figured out where it goes wrong, at the TWRP step. The "no OS detected" made no sense so I tried flashing using the same method but just the "Full" package first. It eventually does boot and it appears Android 7 is working.
The bootloader shows as unlocked. However when I install the TWRP package after, TWRP is restored but then the phone is bricked and TWRP says no OS detected. I'm not sure if this is because I clicked "allow modifications" and if so why that causes it to go wrong and what I missed. I tried flashing TWRP manually using fastboot mode in case something was wrong with that EDL package, and the result is the same, after installing TWRP and clicking allow modifications the OS is no longer detected.
What am I missing? I must have missed a step.
ok. go to twrp and format data to ext 4 then flash new and restart.
tester2017 said:
ok. go to twrp and format data to ext 4 then flash new and restart.
Click to expand...
Click to collapse
When go to "Format Data", enter yes to allow it, it fails and says:
"mkfs.f2fs -t 0 /dev/block/sda9 process ended with
ERROR: 255
Unable to wipe Data.
Unable to format to remove encryption
Upadting partition details...
Failed to mount '/data' (device or resource busy)
... done"
Even if that went through I'm unsure what you mean flash new? Flash a new what?
When I enter repair/change it says the file system is ext4 anyway.
Well I tried starting at that point again since I didn't allow modifications in TWRP this time, and it actually booted Android but then asks for a password... what?
So something about allowing modifications in TWRP seems to be the culprit, but then I'm unsure why it would ask for a password to start the device when it boots after, it's obviously encrypted.
Flashing back to the "Full" package yet again to restore it working.
Edit: I thought double posts would be auto-merged...
Edit 2: "Format Data" left my device encrypted and the only way around it was a factory reset!
Edit 3: I read over the instructions in the TWRP thread again and I think I've found what I missed. If I don't update this thread again by tomorrow that means I've figured it out and everything should be fine.
Thank you everyone who tried to help.
Can you please give me instructions of what you did to upgrade to Nougat, I'm like you when started the upgrade on B29 Unlocked and rooted. I like the way of EDL process but It is a little vague and I don't want to brick my phone. Thanks in advance.
Cyrus D. said:
Well I tried starting at that point again since I didn't allow modifications in TWRP this time, and it actually booted Android but then asks for a password... what?
So something about allowing modifications in TWRP seems to be the culprit, but then I'm unsure why it would ask for a password to start the device when it boots after, it's obviously encrypted.
Flashing back to the "Full" package yet again to restore it working.
Edit: I thought double posts would be auto-merged...
Edit 2: "Format Data" left my device encrypted and the only way around it was a factory reset!
Edit 3: I read over the instructions in the TWRP thread again and I think I've found what I missed. If I don't update this thread again by tomorrow that means I've figured it out and everything should be fine.
Thank you everyone who tried to help.
Click to expand...
Click to collapse
romeoh said:
Can you please give me instructions of what you did to upgrade to Nougat, I'm like you when started the upgrade on B29 Unlocked and rooted. I like the way of EDL process but It is a little vague and I don't want to brick my phone. Thanks in advance.
Click to expand...
Click to collapse
Hi...I ran into your original issue and I believe it's related to dm-verify. For anyone that runs into this again, try flashing a dm-verify disabling zip and see if it'll boot again. This was the only way I could get the phone to boot after upgrading to nougat...not sure why this is an issue though as (I think) I had the stock bootstack in place along with stock System files.
Here is a link to the dm-verify disabling tool I used:
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
flyer_andy said:
Hi...I ran into your original issue and I believe it's related to dm-verify. For anyone that runs into this again, try flashing a dm-verify disabling zip and see if it'll boot again. This was the only way I could get the phone to boot after upgrading to nougat...not sure why this is an issue though as (I think) I had the stock bootstack in place along with stock System files.
Here is a link to the dm-verify disabling tool I used:
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Click to expand...
Click to collapse
This is clearly posted in the TWRP thread.
flyer_andy said:
Hi...I ran into your original issue and I believe it's related to dm-verify. For anyone that runs into this again, try flashing a dm-verify disabling zip and see if it'll boot again. This was the only way I could get the phone to boot after upgrading to nougat...not sure why this is an issue though as (I think) I had the stock bootstack in place along with stock System files.
Here is a link to the dm-verify disabling tool I used:
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Click to expand...
Click to collapse
Thanks, already read the TWRP thread and found what I was missing.
romeoh said:
Can you please give me instructions of what you did to upgrade to Nougat, I'm like you when started the upgrade on B29 Unlocked and rooted. I like the way of EDL process but It is a little vague and I don't want to brick my phone. Thanks in advance.
Click to expand...
Click to collapse
I used the EDL method in the end. Part of the reason I set that up to begin with was just in case in the future I brick something, I'll have the ability to recover from anything prepared.
The step I missed which resulted in a brick was installing SuperSU (since I wanted root anyway, or you can disable dm-verity as the other fellow posted here) after allowing TWRP to be able to do modifications. Then I ended up with more bricks because I used SuperSU 2.79-SR2 and SR3, I thought it was fine since SR2 is what I was using with Marshmallow, apparently not, you have to use a non-SR version of 2.79 with Nougat.
So in summary, from EDL mode I:
1 - Installed the "Full" EDL package.
2 - Installed the "TWRP" EDL package, or you can flash it from Fastboot mode which might be more convenient since you'll have to restart EDL mode after flashing the first package to get it working/ready to flash in EDL mode again.
3 - Gave TWRP permission to do modifications and immediately (without rebooting/starting which would result in a brick) installed SuperSU 2.79 (non-SR), then rebooted (this could take a few mins as it says and can bootloop a few times).
If you said no to permissions for SuperSU and it's not giving you the option again you can reflash SuperSU then reboot to bootloader then reboot to recovery, that should make it show the option again. And in case you're not aware, to make changes to system files and such permanent when you have root, you have to enter a command in TWRP's terminal emulator or ADB shell. I think it was "reboot disemmcwp", it may need "SU" in front if you're doing it through an ADB shell in Windows, I'm not sure. Not quotes of course. Search the forums to find out for sure, it had to be in a guide somewhere.
Edit: Just to be clear, for step 2, when I said "or you can flash it from Fastboot" I meant TWRP in general, not the TWRP EDL package.
Cyrus D. said:
Thanks, already read the TWRP thread and found what I was missing.
I used the EDL method in the end. Part of the reason I set that up to begin with was just in case in the future I brick something, I'll have the ability to recover from anything prepared.
The step I missed which resulted in a brick was installing SuperSU (since I wanted root anyway, or you can disable dm-verity as the other fellow posted here) after allowing TWRP to be able to do modifications. Then I ended up with more bricks because I used SuperSU 2.79-SR2 and SR3, I thought it was fine since SR2 is what I was using with Marshmallow, apparently not, you have to use a non-SR version of 2.79 with Nougat.
So in summary, from EDL mode I:
1 - Installed the "Full" EDL package.
2 - Installed the "TWRP" EDL package, or you can flash it from Fastboot mode which might be more convenient since you'll have to restart EDL mode after flashing the first package to get it working/ready to flash in EDL mode again.
3 - Gave TWRP permission to do modifications and immediately (without rebooting/starting which would result in a brick) installed SuperSU 2.79 (non-SR), then rebooted (this could take a few mins as it says and can bootloop a few times).
If you said no to permissions for SuperSU and it's not giving you the option again you can reflash SuperSU then reboot to bootloader then reboot to recovery, that should make it show the option again. And in case you're not aware, to make changes to system files and such permanent when you have root, you have to enter a command in TWRP's terminal emulator or ADB shell. I think it was "reboot disemmcwp", it may need "SU" in front if you're doing it through an ADB shell in Windows, I'm not sure. Not quotes of course. Search the forums to find out for sure, it had to be in a guide somewhere.
Click to expand...
Click to collapse
Many thanks body, As you said using EDL mode is great to unbrake your phone from any state plus it reminds me with Odin that's why I like this way it's very simple, but as you know this is not Samsung phone and it has so many complications. ???
romeoh said:
Many thanks body, As you said using EDL mode is great to unbrake your phone from any state plus it reminds me with Odin that's why I like this way it's very simple, but as you know this is not Samsung phone and it has so many complications.
Click to expand...
Click to collapse
No problem. I threw in an edit to my last post to clarify point 2 in case you thought I meant you can flash the EDL package from Fastboot mode, I meant TWRP in general. In case you forgot the command to use in the ADB shell it's "fastboot flash recovery FileName.img" (twrp-3.0.4-1-ailsa_ii.img in my case).
If you already had the "reboot disemmcwp"/"SU reboot disemmcwp" step done you don't need to do it again.
And just some general information for you regarding my experience with Nougat so far:
1 - When I started it I selected Canadian English as my language. This apparently disables ZTE voice functions, or Nougat is missing it in general. It's missing from the menus and when I hold the back key it said "Only English and Spanish supported". Piss poorly done as usual, ZTE, since the pronunciation of Canadian and American English is nearly identical with very few exceptions, might as well have left American English enabled for voice commands. So I went into the menu and selected just "English" as my system language, and now the option to set Canadian English is missing entirely, and voice functions are still missing. Holding the back key just results in nothing now instead of the "Only English and Spanish supported" message. So I'm saying I don't know if ZTE voice functions are still there, someone else can answer this, or I guess you'll find out.
2 - Google's Timely alarm app (and possibly other alarms) still don't work properly and will be off by several minutes, so I'm stuck using the default sucky clock app until I find something else that works.
3 - The default apps are all still the exact same trash. If you really want to use the AKM "32 bit" (truncated to 16 bit output) Hi-Fi DAC and amp you're still stuck with the garbage laggy default music app, which now has some sort of bonus lag/stutter. People claiming that you can use the DAC with something like PowerAmp are sadly mistaken, that sounds so different and lower quality than when using the stock music app and even says it's using the SD 820's 24 bit DAC when set to Hi-Fi output. There's even a ridiculous rumour going around that the Axon 7 doesn't have the SD 820's DAC which is retarded, ZTE can't pick and choose components of SoCs supplied by Qualcomm, they just buy some of their stock of what's already made. It's definitely in there, whether or not it's enabled is another story.
4 - Battery life is worse, this is at least partly because there is no Xposed support for Nougat yet so I can't enable the Greenify module to allow really aggressive dozing and dozing on the go (which I thought Nougat was supposed to support?). It could also be partly due to my battery being rapidly degraded from Daydream mode being a firey hell inferno. It heated my battery up to 48C and over 42C in other cases even with my best efforts to keep it cool by enabling Ultra Power Saving Mode (which Daydream may be overriding) and shoving in aluminium foil to act as a heatsink. All phones from reports so far overheat horribly when using Daydream, especially the Pixel XL. It's not surprising that the Axon 7 rapidly overheats as well considering it literally uses the battery as a heatsink; a heatpipe carries heat from the SoC to the battery. I would have not bought the A7 if I knew this.
Edit: I forgot -
5 - ZTE locker no longer allows browsing all of their past content, only what they allow per day, which so far for me has only been the same crap and never anything new. Too bad, I liked some of their old content, though it was all 1080p and not 1440p. Oh well.
Cyrus D. said:
No problem. I threw in an edit to my last post to clarify point 2 in case you thought I meant you can flash the EDL package from Fastboot mode, I meant TWRP in general. In case you forgot the command to use in the ADB shell it's "fastboot flash recovery FileName.img" (twrp-3.0.4-1-ailsa_ii.img in my case).
If you already had the "reboot disemmcwp"/"SU reboot disemmcwp" step done you don't need to do it again.
And just some general information for you regarding my experience with Nougat so far:
1 - When I started it I selected Canadian English as my language. This apparently disables ZTE voice functions, or Nougat is missing it in general. It's missing from the menus and when I hold the back key it said "Only English and Spanish supported". Piss poorly done as usual, ZTE, since the pronunciation of Canadian and American English is nearly identical with very few exceptions, might as well have left American English enabled for voice commands. So I went into the menu and selected just "English" as my system language, and now the option to set Canadian English is missing entirely, and voice functions are still missing. Holding the back key just results in nothing now instead of the "Only English and Spanish supported" message. So I'm saying I don't know if ZTE voice functions are still there, someone else can answer this, or I guess you'll find out.
2 - Google's Timely alarm app (and possibly other alarms) still don't work properly and will be off by several minutes, so I'm stuck using the default sucky clock app until I find something else that works.
3 - The default apps are all still the exact same trash. If you really want to use the AKM "32 bit" (truncated to 16 bit output) Hi-Fi DAC and amp you're still stuck with the garbage laggy default music app, which now has some sort of bonus lag/stutter. People claiming that you can use the DAC with something like PowerAmp are sadly mistaken, that sounds so different and lower quality than when using the stock music app and even says it's using the SD 820's 24 bit DAC when set to Hi-Fi output. There's even a ridiculous rumour going around that the Axon 7 doesn't have the SD 820's DAC which is retarded, ZTE can't pick and choose components of SoCs supplied by Qualcomm, they just buy some of their stock of what's already made. It's definitely in there, whether or not it's enabled is another story.
4 - Battery life is worse, this is at least partly because there is no Xposed support for Nougat yet so I can't enable the Greenify module to allow really aggressive dozing and dozing on the go (which I thought Nougat was supposed to support?). It could also be partly due to my battery being rapidly degraded from Daydream mode being a firey hell inferno. It heated my battery up to 48C and over 42C in other cases even with my best efforts to keep it cool by enabling Ultra Power Saving Mode (which Daydream may be overriding) and shoving in aluminium foil to act as a heatsink. All phones from reports so far overheat horribly when using Daydream, especially the Pixel XL. It's not surprising that the Axon 7 rapidly overheats as well considering it literally uses the battery as a heatsink; a heatpipe carries heat from the SoC to the battery. I would have not bought the A7 if I knew this.
Edit: I forgot -
5 - ZTE locker no longer allows browsing all of their past content, only what they allow per day, which so far for me has only been the same crap and never anything new. Too bad, I liked some of their old content, though it was all 1080p and not 1440p. Oh well.
Click to expand...
Click to collapse
Omg bro, To be honest I hate the software experience on that phone. It is the only thing that turning me off from it. I played a little with my brother's S7 edge the other day, and believe me the software experience is extraordinary. However I noticed that the S7 edge overheats a lot too without even using the daydream. In my opinion I think Axon 7 lacks in hardware wise a bigger battery and the support of the new RCS messaging feature, and in software wise a whole new developed system.
So here's the story..
Everything was running beautifully, I got bootloader unlocked, TWRP installed and rooted with Magisk, even a few modules and of course my favorite Viper4android... All without having to ask any questions. Super silky smooth thanks to all the amazing devs here that made it so easy ?
... The problem, I'm not incredibly familiar with Magisk hide and everything was going phenomenally but low and behold the play store had to show up with an warning notification that Viper could be harmful... It wouldn't allow me to dismiss it, so like the amazing genius I am I remember that Magisk hide is used to hide things from the store...Rrrright?
Not sure if this matters but Viper was a system app at the time and yeah I TRIED to hide it ??
... thought everything was cool for about 30 seconds
... phone shut down, booted to recovery
.... So I thought, ehhh no big deal I'll just do A WIPE and restore my back up
restored the back up.... Seemed to anyhow, went through the complete process.
I went to reboot system and NADA just boots back to TWRP for a moment anyhow...
So then I'm thinking oh well I'll just go back in to restore my backup AGAIN... NOTHING'S THERE!
I go to SDcard and it's nothing but a bunch of folders with jumbled alphanumerics
Fuhhh...
At some point it stopped letting me reboot TWRP, not sure how to differentiate when, but it just loops straight back to Fastboot now Everytime and I can see my device in the computer but I try fastboot boot twrp.img and it says something like failed can't recognize boot.
Edit: (I guess this has to be in the form of a question)... What do I do?
Causical said:
So here's the story..
Everything was running beautifully, I got bootloader unlocked, TWRP installed and rooted with Magisk, even a few modules and of course my favorite Viper4android... All without having to ask any questions. Super silky smooth thanks to all the amazing devs here that made it so easy
... The problem, I'm not incredibly familiar with Magisk hide and everything was going phenomenally but low and behold the play store had to show up with an warning notification that Viper could be harmful... It wouldn't allow me to dismiss it, so like the amazing genius I am I remember that Magisk hide is used to hide things from the store...Rrrright?
Not sure if this matters but Viper was a system app at the time and yeah I TRIED to hide it
... thought everything was cool for about 30 seconds
... phone shut down, booted to recovery
.... So I thought, ehhh no big deal I'll just do A WIPE and restore my back up
restored the back up.... Seemed to anyhow, went through the complete process.
I went to reboot system and NADA just boots back to TWRP for a moment anyhow...
So then I'm thinking oh well I'll just go back in to restore my backup AGAIN... NOTHING'S THERE!
I go to SDcard and it's nothing but a bunch of folders with jumbled alphanumerics
Fuhhh...
At some point it stopped letting me reboot TWRP, not sure how to differentiate when, but it just loops straight back to Fastboot now Everytime and I can see my device in the computer but I try fastboot boot twrp.img and it says something like failed can't recognize boot.
Edit: (I guess this has to be in the form of a question)... What do I do?
Click to expand...
Click to collapse
Hi there. So the warning from the play store was actually from "play protect" which you can disable IN the play store in the left pull out menu. Not something you need Magisk hide for. Now the folders with jumbled characters are because of encryption. When you restored your backup, the device's encryption went wack on you, which happens with this device if you install or restore anything with a previous security patch than you currently have. It's annoying, but you either have to format your data entirely, or (what I recommend) use the MSM Download tool that can be found here in the guide section of this forum. Use the T-Mobile version of the tool if you have a T-Mobile variant of the device, and the global version if you have the global version of the device. What you could try to back up your important stuff, boot TWRP with fastboot using "fastboot boot [TWRPfilename]" and you might be able to plug in your device to a PC to save stuff first. But yeah, MSM tool is your best bet, that has happened to me before, and the play protect option in the play store is what you should have disabled instead of using Magisk for it.
H4X0R46 said:
Hi there. So the warning from the play store was actually from "play protect" which you can disable IN the play store in the left pull out menu. Not something you need Magisk hide for. Now the folders with jumbled characters are because of encryption. When you restored your backup, the device's encryption went wack on you, which happens with this device if you install or restore anything with a previous security patch than you currently have. It's annoying, but you either have to format your data entirely, or (what I recommend) use the MSM Download tool that can be found here in the guide section of this forum. Use the T-Mobile version of the tool if you have a T-Mobile variant of the device, and the global version if you have the global version of the device. What you could try to back up your important stuff, boot TWRP with fastboot using "fastboot boot [TWRPfilename]" and you might be able to plug in your device to a PC to save stuff first. But yeah, MSM tool is your best bet, that has happened to me before, and the play protect option in the play store is what you should have disabled instead of using Magisk for it.
Click to expand...
Click to collapse
Dang I was kind of afraid of that MSM tool thing, I'm going to have to do a little reading on that. That's one thing I've never done on an Android for sure.
Thank you
... On another note conveniently my Laptop keys ZXCVM just stopped working WTF! Not cool timing, I just bought it.
Causical said:
So here's the story..
Everything was running beautifully, I got bootloader unlocked, TWRP installed and rooted with Magisk, even a few modules and of course my favorite Viper4android... All without having to ask any questions. Super silky smooth thanks to all the amazing devs here that made it so easy ?
... The problem, I'm not incredibly familiar with Magisk hide and everything was going phenomenally but low and behold the play store had to show up with an warning notification that Viper could be harmful... It wouldn't allow me to dismiss it, so like the amazing genius I am I remember that Magisk hide is used to hide things from the store...Rrrright?
Not sure if this matters but Viper was a system app at the time and yeah I TRIED to hide it ??
... thought everything was cool for about 30 seconds
... phone shut down, booted to recovery
.... So I thought, ehhh no big deal I'll just do A WIPE and restore my back up
restored the back up.... Seemed to anyhow, went through the complete process.
I went to reboot system and NADA just boots back to TWRP for a moment anyhow...
So then I'm thinking oh well I'll just go back in to restore my backup AGAIN... NOTHING'S THERE!
I go to SDcard and it's nothing but a bunch of folders with jumbled alphanumerics
Fuhhh...
At some point it stopped letting me reboot TWRP, not sure how to differentiate when, but it just loops straight back to Fastboot now Everytime and I can see my device in the computer but I try fastboot boot twrp.img and it says something like failed can't recognize boot.
Edit: (I guess this has to be in the form of a question)... What do I do?
Click to expand...
Click to collapse
have something similar like you and my phone every time go to fastboot so what I have done is installed rom from fastboot and it worked like a charm my phone was up and running. Little notice if you going to install rom via fastboot you will get some error message but just ignore it and wait till phone reboot and it will erase all data on the phone.
Here is the link if you chose to try just read all before on page one
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Sipi1302 said:
have something similar like you and my phone every time go to fastboot so what I have done is installed rom from fastboot and it worked like a charm my phone was up and running. Little notice if you going to install rom via fastboot you will get some error message but just ignore it and wait till phone reboot and it will erase all data on the phone.
Here is the link if you chose to try just read all before on page one
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Click to expand...
Click to collapse
thank you all for your replies, however I'm beginning to get really frustrated. I'm trying to use the MSM tool and how do I frickin run an .exe when the damn thing is a .rar format, the instructions under that thread are not particularly descriptive. Do I extract it? do I have to run something in a window somewhere? if my device is in EDL and the port shows Qualcomm HS-USB QDLoader 9008 (COM6) is that good?
OMG!
Causical said:
OMG!
Click to expand...
Click to collapse
MSM tool isn't too bad really. You're issue there is most likely a corrupted download. Redownload the entire tool and try to extract it again. Let me know what happens!
H4X0R46 said:
MSM tool isn't too bad really. You're issue there is most likely a corrupted download. Redownload the entire tool and try to extract it again. Let me know what happens!
Click to expand...
Click to collapse
I redownloaded that same one at least twice now... Am I doing right by using WinRAR? I just downloaded from official site the trial version.
This has got me wanting to repeatedly dropkick myself in the larynx.
....#slowassWiFi
Causical said:
I redownloaded that same one at least twice now... Am I doing right by using WinRAR? I just downloaded from official site the trial version.
Click to expand...
Click to collapse
Yes, you are doing it right.
I would use 7zip but winRAR is fine. Dont know why someone would be using that in this day and age... but hey, it works...
I have also read other random threads that says that the file is corrupt. If you cant get a good download let me know and I will upload my collection of files. Send me a PM if you need me to upload. It wont be for a couple hours though...
Apparently they're all corrupt. I just downloaded 9.0.11 after doing .12 first and I'm getting the same errors in WinRAR
Yeah good call on 7-zip, I uninstalled winrar... complete garbage, all changing my folder icons without my consent and stuff.
Causical said:
Yeah good call on 7-zip, I uninstalled winrar... complete garbage, all changing my folder icons without my consent and stuff.
Click to expand...
Click to collapse
Was it Ok with 7Zip?
Scott said:
Was it Ok with 7Zip?
Click to expand...
Click to collapse
No lol, but it's a little more clear that the file is corrupt I suppose ?
Edit: Hey I'm going to try the recommendation of the other guy ^^up there with the fastboot ROM, I don't think it will work because I don't think fastboot is recognizing my boot, but guess we'll see... I'm just curious do you recommend doing the flash-all-partitions-fastboot.bat? Or the "Big One" flash-all-partitions.bat...I feel like I'm on the verge of really slipping deeper into the abyss here.
Here I go... Hope you reply within next 30 seconds lol
Edit: Ho-Ly poop I think that was the single most terrifying event of my life... IT WORKED! I used Mauro's fastboot ROM technique....uuggghhh
I think I used flash all bat and that work for me but phone was reset to factory settings after that
---------- Post added at 03:29 AM ---------- Previous post was at 03:23 AM ----------
Causical said:
Here I go... Hope you reply within next 30 seconds lol
Edit: Ho-Ly poop I think that was the single most terrifying event of my life... IT WORKED! I used Mauro's fastboot ROM technique....uuggghhh
Click to expand...
Click to collapse
im glad it worked, have the same filing as you when I brick phone and then make him work again.
Sipi1302 said:
I think I used flash all bat and that work for me but phone was reset to factory settings after that
Click to expand...
Click to collapse
That's alright, I'll reset everything. Thanks A Bunch dude, that was scary.
Remember kids, Magisk hide is bad mmmkay, don't do Magisk hide!
... All this because I didn't want a pesky warning notification gyollee dude, that allowed me to get absolutely nothing else done on my day off work lol.
Causical said:
That's alright, I'll reset everything. Thanks A Bunch dude, that was scary.
Remember kids, Magisk hide is bad mmmkay, don't do Magisk hide!
Click to expand...
Click to collapse
you welcome, Im glad I could help.Now you will know for the next time hehe:laugh:
I think MSM tool would still be valuable to know how it works, but let's hope I don't need it.
At least you are up and running!
But yeah, the MSM tool is pretty easy to use. If you ever used ODIN on a Samsung phone it would be familiar.
I want to install TWRP as my recovery I've tried at least four different versions that are listed here and a few others from other links:
https://forum.xda-developers.com/t/...p-for-oneplus-8-8-pro-unified-stable.4101313/
I'm not having driver issues anymore so I'm working with adb and fastboot fine. All commands are going through fine and I've tried flashing to recovery_a and recovery_b. Factory resetting doesn't resolve the issue. Every walkthrough I find I get to says flash then boot to TWRP but every time I flash it qualcomm dumps and every time I boot to it it qualcomm dumps.
Is there something corrupted in my recovery I need to wipe somehow? If so how do I wipe it because the only command I found online that would run was fastboot -w and that didn't fix the issue either.
Honestly really annoying at this. This is my 4th OnePlus phone and I've never had so many issues flashing it.
Edit:
I have also tried to do whatever steps are needed to go back to base stock and OS and it doesn't seem to work either. Any help would be appreciated.
Edit 2:
I did it. For anyone who finds this thread in the future the MSM tool did finally work. This is the video I used in the end
(I muted it.) and the first few starts it failed. I went into the properties of the MSM exe and under compatibility checked ran as admin. I also did install the qualcomm driver at some point way before this so not sure if that helped. The MSM tool still didn't work until I started it, turned my phone off, held both volume buttons (not the power) while plugging the phone in. All the stuff online I saw had people starting the program at this point but mine had started already and was in a "waiting for device" state when it worked.
What a lifesaver. Won't be messing around with this again until TWRP is available.
Because you are unable to flash phone's Stock ROM take phone to authorized service center and let them fix it.
Flash stock recovery. TWRP is but compatible with OOS11 for 8/Pro.
Edit: not
Lossyx said:
Flash stock recovery. TWRP is but compatible with OOS11 for 8/Pro.
Click to expand...
Click to collapse
I have had so much trouble figuring that out too. Do you have a good link for that? I can't find an easy way to do it. I've seen people recommend the msmdownloadtool but every time I use it it doesn't pick up my phone.
I've settled with Lineage OS and Gapps until I figure out more.
TheFloppyDisk said:
I have had so much trouble figuring that out too. Do you have a good link for that? I can't find an easy way to do it. I've seen people recommend the msmdownloadtool but every time I use it it doesn't pick up my phone.
I've settled with Lineage OS and Gapps until I figure out more.
Click to expand...
Click to collapse
Meant to say it's **not** compatible with Android 11 yet.
Lossyx said:
Meant to say it's **not** compatible with Android 11 yet.
Click to expand...
Click to collapse
Sorry if I wasn't clear either. I was wondering if you have a good resource for flashing the stock again. I haven't been able to myself.
TheFloppyDisk said:
Sorry if I wasn't clear either. I was wondering if you have a good resource for flashing the stock again. I haven't been able to myself.
Click to expand...
Click to collapse
The same way to flashed TWRP.
fastboot flash recovery recovery_a and _b.
In the future, you should not flash both slots, just flash without specifying _a or _b.
Recovery image can be obtained here;
Android Dumps / oneplus / oneplus8pro · GitLab
GitLab Enterprise Edition
dumps.tadiphone.dev
Although i am not sure which OOS version you use, so you might have to change branch
Lossyx said:
The same way to flashed TWRP.
fastboot flash recovery recovery_a and _b.
In the future, you should not flash both slots, just flash without specifying _a or _b.
Recovery image can be obtained here;
Android Dumps / oneplus / oneplus8pro · GitLab
GitLab Enterprise Edition
dumps.tadiphone.dev
Although i am not sure which OOS version you use, so you might have to change branch
Click to expand...
Click to collapse
I hate to be this much of a noob about it but I see a recovery file listed in the link you sent. Is that the recovery I flash? And if so after flashing is this branch also a stock rom? I've been trying for a while now just to get back to the basic oxygen that comes with the phone but it's been a nightmare for me and it feels like no resource I find fully explains it.
TheFloppyDisk said:
I hate to be this much of a noob about it but I see a recovery file listed in the link you sent. Is that the recovery I flash? And if so after flashing is this branch also a stock rom? I've been trying for a while now just to get back to the basic oxygen that comes with the phone but it's been a nightmare for me and it feels like no resource I find fully explains it.
Click to expand...
Click to collapse
If you want OOS back / new start, best way is really to use MSM. Haven't really used it, so can't help you much. There are tutorials online / YouTube though
Lossyx said:
If you want OOS back / new start, best way is really to use MSM. Haven't really used it, so can't help you much. There are tutorials online / YouTube though
Click to expand...
Click to collapse
Gotcha. Unfortunately I haven't been able to get MSM to recognize my phone yet but I guess I will keep working on it and see what I can do. Thanks for your help.
TheFloppyDisk said:
Gotcha. Unfortunately I haven't been able to get MSM to recognize my phone yet but I guess I will keep working on it and see what I can do. Thanks for your help.
Click to expand...
Click to collapse
It is very sensitive to which USB port you use. For some people only USB2.0 works, for me USB3 works fine as long as it's chipset USB3. The second ASMedia controller doesn't work.
Also, use original cable, and switch off the phone completely, get MSM to the point it's waiting for device so start the download before connecting phone, then while holding the volume keys connect the USB cable and it should instantly start flashing.