Database Users

impossible to root HELP ME PLEASE

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.

some rooting help

im following the walkthrough from stock 1.5 to 2.1 rooted and i just did step 1 where i load the PB00IMG.zip. when i turned my phone back on it asked me to login to gmail and all that stuff and now when i check the phone info it says i'm running 2.1 already even though i have not gone through the other steps? i assume i still need to? and am i supposed to be on 2.1 already after step 1? i was just under the impression that i would have 2.1 still the very end?

i also saw that there was a new thread that had a new eris official .zip should i use that one? or the one mentioned in the walthrough?

yes you should be on 2.1 after the first step but you do need to continue on with the other steps. you can use erisofficial.zip or the one in the post or any of the roms that have now been made for the rooted eris. there are quite a few choices in roms now so you can look through them and see which one appeals most to you....

Ok. I am having trouble with step 3... not sure how to get the common prompt to go to the sdk tools folder so I can start inputing the lines? I'm new so any help would be great. also... what is going to be the difference between the 2.1 I have running now and the one that would be flashed in the last step? I have a Droid and am doing this for my wife. is step 3 pretty much like making a nandroid backup?

Go to My Computer and ( C: ). Find your AndroidSDK folder and keep going until you are in your tools folder. Right click on any item and go to Properties. Under your Command Prompt type cd (followed by a space and type whatever it says next to Location in Properties). Hope this helps.
For me, in my cmd I type: cd C:\AndroidSDK\android-sdk-windows\tools
After you hit enter, it should have C:\AndroidSDK\android-sdk-windows\tools (or whatever your path is) followed by a cursor. Now you can type your commands.

Ok Ill try that when I get back home. just curious though... what would happen if I jusT stopped after step 1 with the 2.1 that's on the phone now?

I left it right there for about a week. I didn't have time to finish the rest. Nothing bad will happen, you just won't be able to flash custom ROMs or other root-related things. You still have 2.1 and you can download apps that you couldn't with 1.5. If you're content with that, you may be better off just doing the OTA leak instead.

The roms have fixed alot of the glitches in the original 2.1 root that you have on there now such as having to log in to gmail after each reboot.

i get to the last part of running the commands and the i get errors saying out of memory???

it ran through the errors a bunch and the very end it says error writing recovery: no space left on device...? after doing step 1 i used mybackup pro to re load all my wifes texts... all 8000 of them... could that be the reason?

ok i ran through the steps and didnt get an error this time... but how do i know if it worked?

yamaha83 said:
ok i ran through the steps and didnt get an error this time... but how do i know if it worked?
Click to expand...
Click to collapse
power down your device, then while pressing the end/power button and volume up at the same time and you should come into the recovery menu. From there you can flash updates, roms etc. you can back up your current config all sorts of things.

So I have not been able to check if I flashed the recovery correctly yet cuz my wife had to go out of town. but now she can't send pic messages. is this one of the fixes in some of the roms? Also now that I have root I should be able to back up all her data and apps to restore them onto a new Rom right? Just want to make sure its the same as my Droid...

I'm in the from stock 1.5 to rooted 2.1 thread and everytime I try the command:
adb shell flash_image recovery /sdcard/recovery.img
I get:
flash_image: permission denied
Any help is appreciated as I'm coming form the vogue android forum and this is getting a little foreign to me
EDIT: I'm assuming i'm retarded and forgot to run the command before it.. I just ran through it again with nothing denied

Up and running good!! Thanks for the help everyone!
Anyone have any suggestions on a good stable Rom??

I've been using Jamezelle's Sense-able 2.0. I've tried the others, this one is most stable in my opinion. I'm waiting for the EvilEris 1.2 to come out to try that.

Trying to root - problems [SOLVED]

Hey guys.
I've been attempting this all morning and so far I've had no luck. I have a VodafoneAU Legend which I updated to the official 2.2 yesterday. But now I want to try root.
I've been trying to follow the HBOOT 1.01 guide but there's a few problems. First, I cannot connect to the phone with adb unless it's in htc sync mode. No other mode will work. So when it's time to copy testimage.zip to the card I have to change from sync mode to disk mode, whereby adb loses it's connection. What do I do about this? Is it a driver problem (in Win7 here) or something else?
Thanks,
Dave.

