I am on a replacement phone. 1.5 updated to 2.1OTA trying to root per walkthrough instruction in guide forum.
Firmware 2.1
Baseband 2.40.00.01.22
Kernel 2.6.29-5898f66b
htc-kernel*and18-2 #1 (*added to allow post. noob, system thinks Im adding a link)
Build 2.19.605.1 CL123435 test-keys
Software 2.19.605.1
Browser WebKit 3.1
PRI 2.11_002
PRL 51866
ERI 5
While following the instructions posted, Step II-10.
Have yellow exclamation in Device Manager,
Get this window during update driver step:
Cannot Continue the Hardware Update Wizard
The wizard could not find a better match for your hardware than the software you currently have installed.
I do have usb_driver folder:
c:\AndroidSDK\android-adk-windows\usb_driver
has subfolder amd64 and i386 along with
android_winusb
androidwinusb86
androidwinusba64
source.properties
AndroidSDK has Installed Packages: Usb Driver package, revision 3
I haven't been able to finish the steps and get ROOT to work.
Any help is appreciated. Not very computer software programmer savvy but I follow directions well!
TIA.
and keep up the awsome work. the original phone I loaded 2.1 leak v.3. Loved it! Replaced/ warranty exchanged due to poor call reception and echo-ing on the other end.
have you tried the drivers from htcsync?
http://www.htc.com/www/SupportViewNews.aspx?dl_id=933&news_id=631
Went to that site, doesn't list Eris or model ADR6200.
My HTC Driver Installer is v. 2.0.7.008
When trying to run adb shell ...... "cant find device"
Since i have "test keys" listed in Build, don't I have 2.1 root? If so, am I needing to continue with the next step? which would be run the adb commands...correct? this is where I am running into a wall.
and it seems, from reading the guides, I am stuck in limbo since I don't have Amon's Recovery. I can't go back to 1.5 and start from square 1.
do you have htc sync installed? the dl is at the bottom of the page I linked to.
if so point to the drivers in the install directory.
I just did a reinstall of the drivers to make sure.
also make sure usb debugging is enabled on your phone.
indecently, my driver version is 2.0.7.1 dated 6/10/2009.
UPDATE: Success!
Apparently, the new HTC Sync loaded what it needed as far as updated drivers. I continued on with GUIDE: From stock 1.5 to the latest root 2.1 at running 'install root.bat.
(this time)Phone did what the instructions said it would.
Rebooting......
and there it is.
Now on to tethering, and beyond!
Thanks for your help and patience w/ another 'noob'.
Related
Hey, first of all these are the details of my phone:
Model number- HTC Hero
Firmware Version- 1.5
Baseband Version- 63.18.55.06JU_6.35.08.29
KERNERL VERSION- 2.6.27-430d1aea
Build Number- 2.73.771.73 CL#94055 release keys
Software version- 1.0.0.A6288
PS- Orange UK.
------
Now the problem is I can't create an image. I saw a guide that says that for build #2.73 and up you can't create an image so i need to downgrade first and then create the image and upgrade. I tried to downgrade and couldn't. I did everything as intended and in the middle of the downgrade installation I get the phone out of sync with the computer so I get that "please connect the USB to the phone" error and my phone is just stuck with 3 greed androids and a few scentences, and would not respond until i remove battery and re-insert then it returns to the original firmware version that came with the phone. Please help me!! I've been messing with this for too long. Thanks
PS:The error I'm getting while creating the image is when i start Flashrec the bottom button is "Backup Recovery Image" instead of "Resore Backup Image" and when I insert the /sd/recovery.img in the address like i see the Flash Image button but it's blackened and cannot be pressed.
emmm
anyone? i need help
You're following an old guide. Check out my one in my signature for a quicker and easier way to gain root and install a custom rom.
hmmm
i did everything as noted, everything went OK until the emulator part. In the emulator you noted I cannot seem to get the keyboard to show. I downloaded 3 different emulators and when i type "SU" it says "bla bla has root permission" and then the whole emulator freezes until i see the "force close" prompt with either Wait or Force Close. Tried waiting, tried force closing, tried moving to the next flash_image recovery line... and then I get []erroroutput[usage: flash_image partition file.img
First,you need maybie, to create a GoldCard. Use a 2gb. or 4 gb. sdcard ( no Kingston )for that. Search on internet " how to create a goldcard " for root your phone. Then, use flashrec and recovery image ( last versions ) and finally download and install a customRom. All you have need you find on internet, Good luck! Sorry for my english.
hey
HEy
I already tried that. My SD is already a goldcard i followed some guide on the internet.. and still when i open flashrec and do everything as told and insert the address of the image on my sdcard i see "Flash Image" in an unavailable button .
Some people said that in new versions i might have to downgrade and then create the image and then upgrade..(?)
THIS IS ALL SORTED...DESPITE HAVING A STOPPED ANDROID BOOTLOADER DEVICE...I DISCOVERED THAT I HAD TO USE THE CORRECT FASTBOOT COMMAND AND NOT THE ONE SHOWN....IE I HAD TO USE fastboot -i 0x413c flash recovery recovery.img
SO I JUST HAD THE ANDROID COMPOSITE ADB INTERFACE RUNNING AND BY USING THE 0X413C IN THE COMMAND IT WORKED...
hope somebody can stop me pulling my hair out!
Ive just taken posession of a Dell Streak. Came with the 1.6 android.
Have successfully done the OTA upgrade to Froyo 2.2. NICE
Successfully rooted using SuperOneClick 1.7 rageagainst the cage and allow nonmarket apps.
Want to put clockwork mod on..so can make full backups and perhaps try a rom or two!!
Have downloaded the latest dell drivers (R291096) and Sync Suite(R290209)...
Android Phone - ADB Inteface drivers all good
But i cant for the life of me get the Android Bootloader Interface going so I can use Fastboot commands.
Have tried XP 32bit and & Windows 7 64Bit with same result...have read lots n lots...but whatever i do i cannot get the Android Bootloader Interface to start....advice please my dear experts..
Baseband GAUWB 1A131921-EU
Kernel 2.6.32.9-perf
Build 12792
Thanks in advance...please dont shout out me ive read stuff all over the place and think this is to do with the official 2.2 =OTA upgrade problem...
Dell keepin me out of fastboot and messing with clockwork etc !!
hi there just been having the same problem for the last 2 days i was told that clock work mod wont work with dell streak ?????? look @ this line http://forum.xda-developers.com/showthread.php?t=840326
to boot in fast mode hold the camera button in and press the power button in @ the same time then tap fast boot mode also i have attached a file witch help me also here is a link what helped me 2 n8 when i bricked it in some way lol
http://streakdroid.com/?page_id=78
thanks for that info...i have just started reading through the streakdroid forums and QDL Tool (with drivers) sections...been at it a few hours...am really tired now...time for a rest before i do BRICK it lol......tried some other dell driver but no joy....usually always stick to my flashing in windows XP..for 32 bit and USB compatability but this is driving me nuts....thanks again....ive read read read and reread the pdf file.....
No worries i know what its like i was up till 2a, yesterday trying to do the same and 2 n8 got things working put a file on and it sort of bricked it and i have just sorted it out 20 mins ago
You have XP 64 bit? Isn't that a bit like a mythological beast OS that only exists in fairy tails and Redmond?
Hope you got this sorted out.
sorry should have read windows 7 64bit..only use xp in 32bit mode...all updates installed.
just trying again now...have uninstalled everything dell / drivers...used USBdeview to uninstall already set Android ports and old Qualcom ports from where i flashed my 3 usb stick, and the 3 drivers and software....downloading, again, the android 2.2 drivers and pc suite from dell.....will try again....i see 2.1 users and 1.6 users seem to have fastboot drivers working and clockwork mod....so will start playing all over again ..... at least the night is young!!!
oh bugger this im tired of going over things..guess the 319 version wont let you have proper drivers to "mess" around with the bootloader..ill revisit some time in the future
oh great decided to start again using a factory reset.....now all i get is process com.android.setupwizard has stopped unexepectedly. please try again..
cant get anything but a blank screen cos the setupwizard did not complete..
groan...
UPDATE 1345GMT.....downloaded Streak_319_12792_21.pkg .... renamed to update.pkg.....copied to root of sd card....booted into recovery and selected update from package.....am now back at 2.2 update and screen working...phew....now to spend rest of day setting it up again lol...wonder why doing a factory reset wont clear the caches?
I'm assuming you have sdk setup? If not give this a go great write up.
http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
Sent from Re-Engineered dInc
no not used the sdk files...just the official update which is downloadable....no probs..
Also..update....i have managed to follow the instructions and install StreakMod even though my Android Bootloader device is still not started..Different commands there than what i was using to try n put CWM on.....ill see how that goes...at least im making progress and have saved the Official 319 update package in case i need it another day!! thanks for comments and help on this irritating buisiness...
ALL SORTED NOW..APPARENTLY TO USE FASTBOOT YOU MUST INCLUDE THE DEVICE CODE SO THAT FASTBOOT KNOWS WHAT IT IS TALKING TO!
IE THE FULL PROPER COMMAND LINE IS fastboot -i 0x413c flash recovery recovery.img
CONSIDER THREAD CLOSED..THANKS TO ALL
Last update: solved... I was not doing the right thing and installing CLK over MAGLDR, confusing it with ClockWork. Stupid abbreviations and lack of sleep!
New problem: Task29 - completed, MAGLDR - installed, CLK - installed, CLK Install Recovery - done. Now I have various errors.
Before all this, I used to be able to boot into MAGLDR, select the Recovery option, and go into CLK to backup/update/install new ROM. Now, holding power + up keys just takes me to CLK which prints a lot of enumerated boot information as well as errors. Already tried reinstalling everything many times with the same result.
-------------
Old post: figured it out... just installed the drivers manually pointing Windows Device Manager to the driver folder.
I am reinstalling everything from scratch on my HTC HD2, and having executed Task29, I believe I need to reinstall Google drivers. I have the package on my hard drive, but there are no executables that seem to be doing anything to install the drivers onto my HD2 upon syncing it with the computer.
Is there some procedure I need to follow? HD2 Android NAND Kit application, for example, simply says to download the driver package and "run the executable" - so not very helpful in my case. I suppose the original package it mentions might have a working executable, but the site it's hosted on no longer operates, so I obtained Google Drivers for HD2 from other reputable links here.
Any help would be appreciated - thanks!
[how-to] another advenure: From German "unrootable" 3.2 build10 to rooted 4.0.3R5a
Hi there,
after about 5 nights, this "morning" at 4am, I won over Sony and M$ :highfive:
So i want to write this little tutorial for the ones, who might still be stuck on 3.2 build10.
I bought my tablet S 114DE/S, German with 3G, right before Xmas. Thought, it would be an easy task ... ha-ha.
First thing I read was, that build 10 is unrootable. F#?!
Started reading everyhing on XDA and other forums. Also read Cat McGowan's "adventure". Tried to do it like him... but as my tablet is German region an region changer only works with rooted devices, I could not flash his US files. But the idea was born.
Found the thread: XDA Developers > Sony Tablet S > Tablet S General > NEW Update Links Inc Tablet S/P R5A & Xperia S R6b
The "oldest" downloadable German original Sony FW was ICS R2a. I was not sure if this was still rootable, i would have liked to find a R1a, but what the heck, worst case is a not rooted ICS, which is still better than an unrooted 3.2!!
Downloaded, put on SD an flashed with recovery mode. Went fine.
So all you need to get away from "unrootable" build10 is a rootable original FW for YOUR tablet's country code!!! Hope you find one. There are many in the above mentioned thread.
Installed ADB automatic installer, no probs. i have Windows 7 pro 64bit.
Would be really NICE to add a clearly visible advice to also install the ADB driver (most likely MANUALLY on some systems) before using any special tools... I did not see any advice, maybe I was blind...
At least tell everybody to check, if the driver is working, by booting in recovery and looking at Windows device manager.
Problem is to find the right driver...if you simply choose the INF like for the "normal boot" ADB device, W7/64 does not install properly, you can get an error... really badly misleading message comes from Windows: It's telling something about MTP device ... well, actually you need the ADB driver!! Took me some hours... but as I found that problem only later, it took me 2 nights before, trying Condi's flasher and AIO 5.3 tool, without success...
OK, ADB drivers were installed (I only had the normal boot drivers at that time).
Downloaded Condi's AIO 5.3 tool, used the "root device" option, everything went OK, I was really happy! Rooted ICS R2a. First big step. 3.2 build10 unrootable? Not really... you only need a rootable original Sony firmware, flash it the normal way.
Then, I wanted to upgrade to R5a of course!
Condi's flasher 2.2. did not work. Maybe also because of the missing ADB driver for recovery mode?? Dunno. It always ended with: System.zip and all the other zips "not found", although I also tried pushing them manually to the internal SD before... when checking later, they disappeared.
Tried AIO 5.3 and custom signed zip. Always stuck in recovery mode with "Status 7" Error, like described in post #72 in this post:
XDA Developers > Sony Tablet S > Tablet S Android Development > [FW R5A WIFI/3G] NEW! custom preROOTed newest stock nbx03 R5A with R1A's recovery!
Also here, it would be nice to bring the advice (install ADB drivers for recovery mode) BEFORE! It does NOT appear in the tool's window IF you are stuck!
After finding the right driver, it was no problem installing the prerooted double-flash zip with the AIO tool... Also here, do not panic when the "Status7" Error appears... it's normal, it disappears after a few seconds and at the same time, the hint about the driver comes up in the command window...
Btw I had no problems with missing google market or apps or any Sony applications. Google play is working, also Sony remote etc.
OK, that's it!
Waiting for 4.2
Have fun with your rooted Sonys!
Many thanks to Condi and the other devs for the tools, videos, tutorials... they may not be perfect, but without, it would be impossible for guys like me :angel:
Daniel
I bought a " Figo Atrium 5.5 ". The Figo website has instructions to flash the device to 6.0 Marshmallow instead of Lollipop. I believe these instructions are incomplete. Here is the link, I'll detail for you what I've tried using their recommended software SPFlash https://support.figoglobal.com/support/solutions/articles/16000047848-android-6-0-atrium-5-5
I downloaded and extracted both files on Windows 8 64 bit desktop, the SPFlash tool and the other the Atrium ROM itself. The very first instruction is installing the drivers which I do using the install.bat file from the "Driver_Auto_Installer_v1.352.00" folder. I believe my install fails at this point. Opening the Flash_Tool exe after installing the drivers (the tool does say they installed properly) I never get any information in the Chip Info in the Flash_Tool. It appears those drivers are not installed properly.
Researching this, I came across videos that suggest the drivers were not being installed properly because the drivers are Not digitally signed. I followed the instructions to fix the problem by booting to Advanced StartUp options then choosing to run the OS with digital signing checking disabled. Now on installing the drivers I get the popup asking me if I am sure I want to install the drivers I choose Install Anyway. The driver install tool just sits there for a couple of minutes doing nothing, then the popup message comes back asking again, am I sure I want to install the drivers. This is an endless loop, the application never attempts to install the drivers. The phone is plugged into the the PC at this point because I assume it must be for windows to see the phone. Note, at no time except the End of the instructions does it tell me to have the phone plugged in. This confuses me greatly. I don't know if the phone should be plugged into the pc at this point or not. Can someone who if used to doing these kinda flash jobs look over these instructions and help me figure out what I'm doing wrong. Thank you. I will do my best to answer back with more info, I'll be home all day watching this thread.
( btw, the forum on that site is moderated. I have tried over two weeks ago to post forum messages about my issues, but the moderators never posted any of my messages - it seems customer service is non existent)
Please mark this as Solved. I fixed my problem with a bit more research. Figo gives incomplete and also incorrect information on upgrading the Rom ( as you can see) Nowhere do they tell you in the instructions that you need USB Debugging Enabled or how to do it. This is a critical step or the drivers will never see the phone. The drivers did correctly install the first time as I suggested. That was the incomplete information. The incorrect information is this: They tell you to take the battery out to flash the device - which will never work because the phone needs power for the drivers to flash the device. What you have to do while the phone is On and Connected to PC is remove the battery then put it back in - then the phone will flash. This is critical step 2 they were wrong about. I suspect it has something to do with a bad Chinese translation.