Related
Hi All,
I see a lot of people asking for stock stuff for the HTC One Mini 2, please find them here:
Stock RUUs - https://forum.xda-developers.com/one-mini-2/general/htc-one-mini-2-official-ruu-t3425930
BOOT IMAGE
Signed Boot Image : boot_signed.img for booting problems (FOR INTERNATIONAL/EUROPEAN DEVICES ONLY)
PROCESS
Enter bootloader and then enter fastboot and type the command :
Code:
fastboot flash boot boot_signed.img
fastboot reboot bootloader
Nandroid Backup for restoring to stock, I have used this, working fine (Can be restored through TWRP): https://www.androidfilehost.com/?fid=24052804347818782 (FOR INTERNAITIONAL/EUROPEAN DEVICES ONLY)
Stock Firmware: https://www.androidfilehost.com/?fid=95784891001615234
Stock Recovery: https://www.androidfilehost.com/?fid=24052804347822267 (Newer)
Stock Recovery: https://www.androidfilehost.com/?fid=95784891001615233
Original Page (German): http://www.handy-faq.de/forum/htc-one-mini-2-firmwaresammlung-ruus-otas-backups-t309020/
LINKS WERE WORKING WHEN I POSTED THEM, DOWNLOAD AT THE EARLIEST AS MAY BE THEY WONT WORK WHEN YOU NEED THEM, SO JUST DOWNLOAD AND KEEP.
STEPS TO RESTORE NANDROID BACKUP THROUGH TWRP:
- REBOOT AND ENTER TWRP, PERFORM A BACKUP (THIS WILL CREATE A TWRP BACK UP FOLDER WITH DEVICE SERIAL NUMBER IN THE SD CARD)
- DOWNLOAD AND EXTRACT THE NANDROID BACK UP FILE
- PLACE THE EXTRACTED FILES IN TO THE TWRP>BACKUP<DEVICE SERIAL NUMBER> FOLDER IN THE SD CARD
- RESTART THE DEVICE AND ENTER TWRP, CHOOSE RESTORE
- LOCATE THE FOLDER COPIED IN THE ROOT OF THE SDCARD
- SWIPE TO RESTORE
- FOR SOME REASON THE NANDROID BACKUP DOES NOT CONTAIN CALCULATOR, FLASH LIGHT WHICH CAN BE DOWNLOADED HERE: http://www.apkmirror.com/apk/htc-corporation/
THANK YOU
I cant install
Bear Grylls said:
I cant install
Click to expand...
Click to collapse
What is the exact problem you are facing when flashing the stock file. PLEASE EXPLAIN FOR BETTER UNDERSTANDNG.
ELSE YOU CAN TRY THE BELOW.
NB: I AM ASSUMING THINGS AND GIVING THIS INFORMATION, I AM NOT RESPONSIBLE FOR WHAT HAPPENS AS I DONT KNOW THE EXACT PROBLEM YOU ARE FACING.
Make sure device is 100% battery.
1st try this:
1-Download this file: [ https://drive.google.com/file/d/0B_1zjuazXSqbQ0p6NWtvRk9OMzA/edit?pli=1 ] and install in Windows (Run as Administrator).
2-Open Command window and type:
Code:
cd c:\adb
3-now on your device use Vol keys to choose and power key to select, and choose FASTBOOT
4-now download the attached file boot_signed.rar (extract the file in C:\adb folder)
5-type in the command window:
Code:
fastboot flash boot boot_signed.img
5-type in the command window:
Code:
fastboot erase cache
6-type in command window:
Code:
fastboot reboot
IF THIS DID NOT WORK, THEN TRY THIS:
Download this [ https://www.androidfilehost.com/?fid=95916177934555508 ] file and rename it to 0P8BIMG.zip and place it into the SD card (MMC Card), restart the device and let it boot into the HBoot menu.
Reboot device from the boot mode, if the device automatically reboot into the boot menu then it will start flashing the file automatically.
Good Luck, let me know how it went.
Try and let me know.
this is excellent, all in one place...
However, please forgive my ignorance in recovery/backup terminology (I hope it is not just me) but I get confused by the use of 'Nandroid' backup, Stock Rom, and .zip and .img files for flashing.
I have successfully used TWRP to flash the NostromoPop ROM, but have not been successful with any other .zip file supposedly a Stock ROM.
I have been hoping that somebody could put a rooted Stock ROM so that I can try it as a way to get around the KitKat blocks on writing to the SD card for some of my autosync apps.
Am I making any sense?
Many thanks if you can help
soundrediscovery said:
this is excellent, all in one place...
However, please forgive my ignorance in recovery/backup terminology (I hope it is not just me) but I get confused by the use of 'Nandroid' backup, Stock Rom, and .zip and .img files for flashing.
I have successfully used TWRP to flash the NostromoPop ROM, but have not been successful with any other .zip file supposedly a Stock ROM.
I have been hoping that somebody could put a rooted Stock ROM so that I can try it as a way to get around the KitKat blocks on writing to the SD card for some of my autosync apps.
Am I making any sense?
Many thanks if you can help
Click to expand...
Click to collapse
Hi,
As I understand you cannot flash a stock ROM with customer Recovery, as far as I know you need stock Recovery to flash a stock ROM, I remember trying stock ROM on TWRP but it failed, could be due to some other reason, I read somewhere it has something to do with file signatures.
As for SD write fix, you need to have root access other than that there is no fix for it, rooting with SuperUser Binary... I myself did want to try it now that I am back on stock but then I am greedy for Marshmallow (if they could fix that Loud Speaker issue) I am all in for Android M, I tried to get in touch with people on the Cyanogen Forums but no luck as I have not yet received verification email, tried so many times, no luck and as it seems there is no Marshmallow development on HTC One Mini 2....
I will wait and see how it goes...
If I am correct you can keep stock ROM and flash SU Binary and get root access and then install https://play.google.com/store/apps/details?id=nextapp.sdfix to get it done with, it ought to work, haven't tried myself...
The recovery image you gave seems a little broken, but the backup worked...thought I recommend a factory reset unless you want the system language to be weird...
hanro50 said:
The recovery image you gave seems a little broken, but the backup worked...thought I recommend a factory reset unless you want the system language to be weird...
Click to expand...
Click to collapse
Which recovery image have you used, I have flashed the newer version successfully, yes the backup worked and has non-English language as default.
The command:
Code:
fastboot flash recovery recovery_name.img
fastboot erase cache
If you could elaborate a "little broken"
I maneged to reflash twrp from android, ok these is what happened, I flash it as a recovery image with twrp, when I reboot into recovery later then it just showed a picture of my phone with a red triangle icon in it, after a while my phone resets...and goes back to booting from the main installed os...
---------- Post added at 07:10 AM ---------- Previous post was at 07:08 AM ----------
The name of the file is M8_MINI_UL_Stock_Recovery_2.19.401.2.img
I don't remember if I taped New or old
hanro50 said:
I maneged to reflash twrp from android, ok these is what happened, I flash it as a recovery image with twrp, when I reboot into recovery later then it just showed a picture of my phone with a red triangle icon in it, after a while my phone resets...and goes back to booting from the main installed os...
---------- Post added at 07:10 AM ---------- Previous post was at 07:08 AM ----------
The name of the file is M8_MINI_UL_Stock_Recovery_2.19.401.2.img
I don't remember if I taped New or old
Click to expand...
Click to collapse
Hi,
I believe you flashed a recovery with another recovery, which I think is not the right way, the right way is to use the command to overwrite TWRP with stock recovery.
hanro50 said:
I maneged to reflash twrp from android, ok these is what happened, I flash it as a recovery image with twrp, when I reboot into recovery later then it just showed a picture of my phone with a red triangle icon in it, after a while my phone resets...and goes back to booting from the main installed os...
---------- Post added at 07:10 AM ---------- Previous post was at 07:08 AM ----------
The name of the file is M8_MINI_UL_Stock_Recovery_2.19.401.2.img
I don't remember if I taped New or old
Click to expand...
Click to collapse
HI,
Just wanted to know if you are having any issues with low audio after restoring Android backup from TWRP, I feel my audio is way too low and cant be heard just if I am outside my room..
I didn't have any audio problems, it could just be you being used to cm's 3rd party BoomSound replacement
---------- Post added at 01:25 PM ---------- Previous post was at 01:21 PM ----------
Well that would exsplain why some elements of the stock recovery remained after I reflashed twrp with a app on my phone, e.g. it fixed the image I get when I hook my device up to power when it is turned off...before that it would just boot me into a unusable twrp homepage
The stock RUU file is corrupt! (tried 5 times now)
Where can I get a A stock flash or a ROM that is NOT ROOTED please?
I tried the 0P8BIMG.zip on SD card method and that did not work either.
Also, I thought the RUU file is meant to be an executable not a zip file. I'm confused...
niblettr said:
The stock RUU file is corrupt! (tried 5 times now)
Where can I get a A stock flash or a ROM that is NOT ROOTED please?
I tried the 0P8BIMG.zip on SD card method and that did not work either.
Also, I thought the RUU file is meant to be an executable not a zip file. I'm confused...
Click to expand...
Click to collapse
I doubt its corrupted, which OS are you running currently ?, when I tried it, it failed due to the installed stock ROM being newer than the one being installed and since I have S-ON I cant downgrade it...
You can Nandroid Restore the stock backup, I have personally tried and it works....
Another way to do it is to have the Nandroid Restore and then use Sunshine to S-OFF (as sunshine only works on stock or near-stock ROMs) and then flash with 0P8BIMG.zip, it should work then, just a thought...
Hi, thanks for these links & info. Just about to give this a go. But, what does boot_signed.img do?
pavsid said:
Hi, thanks for these links & info. Just about to give this a go. But, what does boot_signed.img do?
Click to expand...
Click to collapse
Its a signed boot file, meaning it flashes successfully should the device fail to boot or stuck on boot or in other words if the device does not boot and remains on HTC, this flashing this should solve your problem.
Hi all I have been directed here from another thread as I am looking to place a stock rom on my htc one mini 2 without bloatware, I have unlocked the bootloader and installed TWRP but the stock rom remains the same all I want is to install a rom via TWRP if at all possible. Is the 1gig one ok for that or will i need to completely put the stock recovery back on and the phone is unlocked to all networks if that makes any different
Thank in advance
The Watergod said:
Hi all I have been directed here from another thread as I am looking to place a stock rom on my htc one mini 2 without bloatware, I have unlocked the bootloader and installed TWRP but the stock rom remains the same all I want is to install a rom via TWRP if at all possible. Is the 1gig one ok for that or will i need to completely put the stock recovery back on and the phone is unlocked to all networks if that makes any different
Thank in advance
Click to expand...
Click to collapse
Hi,
Its not possible to flash stock rom via TWRP, plus you need to have S-Off.
The only way to go complete stock is to restore Nandroid Backup and then flash stock recovery.
TryllZ said:
Hi,
Its not possible to flash stock rom via TWRP, plus you need to have S-Off.
The only way to go complete stock is to restore Nandroid Backup and then flash stock recovery.
Click to expand...
Click to collapse
so is this the nandroid back up of a stock rom that I can use with the latest update for use with twrp and when I mean stock rom I mean a rom that has not been majorly altered to class it as a custom rom. I.e still has sense and no additional apps added
Again Thanks in advance
The Watergod said:
so is this the nandroid back up of a stock rom that I can use with the latest update for use with twrp and when I mean stock rom I mean a rom that has not been majorly altered to class it as a custom rom. I.e still has sense and no additional apps added
Again Thanks in advance
Click to expand...
Click to collapse
Hi,
Yes you will have to restore the Nandroid Backup, this backup is completely of a stock ROM, no edition, however it does not have some apps like the Calculator, Flash etc for some reason.
However I found the missing apps from here: http://www.apkmirror.com/apk/htc-corporation/
TryllZ said:
Hi,
Yes you will have to restore the Nandroid Backup, this backup is completely of a stock ROM, no edition, however it does not have some apps like the Calculator, Flash etc for some reason.
However I found the missing apps from here: http://www.apkmirror.com/apk/htc-corporation/
Click to expand...
Click to collapse
Excellent much appreciated for this right, so I need to first copy the nandroid backup to my Phones root and run TWRP and restore using the downloaded nandroid yes?
if yes could I please have the steps to put the stock recovery on with ADB commands as I really don't want to brick my phone (Yes I know you take no resposibilty etc) just happier to have as least the correct file names and adb commands.
And last I just copy the new stock RUU to my phone and install?
You help is as always greatly appreciated as no one seems to be ddoing anything anymore for this phone
Hey there everyone.
I have CyanogenMod flashed in my H811. It was working just fine when in Marshmallo i.e. Cm13. but a few days ago it upgraded to cm14, nougat. there were a lot of issues and i wanted to revert but cm13 was nowhere to be found. the nougat version was working just fine when yesterday it notified me of an update. i downloaded that update and tried to install it. phone rebooted into recovery but it didn't automatically flash the update ( which it usually does whenever a new update is set to install) so i just located the file and flashed it and then rebooted it afterwards. that's when i saw that it rebooted into TWRP again instead of system. i've tried almost everything since yesterday. Flashed other roms, tried to restore backups but no success. even reset my phone completely and then tried to, but to no success. i cannot even access download mode which if i could, i would've had flashed the stock kdz. Everytime i try to reboot it into system or download mode, it just reboots back into TWRP. Please help.
Edit: I was using the wrong method for entering the download mode. i was pressing the volume down button instead of volume up while plugging into my pc. If you encounter the same problem, make a backup ( to restore apps later) in TWRP and move it to your pc, also backup your internal data (music, pictures etc). Also download gapps, check arm64 and android 7.1. Now Using the lgup tool, flash the stock rom kdz, the latest one is 20o. Your phone will be back to stock. Then flash twrp again using adb and use adb to boot into twrp. once booted, copy the cm update from your pc to phone, ( this is the update which caused the problem, back it up too. it'll be in sdcard/cmupdate/ ) and also the twrp backup that you had made earlier. Then on your phone, flash the cm rom and Gapps, and then restore the twrp backup when when restoring, go to advanced restore and select data only. and restore that. after it completes, turn on your phone, connect it to pc and move the internal data (pics and music) back to your phone.
I am in the same trouble except I am using CM recovery
Screen prompts below error message when flashing any ROM:
Patching system image unconditionally....
E: unknown command [log]
Somtimes I can see a broken (heart) android Robot
Then phone goes back to recovery home page
Anyone can help us? Should I flash TWRP recovery to overwrite CM recovery? Is phone hard/soft bricked?
Same exact issue. I have TWRP. Did the December second CM update and have no clue what to do.
TechGuruGJ said:
Same exact issue. I have TWRP. Did the December second CM update and have no clue what to do.
Click to expand...
Click to collapse
eruisi said:
I am in the same trouble except I am using CM recovery
Screen prompts below error message when flashing any ROM:
Patching system image unconditionally....
E: unknown command [log]
Somtimes I can see a broken (heart) android Robot
Then phone goes back to recovery home page
Anyone can help us? Should I flash TWRP recovery to overwrite CM recovery? Is phone hard/soft bricked?
Click to expand...
Click to collapse
i found the solution. i was using the wrong method to enter download mode. it was pressing Volume up button while plugging into my pc. i recommend you both to make a backup and move that to your pc, enter download mode and flash the stock rom, then flash twrp again and the current cm rom and restore the 'data' from the backup made. it'll restore the phone to back where it was.
Armaghan Bashir said:
Edit: I was using the wrong method for entering the download mode. i was pressing the volume down button instead of volume up while plugging into my pc. If you encounter the same problem, make a backup ( to restore apps later) in TWRP and move it to your pc, also backup your internal data (music, pictures etc). Also download gapps, check arm64 and android 7.1. Now Using the lgup tool, flash the stock rom kdz, the latest one is 20o. Your phone will be back to stock. Then flash twrp again using adb and use adb to boot into twrp. once booted, copy the cm update from your pc to phone, ( this is the update which caused the problem, back it up too. it'll be in sdcard/cmupdate/ ) and also the twrp backup that you had made earlier. Then on your phone, flash the cm rom and Gapps, and then restore the twrp backup when when restoring, go to advanced restore and select data only. and restore that. after it completes, turn on your phone, connect it to pc and move the internal data (pics and music) back to your phone.
Click to expand...
Click to collapse
Hi , I have the same problem, just wanted to get some clarification on how to sort this out as I've not used LGUP before or flashed stock rom:
from here: http://forum.xda-developers.com/tmo...om-mm-lg-g4-h811-20o-stock-debloated-t3412394
which file do i need? is it the KDZ version? once that's downloaded do i follow these instructions from LGUP page?
"TO GO BACK TO LP FROM MM - Open LGUP on your computer, click on FILE PATH and point it towards your LP KDZ. Close LGUP and re-open LGUP. Make sure you select REFURBISH this will do a full wipe, tick BIN file. Press Start. Make cup of tea and be patient "
thanks.
charmander21 said:
Hi , I have the same problem, just wanted to get some clarification on how to sort this out as I've not used LGUP before or flashed stock rom:
from here: http://forum.xda-developers.com/tmo...om-mm-lg-g4-h811-20o-stock-debloated-t3412394
which file do i need? is it the KDZ version? once that's downloaded do i follow these instructions from LGUP page?
"TO GO BACK TO LP FROM MM - Open LGUP on your computer, click on FILE PATH and point it towards your LP KDZ. Close LGUP and re-open LGUP. Make sure you select REFURBISH this will do a full wipe, tick BIN file. Press Start. Make cup of tea and be patient "
thanks.
Click to expand...
Click to collapse
Hey, The flash rom of LG G4 is in the format .kdz. also, i used the .kdz which i already had from almost 3 months ago when i had to flash my phone to stock. so I don't remember from where did i get it but here is a link that i extracted from IDM.
https://www.androidfilehost.com/?fid=24572369242688134
Download this file, then on the lg flash tool, select ''Upgrade'', select your .kdz file by clicking the rectangular bar next to 'bin file' and then flash it. That's all.
Armaghan Bashir said:
Hey, The flash rom of LG G4 is in the format .kdz. also, i used the .kdz which i already had from almost 3 months ago when i had to flash my phone to stock. so I don't remember from where did i get it but here is a link that i extracted from IDM.
https://www.androidfilehost.com/?fid=24572369242688134
Download this file, then on the lg flash tool, select ''Upgrade'', select your .kdz file by clicking the rectangular bar next to 'bin file' and then flash it. That's all.
Click to expand...
Click to collapse
Thanks - you mean using LGUP tool? what mode do I have to put my phone into to run LGUP? LGUP is not seeing my phone, even though it shows up fine in windows.
---------- Post added at 02:44 PM ---------- Previous post was at 02:15 PM ----------
charmander21 said:
Thanks - you mean using LGUP tool? what mode do I have to put my phone into to run LGUP? LGUP is not seeing my phone, even though it shows up fine in windows.
Click to expand...
Click to collapse
Ah no worries, in download mode now.
Glad to know
charmander21 said:
Thanks - you mean using LGUP tool? what mode do I have to put my phone into to run LGUP? LGUP is not seeing my phone, even though it shows up fine in windows.
---------- Post added at 02:44 PM ---------- Previous post was at 02:15 PM ----------
Ah no worries, in download mode now.
Click to expand...
Click to collapse
Hey, i had to contact you again. Just wanted to ask if you by any chance had a cm13 backup or rom zip? I want to revert back.
Hey, sorry I don't, I wiped it I reverted to stock and the flashed cm 14.1 - its working well, but no xposed available yet.
Incidentally I think the whole problem was to do with updating from cm with xposed, to cm nougat (as yet no xposed) without disabling/uninstalling xposed first.
charmander21 said:
Hey, sorry I don't, I wiped it I reverted to stock and the flashed cm 14.1 - its working well, but no xposed available yet.
Incidentally I think the whole problem was to do with updating from cm with xposed, to cm nougat (as yet no xposed) without disabling/uninstalling xposed first.
Click to expand...
Click to collapse
Tell me this, when you had cm13, could you record 4k videos with any third party camera app? Or play 2k videos on youtube or a media player? Because i couldn't until i recieved a cm13 update which enabled those features. Now i actually have a cm13 backup which is dated 31st of august. And it doesn't let me record in 4k or play jn 2k. So I'm searching for someone who has a backup after that. And the reason i want to revert is actually theming option in cm 13. 14 doesnt have it yet. Hope it gets soon and also Xposed.
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
Tutorial(downgrade8.1.0=>7.1.1)use nougat stok/custom-roms on Oreo BC-12 bootloader
This tutorial is for the users wich are not satisfied by Oreo 8.1.1 rom
Also can be used by users wich changed the touchscreen from some reazons
and on Oreo 8.1.1 this new touchscreen not work
First got to Settings/System/Developer option and chec OEM-unlockin to be ENABLED!
for flashing twrp-recovery may be need to unlock the bootloader by code but it should work only with OEM-unlocking enabled
Downgrading with FASTBOOT!
1) Charge youre phone to at least 50-70%, better is 100%
2) Download the FILES necessary for downgrading
3) Reboot the phone in bootloader and connect to the pc
4) Opend the terminal and write "fastboot" or "mfastboot" depends by your instaled fastboot
5) Copy/Paste in terminal the lines writed in "fastboot-mfastboot.txt" atached to files
or write them one by one and press ENTER
WAIT 'till it finish
6) In bootloader screen, from buttons vol-up & vol-down navigate and set to "reboot recovery" and press Power
Phone should boot in TWRP-recovery!
Now you have to install a custom-rom or a stok-rom TWRP flashable with Install option
""for this use the instruction to install posted by the developer of each rom""
Also you can RESTORE an older 7.1.1 backup made before update to OREO
Reboot and enjoy by nougat-7.1.1 rom on oreo-8.1.0 bootloader
Downgrading with TWRP
Files to be flashed with TWRP for the users wich have olready the TWRP-recovery instaled!
1) Download the files
2) Copy the zip archive on the sdcard
3) Reboot the phone in TWRP-recovery
4) Search and install the zip
5) Install nougat 7.1.1 rom or restore an older backup made before update to OREO
Enjoy!
reserved
Thank You very much
---------- Post added at 06:02 PM ---------- Previous post was at 05:38 PM ----------
vaserbanix said:
This tutorial is for the users wich are not satisfied by Oreo 8.1.1 rom
Also can be used by users wich changed the touchscreen from some reazons
and on Oreo 8.1.1 this new touchscreen not work
First got to Settings/System/Developer option and chec OEM-unlockin to be ENABLED!
for flashing twrp-recovery may be need to unlock the bootloader by code but it should work only with OEM-unlocking enabled
Downgrading with FASTBOOT!
1) Charge youre phone to at least 50-70%, better is 100%
2) Download the FILES necessary for downgrading
3) Reboot the phone in bootloader and connect to the pc
4) Opend the terminal and write "fastboot" or "mfastboot" depends by your instaled fastboot
5) Copy/Paste in terminal the lines writed in "fastboot-mfastboot.txt" atached to files
or write them one by one and press ENTER
WAIT 'till it finish
6) In bootloader screen, from buttons vol-up & vol-down navigate and set to "reboot recovery" and press Power
Phone should boot in TWRP-recovery!
Now you have to install a custom-rom or a stok-rom TWRP flashable with Install option
""for this use the instruction to install posted by the developer of each rom""
Also you can RESTORE an older 7.1.1 backup made before update to OREO
Reboot and enjoy by nougat-7.1.1 rom on oreo-8.1.0 bootloader
Downgrading with TWRP
Files to be flashed with TWRP for the users wich have olready the TWRP-recovery instaled!
1) Download the files
2) Copy the zip archive on the sdcard
3) Reboot the phone in TWRP-recovery
4) Search and install the zip
5) Install nougat 7.1.1 rom or restore an older backup made before update to OREO
Enjoy!
Click to expand...
Click to collapse
Also, can I flash Stock Nougat (using fastboot) after this? And is there any chance of my device being hardbricked?
ShattrdChain said:
Thank You very much
---------- Post added at 06:02 PM ---------- Previous post was at 05:38 PM ----------
Also, can I flash Stock Nougat (using fastboot) after this? And is there any chance of my device being hardbricked?
Click to expand...
Click to collapse
No! you cant flash a full nougat rom with fastboot.
Bootloader cant be downgraded!
for hardbricked phones you have first to boot it using the sdcard img.
then when you get bootloader working without sdcard, can use this tutorial
Sent from my Moto G (5S) using Tapatalk
vaserbanix said:
No! you cant flash a full nougat rom with fastboot.
Bootloader cant be downgraded!
for hardbricked phones you have first to boot it using the sdcard img.
then when you get bootloader working without sdcard, can use this tutorial
Sent from my Moto G (5S) using Tapatalk
Click to expand...
Click to collapse
Oh ok. Thank You very much
I successfully rolled back to 7.1 using this method. No errors or issues. Everything worked flawlessly. A big thank you @vaserbanix
What are the problems with 8.1? I'm still on Android 7 (RETEU)
Argon007 said:
What are the problems with 8.1? I'm still on Android 7 (RETEU)
Click to expand...
Click to collapse
1. Oreo Battery drains considerably faster than 7.1. (But charges faster too)
2. Fingerprint unlocks slower than 7.1
3. Lags slightly when doing intensive tasks.
Now we need a maintainer for (a) Nougat rom(s)..
Ænimal said:
Now we need a maintainer for (a) Nougat rom(s)..
Click to expand...
Click to collapse
YES indeed!
Im in 8.1.1 stock rom. Can i install a custom 7.1.2 (ViperOS) with this method? Tks.
mysticauls said:
Im in 8.1.1 stock rom. Can i install a custom 7.1.2 (ViperOS) with this method? Tks.
Click to expand...
Click to collapse
lineage 14.1 work so it should work ViperOS too!
to be sure ask in ViperOS thread.
Thankyou!
Hello!
Do you lose biometrics by installing twrp?
vaserbanix said:
YES indeed!
Click to expand...
Click to collapse
LOS14.1 has been updated:
NEW BUILD: https://www.androidfilehost.com/?fid...63190603848665
Change log: November 18 Security Update
NOTE: Like so many other users, I too updated my device with OREO and stuck with that. I haven't tried downgrading it because I don't want to end up with a hard-bricked device once again. Point here is the new build is not tested. So please take a TWRP backup before using this build. Don't forget to post me even if works fine.
Thanks,
KS
Click to expand...
Click to collapse
EDIT: When I try to quote properly I get logged out for some reason, so see this thread obviously (and don't forget to thank @kalyansundhar ):
https://forum.xda-developers.com/moto-g5s/development/rom-lineageos-14-1-t3727918
Fantastic tutorial, vaserbanix. Thank you!
Does anybody know where can I get a nougat stock rom TWRP flashable? There is a thread with stock roms but all of them are only flashable via Fastboot...
I would like to get this in particular: [MONTANA_NPP26.102-49-14]
---------- Post added at 08:38 PM ---------- Previous post was at 08:13 PM ----------
ShattrdChain said:
I successfully rolled back to 7.1 using this method. No errors or issues. Everything worked flawlessly. A big thank you @vaserbanix
Click to expand...
Click to collapse
Thank you so much for your feedback, ShattrdChain! :good:
May I know what rom did you use for flashing with this method?
And do you know if bootloader needs to be unlocked in order to downgrade with this guide?
TWRP method doesn't work (bootloop), pls fix or delete.
FanderWasTaken said:
TWRP method doesn't work (bootloop), pls fix or delete.
Click to expand...
Click to collapse
i understand it work!
just chek the twrp version!
is posible the twrp to dont read some partitons.
this can make the differences betwen work or not
ask eric rutgers ( @GoldeneyeS2), he instaled sucesful that downgrade.zip
Thankyou!
vaserbanix said:
i understand it work!
just chek the twrp version!
is posible the twrp to dont read some partitons.
this can make the differences betwen work or not
ask eric rutgers ( @GoldeneyeS2), he instaled sucesful that downgrade.zip
Thankyou!
Click to expand...
Click to collapse
Its works great.
You can also use fastboot to downgrade!
can the downgrade be done without the bootloader unlocked?
the methods don't work for xt1799-2!
I tried to perform a factory reset from TWRP cause it wouldn't let me from Configuration>Reset and Restore (or something like that), and after a reboot system didn't launch, it said something about an encryption problem, so I decided to restore a system backup I did and now my phone is stuck in bootloop. Someone can point me in the right direction? Thanks in advance.
Yzakz said:
I tried to perform a factory reset from TWRP cause it wouldn't let me from Configuration>Reset and Restore (or something like that), and after a reboot system didn't launch, it said something about an encryption problem, so I decided to restore a system backup I did and now my phone is stuck in bootloop. Someone can point me in the right direction? Thanks in advance.
Click to expand...
Click to collapse
We're you on stock Orero, Pie? Or one of the custom Pie, Q ROMs?
Ainz_Ooal_Gown said:
We're you on stock Orero, Pie? Or one of the custom Pie, Q ROMs?
Click to expand...
Click to collapse
Stock Pie
Yzakz said:
Stock Pie
Click to expand...
Click to collapse
Yeah TWRP and Stock are at odds with each other.... You must fallow the guide to make TWRP and Stock compatible with each other when restoring.... alternatively you can try to flash one of the custom ROMs and see if it boots.
---------- Post added at 11:55 PM ---------- Previous post was at 11:51 PM ----------
This guide specifically https://forum.xda-developers.com/lg-v40/how-to/guide-twrp-data-access-stock-t3970149
Ainz_Ooal_Gown said:
Yeah TWRP and Stock are at odds with each other.... You must fallow the guide to make TWRP and Stock compatible with each other when restoring.... alternatively you can try to flash one of the custom ROMs and see if it boots.
---------- Post added at 11:55 PM ---------- Previous post was at 11:51 PM ----------
This guide specifically https://forum.xda-developers.com/lg-v40/how-to/guide-twrp-data-access-stock-t3970149
Click to expand...
Click to collapse
I tried with LineageOS but no luck. In fact, I tried to install LineageOS before I had this problem and even when TWRP said "Success", the phone booted into stock pie rom
Yzakz said:
I tried with LineageOS but no luck. In fact, I tried to install LineageOS before I had this problem and even when TWRP said "Success", the phone booted into stock pie rom
Click to expand...
Click to collapse
Did you switch slots?
Ainz_Ooal_Gown said:
Did you switch slots?
Click to expand...
Click to collapse
When? When installing LineageOS? To be honest right now I don't remember exactly what I did, but I'm 100% that I followed the write-up in the TWRP thread step by step.
Which slot should I select to install a custom rom?
Yzakz said:
Which slot should I select to install a custom rom?
Click to expand...
Click to collapse
When you install a ROM made for the V40 if your on Slot A when you boot into TWRP then the ROM installs in Slot B and if on B the it installs into A. But gapps and other flashable zips install into the current booted slot.
So flashing steps would be
1. Boot TWRP
2. Check which slot your on in the reboot menu
3. Flash ROM
4. Flash the TWRP recovery IMG. To ram disk
5. Go to reboot menu and select opposite Slot
6. Select reboot recovery and swipe to reboot
7.flash anything else gapps etc.
8. Reboot into your new working ROM.
Ainz_Ooal_Gown said:
When you install a ROM made for the V40 if your on Slot A when you boot into TWRP then the ROM installs in Slot B and if on B the it installs into A. But gapps and other flashable zips install into the current booted slot.
So flashing steps would be
1. Boot TWRP
2. Check which slot your on in the reboot menu
3. Flash ROM
4. Flash the TWRP recovery IMG. To ram disk
5. Go to reboot menu and select opposite Slot
6. Select reboot recovery and swipe to reboot
7.flash anything else gapps etc.
8. Reboot into your new working ROM.
Click to expand...
Click to collapse
I thought I did that, but when I rebooted the phone it booted to the stock Android rom
Yzakz said:
I thought I did that, but when I rebooted the phone it booted to the stock Android rom
Click to expand...
Click to collapse
My guess is you didn't select reboot recovery and instead hit reboot system...