Database Develop

[Q] Flashing a ROM with Unlocked Bootloader but S-ON. Possible ?

Hi
I have a HTC one m7 which went in Boot loop just like that. It was working perfectly some time back., just rebooted and won.t me back now. I had the latest stock OS 4.4 with sense 6 developer edition on it with no tamperig.
I tried many time wipe cache and factory reset. Nothing helped. Finally someone here suggested i do a unlock bootloader -> custom recovery -> custom rom -> s-off -> Load my Stock RUU.
Problem with above is i have done the unlock boot loader and install twrp recovery. But to do a s-off i need my device to read adb commands. As its in boot loop i cannot. Can i flash a custom binary which can run on S-on just to run those commands of firewater to make s-off.
I am stuck here. Please help to revive my device and reach me back to stock 4.4 sense 6 .
Also i came to know as i was on latest version if i flash a older RUU with S-On it can brick my device. True ?
And something else i noticed , i read some 4-5 thread in last two days complaining of HTC going in boot loop just like that.
HTC to blame ? Is this some issue with htc ???
Thanks

anirudhgargi said:
Hi
I have a HTC one m7 which went in Boot loop just like that. It was working perfectly some time back., just rebooted and won.t me back now. I had the latest stock OS 4.4 with sense 6 developer edition on it with no tamperig.
I tried many time wipe cache and factory reset. Nothing helped. Finally someone here suggested i do a unlock bootloader -> custom recovery -> custom rom -> s-off -> Load my Stock RUU.
Problem with above is i have done the unlock boot loader and install twrp recovery. But to do a s-off i need my device to read adb commands. As its in boot loop i cannot. Can i flash a custom binary which can run on S-on just to run those commands of firewater to make s-off.
I am stuck here. Please help to revive my device and reach me back to stock 4.4 sense 6 .
Also i came to know as i was on latest version if i flash a older RUU with S-On it can brick my device. True ?
And something else i noticed , i read some 4-5 thread in last two days complaining of HTC going in boot loop just like that.
HTC to blame ? Is this some issue with htc ???
Thanks
Click to expand...
Click to collapse
as mentioned in the previous post you made, you need to install a custom ROM first in order to boot back into your phone. You have unlocked the bootloader and installed TWRP recovery. Now you need to sideload the ROM by adb sideload commands in order to boot the phone up again
Do not run an earlier RUU.zip as you will brick your phone. Firewater needs a working ROM, there are no ways to bypass this

Flash ARHD 81 or Insert Coin or Team Venom Rom
Step 1. Unlock Bootloader and Install TWRP 2.7.x.x recovery. Don't install Twrp v2.8.x.x, wont work with any roms.
Step 2. Boot to Recovery.
Step 3. Mount the system using twrp. I am assuming that you don't have custom rom on your phone storage.
Note that TWRP v2.7.x.x wont mount the phone storage. v2.7 and above always had issues. My recommendation is to install TWRP v2.8 for temporary purposes. Now mount the phone storage copy any rom you downloaded to the system.
Step 4. Assuming that you install TWRP v2.8 to copy rom files to phone storage. Boot to bootloader again and Install TWRP using fastboot. Command: "Fastboot flash recovery openrecovery-twrp-2.7.1.1-m7.img"
Step 5. Reboot to recovery. WIPE DATA, CACHE, DALVIK CACHE, SYSTEM > Install Rom.
Note do not wipe "internal storage." Otherwise you have to go back and start again with installing twrp v2.8, then copy rom...
Step 6: follow the steps.
IMO ARHD 81 is a stable rom, provides better battery life. If you like Sense then stick with this Rom, if you want Stock Android aka AOSP then try aospa legacy, CM, SlimKAT, AOSB and many more.
Moreover, i haven't found RUU for Sense 6 KK4.4.3, if you do please provide me a link as well.

As of yet there are no links for 4.4.3 RUU's. Haven't been released anywhere. He just needs a working ROM to get s off again. Nice step by step guide tho

