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:
Related
I've searched this thread, and google with no clear answer as to what to do to solve this problem, a similar thread exists but it looks just like troll answers so here is my issue! I've rooted and installed the CWM but now my Jetstream seems to crash everytime I press the power button to lock the screen, also when the screen locks itself. I've tried resetting to factory settings, nothing works. Any help would be greatly appreciated
Mitchface said:
I've searched this thread, and google with no clear answer as to what to do to solve this problem, a similar thread exists but it looks just like troll answers so here is my issue! I've rooted and installed the CWM but now my Jetstream seems to crash everytime I press the power button to lock the screen, also when the screen locks itself. I've tried resetting to factory settings, nothing works. Any help would be greatly appreciated
Click to expand...
Click to collapse
Are you still on the factory kernel or did you upgrade to the DoomKernel? I found the reboots happened with the DoomKernel but have not had a single reboot since I went back to the factory kernel.
ATT Intruder said:
Are you still on the factory kernel or did you upgrade to the DoomKernel? I found the reboots happened with the DoomKernel but have not had a single reboot since I went back to the factory kernel.
Click to expand...
Click to collapse
Im still on doomkernel, I don't know how to go back to normal, this is my first Android device haha I only got it because it was 169.99 on a one year term since I work for Rogers in Canada. I could fix my iPhone easily but this is proving to be a little more challenging
here's what you need to do:
backup whatever you can
Re-lock the bootloader. (using the instructiones at htcdev.com/bootloader)
download and run the RUU file from htc.com/us
it will update the version of the device and will clear all the data from it, including root access and kernels
now that the device is like new again - root it if you wish to, but do not flash the kernel by doomlord. its not stable.
Okay so to relock bootloader do I just plug it in and go to fastboot and use the command fastboot oem lock? I will try when I get home from work, I tried this before but got an error when I tried to use the RUU installer I cant remember what it was exactly, but ill post results when I have them
Mitchface said:
Okay so to relock bootloader do I just plug it in and go to fastboot and use the command fastboot oem lock? I will try when I get home from work, I tried this before but got an error when I tried to use the RUU installer I cant remember what it was exactly, but ill post results when I have them
Click to expand...
Click to collapse
Correct. Relock, run the Ruu and then root and install the doom recovery. I've done everything but put his kernel back on (not the insecure kernel, that gives you root) and am very pleased with how my Jetstream functions. Still needs a good custom ROM though.
Sent from my SAMSUNG-SGH-I777 using XDA App
Alrighty thanks! Will try it as soon as filefactory lets me download my ROM -.- are there any other download links available because the trouble I have trying to download this is ridiculous I've been trying for 2 hours and I keep getting All free download slots on this server are currently in use.
For immediate access, upgrade to FileFactory Premium. Alternatively, you can try again shortly.
Retry download
it says the rom update utility cannot update your phone please get the correct rom update utility and try again
there is a chance that there are two different RUUs. one for Rogers and one for at&t.
try searching rogers for an RUU..
Mitchface said:
it says the rom update utility cannot update your phone please get the correct rom update utility and try again
Click to expand...
Click to collapse
If you look through the forum you will find a link for the Rogers ROM.
Sent from my SAMSUNG-SGH-I777 using XDA
Ive tried all three roms found in the dev section! The first two were exes and didnt work and when i tried to flash the zip i get an error that says FAILED Remote: 12 signature verify fail -sigh
if u'r having crashes you need to flash the RUU from Rogers. RUU means Rom Upgrade Utility. it's an exe file published by htc/rogers.
you need to d/l the file, connect the device to the computer and run it, after relocking the bootloader.
the ROMs that are in the development section are very raw and pretty much neglacted by now. do not try to flash them, it will probably only make things worse.
Okay, so where would I find the Rom from HTC. I work for Rogers and we do not provide them.
try searching the forum for a rogers version.
if you can't find one - i'd try resetting the device first.
long press the power button.(20 sec).
than turning it on while holding Vol. down. there you can find the factory reset.
if that takes you to the recovery try wiping all the data (cach,data,delvik whatever)
if nothing works, try the link below. maybe it'll work on your version.
http://www.htc.com/us/support/jetstream-att/downloads/
Booo nothing works I give up my jetstream is a brick (((
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
A long while back I used the HTC official unlock ( cant remember what it is called ), I installed clockword recovery (5.8.1.5) and rooted but didnt mess with my rom beyond that.
Today my daughter was playing a game and the phone suddenly rebooted (saw it happen) it reboots to recovery. I tried clearing the cache and factory reset still wouldnt boot. Decided to try a ROM to see if that would fix it (did CG ROM Jelly Bean) no change. Not really sure what my next step should be.
It does say "E:unknown misc partition fs_type "ext4"" at the bottom of the clockwork recovery page.
still working on this to no avail, not really sure what to try next. I am worried the tablet may have died proper like.
Halp please!
Sent from my SPH-L900 using xda app-developers app
yehoshua said:
Halp please!
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
try flashing ruu with fastboot see http://forum.xda-developers.com/showthread.php?t=1428104
copperdawgnc said:
try flashing ruu with fastboot see http://forum.xda-developers.com/showthread.php?t=1428104
Click to expand...
Click to collapse
Sorry for the long reply, I spent a TON of time figuring out how to do all this stuff for the version of stuff I beleive I have. At any rate the problem I am consistantly encoutnering is that I cant get to hboot at all. I also cant find advice on how I might repair hboot from recovery. I do have adb access from recovery and can do adb reboot-bootloader but it just thinks for a bit and comes back to recovery. I also tried many times doing the vol-down + power button to get to hboot.
So what is the next step if you cant get to hboot?
so have you done something like
adb reboot-bootloader
fastboot flash zimage zImage
fastboot flash zimage zImage
fastboot reboot
copperdawgnc said:
so have you done something like
adb reboot-bootloader
fastboot flash zimage zImage
fastboot flash zimage zImage
fastboot reboot
Click to expand...
Click to collapse
Yes, when I do adb reboot-bootloader it just reboots into recovery again. fastboot gives the <waiting for device>. I also tried copying the rom.zip from the ruu to an sd card and then using recovery to flash to it. It starts to try then ends with "Installation Aborted".
Not sure if there is a small easy to flash to rom that I could try, even if it wouldnt have much in the way of function. Not sure if this whole thing implies my flash is partially dead or something.
Thanks
Anyone have any ideas for me? I don't really see other posts covering this problem.
Thanks
yehoshua said:
Anyone have any ideas for me? I don't really see other posts covering this problem.
Thanks
Click to expand...
Click to collapse
Moderator moved the thread (thanks), mayhap someone in here can help. Anyone have any ideas?
Only thing I can think of is grabbing a proper RUU executable, there might be a thread in the view dev area that links to some, plugging in your view and try running that. You'll loose root and all but it may bring it back to life
Sent from my ADR6410LVW using Tapatalk 2
gersto said:
Only thing I can think of is grabbing a proper RUU executable, there might be a thread in the view dev area that links to some, plugging in your view and try running that. You'll loose root and all but it may bring it back to life
Sent from my ADR6410LVW using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the idea Gersto but I cant get to fastboot so I cant use an RUU (Unless there is something I dont know). I experimented a bit trying to get the errors about the misc partition and ext4 to go away but nothing I did to that stuff seemed to persist. I do have root and can access it from adb shell.
Not sure if it is the culprit but if anyone knows how to fix the problem wit my misc partition I am all earsl.
Thanks
After screwing up when flashing the wrong u-boot and xloader in fastboot, my phone won't connect in debug mode and the notification bar crashes on 15% battery. I've tried everything imaginable to fix this, factory reset, flashing almost every kdz, updating through ota, completely removing everything through fastboot and reflashing a stock kdz. Please help, i've had this problem for 3 months and nobody else has this. I just need an estimate, does it sound like a hardware problem or a software problem?
Try flashing my persist image with fastboot and see if it fixed adb.
https://mega.co.nz/#!8pt0xCqA!3-uV70G_ItL46LwE8mYCQ7FUYMEXGYNU0KDUqQRVVbo
Messing with the persist image will mess up adb
Sent from my LGMS769 using XDA Premium 4 mobile app
kuma82 said:
Try flashing my persist image with fastboot and see if it fixed adb.
https://mega.co.nz/#!8pt0xCqA!3-uV70G_ItL46LwE8mYCQ7FUYMEXGYNU0KDUqQRVVbo
Messing with the persist image will mess up adb
Sent from my LGMS769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OMG, Kuma you are god sent. Thank you so much, I almost cried just seeing that device in adb. My phone is scanning the sd but if the camera and battery percentage works, everything will be fixed. No doubt thanked your post. Haha, again thanks soo much!!
If anyone else has this same problem this is what I did:
1.Downloaded kuma's persist.img
2.Moved the persist.img to the fastboot yours folder
3.Opened fastboot selected option 1, then used the command (fastboot flash persist persist.img)
4.reboot
Thank you both. This fixed my issue with ADB not showing up. Yay I have ADB back!
Sent from my LGMS769 using Tapatalk
can you reupload please mega link isn't working. thank you very much
tatsuyin said:
can you reupload please mega link isn't working. thank you very much
Click to expand...
Click to collapse
Hi tatsuyin, mega link has worked fine for me just now.
Cheers . Good luck.
Sent from my LG P76020L-EUR-XX unlocked and rooted
tatsuyin said:
can you reupload please mega link isn't working. thank you very much
Click to expand...
Click to collapse
If you're trying to download the mega file from your phone, once the web page loads press the menu button and select/check "request desktop site" and you should be able to download it.
OMG !! I cant belived.
Thank you !!!!
Almost . . . . . . . .
AlbinoCookie said:
If anyone else has this same problem this is what I did:
1.Downloaded kuma's persist.img
2.Moved the persist.img to the fastboot yours folder
3.Opened fastboot selected option 1, then used the command (fastboot flash persist persist.img)
4.reboot
Click to expand...
Click to collapse
So i thought it wad gonna work. Then at the end....it says this.....
writing 'recovery'...
C:\Users\Weldon Evridge\Android-Mobile-Phone-Tools\droid manager\Android_AIO_Flasher_1.00_by_Fonehacker\Android_AIO_Flasher\tools>
FAILED (remote: partition does not exist)
finished. total time: 2.275s
Hi, I think I might have a similar problem. I was running on stock JB for a while and then decided to give a try to CM10 or 11. I tried to flash CM11 without artas's recovery, so it did not work. So I've tried CM10, which seemed pretty buggy and camera was not working. Then I did all the reading etc and tried about 10 different roms based on 4.3, .4.4 and even stock rom, camera did not work anywhere.
Every time I try to open an app using camera, it reports: Unfortunately: com.android.camera has stopped. I have tried all kinds of resets (everything available in both CWM and TWRP), online kdz fix, back to stock rom (tried multiple versions of JB) but nothing seems to help. Any ideas? I've tried to flash this persist.img using adb but I got the same error saying that there is no such partition.
Thanks for response.
WeldonEvridge said:
So i thought it wad gonna work. Then at the end....it says this.....
writing 'recovery'...
C:\Users\Weldon Evridge\Android-Mobile-Phone-Tools\droid manager\Android_AIO_Flasher_1.00_by_Fonehacker\Android_AIO_Flasher\tools>
FAILED (remote: partition does not exist)
finished. total time: 2.275s
Click to expand...
Click to collapse
I'm not sure if you have fixed your phone yet, but try having a fresh offline flash, then copy the persist img.
Help bro
It (persist image) use only LG L9 .
Can I use for my motorola razr. Because I have same problem on my phone.
kuma82 said:
Try flashing my persist image with fastboot and see if it fixed adb.
https://mega.co.nz/#!8pt0xCqA!3-uV70G_ItL46LwE8mYCQ7FUYMEXGYNU0KDUqQRVVbo
Messing with the persist image will mess up adb
Sent from my LGMS769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hello, can you upload again this file?
Thanks!
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?