Related
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.
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 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%
Basically, I need the 4.4.2 OTA.
I unlocked the bootloader. I need root to get S-off. Except I'm currently on S-on and the only way to install a recovery and get root is to have S-off (correct me if I'm wrong). Any workaround to this that isn't super complicated?
I've checked USB ports, and I can't seem to get my device to be recognized. "fastboot devices" shows up nothing. Currently unlocked, and S-on.
Forgot that unlocking bootloader again would wipe my phone, forgot to make backup, so everything's deleted ;(. Not possible to get s-off anymore?
Any help would be appreciated.
mch277 said:
Basically, I need the 4.4.2 OTA.
I unlocked the bootloader. I need root to get S-off. Except I'm currently on S-on and the only way to install a recovery and get root is to have S-off (correct me if I'm wrong). Any workaround to this that isn't super complicated?
I've checked USB ports, and I can't seem to get my device to be recognized. "fastboot devices" shows up nothing. Currently unlocked, and S-on.
Forgot that unlocking bootloader again would wipe my phone, forgot to make backup, so everything's deleted ;(. Not possible to get s-off anymore?
Any help would be appreciated.
Click to expand...
Click to collapse
You just need an unlocked bootloader to install a recovery, when you are in fastboot (if you turn the phone on and do adb reboot fastboot, or hold down vol down and power and select fastboot when the HBOOT menu comes up) you can do the command line fastboot flash recovery recovery.img (recovery.img being your recovery you want to load) you can then start the phone up, copy superuser.zip on there somewhere and install with your custom recovery.
All that said, you don't need to do any of that to do 4.4.2 OTA, and in fact it wont install if you have a custom recovery. Are you having a problem that it wont download/install. If your phone is stock other than an unlocked bootloader it will install (trust me i just did it). If you have stock recovery just download the 4.4.2 OTA file from the other thread, then save it to the phone somewhere, the go to recovery in HBOOT, wait 1 second and then hold up vol and power for 5 seconds (may have to do this more than once). Menu comes up, do wipe cache, and then do install from device storage.
After thats done you can follow my above instructions and root it
Sorry if I didn't state it more clearly, but my issue is I can't install a recovery. I can boot into bootloader and fastboot but when I type in "fastboot" devices on my PC nothing comes up.
mch277 said:
Sorry if I didn't state it more clearly, but my issue is I can't install a recovery. I can boot into bootloader and fastboot but when I type in "fastboot" devices on my PC nothing comes up.
Click to expand...
Click to collapse
Have you installed HTC Sync? When you boot into the bootloader then fastboot and then plug in your usb cable does it say "fastboot usb" on screen?
Rogue Leader said:
Have you installed HTC Sync? When you boot into the bootloader then fastboot and then plug in your usb cable does it say "fastboot usb" on screen?
Click to expand...
Click to collapse
I uninstalled HTC sync so as to not have it interfere with any s-off/etc. programs. I still have HTC drivers installed. Re-install both HTC sync and drivers?
mch277 said:
I uninstalled HTC sync so as to not have it interfere with any s-off/etc. programs. I still have HTC drivers installed. Re-install both HTC sync and drivers?
Click to expand...
Click to collapse
HTC Sync won't interfere with anything. You need that and the drivers installed for it to work, I would start there and see what happens.
I'll re-install it again.
Is there anything I can do to just completely get back to stock everything? Willing to manually update it but I'd like to be able to just go to settings and just update via OTA from there.
mch277 said:
I'll re-install it again.
Is there anything I can do to just completely get back to stock everything? Willing to manually update it but I'd like to be able to just go to settings and just update via OTA from there.
Click to expand...
Click to collapse
As long as you have an active AT&T SIM card in there it will update even with an unlocked bootloader, even if its rooted. As long as you didn't mod anything. I just did the update like this, it worked fine.
I've rooted and unlocked the bootloader before but I've unrooted since then. Is there still a chance I just haven't gotten the update pushed to my device yet?
mch277 said:
I've rooted and unlocked the bootloader before but I've unrooted since then. Is there still a chance I just haven't gotten the update pushed to my device yet?
Click to expand...
Click to collapse
here's the OTAPkg.zip with instructions
http://forum.xda-developers.com/showthread.php?t=2659374
clsA said:
here's the OTAPkg.zip with instructions
http://forum.xda-developers.com/showthread.php?t=2659374
Click to expand...
Click to collapse
Thanks. I have that file all ready to go in my folder. Only problem I have now is that I can't get s-off. I've installed recovery + custom kernel but the su binaries are outdated for both superSU and superuser. I've tried to flash a 4.3 version of superSU only to have the same error.
I followed instructions for root after I flashed a super tool I also flashed a custom kernel. After I rebooted is where I started to get the "outdated binaries" prompts.
mch277 said:
Thanks. I have that file all ready to go in my folder. Only problem I have now is that I can't get s-off. I've installed recovery + custom kernel but the su binaries are outdated for both superSU and superuser. I've tried to flash a 4.3 version of superSU only to have the same error.
I followed instructions for root after I flashed a super tool I also flashed a custom kernel. After I rebooted is where I started to get the "outdated binaries" prompts.
Click to expand...
Click to collapse
Ok that changes things. IMO you need to backup your data, install the 4.3 RUU to wipe everything out and make sure you have stock recovery, then you can install the OTA zip from stock recovery, or go ahead and download it direct from AT&T. You can then root and go from there. Now as for S-Off if you have HBOOT 1.55 or newer I don't think you can get it. I can't get it on mine I tried every way possible. You don't need S-Off for this to work
So I am a first time rooter, so I'll try my best to use the proper terms and whatnot.
Anyways, I have an unlocked HTC One X+ that I am trying to root. I was using the AIO kit by Hasoon2000. I had my bootloader successfully unlocked, and so I proceeded to continue with rooting. I thought I pushed the SuperSU.zip to the device, because the cmd line said it was successful. So I booted into recovery mode, made a backup, and then when to flash the SuperSU.zip file. However, I could not find it in the file explorer in recovery mode.. so I went to push the file to the phone again, but now it says device not found. The only thing I can think that's happened is my USB debugging got turned off... which is bad. So is SuperSU.zip in my phone somewhere, or am I stuck with a phone that can only go into recovery mode?
Thanks for any help!
I have now similar problem too...
actually I had rooted successfully, but after many failed CM11 installation attempts, I decided to relock the bootloader, in order to update the Firmware. But it didn't work too and I came the way back again, in which I unlocked the bootloader with Unlock Token etc. again. Now the bootloader is unlocked but apparently not rooted!?! I can't push superuser via adb because **Device is not found** and I can only go to TWRP Recovery and bootloader...
COULD SOMEONE HELP??!
PS: when i press the reboot in TWRP, it says that "the phone seems not to be rooted, do you want to install the SuperUser? and when I accept it... it reboots only and nothing does change!
well... im not sure what I did differently but it finally recignized the device!! And now I managed to get everything installed... weird!