Not able to copy my custom rom in phone.
stovie_steve said:
As of yet there are no links for 4.4.3 RUU's. Haven't been released anywhere. He just needs a working ROM to get s off again. Nice step by step guide tho
Click to expand...
Click to collapse
Hi , i got stuck with a minor issue. I am with 2.8 TWRP was trying to mount the phone . i am using a mac os with the Android Revolution Rom downloaded in place. .
m7 gets mount i could see the phone in android fie transfer ( MTP utility for mac) . I selected the System and data and cache back in the twrp mount page. I can write and create some folders etc.
Issue is when i start to copy the Custom ROM file to the phone ( any folder) it says 'filexxx.zip not copy'. However i copied a small file (1mb). It was copied ok.
Any idea what is the issue with the file size restrictions?
I tried the adb sideload that also fails with saying device not found. Wanna avoid sideload, as sideload will execute also the zip after copying . I Want to change the recovery file as the recovery file need to changed to a twrp 2.7xx before installation starts. I hear that V2.8 is not compatible with lot of roms.

anirudhgargi said:
Hi , i got stuck with a minor issue. I am with 2.8 TWRP was trying to mount the phone . i am using a mac os with the Android Revolution Rom downloaded in place. .
m7 gets mount i could see the phone in android fie transfer ( MTP utility for mac) . I selected the System and data and cache back in the twrp mount page. I can write and create some folders etc.
Issue is when i start to copy the Custom ROM file to the phone ( any folder) it says 'filexxx.zip not copy'. However i copied a small file (1mb). It was copied ok.
Any idea what is the issue with the file size restrictions?
I tried the adb sideload that also fails with saying device not found. Wanna avoid sideload, as sideload will execute also the zip after copying . I Want to change the recovery file as the recovery file need to changed to a twrp 2.7xx before installation starts. I hear that V2.8 is not compatible with lot of roms.
Click to expand...
Click to collapse
You are better using the 2.7.xx version of TWRP. Sounds like you could also be using out of date adb drivers. You can download the most up to date ones by downloading the latest Google sdk
Try fixing the above and sideloading again

