I was using the AOSP Extended ROM (Nougat) with Magisk 14.x (I do not remember the exact version). I had also enabled some Magisk modules, like Viper4Android. I had also installed the Xposed Framework. I have TWRP as my recovery. I had also enabled USB debugging.
I was having root capabilities and all, but for instance AOSP Extended updates would not install. So, I decided yesterday to update Magisk and see if it solves my couple of issues. I chose the direct install method (the recommended) and rebooted. Then, I was greeted with a "FASTBOOT" screen and an image of an android being operated on by a white creature. It would reboot after a few seconds. I booted into TWRP holding the Volume-UP and Power buttons. Then, I tried to reflash the Magisk 15.3 file a couple of times, nothing changed. I searched online and found some posts that said to download some zip files and flash them. So, I tried to use adb from my laptop for that. But, my mobile is not seen *at all* by the laptop (I run arch linux). Then I tried from another Windows 10 laptop and also installed drivers I have found online. It doesn't show up there either. I connected, reconnected the mobile several times, tried different cables, usb ports, while in TWRP or in the "FASTBOOT" screen, nothing. I tried running 'fastboot -w', it was eternally waiting for a device. I also tried to mount in TWRP a usb-otg using a regular usb drive with an adaptor. I failed. I also wiped the caches. Failed again. I created a 'adb_usb.ini' file both on Windows and Linux containing:
0x8087
0x2080
0x2717
Or some other hex I found online. Nothing.
Right now, the only useful stuff on my mobile that I have access through TWRP is the magisk 15.3 zip.
Could someone help to defibrillate my phone? I thought of wiping everything from the mobile, storage, system, data, all. But as I cannot write to it from my laptop I thought I should better ask here first.
tterranigma said:
I was using the AOSP Extended ROM (Nougat) with Magisk 14.x (I do not remember the exact version). I had also enabled some Magisk modules, like Viper4Android. I had also installed the Xposed Framework. I have TWRP as my recovery. I had also enabled USB debugging.
I was having root capabilities and all, but for instance AOSP Extended updates would not install. So, I decided yesterday to update Magisk and see if it solves my couple of issues. I chose the direct install method (the recommended) and rebooted. Then, I was greeted with a "FASTBOOT" screen and an image of an android being operated on by a white creature. It would reboot after a few seconds. I booted into TWRP holding the Volume-UP and Power buttons. Then, I tried to reflash the Magisk 15.3 file a couple of times, nothing changed. I searched online and found some posts that said to download some zip files and flash them. So, I tried to use adb from my laptop for that. But, my mobile is not seen *at all* by the laptop (I run arch linux). Then I tried from another Windows 10 laptop and also installed drivers I have found online. It doesn't show up there either. I connected, reconnected the mobile several times, tried different cables, usb ports, while in TWRP or in the "FASTBOOT" screen, nothing. I tried running 'fastboot -w', it was eternally waiting for a device. I also tried to mount in TWRP a usb-otg using a regular usb drive with an adaptor. I failed. I also wiped the caches. Failed again. I created a 'adb_usb.ini' file both on Windows and Linux containing:
0x8087
0x2080
0x2717
Or some other hex I found online. Nothing.
Right now, the only useful stuff on my mobile that I have access through TWRP is the magisk 15.3 zip.
Could someone help to defibrillate my phone? I thought of wiping everything from the mobile, storage, system, data, all. But as I cannot write to it from my laptop I thought I should better ask here first.
Click to expand...
Click to collapse
Have you tried entering adb mode in twrp, and then trying?
This zip should work in order to remove magisk
http://tiny.cc/latestuninstaller
After downloading, try sideloading the zip by using command
adb sideload <zip path>
Here's the platform zip file
https://drive.google.com/file/d/13Sjej5zIJPm_yiJQOVR4rEocwbhDc9oh/view?usp=drivesdk
Now copy the uninstaller file inside the folder platform-tools
Right click on empty space to open powershell or cmd there and then run
adb sideload <magiskfilename.zip>
If you have powershell then
.\adb sideload <filename.zip>
If you are successful in sideloading the file, this should remove magisk.
Enter TWRP then Flash Lazy Flasher or Magisk Uninstaller.
tterranigma said:
I was using the AOSP Extended ROM (Nougat) with Magisk 14.x (I do not remember the exact version). I had also enabled some Magisk modules, like Viper4Android. I had also installed the Xposed Framework. I have TWRP as my recovery. I had also enabled USB debugging.
I was having root capabilities and all, but for instance AOSP Extended updates would not install. So, I decided yesterday to update Magisk and see if it solves my couple of issues. I chose the direct install method (the recommended) and rebooted. Then, I was greeted with a "FASTBOOT" screen and an image of an android being operated on by a white creature. It would reboot after a few seconds. I booted into TWRP holding the Volume-UP and Power buttons. Then, I tried to reflash the Magisk 15.3 file a couple of times, nothing changed. I searched online and found some posts that said to download some zip files and flash them. So, I tried to use adb from my laptop for that. But, my mobile is not seen *at all* by the laptop (I run arch linux). Then I tried from another Windows 10 laptop and also installed drivers I have found online. It doesn't show up there either. I connected, reconnected the mobile several times, tried different cables, usb ports, while in TWRP or in the "FASTBOOT" screen, nothing. I tried running 'fastboot -w', it was eternally waiting for a device. I also tried to mount in TWRP a usb-otg using a regular usb drive with an adaptor. I failed. I also wiped the caches. Failed again. I created a 'adb_usb.ini' file both on Windows and Linux containing:
0x8087
0x2080
0x2717
Or some other hex I found online. Nothing.
Right now, the only useful stuff on my mobile that I have access through TWRP is the magisk 15.3 zip.
Could someone help to defibrillate my phone? I thought of wiping everything from the mobile, storage, system, data, all. But as I cannot write to it from my laptop I thought I should better ask here first.
Click to expand...
Click to collapse
Or you can just use an sdcard. Load the rom files and uninstaller file onto an sdcard, and just insert it in phone. Then just boot to recovery and flash the required files.
Related
I have a Vibrant T959. I just flashed from the latest official Cyanogenmod (android 4.2), to the latest unofficial cyanogenmod (Android 4.4.4).
However the phone is crashing in the setup process. I need to get back into clockworkmod, however I have tried the hold vol+, vol-, and power technique tons of times, and it does not work. I had trouble with that method before but would always just use rom manager to reboot to recovery, but needless to say, can't do that this time.
I'm currently attempting to use the ADB to reboot to recovery (which I've never used). I installed the latest JRE, and downloaded ADB, however currently I am unable to get the drivers for my phone. I understand I'm supposed to launch SDK manager to download them, however SDK manager does nothing, just pops up an empty command window for a split second and quits. Did some searching to see if I can download the ADB drivers seperate, but just found many dead, or untrustworthy looking links.
Been reading for hours, but i'm stumped now. All I need to do is just get back to clockworkmod recovery. Is there any way to do so?
Well just an update, by sheer luck I found a roundabout way to get back into recovery. Apparently from all the web searching lots of people are having the same problem with the 3 button combo not working. Supposedly it might be hardware locked.
Here is what worked for me.
Hold volume down and power, and after a couple seconds plug in a usb cord (other end was attached to pc, but no software or anything running)
Keep holding those 2 buttons for about 30 seconds, you'll see the battery icon flash a number of times, along with a little round loading cursor type thing which will also be flashing.
After about 30 seconds, release the power button but keep holding the volume down button for awhile.
After about 10 seconds, clockworkmod recovery pops right up.
Tags (for anyone else who may have this problem: Samsung vibrant T959 how to enter recovery. recovery fix. recovery not working. can't get to clockworkmod.
Try this!
servohead said:
I have a Vibrant T959. I just flashed from the latest official Cyanogenmod (android 4.2), to the latest unofficial cyanogenmod (Android 4.4.4).
However the phone is crashing in the setup process. I need to get back into clockworkmod, however I have tried the hold vol+, vol-, and power technique tons of times, and it does not work. I had trouble with that method before but would always just use rom manager to reboot to recovery, but needless to say, can't do that this time.
I'm currently attempting to use the ADB to reboot to recovery (which I've never used). I installed the latest JRE, and downloaded ADB, however currently I am unable to get the drivers for my phone. I understand I'm supposed to launch SDK manager to download them, however SDK manager does nothing, just pops up an empty command window for a split second and quits. Did some searching to see if I can download the ADB drivers seperate, but just found many dead, or untrustworthy looking links.
Been reading for hours, but i'm stumped now. All I need to do is just get back to clockworkmod recovery. Is there any way to do so?
Click to expand...
Click to collapse
ADB will work. Use the process given below and let me know if it works
1. Install stand alone SDK tools from here, they should work. (h ttp://dl .google.com/android/ins taller_r23-windows.ex e)(Delete all spaces in between.)
2.Note the folder where you have installed SDK tools.
3. Move all the ADB driver files ( Probably 2 .exe and 2 .dll files, or just copy all the files from the ADB driver folder in which you installed the ADB drivers ) to the SDK tools folder.
4.Make sure all usb drivers for your phone have been installed. ( If not just google it, you will find them in the first or second link)
5. Connect your phone and make sure it is recognized by your PC.
6.Navigate to the SDK folder where you have also copied the ADB files. Hold down SHIFT and right click, Select Open Command Window Here.
7. Type adb devices .It should show you all the connected devices, mainly numbers. If not, the ADB drivers have not been installed correctly.
8. If Step 8 works, to reboot into recovery just type " adb reboot recovery " without quotes.
9. Your phone will reboot into recovery .
(If the steps above don't work, you will have to install the latest custom CWM recovery for your device and then boot into recovery from Step 5. And if you get errors while flashing the rom or the custom recovery then you may have to check if signature verification toggle is enabled and disabled,it SHOULD be disabled.And then repeat the flashing process.)
Hope this works . Happy Flashing!:good:
Glad to know it works for you, for people who can't gain access to recovery any other way, ^ This is the way
I have an answer to this. I had the problem, then I found the solution and now I'm sharing it:
Problem: I tried to put SuperSU on my M9 with CM-13 because I thought I needed root (you don't, under developer options there is the ability to turn on root essentially). So I flashed SuperSU from an apk and then it auto-updated itself then rebooted and got in a start up loop! Now I couldn't access the phone via adb, I'm not sure why. I think USB Debugging was off, but I'm not sure. AND I had not installed SuperSU from a zip so I didn't have that file laying around! So I went and got the latest SuperSU which I heard would work (it did) here: http://download.chainfire.eu/969/SuperSU/ THEN....how do I get it on my phone? I mean, who has a micro-SD reader laying around...not me today.
I DID have fastboot working but not adb. SO....I went into my phone and launched recovery mode then I chose this new thing called "adb sideload." That turns ON MTP so your phone comes up technically on your PC via USB but it doesn't show under my computer. But then I was able to go to my command prompt and type "adb-killserver" then "adb sideload NewSuperSU.zip" and it loaded!!! And I could then boot in!
Now I'm sure I shouldn't have SuperSU running but at least now I can put all the needed binarys (like CM and gApps to get started if I needed to from scratch) on !!!
So it works now.
I had TWRP installed and all was good. Then I tried an OTA update. Update failed and now I can't get into recovery or fastboot. When I try it stops at the 1+ logo with Fastboot Mode written under the logo. This happens if I try Volum Up + power button or adb reboot-bootloader. Device is listed with ADB but won't show up for fastboot.
How do I get back to stock recovery and get the update installed?
Thanks!
Is fastboot installed properly on your PC?
Drivers?
If not and you get it working, you can use fastboot to flash a new recovery. Otherwise read ahead.
Does your phone boot? Is it rooted?
If so, you can try to flash a new recovery via tools like FlashFire, Flashify, Rashr, etc.
If none of those work for you, you can try the un-bricking methods.
I've had my Oneplus 2 hardbrick 3 times on me so far. The solution was to put the phone into a Qualcomm QHUSB_BULK mode, installing unsigned drivers in Windows, and using Chinese software to push recovery files to your phone.
For my first two hard bricks (My phone wasn't responding to anything - it would just show up in the device manager when plugged into the PC). I was able to write the stock recovery and boot files onto my phone by using Method 1 from this OnePlus Forums thread: https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/.
I was then able to boot to recovery and dirty flash my OS without any data loss this way.
The last hard brick was much worse and required me to completely reinstall everything on my phone via one of the other methods (I used this link: http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449 and ended up with H2OS, which I then replaced with OOS 3.1.0) - if it comes to that I would recommend checking out the other methods in the OnePlus Forum link below to hopefully avoid going through H2OS - but if not, this one worked.
Also, for updates: You'll need to to reflash (dirty flash) your rom first (this is to unroot/undo any modifications you made to the system, otherwise the OTA will fail) and then flash the OTA. You should be able to use TWRP for this.
Thanks for the reply. Got fastboot working on a different computer.
Phone boots just fine. Not rooted. Just can't access recovery mode or install updates
I tried loading stock recovery (as per this thread) with no change. Thinking I'll have to treat it like it's bricked. Would rather not have to wipe phone though, but doesn't look like I have much choice .
For the past two days I had faced the issue of connecting the device in fastboot mode. Mobile is working fine, loaded with latest firmware OTA updates from OnePlus.
I would like to install TWRP on my mobile but the device is getting detected in the fastboot mode. Tried various steps, reinstalled adb & fastboot as well as OnePlus drivers nothing works. However my mobile is being detected in the adb mode. If I run the command adb devices, it displays my mobile serial number but in fastboot it just sits at the waiting for the device screen.
After a lot of googling, xda search & Oneplus forums search, nothing found. Then I tried reinstalling the adb interface drivers manually, where I have noticed that Win10 installed the latest drivers adb drivers updated in the month of Sep16. Here I have selected the older version driver which was released in the year 2014 and installed it successfully. I run the fastboot devices command again Voila... It worked. no restart, no rebooting the phone. Immediately worked.
Lesson learnt : - Always do not use latest drivers, sometimes try the older drivers if something is not working in your phone.
CrazyArjun said:
For the past two days I had faced the issue of connecting the device in fastboot mode. Mobile is working fine, loaded with latest firmware OTA updates from OnePlus.
I would like to install TWRP on my mobile but the device is getting detected in the fastboot mode. Tried various steps, reinstalled adb & fastboot as well as OnePlus drivers nothing works. However my mobile is being detected in the adb mode. If I run the command adb devices, it displays my mobile serial number but in fastboot it just sits at the waiting for the device screen.
After a lot of googling, xda search & Oneplus forums search, nothing found. Then I tried reinstalling the adb interface drivers manually, where I have noticed that Win10 installed the latest drivers adb drivers updated in the month of Sep16. Here I have selected the older version driver which was released in the year 2014 and installed it successfully. I run the fastboot devices command again Voila... It worked. no restart, no rebooting the phone. Immediately worked.
Lesson learnt : - Always do not use latest drivers, sometimes try the older drivers if something is not working in your phone.
Click to expand...
Click to collapse
can you share those drivers,,facing same issue actually
Hi all,
I'm not an expert with flashing ROMs/recovery and stuff, but I think I know the basics. So, if I was missing something, please forgive me in advance
I'm trying to install TWRP on my Oukitel K6000 Pro, but can't do it for some reason. The things I tried:
1. Rooting my phone w/ kingroot to install flashify. Kingroot failed to root my phone.
2. Via linux machine, using fastboot command. Fastboot failed installing the recovery (USB debugning was turn on. OEM unlocking was turn on, but I wasn't sure I even needed it). Error message I got: "FAILED (remote: download for partition 'recovery' is not allowed"
3. Using windows 7 and windows 10 machines to install it via SP-flash-tool (USB debuging and OEM unlocking was turned on). The SP-flash-tool did not recognized my phone.
4. Using SP-flash-tool with FWUL live-CD. It did not recognize my phone.
5. Using SP-flash-tool with linux machine. It did not recognize my phone.
As for #3 above, I was trying to install MTK drivers before performing the flash process. I think I got it right (for the win10 machine, I rebooted to a mode without signature check as required), but I'm not sure though.
If anyone can step in and help with that - I would much appreciate it.
Thanks in advance,
Tamir
you need the right drivers and the right adb tool.
Download adb tools of android sdk, google it.
Then download the oukitel drivers-> Driver_Auto_Installer_v5.1453.03, search for those., install them.
Try again, good luck.
Rooting and unlocking your phone will format your phone, beware of losing everything on it.
Btw, never use kingroot. Use latest SP Flashtool Version 1728,
Guide:
Download Magisk V16 or SuperSu to your micro sd on your phone.
--(Download your desired firmware, if you want to upgrade as well. (if you want, not needed, since you only want to root or install twrp)--
Download SPFlashTool compatible TWRP from a site that i can't mention here.
Turn off your phone.
Open Splflashtool, select the Android Scatter file that was downloaded with your twrp.
A little bit under that, select Download Only, and NOT firmware ugprade etc.
Now click Download, connect your turned off phone to your pc.
You should hear a windows sound, look at the tool and DO NOT Disconnect your phone. until a popup with Success and a green Symbol appears.
be patient and let it run. (shouldn't actually take longer than 3-5seconds)
After it is done, press simultaneously the Power and Volume+ Keys until a really small menu on the left side screen appears.
Now you can navigate with the Volume+ Key, from the top to the bottom, in an endless loop.
With the Volume- Key you can select on of the three options:
Recovery <-this is what we want, select it!
Fastboot (not really needed for us)
Normal (normal Reboot - Start of the phone)
You will now see the bootlogo, then the twrp menu will show up.
Now you can Flash Magisk or SuperSu for Root. Wipe Dalvik and cache, Reboot, Enjoy.
Hi People,
I hope I am putting this question in the proper location.
I have had several attempts ate flashing a new ROM to my device as it was the Chinese version & kinda useless to me not having Play store or several other APPs I want. I also wanted to try ROOT a phone for the first time.
I managed to get as far as getting ADB & fastboot working & TWRP installed on the device. The first ROM I had put in my file storage was corrupt so I tried the Lineage 17 version which "seemed"to install with a success message, but the phone would only boot into TWRP. so I tried the Havoc ROM from the thread in this site area. Same thing, would only boot into TWRP. Then I thought I would start over & install the factory ROM from: https://xiaomifirmwareupdater.com/miui/olivelite/stable/V12.0.2.0.QCPMIXM/ with ADB & fastboot. I got a success message from the MiFlash tool but the device is now saying the "MIUI verson cannot be installed on this device" in one screen from the Redmi-Recovery 3.0 menu that's now on it.
From here I can Reboot, wipe data or connect with MiAssistant. When I try MiAssistant (PC Suite) the phone does not connect to my PC but I can see the ADB device from device manager and ./adb fastboot devices shows a serial number -but connected as sideload if that makes a difference?
I hope I explained well enough to be understood. Is there anything I can do from here to get it working or is it fully stuffed?
Ur device's bootloader still unlocked?
T0B3R said:
Hi People,
I hope I am putting this question in the proper location.
I have had several attempts ate flashing a new ROM to my device as it was the Chinese version & kinda useless to me not having Play store or several other APPs I want. I also wanted to try ROOT a phone for the first time.
I managed to get as far as getting ADB & fastboot working & TWRP installed on the device. The first ROM I had put in my file storage was corrupt so I tried the Lineage 17 version which "seemed"to install with a success message, but the phone would only boot into TWRP. so I tried the Havoc ROM from the thread in this site area. Same thing, would only boot into TWRP. Then I thought I would start over & install the factory ROM from: https://xiaomifirmwareupdater.com/miui/olivelite/stable/V12.0.2.0.QCPMIXM/ with ADB & fastboot. I got a success message from the MiFlash tool but the device is now saying the "MIUI verson cannot be installed on this device" in one screen from the Redmi-Recovery 3.0 menu that's now on it.
From here I can Reboot, wipe data or connect with MiAssistant. When I try MiAssistant (PC Suite) the phone does not connect to my PC but I can see the ADB device from device manager and ./adb fastboot devices shows a serial number -but connected as sideload if that makes a difference?
I hope I explained well enough to be understood. Is there anything I can do from here to get it working or is it fully stuffed?
Click to expand...
Click to collapse
You should flash China factory rom, if you can.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com