I flashed GreyBlur to my Atrix after rooting and had no problems and didn't lose anything. I followed the instructions off the briefmobile site after d/ling the 2.3.4 zip. Copied it to my SD card and pointed CWM to it. It appeared to install; but upon reboot I get caught in a loop. I get the moto emblem; then I see the Greyblur boot screen then it loops. I'm trying to recover the phone and I've dug thru the forums but I haven't found anything that lines up with what I'm experiencing. Any idea how I can recover my phone? I'd like to push fwd to GB but I'm kinda lost at this point. I guess it was dumb of me to make the assumption that this would go as smooth as the move to GreyBlur. Any help is appreciated; thx in advance!
Wipe and format phone then put your phone in fastboot and fastboot 2.3.4 . Then at least you have a working phone then you can upgrade to the new build by kenneth
Sent from my MB860 using XDA Premium App
I'll give it a go when I get home. Thanks for the help! I'll reply if I run into any issues. Thx again!
Np keep updated and I will keep checking post.
Sent from my MB860 using XDA Premium App
OK I wiped and then hit the down volume button to put it into the recovery mode. I selected the fastboot option and it seems to hang. On the screen it sez:
Fastboot
Starting fastboot protocol support
and that's as far as it gets. Is there another way I should be approaching this? Damn this noobism!!
lol thats what it is suppost to do. the rest you have to use is off computer have you ever used fastboot? if not i will walk you though it.
1st go download the htkw build http://www.megaupload.com/?d=VLAKXBB3
Fastboot files for u http://forum.xda-developers.com/showthread.php?t=1138092 choose if u have
32 or 64 bit
2st make sure the moto-fastboot or fastboot (they both work i have tested )file is in your c:\
you have to cd the drive first so make sure its in c:\ .FYI make sure all the files are in one folder not the root drive
so name a folder (whatever) then cd that folder from cmd.
Dont use " " just showing you commands
one at a time and wait for them
Then go to cmd
"cd c:\moto-fastboot"
click enter
then type
moto-fastboot flash boot atrix-2.3.4-hktw-boot.img
then
moto-fastboot flash system atrix-2.3.4-hktw-system.img
then
moto-fastboot -w
click enter
Should say writing\sending
Once your done and it completes
type moto-fastboot reboot
enter
cool mang lemme roll thru this and see if I can get this going. thanks again for taking the time to help a noob out!
wait for me to upload this file u will need it to finish steps
also this is a zip file please remove the img files from the zip and place in fastboot folder
not having any luck; can you give me links for the moto-fastboot and HKTW files?
I'm running fastboot and the Gingerbread-Atrix-Beta-4-5.zip file. I've found the boot.img file in the zip but the system.img is being a bit elusive. thx again!
it is now in my first post a link like i said please extract the 2 files into fastboot folder.
I added link for fastboot if u are on windows just use the moto-fastbootwin32 one
Once you get 2.3.4 installed with fastboot let me know and then we will
go on how to install the new build and which clockworkmod did u use?
OK finally got the hktw file downloaded; moto-fastboot wasn't cooperating so I went with the fastboot command; upon attempting to run the commands provided here's the output I get in my CMD prompt:
C:\gb\atrix>fastboot flash boot atrix-2.3.4-hktw-boot.img
sending 'boot' (3358 KB)...
OKAY [ 0.185s]
writing 'boot'...
FAILED (remote: (00180002))
finished. total time: 0.247s
C:\gb\atrix>fastboot flash system atrix-2.3.4-hktw-system.img
sending 'system' (327554 KB)...
(bootloader) Image is too big, use 0x10000000 bytes chunks
FAILED (remote: (00000006))
finished. total time: 0.003s
on the phone itself it states the following after each command:
Flashing StorMgr partition boot
Flashing MBR to device
Failed to process command flash:boot error (0x180002)
Failed to process command download:13fe0800 error(0x6)
any ideas?
You will have to use mot-fastboot no way around it the files is to big for fastboot try motor again
Sent from my MB860 using XDA Premium App
Aight; I'm gonna do some digging; cuz when I tried to run moto-fastboot is said that it couldn't find the file. Anything special I need to do with the moto-fastboot to get the computer to recognize it's there? I really think I'm close; but this is getting frustrating. Looks like my battery died as well. Fortunately my wife has the same phone so I've got a way to charge it back up *whew*. Didn't realize how much of a hole in my life not having a phone would leave; now I know how heroin addicts feel when trying to kick the habit!! LOLz!
OK; I figured it out; knew it HAD to be something simple. Turns out I was not using the Windows verison of moto-fastboot. I'm gonna give it another shot when I get home and letchya know the results. *crosses fingers* *shakes fist* Victory will be MINE!!!
GruvRegulator said:
Aight; I'm gonna do some digging; cuz when I tried to run moto-fastboot is said that it couldn't find the file. Anything special I need to do with the moto-fastboot to get the computer to recognize it's there? I really think I'm close; but this is getting frustrating. Looks like my battery died as well. Fortunately my wife has the same phone so I've got a way to charge it back up *whew*. Didn't realize how much of a hole in my life not having a phone would leave; now I know how heroin addicts feel when trying to kick the habit!! LOLz!
Click to expand...
Click to collapse
Rofl , take your time. This is part of flashing a phone.
Sent from my MB860 using XDA Premium App
Lol sigh nubby move hehe
Sent from my MB860 using XDA Premium App
....and the hits just keep on comin'!!
Looks like I'm going to learn more than I ever wanted to about flashing and fastboot.
OK; so I'm in the middle of moto-fastbooting the boot and system file when my battery dies; I KNOW I had 60% battery when I hooked it up; but apparently that's of no consequence now. Recharged the battery to full on my wife's Atrix (thank god she has one!!) and when I load the phone I'm getting:
"Failed to boot 4" then the next line reads "Starting RSD mode"
Jesus; this just keeps getting better; I'm guessing I'm at the soft brick point; teetering on the edge of hard bricking the damn thing. *sigh*
So did some digging thru the forums and I guess the only route I have now is to pull SIM and SD card out; boot up RSD Lite and flash the 1.5.7 SBF to the damn thing to get back to square one.
Here's the guide I'm following:
http://forum.xda-developers.com/showthread.php?t=1065740
So I'm currently pulling down OLYFR_U4_1.5.7_SIGNED_OLPSATTSPE_P012_HWolympus_1g_1FF.sbf.gz
from briefmobile.com's site and hope that this will be enuff to get the phone back to stock working order. Unfortunately I live out in the country (I keeps it RURAL!!) so I'm working over a 4g AT&T mifi connection. I get about 3-6 Mb/s so this is going to take a while. I'll report back on any progress that I've been able to make out of this hole that I've dug myself into.
One thing I will say this HAS been a learning experience. More updates to follow...lemme know if you have any suggestions on any of the above and if ya think I'm on the right track. thx again.
Nope your on the right track all you can do is flash a rsd . Any time you do flashing battery has to be 100 flash takes alot of battery. Other than that let me know what goes on keep updated.
Sent from my MB860 using XDA Premium App
why dont you just flash a fresh .sbf via rsd then go to gingerbread from there
that's what he is doing. Lol poor guy has been though hell
Sent from my MB860 using XDA Premium App
Greyblur is a froyo theme and really old, it's not made for gingerbread, that is why you bootloop
Related
I have a motola photon that I believe is bricked due to and attempt to flash the electrified 2. 3. 5 without doing my research. The bootloader is unlocked but every attempt at a fastboot command freezes at waiting for device. I've flashed every sbf under the sun threw rsd with failure at the phone "re-enumerate" stage. I'm so stuck and very confused.. ive been using this stuff since my Android Leo, g 2 and many more.
ashirback said:
I have a motola photon that I believe is bricked due to and attempt to flash the electrified 2. 3. 5 without doing my research. The bootloader is unlocked but every attempt at a fastboot command freezes at waiting for device. I've flashed every sbf under the sun threw rsd with failure at the phone "re-enumerate" stage. I'm so stuck and very confused.. ive been using this stuff since my Android Leo, g 2 and many more.
Click to expand...
Click to collapse
If you flash a 2.3.4 Locked sbf via RSD after the flash failure what does the wcreen on your phone say?
I think I am in a similar situation but found a way to unbrick.
Failed flashing process. Failed flashing process. Phone [0000] "The Secure_Motorola_Flash" Interface could not be found. The super-file is secure and for re-flash; the phone needs a super-file that is not secure and not for re-flash. (0x7066)
The rsd fails at 98% when the phone attempts to switch to a BP passthrough.
Im baffled
have you tried booting even tho rsdlite fails? it "fails" for me everytime nd still boots xD
Sent from my MB855 using xda premium
it's supposed to fail, the phone still boots perfectly and if not try a battery pull or flashing a locked sbf
Guys of course I tried to boot the phone afterwards. It just sits at the Motorola logo, says unlocked in the upper left corner with 0 animation to the logo. I cant get into recovery either.. its back to the stock exclanation point one.
Anyone have an idea of what could be wrong? How am I supposed to do anything to the phone if Rsd continues to fail and I don't have access threw fastboot? Also the phone model in rsd is listed as NS Flash Sunfire, it lists my bootloader as ver v0x000007 but everything else is listed as N/A
ashirback said:
Anyone have an idea of what could be wrong? How am I supposed to do anything to the phone if Rsd continues to fail and I don't have access threw fastboot? Also the phone model in rsd is listed as NS Flash Sunfire, it lists my bootloader as ver v0x000007 but everything else is listed as N/A
Click to expand...
Click to collapse
What happens when you try to force the phone into fastboot mode by pulling the battery, putting it back in and holding the VOL down and POWER buttons?
Well it let's me get into fast boot with no problem after some fooling around today. however when I try to erase my data threw fast boot it says I don't have a product name. The device is listed in fastboot though as TA00.. (don't remember # off hand). I know the values for this is changeable but is it necessary or is that minor in this large issue.
From what you are telling me this should work...
Make sure that your phone says UNLOCKED at the top left corner..
Follow this: Go specifically to the ROOT instructions: and flash the system image
http://forum.xda-developers.com/showthread.php?t=1216143
Please let me know if it works.
That sounds perfect but the link for the system file is down. Anti piracy bull**** government hoopla. GARRRR ! Anyone by any chance have a copy of the file or a mirror to where i cant find it?
ashirback said:
That sounds perfect but the link for the system file is down. Anti piracy bull**** government hoopla. GARRRR ! Anyone by any chance have a copy of the file or a mirror to where i cant find it?
Click to expand...
Click to collapse
After going to the link have you tried the other sites besides mega downloads?
Yea I tried. The file has been deleted or moved from every file site there. =\ I'm going to continue to troll the net after I escape from work tonight. Hopefully with some luck I can find one that someone else has uploaded.
Fastboot attempts to flash the file but it fails stating "INFOImage is too big, use 0x10000000 bytes chunks"
ashirback said:
Fastboot attempts to flash the file but it fails stating "INFOImage is too big, use 0x10000000 bytes chunks"
Click to expand...
Click to collapse
Well!!! did you wipe before you had flashed the 2.3.5 SBF ????
If running in Win 7 make sure that you opened up the command prompt as administrator. Also make sure that you put the system.img in the fastboot folder/directory. So you should be doing:
1. fastboot erase system
2. fastboot flash system.img
3. fastboot reboot
Still wouldnt let me because the system image was too big.
But i managed to flash clockwork threw fastboot and was able to boot that up. I did a factory reset in clockwork rebooted and it was still frozen. But i was able to flash redROCKO 1.1.1 and then it booted and is now working flawlessly.
Hello friends I have a Motorola Brick Hard SVF : 105:1:2. FAILED TO BOOT RECOVERY NVFLASH ENTERING 0x1000 and off the screen immediately goes out, and I can not enter nor in RSD mode Fastboot, eh been watching and say they can not fix, but I wanted to make sure it's so opening a new topic.
Greetings and thanks.
HelP Me please
Hard brick. Done deal!
Try a warranty return or buy a new phone.
You specifically said in your op that you had a hard brick. Think really carefully about this... what does hard brick mean?
And there's your answer. Looks like its time for you to shop for a new phone. Next time use search, and dont make a topic "just to be sure" when there's almost literally a million topics confirming what you're asking.
failed to boot hard brick SOLVED!!!!!!
People on here shouldnt give up so easily, I have a solution for failed to boot brick.
Download moto-fastboot, and unzip to C:\moto-fastboot
DL here:http://www.android-advice.com/file-downloads.php?filename=Atrix_Root_Files
Download system image for 2.3.4 and unzip to moto-fastboot folder
DL here http://www.android-advice.com/file-downloads.php?filename=Atrix_Gingerbread_4591_ROM
Download atrix oem unlock and unzip to moto-fastboot folder
DL here:http://gititbit.ch/pub/unlock.zip
open cmd and navigate to C:\moto-fastboot\
Force fastboot on phone by holding down PWR and VOL UP while inserting battery.
Type these commands:
moto-fastboot oem unlock (it will show atrix ID re-enter with ID at end of line)
when finished, then enter these commands:
moto-fastboot flash boot boot.img
moto-fastboot flash system system.img
moto-fastboot -w
moto-fastboot reboot
When it reboots, you will be back to stock, fully restored!!
I then used Pete's Motorola Tools to root my atrix.
Info and DL here http://www.psouza4.com/Bionic/
yes it did work on my atrix make sure usb debugging is on and unknown sources checked.
I then installed CWM to my Atrix
DL here http://forum.xda-developers.com/showthread.php?t=1475444
unzip to moto-fastboot, put atrix in fastboot mode and open cmd, navigate to moto-fastboot folder and type this:
moto-fastboot flash recovery recovery.img
Reboot and you are DONE!!!! All thats left is to find a ROM and you are good to go.
mcjinx216 said:
People on here shouldnt give up so easily, I have a solution for failed to boot brick.
blah...
Reboot and you are DONE!!!! All thats left is to find a ROM and you are good to go.
Click to expand...
Click to collapse
Annnnnd, you will find out the reason we call it a HARD brick, it will NOT enter fastboot mode, or RSD or anything else other than Nvflash.
I'm going to come across rude, but if you have no idea, don't post rubbish.
And you should read my post; I got into fastboot mode by holding volume up and Power while inserting the battery. Using my method WILL restore your phone from the failure to boot error, as I did the same thing and Im now restored. I used moto fastboot to restore in fastboot mode.
mcjinx216 said:
And you should read my post; I got into fastboot mode by holding volume up and Power while inserting the battery. Using my method WILL restore your phone from the failure to boot error, as I did the same thing and Im now restored. I used moto fastboot to restore in fastboot mode.
Click to expand...
Click to collapse
Yes we read your post! IT DOES NOT WORK. That works with no brick or a SOFTBRICK not a hard one...
Understood.....that would mean that 0x1000 is obviously not a hard brick then. It seems to me that some of the confusion comes from a lack of properly identifying the brick status. I too got that message from accidentally attempting to flash and older file over a newer one. I used the method I described to restore my phone. Try for yourself; if it works then cool. If not then not. All Im trying to do is give insight on a common problem I encountered and how i fixed it. This site is supposed to be the best in the mobile world, I wish people would spend less time trying to be rude and insulting and more time trying to help. And thank you Alaq for helping clarify and acknowledging that my method could help some people.
Imean, at the end of the day, XDA is supposed to be a help and support site, right?
mcjinx216 said:
Understood.....that would mean that 0x1000 is obviously not a hard brick then. It seems to me that some of the confusion comes from a lack of properly identifying the brick status. I too got that message from accidentally attempting to flash and older file over a newer one. I used the method I described to restore my phone. Try for yourself; if it works then cool. If not then not. All Im trying to do is give insight on a common problem I encountered and how i fixed it. This site is supposed to be the best in the mobile world, I wish people would spend less time trying to be rude and insulting and more time trying to help. And thank you Alaq for helping clarify and acknowledging that my method could help some people.
Imean, at the end of the day, XDA is supposed to be a help and support site, right?
Click to expand...
Click to collapse
Nobody is confused here but you. That error shows up in 2 scenarios. The one the OP posted is a HARD brick. You had a SOFT brick!
Sent from my MB860 using xda premium
mcjinx216 said:
Understood.....that would mean that 0x1000 is obviously not a hard brick then. It seems to me that some of the confusion comes from a lack of properly identifying the brick status. I too got that message from accidentally attempting to flash and older file over a newer one. I used the method I described to restore my phone. Try for yourself; if it works then cool. If not then not. All Im trying to do is give insight on a common problem I encountered and how i fixed it. This site is supposed to be the best in the mobile world, I wish people would spend less time trying to be rude and insulting and more time trying to help. And thank you Alaq for helping clarify and acknowledging that my method could help some people.
Imean, at the end of the day, XDA is supposed to be a help and support site, right?
Click to expand...
Click to collapse
0x1000 shows up in both hard and soft bricks... It's what it says under it that separates the two, you obviously didn't read, and you confused yourself... I didn't want to be rude, sorry...
@OP the best you can do is sell it, it sells on ebay for around 100$ if it's good condition, but you have to state that it is hardbricked... Or you can donate it to a well known developer to help try to solve it...
Ignore this post, posted in error. Sorry.
Wow, lots of negativity here. I'm shocked anyone would want to help people here.
One wrong mistake and bam, insults flying everywhere.
Btw, next time, use the search feature, you would've found an answer faster.
Milenko2121 said:
Wow, lots of negativity here. I'm shocked anyone would want to help people here.
One wrong mistake and bam, insults flying everywhere.
Btw, next time, use the search feature, you would've found an answer faster.
Click to expand...
Click to collapse
Not negativity or insults. OP got their answer right away. I gave the OP the answer in post #3!
What we had once again was someone giving the wrong advice, and then when corrected, continued to give the wrong advice.
thank you all for your help, but unfortunately could not arrange a HardBrick, SoftBrick if the fix in the end sold the team and acquired another.
regards
mcjinx216 said:
People on here shouldnt give up so easily, I have a solution for failed to boot brick.
Download moto-fastboot, and unzip to C:\moto-fastboot
DL here:http://www.android-advice.com/file-downloads.php?filename=Atrix_Root_Files
Download system image for 2.3.4 and unzip to moto-fastboot folder
DL here http://www.android-advice.com/file-downloads.php?filename=Atrix_Gingerbread_4591_ROM
Download atrix oem unlock and unzip to moto-fastboot folder
DL here:http://gititbit.ch/pub/unlock.zip
open cmd and navigate to C:\moto-fastboot\
Force fastboot on phone by holding down PWR and VOL UP while inserting battery.
Type these commands:
moto-fastboot oem unlock (it will show atrix ID re-enter with ID at end of line)
when finished, then enter these commands:
moto-fastboot flash boot boot.img
moto-fastboot flash system system.img
moto-fastboot -w
moto-fastboot reboot
When it reboots, you will be back to stock, fully restored!!
I then used Pete's Motorola Tools to root my atrix.
Info and DL here http://www.psouza4.com/Bionic/
yes it did work on my atrix make sure usb debugging is on and unknown sources checked.
I then installed CWM to my Atrix
DL here http://forum.xda-developers.com/showthread.php?t=1475444
unzip to moto-fastboot, put atrix in fastboot mode and open cmd, navigate to moto-fastboot folder and type this:
moto-fastboot flash recovery recovery.img
Reboot and you are DONE!!!! All thats left is to find a ROM and you are good to go.
Click to expand...
Click to collapse
english:
really works, no longer a paperweight working again my Motorola Atrix 4G, read carefully this post, that really works, greetings from Venezuela, and thanks for the help!
spanish:
realmente funciona, dejo de ser un pisapapeles, a funcionar nuevamente mi motorola atrix 4g, lean detenidamente este post, por que realmente funciona, saludos desde venezuela, y gracias por la ayuda!!!
i just tired this which failed. while trying to moto fastboot the unlock it had failed. says ... INFOOEM unlock is not implemented
mcjinx216 said:
People on here shouldnt give up so easily, I have a solution for failed to boot brick.
Download moto-fastboot, and unzip to C:\moto-fastboot
DL here:http://www.android-advice.com/file-downloads.php?filename=Atrix_Root_Files
Download system image for 2.3.4 and unzip to moto-fastboot folder
DL here http://www.android-advice.com/file-downloads.php?filename=Atrix_Gingerbread_4591_ROM
Download atrix oem unlock and unzip to moto-fastboot folder
DL here:http://gititbit.ch/pub/unlock.zip
open cmd and navigate to C:\moto-fastboot\
Force fastboot on phone by holding down PWR and VOL UP while inserting battery.
Type these commands:
moto-fastboot oem unlock (it will show atrix ID re-enter with ID at end of line)
when finished, then enter these commands:
moto-fastboot flash boot boot.img
moto-fastboot flash system system.img
moto-fastboot -w
moto-fastboot reboot
When it reboots, you will be back to stock, fully restored!!
I then used Pete's Motorola Tools to root my atrix.
Info and DL here http://www.psouza4.com/Bionic/
yes it did work on my atrix make sure usb debugging is on and unknown sources checked.
I then installed CWM to my Atrix
DL here http://forum.xda-developers.com/showthread.php?t=1475444
unzip to moto-fastboot, put atrix in fastboot mode and open cmd, navigate to moto-fastboot folder and type this:
moto-fastboot flash recovery recovery.img
Reboot and you are DONE!!!! All thats left is to find a ROM and you are good to go.
Click to expand...
Click to collapse
Don't know why are some peolpe saying that it doesn't work.... it works like a charm! I flashed a worng SBF file, had the boot error, followed this tutorial and had my phone back Thanks a Million Times
My experience with mcjinx216's fix procedure was entirely _positive_. I was able to unlock and to install the boot image. I was _not_ able to install the system image which returned a "file too large" indication; however when I executed "fastboot reboot" the Atrix rebooted to the setup screen!
I now have Android version 2.3.4 build 4.5.1 on the Atrix, so it is possible that the system image actually installed during the fastboot routine. I have forgotten the version which was installed before the crash.
The entire problem arose out of an attempt to install ICS on the Atrix during the course of which the Atrix failed to reboot and returned the error "failed to boot 1". I was unable to reflash the stock sbf file. RSD simply failed, even though it recognized that the Atrix was connected. I was stumped.
I cannot thank mcjinx216 enough. Great post and recommended for brickees.
I should point out that you must be careful with the syntax in fastboot. Be sure that fastboot executes and that you follow the displayed instructions carefully. I could not get mcjinx216's syntax to work so I just used e.g. "fastboot flash boot boot.img" without the "moto-" prefix.
I think we will have some good news about fixing the Atrix Hard Brick with the Riff Box. I read at other forum that the team had some major steps towards the jtag flash fix.
Ok so i got the 2.3.5 soak test installed awhile ago and wanted to try to go back to 2.3.4 so after going through the forums i found a way to use recovery with bootstrap so then i went and installed the Stock-rooted-198_7 that loki posted and now my mopho turns on with no motorola logo it only says failed to boot 1 starting rsd protocol
willistheyounger said:
Ok so i got the 2.3.5 soak test installed awhile ago and wanted to try to go back to 2.3.4 so after going through the forums i found a way to use recovery with bootstrap so then i went and installed the Stock-rooted-198_7 that loki posted and now my mopho turns on with no motorola logo it only says failed to boot 1 starting rsd protocol
Click to expand...
Click to collapse
I'd hate to tell you this but you are LOCKED. The bad part is you need to flash a Locked ROM but without access to bootstrap it's going to be a problem. Try this;
battery pull
power on holding down the volume down button
pray to the phone spirits for "fastboot" to show up
Post you results
Lokifish Marz said:
I'd hate to tell you this but you are LOCKED. The bad part is you need to flash a Locked ROM but without access to bootstrap it's going to be a problem. Try this;
battery pull
power on holding down the volume down button
pray to the phone spirits for "fastboot" to show up
Post you results
Click to expand...
Click to collapse
yes i can get it to fast boot but i have no idea what to do
willistheyounger said:
yes i can get it to fast boot but i have no idea what to do
Click to expand...
Click to collapse
This is good news. I'm going to need some time (couple hours) but I may have a way to get you running. I need to get things set up as I'm working on Ubuntop right now and need to flash back.
Lokifish Marz said:
This is good news. I'm going to need some time (couple hours) but I may have a way to get you running. I need to get things set up as I'm working on Ubuntop right now and need to flash back.
Click to expand...
Click to collapse
ok thanks
Oh, while you are waiting, download this root-unlock-relock pack. It's going to have the driver files and software you will need for me to walk you through this.
i already have it
Extract the zip I pm'd you and place "system.img" it in the "Unlock" folder of the root-unlock-relock
Download and extract RDL3_unlocked.smg and place it in the "Unlock" folder
Boot phone while holding down the volume down button
When you see "fastboot" on the phone's screen hit volume up
Connect the phone to your computer
In the "Unlock" folder, double click the "command prompt" shortcut
Enter the following commands
Code:
moto-fastboot flash rdl.bin RDL3_unlocked.smg
moto-fastboot devices
moto-fastboot erase system
moto-fastboot flash system system.img
moto-fastboot reboot
If this does not work I'm not sure where to go at this point. There is no 2.3.5 "update.zip" or SBF that you could flash right now. You may very well have to get a replacement.
I'm not going to be able to help beyond this point as I killed my battery with no way to charge it so we both may be SOL
This is what i get
C:\Users\Will\Desktop\Photon\Root-Unlock-Relock\Root-Unlock-Relock\moto-fastboot
>moto-fastboot flash rdl.bin RDL3_unlocked.smg
sending 'rdl.bin' (3072 KB)... OKAY [ 0.289s]
writing 'rdl.bin'... OKAY [ 0.001s]
C:\Users\Will\Desktop\Photon\Root-Unlock-Relock\Root-Unlock-Relock\moto-fastboot
>moto-fastboot devices
038061024440b4d7 fastboot
C:\Users\Will\Desktop\Photon\Root-Unlock-Relock\Root-Unlock-Relock\moto-fastboot
>moto-fastboot erase system
erasing 'system'... FAILED (command write failed (Unknown error))
C:\Users\Will\Desktop\Photon\Root-Unlock-Relock\Root-Unlock-Relock\moto-fastboot
>moto-fastboot flash system system.img
sending 'system' (262144 KB)... FAILED (command write failed (Unknown error))
C:\Users\Will\Desktop\Photon\Root-Unlock-Relock\Root-Unlock-Relock\moto-fastboot
>
I don't see a moto-fastboot oem unlock in there after devices and shouldn't it be moto-fastboot erase recovery?
willistheyounger said:
This is what i get
Click to expand...
Click to collapse
So unlocked RAMloader exploit is a fail. The only other thing I could think of is SBF a 2.3.5 engineering build? If that won't work then yes you have bricked until we get a full update zip or SBF for this.
Again. Don't feel bad as I'm now (hopefully only) softbricked with a dead battery and no charger.
Kevets said:
I don't see a moto-fastboot oem unlock in there after devices and shouldn't it be moto-fastboot erase recovery?
Click to expand...
Click to collapse
You are thinking about unlocking. This is dealing with bricked 2.3.5
Its really not that big of a deal i can go to sprint and have them get me another one i mainly use my epic touch
Sent from my SPH-D710 using XDA
but if you can help me out it would be better because then i wont have to make something up
Sent from my SPH-D710 using XDA
willistheyounger said:
but if you can help me out it would be better because then i wont have to make something up
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
I'm bricked because battery died during flashing in fastboot and will be without a phone for at least a couple days.
Unless the policy has changed recently, it doesn't matter. If you have the service coverage they simply replace it.
Oh **** man now i feel bad
Sent from my SPH-D710 using XDA
willistheyounger said:
Oh **** man now i feel bad
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
It's all good. It's my fault for not buying and external charger when I got rid of my dev photon.
yea whats worse for me i just ordered 2 cases a extra battery a car dock and should get it tuesday
Sent from my SPH-D710 using XDA
Maybe a solution to this problem is flashing electrify 2.3.5 sbf, just to get the phone working.
But then you will be stuck with electrify.
maxon_yalta said:
Maybe a solution to this problem is flashing electrify 2.3.5 sbf, just to get the phone working.
But then you will be stuck with electrify.
Click to expand...
Click to collapse
I was trying not to send him down that road but that is an option
I already made an appointment at my local sprint store
Sent from my SPH-D710 using XDA
Last night I was able to unlock my bootloader on my rezound. And I installed Amon Ra recovery. I did a nand backup before I made any other choices from there. But I don't know if I was perm rooted. But I installed su and busybox. well I went ahead and installed Rom Manager just to start out with instead of using amon recovery.
Through rom manager I had to flash clockwork mod. did that. so I thought i was ready to go with flashing a ROM. well I downloaded a ROM through my phone. but it wasn't on my sd card. so i pulled the notifications down on my phone and just clicked the downloaded ROM and it said what would you like to do with it? I clicked the rom manager option. cleared dalvik and cache n all. Everything said installed successfully. well it just stayed on the htc screen FOREVER. so i pulled battery and tried to recover my backup. well now that i have clockwork as recovery. my backup isn't on my phone. I can't even use clockwork now. I can't get my phone to boot at all. I don't think my phone is bricked cuz I can get into the bootloader menu. But i can't get my phone to boot back up at all whatsoever
So I was either not rooted like I thought I was or something. I can't even factory reset through bootloader. it just takes me back to clockwork mod and everytime i click an option through cwm it goes blank. every single option. I need my amon recovery back somehow so i can restore my backup....please somebody help me out. I hope its not bricked. Thanks
You need to flash the boot.img from fast boot if you're not s-off
Sent from my ADR6425LVW using Tapatalk 2
and how am i able to do so??? I guess I'm still a noob with some things. just need a good step by step way of how lol
Edit: Ok I opened up a command prompt and typed in fastboot boot.img. then a whole bunch of stuff popped up. what do i do from there?
npainter7 said:
and how am i able to do so??? I guess I'm still a noob with some things. just need a good step by step way of how lol
Edit: Ok I opened up a command prompt and typed in fastboot boot.img. then a whole bunch of stuff popped up. what do i do from there?
Click to expand...
Click to collapse
extract boot.img from your downloaded ROM. place it in folder on your PC where you have fastboot.
put the phone in fastboot mode and connect to PC , it shows fastboot usb.
issue below in command prompt
fastboot flash boot boot.img
kancherlapraneeth said:
extract boot.img from your downloaded ROM. place it in folder on your PC where you have fastboot.
put the phone in fastboot mode and connect to PC , it shows fastboot usb.
issue below in command prompt
fastboot flash boot boot.img
Click to expand...
Click to collapse
Ok i did this. and this is what popped up.
c:\Android>fastboot flash boot boot.img
sending 'boot' (3950 KB)...
OKAY [ 0.905s]
writing 'boot'...
OKAY [ 1.174s]
finished. total time: 2.082s
Now what???
Edit: Nevermind I got it to work now thank you SO MUCH you guys. much appreciated
@@#$$%#$% Freaking hell I am getting so frustrated with my phone!!! I am going through a continuous bootloop. I can't do anything in time on my phone before it bootloops again over and over. I installed one of newts one xxx ROMS and the continuous bootloop will not stop. I tried installing a different RUU and tried flashing using command prompt and nothing happened....I am so frustrated and have been trying to figure out this rooting stuff over 4 days now straight....I could really use some help!!!
npainter7 said:
@@#$$%#$% Freaking hell I am getting so frustrated with my phone!!! I am going through a continuous bootloop. I can't do anything in time on my phone before it bootloops again over and over. I installed one of newts one xxx ROMS and the continuous bootloop will not stop. I tried installing a different RUU and tried flashing using command prompt and nothing happened....I am so frustrated and have been trying to figure out this rooting stuff over 4 days now straight....I could really use some help!!!
Click to expand...
Click to collapse
Your firmware is probably still GB, Newt's is for ICS. There is a patch allows you to use his ROM on a GB firmware base. So, over on MikMIk possibly, is this patch you need. Flash it in recovery, just like you would a ROM.
Here found a helpful link, look at PRDOG's post. He rocks... Depending on which release of Newt's ROM you are on, he also has a RLS 3.2.1 which is also a patch. Sorry it is a little confusing. But stick with it. Lots of people to help you. You don't need to flash the 3.2.1 patch, just the GB one.
http://themikmik.com/showthread.php?13767-rls-3-2-1/page2
paulhoop said:
Your firmware is probably still GB, Newt's is for ICS. There is a patch allows you to use his ROM on a GB firmware base. So, over on MikMIk possibly, is this patch you need. Flash it in recovery, just like you would a ROM.
Here found a helpful link, look at PRDOG's post. He rocks... Depending on which release of Newt's ROM you are on, he also has a RLS 3.2.1 which is also a patch. Sorry it is a little confusing. But stick with it. Lots of people to help you. You don't need to flash the 3.2.1 patch, just the GB one.
http://themikmik.com/showthread.php?13767-rls-3-2-1/page2
Click to expand...
Click to collapse
Hey thank you so much!! It's nice to have people help out....so when I flash the GB one, I don't have to relock my bootloader do I? I hope not lol
Sent from my ADR6425LVW using xda app-developers app
So in order to flash a PH98IMG.zip what do I have to do? do i have to go into the command prompt and go from there?
So, the other night my Rezound slipped off a shelf and into the toilet. I pulled it out immediately, popped open the case and used a blow dryer on it, then stuck it in a bag of rice. The next day I stuck the battery in and it seemed to be working alright. Then I went to respond to a snapchat and found that the camera was not working. I thought maybe a simple restart might help, but the phone never restarted. I stuck it back in the bag of rice, thinking maybe their was still some moisture that could be pulled out. Today, after roughly 48 hours in the rice, I put the battery in, and it goes into the bootloop.
I pulled the SIM, tried going into recovery, factory reset, wipe cache, etc. Everything I can find on any forum does not work. I found a couple different PH89IMG.zip files, but after the bootloader analyzes them, it says that it can't do anything because they're older versions that what is on the device, which is "4.05.605.14 710RD" according to my wife's phone. I also downloaded the RUU, but the device has to be powered on for that to work, and it won't go past the white screen with green htc logo.
I would really love to resolve this without doing a factory reset, because there are a few things saved on the device itself that I can't really replace. Does anybody have any ideas for anything else I could try? Including maybe having the PH89IMG.zip file for the stock version of Android...
Is there a way that I could extract the PH89IMG.zip file from my wife's rezound, or utilize her phone in any way to repair my own?
ggoodman1022 said:
Is there a way that I could extract the PH89IMG.zip file from my wife's rezound, or utilize her phone in any way to repair my own?
Click to expand...
Click to collapse
You can edit the version.txt in the PH98IMG.zip to the same version as your wife's, that would get you around the mainver errors. Something tells me you did too much water damage and it's just dead though.
mjones73 said:
You can edit the version.txt in the PH98IMG.zip to the same version as your wife's, that would get you around the mainver errors. Something tells me you did too much water damage and it's just dead though.
Click to expand...
Click to collapse
Thanks. I'll give that a shot. It was working the next day, but then stopped after a restart. And it was only in the water for maybe 2 seconds, max. My wife's phone fell in a pool before, and got pulled out about a minute later, then worked after about 48 hours in rice.
mjones73 said:
You can edit the version.txt in the PH98IMG.zip to the same version as your wife's, that would get you around the mainver errors. Something tells me you did too much water damage and it's just dead though.
Click to expand...
Click to collapse
So editing the version listed in the .txt file made it so it didn't hang up on loading the file, but then it just refreshed the main bootloader screen. When I select fastboot, or go to restart the phone, it's still hung up in the bootloop :crying:
I'm not up for an upgrade until November 1, so I've been using my OG Incredible...
ggoodman1022 said:
So editing the version listed in the .txt file made it so it didn't hang up on loading the file, but then it just refreshed the main bootloader screen. When I select fastboot, or go to restart the phone, it's still hung up in the bootloop :crying:
I'm not up for an upgrade until November 1, so I've been using my OG Incredible...
Click to expand...
Click to collapse
Can you get to recovery? I see you have no recovery. You can try to fastboot a recovery.img, I am sorry but sounds like you screwed up your system, you will be lucky if it accepts a recovery. I deal with lots of broken phones in the business I am in and sorry to say once they are water damaged they 90 percent of the time they end up useless. If you need help with fastboot I will help.
jhr5474 said:
Can you get to recovery? I see you have no recovery. You can try to fastboot a recovery.img, I am sorry but sounds like you screwed up your system, you will be lucky if it accepts a recovery. I deal with lots of broken phones in the business I am in and sorry to say once they are water damaged they 90 percent of the time they end up useless. If you need help with fastboot I will help.
Click to expand...
Click to collapse
How does one go about trying to "fastboot a recovery.img?" I'm very limited in my knowledge on these things...
ggoodman1022 said:
How does one go about trying to "fastboot a recovery.img?" I'm very limited in my knowledge on these things...
Click to expand...
Click to collapse
You can follow the instructions at htcdev.com if you haven't yet unlocked your bootloader. After following the instructions they provide for you, you can download http://forum.xda-developers.com/showthread.php?t=1902381 and write it to the recovery partition via fastboot command. To finally flash it, make sure you're in the bootloader and you see "FASTBOOT USB". Hold the shift key and right-click, and click "Open command window here". Now place TWRP in the folder used to push the Unlock_code.bin (Contains fastboot.exe and is usually located at C:\Android or C\:fastboot) and type "fastboot flash recovery (name of recovery file).img. If you want, I can elaborate further.
kcipopnevets said:
You can follow the instructions at htcdev.com if you haven't yet unlocked your bootloader. After following the instructions they provide for you, you can download http://forum.xda-developers.com/showthread.php?t=1902381 and write it to the recovery partition via fastboot command. To finally flash it, make sure you're in the bootloader and you see "FASTBOOT USB". Hold the shift key and right-click, and click "Open command window here". Now place TWRP in the folder used to push the Unlock_code.bin (Contains fastboot.exe and is usually located at C:\Android or C\:fastboot) and type "fastboot flash recovery (name of recovery file).img. If you want, I can elaborate further.
Click to expand...
Click to collapse
I'll give this a shot next time I have access to a windows machine... Some time in the next few days or so
ggoodman1022 said:
I'll give this a shot next time I have access to a windows machine... Some time in the next few days or so
Click to expand...
Click to collapse
This can be done on a Mac or Linux box as well, ADB is available for both, just substitute the appropriate filenames or commands for each OS.
Sent from my Nexus 4 using Tapatalk
acejavelin said:
This can be done on a Mac or Linux box as well, ADB is available for both, just substitute the appropriate filenames or commands for each OS.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Sweet!! I'll look into it after I finish my homework
kcipopnevets said:
You can follow the instructions at htcdev.com if you haven't yet unlocked your bootloader. After following the instructions they provide for you, you can download http://forum.xda-developers.com/showthread.php?t=1902381 and write it to the recovery partition via fastboot command. To finally flash it, make sure you're in the bootloader and you see "FASTBOOT USB". Hold the shift key and right-click, and click "Open command window here". Now place TWRP in the folder used to push the Unlock_code.bin (Contains fastboot.exe and is usually located at C:\Android or C\:fastboot) and type "fastboot flash recovery (name of recovery file).img. If you want, I can elaborate further.
Click to expand...
Click to collapse
So I finally got around to doing this, after buying a replacement phone off a guy on Craigslist, but I would still like to try and get this phone back up and running... I downloaded all the files and installed adb, etc. When I try to run the command, "fastboot flash recovery TWRP_2.6.3.0_Vigor_PH98IMG.zip" I get the following in the terminal:
sending 'recovery' (6323 KB)...
OKAY [ 1.464s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.780s
Any other ideas??
ggoodman1022 said:
So I finally got around to doing this, after buying a replacement phone off a guy on Craigslist, but I would still like to try and get this phone back up and running... I downloaded all the files and installed adb, etc. When I try to run the command, "fastboot flash recovery TWRP_2.6.3.0_Vigor_PH98IMG.zip" I get the following in the terminal:
sending 'recovery' (6323 KB)...
OKAY [ 1.464s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.780s
Any other ideas??
Click to expand...
Click to collapse
You don't flash the zip, extract the file and flash the recovery.img file.
Sent from my Nexus 4 using Tapatalk
acejavelin said:
You don't flash the zip, extract the file and flash the recovery.img file.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
got it. thanks! it said the recovery was successful, but it still gets stuck in the bootloop :crying:
It may be time to admit what I feared from the moment it hit the water...
ggoodman1022 said:
got it. thanks! it said the recovery was successful, but it still gets stuck in the bootloop :crying:
It may be time to admit what I feared from the moment it hit the water...
Click to expand...
Click to collapse
Wipe, flash a ROM, and manually flash boot image... Other than that, could be toast.
Sent from my Nexus 4 using Tapatalk
acejavelin said:
Wipe, flash a ROM, and manually flash boot image... Other than that, could be toast.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Can it be a stock ROM, or would it have to be something like CyanogenMod?
ggoodman1022 said:
Can it be a stock ROM, or would it have to be something like CyanogenMod?
Click to expand...
Click to collapse
I think its irrelevant at this point... Personally, I would use EclipticRez v9 or Tachyon as they are both rock solid ROMs. EclipticRez includes an Aroma installer script, so it might be a little easier (select S-ON and Lunar kernel).
Sent from my Nexus 4 using Tapatalk
acejavelin said:
I think its irrelevant at this point... Personally, I would use EclipticRez v9 or Tachyon as they are both rock solid ROMs. EclipticRez includes an Aroma installer script, so it might be a little easier (select S-ON and Lunar kernel).
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I actually found this thread earlier - http://forum.xda-developers.com/showthread.php?t=2632629 and followed the instructions, it was giving me some trouble around step 10 and kept going back into the bootloop. Then I tried it for probably the 5th time and it finally worked!! So the phone is back to full function now. I've been out of the house for a few hours, but it worked before your last reply literally right before I walked out the door.
Thank you SOOOO SOOOO SOOOOO much for the advice both on this thread and on that one I mentioned above (since it was also your instructions there)
ggoodman1022 said:
I actually found this thread earlier - http://forum.xda-developers.com/showthread.php?t=2632629 and followed the instructions, it was giving me some trouble around step 10 and kept going back into the bootloop. Then I tried it for probably the 5th time and it finally worked!! So the phone is back to full function now. I've been out of the house for a few hours, but it worked before your last reply literally right before I walked out the door.
Thank you SOOOO SOOOO SOOOOO much for the advice both on this thread and on that one I mentioned above (since it was also your instructions there)
Click to expand...
Click to collapse
No prob... glad you got it working. Water damage is weird, hopefully it sticks!
acejavelin said:
No prob... glad you got it working. Water damage is weird, hopefully it sticks!
Click to expand...
Click to collapse
The [semi] good news is that I found one on Craigslist (same phone because I really like it) for just $60 a couple days after I got fed up with using the OG Incredible. And the guy had 2 extra batteries, a case, and ghost armor on the screen as well. So now I have the original Rezound and the spare.