No luck ! Fastboot mode also not getting detected now.
stovie_steve said:
You are better using the 2.7.xx version of TWRP. Sounds like you could also be using out of date adb drivers. You can download the most up to date ones by downloading the latest Google sdk
Try fixing the above and sideloading again
Click to expand...
Click to collapse
Hello i tried updating the drivers from the sdk itself. No luck . The device won't just get detect as adb device. Tried cache clear. factory reset , reboot pc and phone. And Loaded other twrp recovery images ( 2.8 and 2.7).
Today tried with a window machine also. I thought some issue with Mac + adb drivers. But with window also No luck.
Also one more issue, my phone fastboot has stopped detecting om pc and mac. Tried everything almost.
It was like just working some time back, i loaded twrp 2.7.x and booted to recovery for adb sideload.
Adb Sideload failed as mentioned above on this window machine also ... so i was like this adb is not working at all.
But then i thought of loading 2.8 twrp and see if mount (mtp) works, i can send the ROM to device this way. But for that when i booted to fastboot. Fastboot just stopped detecting in PC (window and mac)
I wonder can the Fastboot mode ( within Hboot bootloader) can go corrupt ?
I am sure drivers are there, usb cable is fine, usb port in HTC one is fine. It just show "fastboot ac" not "fastboot usb" . No activity in the device manager when i plug surprisingly !! (can't see Android phone there " . Afterall it was working ok when i loaded the recovery image of 2.7.1.
Also , can the recovery mess up with the fastboot mode ? i am still s-on and in boot loop.
-Thanks,

anirudhgargi said:
Hello i tried updating the drivers from the sdk itself. No luck . The device won't just get detect as adb device. Tried cache clear. factory reset , reboot pc and phone. And Loaded other twrp recovery images ( 2.8 and 2.7).
Today tried with a window machine also. I thought some issue with Mac + adb drivers. But with window also No luck.
Also one more issue, my phone fastboot has stopped detecting om pc and mac. Tried everything almost.
It was like just working some time back, i loaded twrp 2.7.x and booted to recovery for adb sideload.
Adb Sideload failed as mentioned above on this window machine also ... so i was like this adb is not working at all.
But then i thought of loading 2.8 twrp and see if mount (mtp) works, i can send the ROM to device this way. But for that when i booted to fastboot. Fastboot just stopped detecting in PC (window and mac)
I wonder can the Fastboot mode ( within Hboot bootloader) can go corrupt ?
I am sure drivers are there, usb cable is fine, usb port in HTC one is fine. It just show "fastboot ac" not "fastboot usb" . No activity in the device manager when i plug surprisingly !! (can't see Android phone there " . Afterall it was working ok when i loaded the recovery image of 2.7.1.
Also , can the recovery mess up with the fastboot mode ? i am still s-on and in boot loop.
-Thanks,
Click to expand...
Click to collapse
Sounds also like a driver issue
Try instling HTC sync to get the up to date HTC drivers and retry. Use different usb ports (2.0 preferably) and different cables. If it's saying fastboot ac then the phone is not being detected correctly, so it's a driver issue
You can also try manually installing the driver by searching for I think the Google naked driver

[GUIDE]Steps To Revert back to Lollipop 5.1.1 Stock After Marshmallow Update

Ever since google rolled out the marshmallow update I have been plagued with battery issues to an extent where it was dropping to half from a full charge within a day even on standby . Having looked at many fixes on this forum which including rooting and replacing the kernel or simply turning core features like wifi off.For some users it may be tedious and it may risk bricking their device . So I decided to go back to stock 5.1.1 until google fixes the battery issues.
Before Proceeding Backup Your Data.
Follow the steps below to roll back to stock 5.1.1 along with stock recovery.
1) Download the Android One Toolkit http://forum.xda-developers.com/cro...oolbox-android-one-toolkit-one-click-t3030165.
2) Download 5.1 OTA update from here : http://forum.xda-developers.com/cro...l/ota-micromax-official-ota-captured-t3058879
3) Download 5.1.1 OTA update from here: http://forum.xda-developers.com/cro...al/ota-canvas-a1-5-1-1-captured-link-t3121543
4) Place both the OTA zips in root of SD CARD.Note the names of both versions.
5) Open Android One Toolkit.Enable USB Debugging . Unlock the Bootloader.
6) Install CWM Recovery from the Toolkit.
7) Reboot to Recovery.
8) Make a full backup of your existing ROM in case something goes wrong.
9) Erase Data , Cache & Dalvik Cache.
10) Select install zip from ext-sd card select the 5.1 OTA zip.
11) After completion reboot your phone. Update will also replace CWM with stock recovery ( No Worries)
12) Keep Wifi Off & Data connection off to prevent marshmallow being downloaded again during Setup . Setup your device Offline.
13) Reboot to stock recovery using key combo Power + Volume Up.If you get "No command" in stock recovery continue pressing Power+Volume Up until menu appears.
14) Select Update from SD Card . Select 5.1.1 OTA zip.
15) Reboot phone and you will now be on 5.1.1. Along with Stock Recovery.
16)Once Data or Wifi is enabled you may get update prompts of Marshmallow in notification. Disable update notification by long pressing on notification and goto settings from there you can disable it.
17) You may Relock Bootloader if You Wish from toolkit
Disclaimer:
I Am Not Responsible For Any Damage Caused To your Phone.
Credits to:
@anil293 for his toolkit
@varun.chitre15 For His Recoveries
@ghpranav & @GokulNC for OTA links.

Draining continues
Can't go to CWM even I unlocked bootloader I flash ed CWM but still on NO COMMAND

ranj9660 said:
Can't go to CWM even I unlocked bootloader I flash ed CWM but still on NO COMMAND
Click to expand...
Click to collapse
FIrst check in android toolkit in list devices if your device is mentioned.
After flashing CWM boot straight to recovery. Booting to OS may cause the recovery to be overwritten by STOCK recovery.

Yeah my device
My device mentioned too . I clicked list devices and I got device id then only I unlocked bootloader and installed custom recovery also but I can't enter to customer recovery ?

ranj9660 said:
My device mentioned too . I clicked list devices and I got device id then only I unlocked bootloader and installed custom recovery also but I can't enter to customer recovery
Click to expand...
Click to collapse
After installing CWM from toolkit don't restart to OS. Press Power+Volume Up until recovery select option appears.

