Database Develop

Deleted files return on boot

Hi all, just purchased an HTC one and rooted following some instructions via an xda video.
The phone is confirmed rooted s-on (via root checker) and has super su installed. Now the phone came only with some O2 hideous bootanimation and downanimation and I wanted to remove them. Installed root browser and deleted the .zip files from system/customise/resources and restarted to confirm. When turning off, the animation isnt there, but upon restart the animations return, together with the files deleted previously. Any ideas what can I do to leave these files permanently deleted?
thx

aquist said:
Hi all, just purchased an HTC one and rooted following some instructions via an xda video.
The phone is confirmed rooted s-on (via root checker) and has super su installed. Now the phone came only with some O2 hideous bootanimation and downanimation and I wanted to remove them. Installed root browser and deleted the .zip files from system/customise/resources and restarted to confirm. When turning off, the animation isnt there, but upon restart the animations return, together with the files deleted previously. Any ideas what can I do to leave these files permanently deleted?
thx
Click to expand...
Click to collapse
Flash an unsecure kernel, the stock kernel doesn't allow deleting of anything.

Seanie280672 said:
Flash an unsecure kernel, the stock kernel doesn't allow deleting of anything.
Click to expand...
Click to collapse
any recommendations? and i assume you'd flash it normally?

aquist said:
any recommendations? and i assume you'd flash it normally?
Click to expand...
Click to collapse
I use ElementalX, a lot of guys on here do, and flash it in recovery, twrp 2.6.3.3 its recommended, I know there is newer versions on that site ive linked below, but use 2.6.3.3 as its the most compatible.
TWRP 2.6.3.3. can be found here: http://techerrata.com/browse/twrp2/m7
ElementalX here: http://forum.xda-developers.com/showthread.php?t=2249774
make sure you do a full back-up beore flashing anything, bootloader must be unlocked, and select the correct kernel as per your phone sense and rom version, found in settings, about phone.

Seanie280672 said:
I use ElementalX, a lot of guys on here do, and flash it in recovery, twrp 2.6.3.3 its recommended, I know there is newer versions on that site ive linked below, but use 2.6.3.3 as its the most compatible.
TWRP 2.6.3.3. can be found here: http://techerrata.com/browse/twrp2/m7
ElementalX here: http://forum.xda-developers.com/showthread.php?t=2249774
make sure you do a full back-up beore flashing anything, bootloader must be unlocked, and select the correct kernel as per your phone sense and rom version, found in settings, about phone.
Click to expand...
Click to collapse
cheers man, it worked. what a ton of features from which to choose!
A small note, I managed to go through the whole process with the latest TWRP and not on the 2.6.3.3...just a heads up for those who might have the same problem

[Q] HTC stuck on HTC logo screenwhen installing Kernel

Hi Team,
I am stuck at HTC logo screen after updating. the Kernel.
TWRP Recovey
Rooted S-on
Android 4.1.2
HTC Sense 5.0
Can someone please help me ?

patelkd007 said:
Hi Team,
I am stuck at HTC logo screen after updating. the Kernel.
TWRP Recovey
Rooted S-on
Android 4.1.2
HTC Sense 5.0
Can someone please help me ?
Click to expand...
Click to collapse
your android version is over a year old .. where did you find a kernel that supports 4.1.2 ?
you have to reflash your rom to overwrite the bogus kernel
you should also at this time update your custom recovery to TWRP 2.6.3.3 or 2.6.3.0 if your on Sprint

@patelkd007
ok first of all:
Never change a Kernel without being entirely sure that 1) it's for the device 2) it works with the OS 3) it is know to be working on sys configs like yours.
In order for me to help you please provice the following things:
> Link to Kernel you downloaded
> Link to OS you have previously installed if it isn't stock
Remember to quote or mention me to get an answer!
Most likely you won't be able to save your old ROM. But hey, give me the infos and I'll take a look into that. Maybe check out this thread: http://forum.xda-developers.com/showthread.php?t=2632736 and read through the part "Bootloop, No OS, Totally f*cked up OS? No Problem"
I have a tool that can save automatically your SD Card to your pc. So your data won't be lost!

clsA said:
your android version is over a year old .. where did you find a kernel that supports 4.1.2 ?
you have to reflash your rom to overwrite the bogus kernel
you should also at this time update your custom recovery to TWRP 2.6.3.3 or 2.6.3.0 if your on Sprint
Click to expand...
Click to collapse
@clsA
Hi Thanks for your help.
I left the phone on the same screen till it drained out battery.
I rebooted phone in recovery mode and restore the backup and fixed the issue.
I would like to update my ROM and I have tried many different way and unable to succeed.
Hope you can help me to update the ROM.
Device Information:
HTC One 32 GB (New Zealand)
Rooted and Unlocked boot-loader
S-ON
Super CID: VODAP021
TWRP 2.6.3.0
Android Version 4.1.2
HTC Sense Version 5.0
HTC SDK API level 5.12
Kernel version:
3.4.10 - gcf4caea
[email protected] #1
SMP PREEMPT
Browser Version: Webkit/534.30
What I already tried:
1) Tried to S-off using Firewater and Rum runner method
> Error:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner
(preferred and most reliable method).
2.) flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix thi
s issue for you!!!.
2)Tried Flashing ROM
>Error:
Rebooting into recovery mode and needs to be restored from backup
Can you please suggest me whats the right way to progress further so, I can enjoy installing custom ROM?
Also, Please do let me know what needs to be take care while choosing custom ROM?

