Hi Guys,
I have been reading and trying this for two weeks now and Im lost still. Never had an issue where I just couldnt figure it out now i need to ask for some help. I have a Kindle Fire HDX 7 ITS BEEN ROOTED AND USED FOR ABOUT A YEAR NOW WITH NO ISSUES. I decided to upgraade the ROM and installed the wrong version (apollo) how I done that is becide me, anyway now Im stuck in bootloop grey kindlefire screen. I do have ADB working whoever it is in a loop state so I have to be quick to insert commands. My bootloader is locked so im limited. I also am able to get into Fastboot and it works and also verified the device is locked. I have my download size 0x20000000 and I have my manfid 0x000045 and my device serial 0xf0bf7e1d . I just cant get the img created correctly or size correct c
would someone help me with the file creating and flashing procedure in fastboot to get my device working again? Im pure crosseyed at this point and about to use the Kindle as a Target at the range lol.
Thanks to anyone that can help
Which Fire OS version is on your HDX? The wrong Apollo version? Note that bootloader unlock is possible from 3.1.0 to 3.2.3.2 only.
The bootloader unlock procedure ist described here (might require these drivers). Note that you have to install the software mentioned, download the script and use it with your ID and serial to create the .unlock file.
Cl4ncy said:
Which Fire OS version is on your HDX? The wrong Apollo version? Note that bootloader unlock is possible from 3.1.0 to 3.2.3.2 only.
The bootloader unlock procedure ist described here (might require these drivers). Note that you have to install the software mentioned, download the script and use it with your ID and serial to create the .unlock file.
Click to expand...
Click to collapse
is there a commant in ADB or Fastboot that will tell me the OS Version?
iv got the product THOR
getvar version 0.5
Kernal 1K
getvar production 1
getvar serialno D0FBA0A03464QM7Q
GETVAR MAX DOWNLOAD 0X20000000
bowman1966 said:
is there a commant in ADB or Fastboot that will tell me the OS Version?
iv got the product THOR
getvar version 0.5
Kernal 1K
getvar production 1
getvar serialno D0FBA0A03464QM7Q
GETVAR MAX DOWNLOAD 0X20000000
Click to expand...
Click to collapse
I don't know, I'd hoped you'd still have the Apollo update file you flashed - it should have the version number right there in its file name.
Cl4ncy said:
I don't know, I'd hoped you'd still have the Apollo update file you flashed - it should have the version number right there in its file name.
Click to expand...
Click to collapse
ill check for the file but my issue now is the steps in Python27 for creating a file , i created but wrong size wrong number that kind of issue. Was hoping I could get someone to do a step by step in order using the cuberHDX.py
bowman1966 said:
ill check for the file but my issue now is the steps in Python27 for creating a file , i created but wrong size wrong number that kind of issue. Was hoping I could get someone to do a step by step in order using the cuberHDX.py
Click to expand...
Click to collapse
Well, if you don't have 3.1.0 - 3.2.3.2 it doesn't make any sense anyway, but ...
it's easier than you think.
You open a DOS box, change dir to your ADB directory (enter cd\adb) then enter the following commands:
adb shell
cat /sys/block/mmcblk0/device/manfid
cat /sys/block/mmcblk0/device/serial
then open another DOS box, change dir to your Python Directory with the .py script (enter cd\python27 or whatever the path of your Python directory is), then
python.exe cuberHDX.py 0xmmssssssss
with mm being the last two digits of your ID, and the ssssssss being your serial, the script should create the .unlock file then.
So assuming the numbers you mentioned are correct the python command would be
python.exe cuberHDX.py 0x45f0bf7e1d
Copy/move the .unlock file to your ADB directory then, open another DOS box for the adb reboot-bootloader command, and yet another DOS box for the fastboot commands (change dir cd\adb both times before you enter the adb & fastboot commands):
fastboot -i 0x1949 devices
fastboot -i 0x1949 flash unlock 0xmmssssssss.unlock
fastboot -i 0x1949 reboot
Cl4ncy said:
Well, if you don't have 3.1.0 - 3.2.3.2 it doesn't make any sense anyway, but ...
it's easier than you think.
You open a DOS box, change dir to your ADB directory (enter cd\adb) then enter the following commands:
adb shell
cat /sys/block/mmcblk0/device/manfid
cat /sys/block/mmcblk0/device/serial
then open another DOS box, change dir to your Python Directory with the .py script (enter cd\python27 or whatever the path of your Python directory is), then
python.exe cuberHDX.py 0xmmssssssss
with mm being the last two digits of your ID, and the ssssssss being your serial, the script should create the .unlock file then.
So assuming the numbers you mentioned are correct the python command would be
python.exe cuberHDX.py 0x45f0bf7e1d
Copy/move the .unlock file to your ADB directory then, open another DOS box for the adb reboot-bootloader command, and yet another DOS box for the fastboot commands (change dir cd\adb both times before you enter the adb & fastboot commands).
Click to expand...
Click to collapse
thanks for the help, Well I guess I have been doing this correctly the whole time. Still getting Unload code not correct in fastboot, so apparently I have the noncapadible bootloader.
is there anything I can do with it besides taking it to the range for target practice?
bowman1966 said:
thanks for the help, Well I guess I have been doing this correctly the whole time. Still getting Unload code not correct in fastboot, so apparently I have the noncapadible bootloader.
is there anything I can do with it besides taking it to the range for target practice?
Click to expand...
Click to collapse
Difficult to say, but it doesn't look good.
Did you figure out which Apollo update you flashed? Did you have Safestrap installed (probably not)?
Cl4ncy said:
Difficult to say, but it doesn't look good.
Did you figure out which Apollo update you flashed? Did you have Safestrap installed (probably not)?
Click to expand...
Click to collapse
apollo-nexus-rom-v2.0.5.zip yep the apollo version and it clearly says not to install with safstrap its a target now i just hate the fact that I have access to the bootloader but cant do anything with it
bowman1966 said:
apollo-nexus-rom-v2.0.5.zip yep the apollo version and it clearly says not to install with safstrap its a target now i just hate the fact that I have access to the bootloader but cant do anything with it
Click to expand...
Click to collapse
¡Ay caramba!
It says not for Safestrap, because it says "This is for users with TWRP installed." in the introduction. Do you have TWRP installed? That would help of course. How did you flash the Apollo ROM anyway?
Cl4ncy said:
¡Ay caramba!
It says not for Safestrap, because it says "This is for users with TWRP installed." in the introduction. Do you have TWRP installed? That would help of course. How did you flash the Apollo ROM anyway?
Click to expand...
Click to collapse
yes I do have TWRP installed,I used it to install the zip file
bowman1966 said:
yes I do have TWRP installed,I used it to install the zip file
Click to expand...
Click to collapse
Then start TWRP (press and hold Volume up and Power On, release when the Kindle Fire logo appears on the screen), connect the HDX to your PC, download the Thor ROM, copy it to the HDX, and flash it in TWRP.
Kinda weird though you can not unlock the bootloader. You sure you have the real TWRP installed?
Cl4ncy said:
Then start TWRP (press and hold Volume up and Power On, release when the Kindle Fire logo appears on the screen), connect the HDX to your PC, download the Thor ROM, copy it to the HDX, and flash it in TWRP.
Kinda weird though you can not unlock the bootloader. You sure you have the real TWRP installed?
Click to expand...
Click to collapse
I sure wish I could start TWRP ,the unit is in a bootloot grey kindle fire screen.Just reboots
bowman1966 said:
I sure wish I could start TWRP ,the unit is in a bootloot grey kindle fire screen.Just reboots
Click to expand...
Click to collapse
Tried to re-flash TWRP via adb? Dunno if flashing Apollo Nexus ROM could destroy TWRP. Do you know which Fire OS you were running when you installed TWRP, and before you flashed the Apollo Nexus ROM?
Cl4ncy said:
Tried to re-flash TWRP via adb? Dunno if flashing Apollo Nexus ROM could destroy TWRP. Do you know which Fire OS you were running when you installed TWRP, and before you flashed the Apollo Nexus ROM?
Click to expand...
Click to collapse
Man its been about a year or so since I rooted , I know I had to roll the update back before I could load the twrp rom.etc. I think it was the first Nex rom that was stable with kdx7
Cl4ncy said:
¡Ay caramba!
It says not for Safestrap, because it says "This is for users with TWRP installed." in the introduction. Do you have TWRP installed? That would help of course. How did you flash the Apollo ROM anyway?
Click to expand...
Click to collapse
thats right I did have TWRP , I used it to install the file.
remote unlock code is not correct, would that mean my bootloader is updated and not repairable at this time? my date size is 0x20000000 i keep sending 536870912 to it, this is the problem correct?
When i create the unlock .img file and flash the device goes through the motion of loading but fails saying the the unlock code is not correct. The file size is 536870912 and the kindle fastboot says its 0x20000000. Is this the problem? Am I using the wrong cuberHDX file or what any help would be greatly appreciated.
bowman1966 said:
When i create the unlock .img file and flash the device goes through the motion of loading but fails saying the the unlock code is not correct. The file size is 536870912 and the kindle fastboot says its 0x20000000. Is this the problem? Am I using the wrong cuberHDX file or what any help would be greatly appreciated.
Click to expand...
Click to collapse
What do you mean the file size is 536870912? The file size of the .unlock file should be 256 bytes.
Did you install all software mentioned in the unlock thread, i.e. Python 2.7 and GMPY2 for Python 2.7?
Yes and Yes, I DID exactly like thread said and I get that file size...... 536870912 doesnt matter what T F I D....either.....I dont understand whats happening here but I guess its just my luck...... Been doing this for about 3 years now I guess Its time for me to BRICK ONE lol......................
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.
Hey everyone,
This is my first time posting to the forums. I have been trying to get everything done without having to ask questions since there are so many all over the place and I can see how it can get tiring trying to help everyone when their may be an answer out there already if you look. However, I have ran into an issue that I can't seem to find much information on. I have the HTC Rezound that is S-On (apparently you need a Linux machine to get S-Off which I don't have. Using Windows 7.) and have been using fastboot to get things done. I have unlocked the bootloader and have installed the 'Amon Ra' recovery and setup Superuser and SU. As far as I know, I have to use ROM's that are S-On friendly (right?) and I chose to try out 'EclipticRez' and later 'Talon'.
As I tried to flash the ROM's through fastboot it fails with the following errors every time and I cannot continue:
archive does not contain android-info.txt
archive does not contain android-product.txt
From what I found is that it may be a bad download of the ROM. Maybe.... But it happened consecutively with two different ROM downloads.
I also read that maybe the recovery wasn't setup, which as far as I know it is. Should I use a different recovery? Everyone usually references to using CWM, which I wouldn't mind using but I couldn't figure out how to get SU access.
Can I just create the files myself? They are only txt files after all.
If anyone can help me with this I will be so grateful! I'm pretty new to this and it has definitely been a fun learning experience for me
Much thanks in advance!
Strikerz87 said:
Hey everyone,
This is my first time posting to the forums. I have been trying to get everything done without having to ask questions since there are so many all over the place and I can see how it can get tiring trying to help everyone when their may be an answer out there already if you look. However, I have ran into an issue that I can't seem to find much information on. I have the HTC Rezound that is S-On (apparently you need a Linux machine to get S-Off which I don't have. Using Windows 7.) and have been using fastboot to get things done. I have unlocked the bootloader and have installed the 'Amon Ra' recovery and setup Superuser and SU. As far as I know, I have to use ROM's that are S-On friendly (right?) and I chose to try out 'EclipticRez' and later 'Talon'.
As I tried to flash the ROM's through fastboot it fails with the following errors every time and I cannot continue:
archive does not contain android-info.txt
archive does not contain android-product.txt
From what I found is that it may be a bad download of the ROM. Maybe.... But it happened consecutively with two different ROM downloads.
I also read that maybe the recovery wasn't setup, which as far as I know it is. Should I use a different recovery? Everyone usually references to using CWM, which I wouldn't mind using but I couldn't figure out how to get SU access.
Can I just create the files myself? They are only txt files after all.
If anyone can help me with this I will be so grateful! I'm pretty new to this and it has definitely been a fun learning experience for me
Much thanks in advance!
Click to expand...
Click to collapse
1) Switch to TWRP or CWM for your recovery.
2) You install the rom zip via recovery.
3) You then need to fastboot flash the kernel from the rom zip you downloaded. You don't install the whole rom via fastboot.
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom. Using these steps, you can install any rom you want.
Strikerz87 said:
Hey everyone,
This is my first time posting to the forums. I have been trying to get everything done without having to ask questions since there are so many all over the place and I can see how it can get tiring trying to help everyone when their may be an answer out there already if you look. However, I have ran into an issue that I can't seem to find much information on. I have the HTC Rezound that is S-On (apparently you need a Linux machine to get S-Off which I don't have. Using Windows 7.) and have been using fastboot to get things done. I have unlocked the bootloader and have installed the 'Amon Ra' recovery and setup Superuser and SU. As far as I know, I have to use ROM's that are S-On friendly (right?) and I chose to try out 'EclipticRez' and later 'Talon'.
As I tried to flash the ROM's through fastboot it fails with the following errors every time and I cannot continue:
archive does not contain android-info.txt
archive does not contain android-product.txt
From what I found is that it may be a bad download of the ROM. Maybe.... But it happened consecutively with two different ROM downloads.
I also read that maybe the recovery wasn't setup, which as far as I know it is. Should I use a different recovery? Everyone usually references to using CWM, which I wouldn't mind using but I couldn't figure out how to get SU access.
Can I just create the files myself? They are only txt files after all.
If anyone can help me with this I will be so grateful! I'm pretty new to this and it has definitely been a fun learning experience for me
Much thanks in advance!
Click to expand...
Click to collapse
also to note....you dont have to install linux to get s-off....if you follow my guide you can do it straight from a live disk rather than installing it....so it wont erase or mess up your windows partition at all
Solved!
Thank you, Mjones, I finally got it! I knew it was much easier than I was making it out to be. I was missing the kernel! Yeah, a crucial part in the process, I know
I first ran CWM and flashed the ROM over and ran the .zip through recovery (which I couldn't understand at first as I could never find it in the directory) but the installer would only go 50% and would fail... makes sense why now lol
I later flashed TWRP and backed up again after recovering from the fail. I flashed over the kernel and voila! So simple... Had to slap myself.
Thanks again! Case solved.
REV3NT3CH, that is sweet!! I have been hoping there is a way to gain s-off with Windows. I have 7 at work and 8.1 (which I can't get anything to work on) at home. I actually have to focus on work today haha so I'll look into the method and try it out tomorrow if I can. Thanks for all of the help.
mjones73 said:
1) Switch to TWRP or CWM for your recovery.
2) You install the rom zip via recovery.
3) You then need to fastboot flash the kernel from the rom zip you downloaded. You don't install the whole rom via fastboot.
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom. Using these steps, you can install any rom you want.
Click to expand...
Click to collapse
Thank You So much, Mine case also Resolved. I was too frustated sice last 3 days cause my phone was in dead mode. At the end, fastboot flash boot boot.img Worked. ThankYOu
mjones73 said:
1) Switch to TWRP or CWM for your recovery.
2) You install the rom zip via recovery.
3) You then need to fastboot flash the kernel from the rom zip you downloaded. You don't install the whole rom via fastboot.
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom. Using these steps, you can install any rom you want.
Click to expand...
Click to collapse
I need to be able to do it via fastboot, as my Motorola Electrify M is stuck in a bootloop and there's no way I could find to boot into recovery. I'm using ./fastboot update name_of_update.zip and it is an official OTA .zip but I still get this error. Any suggestions?
ecols33 said:
I need to be able to do it via fastboot, as my Motorola Electrify M is stuck in a bootloop and there's no way I could find to boot into recovery. I'm using ./fastboot update name_of_update.zip and it is an official OTA .zip but I still get this error. Any suggestions?
Click to expand...
Click to collapse
Sorry, don't know anything about that phone.
ecols33 said:
I need to be able to do it via fastboot, as my Motorola Electrify M is stuck in a bootloop and there's no way I could find to boot into recovery. I'm using ./fastboot update name_of_update.zip and it is an official OTA .zip but I still get this error. Any suggestions?
Click to expand...
Click to collapse
Did you try this first? (Right from Moto's site)
Perform a factory reset using external keys
1. Power off the phone, press and hold volume down button, press power button
2. Screen will come up with "Fastboot", press Vol down key to cycle through choices until you get "Android Recovery", then press Vol up key
3. Wait for the "triangle ! / Android" screen then go on to step 4
4. Press both Vol up and Vol down key simultaneously. A menu will come up
5. Tap on Vol down key until "wipe data/factory reset" is highlighted, and tap Power key. Another Confirmation screen will come. Tap on Vol down key until coming to Yes and tap Power key
6. After userdata is cleared, the "reboot system now" option will be highlighted by Default. Tap Power key
7. Phone will reboot to initial setup screen.
PLEASE HELP! I have a Huawei P8 and I tried to update to android 6.0 (GRA-L09xxxxxxxxxxxB317 or something) Went to install it and now im stuck in bootloop (a very annoying one, I can rarely get into eRecovery and eRecovery is not able to fix my problem: "Getting package info failed") so I went into fastboot&rescue mode and I did the flash thing via my PC (that Fastboot flash boot boot.img etc.) but I get this error saying: "FAILED (remote: Command not allowed)" for any image im trying to flash. My fastboot/bootloader or whatever it's called is locked my android is unrooted and stock android. I don't know how to unlock it I can't find anything anywhere.. HELP ME
not working
hariom.gupta11 said:
Thank You So much, Mine case also Resolved. I was too frustated sice last 3 days cause my phone was in dead mode. At the end, fastboot flash boot boot.img Worked. ThankYOu
Click to expand...
Click to collapse
not working on my 4c. write successful but when reboot is completed it goes to previous state.
"the user data partition can no longer be used"
zb602kl_x00tdb
L0RDZ3RO said:
PLEASE HELP! I have a Huawei P8 and I tried to update to android 6.0 (GRA-L09xxxxxxxxxxxB317 or something) Went to install it and now im stuck in bootloop (a very annoying one, I can rarely get into eRecovery and eRecovery is not able to fix my problem: "Getting package info failed") so I went into fastboot&rescue mode and I did the flash thing via my PC (that Fastboot flash boot boot.img etc.) but I get this error saying: "FAILED (remote: Command not allowed)" for any image im trying to flash. My fastboot/bootloader or whatever it's called is locked my android is unrooted and stock android. I don't know how to unlock it I can't find anything anywhere.. HELP ME
Click to expand...
Click to collapse
I have same problem on asus zenfone max pro m1 I bought it online said used and now working
can't boot into recovery.
can't boot into system.
Only EDL Mode and Fastboot Mode, but fastboot is Locked whic I cant unlock because I cannot boot into system to toggle USB Debugging and allow OEM unlocking
Qualcomm is harder to flash than MTK that can use SP FlashTool.
on this I use QFIL but keeps "sahara error". I tried searching and try moving firmware file to bin but no Luck. I'm currently trying different version of QFIL Tool.
If it FAILS my only HOPE is to use MUT-QCfire which will Require a "SmartCardReader" Which is a bit pricey and I don't even know if it will work on my device.
Ohh.... Help please!!
I was flashing rom but I skipped a step and end does not pass the white HTC screen.
The fact is that it was installing the rom and Gapps but I miss the boot.img I have it on PC, the problem is that as the phone will not start, i can enter to bootloader but does not recognize the pc, I get the normal bootloader but how i do to pass the boot.img again if the phone does not recognize it??
And sorry for my bad english---- Help please!
rikrdoVe said:
Ohh.... Help please!!
I was flashing rom but I skipped a step and end does not pass the white HTC screen.
The fact is that it was installing the rom and Gapps but I miss the boot.img I have it on PC, the problem is that as the phone will not start, i can enter to bootloader but does not recognize the pc, I get the normal bootloader but how i do to pass the boot.img again if the phone does not recognize it??
And sorry for my bad english---- Help please!
Click to expand...
Click to collapse
If you can get into the recovery and have a valid backup then in that case restore it and restart the process. Else you can boot into fastboot and flash the desired boot.img the process will be
adb reboot-bootloader
fastboot flash boot boot.img
fastboot reboot
ethanon said:
If you can get into the recovery and have a valid backup then in that case restore it and restart the process. Else you can boot into fastboot and flash the desired boot.img the process will be
adb reboot-bootloader
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
adb reboot bootloader
ethanon said:
If you can get into the recovery and have a valid backup then in that case restore it and restart the process. Else you can boot into fastboot and flash the desired boot.img the process will be
adb reboot-bootloader
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
Sorry bro, I'm ignorant in android... To use adb i need android sdk tools? What i need?
rikrdoVe said:
Sorry bro, I'm ignorant in android... To use adb i need android sdk tools? What i need?
Click to expand...
Click to collapse
rikrdoVe said:
Sorry bro, I'm ignorant in android... To use adb i need android sdk tools? What i need?
Click to expand...
Click to collapse
Well you do need to have the Android SDK tools download but if you select the "Platform Tools" at the SDK manager , that will only install the platform tools on your hard disk. and yes the device drivers needs to installed , to work with ADB ,
Any ways this tutorial by LUCKY_THIRTEEN just might help you
http://forum.xda-developers.com/showthread.php?t=2213910
ethanon said:
Well you do need to have the Android SDK tools download but if you select the "Platform Tools" at the SDK manager , that will only install the platform tools on your hard disk. and yes the device drivers needs to installed , to work with ADB ,
Any ways this tutorial by LUCKY_THIRTEEN just might help you
http://forum.xda-developers.com/showthread.php?t=2213910
Click to expand...
Click to collapse
I cant install sdk and use adb... I resume: Dowloaded sdk from the page, and when i start sdk manager "Platform Tools" cant update i got this error: Stopping adb server succeeded. Failed to rename directory C:\adt.bundle.windows-x86-20131030\sdk\platform-tools to C:\adt.bundle.windows-x86-20131030\sdk\temp\PlatformToolPackage.old01. Nothing was installed"
I dont know if sdk was installed or what. only have the folder in C:
I put the boot.img file in platform-tools and tried to flash the image using the command fastboot flash boot boot.img but tells me the boot.img arrchivo not be found.
The phone does not recognize the pc, the bootloader is relocked.
Thanks for your support bro, I would like resolve this as soon as possible.
rikrdoVe said:
I cant install sdk and use adb... I resume: Dowloaded sdk from the page, and when i start sdk manager "Platform Tools" cant update i got this error: Stopping adb server succeeded. Failed to rename directory C:\adt.bundle.windows-x86-20131030\sdk\platform-tools to C:\adt.bundle.windows-x86-20131030\sdk\temp\PlatformToolPackage.old01. Nothing was installed"
I dont know if sdk was installed or what. only have the folder in C:
I put the boot.img file in platform-tools and tried to flash the image using the command fastboot flash boot boot.img but tells me the boot.img arrchivo not be found.
The phone does not recognize the pc, the bootloader is relocked.
Thanks for your support bro, I would like resolve this as soon as possible.
Click to expand...
Click to collapse
Well it seems you have installed the Android SDK all right. and make sure you put the file in the platform tools folder, and also make sure you have installed the HTC drivers for your PC to detect your phone , you can also try uninstall the driver and re install
ethanon said:
Well it seems you have installed the Android SDK all right. and make sure you put the file in the platform tools folder, and also make sure you have installed the HTC drivers for your PC to detect your phone , you can also try uninstall the driver and re install
Click to expand...
Click to collapse
Ok, i updated Platform-Tools to rev. 19.0.1, I had to start windows in safe mode.
But, yestarday Android sdk tools appeared in the list of installed programs in windows, i uninstalled and install today again but now i dont see sdk in list. Anyway, i open cdm and type "adb reboot-bootloader" and it says "error: device not found".
Then y type: fastboot flash boot boot.img and it says "error: cannot load boot.img"
I put the boot.img in C:\adt-bundle-windows-x86-20131030\sdk\platform-tools
And now... I dont know what to do
rikrdoVe said:
Ok, i updated Platform-Tools to rev. 19.0.1, I had to start windows in safe mode.
But, yestarday Android sdk tools appeared in the list of installed programs in windows, i uninstalled and install today again but now i dont see sdk in list. Anyway, i open cdm and type "adb reboot-bootloader" and it says "error: device not found".
Then y type: fastboot flash boot boot.img and it says "error: cannot load boot.img"
I put the boot.img in C:\adt-bundle-windows-x86-20131030\sdk\platform-tools
And now... I dont know what to do
Click to expand...
Click to collapse
Install the windows drivers , better try installing the the HTC sync manager. that way your device will be detected.
ethanon said:
Install the windows drivers , better try installing the the HTC sync manager. that way your device will be detected.
Click to expand...
Click to collapse
Ready, installed the HTC Sync Manager, and same result. "Device not Found"
if only I could get the phone to be recognized by the pc, I think it could solve the problem.
rikrdoVe said:
Ready, installed the HTC Sync Manager, and same result. "Device not Found"
if only I could get the phone to be recognized by the pc, I think it could solve the problem.
Click to expand...
Click to collapse
From where are u trying the commands.............
u must put ur phone in recovery mode.......
Connect ur phone to PC......
from the platform-tools folder try "adb devices"........
The adb commands will work in recovery only........
in bootloader the fastboot commands will work..........
[email protected] said:
From where are u trying the commands.............
u must put ur phone in recovery mode.......
Connect ur phone to PC......
from the platform-tools folder try "adb devices"........
The adb commands will work in recovery only........
in bootloader the fastboot commands will work..........
Click to expand...
Click to collapse
The phone is not recognized by the pc.
I can not get into recovery because the bootloader is relocked. I can only enter fastboot, but when executing commands, either with adb, All in One Toolkit, Flasher Venom or the phone is not recognized "Error: Device not found"
I have the drivers installed, htc sync manager, and I'm afraid that this phone unusable ... Also I did have a backup but on PC, but if the phone is not recognized I can not run any command ...
Also, I was trying to run teh Stock RUU:
RUU_ENRC2B_U_JB_45_HTC_Europe_1.17.401.1_Radio_3.1204.168.32_release_299688_signed
But When I run the. Exe signature throws an error (132) "find the correct signature and try again" and which is not correct. had sense 5 and 4.2.2 HTC One X + International.
Help please ... : (
same issue, cannot access recovery fastboot only
I hope this adds to this post if I miss speak I apologize in advance but I do not have the time or knowledge to post 10 times before strating my own thread so if this doesn't add value to this post, I have been reading and researching all week and now that I cannot use my phone I must intensely focus on this until it is fixed
Fed up with 4.3 and lower limitations and looking to get my monies worth on my phone, I look to upgrade to 4.3.1 or higher just started this week so I am a total newb, and if it means anything to anyone I would be happy to donate to contributors via papal once a solution is found I am a working professional and I am happy to pay you to save my time/phone
with that said here is what I have done
HTC One X+ (AT&T US) Quad Core Tegra 3
OTA upgraded 4.2.2 Android Firmware 2.15
Unlocked BL via HTCDev
Was using;
Recovery-clockwork-6.0.3.7-enrc2b.img
With intent to upgrade to 4.3.1
Used the following Rom and GAPPS to load .zips via CWM
cm-10.2.1-enrc2b (stable)
gapps-jb-20130813-signed.zip
Did not work
Tried more recent gapps
Did not work got stuck on Circling Cyanogenmod screen
//goo.gl/YzZ75o
THEN
I realized I was not flashing boot.img taken from the CM 10.2.1 zip so I followed directions to use the boot.img then load the zip files, since doing this I can no longer use my recovery
Erase Cache (from fastboot)
COMMANDs:
./fastboot erase cache
./fastboot reboot-bootloader
Results:
White HTC “Quietly Brilliant” Screen for a few seconds then turns off
Plug in charger and Red light turns on grey empty battery symbol appears with a lightning bolt inside then disappears
red light turns off :-/
//goo.gl/JrBJph
Current state: I can fastboot, but I cannot load recovery
//goo.gl/43F6XT
Also, if I can get back into recovery
The last time I was in it, last night I believe I reformatted my internal SD, because when I was looking for my backup, and my zips they were all gone...I was very tired and should haven't pushed it.
I don't care about loss of data I just need to get my phone working again, thanks for your time and careful considerations
UPDATE+++
Used WinDroid HTC One X+ Toolkit 3 to flash custom recovery CWM 6.0.3.7 back in recovery again, now I think I need to side load a ROM because I deleted what I had internally
cclifford81 said:
I hope this adds to this post if I miss speak I apologize in advance but I do not have the time or knowledge to post 10 times before strating my own thread so if this doesn't add value to this post, I have been reading and researching all week and now that I cannot use my phone I must intensely focus on this until it is fixed
Fed up with 4.3 and lower limitations and looking to get my monies worth on my phone, I look to upgrade to 4.3.1 or higher just started this week so I am a total newb, and if it means anything to anyone I would be happy to donate to contributors via papal once a solution is found I am a working professional and I am happy to pay you to save my time/phone
with that said here is what I have done
HTC One X+ (AT&T US) Quad Core Tegra 3
OTA upgraded 4.2.2 Android Firmware 2.15
Unlocked BL via HTCDev
Was using;
Recovery-clockwork-6.0.3.7-enrc2b.img
With intent to upgrade to 4.3.1
Used the following Rom and GAPPS to load .zips via CWM
cm-10.2.1-enrc2b (stable)
gapps-jb-20130813-signed.zip
Did not work
Tried more recent gapps
Did not work got stuck on Circling Cyanogenmod screen
//goo.gl/YzZ75o
THEN
I realized I was not flashing boot.img taken from the CM 10.2.1 zip so I followed directions to use the boot.img then load the zip files, since doing this I can no longer use my recovery
Erase Cache (from fastboot)
COMMANDs:
./fastboot erase cache
./fastboot reboot-bootloader
Results:
White HTC “Quietly Brilliant” Screen for a few seconds then turns off
Plug in charger and Red light turns on grey empty battery symbol appears with a lightning bolt inside then disappears
red light turns off :-/
//goo.gl/JrBJph
Current state: I can fastboot, but I cannot load recovery
//goo.gl/43F6XT
Also, if I can get back into recovery
The last time I was in it, last night I believe I reformatted my internal SD, because when I was looking for my backup, and my zips they were all gone...I was very tired and should haven't pushed it.
I don't care about loss of data I just need to get my phone working again, thanks for your time and careful considerations
Click to expand...
Click to collapse
ummm your flashing the X+ International CM rom and not the evitareul one, reboot into the bootloader and then enter recovery from there.
Lloir said:
ummm your flashing the X+ International CM rom and not the evitareul one, reboot into the bootloader and then enter recovery from there.
Click to expand...
Click to collapse
Will do, thanks!
evitareul? Does that mean Flash TWRP recovery and then use evita ROM?
cclifford81 said:
Will do, thanks!
evitareul? Does that mean Flash TWRP recovery and then use evita ROM?
Click to expand...
Click to collapse
Evitareul = X+ AT&T
Sent from my Nexus 5 using Tapatalk
Lloir said:
Evitareul = X+ AT&T
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Ok so I just need the evitareul Rom, I'm looking for it now, I just need something stable at 4.3 or higher with GAPPS anyone have any links
cclifford81 said:
Ok so I just need the evitareul Rom, I'm looking for it now, I just need something stable at 4.3 or higher with GAPPS anyone have any links
Click to expand...
Click to collapse
look in original development
Lloir said:
look in original development
Click to expand...
Click to collapse
Ok, from what I can tell I think I have to go with this?
[ROM][2/18/2014][AT&T X+ S5 eXtreme V1.0.3.3]
I will be very happy if I can get this to work, and I will just "stay tuned" for when I can flash a stable 4.3 or higher for my phone
Under downloads I see the following: (would post picture but still too n00b)
S6 eXtreme RC1
S5 RC2 Patch
Native WiFi
Hotspot Patch
S5 eXtreme
V1.0.3.2
S5 eXtreme
V1.0.3.3
I am not sure what to download here, I will continue reading these directions as I believe this is my best option, please confirm if I am on the right path, thanks guys!
Update+++
Downloaded S5_eXtreme_V1.0.3.3_Signed.zip
about to flash this ROM, is GAPPS included in this?
Update+++
Downloaded S5_eXtreme_V1.0.3.3_Signed.zip Rom
Extracted the boot.img file and followed instructions
Extract boot.img from zip file and place in your sdk platform tools folder, (or wherever your adb tools are located)reboot device to bootloader and connect it to your PC.
From a command prompt type:
1. fastboot flash boot boot.img
2. fastboot erase cache
reboot to recovery and flash ROM.
but I am not sure how I flashed the ROM, I tried sideloading from recovery with WinDroid HTC One X+ Toolkit, before and after and it said no package loaded
Then I tried to load from fastboot, finally I figured "well I might as well reboot" and amazingly enough it booted...not sure what exactly but I am back on 4.2.2 so thank you!
Hi,
this is a small tutorial to show you how to flash the recovery, also eRecovery, via command line / adb shell within Android.
Flashify and other apps never worked for me, so I used commands to flash it without the need of fastboot.
It's a small tutorial for those who never worked with commands like this.
Please notify me if something went wrong or if you found any other issues.
I wanted to make a small script but I stopped it because of the lack of available commands in Android.
DISCLAIMER:
Read this tutorial first.
Never flash custom recovery to eRecovery.
Never flash recoveries from different devices.
Don't try to flash other partitions with this commands if you don't want to risk a brick.
Requirements:
- Oreo / EMUI 8 installed, Nougat hast other partition names. Pie isn't supported by me until final release.
- working root access
- terminal emulator app (I recommend Termius, it's easy to use and has nice features, it's free to use)
> or a PC, and USB cable and working ADB, also USB Debugging enabled in developer settings
- recovery img files on your phone, I recommend it to put them into your user root /data/media/0/ (internal memory)
NOTE: All commands are case sensitive!
Now open your terminal app or open the adb shell.
Type following command to enable root access:
Code:
su
SuperSU will ask you for root access, grant it.
Following command is needed to figure out, which type of memory your phone has:
Code:
ls /dev/block/platform
There are two possible outputs:
If you've a device with the faster UFS memory, it's ff3b0000.ufs, if eMMC it's hi_mci.0.
From now I'll write MEMORY instead of ff3b0000.ufs or hi_mci.0.
For flashing the recovery fire up following command:
Code:
dd if=/PATH/TO/YOUR/RECOVERY.IMG of=/dev/block/platform/MEMORY/by-name/recovery_ramdisk_a
Example: dd if=/data/media/0/twrp_3.2.1.img of=/dev/block/platform/ff3b0000.ufs/by-name/recovery_ramdisk_a
The output should look like this:
Code:
65536+0 records in
65536+0 records out
33554432 bytes transferred in 0.247 secs (135847902 bytes/sec)
If not, check your command and file paths.
For flashin the eRecovery fire up following command:
Code:
dd if=/PATH/TO/YOUR/ERECOVERY.IMG of=/dev/block/platform/MEMORY/by-name/erecovery_ramdisk_a
Example: dd if=/data/media/0/ERECOVERY_RAMDI.IMG of=/dev/block/platform/ff3b0000.ufs/by-name/erecovery_ramdisk_a
IMPORTANT NOTE: DO NOT INSTALL TWRP IN THIS! Flash only stock eRecovery!
The dd command won't give you any progress output, so be a bit patient. It should be done in a few second, but don't close the terminal app or connection before you got any output.
Unix systems like Android will give an output if something went wrong, always.
I use this to flash new TWRP versions or to flash stock recovery before I update.
If you recently updated your phone, you still need to flash via fastboot, because you lost root during the update.
The dd commands also work with fastboot. Mostly you'll use "fastboot flash recovery_ramdisk", but if you need to flash eRecovery, you can use the dd command.
23. February 2019:
Pie should also work, but you have to remove the "_a" after the partition name.
Example:
dd if=/data/media/0/twrp_3.2.1.img of=/dev/block/platform/ff3b0000.ufs/by-name/recovery_ramdisk
Please report if it's working or not.
How to know the path to the recovery_ramdisk?? Is all devices the same?? I didn't get it right the 1st time .. it shows path is invalid
Sent from my VTR-L29 using Tapatalk
fr3ker said:
How to know the path to the recovery_ramdisk?? Is all devices the same?? I didn't get it right the 1st time .. it shows path is invalid
Sent from my VTR-L29 using Tapatalk
Click to expand...
Click to collapse
Should be the same on every device. Remember, case sensitive and use _ and not -.
Maybe it's different on non UFS devices, which one do you have?
Are you able to post a screenshot of your command and output?
Jannomag said:
Should be the same on every device. Remember, case sensitive and use _ and not -.
Maybe it's different on non UFS devices, which one do you have?
Are you able to post a screenshot of your command and output?
Click to expand...
Click to collapse
Maybe @fr3ker is not on Oreo? The recovery_ramdisk partition is only for Oreo. In Nougat it is just called recovery. I don't know how the Pie partitions are called.
M1chiel said:
Maybe @fr3ker is not on Oreo? The recovery_ramdisk partition is only for Oreo. In Nougat it is just called recovery. I don't know how the Pie partitions are called.
Click to expand...
Click to collapse
Also my thought, I wanted to add this to the requirements when I created this post but apparently I forgot this. Now it's added as first point.
Hi.
I have a hard bricked p10. When I connect to laptop it's says USB SER. It doesn't not turn on I can't access recovery with power + vol. I can't get into fastboot. Anyway I can access fastboot to flash kernel and erecovery?
Jannomag said:
I use this to flash new TWRP versions or to flash stock recovery before I update.
Click to expand...
Click to collapse
Is it mandatory to flash stock recovery before update? Is it applies only to ota update or ff method?
Yes, FF or OTA are using stock recovery to flash the update. With TWRP it won't work.
Updated?
@ Jannomag:
Have you checked this for Pie meanwhile?
I currently have the problem, not being able to enter fastboot with:
Code:
sudo adb reboot bootloader
Additionally, there's something I do not understand. For the dd-command for flashing, why is the input-file (if=) the file in "/dev/block/platform/..." and the output on the sd-card? Wouldn't mean flashing an img to the device, that if= on the sd (or connected PC) and of= the path to the device (phone)?
Blümchen Blau said:
@ Jannomag:
Have you checked this for Pie meanwhile?
I currently have the problem, not being able to enter fastboot with:
Code:
sudo adb reboot bootloader
Additionally, there's something I do not understand. For the dd-command for flashing, why is the input-file (if=) the file in "/dev/block/platform/..." and the output on the sd-card? Wouldn't mean flashing an img to the device, that if= on the sd (or connected PC) and of= the path to the device (phone)?
Click to expand...
Click to collapse
WTF....Why didn't I notice this terrible mistake! Thank you for reading my post completely, you're 100% correct, I'll correct this directly after I submit this post.
Huawei did also a small change at naming the recovery partition, which I'll update, too.
I had also the problem that I wasn't able to boot into fastboot by command before I fried my phone - I couldn't figure out the reason for this.
Again, thank you!
Jannomag said:
Again, thank you!
Click to expand...
Click to collapse
Your'e welcome! I did update now, but didn't need your (correct ) way to fastboot, because the method described by borgerapper did the trick for me to get into fastboot and flash the needed original recovery.
Thanks anyway!
Hi there everyone, i want to know, how can i take a backup of stock rom of my device.
Do i need to root my device before taking a backup? If not then is there any other way to take backup of Stock Rom (i.e boot.img etc) with the help of PC (here Ubuntu Linux in my case) via using ADB, Fastboot and not using custom recoveries like TWRP, Orange Fox, SHRP.
Also do i have to root my device before installing any custom recovery in it?
I am very sorry for any inconveniences, as i am a newbie please accept my apologies.
as already mentioned in other thread one can't do anything on locked bootloader, therefore backup is impossible
https://forum.xda-developers.com/t/a-question-from-a-newbie.4407343
akram0010 said:
Hi there everyone, i want to know, how can i take a backup of stock rom of my device.
Do i need to root my device before taking a backup? If not then is there any other way to take backup of Stock Rom (i.e boot.img etc) with the help of PC (here Ubuntu Linux in my case) via using ADB, Fastboot and not using custom recoveries like TWRP, Orange Fox, SHRP.
Also do i have to root my device before installing any custom recovery in it?
I am very sorry for any inconveniences, as i am a newbie please accept my apologies.
Click to expand...
Click to collapse
Assuming that the bootloader is unlocked.
aIecxs said:
as already mentioned in other thread one can't do anything on locked bootloader, therefore backup is impossible
https://forum.xda-developers.com/t/a-question-from-a-newbie.4407343
Click to expand...
Click to collapse
Sorry i forgot to mention, but still unlocking bootloader doesn't root device.
I think the question is still valid
if your bootloader is unlocked just boot into TWRP and create backup, no root required
Code:
fastboot boot recovery.img
edit: or just download MIUI according to your current properties
Code:
adb shell getprop ro.build.fingerprint
the only other method would be MTK secure boot authentification exploit
https://github.com/francescotescari/XiaoMiToolV2
https://github.com/bkerler/mtkclient
https://forum.xda-developers.com/t/mod-dev-mediatek-mtk-auth-bypass-sla-daa-utility.4232377
aIecxs said:
if your bootloader is unlocked just boot into TWRP and create backup, no root required
Code:
fastboot boot recovery.img
edit: or just download MIUI according to your current properties
Code:
adb shell getprop ro.build.fingerprint
the only other method would be MTK secure boot authentification exploit
https://github.com/francescotescari/XiaoMiToolV2
https://github.com/bkerler/mtkclient
https://forum.xda-developers.com/t/mod-dev-mediatek-mtk-auth-bypass-sla-daa-utility.4232377
Click to expand...
Click to collapse
Is root needed
aIecxs said:
if your bootloader is unlocked just boot into TWRP and create backup, no root required
Code:
fastboot boot recovery.img
edit: or just download MIUI according to your current properties
Code:
adb shell getprop ro.build.fingerprint
the only other method would be MTK secure boot authentification exploit
https://github.com/francescotescari/XiaoMiToolV2
https://github.com/bkerler/mtkclient
https://forum.xda-developers.com/t/mod-dev-mediatek-mtk-auth-bypass-sla-daa-utility.4232377
Click to expand...
Click to collapse
Can you please tell me what is this recovery.img, and where would i get it (in Fastboot rom or recovery rom).
As i said earlier i am a newbie in this field and very much confused with these terms.
no root required click on the first link above and download TWRP for your device (TWRP-3.4.2.b_lancelot.zip)
I assume you are running windows?
extract zip file and place recovery.img on your PC in platform-tools directory. connect phone in fastboot mode, install android_winusb.inf "Android Bootloader Interface" drivers and from cmd.exe check fastboot devices
if you can see device serialno you are ready to boot TWRP from fastboot with above first command.
for linux just install android-tools-fastboot
As i am using Ubuntu i installed ADB, FASTBOOT using the APT :
Code:
sudo apt install android-tools-adb android-tools-fastboot
.
Therefore i don't have the platform-tools directory.
Also I am unable to quote reply, its showing error (Oops, we broke the Matrix, someone call Neo)
yes that's right. it doesn't matter which directory files are placed. that way you installed fastboot binary is already in PATH. linux is far more easier and doesn't require additional drivers. it might require additional udev rules to make fastboot work, but you can simply by-pass with sudo fastboot for now...