But now
(First i have to thank you to giving me the instruction now its worked) Doesn't show zip files. What to do? I wiped dalvik cache, data and cache partition but doesn't show zip file ? got another problem

Can I use Twrp?
What's wrong using TWRP instead of CWM? I do not have windows. I have Linux(Ubuntu). From linux I can flash anything. But the problem is I don't have the latest recovery image of CWM for Android one devices. (The CWM project has been abandoned anyway).
My only concern is to get back the stock recovery after flashing 5.1.

The process you told to revert back to Lollipop after Marshmallow update, have u done that, are u succeeded.
Please tell me, because after Marshmallow update i got a severe battery drain and over heat in My Spice Dream Uno MI-498.
When my phone is in ideal it is okay but when i started using it then the issue started.
After revert back to Lollipop according to your process is there any IMEI problem.
Is it possible after flashing the ROM in Custom Recovery can it revert back to Stock Recovery.

androidone14 said:
The process you told to revert back to Lollipop after Marshmallow update, have u done that, are u succeeded.
Please tell me, because after Marshmallow update i got a severe battery drain and over heat in My Spice Dream Uno MI-498.
When my phone is in ideal it is okay but when i started using it then the issue started.
After revert back to Lollipop according to your process is there any IMEI problem.
Is it possible after flashing the ROM in Custom Recovery can it revert back to Stock Recovery.
Click to expand...
Click to collapse
Just flash away the STOCK ROM and you'll get everything STOCK
---------- Post added 5th November 2015 at 00:06 ---------- Previous post was 4th November 2015 at 23:57 ----------
ranj9660 said:
(First i have to thank you to giving me the instruction now its worked) Doesn't show zip files. What to do? I wiped dalvik cache, data and cache partition but doesn't show zip file �� got another problem
Click to expand...
Click to collapse
Please give more details or send a pic of what is going wrong for you. You have to put the zip file in your external card and flash from install from external SD card if that's what you are asking for.

wickedspice said:
Ever since google rolled out the marshmallow update I have been plagued with battery issues to an extent where it was dropping to half from a full charge within a day even on standby . Having looked at many fixes on this forum which including rooting and replacing the kernel or simply turning core features like wifi off.For some users it may be tedious and it may risk bricking their device . So I decided to go back to stock 5.1.1 until google fixes the battery issues.
Before Proceeding Backup Your Data.
Follow the steps below to roll back to stock 5.1.1 along with stock recovery.
1) Download the Android One Toolkit http://forum.xda-developers.com/cro...oolbox-android-one-toolkit-one-click-t3030165.
2) Download 5.1 OTA update from here : http://forum.xda-developers.com/cro...l/ota-micromax-official-ota-captured-t3058879
3) Download 5.1.1 OTA update from here: http://forum.xda-developers.com/cro...al/ota-canvas-a1-5-1-1-captured-link-t3121543
4) Place both the OTA zips in root of SD CARD.Note the names of both versions.
5) Open Android One Toolkit.Enable USB Debugging . Unlock the Bootloader.
6) Install CWM Recovery from the Toolkit.
7) Reboot to Recovery.
8) Make a full backup of your existing ROM in case something goes wrong.
9) Erase Data , Cache & Dalvik Cache.
10) Select install zip from ext-sd card select the 5.1 OTA zip.
11) After completion reboot your phone. Update will also replace CWM with stock recovery ( No Worries)
12) Keep Wifi Off & Data connection off to prevent marshmallow being downloaded again during Setup . Setup your device Offline.
13) Reboot to stock recovery using key combo Power + Volume Up.If you get "No command" in stock recovery continue pressing Power+Volume Up until menu appears.
14) Select Update from SD Card . Select 5.1.1 OTA zip.
15) Reboot phone and you will now be on 5.1.1. Along with Stock Recovery.
16)Once Data or Wifi is enabled you may get update prompts of Marshmallow in notification. Disable update notification by long pressing on notification and goto settings from there you can disable it.
17) You may Relock Bootloader if You Wish from toolkit
Disclaimer:
I Am Not Responsible For Any Damage Caused To your Phone.
Credits to:
@anil293 for his toolkit
@varun.chitre15 For His Recoveries
@ghpranav & @GokulNC for OTA links.
Click to expand...
Click to collapse
Thanks!!!
But is there any way to roll back without rooting the phone.
i don't want to my phone now.