patelkd007 said:
@clsA
Hi Thanks for your help.
I left the phone on the same screen till it drained out battery.
I rebooted phone in recovery mode and restore the backup and fixed the issue.
I would like to update my ROM and I have tried many different way and unable to succeed.
Hope you can help me to update the ROM.
Device Information:
HTC One 32 GB (New Zealand)
Rooted and Unlocked boot-loader
S-ON
Super CID: VODAP021
TWRP 2.6.3.0
Android Version 4.1.2
HTC Sense Version 5.0
HTC SDK API level 5.12
Kernel version:
3.4.10 - gcf4caea
[email protected] #1
SMP PREEMPT
Browser Version: Webkit/534.30
What I already tried:
1) Tried to S-off using Firewater and Rum runner method
> Error:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner
(preferred and most reliable method).
2.) flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix thi
s issue for you!!!.
2)Tried Flashing ROM
>Error:
Rebooting into recovery mode and needs to be restored from backup
Can you please suggest me whats the right way to progress further so, I can enjoy installing custom ROM?
Also, Please do let me know what needs to be take care while choosing custom ROM?
Click to expand...
Click to collapse
Try this
from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then sideload this Rom to your phone
https://www.androidfilehost.com/?fid=23269279319197489
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot
Click to expand...
Click to collapse
Once you have ARHD on the phone try moonshine or rumrunner again. Firewater may also work to s-off your phone.

clsA said:
Try this
Once you have ARHD on the phone try moonshine or rumrunner again. Firewater may also work to s-off your phone.
Click to expand...
Click to collapse
@clsA
I tried following as you suggested.
- Flash recovery TWRP 2.6.3.3
- then sideload this Rom to your phone
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
adb sideload name-of-rom.zip
it was 100 percent successful when I have followed above step but It stuck on black screen.

LibertyMarine said:
@patelkd007
ok first of all:
Never change a Kernel without being entirely sure that 1) it's for the device 2) it works with the OS 3) it is know to be working on sys configs like yours.
In order for me to help you please provice the following things:
> Link to Kernel you downloaded
> Link to OS you have previously installed if it isn't stock
Remember to quote or mention me to get an answer!
Most likely you won't be able to save your old ROM. But hey, give me the infos and I'll take a look into that. Maybe check out this thread: http://forum.xda-developers.com/showthread.php?t=2632736 and read through the part "Bootloop, No OS, Totally f*cked up OS? No Problem"
I have a tool that can save automatically your SD Card to your pc. So your data won't be lost!
Click to expand...
Click to collapse
@LibertyMarine
Thank you for your help so far.
As. I am beginner in this field and learning many new things enjoying it.
Question: What things do I need to check when choosing custom ROM or any other ROM for my device?
I have flashed one ROM downloaded from http://forum.xda-developers.com/showthread.php?t=2441111.
Now my device is with following info:
My HTC one is S-off using Moonshine S-OFF method.
HTC sense version 5.5
Android version 4.4.2
SuperCID: VODAP021
HBOOT: 1.44
Recovery: TWRP 2.6.3.3
Let me know,If you need more information on this.

patelkd007 said:
Hi Team,
I am stuck at HTC logo screen after updating. the Kernel.
TWRP Recovey
Rooted S-on
Android 4.1.2
HTC Sense 5.0
Can someone please help me ?
Click to expand...
Click to collapse
patelkd007 said:
@LibertyMarine
Thank you for your help so far.
As. I am beginner in this field and learning many new things enjoying it.
Question: What things do I need to check when choosing custom ROM or any other ROM for my device?
I have flashed one ROM downloaded from http://forum.xda-developers.com/showthread.php?t=2441111.
Now my device is with following info:
My HTC one is S-off using Moonshine S-OFF method.
HTC sense version 5.5
Android version 4.4.2
SuperCID: VODAP021
HBOOT: 1.44
Recovery: TWRP 2.6.3.3
Let me know,If you need more information on this.
Click to expand...
Click to collapse
you may have gotten a blackscreen because you didn't wipe your phone properly. It's about the same as @clsA wrote. But it's a bit more step for step. The recovery seems to be working. The ROM he gave you seems to be ok, you just need to MD5 check it with this tool here (compare with md5 given on the download page): http://download.cnet.com/MD5-Checker/3000-2092_4-10410639.html
Bootloop, No OS, Totally f*cked up OS? No Problem​​
THIS WILL DELETA ALL YOUR APPS AND APP DATA BUT NOT SDCARD!​
First of all, make a factory reset in TWRP... then follow the next steps.
Now the key step here copying the rom.zip to your sdcard. You do this this way
Since you are in the recovery you should be able, no.. actually will be able to use adb commands
To copy the rom zip us this command:
Code:
adb push "C:\path_to_rom\rom_name.zip" /sdcard/rom.zip
If this one results in supersu and permission errors, try these paths(Thanks @Sneakyghost for this advice!)
Code:
adb push "C:\path_to_rom\rom_name.zip" /storage/emulated/0/rom.zip
Code:
adb push "C:\path_to_rom\rom_name.zip" /data/media/0/rom.zip
Now, in the recovery, choose install and select the rom you should've just copied and install/flash it.
After that make a factory reset, the standart when chosing wipe in TWRP.
Happy rebooting!
​

