Related
Here is a link to the latest US AT&T 4.5.91 sbf with the unlocked bootloader and /preinstall root added.
Warning!
Use this with caution, and don't downgrade to 1.26, 1.5.7, or 1.8.3 unless it has the unlocked bootloader properly integrated into the sbf, and you have already used fastboot to unlock. In general I don't recommend downgrading at all.
If you already installed the official sbf without modification or updated to OTA without unlock, and not unlocked, then I recommend waiting and not installing anything from anyone for now.
We do have reports of hard bricks. We don't yet understand why only a few people have hard bricked. You are doing this at your own risk.
Download:
4.5.91 sbf with unlocked bootloader and /preinstall root
Thanks the2dcour!
Thanks is awasome
Nice. Is this safe? This is the official GB AT&T update with unlocked boot-loader correct? Can you use the preinstall method to root afterwards?
Has anyone used this over Gingerblur?
Great, what's the difference between this and another sbf posted today itself. Looks like both are same.
Sent from my MB860 using XDA Premium App
Did someone already tested this?
Sent from my MB860 using XDA App
Noob question... can I update this over the OTA that was leaked by Sam? Since his wasn't unlocked..?
anupash said:
Did someone already tested this?
Click to expand...
Click to collapse
This was tested before release on two phones.
ceo.mtcl said:
Great, what's the difference between this and another sbf posted today itself. Looks like both are same.
Click to expand...
Click to collapse
This is the same sbf, but with the unlocked bootloader added.
n0kia916 said:
Noob question... can I update this over the OTA that was leaked by Sam? Since his wasn't unlocked..?
Click to expand...
Click to collapse
I'd also be interested to know whether this is a possibility.
Even better, can you update over the OTA version that I flashed using the Motorola Update Service???
n0kia916 said:
Noob question... can I update this over the OTA that was leaked by Sam? Since his wasn't unlocked..?
Click to expand...
Click to collapse
If you already installed OTA without an unlock. Then you have the fuse burned that prevents you from downgrading to the official 1.8.3 sbf. If you do, you will brick your phone.
This sbf should work over the OTA. Think of it like a full reinstall of Windows, but in this case it is Android. To extend the metaphor further, this sbf is like having SP1 slipstreamed in, in that it has the unlocked bootloader integrated.
gogorman said:
I'd also be interested to know whether this is a possibility.
Even better, can you update over the OTA version that I flashed using the Motorola Update Service???
Click to expand...
Click to collapse
As I said in the post above, yes.
Isn't there a rooted version of this on the pudding page? or is it different
I updated over the OTA 2.3.4 by Samcripp but..
edgan said:
If you already installed OTA without an unlock. Then you have the fuse burned that prevents you from downgrading to the official 1.8.3 sbf. If you do, you will brick your phone.
This sbf should work over the OTA. Think of it like a full reinstall of Windows, but in this case it is Android. To extend the metaphor further, this sbf is like having SP1 slipstreamed in, in that it has the unlocked bootloader integrated.
Click to expand...
Click to collapse
So I decided to try and use RSD Lite 5.0 to update with the sbf posted from edgan. Previous version I had was the OTA update that was posted by Sammcripp but I wanted an unlocked bootloader. While waiting for the rsd to finish it failed at 99 percent when the phone rebooted and got an error 0x1000.. at this point I was ****ting myself..wtf! So it automatically went to fastboot mode and nothing else.. not even volume down menu.
To resolve this issue.. I did a fastboot oem unlock (your UID #)
then did a fastboot reboot and first it was stuck at the dual core screen. I rebooted again and did the volume down~ approach and was able to get into Recovery mode then allowed me to wipe data / cache and restore to factory defaults... bam phone booted up fine with unlocked message and able to use my phone again.. thanks Edgan! lol sorry if It's hard to understand me..
Also just ran quadrant and comparing to the leak 2.3.4 by samcripp this one gives me 300 more points consistently....
n0kia916 said:
So I decided to try and use RSD Lite 5.0 to update with the sbf posted from edgan. Previous version I had was the OTA update that was posted by Sammcripp but I wanted an unlocked bootloader. While waiting for the rsd to finish it failed at 99 percent when the phone rebooted and got an error 0x1000.. at this point I was ****ting myself..wtf! So it automatically went to fastboot mode and nothing else.. not even volume down menu.
To resolve this issue.. I did a fastboot oem unlock (your UID #)
then did a fastboot reboot and first it was stuck at the dual core screen. I rebooted again and did the volume down~ approach and was able to get into Recovery mode then allowed me to wipe data / cache and restore to factory defaults... bam phone booted up fine with unlocked message and able to use my phone again.. thanks Edgan! lol sorry if It's hard to understand me..
Also just ran quadrant and comparing to the leak 2.3.4 by samcripp this one gives me 300 more points consistently....
Click to expand...
Click to collapse
I don't know why you would see any performance difference. It should be exactly the same.
As for your 0x1000 problem, I have no idea why you got this. I tried this on some phones, and didn't have this problem. Though I used sbf_flash instead of RSD Lite 5.0.
I went back and checked the fuses on one phone to be sure a new one hadn't been blown. It came up the way I expected, not blown.
cat ReservedOdm
10000000000010001000100000000
Is that cat /mnt/proc/ReservedOdm that gives those 32 bits?
10000000000010001000100000000
This is great. What version of RSD does this work with? I did my friends with another method, and was missing all sounds/motoblur login didn't work. I will refer him to this thread.
From seeing the new MotoBlur, it is really nice. The screen rotation animation is very nice (not sure why all OEM's don't do that) very smooth.
edgan said:
I don't know why you would see any performance difference. It should be exactly the same.
As for your 0x1000 problem, I have no idea why you got this. I tried this on some phones, and didn't have this problem. Though I used sbf_flash instead of RSD Lite 5.0.
I went back and checked the fuses on one phone to be sure a new one hadn't been blown. It came up the way I expected, not blown.
cat ReservedOdm
10000000000010001000100000000
Click to expand...
Click to collapse
Before I flashed with rsd my RerservedOdm was and still is after upgrade is 10000000000010001000300004000 which showed my fuse was blown.
I didn't use fruit/pudding with the samcripp update. just did update.zip from the recovery.
stvmac11 said:
Isn't there a rooted version of this on the pudding page? or is it different
Click to expand...
Click to collapse
I have the same question. I just finished downloading the one on the pudding thread then saw this and am downloading it now. Does this have root? Is there any difference between the two?
lutharigno said:
I have the same question. I just finished downloading the one on the pudding thread then saw this and am downloading it now. Does this have root? Is there any difference between the two?
Click to expand...
Click to collapse
This doesn't come rooted.. you would have to do it again real quick.
OK I just bought another atrix of my friend who had already updated to the ota last night, will it be safe for me to use this?
Sent from my MB860 using XDA Premium App
Telstra ROM showing update available to ICS
System upgrade to 3.44.841.3
Anyone else getting this?
My phone is on the standard Telstra ICS ROM, however is S-off and unlocked... and has recovery if I update will this bork my phone?
Download Here https://docs.google.com/open?id=0B_yipCshKsIQa3B6bHl6UnVDMGs 58.8MB
I upgraded to this about 2 days ago, admittedly on a stock Velocity....rumblings seem to say that this is a radio fix from Telstra only at this stage (and an unsuccessful one at that)
Ah righto, I attempted applying it but it just made my phone display a belly up android with a hazard sign sticking our of its belly, I'm uploading the file now for people to play with should be done soon :laugh:
I did the upgrade on stock too, any idea what it was supposed to fix? I've yet to notice any differences, not that I noticed any problems before...
Sent from my HTC Velocity 4G using xda
I do believe this article may enlighten you.
Not sure.. That's really for the nexus in US only. Maybe related...
One thing I just noticed with this update is that it finally muted the camera sounds when the phone is on silent
Leigh Kennedy said:
I do believe this article may enlighten you.
Click to expand...
Click to collapse
I'm not sure that's it. The patent in my understanding is about apps/contacts/other stuff showing up in the universal search, which mine still does after the update.
Update fails. any hints welcome
I have a Velocity with the OTA 4.0.3 ICS update. When I bought it I tried to root it using hansoon2000s 1 in all kit. I did unlock the bootloader, but attempts to gain root access failed so at that time I relocked the bootloader and just forgot about it.
When I try to install the 3.44.841.3 update, the phone shuts down then reboots to the FASTBOOT menu which gives me the option of
BOOTLOADER,
REBOOT,
REBOOT BOOTLOADER or
POWER DOWN
and it shows at the top *RELOCKED*.
If I select BOOTLOADER I go to the HBOOT menu and I can see
FASTBOOT
RECOVERY
FACTORY RESET
CLEAR STORAGE
SIMLOCK
IMAGE CRC
I have limited skills but I am guessing if I got to the recovery menu I would be able to choose a zip file to run and I could point it at the OTA zipfile which it downloaded, but when I go to recovery it just goes back to the FASTBOOT menu.
Any ideas which course of action I should take. Because it's not rooted I don't have a good backup of app data so I'd really prefer not to take any action which is going to set the phone back to Factory unless I am fairly certain of the outcome. I'm still not even sure that I need to apply this update because I have no issues with my phone (but just for the sake of the exercise lets presume I'm trying to load a Jellybean OTA update, which is something I definitely would want to do even if I reset the phone).
Ideas or suggestions ?
Bro use all in one to unlock bootloader from the menu your talking about select recovery then when it boots into a recovery you chose from the all in one use the volume to navigate to the zip file there's a prerooted gb one that I'm using then once you install it and phone reboots let the phone update to ics
Sent from my HTC PH39100
I've got a feeling that this may have updated the Velocity to a custom hboot version, because now I'm having all sorts of trouble with custom kernals and roms. Investigating now to make sure it's not my own derpiness that's causing this.....
Demomanca said:
I've got a feeling that this may have updated the Velocity to a custom hboot version, because now I'm having all sorts of trouble with custom kernals and roms. Investigating now to make sure it's not my own derpiness that's causing this.....
Click to expand...
Click to collapse
Yeah same thing happened to me because of using a deodexed rom, but you can get it fixed pretty easily.
Only problem is I don't know how to get the update to work with the stock rom as i doesn't keep. I assume leigh kennedy knows how to apply the update to stock rom and then deodex, as he did it the for stock. Hope he does it for this too.
does anyone know exactly what the update does or are we all in the dark about it? It looks like its just an update to a few APK's, using my
*mad grand karate master winzip skillz, yo*
Is it a radio fix or what?
davidcampbell said:
does anyone know exactly what the update does or are we all in the dark about it? It looks like its just an update to a few APK's, using my
*mad grand karate master winzip skillz, yo*
Is it a radio fix or what?
Click to expand...
Click to collapse
Google result said the update was to fix radio reception issues for some users, I think it was mentioned on whirlpool and a telstra support site.
OTA update.
Hi I also have received the notification for an OTA update with a link to HTC.com for my Velocity 4G, But I am running "nightly Build 4" since it came out and it is running like a dream. I also got the error msg with Mr android, belly open and a triangle warning sign. Not surprised tho. However I am thirsty still and ofc with Jelly Bean bouncing in I am tempted to flash the new ROM when it is avail.. Any ideas when it will be? :fingers-crossed:
How can I flash this OTA manually?
My Velocity is stock non rooted an locked.
The phone is stuck at the HTC screen so really only have access to fastboot...
Also, does anyone have the stock build.prop for the velocity 4g?
Ryyuu said:
How can I flash this OTA manually?
My Velocity is stock non rooted an locked.
The phone is stuck at the HTC screen so really only have access to fastboot...
Also, does anyone have the stock build.prop for the velocity 4g?
Click to expand...
Click to collapse
If you have access to fastboot, try running the RUU while connected in fastboot (drivers must be installed). This will put the phone back to a factory state, then you can check for and install the OTA
Any word on this coming to rogers? I would hate having to revert to stock to accept the update
Screw the update lol
Sent from my Holiday using xda app-developers app
Homeslice's PACman ROM doesn't prompt me for an update
Sent from my Holiday using Tapatalk 2
I'm looking to upgrade to JB or another rom as my current version is starting to act up. My phone has gotten ridiculously slow and I struggle with switching tasks and random reboots. I'm currently running 6.7.232, I flashed this version last year before the official ICS release came out. Can I flash straight to JB from my current version or do I have to go back to GB then doing the OTA upgrades? I'm very confused on what order I should follow when trying to get JB. I've been trying to find a guide but I'm afraid of bricking my phone if I try to go back to GB or straight to JB.
Thanks for the help!
jradicle11 said:
I'm looking to upgrade to JB or another rom as my current version is starting to act up. My phone has gotten ridiculously slow and I struggle with switching tasks and random reboots. I'm currently running 6.7.232, I flashed this version last year before the official ICS release came out. Can I flash straight to JB from my current version or do I have to go back to GB then doing the OTA upgrades? I'm very confused on what order I should follow when trying to get JB. I've been trying to find a guide but I'm afraid of bricking my phone if I try to go back to GB or straight to JB.
Thanks for the help!
Click to expand...
Click to collapse
My suggestion is don't touch the Jelly Bean leak. I check the thread out every couple days and nothing but problems. If you want to try Jelly Bean download Liquid Smooth 2.3. The only thing not working is Bluetooth (apparently, have no use for bluetooth).
I believe you must be on .246 to update to JB. No frozen, deleted, or altered system files either. I took the update and am very happy with it.
mikemikemikexxx said:
My suggestion is don't touch the Jelly Bean leak. I check the thread out every couple days and nothing but problems. If you want to try Jelly Bean download Liquid Smooth 2.3. The only thing not working is Bluetooth (apparently, have no use for bluetooth).
Click to expand...
Click to collapse
Even with it being an official upgrade?
Can't you flash to 246 using RSD then OTA to JB? I'm not sure you can flash to GB from 232 or whatever u said u are on. I tried doing that and got an error each time, but I was trying to go from 246 to GB. I flashed 246 over my installed 246 then OTA to JB and my device has been stellar since.
Sent from my DROID BIONIC using xda app-developers app
flyfisher7 said:
Can't you flash to 246 using RSD then OTA to JB? I'm not sure you can flash to GB from 232 or whatever u said u are on. I tried doing that and got an error each time, but I was trying to go from 246 to GB. I flashed 246 over my installed 246 then OTA to JB and my device has been stellar since.
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse
That's exactly what I ended up doing. I flashed to 246 and OTA'd to JB. It ended up working quite well. I want to put on CM10.1, hopefully I don't have to flash back to 246.
A couple things here. First you could have saved time and effort by just fxz'ing to jb directly using the 98.72.22 fxz. Yes, even over 232. Second, your comment about "hoping you don't have to downgrade" is frightening. Simple solution to that one. You can't. Period.
Sent from my Xoom using Tapatalk HD
SamuriHL said:
A couple things here. First you could have saved time and effort by just fxz'ing to jb directly using the 98.72.22 fxz. Yes, even over 232. Second, your comment about "hoping you don't have to downgrade" is frightening. Simple solution to that one. You can't. Period.
Sent from my Xoom using Tapatalk HD
Click to expand...
Click to collapse
So if you've taken the OTA JB update then you're screwed? No possible way to go back to ICS?
My phone worked great on ICS but since the forced OTA JB update it has become a complete piece of crap. I lose Verizon signal constantly and have to reboot my phone to get it back. This happens probably 6-7 times a day. Text messages hang and don't send, I get strange UI FC's, etc.
Has anyone else run into these issues? Any suggestions on how to fix?
Thanks,
Michael
Correct, there is no possible way to downgrade to ICS once you've taken the JB update. The security mechanism behind this inability to downgrade has been well understood since the ICS days. Given that you couldn't downgrade to GB from ICS, I'm not sure why so many people are surprised to find the same situation with JB.
Anyway, to fix your issues you should probably do a Factory Data Reset (FDR). This will wipe your data partition so you will have to reinstall your apps and setup the phone as if it were brand new out of the box. However, this will give it a fresh start and will likely fix the issues you're seeing with the phone.
SamuriHL said:
Correct, there is no possible way to downgrade to ICS once you've taken the JB update. The security mechanism behind this inability to downgrade has been well understood since the ICS days. Given that you couldn't downgrade to GB from ICS, I'm not sure why so many people are surprised to find the same situation with JB.
Click to expand...
Click to collapse
Honestly I am not surprised. I am the idiot who clicked OK without researching what the update was first. If I had, I wouldn't have taken it.
SamuriHL said:
Anyway, to fix your issues you should probably do a Factory Data Reset (FDR). This will wipe your data partition so you will have to reinstall your apps and setup the phone as if it were brand new out of the box. However, this will give it a fresh start and will likely fix the issues you're seeing with the phone.
Click to expand...
Click to collapse
I thought about doing that, but I was hoping not to have to do so.
Since I was also dumb enough to not have OTA root keeper installed of course I lost root too. I see there is another post about rooting stock JB using Linux, etc. Has anyone developed another method yet? I have searched but haven't found anything. I used the motofail method to get root on ICS, but no posts as to whether that works on JB or not.
Thanks,
Michael
No possibility of root without using the Linux exploit. Don't bother waiting for a windows version as it's not coming. There are "easy root" solutions out there that are basically a virtualbox image that you can just load up and run the script.
As for an FDR, you're needing to if you're having those problems. Nothing else is going to fix it.
SamuriHL said:
No possibility of root without using the Linux exploit. Don't bother waiting for a windows version as it's not coming. There are "easy root" solutions out there that are basically a virtualbox image that you can just load up and run the script.
As for an FDR, you're needing to if you're having those problems. Nothing else is going to fix it.
Click to expand...
Click to collapse
Ok so be it. I saw that post on the Easy Root using a virtualbox image.
I also saw this post: http://forum.xda-developers.com/showpost.php?p=40430047&postcount=73
Since I previously had root on ICS, will this work for me?
Thanks for patiently answering my questions, I appreciate it.
Michael
It's worth a shot. FDR won't affect the system partition at all so if it works you won't lose root doing the FDR.
SamuriHL said:
It's worth a shot. FDR won't affect the system partition at all so if it works you won't lose root doing the FDR.
Click to expand...
Click to collapse
Ok I will give it a try and go from there..
Hopefully with root restored and FDR my phone will return to what it was and I will be happy with it once again.
Thanks again,
Michael
My phone has been saying for a couple weeks now that I need to update it so i go to update it and it shuts down and then you see the android trying to complete the update then about halfway through it stops and i get the orange warning sign like it failed then the phone reboots and says update failed then i tryed rebooting it into recovery and it wont even boot into recovery.
bpc87 said:
My phone has been saying for a couple weeks now that I need to update it so i go to update it and it shuts down and then you see the android trying to complete the update then about halfway through it stops and i get the orange warning sign like it failed then the phone reboots and says update failed then i tryed rebooting it into recovery and it wont even boot into recovery.
Click to expand...
Click to collapse
Hasn't this already been discussed in the update thread? Flash the stock ATT JB, then accept the update.
bpc87 said:
My phone has been saying for a couple weeks now that I need to update it so i go to update it and it shuts down and then you see the android trying to complete the update then about halfway through it stops and i get the orange warning sign like it failed then the phone reboots and says update failed then i tryed rebooting it into recovery and it wont even boot into recovery.
Click to expand...
Click to collapse
If you ever rooted, ran a custom recovery, chances are you tweaked something under /system that's causing it to fail. Flash stock recovery and stock system then take the OTA.
Now, with my old Atrix HD, the OTA took just fine with a rooted system and Philz CWM, on my new Atrix HD, I had to be using stock recovery and unrooted...odd.
skeevydude said:
If you ever rooted, ran a custom recovery, chances are you tweaked something under /system that's causing it to fail. Flash stock recovery and stock system then take the OTA.
Now, with my old Atrix HD, the OTA took just fine with a rooted system and Philz CWM, on my new Atrix HD, I had to be using stock recovery and unrooted...odd.
Click to expand...
Click to collapse
My friend also asked me about this prob today I also told him that but thanks for the info since it's just my thinking and i havent tried still on CM11 to wait official kitkat
devilsking said:
My friend also asked me about this prob today I also told him that but thanks for the info since it's just my thinking and i havent tried still on CM11 to wait official kitkat
Click to expand...
Click to collapse
Same here!
i have the same problem but i'm on stock jb. just rooted the phone and stock bootloader. i don't now if it has something to do with not being in usa and using an AT&T phone. but it's really annoying the message every hour.
magocop said:
i have the same problem but i'm on stock jb. just rooted the phone and stock bootloader. i don't now if it has something to do with not being in usa and using an AT&T phone. but it's really annoying the message every hour.
Click to expand...
Click to collapse
The OTA update should install even without an ATT SIM card in the phone. I have a Bell Atrix HD in Canada with an unlocked bootloader. I installed the stock JB ATT ROM, ran the update, installed a customer recovery, and went back to using a custom ROM.
audit13 said:
The OTA update should install even without an ATT SIM card in the phone. I have a Bell Atrix HD in Canada with an unlocked bootloader. I installed the stock JB ATT ROM, ran the update, installed a customer recovery, and went back to using a custom ROM.
Click to expand...
Click to collapse
Did you have to call Bell to get that customer recovery? And where can I get one at?
skeevydude said:
Did you have to call Bell to get that customer recovery? And where can I get one at?
Click to expand...
Click to collapse
I apologize. I meant to say "custom" and not "customer". I was posting from my phone and didn't notice that auto correct changed the word to customer.
audit13 said:
I apologize. I meant to say "custom" and not "customer". I was posting from my phone and didn't notice that auto correct changed the word to customer.
Click to expand...
Click to collapse
I know. Just having a bit of fun
Autocorrect....Adding the wrong word for the lulz since 2009
skeevydude said:
I know. Just having a bit of fun
Autocorrect....Adding the wrong word for the lulz since 2009
Click to expand...
Click to collapse
No worries. Good thing you brought the error to my attention; otherwise, Bell would start receiving requests for the "customer" recovery files:laugh:
skeevydude said:
If you ever rooted, ran a custom recovery, chances are you tweaked something under /system that's causing it to fail. Flash stock recovery and stock system then take the OTA.
Now, with my old Atrix HD, the OTA took just fine with a rooted system and Philz CWM, on my new Atrix HD, I had to be using stock recovery and unrooted...odd.
Click to expand...
Click to collapse
I probably did when i first figured out how to use custom roms i was trying a whole bunch of them but that was awhile ago and now i dont remember how to flash a stock recovery or where to get it and i did awhile ago use RSD Lite to flash a stock rom onto my phone but that is the last thing I did and know its been sooo long i dont remember how any help from anyone would be greatly appreciated and sorry i have not got back to this post in a few days been busy doing other things but once again if anyone could help me it would be appreciated
Thanks
- Bart
Try using Myth Tools to flash back to stock, take the update, install a custom recovery, and flash a KK ROM.
http://forum.xda-developers.com/showthread.php?t=2262726
To start off with
1. No im not Boot loader Unlocked ( i forgot to Unlock Boot loader )
2. i used to be rooted? ( not sure now? )
3. i got phone it was on 4.0.4 Stock i got OTA now its on 4.1.1 Stock with Root ( not sure any more? )
4. its AT&T US
so right now what im looking at is this
I Can Charge battery with ICON %Battery
I can access Recovery ( Slandered ) Not Custom Rooted One booo
i can access Fastboot & well that white menu by holding VOL - & VOL +
i can see it telling me Device Locked Statue 0
now what happen to get to this point was this
i wanted to change the AT&T Carrier Logo to something else i download app off internet and i was stupid to give it ROOT ACCESS.... ya i know
next thing i know poof it tells me to reboot i reboot and now i see Moto Logo then nothing but Black screen.....
i try to use RSD Lite and use the .XML.zip files all 3 of them but no luck
i try everything no luck.... im freaking out..... with no luck lol.....
can someone help with this?.....
when i try to RSD LITE it i got many errors
some forums told me to Edit 2 to 3 lines to remove a VAR or somthing it started to work bu then got stuck at Boot.img and other system.img and anohter called NON-HLOS.bin?
i try to use another file called Blur_Version.77.12.22.MB886.ATT.en.US.zip
its got some strange files in it? ..... ill upload photo but i place it on sd card and try to update it but tells me somehting about ro.build pro 4.0.4 release keys ro.build pro 4.1.1? makes no since to me?
View attachment 2802750
I'm helping a friend on the same situation.
Phone doesn't boot.
Stuck on M logo.
Locked bootloader.
Able to go to AP fastboot
No custom recovery.
Particularly this is my first time dealing with a motorola phone. Have flashed HTC and have owned mostly samsung phones.
But I know my way a bit on adb and fastboot.
Anyways I'll keep an eye on this thread and let you know if I find something on my own.
I'll try with RSDLite, Myth tools and fastboot.
Maybe one of them will work.
Good luck.
Silenus21 said:
I'm helping a friend on the same situation.
Phone doesn't boot.
Stuck on M logo.
Locked bootloader.
Able to go to AP fastboot
No custom recovery.
Particularly this is my first time dealing with a motorola phone. Have flashed HTC and have owned mostly samsung phones.
But I know my way a bit on adb and fastboot.
Anyways I'll keep an eye on this thread and let you know if I find something on my own.
I'll try with RSDLite, Myth tools and fastboot.
Maybe one of them will work.
Good luck.
Click to expand...
Click to collapse
from what i can tell..... RSD LITE is not gonna work.... but im sure if i get the New 4.1.1 Update zip file that u add to SD CARD and Flash update through there it will work as long as its singed. i have 4.0.4 but keeps crashing durning install telling me ro.buildprop 4.0.4 & ro.buildprop.4.1.1 so i think that i has a 4.0.4 update file when i need a 4.1.1 but unsure where to get it? ..... so mad i spent $250 bucks on this thing to have a Rouge App do this to me lol...... next time NO more root for me lol
Have you tried mythtools??
Sent from my ATRIX HD using XDA Free mobile app
Silenus21 said:
I'm helping a friend on the same situation.
Phone doesn't boot.
Stuck on M logo.
Locked bootloader.
Able to go to AP fastboot
No custom recovery.
Particularly this is my first time dealing with a motorola phone. Have flashed HTC and have owned mostly samsung phones.
But I know my way a bit on adb and fastboot.
Anyways I'll keep an eye on this thread and let you know if I find something on my own.
I'll try with RSDLite, Myth tools and fastboot.
Maybe one of them will work.
Good luck.
Click to expand...
Click to collapse
From fastboot, I recommend unlocking the bootloader, install Philz, and flash a custom KK ROM.
Manual fastboot didn't work. Always stuck on flashing boot.img and system.img
The same happen on that step in rds lite and myth tools.
Phone said can't downgrade or something like that.
So I haven't had any luck yet.
Open to suggestions.
Sent from my SM-N900V using XDA Premium 4 mobile app
Silenus21 said:
Manual fastboot didn't work. Always stuck on flashing boot.img and system.img
The same happen on that step in rds lite and myth tools.
Phone said can't downgrade or something like that.
So I haven't had any luck yet.
Open to suggestions.
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
im just gonna sell it on Craigslist & let it be someone else issue!
News
so i went to here http://sbf.droid-developers.org/phone.php?device=7 to just see if they added a new Update file and Poof they did.
they added: Android 4.1.1
Blur_Version.98.5.38.MB886.ATT.en.US
so i ran RSD LITE nothing fail, i edit the xml, nothing fail... i used the Mytool thing that people keep saying to use for Moto phones and Poof it worked now my phone works again and i did not has to sell it on craglist dead.... but now there is an issue that was not there before... 4 times a day i get a RED CROSS with no signal and no bars and no service telling me emergancy calls only so i do air plane mode and works again for a while? does any one know why it does this?
any way back to sell it to craglist lol....
Maybe have to flash a modem.
Thanks for the update, I gave the phone back to my friend but will tell him to bring it back to me to test.
Hopefully this works for that phone too.