anupamdubey said:
Thanks!!!
But is there any way to roll back without rooting the phone.
i don't want to my phone now.
Click to expand...
Click to collapse
Downgrade is possible only through unlocking bootloader and then flashing custom recovery which shall help you flash the LP firmware.
Rooting has nothing to do with this.

wickedspice said:
After installing CWM from toolkit don't restart to OS. Press Power+Volume Up until recovery select option appears.
Click to expand...
Click to collapse
it gets rebooted automatically after flashing cwm recovery but still no command.

stan1996 said:
it gets rebooted automatically after flashing cwm recovery but still no command.
Click to expand...
Click to collapse
Yes , thats the tricky part as os tries to restore stock recovery on boot. Here's what you need to do. On your computer when the toolkit prompt says " completed /finished" prevent rebooting by quickly pressing power+volume up. Once you get the selection prompt select recovery by volume up and confirm selection by volume down.
You have to do this only once , After you successfully boot to cwm it will prevent os from re writing recovery

wickedspice said:
Yes , thats the tricky part as os tries to restore stock recovery on boot. Here's what you need to do. On your computer when the toolkit prompt says " completed /finished" prevent rebooting by quickly pressing power+volume up. Once you get the selection prompt select recovery by volume up and confirm selection by volume down.
You have to do this only once , After you successfully boot to cwm it will prevent os from re writing recovery
Click to expand...
Click to collapse
thank you so much:angel::angel::angel:

I am getting stuck on unlock bootloader, it freezes and does nothing ? any ideas guys ? I really need to get away from marshmallow, hot phone, no 4g etc etc

[NEED HELP] I need help. and will deletehis asap

i have a symphony roar a50 (Bangladesh). it was running everything stock and updated with twrp 2.8.7.0 without root. bootloader was unlocked.
i was trying to root the device with the AIO from this thread:
http://forum.xda-developers.com/cro.../android-one-toolkit-unlocks-relocks-t3294448
the phone suddenly rebooted in the middle of the process and was stuck in a bootloop. i tried to factory reset it but it still didn't work. was still on boot loop.
then i tried to flash the appropriate stock firmware but that didn't help it wont boot. stuck on the boot logo for 1.5 hrs. then tried CM13 nightlies and the cyanpop roms. still nothing.
i am currently in a state of shock as this is a fairly a new phone and i am to travel to Chittagong in ~11 hours.
please help

don't you take a backup ?
and don't you wipe every thing before flashing the cm13 ?

mithun mpk said:
don't you take a backup ?
and don't you wipe every thing before flashing the cm13 ?
Click to expand...
Click to collapse
yes i had a nandroid backup. but twrp says it is corrupt or some reason. and yes i wiped everything before cm13

downgrade twrp2.8.7 to 2.8.4.... 2.8.7 has problem with backup and recovery

https://www.androidfilehost.com/?fid=24389512218018336 twrp 2.8.8.x beta 3
btw this thread is wrong section

I too Had the same Problem once as I Tried Rooting My Android One through the same method as u did, So for fixing it I prefer that U FLASH The Stock MM ROM for Ur Device through STOCK Recovery ( Remember to Wipe Cache and Data b4 Flashing ) AND then ur Device mst be Fixed ( This method worked for me ) And Dude if u want to root Ur Device Follow This Method : -
1) FLASH TWRP RECOVERY
2) Reboot into Recovery and FLASH Thunderzap 5.1 Kernel through Recovery
3) Then FLASH SUPERSU ZIP from Recovery
4) Reboot And Done ! Ur Device is Rooted ! ?

@RoxAndroid how did you fallback to stock recovery from twrp? I'm stuck.

