I used the System Recovery app to flash recovery and boot into it, then I installed Neutrino ROM EE but now when I try to boot all I get is 'failed to boot 2. starting RSD mode.' help?
bjgrenke said:
I used the System Recovery app to flash recovery and boot into it, then I installed Neutrino ROM EE but now when I try to boot all I get is 'failed to boot 2. starting RSD mode.' help?
Click to expand...
Click to collapse
Is our phone bootloader unlocked if No u will have to unlock the bootloader first.
And check this thread
[Updated 1-7-2012] THE BEGINNERS (N00B) GUIDE!!! N00BS LOOK HERE FOR YOUR HOW TOs
I don't think the bootloader is unlocked, and I'm not sure how I can do that since I can't boot.
Is this a brick? Or is there a fix for this. Need help here people.
bjgrenke said:
Is this a brick? Or is there a fix for this. Need help here people.
Click to expand...
Click to collapse
As terminator 1983 said, you need to unlock your bootloader. Click through the link that was posted and read up on the unlocking process. You'll see that involves being in RSD mode, and flashing the pudding .sbf. Then reflash CWM, and re-install your ROM.
Alright, I clicked the link, and scrolled down to HOW TO UNLOCK BOOTLOADER. The first option, the link is dead. The second option, which seems to be easiest, the download link is dead also. Is there any other way I can get the file "Full 2.3.4 with preinstall root and pudding bootloader unlock, full sbf" ? Then using RSD Lite to flash that should be all I need.
Also, in that second option, I scrolled down to the second post since I'm not an ATT user, and tried doing the CMD commands, but when I put in the first command "fastboot flash preinstall preinstall.img" it says this is not a command.
bjgrenke said:
Also, in that second option, I scrolled down to the second post since I'm not an ATT user, and tried doing the CMD commands, but when I put in the first command "fastboot flash preinstall preinstall.img" it says this is not a command.
Click to expand...
Click to collapse
make sure you run the command from the same folder your fastboot.exe is at. Also, any file you are trying to flash has to also be in that folder.
i.e. fastboot.exe and preinstall image are in c:\atrix, then cd into c:\atrix and then run your commands.
Sorry, I can't help with the dead links.
*Edit*Btw, you can just get the pudding .sbf from here, instead of using the automatic ones.
Alright, moved fastboot and the img into the same folder, ran the commad, and it says the following:
"sending 'preinstall'
OKAY
writing 'preinstall'
FAILED (status read failed (unknown error))
finished"
followed the link you provieded to the main pudding thread, downloaded the IHOP file for international useds, flashed the SBF succesfully, but I'm just where I was before.
When following this guide http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader I type in the command in fastboot and it says OEM Fastboot Not supported.
Need help here guys.
Edit: Tried again and it gave me my code, redid the command with the code, this time it said ERROR: Failed to write.
Okay, making progress now, checked my phone and it said Your phone is not unlocked. Rebooted and not instead of saying Unable to boot 2 Starting RSD Mode, all it says is unlocked. I'm able to get into recovery mode, but it's the default android recovery in blue. What else can I do?
bjgrenke said:
Okay, making progress now, checked my phone and it said Your phone is not unlocked. Rebooted and not instead of saying Unable to boot 2 Starting RSD Mode, all it says is unlocked. I'm able to get into recovery mode, but it's the default android recovery in blue. What else can I do?
Click to expand...
Click to collapse
Glad to hear you got it unlocked. I would recommend flashing romracer's recovery. Make sure to read through the first 2 posts of that thread. There is a file you have to delete in order for it to stick. Since you're familiar with fastboot now, I would just use that method to install.
After that, follow the instructions to install your ROM of choice.
ghost_og said:
Glad to hear you got it unlocked. I would recommend flashing romracer's recovery. Make sure to read through the first 2 posts of that thread. There is a file you have to delete in order for it to stick. Since you're familiar with fastboot now, I would just use that method to install.
After that, follow the instructions to install your ROM of choice.
Click to expand...
Click to collapse
I've downloaded the Light green version, placed the img in a folder along with fastboot and the 2 dll files associated with fastboot, ran cmd to that folder, typed in the first command, and it says it's not an external or external command. Is there something else I should be doing?
Whattheheck, may as well copy what I posted on another forum for some additional info:
Hello, I've been on many forum sites looking for a fix for my problems, but nothing SO here's my story. I have a rooted Motorola Atrix on Bell. I installed the app "System Recovery" and used that to flash recovery, then booted into recovery and installed the rom "Neutrino Rom EE". The problem is, I didn't unlock my bootloader, so every time I tried turning my phone on it'd say "Failed to boot 2. Starting RSD mode." I used the guide "How To: Unlock the Atrix 4G Bootloader" on Breifmobile (can't post link) to unlock my bootloader, and from what I can see (my phone being stuck at the boot screen with a motorola logo and the word UNLOCKED in the top left) it worked. Problem is now I'm stuck here. I can access the menu by holding pwr and vol down, then I can select an option. I tried selecting Android Recovery, and this brings me to the default recovery, but there's nothing I can do here. I can still access RSD mode and Fastboot from the menu, so perhaps there's a fix from there.
Anyone? Need my phone for a meeting tomorrow
bjgrenke said:
Anyone? Need my phone for a meeting tomorrow
Click to expand...
Click to collapse
Download CWM recovery img file from here (not the zip one)
[Unlocked Only][RECOVERY][2011-11-14] Custom CWM-based Recovery 5.0.2.7-atrix5
Place the recovery img file in fastboot folder and type these commands on command prompt after getting to fastboot folder.
fastboot erase recovery (it will erase the earlier recovery)
fastboot flash recovery recovery-blue-atrix5.img
The second command will flash the recovery img on your device you will have to change this portion "recovery-blue-atrix5" of the command according ur revcover img name or rename ur recovery img with this name.
Related
Hi,
I was trying to install Cyanogenmod on my phone using the guide on the cyanogenmod wiki (I can't post the link, but it's the first google result for Motorola Atrix 4G: Full Update Guide)
I did everything in the guide, up to the point where I was supposed to flash the ROM onto my phone using RSD, but then it failed and gave me a "Error switching phone to BP Pass through mode". I unplugged it from the computer, took out the battery put it back in, and now it's giving me the
"Failed to boot 0x1000
No OS detected, going to RSD mode
in 5 seconds
...
..."
Menu. When plug my computer back in, and try to flash the same ROM using RSD Lite again, it says "Failed Flashing Process: Unable to retrieve interface handle". How do I fix this? I've never unlocked or rooted my phone or anything before. It was completely stock before I tried to do this.
Also, when trying to use fastboot and typing in fastboot oem unlock, it's just stuck on <waiting for device>
You tried to rsd a flashable rom on a locked bootloader phone. Your first error. You will need to rsd back to stock first. Then you need to root the phone. Then You need to follow the steps in the guide here http://forum.xda-developers.com/showthread.php?t=1202883 or here http://forum.xda-developers.com/showthread.php?t=1182871 (the second one I used recently). Once you've done that stuff THEN you can flash cm thru recovery. Hope you didn't hard brick.
pre4speed said:
You tried to rsd a flashable rom on a locked bootloader phone. Your first error. You will need to rsd back to stock first. Then you need to root the phone. Then You need to follow the steps in the guide here http://forum.xda-developers.com/showthread.php?t=1202883 or here http://forum.xda-developers.com/showthread.php?t=1182871 (the second one I used recently). Once you've done that stuff THEN you can flash cm thru recovery. Hope you didn't hard brick.
Click to expand...
Click to collapse
Thanks for your help, but could you be more specific on how to do all of that? As you can tell, I'm (quite obviously) a noob at this.
Also: I downloaded a file called 1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012 , which is supposed to be the stock ROM. But when I run RSD, it gives me the error "Failed Flashing Process: Unable to retrieve interface handle (0x7027)
EDIT:: Your second link worked! Thank you very much!
Don't worry about it, it is common. All you need is the small unlock RSD file for your device found in post # 1136261 and the attempted flash that fails in the step that you described. Then you need to move on to the next step in the process. You need to get the phone into fastboot though, by holding the volume down key during the boot up / or if you get that crazy menu with options 0 though 9, use the volume up and down to select fastboot. Then on the PC continue with the process:
fastboot oem unlock
Then when that is successful, flash recovery.img or whatever recovery you have downloaded:
fastboot flash recovery recovery.img
Sent from my MB860 using Tapatalk 2
MCDong said:
Thanks for your help, but could you be more specific on how to do all of that? As you can tell, I'm (quite obviously) a noob at this.
Also: I downloaded a file called 1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012 , which is supposed to be the stock ROM. But when I run RSD, it gives me the error "Failed Flashing Process: Unable to retrieve interface handle (0x7027)
EDIT:: Your second link worked! Thank you very much!
Click to expand...
Click to collapse
You're welcome!
I was on 4.0.3 and I flashed the zip through AromRa recovery.
Now, when booting up, its stuck at the 4G screen.
The update was the OTA update released to update radios to Global. THIS
It didn't gave any error at all, it said "Reboot to complete installation or update". But when I clicked the reboot option, I saw a line saying something like "Can't write....." then the screen went off and it rebooted. This line was not there, or atleast not visible before I clicked the reboot option.
I am new to rezound and android, so please let me know what I can do. I wasn't able to get a nandroid backup before doing this, had no ext. SD card.
All I did before flashing the zip was flashing the custom recovery. Nothing else. No SU or anything else.
Can I RUU 4.0.3 to fix this problem?
Yes you need to ruu to get it back. I'm assuming your s on. You need to be s off in order to flash radios by themselves.
Sent from my ADR6425LVW using xda app-developers app
Yes, I am s-on and not rooted.
Is there any specific RUU that I should go to? I was thinking of using 4.03.605.2
Thanks
lamborg said:
Yes, I am s-on and not rooted.
Is there any specific RUU that I should go to? I was thinking of using 4.03.605.2
Thanks
Click to expand...
Click to collapse
Yes, that's the latest global RUU.
You need to relock to run it:
fastboot oem lock
Put it on your sd card and it should do it's thing when you reboot. Run it a couple times and make sure it's finished so it will get all the system files. I believe it reboots you once it's done.
Then you can unlock again, flash recovery and root. If you have trouble rooting again search this forum for "super su" and you'll find a version you can flash to gain root.
feralicious said:
Yes, that's the latest global RUU.
You need to relock to run it:
fastboot oem lock
Put it on your sd card and it should do it's thing when you reboot. Run it a couple times and make sure it's finished so it will get all the system files. I believe it reboots you once it's done.
Then you can unlock again, flash recovery and root. If you have trouble rooting again search this forum for "super su" and you'll find a version you can flash to gain root.
Click to expand...
Click to collapse
I relocked but then tried flashing the zip twice.
Here's what comes in cmd:
sending....
OKAY
writing
<bootloader>adopting sig ....
<bootloader>checking sig
failed <remote: not allowed>
finished
After rebooting, it gets stuck on the white HTC screen.
sounds like a bad download, go back to android police and try to get the mirror from Illinois, it worked for me a couple of weeks ago after having the same issue as you.
sent from my rooted SAMSUNG GALAXY NOTE 2...
mike7728 said:
sounds like a bad download, go back to android police and try to get the mirror from Illinois, it worked for me a couple of weeks ago after having the same issue as you.
sent from my rooted SAMSUNG GALAXY NOTE 2...
Click to expand...
Click to collapse
Thanks mike.
I downloaded the same RUU from a different source and flashed it. But the same failed remote not allowed error.
1 question.
In adb, do I need to type the command fastboot flash zip PH98IMG.zip in the hboot (with otions fastboot, recovery, clear storage, simlock, image crc) or after selecting the fastboot option at the hboot screen?
I am asking because nothing happens when I put the command while on the hboot screen and I get the remote error when commanded from the fastboot screen.
lamborg said:
Thanks mike.
I downloaded the same RUU from a different source and flashed it. But the same failed remote not allowed error.
1 question.
In adb, do I need to type the command fastboot flash zip PH98IMG.zip in the hboot (with otions fastboot, recovery, clear storage, simlock, image crc) or after selecting the fastboot option at the hboot screen?
I am asking because nothing happens when I put the command while on the hboot screen and I get the remote error when commanded from the fastboot screen.
Click to expand...
Click to collapse
You have to fastboot oem rebootRUU first
then fastboot flash zip PH98IMG.zip
you may have to flash the zip twice.
Code:
androidforums.com/incredible-all-things-root/487280-easier-way-flash-pb31img-files.html
(I can't link yet)
lamborg said:
Thanks mike.
I downloaded the same RUU from a different source and flashed it. But the same failed remote not allowed error.
1 question.
In adb, do I need to type the command fastboot flash zip PH98IMG.zip in the hboot (with otions fastboot, recovery, clear storage, simlock, image crc) or after selecting the fastboot option at the hboot screen?
I am asking because nothing happens when I put the command while on the hboot screen and I get the remote error when commanded from the fastboot screen.
Click to expand...
Click to collapse
You don't flash this in fastboot since it's a zip file.
EDIT: Looks like you can flash in fastboot as mentioned in the above post. Cool, I like that. I would flash it twice as I've read several times that you need to to make sure it gets all the system files.
If htat doesn't work for whatever reason, just put it on the sd card of your phone, detach your phone from your pc and reboot. hboot should find it (it looks for the PH98IMG.zip file) and flash it. Flash it twice to be sure it gets all the system files.
When it's done and you're rebooted use a file explorer and delete the PH98IMG file so it doesn't flash again on the next reboot.
I am new to cell phone mods. My goal was to gain some experience by rooting and replacing the os image on my Atrix 4G. I use it for my alarm clock which uses an application that won't run on newer version of android than v2.x.x. I successfully rooted and installed super use. I then installed Titanium Backup and did a full backup to sdcard. I installed Rom Manager, chose ClockworkMod Recovery and then the correct image, and told it to flash the recovery partition. Rebooted. Got an error with the android logo and a circle with a triangle. Went back to all the how to's and attempted to install unlockable_bootloader. It now comes up to rsd, seems to fail, then goes into fastboot. Fastboot devices sees it and I can reboot from fastboot but it goes back to the same place. HELP.
Forget about any and all automatic methods, including ROM manager and similar. Good old-fashioned manual methods work best.
Try this guide. http://forum.xda-developers.com/showthread.php?t=2262869
ravilov said:
Forget about any and all automatic methods, including ROM manager and similar. Good old-fashioned manual methods work best.
Click to expand...
Click to collapse
I think I have read all the posts and how to's on manually flashing. Temporarily recovered but persued my goal of learning something. Only thing it can do now is fastboot when I hold the volume key UP while restarting. Used to be down but that's gone. RSD protocol is no more. Says "Failed to boot 1" when restarting. Something I flashed apparently relocked the boot loader and who knows what else I've screwed up. Fastboot -w indicates it cas erase the cache and userdata partitions. Surely there is still hope for this as I can still access fastboot. Can you give a little help please?
Phatdaddy said:
I think I have read all the posts and how to's on manually flashing. Temporarily recovered but persued my goal of learning something. Only thing it can do now is fastboot when I hold the volume key UP while restarting. Used to be down but that's gone. RSD protocol is no more. Says "Failed to boot 1" when restarting. Something I flashed apparently relocked the boot loader and who knows what else I've screwed up. Fastboot -w indicates it cas erase the cache and userdata partitions. Surely there is still hope for this as I can still access fastboot. Can you give a little help please?
Click to expand...
Click to collapse
Ỳou need to download the image of the recovery partition and flash it using fastboot flash recovery recovery.img
flash recovery failed
andresrivas said:
Ỳou need to download the image of the recovery partition and flash it using fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I previously found a thread that described that process and tried it. Fastboot reported it failed flashing recovery.
That usually happens if the BL is not unlocked (properly).
Phatdaddy said:
I think I have read all the posts and how to's on manually flashing. Temporarily recovered but persued my goal of learning something. Only thing it can do now is fastboot when I hold the volume key UP while restarting. Used to be down but that's gone. RSD protocol is no more. Says "Failed to boot 1" when restarting. Something I flashed apparently relocked the boot loader and who knows what else I've screwed up. Fastboot -w indicates it cas erase the cache and userdata partitions. Surely there is still hope for this as I can still access fastboot. Can you give a little help please?
Click to expand...
Click to collapse
reflash the pudding sbf to unlock the bl, then go ahead and flash recovery as advised. if I remember correctly, when it says failed to boot 1, its automatically in rsd, which means just hook it up and let rsd lite do its job then fastboot for recovery
flash boot failed
palmbeach05 said:
reflash the pudding sbf to unlock the bl, th
en go ahead and flash recovery as advised. if I remember correctly, when it says failed to boot 1, its automatically in rsd, which means just hook it up and let rsd lite do its job then fastboot for recovery
Click to expand...
Click to collapse
Installed pudding successfully with RSD Lite. Attempted to flash recovery with "fastboot flash recovery image_name". Reports "sending recovery" and then "writing recovery". When I reboot, it still has has the stock recovery utility.Otherwise, I'm back to stock 2.3.6 except that it reports unlocked upon rebooting. Am I not flashing the correct thing? Thanks for the pointers.
Phatdaddy said:
Installed pudding successfully with RSD Lite. Attempted to flash recovery with "fastboot flash recovery image_name". Reports "sending recovery" and then "writing recovery". When I reboot, it still has has the stock recovery utility.Otherwise, I'm back to stock 2.3.6 except that it reports unlocked upon rebooting. Am I not flashing the correct thing? Thanks for the pointers.
Click to expand...
Click to collapse
hmm, sounds like you're on the 145 build of 2.3.6. Check to see what your phone says in about phone. its going to give you a system version ending in 141 or 145.
palmbeach05 said:
hmm, sounds like you're on the 145 build of 2.3.6. Check to see what your phone says in about phone. its going to give you a system version ending in 141 or 145.
Click to expand...
Click to collapse
This one says "4.5.141". Before undertaking to hack this piece, it was 4.5.145. I have flashed preinstall and boot and attempted to flash recovery. I don't know where it stores the build number. Could it be reporting .141 while really .145 ? I am confident the .145 is correct because we have two phones purchased the same day from same vendor and the other reports .145. I also remember it as .145 but my memory is pretty faulty.
Phatdaddy said:
This one says "4.5.141". Before undertaking to hack this piece, it was 4.5.145. I have flashed preinstall and boot and attempted to flash recovery. I don't know where it stores the build number. Could it be reporting .141 while really .145 ? I am confident the .145 is correct because we have two phones purchased the same day from same vendor and the other reports .145. I also remember it as .145 but my memory is pretty faulty.
Click to expand...
Click to collapse
ok. I think the file we need to look for in order to fix this is in system/etc. its called install-recovery.sh and that file forces stock recovery to be installed. delete that file and try flashing the custom recovery.
palmbeach05 said:
ok. I think the file we need to look for in order to fix this is in system/etc. its called install-recovery.sh and that file forces stock recovery to be installed. delete that file and try flashing the custom recovery.
Click to expand...
Click to collapse
ls of /system/etc/install-recovery.sh says the file does not exist.
When I bricked my atrix i used the xatrix tool to unbrick it. works really well and once unbricked was fully unlocked so was easy to flash new roms
xatrix (dot) webs (dot) com
once on there website click to download tab to get the downloads
This tool will remove everything from phone root, unlock and install cwm. What you do after that is upto you. sometimes its easier to start over then figure out what went wrong when installing a mod.
My problem is now this, I'm recovered, rooted, and unlocked. If I flash recovery with fastboot, it says I am successful but when I reboot the original recovery image still exists.
And thats the part that confuses me. It says 141, but the recovery issue is acting like its a 145. I'm stumped, but i do believe there is an install-recovery.sh script or something thats preventing this thing from sticking after flashing. I'm really baffled by this b/c i ran 141 for the longest time, i did all my rooting, unlocking, and recovery flashing on 141, and got no issues. I could advise that you download and flash the ICS leak (the true leak, not the ROMs we have available) via fastboot and see if that changes the situation, but i don't want to advise you to do something and then a bigger mess appears.
Sent from my MB886 using xda app-developers app
Phatdaddy said:
My problem is now this, I'm recovered, rooted, and unlocked. If I flash recovery with fastboot, it says I am successful but when I reboot the original recovery image still exists.
Click to expand...
Click to collapse
sounds like you had 145 installed and flashed 141 over it without doing a wipe first. i would use cwm recovery and do a factory reset wipe all data and flash the rom you want to run.
overboard1978 said:
sounds like you had 145 installed and flashed 141 over it without doing a wipe first. i would use cwm recovery and do a factory reset wipe all data and flash the rom you want to run.
Click to expand...
Click to collapse
he can't get cwm installed. it may say it gets flashed correctly, but he cannot get cwm to show up and be usable.
as a work around, via fastboot, run the commands:
fastboot erase data
fastboot erase cache
that would cover what factory reset does.
palmbeach05 said:
he can't get cwm installed. it may say it gets flashed correctly, but he cannot get cwm to show up and be usable.
as a work around, via fastboot, run the commands:
fastboot erase data
fastboot erase cache
that would cover what factory reset does.
Click to expand...
Click to collapse
That should do it. If for some reason it doesnt the xatrix tool will wipe everything off the phone and start it over with 141 unlocked bootloader, with cwm. Only automated tool i found that will unbrick phone with rsd lite. Make sure phone is fully charged before starting xatrix tool as it wipes battery fast and if it dies you will need to start over.
Erase cashe was successful, erase data failed. Found reference to additional file to delete but it did not exist either. If I conttinue, I will repost. Thanks for everyone's effort trying to get this working.
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.
I was in the process of returning my dna to stock so that I could sell it. I performed the OEM lock function which resulted in my bootloader screen looking what what is in the attached picture. After this I attempted multiple, multiple times to install the RUU.exe on my Mac Mini running Windows 7 in bootcamp mode (not virtualization). Each time it popped up an error saying that it couldn't install. At this point, even after flashing the 1.15 hboot I'm still mostly stuck int he bootloader. My operating system no longer boots. I really only have fastboot access and no idea how to get out of this situation.
I've tried to flash a custom recovery so that at least I could flash a rom, but whenever I try to fastboot it over I get an error saying "FAILED <remote: not allowed>". So if I can't flash a recovery ROM, and I can unlock my bootloader again, and I can't boot into a ROM, what can I do. I spent the last 6 hours trying to find an answer and I'm totally out of options now.
doctajay said:
I was in the process of returning my dna to stock so that I could sell it. I performed the OEM lock function which resulted in my bootloader screen looking what what is in the attached picture. After this I attempted multiple, multiple times to install the RUU.exe on my Mac Mini running Windows 7 in bootcamp mode (not virtualization). Each time it popped up an error saying that it couldn't install. At this point, even after flashing the 1.15 hboot I'm still mostly stuck int he bootloader. My operating system no longer boots. I really only have fastboot access and no idea how to get out of this situation.
I've tried to flash a custom recovery so that at least I could flash a rom, but whenever I try to fastboot it over I get an error saying "FAILED <remote: not allowed>". So if I can't flash a recovery ROM, and I can unlock my bootloader again, and I can't boot into a ROM, what can I do. I spent the last 6 hours trying to find an answer and I'm totally out of options now.
Click to expand...
Click to collapse
You need to unlock again in order to flash back a custom recovery. You also need to have the stock splash screen before you ruu. Had the exact same issue you had. Stock h-boot, stock splash screen and relock and all should be good.
That is my main problem. All of the unlock methods require me to load load an apk to change the CID. I can't do that in fastboot. Is there another unlock method I'm missing that allows you to do it from the fast boot mode?
Sent from my LG-D800 using Tapatalk
if u have your original unlock code from htc dev I think u can fastboot flash that code to unlock again. its in the forum somewhere just not sure where it is.
try this thread, good luck
http://forum.xda-developers.com/showthread.php?t=2160677
You don't have to run a apk to change the cid just Google change cid commands, you do it through adb change it to 22222222 then redo the HTC dev to get your unlock.bin again if u don't have it.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
doctajay said:
I was in the process of returning my dna to stock so that I could sell it. I performed the OEM lock function which resulted in my bootloader screen looking what what is in the attached picture. After this I attempted multiple, multiple times to install the RUU.exe on my Mac Mini running Windows 7 in bootcamp mode (not virtualization). Each time it popped up an error saying that it couldn't install. At this point, even after flashing the 1.15 hboot I'm still mostly stuck int he bootloader. My operating system no longer boots. I really only have fastboot access and no idea how to get out of this situation.
I've tried to flash a custom recovery so that at least I could flash a rom, but whenever I try to fastboot it over I get an error saying "FAILED <remote: not allowed>". So if I can't flash a recovery ROM, and I can unlock my bootloader again, and I can't boot into a ROM, what can I do. I spent the last 6 hours trying to find an answer and I'm totally out of options now.
Click to expand...
Click to collapse
You device most likely can't downgrade due to having a locked device. Have you tried flashing the 2.07 ruu
Thank you for all of the replies. Actually the change of the CID command might have worked but I didn't see that reply before I had tried another method found in this thread: http://forum.xda-developers.com/showthread.php?t=2570548.
I was truly stuck in fastboot and couldn't flash a custom recovery at all. Well I used the advice from a previous thread and edited the firmware .zip posted in the first post of this thread: http://forum.xda-developers.com/showthread.php?t=2314771. I had initially tried to flash the .zip posted but when I tried to boot into the recovery it wouldn't work. So I opened the .zip file without extracting it and removed the recovery.img from the .zip, I then took the TWRP custom recovery and inserted it into the .zip (if you extract the zip this will not work; you need to use software that can edit a zip without extracting it. On the Mac, which I was using, I used Spring). I renamed the TWRP recovery to "recovery.img" to match what I had previously deleted.
Then I flashed this edited firmware.zip by using the following command in usb fastboot mode (here's the link for my edited file):
fastboot oem rebootRUU
fastboot flash zip YOUREDITEDFILE.zip
fastboot reboot
This then allowed me to boot into recovery. I thought I had figured it out and could now sideload a ROM using the "adb sideload" command and flash some type of ROM that would boot. This failed miserably; it would allow me to push the file, but the install would always fail before it completed.
So then I found this thread here: http://forum.xda-developers.com/showthread.php?t=2570548. I first flashed the two .zip files that were posted in post #44. then I flashed the full RUU posted in post #1. This gave me a bootable stock ROM. Praise God!!!
Finally I went back to this thread: http://forum.xda-developers.com/showthread.php?t=2293919, and flashed the following code.
Code:
adb devices (your device should be listed)
adb reboot bootloader
fastboot devices (your device should be listed)
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
Not sure why I had such a terrible time, but I'm glad its over and the DNA is finally sold. Thank you for all your help!
trying to restore my dna back to stock
I got my dna locked again and now I am running the ruu file and i am stuck at 6%. Can someone help please!! Tried it by double clicking the ruu file and running it like that, and i also ran it in administration and both ways i am stuck at 6%