Please help me guys.............
Before some days i Rooted my phone. ( I am on latest 2.3.5 OTA)
Then due to some reason i have to do factory reset and phone lost root access.
so, again i rooted my phone.
And today i just switch off it... and after that when started, it is stuck to dual core logo....
Cooldevil1989 said:
Please help me guys.............
Before some days i Rooted my phone. ( I am on latest 2.3.5 OTA)
Then due to some reason i have to do factory reset and phone lost root access.
so, again i rooted my phone.
And today i just switch off it... and after that when started, it is stuck to dual core logo....
Click to expand...
Click to collapse
sbf back to stock and do a factory/data reset (if it bootloops after sbf). then you should be good to go.
also it seems that that latest update is bricking lots of peoples phones!
na7q said:
sbf back to stock and do a factory/data reset (if it bootloops after sbf). then you should be good to go.
also it seems that that latest update is bricking lots of peoples phones!
Click to expand...
Click to collapse
as the OP states he is on the latest 2.3.5. update there is no sbf yet.
Cooldevil1989 said:
Please help me guys.............
Before some days i Rooted my phone. ( I am on latest 2.3.5 OTA)
Then due to some reason i have to do factory reset and phone lost root access.
so, again i rooted my phone.
And today i just switch off it... and after that when started, it is stuck to dual core logo....
Click to expand...
Click to collapse
I had a similar issue. Through a long list of things that I tried, I was able to get back in. However, WIFI does not work at all, and none of the fixes posted here have worked.
Did you have bootstrap and a backup prior? That would be helpful for you. Try cold booting through linux. If that alone doesn't work, here is what I did. I cold booted though linux to get in after using the us cellular SBF, then I was able to restore my backup. Again, this got me back into the phone, but no WIFI.
Not sure if that helps at all.
chris.carstens said:
I had a similar issue. Through a long list of things that I tried, I was able to get back in. However, WIFI does not work at all, and none of the fixes posted here have worked.
Did you have bootstrap and a backup prior? That would be helpful for you. Try cold booting through linux. If that alone doesn't work, here is what I did. I cold booted though linux to get in after using the us cellular SBF, then I was able to restore my backup. Again, this got me back into the phone, but no WIFI.
Not sure if that helps at all.
Click to expand...
Click to collapse
Thanx for your reply.....
But can u please tell me how to try cold booting through linux. & then what to do???
Sorry as I am noob to photon ...
Cooldevil1989 said:
Thanx for your reply.....
But can u please tell me how to try cold booting through linux. & then what to do???
Sorry as I am noob to photon ...
Click to expand...
Click to collapse
Sorry, I can't remember for sure. (and my wife is not letting me touch her phone, who can blame her) But I think it was vol. up and power until you get some words on the screen. Then scroll thought the options and select the correct one.
sorry, I'm a noob also, and I can't check right now.
chris.carstens said:
Sorry, I can't remember for sure. (and my wife is not letting me touch her phone, who can blame her) But I think it was vol. up and power until you get some words on the screen. Then scroll thought the options and select the correct one.
sorry, I'm a noob also, and I can't check right now.
Click to expand...
Click to collapse
ok... buddy....thanx for your reply....
I am going to copy/paste this.
This will recover from brick, when you are permanently locked on Photon after 2.3.5 OTA update.
Take USC_19 full sbf from 2.3.5 sv2 custom sbf thread, flash that, wipe data in recovery, root it, install bootstrap recovery.
After that, you can flash mof 2.3.5ish rom or my rom (locked).
Then install bootstrap recovery again, if it's not preinstalled there. And flash 254_13 modules. After that flash 2.3.5sv2 unbrick sbf with 254_13 boot, recovery and cdrom. If you have no radio service, flash 254_12 libmoto_ril.so.
Here is the thread he copied that from. http://forum.xda-developers.com/showthread.php?t=1798145
Hopefully we both can solve our problems with that.
Thanx to u peetr_ sir..... great... help... nw my photon is perfectly workng....
Sent from my MB855 using xda app-developers app
Related
Good morning everyone. I have a major technical issue with my phone after flashing to HKTW 2.3.4 and I am in dire need of assistance. I hope someone here can help me asap since I really need to use this phone.
So here is my issue. After flashing to 2.3.4 via Flash Recovery, I was greeted with an unusable touchscreen. Everything looked fine, however when I try to "touch" anything on the screen (keyboard, icons, menus, etc) I am forced to touch the opposite side of it, which means to click on an icon on the left side of the screen, i have to touch the right side of the screen. Similarly with the keyboard, to click a letter that's on the right side of the screen, I have to touch on the left side. I think the touchscreen is mirrored, probably for the Chinese characters?
But not only that, apparently, the 4 primary touch buttons (menu, home, return, search) are also reversed, thus having me to touch search in order to access menu.
I practically can't set up the phone due to this, and I didn't make a backup of /data prior to unlocking the phone (didnt know how to do so earlier). I have backups from TiBu but it's at home right now.
Is there anything I can do? Maybe change a setting via root explorer, or maybe through Flash recovery? Please someone help me.
Thanks,
Aqua
p.s. Moderators/Admins, I know I've posted this in several threads and I apologize for "spamming" but this is very urgent, so please don't delete this thread. Thank you.
Try to SBF flash 1.83 via RSDLite
Sent from my MB860 using XDA App
neer2005 said:
Try to SBF flash 1.83 via RSDLite
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Hi Neer, I will try that right now. If it fixes the issue, then something's wrong my flash to 2.3.4. I was hoping that I can resolve this without going backwards but I guess have no choice.
aquariuz23 said:
Hi Neer, I will try that right now. If it fixes the issue, then something's wrong my flash to 2.3.4. I was hoping that I can resolve this without going backwards but I guess have no choice.
Click to expand...
Click to collapse
That's the only hope you've got buddy.
Sent from rooted Atrix on 2.3.4 with unlocked bootloader using xda premium app.
ceo.mtcl said:
That's the only hope you've got buddy.
Sent from rooted Atrix on 2.3.4 with unlocked bootloader using xda premium app.
Click to expand...
Click to collapse
Crap!! now it's stuck in a boot loop. After flashing 1.8.3, it attempts to boot, and after passing the att screen, the screen goes black and the red led continuously blinks. Afterwards it just reboots again. What should I do?
the cwm flash method seems to present this bug to several people. Now that you have flashed to 1.8.3, try going into recovery and doing a factory reset. If that does not do it, i would then try flashing either 1.8.3 or 2.3.4 via fastboot, by manually flashing the system and boot partitions. if neither suggestion works, then this problem is beyond my realm of expertise and youll have to wait on someone who knows what they are talking about to chime in.
Well, I now can't proceed nowhere. Apparently, I bricked my phone flashing back to 1.8.3. Now another ordeal to tackle. Gonna try Designgear's guide to recovering from a brick. Wish me luck
aquariuz23 said:
Well, I now can't proceed nowhere. Apparently, I bricked my phone flashing back to 1.8.3. Now another ordeal to tackle. Gonna try Designgear's guide to recovering from a brick. Wish me luck
Click to expand...
Click to collapse
the same thing happened to me.. charge up your phone all the way and flash the 1.2.6 SBF. it took 2 seperate flashed for me, but it worked. and then i was able to proceed flashing 2.3.4 again
Successfully unbricked the phone via this guide: (just posting it in case some people encountered the same issue)
http://forum.xda-developers.com/showthread.php?t=966648
Now i'm in stock 1.83 froyo. Gonna do the unlock again, and proceed from there on. Not gonna do the 2.3.4 flash via CWM, will try a different method, hopefully it wont fail on me this time
what does bricking mean?
for the record a bricked device cannot be unbricked.
SuperUserMovado said:
for the record a bricked device cannot be unbricked.
Click to expand...
Click to collapse
I guess i did a soft-brick? Not to argue with you, but based on several threads here on the forum, if the atrix is stuck boot-looping with the red led flashing rapidly, then it's considered bricked, but hey what do i know. All I care is I managed to get out of the predicament and proceed with trying to flash 2.3.4.
use the fastboot flash method, very clean and works great.
Success!!
I managed to get 2.3.4 without any issues (excluding whatever bugs there might be on this release). The touchscreen works perfectly fine without the crazy reversed touch or super sensitive responses.
After unlocking the phone using the pudding guide, I went and flashed the following through fastboot:
http://forum.xda-developers.com/showthread.php?t=1139715
And it works like a charm. I am guessing either Tenfar's CWM or his flashable 2.3.4 release is buggy and did not want to work with mine. Or maybe I simply had to start from scratch (1.83 sbf) instead of continuing from my deodexed 1.83 *shrugs*. But yeah, things are looking much better now thank god.
Now, I will try to install Tenfar's CWM and this as well:
http://forum.xda-developers.com/showthread.php?t=1142674
Hopefully all will stay well
Thanks for all your help and suggestions guys/gals.
pyro254750 said:
use the fastboot flash method, very clean and works great.
Click to expand...
Click to collapse
Did so, n it works much better than through flash recovery. Thanks.
I have Bricked my phone edditing system folder permissions...
REGREATED ROOTING EVER SINCE
Any way to fix it its simply the phone keeps rebooting with a red light blinking and the M sign dual core stuck
Ive tried 2 methods but they didnt work!! :'(
Rsd method
and the abd method i didnt fully understand because im still nubbish
sbf should fix this, after flash is complete if it still bootloops your probably using a service sbf so will need to enter android recovery and manually clear data etc. to do this hold volume down while turning on device, then keep pressing it till it says android recovery, press volume up, then you have to tap the bottom right corner to show the options when the android logo appears
Hi all I am in the same boat I followed the briefmobile instructions http://briefmobile.com/download-android-2-3-4-gingerbread-for-motorola-atrix-4g
Tried the Android recovery deleting cash and installing from SD but I keep getting failed authentication (or something like that)
Can anybody help or post a topic that can lead me in the right direction
ears1991 said:
sbf should fix this, after flash is complete if it still bootloops your probably using a service sbf so will need to enter android recovery and manually clear data etc. to do this hold volume down while turning on device, then keep pressing it till it says android recovery, press volume up, then you have to tap the bottom right corner to show the options when the android logo appears
Click to expand...
Click to collapse
Ive done this and it hasnt worked 0.0
heyhey24 said:
Ive done this and it hasnt worked 0.0
Click to expand...
Click to collapse
which sbf are you using?
ears1991 said:
which sbf are you using?
Click to expand...
Click to collapse
stock US att 1.8.3 with 2.2.2 froyo installed a couple of root apps
heyhey24 said:
stock US att 1.8.3 with 2.2.2 froyo installed a couple of root apps
Click to expand...
Click to collapse
download and try: http://www.megaupload.com/?d=IJC7SGJZ or http://www.megaupload.com/?d=0AH1MQDS
Id be suprised if neither worked
do i still get ota updates?
Also im longing to try the gingerbread atrix leak so do you think you could help me with that?
yes you will still get ota updates
i wouldnt recommend you trying the gingerbread stuff without doing A LOT of reading first, id just wait for it to arrive ota personally rather than risk messing your phone up again
What I don't get is that people edit random things and break their phones. Why did you change the permissions?
Sent from my Nexus S using XDA App
Question do you use Android Recovery or RSD or Fastboot? with the 1.8.3 file
I tried it cause I got the unlock and bootloader without any issue. so i was daring.....
you speak the truth lol
yea its comming this month anyway an the moth is have over
Not to sounds lik an idiot but can you tell me how to sbf because i think im doing it badly or something using rsq or something like that
http://briefmobile.com/motorola-atrix-4g-system-boot-file-sbf-leaked
scroll down for guide
dario3040 said:
What I don't get is that people edit random things and break their phones. Why did you change the permissions?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
because i needed it for emoji but i guess i screwed up huh? lol
OmniMoAK said:
Question do you use Android Recovery or RSD or Fastboot? with the 1.8.3 file
I tried it cause I got the unlock and bootloader without any issue. so i was daring.....
Click to expand...
Click to collapse
...RSD and tried using android recovery to restore
RSD dosent recognize my phone ...
nevermind E-FAIL on my part
THANK YOU ALL YOU AMAZING AND TALENTED PEOPLE ON THE FORUMS IF ANYTHING GOES WRONG DURING THE PROCESS ILL CONTACT YOU LOVE YOU GUYS N THANKS FOR LETTING ME INTO MY NEW HACK HOME ... ANDROID AND XDA
OK new problem now I am out of battery, and I cant do anything to charge it. So the only thing I can do is in Android recovery but I cant find a update.zip file that will authenticate. Any ideas on how to get the battery charged? and where to get a update.zip that will work?
please help I know I may of hijacked this thread but it is a similar situation.
Hey guys, I hope you can help, I have a motorola atrix (At&t), and this is what happened:
My phone is rooted, and i was running Alien rom, but things went wrong when I installed Grey Blur.
Now my phone doesnt boot, and it doesnt go into recovery mode, I am not sure what to do, please help me
Thanks in Advance
droidict said:
Hey guys, I hope you can help, I have a motorola atrix (At&t), and this is what happened:
My phone is rooted, and i was running Alien rom, but things went wrong when I installed Grey Blur.
Now my phone doesnt boot, and it doesnt go into recovery mode, I am not sure what to do, please help me
Thanks in Advance
Click to expand...
Click to collapse
Why don't u flash recovery through adb, so the recovery will work and then you can install a Rom next...
You think you can walk me though it, im still a noob at this
droidict said:
You think you can walk me though it, im still a noob at this
Click to expand...
Click to collapse
You certainly can enter the boot loader ryt?
I actually own HTC incredible s so can't say much about it, nut then android OS works around the same way with bootloaders and recoveries, so hope I can get u some head start....
What exactly happens when you turn on the phone?
My ATRIX has wrote this without my consent!
Can you get into "Fastboot" mode? Wait.. are you just rooted or rooted and unlocked? If you are unlocked or even not unlocked and can get into RSD Mode, you could flash the Pudding 2.3.4 sbf. Or you could go to the "Fruit Cakes" thread, download the zip file extract the boot.img and system.img and flash them via fastboot...
The issue has been resolved...
It seemed that he could flash roms with sense 2.0 or 2.1 without any problems, but then he couldn't flash the 4ext recovery, as it did not seem to work, all it would do is give a blank screen, wherein the recovery would run but the text wasn't visible at all...
He first formatted his SD card...
Flashed 4extrecovery 2.1.0 final version. And it worked...
Next he flash VU 2.35 ROM. And power off the device after the flash from the recovery itself.
Went back into recovery again (keep in mind he hasn't started his phone, it actually ends up in boot loops) and flashed the unity v3 kernel.
Power off Tue device again and power on... Voila!!! It worked....
Some cpu's tend to be a little diff. than others. So some can bare the alterations made to their frequencies and voltage while others can't. Hope it goes well with all the IncS users....
EDIT: sorry posted this on the wrong thread... This is how another incredible s user had a problem like, so solved his one....
OK fellas. Had newest version of CM7 on the phone (phone is unlocked, rooted, etc). Keep getting random shut-offs while in stand-by. Decided to go back to official AT&T ROM.
Started flashing phone via RSD Lite. Got an error, no changes were made. Flashed again, got a different error. Stuck in boot loop. Erased cache and userdata via Fastboot, flashed AGAIN. Stuck in boot loop STILL.
Basically I can't get into the phones stock recovery, I get to the triangle screen and pressing above the search button does nothing. The phone loads up to the AT&T screen, then reboots and keeps looping at the animated "M" logo - not the M Dual Core logo. Any ideas fellas? 'cause I'm out of them. I even tried flashing a different recovery with the Atrix Fastboot Tool I found on here and got an error.
ffffffuuuuuuuuuuuuuuu
NickS_ said:
OK fellas. Had newest version of CM7 on the phone (phone is unlocked, rooted, etc). Keep getting random shut-offs while in stand-by. Decided to go back to official AT&T ROM.
Started flashing phone via RSD Lite. Got an error, no changes were made. Flashed again, got a different error. Stuck in boot loop. Erased cache and userdata via Fastboot, flashed AGAIN. Stuck in boot loop STILL.
Basically I can't get into the phones stock recovery, I get to the triangle screen and pressing above the search button does nothing. The phone loads up to the AT&T screen, then reboots and keeps looping at the animated "M" logo - not the M Dual Core logo. Any ideas fellas? 'cause I'm out of them. I even tried flashing a different recovery with the Atrix Fastboot Tool I found on here and got an error.
ffffffuuuuuuuuuuuuuuu
Click to expand...
Click to collapse
reflash pudding, install newest recovery, flash a fruit cake to go back to stock.
Alcapone263 said:
reflash pudding, install newest recovery, flash a fruit cake to go back to stock.
Click to expand...
Click to collapse
I just did this (completely unrelated to thread) and it gave me a totally fresh device. Perfect. Thanks!
My question: Can att still tell that at one point my Atrix was unlocked/rooted?
SielickiN said:
I just did this (completely unrelated to thread) and it gave me a totally fresh device. Perfect. Thanks!
My question: Can att still tell that at one point my Atrix was unlocked/rooted?
Click to expand...
Click to collapse
once you unlock your bootloader, it burns a fuse that motorola can check on to see if the device has been tampered with. that's why people say once unlocked, always unlocked.
it's possible to hide the 'unlocked' text at boot, but it's not possible to hide the burned fuse.
Alcapone263 said:
reflash pudding, install newest recovery, flash a fruit cake to go back to stock.
Click to expand...
Click to collapse
Trying to flash CWM, it's giving me an error..
Failed to process command flash:recovery error (0x180002)
Click to expand...
Click to collapse
Ruh roh
Alcapone263 said:
once you unlock your bootloader, it burns a fuse that motorola can check on to see if the device has been tampered with. that's why people say once unlocked, always unlocked.
it's possible to hide the 'unlocked' text at boot, but it's not possible to hide the burned fuse.
Click to expand...
Click to collapse
Do they actually check that? Or is just theoretically they can...?
SielickiN said:
Do they actually check that? Or is just theoretically they can...?
Click to expand...
Click to collapse
it's a theoretically they can sort of deal.
NickS_ said:
Trying to flash CWM, it's giving me an error..
Ruh roh
Click to expand...
Click to collapse
it's because you don't have an unlocked bootloader, flash pudding through RSDlite.
Alcapone263 said:
it's a theoretically they can sort of deal.
it's because you don't have an unlocked bootloader, flash pudding through RSDlite.
Click to expand...
Click to collapse
I had one, does flashing back to the AT&T stock rom re-lock it? I thought it didn't.. regardless I'm currently flashing pudding with the version of RSDLite in his thread which is slightly different than the one I was using. (red logo vs blue)
Alcapone263 said:
it's a theoretically they can sort of deal.
Click to expand...
Click to collapse
I'm sorry to reply so much and take your time, (by the way thanks for the information, really appreciate it)
I've been having (i'm assuming) hardware issues with this phone and I only got it yesterday so I want to swap it at a local ATT store tomorrow. Can I do that without worries in my current state? Will they eventually notice and bill me? Or will I be safe?
NickS_ said:
I had one, does flashing back to the AT&T stock rom re-lock it? I thought it didn't..
Click to expand...
Click to collapse
pudding has the 'fastboot oem unlock' function built into it, the stock bootloader doesn't. so when you reflashed gingerbread, you replaced the bootloader which caused the phone to believe that it's locked again (even though it isn't)
this causes your phone to have a 'locked' bootloader in every function, except that your fuse is still burned.
after flashing pudding, you should stay away from RSDlite completely and use fruitcakes for all of your stock needs.
SielickiN said:
I'm sorry to reply so much and take your time, (by the way thanks for the information, really appreciate it)
I've been having (i'm assuming) hardware issues with this phone and I only got it yesterday so I want to swap it at a local ATT store tomorrow. Can I do that without worries in my current state? Will they eventually notice and bill me? Or will I be safe?
Click to expand...
Click to collapse
i personally hard bricked my first Atrix while attempting to unlock the bootloader, AT&T replaced it without any questions. not to say that they'll do this for anyone, but just my personal experience.
as far as i know, AT&T will replace your phone as long as it's a hardware malfunction, and not anything caused by flashing custom firmware onto your device.
Alcapone263 said:
pudding has the 'fastboot oem unlock' function built into it, the stock bootloader doesn't. so when you reflashed gingerbread, you replaced the bootloader which caused the phone to believe that it's locked again (even though it isn't)
this causes your phone to have a 'locked' bootloader in every function, except that your fuse is still burned.
after flashing pudding, you should stay away from RSDlite completely and use fruitcakes for all of your stock needs.
i personally hard bricked my first Atrix while attempting to unlock the bootloader, AT&T replaced it without any questions. not to say that they'll do this for anyone, but just my personal experience.
as far as i know, AT&T will replace your phone as long as it's a hardware malfunction, and not anything caused by flashing custom firmware onto your device.
Click to expand...
Click to collapse
Thanks SO much. Really appreciate your help.
Alcapone263 said:
pudding has the 'fastboot oem unlock' function built into it, the stock bootloader doesn't. so when you reflashed gingerbread, you replaced the bootloader which caused the phone to believe that it's locked again (even though it isn't)
this causes your phone to have a 'locked' bootloader in every function, except that your fuse is still burned.
after flashing pudding, you should stay away from RSDlite completely and use fruitcakes for all of your stock needs.
i personally hard bricked my first Atrix while attempting to unlock the bootloader, AT&T replaced it without any questions. not to say that they'll do this for anyone, but just my personal experience.
as far as i know, AT&T will replace your phone as long as it's a hardware malfunction, and not anything caused by flashing custom firmware onto your device.
Click to expand...
Click to collapse
Thanks so much man. I have a replacement phone on the way due to the random shut offs considering people have been reporting it with the stock GB rom too, and it's believed to be a hardware malfunction, I just wanted it to appear more "stock" when they received it to avoid any question asking. Would really suck if I bricked it before hand haha.
I actually like the stock ROM on this phone anyway, probably won't be going back to CM7 once the new one comes in. It's rebooting now with the pudding SBF, we'll see if she still loops or not. If it still loops, I'll flash the modified CWM and the fruitcake ROM and report back. You guys are super helpful, thanks again!
you're welcome, both of you. glad i could help, when i was new i had a lot of help from the community here and i like to give back as much as possible. since i'm no programmer, all i can do is help answer questions for people and make sure they don't screw up their devices.
i hope you get your problems worked out, this is an amazing phone with awesome developers.
also, if you enjoy the stock ROM i would highly suggest for you to check out Aura, it's simply amazing for being a moto-based ROM.
Alcapone263 said:
you're welcome, both of you. glad i could help, when i was new i had a lot of help from the community here and i like to give back as much as possible. since i'm no programmer, all i can do is help answer questions for people and make sure they don't screw up their devices.
i hope you get your problems worked out, this is an amazing phone with awesome developers.
also, if you enjoy the stock ROM i would highly suggest for you to check out Aura, it's simply amazing for being a moto-based ROM.
Click to expand...
Click to collapse
Will do, thanks!
Oh snap! Phone just rebooted. Flashed the modified CWM via fastboot, cleared the userdata, cache & dalvik cache once more and it booted up! No need for fruitcake I guess, but I'm off to check out those Aura roms haha.
I hard bricked my first one it was also rooted and unlocked and att sent me a new on on,the warrenty for free
Sent from my MB860 using xda premium
NickS_ said:
Will do, thanks!
Oh snap! Phone just rebooted. Flashed the modified CWM via fastboot, cleared the userdata, cache & dalvik cache once more and it booted up! No need for fruitcake I guess, but I'm off to check out those Aura roms haha.
Click to expand...
Click to collapse
well i'm glad you got your problem sorted out! before you flash any ROMs though, be sure to do a complete backup of your phone as it is right now. it'll help you in case of PDS corruption later on.
What exactly is PDS corruption? And what do you recommend I do a backup with? I've actually never done a backup for any of my many android devices.
EDIT: guessing nandroid, lol google ftw
NickS_ said:
What exactly is PDS corruption? And what do you recommend I do a backup with? I've actually never done a backup for any of my many android devices.
EDIT: guessing nandroid, lol google ftw
Click to expand...
Click to collapse
i'm sure you have CWM installed by now, use Romracer's and do a full backup of your device. just keep it on your phone, with a copy of it backed up on your computer.
the PDS partition is a place on our phone that holds a lot of information about our device, if it gets corrupted you can experience a lot of touchscreen issues. just better to be safe. i flash my phone every 2-3 days and haven't experienced anything, but other people have, so like i already said; better safe than sorry
i just got my razr maxx yesterday,
and i was on ABYSM ROM, when i restarted my phone it is never starting and going to endless boot looping, and i don't have saftstrap installed i only have bootstrap!
help please!
You're going to have to fastboot with RSD Lite.
Follow this video:
http://www.youtube.com/watch?v=WBySMO8n1r4
aktrazer said:
You're going to have to fastboot with RSD Lite.
Follow this video:
http://www.youtube.com/watch?v=WBySMO8n1r4
Click to expand...
Click to collapse
Thanks a lot
i will try that right now
PM me if you have any issues. I've fastbooted 3 or 4 times now.
just the VRZ_XT912_6.5.1-73_DHD-11_TA-3_1FF_02.xml is over a GB size, and it is taking forever to get downloaded, just waiting for it, otherwise i have everything else ready...
Thanks in advance buddy
do u think i should install safestrap? i mean after booting? is it safer?
I've used CWM and Safestrap, both work well. Safestrap gives you the advantage of basically being able to dual boot your system while leaving your primary ROM untouched, good for testing and messing around. I don't personally care for CWM, some people like it, just a matter of preference.
Yeah, the file is huge but once you have the fastboot files you don't have to worry about bricking your phone as long as you can get into AP Fastboot mode.
Quick question...did you try to wipe data/cache? When I had my DX ran into this same issue and needed to do a simple wipe. Just a thought.
Sent From My Droid RAZR MAXX
I have a simmilar problem as described above. But my problem is that when I try to flash the ROM via RSD, it flashes just one file, and then I get an error stating that I am low on battery...
Is there anyway to charge it whitouth buying a factory cable?
The method of velocity doesn't work either for me.
I feel lost whitouth my motorola
Fixed the problem with a factory cable. If someone in Switzerland needs help, PM me!