After i'm rooted am i able to install twrp from fastboot or do i HAVE to use goomanager?
and if i can do it through fastboot why do i have to be rooted for it to work if its fastboot?
on 4.2.2 if it changes anything thanks
what phone do you have. your info says you are on tmobile. this is att. or, is your info not up to date?
if you have an i337 att phone, you can't use fastboot
rugmankc said:
what phone do you have. your info says you are on tmobile. this is att. or, is your info not up to date?
if you have an i337 att phone, you can't use fastboot
Click to expand...
Click to collapse
not up to date at all and oh ok thanks so my only option is goomanager?
depends on your build. if you are mdl, I would recommend Adam's Casual. Flashes twrp and roots. Otherwise, you can use goo initially then i would flash thru recovery. BTW twrp 2.5.0.2 seems best for most
you must be rooted to use goo mananger though
if you are mf3 you can only root and not able to put recovery or roms on phone. with a locked bootloader some recommend not to root on mf3 as some situations may not be fixable
We don't have fastboot on the S4 -- we have Odin mode instead.
I'm a new fan of Heimdall (http://www.glassechidna.com.au/products/heimdall/) given it's fastboot-like command line interface. Once you have it set up on you workstation, you should be able to to run:
Code:
heimdall flash --RECOVERY "C:\path\to\recovery.img" --no-reboot
More information about using Heimdall to flash recoveries can be found here: http://forum.xda-developers.com/showthread.php?t=2346806 (be careful though, this is from the Sprint S4 forum)
Related
I'm attempting to flash a ROM to my Galaxy S4 using the adb sideload method. However, my computer doesn't recognize my phone unless I use the default recovery mode. I can't use the default recovery mode because the signature verification fails. I've tried CWM and TWRP, and in both cases adb returns "error: device not found". Are there extra drivers I need to install?
Using an AT&T Galaxy S4 I337 on stock 4.2.2 rooted.
Motu88 said:
I'm attempting to flash a ROM to my Galaxy S4 using the adb sideload method. However, my computer doesn't recognize my phone unless I use the default recovery mode. I can't use the default recovery mode because the signature verification fails. I've tried CWM and TWRP, and in both cases adb returns "error: device not found". Are there extra drivers I need to install?
Using an AT&T Galaxy S4 I337 on stock 4.2.2 rooted.
Click to expand...
Click to collapse
If your rooted just do a straight flash in recovery.. Please wipe 1st no dirty flashes then flash the kernel
sloanster said:
If your rooted just do a straight flash in recovery.. Please wipe 1st no dirty flashes then flash the kernel
Click to expand...
Click to collapse
Thanks for your reply. I have been flashing straight from the phone's memory, but I would still like to know what I can do to get the adb method working for future reference. If I accidentally get to a point where I can't boot properly and I don't have an available backup on the phone, I want to be able to flash from my desktop.
Motu88 said:
I'm attempting to flash a ROM to my Galaxy S4 using the adb sideload method. However, my computer doesn't recognize my phone unless I use the default recovery mode. I can't use the default recovery mode because the signature verification fails. I've tried CWM and TWRP, and in both cases adb returns "error: device not found". Are there extra drivers I need to install?
Using an AT&T Galaxy S4 I337 on stock 4.2.2 rooted.
Click to expand...
Click to collapse
I had similar problems with TWRP. I ended up searching around Google and found some drivers that worked. Some keywords I used were the Hardware ID(s) that the unknown device gave to Windows, and "twrp". It's just using a different version of ADB or something, and Windows doesn't like it. I'm out of time for today, but I'm sure you'll find it. Look for google results that take you either to XDA or over to TWRP's website.
I had rooted my Nexus 4 when on 4.2.x by putting it in bootloader mode first and typing fastboot boot <name of twrp custom recovery>.img at the command prompt to reboot it into TWRP custom recovery mode without if actually flashing the TWRP recovery on the device. Back then, this temporarily recovery mode allowed me to flash the supersu update zip file I needed to. Since 4.3, this command reboots the phone, but the screen is now blank, and I can't flash the zip file. I can reboot the phone normally into stock recovery mode using the volume keys and power button, but this does not allow me to flash the zip file to root it. Can I still use fastboot boot method like before, and how? The reason I want t stay on stock recovery for now is to keep future OTA updates from throwing an error message.
rajendra82 said:
I had rooted my Nexus 4 when on 4.2.x by putting it in bootloader mode first and typing fastboot boot <name of twrp custom recovery>.img at the command prompt to reboot it into TWRP custom recovery mode without if actually flashing the TWRP recovery on the device. Back then, this temporarily recovery mode allowed me to flash the supersu update zip file I needed to. Since 4.3, this command reboots the phone, but the screen is now blank, and I can't flash the zip file. I can reboot the phone normally into stock recovery mode using the volume keys and power button, but this does not allow me to flash the zip file to root it. Can I still use fastboot boot method like before, and how? The reason I want t stay on stock recovery for now is to keep future OTA updates from throwing an error message.
Click to expand...
Click to collapse
This is still possible but the command for booting into custom recovery changed.
This helps.
rajendra82 said:
I had rooted my Nexus 4 when on 4.2.x by putting it in bootloader mode first and typing fastboot boot <name of twrp custom recovery>.img at the command prompt to reboot it into TWRP custom recovery mode without if actually flashing the TWRP recovery on the device. Back then, this temporarily recovery mode allowed me to flash the supersu update zip file I needed to. Since 4.3, this command reboots the phone, but the screen is now blank, and I can't flash the zip file. I can reboot the phone normally into stock recovery mode using the volume keys and power button, but this does not allow me to flash the zip file to root it. Can I still use fastboot boot method like before, and how? The reason I want t stay on stock recovery for now is to keep future OTA updates from throwing an error message.
Click to expand...
Click to collapse
The short answer is no, you need a custom recovery to install superuser. The long answer is you can flash a custom recovery and install superuser and then flash back the stock recovery. If that doesn't work then your out of luck.
kzoodroid said:
The short answer is no, you need a custom recovery to install superuser. The long answer is you can flash a custom recovery and install superuser and then flash back the stock recovery. If that doesn't work then your out of luck.
Click to expand...
Click to collapse
You are absolutely wrong. I just booted into TWRP without flashing it and rooted my Nexus 4, which is otherwise stock 4.3. I still have the stock recovery on the device and can access it using the volume keys. Booting into TWRP was a temporary state achieved using the command line syntax:
fastboot -c "<your_default_command_line> lge.kcal=0|0|0|x" boot <name of custom recovery>.img
The 4.2.x version of this command was simpler, as it did not require the -c "<your_default_command_line> lge.kcal=0|0|0|x" part, but you do need it on 4.3, or the device just temporarily boots into a blank screen, instead of the custom recovery. So the long answer is you do need to boot into a custom recovery, but it does not have to be flashed to the boot partition. With a Nexus 4, you are never out of luck.
rajendra82 said:
You are absolutely wrong. I just booted into TWRP without flashing it and rooted my Nexus 4, which is otherwise stock 4.3. I still have the stock recovery on the device and can access it using the volume keys. Booting into TWRP was a temporary state achieved using the command line syntax:
fastboot -c "<your_default_command_line> lge.kcal=0|0|0|x" boot <name of custom recovery>.img
The 4.2.x version of this command was simpler, as it did not require the -c "<your_default_command_line> lge.kcal=0|0|0|x" part, but you do need it on 4.3, or the device just temporarily boots into a blank screen, instead of the custom recovery. So the long answer is you do need to boot into a custom recovery, but it does not have to be flashed to the boot partition. With a Nexus 4, you are never out of luck.
Click to expand...
Click to collapse
Can you please write a Step by Step guide to root without flashing custom recovery,
I am familiar with basic commands of adb and fastboot. But a step wise guide will hep me get my N4 rooted
ajay_zalavadia said:
Can you please write a Step by Step guide to root without flashing custom recovery,
I am familiar with basic commands of adb and fastboot. But a step wise guide will hep me get my N4 rooted
Click to expand...
Click to collapse
Follow @efrant's guide. Section E is enough assuming you are on stock android.
That will do the trick.
rajendra82 said:
I had rooted my Nexus 4 when on 4.2.x by putting it in bootloader mode first and typing fastboot boot <name of twrp custom recovery>.img at the command prompt to reboot it into TWRP custom recovery mode without if actually flashing the TWRP recovery on the device. Back then, this temporarily recovery mode allowed me to flash the supersu update zip file I needed to. Since 4.3, this command reboots the phone, but the screen is now blank, and I can't flash the zip file. I can reboot the phone normally into stock recovery mode using the volume keys and power button, but this does not allow me to flash the zip file to root it. Can I still use fastboot boot method like before, and how? The reason I want t stay on stock recovery for now is to keep future OTA updates from throwing an error message.
Click to expand...
Click to collapse
Sorry for asking about your reason, but if you install the TWRP (or some other) custom recovery then can't you simply manually flash the OTA yourself? That's how I upgraded to 4.3.
ajay_zalavadia said:
Can you please write a Step by Step guide to root without flashing custom recovery,
I am familiar with basic commands of adb and fastboot. But a step wise guide will hep me get my N4 rooted
Click to expand...
Click to collapse
Copy your custom recovery to where fastboot.exe is.
Open a CMD window and type
adb reboot-bootloader
Click to expand...
Click to collapse
Then, once you're booted into Bootloader, type
fastboot -c "lge.kcal=0|0|0|x" boot customrecoveryname.img
Click to expand...
Click to collapse
Flash SuperSU 1.51 zip and then reboot your device.
rajendra82 said:
You are absolutely wrong. I just booted into TWRP without flashing it and rooted my Nexus 4, which is otherwise stock 4.3. I still have the stock recovery on the device and can access it using the volume keys. Booting into TWRP was a temporary state achieved using the command line syntax:
fastboot -c "<your_default_command_line> lge.kcal=0|0|0|x" boot <name of custom recovery>.img
The 4.2.x version of this command was simpler, as it did not require the -c "<your_default_command_line> lge.kcal=0|0|0|x" part, but you do need it on 4.3, or the device just temporarily boots into a blank screen, instead of the custom recovery. So the long answer is you do need to boot into a custom recovery, but it does not have to be flashed to the boot partition. With a Nexus 4, you are never out of luck.
Click to expand...
Click to collapse
In your original post you said you tried using the boot into recovery method and it didn't work so how am I wrong in saying that your only other option was to flash the custom recovery, install su, then flash the stock recovery all without rebooting? It was just another way of accomplishing the same thing. I posted at the same time as the other guy did who knew the new fastboot command, which I was unaware of and obviously you were too.
Mercado_Negro said:
Copy your custom recovery to where fastboot.exe is.
Open a CMD window and type
Then, once you're booted into Bootloader, type
Flash SuperSU 1.51 zip and then reboot your device.
Click to expand...
Click to collapse
thank you, will try when I get chance :good:
kzoodroid said:
In your original post you said you tried using the boot into recovery method and it didn't work so how am I wrong in saying that your only other option was to flash the custom recovery, install su, then flash the stock recovery all without rebooting? It was just another way of accomplishing the same thing. I posted at the same time as the other guy did who knew the new fastboot command, which I was unaware of and obviously you were too.
Click to expand...
Click to collapse
I just prefer the command line booting instead of having to flash a recovery twice. I already knew that I could flash the custom recovery to get it done, although I didn't clearly state that in the original post.
Mercado_Negro said:
Copy your custom recovery to where fastboot.exe is.
Open a CMD window and type
Then, once you're booted into Bootloader, type
Flash SuperSU 1.51 zip and then reboot your device.
Click to expand...
Click to collapse
Thanks for you guide, but for use it, do I nerd unlocke the bootloader ?
Inviato dal mio Nexus 4 con Tapatalk 2
futuro82 said:
Thanks for you guide, but for use it, do I nerd unlocke the bootloader ?
Inviato dal mio Nexus 4 con Tapatalk 2
Click to expand...
Click to collapse
Yes
Thanks
Inviato dal mio Nexus 4 con Tapatalk 2
kzoodroid said:
In your original post you said you tried using the boot into recovery method and it didn't work so how am I wrong in saying that your only other option was to flash the custom recovery, install su, then flash the stock recovery all without rebooting? It was just another way of accomplishing the same thing. I posted at the same time as the other guy did who knew the new fastboot command, which I was unaware of and obviously you were too.
Click to expand...
Click to collapse
LOL.. You were still wrong though bro. Don't get upset about it. He didn't seem to be...
Sent from my Nexus 4 using xda app-developers app
Ok after several tries many flashes I found a way that you can root you device. so here goes this tutorial.
after flashing KK AT&T or T-Mobile, once it rebooted manually keep holding dow volumen key to get into fastboot mode. In there you need to do the following.
download TWRP for KK from here http://androidhosting.org/Devs/Dhacker29/MotoX/
flash it using fastboot. "fastboot flash recovery twrp_name.img" without the cuotes where twrp_name is the file you downloaded.
once flashed access recovery and reboot from TWRP, it will ask if you want to root, click yes.
then follow the normal process of sign into your google account etc.
Note that you need to wipe all your data before installing any of the leaks. to do that using fastboot the command is fastboot -w
Note 2: after flashing you cant go into android setup. ypu need to press volumen down antil it goes to recovery.
Note3: I'm not responsable for any demage or bricked device.
hope this helps.
Regards
This is only for people who have an unlocked bootloader. It will not help those who are running the AT&T phones and flashing the system.img and boot.img
This method is no different than what is already known for unlocked bootloaders.
BrokenWall said:
This is only for people who have an unlocked bootloader. It will not help those who are running the AT&T phones and flashing the system.img and boot.img
This method is no different than what is already known for unlocked bootloaders.
Click to expand...
Click to collapse
It is different, becasue after yo have a full working rom and sign in with google everytime you access twrp it crashes
beelzebu said:
It is different, becasue after yo have a full working rom and sign in with google everytime you access twrp it crashes
Click to expand...
Click to collapse
I will not argue the point with you. Your method you listed here is no different than that of the standard method to install a recovery and root on a phone that has an unlocked bootloader.
EDIT - UPDATED INSTRUCTIONS 12th May 2014
Due to the partition sizes being different in the GPE RUU it is not simply a case of flashing a sense rom in recovery. You will experience problems if you do this. This might involve getting the storage encrption message, bootloops, freezing etc etc.
This thread is specifically for users who have problems getting back to sense. Solution is below. If you have alternative solutions that have worked without issues please post.
I have tried to make them as simple as possible. This guide assumes you are S-Off otherwise how did you get here. (
This does not apply if you have installed a GPE ROM. You can flash as normal through recovery. (using instructions of new rom)
Thanks to @exad for his continuing support/assistance throughout the thread, as well as @graffixnyc for the GPE RUU and both he and @navalynt for finding the initial fixes.
It will be much easier if you have your new Rom on your external sdcard prior to starting this. It will also stop a number of problems if you have SuperCID (11111111) If you don't know how to - FASTBOOT Commands
1. Enter the command "fastboot oem readcid". Make and KEEP a note of your original CID.
2. Enter the command "fastboot oem writecid 11111111"
3. Enter the command "fastboot read cid" [it should confirm your CID is 11111111]
4. Press the volume down button twice on your phone and navigate to reboot bootloader, then hit power button to reboot the bootloader.
5. Bootloader will also say "CID-11111111" now to confirm (Thanks to @xl VipeR lx ) Also to @umjammerlammy for the GENTLE reminders to include this
Make sure the firmware file and twrp recovery are in your Android directory on your PC - Mine is
C:\Users\Grentuu\AppData\Local\Android\android-sdk\platform-tools\
During this process you may find that when you reboot the phone starts to boot into android. Mine did but simply had the GPE animated logo but never entered GPE. All you do is press Vol up and power for about 10 seconds to reset. As soon as it resets press vol down and power to get back to bootloader.
Flash 1.54.401.5 firmware from Here
Fastboot Method
Boot device into FASTBOOT mode either by adb reboot bootloader or Vol down & Power (device should show FASTBOOT USB)
Make sure the firmware file to be flashed is in your android folder
Open a command prompt from the folder where fastboot resides. (Hold shift key/right click in the dir to get menu - left click on Open Command Prompt here.)
Run the following commands:
fastboot oem rebootRUU (this will reboot the device into RUU mode in preparation for zip flashing)
fastboot flash zip 1.54.401.5-W_Splash.zip (the name of the zip should EXACTLY match the name of the file you're flashing)
It will fail the first time. Run the same command AGAIN until you see it has flashed successfully.
I repeat - Run the same command TWICE until you see it has flashed successfully.
Once complete, type fastboot reboot-bootloader The hyphen is required.
Some users have stated this firmware (1.54.401.5) did not work for them as they weren't GSM and reboots just threw them back to recovery. If this happens try a stock (your original e.g. T-mobile) firmware then follow the rest of the process.
Boot into stock recovery
Factory reset
Reboot into bootloader
Flash TWRP - command = fastboot flash recovery openrecovery-twrp-2.7.0.2-m8.img (The must match exactly the name of the recovery you are flashing and remember the recovery file must be in your android folder)
Boot into TWRP
Go into Wipe menu
do a full factory reset wipe
Reboot back into recovery
Install rom
Profit
These have worked for me everytime (Change count =19)
Thanks for this. I'm about to give it a shot now.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
---------- Post added at 05:08 PM ---------- Previous post was at 04:40 PM ----------
For some reason the firmware wont flash in twrp. Should I sideload the firmware?
Sent from my GT-P5210 using XDA Premium 4 mobile app
To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firmwarefilename.zip
Then again
Fastboot flash zip firmwarefilename.zip
Fastboot reboot-bootloader
exad said:
To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firnwarefilename.zip
Then again
Fastboot flash zip firnwarefilename.zip
Fastboot reboot-bootloader
Click to expand...
Click to collapse
Thanks. Understood, I was just reviewing my steps for the conversion. I really just want to try out that new Sense rom and then I'll probably revert back. BRB...I'll let you know how it goes.
Bear in mind you must have S-off to flash a firmware that way.
exad said:
To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firmwarefilename.zip
Then again
Fastboot flash zip firmwarefilename.zip
Fastboot reboot-bootloader
Click to expand...
Click to collapse
Those are the instructions in post 1 the original thread.
The issue is with people wanting to go back to sense
This thread is about returning to sense. Flashing a firmware is always the same. It's the firmware itself that's different...
Here is where I am at..
I converted to GP easily and it worked well.. I wanted to convert back so I installed twrp first, then through twrp installed the 1.54.401.5 firmware.
Installing that firmware removed twrp and the rom. So I am without an OS at all, and have stock recovery.
Is there anyway I can flash a custom recovery or a rom via the stock firmware/recovery?
My computer will not recognize adb devices. But it used to obviously.
I have an SD card.
Any help and I will be sooo grateful. (maybe even donate)
Thanks!
You can't flash a firmware through recovery... You can flash a stock recovery after the steps listed above if you like. See the stock backup thread.
You can flash any recovery through fastboot... Adb only works with the rom booted or with custom recovery booted.
Thanks will try it out.
exad said:
You can't flash a firmware through recovery... You can flash a stock recovery after the steps listed above if you like. See the stock backup thread.
You can flash any recovery through fastboot... Adb only works with the rom booted or with custom recovery booted.
Click to expand...
Click to collapse
So what do I do in this situation with no rom installed only 1.54 firmware and stock recovery.
Flash twrp
exad said:
Flash twrp
Click to expand...
Click to collapse
I have no rom installed, so it wont show in adb devices.
PunchLick said:
I have no rom installed, so it wont show in adb devices.
Click to expand...
Click to collapse
You flash recovery via fastboot, no need for a rom.
Just make sure you have the proper fastboot drivers from htc.
Dmaxon said:
You flash recovery via fastboot, no need for a rom.
Just make sure you have the proper fastboot drivers from htc.
Click to expand...
Click to collapse
ADB devices shows no devices. If i had custom recovery this would be so much easier, but im using 1.54.401.5 firmware with stock recovery and no ROM.
Just dont know what to do to get a working device again. All i can do is boot into stock recovery, hboot and fastboot.. but computer shows no device.
PunchLick said:
ADB devices shows no devices. If i had custom recovery this would be so much easier, but im using 1.54.401.5 firmware with stock recovery and no ROM.
Just dont know what to do to get a working device again. All i can do is boot into stock recovery, hboot and fastboot.. but computer shows no device.
Click to expand...
Click to collapse
I would recommend the All-In-One Toolkit. This will allow you to fastboot the recovery, even though the pc doesn't recognize it. This has worked for me in the past.
Meanwhile, I get the following error message when attempting to flash the 1.54...
Any suggestions guys???
Problem solved. I had not supercid. After I did that, I was able to successfully flash 1.54...
Why post steps if your not willing to help?
The steps in the OP can still cause issues for some people.
Sent from my HTC One_M8 using Tapatalk
Ideas4ya said:
I would recommend the All-In-One Toolkit. This will allow you to fastboot the recovery, even though the pc doesn't recognize it. This has worked for me in the past.
Meanwhile, I get the following error message when attempting to flash the 1.54...
Any suggestions guys???
Problem solved. I had not supercid. After I did that, I was able to successfully flash 1.54...
Click to expand...
Click to collapse
Can you elaborate a little on which options etc, because that sounds fantastic and would help me so much!
PunchLick said:
Can you elaborate a little on which options etc, because that sounds fantastic and would help me so much!
Click to expand...
Click to collapse
When you open the all in one...the 3rd option on the top right is what you need. Follow the step, even if fastboot says device is not connected, this will still send the recovery to your device as long as you're in the bootloader.
I will never understand why people play with there phones and have no understanding of adb and fastboot commands with the bootloader. if people would learn that first there wouldn't be so many threads when they get stuck. tool kits are bad it makes people lazy. but I appreciate the devs who make them
Afaik you loose the OTA updates after rooting (because of twrp) so how do you keep your system up to date? or is this somthing that you risk in order to root your phone
You can try to flash the stock recovery back and install the firmware manually or using the updater, or you find the firmware in flashible zip format and flash it through twrp. I personally rooted without keeping Twrp so i can still update.
Thanks for answering! And yeah the problemas is that I cant find the firmware updates anywhere, so how do I root without a custom recovery? Can you tell me some hints to find the solution or a link? Thanks again
EDIT: Oh, just found a way, and in case someone is also wondering heres how its done: You have to boot to twrp through adb, and then you can flash super su without flashing the custom recovery . This is the generic way to do it, have not tested im my P8 yet, will report later.
fede011 said:
Thanks for answering! And yeah the problemas is that I cant find the firmware updates anywhere, so how do I root without a custom recovery? Can you tell me some hints to find the solution or a link? Thanks again
EDIT: Oh, just found a way, and in case someone is also wondering heres how its done: You have to boot to twrp through adb, and then you can flash super su without flashing the custom recovery . This is the generic way to do it, have not tested im my P8 yet, will report later.
Click to expand...
Click to collapse
*No need to go through all the hassle there is an automated script which i used it myself if you are still on stock recovery, it installs Twrp to flash superSu and then restores the original recovery.
http://forum.xda-developers.com/p8l...otloader-root-p8-p8lite-t3164956#post62851688
*If you are on Twrp, you can download "Huawei update extractor" http://forum.xda-developers.com/showthread.php?t=2433454 use it to extract your firmware (update.app) and take from it the 'recovery.img'. Then go to platform-tools where you open the CMD from, place the recovery.img in it you can rename it to "stockrecovery.img"
then "shift+right click" open the command line.
type: adb reboot bootloader
type: adb devices ----->to see your device
type: fastboot flash recovery 'type hear the name of recovery'
example: flastboot flash recovery stockrecovery.img
type: fastboot reboot ----->reboot device
some tutorial i found on youtube:
https://www.youtube.com/watch?v=YfWYKREeQeQ
By the way the method for Twrp i haven't tested but that's the theory, so please do it on your own risk and do the required research. Goodluck:good:
Edit: Another method in theory if you have Twrp could be to use 'flashify' app https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en to flash the stock 'recovery.img' which you extracted from the stock firmware. No need to use adb.
Rashad83 said:
*No need to go through all the hassle there is an automated script which i used it myself if you are still on stock recovery, it installs Twrp to flash superSu and then restores the original recovery.
http://forum.xda-developers.com/p8l...otloader-root-p8-p8lite-t3164956#post62851688
*If you are on Twrp, you can download "Huawei update extractor" http://forum.xda-developers.com/showthread.php?t=2433454 use it to extract your firmware (update.app) and take from it the 'recovery.img'. Then go to platform-tools where you open the CMD from, place the recovery.img in it you can rename it to "stockrecovery.img"
then "shift+right click" open the command line.
type: adb reboot bootloader
type: adb devices ----->to see your device
type: fastboot flash recovery 'type hear the name of recovery'
example: flastboot flash recovery stockrecovery.img
type: fastboot reboot ----->reboot device
some tutorial i found on youtube:
https://www.youtube.com/watch?v=YfWYKREeQeQ
By the way the method for Twrp i haven't tested but that's the theory, so please do it on your own risk and do the required research. Goodluck:good:
Edit: Another method in theory if you have Twrp could be to use 'flashify' app https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en to flash the stock 'recovery.img' which you extracted from the stock firmware. No need to use adb.
Click to expand...
Click to collapse
I still haven't changed the bootloader so it will be easier, I was waiting for the email from huawei but never received, but with the link you provided I was able to get the code instantly (since my model GRA-UL10 isn't on the list) its late here so will try it tomorrow. But I have a final question, will be possible to flash SuperSU without flashing twrp? There is a command that lets you boot twrp without flashing I just don't want to reflash my bootloader unnecessarily, thanks in advance. After this I will probably post a guide since it is not easy to find everything in one place.
fede011 said:
I still haven't changed the bootloader so it will be easier, I was waiting for the email from huawei but never received, but with the link you provided I was able to get the code instantly (since my model GRA-UL10 isn't on the list) its late here so will try it tomorrow. But I have a final question, will be possible to flash SuperSU without flashing twrp? There is a command that lets you boot twrp without flashing I just don't want to reflash my bootloader unnecessarily, thanks in advance. After this I will probably post a guide since it is not easy to find everything in one place.
Click to expand...
Click to collapse
In order to root your device you need a custom recovery which gives you the ability to push files which is not possible with the stock recovery that's how i understand it. The script in the link i gave u automates the steps you have to do manually, if you are going to root the device using the command line you will need a su.zip to flash using twrp, and a twrp recovery image through which you will access the file system, and finally knowing the command lines to do it all which is all in all is a hassle. So booting into or flashing twrp isn't really a big deal (at least for me) as long as you have the stock recovery by the end of it all.