Ok, the first problem were drivers.
Now I can't finish the second guide. When I try using clockwork to install the firmware.zip, the phone just boots to the red triangle. What do I have to do?
Dave.

So I pressed the up button/power combo at the red triangle and get the Android system recovery. Selecting "apply update.zip" says it can't verify. What do I do? Is this guide for my phone or do I need to follow something else?

I don't understand this guys. Anyone help? I'm thinking since this is a step to root the phone, I'm not actually rooted yet so I can't use the clockworkmod? Then what is the guide for? The guides at unlockr don't mention what firmware/hboot they work for so I'm not keen to try them yet.

Read the guide on fake flash. You need the recovery file named "update.zip" in the root of your sd to proceed..
Sent from my Legend using XDA App

whitetigerdk said:
Read the guide on fake flash. You need the recovery file named "update.zip" in the root of your sd to proceed..
Sent from my Legend using XDA App
Click to expand...
Click to collapse
But isn't that what Rom Manager does? Download the update.zip then run it? Man this is getting even harder to understand.
Edit: And this is left out of the HBOOT 1.01 guide because.....????? When I work this out I'll write a PROPPER guide, lol.

Just checked and update.zip is on the card.
So which part of the guide am I getting wrong?

Decided to reinstall phone with the official froyo release and am now ready to try this again. Is there anyone that will walk me through the process? I will write a complete guide if the "gotchas" are still there.

i feel for you ... hope you get it fixed... thats one of the reason i havent dared messing with the phone because i've seen a few post like yours where something didnt go quite as described... for whatever reason... and im sure the answer is out there but just not within the guide instructions... i guess there is no way to gather all gotchas because there are so many environment variables...
good luck
and please share your technique

Just saw gobczak's thread in the developer forum having similar troubles with Vodafone UK phone, getting the red triangle at reboot. I'll keep an eye on his thread and see how he goes with it.

Did you run the stage1 and stage2 bats while in recovery?

dezzadk said:
Did you run the stage1 and stage2 bats while in recovery?
Click to expand...
Click to collapse
No because the guide didn't say to.
The thing is it seems I'm only stuck on the part where the firmware.zip file has to be flashed. The guide says to use clockworkmod for this. But when I try installing the clockworkmod recovery it gives some file verification error. Isn't there ways to do this via the pc, either through those batch files, adb etc? Or will that fake-flash update.zip file work?

jabbado said:
No because the guide didn't say to.
Click to expand...
Click to collapse
As I just posted on the other forum, I think you need to skip that step in guide 2 and go straight onto guide 3 after you have flashed the LEGEIMG.zip, rebooted, and then removed LEGEIMG.zip from the SD card.

Guys I've got to the point of downgrading to 1.31. But when I run the first batch file it just hangs at the "Writing zip" part, with the htc logo on the screen. Is there any way to fix this?

Can someone please explain this part of the guide:
Phone will reboot and find LEGEIMG.zip on your sdcard, copy it into RAM and check it. If you get CID error at this point, then you don't have goldcard.
Click to expand...
Click to collapse
Ok, so I don't get an error. I get nothing. The phone just boots to the fastboot screen. If I press the power button it goes to the hboot screen and I can see the messages of loading LEGEIMG.zip. But the guide doesn't say to press anything.
So should I or shouldn't I press the power button? Also, if I try making the goldcard again, at which point in the guide do I start from again? The entire process or just copying LEGEIMG.zip to card then rebooting phone? I mean, will all the other things like flashing misc1-2.img still be there?

Guys I finally got this working.
The first problem was with the goldcards. For whatever reason formatting them with the win7 format tool just wouldn't work. I had to use the command-line format tool, setting the block size etc manually.
The second problem was the unnecessary steps in the guide. A few people helped me out with this (namely blackbart at the Aus Whirlpool forum), but basically in the second step you can stop after flashing the LEGEIMG.zip. The updating froyo part isn't needed - for my phone anyway.
Then when running the batch files in the third part, for whatever reason the first batch would keep hanging at 'writing zip...' and I needed to remove the battery to unfreeze the phone. flannigan, also from the Aus Whirlpool forums suggested to just go on to the second batch file. This worked!
So my Legend is now finally a true Legend
Anyway, thanks for the help everyone - couldn't have done this by myself.
Dave

