Related
Where do I download it? I need it for the the ext4 roms which I've been just flashing through fastboot :/
Sent from my MB860 using XDA App
http://forum.xda-developers.com/showthread.php?t=1204500
Thx for the prompt reply!
Sent from my MB860 using XDA App
How exactly do i install this? If you guys dont mind me asking such a noobish question cause i can't seem to figure it out from the thread posted above =/ Step by step would be helpful?
TfzSCVang said:
How exactly do i install this? If you guys dont mind me asking such a noobish question cause i can't seem to figure it out from the thread posted above =/ Step by step would be helpful?
Click to expand...
Click to collapse
*face palm
How about the directions in his OP.
Sent from my MB860 using xda premium
Well, the thing is i dont know how to adb push, and thats what it seems like is happening, so what i did was i just put the zip file into my sd card and flashed it =/ but i dont know if that will work, since in the op, he had some commands to erase the previous recovery =/ which is why i was asking =]
---EDIT---
Well it seems to be working? I'll re-edit again should i encounter any problems? And yes, im a noob, please dont troll on it...
TfzSCVang said:
Well, the thing is i dont know how to adb push, and thats what it seems like is happening, so what i did was i just put the zip file into my sd card and flashed it =/ but i dont know if that will work, since in the op, he had some commands to erase the previous recovery =/ which is why i was asking =]
---EDIT---
Well it seems to be working? I'll re-edit again should i encounter any problems? And yes, im a noob, please dont troll on it...
Click to expand...
Click to collapse
You can flash roms through fastboot but you can't flash recovery through fastboot? What's the deal with that?
Sent from my MB860 using xda premium
Alcapone263 said:
You can flash roms through fastboot but you can't flash recovery through fastboot? What's the deal with that?
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Yeah, I've been trying to find a good explanation for the difference between moto-fastboot and fastboot. What exactly is the difference between the two? Are all of the 'erase' commands just as effective between the two?
Can I just drag my fastboot.exe file into the same one my moto-fastboot and adb ones are, and use it interchangeably or will I need to copy other files as well?
Moto-fastboot and fastboot are basically the same, moto-fastboot allows for bigger file chunks(something like that)and is made for the motorola phones. Just use the same commands as you would for fastboot but use mot-fastboot instead.
Hope this helps.
bamastang said:
Moto-fastboot and fastboot are basically the same, moto-fastboot allows for bigger file chunks(something like that)and is made for the motorola phones. Just use the same commands as you would for fastboot but use mot-fastboot instead.
Hope this helps.
Click to expand...
Click to collapse
Thanks.
Out of the two I've only used moto-fastboot to install a deodexed system.img. I've done everything else through CWM. I've noticed the moto version seems to be required with certain type of flashes (i.e. recovery,system).
I had to reflash my first backup yesterday and ended up using moto-fastboot for all the erase commands. I just wanted to make sure I was using the correct program to get the cleanest recovery.
ghost_og said:
Thanks.
Out of the two I've only used moto-fastboot to install a deodexed system.img. I've done everything else through CWM. I've noticed the moto version seems to be required with certain type of flashes (i.e. recovery,system).
I had to reflash my first backup yesterday and ended up using moto-fastboot for all the erase commands. I just wanted to make sure I was using the correct program to get the cleanest recovery.
Click to expand...
Click to collapse
weird, i use normal fastboot and have yet to have a problem flashing any file; recovery and system images included.
Hi I tried to flash recovery with romracer's . I got these instructions:Copy the recovery image to a convenient location on your computer, preferably with a short path. We will be placing it on the C Drive directly (not in any folder) and using that in the next steps.
Note: The recovery image should have .img extension. If it is in a zip file, extract the .img file from it.
But I can't even extract the zip file with the .img file to C because it says Error:internal error processing iso image.
I am a noobie. Could you guys give me a hand??
Thanks!
kncha said:
Hi I tried to flash recovery with romracer's . I got these instructions:Copy the recovery image to a convenient location on your computer, preferably with a short path. We will be placing it on the C Drive directly (not in any folder) and using that in the next steps.
Note: The recovery image should have .img extension. If it is in a zip file, extract the .img file from it.
But I can't even extract the zip file with the .img file to C because it says Error:internal error processing iso image.
I am a noobie. Could you guys give me a hand??
Thanks!
Click to expand...
Click to collapse
This is what is did I downloaded automatic bootloader unlock from here http://forum.xda-developers.com/showthread.php?t=1182871, unzip it, you will find img file named recovery-en-goapk-0630-1029 replace it with romracer recovery you downloaded and rename the romracer recovery as recovery-en-goapk-0630-1029. Just to be safe even replace the recovery-clockwork-4.0.1.4-olympus with rom racer recovery and rename it as recovery-clockwork-4.0.1.4-olympus. Open main and select option 2 and follow the instructions.It worked for me
First of all thanks!
I did what you told me chose option #2 but when I got into the next #5 "now release vol down and press vol down until ...... it showed the exclamation sign with the lil android. Did I do something wrong?
kncha said:
First of all thanks!
I did what you told me chose option #2 but when I got into the next #5 "now release vol down and press vol down until ...... it showed the exclamation sign with the lil android. Did I do something wrong?
Click to expand...
Click to collapse
what was the error you got, just to be sure download the romracer recovery again it may be a bad download.You just have to switch off the phone switch off the phone holding volume down until you see fastboot then connect it to pc open main and select option 2. It will ask you to do the stuff i just said, press enter it will show device serial number and then again enter and it will write the recovery image and will ask for reboot, hold the volume down button until it shows fastboot disconnect the cable then keep pressing vol down till you get android recovery press vol up to select and that's it you get the recovery.
Edit: Are you rooted and have an unlocked bootloader.
Hi, I recently purchased an HTC ONE Carrier unlocked AT&T and this is my first ever android phone. I wanted to get rid of the bloatware so by online guides i rooted the phone somehow but i want to unroot it again since its getting too technical for me to handle the weird updates for this SuperSU thing it restarts my phone when i try to update it. I want to unroot the device by any means and bring it to stock, i donot have the stock firmware with me which is 1.26.502.10, it seems there is also something called the modelid and cid which have to match, i donot even know how to flash things or what does it even mean. Can someone please respond with a highly detailed unrooting process for my phone as its just been a week since i bought this phone and im regretting messing with it. Would be a huge favor to me thanks.
hasnain89 said:
Hi, I recently purchased an HTC ONE Carrier unlocked AT&T and this is my first ever android phone. I wanted to get rid of the bloatware so by online guides i rooted the phone somehow but i want to unroot it again since its getting too technical for me to handle the weird updates for this SuperSU thing it restarts my phone when i try to update it. I want to unroot the device by any means and bring it to stock, i donot have the stock firmware with me which is 1.26.502.10, it seems there is also something called the modelid and cid which have to match, i donot even know how to flash things or what does it even mean. Can someone please respond with a highly detailed unrooting process for my phone as its just been a week since i bought this phone and im regretting messing with it. Would be a huge favor to me thanks.
Click to expand...
Click to collapse
just uninstall SuperSU
click SuperSU in the app drawer
it opens choose settings / uncheck enable superuser
then scroll down to cleanup and choose Full unroot
thats all their is to it
clsA said:
just uninstall SuperSU
click SuperSU in the app drawer
it opens choose settings / uncheck enable superuser
then scroll down to cleanup and choose Full unroot
thats all their is to it
Click to expand...
Click to collapse
When i select SuperSU it gives me a message saying " The SU Binary Needs to be updated.Continue? " Hence i cannot access the settings, i will await your response on this and then proceed with the uninstallation. P.S this would only remove SuperSU how do i get to relock my device? BTW Thank you very much for the response, would be glad to receive further help from you mate.
hasnain89 said:
When i select SuperSU it gives me a message saying " The SU Binary Needs to be updated.Continue? " Hence i cannot access the settings, i will await your response on this and then proceed with the uninstallation. P.S this would only remove SuperSU how do i get to relock my device? BTW Thank you very much for the response, would be glad to receive further help from you mate.
Click to expand...
Click to collapse
I tried uninstalling the SuperSU from the app drawer but the uninstall icon is greyed out, also when i try to open the app it says The SU binary needs an update, if i select normal update it restarts my phone and if i select twrp it takes me to the bootlogger mode from where i have no clue what to do, please help.
hasnain89 said:
When i select SuperSU it gives me a message saying " The SU Binary Needs to be updated.Continue? " Hence i cannot access the settings, i will await your response on this and then proceed with the uninstallation. P.S this would only remove SuperSU how do i get to relock my device? BTW Thank you very much for the response, would be glad to receive further help from you mate.
Click to expand...
Click to collapse
Humm.. well I'm not able to reproduce the error so I'm kinda at a loss here..
do you know how to flash the superSU from recovery ?
this is the newest one here >> http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
put that zip file in your sdcard and install(flash) it from recovery
clsA said:
Humm.. well I'm not able to reproduce the error so I'm kinda at a loss here..
do you know how to flash the superSU from recovery ?
this is the newest one here >>
put that zip file in your sdcard and install(flash) it from recovery
Click to expand...
Click to collapse
Ok i got to the settings of SuperSU, when in select uninstall it gives me an error saying uninstall failed, i select complete unroot the device restarted with the SuperSU still being there. Now with the url you shared what exactly do i have to do after copying into my sd card and what about the current SuperSU that i still have wont it somehow conflict?
hasnain89 said:
Ok i got to the settings of SuperSU, when in select uninstall it gives me an error saying uninstall failed, i select complete unroot the device restarted with the SuperSU still being there. Now with the url you shared what exactly do i have to do after copying into my sd card and what about the current SuperSU that i still have wont it somehow conflict?
Click to expand...
Click to collapse
Copy to your sdcard
reboot phone holding vol down to enter recovery
install
choose the zip you downloaded
that should overwrite you old version and fix the problem of not being able to uninstall
clsA said:
Copy to your sdcard
reboot phone holding vol down to enter recovery
install
choose the zip you downloaded
that should overwrite you old version and fix the problem of not being able to uninstall
Click to expand...
Click to collapse
Installed the version you gave, tried uninstalling the supersu, the icon got removed but upon restart it still comes back and when i again try uninstalling , it says uninstall failed.
hasnain89 said:
Installed the version you gave, tried uninstalling the supersu, the icon got removed but upon restart it still comes back and when i again try uninstalling , it says uninstall failed.
Click to expand...
Click to collapse
well your only other option that i know of is to run a full Retail Update Utility (RUU)
from the bootloader what is your hboot version and firmware version ?
Edit I re-read your first post .. if you are on 502.10
you can run this RUU to get you phone back to stock
http://www.androidfilehost.com/?fid=22964708692722204
I assume you have fastboot on your pc and know how to use a command prompt?
you need to relock your bootloader to run the RUU
the commands are
Fastboot oem lock
then the RUU will run and completely wipe your phone
clsA said:
well your only other option that i know of is to run a full Retail Update Utility (RUU)
from the bootloader what is your hboot version and firmware version ?
Click to expand...
Click to collapse
How do i find the hboot version? The firmware version is HTCOne 32GB ATT-1.26.502.10
I donot have any backups of the original firmware RUU, where do i get it from.
hasnain89 said:
How do i find the hboot version? The firmware version is HTCOne 32GB ATT-1.26.502.10
I donot have any backups of the original firmware RUU, where do i get it from.
Click to expand...
Click to collapse
I edited my post look up
clsA said:
well your only other option that i know of is to run a full Retail Update Utility (RUU)
from the bootloader what is your hboot version and firmware version ?
Edit I re-read your first post .. if you are on 502.10
you can run this RUU to get you phone back to stock
I assume you have fastboot on your pc and know how to use a command prompt?
you need to relock your bootloader to run the RUU
the commands are
Fastboot oem lock
then the RUU will run and completely wipe your phone
Click to expand...
Click to collapse
Ok Great! Thanks for the RUU file, now just one more question, once i download the RUU file what do i do with it, i'll run the command of fastboot oem lock but the ruu file needs to be on the sd right?
I assume the fastboot oem lock command will relock the device but after that how to install the RUU
hasnain89 said:
Ok Great! Thanks for the RUU file, now just one more question, once i download the RUU file what do i do with it, i'll run the command of fastboot oem lock but the ruu file needs to be on the sd right?
I assume the fastboot oem lock command will relock the device but after that how to install the RUU
Click to expand...
Click to collapse
The RUU an exe file you run from your PC with the phone plugged in
it doesn't go on the sdcard
clsA said:
The RUU an exe file you run from your PC with the phone plugged in
it doesn't go on the sdcard
Click to expand...
Click to collapse
I know im being a pain in the butt but i greatly appreciate your help man thanks alot, but im using a mac and exe files dont execute on a mac osx so maybe a url to the zip file might make things a bit easier and if you can link me to it that would be great along with what do i do with the zip file. By the way do you need any more device info to make sure you get the correct RUU for my device cuz i really dont want my device to be bricked :/
Thanks alot CHEERS!
hasnain89 said:
I know im being a pain in the butt but i greatly appreciate your help man thanks alot, but im using a mac and exe files dont execute on a mac osx so maybe a url to the zip file might make things a bit easier and if you can link me to it that would be great along with what do i do with the zip file. By the way do you need any more device info to make sure you get the correct RUU for my device cuz i really dont want my device to be bricked :/
Thanks alot CHEERS!
Click to expand...
Click to collapse
Rom.zip >> https://mega.co.nz/#!yNQlFJKb!aTXDHQRG0mcv3htWOHjnYxpExjB5dT7HdkuNxCtSVyo
here are some directions to flash "rom.zip":
Quote:
if youre working with a booted,operational phone,you can flsh the file in the following manner:
-open a cmd window
-change to adb/fastboot directory
cd c:\foldername
-place the zip file you want to flash into adb/fastboot directory
-enable usb debug,disable fastboot,plug in phone
-check for connectivity
adb devices (should return serial number)
-boot to fastboot
adb reboot bootloader
-check for connectivity again
fastboot devices
-flash the file
fastboot erase cache
fastboto oem rebootRUU (will put you in ruu mode,black screen silver htc letters)
fastboot flash zip zipfilename.zip (will send and flash the file. dont interupt it while the cmd window shows its writinging,and the green status bar is moving on the phone screen)
*sometimes a file will fail with a pre-update error. this is normal,just enter again:
fastboot flash zip zipfilename.zip
and this time it will finish
-when you get "finished" and "OK"
fastboot reboot-bootloader (takes you back to fastboot)
-reboot back to the OS
fastbooot reboot
you can use this if you dont have an operational phone as well. you just need to manually put the phone in fastboot(select from hboot menu) then skip the "adb" commands and start with fastboot devices
to answer your other question,yes,you will need to re-unlock and re-install recovery after running the RUU. an ruu is designed as an "unroot" solution, or emergency fix,if other attempts have not made the phone operational.
Click to expand...
Click to collapse
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.
Hello everyone. I have a T-Mobile HTC One M7. I had Viper One installed on it and then decided to restore it to stock, and ship it to my lill bro in Europe. I accidentally wiped the whole system on the phone. Now it shows:
***Tampered***
***Relocked***
***Security Warning***
and I can only get into the bootloader and recovery modes. I am a noob when it comes to this. PLease help me put a stock system on my phone!!
Thank you much!!!
Shtehla said:
Hello everyone. I have a T-Mobile HTC One M7. I had Viper One installed on it and then decided to restore it to stock, and ship it to my lill bro in Europe. I accidentally wiped the whole system on the phone. Now it shows:
***Tampered***
***Relocked***
***Security Warning***
and I can only get into the bootloader and recovery modes. I am a noob when it comes to this. PLease help me put a stock system on my phone!!
Thank you much!!!
Click to expand...
Click to collapse
This is the latest RUU for your phone. Just follow the instructions on the page. The "Security Warning" may go away but the other two will more than likely remain.
Rom update utility gives me low battery error
I downloaded the RUU from the link u gave me. I made sure there's a usb driver in place, for my htc one. When i start the rom update thing, and i go through the "agree" and check boxes....the rom utility gives me error 120, saying that my main battery power is low (less than %30), though my phone is fully charged and my laptop is fully charged.... Please advice
Got past the battery error message
Shtehla said:
I downloaded the RUU from the link u gave me. I made sure there's a usb driver in place, for my htc one. When i start the rom update thing, and i go through the "agree" and check boxes....the rom utility gives me error 120, saying that my main battery power is low (less than %30), though my phone is fully charged and my laptop is fully charged.... Please advice
Click to expand...
Click to collapse
now I cant go past error 170 within the RUU instalation process... can figure out how to get past that...
Shtehla said:
now I cant go past error 170 within the RUU instalation process... can figure out how to get past that...
Click to expand...
Click to collapse
Try this process for getting past error 170. If this doesn't work then try this procedure:
Start the RUU.EXE, it will creat a temporary directory in %TEMP%, and within that folder you will find a 1GB+ file called ROM.ZIP <- this is the full ruu.zip which you can flash using fastboot.
After starting the RUU.EXE, when it's on the first screen, in Windows Explorer type %TEMP% in the location box that will jump you to the folder, sort by date modified, and find the newest folder within that, it's going to have a weird long alpha numeric name, and within that you'll find plenty of files, but one very large file called ROM.ZIP, that's the one you want.
Copy rom.zip into your fastboot/adb folder.
At this point just Cancel and quit out of the ROM Update Utility.
Open a command window in your fastboot/adb folder and
Go to your bootloader. Type:
Code:
adb reboot bootloader
Type:
Code:
fastboot oem rebootRUU
This will reboot your HTC One and you will see a black screen with a silver HTC logo. Now, you will need to access the rom.zip file and flash it. I have copied my rom.zip to my adb folder located at: C:/mini-sdk/rom.zip. So, type:
Code:
fastboot flash zip rom.zip
Don't touch anything during the flash process. It will start and after some time, you will see FAILED error. Don't worry; it's the file preparation process if you have firmware higher than that of the RUU. Just do the same command again and the flash process will complete successfully this time.
Code:
fastboot flash zip rom.zip
Look at the Command Prompt to know when the flash is complete. At the same time if you look at your phone, you will notice a green progress bar. When the flashing is complete on the Command Prompt, you will notice that the green bar is stuck at about 95%. This is normal. It's just a bug in the progress bar - what matters is the output from the Command Prompt window.
Now, you can reboot. Type:
Code:
fastboot reboot
This will restart your phone. Let it boot up. It might take a little longer for the first boot up sequence. You will then have completely stock software (firmware & ROM). Go to your bootloader and check that you are S-ON/OFF and Bootloader lock/unlock are unchanged from before the RUU rom.zip flashing procedure. You can now also receive OTA updates.
I get an error right when getting to the step to flash ROM unto phone.
Start the RUU.EXE, it will creat a temporary directory in %TEMP%, and within that folder you will find a 1GB+ file called ROM.ZIP <- this is the full ruu.zip which you can flash using fastboot.
After starting the RUU.EXE, when it's on the first screen, in Windows Explorer type %TEMP% in the location box that will jump you to the folder, sort by date modified, and find the newest folder within that, it's going to have a weird long alpha numeric name, and within that you'll find plenty of files, but one very large file called ROM.ZIP, that's the one you want.
Copy rom.zip into your fastboot/adb folder.
At this point just Cancel and quit out of the ROM Update Utility.
Open a command window in your fastboot/adb folder and
Go to your bootloader. Type:
Code:
adb reboot bootloader
Type:
Code:
fastboot oem rebootRUU
This will reboot your HTC One and you will see a black screen with a silver HTC logo. Now, you will need to access the rom.zip file and flash it. I have copied my rom.zip to my adb folder located at: C:/mini-sdk/rom.zip. So, type:
Code:
fastboot flash zip rom.zip
Don't touch anything during the flash process. It will start and after some time, you will see FAILED error. Don't worry; it's the file preparation process if you have firmware higher than that of the RUU. Just do the same command again and the flash process will complete successfully this time.
Code:
fastboot flash zip rom.zip
Look at the Command Prompt to know when the flash is complete. At the same time if you look at your phone, you will notice a green progress bar. When the flashing is complete on the Command Prompt, you will notice that the green bar is stuck at about 95%. This is normal. It's just a bug in the progress bar - what matters is the output from the Command Prompt window.
Now, you can reboot. Type:
Code:
fastboot reboot
This will restart your phone. Let it boot up. It might take a little longer for the first boot up sequence. You will then have completely stock software (firmware & ROM). Go to your bootloader and check that you are S-ON/OFF and Bootloader lock/unlock are unchanged from before the RUU rom.zip flashing procedure. You can now also receive OTA updates.
[/QUOTE]
I follow the steps just fine, and I get to step "fastboot flash zip rom.zip" and it gives me an error. see file attached
Shtehla said:
Start the RUU.EXE, it will creat a temporary directory in %TEMP%, and within that folder you will find a 1GB+ file called ROM.ZIP <- this is the full ruu.zip which you can flash using fastboot.
After starting the RUU.EXE, when it's on the first screen, in Windows Explorer type %TEMP% in the location box that will jump you to the folder, sort by date modified, and find the newest folder within that, it's going to have a weird long alpha numeric name, and within that you'll find plenty of files, but one very large file called ROM.ZIP, that's the one you want.
Copy rom.zip into your fastboot/adb folder.
At this point just Cancel and quit out of the ROM Update Utility.
Open a command window in your fastboot/adb folder and
Go to your bootloader. Type:
Code:
adb reboot bootloader
Type:
Code:
fastboot oem rebootRUU
This will reboot your HTC One and you will see a black screen with a silver HTC logo. Now, you will need to access the rom.zip file and flash it. I have copied my rom.zip to my adb folder located at: C:/mini-sdk/rom.zip. So, type:
Code:
fastboot flash zip rom.zip
Don't touch anything during the flash process. It will start and after some time, you will see FAILED error. Don't worry; it's the file preparation process if you have firmware higher than that of the RUU. Just do the same command again and the flash process will complete successfully this time.
Code:
fastboot flash zip rom.zip
Look at the Command Prompt to know when the flash is complete. At the same time if you look at your phone, you will notice a green progress bar. When the flashing is complete on the Command Prompt, you will notice that the green bar is stuck at about 95%. This is normal. It's just a bug in the progress bar - what matters is the output from the Command Prompt window.
Now, you can reboot. Type:
Code:
fastboot reboot
This will restart your phone. Let it boot up. It might take a little longer for the first boot up sequence. You will then have completely stock software (firmware & ROM). Go to your bootloader and check that you are S-ON/OFF and Bootloader lock/unlock are unchanged from before the RUU rom.zip flashing procedure. You can now also receive OTA updates.
Click to expand...
Click to collapse
I follow the steps just fine, and I get to step "fastboot flash zip rom.zip" and it gives me an error. see file attached[/QUOTE]Could you post a fastboot getvar all (except for imei and serialno)? Also, open up the rom.zip and post the contents of the android-info.txt file. Were there two rom.zip files?
Here's teh getvar all results
majmoz said:
[/HIDE]
there was only one zip file.
Click to expand...
Click to collapse
Here's what I get when trying to open the rom.zip
See attachement
Shtehla said:
See attachement
Click to expand...
Click to collapse
Let try the RUU 5.14.531.1 it is the next one up from your version.
I relocked the bootloader
majmoz said:
If you remember I had my bootloader relocked through oem relock. I did unlock it yesterday, would that make a difference in the whole process?
Not it says ***tempered*** and ***unlocked*** on the top of the screen.
Click to expand...
Click to collapse
Shtehla said:
majmoz said:
If you remember I had my bootloader relocked through oem relock. I did unlock it yesterday, would that make a difference in the whole process?
Not it says ***tempered*** and ***unlocked*** on the top of the screen.
Click to expand...
Click to collapse
Yes, since you are S-ON your bootloader needs to be locked/relocked to run RUU and OTA.
Click to expand...
Click to collapse
Here's what I get
majmoz said:
Let try the RUU 514.531.1 it is the next one up from your version.
Click to expand...
Click to collapse
when I flash the ruu it starts with the same message, but then it continues and has a finish. Not the one I need I gues. See attachement.
after i started RUU to create the ROM file in TEMP, it did create 2 rom files (rom_01, rom_02) the rom_02 was the 1.5gb one, and I renamed it to "rom.zip" and i continued with original instructions....
P.S thank you for helping me
Shtehla said:
when I flash the ruu it starts with the same message, but then it continues and has a finish. Not the one I need I gues. See attachement.
after i started RUU to create the ROM file in TEMP, it did create 2 rom files (rom_01, rom_02) the rom_02 was the 1.5gb one, and I renamed it to "rom.zip" and i continued with original instructions....
P.S thank you for helping me
Click to expand...
Click to collapse
Did you try the 5.14.531.1 RUU.exe?
Yes I did.
majmoz said:
Did you try the 5.14.531.1 RUU.exe?
Click to expand...
Click to collapse
Those are the results with this new ruu
Shtehla said:
Those are the results with this new ruu
Click to expand...
Click to collapse
Did you try it as a windows executable file not as a rom.zip?
Yep
majmoz said:
Did you try it as a windows executable file not as a rom.zip?
Click to expand...
Click to collapse
the exe file creates the rom zip. I didn't touch the zip, except i copied it in the fastboot folder
Shtehla said:
the exe file creates the rom zip. I didn't touch the zip, except i copied it in the fastboot folder
Click to expand...
Click to collapse
Yes, I know you pull the rom zip out of the %TEMP% folder. Did you Cancel the update in Windows or did you select Next to allow it to continue?
I
majmoz said:
Yes, I know you pull the rom zip out of the %TEMP% folder. Did you Cancel the update in Windows or did you select Next to allow it to continue?
Click to expand...
Click to collapse
I canceled it, after I copied the rom.zip from temp into fastboot folder.
Shtehla said:
I canceled it, after I copied the rom.zip from temp into fastboot folder.
Click to expand...
Click to collapse
Try to run it completely through in Windows.
Hello People !!!
Want to return your OP2 to 100% Stock Factory Image or have you soft bricked OP2 and nothing except fastboot works or you need OxygenOS fastboot images ? This is the thread for you !!
Download Fastboot Image from here :- https://mega.nz/#!itR00ZaI!gJ6T0jgqfZaIF9NLlCzWj4LIGMMhCw8m8owFdeB_2B4
Extract the Zip in a folder .
Boot the phone into fastboot.
Run the batch file.
Done.
This method WILL NOT WIPE DATA
If you want to wipe data to,flash userdata.img from here :- https://www.androidfilehost.com/?fid=24052804347833307
Use command
fastboot flash userdata userdata_64.img
Click to expand...
Click to collapse
You need the latest adb/fastboot package to be successful.For that,do this :-
Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only)
Extract the zip and place the android-sdk-windows folder on your desktop.
Go into the android-sdk-windows folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):-
Tools > Android SDK Tools, Android SDK Platform-tools- Extras > Android Support Library, Google USB Driver
Click to expand...
Click to collapse
Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If you don't see this new folder, repeat the step above.
Thanks for reading ...
Credits :- @jcespi2005 For making the fastboot zip ... @Naman Bhalla for making the thread and partitions images thread.
Done to @jcespi2005 here :- http://forum.xda-developers.com/donatetome.php?u=281521
Donate to me here :- http://www.amazon.in/gp/registry/wishlist/1X55WMSVTW3KW/
Thanks again. !!
This method has been tested successfully by atleast 2 people ,including me
This img is oxygen os 2.1.1?
Sent from my Nexus 5 using XDA Free mobile app
matitorres07 said:
This img is oxygen os 2.1.1?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Correct
DEAD
OMG MY OPT IS DEAD... dont start just vibrate and flashing dont star...i cant went in to the recovery mode...just on fastboot HELPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPP
S0ad113 said:
OMG MY OPT IS DEAD... dont start just vibrate and flashing dont star...i cant went in to the recovery mode...just on fastboot HELPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPP
Click to expand...
Click to collapse
i've got the exact same problem. Let me guess: your bootloader is locked?
anyways, try this: press POWER + VOLUME UP until you're in fastboot mode. connect the OP2 to your PC and execute the command 'fastboot continue' in a cmd window. if not, repeat until it works. your phone should boot like normal, you can't restart or shutdown though, since you'll be stuck in the same loop again.
at least that's my problem. can't flash anything since bootloader is locked, ADB does work fine though, as long as the phone is running.
really sucks to need a PC everytime you want to power on your phone.. if anyone can help, i'd gladly appreciate it
S0ad113 said:
OMG MY OPT IS DEAD... dont start just vibrate and flashing dont star...i cant went in to the recovery mode...just on fastboot HELPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPP
Click to expand...
Click to collapse
I TRY TO USE TOOLBOX and try to flash..some via CMD But give me error writing "recover" ...Failed Remote: device is Locked. Cannot Flash images)
Helppppppp me
---------- Post added at 11:13 PM ---------- Previous post was at 11:08 PM ----------
rattig said:
i've got the exact same problem. Let me guess: Your bootloader is locked?
Anyways, try this: Press power + volume up until you're in fastboot mode. Connect the op2 to your pc and execute the command 'fastboot continue' in a cmd window. If not, repeat until it works. Your phone should boot like normal, you can't restart or shutdown though, since you'll be stuck in the same loop again.
At least that's my problem. Can't flash anything since bootloader is locked, adb does work fine though, as long as the phone is running.
Really sucks to need a pc everytime you want to power on your phone.. if anyone can help, i'd gladly appreciate it
Click to expand...
Click to collapse
i try all always locked always loop omg
---------- Post added at 11:38 PM ---------- Previous post was at 11:13 PM ----------
Helpppppppppppppppppppppppppppppppppppppppppppppppppppppppp
Please note that on the fastboot userdata command you are missing a letter. You have "fastboot flash userdata userdata_64.img" and it should be fastboot flash userdata userdata_64G.img. Great job by the way, used it to reset the OP2 and works great.
ukcain said:
Please note that on the fastboot userdata command you are missing a letter. You have "fastboot flash userdata userdata_64.img" and it should be fastboot flash userdata userdata_64G.img. Great job by the way, used it to reset the OP2 and works great.
Click to expand...
Click to collapse
I did it..but is not that the problem....the problem is..when i try to flash some...fail always. give the error : device is Locked. Cannot Flash images
REBORN
Solved ty allll
How on earth did you manage to get a fastboot image for the OP2?
Thanks by the way
Stevles said:
How on earth did you manage to get a fastboot image for the OP2?
Thanks by the way
Click to expand...
Click to collapse
Converting the .DAT inside the official recovery ZIP to .IMG format
The rest of partitions are on the fastboot format, so only system and cache needs conversion, and userdata comes from hydrogenOS fastboot package...
jcespi2005 said:
Converting the .DAT inside the official recovery ZIP to .IMG format
The rest of partitions are on the fastboot format, so only system and cache needs conversion, and userdata comes from hydrogenOS fastboot package...
Click to expand...
Click to collapse
Nice
is not flash me the file system.img
i get error message "the app crash" from windows
pls help
Zahi122 said:
is not flash me the file system.img
i get error message "the app crash" from windows
pls help
Click to expand...
Click to collapse
I'm having the same issue
I'll try to do it through TWRP and see if that works for me
Naman Bhalla said:
Hello People !!!
Want to return your OP2 to 100% Stock Factory Image or have you soft bricked OP2 and nothing except fastboot works or you need OxygenOS fastboot images ? This is the thread for you !!
Download Fastboot Image from here :- https://mega.nz/#!itR00ZaI!gJ6T0jgqfZaIF9NLlCzWj4LIGMMhCw8m8owFdeB_2B4
Click to expand...
Click to collapse
Hi,
Are these images from a Chinese, EU or US version of the device?
thanks
Hello all,
is there a new img.image?
I have great problems and need a super clean install included wipe data!!
Thanxx for helping
S5 & One + Boeffla Inside
S0ad113 said:
Solved ty allll
Click to expand...
Click to collapse
How? What did you do different? For me, the fastboot.exe stops working at the below step.
..\fastboot>fastboot flash system system.img
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
avi0889 said:
How? What did you do different? For me, the fastboot.exe stops working at the below step.
..\fastboot>fastboot flash system system.img
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
Click to expand...
Click to collapse
I got the same error at first then I copied all the files into my platform-tools dir that has ADB & fastboot then run it.
Try this tool. It works good for me. But the windows driver for OP2 and the Qualcomm Diagnostic 9006 Driver must be installed.
Sry, can`t post the link. please PN.
Worked great, but it switched my wifi off. Even if I turn it on manually it doesn't show any active networks. I have rebooted several times. Any workaround?