Just wondering how I can check which bootloader I have? as in the froyo or gingerbread one? Iflashed JVK and then tried to flash old bootloader but I'm not sure if it worked.......
When you reboot to recovery mode isnt the bootloader version shown there? like by default 2e or something like that?
cant remember exctaly but think that's it? Personally I have clockwork mod installed and would highly recommend it.
You can try if on windows :
adb bugreport | find "bootloader"
or if on linux :
adb bugreport | grep bootloader
Bootloader info?
+1 to that question: can't run adb on windows connected to phone and adb on phone terminal doesn't work. Can't find info on bootloader on default CW recovery.
Phone info shows Baseband version I9000XXJVK - but I don't know its connected anyhow?
There is no simple way to tell which bootloaders you have installed, there is no code to display it, no settings menu that will give you a clue. To be honest, 99,999 times out of 100,000 there is absolutely no need for you to know if you have Froyo of Gingerbread bootloaders.
However if you really want to know, and know your way around .bin files and hexadecimal editors, you can try the methods advised in this post: http://forum.xda-developers.com/showpost.php?p=16319901&postcount=13308
Daneshm90 said:
You can try if on windows :
adb bugreport | find "bootloader"
or if on linux :
adb bugreport | grep bootloader
Click to expand...
Click to collapse
I did it and, in my case (sgs i9000 cm7.1) says:
[ro.bootloader]: [unknown]
is it bad?
*#1234#
madigan94 said:
Just wondering how I can check which bootloader I have? as in the froyo or gingerbread one? Iflashed JVK and then tried to flash old bootloader but I'm not sure if it worked.......
Click to expand...
Click to collapse
Dis you try going to dialer and pressing *#1234# ?
What was the last stock version you had? GB?
Sent from my GT-I8190 using Tapatalk
rb1725 said:
Dis you try going to dialer and pressing *#1234# ?
Click to expand...
Click to collapse
LOL look at the date of the post you've answered.... 3 years old.
tetakpatalked from Nexus 7 flo
tetakpatak said:
LOL look at the date of the post you've answered.... 3 years old.
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
Lol, here I am 3 years after you, trying to find my bootloader version
just_another_guy said:
Lol, here I am 3 years after you, trying to find my bootloader version
Click to expand...
Click to collapse
and me also but for i9305
7 years later, here is the answer:
The current bootloader version can be checked by running the command getprop ro.bootloader in a terminal app or an adb shell from a command prompt (on Windows) or terminal (on Linux or macOS) window.
just_another_guy said:
Lol, here I am 3 years after you, trying to find my bootloader version
Click to expand...
Click to collapse
MystaMagoo said:
and me also but for i9305
Click to expand...
Click to collapse
Easiest solution: use the app Kernel Adiutor, you’ll find the info on the “Device” tab.
8 years later, here is the simple answer:
Use cpuz for android under "system" tab!
https://play.google.com/store/apps/details?id=com.cpuid.cpu_z&hl=en
Related
hey tell me why i cant flash this recover. in the command said cannot load '/path/to/recovery-clockwork-3.0.0.5-passion.img'
whats wrong with me ? thanks
More details of what you are doing, help us help you.
baseballfanz said:
More details of what you are doing, help us help you.
Click to expand...
Click to collapse
yes 1st unlock the bootloader i follow on modacco forum
http://android.modaco.com/topic/299078-how-to-unlock-the-bootloader-on-your-nexus-one/
2nd i wanna flash the custom recovery , i follow on wiki nexus one .
what am i doing wrong ? or step that i take ?
thanks for reply brother
easiest way is to get ROM Manger from market and flash CWM that way.
I would stay away from CWM 3.0 since it's known to cause problems.
baseballfanz said:
easiest way is to get ROM Manger from market and flash CWM that way.
I would stay away from CWM 3.0 since it's known to cause problems.
Click to expand...
Click to collapse
yeah ithink like that ,but it needs root ,and im on stock rom 2.3.4 how to root it?
Sent from my Nexus One using Tapatalk
Oh, all this time I though you were already rooted.
Yeah you can't install custom recovery till you root first.
Read the WIKI on rooting
If you have unlocked your bootloader (I think that is what you said earlier?), then just flash recovery via fastboot like the wiki says...
What part are you struggling with? Are you getting any error messages?
baseballfanz said:
Oh, all this time I though you were already rooted.
Yeah you can't install custom recovery till you root first.
Read the WIKI on rooting
Click to expand...
Click to collapse
yes i see .but how to root 2.3.4 ?wiki just 2.3.3 downgrade?
Sent from my Nexus One using Tapatalk
danger-rat said:
If you have unlocked your bootloader (I think that is what you said earlier?), then just flash recovery via fastboot like the wiki says...
What part are you struggling with? Are you getting any error messages?
Click to expand...
Click to collapse
i got problem on command ,it said cant load recovery-clockwork.whats my problem?
Sent from my Nexus One using Tapatalk
When you boot up your phone, do you see a symbol of a open lock?
Sent from my Transformer TF101 using Tapatalk
baseballfanz said:
When you boot up your phone, do you see a symbol of a open lock?
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
yes i see under symbol X .what should i do?
Sent from my Nexus One using Tapatalk
I think you are just copying the command verbatim.
When it says /path/to/recovery.img it literally means wherever you have saved that file on your computer. In windows, it could very much look like
Code:
fastboot flash recovery "c:\user\john doe\Downloads\clockworkmod\recovery.img"
Keep in mind, if you are using windows, if the location has any spaces in it, it requires quotes around the whole thing.
bassmadrigal said:
I think you are just copying the command verbatim.
When it says /path/to/recovery.img it literally means wherever you have saved that file on your computer. In windows, it could very much look like
Code:
fastboot flash recovery "c:\user\john doe\Downloads\clockworkmod\recovery.img"
Keep in mind, if you are using windows, if the location has any spaces in it, it requires quotes around the whole thing.
Click to expand...
Click to collapse
it workss broo !! thanks youu i love you :* LOL
No problem. Now go enjoy your phone
bassmadrigal said:
No problem. Now go enjoy your phone
Click to expand...
Click to collapse
yes thanks you , actually i got a problem with stock rom 2.3.4 i was alwys rebooting , so i try to flash cwm for cm7 thanks .
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 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.
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!
when you go into settings the wifi is grayed out. I tried a hard reset and same problem exist. My other tablets all work fine. Any Suggestions?
kapebretoner said:
when you go into settings the wifi is grayed out. I tried a hard reset and same problem exist. My other tablets all work fine. Any Suggestions?
Click to expand...
Click to collapse
Custom rom or stock? Name and Version? Kernel? bootloader version? Much more info required ......
wifi greyed out
sbdags said:
Custom rom or stock? Name and Version? Kernel? bootloader version? Much more info requires
stock rom
android version 4.3
Click to expand...
Click to collapse
kapebretoner said:
sbdags said:
Custom rom or stock? Name and Version? Kernel? bootloader version? Much more info requires
stock rom
android version 4.3
Click to expand...
Click to collapse
If a factory reset doesn't fix it and you haven't unlocked and customised it then it looks like a hardware failure to me.
Can you enable usb debugging in settings / developer settings and try and capture a logcat and dmesg. That will tell us for sure.
Zip them up and post them please.
Run these from a pc (you will need to install adb if you don't have it) whilst connect to the tablet via a command line prompt.
Code:
adb logcat -v time > logcat.txt
adb dmesg > dmesg.txt
Click to expand...
Click to collapse
this is what I get when enter the first command listed.
the process cannot access the file because it is being used by another process.
kapebretoner said:
this is what I get when enter the first command listed.
the process cannot access the file because it is being used by another process.
Click to expand...
Click to collapse
What do you get with the command
Code:
adb devices
Copy the entire contents of the cmd window and post it please.