Related
Hey guys, I've just rooted my KFHD 7" and am wanting to custom rom it with either CM or kinology, but am unsure how to go about it.
Firstly...do you need a fastboot cable to do this? If so can anyone provide a link to one on ebay.
Secondly...my kindle is on version 7.4.6 so can I put on a custom rom with this version or does it need to be a lower version eg 7.2.3 etc?
Thanks
You can do it without a fast boot cable
By sending a fast boot command BUT if a single thing goes wrong you will wind up waiting for one to be delivered to you.
Just search fastboot kindle on eBay
Sent from my XT907 using xda app-developers app
---------- Post added at 12:25 AM ---------- Previous post was at 12:24 AM ----------
FYI the kffa tool will do it without a fast boot cable
Sent from my XT907 using xda app-developers app
stryda said:
Hey guys, I've just rooted my KFHD 7" and am wanting to custom rom it with either CM or kinology, but am unsure how to go about it.
Firstly...do you need a fastboot cable to do this? If so can anyone provide a link to one on ebay.
Secondly...my kindle is on version 7.4.6 so can I put on a custom rom with this version or does it need to be a lower version eg 7.2.3 etc?
Thanks
Click to expand...
Click to collapse
You can flash it or use a fastboot command with a USB but as stated above, you will need one if something goes wrong.
I would definitely recommend taking it to 7.2.3 or 7.3. Using this tool will give you the option to use a standard USB and let the tool boot you into fastboot http://forum.xda-developers.com/showthread.php?t=2096888 Use that tool (KFFA) tool to root first and disable OTA updates. The restore tool listed in the reference thread works fine too. Fairly sure you need to be rooted for Bionary restore tool to work.
Then use this link for directions on flashing a custom ROM http://forum.xda-developers.com/showthread.php?t=2271909 read it all twice before proceeding.
This is the link that will be referenced in the first link I provided where the files are got from http://forum.xda-developers.com/showthread.php?t=2128848
Make sure you put a ROM and Gapps on the root of your SD card (just drag and drop like any data transfer on PC) before you flash just in case you do bootloop you can go into TWRP and flash it.
I would totaly recommend having fastboot cable first, I don't know why by my KFHD simply don't boot into the fastboot any other way then thru fastboot cable, when connecting normal USB it boot regulary into the rom. I had also 7.4.6 as you do, so it might caused by this. Soldering your own cable is not that hard, I had my coleague do it for my If you find anyone with soldering iron, you are good to go, there are plenty of tutorials how to make one. (solder pin 1 to the pin 4 that is empty by default basicaly). It will save you lot of nerves later on.
I started by softbricking my kindle while toying with build.prop so I went directly from there to custom rom having KFFA on you can help you lot also. First I flashed 7.2.3 from it, then rooted from it and then I went to 2nd bootloader and TWRP tutorial. from then on its just matter of flashing rom as on any other android device.
Q&A for [Root] Root and TWRP for R
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Root] Root and TWRP for R. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
I couldn't get TWRP to stick even with a custom kernel. When I executed a fastboot command to boot from the TWRP image it said that the image is corrupted and not bootable. Tried redownloading ~4 times all with the same error. On latest OTA update for LGGWR.
Hi,
when launch SuperSU appear this error:
"about"
application supersu crashed abnormally
Click to expand...
Click to collapse
Ok this might sound like a stupid question but I just had some problems installing TWRP + rooting and now that everything seems to be working fine I want to check that root is actually working so... is there any way to do that? How can I check that su access is available?.
good question.
I have another problem: I unlocked the bootloader, flashed TWRP but then I can't push Supersu to the watch in the bootloader mode, because the device can't be found (adb devices).
When I try to check if TWRP is on the watch and I say "adb reboot recovery" I only see the original recovery although the flashing of TWRP ran smoothly.
Can anyone help me?
Thanks in advance!!
---------- Post added at 09:57 AM ---------- Previous post was at 09:18 AM ----------
OK, sorry - It's me again.
I made the mistake that I didn't put the twrp.img into the fastboot folder
although adb always replied that the flashing was successfull.
Anyway - twrp is now installed but I had the same issue as mentioned above: Supersu can't be pushed because there is no device to be found. Then I went into twrp which prompted me that the device doesn't seem to be rooted and I affirmed to install supersu. Now when I am back into the normal mode of the watch supersu pops up but can't be installed because it crashes everytime.
---------- Post added at 10:26 AM ---------- Previous post was at 09:57 AM ----------
I flashed Supersu 2.46 by the way
Hey Kreiger1981,
I had also a lot of problems with rooting the watch., but finally it's working now using the steps described in this thread and WinDroid.
But I had to disconnect the usb wire multiple times in some steps. Than WinDroid received the signal from the watch and triggered e.g. the installation of TWRP.
Hope this helps a bit.
I also have the same issue with su not installing with the wintool (no adb drivers). Also getting the force close of su after restarting watch like the others have mentioned here. I wanted to install the wifi mod also, can't figure that out either. not to familure with adb, and was hoping the wintool would install it to the phone. No luck so far. Any suggestions would be appreciated.
Thanks.
ejl2002 said:
I also have the same issue with su not installing with the wintool (no adb drivers). Also getting the force close of su after restarting watch like the others have mentioned here. I wanted to install the wifi mod also, can't figure that out either. not to familure with adb, and was hoping the wintool would install it to the phone. No luck so far. Any suggestions would be appreciated.
Thanks.
Click to expand...
Click to collapse
I've done this multiple times and sometimes the behaviour is a little bit strange but in the end these are my steps to flash the watch
(I'm flashing everything, so be aware that every data from the watch will be deleted
1. Watch is on and home screen is visible
1. a) adb push supersu.zip /sdcard/
1.b) adb push lenok_wifi_zip-02.zip /sdcard/
2. adb reboot-bootloader
3. Check "fastboot devices" if device is available, if not, unplug cable and reconnect it (I have to do it everytime for fastboot!)
4. fastboot flash boot boot_gwr_5.1.1.img
5. fastboot flash system system_gwr_5.1.1.img
6.a) fastboot flash recovery recovery.img
6.b) fastboot flash recovery twrp-2.8.6.0-lenok.img
-> this is strange for me: If I only flash twrp, then twrp will not be started. If the original recovery.img is flashed before, then it's working!
7.) In twrp install supersu.zip
8) in twrp install lenok_wifi_zip-02.zip
Hope this helps a bit
Thanks for your help, I finally figured out how to use adb, and I was able to push the superuser file and wifi zip. All is working well, thanks again.
fastboot not finding my watch
hi all, i am trying to unlock my g watch r and install twrp the problem i have is after i reboot into fastboot, fast boot cannot find my device, it still shows in my computers device manager list as a android bootloader interface but fast boot commands all just say waiting for device, i have tried every driver i can find and have made no progress, i have also tried a factory reset and still nothing.
any ideas ?
I DL the twrp on post 1 and I got the twrp...but it has ext img.dmg. .... Not sure how to convert to img only? I tried flashing it and it gave me an error.
---------- Post added at 03:11 PM ---------- Previous post was at 02:31 PM ----------
I managed to get the right img. file....however I can't get this flashed at all. Tried changing the name...I made sure the "img" wasnt duplicated. But I keep getting and "error cannot load". BY THE WAY...I'M USING A MAC!!!DONT KNOW IF THAT MAKES A DIFFERENCE
Please help....TIA
---------- Post added at 03:28 PM ---------- Previous post was at 03:11 PM ----------
I'm curious...since I can't get Twrp to flash..... do i have to use a custom recovery to flash the su? I can get into stock recovery....can i install the su via adb in stock recovery?
Okay...with a little surfing on the information highway and making some connections....I figured out how to do use this method on Mac. If anyone has any questions about the method i used... hit reply.
Thanks to the og post.
Sent from my Nexus 6 using Tapatalk
Rooted!
Using posts #1 and #130 I successfully rooted my LG Watch R! Thanks clicked, of course!
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
ok, i am stuck on my boot up screen. i flashed a zip file xposed arm zip. after the reboot it will not pass the boot animation screen. now on my old Motorola phone, i would do the pwr + vol keys to boot back in to recovery. well this does no work on my X. any one have any ideas. I am rooted, unlocked, twrp was installed from play store, & i did do a back up. thanks
JWACK72 said:
ok, i am stuck on my boot up screen. i flashed a zip file xposed arm zip. after the reboot it will not pass the boot animation screen. now on my old Motorola phone, i would do the pwr + vol keys to boot back in to recovery. well this does no work on my X. any one have any ideas. I am rooted, unlocked, twrp was installed from play store, & i did do a back up. thanks
Click to expand...
Click to collapse
What device do you have, XT1095, XT1097, etc? And you are not able to boot into the bootloader using vol down + power correct?
It was a 1096, now its trash. it would go into fastboot, but could not get into twrp recovery. its done. RIP
JWACK72 said:
It was a 1096, now its trash. it would go into fastboot, but could not get into twrp recovery. its done. RIP
Click to expand...
Click to collapse
If it boots to fastboot, it's not dead. Just reflash the recovery and you're good to go.
Sent from my XT1095 using Tapatalk
Was there a resolution for this? I'm having a similar problem. I'm not sure how I got to this status, but here's what I'm dealing with:
Device: XT1095
Bootloader: Unlocked
Rooted, ROM - Resurrection Remix, TWRP
Turning on the phone reaches the RR bootsplash and proceeds to bootloop.
When holding down the power and volume down, it will enter fastboot.
When I try to open TWRP recovery, it'll show the blue TWRP screen and just sit there.
I have tried to reinstall TWRP, but that has no effect. I didn't want to manually flash another ROM or go back to stock because at least now it seems USB debugging is on and if I flashed a ROM I cant be sure I'd be able to turn it on. Do any of you pros have some ideas hove I can get back into my phone? Thanks
bibbin said:
I have tried to reinstall TWRP, but that has no effect. I didn't want to manually flash another ROM or go back to stock because at least now it seems USB debugging is on and if I flashed a ROM I cant be sure I'd be able to turn it on. Do any of you pros have some ideas hove I can get back into my phone? Thanks
Click to expand...
Click to collapse
Do you have a USB-OTG device plugged in while trying to start TWRP? If so remove it, you can mount it after TWRP starts if this helps.
Have you tried a different build of TWRP? I'm currently using the one built by invisiblek, one of the CM devs for the victara. It was built and posted on December 8th and is here: http://www.invisiblek.org/twrp/twrp_2.8.7.0-0624b8bd_victara.img
Have you tried flashing the stock recovery to see if that will start? If it does, you could use the factory reset option there and then try reinstalling TWRP. (TWRP has a settings directory in /sdcard and maybe that is corrupted.)
There have been a few people posting with this problem but I've not seen a definitive fix for it.
Thank for the quick response. No, I don't have USB-OTG inserted. It is using TWRP 2.8.7.1. No, I haven't tried installing the version you mentioned. What I did do was attempt to flash the pre-installed TWRP 2.8.1.0 via MOTO X TOOLKIT. It failed. I'm not very experienced at using ADB manually. As I mentioned, I've been reluctant to flash another ROM (custom or stock) because I don't want to get stuck with USB debugging inactive with no way to get in far enough to reactivate it.
---------- Post added at 04:32 PM ---------- Previous post was at 03:40 PM ----------
If I manage to install the invisiblek TWRP and it opens properly will I then be able to restore the backups created with TWRP 2.8.7.1?
If that's the case, I need to find a tutorial on installing TWRP manually via ADB, right? I usually install TWRP via TWRP Manager.
bibbin said:
Thank for the quick response. No, I don't have USB-OTG inserted. It is using TWRP 2.8.7.1. No, I haven't tried installing the version you mentioned. What I did do was attempt to flash the pre-installed TWRP 2.8.1.0 via MOTO X TOOLKIT. It failed. I'm not very experienced at using ADB manually. As I mentioned, I've been reluctant to flash another ROM (custom or stock) because I don't want to get stuck with USB debugging inactive with no way to get in far enough to reactivate it.
---------- Post added at 04:32 PM ---------- Previous post was at 03:40 PM ----------
If I manage to install the invisiblek TWRP and it opens properly will I then be able to restore the backups created with TWRP 2.8.7.1?
If that's the case, I need to find a tutorial on installing TWRP manually via ADB, right? I usually install TWRP via TWRP Manager.
Click to expand...
Click to collapse
That's interesting, the TWRP Manager has never worked correctly for me although it's been a long time since I've tried it.
To flash manually, you actually need fastboot which is usually installed along with adb. If you open a command window, and type in fastboot and it runs, the rest is pretty easy. If it doesn't run, this thread has the 15 second ADB/Fastboot installer, select to install it system-wide: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Download the recovery image, rename the file to twrp.img, then open a command window in the folder where you downloaded it (type cmd then Enter in the address line at the top of the folder window.)
When the command window is open and the phone is in bootloader mode and connected to the computer with the USB cable, enter the command "fastboot device" (without the quotes) If everything is working it will list the serial number of your phone.
Then enter "fastboot flash recovery twrp.img" (without the quotes) to start the flashing process, ignore the size mismatch message. It will only take a few seconds to complete.
Use the volume down key to highlight recovery, then volume up to select it. Hopefully TWRP will boot up and you'll be good to go!
Well, reinstalling TWRP didn't fix it. Thoughts? Anyone?
bibbin said:
Well, reinstalling TWRP didn't fix it. Thoughts? Anyone?
Click to expand...
Click to collapse
Reflash stock rom from fastboot.
Sent from my XT1095 using Tapatalk
UPDATE: Thanks all. Well, after fiddling around with various methods of reinstalling TWRP, I managed to get it reinstalled and all is back to normal now.
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