Question to those who have updating their Dream from Rogers, was it at all slow or where their noticeable improvements?
I have one at my disposal but running stock OS (1.5/1.6 i assume). Anyone have a nice and easy to follow tutorial to update this phone without hassles? Also does updating android OS require rooting the device?
Thanks in advance.
Bloodyskullz said:
Question to those who have updating their Dream from Rogers, was it at all slow or where their noticeable improvements?
I have one at my disposal but running stock OS (1.5/1.6 i assume). Anyone have a nice and easy to follow tutorial to update this phone without hassles? Also does updating android OS require rooting the device?
Thanks in advance.
Click to expand...
Click to collapse
try this:
http://theunlockr.com/category/howto/android_how_tos/htc-g1-dream-how-tos/
Follow instructions. This seems to me to be the easiest guide. Be careful of the Rogers/T-Mobile thing. Seems there are different radio's and such. I don't know anything about Rogers. As far as Roms, I use HTCclay's Superfly TCBY. Lot of memory left on phone. Just try a few to see which you like. Good Luck.
By the way, you do have to be rooted. The guide will walk you through it.
crz6662 said:
try this:
http://theunlockr.com/category/howto/android_how_tos/htc-g1-dream-how-tos/
Follow instructions. This seems to me to be the easiest guide. Be careful of the Rogers/T-Mobile thing. Seems there are different radio's and such. I don't know anything about Rogers. As far as Roms, I use HTCclay's Superfly TCBY. Lot of memory left on phone. Just try a few to see which you like. Good Luck.
By the way, you do have to be rooted. The guide will walk you through it.
Click to expand...
Click to collapse
I would say to try the ROM in my sig (the stock ROM)
works for g1 and 32B Magic
he is going to need the EBI1 kernel to go with the rom.
Ok I am reviving this thread because I want to make sure I am following the right steps in doing so. Don't want to mess this up.
Successfully rooted the phone following video I found in the second post of this thread. Can't link you to it because I am still a new member =S! I checked the radio version of the phone and it is 3.22.20.17. Which ROM is recommended?As I said, I just want to get rid of this terrible stock rom from rogers and put froyo (which in turn also allows me to get touch screen keyboard activated) on here.
Thanks in advance.
With that radio you will need to flash ebi1 kernels after you flash the roms.
I completely forgot that Rogers blocked the virtual keyboard with their firmware. That's such bull****.
Sent from my HTC Hero using XDA App
asb123 said:
With that radio you will need to flash ebi1 kernels after you flash the roms.
Click to expand...
Click to collapse
Now you have more information in the link in your sig. Question: Can you re up the RS link you have there? Also, rooting the phone just means that you have the app called Superuser?
Now I get quite lost the moment you start explaining the options HTC Dream users have. Is there a recommended ROM to download for this phone considering its specs?
I completely forgot that Rogers blocked the virtual keyboard with their firmware. That's such bull****.
Click to expand...
Click to collapse
Yes it is sad that rogers has done this. Do whatever they can to screw the consumers over. Just found out it is 1.5.
Any help on this?
Ok still lost on trying to do this and want to follow the set up from cyanogen but its really complicated. I don't want to make a backup of contacts and stuff because it wasn't originally my phone.
Do I still need the amon_ra's recovery?
Bloodyskullz said:
Ok still lost on trying to do this and want to follow the set up from cyanogen but its really complicated. I don't want to make a backup of contacts and stuff because it wasn't originally my phone.
Do I still need the amon_ra's recovery?
Click to expand...
Click to collapse
Think of what you need to do:
1) Obtain root access so that you can flash a new recovery
2) Replace recovery so that you can flash new SPL
3) Flash new SPL so that you can be more compatible with roms / kernels
4) Flash a new rom (IE/ Cyanogenmod 6), and a compatible EBI1 kernel (for instance, Brian Crook's ones on the Cyanogenmod website)
Without getting into huge detail, you do it in this order to prevent your device from being unable to boot / recover.
You can flash the new RADIO and SPL from here: http://forum.xda-developers.com/showthread.php?goto=newpost&t=831139
Along with that, you use the appropriate supported +14MB EBI0 kernel.
More RAM is good
Well that makes sense.
Now I am following the Cyanogen wiki link (can't post there) and it says to launch flash rec but I can't understand from where I have to do this. Anyone care to help? And how does the Andriod SDK help?
Bloodyskullz said:
Well that makes sense.
Now I am following the Cyanogen wiki link (can't post there) and it says to launch flash rec but I can't understand from where I have to do this. Anyone care to help? And how does the Andriod SDK help?
Click to expand...
Click to collapse
Andriod sdk has the adb component needed to initiate commands to your device from your computer. then you need the android windows usb drivers.after installing sdk to see if you have connection with your device, open console on your computer start>run>type cmd and hit enter at the prompt type adb you should get several lines back kind of an options menu. at next prompt type adb devices. if your device is recognized you will get back:
device XXXXXXXX (this will be an actual number).
if you dont get any devices back with your phone attached to usb then you probably need the driver. just google it.
as for flashrec I dont believe I used this. I used exploid to gain root and install 1.33.2005 spl
Where do I get the android driver for windows (7 64bit specifically)? Adb command aint working in my cmd.
So what do I do about flashrec? Man updating this thing is driving me nuts. So many unexpected curves.
I also have Windows 7 64bit and I didn't need a driver it just works for me. Please tell us exactly what you are typing in and what output you are getting. You could also try the instruction to install the usb driver here:
http://developer.android.com/sdk/win-usb.html
What is your build number in settings? If it is 1.89.631.1 you are following the wrong guide. (see the top of that guide)
beav_35 said:
I also have Windows 7 64bit and I didn't need a driver it just works for me. Please tell us exactly what you are typing in and what output you are getting. You could also try the instruction to install the usb driver here:
http://developer.android.com/sdk/win-usb.html
What is your build number in settings? If it is 1.89.631.1 you are following the wrong guide. (see the top of that guide)
Click to expand...
Click to collapse
When I type in ADB command it just states that the command is not recognized (even when SDK is open).
Build number 1.85.631.5.
Now when I turn on phone it accepts it after I plug it into computer. I can mount sd card to copy files without issue.
Do I need another tutorial (preferably video since its easier for me but text is just fine)?
Bloodyskullz said:
When I type in ADB command it just states that the command is not recognized (even when SDK is open).
Click to expand...
Click to collapse
This doesn't mean that it can't find your phone, it means that it can't find the adb.exe.
Bloodyskullz said:
Build number 1.85.631.5.
Click to expand...
Click to collapse
That is a pre-911 build. Don't see too many of those any more. Rogers harassed everyone into updating.
Bloodyskullz said:
Now when I turn on phone it accepts it after I plug it into computer. I can mount sd card to copy files without issue.
Do I need another tutorial (preferably video since its easier for me but text is just fine)?
Click to expand...
Click to collapse
http://www.bleepingcomputer.com/tutorials/tutorial76.html
http://forum.xda-developers.com/showthread.php?t=502010
http://www.youtube.com/watch?v=Z3SpI7m7mFI
Does the zip file for the android SDK make a difference if I can't install it through the .exe? It keeps saying that it doesnt detect the Java SDK when I try to install.
Yes, you can use the .zip. Extract it, run setup.exe, install Platform-tools, cd to the platform-tools directory then you can use adb. Fastboot is in the tools directory. That was just changed in the 2.3 sdk update so I don't know if the guide has been updated yet.
beav_35 said:
Yes, you can use the .zip. Extract it, run setup.exe, install Platform-tools, cd to the platform-tools directory then you can use adb. Fastboot is in the tools directory. That was just changed in the 2.3 sdk update so I don't know if the guide has been updated yet.
Click to expand...
Click to collapse
The only .exe file in the zip is the SDK Manager which isnt exactly an install.
Related
MODS - can you please move this thread to the sapphire development forum and stick it? thanks
_______________________________________________________________
WE HAVE A ROOT NOW
haykuro said:
GOT ROOT?
http://droiddeveloper.com/hrbuilds/boot-new.img.zip
1. download this, extract boot-new.img to your computer.
2. place your device into bootloader mode (BACK+POWER, or VOLUME DOWN+POWER)
3. fastboot boot boot-new.img
4. wait for device to boot
5. adb push boot-new.img /sdcard/boot-new.img
6. adb shell flash_image boot /sdcard/boot-new.img
that's it!
your device now has root via adb shell.
i'm making the rooted recovery.img now for magic
Click to expand...
Click to collapse
It shouldn't be too hard.
Viper only needs to update his QMAT for creaatin goldcards for the Magic.
Then you have to flash the RC29 nbh with it.
If only adb successes connecting to the magic with rc29 of g1, you can start telnetd.
Then you should be able to. Flash a custom recovery image to flash a modified cupcake.
maxisma said:
It shouldn't be too hard.
Viper only needs to update his QMAT for creaatin goldcards for the Magic.
Then you have to flash the RC29 nbh with it.
If only adb successes connecting to the magic with rc29 of g1, you can start telnetd.
Then you should be able to. Flash a custom recovery image to flash a modified cupcake.
Click to expand...
Click to collapse
Well, you see what I meant? all the expert are here!
Let's wait for Viper comment and/or ideas.
But one problem:
I don't know if the RC29 is compatible with the Magic. Maybe someone has to create a custom .nbh with customized drivers for the magic.
And please. Don't call me an expert
It's only an idea I know linux commands etc. But i know only some basics of programming (e.g. to make a DOS caluclator in C++ )
maxisma said:
But one problem:
I don't know if the RC29 is compatible with the Magic. Maybe someone has to create a custom .nbh with customized drivers for the magic.
And please. Don't call me an expert
It's only an idea I know linux commands etc. But i know only some basics of programming (e.g. to make a DOS caluclator in C++ )
Click to expand...
Click to collapse
I am far from being an expert but even if RC29 works and the DREAM test recovery works (which I doubt), it has no support for virtual keyboard, so right after he gets root he will need a hacked rooted ROM for the Magic. Isn't it safe to assume that until someone cook a special ROM for the Magic he is stuck with a rooted but unusable device?
A much bigger problem: how in the hell can you telnet in the Magic with no keyboard? Or even get past the setup wizard? In other words, even with RC29 there'll be no way to get root or even use the phone. This is gonna be a hell of a lot more difficult than it was for the G1(and it was pretty damn difficult for that)
Well, I guess HTC created this function for their reasons (tests etc.) and now it's only a matter of time until someone will find the way to do it too.
that's the reasone I posted the request, I seen things in XDA that i could never believe before, let's hope it'll happen again ...
Will this post help? http://www.codeandroid.org/forum/?wpforumaction=viewtopic&t=9.2
The guy pk detailed a 27 step, step-by-step guide to unlock those HTC Dream outside UK and US. Hope it helps.
chuazy said:
Will this post help? http://www.codeandroid.org/forum/?wpforumaction=viewtopic&t=9.2
The guy pk detailed a 27 step, step-by-step guide to unlock those HTC Dream outside UK and US. Hope it helps.
Click to expand...
Click to collapse
"2) Launch Terminal Emulator
3) Enter the following:
cd /sys/class/mmc_host/mmc1:*"
Terminal Emulator doesn't seem to work without hardware keyboard(doesn't bring up vk for me on G1 using cupcake, I'd imagine it wouldn't work on magic either). Speaking of which, you guys with Magic's wouldn't be able to use any of the recovery mode options either since those all require a hw keyboard. So even if you got a JF build you wouldn't be able to flash it.
[email protected] said:
"2) Launch Terminal Emulator
3) Enter the following:
cd /sys/class/mmc_host/mmc1:*"
Terminal Emulator doesn't seem to work without hardware keyboard(doesn't bring up vk for me on G1 using cupcake, I'd imagine it wouldn't work on magic either). Speaking of which, you guys with Magic's wouldn't be able to use any of the recovery mode options either since those all require a hw keyboard. So even if you got a JF build you wouldn't be able to flash it.
Click to expand...
Click to collapse
But you do understand this function must be exist right? even if you can't find it now, HTC created it because they do use the recovery mode options for test and stuff...
avimak said:
But you do understand this function must be exist right? even if you can't find it now, HTC created it because they do use the recovery mode options for test and stuff...
Click to expand...
Click to collapse
Unless they do so using some external hardware which is fully possible...(think external keyboard, possibly through extUSB)
EDIT: btw: not trying to be an ass or say that you guys are screwed, just pointing out problems that will need to be solved in order for this to work.
[email protected] said:
Unless they do so using some external hardware which is fully possible...(think external keyboard, possibly through extUSB)
EDIT: btw: not trying to be an ass or say that you guys are screwed, just pointing out problems that will need to be solved in order for this to work.
Click to expand...
Click to collapse
Well, if external USB keyboard is the only thing it takes to root my device - I'll buy one, and root the rest of the Magic Israeli users for free
You don't need a virtual keyboard.
If USB-Connection an ADB wworks, you can get in the hidden root shell by using adb shell with the sdk-tools.
maxisma said:
You don't need a virtual keyboard.
If USB-Connection an ADB wworks, you can get in the hidden root shell by using adb shell with the sdk-tools.
Click to expand...
Click to collapse
I got it:
$ (I can write stuff)...
what next?
@avimak:
You mean, you've connected your magic with installed rc29?
maxisma said:
@avimak:
You mean, you've connected your magic with installed rc29?
Click to expand...
Click to collapse
No, I have the Magic (vodafone version) connected to my PC (win xp) and I can run ADB shell.
avimak said:
No, I have the Magic (vodafone version) connected to my PC (win xp) and I can run ADB shell.
Click to expand...
Click to collapse
ok.
But i meant someone has to test if a magic downgraded to rc29 (via goldcard) works.
Not the orig. Firmware.
maxisma said:
You don't need a virtual keyboard.
If USB-Connection an ADB wworks, you can get in the hidden root shell by using adb shell with the sdk-tools.
Click to expand...
Click to collapse
That's true for the terminal once the operating system has started, but they'll be hosed if they ever reach a boot looping problem or need to flash any ROM.
EDIT: Well not if they boot loop on the android screen, but if it loops on the SPL, then they're hosed.
[email protected] said:
That's true for the terminal once the operating system has started, but they'll be hosed if they ever reach a boot looping problem or need to flash any ROM.
EDIT: Well not if they boot loop on the android screen, but if it loops on the SPL, then they're hosed.
Click to expand...
Click to collapse
Can you please write it again in simple words?
It's a bit "pro only" talking. I got my Android yesterday...
maxisma said:
ok.
But i meant someone has to test if a magic downgraded to rc29 (via goldcard) works.
Not the orig. Firmware.
Click to expand...
Click to collapse
There is an option to go back to the orig. version after the downgrade? can I "dump" my OS somewhere and Install it again from SPL if it failed the rc29?
I'm coming from WM - I'm speaking they lang...
I'm so confused with all the lingo, root, kernel, s-off, ruu.
It just seems so overwelming. I don't think I want custom roms, all I want is att stuff removed, and faster data speeds.
And I'd like a way to return to stock in case I need to return the phone.
What phone are you coming from?
Read, as much as you can Google is your friend. Also if your having problems with goldcard checkout the unlockr. Setting up sdk isn't all that bad. This is coming from a renewed rookie with HTC phones because I've been away from adb for two years since I got rid of my dream and magic.
Coming from an iPhone. Don't understand anything about adb, sdk, terminal, etc.
Haven't tried making the gold card yet, ordered an sdcard but it hasn't come in yet.
harlenm said:
Coming from an iPhone. Don't understand anything about adb, sdk, terminal, etc.
Haven't tried making the gold card yet, ordered an sdcard but it hasn't come in yet.
Click to expand...
Click to collapse
Just use the card that came with the phone for goldcard. Use the goldcard helper tool from the market, get the mcc 2 number from the tool, go to the link provided, insert the mcc 2 number into the box on the page where it asks for it, get the file that was emailed to you, download the hack kit in the stickied thread of development, after installing Android sdk, unzip the hack kit using 7zip and only 7zip into the tools folder located in the Android folder. From that point you are ready to create a goldcard. That's where the sticky thread is your friend.
I know it sounds like a lot and in the end once you read up and understand how to use adb you'll understand its not that bad. Remember i am a rookie as well with most of this and would be glad to help as you progress
I think creating the gold card seems like the easy step, found a program that will do it and upload it to phone without needing the sdk.
My concern is all the other stuff, different kernels, different radios, etc. Downgrading the radio loses sound, so then you have to upgrade it again, but then the sound isn't as good, etc.
Then someone posted the stock kernel, compared to a telus kernel, what's the difference, and why put one over the other?
harlenm said:
I think creating the gold card seems like the easy step, found a program that will do it and upload it to phone without needing the sdk.
My concern is all the other stuff, different kernels, different radios, etc. Downgrading the radio loses sound, so then you have to upgrade it again, but then the sound isn't as good, etc.
Then someone posted the stock kernel, compared to a telus kernel, what's the difference, and why put one over the other?
Click to expand...
Click to collapse
The program doesn't work you need mcc2 number. The sound problem is a correlation of combining the dhd time with our kernel.
harlenm said:
Coming from an iPhone. Don't understand anything about adb, sdk, terminal, etc.
Haven't tried making the gold card yet, ordered an sdcard but it hasn't come in yet.
Click to expand...
Click to collapse
This will help with adb.Once you start tinkering you will figure it out quickly. As far as reading all the sound issues its really personal preference. You have to do these thing on your device and see if you have the same issue. Alot of the times you will find it that it comes down to different strokes for different folks. I myself have none of the issues that others have other than a weak external speaker. Reading is a great tool but dont get overwhelmed with the information your taking in because a good chunk will not pertain to you and your device. Just stick with the core information and what the op stated
The sound issue is the only thing that is not 100%, which will be fixed soon enough. We will get our own source soon enough, but for the time being dhd roms will do fine with either the stock or TELUS kernel. Personally the TELUS is better for fast data speeds.
harlenm said:
Coming from an iPhone. Don't understand anything about adb, sdk, terminal, etc.
Haven't tried making the gold card yet, ordered an sdcard but it hasn't come in yet.
Click to expand...
Click to collapse
Just my two cents and I hope you don't take offense to this, but you picked the wrong phone to jump into rooting and customizing since it's a new phone and the forums aren't yet up to speed on info. I would first read up in the Rodgers Magic 32A forum on how gold cards work, recovery, fastboot, adb, and custom roms work - these phones are broadly used and have been around for a while too.
I've read the instructions in the hack kit, and I still dont' get it.
I need to download the sdk, found that at http://developer.android.com/sdk/index.html
It says Terminal on the phone, so I need to download a terminal app from the market?
The commands look simple enough if I can figure out how to do them.
Edit, also need to download HTC sync?
read the guide Ive listed on how to install adb on the sdk and you will be fine.
harlenm said:
I've read the instructions in the hack kit, and I still dont' get it.
I need to download the sdk, found that at http://developer.android.com/sdk/index.html
It says Terminal on the phone, so I need to download a terminal app from the market?
The commands look simple enough if I can figure out how to do them.
Edit, also need to download HTC sync?
Click to expand...
Click to collapse
After the downgrade, terminal gets installed with the Rom. Always remember to enable debugging and charge only. The terminal part is the hardest. Also after receiving temproot exit out so you can go back into your sdk folder. All the hackerize commands are done from the kit location.
Well, I can't do this at work, was planning on trying, but the sdcard reader in my printer here doesn't work, so I'll have to try it with my laptop at home. Just wasted time downloading all the packages.
Still seems very cumbersome and confusing.
harlenm said:
Well, I can't do this at work, was planning on trying, but the sdcard reader in my printer here doesn't work, so I'll have to try it with my laptop at home. Just wasted time downloading all the packages.
Still seems very cumbersome and confusing.
Click to expand...
Click to collapse
You don't even need the SD reader. Just leave it the phone.
davwman said:
You don't even need the SD reader. Just leave it the phone.
Click to expand...
Click to collapse
Oh.
Now, once I get this done, how do you flash the new ROM?
harlenm said:
Oh.
Now, once I get this done, how do you flash the new ROM?
Click to expand...
Click to collapse
Once you have root, you can install ROM manager from the market. Run ROM manager, scroll to the bottom and tap on "All ClockworkMod Recoveries" and select 2.5.1.3 or 2.5.1.4. DO NOT INSTALL 3.0.0.5, it is NOT compatible with Froyo ROMs.
Once you tap one of those versions, it will automatically download and install ClockworkMod Recovery. Load the ROM you want to install onto your SD card, and in ROM manager, hit "reboot into recovery".
When you get to recovery, go to Backup/Restore and make a backup of your current ROM. Then do a data/cache wipe (factory restore) and then go to Install ZIP from SD Card and select your new ROM. Flash and you're on your merry way
harlenm said:
Oh.
Now, once I get this done, how do you flash the new ROM?
Click to expand...
Click to collapse
Read the included readme file in the kit its part of step two. The kit is designed so all you need to do is follow the instructions and input a few commands and it pretty much does everything for you minus pushing the power button to get into hboot. The second hackerize command is the actual downgraded Rom.
r34p3rex said:
Once you have root, you can install ROM manager from the market. Run ROM manager, scroll to the bottom and tap on "All ClockworkMod Recoveries" and select 2.5.1.3 or 2.5.1.4. DO NOT INSTALL 3.0.0.5, it is NOT compatible with Froyo ROMs.
Once you tap one of those versions, it will automatically download and install ClockworkMod Recovery. Load the ROM you want to install onto your SD card, and in ROM manager, hit "reboot into recovery".
When you get to recovery, go to Backup/Restore and make a backup of your current ROM. Then do a data/cache wipe (factory restore) and then go to Install ZIP from SD Card and select your new ROM. Flash and you're on your merry way
Click to expand...
Click to collapse
Thanks, gonna read up more and then go for it.
dears,
i have rooted 3G Xoom (MZ601).. 3.0.1
now i want to update it to 3.1 or 3.2
and i want to activate the US market ..
please, any one can guide me to do it ..
Simplest way i know.
1. Relock your zoom and go back to stock:
http://forums.androidcentral.com/xo...stboot-official-system-images.html#post708799
2. Update through the system update on your xoom.
3. Once you get up to 3.2 unlock and reroot your xoom:
http://forum.xda-developers.com/showthread.php?t=1170760
+ this way now you can reset it back to stock completely if you ever need too. Step by step guides are very easy to follow. Mostly copy and paste commands into notepad if your lazy like me. The whole process takes maybe 20 minutes.
is3od said:
dears,
i have rooted 3G Xoom (MZ601).. 3.0.1
now i want to update it to 3.1 or 3.2
and i want to activate the US market ..
please, any one can guide me to do it ..
Click to expand...
Click to collapse
Hi ,
I think you can go directly from 3.01 to 3.2 using this guide:
http://forum.xda-developers.com/showthread.php?t=1183416
If you don't already have ClockworkMod recovery v3.2.0.0 R4c installed, pay attention to post #7.
Good luck!
incase you dont have sdk installed put all files in a folder on your C:/ directory with a name you can find. Youll need these in addition to be able to use adb on your computer File name: SDK ADB.zip File size: 359.93 KB put them all in a folder called rootxoom or something.
prowlex said:
1. Relock your zoom and go back to stock:
http://forums.androidcentral.com/xo...stboot-official-system-images.html#post708799
2. Update through the system update on your xoom.
3. Once you get up to 3.2 unlock and reroot your xoom:
http://forum.xda-developers.com/showthread.php?t=1170760
+ this way now you can reset it back to stock completely if you ever need too. Step by step guides are very easy to follow. Mostly copy and paste commands into notepad if your lazy like me. The whole process takes maybe 20 minutes.
Click to expand...
Click to collapse
His Xoom is 3G there is no OTA update to 3.2 for 3G.
I really would not relock and go back to stock. He's rooted and that's more than half the battle.
is3od, the method I posted is for non-US Xooms as long as they are rooted.
i'll try it
prowlex said:
1. Relock your zoom and go back to stock:
http://forums.androidcentral.com/xo...stboot-official-system-images.html#post708799
2. Update through the system update on your xoom.
3. Once you get up to 3.2 unlock and reroot your xoom:
http://forum.xda-developers.com/showthread.php?t=1170760
+ this way now you can reset it back to stock completely if you ever need too. Step by step guides are very easy to follow. Mostly copy and paste commands into notepad if your lazy like me. The whole process takes maybe 20 minutes.
Click to expand...
Click to collapse
thank you for your help... today i'll try it and will inform you about the result.
Dear friends
Could you please confirm that above tutorial can be applied for 3G version of xoom?
I see some of guide with noted that applying for wifi version only.
Regards,
okantomi said:
Hi ,
I think you can go directly from 3.01 to 3.2 using this guide:
http://forum.xda-developers.com/showthread.php?t=1183416
If you don't already have ClockworkMod recovery v3.2.0.0 R4c installed, pay attention to post #7.
Good luck!
Click to expand...
Click to collapse
first i will relock my xoon then i'll update it ..
thank you,
prowlex said:
incase you dont have sdk installed put all files in a folder on your C:/ directory with a name you can find. Youll need these in addition to be able to use adb on your computer put them all in a folder called rootxoom or something.
Click to expand...
Click to collapse
ok
thanks...
k66473 said:
Dear friends
Could you please confirm that above tutorial can be applied for 3G version of xoom?
I see some of guide with noted that applying for wifi version only.
Regards,
Click to expand...
Click to collapse
it should be, because my Q is for 3G Xoom.
is3od said:
it should be, because my Q is for 3G Xoom.
Click to expand...
Click to collapse
You have ignored my posts which are for non-US 3G Xoom. Pleease check them again. I was not the one to tell you to go back to stock, unroot and relock. Please don't do that...no need.
Just try to follow the guide I posted in #3. Good luck.
thanks a lot
okantomi said:
You have ignored my posts which are for non-US 3G Xoom. Pleease check them again. I was not the one to tell you to go back to stock, unroot and relock. Please don't do that...no need.
Just try to follow the guide I posted in #3. Good luck.
Click to expand...
Click to collapse
I really appreciate your help .. thanks a lot ..
adb devices returns no devices
I have followed the tutorial after reading through it several time to unlock and root stock xoom 3.2. when i get to the adb devices command it returns me to the prompt with no devices returned or shown. i have android sdk windows in root of C:. i have rootboot.img, superuser.apk & su binary in a xoom folder in my downloads folder. i open the cmd in the download folder wherein resides rootboot.img, superuser.apk & su binary and type adb devices and nothing. i can see the xoom in explorer so i assume the usb drivers are there. i do have a yellow flag in other devices in device manager-other devices that says MZ604. but i can find no drivers anywhere for it though i have scoured the web for 2 days. i am at a loss as i have tried to perform this root for 2 days using all of my adb noob skills, but have had no luck as of yet. any suggestions? win7, stock xoom 3.2 wifi, pretty computer savvy except for adb
Thanks for any help as i only have 4 days of return left in case of brickage, which i am not so sure i would do inasmuch as it would be my fault...
big flamingo said:
I have followed the tutorial after reading through it several time to unlock and root stock xoom 3.2. when i get to the adb devices command it returns me to the prompt with no devices returned or shown. i have android sdk windows in root of C:. i have rootboot.img, superuser.apk & su binary in a xoom folder in my downloads folder. i open the cmd in the download folder wherein resides rootboot.img, superuser.apk & su binary and type adb devices and nothing. i can see the xoom in explorer so i assume the usb drivers are there. i do have a yellow flag in other devices in device manager-other devices that says MZ604. but i can find no drivers anywhere for it though i have scoured the web for 2 days. i am at a loss as i have tried to perform this root for 2 days using all of my adb noob skills, but have had no luck as of yet. any suggestions? win7, stock xoom 3.2 wifi, pretty computer savvy except for adb
Thanks for any help as i only have 4 days of return left in case of brickage, which i am not so sure i would do inasmuch as it would be my fault...
Click to expand...
Click to collapse
Make sure USB Debugging is checked under Settings/Applications/Development. If it is checked, then there is something wrong with your drivers.
big flamingo said:
I have followed the tutorial after reading through it several time to unlock and root stock xoom 3.2. when i get to the adb devices command it returns me to the prompt with no devices returned or shown. i have android sdk windows in root of C:. i have rootboot.img, superuser.apk & su binary in a xoom folder in my downloads folder. i open the cmd in the download folder wherein resides rootboot.img, superuser.apk & su binary and type adb devices and nothing. i can see the xoom in explorer so i assume the usb drivers are there. i do have a yellow flag in other devices in device manager-other devices that says MZ604. but i can find no drivers anywhere for it though i have scoured the web for 2 days. i am at a loss as i have tried to perform this root for 2 days using all of my adb noob skills, but have had no luck as of yet. any suggestions? win7, stock xoom 3.2 wifi, pretty computer savvy except for adb
Thanks for any help as i only have 4 days of return left in case of brickage, which i am not so sure i would do inasmuch as it would be my fault...
Click to expand...
Click to collapse
Check the thread you started...people have answered there.
okantomi said:
Hi ,
I think you can go directly from 3.01 to 3.2 using this guide:
http://forum.xda-developers.com/showthread.php?t=1183416
If you don't already have ClockworkMod recovery v3.2.0.0 R4c installed, pay attention to post #7.
Good luck!
Click to expand...
Click to collapse
I'd like to do the same as OP, update a rooted stock 3.0.1 euro 3G to 3.2 - I've already come across the thread you link to, but there's something I don't get.
pienut (user whose post you linked to) is saying that he went from 3.0.1 to 3.2, but in step 3 he writes:
Step 3 - Install 3.2 EURO rom:
Just copied the Euro 3.2 update from this post to my SD Card and flashed it from recovery.
Just to be sure, I did a full wipe after flashing.
Click to expand...
Click to collapse
Am I missing something, or is the SD card not disabled in 3.0.1? I know it is for me, afaik it only started working with 3.1 and up. I can't wrap my mind around going from 3.0.1 -> 3.2 using the SD card method, and yet it's mentioned in quite a few more threads and posts.
Ideally, I'd like to update to the Xoom ROM 2.1 Hammerhead (http://forum.xda-developers.com/showthread.php?t=1203635), but in those instructions, too, step 2 says
Download the 2.1 rom zip file and place it on your external sdcard
Click to expand...
Click to collapse
How, if I can't access it in the first place? Should I install 3.1 first before I install Hammerhead? If so, do you know about any step-by-step I can follow?
Sorry to jump in on this thread like this... it was the closest I could find related to my problem after hours of searching and reading. Thanks.
Alright, I figured it out on my own... I took a leap of faith and installed the ClockworkMod Recovery 3.2.0.0 (R4c), booted to recovery, and in there it's possible to mount the SD card under mounts and storage > mount usb storage. It will then appear in Windows as an external drive (as usual).
Yay, learned something new today. Now on to the next battle
Sticky Worthy?
How To Guides in Video Form:
How To One Click Unlock Bootloader http://www.youtube.com/watch?v=sSVD5b9nAcI&list=UU1J4DKcJXENzC-FkyMU6dow&index=15&feature=plcp
How To Manually Unlock Bootloader http://www.youtube.com/watch?v=sSVD5b9nAcI&list=UU1J4DKcJXENzC-FkyMU6dow&index=15&feature=plcp
One Click DebugFS method: http://www.youtube.com/watch?v=EpuiKIl7lpI&feature=share&list=UU1J4DKcJXENzC-FkyMU6dow
Video Root Guide: http://youtu.be/cuiJYKV2GGU
^^This is just a Visual aid for the method provided by Invisiblek outlined here http://forum.xda-developers.com/showthread.php?t=1756885
How to Update Your Baseband/Modem to latest OTA : http://www.youtube.com/watch?v=K2dQ2kv9kYs&feature=share&list=UU1J4DKcJXENzC-FkyMU6dow
How To Nandroid backup in Cwm Recovery: https://www.youtube.com/watch?v=4zWSK7cO3xg&feature=youtube_gdata_player
How To Unbrick, Unroot, Factory Restore Galaxy S III http://youtu.be/p0T4FO_NZ8Y
How To Easily Backup Apps and Data to Flashable.zip http://youtu.be/OPPoKlu_4qw
How To Install CM9 or CM10: http://youtu.be/f68NgGgrwAQ
How To Back up and Restore IMEI: http://www.youtube.com/watch?v=dl6Ms3oVEDo&feature=share&list=UU1J4DKcJXENzC-FkyMU6dow
How To Use Your SGS3 as a Netflix Remote: http://www.youtube.com/watch?v=JICq0P1Ywg4&feature=share&list=UU1J4DKcJXENzC-FkyMU6dow
Rom Reviews and Install Guides:
JellyWiz Touchwiz Jelly Bean 4.1.1 Rom Review and Install: http://www.youtube.com/watch?v=twDBZg4wkBk&feature=share&list=UU1J4DKcJXENzC-FkyMU6dow
Liquid v2 RC3 Rom Review and Install http://www.youtube.com/watch?v=ieuy5Bx76-Q&feature=share&list=UU1J4DKcJXENzC-FkyMU6dow
AOKP 4.1.1 Rom Review and Install: http://www.youtube.com/watch?v=kjULad8XS-4&feature=share&list=UU1J4DKcJXENzC-FkyMU6dow
MIUI v4.1 Jelly Bean Review and Install for Unlocked Bootloaderhttp://www.youtube.com/watch?v=azkToBXLjig&list=UU1J4DKcJXENzC-FkyMU6dow&index=2&feature=plcp
Cyanogen Mod 10 Jelly Bean for Unlocked Bootloader http://www.youtube.com/watch?v=7nW0SRKxUQk&list=UU1J4DKcJXENzC-FkyMU6dow&index=14&feature=plcp
Clean Rom Full Review and Install For Unlocked Bootloader http://www.youtube.com/watch?v=0PtIKXddfNI&list=UU1J4DKcJXENzC-FkyMU6dow&index=7&feature=plcp
Bean's Custom Stock Rom Review and Install For Unlocked Bootloader http://www.youtube.com/watch?v=napoMpZKCDA&list=UU1J4DKcJXENzC-FkyMU6dow&index=13&feature=plcp
First ROM Stock Stripped by Invisiblek: for Locked Bootloader https://www.youtube.com/watch?v=9Oek_24wEXI&feature=youtube_gdata_player
Cyanogen Mod 10 Rom Review: for Locked Bootloader http://youtu.be/2efLx_iTBDk
AOKP Android Open Kang Project Milestone 6 Review and Install for Locked Bootloader http://youtu.be/ATiFaCssKHs
Synergy Rom (Battery life and Stability) Review and Install for Locked Bootloader http://youtu.be/bj7w2nu_sKk
fix your link. you forgot the opening [ preceding the closing youtube tag.
Could you please do a back-to-stock video as well?
Thanks for doing this. First Samsung phone so it's quite new to me. Appreciate the video, it'll definitely help
Sent from my PC36100 using Tapatalk 2
Always wish these were made for each phone, the devs put so much work into making roms and root methods, but usually skimp on the instructions for those of us who aren't as experienced. Thanks for this
I will try to update this thread with any other videos I make, or I might make a separate thread. Glad its helped though.
Sent from my Galaxy Nexus using xda app-developers app
Thanks for the video. I'll be going through this as quickly as I can get home from work tomorrow!!
Great video, but in your description, to install the SDK using the Java links, I installed the JDK but the SDK install still thinks it's missing, and won't go any further, making me Cancel out. No idea what to do now...no SDK = no ADB commands :-(
minmongoblin said:
Great video, but in your description, to install the SDK using the Java links, I installed the JDK but the SDK install still thinks it's missing, and won't go any further, making me Cancel out. No idea what to do now...no SDK = no ADB commands :-(
Click to expand...
Click to collapse
Alos agree great video and helped me do root in no time at all! However, like you I am unable to get the adb part of the video working. I followed your other video and written instructions to the "t", and I only got as far as..
"adb is not recognized as an internal or external command"
I got the Java JDK to install fine as well as the SDK with all the required installs you said were needed for it to work. I left out all others as I'm not really too familiar with adb is it is. I changed the path, and named folders and files exactly as you did in your video. However I could never get the cmd to show adb devices.
I know the original post stated that we should know how to use it before we try this, but after trying to do research on this for the past 4 hours last night.. I concluded I have no idea what I am doing wrong/nor how to do it properly apparently.
If anyone would be able to possibly give me some assistance that would be great .
Lemonhead8890 said:
Alos agree great video and helped me do root in no time at all! However, like you I am unable to get the adb part of the video working. I followed your other video and written instructions to the "t", and I only got as far as..
"adb is not recognized as an internal or external command"
I got the Java JDK to install fine as well as the SDK with all the required installs you said were needed for it to work. I left out all others as I'm not really too familiar with adb is it is. I changed the path, and named folders and files exactly as you did in your video. However I could never get the cmd to show adb devices.
I know the original post stated that we should know how to use it before we try this, but after trying to do research on this for the past 4 hours last night.. I concluded I have no idea what I am doing wrong/nor how to do it properly apparently.
If anyone would be able to possibly give me some assistance that would be great .
Click to expand...
Click to collapse
Is your usb debugging enabled on your phohne?
When you cd <path to platform-tools>, then type: adb.exe
Does a long list of commands scroll across the screen?
Having the same problem. I see the long list of commands. But when I type "adb devices" nothing is listed.
trginter said:
Having the same problem. I see the long list of commands. But when I type "adb devices" nothing is listed.
Click to expand...
Click to collapse
I haven't tried it myself yet, but it sounds like you don't have the drivers properly installed.
Sent from my Ally (Cant wait to get rid of this POS and replace it with my S3 tomorrow!)
NightxFall said:
I haven't tried it myself yet, but it sounds like you don't have the drivers properly installed.
Sent from my Ally (Cant wait to get rid of this POS and replace it with my S3 tomorrow!)
Click to expand...
Click to collapse
That would be my guess. Put it in USB Debug mode, and plug the phone in, I think it auto-installs the ADB drivers.
Hmm, the phone is in USB Debugging Mode and plugged in, nothing downloaded.
trginter said:
Hmm, the phone is in USB Debugging Mode and plugged in, nothing downloaded.
Click to expand...
Click to collapse
What is the exact output when you type adb devices?
Good to know root is avail
Will try this tomorrow after work
s197 said:
Is your usb debugging enabled on your phohne?
When you cd <path to platform-tools>, then type: adb.exe
Does a long list of commands scroll across the screen?
Click to expand...
Click to collapse
For those having problems with this, look up "how to add a path to the windows command line“. You should not have to CD to a directory to make a command work .
Sent from my SCH-I535
s197 said:
Is your usb debugging enabled on your phohne?
When you cd <path to platform-tools>, then type: adb.exe
Does a long list of commands scroll across the screen?
Click to expand...
Click to collapse
Yes, usb debugging was on when I tried to do this. I usually always just leave it on honestly.
I guess I should have been more clear about where I was at, but yes i did the
cd platform-tools .. enter.. then adb.exe.. and thats when I got the 'adb' is not an internal or external command. I dont know where I messed up along the way... . I feel pretty confident I did everything correctly.
However there was one difference i did notice. On the path stated in the guide it says system32 something then you list the path to platform tools and whatnot.... but mine had something /windowspowershell/ or something like that.
I went back to the start and deleted my drivers and reinstalled them but deleted the jdk and sdk for the time being.. Maybe ill try again soon if I can figure it out better.
I believe this will help a lot of you. Thanks goes to Adrynalyne....
http://forum.xda-developers.com/showthread.php?t=879701
Lemonhead8890 said:
Yes, usb debugging was on when I tried to do this. I usually always just leave it on honestly.
I guess I should have been more clear about where I was at, but yes i did the
cd platform-tools .. enter.. then adb.exe.. and thats when I got the 'adb' is not an internal or external command. I dont know where I messed up along the way... . I feel pretty confident I did everything correctly.
However there was one difference i did notice. On the path stated in the guide it says system32 something then you list the path to platform tools and whatnot.... but mine had something /windowspowershell/ or something like that.
I went back to the start and deleted my drivers and reinstalled them but deleted the jdk and sdk for the time being.. Maybe ill try again soon if I can figure it out better.
Click to expand...
Click to collapse
It sounds like you're not moving to the right directory. Check to see where your adb file is, on the new SDK it's in platform-tools but if you downloaded ADB from a long time ago, it's in another folder (I think tools, but it's been a while).
What I would do is navigate to your adb file from "my computer". At the top, under address, it will show you the path you need to type. For instance, for me, I open my computer, C: drive, Android folder, then platform-tools. So my path would be:
Code:
cd C:\Android\platform-tools
Everyone's path is different depending on where you put your files.
This guide assumes that you are on a stock Pantech Flex P8010 running either ICS (v4.0.4). or the updated JB (v4.1.2) Please note that rooting a ICS phone has been known to cause issues when trying to run the over the air update. If you have already rooted and are looking for a way to update to JellyBean please skip to the section on updating, if this isn't you keep reading.
So at this point you have decided to continue. You shouldn't run into any issues if you follow the directions and you shouldn't mess your phone up even if root doesn't take. However, in the spirit of covering ones back side....
I am not responsible for anything that goes wrong.
Jelly Bean 4.1.2 or ICS 4.0.4
This method was found by LuneBear and has not been tested by myself so I cannot personally verify its effectiveness. I did check and it seems to work with both ICS and JB but your mileage may vary. You will need to download SRSroot and install it on a Windows machine.
SRS ROOT
SRS Homepage
Make sure that USB debugging is enabled on your phone. Connect your phone via USB and run the program. Select the button for all root methods. Then you will need to select the Legolas exploit. Once everything is done (may take some time) just reboot the phone and you should be good to go.
Ice Cream Sandwich 4.0.4 ONLY
Windows Option
This method has been tried on a number of Windows versions and some work some don't so your mileage may very. This method uses Bin4ry's Root method and was orgnially discovered by aaki_rocker and is WAY LESS COMPLICATED. However please note that some users have had issues using this method with Bin4ry's latest version of the root script. It is recommended that you download an older version if you run into any issues or the root doesn't take.
First lets get some drivers on your Windows box. To do this you will need to download the Pantech PC Suite and install it.
http://c724062.r62.cf2.rackcdn.com/PantechPCSuite_1.1.1.3437.exe
Next you will need to download and extract Bin4ry's root script.
http://ul.to/z7krermj
Once you have these two files you will need to plug your phone into the PC via USB and enable the USB type as Data Mode.
Next run the Bin4ry's script and follow the directions when in doubt about what to choose select the simplest option in all cases.
If everything goes well you will have a nicely rooted phone.
Linux Option
This is not a point and click root and is not for the faint of heart. This method of rooting is based off of Bin4ry's root for ICS/JB. Changes have been made to the srcipt to allow it to work with the Flex please follow the steps below and you will have root in just a few minutes. It will probably take you longer to download the files you need than to actually root the phone.
This method has been performed successfully using Ubuntu 12.10 64bit it may work with other versions of linux but it will not work with Windows due to the driver issues and the fact that I didn't alter the windows batch file, in fact I removed any windows related files from Bin4ry's original package.
First you will need to set up the linux machine if you don't already have it. This can be done in one of a few ways you can run a live copy using a Live CD/USB boot (this will not install linux on your computer unless you tell it to) or you can install it in the standard manner or using WUBI, the third option us setting up linux in a virtual machine. If you don't know how to do this google it, there is a wealth of information out there on these subjects and probably some you can even understand without a degree in astro-physics.
Second you will need to set your phone up so that USB debug mode is turned on [settings>developer options]. Make sure you phone isnt plugged into the USB or it won't let you change the setting.
Now plug your phone into to the (linux) computer with the USB. Next you will need to set the USB computer connection type to Media Device(MTP)
In order for the computer to communicate with the phone we will need to install Android Debug Bridge (ADB) and create a couple of files.
These files will basically trick the computer into thinking it has actual drivers for the phone.
Open a terminal window, and enter the following (this will install ADB):
sudo apt-get install android-tools-adb
Once this is done enter the following
sudo gedit /etc/udev/rules.d/70-android.rules
Gedit will open at this point copy the the following into it and then click save and close the window.
SUBSYSTEMS=="usb", ATTRS{idVendor}=="10a9:6055", MODE="0666"
In the terminal window enter this (yeah I know it looks the same just go with it)
sudo gedit /lib/udev/rules.d/70-android.rules
After the window opens paste the same line of code into the file that you did in the previous files, save and close.
Test your connection by issuing the following command in the terminal window:
adb devices
Should see something similar to:
OSCAR01111112010204 device
Your adb is now recognizing your phone and you can now move on to the next step if you are not getting this don't even bother moving to the next step it wont work. If you don't see this check your settings and go again.
Ok so you are now ready to actually root the phone. The first thing your going to need to do is download my modified Bin4ry script. See the attached file.
After you have it downloaded you will need to extract it you can do this by opening the file manager (click on the home folder icon) and going to download. Find the file called Root_Flex.zip. Right click on it and select EXTRACT HERE. After its done extracting you should see a directory called Root_Flex. In a terminal windows enter the following:
cd Downloads/Root_Flex
Your prompt should now look something like
[email protected]_name~/Downloads/Root_Flex$
From here just enter the command:
bash RunMeFlex.sh
At this point you should see a bunch of junk come up and a menu asking which way you want to try to root. Type 1 and press enter. It will give you 3 errors, ignore them. It should copy a bunch of files and ask you to press restore on your phone, do it. It should ask you to press Enter to reboot the phone, do so and the phone will reboot. It should be waiting on you to press enter again dont press enter until the phone is completely rebooted and for good measure give it an extra few seconds. The script should finish and the phone will reboot again this time you should see a little box with an update appear on the phone. At this point you should be rooted. If not try the script again.
I hope this helps out a lot of folks out there. Let me know if I need to change anything in this How to or if I made any mistakes along the way.
Updating If you're already rooted
So you rooted your phone and now you want JellyBean but when you run the update you get the dead droid image and the update fails OR you live in an area that isn't covered by AT&T and you want the update, what do you do? Well thanks to some hard work by Attn1 we have a solution and its pretty simple. First off you will need to have CWM running on the phone. Now there are a few ways to go about this but the method I used was here:
http://forum.xda-developers.com/showthread.php?t=2133857
You only need to go as far as getting CWM up an running on the phone you do not need to install it as the the update by Attn1 will take care of a full install of a better version. You will need to have a copy of Fastboot.exe and some img files. Below is a rar file that has all the necessary files to get CWM running (not installed) on the phone using windows (sorry I don't have the linux files for this one). Just unpack them into a convienent folder somewhere and follow the instructions on the link above.
http://tinyurl.com/oa2p48f
I recommend using the boot_external.img but if you do not have an external SD card and only have the internal storage just use boot_internal.img instead. This method relys on you being able to get into fast boot. If you do not have access to fastboot for what ever reason I suggest you jump ahead in the thread and read Attn1 methods for installing CWM:
http://forum.xda-developers.com/showthread.php?t=2008888&page=44
Next get the update files from this link (second post)
http://forum.xda-developers.com/showthread.php?t=2008888&page=47
Once you have all the files downloaded and copied everything to the appropriate SD cards on your phone your ready to go. If you don't know how to do this don't even think about anything else till you learn this. After this is all done follow the directions below (copied from Attn1's post)
Procedure if you ARE NOT running baseband JYUS06032013 (ICS Basebands) :
boot ICS CWM
flash FLEX-JB-JYUS06032013-FIRMWARE.zip from CWM
format system in CWM (will NOT wipe data, but makes sure old rom does not flash back stock recovery)
restart start recovery/adb reboot recovery (JB CWM is installed - do not try to fastboot boot ICS CWM)
flash FLEX-JB-JYUS06032013-ROM.zip from CWM.
reboot
Procedure if you ARE running baseband JYUS06032013 (JB Baseband) :
get root (Instructions HERE - use GANDALF)
install CWM (Instructions HERE)
flash FLEX-JB-JYUS06032013-FIRMWARE.zip from CWM
format system in CWM (will NOT wipe data, but makes sure old rom does not flash back stock recovery)
reboot to CWM
flash FLEX-JB-JYUS06032013-ROM.zip from CWM.
reboot
This ROM is Pantech stock with no mods other than CWM installation protection and all stock permissions and symlinks carefully maintained and consistent with the product of a successful OTA.
The firmware is also stock, with the exception of the open aboot allowing fastboot boot <bootimage>, and installation of JB CWM with nothing else added or changed. It runs well with nothing broken. You MUST be on JB firmware (below) to run it properly.
You can let the new CWM root it if you like when you exit - it will prompt you. It will also prompt you to disable CWM on reboot make sure this gets disabled or the phone will keep booting to CWM rather than the ROM.
Downloads:
md5: 1a0ca5f177bce2f4c428931616e0ecd1 FLEX-JB-JYUS06032013-FIRMWARE.zip
md5: 17c0e611ab6dfbca230571c1e40f3d14 FLEX-JB-JYUS06032013-ROM.zip
Make sure you check the md5sum on the files before you flash them if there wrong download them again this is vital.
If you need a program to check md5sums copy this .exe file to your c:\windows\system\ and run it from the command line.
http://tinyurl.com/l74wl9q
Thanks go to Bin4ry for the original script and all the technical help provided.
Check out the thread and give a thanks and donate a few bucks if you can.
http://forum.xda-developers.com/showthread.php?t=1886460
Thanks to Atadres for getting me going in the right direction and help testing along the way.
Thanks to Esau Silva for this post that helped get the drivers working for us in Ubutnu.
http://esausilva.com/2010/05/13/setting-up-adbusb-drivers-for-android-devices-in-linux-ubuntu/
Thanks to Aaki_rocker for coming up with the Windows version of this root method you can find his original post here.
http://forum.xda-developers.com/showthread.php?t=2141538
Thanks to LuneBear for finding the root method for JellyBean.
Thanks to Attn1 for the JellyBean update and CM 10.2 version of CWM Recovery.
jist a quick memo guys when you issue the command adb devices please cd to proper android sdk platform tools folder or else youll get an error like no command did you mean..... heres the proper way do this step before you do the adb devices step type in cd ~/android-sdk-linux/platform-tools press enter then type in ./adb devices
i am now trying to contact team win for help with porting the recovery image team win recovery so we can start roming this device and adding ports and roms
atadres said:
jist a quick memo guys when you issue the command adb devices please cd to proper android sdk platform tools folder or else youll get an error like no command did you mean..... heres the proper way do this step before you do the adb devices step type in cd ~/android-sdk-linux/platform-tools press enter then type in ./adb devices....
Click to expand...
Click to collapse
Acutally this assumes you are on a completely fresh install and did not have adb installed through the platform tools if that is the case everything I typed up will work. However you are correct too. Let me know if you think I should go ahead and rework the stuff to be a little more universal if so please PM me an update of the commands.
your right my apologies but one thing i noticed that i would like to say idk if its my experiance or universal after successfully rooting the flex the lockscreen fails to resize itself leaving a black space where the onscreen dock is usualy located no big issue though and the rooting was easy and painless once adb was set up correctly 100000+ points thanks so much
Good job guys. Respect! I have a Pantech Flex, which is an awesome device with the same specs (things that matter to me) as S3, but without big name. I like Pantech Flex because it's size is much better for me than.
The only thing now is to create a ROM! Is it difficult to make a pure Android ROM? Nothing additional, just a pure Android like in Nexus?
Again, thank you guys for your dedication! I'll definitely donate as soon as I have Jelly Bean loaded on my Pantech Flex!
Thanks, this worked great. I am gonna start on a ROM. Hope I don't get bricked.
Sent from the new Pantech Flex. Nominated best lowest priced new smartphone. U jelly I paid nothing, for a phone almost as good as the Galaxy S3?
HighCommander540 said:
Thanks, this worked great. I am gonna start on a ROM. Hope I don't get bricked.
Sent from the new Pantech Flex. Nominated best lowest priced new smartphone. U jelly I paid nothing, for a phone almost as good as the Galaxy S3?
Click to expand...
Click to collapse
lets not get ahead of ourselves here guys in order to create a rom we would need to get a custom recovery on our phone this can be achived by mapping out the devices bootloader extracting an img file of it and using koushes clockworks mod recovery creator only when we achive a port of a custom recovery can we make roms and be able to flash them if any of you have knowledge of this as i am a noob when it comes to recoveries pleasae feel free to input we need all the help we can get guys
---------- Post added at 02:03 PM ---------- Previous post was at 01:58 PM ----------
ivansana said:
Good job guys. Respect! I have a Pantech Flex, which is an awesome device with the same specs (things that matter to me) as S3, but without big name. I like Pantech Flex because it's size is much better for me than.
The only thing now is to create a ROM! Is it difficult to make a pure Android ROM? Nothing additional, just a pure Android like in Nexus?
Again, thank you guys for your dedication! I'll definitely donate as soon as I have Jelly Bean loaded on my Pantech Flex!
Click to expand...
Click to collapse
lol right now we need knowledge donations unfourtunatly we cannot start working on roms till we have a custom recovery ported over either team win or clockworks mod recovery this will take a little bit of time and knowledge and to answer your question about the stock nexus rom your talking along the terms of a cynaogen mod port? or akop port looking into it i would say untill we have mapped the bootloader we wouldnt know how diffcult it would be because the simlinks maybe difcult for a phone that has not yet caught fire in the dev world
i wish i had the time to do a recovery myself and get cwm working but with my family and my fulltime job i barely get any time. Im going to spend all my time on this amazing little phone to do what i can. props to the root method it worked flawlessly!!!
Sent from my PantechP8010 using Tapatalk 2
Awesome I'm glad im getting some good feed back on the root. I wasnt sure if I did the rightup correctly and im glad its working out for everyone.
If I get some time I will start looking into a custom CWM and all that junk I have a contact that should be a pretty good help in this just have to find the time to do it.
Yeah after coming from the LG Nitro HD I was surprised at how easy this was to root.
If you want to get together on gtalk we can work on this together. Right now I'm in the process of getting a ROM dump so we can recover our phones from stock images if we happen to mess them up, which I'm sure we will, but that's the best part! Lol.
I can smell CM9 and CM10 calling to this phone!!!
Sent from my PantechP8010 using Tapatalk 2
jSterling said:
Yeah after coming from the LG Nitro HD I was surprised at how easy this was to root.
If you want to get together on gtalk we can work on this together. Right now I'm in the process of getting a ROM dump so we can recover our phones from stock images if we happen to mess them up, which I'm sure we will, but that's the best part! Lol.
I can smell CM9 and CM10 calling to this phone!!!
Sent from my PantechP8010 using Tapatalk 2
Click to expand...
Click to collapse
Yeah I love this phone but I have to say the Pantech launcher kinda pisses me off.
donavan01 said:
Yeah I love this phone but I have to say the Pantech launcher kinda pisses me off.
Click to expand...
Click to collapse
Agreed lol im using nova
I actually don't mind the launcher, its pretty nice compared to other brand launchers. I'm probably going to try launcher pro though that's been my favorite sense I had my prepaid optimus V
Sent from my PantechP8010 using Tapatalk 2
jSterling said:
I actually don't mind the launcher, its pretty nice compared to other brand launchers. I'm probably going to try launcher pro though that's been my favorite sense I had my prepaid optimus V
Sent from my PantechP8010 using Tapatalk 2
Click to expand...
Click to collapse
I had launcher pro and hated it ... check out APEX seems like the stock ICS but with a lot of extras and without the annoying bits of the pantech that make me insane
donavan01 said:
I had launcher pro and hated it ... check out APEX seems like the stock ICS but with a lot of extras and without the annoying bits of the pantech that make me insane
Click to expand...
Click to collapse
hey guys... is there a pantech flex forum????????
also is it possible to unlock the device if you forget the log in pattern????? thanks
I don't know anything about mapping the device. So I am just going to work on a ROM for my infuse.
I will help with anything for testing. A stock image would be awesome. =-)
No flex forum yet.
_______
Sent from the new rooted Pantech Flex. Nominated best lowest priced new smartphone. U jelly I paid nothing, for a phone almost as good as the Galaxy S3?
jSterling said:
I actually don't mind the launcher, its pretty nice compared to other brand launchers. I'm probably going to try launcher pro though that's been my favorite sense I had my prepaid optimus V
Sent from my PantechP8010 using Tapatalk 2
Click to expand...
Click to collapse
sense is my fav launcher and no no forum yet ive requested and gotten no reply smh
did this thread die guys?
atadres said:
did this thread die guys?
Click to expand...
Click to collapse
Wait till after Xmas I bet you a lot of people will get this phone as presents.
donavan01 said:
Wait till after Xmas I bet you a lot of people will get this phone as presents.
Click to expand...
Click to collapse
Yeah I can see that happening. This weekend I am going to work on it to see what I can come up with. I've been so swamped with work and life bs that I haven't had a chance.
No this thread didn't die.
Sent from my PantechP8010 using Tapatalk 2