Related
I got the s-off files from xda and had no problems with turning it off. i then used the superoneclick method to root my HTC Aria running the OTA 2.2.2 att update. my phone is rooted, i have superuser and all is good..... except that when i try to go into recovery mode to install a custom rom it just gives me a failure screen of a phone and a red triangle with a red exclamation point in it. i have to take the battery out to reset the phone.
why wont it let me into recovery?
if anyone has some insight for me it would be greatly appreciated.
thank u
AlphaRevX doesn't install recovery automatically for you, but once you have S-OFF you can do it yourself. This post tells you what to do:
http://forum.xda-developers.com/showthread.php?t=1122694
thanks for the quick response.
i downloaded all the files (to windows computer) then extracted files. then i went and put my phone into fastboot usb.
i guess im getting confused on the next step. it says to fastboot flash recovery <recovery.img> from a command line <----- (not sure what the command line is)
i know about phones and apps but am just getting into roms and rooting.
sorry for having a blonde moment
Start > Run > Type "cmd"
Then from command prompt do:
Code:
cd C:\path\to\folder
fastboot flash recovery recovery.img
(replace C:\path\to\folder with the place you extracted the files)
Preamble
This is the S-OFF upgrade from GingerBread to HoneyComb
Do not perform this procedure if you have the official HTC hboot, it will not work. You must have a revolutionary hboot (see prerequisites).
***If you performed this procedure with previously and have hboot version 6.14.5555 please update to the new hboot, 6.14.5555 is no longer supported***
Upgrade instructions at the bottom of the procedures.
Prerequisites
You must have performed Revolutionary S-OFF
If running on windows you will need these fastboot drivers
If running the procedure on Linux or MacOS you must have fastboot working.
There are no other software prerequisites for this procedure, it does not matter what ROM/Kernel or recovery you are using.
Don't bother asking for help if you try to do this on a virtual machine, you won't get any.
Run on a real machine.
Windows Instructions
Download this file MD5=c62cc1d0453799a7277abfea444d20e4
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Copy the superuser zip file to the root of your SDCARD
Extract the large zip file downloaded in step 1
Navigate to the RUU_Express_B02 directory
Double-click ARUWizard.exe and proceed like any other RUU, ticking the boxes and pressing next the screen as required.
Postinstall
Reboot to recovery
Flash the SU zip file copyed in instruction 3
Linux/MacOS Instructions (Also works on windows, use if ARUWizard.exe crashes for you)
Download this file MD5=5ef525038a3b8b0af2f214098fd80252
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Copy the superuser zip file to the root of your SDCARD
Boot your view to fastboot mode.
Run the following commands:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip RUU_Express_B02_RAW.zip
[COLOR="Red"][I]***This will fail first time with error 90, repeat the command[/I][/COLOR]
fastboot flash zip RUU_Express_B02_RAW.zip
[COLOR="Red"][I]***Ignore the on-screen progress bar, the flash is complete when fastboot completes[/I][/COLOR]
fastboot reboot
Postinstall
Reboot to recovery
Flash the SU zip file copyed in instruction 3
Alternative Installation Instruction (Any OS)
Download this file MD5=5ef525038a3b8b0af2f214098fd80252
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Rename the RUU_Express_B02_RAW.zip file PG41IMG.zip and place on the root of your (external) sdcard
Copy the superuser zip file to the root of your SDCARD
Boot your view bootloader, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update
***This will fail after completing part of the update, don't worry it's expected***
Boot your view bootloader a second time, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update again.
Postinstall
Reboot to recovery
Flash the SU zip file copyed in instruction 3
Do not mirror files from this post.
No discussion of Honeycomb content or changes or the relative merits of Gingerbread and Honeycomb. This thread is for the procedure and support thereof only! Also please don't quote the first post because your post becomes an automatic TLDR.
Update Instructions
Use these instructions if you currently have hboot 6.14.5555 - Your data should be preserved but take a backup first just in case.
Method 1
Download this file MD5=20fd6e7546ac2fc422c5a9a5b366f77c
Copy the file to the root of your external SDCARD
Boot your view bootloader, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update
Method 2
Download this file MD5=20fd6e7546ac2fc422c5a9a5b366f77c
Boot your view to fastboot mode.
Run the following commands:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip PG41IMG.zip
[I][COLOR="Red"]***Ignore the on-screen progress bar, the flash is complete when fastboot completes[/COLOR][/I]
fastboot reboot
[Revision History]
B02 - updated full version: hboot 6.14.5556
New bootloader to patch bugs with fastboot flashing
- Fastboot flashing splash1 fixed
- Fastboot flashing hboot fixed
Patch for upgrading from a previous version added.
B01 - Initial full version: hboot 6.14.5555
BETA- Developer preview
Special thanks: contradude for the early and riskiest testing, and Maine_Coon for all the ongoing testing
Downgrade to Gingerbread
Preamble
This is the S-OFF downgrade from HoneyComb to S-OFF GingerBread if you are not S-OFF and have a HTC (not revolutionary) hboot then do not do this it will not work.
The full versions of these files will give you a fully functional Gingerbread installation with S-OFF, CWM recovery and boot image with the secure flag turned off.
Windows Instructions
Download this file MD5=f5afc4b457a17f88cc611b40e6c7cdc8
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Copy the superuser zip file to the root of your SDCARD
Extract the large zip file downloaded in step 1
Navigate to the Express_Downgrade directory
Double-click ARUWizard.exe and proceed like any other RUU, ticking the boxes and pressing next the screen as required.
Postinstall
Reboot to recovery
Flash the SU zip file copied in instruction 3 if using the full version.
Linux/MacOS Instructions (Also works on windows, use if ARUWizard.exe crashes for you)
Download this file MD5=7cfbaf099d80d899b13848a3ed3fd66a
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Copy the superuser zip file to the root of your SDCARD
Boot your view to fastboot mode.
Run the following commands:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip Express_dg.zip [colour=blue](or Express_dg_lite.zip as appropriate)[/blue]
[COLOR="Red"][I]***This will fail first time with error 90, repeat the command[/I][/COLOR]
fastboot flash zip Express_dg.zip [colour=blue](or Express_dg_lite.zip as appropriate)[/blue]
[COLOR="Red"][I]***Ignore the on-screen progress bar, the flash is complete when fastboot completes[/I][/COLOR]
fastboot reboot
Postinstall
Reboot to recovery
Flash the SU zip file copied in instruction 3 if using the full version.
Alternative Installation Instruction (Any OS)
Download this file MD5=7cfbaf099d80d899b13848a3ed3fd66a
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Rename the file downloaded in step1 to PG41IMG.zip and place on the root of your (external) sdcard
Copy the superuser zip file to the root of your SDCARD
Boot your view bootloader, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update
***This will fail after completing part of the update, don't worry it's expected***
Boot your view bootloader a second time, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update again.
Postinstall
Reboot to recovery
Flash the SU zip file copied in instruction 3 if using the full version.
Do not mirror files from this post.
wow you are really fast, excellent men.
One for me please
reserved 2
Great response time!
For us newbs, I'd like to clarify... This isn't an alternative HoneyComb, yet. Just an attempt to make the OTA honeycomb "unlockable", right?
vancraft said:
Great response time!
For us newbs, I'd like to clarify... This isn't an alternative HoneyComb, yet. Just an attempt to make the OTA honeycomb "unlockable", right?
Click to expand...
Click to collapse
This is an attempt to make downgrading easier for us.
spartan1987 said:
This is an attempt to make downgrading easier for us.
Click to expand...
Click to collapse
Right. That's the "recovery" part.
But its also described as "root, and all". I'm wondering if this allows the installer to root the OTA Honeycomb? Or will more work be required before the install can be further changed (i.e. s-off, eventually upgraded to ICS, etc.)?
It works
I can confirm this works with root flashed and all. I now have a rooted HC. tyvm globatron
risb577 said:
I can confirm this works with root flashed and all. I now have a rooted HC. tyvm globatron
Click to expand...
Click to collapse
so, does that mean you could, in theory, flash a custom HC rom once we get one?
Throw up some screenshots or a video would you?
edit: oh and test rom manager and titanium backup if you don't mind.
I have a rooted CWM backup of the stock.
Do I need to restore and then unroot before proceeding with HC?
stuck on soft brick..
Hey Guys
how do you do the step 6?
I am in cmd and kept telling me command not recornized or something...
I guess I need to know how to flash that RUU-mini zip...
thanks for all your help...
Maine_Coon said:
I have a rooted CWM backup of the stock.
Do I need to restore and then unroot before proceeding with HC?
Click to expand...
Click to collapse
No, as it says in the OP, You MUST be s-off and THEN run an RUU. Accept all updates to include the HC update and the view will be soft bricked. THEN use fastboot to push the mini ruu.
---------- Post added at 10:09 PM ---------- Previous post was at 10:07 PM ----------
myowin said:
Hey Guys
how do you do the step 6?
I am in cmd and kept telling me command not recornized or something...
I guess I need to know how to flash that RUU-mini zip...
thanks for all your help...
Click to expand...
Click to collapse
If it says it's an unrecognized command, then either you do not have fastboot installed, or you haven't gone into environment variables (assuming it's a windows box) and added those commands to the path. try that first (google is your friend and you can google in XDA). Good luck.
A quick question here. Once it is the soft brick mode, I hold down power and volume down to get back to fastboot mode. Is this correct? And I know the ruu will wipe my data but nothing here should wipe the internal sd, correct?
thank you so much for quick respond..
I think I found it here how to do that.. (for someone like me... )
http://forum.xda-developers.com/showthread.php?t=532719
root
Im not sure what this method of rooting will do for us, but I am under the impression that this will help if we need to go back to GB, or flash another custom HC rom when someone else cooks one up. I have not tested downgrading.
I can report that clockwork is installed with the option to flash from zip, mounts, etc just like the old clockwork. And I still have S-OFF. I installed ROM manager, but it gave me the "you don't have clockwork installed" message. I'm not sure if that is normal, because I don't use ROM Manager. Titanium did see root. Check out the screens.
ElAguila said:
A quick question here. Once it is the soft brick mode, I hold down power and volume down to get back to fastboot mode. Is this correct? And I know the ruu will wipe my data but nothing here should wipe the internal sd, correct?
Click to expand...
Click to collapse
I haven't done this yet, but I'm dling the RUU right now to do it and help people troubleshoot.
To answer your question, if you hold down the power button long enough, the view will power off, then you can hold power + vol down to get back into the bootloader and select fastboot mode, then open cmd, type fastboot devices and check to make sure yours shows up, then proceed with pushing the mini-ruu. If I'm wrong guys, correct me. Hope it works out for you.
ElAguila said:
A quick question here. Once it is the soft brick mode, I hold down power and volume down to get back to fastboot mode. Is this correct? And I know the ruu will wipe my data but nothing here should wipe the internal sd, correct?
Click to expand...
Click to collapse
Im not sure if this matters, but when I was in soft brick, I rebooted a few times and could not get into the bootloader. It just seemed to ignore the vol down keypress. I then unplugged the usb, powered off from soft brick, and held the vol. down button down even before I hit the power button as I was turning it on. Once I was in bootloader, I just plugged the usb back in.
EDIT: More tips:
1.After I flashed the initial stock ruu, and before I accepted any updates, I turned off fastboot in the power options and enabled usb debugging.
2. I did this from a Windows 7 laptop. When I initially tried to perform the softbrick steps, I got an access denied error message. The files were sent ok, but errored on saving. I closed the command prompt, and re-lauched the command prompt as administrator. The commands sent successfully.
3. Also, once you send the mini ruu over, the Tablet sat in the the oem loader with a 70% full progress bar after I successfully sent the mini ruu. I waited about 10 minutes because I was unsure how to proceed. I finally issued:
fastboot reboot-bootloader
Once back into bootloader, I mounted usb storage, copied SU to the card, and flashed from zip
risb577 said:
Im not sure what this method of rooting will do for us, but I am under the impression that this will help if we need to go back to GB, or flash another custom HC rom when someone else cooks one up. I have not tested downgrading.
I can report that clockwork is installed with the option to flash from zip, mounts, etc just like the old clockwork. And I still have S-OFF. I installed ROM manager, but it gave me the "you don't have clockwork installed" message. I'm not sure if that is normal, because I don't use ROM Manager. Titanium did see root. Check out the screens.
Click to expand...
Click to collapse
Yeah, rom manager won't work bc we don't have official support from Koush for CWM recovery so that's no issue, I was just curious is all lol. I'm glad to hear titanium detects root, as that was an issue initially for the view. Try to backup your apps, test radios (3g, 4g, wifi, bluetooth, GPS, ETC), run quadrant. I don't know how familiar you are with honeycomb to test out all of it's functions, but we are going to need a few people to test this out for globatron so he can make fixes and/or adjustments as necessary, which is why he specifically asked for devs and people familiar with troubleshooting to do this first. That's the beauty of open source, we're all guinea pigs.
I forgot to ask this earlier. What does the soft brick state look like? Is it just the white screen the the green HTC on it? I want to make sure I don't power it off while it is still flashing HC.
soft brick screen
ElAguila said:
I forgot to ask this earlier. What does the soft brick state look like? Is it just the white screen the the green HTC on it? I want to make sure I don't power it off while it is still flashing HC.
Click to expand...
Click to collapse
It looks like this pic. Plus another clue you are soft bricked is it stays here longer than 10 minutes if you care to wait lol
I rooted my htc evo 4g lte and have twrp installed, and tried to flash a rom, when i rebooted it always takes me back to hboot screen and is stuck there, won't actually boot up. I am able to go to recovery and use twrp including usb mount (maybe a zip i could flash to help). I have searched for awhile but haven't found any real solution for my phone yet.
I have S-on, no external sd card.
If you need any more info just ask.
Thanks in advance for the help!
Extract the boot.img from the rom, place it in adb folder and put phone in fastboot
Type fastboot flash boot boot.img and restart the phone
solved!!!!!!!
om4 said:
Extract the boot.img from the rom, place it in adb folder and put phone in fastboot
Type fastboot flash boot boot.img and restart the phone
Click to expand...
Click to collapse
Thankyou so much for the fast reply, and fix!! I did what you said and it worked! The funny thing is that it was my first flash, is there something i did or should avoid to have this happen to me again? Any way I am so grateful and now am going to try out team venoms viper4g 2.0.2 new rom!
If others have the same problem and want more detailed info about what I did:
1. downloaded sdk manager developer.android.com/sdk/index. html opened the program and installed platform tools
2. Since I have twrp I put into recovery and mounted usb found the zip of the rom i wanted to flash opened it found the boot.img and copied it to the folder where platform tools where installed (C:\Users\yourname\AppData\Local\Android\android-sdk\platform-tools)
3. got back to hboot screen
4. opened cmd to the folder by typing: cd then file path like mine above
5. then in cmd typed fastboot flash boot boot.img it will do its thing
6. restart phone and hopefully work for you too!
vipomorge said:
Thankyou so much for the fast reply, and fix!! I did what you said and it worked! The funny thing is that it was my first flash, is there something i did or should avoid to have this happen to me again? Any way I am so grateful and now am going to try out team venoms viper4g 2.0.2 new rom!
If others have the same problem and want more detailed info about what I did:
1. downloaded sdk manager developer.android.com/sdk/index. html opened the program and installed platform tools
2. Since I have twrp I put into recovery and mounted usb found the zip of the rom i wanted to flash opened it found the boot.img and copied it to the folder where platform tools where installed (C:\Users\yourname\AppData\Local\Android\android-sdk\platform-tools)
3. got back to hboot screen
4. opened cmd to the folder by typing: cd then file path like mine above
5. then in cmd typed fastboot flash boot boot.img it will do its thing
6. restart phone and hopefully work for you too!
Click to expand...
Click to collapse
If you are s-on, the kernel won't flash with the rom so you have to flash it separately like om4 showed you. Some roms, like MeanRom have modified their install script to automatically load the kernel to avoid this extra step.
The latest Mean installer failed for me, as did the latest Viper, something to keep in mind if you try those and they don't boot
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.
Thanks to everyones help I was able to get 320 updated, then OTA 321 came without issue. Now I am trying to re-root and having no luck. (And please let me know if this is the wrong section, but I see all the rooting questions in this one.)
Followed the steps someone posted in the thread "How does one get root again once upgraded to 5.1?":
• Phone was still unlocked but I went through the steps and clicked ‘ROOT’ in the software tool anyways (and got no errors).
• Downloaded and renamed and moved the TWRP Recovery from the link in those steps (and later tried with twrp-2.8.7.0, to the same end).
• Found my phone listed in the “adb devices” list in command prompt, unplugged, ran ‘fastboot flash recovery TWRP.img’ from that folder, booted into recovery, plugged it back in and it successfully finished on the computer screen (nothing showed up on the phone).
• Rebooted into TWRP (Up and power) right from that recovery screen, and it boots to the EMUI screen asking me to navigate with up and down through “Reboot system now”, “Wipe data/factory reset”, etc.
All drivers are the same as when I rooted my phone on this same computer 2-3 months ago and again 2-3 weeks ago before I upgraded to 5.1, but just to be sure, I rechecked my ADB drivers, fastboot files, and confirmed it sees this as a fastboot device when in recovery… it just wont boot into TWRP so I can put supersu on.
Not sure if I am doing something wrong, if something is different in B321, or if I should try some of the alternate rooting methods (Shuame or whatnot… I’ve never tried them). It's the last step, and I can be happy and get back to where I was.
I have tried flashing that TWRP file a dozen times… and it works every time, but then it boots to the stock EMUI every time. I heard someone once say that the phone could be overwriting it? But I am booting into it, or trying to, right from the recovery screen. Of course I tried rebooting into the phone normally a few times as well, then restarting and going into ‘Up + Power’, every time the same thing.
Appreciate your suggestions.
try rename a file detailed here:
http://forum.xda-developers.com/showthread.php?p=62380255
xordos said:
try rename a file detailed here:
http://forum.xda-developers.com/showthread.php?p=62380255
Click to expand...
Click to collapse
That looks almost like my issue. However, I don't believe I understand your post entirely.
So you were unable to get TWRP to stick? I am unable to even get there once.
1. I don't understand how to rename that file.
2. Your steps say I have to get into TWRP, then "install SU.zip inside twrp". Since I cannot get into TWRP, I cannot get to step 2, and I cannot get to step 3, renaming the file.
Beggars can't be choosers, but could you dumb it down for me just a smidge? Can I get into any place on the phone or from my Windows PC to change this file name to make it work?
save the SU.zip from that post to your sdcard.
then run this cmd after goto bootloader:
fastboot boot twrp.img
Note is cmd is different from the regular flash cmd.
this will boot into twrp, then install the SU.zip you just downloaded.
This way, when you boot into OS, you will have full supersu completely installed. Now your phone is rooted, and you can use root browser or anything you like to rename the file.
xordos said:
save the SU.zip from that post to your sdcard.
then run this cmd after goto bootloader:
fastboot boot twrp.img
Note is cmd is different from the regular flash cmd.
this will boot into twrp, then install the SU.zip you just downloaded.
This way, when you boot into OS, you will have full supersu completely installed. Now your phone is rooted, and you can use root browser or anything you like to rename the file.
Click to expand...
Click to collapse
So perfect; so simple. Thanks!
Now rooted... I'll go rename that now.
I went to /firmware/image/update, and renamed update.app to updatex.appx. Rebooted with Up+Power, and TWRP is there by default.