Database Info

[Q] I installed whispercore without creating a restore image and want to leave.

I'm having trouble getting back to a regular non locked down firmware. I flashed whispercore without fully understanding that it was actually in fact changing my entire rom.
I didnt even think to try and install CWM first to create a recovery image I need help getting out of this mess. I've used the Whispercore installer to unlock fastboot because whispercore relocks your fastboot after it does its thing.
Seems as though the stock sdk tools hated me for a while there and wouldnt detect my device than I later realised it was just because the sdk downloads itself all fragmented it basically took fastboot and adb and separated the two even though fastboot requires adb to function properly. I wont even begin to speculate as to why that happened, as thats beyond the scope of my question.
I basically have gotten to the point where i have Clock work mod (CWM) installed on my droid and the fastboot oem unlocked but am currently stuck at trying to get Cyanogenmod 7 stable on here.
***UPDATE**
Ok. This situation has been resolved. If you are having trouble with leaving whisper core and you've flashed a bunch of stuff trying desperately trying to fix this issue. Recognize the nexus S is a very easy device to fix. Fastboot is your saviour and the WhisperCore installer will even be kind enough to install all the drivers required to OEM unlock fastboot and do it for you.
Anyways the solution was: Re run the whispercore installer. Let it do its automagic.
Than flash a new Clockwork Mod recovery image this thread provided some clean Clockwork Mod images for flashing with fastboot that link is also for rooting but provides a good example for how to flash a new recovery.
Than Just reboot into recovery and use it to mount your phone via the Clockwork Mod recovery console to your computer, upload your favorite flavor of rom and than unmount the device. Once unmounted go back to the main menu in Clockwork mod and "Flash zip from SD" look for your rom in my case it was update-cm-7.0.3-NS-signed.zip Latest stable at the time. let it do its job.
Basically my issue was a combination of several factors. A bad Clockwork mod and a semi corrupt installation of SDK tools and Whispercore.

Possibly a stock firmware might be required first I just know that trying to straight flash cm7 stable from cwm is not working out.

you can get adb and the 2 dll files and fastboot in the same folder and cd to that directory. fastboot oem unlock should unlock your bootloader. then you should be able to flash a recovery if you want. might also want to check out the 1 click stock thread to see if that works.

I will probably have trouble finding this thread but I will look and if i come up with anything I will certainly post my findings.

