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.
Hi
I'm in the process of recovering a bricked Photon 4G. Not sure There's a chance to actually succeed.
I managed to gain root. But then accidentally used "Atrix2Bootstrap" to unlock the bootloader.
After restarting the phone got stuck on the dual core screen.
I tried entering cold boot, recovery mode for a factory reset and unlocking fastboot as described here :http://forum.xda-developers.com/showthread.php?t=1573727.
Then I tried recovery via rsd lite following this guide:
http://forum.xda-developers.com/showthread.php?t=1202666
But got the following error:
Flash failure: Phone[0000]: Error sending RAM download for bootloader.
Is there a way to recover the phone with fastboot? Or any other method?
thanks.
p.s
The phone had the most recent update installed : OTA 45.4.13.MB855
edit:
solved thanks to acvice's post and the battery trick which for unknown reasons was the only way to enter bootstrap recovery
(install bootstrap recovery, shutdown, remove battery for a minute, insert battery, plug to wall and boot normally).
You can not unlock, if you are on the latest OTA.
Follow this thread to unbrick your device, thats the inly way.
http://forum.xda-developers.com/showthread.php?t=1798145
peetr_ said:
This will recover from brick, when you are permanently locked on Photon after 2.3.5 OTA update.
Take USC_19 full sbf from 2.3.5 sv2 custom sbf thread, flash that, wipe data in recovery, root it, install bootstrap recovery.
After that, you can flash mof 2.3.5ish rom or my rom (locked).
Then install bootstrap recovery again, if it's not preinstalled there. And flash 254_13 modules. After that flash 2.3.5sv2 unbrick sbf with 254_13 boot, recovery and cdrom. If you have no radio service, flash 254_12 libmoto_ril.so.
Click to expand...
Click to collapse
Did someone say copypasta?!
I believe this will fix you.
Your input looks very promising.
I'll check it out.
Edit:
2.3.5_USC_19 sbf is still downloading. In the meanwhile I tried flashing the smaller "2.3.5_254_13 sv2 boot, recovery and cdrom image sbf"
and get the same error as before:
Failed flashing process. Failed flashing process. Phone[0000]: Error sending RAM download for bootloader. Device API Error: 0xE0030009 Command: ADDR (0xE0231009); Phone connected.
Is this a side effect from using the atrix2bootstrap app. Or maybe because i'm running win 7 64bit?
vrid said:
Your input looks very promising.
I'll check it out.
Edit:
2.3.5_USC_19 sbf is still downloading. In the meanwhile I tried flashing the smaller "2.3.5_254_13 sv2 boot, recovery and cdrom image sbf"
and get the same error as before:
Failed flashing process. Failed flashing process. Phone[0000]: Error sending RAM download for bootloader. Device API Error: 0xE0030009 Command: ADDR (0xE0231009); Phone connected.
Is this a side effect from using the atrix2bootstrap app. Or maybe because i'm running win 7 64bit?
Click to expand...
Click to collapse
You havta follow the instructions in order. Flash the sbf with rsdlite first =) Make sure you have the motorola 64bit windows drivers installed.
Acvice said:
You havta follow the instructions in order. Flash the sbf with rsdlite first =) Make sure you have the motorola 64bit windows drivers installed.
Click to expand...
Click to collapse
thanks, your were right, although the flash process got interrupted it was enough for the phone to boot up.
It now thinks it's an electrify.
I managed to root using photon-torpedo but the bootstrap recovery isn't working. It says "install success" but refuses to reboot into the bootstrap recovery mode. It just shuts down and when i manually boot it up it goes back to android.
any thoughts?
(small detail for others who are also stuck, I did the flash from a 32bit XP box. Not sure flashing from 7 64bit wouldn't work because i didn't try it)
vrid said:
thanks, your were right, although the flash process got interrupted it was enough for the phone to boot up.
It now thinks it's an electrify.
I managed to root using photon-torpedo but the bootstrap recovery isn't working. It says "install success" but refuses to reboot into the bootstrap recovery mode. It just shuts down and when i manually boot it up it goes back to android.
any thoughts?
(small detail for others who are also stuck, I did the flash from a 32bit XP box. Not sure flashing from 7 64bit wouldn't work because i didn't try it)
Click to expand...
Click to collapse
Making progress! It shouldnt boot directly to recovery. Youll havta do the hold vol down and power while booting up then scroll dow to android recovery using vol down and vol up to select.
And what do you mean the flash got interrupted?
vrid said:
thanks, your were right, although the flash process got interrupted it was enough for the phone to boot up.
It now thinks it's an electrify.
I managed to root using photon-torpedo but the bootstrap recovery isn't working. It says "install success" but refuses to reboot into the bootstrap recovery mode. It just shuts down and when i manually boot it up it goes back to android.
any thoughts?
(small detail for others who are also stuck, I did the flash from a 32bit XP box. Not sure flashing from 7 64bit wouldn't work because i didn't try it)
Click to expand...
Click to collapse
If you hav installed bootstrap & you press recovery mode, be sure phone is connected to wall charger.....
then only you would go in recovery mode....
Cooldevil1989 said:
If you hav installed bootstrap & you press recovery mode, be sure phone is connected to wall charger.....
then only you would go in recovery mode....
Click to expand...
Click to collapse
It was connected to the wall. I did boot into recovery manualy but found the standard recovery. not the installed bootstrap recovery.
When bootstrap recovery installed it stated "su binaries outdated" so i'm guessing that might be in indicator.
@ acvice. the error message :
"Failed flashing process. Interface BP: Error sending JUMP command Device API Error: 0xE003003F Address: 0x800000 Command: Jump (0xE053203F); phone connected
edit:
I updated the su binaries but still no bootstrap recovery. tried manualy entering recovery as well...
any alternate bootstrap recovery methods i could try?
First of all, tell me how u access recovery mode....???
Don't use power button to access recovery...
Sent from my MB855 using xda app-developers app
Cooldevil1989 said:
First of all, tell me how u access recovery mode....???
Don't use power button to access recovery...
Click to expand...
Click to collapse
well i boot up the phone by pressing the power and volume down buttons. Then scroll to recovery and press volume up.
How else should i enter recovery mode? after i install bootstrap and press recovery mode the phone simply shuts down without restarting by itself.
When u press recovery mode in boot strap recovery remember wall charger must be connected to phone... then only u will boot into recovery. ...
Sent from my MB855 using xda app-developers app
update:
The phone entered bootstrap recovery.
I pressed install. after the success message i simply returned to the home screen and let the battery die.
then i connected the phone to the wall and turned it on only pressing on the power button (no combinations).
then the bootstrap recovery screen finally showed.
so now i managed to flash MOF 2.3.5.ish v1.4.
I guess this is solved...
thank you for the replies and help.
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!
FINAL EDIT: My problem has been solved. I kept trying the RUU.exe method over and over until it finally worked (more info in my last reply).
EDIT: My only issue now is that I cannot select "Mount data" in the Mount menu within TWRP recovery. Also, even when I have "mount system" and "mount cache" selected, I get an "Unable to mount system" or "Unable to mount cache" when I try to factory reset, wipe cache, install a ROM, or sideload ADB a ROM
Hello everyone. After recently purchasing an HTC DNA, I used the "HTC Droid DNA AIO Kit" to unlock the bootloader (HTCDev + unlock code), root the phone, and load TWRP recovery. From the recovery menu, I flashed the Viper custom ROM. I noticed some wifi problems, so I wanted to go back to stock to see if the problem (couldn't connect to wifi) was still there. The dumbass that I am used the "Wipe System" ("This will wipe your ROM") option within the recovery hoping it would boot back into stock. Obviously that didn't work (and has started me down a horrible path to bricking). I tried re-flashing the viper ROM, and half way through the setup it would reboot and stick on a white "HTC" screen. Every time. I googled and tried the RUU.exe method and got 155 error "Wrong RUU version" or whatever. I tried flashing the RUU.zip stock ROM using the All-in-one kit. No luck (error in command prompt saying "too many links"). I don't know what to do I just need to get back to Stock ROM, or anything similar that can help fix my situation. I appreciate all of your technical expertise and any help you give! I can provide more information about my phone and setup and version and such. I realize many of you will cringe at my methods, and I apologize for all of my stupid errors.
Mcsquizzy said:
Hello everyone. After recently purchasing an HTC DNA, I used the "HTC Droid DNA AIO Kit" to unlock the bootloader (HTCDev + unlock code), root the phone, and load TWRP recovery. From the recovery menu, I flashed the Viper custom ROM. I noticed some wifi problems, so I wanted to go back to stock to see if the problem (couldn't connect to wifi) was still there. The dumbass that I am used the "Wipe System" ("This will wipe your ROM") option within the recovery hoping it would boot back into stock. Obviously that didn't work (and has started me down a horrible path to bricking). I tried re-flashing the viper ROM, and half way through the setup it would reboot and stick on a white "HTC" screen. Every time. I googled and tried the RUU.exe method and got 155 error "Wrong RUU version" or whatever. I tried flashing the RUU.zip stock ROM using the All-in-one kit. No luck (error in command prompt saying "too many links"). I don't know what to do I just need to get back to Stock ROM, or anything similar that can help fix my situation. I appreciate all of your technical expertise and any help you give! I can provide more information about my phone and setup and version and such. I realize many of you will cringe at my methods, and I apologize for all of my stupid errors.
Click to expand...
Click to collapse
did you do flash boot.img image file before the rom? if not, flashing that then reloading your desired rom might get you back.
if you can still get to recovery you can use the sideload option and try flashing a rom that doesn't use the aroma installer.. there are a couple stock roms in the development section.
I flashed a boot.img using flash gui from playstore. Ended up disabling my WiFi. I can only use LTE now . I'm on stock right now. Any ideas?
Sent from my HTC6435LVW using xda app-developers app
In order to run the RUU you must be locked. Relock and give it a try.
D
.
dj2muchxx said:
I flashed a boot.img using flash gui from playstore. Ended up disabling my WiFi. I can only use LTE now . I'm on stock right now. Any ideas?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
If the kernel you flashed also came with it's modules.zip then you have to also install the modules .zip file from recovery. If the kernel came with the rom then the modules are probably already installed with the rom.
To flash the kernal manually (which is more reliable) use the following command:
fastboot.exe flash boot boot.img
make sure the boot.img is located in the same folder as the fastboot.exe file.
If you're on Windows 7 you can hold the SHIFT key and right click while in the folder containing fastboot.exe and select "Open command prompt here" to make sure you are in the right folder in the command window. Not sure which other versions of Windows lets you use that shortcut.
DSB is also correct that you have to lock the bootloader if you want to use RUU.
I think the bootloader lock command is (must be at bootloader):
fastboot.exe oem lock
rootntootn said:
did you do flash boot.img image file before the rom? if not, flashing that then reloading your desired rom might get you back.
Click to expand...
Click to collapse
Thank you for the reply. I used the HTC Droid DNA All-in-one program to flash a stock boot.img file BEFORE flashing the ROM. No luck. I have since been able to adb push a stock ROM, but when I try to wipe the cache or install the ROM.zip file using the recovery (TWRP) I get a "Unable to mount /data". When I go into Mount settings within the recovery, I am unable to select "Mount data". I can only check "Mount system" and "Mount cache". Any ideas?
Also, I did relock the bootloader (It says "***Tampered*** ***Relocked***) using the same All-in-one tool. I have also tried flashing Clockwork recovery, but I get stuck on the "HTC This is only for development purposes legal blah" white screen, so I have reflashed TWRP. I ran both the RUU.exe (relocked bootloader), and tried flashing the RUU.zip method. Thoughts?
I will try doing all of my previous methods manually (through command prompt, without the All-in-one tool) when I get home (as you said, it is more reliable).
Thank you so much for the help you guys!
dj2muchxx said:
I flashed a boot.img using flash gui from playstore. Ended up disabling my WiFi. I can only use LTE now . I'm on stock right now. Any ideas?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
If you are flashing stock RUU -the bootloader has to be relocked for it to work....
In general each rom other than that usually has it's own boot image which has to be loaded first before the rom is. Usually downloadable from where the rom is. The one click varieties have not worked so well for me. so I agree with using the adb command version-more involved but reliable...
lazarus2297 said:
if you can still get to recovery you can use the sideload option and try flashing a rom that doesn't use the aroma installer.. there are a couple stock roms in the development section.
Click to expand...
Click to collapse
I tried the ADB sideload option within recovery, but I get a message saynig "Unable to mount '/data'". I also get this message after trying to install a ROM through recovery. When I try to select "Mount data" in the Mount menu of the TWRP recovery, I am unable to check the box. I can only check "Mount system" and "Mount cache". This is the only hangup right now. I have the bootloader unlocked, and I have flashed the boot.img (the stock version), but I cannot install or ADB sideload any ROMs because of the "Unable to mount '/data'" message Any ideas?
Why not just fasbtboot the boot.img then boot into recovery and adb push romname.zip and then flash the zip?
Sorry...read your post backwards.
Dude...just relock and ruu
Btw...anyone have a ruu in zip format?
Like a PH98IMG.zip as an example..that file name correlates with the rezound nut ya know what I mean??
Sent from my HTC6435LVW using xda premium
andrewp3481 said:
Why not just fasbtboot the boot.img then boot into recovery and adb push romname.zip and then flash the zip?
Sorry...read your post backwards.
Dude...just relock and ruu
Btw...anyone have a ruu in zip format?
Like a PH98IMG.zip as an example..that file name correlates with the rezound nut ya know what I mean??
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
I have relocked the bootloader, then tried the RUU exe method (followed all steps) and I get a "Error 155" message. What can I do to fix that?
I have even flashed ClockworkMod recovery and tried to mount the /data, but I get the same "Unable to mount /data" message
Someone else might know this more than me.. but is it possible to format partitions from fastboot? Maybe you could format data from there then try some of your other steps..
Sent from my HTC6435LVW using xda app-developers app
lazarus2297 said:
Someone else might know this more than me.. but is it possible to format partitions from fastboot? Maybe you could format data from there then try some of your other steps..
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Yeah, it definitely sounds like I need to do some reorganizing/reformatting/file therapy. The only question I have is HOW :/
I appreciate your replies and your help Hopefully I can get this figured out. Is there some chat/irc channel or some other way to reach out for help? I want to exhaust all options.
Mcsquizzy said:
I tried the ADB sideload option within recovery, but I get a message saynig "Unable to mount '/data'". I also get this message after trying to install a ROM through recovery. When I try to select "Mount data" in the Mount menu of the TWRP recovery, I am unable to check the box. I can only check "Mount system" and "Mount cache". This is the only hangup right now. I have the bootloader unlocked, and I have flashed the boot.img (the stock version), but I cannot install or ADB sideload any ROMs because of the "Unable to mount '/data'" message Any ideas?
Click to expand...
Click to collapse
I think maybe it might be worth going back to re read how to return to stock posts carefully-link below. You should first have the phone locked again, the RUU is executable from your pc. You won't be using a recovery program and therefore shouldn't be doing any part from their menu to get it done. Everything your phone needs should get loaded up if correctly done.
http://forum.xda-developers.com/showthread.php?t=2011243
andrewp3481 said:
Btw...anyone have a ruu in zip format?
Like a PH98IMG.zip as an example..that file name correlates with the rezound nut ya know what I mean??
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
All you have to do is extract the RUU contents and put them in a folder called whatever.zip(THIS IS NOT THE NAME OF THE FOLDER) and bam you got a .zip
Sent from my HTC6435LVW using XDA Premium HD app
rootntootn said:
I think maybe it might be worth going back to re read how to return to stock posts carefully-link below. You should first have the phone locked again, the RUU is executable from your pc. You won't be using a recovery program and therefore shouldn't be doing any part from their menu to get it done. Everything your phone needs should get loaded up if correctly done.
http://forum.xda-developers.com/showthread.php?t=2011243
Click to expand...
Click to collapse
I HAVE relocked my phone, AND used the RUU.exe method. I get an "Error [155]" message.
I wonder if this has to do with anything, though. I have the HTC drivers installed, my phone is unlocked and in the fastboot usb bootloader screen. I am using the HTC Droid DNA All-in-one kit to relock the phone. When I do so, I get this message:
Code:
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
FAILED (status read failed (Too many links))
finished. total time: 1.267s
D:\Android\adt-bundle-windows-x86_64\sdk\Droid_DNA_All-In-One_Kit_v2.1\Droid_DNA_All-In-One_Kit_v2.1\data>
Then my phone reboots and says:
Code:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
If I were to reboot into bootloader again, the "Security Warning" goes away. Could that have anything to do with it?
Otherwise, even after relocking and following all steps, when I try the RUU.exe method, I get to "Verifying information on android phone" -> "Update image version" -> "Checking" -> Waiting for bootloader" -> "Sending" -> "Updating Signature" -> "Error [155]"
Could it be a CID thing? If my phone is the wrong CID might the RUU.exe not work? Maybe if I change the CID to a generic one?
SUCCESS!!! I kept trying the RUU.exe method over and over and over. Finally I redownloaded the same exact file. I entered Windows Task Manager and closed any program I suspected of interfering (Command prompts, driver software, All-in-one tool, etc.). I unplugged my phone from USB, booted into bootloader (fastboot), then connected the USB cable again. I ran the RUU.exe as an Administrator. The "Previous Version" or whatever was empty, with "New Version" as the 1.15.605.4 version. It went through all of the usual steps (Bootloader -> Wiping -> Sending -> Signature stuff) then (where it would usually give me the "Error [155]", it kept going. I was actually researching warranty Acts and packaging my cables and etc. back into the box to go plead a BS "Phone died during update" case to Verizon So excited right now. Thank you guys so much for all of your help, and I hope this thread can help other users in a situation similar to mine. As long as you can get into bootloader and recovery YOUR PHONE IS OKAY. Just keep at it
Glad to hear it!!
Sent from my HTC6435LVW using xda app-developers app
Hi all. Before i start i want to say, i read a lot of threaths and comments before i started to booting recovery and i followed Tutorial that you can find somewhere here on XDA for MotoE.
I unlocked Bootloader correctly and everything was right. Then i downloaded latest version of TWRP and CWM if something will be wrong.
So i booted into bootloader, connected to PC (windows 8.1) and using adb i installed TWRP (by command window). After instalation was complete, i used comand: "fastboot reboot" to get my mobile start normally. Everything worked fine so i started last step. Turned off mobile, booted into bootloader(or maybe fastboot? idk...) and by volumebuttons i choosed "Recovery" . Then a black screen for a minute. After that mobile stuck on screen that i attached down below. So i tried this but with CWM (same process way). But nothing new... Someone said me i had to try "Minimal ADB and Fastboot" but again, nothing happend.
Can you help me guys?
The recovery isn't installed! Reinstall the recovery and follow correct steps!
I tried it one more time. I´m attaching image that is from command window showing that .img was booted ... Strange is, immediately after booting was completed, mobile restarted... and after i turned off mobile again, still i can´t reach recovery. Isn´t that problem in .img file? maybe it´s broken, isn´t it?
Tried once again
Ok last try didnt worked. So i complettly followed this guide http://forum.xda-developers.com/moto-e/general/guide-one-moto-e-beginners-guide-t2807891 STEP-BY STEP!
Command window screen attached, Fastboot screen attached.
After reboot, turn off i tried to open recovery and again that image that i posted in first coment. (android figure with words: no command)
By that guide i downloaded recovery from here: https://goo.im/devs/OpenRecovery/condor/
and i downloaded just "openrecovery-twrp-2.7.1.0-condor.img" as i have to do it (written in guide)
Well, your recovery is flashing fine from cmd but its not detected by your phone.
Try re-downloading the recovery and check md5 before flashing.
I'll look into it and see if the issue can be pinpointed.
Btw, you might need the flash the stock ROM back if nothing works.
Tapatalk with RAZR HD
neo.ank said:
Well, your recovery is flashing fine from cmd but its not detected by your phone.
Try re-downloading the recovery and check md5 before flashing.
I'll look into it and see if the issue can be pinpointed.
Btw, you might need the flash the stock ROM back if nothing works.
Tapatalk with RAZR HD
Click to expand...
Click to collapse
Ok i will re-download recovery, is that file that i downloaded ok? i mean should i dowload same file as before?
+ sorry for that but i completly dont know what the "md5" is. can you send me link from where i can learn what it is? you can explain that too but i dont want take your free time.
Mondop said:
Ok i will re-download recovery, is that file that i downloaded ok? i mean should i dowload same file as before?
+ sorry for that but i completly dont know what the "md5" is. can you send me link from where i can learn what it is? you can explain that too but i dont want take your free time.
Click to expand...
Click to collapse
Okay try this.
Flash CWM
If flashing fails or you get any error, then try booting into recovery.
Code:
fastboot boot recovery.img
If you boot into recovery, flash the SuperSU package.
Reboot and then flash the recovery.
See if it works.
neo.ank said:
Okay try this.
Flash CWM
If flashing fails or you get any error, then try booting into recovery.
Code:
fastboot boot recovery.img
If you boot into recovery, flash the SuperSU package.
Reboot and then flash the recovery.
See if it works.
Click to expand...
Click to collapse
no
flashed CWM from here http://forum.xda-developers.com/showthread.php?t=2793625
concretly from here http://www.mediafire.com/download/6odyyqgodw15f1b/recovery.img
then i flashed it, then i rebooted phone then i shuted it off (to boot into fastboot) in fastboot i selected recovery and again, that screen with android figure (no command) so i pressed power button for long. mobile rebooted. again i went into fastboot to write command you said me to boot into recovery. but i stucked at starting screen (that blue big M in "water" cycle)
this all means, files i downloaded was OK but my phone isnt :/
any idea :/
Mondop said:
no
flashed CWM from here http://forum.xda-developers.com/showthread.php?t=2793625
concretly from here http://www.mediafire.com/download/6odyyqgodw15f1b/recovery.img
then i flashed it, then i rebooted phone then i shuted it off (to boot into fastboot) in fastboot i selected recovery and again, that screen with android figure (no command) so i pressed power button for long. mobile rebooted. again i went into fastboot to write command you said me to boot into recovery. but i stucked at starting screen (that blue big M in "water" cycle)
this all means, files i downloaded was OK but my phone isnt :/
any idea :/
Click to expand...
Click to collapse
Do not flash CWM, just boot into it by the command I posted above.
Then try and flash SuperSU, (if you get a root prompt from CWM, select NO.)
Reboot device.
Then again boot into fastboot and now flash recovery (twrp).
neo.ank said:
Do not flash CWM, just boot into it by the command I posted above.
Then try and flash SuperSU, (if you get a root prompt from CWM, select NO.)
Reboot device.
Then again boot into fastboot and now flash recovery (twrp).
Click to expand...
Click to collapse
so now what if i flashed that CWM before?
Now i tried go to fastboot and used just command that you said(to boot into recovery) and as i said, i stucked on motorola starting logo
+ you said i have to flash cwm
Mondop said:
so now what if i flashed that CWM before?
Now i tried go to fastboot and used just command that you said(to boot into recovery) and as i said, i stucked on motorola starting logo
+ you said i have to flash cwm
Click to expand...
Click to collapse
I said if flash is not successful, then boot into it. So you can't boot into recovery either.
Here's last resort, extract the stock recovery from stock ROM and flash it. Then we'll try flashing TWRP again.
If you don't have stock ROM, download it. as you might need it to recover.
neo.ank said:
I said if flash is not successful, then boot into it. So you can't boot into recovery either.
Here's last resort, extract the stock recovery from stock ROM and flash it. Then we'll try flashing TWRP again.
If you don't have stock ROM, download it. as you might need it to recover.
Click to expand...
Click to collapse
Okay, can you give me link with tutorial? i found just this one which restores whole system (and its 4.4.3 and i have now 4.4.4, i mean this will be maybe problem, wouldn´t it?)
i mean this one (tutorial how to restore moto E)
http://forum.xda-developers.com/showthread.php?t=2759495
did you try updating / reinstalling USB-driver on your computer?
magicw said:
did you try updating / reinstalling USB-driver on your computer?
Click to expand...
Click to collapse
no i didnt, think you it will help? i mean if i can connect my mobile into pc without any problem in normal mode and in fastboot too... i will unninstal drivers, intall them again and them i will try unninstal motorola device manager and then again intall him.
(i had newest drivers i can update them)
LOL?
OK im in recovery i already flashed superSU...
What did i do?
As you said, i reinstalled all drivers...
then i downloaded same TWRP again (but with mirror source)
I downloaded attached md5 file ( still dont know what should i do with it )
moved recovery and .md5 files into minimal adb and fastboot (both files i renamed to "recovery")
turned off devices
started fastboot
connected to PC
started command window and entered command "fastboot flash recovery recovery.img"
then i didnt wrote sommand "fastboot reboot" as i done before
i just unpluged usb and navigate to recovery button and launched it
and VUALA im in recovery
hurraaa
just installed superSU and then rebooted.
everything works (superSU too)
i have one more question...
i downloaded twrp manager from google play
first start: asked for root permission a allowed it
then message appeard:
"The only compatible version of busybox we support is Stericson. All other cause havoc on all operations in this app. Please click yes to install Stericson busybox"
what the heck is busybox?
+Should i download it or not?
Do not use TWRP Manager, ROM Manager, CWM Manager or any other of these Tools. They often do not really work good together with "exotic" fones. Why the heck do you need TWRP manager? You have TWRP installed
Anyway - Busybox you also can download and install from Playstore. Busybox is a collection of executable terminal commands helpful for any kind of script. There are a couple of rooted apps who will ask for busybox support - so don't hesitate to install busybox - but do it directly with busybox app from playstore.
After you have installed the binaries you can de-install the busybox-app. Because all necessary binaries then are copied into /system/bin/ folder and the app itself only will become active once a new version would be available (but this is not the case very often).
ok then
magicw said:
Do not use TWRP Manager, ROM Manager, CWM Manager or any other of these Tools. They often do not really work good together with "exotic" fones. Why the heck do you need TWRP manager? You have TWRP installed
Anyway - Busybox you also can download and install from Playstore. Busybox is a collection of executable terminal commands helpful for any kind of script. There are a couple of rooted apps who will ask for busybox support - so don't hesitate to install busybox - but do it directly with busybox app from playstore.
After you have installed the binaries you can de-install the busybox-app. Because all necessary binaries then are copied into /system/bin/ folder and the app itself only will become active once a new version would be available (but this is not the case very often).
Click to expand...
Click to collapse
i have no reason to want twrp manager, i just wanted to look at this app, and i found that busybox there so i wanted to ask here
thx for answer, now i undertand