Related
To all devs out there ,im been trying to root the hero for a week now ,ive tried every guide going also the gold card with 10 different sd cards with no luck.the rom what ive got is the release 2.73.405.66 rom.it has the new nboot is thats why i cant flash.is there any way i can wipe all date and software so i will have nothing on the phone and then install an earlier rom, its just an idea as im starting to lose it with this fone.i hope someone can help me or do i have to wait for the official update from htc
with this rom version you need to create a goldcard and downgrade your rom before you can install a custom rom. if you have problems with the goldcard you should be more specific.
waiting for the update doesn't seem like the best idea, because it might take some until a security flaw is found that allows to root the rom when already installed on the phone. if you have the custom recovery image you will be able to install the (pre-rooted) update short time after it was released.
You should be able to use fastboot for this issue.
Search around the forums, (also http://hero.modaco.com) and read about it.
All you need is the fasboot tool, a usb cable and the "debugging mode" switched on at ur phone...
everytime i create the gold card and try to downgrade the rom it states boot error 140.i follow the guides very indepth i get the serial number from the sdcard than i reverse the string and then replace the first two numbers or letters with 2 zeros how can you tell when the goldcard is on the sdcard.when i replace the sdcard back in sdcard reader it states that the folder is empty.im quite clued up on winmo but android is giving me a headache
wouldn't the fastboot give you the "remote: not allowed" error?
anyway, you can try:
start your phone by holding back and pushing power, you should see three skating androids. put recovery image in the folder where your fastboot.exe is, open terminal and go to that folder and type:
Code:
fastboot boot recovery-RA-hero-v1.5.3.1.img
if that works report back.
for the goldcard i can't help, never did it.
at last im rooted thanks for for the help .the way i did
(with the phone in normal mode)
1) Connect your Hero via usb to your pc/mac/...
2) Open Command Prompt ->
Put in the following text ->
C:\Users\Username> cd\
C:\>cd android\tools\
C:\>android\tools>adb push recovery-RA-Hero-v1.5.3.1.img /sdcard/recovery-RA-Hero-v1.5.3.1.img
C:\>android\tools>adb shell flash_image recovery /sdcard/recovery-RA-Hero-v1.5.3.1.img
3) JOB DONE!
rednose30 said:
at last im rooted thanks for for the help .the way i did
(with the phone in normal mode)
1) Connect your Hero via usb to your pc/mac/...
2) Open Command Prompt ->
Put in the following text ->
C:\Users\Username> cd\
C:\>cd android\tools\
C:\>android\tools>adb push recovery-RA-Hero-v1.5.3.1.img /sdcard/recovery-RA-Hero-v1.5.3.1.img
C:\>android\tools>adb shell flash_image recovery /sdcard/recovery-RA-Hero-v1.5.3.1.img
3) JOB DONE!
Click to expand...
Click to collapse
I guys, I seem to be having the same issue as the OP. Having tried the above it tells me that there is an error writing recovery: Permission denied. Any idea how to solve this?
Thanks!
mjames_84 said:
I guys, I seem to be having the same issue as the OP. Having tried the above it tells me that there is an error writing recovery: Permission denied. Any idea how to solve this?
Thanks!
Click to expand...
Click to collapse
Getting exactly the same. Tried the goldcard method numerous times using 3 different cards and always get the bootloader 140 error. Tried the above with same errors... very frustrating!
Mine is a UK T-Mobile G2 with build number 2.73.110.26, any suggestions gratefully tried!
Edit: Finally managed to sort it. I was using "RUU_Hero_HTC_WWE_1.76.405.1_R3_WWE_release_signed_NoDriver.exe" - this didnt work. Once I found and tried RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe it all clicked into place!
Thanks for all the info provided on these forums, cheers!
TastyBurger said:
Getting exactly the same. Tried the goldcard method numerous times using 3 different cards and always get the bootloader 140 error. Tried the above with same errors... very frustrating!
Mine is a UK T-Mobile G2 with build number 2.73.110.26, any suggestions gratefully tried!
Edit: Finally managed to sort it. I was using "RUU_Hero_HTC_WWE_1.76.405.1_R3_WWE_release_signed_NoDriver.exe" - this didnt work. Once I found and tried RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe it all clicked into place!
Thanks for all the info provided on these forums, cheers!
Click to expand...
Click to collapse
Hi
I have tried making a goldcard, and installed via. the RUU shown here.. 405.5 .. but then I tried using Flashrec to get another recovery image, it failed making the first step...
So is my phone rooted or did something go wrong ?
the phone is still unfortunately not rooted. I would've tried the fastboot method
Sent from my HTC Hero using the XDA mobile application powered by Tapatalk
just curious but did anyone just try to flash the older version without bothering with the goldcard...i dun know what i did to my htc hero orange but when i was researching i was told i needed to downgrade to root. I tried to take a long shot and used htc sync and old orange ruu..and somehow it just downgraded itself.... i know it might not help but its a long shot!
nicknyhk said:
just curious but did anyone just try to flash the older version without bothering with the goldcard...i dun know what i did to my htc hero orange but when i was researching i was told i needed to downgrade to root. I tried to take a long shot and used htc sync and old orange ruu..and somehow it just downgraded itself.... i know it might not help but its a long shot!
Click to expand...
Click to collapse
Very similar story. I did make a goldcard but hadn't got as far as finding out how to extract the update.zip out of the RUU exe, in order to use it. I tried running the RUU to see what would happen & my Hero downgraded.
How do I go about installing a new boot screen? also how easy is it do design my own?
Any guide around? do I need to install a full rom to do this everytime I want to change the boot screen?
Thanks
There are a few guides around. No you don't have to reflash a ROM you can ADB push the bootanimation.zip file see some info here
So far I haven't manged to make one that boots correctly
You could have also scrolled down a bit and seen this
Thanks! Will look in to it now
-------------------------------------
Sent via the XDA Tapatalk App
I cant do it!
this guide is for ubuntu which I dont have. Is there a guide for windows? I cant seem to get in to console to do the push codes
adb push bootanimation.zip /data/local
where do I type this in? ^^
its ok ive figured it out. Theres no need to push any files just flash .zip file while in recovery mode! Sorted cheers
Could someone please advise me on what I am doing wrong here.
Ive been posting on this thread:
http://android.modaco.com/content/a...ired-of-nexus-boot-animation-get-some-liquid/
I cant seem to get my boot animation signed properly so the desire will install it.
Could someone give the thread a quick read (only 2 pages) and let me know what I'm doing wrong?
Thanks,
Andy.
and I thought these forums were cool................
*sigh*
They are cool. Use that command (the adb) one from recovery.
these forums rock
JupiterDroid said:
these forums rock
Click to expand...
Click to collapse
+5 so True
Im absolutely racking my brains and I cant seem to find an answer to my problem.. Im trying to root my Legend with software version 2.05, which means I need to downgrade to 1.31 1st.. which is where my problems start..
http://forum.xda-developers.com/showthread.php?t=725430
Ive followed this guide and I always 100% fail to push the files to the phone, on searching for an answer it seems it happens alot and no one has a specific answer.
Like here..
I am absolutely sure I have a working gold card (2 infact!)
I can connect my device in ADB to find the serial, and "adb devices" displays my device.
I can run the reboot command from adb and it works, but pushing will always give a 0 bytes pushed result.
I really want to root my phone and i will be devloping on it at some point (already made my hello world app!) Has anyone got any ideas? Beer money via paypal is the only reward I can offer for any assistance, cheers! ;D
Try this.. Use the softroot (in another thread inhere) use the soft root to install rom manager and download the recovery file.. try rebooting to recovery mode and flash a rooted rom.. dunno if it will work but give it a try..
Sent from my Legend using XDA App
Hi I've been reading these forums for ages but only just signed up, I'm looking to root my hero (surprise) and complete newb.
Basically current build/software is 3.32.405.1 so 2.1, followed the rooting instructions exactly, then rebooted holding home and power on buttons but it just boots straight into a red triangle with exclamation mark in the middle of it, I can hold power and volume up to get a small menu with apply sdcard: update but tried that after getting frustrated and that said that the file wasn't verified.
how do I get the normal recovery screen because already have a villainrom on the sdcard.
You need to do the root process to get to the care bear, then flash villainrom on the care bear, before rebooting.
That will get you sorted
Well I rooted using universal androot, then used the teminal to input the su (press enter)
flash_image recovery /sdcard/recovery.img (press enter) part of instructions but at no point do I see the care bear :S
I have the same problem as Ejen. The phone is root i have superuser permission i do titanium backup .I put RA-hero-v1.7.0.1 with Better Terminal Emulator. When I turn off phone and press Home&Power I get a picture phone with a triangle. Does anyone have an idea how to solve this?
Yes, this is because stock rom automatically reflashes recovery with the stock one each shutdown iirc.
You need to stop this happening, but I can't remember the command. When you have root using universal androot though, you can stop it happening.
Or maybe it's too early for me. Wait till I've had a coffee or two and I'll revisit this...
Perhaps you can edit /system/etc/install-recovery.sh. A quick look trough /system didn't find anything like a shutdown script so perhaps this file is run by the android environment.
I had this same issue the other night, been searching for a fix, hopefully one appears here soon, thanks Pulser_g2, i was hoping to install your 1.5 Rom
Bloke
Ah seems I'm not the only one well at least I wasn't just being silly then, well tried it multiple times but still seem to have no success even tried the unlockr websites method with no success either.
If anyone knows thanks
Right... Are you on 1.5 or 2.1 just now?
Could someone (preferably the most tech savvy here) if you're on 2.1, try http://forum.xda-developers.com/showthread.php?t=726118 and see if that works.
I'm trying to work out what's going on here...
P
I'm 2.1 and had been using your other guide to root my phone but embarrasingly got stuck at stage 2 whilst trying to set up ADB (my knowledge of cmd is very limited to the point I only know the command tree ), saw the guide on XDA and thought that looks really simple so tried that instead, then tried unlockr method when XDA's didn't work now given up and asked for help
Ejen said:
I'm 2.1 and had been using your other guide to root my phone but embarrasingly got stuck at stage 2 whilst trying to set up ADB (my knowledge of cmd is very limited to the point I only know the command tree ), saw the guide on XDA and thought that looks really simple so tried that instead, then tried unlockr method when XDA's didn't work now given up and asked for help
Click to expand...
Click to collapse
Ok,... So how far did you get on setting up adb http://www.villainrom.co.uk/forum/s...de-Setting-up-ADB-and-how-to-use-it.-(Windows) ?
I had done up to part 4 using ADB, opened up cmd prompt I couldn't seem to push stuff to the SD card and was unsure what I did wrong.
When checking the USB works part 3, I used the link chose part 2, HTC sync users > ADB I couldn't find android_winusb when updating the driver software. I'm probably missing something or being silly now but I don't know
Ejen said:
I had done up to part 4 using ADB, opened up cmd prompt I couldn't seem to push stuff to the SD card and was unsure what I did wrong.
When checking the USB works part 3, I used the link chose part 2, HTC sync users > ADB I couldn't find android_winusb when updating the driver software. I'm probably missing something or being silly now but I don't know
Click to expand...
Click to collapse
Type adb devices, and if you see your phone's serial number, then you don't need to worry about drivers. Remember to "cd" into the correct folder first.
I'll try that but CD did nothing I'm running windows 7 and it sticks on C:\users\username Can't go back
Ejen said:
I'll try that but CD did nothing I'm running windows 7 and it sticks on C:\users\username Can't go back
Click to expand...
Click to collapse
Where have you downloaded your Android SDK too?
for example > "cd c:\SDK\tools"
pulser_g2 said:
Right... Are you on 1.5 or 2.1 just now?
Could someone (preferably the most tech savvy here) if you're on 2.1, try VillainROM Roots 2.1 and see if that works.
I'm trying to work out what's going on here...
P
Click to expand...
Click to collapse
I guess that is already on the phone RA-hero-v1.7.0.1 as you said stock rom automatically reflashes recovery. I suppose that the method VillainROM Roots 2.1contains RA-hero-v1.6.2.img. What will then happen with recovery if i try to do again root with VillainROM Roots 2.1?
When you try that method, you get the phone booted into patched recovery, at which point you take a nandroid backup and flash a custom ROM.
this prevents the recovery being lost. Just try it
I'm not at home and can not install ADB and run runindos.bat. I have on SD card recovery and FroydVillain 1.5. That's why I tried this method.Next week I'll be home and if someone does not fix the problem i will try the method you suggested me.
Can I try to put again recovery with Better Terminal Emulator, maybe recovery was corrupted ....
i went through the same thing!!
Ejen said:
Hi I've been reading these forums for ages but only just signed up, I'm looking to root my hero (surprise) and complete newb.
Basically current build/software is 3.32.405.1 so 2.1, followed the rooting instructions exactly, then rebooted holding home and power on buttons but it just boots straight into a red triangle with exclamation mark in the middle of it, I can hold power and volume up to get a small menu with apply sdcard: update but tried that after getting frustrated and that said that the file wasn't verified.
how do I get the normal recovery screen because already have a villainrom on the sdcard.
Click to expand...
Click to collapse
helloo!! i apologise if i am interupting or butting in whilst your in the middle of other solutions... i just saw the title and jump right in. i went through the exact same thing just 2 weeks ago!! unfortunately for me there was no successful forums or websites at the time... it sounded like a simple problem, with no simple solution.
this may not be what you where looking for, but its a very quick easy method that definately worth a try.
so... am i right in saying you have the official OTA HTC android 2.1 update?? and you now want to get this rooted?? and have you also tried rooting using the two common methods, the "one click root" and the "unrevoked" one? thats wat i did and i kept being stuck at the same red triangle and exclamation mark.
those methods (and countless others) will not work with the official htc hero android 2.1. (as far as i know) what you will need to do is downgrade the phones software. check htc's website and look for the older RUU and using the computer get your hero back to android 1.5. (under no circumstance should you upgrade your 1.5 android to the 2.1 android via HTC's OTA update... its only going the remove the root access!!!! - always reject it)
then continue to root as per the numerous rooting guides. done? now, obviously you will want to flash an android 2.1 rom. if you want to keep to htc's original 2.1, you can search for this in the forums under 'development'. or go ahead and flash the custom roms (villianrom).
thats exactly how i did it. im not entirely sure if this is the info you are after... but reply back and ill be happy to answer any query - big or small. (i should warn you, im no expert - but this forum is filled with the earths most powerful brains - u should have an answer in no time!!)
I have an HTC Hero. I ran the simple root method and got Carebare response.
I too have read numerous threads in the forum here and elsewhere but can't seem to get past the USB section.
adb says no device
I can use HTC Sync to sync data to the phone.
The SDK is installed and I have previously used it to capture screen shots of my device.
If I try to run one of the RUU executables, it fails with a [114: USB Error] (number may be wrong but the message is right.
I can mount the SD card and copy files to/from it.
I am running Windows 7 Home Premium 64bit on a Quad Core AMD CPU.
If I do the Home/Power thing, I get the same red triangle as described in the 1st message of this thread.
Fwiw, I have successfully and repeated loaded ROM's on my previous phone (HTC S621) so I am not a complete newb (but i am newb to Android).
What am I missing? This shouldn't be this hard (at least from what I've seen posted anyway)
DISCLAIMER: I NOR ANY ONE ELSE ASSUMES RESPONSIBILITY IF YOU BREAK YOUR DEVICE.
THIS DID WORK FOR MY STRAITTALK XT555C USING .67D FIRMWARE. ALWAYS MAKE A BACKUP!
update
I am rooted thanks to rootdefyxt320.... its a funny process as it seems i got an asian version of the
app but it worked flawlessly. after poking around to guess the right button to click the device restarted and (pc-win7)
showed asian language and big bold letters showed xt555c. clicked green buttonto "close" and unplugged device. i got a version
of what looked like su.apk in an asian language. then get supersu from market to "replace su app" (in super su settings)
reboot asian su gone and now need to move supersu to system app then all good!
status of su proven by:
terminal emulator ($ + SU = #)
for safety reasons you can know all went well by typing:
$ su
# reboot
if the device reboots then you are good as power off is not a su command but reboot option is
titanium backup "status on splash screen confirmed su access" "removed facebook app" can some one upload the
non-updated face book app so i can put it back and get a full blown firmware back up. as i had to confirm this working
the quickes thing i could think of to verify was dumping facebook app
busy box "confirmed su is installed and busy box did update sucessfully"
supersu "kept disappearing, used link2sd to move superuser to system fixed this" During this time i still had su access
but with the "lack" of supersu it would not prompt me for su access but would grant access automatically.
dont know why but supersu would not show in titanium untill i did this.
I just have to say with so many things going on in life breaking my little phone from its cage has made me smile!
thanks again rootdefyxt320!
If this has helped you please scroll down and hit the "thanks" button for user rootdefyxt320 as i did. wish they had a thanks a million button
ORIGINAL POST:
PREVIOUSE POST AND POSSIBLY DATED INFO FOLLOWS:
First off I am requesting any developers help to figure this out, I want to thank in advance the
awesome devs and community of xda as im sure there is some one out there way more
knowledgeable than I willing to help. Simply put please educate me as im willing to learn what it
takes to complete this task sucessfully.
Hello, today I have a whole slew of questions about the Motorola Defy XT, XT555c to be exact.
It seems as though there are many different defy's out there and this on has the least amound
of development. I am attempting to get all the info in to one place as searching for this device
seems a bit messy. I will update this thread as info is found\refound and brought to my attention.
Enough of the mumbo jumbo, off to the good stuff...
Chances are if you arte reading this you already know that all the "normal" methods of rooting
android (z4root, super1click, Framaroot, republic wirless .apk root) does not work for this device with 2.3.7
as all known exploits had been "fixed" by motorola. This is the first device of about 20 android
devices that I havent been able to research and root! Im creating this post in hopes to grab the
attention of any developer willing to help.
My PC configurations:
windows 7 x64 & x86, moto drivers
ubuntu 12.04 x86 installed to and running from 16gb usb thumb drive, moto rules created a.k.a. drivers for linux
adb installed on all of the above systems
Device specifics:
model xt555c
android ver. 2.3.7
baseband ver. pcr
kernel ver. Apps_2.6.38.6-perf
build no. 1_67d_1014
NOTES:
*ubuntu stick was created soley for the root procetures for the xt555c
*I preferr to use ubuntu but if nesasary I have windows at my disposal
*both win and ubuntu speak to the device flawlessly (ADB)
*used adm to grab logcat @ boot (see attached)
*need to grab full backup of system software because you know how this sort of
thing goes. Any suggestions?
*this particular defy in question was apparently manufactured/released in 2012
*This particular defy XT555C is also called other model numbers on various sites.
It has become increasingly difficult to find out witch defy I hold in my hand due to
conflicting specs\models on various other sites. some are dualband and others not.
some do not have a front camera, some state 800mhz processor while others state 1ghz
but all are called "defy XT"
Questions I have currently are:
Is this device downgradeable? possible solution (use google translate) www.android-hilfe.de/2729429-post10.html
Are the firmwares from any other defys capable of running on this device?
http://forum.xda-developers.com/showthread.php?t=1827338
http://forum.xda-developers.com/showthread.php?t=1542956
**Zeroemd: "Also the only difference between xt555c and xt535 is the region and the CDMA for US and GSM for Asia"
If any one can confirm this then it may be possible to use other firmwares from other models of defy and simply
have issues to hammer out with the "modem/radio" . I remember from the early cyanogen days and the MT3G you could
flash any number of builds and combine those builds with different radio versions and get insanely different results but as
i remember it if you ended up with the wrong radio all else would work you simply would have bad/low cellular signal, lacking
3g/data or no signal at all.
Here is the terminal output that I get when attemting any thing that requires su\root:
[email protected]:~$ adb devices
List of devices attached
TBEN1238500049 device
[email protected]:~$ sudo -s
[sudo] password for reemo:
bash: PATH=${/home/reemo/Desktop/android-sdk-linux/tools}:~/android-sdk-linux/tools: bad substitution
bash: PATH=${/home/reemo/Desktop/android-sdk-linux/tools}:~/android-sdk-linux/platform-tools: bad substitution
[email protected]:~# adb shell
$ adb reboot
adb: permission denied
$
The info found at the following link has led me to feel the need to investigate the boot
process to resolve rooting method hints the boot-logcat
http://www.apriorit.com/our-company/dev-blog/255-android-rooting
The logcat from ADM taken from "phone off" to "fully booted @ lock screen" has been
attached along with screen shots of my device info
I am aware of the "bad substitution" error. due to laziness and sligh bad config Ive just been "cd"ing to the directory
more info to thumb through and organize at a later date
http://forum.xda-developers.com/wiki/Motorola_Defy#Rooting_DEFY.2B_Bootloader_v7
I have included pictures of my lense as I am colorblind, red green colorblind to be exact. ive showed the pictures on
line in hopes some one could tell me what color mine is... every one seems to tell me the lense is black. if any one
wants to look at these and tell me it would be greatly appreciated.
Good Luck
I wish you good luck and thank you for trying to give this great little phone some well deserved attention.
VyKng said:
I wish you good luck and thank you for trying to give this great little phone some well deserved attention.
Click to expand...
Click to collapse
I'm awaiting reply from one of the defy devs in hopes to get some one to help me make light of things. I was
reading that apparently gingerbreak has been patched on a lot of devices as it its a security vulnerability. There
are other people/devices with our dreaded "gingerbreak proof" issue. Either I/we figure it out, some one hears
our cries for help or its exploited for another device and ported to ours using other exploits not found to date.
Wish I had better news.
Developers please tell me if there its more info needed to start this rooting process. I'm sure finding testers
won't be an issue a time goes by people will lay there defys to the side along with Motorola for devices we can
do what we want with. Thanks in advance.
reemobeens19 said:
I'm awaiting reply from one of the defy devs in hopes to get some one to help me make light of things. I was reading that apparently gingerbreak has been patched on a lot of devices as it its a security vulnerability. There are other people/devices with our dreaded "gingerbreak proof" issue. Either I/we figure it out, some one hears our cries for help or its exploited for another device and ported to ours using other exploits not found to date. Wish I had better news.
Developers please tell me if there its more info needed to start this rooting process. I'm sure finding testers won't be an issue a time goes by people will lay there defys to the side along with Motorola for devices we can do what we want with. Thanks in advance.
Click to expand...
Click to collapse
I have a green lens defy but I wish you get info you need as soon as possible. Have you tried Framaroot?
EDIT:Check This.it is from this thread, it may help you.
Zeroemd said:
I have a green lens defy but I wish you get info you need as soon as possible. Have you tried Framaroot?
Click to expand...
Click to collapse
I'm partially color blind, red green to be exact so i have to find alternate ways
to find out which lense i have. as for framroot i jumped up and tried it and in seconds i get an error#5.
dev for that package of exploits states
"What means error# on result ?
All errors less or equal to 9 mean your device is not vulnerable"
reemobeens19 said:
I'm partially color blind, red green to be exact so i have to find alternate ways
to find out which lense i have. as for framroot i jumped up and tried it and in seconds i get an error#5.
dev for that package of exploits states
"What means error# on result ?
All errors less or equal to 9 mean your device is not vulnerable"
Click to expand...
Click to collapse
I suggested it because it made rooting easier on complicated devices, (like a Droid pro with an Argentinian SBF, which requires ubuntu to root.)
Check the framaroot post maybe you will find something or try to contact its creator.
If i find anything I will PM you.
Zeroemd said:
I suggested it because it made rooting easier on complicated devices, (like a Droid pro with an Argentinian SBF, which requires ubuntu to root.)
Check the framaroot post maybe you will find something or try to contact its creator.
If i find anything I will PM you.
Click to expand...
Click to collapse
stubborn little phone, thanks for the tip though
@reemobeens19 Please do the Canadian XT615 Root Method to root your phone.
http://forum.xda-developers.com/showpost.php?p=44058727&postcount=92
If you want the English version of the Canadian XT615 root program, refer to this post:
http://forum.xda-developers.com/showpost.php?p=45212970&postcount=102
The Canadian XT615 Root Program
@reemobeens19 This Canadian XT615 Root program can root all Motorola Android Phones on Android 2.3.7 and it will install a Chinese SuperUser on your device.
How to check for root after using the root program. Please use cmd to type in these commands
Code:
adb shell
Code:
su
and it should give you a # sign in cmd.
After that you can update to another SuperUser program from the Play Store such as Superuser by ChainsDD, SuperSU by Chainfire or SuperUser by koush.
@reemobeens19 Does your Defy XT have fastboot mode? I'm going to help you to port CWM.
You can test it by typing this command in cmd
Code:
adb reboot bootloader
If your phone reboots normally means your phone doesn't have fastboot mode . If your phone gets stuck on a screen with the M logo then you have fastboot mode
rootdefyxt320 said:
@reemobeens19 Does your Defy XT have fastboot mode? I'm going to help you to port CWM.
You can test it by typing this command in cmd
Code:
adb reboot bootloader
If your phone reboots normally means your phone doesn't have fastboot mode . If your phone gets stuck on a screen with the M logo then you have fastboot mode
Click to expand...
Click to collapse
i do not have fast boot mode. got normal boot using the commands supplied
pwr+vol up gives me:
MBM Flash-mode.
Tinboost+ EVDO TRACFONE
version: 01.08
Bootloader USB Init SECURE BOOT ENABLED
bootloader right, not fastboot?
how can i obtain a full system back up including recovery and boot loader?
i would like to do this from the command as im using ubuntu for most of my work.
once i have the back up how then do i restore it back to the device in case of failure?
once again thank you very much for the well needed assistance
reemobeens19 said:
i do not have fast boot mode. got normal boot using the commands supplied
pwr+vol up gives me:
MBM Flash-mode.
Tinboost+ EVDO TRACFONE
version: 01.08
Bootloader USB Init SECURE BOOT ENABLED
bootloader right, not fastboot?
how can i obtain a full system back up including recovery and boot loader?
i would like to do this from the command as im using ubuntu for most of my work.
once i have the back up how then do i restore it back to the device in case of failure?
once again thank you very much for the well needed assistance
Click to expand...
Click to collapse
Yes, that is the bootloader. Use this tool to make a nandroid backup and restore nandroid backup http://forum.xda-developers.com/showthread.php?p=25328650
Okay, I need help unlocking the bootloader. I don't really understand the instructions on the Motorola website. Thx!
Sent from my SCH-S720C using Tapatalk 2
Nick_73 said:
Okay, I need help unlocking the bootloader. I don't really understand the instructions on the Motorola website. Thx!
Sent from my SCH-S720C using Tapatalk 2
Click to expand...
Click to collapse
Motorola only supports a few devices and the odds that this one will ever be supported
are slim as it is not a "main stream" device. One thing i hate messing with are
bootloaders. Im currenty awaiting proven methods my self before attempting to
heavily modify this device. ive been playing a lot with linux and have "broken" my pc
numerous times in the past few weeks trying to learn more about under the hood unix.
one thing i cant seem to "fix" rather than reinstall is the bootloader when its broken im
hoping it will help me better understand what is going on in side this little android. if there are proven methods
im willing to try them as i took the plunge and rooted. does any one have any advice for this?
@reemobeens19 Can you please provide me your build.prop and flex.prop please so I can obtain the original firmware for you? Thanks
I just bought a xt555c from straight talk and tried both the Asian and English programs posted on this thread but neither of them worked for me. At the risk of sounding dumb did I miss something. I turned on the phone, enabled USB debugging and clicked the green button. It recognized my device as an xt555c, said rooting. Then my phone rebooted and the program said try again... Can anyone tell me where I went wrong? Thanks in advance.
nerdmonger said:
I just bought a xt555c from straight talk and tried both the Asian and English programs posted on this thread but neither of them worked for me. At the risk of sounding dumb did I miss something. I turned on the phone, enabled USB debugging and clicked the green button. It recognized my device as an xt555c, said rooting. Then my phone rebooted and the program said try again... Can anyone tell me where I went wrong? Thanks in advance.
Click to expand...
Click to collapse
Retry the process again.
rootdefyxt320 said:
Retry the process again.
Click to expand...
Click to collapse
I've tried over a dozen times to no avail. My front camera has a
red lense if that makes a difference
nerdmonger said:
I've tried over a dozen times to no avail. My front camera has a
red lense if that makes a difference
Click to expand...
Click to collapse
Ok, first uninstall all Motorola Drivers the reinstall them
Download the zip file here: http://d-h.st/33x
Instructions:
1. Extract the zip file. I have included both 32 bit and 64 bit drivers.
2. Then uninstall all Motorola Drivers and reinstall them.
3. Then uninstall the VRoot program and reinstall the VRoot program.
4. Then retry the VRoot program and tell me your outcome.
Press the thanks button if I helped you instead of saying thanks