Related
( I posted this elsewhere, but i guess its beter in the actual HTCONE section) , mod feel free to delete my other one, thank you.
Good afternoon, !!!
First and foremost , I want to thank you all in advance for ANY and help, time & consideration with my current issue. I will try my best to be clear, and give all relevant info here in my first post. Please bear with me, I am pretty good when it comes to following directions, but i havent been able to find a CLEAR solution to this yet, and worried about further screwing up my phone.
** I use a mac. I currently dont have access to a PC, so i am looking for a mac remedy if possible.
I have an HTCONE m7. Tmobile.
- Bootloader - Unlocked
- S- ON
- Rooted
I kept getting a OTA software update notice for 5.14xxx, i understand the install kept failing due to the bootloader being unlocked and/or root. So after being annoyed for not able to get it, i began googling ways to get the update but to no avail. So i decided to do CM11, & recovery which i installed with no problem via, Cyanogenmod Installer.
After doing so, i realized i lost my Tmobile Wifi Calling (Yes, my own fault for not further checking that scenario before doing cm11), The wifi calling is needed 10000%, due to bad service in my apartment. Prior to finding out that cm11 doesnt contain the tmobile wifi calling , I attempted another system update thru the phone, (I assume it was updating cm11).
This is where the problem began, phone rebooted to Cyanogenmod simple recovery ,
1st few times that i tried = "apply update" > choose from internal storage , i searched different folders for the "update" file, but to no avail. The phone wouldnt start up, or install anything , and will just stay on the simple recovery. I even attempted an adb sideload. But couldnt figure that out correctly either.
After a few failed attempts, I tried wiping the phone, cache, factory reset etc. now the phone still stays on simple recovery, and all folders are gone, except for an o/ folder, that contains a clockworkmod folder, which contains nothing.
So now basically,Do i have to eventually get back to STOCK on this phone, to regain tmobile wifi calling ? IF So i need the easiest, mac friendly route to go .
Again, i thank you ALLLLL in advance, & my apologies if this is in the wrong section. Please note ive done my fair share of googling , and reading up on this. But consistently run into a problem.
OnlyEYEShine said:
Good afternoon, !!!
First and foremost , I want to thank you all in advance for ANY and help, time & consideration with my current issue. I will try my best to be clear, and give all relevant info here in my first post. Please bear with me, I am pretty good when it comes to following directions, but i havent been able to find a CLEAR solution to this yet, and worried about further screwing up my phone.
** I use a mac. I currently dont have access to a PC, so i am looking for a mac remedy if possible.
I have an HTCONE m7. Tmobile.
- Bootloader - Unlocked
- S- ON
- Rooted
I kept getting a OTA software update notice for 5.14xxx, i understand the install kept failing due to the bootloader being unlocked and/or root. So after being annoyed for not able to get it, i began googling ways to get the update but to no avail. So i decided to do CM11, & recovery which i installed with no problem via, Cyanogenmod Installer.
After doing so, i realized i lost my Tmobile Wifi Calling (Yes, my own fault for not further checking that scenario before doing cm11), The wifi calling is needed 10000%, due to bad service in my apartment. Prior to finding out that cm11 doesnt contain the tmobile wifi calling , I attempted another system update thru the phone, (I assume it was updating cm11).
This is where the problem began, phone rebooted to Cyanogenmod simple recovery ,
1st few times that i tried = "apply update" > choose from internal storage , i searched different folders for the "update" file, but to no avail. The phone wouldnt start up, or install anything , and will just stay on the simple recovery. I even attempted an adb sideload. But couldnt figure that out correctly either.
After a few failed attempts, I tried wiping the phone, cache, factory reset etc. now the phone still stays on simple recovery, and all folders are gone, except for an o/ folder, that contains a clockworkmod folder, which contains nothing.
So now basically,Do i have to eventually get back to STOCK on this phone, to regain tmobile wifi calling ? IF So i need the easiest, mac friendly route to go .
Again, i thank you ALLLLL in advance, & my apologies if this is in the wrong section. Please note ive done my fair share of googling , and reading up on this. But consistently run into a problem.
Click to expand...
Click to collapse
Here is a TWRP nandroid backup. You will have to put TWRP 2.6.3.3 on your phone. You will unzip the file and the resulting folder you will put on your phone in the following directory: //sdcard/TWRP/BACKUP/<Serial #>/<Name_of_folder>. If you are not able to get TWRP on your phone and the folder on your phone then you will need to find a Windows machine. Here is what you will need to do:
** Extract the RUU and grab the rom.zip file. This is the most important file you need from the RUU and afterwards you can delete the RUU exe if you want. To get the rom.zip from your RUU exe file, you just need to run the RUU exe file once, and then when the window is ready and waiting for you to press on the "Next" button, just leave it open and go to your temp folder. I'm using Windows XP SP3 32-bit and my temp folder is located at this path: C:\Documents and Settings\Administrator\Local Settings\Temp. Now, you will see several files and folders. Sort everything in that temp folder based on "Date Modified" with the most recent folder showing up above all other folders. This is the folder you want. The folder name will be bunch of letters and numbers. Inside that folder you will find several files, but what you need is rom.zip and android-info.txt. Copy both these files and paste them somewhere safe on your hard drive. The android-info.txt contains crucial information about the compatibility of that RUU for your phone.
** Go to your bootloader. Do:
Code:
fastboot oem lock
fastboot oem rebootRUU
This will reboot your HTC One and you will see a black screen with a silver HTC logo. Now, you will need to access the rom.zip file and flash it. I have copied my rom.zip to my adb folder located at: C:/mini-sdk/rom.zip. So, type:
Code:
fastboot flash zip C:/mini-sdk/rom.zip
Don't touch anything during the flash process. It will start and after some time, you will see FAILED error. Don't worry; it's the file preparation process if you have firmware higher than that of the RUU. Just do the same command again and the flash process will complete successfully this time. Look at the Command Prompt to know when the flash is complete. At the same time if you look at your phone, you will notice a green progress bar. When the flashing is complete on the Command Prompt, you will notice that the green bar is stuck at about 95%. This is normal. It's just a bug in the progress bar - what matters is the output from the Command Prompt window.
** Then, you reboot. Do:
Code:
fastboot reboot
This will restart your phone. Let it boot up. It might take a little longer for the first boot up sequence. You will then have completely stock software (firmware & ROM). Go to your bootloader and check that you are S-ON/OFF and Bootloader lock/unlock are unchanged from before the RUU rom.zip flashing procedure. You can now also receive OTA updates.
majmoz said:
Here is a TWRP nandroid backup. You will have to put TWRP 2.6.3.3 on your phone. You will unzip the file and the resulting folder you will put on your phone in the following directory: //sdcard/TWRP/BACKUP/<Serial #>/<Name_of_folder>. If you are not able to get TWRP on your phone and the folder on your phone then you will need to find a Windows machine. Here is what you will need to do:
** Extract the RUU and grab the rom.zip file. This is the most important file you need from the RUU and afterwards you can delete the RUU exe if you want. To get the rom.zip from your RUU exe file, you just need to run the RUU exe file once, and then when the window is ready and waiting for you to press on the "Next" button, just leave it open and go to your temp folder. I'm using Windows XP SP3 32-bit and my temp folder is located at this path: C:\Documents and Settings\Administrator\Local Settings\Temp. Now, you will see several files and folders. Sort everything in that temp folder based on "Date Modified" with the most recent folder showing up above all other folders. This is the folder you want. The folder name will be bunch of letters and numbers. Inside that folder you will find several files, but what you need is rom.zip and android-info.txt. Copy both these files and paste them somewhere safe on your hard drive. The android-info.txt contains crucial information about the compatibility of that RUU for your phone.
** Go to your bootloader. Do:
Code:
fastboot oem lock
fastboot oem rebootRUU
This will reboot your HTC One and you will see a black screen with a silver HTC logo. Now, you will need to access the rom.zip file and flash it. I have copied my rom.zip to my adb folder located at: C:/mini-sdk/rom.zip. So, type:
Code:
fastboot flash zip C:/mini-sdk/rom.zip
Don't touch anything during the flash process. It will start and after some time, you will see FAILED error. Don't worry; it's the file preparation process if you have firmware higher than that of the RUU. Just do the same command again and the flash process will complete successfully this time. Look at the Command Prompt to know when the flash is complete. At the same time if you look at your phone, you will notice a green progress bar. When the flashing is complete on the Command Prompt, you will notice that the green bar is stuck at about 95%. This is normal. It's just a bug in the progress bar - what matters is the output from the Command Prompt window.
** Then, you reboot. Do:
Code:
fastboot reboot
This will restart your phone. Let it boot up. It might take a little longer for the first boot up sequence. You will then have completely stock software (firmware & ROM). Go to your bootloader and check that you are S-ON/OFF and Bootloader lock/unlock are unchanged from before the RUU rom.zip flashing procedure. You can now also receive OTA updates.
Click to expand...
Click to collapse
Thanks for the info !!!,
But right off of the top, i am confused. I am currently downloading TMRP nandroid back up, as you said in beginning. Thing is i am unaware how to get that file onto my phone. Since it is stuck on the recovery page.... (DL is going to take a while on this machine), But if this fails, ill probably end up just tossing the phone, as i dont know anyone , nor have access to a PC machine. Sadly.
update - will attempt to push this thru via Terminal / adb will keep u posted !
-Update .. @majmoz well, i got hold of a PC laptop, did an adb / fastboot installed, dl'd the RUU, but i cant find the file from it after running the RUU. I even did cmd - Echo %temp% to make sure i was in the correct temp folder etc. Searched every sub folder there , and no zip files , or android.txt files was found . and i sorted them as u said as well.
Will continue trying tho...
Updated again - Well this time as RUU was installing again, i went to the temp files faster, and found 2 files Rom_01 & Rom_02 both zip files. But was unable to find any android text file. So now im at a standstill.
OnlyEYEShine said:
update - will attempt to push this thru via Terminal / adb will keep u posted !
-Update .. @majmoz well, i got hold of a PC laptop, did an adb / fastboot installed, dl'd the RUU, but i cant find the file from it after running the RUU. I even did cmd - Echo %temp% to make sure i was in the correct temp folder etc. Searched every sub folder there , and no zip files , or android.txt files was found . and i sorted them as u said as well.
Will continue trying tho...
Click to expand...
Click to collapse
The RUU Update Window should still be on the computer when you are looking for the files. Once the RUU goes past the first screen, the folder will be erased. You should also sort the /Temp folder by date so the most recent folder is at the top.
majmoz said:
The RUU Update Window should still be on the computer when you are looking for the files. Once the RUU goes past the first screen, the folder will be erased. You should also sort the /Temp folder by date so the most recent folder is at the top.
Click to expand...
Click to collapse
If i would of refreshed the page i would of seen your response, as i just re-editted my last post. with another update. =0)
I found 2 files with rom, Rom_01 & Rom_02 , both are zip files. but i cant find any android text file .
another thing, i am trying to find adb devices , but it is not locating my phone . I was able to earlier reboot into bootloader , etc. Now it tells me repeatedly that device is not found , i have tried adb kill-server, start-server etc. .. and phone is still on cyanogen simple recovery screen . .
Thanks again for ur time & help .. .definetly is appreciated !
OnlyEYEShine said:
If i would of refreshed the page i would of seen your response, as i just re-editted my last post. with another update. =0)
I found 2 files with rom, Rom_01 & Rom_02 , both are zip files. but i cant find any android text file .
another thing, i am trying to find adb devices , but it is not locating my phone . I was able to earlier reboot into bootloader , etc. Now it tells me repeatedly that device is not found , i have tried adb kill-server, start-server etc. .. and phone is still on cyanogen simple recovery screen . .
Thanks again for ur time & help .. .definetly is appreciated !
Click to expand...
Click to collapse
Keep both ROM files and save them for future use. Since you are able to use the PC, I would just run the RUU from the PC. Then in the future try to figure out how to run the two ROM files on your Mac. Just start the RUU again and let it do its thing.
majmoz said:
Keep both ROM files and save them for future use. Since you are able to use the PC, I would just run the RUU from the PC. Then in the future try to figure out how to run the two ROM files on your Mac. Just start the RUU again and let it do its thing.
Click to expand...
Click to collapse
Hey hey , good morning. Had some errands to do last nite then fell asleep. Going to attempt this again today . Oh, and i did run the RUU on the PC so thats where ill keep them also.
Will attempt to see if i can even connect to the phone with ADB, it seemed as if i was unable to last nite.
-update I got the phone to load to bootloader, & to fastboot usb I will try now to attempt this after coffee.. =0)
HAHAHAHHAHA ,, Oh man. Ok well being that it was pretty late last nite, and i had just woken up earlier .... I didnt realize that the RUU actually does the entire process on the PC. and that i DIDNT need to use cmd., and adb etc.
I want to thank you a TON @majmoz With my day or two of aggravation , then to just not get it right last nite.. I think i wasnt there mentally to actually read and pay attention.
My phone is in set up mode now. So i am 99% sure it is all good... Again, thanks , i definetly appreciate it !
OnlyEYEShine said:
HAHAHAHHAHA ,, Oh man. Ok well being that it was pretty late last nite, and i had just woken up earlier .... I didnt realize that the RUU actually does the entire process on the PC. and that i DIDNT need to use cmd., and adb etc.
I want to thank you a TON @majmoz With my day or two of aggravation , then to just not get it right last nite.. I think i wasnt there mentally to actually read and pay attention.
My phone is in set up mode now. So i am 99% sure it is all good... Again, thanks , i definetly appreciate it !
Click to expand...
Click to collapse
Glad you are back in business! :good:
@majmoz Hey i tried sending a PM earlier . but i see it never went thru in my sent Messages.
Just wondering if you can help me one last time. As i stated, i MUST have tmobile wifi calling. I initially had my bootloader unlocked months ago, and only rooted it few days before this brick issue.
Now since i did this process to fix the phone, i see bootloader = Relocked.
I dont want to add any custom roms etc, I simple want to root the device again. I know when i just did it , it was quick n easy and simple. But as im googling for the process now, i cant seem to find any that is similar to what i just did a few days ago. The processes seem extremely long. I think i just added a superuser apk of sorts , and it rooted.
Thanks again !
OnlyEYEShine said:
@majmoz Hey i tried sending a PM earlier . but i see it never went thru in my sent Messages.
Just wondering if you can help me one last time. As i stated, i MUST have tmobile wifi calling. I initially had my bootloader unlocked months ago, and only rooted it few days before this brick issue.
Now since i did this process to fix the phone, i see bootloader = Relocked.
I dont want to add any custom roms etc, I simple want to root the device again. I know when i just did it , it was quick n easy and simple. But as im googling for the process now, i cant seem to find any that is similar to what i just did a few days ago. The processes seem extremely long. I think i just added a superuser apk of sorts , and it rooted.
Thanks again !
Click to expand...
Click to collapse
Here is a step by step guide with pictures. This is called the HTCDev method and it is pretty standard. It just looks like a lot of steps but it isn't that bad.
majmoz said:
Here is a step by step guide with pictures. This is called the HTCDev method and it is pretty standard. It just looks like a lot of steps but it isn't that bad.
Click to expand...
Click to collapse
Gotcha, will try this in an hour or so . Have some errands to run. Thanks again !
OnlyEYEShine said:
Gotcha, will try this in an hour or so . Have some errands to run. Thanks again !
Click to expand...
Click to collapse
Keep this for future reference on how to flash the two RUU ROM zip files:
From nkk71's SuperGUIDE to returning 100% back to stock - Post #1211
http://forum.xda-developers.com/showpost.php?p=55921790&postcount=1211
How to flash two RUU ROM zip files
Code:
[B]fastboot oem rebootRUU
fastboot flash zip RUU_ROM_1.zip [COLOR="Red"][I]<-- hboot preupdate[/I][/COLOR]
fastboot flash zip RUU_ROM_1.zip[COLOR="Red"][I] <-- rest of the files in "1"[/I][/COLOR]
fastboot flash zip RUU_ROM_2.zip [I][COLOR="Red"]<-- files in "2" (kernel, touchscreen drivers 2, wipe userdate)[/COLOR][/I]
fastboot reboot-bootloader
[/B]
Click to expand...
Click to collapse
I just got my motorola yesterday. I did quite a few things like unlocking it and rooting it..After my first initial root it worked fine but earlier today i decided to install lollipop. I was using the twrp version 2.7 to install the rom but i realised it wasnt working till i tried a few more time and it finally it. I tried back up my stock 4.4.4 room before i installed my new rom but it failed several times because i think the recovery was faulty to say the least. Anyways my lollipop worked very fine but i notice anytime i restarted the phone it took a long freaking time to restart but it was working normal as usual until i restarted my phone another time and realised i couldn't go past the bootanimation.It takes forever but i never get past it. I then decided to flash the twrp 2.8.0.1. After flashing i realised I could do a backup but it was too late. I tried a few tricks I've always used to get past the bootanimation like mounting the storage but it never shows up on my pc. I also tried side loading the rom using the adb sideload command but it never workedd.it always shows up saying "error: device not found" but when i go back to the bootloader and use the fastbootdevices command it shows up my device. IS there any recovery that will allow me to sucessfully mount my storage or sideload my rom without all this hussle?Even my the the bootloader unlock warning reboots several times before getting to the never ending bootanimation
rom:TitanPrimeROMv1.3-XT1068-69_RC1
XT1068
Rooted
TWRP 2.0.8.1
Window 8.1 64bit
I already have my mini sdk files
There's a number of guides in this subforum that goes through flashing the stock firmware for your phone. The reason you're getting bootloops is because there's currently no stable way to get root access on Lollipop for this phone, but it is being worked on.
ADB can be a bit finicky, so it'd probably be easier to have your ROM on the phone itself, whether in the data/media/ folder in Internal Storage, or on an SD card, since neither are wiped whenever you factory reset or clean your phone. TWRP 2.8.2.0 and above allows you to enable MTP mode so you can move your files straight onto or off your phone.
Actaully i managed to root my phone using chainfare's auto rode for the moto G.I just also installed twrp 2.8.0.3. Unfortunately,I dont have any rom on my phone which is bummer. Yh I do get to MTP enable my device in recovery but it never shows up on my pc.I have had issues like this before and I got it done in minutes without no problem..This is my first motorola device and I'm regretting my choice in buying this phone
sleekykenny said:
Actaully i managed to root my phone using chainfare's auto rode for the moto G.I just also installed twrp 2.8.0.3. Unfortunately,I dont have any rom on my phone which is bummer. Yh I do get to MTP enable my device in recovery but it never shows up on my pc.I have had issues like this before and I got it done in minutes without no problem..This is my first motorola device and I'm regretting my choice in buying this phone
Click to expand...
Click to collapse
Did you try manually selecting the driver is device manager?
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657 This thread is your best friend. The other thing is that you'll probably need to uninstall the drivers for your phone from Hardware Manager on your OS, unplug your phone, then plug it back in when you're in recovery, and your OS should pull the right drivers to get ADB working. Still, you've got fastboot so the best option for you at the moment is to just restore your phone to stock and go from there.
As I said, though, root doesn't work on Lollipop for our phone yet, and AFAIK we don't have the kernel sources yet for Chainfire (the developer of SuperSU amongst other things) to get root access working without causing bootloops.
Traediras said:
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657 This thread is your best friend. The other thing is that you'll probably need to uninstall the drivers for your phone from Hardware Manager on your OS, unplug your phone, then plug it back in when you're in recovery, and your OS should pull the right drivers to get ADB working. Still, you've got fastboot so the best option for you at the moment is to just restore your phone to stock and go from there.
As I said, though, root doesn't work on Lollipop for our phone yet, and AFAIK we don't have the kernel sources yet for Chainfire (the developer of SuperSU amongst other things) to get root access working without causing bootloops.
Click to expand...
Click to collapse
I tried this thread but the problem is that the required mfastboot-v2 file link is not working for me.Anytime i try downloading it i get the message "Sorry, this file is infected with a virus,Only the owner is allowed to download infected files."
sleekykenny said:
I tried this thread but the problem is that the required mfastboot-v2 file link is not working for me.Anytime i try downloading it i get the message "Sorry, this file is infected with a virus,Only the owner is allowed to download infected files."
Click to expand...
Click to collapse
Huh.
http://forum.xda-developers.com/showpost.php?p=47820707 This contains just the mfastboot.exe file for each OS, it /should/ work since it's essentially the same file. Just put the files in that .zip into your folder with adb and fastboot in it, and you should be good to go.
Traediras said:
Huh.
http://forum.xda-developers.com/showpost.php?p=47820707 This contains just the mfastboot.exe file for each OS, it /should/ work since it's essentially the same file. Just put the files in that .zip into your folder with adb and fastboot in it, and you should be good to go.
Click to expand...
Click to collapse
Thanks Dude, After your last message I rechecked the mfastboot-v2 folder on the thread and realised the only new file in there was the mfastboot.exe file so i quickly googled it and saw another thread in which i found the file.I downloaded it and then executed all the commands. Goshh I finally saw my phone boot up in a long time which brought a huge smile to my face.
I would like Thank all of you guys who took the time out to visit this thread and give me suggestions. THANK YOU BROS
I really appreaciate it. Happy new year
Glad to hear everything worked out for you. Happy New Year to you too.
Duplicate thread created by OP
Original is here
Please do not create multiple threads again.
Thread closed
I wanted to go back from Oxygen OS 5 to 4. And started with making a full wipe, data and system. Now I know that was my mistake. But I did it anyways because it worked the same way before as i upgraded to Oxygen OS Beta xx (An Oreo one).
For refreshing 1I did go trough some tutorials but the process was how I remembered it. I did not change the computer or reseted it since the last time. So I was confidend I still got everthing istalled properly. Driver for my OnePlus 3T seemed to have been installed, too, because I drag&dropped the files I wanted to save on my computer from my OP3T priviously.
But then I starttyped everything in cmd this came up. https://i.imgur.com/Zmo1qeD.png?1
Here is the Installation Folder of ADB with the new Rom inside: https://i.imgur.com/9RD20Ac.png
I already tried this workaround: https://forum.xda-developers.com/showpost.php?p=69648733&postcount=47
As I researched on my own the idea came to my mind that adb/windows does not recognize my device. This thing is listed in my device manager: https://i.imgur.com/VO86zuw.png
Thank you in advance! Hope u guy can help me.
Edit: After some digging depper I think I found my mistake. ADB only works when the devices is booted into OS. Which is not possible anymore for me. Now I need to find a way around that.....
You will need a recovery for adb sideload. Easiest is to use twrp, first flash twrp, and when in twrp click on sideload so the device is able to receive the files. If you are trying to sideload stock rom, you can also flash stock recovery and click sideload from there.
I guess you are now trying to sideload a rom in fastboot mode?
Edit: excuse me, i think i misunderstood you.
knijntjes said:
You will need a recovery for adb sideload. Easiest is to use twrp, first flash twrp, and when in twrp click on sideload so the device is able to receive the files. If you are trying to sideload stock rom, you can also flash stock recovery and click sideload from there.
I guess you are now trying to sideload a rom in fastboot mode?
Edit: excuse me, i think i misunderstood you.
Click to expand...
Click to collapse
At the moment I am trying to find a way to install TWRP without an OS installed and OEM locked. In research I recognized this as the easiest way to install a new ROM. The only thing I need TWRP now.
If I were you, I'd flash the phone using the unbrick method and unlock the bootloader, so you won't lock yourself out in the future
TaddyQuup said:
I wanted to go back from Oxygen OS 5 to 4. And started with making a full wipe, data and system. Now I know that was my mistake. But I did it anyways because it worked the same way before as i upgraded to Oxygen OS Beta xx (An Oreo one).
For refreshing 1I did go trough some tutorials but the process was how I remembered it. I did not change the computer or reseted it since the last time. So I was confidend I still got everthing istalled properly. Driver for my OnePlus 3T seemed to have been installed, too, because I drag&dropped the files I wanted to save on my computer from my OP3T priviously.
But then I starttyped everything in cmd this came up. https://i.imgur.com/Zmo1qeD.png?1
Here is the Installation Folder of ADB with the new Rom inside: https://i.imgur.com/9RD20Ac.png
I already tried this workaround: https://forum.xda-developers.com/showpost.php?p=69648733&postcount=47
As I researched on my own the idea came to my mind that adb/windows does not recognize my device. This thing is listed in my device manager: https://i.imgur.com/VO86zuw.png
Thank you in advance! Hope u guy can help me.
Edit: After some digging depper I think I found my mistake. ADB only works when the devices is booted into OS. Which is not possible anymore for me. Now I need to find a way around that.....
Click to expand...
Click to collapse
This might help:
http://www.oneplusbbs.com/thread-3203158-1-1.html
I can translate this for you if you need.
You need to flash a special build of Oreo beta to be a more to downgrade to Nougat according to the thread here below.
https://forums.oneplus.net/threads/guide-how-to-go-from-oreo-to-stock-nougat.661713/
But since you've deleted everything your best bet now is the Qualcomm factory restore recover method.
https://www.google.se/amp/s/forum.x...ick-unbrick-tutorial-oneplus-3t-t3515306/amp/
TaddyQuup said:
I wanted to go back from Oxygen OS 5 to 4. And started with making a full wipe, data and system. Now I know that was my mistake. But I did it anyways because it worked the same way before as i upgraded to Oxygen OS Beta xx (An Oreo one).
For refreshing 1I did go trough some tutorials but the process was how I remembered it. I did not change the computer or reseted it since the last time. So I was confidend I still got everthing istalled properly. Driver for my OnePlus 3T seemed to have been installed, too, because I drag&dropped the files I wanted to save on my computer from my OP3T priviously.
But then I starttyped everything in cmd this came up. https://i.imgur.com/Zmo1qeD.png?1
Here is the Installation Folder of ADB with the new Rom inside: https://i.imgur.com/9RD20Ac.png
I already tried this workaround: https://forum.xda-developers.com/showpost.php?p=69648733&postcount=47
As I researched on my own the idea came to my mind that adb/windows does not recognize my device. This thing is listed in my device manager: https://i.imgur.com/VO86zuw.png
Thank you in advance! Hope u guy can help me.
Edit: After some digging depper I think I found my mistake. ADB only works when the devices is booted into OS. Which is not possible anymore for me. Now I need to find a way around that.....
Click to expand...
Click to collapse
Some things you've missed:
1. Your first screenshot shows that ADB connects successfully to your phone because it shows the device ID. So drivers and ADB are ok.
2. ADB reads files from the directory it is invoked in. Your command shell is starting in c:/windows/system, so that's the directory ADB is looking in for OP.zip. you can either cd to the correct directory or specify the full path of the OP.zip file.
So, if you reboot your phone into recovery and select install from ADB then start ADB and verify its connected then run the sideload command pointing to the correct director it should flash the ROM successfully.
Sent from my OnePlus3T using XDA Labs
Greetings,
I recently got a Pixel 2 XL and the first thing I did was try to root with SuperSU and TWRP. I had some issues with it and someone suggested Magisk. It worked great and I was able to update from the 8.0 to 8.1 with root. I kept up with the latest Magisk installs until the past week or so.
My phones USB port appears to have failed partially. Luckily I can still charge, but there is no way to see the device storage from a PC. Support has defaulted, after much troubleshooting, to an RMA solution with a refurbished phone. Thankfully, this seems to be covered by warranty and isn't going to pose a cost issue. However, through the troubleshooting I was forced to do a factory reset. I looked up some information regarding factory reset with rooted devices. I cannot find the exact tutorial I followed or thread I gained the how-to information, I'm not sure which it was. I simply searched how to factory reset magisk 8.1 device. It was quick and most of the stuff I find now has the same information.
Open Magisk, uninstall. Open TWRP, uninstall. Device Settings, Factory Reset. Easy
This seemed to have worked. I didn't run into any locked hardware issues thankful because I don't have USB to really flash something to it.
Before I continued, prior to attempting the reset I fully backed up the device to my computer using ES File Explorers FTP transfer over the wifi. This was great, lots of photos were able to be saved with no hassle. I copied the entire root directory and have it backed up.
The problem with the reset is that while Magisk remained uninstalled, TWRP has a basic file installed that upgrades to the full app. I still have root, which would have been nice, except I still need to unroot and go back to factory settings before I can send this device in.
Before I make a mistake moving forward, I want to find the best way to unroot, (preferrably relock the boot also), and return to factory stock as it was the day I got it so I can return in it in the best state I can.
I am running rooted android 8.1.0 Pixel 2 XL with kernel 4.4.88 if the helps. When I reset to factory defaults TWRP remains installed and root persists. I cannot connect via USB and run android dev tools to flash anything directly. How can I restore this device? I should have all original kernels backed up. During the root process I remember them saying to copy the old ROMs first and I performed every step exactly. I do have access to move files to and from the device via WiFi. Is it this even possible?
PS, does anyone think the firmware and rooted install could be the problem with the USB? It seems entirely like failed hardware to me but the troubleshooting was extremely thorough and seems to indicate softare/firmware are likely to be the issue instead of the hardware issue that was determined. Could this still rooted device have corrupted the USB transfer? It seems I should do my best to rule this out as well, more so than just giving them a factory reset device. I'd rather keep my phone if it can be fixed easily, than obtain a possibly low quality heavily used refurbished model.
Regards
Did you try removing and reinstalling the drivers?
Sent from my MI 5 using Tapatalk
teddy0209 said:
Did you try removing and reinstalling the drivers?
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
I assume you mean for the PC. Yes, I have tried uninstalling and reinstalling both using Microsofts found drivers and directly sent packages from the support team. Updates and 2 different PCs. DevKit installed on the one I originally used to root and a new PC with fresh driver installs.
They wouldn't suggest drivers for the phone, if you know of a way to install new drivers for the phone, please let me know, I'd definitely give that a shot.
Regards
BlazzedTroll said:
I assume you mean for the PC. Yes, I have tried uninstalling and reinstalling both using Microsofts found drivers and directly sent packages from the support team. Updates and 2 different PCs. DevKit installed on the one I originally used to root and a new PC with fresh driver installs.
They wouldn't suggest drivers for the phone, if you know of a way to install new drivers for the phone, please let me know, I'd definitely give that a shot.
Regards
Click to expand...
Click to collapse
I should include all troubleshooting I mentioned for those that think they have a solution for the dead USB. My original request was for the OTA flash directions without USB, but I think a lot of people will want to suggest fixes for the phone as I suggested in the PS section.
Step 1: Check computer software.
Windows users, check to see if you have the latest version of Windows Media Player and have installed all recent system updates. Visit omitted for more information.
Mac users, make sure you install and are using Android File Transfer. Visit omitted for more information.
Step 2: Check for system updates.
On your device, go to "Settings" > Scroll down to "System" > Touch "About phone" (or tablet) > Touch "System updates".
If your device has a modified OS, troubleshooting may not resolve your device issue. Re-image your device back to Android factory settings using the instructions from the following link: omitted
Step 3: Restart your device in safe mode.
With the device on, hold the Power button to get the "Power off" prompt.
Touch and hold "Power off" until the "Reboot to safe mode" prompt appears.
Touch "OK" to reboot in safe mode.
Note: To exit safe mode later, simply restart the device normally.
Step 4: Unlock your device.
Before connecting the device to a computer, if your device is password protected, unlock your device. A locked device will not connect to the computer.
Step 5: Connect USB cable directly into computer.
If the USB cable is connected through a USB hub or extension, unplug the cable from the hub/extension and plug it directly to the computer.
A pop-up window should appear.
Mac users will have the Android File Transfer window appear.
Windows users may have a pop-up window appear. If not: On the computer, click the Windows Start button on the bottom left > click Computer > under Portable Devices, click on the device > click on the device's Internal Storage.
Step 6: Test if you can transfer files.
Try transferring a small file.
If file transfer works, success! No need to do the next steps.
If file transfer still isn't working (no pop-up windows to allow file transfer), proceed to Step 7.
Step 7: Change your USB computer connection settings.
Android 6+ Marshmallow only:
Plug in the device.
Slide down the notifications drawer from the top of the screen.
Touch the notification saying "USB for charging."
Touch the option for "File Transfers".
Test file transfer again (from Step 6). If the file transfer does not work, proceed to Step 8.
Older Android OS Versions:
Go to "Settings", under "Device," touch "Storage" > touch the "Menu" button (three vertical boxes at the top right) > touch "USB computer connection".
Only Media Transfer Protocol (MTP) should be checked. Uncheck MTP, check and then uncheck PTP, then re-check MTP.
Test file transfer again (from Step 6). If the file transfer does not work, proceed to Step 8.
Step 8: Windows Only: Install Google USB Driver.
Go to omitted and click the blue button on the right labeled "Download Google USB Driver."
After the download completes, right click the file ("latest_usb_driver_windows.zip") and select "Extract All."
Follow the USB Driver installation instructions available here: omitted
Test file transfer again. If file transfer still isn't working (no pop-up windows to allow file transfer), proceed to Step 9.
Step 9: Turn on "Developer options" and disable USB debugging.
Go to "Settings."
If using a phone, swipe down the screen with two fingers, then touch "Settings."
If using a tablet, swipe down the screen from the right side of the top of the screen, then touch "Settings."
Scroll down to "System" and touch "Developer options." If you don't see "Developer options," turn them on as follows:
Touch "About phone."
Scroll down to the "Build number."
Touch "Build number" 7 times to activate "Developer options."
Under "Debugging," verify that the box for "USB Debugging" is not checked. If it is checked, touch the checkmark to uncheck "USB Debugging."
Once USB Debugging has been deactivated, test file transfer again.
Step 10: Try different USB connections.
Try plugging the USB cable into a different USB port on the same computer.
Try connecting to the same computer but using a different/spare USB cable.
Try connecting your device to another computer.
Click to expand...
Click to collapse
My apologies on readability, I tried to include HTML formatting. I couldn't figure it out, the options support code highlighting but not the code itself.
Additionally, I tried different USB cables, safe mode, and the factory reset that I could perform.
@BlazzedTroll
Summary:
You've uninstalled Magisk, so you don't have root access when booted. TWRP still remains, so you have root access there.
If I read you correctly, what you need to do is to get rid of TWRP. Right?
Download the corresponding factory image, extract recovery.img and flash that by issuing the Install Image option in TWRP.
Just make sure you've done everything you need to before doing this, since you can't get back to a custom recovery if your USB really is busted. Other things to do could include flashing the system.img the same way to revert any possible /system modifications, etc.
Didgeridoohan said:
@BlazzedTroll
Summary:
You've uninstalled Magisk, so you don't have root access when booted. TWRP still remains, so you have root access there.
If I read you correctly, what you need to do is to get rid of TWRP. Right?
Download the corresponding factory image, extract recovery.img and flash that by issuing the Install Image option in TWRP.
Just make sure you've done everything you need to before doing this, since you can't get back to a custom recovery if your USB really is busted. Other things to do could include flashing the system.img the same way to revert any possible /system modifications, etc.
Click to expand...
Click to collapse
When you say corresponding factory image, does that mean I need the exact one that came on the device? Or just the latest factory image for the right device?
*EDIT* Never mind that, I found the backup folder in the Unified Toolkit which contains a compressed zip just like the ones on the site. I'll use that and transfer to my device over WiFi and use TWRP to flash it and come back with the results.
Thank you for your assistance
@Didgeridoohan
I have a backup locally saved that resembles those packages. I was unable to locate a recovery.img in either my saved file or the one on the site. My version that was backed up was 1.171019.011, which is 8.1. I know my phone came originally with 8.0 so I tried looking at one of the those for a recovery.img and still could not locate one.
In the zip there are several files
bootloader-taimen-tmz12a.img
flash-all.bat
flash-all.sh
flash-base.sh
another zip
radio-taimen-g8998-00164-17... .img
inside the second zip, many more .img files looked promising
abl.img
aes.img
android-info.txt
boot.img
cmnlib.img
cmnlib64.img
devcfg.img
dtbo.img
hyp.img
keymaster.img
laf.img
modem.img
pmic.img
rpm.img
system.img
system_other.img
tz.img
vbmeta.img
vendor.img
xbl.img
Same files in all 3 zips I checked.
TWRP only expects recovery.img for "BACKUP EXISTING RECOVERY"
TWRP also has "TWRP FLASH", which I did as one of my troubleshooting steps before and got the Google Pixel 2 XL (taimen) flash. These still keep the TWRP and root, which I believe is to be expected for that flash option.
DELETED
BlazzedTroll said:
I assume you mean for the PC. Yes, I have tried uninstalling and reinstalling both using Microsofts found drivers and directly sent packages from the support team. Updates and 2 different PCs. DevKit installed on the one I originally used to root and a new PC with fresh driver installs.
They wouldn't suggest drivers for the phone, if you know of a way to install new drivers for the phone, please let me know, I'd definitely give that a shot.
Regards
Click to expand...
Click to collapse
You're right, I mean for PC...
You can usually get twrp backups from same device with same rom and flash it on yours via twrp ( ask on your device forum)... You will need system.img, recovery.img, and boot.img... I'm not so sure if you can relock the device without working usb/fastboot...
Sent from my MI 5 using Tapatalk
@BlazzedTroll
My apologies... I'm still not used to these damned A/B devices. :laugh:
If I remember correctly, recovery is included in the boot image, so what you need to do is flash the stock boot.img file to slot A. Don't know if this is possible in TWRP.
teddy0209 said:
You're right, I mean for PC...
You can usually get twrp backups from same device with same rom and flash it on yours via twrp ( ask on your device forum)... You will need system.img, recovery.img, and boot.img... I'm not so sure if you can relock the device without working usb/fastboot...
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
I'll give this a shot, I have system.img and boot.img, as I said in reply to Didgeridoohan, I do not have a recovery.img in the files.
Sad news about relocking, but that should be OK.
Thanks for lending some help
Didgeridoohan said:
@BlazzedTroll
My apologies... I'm still not used to these damned A/B devices. :laugh:
If I remember correctly, recovery is included in the boot image, so what you need to do is flash the stock boot.img file to slot A. Don't know if this is possible in TWRP.
Click to expand...
Click to collapse
That's alright. I don't know much of anything about them. It's easy enough to follow tutorials and if I had my USB connection I could do as you say pretty quickly. The problem is I don't understand what TWRP even is. There doesn't seem to be an option to flash you own custom img. "TWRP FLASH" only lets you select from the latest versions and downloads the one you select and starts the flash. "BACKUP EXISTING RECOVERY" expects a recovery.img and doesn't let me select anything other than that. I could try renaming system.img to recovery.img, but until I find out what the difference between the images is, I'm not to keen on trying that one. Sounds like a good way to get hosed before I return it. At this time, I would think without having USB access the folks at Google would be happy to have root on the phone. Rather return it working, but rooted, than bricked.
So I was trying to follow some other suggestions and it seems like maybe the device is actually not rooted anymore.
There is no SU file located in system/bin or system/xbin.
When I download something like "Root Checker" it gets stuck verifying the root.
I tried to use apps like rashr and flashify to flash a stock recovery and neither app will load properly suggesting no root access.
This means when I ran the uninstalls, everything did uninstall and unroot but the TWRP install must not be very clean (I don't think it's being maintained anymore for most devices). So I need to try and find where this app is located and remove it manually before I run the recovery again. If I solve this I'll post back.
BlazzedTroll said:
So I was trying to follow some other suggestions and it seems like maybe the device is actually not rooted anymore.
There is no SU file located in system/bin or system/xbin.
When I download something like "Root Checker" it gets stuck verifying the root.
I tried to use apps like rashr and flashify to flash a stock recovery and neither app will load properly suggesting no root access.
This means when I ran the uninstalls, everything did uninstall and unroot but the TWRP install must not be very clean (I don't think it's being maintained anymore for most devices). So I need to try and find where this app is located and remove it manually before I run the recovery again. If I solve this I'll post back.
Click to expand...
Click to collapse
You don't have root access, since you uninstalled Magisk. TWRP has it's own root, so while booted to recovery you can still do root stuff...
The only way to restore the stock recovery is to flash the boot image to your device.
And TWRP is pretty much the only maintained custom recovery for most devices...
Just a small note: this demonstrates the issues with using toolkits... It's just to click away and you never really learn how things actually works. Can bite you in the bee-hind when things go south.
Didgeridoohan said:
You don't have root access, since you uninstalled Magisk. TWRP has it's own root, so while booted to recovery you can still do root stuff...
The only way to restore the stock recovery is to flash the boot image to your device.
And TWRP is pretty much the only maintained custom recovery for most devices...
Just a small note: this demonstrates the issues with using toolkits... It's just to click away and you never really learn how things actually works. Can bite you in the bee-hind when things go south.
Click to expand...
Click to collapse
At this point I've just ordered the RMA replacement and I'll send it in. Hopefully those at Google are able to verify that the hardware malfunction is entirely unrelated to the root and they still honor the warranty. If the USB hadn't failed, I would easily flash back to stock as you have suggested. It's a fairly trivial action.
I agree somewhat with the idea that toolkits can be problematic in this way. There was quite a bit involved in running through the toolkit, it wasn't that One-Click root/jailbreak type stuff. I issued all of the commands over ADB and was fairly knowledgeable about what actions I was performing. This issue lies in this toolkits maintenance. The latest update to TWRP removed a ton of features and I'm unable to find the other version. Magisk was fully uninstalled as expected. TWRP did not make it clear that the flashed recovery would in fact contain was is essentially an ad for their toolkit. The placeholder app, as they call it, is literally just an ad that pops up when your recover that says "Don't forget to install us!". You can't even remove that file from the recovery partition, you must reflash to remove it. So the problem isn't just that you don't learn how it works, it's that you aren't forced to go through the changes with a fine-toothed comb as you would creating your own recovery. Had I created my own recovery I would have left it stock so that in the event of a failure such as this you are returned to factory stock without any changes except the unlocked bootloader. I guess in the future I'll have to do this myself. I did take the easy way out and just run the defaults from the toolkit in most cases.
Thanks to you and the others who threw in some helpful suggestions.
For anyone stumbling across this in the future, the problem is a 'semi-rooted' recovery can't be flashed without USB transfer capabilities. The solution is to RMA the faulty hardware hopefully. They should be reflashing all phones they get after repair/refurbish anyway.
Best Regards
For future reference...
BlazzedTroll said:
Greetings,
I recently got a Pixel 2 XL and the first thing I did was try to root with SuperSU and TWRP. I had some issues with it and someone suggested Magisk. It worked great and I was able to update from the 8.0 to 8.1 with root. I kept up with the latest Magisk installs until the past week or so.
My phones USB port appears to have failed partially. Luckily I can still charge, but there is no way to see the device storage from a PC. Support has defaulted, after much troubleshooting, to an RMA solution with a refurbished phone. Thankfully, this seems to be covered by warranty and isn't going to pose a cost issue. However, through the troubleshooting I was forced to do a factory reset. I looked up some information regarding factory reset with rooted devices. I cannot find the exact tutorial I followed or thread I gained the how-to information, I'm not sure which it was. I simply searched how to factory reset magisk 8.1 device. It was quick and most of the stuff I find now has the same information.
Open Magisk, uninstall. Open TWRP, uninstall. Device Settings, Factory Reset. Easy
This seemed to have worked. I didn't run into any locked hardware issues thankful because I don't have USB to really flash something to it.
Before I continued, prior to attempting the reset I fully backed up the device to my computer using ES File Explorers FTP transfer over the wifi. This was great, lots of photos were able to be saved with no hassle. I copied the entire root directory and have it backed up.
The problem with the reset is that while Magisk remained uninstalled, TWRP has a basic file installed that upgrades to the full app. I still have root, which would have been nice, except I still need to unroot and go back to factory settings before I can send this device in.
Before I make a mistake moving forward, I want to find the best way to unroot, (preferrably relock the boot also), and return to factory stock as it was the day I got it so I can return in it in the best state I can.
I am running rooted android 8.1.0 Pixel 2 XL with kernel 4.4.88 if the helps. When I reset to factory defaults TWRP remains installed and root persists. I cannot connect via USB and run android dev tools to flash anything directly. How can I restore this device? I should have all original kernels backed up. During the root process I remember them saying to copy the old ROMs first and I performed every step exactly. I do have access to move files to and from the device via WiFi. Is it this even possible?
PS, does anyone think the firmware and rooted install could be the problem with the USB? It seems entirely like failed hardware to me but the troubleshooting was extremely thorough and seems to indicate softare/firmware are likely to be the issue instead of the hardware issue that was determined. Could this still rooted device have corrupted the USB transfer? It seems I should do my best to rule this out as well, more so than just giving them a factory reset device. I'd rather keep my phone if it can be fixed easily, than obtain a possibly low quality heavily used refurbished model.
Regards
Click to expand...
Click to collapse
Try downloading a stock Fastboot Image for your device then unzip it, collect boot.img, then flash just the stock boot.img from TWRP. Should solve the issue upon the following reboot with no more TWRP or root. If youre on magisk or systemless SuperSU. Not locking the bootloader though lol that's hopeless without usb function unless it's possible to lock bootloader using the terminal command with an WiFi ADB app from another device then follow with "adb reboot bootloader", "fastboot boot TWRP.img", then flash stock boot.img from there. I'm just spitballing the second one lol, but if it'll make it to the TWRP part successfully it should work in theory unless the WiFi ADB connection can't make it past reboot which I've never tried. Should probably get an unlock box like NCK Box Pro or whatever supports your device and you'll always know if the port is ****ed or not and flash back to full locked stock with the box if it isn't. It's what I do now. Handy little ****ers lol.
My pixel 4xl overheats and will go off in its own.
When I try to switch back on it won't work until I connect my charger. What could be the issue
It's possible that you might have some sort of malware/virus on the device. Overheating is one symptom of a mobile device virus.. In order to rule it out I would install a Google factory image for your device model from here:
https://developers.google.com/android/images
Flashing stock is always my first "go to.."
Make sure your device gets formatted.. Meaning don't edit the script if you are manually flashing the factory image. Allow it to: fastboot -w so that it gets wiped. I'm one of those weird people who believes in thoroughly wiping my devices , sometimes more than once just to make sure it was done . : Formatting your data and installing a factory image is always the first move when things happen that aren't supposed to happen. Then if problems continue after you've flashed stock and wiped your device you will know it is something else that is wrong.
Did you drop it recently or anything like that? My Pixel 4XL has never been hot or cut out as you describe. Hopefully it is some sort of virus and installing factory image and formatting solves your problems.
Not sure if you have fastboot and adb installed on your PC but if not here is what I believe is probably the best tutorial on installing adb and fastboot that's there is! Just download them from Google and extract to PC, open terminal in extracted platform-tools folder and type a few small sentences and you are ready to use fastboot and adb.
Detailed adb & fastboot tools installation thread is here: https://forum.xda-developers.com/t/guide-unlock-flash-root-for-the-pixel-2-xl-taimen.3702418/
It's in Pixel 2XL forums but it applies to all.
You can also use the web/browser installer to install factory image. Directions are on same page as factory images ..See first link here .. Hopefully this helps .. I hope you get it fixed. If you need help my name is the same here as it is on telegram.