(SOLVED)My one only boots to recovery (TWRP) after installing custom rom

Hi guys I really need your help.
Basically any rom I run ( via adb sideload or adb push and then install zip) will not work. I get into the aroma (usually) installer and after that is finished I usually get "successfull" but with the exception of "Set_metadata_recursive - some changes failed". After that I have tried a) reboot to system b) wipe cache, dalvik - then reboot c) wipe cache, dalvik and factory reset - then reboot. And pretty much all possible variations of this.
I have tried a few roms like Android revolution HD 84 & 90, Maximus HD same story, one google play edition and some others. I can't figure out wich stock rom I should choose because there are so many to choose from, the CID and MID subjects always gets my confused and I have HBOOT 1.57 ( I should tell you I have s-on)
I can't seem to find anyone/any thread/guide that explaines exactly this problem even with hours and hours going into searching.
My bootloader info:
UNLOCKED
m7_UL PVT SHIP S-ON RH
HBOOT-1.57.000
OS-6.09.401.11
Nov 14 2014, 22:08:05.0 (what's this)
I hope to good there is a solution to this even if I'm not that religous. I would very much appriciate some help from you experts.
forgot to mention: I am almost 100% sure I have superSU and root access (after installing it before and later opening the UPDATE-SuperSU-v.2.45.zip in install zip via TWRP but I do often get the "SuperSU does not seem to be installed" message when rebooting after install. note: I have used the "swiped to install" option and I have also not used it.

fhawkes54 said:
Hi guys I really need your help.
Basically any rom I run ( via adb sideload or adb push and then install zip) will not work. I get into the aroma (usually) installer and after that is finished I usually get "successfull" but with the exception of "Set_metadata_recursive - some changes failed". After that I have tried a) reboot to system b) wipe cache, dalvik - then reboot c) wipe cache, dalvik and factory reset - then reboot. And pretty much all possible variations of this.
I have tried a few roms like Android revolution HD 84 & 90, Maximus HD same story, one google play edition and some others. I can't figure out wich stock rom I should choose because there are so many to choose from, the CID and MID subjects always gets my confused and I have HBOOT 1.57 ( I should tell you I have s-on)
I can't seem to find anyone/any thread/guide that explaines exactly this problem even with hours and hours going into searching.
My bootloader info:
UNLOCKED
m7_UL PVT SHIP S-ON RH
HBOOT-1.57.000
OS-6.09.401.11
Nov 14 2014, 22:08:05.0 (what's this)
I hope to good there is a solution to this even if I'm not that religous. I would very much appriciate some help from you experts.
forgot to mention: I am almost 100% sure I have superSU and root access (after installing it before and later opening the UPDATE-SuperSU-v.2.45.zip in install zip via TWRP but I do often get the "SuperSU does not seem to be installed" message when rebooting after install. note: I have used the "swiped to install" option and I have also not used it.
Click to expand...
Click to collapse
Set metadata errors are caused by using the wrong recovery version ( explained in the FAQ sticky thread page 3 post 1 C) ).
Flash twrp 2.6.3.3 and reflash the rom.

alray said:
Set metadata errors are caused by using the wrong recovery version ( explained in the FAQ sticky thread page 3 post 1 C) ).
Flash twrp 2.6.3.3 and reflash the rom.
Click to expand...
Click to collapse
Thank you so much, you're awesome!!!!!
Got everything up and running

fhawkes54 said:
Thank you so much, you're awesome!!!!!
Got everything up and running
Click to expand...
Click to collapse
you're welcome
Can you edit your first post then click "go advanced" and edit your title to "(SOLVED) My one only boots to recovery (TWRP) after installing custom rom"

alray said:
Can you edit your first post then click "go advanced" and edit your title to "(SOLVED) My one only boots to recovery (TWRP) after installing custom rom"
Click to expand...
Click to collapse
s
Yes consider it done

boot into recovery after installing rom
alray said:
Set metadata errors are caused by using the wrong recovery version ( explained in the FAQ sticky thread page 3 post 1 C) ).
Flash twrp 2.6.3.3 and reflash the rom.
Click to expand...
Click to collapse
hey i'm facing the same problem can you please help ?
currently on TWRP v2.6.3.0

morningmilk said:
hey i'm facing the same problem can you please help ?
currently on TWRP v2.6.3.0
Click to expand...
Click to collapse
Well you din't give us much to go on .. what carrier is your phone and whats the problem

