Hello all- I am trying to root my unlocked Redmi Note 4 but find the entire adb, command thing extremely confusing and frustrating.
Also my computer has this thing called Windows Power Shell (or something like that) so dont even have the option to open a command window.
Is there a way to root this phone that does not involve this whole adb fastboot command scenario ?
Thanks for any help, LL
lamplighter13 said:
...my computer has this thing called Windows Power Shell (or something like that) so dont even have the option to open a command window.
Click to expand...
Click to collapse
Right click on the Windows start menu icon at the extreme left, select "Run", type "cmd", and press ENTER. There you have your command window.
lamplighter13 said:
Is there a way to root this phone that does not involve this whole adb fastboot command scenario ?
Click to expand...
Click to collapse
Only if you can install Supersu or Magisk from stock Xiaomi recovery - which I very much doubt. You need a custom recovery (TWRP or whatever), and you most likely need adb to install them.
lamplighter13 said:
Hello all- I am trying to root my unlocked Redmi Note 4 but find the entire adb, command thing extremely confusing and frustrating.
Also my computer has this thing called Windows Power Shell (or something like that) so dont even have the option to open a command window.
Is there a way to root this phone that does not involve this whole adb fastboot command scenario ?
Thanks for any help, LL
Click to expand...
Click to collapse
Just follow steps carefully and you are done in seconds. Take all precautions (that your device is correctly detected through adb and fastboot, drivers installed etc) and you can't miss it. Procedure is like this since you unlocked bootloader: flash latest twrp recovery.img, boot into recovery, flash su or magisk for root, flash lazyflasher if you are staying on stock kernel and you are done. If you flash a custom rom or kernel, no need to flash lazyflasher.
Also, powershell in windows is the same as command prompt, just a more advanced version [emoji14] All commands are the same
Very very old thing: if you're not familiar how to root, don't do it!
lamplighter13 said:
Hello all- I am trying to root my unlocked Redmi Note 4 but find the entire adb, command thing extremely confusing and frustrating.
Also my computer has this thing called Windows Power Shell (or something like that) so dont even have the option to open a command window.
Is there a way to root this phone that does not involve this whole adb fastboot command scenario ?
Thanks for any help, LL
Click to expand...
Click to collapse
I know why you are frustrated, this is because that evertime you type a command in powershell it gives an error,
To actually use the commands you need to write -
"./fastboot flash recovery recovery.img"
Note that addition of two characters in the beginning? That's what you needa do.
Just install twrp and after that, life's easy:silly:
krisztian b said:
Very very old thing: if you're not familiar how to root, don't do it!
Click to expand...
Click to collapse
Read the question before you reply, don't be that guy that everyone else thinks is an idiot because your reply shows you're dangerously close.
Cheers to everyone for your help, I'm gonna try again when I get home.
Related
Ok, Im retarted. I got my HTC One and had no clue what I was doing trying to unlock it. Well, I eventually got it unlocked but somehow installed the ADB and Bootloader from my Nexus4 onto it. I cant figure out how I did that or how to get the correct ADB and Bootloader onto the device now.
Can anyone assist me?
HyperM3 said:
Ok, Im retarted. I got my HTC One and had no clue what I was doing trying to unlock it. Well, I eventually got it unlocked but somehow installed the ADB and Bootloader from my Nexus4 onto it. I cant figure out how I did that or how to get the correct ADB and Bootloader onto the device now.
Can anyone assist me?
Click to expand...
Click to collapse
well you dont install ADB to your phone, thats on your computer. You may have installed the wrong boot.img but probably not the bootloader. please give more details. list the files you installed to the One.
Ok, so I went out and bought a new laptop since the one I was using was 8 years old running XP and took 5 minutes to open any program.
Anyway, I downloaded the all-in-one-toolkit on the laptop and did a factory reset on the phone. I installed the correct drivers on the computer(hopefully). The phone is still saying its unlocked when I put it in fastboot mode. I have it connected right now and Im trying to install the TWRP but the CMD prompt is just sitting there saying <waiting for device>.
Im the least techie technophile there is apparently. I usually have a friend do all this set up crap on every phone and then I have no problems installing kernels and ROM's after that. Its this beginning crap I always get lost on.
Im seriously so frustrated that Im debating if I even want to keep the phone anymore.
wait because you can't get it install a recovery your going to rage quit ..... dang
CheesyNutz said:
wait because you can't get it install a recovery your going to rage quit ..... dang
Click to expand...
Click to collapse
If you have had this phone since Friday and have been working on doing this the whole time, wouldnt you be feeling the same way?? Maybe since you have already done all this you might be able to lend a helping hand.
you're seeing waiting for device because you don't have the drivers installed correctly.
are you on windows 8?
get the drivers from http://forum.xda-developers.com/showthread.php?t=2135381
then look at the link to how to use adb and fastboot in my signature
gunnyman said:
you're seeing waiting for device because you don't have the drivers installed correctly.
are you on windows 8?
get the drivers from http://forum.xda-developers.com/showthread.php?t=2135381
then look at the link to how to use adb and fastboot in my signature
Click to expand...
Click to collapse
Now Im on W8, never used this operating system before either so Im trying to figure this out as I go. Im a Mac guy(still on Leopard though, dont get me started).
So I used the CMD prompt to unlock the bootloader in the first place. The all in one toolkit is a POS, it doesnt seem to do anything. Anyway, so I went to your link and installed the drivers. All I want to do is root the device so I can install TWRP or vice versa(again, I always had a friend do this).
HyperM3 said:
Now Im on W8, never used this operating system before either so Im trying to figure this out as I go. Im a Mac guy(still on Leopard though, dont get me started).
So I used the CMD prompt to unlock the bootloader in the first place. The all in one toolkit is a POS, it doesnt seem to do anything. Anyway, so I went to your link and installed the drivers. All I want to do is root the device so I can install TWRP or vice versa(again, I always had a friend do this).
Click to expand...
Click to collapse
once you have the drivers installed
it's simple and all in ones aren't needed really.
I have a mac too and have to do it all by hand.
follow the directions in this thread http://forum.xda-developers.com/showthread.php?t=2182792
I installed cwm then installed the root.zip.
gunnyman said:
once you have the drivers installed
it's simple and all in ones aren't needed really.
I have a mac too and have to do it all by hand.
follow the directions in this thread http://forum.xda-developers.com/showthread.php?t=2182792
I installed cwm then installed the root.zip.
Click to expand...
Click to collapse
Im just extremely computer illiterate apparently. No matter what I do my computer still says device not recognized. When I click on the device manager theres a yellow triangle over "my HTC". I click on it to try to update the drivers and it says they are up to date. I have no clue if thats even important. Im in research overload right now.
Still have access to a Mac? So much easier
gunnyman said:
Still have access to a Mac? So much easier
Click to expand...
Click to collapse
Yeah, Im on the mac for all of this research.
HyperM3 said:
Yeah, Im on the mac for all of this research.
Click to expand...
Click to collapse
install fastboot and adb for the mac and use it instead
commands are the same, no driver BS to worry about
gunnyman said:
install fastboot and adb for the mac and use it instead
commands are the same, no driver BS to worry about
Click to expand...
Click to collapse
I might just have to try that. I went through the whole rigamarole of creating the android folder and in there I put ADB, fastboot, adbwinapi.dll and the TWRP img file. I got the command line open trying to install the TWRP and it just sits there still saying <waiting for device>.
Trust me the mac is much easier
gunnyman said:
Trust me the mac is much easier
Click to expand...
Click to collapse
Ok, I have everything hooked up to the mac. When the phone is powered on I can use android file transfer to see all the folders in the phone. When I disconnect the phone, reboot into bootloader and then reconnect the phone, thats where Im lost. No clue what Im supposed to do next.
I have a folder on the desktop with the fastboot, adb and TWRP file in there. Im able to navigate my command prompt to that folder and then.....no clue what next.
HyperM3 said:
Ok, I have everything hooked up to the mac. When the phone is powered on I can use android file transfer to see all the folders in the phone. When I disconnect the phone, reboot into bootloader and then reconnect the phone, thats where Im lost. No clue what Im supposed to do next.
I have a folder on the desktop with the fastboot, adb and TWRP file in there. Im able to navigate my command prompt to that folder and then.....no clue what next.
Click to expand...
Click to collapse
ok open a command prompt
use spotlight and type terminal
once terminal is open
cd to the directory you put those files in
for example
cd /Users/Gunnyman/Desktop/files
once you're there
type ls and hit enter
this will give you a list of the files in that directory
you should see fastboot and adb and the recovery image
make sure your recovery is unzipped and says somefilename.img
once you've verified the files are there
type ./fastboot devices
you should see a serial number there
if it isn't there make sure you see fastboot when you did the ls command from before
next is installing the recovery
the command is ./fastboot flash recovery nameofrecovery.img
after that completes completely power down your phone
power it back up and when it boots type ./adb reboot bootloader
from there choose recovery and recovery should boot
sometimes this takes a couple of tries to make it stick.
---------- Post added at 03:57 PM ---------- Previous post was at 03:55 PM ----------
gunnyman said:
ok open a command prompt
use spotlight and type terminal
once terminal is open
cd to the directory you put those files in
for example
cd /Users/Gunnyman/Desktop/files
once you're there
type ls and hit enter
this will give you a list of the files in that directory
you should see fastboot and adb and the recovery image
make sure your recovery is unzipped and says somefilename.img
once you've verified the files are there
type ./fastboot devices
you should see a serial number there
if it isn't there make sure you see fastboot when you did the ls command from before
next is installing the recovery
the command is ./fastboot flash recovery nameofrecovery.img
after that completes completely power down your phone
power it back up and when it boots type ./adb reboot bootloader
from there choose recovery and recovery should boot
sometimes this takes a couple of tries to make it stick.
Click to expand...
Click to collapse
installing the root is as simple as dragging the root.zip or whatever it's called onto your phone rebooting to recovery and installing it
gunnyman said:
ok open a command prompt
use spotlight and type terminal
once terminal is open
cd to the directory you put those files in
for example
cd /Users/Gunnyman/Desktop/files
once you're there
type ls and hit enter
this will give you a list of the files in that directory
you should see fastboot and adb and the recovery image
make sure your recovery is unzipped and says somefilename.img
once you've verified the files are there
type ./fastboot devices
you should see a serial number there
if it isn't there make sure you see fastboot when you did the ls command from before
next is installing the recovery
the command is ./fastboot flash recovery nameofrecovery.img
after that completes completely power down your phone
power it back up and when it boots type ./adb reboot bootloader
from there choose recovery and recovery should boot
sometimes this takes a couple of tries to make it stick.
---------- Post added at 03:57 PM ---------- Previous post was at 03:55 PM ----------
installing the root is as simple as dragging the root.zip or whatever it's called onto your phone rebooting to recovery and installing it
Click to expand...
Click to collapse
I was good up until this failed:
Macintosh-2:android HyperM3$ ls
adb openrecovery-twrp-2.5.0.0-m7.img
fastboot
Macintosh-2:android HyperM3$ ./fastboot devices
HT348W907962 fastboot
Macintosh-2:android HyperM3$ ./fastboot flash recovery openrecovery-twrp-2.5.0.0-m7.img
sending 'recovery' (0 KB)...
FAILED (remote: unknown command)
finished. total time: 0.000s
That looks like a bad.download of the recovery. It shouldn't say 0 kb. Your command looks right
gunnyman said:
That looks like a bad.download of the recovery. It shouldn't say 0 kb. Your command looks right
Click to expand...
Click to collapse
I didnt even notice that 0 file size. Just downloaded it again and followed your steps. Totally worked and Im looking at TWRP on my phone right now. Thank you for your patience and rocking ability to walk me through this. Is there anyway I can donate to you for something? I cant click "thank you" for your posts enough.
Happy to help. No donations necessary.
Hello everyone, I really messed up my phone. Right now i have twrp recovery with no rom or anything ive tried to sideload roms through the wonderful tool That Hasoon2000 has made is there a way to fix my phone or do i need to just pay htc to fresh install everything?
dqlover4ever said:
Hello everyone, I really messed up my phone. Right now i have twrp recovery with no rom or anything ive tried to sideload roms through the wonderful tool That Hasoon2000 has made is there a way to fix my phone or do i need to just pay htc to fresh install everything?
Click to expand...
Click to collapse
So sideload did not work with toolkit i guess? It may take some minutes for your computer to recognize your phone in recovery or adb sideload state. Honestly said i don't use the toolkit.
What i recommend is:
- read this: http://forum.xda-developers.com/showthread.php?t=2213910
and set up an adb/fastboot environment like explained. copy the desired rom into this adb/fastboot folder.
- boot your phone in recovery, connect it to your computer, start adb sideload in TWRP
- open command line (if necessary navigate to your adb/fastboot folder) and type "adb start-server"
- wait some minutes and type "adb devices". your device should now be listed there as in sideload mode. if it's not the case, repeat this step.
(shouldn't take more than 10 minutes for your pc to recognize your phone, otherwise there's most likely something wrong with your driver)
- now that it shows up in the list as in sideload mode, type "adb sideload name_of_your_rom.zip" and command line should start displaying progress in %.
When it is finished, rom installation should be started automatically. Otherwise, the rom is now saved as "sideload.zip" on the root of your virtual sdcard folder, so you can flash it.
Also don't forget to install the right boot.img/kernel for the rom!
reaper90 said:
So sideload did not work with toolkit i guess? It may take some minutes for your computer to recognize your phone in recovery or adb sideload state. Honestly said i don't use the toolkit.
What i recommend is:
- read this: http://forum.xda-developers.com/showthread.php?t=2213910
and set up an adb/fastboot environment like explained. copy the desired rom into this adb/fastboot folder.
- boot your phone in recovery, connect it to your computer, start adb sideload in TWRP
- open command line (if necessary navigate to your adb/fastboot folder) and type "adb start-server"
- wait some minutes and type "adb devices". your device should now be listed there as in sideload mode. if it's not the case, repeat this step.
(shouldn't take more than 10 minutes for your pc to recognize your phone, otherwise there's most likely something wrong with your driver)
- now that it shows up in the list as in sideload mode, type "adb sideload name_of_your_rom.zip" and command line should start displaying progress in %.
When it is finished, rom installation should be started automatically. Otherwise, the rom is now saved as "sideload.zip" on the root of your virtual sdcard folder, so you can flash it.
Also don't forget to install the right boot.img/kernel for the rom!
Click to expand...
Click to collapse
I got Sideload to work got to the android revolution to start installing... after that just the same boot screen trying elegancia now thanks for your reply im just wondering why it went right back to the boot splash screen right after it installed
reaper90 said:
Also don't forget to install the right boot.img/kernel for the rom!
Click to expand...
Click to collapse
dqlover4ever said:
I got Sideload to work got to the android revolution to start installing... after that just the same boot screen trying elegancia now thanks for your reply im just wondering why it went right back to the boot splash screen right after it installed
Click to expand...
Click to collapse
Did you flash the correct boot.img like i said? what boot logo is it? the "htc quietly brilliant" one or the "htc one" with beats audio logo?
If it's the first one you did not flash the boot.img.
If second (and of course you did flash the boot.img), there must be something else wrong. boot in recovery:
Wipe > Advanced Wipe > Check all boxes > Swipe to wipe > reinstall rom!
Just DON'T format /data partition.
you were right thank you very much!:fingers-crossed:
I kinda messed up about a month ago, I was wanting to root my HTC One so I could try some custom ROMS and experience other cool stuff
However, Me, feeling nervous decided to go the Cyanogenmod Installer route (You know this isn't gonna end well). And so I plugged in my device and everything was good and fine until It was unlocking my bootloader, it seemed to do the HTCDev one, I got the option to unlock it or lock it, and as soon as the device restarted the phone disconnected.
Some apps went missing, however I recently had a talk to a friend who said that is normal, and he recommended me to come here to get some help.
I can boot into the bootloader where you can go into fastboot and stuff, I can factory reset through the Android OS once its booted, however when I enter recovery in the bootloader, the screen goes black and a red exclamation mark shows up for about 5-10 minutes and then the device reboots into Android.
The same thing happens when I try to get Over the air updates, I can still get OTA updates, they just don't install.
So what I'm looking for is, can I relock my device and get it back to how it was before I ran Cyanogenmod installer and then maybe I can try root it manually and have more control over the situation.
I hope you guys can help me and I hope I can find a place on this forum
Thanks in advance guys!
First of all, it seems you shouldn't have started to mess with this at all...
now to fix this...
Download the latest recovery of your choice e.a. twrp. @ http://techerrata.com/browse/twrp2/m7 the normal one is the m7 i suppose? else go to the right section...
save it to your /sdcard directly or move it there. than for the eaz just rename it to twrp.img
open an terminal if installed on your device and type
su
than
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p34 (note command for the m7)
if you however don't have the capability to install an app because of missing gapps... which sounds like it...
install adb/fastboot on your pc with the htc drivers..
download the recovery image with your pc and rename it to twrp.img and put it at your fastboot file
turn off your device
keep holding volume down until a menu shows up
select fastboot from the menu
attach the device to your pc
open cmd and type fastboot devices (to see if you actually installed the right driver... and that it's recognizing it)
if it does
type:
fastboot flash recovery twrp.img
if that all succeeded, you can download gapps for the android version your using or flash something else with the working recovery..
goodluck!
Hawkysoft said:
First of all, it seems you shouldn't have started to mess with this at all...
now to fix this...
Download the latest recovery of your choice e.a. twrp. @ (It prevented me posting links) the normal one is the m7 i suppose? else go to the right section...
save it to your /sdcard directly or move it there. than for the eaz just rename it to twrp.img
open an terminal if installed on your device and type
su
than
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p34 (note command for the m7)
if you however don't have the capability to install an app because of missing gapps... which sounds like it...
install adb/fastboot on your pc with the htc drivers..
download the recovery image with your pc and rename it to twrp.img and put it at your fastboot file
turn off your device
keep holding volume down until a menu shows up
select fastboot from the menu
attach the device to your pc
open cmd and type fastboot devices (to see if you actually installed the right driver... and that it's recognizing it)
if it does
type:
fastboot flash recovery twrp.img
if that all succeeded, you can download gapps for the android version your using or flash something else with the working recovery..
goodluck!
Click to expand...
Click to collapse
Thank you! Will there be a risk in ruining my device?
And thank you once again! I definitley shouldn't have messed with this, but you gotta start somewhere right?
If I never took the risk of building my own computer then I never could have done it Its how we learn.
Anyways, I'm not sure about the terminal bit, I don't run linux and I don't have a mac? So, how would I have access to the terminal. Unless I somehow got it on my device (I don't know how to do that).
And one more question, once I've done the things you've told me to do I can just put Cyanogenmod on it?
Thanks once again
Oh, and I have got Gapps, if my Gapps you mean Google Apps, yes I have I've got Google play services, Google play, hangouts etc.
Thank you! Will there be a risk in ruining my device?
Click to expand...
Click to collapse
Further than now? i highly doubt it... unless you totally put in a wrong recovery which magically wud fk up the partitions?
And thank you once again! I definitley shouldn't have messed with this, but you gotta start somewhere right?
Click to expand...
Click to collapse
True, but babysteps mate...
Anyways, I'm not sure about the terminal bit, I don't run linux and I don't have a mac? So, how would I have access to the terminal. Unless I somehow got it on my device (I don't know how to do that).
Click to expand...
Click to collapse
Terminal should be on the phone, if not use command prompt in windows... u need to do a little research on the m7 forums which driver you need they probably have an m7 toolkit again if the one is the m7, as far as i knew it is.. than you could put the recovery.img in the folder of fastboot.exe and go there with command prompt and do what i've written before
And one more question, once I've done the things you've told me to do I can just put Cyanogenmod on it?
Click to expand...
Click to collapse
erhm ofcourse you can, however just download the rom instead of an installer...
p.s. you got gapps.. install an emulator oh... better solution... install flashify download the latest twrp and install it with that if u have proper root that is!
Hawkysoft said:
Further than now? i highly doubt it... unless you totally put in a wrong recovery which magically wud fk up the partitions?
True, but babysteps mate...
Terminal should be on the phone, if not use command prompt in windows... u need to do a little research on the m7 forums which driver you need they probably have an m7 toolkit again if the one is the m7, as far as i knew it is.. than you could put the recovery.img in the folder of fastboot.exe and go there with command prompt and do what i've written before
erhm ofcourse you can, however just download the rom instead of an installer...
p.s. you got gapps.. install an emulator oh... better solution... install flashify download the latest twrp and install it with that if u have proper root that is!
Click to expand...
Click to collapse
Thanks I don't have root, I've run rootchecker, and it says I don't have root.
And what if I do Cyanogenmod but I want to go back to HTC Sense (Doubt it though)
Will instlaling the recovery root my device? If not, how will I root it?
Oh and, how do I get fastboot and ADB?
So I need to appeal to the android gurus of the world. I have an issue that I am having a difficult time sussing out and I am hoping someone else can help me figure it out.
My device is an HTC One M7, rooted, running Insert Coin 3.0.2 (Android 4.4.2), S-On., Hboot 1.44, TWRP Recovery
My problem is I can not access my Recovery and Fastboot isn't seeing my device, so I can not flash a new one. I can get to my phone in adb, just fine, but using flash_image to flash a recovery threw up a -1 error, so flashing recovery through adb appears to be out, as well. If I go to my Bootloader, selecting Recovery simply dumps me back to Fastboot.
I haven't booted into recovery since I installed this Rom, months ago, so I don't know exactly when my Recovery broke. I do know that today, I tried updating TWRP through Flashify and I suspect that may be part of the issue, since Flashify insisted on pulling down the TWRP for the M8 instead of the M7. I didn't catch that little nugget till after I flashed it.
I am pretty well open to anything that might work, but I am not sure what my options are when I can't even get into recovery. A pre-emptive thank you to anyone attempting to help. It should be said that apart from this, the phone works fine. I simply can't get into recovery to update my ROM, anymore.
Ok, I am an idgit. Could a mod move this to the Q&A forum? Apologies.
EqualOpportunityDork said:
So I need to appeal to the android gurus of the world. I have an issue that I am having a difficult time sussing out and I am hoping someone else can help me figure it out.
My device is an HTC One M7, rooted, running Insert Coin 3.0.2 (Android 4.4.2), S-On., Hboot 1.44, TWRP Recovery
My problem is I can not access my Recovery and Fastboot isn't seeing my device, so I can not flash a new one. I can get to my phone in adb, just fine, but using flash_image to flash a recovery threw up a -1 error, so flashing recovery through adb appears to be out, as well. If I go to my Bootloader, selecting Recovery simply dumps me back to Fastboot.
I haven't booted into recovery since I installed this Rom, months ago, so I don't know exactly when my Recovery broke. I do know that today, I tried updating TWRP through Flashify and I suspect that may be part of the issue, since Flashify insisted on pulling down the TWRP for the M8 instead of the M7. I didn't catch that little nugget till after I flashed it.
I am pretty well open to anything that might work, but I am not sure what my options are when I can't even get into recovery. A pre-emptive thank you to anyone attempting to help. It should be said that apart from this, the phone works fine. I simply can't get into recovery to update my ROM, anymore.
Click to expand...
Click to collapse
ADB works in an OS or in custom recovery and fastboot works in the bootloader. ADB doesn't work if the phone is in bootloader. I think you will have to run a RUU then go into stock recovery and do a factory reset. Let the phone boot normally then you can start the custom routine. You might also check to see if your ADB & fastboot are up to date. To run the RUU you will have to relock your bootloader since you are S-ON.
Thanks. Yea, I've managed to figure out the difference between adb and fastboot through all this. so plus for learning! However, the only method I have found for relocking my bootloader is through fastboot, which I can't seem to be able to use.
I will see if there's a newer version of fastboot out there, though. hadn't thought of that.
EqualOpportunityDork said:
Thanks. Yea, I've managed to figure out the difference between adb and fastboot through all this. so plus for learning! However, the only method I have found for relocking my bootloader is through fastboot, which I can't seem to be able to use.
I will see if there's a newer version of fastboot out there, though. hadn't thought of that.
Click to expand...
Click to collapse
Another quick thought, you wouldn't happen to be using Win 8 are you? If so, Win 8 doesn't see hboot 1.44 you are going to have to use a Win 7, Mac or Linux machine. Sorry, I didn't catch it earlier. Here is a how to for Linux and you don't have to install it permanently on your computer:
HOW TO USE LINUX FOR FASTBOOT & ADB VIA USB
This guide originally posted by @Danny201281
http://forum.xda-developers.com/showpost.php?p=54272479&postcount=219Linux is your friend; if your drivers are not working the chances of getting them working again without the phone booting are slim. But Linux doesn't need drivers to talk to your device.
Go here: http://www.pendrivelinux.com/ and download Universal USB Installer – Easy as 1 2 3
Then go here: http://releases.ubuntu.com/12.04/ and download Ubuntu from the first link at the top that says PC (Intel x86) desktop CD
Then use these files to create a bootable Linux USB drive with at least a 2 GB persistent file for storing files. You'll also probably need to change your boot settings in the computers bios to boot from USB.
MOVING YOUR FILES TO UBUNTU
Once booted you should be at a screen with options to "Try Ubuntu” or "Install Ubuntu". We don’t need to Install anything so just choose "Try Ubuntu" and the computer will boot to the Ubuntu Desktop (If you get a popup saying "system has encountered an error" or something similar just cancel and ignore it, it should have no effect on what we need to do as it is due to missing Linux OS updates we don’t need). On the left of the screen you'll see the Dock. Open the orange folder icon near the top this is the Home folder. It’s where we need to put any files we need to work with such as a rom.zip you want to push to the device or recovery.img files for flashing.
To get your files here is a simple drag and drop process. In the top left of the Home folder you'll see the drive structure of you pc under devices. Choose your PCs hard drive and Right-Click then" Open in a new window". Locate your .zip or .img files and drag them into the home folder. Now wait for the copy process to complete and rename them for easier typing later, e.g., rom.zip, firmware.zip or recovery.img etc.
USING ADB AND FASTBOOT
First you need to install adb fastboot; this is easy just 3 commands in the terminal. Thanks to Webupd8 team.
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
Code:
sudo apt-get update
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
Make sure your connected to the internet and press Ctrl+Alt+T to open the terminal then type or copy and paste the above commands one at a time waiting for each to complete their output. It may seem to have stopped at times but be patient when the prompt returns to normal enter the next command and when there all done you’re ready to use adb and fastboot.
Once you've moved all the files you need to the home folder that’s it you’re ready to go. Close everything down on the desktop (optional) and press Ctrl+Alt+T this will open the terminal now connect your phone with the USB cable. All fastboot commands need to have the "sudo" prefix added at the start, e.g.
fastboot flash recovery recovery.img becomes sudo fastboot flash recovery recovery.img
fastboot devices becomes sudo fastboot devices
However, adb should work basically the same as on windows. If you do have problems with normal adb commands adding “sudo” can help here as well.
Click to expand...
Click to collapse
Dude, you are my hero. I couldn't get fastboot to work, because I had missed the part where I needed to preface it with sudo. I had adb and fastboot running a couple of days ago on my Mint install, but I didn't realize I was missing 4 freaking letters to get it right. Just flashed latest twrp and booted into recovery, no problem.
Thanks again, for the help, even if I should have found that on my own, sooner. I thought I had really hosed something on my phone. Now I can move on to hopefully not screwing something else up.
You could have used flashify to flash a recovery.IMG. free app from app store
I mentioned trying Flashify in the OP.
hi all,
i have a rooted vivo air lte with supersu.
i wanted to install magisk with the manager 8.0.3 (the boot.img from stock rom i extracted to downloads folder) by choosing direct install.
now the phone hangs on the bootlogo.
i can boot into recovery and choose "apply update from adb"
i installed fastboot and adb on the pc.
in the terminal command "adb devices" i see "devicenr sideload".
when i enter fastboot devices, there is no device shown.
im not sure if i have unlocked the bootloader when i rooted the phone a year ago..
so what do i have to do now to get it booting again?
thanks for the help!
schlunk said:
in the terminal command "adb devices" i see "devicenr sideload".
Click to expand...
Click to collapse
Device is configured to get booted in "Sideload" mode what is a variant of ADB mode.
Try this
Code:
adb devices
adb reboot
to return to "Normal" mode.
no, this is what i have chosen in the recovery, otherwise i dont get any device listed in the terminal..
@schlunk
Once being in the Android Recovery Mode and you select option Reboot system the Android device simply gets restarted: the actually configured ADB mode herewith doesn't get changed / reset.
when i enter "adb reboot" in the terminal its "error closed"..
is ther e something i can sideload then to solve this, when the phone is waiting for the package to sideload?
thanks for helping!
schlunk said:
when i enter "adb reboot" in the terminal its "error closed"..
is ther e something i can sideload then to solve this, when the phone is waiting for the package to sideload?
thanks for helping!
Click to expand...
Click to collapse
QFIL is the answer.
this is a flasher like odin?
so can i just flash the boot.img, that magisk wrote back to the stock one?
and like i said im not sure if the bootloader is unlocked, does it play a role in this?
schlunk said:
this is a flasher like odin?
so can i just flash the boot.img, that magisk wrote back to the stock one?
and like i said im not sure if the bootloader is unlocked, does it play a role in this?
Click to expand...
Click to collapse
https://firmwarefile.com/blu-vivo-air-lte-v0010uu
https://www.youtube.com/watch?v=MdknZvaTwl4
thats exactly the file i downloaded to extract the boot.img and see what happend
i dont want to flash the complete stock firmware again with the risk that my phone is bricked after that.
there must be some easier solution for this??
cant i just flash what magisk messed up?
schlunk said:
there must be some easier solution for this??
cant i just flash what magisk messed up?
Click to expand...
Click to collapse
Nope, I don't think there is.
Depends if that boot is same that was in your device. See the video
and the thread too: https://forum.hovatek.com/thread-31476.html
The boot should be the same, the firmware is exactly the same like in the phone regarding the label.
So with this linked method, flashing a single partition means, the boot.img can be flashed solo, without the need of flashing the whole firmware?
And when that doesnt work, i still could flash the whole firmware then as last resort?
That what I would do... Good luck!