Tanzim Abir said:
@RoxAndroid how did you fallback to stock recovery from twrp? I'm stuck.
Click to expand...
Click to collapse
So......to do that Follow these Steps :-
Download Stock Recovery from here http://forum.xda-developers.com/crossdevice-dev/android-one-general/stockrecoveryandroid-one-t2917457
1) Make sure u have Installed ADB drivers ( If Already did, Skip Step 2)
2) To install ADB drivers first Unable USB debugging From the developer Options in the Setting ( If there is No Developer Options Goto-Setting-About Phone-Tap Build Number 7 Times and go back to settings and Open Developer Options and Unable USB debugging) And then Connect Your Phone to PC and Open ADB DRIVER executable File And Install Drivers.
3) Once Drivers are installed Download ADB AND FASTBOOT from here http://drive.google.com/file/d/0B1nu6Ydzrmi-dWdmS00tWjE1WHM
4)Extract the zip and open the folder and then HOLD SHIFT+Right Click and then click on Open Command Window here
5)And then boot your phone to Fastboot Mode, To do that Power Off the Device and HOLD POWER AND VOLUME UP key at the same time and then navigate to the Fastboot Mode by Volume UP button and and Click Volume Down button to select. Once you are in Fastboot Mode connect your Device to PC and go back to PC
6)Once Command Window is opened type following Command :-
Code:
fastboot devices
Code:
fastboot oem unlock
Code:
fastboot format userdata
Code:
fastboot flash recovery <Name of the Recovery in ur PC>
Code:
fastboot boot <Name of the Recovery in ur PC>
6) DONE ! STOCK RECOVERY IS FLASHED and Remember to keep Stock Recovery img file in the ADB AND FASTBOOT FOLDER

Thanks I'll try this asap currently on a train..

Okay.. I've shipped it to the customer care. They said I'll have to wait 3 days for it to get back. I'll report back then.
Thank you everyone for your input.

Closed as this has run its course.

System update with TWRP??

Hi guys,
my P10 (stock rom, rooted and TWRP installed) says I can install a new system update: VTR-L09C02B151
So it downloads the update, then reboot, but TWRP shows up and so no update is done.
How can I install this update?
Thank you

Would probably need to be on stock recovery

Hi,
I have the same problem, do you have the stock recovery
EDIT:
i don't tested that but he can solve this problem
https://forum.xda-developers.com/p10/how-to/dev-introducing-redlotus-source-huawei-t3601493

Thank you guys

sorry guys, back from holidays today.
I still don't understand how to do it
can anyone please write the steps in order to install this OTA update please? (not using redlotus)

Ok I solved.

antani2 said:
Ok I solved.
Click to expand...
Click to collapse
Can you please post your solution so others can benefit if this comes up for them?
Cheers

stillrottentothegore said:
Can you please post your solution so others can benefit if this comes up for them?
Cheers
Click to expand...
Click to collapse
It's easy:
===============================
Step 1 - Back to Stock recovery:
Download this recovery - https://mega.nz/#!ucAnQD5D!VZETUq38R_drskwFgOXz_aK9wIsoIlbjUS5KHrULcTY
Connect your phone to PC and run these commands
adb devices (check your phone is connected)
adb reboot bootloader (reboot in fastboot mode)
fastboot devices (check your phone is in fastboot mode)
fastboot flash recovery RECOVERY.img (flash to stock recovery)
fastboot reboot (reboot the phone)
==================================
Step 2 - Download System Update and install it
Go to Settings -> System Update -> Check for Update
==================================
Step 3 - Flash TWRP again
Download TWRP 3.1.1-2 - https://mega.nz/#!8JwhzBzD!jiuod03amEPlWpo1LD7GWiwP62Z9I97F_TEarmXRrFU
Download SuperSU 2.82 for EMUI5 - https://mega.nz/#!WAYhHRwC!KAaTqWDID9-0e4s4RuKmUN_AKWBPjDJ0ynTXi7sYAv4
Put the 2.6.SuperSU2.82-EMUI5-SelEnforcing.zip in your SD card
Connect your phone to PC and run these commands
adb devices (check your phone is connected)
adb reboot bootloader (reboot in fastboot mode)
fastboot devices (check your phone is in fastboot mode)
fastboot flash recovery recovery.img (flash to TWRP)
fastboot boot recovery.img (reboot into recovery)
Go to "Install" menu and choose storage "Micro SD card" and install 2.6.SuperSU2.82-EMUI5-SelEnforcing.zip
Go to "Reboot" menu and press System for normal reboot.
Tested and works on my WAS-LX1C432.