Htc one 32gb at&t
Thanks for your reply i think i have to install the different version of TWRP
Cause the problem i'm facing is after booting into system from new rom installation is my device is ending up into bootloader.
clsA said:
Well you din't give us much to go on .. what carrier is your phone and whats the problem
Click to expand...
Click to collapse
---------- Post added at 09:35 PM ---------- Previous post was at 08:54 PM ----------
Thanks but i figured out and everything is working now
morningmilk said:
Thanks for your reply i think i have to install the different version of TWRP
Cause the problem i'm facing is after booting into system from new rom installation is my device is ending up into bootloader.
Click to expand...
Click to collapse

[Stock Rom] Huawei *Prague* PRA-xxxC432B182

[Stock Rom] Huawei (Prague) PRA-xxxC432B182
For restoring/ rescue your device.​P8 Lite 2017 - PRA-LX1, LX2, LX3, LA-1
P9 Lite 2017
Nova Lite
Honor 8 Youth
Created and tested on this device:
Huawei P8 lite 2017 [PRAGUE]
Model number: PRA-LX1
Build number: PRA-LX1C432B182
free device
The PRA is extrem sensitiv.
Any unconsidered, unofficial intervention, don't forgive it.
Hundreds of users have already "bricked" their device.
The response to the dealers is enormous.
To restore your devices,
I'll provide a complete rom.
It is 100% functional and rooted with SuperSu.
It is to be applied to the device via TWRP restoring.
But it is also suitable for this purpose without an OTA update,
to get the current firmware.
Be sure to read the following instructions carefully.
You're doing it at your own risk!
Rom installation:
In the download folder:
2017-12-30-PRAstockB182root (zip)
there are 26 backup files compressed as Zip files.
After downloading, unpack all files individually into this directory. Then delete all zip's. Now copy the whole directory to your TWRP backup folder. Where your other backups are.
Now flash the stock recovery and perform a factoryreset.
Now flash TWRP and make a wipe of the data and system partitions in TWRP.
Then restore my backup and reboot.
The firmware and the kernel are already rooted.
If necessary, you can install Busybox.
If the device does not boot, the bootloader must be unlocked again with the Huawei unlockcode.
It is a little bit more work for you to unpack everything individually, but this way a faultless installation is possible.
I have tested the up- and download, unpacking and restoring several times. It works perfectly. The rom is bug free.
Now create a new TWRP backup
and remove all older backups from the TWRP backup folder, otherwise they could cause problems later.
Save it to another folder or to
USB-/Stick, or HD.​
I would now like to make a few comments on the end of the year:
I've had the P8 lite 2017 for a year.
The first rooting was developed by me.
The SuperSu and the first rooted kernel,
enabled the developers
@Tecalote and KangVip.
TWRP was provided by the LineageOS team. Again and again I have added fresh rootings and roms.
Nevertheless, increased Bricks are not missing.
It took an enormous amount of time to find
help the users. Unfortunately, this didn't work out for everyone.
My recommendation:
Now set up your device completely. Then create a complete backup with the ingenious Huawei Backup App. Now you take the recovery back.
"fastboot flash recovery recovery. img"
Removes TWRP from your brain for the time being.
Your device is now perfect and the firmware is original. You also have root and the OTA update authorization. When OREO comes, you just wait until I announce the new rooting."
I wish you all the best for 2018.
WARNING !
If all this has worked on my device, it does not mean that it goes with everyone else. Follow exactly the instructions to prevent damage. The execution is your risk.
Never make a factory reset in TWRP. Brick !!! Wipes only in stock recovery.
NOTE: Despite careful preparation I can not guarantee that through the implementation of this Guidance does not create damage to the device or operating system, and therefore assume no liability for ensuing damage and malfunction of hardware and software! If you are still unsure, follow these steps: Only perform the procedure if any mentioned conditions (model number, Android version, etc.) apply to you or your device. Read the instructions carefully and completely, check unfamiliar terminology by google or xda. Downloaded files check for viruses. A backup of important settings and data make. The instructions do not perform, if you do not know what you're doing.
Thank you very much: @Tecalote, KangVip,Chainfire, Stephen (Stericson), Jmz Software, LinageOs team, JRummy, as well as.
Huawei Technologies Co., Ltd.
Update 2017-12-31:
I removed the part "dual recovery".
The support on xda is finished.
Only here:
https://www.android-hilfe.de/forum/huawei-p8-lite-2017.2980/​

I couldn't restore my phone. I followed all of your instructions and after restoring, when I reboot, the phone goes only in TWRP (no volume keys pressed). Any ideas on what I can do?
In any case thank you for the thread, it's good to have a well described procedure for these things

Restore your last backup and repeat the procedure.
Try this one first:
Root again with the SU (B182) from the download.

Tip for life: try not to trust random nerds on forums, offering "ROMs" and what they call "tutorials". Stick to the outlet which sold you the phone, and deal with them and/or the manufacturer, and you can't go far wrong.

