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
Related
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
Hi
deleted the following apps as it was nagging while restarting the phone.
SprintZone_SZ_2.5.15.apk
Sprint_InstallerNC_2.1.0.apk
SprintMobileWallet_1.5.apk
vtt-sprint_T.5.1.0.74.apk
I have a backup of these apps
now when I start the phone, it continuously shows "Contacting Network" then fails
then after a while it shows "Hands Free Activation"
Your activation could not be completed. Please try again later.
if I press "OK" it shows
Sorry!
The application SprintOmaDm (process com.motorola.android.sprintomadm) has stopped unexpectadly. Please try again
ROM details
45.4.13.MB855.Sprint.US
Androd 2.3.5
Baseban Ver N_01_29.10R
Kernel 2.6.32.29
Build No: 4.5.1A-1_SUN-254_13
the phone is rooted
please help
Did you try restoring the apps you deleted to see if that fixed it?
Sent from my MB855 using xda app-developers app
Shad0wguy said:
Did you try restoring the apps you deleted to see if that fixed it?
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
can't access the home screen. it is constantly trying to connect to the network and will not go further.
it restarts the network search after it fails. loop.
problem got worse.
tried fastboot recovery and flashed cg59.smg boot
now the phone shows "Failed to boot 2
Starting RSD mode
please help
From where did you take that cg?
Cg59 is not recovery. How did you got such idea?
peetr_ said:
From where did you take that cg?
Cg59 is not recovery. How did you got such idea?
Click to expand...
Click to collapse
followed this thread.
http://forum.xda-developers.com/showthread.php?t=1573727
You probably mean this...
scottgl9 said:
Confirmed! I got rid of the aweful 2.3.5 electrify bootloader. Just did this:
[email protected]:~/Desktop/SMG_BP011UP$ fastboot flash boot CG59_0x00000130.smg
sending 'boot' (3294 KB)...
OKAY [ 0.206s]
writing 'boot'...
OKAY [ 0.734s]
finished. total time: 0.940s
Click to expand...
Click to collapse
That was last post from scottgl9...
And there is written fastboot flash boot, not recovery. And noone knows, where did he take that.
You need to take and try 2.3.5 recovery dump.
peetr_ said:
You probably mean this...
That was last post from scottgl9...
And there is written fastboot flash boot, not recovery. And noone knows, where did he take that.
You need to take and try 2.3.5 recovery dump.
Click to expand...
Click to collapse
looks like I may have to wait a long time if I am lucky! otherwise parts for sale! new phone just two weeks old from ebay India about $500 wasted.
You need to read all over here, download the dump and try flashing things with fastboot (in your case, just recovery), if you find a solution, you will help others too.
peetr_ said:
You need to read all over here, download the dump and try flashing things with fastboot (in your case, just recovery), if you find a solution, you will help others too.
Click to expand...
Click to collapse
thanks peetr
I am prepared to try any options available. but the thing is I have only two weeks familiarity with Android and this is my first Android phone.
hope I can get some help with flash mem dump using RSD
found a solution
its here
http://forum.xda-developers.com/showthread.php?t=1785561
portman said:
can't access the home screen. it is constantly trying to connect to the network and will not go further.
it restarts the network search after it fails. loop.
problem got worse.
tried fastboot recovery and flashed cg59.smg boot
now the phone shows "Failed to boot 2
Starting RSD mode
please help
Click to expand...
Click to collapse
i got past this error, you need to get a few files for the photon, one is an sbf (511 mb), another is the stock rom 2.3.5 which you will install through bootstrap, and third when you finally boot into the rom itself, another sbf through rsd and you're good to go. check the "revive the photon from grave" thread, it is all there
say thanks, it helps motivate :angel:
Hi,
Does anyone know how to fix the problem in the attached pictures?
Thanks,
Seems to be an issue with your bootloader, try flashing a new one through fastboot
fastboot flash hboot hboot.img
Sent from my Nexus 4 using xda premium
i got same problem, Does anyone know how to fix it?
Fastboot flash a Google stock image for it. Worked for me..... twice
Sent from carbon note 2 on XDA premium app
Booting Failed
Im having the same problem, Can someone help me? I am a bit of a noob. i did download nexus root tool kit. But now i cant even get it to be seen on the computer. all i can hit is restart bootloader or power off. Everything else leads to booting failed.please help need tablet for school.
Help!!!
Okay. i messed up somewhere when trying to flash back to factory rom and completely restore my Nexus 7(I had rooted it and flashed to a custom rom perfectly fine, just wanted to go back to factory just because). Because now whenever i turn on my nexus it says booting failed. Can someone use team viewer or something with me to help me get this fixed. i really need my Nexus for school...
If you need teamviewer I'll be at a PC soon but you should be able to do all this yourself quite easily
Which model do you have 2012? 2013? WiFi? Gsm?
Do you have adb and fastboot set up on PC?
Windows? Linux?
Bootloader locked or unlocked right now?
Boot to bootloader and write down everything on screen here
Let me know and I'll get you the proper software
Sent from my Nexus 7 using XDA Premium 4 mobile app
Thanks for replying
demkantor said:
If you need teamviewer I'll be at a PC soon but you should be able to do all this yourself quite easily
Which model do you have 2012? 2013? WiFi? Gsm?
Do you have adb and fastboot set up on PC?
Windows? Linux?
Bootloader locked or unlocked right now?
Boot to bootloader and write down everything on screen here
Let me know and I'll get you the proper software
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have the 2012 wifi version of the Nexus 7. i have ADB set up on my computer but i'm not sure about fastboot... Bootloader is unlocked. just booted to bootloader, it says google in the middle, a little unlocked lock at the bottom, and with the volume up and down i can choose start, restart bootloader, recovery mode, and power off. When i press start, nothing happens, the screen flashes though for half a second.... Sometimes it will say boot failed at the top left.
Thanks in advanced. i would extremely prefer to do this in team viewer because i'm good with electronics most of the time, but when it comes to this stuff i have no clue what to do. i have watched countless videos with no success.
You'll need to download factory image here
https://developers.google.com/android/nexus/images
Unzip it
Run flash all.bat from fastboot
http://forum.xda-developers.com/showthread.php?t=2277112
I won't be near a PC for about 7-8 hours. If your stuck let me know around then and I can help
Sent from my Nexus 4 using XDA Premium 4 mobile app
THanks!
demkantor said:
You'll need to download factory image here
https://developers.google.com/android/nexus/images
Unzip it
Run flash all.bat from fastboot
http://forum.xda-developers.com/showthread.php?t=2277112
I won't be near a PC for about 7-8 hours. If your stuck let me know around then and I can help
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok so i did the flash all thing and it worked!!! Now do i follow the custom recovery steps? because still when i press start it says booting failed
Edit: i went ahead and did the recovery thing from the one i downloaded from the site you told me to go to. and i still get booting failed
Try this
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now double check you downloaded the correct factory image probably a good idea to check md5sum as well
Then run flashall.bat again
Let me know if that works
Sent from my Nexus 4 using XDA Premium 4 mobile app
errors
demkantor said:
Try this
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now double check you downloaded the correct factory image probably a good idea to check md5sum as well
Then run flashall.bat again
Let me know if that works
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
when typing in the first command it gave me all okays until erasing 'cache'...
Failed <command write failed <No such device or address>>
After that i thought "hmm maybe thats supposed to happen?" so i went ahead to the erase boot command, again
erasing 'boot'...
Failed <command write failed <unknown error>>
Please help. im soooo confused im about to explode... haha
Thanks
EDIT: i realize whenever i run the flash all file, it says
sending bootloader
Failed <command write failed <Invalid argument>>
and then bootloader reboots fine...
then
checking version-bootloader...
Failed
Device version-bootloader is '4.18' .
Update requires '4.23' .
Is this why its not working?? if so how do i update my bootloader?
Can you either attach a pic or write down everything from bootloader screen line by line
Sent from my Nexus 4 using XDA Premium 4 mobile app
Pics
demkantor said:
can you either attach a pic or write down everything from bootloader screen line by line
sent from my nexus 4 using xda premium 4 mobile app
Click to expand...
Click to collapse
View attachment 2551680
View attachment 2551681
First Picture is the flashall file
Second picture is when i type the fastboot erase system -w command
xlilCHeesEitxX3 said:
View attachment 2551680
View attachment 2551681
First Picture is the flashall file
Second picture is when i type the fastboot erase system -w command
Click to expand...
Click to collapse
If you meant the bootloader screen of my nexus im sorry!!
okay so it has the volume rocker buttons and stuff at the top right as usual.
now in order from top to bottom
Fastboot mode (red letters)
Product Name - grouper
Variant - grouper
HW Version - ER3
Bootloader Version - 4.18
Baseband version - N/A
Serial Number - 015d24a42b23ea09
Signing - not defined yet
Lock State - Unlocked (red letters)
hope this is what you were looking for
well I'm at a PC if you want to use team view, if you don't get this until later what I would do is flash everything separate
fastboot flash bootloader bootloader-grouper-4.23.img
(or whatever it is labled)
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash data userdata.img
fastboot flash boot boot.img
if this doesn't work than put up the screenshots of cmd again
Team Viewer
demkantor said:
well I'm at a PC if you want to use team view, if you don't get this until later what I would do is flash everything separate
fastboot flash bootloader bootloader-grouper-4.23.img
(or whatever it is labled)
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash data userdata.img
fastboot flash boot boot.img
if this doesn't work than put up the screenshots of cmd again
Click to expand...
Click to collapse
I really hope you are still able to use Team Viewer at the time. I tried flashing everything separately but still a no go ....
Thanks so much for all the help so far.. i really appreciate it.
Screenshots
xlilCHeesEitxX3 said:
I really hope you are still able to use Team Viewer at the time. I tried flashing everything separately but still a no go ....
Thanks so much for all the help so far.. i really appreciate it.
Click to expand...
Click to collapse
View attachment 2552860
View attachment 2552861
1st image is when i flash the system
2nd is when i flash the bootloader
Yeah this is not looking too good, I've seen a few times that people have gotten there nexi working when the failed boot pops up but when all these flashes fail it becomes unlikely. Is warranty up? If it is we can try when I get to a PC again but that may not be for a while.
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Yeah this is not looking too good, I've seen a few times that people have gotten there nexi working when the failed boot pops up but when all these flashes fail it becomes unlikely. Is warranty up? If it is we can try when I get to a PC again but that may not be for a while.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I think my warranty is up... but alright. maybe im doing something wrong? who knows hopefully we can get it fixed
---------- Post added at 10:54 AM ---------- Previous post was at 10:26 AM ----------
xlilCHeesEitxX3 said:
I think my warranty is up... but alright. maybe im doing something wrong? who knows hopefully we can get it fixed
Click to expand...
Click to collapse
i finnaly got the bootloader to flash. so now everything works except when i try to flash the system... it says
erasing 'system'...
OKAY ( 0.095s)
Sending 'system' <471804 KB>...
FAILED <unknown status code>
finished. total time: 61.355s
hopefully you know of a fix
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.
I installed an app to change the boot animation on my Atrix 4g and when I rebooted to see it, all i get is the m logo with dual core technology under it. It is rooted and i didn't flash any new roms or anything. i wiped the cache partition from the recovery menu and also " wipe data/factory reset" but it still doesn't boot up.
its on android 2.3.6 build 4.5.141
please help me :crying:
Do you have recovery software?
Fervi
Just restore the system partition from the backup you SHOULD do before any modification and you will be good to go.
Otherwise, delete the faulty bootanimation and restore the original via adb on recovery and reboot.
There is also a no bootanimation option on build.prop, althrough I'm not sure if it's avaiable on 2.3
Enviado desde mi MB860 usando Tapatalk 2
i don't have any recovery software or backups made.
If you have fastboot option, you can install TWRP (or CWM) and then install other rom (like Motorola Atrix ICS [4.0])
Fervi
ferviverus said:
If you have fastboot option, you can install TWRP (or CWM) and then install other rom (like Motorola Atrix ICS [4.0])
Fervi
Click to expand...
Click to collapse
and how would I accomplish this?
http://wiki.cyanogenmod.org/w/Template:Recovery_install_fastboot
Remember - There is no guarantee that everything will go fine. You do it at your own risk
Fervi
ferviverus;54222742
Remember - There is no guarantee that everything will go fine. You do it at your own risk
Fervi[/QUOTE said:
whenever i type fastboot devices into command prompt even when it is connected and in fastboot it doesn't work.
Click to expand...
Click to collapse
So I got fastboot and everything working. I think flashing the sbf with rsd lite might work, only problem is that whenever I try to download the sbf files it takes me to some ilivid download manager. Soo anyone know where I can download the actual sbf?
specter187 said:
So I got fastboot and everything working. I think flashing the sbf with rsd lite might work, only problem is that whenever I try to download the sbf files it takes me to some ilivid download manager. Soo anyone know where I can download the actual sbf?
Click to expand...
Click to collapse
http://sbf.droid-developers.org/
Sent from my MB886 CM10.2/4.3.1
i think things just got worse
palmbeach05 said:
[ul]htt://sbfdroid-developers. org/[/url]
Sent from my MB886 CM10.2/4.3.1
Click to expand...
Click to collapse
I tried flashing and now when I put my phone into rsd mode its says: failed to boot 1
PwrReason: PWR_KEY_PRESS
starting fastboot protocol support
and when I try to put it into fastboot my phone comes on says something and it turns off to quickly for me to see what the text says.
and when I just power on without pressing anything it says failed to boot 1 and that same confounded dooming m logo
I feel as though my atrix is unflashable or something.
specter187 said:
I tried flashing and now when I put my phone into rsd mode its says: failed to boot 1
PwrReason: PWR_KEY_PRESS
starting fastboot protocol support
and when I try to put it into fastboot my phone comes on says something and it turns off to quickly for me to see what the text says.
and when I just power on without pressing anything it says failed to boot 1 and that same confounded dooming m logo
I feel as though my atrix is unflashable or something.
Click to expand...
Click to collapse
its actually in a state of i need to be unlocked and searching failed to boot 1 would have brought you to this - http://forum.xda-developers.com/showthread.php?t=1528729
the sbf download link from the forum link you posted doesn't work
A DEAD PAGE 404 ERROR
HIDE THE PIE!!!!
specter187 said:
the sbf download link from the forum link you posted doesn't work
A DEAD PAGE 404 ERROR
HIDE THE PIE!!!!
Click to expand...
Click to collapse
Really? the mini sbf that I'm referring to is not a full sbf. it is a 1 MB file that you should get and do to obtain root.
Where in what you have said in this entire thread did you unlock the bootloader?
palmbeach05 said:
Really? the mini sbf that I'm referring to is not a full sbf. it is a 1 MB file that you should get and do to obtain root.
Where in what you have said in this entire thread did you unlock the bootloader?
Click to expand...
Click to collapse
my bootloader isn't unlocked
specter187 said:
my bootloader isn't unlocked
Click to expand...
Click to collapse
Then I would highly advise that you unlock your bootloader before any more help is given to you. I don't say that in a mean way, I say that in a strong recommendation way. Without that bootloader being unlocked, there is little help we can do to get you back up and running.
palmbeach05 said:
Then I would highly advise that you unlock your bootloader before any more help is given to you. I don't say that in a mean way, I say that in a strong recommendation way. Without that bootloader being unlocked, there is little help we can do to get you back up and running.
Click to expand...
Click to collapse
my bootloader is now unlocked
AVAAAAST YEE!
I HAVE SALVATION! MY PHONE IS ON! I HAVE SEEN THE MOTOBLUR SCREEN.
i am almost afraid now to root it
here goes nothing
specter187 said:
my bootloader is now unlocked
Click to expand...
Click to collapse
delete, wifi on my end didn't post this when I originally did. congrats btw!
Update?
there is an update to upgrade it to 4.5.145 i tried and i got a failed to boot 4 starting rsd protocol support
but i fixed that. So can i not update a phone with unlocked bootloader? or is there some kind of run around?