Here's a stupid question(s). How do we backup the stock firmware, and are the fastboot commands for ADB?
---------- Post added at 02:00 PM ---------- Previous post was at 01:41 PM ----------
Is this systemless root?
Darkscan said:
Here's a stupid question(s). How do we backup the stock firmware, and are the fastboot commands for ADB?
---------- Post added at 02:00 PM ---------- Previous post was at 01:41 PM ----------
Is this systemless root?
Click to expand...
Click to collapse
Adb = Android debug bridge and is used when the phone is booted into the OS and connected to a PC
Fastboot = when the phone is booted into the bootloader and is connected to a PC
Yes it is systemless root
You can backup stock firmware with twrp RC1
Sent from my Pixel using Tapatalk
joetheshmo said:
Adb = Android debug bridge and is used when the phone is booted into the OS and connected to a PC
Fastboot = when the phone is booted into the bootloader and is connected to a PC
Yes it is systemless root
You can backup stock firmware with twrp RC1
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Why is the current version for TWRP and the previous not? Is the bootloader download mode?
Darkscan said:
Why is the current version for TWRP and the previous not? Is the bootloader download mode?
Click to expand...
Click to collapse
Current version of root for twrp and the previous not? If that's what you're asking SuperSU was developed before a working twrp was released so we had to use the boot-to-root.img
I guess bootloader mode could be considered download mode but I've never heard it called that.
Sent from my Pixel using Tapatalk
joetheshmo said:
Current version of root for twrp and the previous not? If that's what you're asking SuperSU was developed before a working twrp was released so we had to use the boot-to-root.img
I guess bootloader mode could be considered download mode but I've never heard it called that.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
I come from using only Samsung devices, I'm not sure what carries over and what doesn't. The extent of my experience is loading a ROM with download mode and flashing it with recovery. Speaking of which, why does the stock recovery just say no command when I try to launch it from fastboot?
Darkscan said:
I come from using only Samsung devices, I'm not sure what carries over and what doesn't. The extent of my experience is loading a ROM with download mode and flashing it with recovery. Speaking of which, why does the stock recovery just say no command when I try to launch it from fastboot?
Click to expand...
Click to collapse
Because you have to hit power button and volume up at the same time to get the commands to show up now
Sent from my Pixel using Tapatalk
joetheshmo said:
Because you have to hit power button and volume up at the same time to get the commands to show up now
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Well that's silly.
Darkscan said:
Here's a stupid question(s). How do we backup the stock firmware, and are the fastboot commands for ADB?
Click to expand...
Click to collapse
Why would you need to back-up the stock firmware? It is available here: https://developers.google.com/android/images
efrant said:
Why would you need to back-up the stock firmware? It is available here: https://developers.google.com/android/images
Click to expand...
Click to collapse
I suppose "where can we download the stock image" was the real question. Thanks.
Should I flash to stock first? I don't see why it would matter. All I've done is update Android and install a couple apps.
Darkscan said:
I suppose "where can we download the stock image" was the real question. Thanks.
Should I flash to stock first? I don't see why it would matter. All I've done is update Android and install a couple apps.
Click to expand...
Click to collapse
No need.
Would this be an acceptable way for me to downgrade my version? I am currently 100% stock and would like to downgrade so I can root, install TWRP, and start flashing custom ROMs.
This thread is like the twilight zone.
chadhoard said:
Would this be an acceptable way for me to downgrade my version? I am currently 100% stock and would like to downgrade so I can root, install TWRP, and start flashing custom ROMs.
Click to expand...
Click to collapse
Verizon phone? If you are on 7.1.1 you are done.
Google phone? You don't need to downgrade to do any of that.
Related
I am having issues after i flashed this Stock AT&T Deodexed JB 4.1.1 | Official AT&T 3.18.502.6 Update Rom..After htc logo at start up all i get is a blank screen and nothing else.S-off,unlocked bootloader & using TWRP here..
Need help as i am clueless right now :crying:
PS:Using At&t One x...Coming from a Nexus..Never thought that i'll get into this much trouble
Versions of TWRP after 2.3 have been known to be problematic. I'd try to install TWRP 2.3, or the official CWM.
So you mean to say that i should try 2.3 TWRP and try to flash the Rom again?
Can i run RUU after relocking the bootloader?
My PC can detect the phone in fastboot mode..
Sak3ater said:
So you mean to say that i should try 2.3 TWRP and try to flash the Rom again?
Click to expand...
Click to collapse
Precisely. What version of TWRP are you using currently? If its the latest (2.5.0.0), I'll bet this is the problem.
TWRP 2.3 seems to be the most stable version. I believe 2.3.1.1 is what you want. If you look through the TWRP thread, there are some folks that have posted links to this older version.
---------- Post added at 12:08 PM ---------- Previous post was at 12:08 PM ----------
Sak3ater said:
Can i run RUU after relocking the bootloader?
My PC can detect the phone in fastboot mode..
Click to expand...
Click to collapse
Since you are s-off, you don't need to relock the bootloader.
---------- Post added at 12:11 PM ---------- Previous post was at 12:08 PM ----------
Sak3ater said:
PS:Using At&t One x...Coming from a Nexus..Never thought that i'll get into this much trouble
Click to expand...
Click to collapse
HTC security can be a pain. But they aren't the only manufacturer with security measures. Every Android device is different. Don't blame the device. Learn, adapt and conquer.
If you have s-off you should be able to flash RUUs to your heart's content, recovery has nothing to do with it. You can try the other twrp by flashing it in fastboot then try flashing the rom again, or try another rom after transferring it in recovery
Sent from my HTC One X using xda premium
flyingriffin said:
If you have s-off you should be able to flash RUUs to your heart's content, recovery has nothing to do with it.
Click to expand...
Click to collapse
I think OP is asking about RUU as an alternative, just to get the phone back up and running again; not as a way to install the stock rooted ROM he linked.
Ok guys thanks for the suggestions...
Yeah i was using TWRP 2.5.0.0...
I had no other choice but to go for RUU...But first i did relock the bootloader & then went for the RUU..
Whole process went smoothly & i got the phone booted up fine..Today i learnt a lesson..Never ever flash anything without doing a backup first..
Yeah i know..I had Desire HD once & i dont wanna think about how i rooted it lol.& today i got stuck in another Htc device..Well it was my mistake in the first place because i forgot to take a backup of stock Rom..
Anyways i wana ask something else now..i used fastboot oem lock command to relock the bootloader..Now how to unlock it again?
htcdev method?I already have the Unlock_code file..
Also now can i flash 4.1.1 RUU this time?Right now i am on 4.0.4..
Thanks guys once again..All of you really were of great help..
Okay i can unlock it again using this command 'fastboot flash unlocktoken Unlock_code.bin'
Sak3ater said:
Okay i can unlock it again using this command 'fastboot flash unlocktoken Unlock_code.bin'
Click to expand...
Click to collapse
I don't recall the exact syntax. But you can reuse the unlock token, with the same fastboot command you unlocked with originally.
---------- Post added at 02:29 PM ---------- Previous post was at 02:27 PM ----------
Sak3ater said:
I had no other choice but to go for RUU...
Also now can i flash 4.1.1 RUU this time?Right now i am on 4.0.4..
Thanks guys once again..All of you really were of great help..
Click to expand...
Click to collapse
Why? Did you try to just flash TWRP 2.3.1.1 (or newest CWM) then re-flash the ROM as previously recommended?
Sak3ater said:
Also now can i flash 4.1.1 RUU this time?Right now i am on 4.0.4..
Click to expand...
Click to collapse
Yes.
redpoint73 said:
Why? Did you try to just flash TWRP 2.3.1.1 (or newest CWM) then re-flash the ROM as previously recommended?
.
Click to expand...
Click to collapse
No..Actually i just pressed my panic button & went directly for the RUU without wasting any time :silly:
Left the recovery as it was
If it was the recovery issue then so sad..Ive been using Twrp in Nexus 4 without any issues..I wonder why it gave me trouble here..
Now i am in search of 4.1.1 RUU
WARNING: THIS HAS BRICKED PHONES! It is suspected that having an encrypted phone causes these bricks, but that has not been confirmed. If your data partition is encrypted, it is extra important that you perform a factory reset before taking this OTA. Doing this will remove the encryption.
WARNING: INSTALLING THIS ON A LOCKED BOOTLOADER WILL ELIMINATE ALL CHANCE OF YOU EVER UNLOCKING YOUR BOOTLOADER.
If your bootloader is unlocked, it will not be re-locked after this update.
Do NOT flash this using TWRP. If you want to do that, use this version: http://forum.xda-developers.com/droid-turbo/development/rom-mcg24-251-5-100-stock-t3512949
So if you're a bad enough dude to flash this anyway, follow these instructions:
1. Backup all data on your phone. It will be lost.
2. If your bootloader is locked, make sure you are on SU4TL-49. If you aren't, take all available OTAs until you are.
3. If your bootloader is unlocked and you have TWRP installed, flash SU4TL-49 using this package: https://mega.nz/#!3xRhiaSR!KxH2Ya_BYK4zBjrxmej7dqaaDJVT1coTFJVJ5Fvb2WM
4. If you have TWRP installed on your phone, download the stock SU4TL-49 recovery here: https://mega.nz/#!L1AkQD4T!qoZIlLa-wuUBLMEi_gE574meiHd6Pehb34a-x3Gb-V8 and install it using the install image option in the install menu in TWRP. Reboot to recovery.
3. Perform a factory reset using the stock recovery menu. This will wipe all data and ensure that everything is formatted exactly as it should be.
4. Boot the phone normally and place the marshmallow update on the root of the directory that pops up when you plug in your phone.
5. Boot to recovery and at the stock recovery menu, select "apply update from sdcard."
6. Select the update and cross your fingers.
Get the update here: https://mega.nz/#!v0pRwThS!Pz9xuOSPjiOMtjlORkFrZ_ok0GTKqCfGzi5KmbDpHQ8
TheSt33v said:
WARNING: THIS HAS BRICKED PHONES! Do not use this unless you know what you're doing.
I will do my best to provide more detailed instructions later today. Good luck.
https://mega.nz/#!v0pRwThS!Pz9xuOSPjiOMtjlORkFrZ_ok0GTKqCfGzi5KmbDpHQ8
Click to expand...
Click to collapse
Are you sure that that file is the right one? It has the same version number as su4tl-49.
zys52712 said:
Are you sure that that file is the right one? It has the same version number as su4tl-49.
Click to expand...
Click to collapse
I'm positive. I seem to remember they did the same thing with SU4TL-49. The OTA was named after SU4TL-44 for some reason.
This is the stock recovery version, correct?
koftheworld said:
This is the stock recovery version, correct?
Click to expand...
Click to collapse
Correct. You install this using the sideload option in the stock recovery.
TheSt33v said:
Correct. You install this using the sideload option in the stock recovery.
Click to expand...
Click to collapse
Thanks for the info and the download! You finally brought the wall down. I'm waiting for the twrp version myself
.
Thank you, now we can see what can be done with the new modem, kernel, etc...
Looking forward to a plethora of improvements to our phones
koftheworld said:
Thanks for the info and the download! You finally brought the wall down. I'm waiting for the twrp version myself
.
Click to expand...
Click to collapse
I'm testing the TWRP version now. It should be up shortly.
EDIT: I flashed it and it seems to work fine. Uploading now. Should be up in a few hours. I'll check on it after I go run some errands real quick.
Despite having software status report official, not modified, I too got a status 7 error. Downloading again.
---------- Post added at 09:52 PM ---------- Previous post was at 09:51 PM ----------
zys52712 said:
Are you sure that that file is the right one? It has the same version number as su4tl-49.
Click to expand...
Click to collapse
This used to always be Motorola's naming scheme. New updates were named after the firmware version they replaced.
Sweet. I am going to wait till it is more stable. I do have a bad esn Turbo but I will need to unlock to bootloader to test.
Mirror for people having "quota exceeded" error at Mega
https://yadi.sk/d/AhmhE-yX32E84p
Rename to Blur_Version.24.81.5.quark_verizon.verizon.en.US.zip before use, throw in internal storage, and check for updates.
PS: I have 64Gb Employee Edition, and still had not receive update by air. What a shame, VZ! )
kitcostantino said:
Despite having software status report official, not modified, I too got a status 7 error. Downloading again.
---------- Post added at 09:52 PM ---------- Previous post was at 09:51 PM ----------
This used to always be Motorola's naming scheme. New updates were named after the firmware version they replaced.
Click to expand...
Click to collapse
Error 7? Are you trying to flash this in TWRP? Because you can't do that with this package. You need the stock recovery. I'm uploading a TWRP-friendly version now, but the internet is being slow today.
TheSt33v said:
Error 7? Are you trying to flash this in TWRP? Because you can't do that with this package. You need the stock recovery. I'm uploading a TWRP-friendly version now, but the internet is being slow today.
Click to expand...
Click to collapse
Negative. Stock recovery on a system that reports "Official". I'm at a loss.
kitcostantino said:
Negative. Stock recovery on a system that reports "Official". I'm at a loss.
Click to expand...
Click to collapse
Strange. Try reflashing SU4TL-49. If my TWRP package doesn't do it for you, use the full firmware package and do it manually with fastboot.
Installed successfully on two devices.
...
kitcostantino, did you refresh system, kernel, modem and recovery by SU4TL-49? Are you sure you didn't mess with Turbo Maxx ROMs in the past? Foreign bootloader can cause even brick, not just error. See bootloader status at fastboot mode should be " locked, status 0"
s5610 said:
Installed successfully on two devices.
...
kitcostantino, did you refresh system, kernel, modem and recovery by SU4TL-49? Are you sure you didn't mess with Turbo Maxx ROMs in the past? Foreign bootloader can cause even brick, not just error. See bootloader status at fastboot mode should be " locked, status 0"
Click to expand...
Click to collapse
lol. lawd, No. Ive been rocking status 3 for over a year.
As a tip, if anyone else with an unlocked bootloader runs into this,
what i had to do was restore my su-44 unmodified backup, OTA to SU-49, and then, after confirming my
q/e status was 0/1 i was able to update via the file in my Mega download folder. all is well now. they even added the newer version of command center. sweet. thank you all!!
It works in LOCKED BOOTLOADER??? .-.
square1230 said:
It works in LOCKED BOOTLOADER??? .-.
Click to expand...
Click to collapse
Um, I couldn't tell you.i be been unlocked since the day Sunshine could unlocked our bootloader's. What I can tell you is you should absolutely unlock that via Sunshine before you even dream of applying this update. There will never be another opportunity.
Just my
.02. This is likely the last update for this phone, and your only chance of seeing N is via custom Roms.
TWRP version up now: http://forum.xda-developers.com/droid-turbo/development/rom-mcg24-251-5-100-stock-t3512949
square1230 said:
It works in LOCKED BOOTLOADER??? .-.
Click to expand...
Click to collapse
Yes it should. See instructions in OP.
Flash using TWRP. This will flash all files in the MCG24.251-5 update except for recovery.
New features in this update that I've noticed:
-Marshmallow, aged to perfection in Verizon's own servers. Only one major release version obsolete, and with outdated security patches!
-WiFi calling (woooooo! Those custom roms just got another carrier-specific, unportable feature to compete with)
-The command center widget has been replaced with the Droid Turbo 2 version
Get it here: https://mega.nz/#!G1xg1aYa!fm2hUL7hDDVaxTAj_iPbtY61P-8VrQEvoOJiVsDtdho
Here's the stock recovery image if you want it: https://mega.nz/#!r1wDQRCJ!KHbo_Q6L-WE_VyB1x8W4FbT6PrerPEyn9H1C6VUAyf8
Flashing this rom updates the bootloader to a version that can communicate with the kernel to tell SafetyNet that it is unlocked, causing it to fail. Fret not, however, as there are two options to fix this:
OPTION 1: Flash the SU4TL-49 bootloader using the following TWRP package: https://mega.nz/#!6logEaIQ!q8qPJw65Upt38Hxiu1JyxErmwbgL7CBzuGzzPC0C9pQ
OPTION 2: Flash this patch made by @bhb27: https://www.androidfilehost.com/?fid=745425885120696423
Wipe cache and dalvik/art cache after either of these options.
NOTE that these options only fix failures due to SafetyNet checking the bootloader status. It will still fail due to root, xposed and the like. There are no known consequences or side effects to either of these options, so just pick whichever one you feel like.
If you notice weird things after you flash this rom (long boots other than the first one which is supposed to be long, random reboots, etc.) try flashing the stock recovery image and factory resetting.
If you want root, flash this version of SuperSU first, then flash whatever newer version you want: https://download.chainfire.eu/751/SuperSU/
If you have trouble flashing this, try TWRP Mod 3 instead of Mod 4.
Ouch, you have almost full flash inside archive, with bootloader too... Who is the most brave, introduce yourself ))
+ mirror
I can confirm that it works on old bootloader.
I had SULT-49 5.1 installed before and I just flashed this via TWRP. I haven't taken the OTA. It works perfectly. Thank you.
PS: My bootloader now is moto-apq8084-70.95 (2016-06-29). Do you have same version after taking OTA?
Did you have to wipe the system, data and cache first like you would with a new ROM or just dirty flash it?
Sent from my XT1254 using Tapatalk
Thanks OP
rickyblaze13 said:
Did you have to wipe the system, data and cache first like you would with a new ROM or just dirty flash it?
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
When in doubt, always wipe.
Hey everyone, what is your safetynet status with this rom? It's failing for me, and I can't figure out why.
rickyblaze13 said:
have to wipe the system, data and cache first
Click to expand...
Click to collapse
It works w/o, but, IMO, better wipe, than not. You don't need extra bugs, right )
It's completing setup now, I did a wipe after I backed up my phone. It's unlocked and rooted before I flashed the zip
Sent from my QMV7A using Tapatalk
Can we get this ULed to Dropbox or Google Drive? The Mega link and the mirror are taking forever...
Crowick said:
Can we get this ULed to Dropbox or Google Drive? The Mega link and the mirror are taking forever...
Click to expand...
Click to collapse
My google drive is full and I don't have Dropbox. But if you wanted to mirror it, I will gladly add the link to the OP.
Sure, I'll throw it up on Google Drive. Do you have just the MM stock recovery kicking around?
---------- Post added at 04:08 AM ---------- Previous post was at 03:50 AM ----------
Google Drive link to the TWRP Flashable version in your OP hosted on Mega.
https://drive.google.com/open?id=0BzQJqGBWW9ViQzFjTWJVUVZNazg
Crowick said:
Sure, I'll throw it up on Google Drive. Do you have just the MM stock recovery kicking around?
---------- Post added at 04:08 AM ---------- Previous post was at 03:50 AM ----------
Google Drive link to the TWRP Flashable version in your OP hosted on Mega.
https://drive.google.com/open?id=0BzQJqGBWW9ViQzFjTWJVUVZNazg
Click to expand...
Click to collapse
thanks for gdrive mirror
Crowick said:
Sure, I'll throw it up on Google Drive. Do you have just the MM stock recovery kicking around?
---------- Post added at 04:08 AM ---------- Previous post was at 03:50 AM ----------
Google Drive link to the TWRP Flashable version in your OP hosted on Mega.
https://drive.google.com/open?id=0BzQJqGBWW9ViQzFjTWJVUVZNazg
Click to expand...
Click to collapse
I don't. I don't know how I would get it since I need root access to get it, and I can't get root access without TWRP, and I have to overwrite the stock recovery to get TWRP.
TheSt33v said:
I have to overwrite the stock recovery to get TWRP.
Click to expand...
Click to collapse
fastboot boot TWRP.img
s5610 said:
fastboot boot TWRP.img
Click to expand...
Click to collapse
Nice! Good call.
https://mega.nz/#!r1wDQRCJ!KHbo_Q6L-WE_VyB1x8W4FbT6PrerPEyn9H1C6VUAyf8
Is anyone else having exceptionally long reboot/start times for their phone after flashing this rom?
Just the first boot after flashing
Sent from my XT1254 using Tapatalk
Thanks for that! Did anybody try to install it right over SU4TL-44? Just in case, I'm rooted, using xposed and twrp.
TheSt33v said:
Hey everyone, what is your safetynet status with this rom? It's failing for me, and I can't figure out why.
Click to expand...
Click to collapse
Perhaps this:
https://www.xda-developers.com/android-safetynet-now-reportedly-tripped-by-unlocked-bootloaders/
I just tried using AP a few hours ago and it failed with the screen in the article. OTA with unlocked bootloader.
Hi
Now i on leedroid 3.00 oreo custom rom.
I want to go back to nougat.
My device is 128/6 dugl india.
If i flash nougat ruu firmware threw download mode it will be good?
Thank you
yossim66 said:
Hi
Now i on leedroid 3.00 oreo custom rom.
I want to go back to nougat.
My device is 128/6 dugl india.
If i flash nougat ruu firmware threw download mode it will be good?
Thank you
Click to expand...
Click to collapse
If you flashed a full Oreo firmware instead of just the dsp, radio and bluetooth images you won't be able to downgrade. Firmware can only be downgraded if S-OFF, and that's not yet available on Oreo. If that's the case you are very well stranded on Oreo for the time being.
To be honest those things are quite basic knowledge you should have learned before you started tinkering with your device. Today most people just start flashing away, while I - when I started it myself back on the Desire days - read up on XDA and other forums for about three weeks to know what is to know. Still reading and learning new ways to accomplish what I want from instructions by developers, themer and many other users. Might never stop doing so until I'll stop tinkering.
Sent from my HTC U11 using XDA Labs
I flash before only bt+dsp, not full oreo firmware
yossim66 said:
I flash before only bt+dsp, not full oreo firmware
Click to expand...
Click to collapse
Download frimwore 1.27.401.11 and flash it
Because base your phone is nogat .
Before flash Unlock your phone's screen to decrypt it later restore back up
---------- Post added at 05:19 PM ---------- Previous post was at 05:15 PM ----------
I think you should go on the ruu mod by
Fastboot oem rebootRUU
Fastboot flash zip frimware.zip
(Again)
Fastboot flash zip frimware.zip
mehrdad_esmaeeli said:
Download frimwore 1.27.401.11 and flash it
Because base your phone is nogat .
Before flash Unlock your phone's screen to decrypt it later restore back up
---------- Post added at 05:19 PM ---------- Previous post was at 05:15 PM ----------
I think you should go on the ruu mod by
Fastboot oem rebootRUU
Fastboot flash zip frimware.zip
(Again)
Fastboot flash zip frimware.zip
Click to expand...
Click to collapse
If he has the wrong or to old fastboot on his PC, he won't be able to flash the RUU, due to file size restrictions in older fastboot versions. On the other hand, I'd personally prefer the SD card method instead of fastboot RUUing, as that always avoids such problems.
Sent from my HTC U11 using XDA Labs
5m4r7ph0n36uru said:
If he has the wrong or to old fastboot on his PC, he won't be able to flash the RUU, due to file size restrictions in older fastboot versions. On the other hand, I'd personally prefer the SD card method instead of fastboot RUUing, as that always avoids such problems.
Sent from my HTC U11 using XDA Labs
Click to expand...
Click to collapse
very well. So please explain step by step
Hi.
Everything o. K., i flash nougat ruu threw download mode from ext. Sd card. Everything goes well.
I am on nougat viper 1.80.
Thank you for helping.
yossim66 said:
Hi.
Everything o. K., i flash nougat ruu threw download mode from ext. Sd card. Everything goes well.
I am on nougat viper 1.80.
Thank you for helping.
Click to expand...
Click to collapse
Who to?
Please explain
I download ruu firmware, put it on root of ext. Sdcard.
Reboot the phone to download mode. In the starting of download mode, it give you to choose, vol + to flash, vol - to cancel.
The ruu firmware must rename to "2PZCIMG. Zip",
If you have twrp, you must wipe data.
May I ask why you decide to switch back?
mehrdad_esmaeeli said:
very well. So please explain step by step
Click to expand...
Click to collapse
There is a guide in the OP of my collection thread. No need to do a step by step yet again. Just got to the first page of my pinned topic in the guides section and you find it, as long as you care to read the first 5 posts carefully.
yossim66 said:
Hi.
Everything o. K., i flash nougat ruu threw download mode from ext. Sd card. Everything goes well.
I am on nougat viper 1.80.
Thank you for helping.
Click to expand...
Click to collapse
Glad it helped mate. Have fun with your U11.
Sent from my HTC U11 using XDA Labs
Sorry.you flashed ruu frimware or ruu ROM?
Why should I before flash wiped data?
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/htmlview#
This is the link to download the firmware according the model of your device.
Wipe data is to prevent errors.
yossim66 said:
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/htmlview#
This is the link to download the firmware according the model of your device.
Wipe data is to prevent errors.
Click to expand...
Click to collapse
Sorry before flash ruu ROM zip you do relocked the bootloader or not?
mehrdad_esmaeeli said:
Sorry before flash ruu ROM zip you do relocked the bootloader or not?
Click to expand...
Click to collapse
No.
My device is still unlocked.
yossim66 said:
No.
My device is still unlocked.
Click to expand...
Click to collapse
So build 401 not updated to oero yet?
mehrdad_esmaeeli said:
So build 401 not updated to oero yet?
Click to expand...
Click to collapse
I don't know, i been on viper 2.01 after flash radio, bt, dsp.
Now i return to viper 1.80 custom rom.
In custom rom you don't get official update.
???Ok I flashed ruu rom 1.27.401.11 ocndul Europe and returned to nogat successfully
Later I really not like android 7.1.1 and again returned to oero
So well . later for getting ota official again returned to nogat
I am trying to get my OP 7 Pro back to factory settings and was wondering will a factory reset do that ? I experimented with some kernels, different adb commands and my phone is acting up. I have magisk and TWRP installed and what would be the best way to go back to factory settings? I changed some system settings so I need to reset those to stock also.
My apps are working fine, should i back them up using TB and restore them or is it best to install them all from scratch ?
Search for fastboot flashable oos and run flash all.bat. You will have to flash in the bootloader mode.
Sent from my GM1911 using Tapatalk
---------- Post added at 07:41 AM ---------- Previous post was at 07:39 AM ----------
This should help
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Sent from my GM1911 using Tapatalk
jamesfitzes said:
I am trying to get my OP 7 Pro back to factory settings and was wondering will a factory reset do that ?
Click to expand...
Click to collapse
No. Factory reset is a misnomer. All it does is wipe user data. The operating system remains the same (in your case modified). Only useful in cases where user data (such as an app) is causing problems.
I suppose in theory, at some point, there may have been a stock OS on one of the A/B partition slots. But depending on what you've subsequently flashing, that may not be the case anymore.
jamesfitzes said:
I have magisk and TWRP installed and what would be the best way to go back to factory settings?
Click to expand...
Click to collapse
I agree with the previous post, to use the fastboot stock ROM.
General suggestion: For every new device I get, I consider it best practice to know how to restore to stock before messing with unlocking the bootloader, root, and other mods. And have the required files ready to go, for that matter.
It used to be, that I never did any phone mods without first making a TWRP backup of the stock ROM (which I can restore if anything went wrong). But it's so easy to flash stock images on OnePlus devices, I've mostly moved away from that thinking (as have others I've seen post to that effect).
jamesfitzes said:
My apps are working fine, should i back them up using TB and restore them or is it best to install them all from scratch ?
Click to expand...
Click to collapse
Restore apps and app data using TB is what I usually do.
zmafreak said:
Search for fastboot flashable oos and run flash all.bat. You will have to flash in the bootloader mode.
Sent from my GM1911 using Tapatalk
---------- Post added at 07:41 AM ---------- Previous post was at 07:39 AM ----------
This should help
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Sent from my GM1911 using Tapatalk
Click to expand...
Click to collapse
I'm assuming only TWRP will remain on my phone, or does that get wiped too?
jamesfitzes said:
I'm assuming only TWRP will remain on my phone, or does that get wiped too?
Click to expand...
Click to collapse
Fastboot rom will take u back to complete stock, unroot, and puts back stock recovery. the only thing that sticks is unlocked bootloader
jamesfitzes said:
I'm assuming only TWRP will remain on my phone, or does that get wiped too?
Click to expand...
Click to collapse
Flashing this stock boot ROM will also remove TWRP, you'll get stock OnePlus recovery.