afit5 said:
I couldn't restore my phone. I followed all of your instructions and after restoring, when I reboot, the phone goes only in TWRP (no volume keys pressed). Any ideas on what I can do?
In any case thank you for the thread, it's good to have a well described procedure for these things
Click to expand...
Click to collapse
I had the same situation. It's a bit tricky and you must really know, what you are doing
I rebooted to bootloader an repeated the oem unlock -> this caused a factory reset!!
I am on dual recovery and so I rebooted to twrp, repeated the restore with the b182 stock rom and could reboot to the system

mbwf said:
Tip for life: try not to trust random nerds on forums, offering "ROMs" and what they call "tutorials". Stick to the outlet which sold you the phone, and deal with them and/or the manufacturer, and you can't go far wrong.
Click to expand...
Click to collapse
100% useless post. This does not help anyone.
ChinHon tries to help others and i would trust him more than you...

KuGeSch said:
I had the same situation. It's a bit tricky and you must really know, what you are doing
I rebooted to bootloader an repeated the oem unlock -> this caused a factory reset!!
I am on dual recovery and so I rebooted to twrp, repeated the restore with the b182 stock rom and could reboot to the system
Click to expand...
Click to collapse
UPDATE: I solved in another way, which is: booted to fastboot mode, restored the stock recoveries (recovery1 to recovery1, erecovery to recovery2), then the phone booted normally as it should have had. At that point I could reflash twrp to recovery1, but that is optional.
I think the phone tried to boot but having the wrong recovery in recovery2 slot caused problems (just a random hypothesis). Hope this helps

afit5 said:
UPDATE: I solved in another way, which is: booted to fastboot mode, restored the stock recoveries (recovery1 to recovery1, erecovery to recovery2), then the phone booted normally as it should have had. At that point I could reflash twrp to recovery1, but that is optional.
I think the phone tried to boot but having the wrong recovery in recovery2 slot caused problems (just a random hypothesis). Hope this helps
Click to expand...
Click to collapse
What you call erecocery is this the stock erecovery or is it prague311.img from ChinHon? If it is the stock erecovery, where can I find it for download?
Thanks a lot!

KuGeSch said:
What you call erecocery is this the stock erecovery or is it prague311.img from ChinHon? If it is the stock erecovery, where can I find it for download?
Thanks a lot!
Click to expand...
Click to collapse
-prague311.img is TWRP
-recovery.img is the stock recovery on recovery partition 1
-recovery2.img is the stock eRecovery on recovery partition 2
https://www.mediafire.com/file/r33el93w5wyqwde/recovery2.img

ChinHon said:
-prague311.img is TWRP
-recovery.img is the stock recovery on recovery partition 1
-recovery2.img is the stock eRecovery on recovery partition 2
https://www.mediafire.com/file/r33el93w5wyqwde/recovery2.img
Click to expand...
Click to collapse
Thanks a lot! You are doing a great job!

Hello!
I want to follow this guide, it should be fine for my Dual SIM Variant, right?
I have a problem with one file, that is 'version.emmc.win.md5.zip' that can't be downloaded from MEGA. Can someone please provide a working link for that file?
Also a doubt: when all the files will be ready my idea is to restore your TWRP backup, flash stock recovery then lock bootloader, to make it as near to stock as possible: will this work? I have another TWRP backup that is running on my phone, but if I lock the bootloader it won't start, if I unlock the bootloader there no problems at all.
Thanks for your interesting topic!

SnoopyDog said:
100% useless post. This does not help anyone.
ChinHon tries to help others and i would trust him more than you...
Click to expand...
Click to collapse
Very good. Keep smiling.

baffo92 said:
Hello!
I want to follow this guide, it should be fine for my Dual SIM Variant, right?
I have a problem with one file, that is 'version.emmc.win.md5.zip' that can't be downloaded from MEGA. Can someone please provide a working link for that file?
Also a doubt: when all the files will be ready my idea is to restore your TWRP backup, flash stock recovery then lock bootloader, to make it as near to stock as possible: will this work? I have another TWRP backup that is running on my phone, but if I lock the bootloader it won't start, if I unlock the bootloader there no problems at all.
Thanks for your interesting topic!
Click to expand...
Click to collapse
Here's the link.
https://mega.nz/#!4sd3DI6Z!BOfI0teLD_m3aLUROhiMVZuePySmp329RXZpjsH3AM0
Please tell me why you want to take the rom. What's happening?

ChinHon said:
Here's the link.
https://mega.nz/#!4sd3DI6Z!BOfI0teLD_m3aLUROhiMVZuePySmp329RXZpjsH3AM0
Please tell me why you want to take the rom. What's happening?
Click to expand...
Click to collapse
The link works perfectly. Thanks!
I can now give this stock ROM a try!
EDIT 1: I'm trying to install the ROM but I have a problem with TWRP: I launch the command 'fastboot flash recovery prague311.img' then boot to TWRP, but the touchsceen of the phone is unresponsive and I can't do anything to make it work. Have you got any suggestion?
EDIT 2: I made some mistakes here and there, but the TWRP booted and now I have the phone on your ROM Version! I'm trying to clean everything and do a clean install if I can...
EDIT 3: I've done a full phone clean by using the 'Factory Reset' option in 'Settings'... now the phone boots, but:
1. NFC/GPS are not working, they are blinking
2. FM Radio is not working (it says com.huawei.... and has an Android icon instead of the original icon)

