i have these specs:
model number: HTC Desire Z A7272
IMEI SV: 01
Android Version: 2.2.1
kernesystem: 2.6.32.21-g6e170e7
[email protected] #1
softwarenumber: 1.82.405.1
i am guessing that i need to follow the downgrade guide, and the root guide next.
or has the circumstances changed since the guides was written ?
This is the best guide and is regularly updated http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
Sent from my HTC Desire S using XDA Premium App
Hey, I downgraded and rooted my Desire Z by using the wiki few weeks back. Took me about one hour in total, reading through everything and following the instructions! Have you downloaded the ADB? I just used DroidExplorer which I find so much easier to use!
Sent from my HTC Vision using XDA App
..
DroidExplorer instead of ADB ?
i downloaded ADB but cant get the cmd prompt to serve me
c:\> ADB devices
it prompts: "'adb' is not recognized as an internal bla bla bla.."
so im of to a bad start. even before im really getting started
krankdroid said:
DroidExplorer instead of ADB ?
i downloaded ADB but cant get the cmd prompt to serve me
c:\> ADB devices
it prompts: "'adb' is not recognized as an internal bla bla bla.."
so im of to a bad start. even before im really getting started
Click to expand...
Click to collapse
You need to change to the directory where adb is. It will be something like c:\>Android-sdk\platform tools
Sent from my HTC Desire S using XDA Premium App
krankdroid said:
DroidExplorer instead of ADB ?
Click to expand...
Click to collapse
Yeah it's so much easier to manage then ADB. It's basically like using Windows Explorer but for your phone, so it's really easy to add apps and files or whatever to your phone without having to remember to use ADB codes (especially if your a beginner like me).
It comes with the Android SDK everything setup so you don't need to deal with the setup of the ADB which saves the hassle and time. All you would need to do is just point CMD in the path of the ADB inside Droid Explorer and you're good to go! I would post a link for you but I cant obviously, so just give it a Google and you'll find it.
Your IMEI (and probably IMSI?) is personal information that you should not post on the internet. Not sure exactly what nefarious things can be done with it (if any), but it also has no real bearing on the discussion (whether the phone can be rooted), so you best take it off.
redpoint73 said:
Your IMEI (and probably IMSI?) is personal information that you should not post on the internet. Not sure exactly what nefarious things can be done with it (if any), but it also has no real bearing on the discussion (whether the phone can be rooted), so you best take it off.
Click to expand...
Click to collapse
I agree to delete imei number
Sent from my HTC Desire Z using XDA App
ok..
so now ADB is working with my phone..
the next step is downgrading. that will wipe my device. so how on earth do i take a backup, if i need to wipe my device, before i can root, so that i can take a titanium backup?
is it just tuff luck for me?.. goodbye apps and widgets? or can i backup before i root ?
You can use any backup/restore app to do the job.
The guide someone posted earlier in the thread works flawlessly there're only a few things to remember:
When using ADB when pushing files make sure you're in the same folder as the file itself otherwise it'll return the error "No such file or directory".
If you followed the guide to setting up ADB then you will have changed "Path" under "System Variables" in "Environmental Variables" (Right-click My Computer > Advanced tab > Environmental Variables) to include the following:
";C:\Android\android-sdk\platform-tools;C:\Android\android-sdk\tools"
(No quotes and leave out the semicolon at the beginning if there already is one.)
Change C:\Android\android-sdk\ to wherever ADB is on your comp and you can issue ADB commands from any from almost anywhere on the comp rather than having to be in the same folder as it.
Other than that I can't think of much else other than to follow the instructions and ask for help if you get stuck.
I got ADB working..
I will stick to posting if i run into any problems.
But before i can root i need to downgrade my device first. And this procedure will wipe my phone..
I also need to root before i can do a titanium backup.
I have taken a mybackup pro backup. But that is only apps, media and data. And not a complete backup. As i understand it i cannot create a real backup unless i root right?
And to root i need to perform a downgrade that will wipe my device..
So no matter what i will loose all my stuff if i want to root..
Via HTC Desire Z
Your Gmail and Contacts are synched to Google, so no need to back those up. If you want to backup your SMS and MMS, I have been using SMS Backup+, and it works well. It backs up SMS/MMS to Gmail, and restores SMS to the phone (unfortunately does not restore MMS pics to the phone, but those will be saved on Gmail). It also supposed to backup the call log, but it doesn't restore properly for me after switching ROMs.
If you want to backup things like games saves, root is usually need to access those files. Although, there are apps on the Market to backup your Angry Birds progress, if you want that!
Any other things you want backed up before you downgrade?
If you follow the guide to root your Desire Z you shouldn't run into much problems.
There's a few recent post on the forum with similar questions and will be more then happy to help you get rooted. Like I mentioned to someone earlier, I rooted by DZ just now for about 2weeks. Yeah I did brick my phone twice but I did manage to get everything back to working and rooted. My only mistake was that I hadn't created and fallowed the goldcard process but once that was done anything to do with ADB worked like a charm.
i am now trying to learn the INFOCID of my device..
but something is up.
Code:
cd C:\android-sdk-windows\platform-tools
adb reboot bootloader
fastboot oem boot
the first time i tried it. i wrote "adb reboot bootloader"
it booted up with into the volume button navigation. i then wrote "fastboot oem boot"
and it told me "fastboot is not a command"
It start to load when choosing fastboot on the device, but then stops with an error and goes back to boot menu.
the info i obtained from the first command was:
Code:
vision PVT Ship S-on
Hboot-0.85.0010
microp-0425
radio-26.04.02.17_M2
eMMC-boot
no INFOCID there as far as i can see
could someone help a newbie out ?
I need to know my infocid before i can downgrade
KalC87 said:
Hey, I downgraded and rooted my Desire Z by using the wiki few weeks back. Took me about one hour in total, reading through everything and following the instructions! Have you downloaded the ADB? I just used DroidExplorer which I find so much easier to use!
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Hi hoe did you do with droid explorer i can't there is a tutorial or something??
krankdroid said:
....
the first time i tried it. i wrote "adb reboot bootloader"
it booted up with into the volume button navigation. i then wrote "fastboot oem boot"
and it told me "fastboot is not a command"
It start to load when choosing fastboot on the device, but then stops with an error and goes back to boot menu.
....
Click to expand...
Click to collapse
I got fastboot from the HTC Dev Center.
Related
TGA_Gunnman created a one click root that new users will want to use, said thread is a sticky in Captivate Development. If you still want to use the old method (and install ADB) please use this one.
I followed my own guide! This works perfectly if you read everything and follow the instructions.
Also: once you are rooted, be EXTREMELY careful! Half of the new threads are people who have screwed up their phones by deleting this or corrupting that. Please, for the sanity of all of the devs and Android veterans, make backups and just be all around careful. Almost all problems that anyone has had are repareable AND PREVENTABLE with a little reading and care. Just to clarify, rooting does not automatically enable sideloading. Please follow http://forum.xda-developers.com/showthread.php?t=738376 to enable sideloading.
Follow these steps exactly and there will be no risk of bricking your Captivate, the worst that may happen is the phone rejecting the update.zip.
HOWEVER:
I take no responsibility if ANYTHING at all happens to your device that you don't like. Don't come crying to me if your brand new phone breaks in any way. Your warranty is also void, but you could have figured that out for yourself.
Now that that's over with, lets get to the fun bit. If you are on Windows, you can follow this procedure, or for TGA_Gunnman's one click root program (only on Windows), you can go ahead and skip to the bottom.
1) You may need Samsung drivers if you are on a PC, which you can learn about here: ADB Drivers at the Unlockr
For 64 bit Windows, you'll need these drivers: http://zedomax.com/blog/2010/07/14/s...iver-download/
Don't proceed until your phone is fully installed on Windows with the drivers!
2) Download the attached zip (at the bottom of the post) and rename it to update or update.zip if you are on a Mac. (If you are on a Mac, DO NOT USE SAFARI to download the file, it automatically unzips any zip file. Use Google Chrome or firefox instead.) Scroll down the notification bar and click "mount" to allow your computer to read the internal memory. Put the file on the INTERNAL SD card of the Captivate, which won't be tough to figure out if you don't have an SD card in the phone.
3) EDIT--There is an easier way to get to recovery, but do this step anyway. Turn the phone off, then hold power, volume up and volume down. If you still want the android SDK (which will be very useful throughout your rooted experiences) follow the old procedure:
This step requires the Android SDK, and Android Debugging enabled. You can get the SDK here: Android SDK. Just download the zip, extract it to something like C:\Android. You won't need the Java dev pack or anything.
You can enable Android Debugging like this: From the homescreen, press Menu, then click Settings. Navigate to Applications>Development and check USB Debugging. Now, hook the phone to the computer. Next,
On a PC, click start>run>"cmd" (in the text box) or on a Mac, spotlight "Terminal". Linux users, you know what to do.
The command you will use is in the tools folder of wherever you extracted it to (IE: C:\android\tools), so be sure your working directory of command prompt is in that tools location!
Finally, type:
Code:
adb reboot recovery
Click to expand...
Click to collapse
4) Once the phone is booted into recovery, use the volume keys on the phone to scroll to "Reinstall packages." Use power to select what you have highlighted.
5) Give yourself a pat on the back. You are now rooted. You should see a Superuser application now.
MD5 Sum: 1eb65923281c113e8751a7d8a6faff43
Can we please have more detailed instructions? I don't understand the part where it says "type in the terminal"
I am very new to android as this will be my first Android phone.
Also, after rooting will we be able to install 3rd party applications? Or do we have to do anything else to bypass ATT's restrictions?
adb terminal is software you need to install on your PC , will probably need samsung drivers also , guide is indeed not noob friendly. This will help you get needed bits including ADB
Probably None of us have captivate , so writing a guide is a bit troublesome
Ditto, a guide to the adb terminal please! I will acquire this phone, this Sunday.
Actually, you'd have to install a custom ROM for that. MoDaCo should be coming out with them pretty soon, and so will XDA. It won't be too long. BTW, once you have ADB installed on your computer, you can sideload apps all you want. The command is
Code:
adb install /directory/of/app/on/computer
point me to some functioning samsung drivers and I can do this!
If you cant get it to work on windows, try a ubuntu live cd. All you need to do is go to ubuntu and burn a disc and reboot.
Are there no Windows 64 bit drivers?
Edit- I found some that work. I think. Haven't tried it (yet).
http://zedomax.com/blog/2010/07/14/...ic-4g-and-fascinate-galaxy-s-driver-download/
Edit 2- Just did the root. Seems to have worked (no errors) but how do I know if it did? How do I delete say, ATT Maps?
Thanks for this. I am new to smartphones and plan on purchasing the Samsung Galaxy-S, but don't want to mess it up. I am new to editing the OS of any smartphone, but I think if I have a tutorial I will be fine
For Mac and Linux you put a ./ in front of the adb correct? (./adb install...)
NOSintake said:
For Mac and Linux you put a ./ in front of the adb correct? (./adb install...)
Click to expand...
Click to collapse
if you are in the directory above yes. the ./ just saves you from writing out the full path
lets say adb is in "/home/user/Downloads/sdk/tools"
you could type out "/home/user/Downloads/sdk/tools/adb command" regardless of where your terminal window was focused
or if you were currently in the directory "/home/user/Downloads/sdk/tools"
you could use the shortcut "./adb command"
OP I'd change your post based on my experiences... Here's a little more detail and I've rearranged it (you need the drivers before running these commands, for example).
blackjackboy said:
Please let me know if this rooting method works as I have no Captivate to test on. I'm not taking any credit for any of these files, LeshaK made the original file to root the European Galaxy S, Justadude modified it for the T-Mobile Vibrant and chaoscentral edited the file for use on the Captivate.
Follow these steps exactly and there will be no risk of bricking your Captivate, the worst that may happen is the phone rejecting the update.zip.
HOWEVER:
I take no responsibility if ANYTHING at all happens to your device that you don't like. Don't come crying to me if your brand new phone breaks in any way.
Now that that's over with, lets get to the fun bit.
1) You may need Samsung drivers if you are on a PC, which you can learn about here: ADB Drivers at the Unlockr
For 64 bit Windows, you'll need these drivers: http://zedomax.com/blog/2010/07/14/...ic-4g-and-fascinate-galaxy-s-driver-download/
Don't proceed until your phone is fully installed on Windows with the drivers!
2) Download the attached zip (at the bottom of the post) and rename it to update or update.zip if you are on a Mac. Scroll down the notification bar and click "mount" to allow your computer to read the internal memory. Put the file on the INTERNAL SD card of the Captivate, which won't be tough to figure out if you don't have an SD card in the phone.
3) This step requires the Android SDK, and Android Debugging enabled. You can get the SDK here: Android SDK. Just download the zip, extract it to something like C:\Android. You won't need the Java dev pack or anything.
You can enable Android Debugging like this: From the homescreen, press Menu, then click Settings. Navigate to Applications>Development and check USB Debugging. Now, hook the phone to the computer. Next,
On a PC, click start>run>"cmd" (in the text box) or on a Mac, spotlight "Terminal". Linux users, you know what to do.
The command you will use is in the tools folder of wherever you extracted it to (IE: C:\android\tools), so be sure your working directory of command prompt is in that tools location!
Finally, type:
Code:
adb reboot recovery
4) Once the phone is booted into recovery, use the volume keys on the phone to scroll to "Reinstall packages." Use power to select what you have highlighted.
5) Give yourself a pat on the back. You are now rooted. You should see a Superuser application now.
Thank you to LeshaK, Justadude, and chaoscentral. Once again, I didn't discover how to root, that credit goes to LeshaK, bringing it over to the USA was Justadude's doing, and chaoscentral edited the file for use on our Captivates.
MD5 Sum: 1eb65923281c113e8751a7d8a6faff43
Click to expand...
Click to collapse
Ubuntu 10.04 - adb
Any step by step instructions just to get adb running enough on 10.04 to root and side load software? I'm getting command not found when I try to run adb, even after downloading packages.
Hi,
Did this thread worked well to Root the Captivate or anyother suggested link? I'll appreciate any help.
Thanks
rerooting captivate
This worked perfectly on my Captivate. I now have the SuperUser Permission on my application screen. Now I can REALLY screw up my Captivate!!!
Thanks for the answer & More Queston
cellgeek said:
This worked perfectly on my Captivate. I now have the SuperUser Permission on my application screen. Now I can REALLY screw up my Captivate!!!
Click to expand...
Click to collapse
Hi,
Thanks for your helpful answer. As I'm getting my Cativate tomorrow, can you please just answer yes or no to each of my questions as follow ?
After Rooting will I be able to:
1- download any 3rd party Android application?
2- install any "Samsung Galaxy S" ROM on my Captivate?
3- Recieve any "OTA" update as a "Galaxy S" phone?
Thanks again
Muhamadabdelaall said:
Hi,
Thanks for your helpful answer. As I'm getting my Cativate tomorrow, can you please just answer yes or no to each of my questions as follow ?
After Rooting will I be able to:
1- download any 3rd party Android application?
2- install any "Samsung Galaxy S" ROM on my Captivate?
3- Recieve any "OTA" update as a "Galaxy S" phone?
Thanks again
Click to expand...
Click to collapse
1. No. You will have to use adb or the database modification method (which having root access makes possible). Both are described in detail elsewhere in this forum.
2. Rooting means simply getting superuser permissions. Loading a ROM has to do with the bootloader and recovery partition. Unmodded Galaxy S ROMs probably will not work on the Captivate, but be patient.
3. Not sure what you're asking. You will still get any Captivate OTA updates as if you hadn't rooted, but you won't get, for example, the rumored Korean FroYo Galaxy S update OTA when it drops. You'd have to wait for the Captivate OTA FroYo upgrade (or there may be a ROM or patch you can flash by then).
Rooting is basically just allowing programs to run as the superuser account. Many programs like Metamorph, some screenshot apps and some wifi tethering apps require more permission than Android normally gives an app.
Thanks Drachen
Drachen said:
1. No. You will have to use adb or the database modification method (which having root access makes possible). Both are described in detail elsewhere in this forum.
2. Rooting means simply getting superuser permissions. Loading a ROM has to do with the bootloader and recovery partition. Unmodded Galaxy S ROMs probably will not work on the Captivate, but be patient.
3. Not sure what you're asking. You will still get any Captivate OTA updates as if you hadn't rooted, but you won't get, for example, the rumored Korean FroYo Galaxy S update OTA when it drops. You'd have to wait for the Captivate OTA FroYo upgrade (or there may be a ROM or patch you can flash by then).
Rooting is basically just allowing programs to run as the superuser account. Many programs like Metamorph, some screenshot apps and some wifi tethering apps require more permission than Android normally gives an app.
Click to expand...
Click to collapse
Thanks alot for taking all this time & energy to reply to me! WOW, it seems like everytime I wanna step up one, I go back 10 steps. All I need is to use my Captivate for installing a Stock Rom of "Galaxy S" & be able to get rid of any "AT&T" restrictions for anything on this phone, what should I do please?
Thanks
Muhamadabdelaall said:
Thanks alot for taking all this time & energy to reply to me! WOW, it seems like everytime I wanna step up one, I go back 10 steps. All I need is to use my Captivate for installing a Stock Rom of "Galaxy S" & be able to get rid of any "AT&T" restrictions for anything on this phone, what should I do please?
Thanks
Click to expand...
Click to collapse
The ATT stuff doesn't actually run so they aren't a big deal at this point. I also don't see Amazon MP3 background stuff like some Android devices have, so... There's really not a huge case for rooting yet.
That said, when Custom ROMs for this come out I'll still be getting one.
For those of you having a hard time installing ADB Shell, try this video. It worked for me.
http://www.youtube.com/watch?v=YeWH6Bj1DYw&feature=related
Hi, I am looking to root my MT4G.. but I always see "root at your own risk" etc... Well, I am ready to root at my own risk, however I don't really know enough to want to attempt thsi yet.. so I am looking for a general thread explaining what this stuff is and how it is explained..(definitions for commonly used terms and acronyms..) someone please point me somewhere.... Thank you.
I have been looking for a thread that answers these questions I have and I haven't found one in about a week, so I posted this...however I literally just found one, that I think answers most of my questions @ http://forum.xda-developers.com/showthread.php?t=859446&highlight=guide sooo any MOD please close or delete my thread, and I am sorry for wasting your time.
I used grankin01's instructions...
I know there's a lot of info out there, especially if you just search for "root." It can be a bit daunting at first, especially if you're not oriented properly.
I have rooted 3 MT4G's using the following guide by grankin01...
http://forum.xda-developers.com/showthread.php?t=834225
It really can't be any easier. I started out on a G1 and rooting was not this easy back then. To paraphrase grankin01's instructions (please read his instructions carefully and do this at your own risk)...
1. Download and install VISIONary
2. Extract that root.rar file to your sdcard. This is where a lot of people got messed up. There's a 'root' folder within a 'root' folder 'cause the person who originally .RAR'd these files, RAR'd a 'root' folder. Basically, when all is said and done, you should have a folder named 'root' on your SD Card. Within the 'root' folder, will be 3 files - hboot_dhd.nb0, Root.sh & wpx.ko.
3. Run VISIONary and click Temproot now - you now have temporary root access
4. Download and run Terminal Emulator and execute the commands outlined in grankin01's post. You will be prompted to restart. Once your phone boots back up, run VISIONary again only this time, click Attempt permoot now. Your screen will go black and eventually, the phone will reboot.
On two occassions, when I was doing this on replacement MT4G's I received, I forgot to enable USB Debugging. I found that VISIONary would just spin its wheels at the Temproot portion. After rebooting the phone and trying again, VISIONary actually prompted with an error to let me know USB Debugging had to be enabled. Totally my fault, but the app just spins its wheels at first, so you don't really know what's up until you reboot and try again.
To recap:
- VISIONary temproot
- Commands outlined in grankin01's post
- VISIONary permroot
It really is quite easy to do! If anything, there are plenty of redundant posts that explain how to get root access. I hope my info above doesn't add to the mire.
shlongwoodian said:
I know there's a lot of info out there, especially if you just search for "root." It can be a bit daunting at first, especially if you're not oriented properly.
Click to expand...
Click to collapse
I think that is why I posted this... Because I have been searching but I don't know what exactly to search for, or what step to do such thinigs in...I appreciate the help. I am currently following the s=off perma root guide, however I am struggling at getting my ADB drivers installed correctly....sooo I have some tinkering to do but I am looking forward to rooting my phone, and I don't even know what that is gonna open up..CANT WAIT!!!
EDIT: I checked out your link, and I am using a guide written by him, i believe, but it is the one that is a little more complex, and causes a deeper perma root...
For the ADB drivers just look on the sdcard that came with your phone. There should be a file named HTCDRIVER.EXE. Just copy that to your windows desktop and execute it. It will install the drivers you need. As for linux, my Kubuntu 10.10 installation saw my phone without any problems or driver installations.
The new guide with the "deeper" root actually is the better one to follow. Its really not as complicated or difficult as it looks.
grankin01 said:
For the ADB drivers just look on the sdcard that came with your phone. There should be a file named HTCDRIVER.EXE. Just copy that to your windows desktop and execute it. It will install the drivers you need. As for linux, my Kubuntu 10.10 installation saw my phone without any problems or driver installations.
The new guide with the "deeper" root actually is the better one to follow. Its really not as complicated or difficult as it looks.
Click to expand...
Click to collapse
Freaking awesome...in sitting here at work not looking forward to going home to another wasted two hours trying to set the driver up you just saved my day with that info about the driver...you sure it has the adb driver though..?
Sent from my HTC Glacier using XDA App
Jaskwith said:
Freaking awesome...in sitting here at work not looking forward to going home to another wasted two hours trying to set the driver up you just saved my day with that info about the driver...you sure it has the adb driver though..?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Yeah, I had to install it for adb to work on my windows installation and it has saved several other people heartache too.
Ughhhh.. just found out I work at job #2 tonight...how FREAKING lame...like I wasted ALL my freetime not being able to figure it out last night and now that I think I know what to do... I have NO time...BLAH!!
Okay, so my ADB **** is still not working... I don't know why.. I am following the guide over at theunlockr.com and it still won't work.. I installed the SDK from google... I didnt DL the archives however... and then I installed the drivers off my SD card onto my computer, and when I open the Command prompt and type cd\ cd AndroidSDK\tools\ it says the directory does not exist... it says on the unlocr guide to try installing PDAneT and that might help, and so i did that as well, still says directory does not exist...ARGH this is frustrating!
Do you need perma root to boot into recovery?
I would just follow the visionary method so you won't even have to bother with adb. Just use root explorer to copy and past the files into the right directory. Did it on the bus, took me 5 minutes. No need to get true/deep root especially for someone just starting off. I promise, for all you'll be doing (and a hell of a lot more) you'll NEVER know the difference. Just gives you more options to screw up your phone. Start with perm root (set up the easy way), flash a rom or two, mess around with some cool apps for root users, figure out adb, and then work your way up to messing with the deeper system stuff (if you still feel need).
Just my 2¢
Sent from my HTC Glacier using XDA App
It sounds like you are looking in the wrong directory. Open your file browser and do a search for adb and pay attention to what folder it is in. My installation had like two subdirectories before I could even get to the tools directory on my windows drive.
That is if you still want to try adb. It is a valueable thing to learn. Espescially if your going to be doing these kinds of things to your devices. It can take a brick and turn it back into a phone if you know how to use it.
Thank you kind sirs you are very helpful to a pour nub such as myself...well it seems like I dont havr any freaking time ever so I think I might take c_licious's advice for now and read up on adb some more...i did see that in the thread its easy to convert from the perma root to the deep perma root so think that's what ill do. Thank you grankin for the tip on finding adb drivers that will definitely come in handy when I get to that. Yayyyyy!!!!
Sent from my HTC Glacier using XDA App
I am trying to downgrade from stock GB 2.3.3 ROM.
My SD card has now disappeared when i tried to put the PD98img.zip file on it.
When i tried to change from USB charging to disk drive there isn't any option anymore for disk drive.
However the SD drive and it's contents is shown in Astro file manager, very strange
I did this as per instructions:
1. Download Gingerbreak, and install it. Then tap root button.
2. You might get force close errors, just click the force close button and let Gingerbreak do it's job
3. Gingerbreak will, in the end, usually say that something went wrong. Just leave it open in your phone, and connect your phone to a PC. Charge only, USB Debugging enabled!
4. Open up a cmd and go to Downgrade folder, execute commands: (after command "su", allow SuperUser in phone)
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
su
If you got "#" in the result, you have temporary root! Proceed with commands:
Code:
cd /data/local/tmp
./misc_version -s 1.31.405.6
Next step is to put the PD98img.zip file on SD card so i tried to change the USB connection but the option is gone to connect to the SD.
Also when i go to Settings my SD card is not available, the system can not see any SD and i can't mount it either, it's gone.
What should i do now?
put the SD into ur pc, simples
Take out the sd card and reinsert it.
Then put the PD file on the SD card before beginning the process.
I rebooted it now and now i can choose USB disk drive.
What is the cause this was happening in the first place? somehow Gingerbreak did something.
I think it was trying to remove things whilst still mid adb shell.
[EDIT] Said something that wasn't quite right so removed, thanks for the heads up jkoljo.
Sent using witchcraft via XDA Developers Premium App.
That is incorrect, gingerbreak also works without S-OFF, like in the downgrade guide. The difference is, with S-OFF you get permanent root, and without it only temporary, which is enough for downgrading.
Sent from my Desire HD using Tapatalk
jkoljo said:
That is incorrect, gingerbreak also works without S-OFF, like in the downgrade guide. The difference is, with S-OFF you get permanent root, and without it only temporary, which is enough for downgrading.
Click to expand...
Click to collapse
My bad, I must have mis-understood something someone said to me previously.
Sent using witchcraft via XDA Developers Premium App.
Ok everything fine now running latest Lee, thanks.
Anyone had success with telus dhd?
Sent from my Desire HD using Tapatalk
goodrench said:
Anyone had success with telus dhd?
Click to expand...
Click to collapse
What problems are you having trying to downgrade your Telus DHD?
Sent from my Ericsson T39m
goodrench said:
Anyone had success with telus dhd?
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
what, with gingerbread or downgrading.... in my case, both.
gingerbreak will say its attempting, let it go into standby, then go back to using the phone, gingerbreak will say there's an error, reboot the phone..... you're rooted.
If you want to go downgrade, just use the RUU, it overides everything (something that the recovery tool isnt able to do when using the p98img.zip)
Downgrading and rooting with simple steps and no code entry, Made it, and it works for the Telus DHD and Inspire 4G
(Our Telus DHD's are the exact hardware twin of the Inspire 4G; unlike the Euro/Asian DHD's which have different radio controllers)
My trouble is getting su to work. Gingerbreak gets to the error message and when I "adb shell " to the phone it will not accept su. (Permission denied)
What ruu are you referring to? I tried 1.32 and 1.84, and they both fail.
I attempted to use the ruu downloaded from the link in the previous post and it failed saying bootloader version error.
Any thoughts?
success!!!
Had an old version of superuser installed from the telus dhd permanent root files that I previously downloaded. Uninstalled superuser and downloaded from market.
Also had phone unplugged from pc while running gingerbreak. previously left it plugged in through whole procedure.
Hope this helps someone else.
So I am not quite sure what exactly fastboot is supposed to do. I know you can flash recoveries, bootloaders, etc with it but that is about it for my understanding.
I tried to get into fastboot (following instructions here on the forum) mode earlier today and while the tablet gives me the fastboot message in the upper left, windows says that fastboot failed. Is there a folder I am supposed to be running cmd prompt from?
Sorry, still new to this stuff and my understanding of some of these tools is limited at best.
Sent from my A500 using Tapatalk 2
a friendly warning
CyaN1de said:
So I am not quite sure what exactly fastboot is supposed to do. I know you can flash recoveries, bootloaders, etc with it but that is about it for my understanding.
I tried to get into fastboot mode earlier today and while the tablet gives me the fastboot message in the upper left, windows says that fastboot failed. Is there a folder I am supposed to be running cmd prompt from?
Sorry, still new to this stuff and my understanding of some of these tools is limited at best.
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
Give me 30 mins got all the reading u gonna need b4 u make an attempt
if u fk up in here there is definitely NO WAY BACK in meantime you'll
Want to set adb as environmental variable in windows gonna make it
Helluva lot easier . Android sdk will too. f u don't know what I'm on About..
.best do some reading up on these as well.
Fast boot ain't something someone else can talk u thru and I doubt the devs will
Have any sympathy for anyone asking ....i bricked my tab pls help....
dibb_nz said:
Give me 30 mins got all the reading u gonna need b4 u make an attempt
if u fk up in here there is definitely NO WAY BACK in meantime you'll
Want to set adb as environmental variable in windows gonna make it
Helluva lot easier . Android sdk will too. f u don't know what I'm on About..
.best do some reading up on these as well.
Fast boot ain't something someone else can talk u thru and I doubt the devs will
Have any sympathy for anyone asking ....i bricked my tab pls help....
Click to expand...
Click to collapse
Running adb from its native folder is not an issue.....is fastboot the same way having to run cmd from folder that a file is located?
I prefer not to mess stuff that I do not fully comprehend (not that I fully comprehend ANY of this) but some of it makes more sense once you are into it rather than reading someone elses interpretation.
Sent from my A500 using Tapatalk 2
CyaN1de said:
Running adb from its native folder is not an issue.....is fastboot the same way having to run cmd from folder that a file is located?
I prefer not to mess stuff that I do not fully comprehend (not that I fully comprehend ANY of this) but some of it makes more sense once you are into it rather than reading someone elses interpretation.
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
yeh just a group of extended adb commands that allow you to do some pretty awesome stuff - like really, really bricking your tab for instance, lol. I'm unsure as to whether all the fastboot commands are available to us - i havent had enough spare time to devote to heavy duty reading in the Dev Forums!!!! You can flash everything in here so its like a supercharger;;;;Sort of like going from timmydeans EUU root to Civ's nvflash unlocking bootloaders thing, if you know what i mean.......
But heres some reading, most of it tutorial step by step stuff, mostly for other devices which may not apply to our tab but definitely apply to fastboot. AS you know, there is alot of info in our own dev forum but its hard to find a flow as the devs actually speak a different language to us!!!! So the tutorials are quite good in that respect as they use noob-ite speak
the backup and restore tute is a goody, couldnt get it going on v3 so looking forward to giving it a go on v4 (when i can find a quiet 30 mins or so, that is)
anyways happy reading be interested in your thoughts and keep us posted about what you get around to trying
rgds
Full Phone Backup http://forum.xda-developers.com/showthread.php?t=1420351
setup adb http://forum.xda-developers.com/showthread.php?t=1249798
adb http://forum.xda-developers.com/showthread.php?t=879701
adb logcat http://droid-force.com/showthread.php?tid=150&pid=573#pid573
ics BL by Skrilax_CZ http://forum.xda-developers.com/showthread.php?t=1514951
So I located Fastboot in D:\Android\android-sdk\platform-tools\Fastboot.exe
But putting tablet into fastboot mode yields the driver installer to report that "Device driver software was not succesfully installed".......Fastboot X Failed....is this normal? Will it run when I use cmd prompt from D:\Android\android-sdk\platform-tools?
I guess a little linux knowledge would go a long way.....too bad I can't get a grasp on that either.
Thanks for the links.....hopefully I can find time to give a read.
Set up adb/fastboot for noob-ites 101
CyaN1de said:
So I located Fastboot in D:\Android\android-sdk\platform-tools\Fastboot.exe
But putting tablet into fastboot mode yields the driver installer to report that "Device driver software was not succesfully installed".......Fastboot X Failed....is this normal? Will it run when I use cmd prompt from D:\Android\android-sdk\platform-tools?
I guess a little linux knowledge would go a long way.....too bad I can't get a grasp on that either.
Thanks for the links.....hopefully I can find time to give a read.
Click to expand...
Click to collapse
weird??? i kicked straight in to bl, fastboot drivers installed, never saw red x
u mean u arent cmd from platform tools???
in the cpuid guide I suggested extracting the just_adb.zip into C:\ so setting
up the env. var. would be easier I have been meaning to post the steps for
doing that, guess theres no time like the present
Set adb as Environment Variable or call adb direct from command prompt
............ first, copy the path to your install - in your case:
............ "Path to adb" = D:\Android\android-sdk\platform-tools
1. Click on the Start menu
2. Right click on Computer
3. Click on Advanced system settings
4. Click on the Environment Variables button
5. Look for Path in the System Variables section. Double click on it
6. Go to the end of the Variable value box and put in a semicolon ;
7. Now paste your "Path to adb" after the ;
8. it should look like this in your case ;D:\Android\android-sdk\platform-tools
9. Now test it out - start - run/search - cmd - in cmd window type: adb devices
10. If you've followed the steps you will see your device ID - voila!!!!
as you can see this makes trouble shooting so dam easy -
if you cant get a device id do not go any further in what u r doing
cos it aint gonna work....period!!!!! also since ICS has screwed
with getting our cpuid like this, for our purpose here, it is only important
that a device id is shown - not how right or wrong it is.....clear????
so getting back to it, check fastboot*.exe in same folder as adb.exe -
it came like this in my own setup not sure about the asdk setup -
remember too fastboot only has a few commands and i still havent
got round to trying them all out yet....
to anyone following this, I cannot say enough how dangerous this can be
please, please, please take a moment to read thru just one of the links i
posted earlier - they are tutorials and if you see the dev thread regarding
v4 unlock...you will not only learn something amazing but begin to
appreciate and respect the work done by these devs who laid the groundwork
that enabled civato and blakthund3r to produce what they have with the
unlocked bootloader - without this groundwork we would still be waiting
for a way to get full root access and cwm, custom roms, themes and mods......
Thanks for that
Seems my Windows skillz need brushing up on again too....LOL
C:\Users\username>adb devices
List of devices attached
11717XXXXXX device
CyaN1de said:
Thanks for that
Seems my Windows skillz need brushing up on again too....LOL
C:\Users\username>adb devices
List of devices attached
11717XXXXXX device
Click to expand...
Click to collapse
sweet m8 -
yeh whoever thought windoze would actually be useful!!!!
which i guess is freakn handy as having to go linux would spin me out....
what can i say??? I'm a child of windoze had no choice, forced-addiction
before i was born, lol - breaking the habit, but always go back, goddamit
OK....I get the adb ok.
But when I put tab into FB i get the driver error (see attachment). I suppose that I should not be getting this?
Trying just "fastboot reboot" (not wanting to go any farther until I get a grasp...HAHA) I get "waiting for device"
CyaN1de said:
OK....I get the adb ok.
But when I put tab into FB i get the driver error (see attachment). I suppose that I should not be getting this?
Click to expand...
Click to collapse
dont let windows install
choose let me choose where to install dunno exact wording
Does not give me a choice.
Driver is located at D:\Android\android-sdk\extras\google\usb_driver ???
This is making my head hurt....LOL
CyaN1de said:
Does not give me a choice.
Driver is located at D:\Android\android-sdk\extras\google\usb_driver ???
This is making my head hurt....LOL
Click to expand...
Click to collapse
Yr head hurts????
Ive updated the cpuid guide u my wanna take 5 min timeout to read it, the answers r all in there
I don't use full sdk there's a link to mini sdk zip in that post just has ad and fast boot
I've never had to use google drivers
Just plugged my tab in and its just 'worked'
DL Acer drivers if u haven't already . These are the most important ones to have installed right.
Disconnect and reboot everything
Run Acer setup.exe
Plug USB in
Go into fast boot, win doze will want to install f/b drivers let win doze do it, but if they fail, then run again and choose let me install, blah, blah, blah
What OS u got? Vista/win 7 don't normally have any probs
Acer drivers have been installed and all relevant sdk packages installed and up to date AFAIK. (USB_Acer_1.06.1500_A30HA31H_A.zip)
Had no issues installing ICS Bootloader V.3 manually through APX (no auto script) via instructions so I know I can at least do that well.....LOL
Might have to try reinstalling USB drivers and see if that helps.
Thanks
EDIT: Reinstalled USB Drivers now I can't get adb working....F#@K!!!!!!!!!
EDIT II: Re-Re-Installed Drviers and ADB working again...yay...LOL
EDIT III: Used A500_Manager.exe, clicked on "Enter Fastboot" and windows installed and recognized drivers......DBL YAY!!!!
C:\Users\username>fastboot reboot
rebooting...
finished. total time: 0.165s
Now.......to Brick this puppy.....
Thanx for your help dibb_nz....looks like all I needed in the first place was a driver reinstall...HAHA.
Hek m8 for a second or two there, I was feeling ya pain, lol
Oh but the elation when it finally happens!!!!!
I dunno why those drivers act out like that, but it always the same....
Fail, reinstall, fail, reinstall u can understand why peeps get frustrated
Glad u got it m8
Rooting, Backing Up TA and unlocking bootloader on a Mac can be a pain in the backside especially if you're a nube. Since there isn't an obvious guide out there for us (the most hated computer users by developers) Mac users i decided to create one.
Before we start make sure you're running the latest Mac OS X Mavericks (which is free thanks to apple generosity ) this is to make things easier for me when it comes to helping you.
PLZZZZ PLZZZZZ Read Instruction first (making sure you have a general under standing of them) THEN FIND A POSSIBLE ESCAPE PLAN (just incase things go south) and obtain the correct files before proceeding to follow them!!!!
WARNING!!!!From this point onwards I AM NOT RESPONSIBLE for any damages to your phone, whether they are as small as a 1/1000 mm scratch or as big as a worldwide Nuclear Holocast caused by Aliens! You decided to follow these instruction so it's YOUR FAULT!
Here's the order of what we'll be covering first to last:
1) Backing Up TA
2) Unlocking Bootloader
3) Installing a custom kernel
4) Rooting
BACKING UP TA
You may have heard rumours saying that "YOU CANNOT BACKUP TA ON MAC OS X, ONE MUST HAVE WINDOWS!".
Well I'm here to tell you that's TRUE, sadly. But FEAR NOT! Because the GODS have given us a work around (which is probably longer), and here it is:
First Downgrade to .534 using latest flashtool for Mac OS X
DOWNLOAD HERE http://www.flashtool.net/download.php (make sure you dave the app in applications folder)
Downgrade instruction here: http://forum.xda-developers.com/showpost.php?p=45464122&postcount=3
You can find firmware folder by right clicking ( if thats enables, surf the interwebs on how to do it if you don't know) then "show package contents" => Contents ==> MacOS ===> firmwares. This is ware you'll place your .ftf fiiles.
Before you ask, yes I know downgrading to .534 from .290 might kills sim detection but flashing .290 again (which we'll do at the end) using flashtool will fix that.
Then download,buy or any other means that are LEGAL "wink wink" (I bought BTW cause I love these guys!), Parallels Desktop 9 or later. Or use Bootcamp if you know what that is and are willing reboot you Mac lots of times just to change something on your phone. To me personally it completely defeat the purpose of having a Mac in the first place although its a nice option.
You can get Parallels Desktop 9 or later legal and get a 14 day trial of it here at their official website here: http://www.parallels.com/downloads/desktop/
Then get yourself a copy of Windows OS (windows 8 recommend cause it comes with inbuilt anti-virus) or try this 90 day free trail of Windows 8/8.1 from Microsoft:
Here is link http://www.microsoft.com/en-gb/business/products/downloads-and-free-trials#/
Then use common sense to install Windows on mac using Parallels or if your new and confused follow instructions from this video http://www.youtube.com/watch?v=UsChUvlTePE
Once windows is installed use this seksy guide to Root: http://forum.xda-developers.com/showthread.php?t=2439328
And this other seksy guide to Back TA: http://forum.xda-developers.com/showthread.php?t=2292598&highlight=ta
NOTE: Connect your device while Parallels Desktop (PD) is running windows and a window will pop up notifying you whether you want to connect device to mac or windows. Make sure you select Windows.
Make sure you save the TA file some where safe like google drive, skydrive, drop box, box or all 4 of them
then use flashtool to flash .290 back (root might disappear depending on what you do.)
You can practically use Windows from PD with other guides on xda z1 forum to do the rest of the step. But step 3 is going to be a Nightmare especially on window because you're dealing with drivers and command prompt. If you're not in good terms with these youre going to suffer with these, trust me I know .
Unlocking Bootloader "THE EASY PART!"
Turn off Parallels Desktop open browser and head to: http://xperiafirmware.com/8-firmware/42-sony-xperia-z1-c6903
Scroll down to how to unlock bootloader and follow the instruction using Mac OS X.
then check if bootloader is unlocked by dialling *#*#7378423#*#* and go to service info / configuration
If the last line says
bootloader unlocked: Yes
Then its unlocked
If it says
bootloader unlocked allowed: Yes
then it is locked but you can unlock it
If it says
bootloader unlock allowed: No
then you cannot unlock it
Installing a Custom Kernal"THE HARD PART!"
For this you need to First set up ADB and Fastboot on MAC. I will post a link to a very very easy to follow guide on how to do that. This guide is pretty easy to follow but I do advise that you follow it carefully down the way words are spelt other wise you're going to run into problems.
Here is the guide: http://forum.xda-developers.com/showthread.php?t=1917237
Take note on of this step "press CTRL+X to exit, then Y to confirm the save then press ENTER" because people forget to press ENTER and the start complaining.
Now download and unzip DoomKernel from: http://forum.xda-developers.com/showthread.php?t=2448613
Save it some where convenient like the "android" folder you created.
Then open terminal and type the Command while your device in in fastboot mode (turn off phone and connect usb while holding volume up Button, a blue light should be shown on Z1):
"adb fastboot flash boot directory of where you placed the kernel/Z1-DooMKernel-v04.img"
here's an example of my code:
"adb fastboot flash boot /Users/RealibleCandy4/Desktop/android/Z1-DooMKernel-v04.img"
Now you have custom kernel on phone after reboot.
Rooting
Download SuperSU (do not unzip) and place on sdcard from: http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
Flash SuperSU.zip on one of the recoveries which you can access by either holding Volume down/up key after you see the DooMkernel splash screen and phone vibrates.
Well done You are now rooted!
Before you ask, yes I know downgrading to .534 from .290 might kills sim detection but flashing .290 again (which we'll do at the end) using flashtool will fix that.
Click to expand...
Click to collapse
Even on windows if you downgrade from .290 to .534 than flash .290 again, it will fix the sim detection? Also what .290 are you flashing with the mac/windows? Link to the file please?
then use flashtool to flash .290 back (root might disappear depending on what you do.)
Click to expand...
Click to collapse
Again I can't see a link to the file for .290, and root might disappear? What does a user have to do to make sure the root doesn't disappear, obviously they want to avoid this.
Sorry just clarifying questions for other people, and myself. Good work on the guide.
RealiableCandy4 said:
Then use common sense to install Windows on mac using Parallels or if your new and confused follow instructions from this video http://www.youtube.com/watch?v=UsChUvlTePE
Once windows is installed use this seksy guide to Root: http://forum.xda-developers.com/showthread.php?t=2439328
And this other seksy guide to Back TA: http://forum.xda-developers.com/showthread.php?t=2292598&highlight=ta
NOTE: Connect your device while Parallels Desktop (PD) is running windows and a window will pop up notifying you whether you want to connect device to mac or windows. Make sure you select Windows.
Click to expand...
Click to collapse
Or... you know... you could just do it from OS X. Check out my guide, much simpler.
http://forum.xda-developers.com/showthread.php?t=2449244
Seriously?! Backing up TA on Mac or Linux is just a few commands in terminal. Very simple.
Sent from my C6903 using Tapatalk
I know you can use terminal but the problem with that is its pretty easy to make spell miss takes on terminal and it can be frustrating + doing it that way is very dangerous since the TA is a sensitive area also there's no way to check if it worked properly by mock restoring TA. I choose this way cause it's much safer.
Sent from my C6903 using xda app-developers app
RealiableCandy4 said:
I know you can use terminal but the problem with that is its pretty easy to make spell miss takes on terminal and it can be frustrating + doing it that way is very dangerous since the TA is a sensitive area also there's no way to check if it worked properly by mock restoring TA. I choose this way cause it's much safer.
Sent from my C6903 using xda app-developers app
Click to expand...
Click to collapse
Depends on how you define "safe", I much prefer doing it myself, then I know it is done properly. And what do you mean by mock restoring? You can easily verify authenticity by MD5:ing the TA partition, and subsequently the image taken of it.
Good advice didn't know that. Like you said it depends on you. I personally prefer this method because I can root and back up TA and check if it's correctly backed up with a push of a couple of buttona and I don't have to deal with the fear of accidentally miss typing commands. I'll (with your permission) put a link to your method in the tutorial sometime tomorrow. I'll have to test it first.
Sent from my C6903 using xda app-developers app
TagEHeuer said:
Even on windows if you downgrade from .290 to .534 than flash .290 again, it will fix the sim detection? Also what .290 are you flashing with the mac/windows? Link to the file please?
Again I can't see a link to the file for .290, and root might disappear? What does a user have to do to make sure the root doesn't disappear, obviously they want to avoid this.
Sorry just clarifying questions for other people, and myself. Good work on the guide.
Click to expand...
Click to collapse
Yes flash .290 will fix it make sure you use the latest Flashtool NOT 0.9.11.0.
for firmware I'm using the 14.2.A.0.290 Generic NCB (Unbranded/Nordic) found at http://forum.xda-developers.com/showthread.php?t=2572195
you can find the .290 files on xda z1 general forum
As for root it will disappear when using Flashtool but on you can get it back once you unlock bootloader, flash custom kernel and flash superSU.zip file. Im not sure if you can root 4.3 with a locked bootloader i havent found anything all ask in Q&A section. This guide is for root with unlocked bootloader.
Are you kidding me ? I like your guide... Like all oft the others which are the same.... The only difference; you are using parallels.
My suggestion for your guide: "Get Parallels on your mac, install windows and follow the known 100 tutorials".
Sorry for flamewars... But its really boring to read the same tutorials with different spellings like about 100 times.
Kind regards
Meet
Gesendet von meinem Nexus 7 mit Tapatalk 4
Edit;
@TagEHeuer
Dont Quote entire OP.............
Not everyone will read the billion guides you've read. The more the helpful. He's not doing any harm to anyone. Yes, quoting OP was a mistake, thank you for pointing it out.
meetdaleet said:
Are you kidding me ? I like your guide... Like all oft the others which are the same.... The only difference; you are using parallels.
My suggestion for your guide: "Get Parallels on your mac, install windows and follow the known 100 tutorials".
Sorry for flamewars... But its really boring to read the same tutorials with different spellings like about 100 times.
Kind regards
Meet
Gesendet von meinem Nexus 7 mit Tapatalk 4
Edit;
@TagEHeuer
Dont Quote entire OP.............
Click to expand...
Click to collapse
RealiableCandy4 said:
Good advice didn't know that. Like you said it depends on you. I personally prefer this method because I can root and back up TA and check if it's correctly backed up with a push of a couple of buttona and I don't have to deal with the fear of accidentally miss typing commands. I'll (with your permission) put a link to your method in the tutorial sometime tomorrow. I'll have to test it first.
Sent from my C6903 using xda app-developers app
Click to expand...
Click to collapse
Be my guest, I made it specifically because I wanted people to learn more about their devices and as a result hopefully help increase the average knowledge level on these boards! Let me know if you need any help following it.
meetdaleet said:
Are you kidding me ? I like your guide... Like all oft the others which are the same.... The only difference; you are using parallels.
My suggestion for your guide: "Get Parallels on your mac, install windows and follow the known 100 tutorials".
Sorry for flamewars... But its really boring to read the same tutorials with different spellings like about 100 times.
Kind regards
Meet
Gesendet von meinem Nexus 7 mit Tapatalk 4
Edit;
@TagEHeuer
Dont Quote entire OP.............
Click to expand...
Click to collapse
I understand what you mean I did mention that in the post. But i also mentioned that the problem with that method is adb and drivers (mainly drivers) I tried doing that myself and I found that dealing with drivers is a pain, but luckly for use mac users we don't have to deal with that which is a good thing. It makes the installation of custom kernels via fastboot easy and you dont have to wake up the next morning wondering why drivers don't work anymore (which i went though) and causing you to look through 100s of forums for a solution. Somestimes the long why is the best way.