Maybe this guide can be no more valid..
On my P10, updating from B179 to B180 (due to system notification) and TWRP/root installed, update process fails always.
So I extracted recovery.img from B179 Full-OTA update, flashed over TWRP and started system upgrade process, who completed successfully to B180.
However now I get FRP Unlock, (as before update) but PHONE Locked.
So system upgrade has overwrited the unlocked bootloader with a locked one.
Now, to reflash TWRP and apply root, I've to "fastboot oem unlock *Here Huawei Code*" for the second time, loosing all my apps, datas and settings!!
And each time a new update is available is the same way.. you have to go back to stock, and a new unlock will loose all your data....
Really annoying!

Step 2 - Download System Update and install it
Go to Settings -> System Update -> Check for Update
Click to expand...
Click to collapse
So once I got to this part, it downloaded the update and then the phone rebooted into the stock eRecovery, but whenever it would try and install the update, it would say "Getting package info failed." Any ideas?

Hey I know I'm bumping here, but I'm seriously still at a loss with this. Stock recovery flashes fine, but every single time I try to install the new update, it comes up with ""Getting package info failed." If anyone has experienced this, it'd be great to get it resolved.

Rooting Problems Need Help

Hi I'm a new Android user and don't know much about it :'( I recently got my OnePlus 3T and I wanted to root it
so I followed a tutorial video from YouTube successfully unlocked bootloader and flashed twrp recovery then I tried to install SuperSU... well it installed but the device got soft bricked when I rebooted after finishing the installation and wiping cache/dalvik
then I format/factory reset everything using twrp recovery and it's working now but the device isn't rooted :'( tried to install SuperSU again and it got bricked again
Also I'm getting these messages on the startup screen-
1st one: Your device has been unlocked and can't be trusted. If you don't want to see this screen please lock your device by "fastboot oem lock" and erase user data.
2nd one: The dm-verity is not started in enforcing mode and may not work properly.
(My os version is 4.1.7)
device OP 3t A3010
plz help me :'(

The 1st and the 2nd msg that gets displayed is shown because the bootloader is unlocked..
Bootloops are common while flashing su...when I flashed super su for the first time, I got 3 or 4 random reboots and took almost 7 to 10 mins for the phone to boot up..

I would suggest using Magisk as a rooting method instead of SuperSU. If you use SuperSU then some apps can detect root and object to you being rooted and Google's SafetyNet gets triggered. Magisk solves this by trying to hide root from apps and Google so that you can use your device as if it wasnt rooted at all (but in fact is rooted). Go the the Magisk forum and download Magisk 13.3 zip from there.
I am assuming you are using OxygenOS (Oneplus's software) and not a custom ROM. Download the Open Beta or Stable build from here/
These steps will erase all the data on your phone permanently (including internal storage) so please backup anything in there.
To fix the DM verity error youll have to follow the steps outlined here
Once you have fixed that, flash oneplus recovery via fastboot which you can download here
To flash it go to fastboot mode, and cd into the folder where you downloaded it. Run the command 'fastboot flash recovery <RECOVERY_NAME>'.
Then run the command 'fastboot oem lock' to lock the bootloader. After you confirm the prompt on screen, the phone will boot into the recovery and youll see a progress bar. Once the progress completes and the screen turns off, be ready to immediately go back to fastboot mode by pressing volume up and power.
When you enter fastboot mode again, run the command 'fastboot oem unlock' and follow the same steps as before.
Once you are in fastboot mode, the phone is now in a clean state with no OS.
Follow the steps outlined on the oneplus website to flash a clean OxygenOS build (stable or open beta as per your taste)
Once the flashing is complete you have to let the phone boot up completely once. When you get to the setup screen, go through it and reach the launcher.
Now we flash TWRP recovery. Reboot to fastboot again. Flash TWRP recovery (I personally use blu_spark's twrp but you can use one of your choice). When it is done, boot into the recovery. Youll now be able to copy magisk zip into the internal sd. Do that, and flash it. Reboot.
Youll now be rooted. If you have any problems holla at me.