I unlocked my bootloader and everything was fine. Then I installed CM10.1.2 and it loads to the initial Welcome screen (where you select country) but the touch doesn't work at all. The volume and power button works but I can't tap anything.
Also no softbutton shows.
I also tried flashing CM10.1.0 and the latest FXP rom.
If anyone helps solve this it would be so appreciated.
Sounds like you flashed the wrong version for your phone.
Which phone do you have and which cm dud you flash
Sent from my LT30p using xda premium
gregbradley said:
Sounds like you flashed the wrong version for your phone.
Which phone do you have and which cm dud you flash
Sent from my LT30p using xda premium
Click to expand...
Click to collapse
I have an Xperia T and I flashed CM Mint.
ok, try flashing a stock ftf in flashtool to see if touch screen comes back.
If that works redownload the cm mint .zip and try flashing it again.
Let me know how you get on
gregbradley said:
ok, try flashing a stock ftf in flashtool to see if touch screen comes back.
If that works redownload the cm mint .zip and try flashing it again.
Let me know how you get on
Click to expand...
Click to collapse
Okay trying to find an appropriate stock ftf, or does it not really matter?
Like if I had a central european unbranded one or something on my UK Orange phone?
foxyfennec said:
Okay trying to find an appropriate stock ftf, or does it not really matter?
Like if I had a central european unbranded one or something on my UK Orange phone?
Click to expand...
Click to collapse
doesn't matter, just make sure its fir the right phone model or use one of mine from the all in one thread (Its Vodafone, but that does not matter)
gregbradley said:
doesn't matter, just make sure its fir the right phone model or use one of mine from the all in one thread (Its Vodafone, but that does not matter)
Click to expand...
Click to collapse
I flashed yours onto my phone and it loads up but the same problem happens The touchscreen still doesn't work.
I saw this earlier before heading to work: http://forum.xda-developers.com/showpost.php?p=39920703&postcount=11
But when I adb shell I don't get a [email protected] I have some garbled text. Basic commands like ls work. su is not found though, neither is the rmi4_fwloader command found. But then adb devices showed it in "recovery" mode not "device". Though on this computer adb devices shows nothing but fastboot does. Did flashing the stock rom relock it?
Thanks
foxyfennec said:
I flashed yours onto my phone and it loads up but the same problem happens The touchscreen still doesn't work.
I saw this earlier before heading to work: http://forum.xda-developers.com/showpost.php?p=39920703&postcount=11
But when I adb shell I don't get a [email protected] I have some garbled text. Basic commands like ls work. su is not found though, neither is the rmi4_fwloader command found. But then adb devices showed it in "recovery" mode not "device". Though on this computer adb devices shows nothing but fastboot does. Did flashing the stock rom relock it?
Thanks
Click to expand...
Click to collapse
That postwas my next piece of advice to you...
ok, have you unlocked your bootloader? Have you rooted the new firmware? Use bin4ry or doomlords rooting method to root the firware and try again.
also, you can use a USBOTG cable and a mouse to control the phone instead of the touchscreen
gregbradley said:
That postwas my next piece of advice to you...
ok, have you unlocked your bootloader? Have you rooted the new firmware? Use bin4ry or doomlords rooting method to root the firware and try again.
also, you can use a USBOTG cable and a mouse to control the phone instead of the touchscreen
Click to expand...
Click to collapse
The bootloader was still unlocked after putting your firmware on.
Is there a way of enabling usb debug mode outside of the phone? I'm guessing that's what's needed to get adb shell to work.
Woohoo! Progress! Still broken, but progress!!!!
I installed PdaNet and it made adb drivers work. Then I did adb shell from recovery.
This part is important:
The path is messed up on my phone so if anyone has trouble with that method for similar reasons would have to do the same:
Code:
/sbin/su
/system/bin/rmi4_fwloader -b /system/etc/firmware/touch_module_id_0x32.img -d /sys/bus/rmi4/devices/sensor00 -r -f
(echo $PATH is /sbin/ but for some reason su doesn't work without /sbin/. if /sbin/su doesn't work what I actually did was cd /sbin then su)
(It is important to run /system/bin/rmi4_fwloader because it simply can't find rmi4_fwloader, even if you cd /system/bin/)
Now my touch works! I just have no software buttons
Any idea how to get my.. nevermind, after going through the startup bit they just appeared.
Thank you you are a genius!
No problem, Glad its sorted for you now.
Related
Hi all,
prior to any comment, yes, i know there are already posts on this issue, however looking through them didn't help at all unfortunately.
I have a Moto Milestone, origin is Israel.
somewhere along the way i've updated the bootloader to 90.78 and since then - the phone is stuck in the notorious loop and cannot restart the OS.
Tried already to reflash the phone without luck using RSD Lite (downloaded the SBF through http://and-developers.com/sbf:milestone - the 'official' Cellcom IL SBF that was there...)
anyway - i can still access the bootloader which tells me the phone is not fully bricked, however i can't seem to find any proper SBF so it'll reflash itself back to an operative state.
One major problem here - the phone won't get into recovery mode (i've tried all the combinations i know and that have worked before)
i've also read about wiping the cache and user data however - as far as i know, this can only be done by entering the recovery mode, right?
one last resort i've tried - trying to split the SBF and reconstructing it - still no joy.
does anyone here have any advice or solution o this issue? what kind of SBF do i need? how to manually reconstruct the SBF with proper files? etc.
Thanks in advance,
Tomer
Have you tried loooking into fastboot?
Sometimes a phone wont respond to to adb commands and the recovery is corrupted, but you can still flash partitions using fastboot. I "saved" a Moto dext in this fashion once. Cant remember the exact commands, but it was similar to the adb flash commands. I reflashed the recovery partition and then used recovery to flash a ROM in update.zip format. For some reason RSD lite was failing on this phone.
Just something you may want to look into if you are desperate about saving your MS.
Sent from my Milestone using XDA App
Caz666 said:
Have you tried loooking into fastboot?
Sometimes a phone wont respond to to adb commands and the recovery is corrupted, but you can still flash partitions using fastboot. I "saved" a Moto dext in this fashion once. Cant remember the exact commands, but it was similar to the adb flash commands. I reflashed the recovery partition and then used recovery to flash a ROM in update.zip format. For some reason RSD lite was failing on this phone.
Just something you may want to look into if you are desperate about saving your MS.
Sent from my Milestone using XDA App
Click to expand...
Click to collapse
Hi Caz666,
well, thought this might actually work, but had no luck.
when i try to flash my phone it does nothing other than showing me 'downloading boot.img' and thats it.
is there anything else to do in order to save my phone? i really like it
I'm also willing to donate through PayPal to anyone who can describe any working method or that can point me to any valid working process...
thanks again.
barvaz_t said:
Hi Caz666,
well, thought this might actually work, but had no luck.
when i try to flash my phone it does nothing other than showing me 'downloading boot.img' and thats it.
is there anything else to do in order to save my phone? i really like it
I'm also willing to donate through PayPal to anyone who can describe any working method or that can point me to any valid working process...
thanks again.
Click to expand...
Click to collapse
are you sure your drivers for the phone are installed properly? what RSD lite version are you using? What system? windows 32 or 64 bits?
vladstercr said:
are you sure your drivers for the phone are installed properly? what RSD lite version are you using? What system? windows 32 or 64 bits?
Click to expand...
Click to collapse
I'm quite sure they're installed properly as i managed to upgrade my bootloader version using the RSDlite.
my system is 32 bits and the drivers are the ones i installed throught the Motorola website. I've first used RSDlite 4.6 but after reading a bit I understood there are some differences between versions hence upgraded to 4.9.
barvaz_t said:
I'm quite sure they're installed properly as i managed to upgrade my bootloader version using the RSDlite.
my system is 32 bits and the drivers are the ones i installed throught the Motorola website. I've first used RSDlite 4.6 but after reading a bit I understood there are some differences between versions hence upgraded to 4.9.
Click to expand...
Click to collapse
Try the 90.78ch bootloader from http://and-developers.com/sbf:milestone ...
"XT702 variant of the 90.78 bootloader (notes from 90.78 apply here too).
It's reported to work on the A853 too. "
You've got nothing to loose on trying this. Let me know!
vladstercr said:
Try the 90.78ch bootloader from http://and-developers.com/sbf:milestone ...
"XT702 variant of the 90.78 bootloader (notes from 90.78 apply here too).
It's reported to work on the A853 too. "
You've got nothing to loose on trying this. Let me know!
Click to expand...
Click to collapse
*** [update]
I'm now on 90.78ch and see no difference whatsoever.
I've now started investigating how to re-compile an older SBF file so it'll contain the new RAMDL
(I want to flash the Brazilian version however it contains only 90.74 RAMDL)
I've compiled a new file, however the checksum is incorrect.
How it is possible to recompile this properly?
Already tried the website, the mirror there is no leading to the bootloader itself but to a wiki site.
i've tried searching almost anywhere i know, but this bootloader is non available to download.
if there's another mirror site such as rapidshare or megaupload - i'd be happy to be pointed towards it..
Hi barvaz_t!
barvaz_t said:
...
somewhere along the way i've updated the bootloader to 90.78 and since then - the phone is stuck in the notorious loop and cannot restart the OS.
...
Click to expand...
Click to collapse
Why did you upgrade the bootloader
barvaz_t said:
...
i've also read about wiping the cache and user data however - as far as i know, this can only be done by entering the recovery mode, right?
...
Click to expand...
Click to collapse
Right, is it possible to boot into recovery on your device by holding 'X' button?
barvaz_t said:
*** [update]
I'm now on 90.78ch and see no difference whatsoever.
I've now started investigating how to re-compile an older SBF file so it'll contain the new RAMDL
(I want to flash the Brazilian version however it contains only 90.74 RAMDL)
I've compiled a new file, however the checksum is incorrect.
How it is possible to recompile this properly?
Click to expand...
Click to collapse
You locked yourself out by upgrading the bootloader to the latest one.
Neither downgrade of bootloader would be possible, nor flashing older firmware SBF's.
Apart from that the milestone uses signature check on certain parts of the firmware. I really doubt that it's possible to tweak/recompile a complete SBF.
Something worth to try, is to flash vulnerable recovery SBF from within bootloader mode using RSDlite.
Here's the link to gitorious: http://gitorious.org/droid/openrecovery/blobs/master/zips/SHOLS/vulnerable_recovery.sbf
If the link does not work for you, there are also some mirrors of this file floating around. Just search!
I guess this should work, because the recovery SBF is using RAMLDR 90.78 (do know about the sign check during flash, but i guess checksum should be O.K.).
With vulnerable recovery properly installed, you might then use OpenRecovery to check your system and restore to some working state.
Good luck!
scholbert
scholbert said:
Hi barvaz_t!
Why did you upgrade the bootloader
Right, is it possible to boot into recovery on your device by holding 'X' button?
You locked yourself out by upgrading the bootloader to the latest one.
Neither downgrade of bootloader would be possible, nor flashing older firmware SBF's.
Apart from that the milestone uses signature check on certain parts of the firmware. I really doubt that it's possible to tweak/recompile a complete SBF.
Something worth to try, is to flash vulnerable recovery SBF from within bootloader mode using RSDlite.
Here's the link to gitorious: http://gitorious.org/droid/openrecovery/blobs/master/zips/SHOLS/vulnerable_recovery.sbf
If the link does not work for you, there are also some mirrors of this file floating around. Just search!
I guess this should work, because the recovery SBF is using RAMLDR 90.78 (do know about the sign check during flash, but i guess checksum should be O.K.).
With vulnerable recovery properly installed, you might then use OpenRecovery to check your system and restore to some working state.
Good luck!
scholbert
Click to expand...
Click to collapse
Thanks Scholbert for the detailed answer.
the link you gave directs to an image the RSDlite cannot flash (=error validating image).
If your interntion was that I'm supposed to flash the vulnerable recovery only, than bad news - It's already 'installed' on my device (and it shows no error whatsoever during this installation..)
Well, thanks again for trying to help, I think I'm officially out of suggestions or options here unless anyone can give further advice...
barvaz_t said:
...
If your interntion was that I'm supposed to flash the vulnerable recovery only, than bad news - It's already 'installed' on my device (and it shows no error whatsoever during this installation..)
...
Click to expand...
Click to collapse
So can you still enter recovery?
Regards,
scholbert
No, never did (since the upgrade)
If I had access to the recovery i would have at least managed to install OpenRecovery or something and manage to reflash the device
barvaz_t said:
Hi Caz666,
well, thought this might actually work, but had no luck.
when i try to flash my phone it does nothing other than showing me 'downloading boot.img' and thats it.
is there anything else to do in order to save my phone? i really like it
I'm also willing to donate through PayPal to anyone who can describe any working method or that can point me to any valid working process...
thanks again.
Click to expand...
Click to collapse
Did you try to fastboot flash only the boot.img? What about recovery? I seem to remember flashing a recovery.img on the dext...but this was last year. I may be wrong but i believe i flashed only a recovery image and then was able to access the recovery (which would allow all sorts of additional goodies).
I find it strange that fastboot reports only downloading. I seem to remember some error messages and timeouts?
Sent from my Milestone using XDA App
Caz666 said:
Did you try to fastboot flash only the boot.img? What about recovery? I seem to remember flashing a recovery.img on the dext...but this was last year. I may be wrong but i believe i flashed only a recovery image and then was able to access the recovery (which would allow all sorts of additional goodies).
I find it strange that fastboot reports only downloading. I seem to remember some error messages and timeouts?
Sent from my Milestone using XDA App
Click to expand...
Click to collapse
Nope.
trying to flash the recovery / boot images only results in the message 'downloading...' and nothing (waited for like 3 hours..)
when I terminate the action by Ctrl+C and then trying again - the message is instantly 'FAILED..' along with specification that the action of sending the command has failed.
I'm literaly out of ideas, don't know what to do..
Sent from my Milestone using XDA App
I am starting to think that there is something wrong with your device (like broken hardware).
In all my experimenting with rsd/fastboot, i did not once get a "hang". I would get checksum/signature errors, size errors, etc...but i always got some type of error code or status.
This is on 3 different Mot devices that run Android.
Sorry
Sent from my Milestone using XDA App
Caz666 said:
I am starting to think that there is something wrong with your device (like broken hardware).
In all my experimenting with rsd/fastboot, i did not once get a "hang". I would get checksum/signature errors, size errors, etc...but i always got some type of error code or status.
This is on 3 different Mot devices that run Android.
Sorry
Sent from my Milestone using XDA App
Click to expand...
Click to collapse
The device was working fine before upgrading the bootloader, so it seems that this is not a hardware issue.
Either way - guess i'll be taking it to a lab and let them figure this out..
idea
is the milestone n droid from usa same sbf file used if so i have the right sbf file i found i had couple times i had to reinstall to stock if u want to try it i can email it it work for me saved me from bricks its rooted phone just fyi
streetracer89101 said:
is the milestone n droid from usa same sbf file used if so i have the right sbf file i found i had couple times i had to reinstall to stock if u want to try it i can email it it work for me saved me from bricks its rooted phone just fyi
Click to expand...
Click to collapse
@streetracer89101 - no, as far as i know Droid and Milestone use different firmware so it won't help unfortunately. Not that it would matter if I did flash my device - it's not like I can use it anyway..
Thanks again for trying to help out
Tomer
90.78ch bootloader
Hello, I really need the bootloader 90.78ch maybe you can me it someone give Many Thanks
300zxtt said:
Hello, I really need the bootloader 90.78ch maybe you can me it someone give Many Thanks
Click to expand...
Click to collapse
Attached. Enjoy
How to get your BELL ATRIX HD onto At&t Jellybean (4.1.1) - Unlocked bootloader ONLY!
I would like to start saying that I’m not responsible for whatever happens to your phone. Thanks to MATTLGROFF who figure out this way of flashing this jellybean leak on my phone.
Having that said THIS IS ONLY FOR BELL ATRIX HD USERS THAT HAVE THEIR BOOTLOADER UNLOCKED. Please read thru and ask any questions before attempting
OK here we go:
1. I assume you’re in stock BELL ICS ROM (77.55.18.MB886.BellMobility.en.CA) … it doesn’t matter if you’re rooted or not. Make sure you have the motorola drivers installed.
2. Enable debugging mode on your phone (settings>development options> enable USB debugging)
3. MAKE SURE YOU HAVE AN UNLOCKED BOOTLOADER. To do this open command prompt and type “adb reboot-bootloader” and check....
a. It should say: "Device is UNLOCKED. Status Code:1"
4. Now double check you’re unlocked.
5. Make sure you have a charged battery (more than 60%) and boot into fastboot. (if you're not already here)
6. Now download the stock ICS zip for At&t.
a. Unzip it
b. Make sure you have the fastboot files in the same folder/path as your fxz files.
c. Flash the boot.img from the at&t zip.
i. Hold the shift key down and right click on the unzipped folder. Now in the dropdown menu click “open command prompt here”
ii. Now type “fastboot flash boot boot.img”
d. Flash the system.img
i. "Fastboot flash system system.img”
ii. you should be in Stock att ICS rom now.
7. Now download the file for the stock at&t Jellybean zip. ( you will be able to go back to ICS --I have gone back to stock 4.0.4 Bell ROM-- bc you’re only flashing boot and system images)
8. Now start back at step 6 but with the jelly bean leak ---- Or you can try just going to settings and checking for updates! (haven't tried this yet - don't know if it will flash something we don't want it to UPDATE: I guess it doesn't work)
9. You should be on AT&T Jellybean now - and you probably(thanks soulja) lost root...
Fastboot link: https://www.dropbox.com/s/rhlcajoerowtpiw/fastboots.zip
Stock ICS link: http://forum.xda-developers.com/showthread.php?t=1853522
Stock JB link: https://www.dropbox.com/s/65ro5ddf5mhdc9f/7.7.1Q-144_MB886_MR1-22_SIGNED_CFC.xml.zip
reserved. IF you have any questions please ask!
gabo_e30 said:
3. MAKE SURE YOU HAVE AN UNLOCKED BOOTLOADER. To do this open command prompt and type “adb reboot-bootloader” and check....
a. It should say: "Device is UNLOCKED. Status Code:1"
4. Now double check you’re unlocked.
5. Make sure you have a charged battery (more than 60%) and boot into fastboot. (if you're not already here)
Click to expand...
Click to collapse
You might want to just clarify that "adb reboot-bootloader" puts the device into fastboot. Took me a few minutes to figure that out.
gabo_e30 said:
9. You should be on Jellybean now - and you prolly lost root...
Click to expand...
Click to collapse
...probably! not "prolly"!
OK, so I think I followed the directions properly, it appears SafeStrap is gone, and I now get new boot animations, a "thumping" Motorola logo and then an AT&T Rethink Possible. But it seems to be stuck after it plays that, with the AT&T logo and "Rethink Possible" message. Help!
UPDATE: After much flailing about, I got it into Recovery mode (could only get there by adb reboot recovery, the vol up/down + pwr only gets me a white texted menu which included "factory" but didn't do anything".) Will see if this works.
UPDATE 2: YES! After the factory reset, I let it boot up again. I was about to give up and try going back to ICS, but then it went past the Rethink Possible logo to a configure phone screen.
UPDATE 3: What... OK so it thinks it's an AT&T phone now, that's OK. It also shows it connected to 4G which it never has (always E, H or H++) But it's still on 4.0.4 ICS even though I did load the JB rom. But I just checked updates and it's got 4.1.1!!
UPDATE 4: Update (98.4.20.en.US) downloaded. Hitting install now...
UPDATE 5: CRAP. After reboot "The software update failed!" I might try reflashing the file from 7.7.1Q-144_MB886_MR1-22_SIGNED_CFC
UPDATE 6: No joy. :/ Any tried flashing Blur_Version.77.12.22.MB886.ATT.en.US.zip? After the above procedure, is my phone now "really" an AT&T phone?
UPDATE 7: I followed the thread about fixing failed update http://forum.xda-developers.com/showthread.php?t=2050416, and then got the OTA update. THIS TIME IT WORKS!!! I did lose root though. Oh well. I tried motofail2go again, but I couldn't get the "bug report" vibrate to happen.
noob problem with adb
3. MAKE SURE YOU HAVE AN UNLOCKED BOOTLOADER. To do this open command prompt and type “adb reboot-bootloader” and check....
a. It should say: "Device is UNLOCKED. Status Code:1"
sorry where in PC or in motorola atrix ? need i another app ? thanks in advance
i just unlocked root with Motofail2Go
w0hnzimmer said:
3. MAKE SURE YOU HAVE AN UNLOCKED BOOTLOADER. To do this open command prompt and type “adb reboot-bootloader” and check....
a. It should say: "Device is UNLOCKED. Status Code:1"
sorry where in PC or in motorola atrix ? need i another app ? thanks in advance
Click to expand...
Click to collapse
First step is actually to get Motorola drivers installed on your PC, as well as adb tools. Sorry I don't have a link handy. Then from PC do the "adb reboot-bootloader".
Can this be done with at&t and why not ?
Seems like you can go jb > ics easily.
souljaboy said:
Can this be done with at&t and why not ?
Seems like you can go jb > ics easily.
Click to expand...
Click to collapse
Step #4 and the title to the thread.
Sent from my MB886 using xda premium
capran said:
First step is actually to get Motorola drivers installed on your PC, as well as adb tools. Sorry I don't have a link handy. Then from PC do the "adb reboot-bootloader".
Click to expand...
Click to collapse
thanks, now i got "Device is LOCKED. Status Code: 0"
any chance to unlock ?
regards
w0hnzimmer said:
thanks, now i got "Device is LOCKED. Status Code: 0"
any chance to unlock ?
regards
Click to expand...
Click to collapse
The title of this threads says "Unlocked bootloader ONLY!" You haven't unlocked it yet. Please go read up on how to do that first.
1. Root. http://forum.xda-developers.com/showthread.php?t=1940594
2. Can't seem to find the bootloader bit...
ATGAdmin said:
Step #4 and the title to the thread.
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
i know...
what unlocked changes is, you can replace the kernel... but the RSDLite can replace it too, i dont quite get it.
capran said:
You might want to just clarify that "adb reboot-bootloader" puts the device into fastboot. Took me a few minutes to figure that out.
...probably! not "prolly"!
OK, so I think I followed the directions properly, it appears SafeStrap is gone, and I now get new boot animations, a "thumping" Motorola logo and then an AT&T Rethink Possible. But it seems to be stuck after it plays that, with the AT&T logo and "Rethink Possible" message. Help!
Click to expand...
Click to collapse
YOu need to do a factory reset! Sorry forgot to include that in the steps! My Bad!
UPDATE: After much flailing about, I got it into Recovery mode (could only get there by adb reboot recovery, the vol up/down + pwr only gets me a white texted menu which included "factory" but didn't do anything".) Will see if this works.
UPDATE 2: YES! After the factory reset, I let it boot up again. I was about to give up and try going back to ICS, but then it went past the Rethink Possible logo to a configure phone screen.
Click to expand...
Click to collapse
YESSS!!! you figured it out!
UPDATE 3: What... OK so it thinks it's an AT&T phone now, that's OK. It also shows it connected to 4G which it never has (always E, H or H++) But it's still on 4.0.4 ICS even though I did load the JB rom. But I just checked updates and it's got 4.1.1!!
Click to expand...
Click to collapse
Yeah 4G is the same as H+, that's just how At&t symbolizes it
UPDATE 4: Update (98.4.20.en.US) downloaded. Hitting install now...
UPDATE 5: CRAP. After reboot "The software update failed!" I might try reflashing the file from 7.7.1Q-144_MB886_MR1-22_SIGNED_CFC
Click to expand...
Click to collapse
I guess it won't work huh?... we were lucky if it did!
UPDATE 6: No joy. :/ Any tried flashing Blur_Version.77.12.22.MB886.ATT.en.US.zip? After the above procedure, is my phone now "really" an AT&T phone?
Click to expand...
Click to collapse
No it's not really an at&t phone... you can flash back the Bell 4.0.4 ROM (I just did it). Remember it will ONLY WORK IF YOU HAVE AN UNLOCKED BOOTLOADER!
UPDATE 7: I followed the thread about fixing failed update http://forum.xda-developers.com/showthread.php?t=2050416, and then got the OTA update. THIS TIME IT WORKS!!! I did lose root though. Oh well. I tried motofail2go again, but I couldn't get the "bug report" vibrate to happen.
Click to expand...
Click to collapse
Cool you found a solution...(?) But it should work with the above Jellybean file. Gonna try it out again myself!
w0hnzimmer said:
3. MAKE SURE YOU HAVE AN UNLOCKED BOOTLOADER. To do this open command prompt and type “adb reboot-bootloader” and check....
a. It should say: "Device is UNLOCKED. Status Code:1"
sorry where in PC or in motorola atrix ? need i another app ? thanks in advance
i just unlocked root with Motofail2Go
Click to expand...
Click to collapse
Ok. SO install the moto drivers first (just google them -Motocast)
Now the fastboot files and put them in the same folder or path of the system and boot.img
Now connect your phone and make sure its in debugging mode
Open command prompt (cmd) in the folder you have the files you want to install. (do this by holding shift and right click on that folder)
Now type adb reboot bootloader IN CMD. You phone should reboot into fastboot! :victory:
capran said:
The title of this threads says "Unlocked bootloader ONLY!" You haven't unlocked it yet. Please go read up on how to do that first.
1. Root. http://forum.xda-developers.com/showthread.php?t=1940594
2. Can't seem to find the bootloader bit...
Click to expand...
Click to collapse
Capran you can't install it following this procedure. It won't work or you will brick.
This si only for unlocked bootloader Atrix HDs. There's only a few of them out there (they all seem to be BELL models, but not all Bell models) I think its the ones that shipped with system version: 77.55.17.MB886.BellMobility.en.CA. TheBootloader version is 10.96 i believe... and the locked one is 10.97 I think...
souljaboy said:
i know...
what unlocked changes is, you can replace the kernel... but the RSDLite can replace it too, i dont quite get it.
Click to expand...
Click to collapse
From what I understand is that RSDlite changes it but after and Only with kernels and files that r signed (by Moto)
gabo_e30 said:
Capran you can't install it following this procedure. It won't work or you will brick.
This si only for unlocked bootloader Atrix HDs. There's only a few of them out there (they all seem to be BELL models, but not all Bell models) I think its the ones that shipped with system version: 77.55.17.MB886.BellMobility.en.CA. TheBootloader version is 10.96 i believe... and the locked one is 10.97 I think...
Click to expand...
Click to collapse
How about the 77.55.18.MB886.BellMobility.en.CA can we flash it to our unlocked Atrix hd? I saw that there's an update to JB 4.1.2. on this version. Thanks
Sent from my MB886 using xda premium
I have an unlocked Bell Atrix HD. It was running 77.55.17 and I tried this method of flashing the AT&T software using fastboot and it didn't work. I could flash the boot.img, but when I went to flash the system.img.ext4 it would tell me that I had exceeded the download buffer. So at this point I had flashed the boot.img already and the phone wouldn't boot. I actually couldn't get any system.img files to flash from fastboot, even the Bell one, always the same exceeded the download buffer error. So I downloaded RSD lite and flashed the 77.55.18 Bell firmware to it via RSD lite and I was back in business again. At this point I just said to heck with it with fastboot and then flashed the stock ICS AT&T firmware via RSD lite only having used the modified XML file that is suggested to use. This worked perfectly fine as well. I was then able to root with motofail and use voodoo to backup my root. Then I just let it do the JB update OTA and that worked perfectly fine as well and then restored my root through voodoo and verified I still had root. Everything looks fine. The funny thing is I'm selling this phone, I have a Galaxy Note II now, but I was worried if I sold it with the Bell firmware nobody would want it since it was still ICS. Should be a bonus to someone that its unlocked, and rooted already hopefully.
ryuben2k said:
How about the 77.55.18.MB886.BellMobility.en.CA can we flash it to our unlocked Atrix hd? I saw that there's an update to JB 4.1.2. on this version. Thanks
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
I used RSDlite (the latest one) to flash the 77.55.18 version on my phone.. now its the one im currently running. SO yeah you can flash it! ( i still don't have an update though) Link for teh FXZ file is in the OP (same place where the ICS at&t ROM is)
BHUGHESVA said:
I have an unlocked Bell Atrix HD. It was running 77.55.17 and I tried this method of flashing the AT&T software using fastboot and it didn't work. I could flash the boot.img, but when I went to flash the system.img.ext4 it would tell me that I had exceeded the download buffer. So at this point I had flashed the boot.img already and the phone wouldn't boot. I actually couldn't get any system.img files to flash from fastboot, even the Bell one, always the same exceeded the download buffer error. So I downloaded RSD lite and flashed the 77.55.18 Bell firmware to it via RSD lite and I was back in business again. At this point I just said to heck with it with fastboot and then flashed the stock ICS AT&T firmware via RSD lite only having used the modified XML file that is suggested to use. This worked perfectly fine as well. I was then able to root with motofail and use voodoo to backup my root. Then I just let it do the JB update OTA and that worked perfectly fine as well and then restored my root through voodoo and verified I still had root. Everything looks fine. The funny thing is I'm selling this phone, I have a Galaxy Note II now, but I was worried if I sold it with the Bell firmware nobody would want it since it was still ICS. Should be a bonus to someone that its unlocked, and rooted already hopefully.
Click to expand...
Click to collapse
Glad you worked it out! The first time I did it was from the 77.55.17 version, then I updated to at&t ICS the to JEllybean and now back to Bell ICS (77.55.18) Not sure what happened, but still glad you worked it out!
That's the great thing about the forums we can all work together in solving issues!
gabo_e30 said:
Glad you worked it out! The first time I did it was from the 77.55.17 version, then I updated to at&t ICS the to JEllybean and now back to Bell ICS (77.55.18) Not sure what happened, but still glad you worked it out!
That's the great thing about the forums we can all work together in solving issues!
Click to expand...
Click to collapse
Indeed, so glad I didn't brick it, lol. Maybe it was something wrong with the fastboot executables I used, I used the same ones I had downloaded a couple weeks ago to flash the HTC One V's that I got my kids for Christmas and not the ones linked to in the original post. It worked fine for for the One V's, not for the Atrix HD for some reason. Oh well, I just like tinkering with this stuff.
gabo_e30 said:
I used RSDlite (the latest one) to flash the 77.55.18 version on my phone.. now its the one im currently running. SO yeah you can flash it! ( i still don't have an update though) Link for teh FXZ file is in the OP (same place where the ICS at&t ROM is)
Click to expand...
Click to collapse
Thanks. Here's the link that i saw from motorola that there's an update for 77.55.18. and if someone from here can prove that they already upgrade to 4.1.2.
Thanks
https://motorola-global-en-usa.custhelp.com/app/answers/detail/a_id/92147
Sent from my MB886 using xda premium
I really need help here, my phone is basically broken now. After editing boot.prop and rebooting, my phone can only go into recovery. I am using 4.1.2. I have managed to adb pull and edit it however when trying to push it says read only area. When going into adb shell and su it somehow becomes device not found. Please help me.
alantay11 said:
I really need help here, my phone is basically broken now. After editing boot.prop and rebooting, my phone can only go into recovery. I am using 4.1.2. I have managed to adb pull and edit it however when trying to push it says read only area. When going into adb shell and su it somehow becomes device not found. Please help me.
Click to expand...
Click to collapse
KDZ flash and don't play with things you don't understand.
SimonTS said:
KDZ flash and don't play with things you don't understand.
Click to expand...
Click to collapse
Uhh I've found some threads about kdz flash but I can't really find the .kdz for my phone. Do I have to use the same region .kdz?
put 20b open europe
(Deleted)
i ahve tried to install a custom rom but it didnt flash properly, and i tried to do a restore of my stock rom but its not on my phone anymore all i can do is put the phone into bootloader and recovery, i have my stock rom backed up on my pc, but i cant find a way of getting my pc to recognise the phone to enable me to get the stock rom installed, my 400pound htc one might as well be a paperweight at this rate!!
surly there is a way i can get acess to the internal sd card??
Search for: adb sideload
BenPope said:
Search for: adb sideload
Click to expand...
Click to collapse
will that work even tho i only have acess to boot loader and recovery?
also will i loose root?
nottys4 said:
will that work even tho i only have acess to boot loader and recovery?
also will i loose root?
Click to expand...
Click to collapse
It depends on the recovery, but it works in TWRP.
It is the ROM that is rooted, so if you sideload a non-rooted ROM and flash it, you will lose root. It seems you don't have a working ROM, so you don't "have" root.
BenPope said:
It depends on the recovery, but it works in TWRP.
It is the ROM that is rooted, so if you sideload a non-rooted ROM and flash it, you will lose root. It seems you don't have a working ROM, so you don't "have" root.
Click to expand...
Click to collapse
i had root and a custom rom on my phone but i reflashed a differnt rom and it wouldnt load only to realise i didnt have the working rom on my phone, ive tried adb side load and its not working, i followed the tutorial step by step???
any suggestions
nottys4 said:
i had root and a custom rom on my phone but i reflashed a differnt rom and it wouldnt load only to realise i didnt have the working rom on my phone, ive tried adb side load and its not working, i followed the tutorial step by step???
any suggestions
Click to expand...
Click to collapse
Let me correct you. You had a custom ROM that was rooted.
My suggestion is to fix the problem.
I can't help you because:
1) I don't know what recovery you have
2) I don't know what tutorial you followed
3) I don't know in which way it is "not working"
I suggest you flash TWRP 2.6.3.4 and use adb sideload.
BenPope said:
Let me correct you. You had a custom ROM that was rooted.
My suggestion is to fix the problem.
I can't help you because:
1) I don't know what recovery you have
2) I don't know what tutorial you followed
3) I don't know in which way it is "not working"
I suggest you flash TWRP 2.6.3.4 and use adb sideload.
Click to expand...
Click to collapse
i have twrp 2.6.3.3
http://forum.xda-developers.com/showthread.php?t=2559200
thats the tutorial
it wont load any rom says it cant read the rom
Post your commands which you used to copy files
sent from my mobile device
SaHiLzZ said:
Post your commands which you used to copy files
sent from my mobile device
Click to expand...
Click to collapse
all the commands that i sent are in the tutoruial that i shared
Get hold of a OTG cable. Put the ROM from the PC onto a USB stick and then flash it through your recovery using the OTG cable
Sent from my Nexus 7 using XDA Premium HD app
bored_stupid said:
Get hold of a OTG cable. Put the ROM from the PC onto a USB stick and then flash it through your recovery using the OTG cable
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
fanstastic idea but i need my phone to be able to boot back up to install super su and it cant because i dont have a rom installed on it, any idea of where i can get a stock unrooted rom from my m7 international?
i am completly stuck!!!!! is someone willing to connect to me via skype and help me out as i need my phone bacl on asap and dont know how to do it!!!
nottys4 said:
i am completly stuck!!!!! is someone willing to connect to me via skype and help me out as i need my phone bacl on asap and dont know how to do it!!!
Click to expand...
Click to collapse
You need to get adb working on your PC or you could try what bored_stupid is suggesting. You are a long why from requiring supersu at this point.
mb_guy said:
You need to get adb working on your PC or you could try what bored_stupid is suggesting. You are a long why from requiring supersu at this point.
Click to expand...
Click to collapse
are you able to have a chat with me on skype please and explain this in more detail, i've done so much in the past few days i dont even know where i am anymore
nottys4 said:
i had root and a custom rom on my phone but i reflashed a differnt rom and it wouldnt load only to realise i didnt have the working rom on my phone, ive tried adb side load and its not working, i followed the tutorial step by step???
Click to expand...
Click to collapse
Try to be more precise! Which rom are your trying to flash? Give a link!
nottys4 said:
all the commands that i sent are in the tutoruial that i shared
Click to expand...
Click to collapse
If you have posted a screenshot of your cmd prompt maybe we could pinpoint why its failing.
nottys4 said:
fanstastic idea but i need my phone to be able to boot back up to install super su and it cant because i dont have a rom installed on it, any idea of where i can get a stock unrooted rom from my m7 international?
Click to expand...
Click to collapse
You don't even have a working rom so why are you still talking about root??? You don't need root to use a usb otg cable to flash a rom.
Make sure you have the latest android sdk installed on your computer and latest htc drivers.
Post the output of fastboot getvar all minus imei/sn
alray said:
Try to be more precise! Which rom are your trying to flash? Give a link!
If you have posted a screenshot of your cmd prompt maybe we could pinpoint why its failing.
You don't even have a working rom so why are you still talking about root??? You don't need root to use a usb otg cable to flash a rom.
Make sure you have the latest android sdk installed on your computer and latest htc drivers.
Post the output of fastboot getvar all minus imei/sn
Click to expand...
Click to collapse
many thanks guys for your help i managed to get my phone back online again!! but i now have another problem...
hi there after completely messing my phone up i managed to get this rom back on and working!! but my phone gives this error message:
There was a problem communicating with google servers.
try again later.
does anyone know why this is??
anybody else having issues with thier google account??
nottys4 said:
anybody else having issues with thier google account??
Click to expand...
Click to collapse
It is problem globally! Google is experiencing major error with sync servers.
or try this: go to accounts.google.com and in security (left panel) go to the list of 3rd party applications that are using your Google credentials and start revoking the applications that you no longer use.
Softor4pda said:
It is problem globally! Google is experiencing major error with sync servers.
Click to expand...
Click to collapse
bugger!!! i really wanna get my phone set up too, any ideas of how long they will be down?
I'm trying to root my Motorola Razr i XT890.
First I need to unlock the bootloader (right?), so I was fallowing this thread: Unlock the Bootloader on Your RAZR i
The thread is about 2 years old, so if is there any new solution for rooting my phone, please point me to the right direction.
1. I've downloaded the USB driver and the full SDK from moto site. I've installed the USB driver and unzipped the SDK (I was not able to find any install.exe, I clicked "SDK Manager.exe" but nothing happens).
2. Config the phone to USB debug, reboot in fastboot mode, plugged to USB.
3. I opened the CMD, get into the adt-bundle-windows-x86_64-20140321\sdk\platform-tools\ where fastboot.exe and typed: fastboot oem get_unlock_data
the result is: FAILED (remote: Restricted OEM command)
Some phone data:
Version: 982.50.29.XT890.Brasil.en.BR
Kernell: 3.0.34-gf0ff387
[email protected]) )
I've never rooted a phone or anything, so please, give me detailed newbie help. Thanks in advance! :good:
Pedro77 said:
I'm trying to root my Motorola Razr i XT890. First I need to unlock the bootloader (right?)
Click to expand...
Click to collapse
Welcome.
You don´t need to unlock the bootloader to root!
If you are on JB 4.1.2 than the only you need is: "Twerk my Moto" http://forum.xda-developers.com/showthread.php?t=2541398
If you are on ICS 4.0.4 you will need "motofail2go". (second link in OP) http://forum.xda-developers.com/showthread.php?t=1928509
Hope i could help. Good luck!
Thank you for the info. So I do not need to unlock the bootloader. Nice. Anyway, this is odd that I'm not allowed to do so. Also, there is almost no info about this issue.
My Android version is 4.1.2. I followed the link you pointed and the instructions are:
To use:
adb push su /data/local/tmp/
adb push rootme.sh /data/local/tmp/
adb push TwerkMyMoto.jar /data/local/tmp/
adb shell chmod 755 /data/local/tmp/rootme.sh
adb shell /data/local/tmp/rootme.sh
adb reboot
adb shell /data/local/tmp/rootme.sh
Click to expand...
Click to collapse
What a heck is this?
Can you give me some help with it?
Pedro77 said:
What a heck is this?
Can you give me some help with it?
Click to expand...
Click to collapse
ADB is a comandline-tool like cmd.exe, google how to use...
1. Install RAZRi drivers.
2. Enable USB-Debugging in Developer-Options on Handy.
3. Download ADB files (ADB is a comandline-tool, google how to use)
4. Extract "TwerkMyMoto.zip" (rootme.sh + SU + TwerkMyMoto.jar MUST be in same folder with ADB.exe)
5. Connect your RAZRi to PC and run ADB.exe. Check if ADB shows Handy as "device".
6. Follow the Steps "To use". (You have to copy and paste each line in the ADB-Window and execute it)
Good luck!
Thank you very much, as son as I try it I'm going to post the result here!
Yeah, it worked just fine!
I have a doubt:
To use:
...
adb shell /data/local/tmp/rootme.sh
adb reboot
adb shell /data/local/tmp/rootme.sh ->
Click to expand...
Click to collapse
Why I need to exec this line again?
Pedro77 said:
Yeah, it worked just fine!
Why I need to exec this line again?
Click to expand...
Click to collapse
Congrats for rooting your first device :good:
I have had a look in the source code some time ago...
something is loaded into system filesystem and needs a reboot to commit changes.
After that it needs to execute again. So thats why the line is doubled...
Did u test if root is working?
And it would be nice if you hit "Thanks" Button if i could help :cyclops:
greetz
Oh, sorry I'm new to the forum practices. Thanks button pressed! :good:
And yes, I did checked the root, it worked!
Pedro77 said:
Oh, sorry I'm new to the forum practices. Thanks button pressed! :good:
And yes, I did checked the root, it worked!
Click to expand...
Click to collapse
Nice!
I hope this root-methode is still working after KitKat Update in the next weeks...
Now u are rooted i recommend u to enable Adobe Flash: http://forum.xda-developers.com/showthread.php?t=1952878&page=4 (last page)
And to start modding try "Xposed Framework". There u can load tons of "mods" on to your handy.
i recommend "Xposed Framework" + GravityBox + YouTube Addaway.
(maybe its better to backup your important Data befor playing around...)
And no worries that u mess up your device. If u stuck in bootloops or something else is broken just flash back your original firmware with RSD-Lite: http://forum.xda-developers.com/showthread.php?t=2239706
So, have fun with your rooted device and thanks for pressing Thanks-Button!
Using RSD with unlocked BL work fine?? RSD relock BL?
Sent from my XT890 using xda app-developers app
AlmapekeDj said:
Using RSD with unlocked BL work fine?? RSD relock BL?
Click to expand...
Click to collapse
RSD should also work with unlocked bootloader...
And i think there was a trick to relock bootloader by flashing some files, but i dont know the files.
You have to search in this Forum for relock-tutorial ...
P.S. What Kind of Music did you play? Psytrance/GOA?
AlmapekeDj said:
Using RSD with unlocked BL work fine?? RSD relock BL?
Sent from my XT890 using xda app-developers app
Click to expand...
Click to collapse
from my personal experiences: using RSD-Lite with unlocked BL works like a charme
And no, it will not relock your BL
To relock you can use this guide: http://forum.xda-developers.com/showpost.php?p=44430691&postcount=4
Hi there, I am having the same issue but my OS version is 4.4.2 now.
There is also a nice guide here: http://forum.xda-developers.com/showthread.php?t=1928551
But I would still need the code.....
So what do you propose I should do? I only need root so I can use a directory binding tool to make some room on the internal space, I ran out and can no longer update the apps....
(Btw. I did unlock my first RAZR, but that one broke down so now I am on an used one.. )
Thanks!