Great news, I think we need a new guide focused on rooting for HBOOT 1.01 / Stock Froyo to clear up the inconsistencies in the existing one. It's a minefield for a noob (or a rite of passage!), a revised guide will certainly save a lot of time and frustration for those taking this road in the future.
Sent from my HTC Legend using XDA App

EpicSauce said:
Great news, I think we need a new guide focused on rooting for HBOOT 1.01 to clear up the inconsistencies in the existing one. It's a minefield for a noob (or a rite of passage!), a revised guide will certainly save a lot of time and frustration for those taking this road in the future.
Click to expand...
Click to collapse
I'll write one if ya's want. I wanted to include little tidbits like downloading the apps required (visionary, rom manager etc) from the market then backing them up to the card with Astro so if it goes all wrong and you have to start again, you can just install them all from the card Also on using adb to push the files (roms, img's etc) when the guides say "copy this blah blah". Much quicker than changing to disk mode and back. Sound good?

Sounds good! Happy to help and add my 20c worth along the way. The existing guide has got the meaty bits, a new guide would cull the stuff not relevant, help fill in the gaps and alert to the pitfalls we've fallen into.

jabbado said:
I'll write one if ya's want. I wanted to include little tidbits like downloading the apps required (visionary, rom manager etc) from the market then backing them up to the card with Astro so if it goes all wrong and you have to start again, you can just install them all from the card Also on using adb to push the files (roms, img's etc) when the guides say "copy this blah blah". Much quicker than changing to disk mode and back. Sound good?
Click to expand...
Click to collapse
I agree... i've done my reading since june of last year but then didnt check for another 4 months... and so many how to's pop up with various ways of doing it depeding on the situation... a lot of those howtos were consolidated howtos which sometimes make intermediate steps unenecessary (may be in some cases causes more head aches since it didnt take into considerations on newer version of hboots...etc)... an updated how to will be much appreciated...
And you're right the most important pre requirement is to have a safety net ... so starting with how to create a back up in case you screw it up is a must!
but im glad it worked out for you!

[Q] Permaroot process failing, says "unknown user root" Plz help =[

First of all, I'm not going to say I'm a pro at this. I am CERTAINLY not a total n00b, but I have only worked with Leo's and have done a thousand Galaxy @ and EVO Roots/rom installs. This, for some reason, is stumping me...
I am following THIS guide (http://forum.xda-developers.com/showthread.php?t=858996) to gain permaroot on my device, and I have now run into a strange roadblock. I get to step 7:
"7. Open terminal emulator on your device, type "su", and hit enter to gain root privileges."
And terminal gives the response "Unknown user root". I should inform whoever attempts to help, I have already gone through 90% of this before failing initially,(all the way to the "./gfree -f" command at the end, where it threw about three errors at me =/ )... I reverted every change I made on my computer, except for the properly installed ADB drivers, and I obviously kept all my downloads. Phone got an SD card format, and a master reset. IDK what I'm missing, so can anyone pleeeeaassse help?? I donate accordingly =D
Thanks for ur time,
Clark

you got your phone in the last month? what are your stats in "about phone" like android version, baseband version, etc

Yeaaa, I purchased it within a week. But as far as firmware is concerned, yes its 2.2.1... checked vitals like that, as the tutorial said, before I started. I am very cautious as to read not only the tutorial to the "t", but also to search everywhere for a solution before asking.. I just suck today, that's all [=
Baseband : 12.28b.60140eu_26.03.02.26_m
Thanks again..
Sent from my HTC Glacier using XDA App

Allllriiight! Lots of help so far!!
Don't be shy, folks...

[REF][ROOT][SOLVED] Motorola Defy XT555C on 2.3.7 build 67d

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