Related
Please forgive me if there are other threads.. But this is an old phone and al ow-activity device...
I bought a Verizon Mogul from ebay. Was working just fine until I decided I wanted to flash a ROM onto it. The ONLY tool I could fine from any tutorial was some titan unlock tool... All it seemed to do was bring me to the bootloader. Well, now I'm stuck in the bootloader and can't get out. I tried this exit bootloader program for Windows, but it doesn't think my phone is actually plugged in (not compatible with Windows 7?)
Other threads have suggested using some kind of .nbh file, but there is no region of the internet of which this mysitcal file exists. What do I do?
And finally... can someone provide the files needed that every tutorial says you need to flash a rom on this phone? They don't seem to exist on the internet either.
I realize this phone is old. But I like it because I can use it without a data plan
Thank you to anyone who helps.
There are some tutorials - I'll look to see what I have later. I haven't used this phone in awhile
Dr. Hax said:
I realize this phone is old. But I like it because I can use it without a data plan
Thank you to anyone who helps.
Click to expand...
Click to collapse
Did you get it figured out there?
Ok, you know, today I got my phone, I had been waiting forever, I got it and within 2 hours I screwed it up. I have followed and followed many forums and posts on how to fix this, and I am just.. lost. So please i need your help, I am seriously stressing out, and I know I shouldnt, but this is my first android phone. I am shot right now.
I had unlocked the bootloader, and then I tried to root it, then it rebooted and went into bootloop mode or whatever it is.
I still cannot figure out how to use this Hasoons2000's OX+ AIO kit. So I am just leaving it alone.
Ok the PC doesn't recognize it as a storage device, but the fastboot does recognize it, as I have executed a few commands, like reboot or something, just to test that it works.
My phone is ATT but I am in Russia so there is no sending this anywheres. All I want to do is reboot the OS and have it work again, I dont care what mod or stock rom it is, I just really need some direction here.
I know something about RUU, ATT RUU, Fastboot, some other stuff, I have like 5 pages on XDA pulled up and I cant figure this out.
What is the CMW or TWRP or whatever it is called? How do I flash a zip or an img to the phone? I really just want my phone on again.
Yes Ive done stupid noob stuff, but you learn. So please I am kindly asking for any assistance,
No need to stress. Its fairly hard to brick your phone, good way to learn quick also is to screw with it.
Just need the right guide and I think this will help you since u have fastboot access hopefully. Its a pain rebuiling so read everything so u only have to do it once.
Remember these guides are for different phones so don't use the ruu or recovery links, user my links below.
Your phone is:
AT&T(Evitare)
This guide:
http://forum.xda-developers.com/showthread.php?p=30863908
Or this guide:
http://forum.xda-developers.com/showthread.php?p=27301573
This is for another phone so you need to choose an ATT ruu from here for step 1:
Your phone is a HTC One X+ for AT&T(Evitare)*
http://www.androidfiles.org/ruu/?developer=EvitaRE
More info here for custom recoveries etc which is cwm and twrp for deploying roms, backing up your current installed Rom and general tools for fixing or enhancing your phone, displayed prior to your phone booting into android:
http://forum.xda-developers.com/showthread.php?p=37778531
Sent from my HTC One X+ using xda premium
somemadcaaant said:
No need to stress. Its fairly hard to brick your phone, good way to learn quick also is to screw with it.
Just need the right guide and I think this will help you since u have fastboot access hopefully. Its a pain rebuiling so read everything so u only have to do it once.
Remember these guides are for different phones so don't use the ruu or recovery links, user my links below.
Your phone is:
AT&T(Evitare)
This guide:
http://forum.xda-developers.com/showthread.php?p=30863908
Or this guide:
http://forum.xda-developers.com/showthread.php?p=27301573
This is for another phone so you need to choose an ATT ruu from here for step 1:
Your phone is a HTC One X+ for AT&T(Evitare)*
http://www.androidfiles.org/ruu/?developer=EvitaRE
More info here for custom recoveries etc which is cwm and twrp for deploying roms, backing up your current installed Rom and general tools for fixing or enhancing your phone, displayed prior to your phone booting into android:
http://forum.xda-developers.com/showthread.php?p=37778531
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
thank you very much I really appreciate your help. I finally figured out the ruu.exe thing, I didnt know they had to be the same numbers, ex 1.15.xxx.xx or whatever.
You see what happened originally was that I unlocked the bootloader, easy pie, but I tried to root it and that is when it started looping. Maybe I didnt understand something, but I seemed to have messed up right there.
Is there really any reason to root? I mean yeah there is super user, but doesnt bootloader help with that a bit? I know BL is for flashing custom roms and all.
May I ask how to flash a custom rom? I really want all of this ATT stuff off of my phone, I really dislike it.
Yes I know I can search, here, google etc. And maybe I should, but I end up getting so many different results, and here and there, and this and that. It really is just easier to talk to one single person who knows what they are doing. So if you could help me, I would again extend my appreciation.
Also I have the android revolution for ox+, and I dont know if it is.. you know.. THE BEST or not. Dont know what to do.
And yes, you live and learn, took me forever with iphones, then I realized hacking and roms and stuff were completely different from iphone. So new game new story.
i need some help. i just bought my htc one tonight, and of course the first thing i want to do after i turn it on is root. but i can't get fastboot to recognize it. i've reinstalled the drivers a few times, googled my heart out, and can't seem to come up with an answer.
now before a lynch mob starts, please, i'm very frustrated, and i'm fighting the urge to just throw the phone into the wall. (at this point i think it's the only thing i haven't tried).
i read somewhere about firmware and windows 8.1 (which i'm on). my phone is still on 4.1.2. i think i read 4.3 is the only one that works with windows 8.1. but there are no updates available to me.
i greatly appreciate any help here. it's such a let down to get a shiny new phone, and being stuck... once i figure out the fastboot problem i should be good to go. i want to say i had this problem a while back with my htc one x, but it was so long ago i don't remember how i fixed it. in the middle there i switched to the s3 and that rooted without a hitch.
i don't know what i did but the phone magically decided now it wants to do the att update, it's downloading pretty slow but i'll see what happens.
ck4794 said:
i need some help. i just bought my htc one tonight, and of course the first thing i want to do after i turn it on is root. but i can't get fastboot to recognize it. i've reinstalled the drivers a few times, googled my heart out, and can't seem to come up with an answer.
now before a lynch mob starts, please, i'm very frustrated, and i'm fighting the urge to just throw the phone into the wall. (at this point i think it's the only thing i haven't tried).
i read somewhere about firmware and windows 8.1 (which i'm on). my phone is still on 4.1.2. i think i read 4.3 is the only one that works with windows 8.1. but there are no updates available to me.
i greatly appreciate any help here. it's such a let down to get a shiny new phone, and being stuck... once i figure out the fastboot problem i should be good to go. i want to say i had this problem a while back with my htc one x, but it was so long ago i don't remember how i fixed it. in the middle there i switched to the s3 and that rooted without a hitch.
Click to expand...
Click to collapse
Im sure you did this, but did you make sure in HBOOT its highlighted in red "FASTBOOT USB"? And you are in the platform tools folder of the android sdk? How about ADB? Does "adb devices" (Without quotations) work?
Let me know.
GalaxyUser50 said:
Im sure you did this, but did you make sure in HBOOT its highlighted in red "FASTBOOT USB"? And you are in the platform tools folder of the android sdk? How about ADB? Does "adb devices" (Without quotations) work?
Let me know.
Click to expand...
Click to collapse
i haven't gotten there yet. still trying to do the update. for some reason i can only download 10 or 15 mb at a time. it seems like it's timing out, maybe losing connection. after a restart it downloads for a while again. so basically it's going to be a loooong night to get this update done. and some prayer that the update is not corrupted.
ck4794 said:
i haven't gotten there yet. still trying to do the update. for some reason i can only download 10 or 15 mb at a time. it seems like it's timing out, maybe losing connection. after a restart it downloads for a while again. so basically it's going to be a loooong night to get this update done. and some prayer that the update is not corrupted.
Click to expand...
Click to collapse
Are you trying this on wifi or data?
ck4794 said:
i haven't gotten there yet. still trying to do the update. for some reason i can only download 10 or 15 mb at a time. it seems like it's timing out, maybe losing connection. after a restart it downloads for a while again. so basically it's going to be a loooong night to get this update done. and some prayer that the update is not corrupted.
Click to expand...
Click to collapse
you need to s-off your phone before taking that update !!!
and you need a windows 8 or windows 7 PC ... you'll never get fastboot on windows 8.1 and hboot 1.44.000 might as well give up on that.
clsA said:
you need to s-off your phone before taking that update !!!
and you need a windows 8 or windows 7 PC ... you'll never get fastboot on windows 8.1 and hboot 1.44.000 might as well give up on that.
Click to expand...
Click to collapse
no that seemed to do the trick. installed the update this morning. the phone is now on 4.3 and fastboot works just fine.
ck4794 said:
no that seemed to do the trick. installed the update this morning. the phone is now on 4.3 and fastboot works just fine.
Click to expand...
Click to collapse
ok good ...try rumrunner if you want s-off
clsA said:
ok good ...try rumrunner if you want s-off
Click to expand...
Click to collapse
thanks. it's been a hot minute since i've had an htc phone, can you remind me why i would want s-off after i already have the device rooted?
ck4794 said:
thanks. it's been a hot minute since i've had an htc phone, can you remind me why i would want s-off after i already have the device rooted?
Click to expand...
Click to collapse
This pretty well sums it up
S-OFF – What And Why?
In their devices, HTC have installed a sort of security check whose level is determined by S-OFF/S-ON. Essentially, this security level is a flag stored on the device’s radio that checks signature images for any firmware before it is allowed to be written to system memory. This hinders using any custom ROMs, splash images, recovery etc., and also restricts access to the NAND flash memory. However, when security level is set to S-OFF, the signature check is bypassed, allowing a user to upload custom firmware images, unsigned boot, recovery, splash and HBOOT images, as well as official firmware that has been modified, this enabling maximum customization of your HTC Android device.
Furthermore, S-OFF also reduces restrictions on accessing the NAND flash memory on the device, allowing all partitions (including /system) to be mounted in write mode while the operating system is booted.
Source: http://www.addictivetips.com/mobile...on-htc-android-phones-with-unrevoked-forever/
Click to expand...
Click to collapse
Hiya folks, bit of a problem. I never bothered to root or unlock my DNA (it's been getting the job done nicely with a few non-root customizations, and I have other gadgets to tinker away with). This morning I accepted the OTA update from Verizon, and now it's bricked - stuck on the HTC splash screen.
I did a soft reset, cleared the cache partition, and performed a hard reset - no dice. Called Verizon and HTC, no help - I can pretty much do a repair/replacement if I'm still under warranty. I'd really rather avoid going down that path, as I think I'm barely over the warranty (though I can hopefully get them to honor it if I'm within 30 days).
Is there any way I can still flash this back to an older stock, having never unlocked it? I can only get the thing into fastboot mode, and all of the instructions I've found are for when the phone's been bricked after rooting. adb can't seem to talk to it at all, probably because it's in fastboot. Is it safe to attempt using an RUU or some sort of image to flash it using the fastboot utility?
Since it's already bricked, I went ahead and made a go at it using an older RUU, but it quick before even trying, claiming I needed the correct version of the utility. It's possible I did it wrong, though.
Any help would be much obliged! This is what I get for not rooting/learning how to do this stuff earlier...
EDIT: Before this newest update, my phone had the most up-to-date stock ROM. It was fully charged when it performed the OTA.
jaawerth said:
Hiya folks, bit of a problem. I never bothered to root or unlock my DNA (it's been getting the job done nicely with a few non-root customizations, and I have other gadgets to tinker away with). This morning I accepted the OTA update from Verizon, and now it's bricked - stuck on the HTC splash screen.
I did a soft reset, cleared the cache partition, and performed a hard reset - no dice. Called Verizon and HTC, no help - I can pretty much do a repair/replacement if I'm still under warranty. I'd really rather avoid going down that path, as I think I'm barely over the warranty (though I can hopefully get them to honor it if I'm within 30 days).
Is there any way I can still flash this back to an older stock, having never unlocked it? I can only get the thing into fastboot mode, and all of the instructions I've found are for when the phone's been bricked after rooting. adb can't seem to talk to it at all, probably because it's in fastboot. Is it safe to attempt using an RUU or some sort of image to flash it using the fastboot utility?
Since it's already bricked, I went ahead and made a go at it using an older RUU, but it quick before even trying, claiming I needed the correct version of the utility. It's possible I did it wrong, though.
Any help would be much obliged! This is what I get for not rooting/learning how to do this stuff earlier...
EDIT: Before this newest update, my phone had the most up-to-date stock ROM. It was fully charged when it performed the OTA.
Click to expand...
Click to collapse
Exact same thing happened to me last evening...except I'm rooted with S-off.
grimmkt said:
Exact same thing happened to me last evening...except I'm rooted with S-off.
Click to expand...
Click to collapse
Try flashing the latest RUU ZIP in fastboot. someone had a similar issue.
http://forum.xda-developers.com/showpost.php?p=48301738&postcount=6
The actual thread is here: http://forum.xda-developers.com/showthread.php?t=2558885
ryclegman said:
Try flashing the latest RUU ZIP in fastboot. someone had a similar issue.
http://forum.xda-developers.com/showpost.php?p=48301738&postcount=6
The actual thread is here: http://forum.xda-developers.com/showthread.php?t=2558885
Click to expand...
Click to collapse
Aha! Much obliged. I searched for the right RUU and couldn't find it, and completely missed that thread - I was using the wrong search terms. Downloading now - I'll update tonight once I know if it works. Then I'm modifying the crap out of this thing!
jaawerth said:
Aha! Much obliged. I searched for the right RUU and couldn't find it, and completely missed that thread - I was using the wrong search terms. Downloading now - I'll update tonight once I know if it works. Then I'm modifying the crap out of this thing!
Click to expand...
Click to collapse
Sounds good! let us know!:good:
ryclegman said:
Try flashing the latest RUU ZIP in fastboot. someone had a similar issue.
http://forum.xda-developers.com/showpost.php?p=48301738&postcount=6
The actual thread is here: http://forum.xda-developers.com/showthread.php?t=2558885
Click to expand...
Click to collapse
I can't get the phone to connect in fastboot. I keep getting a "driver failed to load" type error when I plug in the USB...the device is never visible.
Worked like a charm! The download took awhile, but once I had it downloaded it was easy.
For others searching for this issue:
Once you have the RUU, just install Android Development tools (specifically fastboot) and enter
>fastboot oem rebootRUU
>fastboot flash install IMAGEFILE.ZIP
Terminal/command prompt on the computer side told me it was finished but the phone was stuck at the very end of the progress bar. I waited a while few minutes, and when it didn't move I risked doing a
>fastboot reboot
and we were good to go.
Arise, thread!
So! My phone never bricked again, but a few weeks after I performed the RUU with the image linked earlier in this thread, I started to see the problem that early DNA's started to have with it randomly giving a "no SIM card" error. I'd had this issue when I first got the DNA, but at the time I just went through the normal phone replacement process to resolve it. Imagine my surprise when it came back after flashing! It's now reached the point where I will lose calls because of it, and will often have to reboot/toggle airplane mode to get data back, so I finally got annoyed enough to post.
Presumably this problem is because the image I flashed from is the original DNA image with the drivers that cause that SIM issue. So my question is: if I s-off, root, and install a custom ROM, will that take care of it? Or is this particular issue so deep on the driver level that I need to find a more recent RUU?
I also have not yet tried a new SIM - because of the timing of the problem, I'm slow to believe that it's related to the SIM card, but I suppose it isn't impossible.
jaawerth said:
Arise, thread!
So! My phone never bricked again, but a few weeks after I performed the RUU with the image linked earlier in this thread, I started to see the problem that early DNA's started to have with it randomly giving a "no SIM card" error. I'd had this issue when I first got the DNA, but at the time I just went through the normal phone replacement process to resolve it. Imagine my surprise when it came back after flashing! It's now reached the point where I will lose calls because of it, and will often have to reboot/toggle airplane mode to get data back, so I finally got annoyed enough to post.
Presumably this problem is because the image I flashed from is the original DNA image with the drivers that cause that SIM issue. So my question is: if I s-off, root, and install a custom ROM, will that take care of it? Or is this particular issue so deep on the driver level that I need to find a more recent RUU?
I also have not yet tried a new SIM - because of the timing of the problem, I'm slow to believe that it's related to the SIM card, but I suppose it isn't impossible.
Click to expand...
Click to collapse
The only way I have seen this permanently resolved is to get a new Sim tray from HTC. I got one and my brother did too and I never get Sim card errors like I used to. Just go to their website contact their support and ask for one and they send it out for free no questions asked.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Jaggar345 said:
The only way I have seen this permanently resolved is to get a new Sim tray from HTC. I got one and my brother did too and I never get Sim card errors like I used to. Just go to their website contact their support and ask for one and they send it out for free no questions asked.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, may as well give it a try. What's odd is that this problem hadn't happened at all with this sim tray until after I flashed, which really makes it sound like a software issue. Still, worth a shot!
jaawerth said:
Thanks, may as well give it a try. What's odd is that this problem hadn't happened at all with this sim tray until after I flashed, which really makes it sound like a software issue. Still, worth a shot!
Click to expand...
Click to collapse
It's a known hardware issue in the DNA. When they give you a new Sim tray it's thicker and it holds the Sim card in place better resulting with no more errors.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
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.