baffo92 said:
The link works perfectly. Thanks!
I can now give this stock ROM a try!
EDIT 1: I'm trying to install the ROM but I have a problem with TWRP: I launch the command 'fastboot flash recovery prague311.img' then boot to TWRP, but the touchsceen of the phone is unresponsive and I can't do anything to make it work. Have you got any suggestion?
EDIT 2: I made some mistakes here and there, but the TWRP booted and now I have the phone on your ROM Version! I'm trying to clean everything and do a clean install if I can...
Click to expand...
Click to collapse
To get the rom completely clean you do the following:
Go to my root thread section: Threadupdate: 2018-01-02 and work through the instructions. Then you have a perfect clean stock rom.

ChinHon said:
To get the rom completely clean you do the following:
Go to my root thread section: Threadupdate: 2018-01-02 and work through the instructions. Then you have a perfect clean stock rom.
Click to expand...
Click to collapse
Your support is very helpful, thanks!
I have problems on the steps to reproduce, even after reading your guide :')
This is what I do:
1. Wipe Data/Factory Reset + Wipe cache with stock recovery
2. Flash TWRP
3. Open TWRP, clean data, system and also cache + dalvik
4. Reboot the phone to a fully working with B182, in English with Dual SIM fully recognised
5. What I have to do from now on to have a fully stock experience (remove custom Kernel, reflash stock recovery and erecover, re-lock bootloader and fully ready to Oreo)?
Can you please guide me?
Thanks and sorry for my problems, but I work with Nexus devices thare a bit more 'elastic' in flashing

The kernel is stock. You just have to flash the eRecovery and recovery. That's all.

ChinHon said:
The kernel is stock. You just have to flash the eRecovery and recovery. That's all.
Click to expand...
Click to collapse
Ok, thanks!
This is what I did before, but I can't do a factory reset due to the problems described (Radio FM not working, NFC not working).
I can't also relock the bootloader, because the phone will boot to erecovery (recovery2) and won't let me reach the boot of the ROM. Have you got any suggestion?
If leave it as it is now (unlocked bootloader with stock recovery1 and recovery2) will Oreo arrive without any problems?
Your support is awesome, thanks

If you now take my UPDATE.APP via dload the problems should be gone.

ChinHon said:
If you now take my UPDATE.APP via dload the problems should be gone.
Click to expand...
Click to collapse
Sounds good!
If I flash the stock recovery, then update officially with an UPDATE.APP from SD Card everything should be ok.
Where can I find your UPDATE.APP? I didn't find it in your MEGA Folder
Thanks, again, for your incredible support!

Stuck in Fastboot Mode / TWRP without OS

Hello people,
I have an OnePlus 3T, which does not start the OS. I can open Fastboot Mode or TWRP. I do not even know which OS is installed (I think stock rom, but do not know). When I boot into Fastboot, I get the dm-verity notification "Phone is unlocked and cannot be trusted". When I boot into system, it stops at the black "Powered by android" Screen (very first screen).
When I connect my phone to the PC and open the internal storage, it shows only the "TWRP" folder.
So what Information do I have so far (with my amateur knowledge):
adb shell getprop ...
ro.build.version.release: 6.0.1
ro.build.version.sdk: 23
ro.build.display.id: omni_oneplus3-eng 6.0.1 MOB31K eng.jc.20170208.012427 test-keys
ro.modversion: OmniROM-6.0.1-20170208-oneplus3-HOMEMADE
ro.twrp.version: 3.0.4-1
When I start the bootloader:
Product_Name - msm8996
Variant - MTP UFS
Bootloader Version -
Baseband Version -
Serial Number - *****
Secure Boot - enabled
Device State - unlocked
I tried to reflash the original recovery => device did not start in recovery anymore => reflashed twrp
I tried to flash the stock ROM => did not work (with this Error 7)
So my first question: Which OS do I have? Really Marshmallow 6.0.1?
Second: Do you need more infos?
Third and most important: How to repair this mess?
What do I want: A stable, rooted ROM. It can be the stock ROM, but also a custom, I do not care right now.
I read that this unlocked-notification appears because I have the wrong kernel? Is that true? Which one do I need?
Thank you very much for your help.

Use ADB Sideload to Sideload a ROM onto the phone since you have TWRP working. It's not a huge problem, and it's easily solvable.
*OR* you can use the Unbrick tool to solve your problem.