This should work. But we shall see I will update the original post if I find a full solution.
Just flash a stock full rom (for i9023 you can use the one in my signature, don't forget get to use the wipe options in cwm recovery before) and the root should be gone. Afterwards, boot into bootloader and use fastboot command "fastboot oem lock" to lock the bootloader again. Than you can do a factory reset (and delete usb storage) to fully restore stock "experience".
__________________
Nexus S running Official 2.3.4 ROM (for i9023) with XTEUV92 Trinity kernel
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1214705&highlight=one+click+stock

I'm getting an error in the zip files no matter what one I use and its "Status 7" whatever that means.

chamunks said:
***UPDATE**
Ok. This situation has been resolved. If you are having trouble with leaving whisper core and you've flashed a bunch of stuff trying desperately trying to fix this issue. Recognize the nexus S is a very easy device to fix. Fastboot is your saviour and the WhisperCore installer will even be kind enough to install all the drivers required to OEM unlock fastboot and do it for you.
Anyways the solution was: Re run the whispercore installer. Let it do its automagic.
Than flash a new Clockwork Mod recovery image this thread provided some clean Clockwork Mod images for flashing with fastboot that link is also for rooting but provides a good example for how to flash a new recovery.
Than Just reboot into recovery and use it to mount your phone via the Clockwork Mod recovery console to your computer, upload your favorite flavor of rom and than unmount the device. Once unmounted go back to the main menu in Clockwork mod and "Flash zip from SD" look for your rom in my case it was update-cm-7.0.3-NS-signed.zip Latest stable at the time. let it do its job.
Basically my issue was a combination of several factors. A bad Clockwork mod and a semi corrupt installation of SDK tools and Whispercore.
Click to expand...
Click to collapse
I am trying to follow what you did and i am completely lost... I have a nexus s g that i am trying to get whispercore off it!
The "Automagic" you talk about. Isnt that just whispercore putting it in fast boot??? If so then then how do you use the recover image?

[Q] Did I Just Screw Up My Phone?

Phone: HTC ONE XL
Carrier: Rogers LTE
Hey guys,
I have a problem that hopefully someone can help me with. Any help is much appreciated. I got my phone a year ago and I rooted it and unlocked it immediately. I removed the stock ROM and put Clean Rom 4.5 on it. Today, I realized my phone could be manually updated to jelly bean, so i wanted to install CM 10.1.
During installation, I just put the boot.img of the Rom in my folder that contained adb, fastboot, etc and I was at the step of loading recovery to install the rom, my phone could not get into the recovery and just kept restarting over and over again. I can still get into the bootloader. I read online to try and type "fastboot erase cache", but that isnt working because my computer can no longer recognize the phone. When I go into bootloader and into fastboot, my computer makes the sound like the USB is recognized but when I type the command "adb devices", no device is showing up.
I'm guessing that my first step to hopefully solving this issue is to find a way to have my device show up when I type "adb devices" but my attempts so far have been futile.
Key Points:
- Can't get past HTC boot screen (keeps looping)
- can still access bootloader
- no device seen when command "adb devices" has been typed.
Any help is greatly appreciated.
EDIT: I should add that when this occured (the looping), I tried to flash "recovery clockwork touch 5.8.2.7" and I was accidentally following a guide meant for the European HTC One X. The recovery image that I should have used (and did use to flash Clean Rom) is "TWRP 2.2.0 evita".

Cheruksr said:
Phone: HTC ONE XL
Carrier: Rogers LTE
Hey guys,
I have a problem that hopefully someone can help me with. Any help is much appreciated. I got my phone a year ago and I rooted it and unlocked it immediately. I removed the stock ROM and put Clean Rom 4.5 on it. Today, I realized my phone could be manually updated to jelly bean, so i wanted to install CM 10.1.
During installation, I just put the boot.img of the Rom in my folder that contained adb, fastboot, etc and I was at the step of loading recovery to install the rom, my phone could not get into the recovery and just kept restarting over and over again. I can still get into the bootloader. I read online to try and type "fastboot erase cache", but that isnt working because my computer can no longer recognize the phone. When I go into bootloader and into fastboot, my computer makes the sound like the USB is recognized but when I type the command "adb devices", no device is showing up.
I'm guessing that my first step to hopefully solving this issue is to find a way to have my device show up when I type "adb devices" but my attempts so far have been futile.
Key Points:
- Can't get past HTC boot screen (keeps looping)
- can still access bootloader
- no device seen when command "adb devices" has been typed.
Any help is greatly appreciated.
EDIT: I should add that when this occured (the looping), I tried to flash "recovery clockwork touch 5.8.2.7" and I was accidentally following a guide meant for the European HTC One X. The recovery image that I should have used (and did use to flash Clean Rom) is "TWRP 2.2.0 evita".
Click to expand...
Click to collapse
ADB is a program that gives you control of your phone "terminal" or "command line" remotely. It requires you to be booted into your ROM with USB debugging turned on so ofcourse it won't show any devices while in bootloader.
There are at least 20 threads that ask this same question. How do I know? I've answered at least that amount just myself. Please use the search function in the future prior to asking. I'm so tired of wasting time answering the same questions over and over.
Download TWRP 2.3.3.1 <- latest version that works properly without any issues with any ROMs
Check MD5 <- If you don't have an md5 checker google and download one. This will verify the download is good.
Put your phone in bootloader/fastboot
fastboot flash recovery recoveryfilename.img
fastboot erase cache
fastboot reboot-bootloader
Select recovery from bootloader menu
Flash your rom from recovery.

exad said:
ADB is a program that gives you control of your phone "terminal" or "command line" remotely. It requires you to be booted into your ROM with USB debugging turned on so ofcourse it won't show any devices while in bootloader.
There are at least 20 threads that ask this same question. How do I know? I've answered at least that amount just myself. Please use the search function in the future prior to asking. I'm so tired of wasting time answering the same questions over and over.
Download TWRP 2.3.3.1 <- latest version that works properly without any issues with any ROMs
Check MD5 <- If you don't have an md5 checker google and download one. This will verify the download is good.
Put your phone in bootloader/fastboot
fastboot flash recovery recoveryfilename.img
fastboot erase cache
fastboot reboot-bootloader
Select recovery from bootloader menu
Flash your rom from recovery.
Click to expand...
Click to collapse
Hey, thanks for the reply. Yeah, I read up on ADB after i posted the thread. I learnt that you can't use ADB commands in the bootloader. I've been trying to flash the recovery but i keep getting "waiting for device". (regardless of what command i try). I don't think its the USB drivers because I downloaded the latest HTC drivers (in fact there is a thread about the latest USB drivers for HTC, which is where I downloaded from) and there isn't any exclamation points in device manager. Not really sure what the issue is, any additional help would be appreciated.
Thanks.
EDIT:
Originally Posted by DvineLord
try using this application if you think your device drivers are dirty but installed correctly for usb devices
USBDeview just uninstall whatever devices you want reinitialized especially since they can change even with rom changes so it is good to clear some old ones out by sorting them based on Last Plug/Unplug Date.
Found that in another thread, going to try that. Hopefully that will work.

Cheruksr said:
Hey, thanks for the reply. Yeah, I read up on ADB after i posted the thread. I learnt that you can't use ADB commands in the bootloader. I've been trying to flash the recovery but i keep getting "waiting for device". (regardless of what command i try). I don't think its the USB drivers because I downloaded the latest HTC drivers (in fact there is a thread about the latest USB drivers for HTC, which is where I downloaded from) and there isn't any exclamation points in device manager. Not really sure what the issue is, any additional help would be appreciated.
Thanks.
EDIT:
Originally Posted by DvineLord
try using this application if you think your device drivers are dirty but installed correctly for usb devices
USBDeview just uninstall whatever devices you want reinitialized especially since they can change even with rom changes so it is good to clear some old ones out by sorting them based on Last Plug/Unplug Date.
Found that in another thread, going to try that. Hopefully that will work.
Click to expand...
Click to collapse
I just install the latest HTC sync. It installs the latest driver.
Also, try to avoid using a USB hub if you are.
Make sure HTC Sync isn't running when you are using fastboot/adb
Worst case scenario, you could always create a VM or something to get it going.

exad said:
I just install the latest HTC sync. It installs the latest driver.
Also, try to avoid using a USB hub if you are.
Make sure HTC Sync isn't running when you are using fastboot/adb
Worst case scenario, you could always create a VM or something to get it going.
Click to expand...
Click to collapse
I can now run the fastboot commands, but in the twrp recovery I can't access my SD card. I'm currently following a guide to see if I can fix it, but yeah thats where I am at. Also, a window popped up in my windows 8 saying "You need to format the disk...". Should I do that or what, Im not exactly sure.
Thanks

Yes format it.
Sent from my HTC One X using xda app-developers app

Am I capable of running CM10.1 Nightlies?
exad said:
Yes format it.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Alright, following a video tutorial (http://forums.team-nocturnal.com/showthread.php/1050) and factory reset the phone. My SD card is wiped clean but I can mount it through the TWRP recovery. Since I don't have a ROM now, I'm debating what I should do: a) Go back to Clean ROM 4.5, b) Install CM 10.1 Nightlies or c) Install Clean ROM 6.5.
***TAMPERED***
***UNLOCKED***
S-ON
HBOOT 1.11.0000
Is there anything I should know before attempting to flash CM 10.1/Clean ROM 6.5 or should I return to Clean ROM 4.5.
Thanks for the helps. Really appreciate it.

Either should work fine. Cleanrom will have somewhat bettery battery life.
Sent from my HTC One X using xda app-developers app

exad said:
Either should work fine. Cleanrom will have somewhat bettery battery life.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
another good tip is that when you are in fastboot mode and write "adb devices" not will work because adb will just work when your phone is turned on inside the android, and fastboot not will work if you arent in mode fastboot

Can I still install any recovery(CWM or TWRP) after I have forgotten my password?

My question is: Is there any way that i can install any custom recovery now, when I am locked out of my phone, so I can try Method 7 from this post . I have enabled USB debugging, but for some reason, my device is unauthorized from executing adb commands.
I have Xiaomi Redmi Note 3, and have forgotten its password. I have tried Method 2, 5 and 6 from this post, but to no avail.
I tried method 2 and 5 which requires ADB to be installed, but I was not able to access my phone. I have USB debugging enabled and my phone is not rooted. When I tried to run the following code:
Code:
adb devices
adb shell
it showed that my phone is unauthorized and error: device unauthorized This adb server's $ADB_VENDOR_KEYS is not set
Here's the screenshot:
When trying method 6, I had to change the path of ADB driver because the file I downloaded from the post, had its own ADB driver which clashed with my already installed ADB driver, but even after that, it again showed the above error. Here' the screenshot:
Finally I want to try method 7 from the above post, which requires custom recovery to be installed on the phone, is there any way now?
Though it seems now that the I have only one option left and that is to factory reset my phone, but if , there is any other way by which I can bypass my lock screen, please please please inform me.

Of course you can. Just boot your phone into fastboot and do "fastboot flash recovery <recovery image name>.IMG" and you'll flash it. And you can't access the adb because your screen is locked... This is how companies prevent phone hacking
So flash custom recovery, backup the /data , factory reset and after resetting restore the /data backup. And you're good to go. I suggest you using TWRP, because I use it and it never left me hanging Keep me updated.
Sent from Lenovo a6000 1GB version.

Install TWRP or CWM with fastboot and then flash the Unlock me! zip that I've created and you won't lose your data.
Sent by my iPad using Tapatalk

joe2k01 said:
Install TWRP or CWM with fastboot and then flash the Unlock me! zip that I've created and you won't lose your data.
Sent by my iPad using Tapatalk
Click to expand...
Click to collapse
Didn't know that such package existed... I'd still do it my way if your phone was laggy/corrupted,... Else do the package flash. Keep me updated!
Sent from Lenovo a6000 1GB version.

Thanks! a lot, could you please guide me a little bit, how should I proceed?
MGlolenstine said:
Of course you can. Just boot your phone into fastboot and do "fastboot flash recovery <recovery image name>.IMG" and you'll flash it. And you can't access the adb because your screen is locked... This is how companies prevent phone hacking
So flash custom recovery, backup the /data , factory reset and after resetting restore the /data backup. And you're good to go. I suggest you using TWRP, because I use it and it never left me hanging Keep me updated.
Sent from Lenovo a6000 1GB version.
Click to expand...
Click to collapse
Thanks! a lot for reply, As I am still a newbie and trying to learn few things. Could you please guide me how should I proceed?
Like What files I need to download and from where? Also how should I use these files to install recovery?

dost25 said:
Thanks! a lot for reply, As I am still a newbie and trying to learn few things. Could you please guide me how should I proceed?
Like What files I need to download and from where? Also how should I use these files to install recovery?
Click to expand...
Click to collapse
OK... So first boot into fastboot. When you've done that, connect It to your pc with usb, download fastboot package from somewhere on xda(you'll find it).
Open command prompt "CD" to the directory where your fastboot is located in, put recovery image in the folder where fastboot.exe is and type "fastboot flash recovery <recovery file name>.IMG". I'm gonna update this answer in 2 days, when I get to my pc, so try to do it by these instructions, if something isn't working, comment and we'll resolve the problem. If something isn't clear, just ask. Keep me updated.
Sent from Lenovo a6000 1GB version.

Ok i will try
MGlolenstine said:
OK... So first boot into fastboot. When you've done that, connect It to your pc with usb, download fastboot package from somewhere on xda(you'll find it).
Open command prompt "CD" to the directory where your fastboot is located in, put recovery image in the folder where fastboot.exe is and type "fastboot flash recovery <recovery file name>.IMG". I'm gonna update this answer in 2 days, when I get to my pc, so try to do it by these instructions, if something isn't working, comment and we'll resolve the problem. If something isn't clear, just ask. Keep me updated.
Sent from Lenovo a6000 1GB version.
Click to expand...
Click to collapse
Can unlocking my bootloader somehow brick my phone?

