Related
Hello everyone. I have a problem with my Motorola Atrix and I am hoping someone might be able to help me.
I got it as a late Christmas present so its still practically new. I tried doing an OTA update from 2.2 to 2.3 and the battery died whilst the update was taking place. I replaced that battery with my spare battery which was fully charged, but now it won't load. When trying to load on startup, it gets stuck at the dual core logo and gives an error message if I press the volume button. The message says something like "Starting RSD protocol support". I am gutted...
I have been searching feverishly through the forums for some help, and I have come across some information with regards to the types of bricks, ie hard/soft, but I am not sure which it is in my case. There is alot of information available, but I can't find any with my problem. I am not opposed to trying to fix the problem myself as I have some experience in messing around with software, though that was back in the days of p2k-tools some 10 years back, but I would appreciate a nudge in the right direction and some advice maybe since I am almost clueless about Android software. Any help would be greatly appreciated.
Additional info:
The phone is completely factory default software wise, so is not rooted or running any form of custom firmware. UK carrier - Tmobile.
I think you have two options. If it's still under a warranty, take it back to the store and ask them to repair it. Or if you don't care about a warranty, you can follow this post http://forum.xda-developers.com/showthread.php?t=1136261 to unlock your phone and install a custom ROM. But if you decide to unlock you phone, before trying anything, read the post completely. I'm saying again, read the post completely before doing anything.
I myself unlock the Atrix and using a custom ROM and I have a pretty good battery life compared with a stock ROM.
Thank you for your response. I will look into the warranty idea and see how that goes. I hope there is not a long wait period which is my biggest reservation about this option since I need my phone.
In so far as installing the custom ROM and unlocking it, is there maybe another way that would allow me to continue to use stock firmware and OTA updates? I have been reading through some threads where they say once there is a custom firmware, running an OTA update could brick the phone. I also really just prefer to keep the phone original. If this can't be done, then I will have to give the warranty thing a serious go before I consider the alternative.
shottah said:
Thank you for your response. I will look into the warranty idea and see how that goes. I hope there is not a long wait period which is my biggest reservation about this option since I need my phone.
In so far as installing the custom ROM and unlocking it, is there maybe another way that would allow me to continue to use stock firmware and OTA updates? I have been reading through some threads where they say once there is a custom firmware, running an OTA update could brick the phone. I also really just prefer to keep the phone original. If this can't be done, then I will have to give the warranty thing a serious go before I consider the alternative.
Click to expand...
Click to collapse
Go here > http://www.motorola.com/Support/US-EN/Android_Products/ATRIX-4G_Software_Update_Page. Another alternative is to flash 2.3.4 stock via RSDLite, but if the update went through on your phone you could brick. Hopefully one of these will work for you! Other option is to unlock the bootloader.
If you have a full battery why not download the T-Mobile software and write it back to the phone via rsd.
Sent from my MB860 using Tapatalk
CaelanT said:
Another alternative is to flash 2.3.4 stock via RSDLite, but if the update went through on your phone you could brick. Hopefully one of these will work for you! Other option is to unlock the bootloader.
Click to expand...
Click to collapse
Thanks for the suggestion. How can I tell if the update went through? Can I access this information in the phone's current state?
lonegunman said:
If you have a full battery why not download the T-Mobile software and write it back to the phone via rsd.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
By now the battery is just short of full, but it should be enough to get through the flash. Where would I get the T-mobile software? I have checked their site and the latest android update they have is 2.1 on the site. I have also looked at the Motorola website, but their means of update is via an update program called Motorola Software Update.
Sorry if I appear a bit dense, its just from what I'm seeing is that I may only have one chance to do this and get it right, else its bye bye Atrix. I am still waiting on a response from Motorola with regards to my query about the warranty. If I can get it sorted myself, I will definitely prefer that as opposed to having to wait on them to diagnose etc.
Have a look for the ATRIX super firmware thread on here and see if the T-Mobile software is in it, it may be the old software but it's worth a try as you can send the phone in to be fixed or just take it to a T-Mobile store and let them deal with it for you.
Sent from my MZ604 using xda premium
CaelanT said:
Another alternative is to flash 2.3.4 stock via RSDLite, but if the update went through on your phone you could brick. Hopefully one of these will work for you! Other option is to unlock the bootloader.
Click to expand...
Click to collapse
If I implemented the automated update via the link you provided, could that circumvent the potential bricking you described, provided the program can access the phone? By the way, the link you gave was software for an AT&T mobile, while mine is T-Mobile UK. Will this make a difference?
shottah said:
If I implemented the automated update via the link you provided, could that circumvent the potential bricking you described, provided the program can access the phone? By the way, the link you gave was software for an AT&T mobile, while mine is T-Mobile UK. Will this make a difference?
Click to expand...
Click to collapse
Ah, you're on an international Atrix? AT&T update won't work for you then.
Sorry, I missed that at bottom of the OP.
If you get stuck and are in london pm me and I will see if I can help.
Sent from my MB860 using xda premium
CaelanT said:
Ah, you're on an international Atrix? AT&T update won't work for you then.
Sorry, I missed that at bottom of the OP.
Click to expand...
Click to collapse
No problem, I appreciate whatever help I can get.
lonegunman said:
If you get stuck and are in london pm me and I will see if I can help.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Thanks for the offer pal. Wish I was in the London area to get the help but, I'm in Stoke.
Ok, i have no idea if this will work but hay the phone is knacked so why not give it a go, it's under warranty so you can send it back if it don't work go http://forum.xda-developers.com/showthread.php?t=1125944 find the orange full and t-mobile service files, download them and write them to your phone via rsd, it's kinda hard to say what one first, its a shame that the t-mobile one is not a full one as that would be perfect, the battery should still charge so leave it on over night, also if can try and make a motorola service cable, that will put power to your so no need to worry about a battery, have a look on here as to how to make it.........ok forget all that if you check out post 276 on the link above it has download for the GB rom t-mobile uk which is what you need to wirte via rsd.
Even if you don't pay you're carrier for warranty Motorola gives you a year warranty on the phone and that's the sane with almost all carriers I sent my unlocked atrix in for screen issues and they still fixed it and same with my hd2 and ipod touch
Any update on this?
Sent from my MB860 using Tapatalk
lonegunman said:
Any update on this?
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Sorry pal, been busy with classes so no time to update the thread. Basically, I tried to update via Motorola software, but it seems it cant access the phone to begin the update process. I tried to do download the OEM ROM of 2.3.4 from the ATRIX superthread, as this seems the safest option to me, bit it seems its on a host that no longer allows downloads. I tried to request a mirror, but I don't seem to have the authority to post in that thread. If you or anyone can make the request for it to be reuploaded to another mirror, I would be most great full.
Post 276 of Atrix Formwares Superthread
ROM:
Original Gingerbread SBF for ATRIX MB860 T-Mobile UK
Android 2.3.4 ---- Blur_Version.45.31.2.MB860.T-Mobile.en.GB
filename:
1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31.2-release-keys-signed-T-Mobile-GB.sbf.gz
Did you try this?
http://forum.xda-developers.com/showpost.php?p=19908591&postcount=276
shottah said:
Sorry pal, been busy with classes so no time to update the thread. Basically, I tried to update via Motorola software, but it seems it cant access the phone to begin the update process. I tried to do download the OEM ROM of 2.3.4 from the ATRIX superthread, as this seems the safest option to me, bit it seems its on a host that no longer allows downloads. I tried to request a mirror, but I don't seem to have the authority to post in that thread. If you or anyone can make the request for it to be reuploaded to another mirror, I would be most great full.
Post 276 of Atrix Formwares Superthread
ROM:
Original Gingerbread SBF for ATRIX MB860 T-Mobile UK
Android 2.3.4 ---- Blur_Version.45.31.2.MB860.T-Mobile.en.GB
filename:
1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31.2-release-keys-signed-T-Mobile-GB.sbf.gz
Click to expand...
Click to collapse
When you say that the updated doesn't start because the Motorola software can't access the phone, is your phone recognized when you plug it into your computer?
dratsablive said:
When you say that the updated doesn't start because the Motorola software can't access the phone, is your phone recognized when you plug it into your computer?
Click to expand...
Click to collapse
The laptop recognizes the phone since I can hear USB noises when plugged and unplugged. When I try to run the software, it tries to connect and then I get the message:
"Motorola Software Update is unable to identify your device at this time. Please try again."
zigbee_chitti said:
Did you try this?
Click to expand...
Click to collapse
Yes I did try the link, but sharing is disabled on that host so I cant download it. That is exactly what I need from what I understand, but I don't have enough access to request a mirror, even though I have more than 10 posts for some reason.
Ok, well it seem over the whole megaupload thing any of the file sharing sites are playing it safe, you need to find someone who has the t-mobile file already and can send it to you, i have the orange one but not sure if it will brick your phone or not.
lonegunman said:
Ok, well it seem over the whole megaupload thing any of the file sharing sites are playing it safe, you need to find someone who has the t-mobile file already and can send it to you, i have the orange one but not sure if it will brick your phone or not.
Click to expand...
Click to collapse
The OP of that file would have access to his files on the host, its only 3rd parties who can't download his files from uploaded to his account. If he/some one else who has it can upload it to another site, it would be fine. He should still have access to his files on his account with the host though, so if anyone is feeling kind to make the request on my behalf, I would appreciate it very much since I am being prevented from posting in that section myself. Thnaks.
Before everyone feels obligated to point this out... yes, I know this will prevent me from unlocking the bootloader. I plan to stick with stock ROM's, so that should not be a problem for me.
I've downloaded the OTA, and made a copy on me SD card.
When I try to run the update normally, it fails without any error message I can see.
When I rename the OTA file to update.zip and try to update from sdcard through recovery, I get an error message referring to build.prop. As far as I can remember, I have never done anything with build.prop on this device. In any event, I'm not sure what to do to fix this.
I would like to get the update installed. Any ideas?
Be glad, that it fails. There is something that do not match and if it would go through, your phone would be dead.
Look in the zip /meta-inf/com/android/metadata, open it and check what pre-build do you need. You must have this one in the phone without root or other changes.
peetr_ said:
You must have this one in the phone without root
Click to expand...
Click to collapse
I doubt that's true. My wife's photon was rooted and did the OTA just fine.
Ok. But after some readings here I wouldn't risk that.
friends, brothers, fellow technologically advanced people lend me your ears
yea, I "figured" it out. had the same problem, but now "at last" i'm on 2.3.5
you're going to have to flash (back to stock; unroot) as done in the qbking video here
http://www.youtube.com/watch?v=J94VcWk-CJc
but when you're choosing which sbf file to flash, dl, - pick '154'
i tried the 198_6 but that didn't work for me.
once you've flashed '154,' you'll have to do two updates before you get to the 2.3.5 one
.....note: after the first one, i lost wifi and 3g, but a quick reboot brought it back.
.............note 2: after you've flashed 154, your photono will take a while to find service, because it'll be deactivated on the phone,
but then it just gives you an option to 'activate' and you're good.
when i was rooted i got rid of some of the bloat sprint stuff; i think that's the 'root' of the problem.
alexthen said:
you're going to have to flash (back to stock; unroot)
Click to expand...
Click to collapse
Not really.
My device has never had anything but stock. It's rooted, but my wife's was also rooted and had no trouble.
I just copied her build.prop to my device and the update went without a hitch. I am fairly certain I never modified my build.prop, but I suppose it's possible. I had to use her 2.3.5 build.prop, too, since this happened after she upgraded.
I never did figure out what the problem was, so the issue that is the thread topic of figuring out what was keeping the update from succeeding is not actually solved. However, a potential solution to the failed upgrade is to copy a different build.prop.
Ok I see that there are a couple of similar threads to this and I apologize in advance but I'm not sure exactly how to correctly interpret some of the answers on those threads...so I'm gonna start my own and see who can help lol. Once again I'm sorry if this new thread is considered obsolete by some or all.
I have a Motorola droid razr. Not the maxx just the standard razr. When I got my phone I started looking into rooting it after seeing one of my friends with a rooted thunderbolt. I successfully rooted my razr after doing a lot of research. I installed Titanium (not pro) and undelete. I'm fairly certain that I made a backup of everything on my phone shortly after installing Titanium Backup. Well through the course of tinkering around with my phone a bit I deleted certain files here and there that I considered useless or annoying to me that they were on my phone in the first place. Well when the upgrade to jellybean came out I tried to do a software update. It finishes, reboots my phone, then says the update was unsuccessful.
After some research I have realized that I probably deleted something that was important (lol yeah I'm an idiot) and so it wont let me update the software because of that. I realize that I could use titanium to restore those files but I have NO idea what files I deleted that were important. And I'm not all that comfortable with TB to just mess with it freely. TB has been something that I have used very little because I know I could probably cause some serious damage to my phone with it haha. I haven't done a factory reset because I know already that it wouldn't bring those files back.
If anyone can help me I would really appreciate it. I'm not a very technical person so I probably shouldn't have rooted in the first place but I tried my hardest to do the research first. Thanks in advance for the help everyone
vetchemh3 said:
Ok I see that there are a couple of similar threads to this and I apologize in advance but I'm not sure exactly how to correctly interpret some of the answers on those threads...so I'm gonna start my own and see who can help lol. Once again I'm sorry if this new thread is considered obsolete by some or all.
I have a Motorola droid razr. Not the maxx just the standard razr. When I got my phone I started looking into rooting it after seeing one of my friends with a rooted thunderbolt. I successfully rooted my razr after doing a lot of research. I installed Titanium (not pro) and undelete. I'm fairly certain that I made a backup of everything on my phone shortly after installing Titanium Backup. Well through the course of tinkering around with my phone a bit I deleted certain files here and there that I considered useless or annoying to me that they were on my phone in the first place. Well when the upgrade to jellybean came out I tried to do a software update. It finishes, reboots my phone, then says the update was unsuccessful.
After some research I have realized that I probably deleted something that was important (lol yeah I'm an idiot) and so it wont let me update the software because of that. I realize that I could use titanium to restore those files but I have NO idea what files I deleted that were important. And I'm not all that comfortable with TB to just mess with it freely. TB has been something that I have used very little because I know I could probably cause some serious damage to my phone with it haha. I haven't done a factory reset because I know already that it wouldn't bring those files back.
If anyone can help me I would really appreciate it. I'm not a very technical person so I probably shouldn't have rooted in the first place but I tried my hardest to do the research first. Thanks in advance for the help everyone
Click to expand...
Click to collapse
So does anyone have any suggestions??
im not sure about this particular phone but search for the SBF file for your phone model and how to use RSDLite. this is how to restore Motorola phones.
Sent from my HTC Glacier using xda premium
It's never a good idea to do an OTA update over a rooted phone.
You should just download a rooted stock ROM from the dev forum (a 4.1 ROM) and flash it via your recovery (flash the zip file) or another custom ROM, they have some good ones!
OR I would just flash stock THEN do the OTA update, because whatever rooting method you used (I don't have that phone so I'm not sure) probably replaced your kernel with an insecure one or your system.img so you're failing the OTA update.
orangekid said:
It's never a good idea to do an OTA update over a rooted phone.
You should just download a rooted stock ROM from the dev forum (a 4.1 ROM) and flash it via your recovery (flash the zip file) or another custom ROM, they have some good ones!
OR I would just flash stock THEN do the OTA update, because whatever rooting method you used (I don't have that phone so I'm not sure) probably replaced your kernel with an insecure one or your system.img so you're failing the OTA update.
Click to expand...
Click to collapse
this is a good point. i would only do the SBF if you can't get into custom recovery.
Sent from my HTC Glacier using xda premium
OP I moved you, here into your device forum Q&A for more visibility from actual users for your device. Thank you.
just try to flash a stock ROM using RSD, and then take the OTA update.
Sent from Motorola Razr XT910 With beatsaudio™ on ICS 4.0.4
gregeorgeraldo said:
just try to flash a stock ROM using RSD, and then take the OTA update.
Sent from Motorola Razr XT910 With beatsaudio™ on ICS 4.0.4
Click to expand...
Click to collapse
Ok I'm not gonna lie that sounds like a different language to me haha. I know I probably shouldn't have done all this without really knowing exactly what i was doing but I'm sure im not the first lol. What exactly is RSD and when I flash the razr stock ROM will it erase anything I already have save on my phone? Sorry I'm not the most intelligent when it comes to stuff like this haha
gregeorgeraldo said:
just try to flash a stock ROM using RSD, and then take the OTA update.
Sent from Motorola Razr XT910 With beatsaudio™ on ICS 4.0.4
Click to expand...
Click to collapse
Is this a good source and video that might explain this to me a little better? I havent posted 10 times so i cant use the link but its a video on youtube called How to use fastboot files to return Droid Razr back to Android 2.3.5! It's the first vid that comes up. has about 9,300 views and was posted 7 months ago. I think my RAZR was on ice cream sandwich (not gingerbread) but it should be the same i guess? Thanks in advance everyone
The reason I suggest just flashing a custom ROM thru your recovery is once you RSD stock then do the OTA you're just going to want to root again and maybe flash a better custom ROM.
Just flash a CM10 ROM from the dev forum and see how you like it, it's jellybean with tons more options that the stock ROM.
orangekid said:
The reason I suggest just flashing a custom ROM thru your recovery is once you RSD stock then do the OTA you're just going to want to root again and maybe flash a better custom ROM.
Just flash a CM10 ROM from the dev forum and see how you like it, it's jellybean with tons more options that the stock ROM.
Click to expand...
Click to collapse
The main issue i'm having is that after i rooted my phone flashing custom roms was pretty much the only aspect i didnt get into, so i'm not comfortable in the least with doing it. So just flashing a new rom might be a little strange for me. If i flash the stock rom will i lose everything i have? Like all my apps and pictures and info? And will it unroot my phone?? And if that video i posted above will work should i just try it that way?
I'm sorry to keep posting but I'm just trying to get some specific answers and I feel like if my thread falls too far down it will be forgotten lol. But that video title that I posted...does anyone know if that could be a viable solution? And if it isn't could someone explain. To me how to flash the stock rom so i can upgrade to ics. I don't think the razr has jellybean yet if I'm not mistaken
It sounds like you might be missing some of the stock apps. I had a similar problem while following the same upgrade path as you. I have a Verizon XT912 (standard RAZR) I'm lookin for a link to send you that helped with the issue...but basically there are several apps that would seem non-essential like Slacker radio or NFL Mobile that seem to have caused people trouble. If your update is failing at 30% or somewhere in the middle, this might be the problem. If this sounds like it could be it, Ill try and find the post that helped me find what I was missing.
watch your phone during the update, make sure its not actually cancelling and booting normally because of this error.
Do you know what version you were on before things happened? GB or ICS? You always use this utility just to start over and get back to stock. You could do like people are saying and get the files but this is easier. There is a version for either GB or ICS. Just need to get into AP Fast Boot mode and follow the directions. Also assume this is the Cdma phone? Here is something similar.
I would just start all over and flash.Make sure if you can that your phone is charged before starting.
blueis300 said:
Do you know what version you were on before things happened? GB or ICS? You always use this utility just to start over and get back to stock. You could do like people are saying and get the files but this is easier. There is a version for either GB or ICS. Just need to get into AP Fast Boot mode and follow the directions. Also assume this is the Cdma phone? Here is something similar.
I would just start all over and flash.Make sure if you can that your phone is charged before starting.
Click to expand...
Click to collapse
I'm on gingerbread 2.3.6. So i can just go to the bootloader menu and use AP fast boot to do what? I'm a little confused lol sorry
So does anyone have any explanation? The only reason i'm so desperate is because i'm planning on potentially selling my razr for the note 2 and i cant do that if its unable to perform this update/missing apps/etc.. lol. please help
Hello, I just got a Samsung Galaxy S2 from a friend (Stock firmware GB 2.3.3)
For some reason I am not able to establish a connection between the phone and the PC.
I tried to install and reinstall Kies and/or the drivers multiple times (and everyone of the other suggestions i found with google) but with no success. The phone recognizes that it's been charged when the cable is plugged in and sometimes the phone even indicates that it's establishing a connection to kies (but this appears randomly, not always). On the PC there's no sign of any connection to the phone, neither Kies connects to it nor the phone is shown as any kind of device in the device-manager or in explorer ("adb devices" and Odin also don't recognize the phone).
Since my fathers S2 (2.3.6 Stock Firmware) connects fine with the same drivers and cable i finally gave up searching for any any other possible reason than a damaged connector on the phone.
So i tried to search for ways to root the phone, put CWM on it and a custom ROM without any PC connection.
I encountered some things like signed custom kernels that should grant you root access, an exploitation, ...
The exploitation didn't work out for my phone, and the kernels I've found are for Jellybean or ICS, so not suitable for my Gingerbread-Firmware,
I've found some older threads on various websites that promised such kernels for Gingerbread, but there were either dead links or nothing suitable for my phone.
So now I'd like to ask the community if anyone knows any signed kernel to gain root access for my phone, or any other way to accomplish my task of upgrading to a custom firmware, or if there's no possible way to do this and I should stop wasting m time on this...
(btw, for some reason the update of the firmware via WiFi doesn't work either, so I would be glad if anyone just knows a way to upgrade to a newer stock-firmware)
My phone:
model: GT-I9100
Android: 2.3.3
Baseband: I9100NEKD5
Kernel: 2.6.35.7-I9100XWKE1-CL181974
Buildnr.: GINGERBREAD.XWKE1
thank you all in advance
Can you download and install the latest version of Odin and check if it recognises that your phone is connected?
Let me know
Sent from my GT-I9100 using Tapatalk 2
You can try ExynosAbuse ( http://forum.xda-developers.com/showthread.php?t=2050297) for rooting; not sure if it works for gingerbread though.
Once you're rooted you should be able to flash cwm with MobileOdinPro (costs 5 bucks; https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro)
Sent from my GT-I9100 using xda app-developers app
MarkyG82 said:
Disi01
Try these:
Boot to recovery and factory reset (backup any pics etc if required)
Set debugging in usb access
Try other usb ports on the pc.
I wanted the same thing untill it took me 2 weeks to decide I wanted to flash in odin. Swapping to a different port gave me access.
Good luck.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
This is what I tried too and for me it didn't work. I got the same problem as TO. I'm going to try some more stuff and if it would work i'll let you know and will follow this.
ps. I even have switched the board inside with the micro usb connector. Didn't work. I am on 4.0.4.
I already tried if Odin recognizes my phone -> no success...
I also tried ExynosAbuse before, it tells me when I start the app made by chainfire, that my device is unable to be rooted via this method.
And I've already tried to connect through every single port on every single computer that's available to me, still no success...
The only chance a can see right now might be to find a signed kernel that gives me root-access via the "install update from SD card" function, I've already found a few, but none of them was suitable for my device...
The problem is that this firmware apparently is that "old", that most of the results when searching for this topic are JB or ICS-related.
disi01 said:
I already tried if Odin recognizes my phone -> no success...
I also tried ExynosAbuse before, it tells me when I start the app made by chainfire, that my device is unable to be rooted via this method.
And I've already tried to connect through every single port on every single computer that's available to me, still no success...
The only chance a can see right now might be to find a signed kernel that gives me root-access via the "install update from SD card" function, I've already found a few, but none of them was suitable for my device...
The problem is that this firmware apparently is that "old", that most of the results when searching for this topic are JB or ICS-related.
Click to expand...
Click to collapse
You really gotta get your device rooted and flashed (mobile odin pro might is a good choice)
Don't you have an External SD card? if not, I'm sure you know someone who does.
Once you get it, you can get your device rooted & flash whatever you want via recovery.
And remember, you can always say to your dad "hey old man, how about this: I give you my phone, and you give me yours".
gastonw said:
You really gotta get your device rooted and flashed (mobile odin pro might is a good choice)
Don't you have an External SD card? if not, I'm sure you know someone who does.
Once you get it, you can get your device rooted & flash whatever you want via recovery.
And remember, you can always say to your dad "hey old man, how about this: I give you my phone, and you give me yours".
Click to expand...
Click to collapse
Yes, I do have an external SD card, but as far as I know, to flash your phone via MobileOdin it needs root access, and I still haven't figured out how to grant my applications root access on this device without any PC connection... I haven't found any useable kernel/update yet that helps me with my problem and can be installed without the phone being rooted already... If you know one, I would be glad if you could tell me
I already tried to negotiate with my dad but he doesnt seem very cooperative. He didn't like the fact that my phone has an older firmware than his and that I haven't found a way to update it... (Somehow the firmware-update via WiFi doesn't work too, it tells me everytime that the phone failed to connect to the server)
disi01 said:
Yes, I do have an external SD card, but as far as I know, to flash your phone via MobileOdin it needs root access, and I still haven't figured out how to grant my applications root access on this device without any PC connection... I haven't found any useable kernel/update yet that helps me with my problem and can be installed without the phone being rooted already... If you know one, I would be glad if you could tell me
I already tried to negotiate with my dad but he doesnt seem very cooperative. He didn't like the fact that my phone has an older firmware than his and that I haven't found a way to update it... (Somehow the firmware-update via WiFi doesn't work too, it tells me everytime that the phone failed to connect to the server)
Click to expand...
Click to collapse
lol, okay, stop and read for a min.
You can root your device with that SD card.
Read this guy's method.
After you root it, you're up for some flashing.
But take it one step at the time.
If we get you to flash a nice looking ROM, your dad's gonna say something like this "hey, that's a nice looking OS you got there, how about I give you mine + 100 bucks"
About the OTA (over the air) update, I recall reading something about it. I'ma see if I can find a thread about that.
Also, you might like to try removing kies from your system (every last trace of it) and reinstalling the latest version. Then try connecting the phone again.
Sent from my GT-I9100 using Tapatalk 2
gastonw said:
lol, okay, stop and read for a min.
You can root your device with that SD card.
Read this guy's method.
After you root it, you're up for some flashing.
But take it one step at the time.
If we get you to flash a nice looking ROM, your dad's gonna say something like this "hey, that's a nice looking OS you got there, how about I give you mine + 100 bucks"
About the OTA (over the air) update, I recall reading something about it. I'ma see if I can find a thread about that.
Click to expand...
Click to collapse
Dude. That method (Rachmat3's) only works for ICS. He's on GB.
ctomgee said:
Dude. That method (Rachmat3's) only works for ICS. He's on GB.
Click to expand...
Click to collapse
Quantity rather than quality lol.
Yes, this method doesn't work on GB, I've tried this before with a huge load of different CWM-bootloaders from a lot of different sources and it always throws an "signature verification failed" or "failed to verify whole-file signature" error or both...
Isn't there any similar way to do this on GB? I've been an iPhone user for a few years now and didn't check the android hacking/modding community very often and because of this I'm not aware of any rooting methods that may have been available back then...
All you need to do is use the exynos exploit to gain root. You can do this via a simple apk.
Once you have root install Mobile Odin and flash Siyah kernel (.tar) to get custom kernel, cwm recovery etc.
Then you're off! Just reboot into recovery and wipe/flash away :good:
ctomgee said:
Dude. That method (Rachmat3's) only works for ICS. He's on GB.
Click to expand...
Click to collapse
ooops.
disi01 said:
I also tried ExynosAbuse before, it tells me when I start the app made by chainfire, that my device is unable to be rooted via this method.
Click to expand...
Click to collapse
Unfortunately the ExynosAbuse-method isn't an option for me neither...
EDIT:
found this in the changelog of ExynosAbuse (added in v1.20):
- Gingerbread-related fixes - note that not all Gingerbread firmwares of affected devices are vulnerable (for example, I know several SGS2 GB firmwares are not exploitable)
I think that unfortunately I have one of those firmwares...
What about changing the usb board.
If nothing else works this will be my last option in the end i guess, but I'd rather prefer a software-based solution because I assume it might be a bit cheaper
Looks like your only option to me.
try this
open the phone dialer
enter *#7284#
then make sure your phone is set to usb mode
you can try switching it to modem or the other option then reboot phone
then enter code again and pick usb option
you might need to reboot again
I had a problem in the past where USB would not connect and when I did the above it worked.
droiduzr2 said:
try this
open the phone dialer
enter *#7284#
then make sure your phone is set to usb mode
you can try switching it to modem or the other option then reboot phone
then enter code again and pick usb option
you might need to reboot again
I had a problem in the past where USB would not connect and when I did the above it worked.
Click to expand...
Click to collapse
You, Sir, are my personal hero from now on I couldn't really try by now if this solved the problem with the USB-connection, but somehow it solved the problem with the firmware-update per WiFi, and now I was able to update to the newest ICS-firmware available to my device. And hopefully I will be able to root it now with one of the signed kernels available for ICS-firmware
Hi, as said in the title, my Motorola XT910 is stuck on the logo, and will not boot, even after charging, and letting it do its thing overnight. I tried everything I could, including trying to wipe the cache via recovery mode, and I do not have access to it via adb in any ways. The only communication I can establish between it and my computer is via fastboot. The RSD Software doesn't recognize it either, though it appears on the computer as "ADB Device". Biggest problem is, I have seen threads from years ago on other forums, all over the internet with people having this issue, some had it fixed via a factory reset, some had to send it back. Obviously, I cannot send it back to motorola, as for the factory reset, I really cannot do it, since my whole objective of making this phone function again was to recover old very important videos and photos on it, which is rendered impossible due to android not starting.
I really hope someone has a solution (does anyone still even come by these threads ?).
Thanks in Advance,
Dylan.
LaMontreBelge said:
Hi, as said in the title, my Motorola XT910 is stuck on the logo, and will not boot, even after charging, and letting it do its thing overnight. I tried everything I could, including trying to wipe the cache via recovery mode, and I do not have access to it via adb in any ways. The only communication I can establish between it and my computer is via fastboot. The RSD Software doesn't recognize it either, though it appears on the computer as "ADB Device". Biggest problem is, I have seen threads from years ago on other forums, all over the internet with people having this issue, some had it fixed via a factory reset, some had to send it back. Obviously, I cannot send it back to motorola, as for the factory reset, I really cannot do it, since my whole objective of making this phone function again was to recover old very important videos and photos on it, which is rendered impossible due to android not starting.
I really hope someone has a solution (does anyone still even come by these threads ?).
Thanks in Advance,
Dylan.
Click to expand...
Click to collapse
RSD lite doesn't work with most Windows 10 machines, use Windows 7. http://forum.xda-developers.com/showpost.php?p=59348530&postcount=6
If you want to save data you need to modify the .XML file if using RSD Lite
Lots of issues can cause a boot loop, bad battery, bad app, bad hardware... even a bad charger or USB cable.
Try [Utility] - = MotoFlashPro =
Hi, thanks for replying, I took note of the software not functionning with windows 10, do you think it will work if I run 7 in VmWare and pass the phone through or do I absolutely have to use a physical 7 machine ?
Also, I really cannot make a factory cable like the one pictured in the post you linked, since none of my cables permit such a modification (the fifth pin does not have a spot to solder onto).
About the bootloop, well I'm not sure it really is one, since it doesn't loop at all, it just stays on the starting screen.
It shouldn't be a battery problem since even when giving power straight to the battery terminals, it does not boot, though the fastboot thing says "battery ok".
It shouldn't be a bad app either since last time I used the phone, like 3 years ago before I broke the screen which I replaced recently, it worked perfectly fine, and obviously I could not install an app in the meantime. The battery just ran down to 0 volts but I managed to make it work again. And what do you mean by bad charger ? Something like not powerful enough perhaps ?
LaMontreBelge said:
Hi, thanks for replying, I took note of the software not functionning with windows 10, do you think it will work if I run 7 in VmWare and pass the phone through or do I absolutely have to use a physical 7 machine ?
Also, I really cannot make a factory cable like the one pictured in the post you linked, since none of my cables permit such a modification (the fifth pin does not have a spot to solder onto).
About the bootloop, well I'm not sure it really is one, since it doesn't loop at all, it just stays on the starting screen.
It shouldn't be a battery problem since even when giving power straight to the battery terminals, it does not boot, though the fastboot thing says "battery ok".
It shouldn't be a bad app either since last time I used the phone, like 3 years ago before I broke the screen which I replaced recently, it worked perfectly fine, and obviously I could not install an app in the meantime. The battery just ran down to 0 volts but I managed to make it work again. And what do you mean by bad charger ? Something like not powerful enough perhaps ?
Click to expand...
Click to collapse
Hi again, quick update, I plugged it into my Windows Xp machine as I do not have a windows 7 computer, and it appeared. Also, could you please tell me what to change in the xml file in order to keep the data ?
Please, are you there ? I really need this help with the XML file, what do I need to edit ? I got the phone to be recognized in windows, even in rsd lite, i just need to know what to edit in the file
LaMontreBelge said:
Please, are you there ? I really need this help with the XML file, what do I need to edit ? I got the phone to be recognized in windows, even in rsd lite, i just need to know what to edit in the file
Click to expand...
Click to collapse
I've never had to use RSD Lite, and you might be better off waiting for him to respond incase I'm wrong (haven't touched this phone in a while). But I've done some digging and heard you can remove the line near the end of that XML file that goes something like
Code:
<step operation="erase" partition="userdata"/>
and it should skip the data wipe. I don't think it's necessary to remove the ones for cache and stuff. It might be a bad idea.
Smu1zel said:
I've never had to use RSD Lite, and you might be better off waiting for him to respond incase I'm wrong (haven't touched this phone in a while). But I've done some digging and heard you can remove the line near the end of that XML file that goes something like
Code:
<step operation="erase" partition="userdata"/>
and it should skip the data wipe. I don't think it's necessary to remove the ones for cache and stuff. It might be a bad idea.
Click to expand...
Click to collapse
Thanks for the info, I will indeed wait for him to reply, but i just checked in the XML file, and I do not have that line anywhere in the file. Does that mean it is incomplete or does this one just default to not erasing ? Also, this is the only file I could find that is a perfect match for my french market xt910.
LaMontreBelge said:
Thanks for the info, I will indeed wait for him to reply, but i just checked in the XML file, and I do not have that line anywhere in the file. Does that mean it is incomplete or does this one just default to not erasing ? Also, this is the only file I could find that is a perfect match for my french market xt910.
Click to expand...
Click to collapse
Also, I just checked in the other file I found, for an english-languaged model this time, it does have these lines, but is only 560mb instead of the 800 something of my french file
LaMontreBelge said:
Thanks for the info, I will indeed wait for him to reply, but i just checked in the XML file, and I do not have that line anywhere in the file. Does that mean it is incomplete or does this one just default to not erasing ? Also, this is the only file I could find that is a perfect match for my french market xt910.
Click to expand...
Click to collapse
Huh, yeah I don't really know then. The model I have is the XT912 (Verizon). I just got this info from a thread for a newer Moto. It could very well just simply not wipe, but I wouldn't go ahead and try incase you end up actually wiping it permanently. I'm not an expert at all, so I'd just wait until he gives you advice. Does this French firmware have similar lines like that for cache or other partitions? It might be in a completely different format then what I'm looking at. But I doubt it's corrupt.
Smu1zel said:
Huh, yeah I don't really know then. The model I have is the XT912 (Verizon). I just got this info from a thread for a newer Moto. It could very well just simply not wipe, but I wouldn't go ahead and try incase you end up actually wiping it permanently. I'm not an expert at all, so I'd just wait until he gives you advice. Does this French firmware have similar lines like that for cache or other partitions? It might be in a completely different format then what I'm looking at.
Click to expand...
Click to collapse
Actually I think the xt912 is pretty much identical unless I'm mistaking something. But either way, I do appreciate your cautiousness about the subject. Yes exactly I really cannot afford to lose the data that remains on the phone. Actually yes it does seem to have fairly similar lines, here have a look, on the left is the french firmware and the right the international. Now, I do not know what the files you're used to working with look like, but they may very well have similar if not identical lines.
Edit: I just re-read your question and realized I completely misunderstood what you asked. No, the french version doesn't have formatting lines at all. Deeply sorry for this misunderstanding.
LaMontreBelge said:
Actually I think the xt912 is pretty much identical unless I'm mistaking something. But either way, I do appreciate your cautiousness about the subject. Yes exactly I really cannot afford to lose the data that remains on the phone. Actually yes it does seem to have fairly similar lines, here have a look, on the left is the french firmware and the right the international. Now, I do not know what the files you're used to working with look like, but they may very well have similar if not identical lines.
Edit: I just re-read your question and realized I completely misunderstood what you asked. No, the french version doesn't have formatting lines at all. Deeply sorry for this misunderstanding.
Click to expand...
Click to collapse
I've noticed the left one is a "1FF" firmware. Which from what I've looked up, is supposed to not have the erasing lines. While the "CFC" ones are. Which is why the right one has those. But I've noticed the left firmware has what seems to be Gingerbread. I don't know if dirty flashing an older firmware will cause issues, if it's even possible. I've found an old thread on droidforums where someone tried to go back to ICS from that JB leak and ended up bricking. I don't think I can post links because I haven't posted 10 times unless they changed something.
Smu1zel said:
I've noticed the left one is a "1FF" firmware. Which from what I've looked up, is supposed to not have the erasing lines. While the "CFC" ones are. Which is why the right one has those. But I've noticed the left firmware has what seems to be Gingerbread. I don't know if dirty flashing an older firmware will cause issues, if it's even possible. I've found an old thread on droidforums where someone tried to go back to ICS from that JB leak and ended up bricking. I don't think I can post links because I haven't posted 10 times unless they changed something.
Click to expand...
Click to collapse
Actually, the phone is still on gingerbread (2.3.5) as I never found updates when it still worked, so this shouldn't be an issue (hopefully) and okay, thanks for the info, so it means my file is sound, right?
LaMontreBelge said:
Actually, the phone is still on gingerbread (2.3.5) as I never found updates when it still worked, so this shouldn't be an issue (hopefully) and okay, thanks for the info, so it means my file is sound, right?
Click to expand...
Click to collapse
I believe the file should be good unless you somehow got a bad download or something. But it seems 2.3.5 and 2.3.6 have different bootloader versions, and it looks like the firmware on the left doesn't have the "mbm" stuff. The last thing you need is a hard brick, so I'd be pretty hesitant to flash unless someone who has more knowledge tells you it's okay. I'm guessing you'd have to find a French CFC firmware and edit out that userdata wipe line (if that even works) or find a 1FF 2.3.5 firmware with an identical bootloader.
Smu1zel said:
I believe the file should be good unless you somehow got a bad download or something. But it seems 2.3.5 and 2.3.6 have different bootloader versions, and it looks like the firmware on the left doesn't have the "mbm" stuff. The last thing you need is a hard brick, so I'd be pretty hesitant to flash unless someone who has more knowledge tells you it's okay. I'm guessing you'd have to find a French CFC firmware and edit out that userdata wipe line (if that even works) or find a 1FF 2.3.5 firmware with an identical bootloader.
Click to expand...
Click to collapse
Alright, then I won't flash it, just in case. Also, do you have any way to check if the bootloader version is different ? If yes, I could check it. And alright, I'll try finding another file that happens to be on 2.3.5. Thanks again for the info sir.
LaMontreBelge said:
Alright, then I won't flash it, just in case. Also, do you have any way to check if the bootloader version is different ? If yes, I could check it. And alright, I'll try finding another file that happens to be on 2.3.5. Thanks again for the info sir.
Click to expand...
Click to collapse
I hyperlinked a link I found with some info on that. I just looked at the build number of the versions listed in that doc, looked at the bootloader version next to it, and looked at the firmware's filename. In your case, "6.5.1-167" has bootloader version "0A.6C" while 2.3.5 with the build number "6.5.1_73" has bootloader version "0A.66". My source was this Doc https://docs.google.com/document/d/1CWZU-4i7jWO26RXJ7YFJV-Ze-mJrDaTuCuVI-ZwxDBE/. I honestly don't know if the bootloader matters, but I wouldn't want to risk it in case it makes the situation worse. Hopefully shadow can help you out.
https://forum.xda-developers.com/t/index-motorola-droid-razr-2012.3023837/post-58684547
Here's a pinned thread with some firmwares if it helps any.
Smu1zel said:
I hyperlinked a link I found with some info on that. I just looked at the build number of the versions listed in that doc, looked at the bootloader version next to it, and looked at the firmware's filename. In your case, "6.5.1-167" has bootloader version "0A.6C" while 2.3.5 with the build number "6.5.1_73" has bootloader version "0A.66". My source was this Doc https://docs.google.com/document/d/1CWZU-4i7jWO26RXJ7YFJV-Ze-mJrDaTuCuVI-ZwxDBE/. I honestly don't know if the bootloader matters, but I wouldn't want to risk it in case it makes the situation worse. Hopefully shadow can help you out.
Click to expand...
Click to collapse
Okay, i just took a look at the doc linked, and I have no idea how you found it, but it is mind boggling. All the roms, listed, just like that. Thank you so much. And yes indeed the bootloader is different, and I wouldn't risk it. I'll keep looking for the 2.3.5 ROM, but for now it seems like a lost cause. Perhaps they have it over on the Motorola forums. I'll make a thread later today.
Smu1zel said:
I hyperlinked a link I found with some info on that. I just looked at the build number of the versions listed in that doc, looked at the bootloader version next to it, and looked at the firmware's filename. In your case, "6.5.1-167" has bootloader version "0A.6C" while 2.3.5 with the build number "6.5.1_73" has bootloader version "0A.66". My source was this Doc https://docs.google.com/document/d/1CWZU-4i7jWO26RXJ7YFJV-Ze-mJrDaTuCuVI-ZwxDBE/. I honestly don't know if the bootloader matters, but I wouldn't want to risk it in case it makes the situation worse. Hopefully shadow can help you out.
Click to expand...
Click to collapse
Also, in the document there is a link that leads to an archive, but no files are downloadable, do you happen to have any of them by chance ?
Smu1zel said:
https://forum.xda-developers.com/t/index-motorola-droid-razr-2012.3023837/post-58684547
Here's a pinned thread with some firmwares if it helps any.
Click to expand...
Click to collapse
This thread does indeed help a little bit, but the firmware center link does not, as it is where i got my 2.3.6 ROM from, and as far as I know, is the only french one. Honestly I do not care if it's an English one, I just want to make sure that it won't mess up the phone
LaMontreBelge said:
Also, in the document there is a link that leads to an archive, but no files are downloadable, do you happen to have any of them by chance ?
Click to expand...
Click to collapse
Yeah I think those links might be out of date. Go under "XT910" and look at some of the links. Also I found that doc under that section.
https://forum.xda-developers.com/t/index-motorola-droid-razr-2012.3023837/post-58684547
I hope I'm not leading you down a wrong path, hopefully he responds soon. Maybe the bootloader doesn't matter, I don't know.