thes3usa said:
Use ADB Sideload to Sideload a ROM onto the phone since you have TWRP working. It's not a huge problem, and it's easily solvable.
*OR* you can use the Unbrick tool to solve your problem.
Click to expand...
Click to collapse
Thank you for your reply.
Okay so it is not important which system I run right now? And what about this kernel thing?
I can just flash it with sideload (e.g. https://forum.xda-developers.com/on...pment/rom-kernel-resurrectionremix-n-t3524715) and finished? Rooted and particularly working?
Sorry for the questions but I am a little nervous

elchico92 said:
Thank you for your reply.
Okay so it is not important which system I run right now? And what about this kernel thing?
I can just flash it with sideload (e.g. https://forum.xda-developers.com/on...pment/rom-kernel-resurrectionremix-n-t3524715) and finished? Rooted and particularly working?
Sorry for the questions but I am a little nervous
Click to expand...
Click to collapse
You may want to Sideload the latest Firmware too, Open Beta 21 that is. And then Sideload a Nougat ROM. Don't sideload any GAPPs.

thes3usa said:
You may want to Sideload the latest Firmware too, Open Beta 21 that is. And then Sideload a Nougat ROM. Don't sideload any GAPPs.
Click to expand...
Click to collapse
So first this one (downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_openbeta_21/), then this (androidfilehost.com/?w=files&flid=131965 - latest)?
Thanks again!
PS: Sorry I cannot post links yet.

elchico92 said:
So first this one (downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_openbeta_21/), then this (androidfilehost.com/?w=files&flid=131965 - latest)?
Thanks again!
PS: Sorry I cannot post links yet.
Click to expand...
Click to collapse
Nope, that's the complete stock Zip. Unless you want to install OOS, that's not the one to Sideload.
Download the FW only from here: https://forum.xda-developers.com/oneplus-3t/how-to/firmware-beta-10-t3631166
And then Sideload it, reboot back to recovery, and then Sideload the ROM.

elchico92 said:
When I connect my phone to the PC and open the internal storage, it shows only the "TWRP" folder.
Click to expand...
Click to collapse
What is in the TWRP folder, anything? The TWRP folder would normally only be created, if a backup was created. You can possibly just boot TWRP, select the RESTORE option, select the backup from the TWRP folder, and get the phone up and running again.
Another possibility, if you aren't that up on adb commands (sideload, etc.), since you can access the internal storage, just download a ROM or fill stock ROM zip onto your PC, then just drag/copy to internal storage. Then boot TWRP, select INSTALL, pick the file, and flash it.
What is the background of the device, how do you not know the OS version? Did you receive it this way, or fixing it for a friend or something?
---------- Post added at 09:19 AM ---------- Previous post was at 09:12 AM ----------
elchico92 said:
When I boot into Fastboot, I get the dm-verity notification "Phone is unlocked and cannot be trusted".
I read that this unlocked-notification appears because I have the wrong kernel? Is that true? Which one do I need?
Click to expand...
Click to collapse
That isn't the dm-verity notification. The dm-verity notification screen is similar, but says "dm-verity is not started in enforcing mode".
What you described is the bootloader unlocked warning screen. The bootloader unlocked warning screen is expected and normal (in fact, unavoidable) if the bootloader is unlocked. And unlocked bootloader is required for TWRP, flashing custom ROMs, etc.
dm-verity warning screen is in fact normal, as well, if you have TWRP installed. That one can be disabled by a couple different methods. But it's only purpose is to notify a "average" user that the system has been modified. For XDA users that are intentionally modifying their phones (TWRP, root, etc.) the warning is pretty meaningless. Under certain conditions, dm-verity will prevent the phone from booting. But TWRP and root in themselves, will normally not do that.
Neither warning means you have the wrong kernel, necessarily. And unless you (or someone else) tried to flash a kernel, there really isn't any reason to believe that.
---------- Post added at 09:29 AM ---------- Previous post was at 09:19 AM ----------
elchico92 said:
I tried to reflash the original recovery => device did not start in recovery anymore => reflashed twrp
Click to expand...
Click to collapse
Flashing stock recovery will (by definition) replace TWRP with stock recovery. You probably have recovery, just the stock one (not TWRP) which is fairly useless in your case (can't flash custom ROMs, root, etc.).
elchico92 said:
I tried to flash the stock ROM => did not work (with this Error 7)
Click to expand...
Click to collapse
Can't really troubleshoot this, unless you tell us what file exactly (file name) and where you got it from. "Stock ROM" is far too vague, and can literally mean a dozen or more different things.
Also, what version TWRP?
Using a TWRP version which does not support Oreo is one reason for Error 7. Or you may have tried a file intended for the 3, not the 3T. So these details need to be provided, before we can figure out what went wrong.
elchico92 said:
What do I want: A stable, rooted ROM. It can be the stock ROM, but also a custom, I do not care right now.
Click to expand...
Click to collapse
You kind of need to decide which of those you want. Otherwise, there are just too many options for us to give.
Yet another option (in addition to those given) would be to flash the full stock OOS zip from here: https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Then before rebooting, flash Magisk to root, and you should be all set. The full zip will put you on a fully stock baseline (including firmware). Which, if you aren't sure if you want stock, beta or custom ROM, is not a bad place to be; you can see what the "stock" condition is, before messing with things like custom ROMs. But again, it's totally subjective and a matter of personal preference, and you really do need to decide for yourself what is best for you (as an individual) at this time.

thes3usa said:
You may want to Sideload the latest Firmware too, Open Beta 21 that is. And then Sideload a Nougat ROM. Don't sideload any GAPPs.
Click to expand...
Click to collapse
Why not just sideload stock ROM which includes the firmware? Make life easier

przemcio510 said:
Why not just sideload stock ROM which includes the firmware? Make life easier
Click to expand...
Click to collapse
Yeah, that is a good option, among many. As I mentioned, there are just too many options since the original poster hasn't even decided stock or custom ROM.

przemcio510 said:
Why not just sideload stock ROM which includes the firmware? Make life easier
Click to expand...
Click to collapse
Since OP hasn't mentioned whether he wants to use a stock or custom ROM. So I gave him the link for the latest FW, in case he wants to use a recently updated custom ROM without needing to download the whole Stock zip.

Done!
Thanks a lot. The phone is working again.
I have flashed with adb sideload the firmware and the ResurrectionRemix-Rom (Nougat) and then via TWRP the gapps.
So I hope, everthing will be fine now.
answers:
- TWRP-folder: yeah I created one because I thought, maybe to restore will fix anything
- I tried to flash with TWRP a ROM, but it says "Error 7", which means: wrong ROM => but I am sure, it was the right one
- background: it was the phone of a friend of mine => he never heard anything about ROMs etc
The thread can be closed.

elchico92 said:
- I tried to flash with TWRP a ROM, but it says "Error 7", which means: wrong ROM => but I am sure, it was the right one
Click to expand...
Click to collapse
I already offered to troubleshoot this error for your, but you never supplied the requested info. Don't assume it is the "right one" next time, but rather, give exact file names, version numbers, and let us verify. Mistakes happen, and it always is good to have another set of eyes look at the specifics.
---------- Post added at 09:58 AM ---------- Previous post was at 09:56 AM ----------
elchico92 said:
The thread can be closed.
Click to expand...
Click to collapse
Threads on xda don't get closed, just because you solved your current issue. Others may have a similar problem, and may want to ask questions, etc.

I'm stuck in Fastboot Mode & TWRP without OS
I everyone,
Like the title say I'm totally stuck, I don't know what to do ....
I've got a OnePlus 3T few years ago, and the first thing i did at the installation was to encrypt the phone with an option of oxygen OS, and after that i unlock the oem and add root access.
But when oneplus release a major update, there was issues with phone encrypted and unlock, for that I never could make an update of the OS, so I did try to install the lastest lineage os recently, and add an "error 7".
After reading a lot of stuff and try a lot of manupilations, i'm now totally stuck with only access to the fastboot, twrp, and the recovery of oneplus.
If someone here could help me, you will be very gratefull because i can't afford to buy a new phone for the moment... thank's

slykereven said:
I everyone,
Like the title say I'm totally stuck, I don't know what to do ....
I've got a OnePlus 3T few years ago, and the first thing i did at the installation was to encrypt the phone with an option of oxygen OS, and after that i unlock the oem and add root access.
But when oneplus release a major update, there was issues with phone encrypted and unlock, for that I never could make an update of the OS, so I did try to install the lastest lineage os recently, and add an "error 7".
After reading a lot of stuff and try a lot of manupilations, i'm now totally stuck with only access to the fastboot, twrp, and the recovery of oneplus.
If someone here could help me, you will be very gratefull because i can't afford to buy a new phone for the moment... thank's
Click to expand...
Click to collapse
This should get you back to OOS:
In TWRP:
1. Do a factory reset
2. Flash OOS 9.0.6 full rom
3. Flash this modified firmware (to avoid the issue 9.0.6 with encrypted+unlocked) https://github.com/nvertigo/firmwar...3t/oxygenos-9.0.6-bl-km-5.0.8-firmware-3T.zip (see https://forum.xda-developers.com/on...5-0-8-firmware-barrier-t3941164/post79758055)
4. Reboot
This should leave you with a clean install of OOS 9.0.6 and an encrypted phone with the stock recovery (TWRP gets replaced when you boot stock OOS).
From that point you can do what you want.
Sent from my OnePlus 3T using XDA Labs

Resolved
OK, that's a little crazy but it's working, i've got a one plus 3T A3003, but i had to install Stable9.0.3+Firmware+Modem_OnePlus3.zip and not the one for the 3T ..... then install the last lineage os 17, and everything seems to work for now !!!
---------- Post added at 09:13 AM ---------- Previous post was at 09:09 AM ----------
BillGoss said:
This should get you back to OOS:
In TWRP:
1. Do a factory reset
2. Flash OOS 9.0.6 full rom
3. Flash this modified firmware (to avoid the issue 9.0.6 with encrypted+unlocked) https://github.com/nvertigo/firmwar...3t/oxygenos-9.0.6-bl-km-5.0.8-firmware-3T.zip (see https://forum.xda-developers.com/on...5-0-8-firmware-barrier-t3941164/post79758055)
4. Reboot
This should leave you with a clean install of OOS 9.0.6 and an encrypted phone with the stock recovery (TWRP gets replaced when you boot stock OOS).
From that point you can do what you want.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Hi, thank's for your help, i didn't see your answer before and i have resolved the issue with other method