Everything can brick your phone. Updating my lenovo phone with official update hardbricked mine... But yeah, it can.

Help! Deleted EVERYTHING on ZTE N817

Okay, so when trying to flash CM ROM, I stupidly ended up wiping EVERYTHING in the "wipe" option. Trying to recover it, I tried sideloading the file through ADB, but TWRP would disconnect off the PC and say failed (TWRP version 3.0.2-0). Pushing a ROM zip won't work, as the phone only connects to the PC as ADB Sideload mode ('error: closed' is what it would say), and nothing else would work except sideload. I no longer have a working OTG cable, as my last one broke on me a week ago. The PC will not connect to phone on the 'Mount USB' option from TWRP. Plz help! I'm running out of ideas. I did make a backup (using Online Nandroid Backup, no it wasn't a zip) on the SD card, but TWRP will not read the SD card on my device. Note that the only thing I have is TWRP; no bootloader, no Fastboot, no nothing. Just TWRP.

TRiP_E said:
Okay, so when trying to flash CM ROM, I stupidly ended up wiping EVERYTHING in the "wipe" option. Trying to recover it, I tried sideloading the file through ADB, but TWRP would disconnect off the PC and say failed (TWRP version 3.0.2-0). Pushing a ROM zip won't work, as the phone only connects to the PC as ADB Sideload mode ('error: closed' is what it would say), and nothing else would work except sideload. I no longer have a working OTG cable, as my last one broke on me a week ago. The PC will not connect to phone on the 'Mount USB' option from TWRP. Plz help! I'm running out of ideas. I did make a backup (using Online Nandroid Backup, no it wasn't a zip) on the SD card, but TWRP will not read the SD card on my device. Note that the only thing I have is TWRP; no bootloader, no Fastboot, no nothing. Just TWRP.
Click to expand...
Click to collapse
You can connect to ADB but the adb push command isn't working when you try to move the ROM.zip to the device?
Get a new OTG cable.
The nandroid backup you made should have been done in TWRP and stored on extsdcard instead of the online backup, online backup is crap because it only works in certain conditions, it's useless when the device can't connect to a network.
Sent from my SM-S903VL using Tapatalk

Yes. ADB commands other than sideload will say 'error:closed', and ADB Sideload will just end up making the phone disconnect. At this point, I may HAVE to end up getting a new OTG Cable.
Yes, I was trying to do the backup on TWRP, but as it couldn't read the SD Card, I used Online Nandroid Backup. Then I realized that everything I was doing was completely stupid while I wiped EVERYTHING....

TRiP_E said:
Yes. ADB commands other than sideload will say 'error:closed', and ADB Sideload will just end up making the phone disconnect. At this point, I may HAVE to end up getting a new OTG Cable.
Yes, I was trying to do the backup on TWRP, but as it couldn't read the SD Card, I used Online Nandroid Backup. Then I realized that everything I was doing was completely stupid while I wiped EVERYTHING....
Click to expand...
Click to collapse
Yeah, new cable seems to be your only option.
Sent from my SM-S903VL using Tapatalk

Alright then, I'm going to go see where I can buy one. Thanks for the confrirmation.

I cant even mount the ****ing usb flashdrive through OTG!!!!! On other devices, it works fine, but on this device it doesn't even show the frickin USB-OTG option.

TRiP_E said:
I cant even mount the ****ing usb flashdrive through OTG!!!!! On other devices, it works fine, but on this device it doesn't even show the frickin USB-OTG option.
Click to expand...
Click to collapse
Try rooting the device and then use the Stick Mount app, if your device has the hardware to support OTG, that should enable it, but if your device does not have the hardware to support OTG then it doesn't matter what you do softwarewise or what you modify, it has to have the hardware or it can't do it at all.
Things like this are why I'd never buy or own a ZTE device of any kind. Relatively soeakibg, they are all junk.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Only thing is, I dont HAVE any system to boot in order to check that. I guess I'm out of luck, no wonder why others said this phone was crap.

TRiP_E said:
Only thing is, I dont HAVE any system to boot in order to check that. I guess I'm out of luck, no wonder why others said this phone was crap.
Click to expand...
Click to collapse
If you can use adb shell or fastboot, you can try getting a copy of system.img from someone with your exact device and dd or fastboot flash the img.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Any ADB commands other than Sideload will just respond as error:closed, as the computer only reads the system when in ADB Sideload mode. However, when trying to sideload a ROM, the phone will disconnect and say failed, while the computer stays on xfer: 0.00. Maybe I could get some instructions to fix that? Maybe a bad TWRP version? If so, I'm ****ed...

After reading other pols forums, it seems that I didn't have to delete the internal storage........

TRiP_E said:
Any ADB commands other than Sideload will just respond as error:closed, as the computer only reads the system when in ADB Sideload mode. However, when trying to sideload a ROM, the phone will disconnect and say failed, while the computer stays on xfer: 0.00. Maybe I could get some instructions to fix that? Maybe a bad TWRP version? If so, I'm ****ed...
Click to expand...
Click to collapse
Sideloading a ROM won't work.
Try
adb reboot bootloader
If you can boot to bootloader or fastboot you can try finding the firmware for another device that has all of the exact same hardware components that your device has then try fastboot flashing it or extract the separate .imgs from the firmware and use the fastboot commands to flash the boot.img and system.img.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

can't get into fastboot, ADB command says error: closed, while doing the command in terminal in the TWRP menu keeps me on ZTE screen (only reboot recovery works, not as ADB command but in terminal).

TRiP_E said:
Any ADB commands other than Sideload will just respond as error:closed, as the computer only reads the system when in ADB Sideload mode. However, when trying to sideload a ROM, the phone will disconnect and say failed, while the computer stays on xfer: 0.00. Maybe I could get some instructions to fix that? Maybe a bad TWRP version? If so, I'm ****ed...
Click to expand...
Click to collapse
I have most, if not all the. Img files for this I managed to successfully root, TWRP, and deKingoCrap my n817
I also have a nandroid of this phone, though mine is the qlink one

help.
equitube said:
I have most, if not all the. Img files for this I managed to successfully root, TWRP, and deKingoCrap my n817
I also have a nandroid of this phone, though mine is the qlink one
Click to expand...
Click to collapse
dude i need the twrp backup of the qlink variant. i formatted the system and got bootloop at zte screen

filldapipe said:
dude i need the twrp backup of the qlink variant. i formatted the system and got bootloop at zte screen
Click to expand...
Click to collapse
Did you ever get the TWRP for this? I have it in my dropbox pm me.
The issue were running into is that the TWRP on this model can't see the ext sd. The backup is 1.5 or 2gb which is usually too large to fit on the internal SD
Slacker is working hard at modding the Fstab file to make TWRP see that storage. Any ideas please let him or I know([email protected] or here )
I'm also working on an EquiMods custom ROM for this. Bare bones battery saver, switchable to performance when needed.
Anyone know if and how these can be overclocked?

I have a deodex rom done for this phone and also should have the working twrp recovery by morning. The cm11.0 ive been working on is almost done. I hope Everytime i flash it to phone i get white screen. Also im going to install xposed on it in the morning. I think i found the fix for that to work

Any news on this? I can't find anything that works with this phone. I have adb sideload working, but that's pretty useless from what I understand.

edsfunsite said:
Any news on this? I can't find anything that works with this phone. I have adb sideload working, but that's pretty useless from what I understand.
Click to expand...
Click to collapse
They obviously got something to work since there are members in this thread that have TWRP installed on their devices, that means they can at least root the device but I doubt there are any ROMs for this device.
Sent from my LGL84VL using Tapatalk

I've rooted my N817 but never made an Nandroid backup. I still have TWRP up and working but I've tried to flash the 2 roms I know of....they both "install" but when I try to boot It stays in the ZTE screen...Help!

Trying to flash TWRP Recovery image & Root G8142 on Ubuntu - Need Help

Hi All,
I had a previously rooted 8142, but it crapped out on me last week, so I've just bought a new one. I'm trying to root it now. I've unlocked bootloader, and installed the TWRP app, but I can't figure out how to root it.
I was running windows and used Xperifix when I did my last one, but now I'm using Ubuntu, and there's not really any software (like Xperifix or One Click Root) available.
I've been using FlashTool, and can get it to show root privelages, but I have no idea how to flash a recovery image using it.
I tried using Platform Tools via the terminal and I think I was able to flash a TWRP recovery image to the device, but the TWRP app isn't seeing it, nor can I boot into recovery mode.
I tried to download a recovery image via the TWRP app, but even when it's downloaded, the TWRP app isn't finding any recovery images despite pointing the app to my downloads folder.
TWRP is also showing "No Root Permissions"
I can't flash SuperSu or any other ROM's without being able to boot into TWRP recovery menu.
Maybe I'll have to install windows to use the rooting software. Does anyone have any ideas? Been messing around with it 6 hours now and still can't boot into recovery.
Thanks for any ideas.

first I dont know if youre using fastboot so do "sudo apt install android-tools-adb android-tools-fastboot" then open a terminal were twrp is located and type fastboot flash recovery "name of twrp".img and then you are ready to go. I dont know if you can use this phone without a specific driver so that can be a problem. If you cant do it that way i recommend you using a virtual machine with windows and run fastboot (platform tools trough there) so you dont have to remove ubuntu.
Also remember how to access fastboot

ricardo99831390 said:
first I dont know if youre using fastboot so do "sudo apt install android-tools-adb android-tools-fastboot" then open a terminal were twrp is located and type fastboot flash recovery "name of twrp".img and then you are ready to go. I dont know if you can use this phone without a specific driver so that can be a problem. If you cant do it that way i recommend you using a virtual machine with windows and run fastboot (platform tools trough there) so you dont have to remove ubuntu.
Also remember how to access fastboot
Click to expand...
Click to collapse
Thanks! I'll try both of those methods over the weekend and report back.

tombow said:
Thanks! I'll try both of those methods over the weekend and report back.
Click to expand...
Click to collapse
well i forgot to mention, the fastboot flash recovery command depends on your android version so take that in count.