Hi people,
I'm trying to write this message with links to the relevant guides I used, but since this is my first post I can't add links to this. I hope it is still kinda clear what I mean.
I've got an HTC Desire Z (or G2 as I think it is called in the US). I bought it new from a store here in the Netherlands without any contract so there is no connection with any carrier. I now want to root my phone so that I can put Cyanogen mod on it. For this I followed some guides which led me to do a firmware downgrade. A guide on the cyanogenmod website worked all well, until I got to step 8: "Select Bootloader to flash the 1.34.707.3 firmware.". After doing this my phone gives an error saying the following:
CID incorrect!
Update Fail!
Press power to reboot.
So after some searching I found that I need to spoof a CID using a "Goldcard". And here I'm kind stuck.
I searched around for goldcards and I found a lot of guides using some sort of Goldcardtool. This however, only works on windows, and since I am on (Ubuntu) Linux I can't use that. I tried to follow a youtube guide, which when typing "cat /sys/class/mmc_host/mmc1/mmc1:*/cid", ended in a "No such file or directory" error.
I then found a guide on the Droid-den website ("Android Guide: How To Create a Gold Card") with which I created two .img files after which I needed to do some hex editing. For this I installed a hex editor called ghex. I can open the .img files I downloaded, but I am not able to select my micro sd card in the hexeditor. I tried Bless hex editor as well, but no luck there either.
So my questions:
Do I absolutely have to use a goldcard (even though my phone is not carrier branded) or am I simply doing something wrong?
If absolutely needed, what am I doing wrong in creating the goldcard? Is there another (preferably easy) way to create a goldcard on Ubuntu?
All tips and hints are welcome!
Hi!
Use "cat /sys/class/mmc_host/mmc1/mmc2:*/cid" or "cat /sys/class/mmc_host/mmc2/mmc2:*/cid"
Related
I have searched these information because I'm a Mac user.
Ok. I have searched the web for a whole day, and I've got the information I need. I've already Application unlocked my phone by editing the registry, and SuperCID unlocked my phone by installing the Cert.cab (I'm really not sure about this, because you will click on something like "Set CID" on a PC).
These are the links and information that I've found:
http://forum.xda-developers.com/showpost.php?p=1018902&postcount=6
http://forum.xda-developers.com/showthread.php?t=295735
http://forum.xda-developers.com/archive/index.php/t-315977.html
The first link is for Typhoon, but I guess it's only the same process used with Tornado. The second link is for Hermes, also used the same process for upgrading. The third one is just some random link about Crossbow on smartphones.
So, I have the files from karhoe's guide:
http://karhoe.net/myfiles/illi_WM6.1_remade_by_rickwyatt_v2a.zip
It's the WM6.1 Standard made by rickwyatt. I found the "nk.nbf" file, and renamed it to "TORNIMG.nbf". I formatted my miniSD card to FAT32. It also says on the links above that you should copy the "xxxxIMG.nbf" (xxxx means the first four letters of your device) in the root folder of your miniSD card, and access the bootloader on your phone by holding down the camera button together with the comm manager button and by hitting the power button. Confirm flashing on screen, and wait until the process is finished (do not reset it, will take about 30min).
I haven't done this yet 'cause I'm not sure if my phone is SuperCID.
My questions are:
1. I have my phone application unlocked by editing something on the registry, and installed "Cert.cab" from SPV-Services. But I'm not sure if my phone is SuperCID, 'cause I think you'll be doing something like this: http://karhoe.net/images/stories/wm6upgrade/step6.jpg
2. Am I going to brick my phone by doing this?
1. No your phone doesn't superCid by installing cert.cab!! You must use SPVservices for it!!
Guys, I bought my T-Mobile G1 Black in Germany few days ago. Shop was not official one, so when I came home and tried to modify it, I came across a problem that whatever "update.zip" file I am trying (official, dev, jfk) - it's always saying something like "Verification Failed". What should I do?
Moreover, when I check my phone's software version, it goes like this:
Firmware v1.1, Build Number 123099
So no RC# and what-so-ever... No idea how to root it.
You have to root it first before flashing another firmware.... Read and learn....
http://forum.xda-developers.com/showthread.php?t=442480
and don't forget to read here:
http://forum.xda-developers.com/showthread.php?t=485364&highlight=continental
and you will need this
Have two questions: in instruction it says "dd it to SD card", what "dd" stands for? I have Mac - what can I do? And, I got my CID by opening CID file with ASTRO (in Text Edit), and I got that number: "0353445355303247809035120d008be0" should I change it before getting my GoldCard through http://revskills.de/pages/goldcard.html?
Thanks in advance
Follow my Guide here:
http://forum.xda-developers.com/showpost.php?p=3720420&postcount=274
Man, I've never used Linux and in your instruction you are saying "Used dd for writing the goldcard.img: (goldcard.img is on the desktop)
cd Desktop
dd if=goldcard.img of=/dev/sdb"
What should I do here? What is DD?
Thx
I am trying to follow this article to install android on my XDA serra
wiki.flexion.org/XDASerra.html#3.0
I downloaded the android system updates from this site, but all I have is a system.ext2 file and nothing else ?
Am I downloading wrong file? I cannot find anything else that says "android os", so i'm not sure what I should be downloading here.
russmichaels said:
I am trying to follow this article to install android on my XDA serra
wiki.flexion.org/XDASerra.html#3.0
I downloaded the android system updates from this site, but all I have is a system.ext2 file and nothing else ?
Am I downloading wrong file? I cannot find anything else that says "android os", so i'm not sure what I should be downloading here.
Click to expand...
Click to collapse
If I'm not mistaken, the XDA Serra is just a rebadged HTC Touch Pro right?
Have a look here, it's the Android thread for the TP. You should be able to find a complete flashing package there (I even saw a Gingerbread one). This forum has been moved from the front page, but you'll find it under 'legacy devices'
Good luck, and welcome to XDA
Yes it is a rebranded htc touch.
I finally discovered that the ext2 file can only be used on Linux, which seems daft if you ask me as most people wanting to do this will be using windows. anyway I finally found a tool that allowed me to extract the file on windows so I have progressed past that block. However I could not get it working using aforementioned guide.
So I carried on searching and I did find a guide on xda-developers as well and tried to follow that, but there are files missing in the download link on this site, the startup files and folder are missing, as are many other key files so I could not follow that guide either.
I finally found a guide with a working download with all files and got it all installed, selected the right startup file for my phone and got Haret to run, the install seems to happen, but I am just left at command prompt, it doesn't boot into Android. I cannot read what it says on the screen as the text is too small, so I have no idea what the problem is.
russmichaels said:
Yes it is a rebranded htc touch.
I finally discovered that the ext2 file can only be used on Linux, which seems daft if you ask me as most people wanting to do this will be using windows. anyway I finally found a tool that allowed me to extract the file on windows so I have progressed past that block. However I could not get it working using aforementioned guide.
So I carried on searching and I did find a guide on xda-developers as well and tried to follow that, but there are files missing in the download link on this site, the startup files and folder are missing, as are many other key files so I could not follow that guide either.
I finally found a guide with a working download with all files and got it all installed, selected the right startup file for my phone and got Haret to run, the install seems to happen, but I am just left at command prompt, it doesn't boot into Android. I cannot read what it says on the screen as the text is too small, so I have no idea what the problem is.
Click to expand...
Click to collapse
Sounds like you're hanging at the bootloader. Wipe the SD card, reformat it and try what you did again. I had a similar issue running an SD build on my HD2 first time. Let me know how you get on. PM me if you need to
Hello, I just started the process of rooting my dinc2 today. One of my friends has an HTC phone, not sure which, but he used a one-click rooter for it after unlocking the bootloader from htcdev.com
I tried doing it the same way, but with no success. After searching for other ways to root my phone, i stumbled across this thread( http://forum.xda-developers.com/showthread.php?t=1751796 ), after downloading everything I needed from the second post (because i unlocked my bootloader using htcdev) and extracting the zips it said to extract into c:\Android i opened command prompt and started copying/pasting. however; on the first line i immediately got an error,
" c:\Android>md5sums RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra dio_1.09.0
1.0622_NV_VZW1.92_release_199487_si.zip
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
Error: Unable to read file/directory RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.6
05.3_Ra "
the post told me i should have gotten "Result should be cea499f51b40055ffd118960e1e73255, if it isn't, redownload the miniadb zip." so i did, restarted the whole process. i had my phone on usb debugging mode. i uninstalled HTC Sync from my pc, etc. I'm still getting the same error. So I tried just skipping it, got down to where i flash the recovery image over to the sd card and it fails within a second. I was hoping to post this in that thread so i'd get a better answer, but i'm not allowed to yet.
any help would be amazing.
I'll be checking this often, if you'd rather email me that's fine. just PM for the email address. If I don't have enough details, just ask me what you need to know and i'll try my best to answer them, thanks.
edit****************************************
i found the issue, on the first line of code in the 2nd post on the thread that i'm following. there is a space where there should not be a space.
Hi
I am trying to install the Jellybean 4.1.1 ROM on my rooted Nexus S.
The history of my attempts so far are here: Rooted Nexus S OTA Upgrade to 4.1 http://forum.xda-developers.com/showthread.php?t=1833420
I have downloaded the "image-soju-jro03e.zip" form the Android open source website, and used the Nexus Root Toolkit to install it.
This failed, and I attempted to install the image using ROM Manager.
This also failed, and produced a lengthy Recovery Log.
I have read through it and it seems to be telling me that certain files or folders are missing from the download.
e.g can't open /dev/tty0: No such file or directory
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
can't find /sd-ext in /etc/fstab
Is that what this means?
How can I correct it?
The full log is here: https://docs.google.com/document/d/1HWeYsXPnppQbgoloz72RH81E8a479LBmvYXIlzYPETo/edit
S
Help with recovery log
Hello?
Can anyone help me to understand this recovery log?
Should I direct my question to the "ROM Manager" people?
I have tried without success to install JB 4.1.1 from the Google Android Images page, and I think it must because something is missing from the file structure of my current ROM.
Am I on the right track?
M S
First of all, what variant of the Nexus S do you have? If you turn off the device and remove the battery, it should be on the sticker showing the device serial number.
Once you find that, you can head over to this link and look for the right image for your device:
http://www.randomphantasmagoria.com/firmware/nexus-s/
I'm assuming that since you're from 4.0.4, you just need to flash the update zip. If you're device is rooted, chances are you have ClockworkMod installed. If so, maybe you should just consider putting in a custom ROM. Flashing it should be much faster. I'd be glad to help you if you can give more info on your variant, current software state (version, rooted/not rooted, etc).
new hope
nightsky87 said:
First of all, what variant of the Nexus S do you have? If you turn off the device and remove the battery, it should be on the sticker showing the device serial number.
Once you find that, you can head over to this link and look for the right image for your device:
http://www.randomphantasmagoria.com/firmware/nexus-s/
I'm assuming that since you're from 4.0.4, you just need to flash the update zip. If you're device is rooted, chances are you have ClockworkMod installed. If so, maybe you should just consider putting in a custom ROM. Flashing it should be much faster. I'd be glad to help you if you can give more info on your variant, current software state (version, rooted/not rooted, etc).
Click to expand...
Click to collapse
Hello nightsky ( is that like, "nice guy",?) thanks for taking a look.
My phone is a Nexus S i9020, no suffix.
It is running Andriod 4.0.4 ICS. It is "rooted" and "unlocked".
I have Clockwork Mod v.6.0.1.0. Superuser v.3.1.3. and ROM Manager v.5.0.2.0.
I have tried over and over again without success to upgrade to JB 4.1.1 and I am getting sick and tired of this stupid game.
I would be happy to just stick with ICS 4.0.4, but every week, the phone tells me that an "update is available", and I have to dismiss the message every time I look at the phone! When I tried to apply the update It used to crash, requiring a battery-pull reset. Now I have CWM it takes over and says "failed to verify file signature", "install untrusted package?"
If I press on and install, it fails and the android is on its back with a red triangle on its belly.
If you look at the posts I have linked to, I have been on a steep learning curve regarding ROM flashing, and I understand the basic idea, its just that when I follow the instructions given on the forum, It doesn't happen that way for me and I suspect that there is something wrong with the file structure on my phone. That is why I have posted the link to my recovery log.
If you can help, please reply.
I have had a look at the "Random Phantasmogoria" site that you recommend, is it offering anything different than the Google developers site https://developers.google.com/android/nexus/images that I have downlooaded my image from?
MS
another version!
PS I have just had a look at the Google Dev. site and there appears to be a new version of 4.1.1 called JRO03L.
My next attempt, I'll try that.
MS
goodnight
Factory images are not to be installed with ROM manager/recovery.
They are factory images that are installed with fastboot.
Your solution is a rather simple but may seem complex to you at first. If that makes sense.
First screw all those one click/ ROM manager crap.
Either download the SDK and get the platform tools add on ( quides are all the over the place). Or use one of those zips people make that include fastboot.exe and a driver or whatnot.
Boot the phone into the bootloader. Connect it to the PC. Open a command prompt in the directory with fastboot.exe and the factory images....
Type in fastboot devices. If your serial comes up just follow the commands in the quide. Re root if you want.
What you where attempting to do reminds me of kids in the arcades just smashing buttons and hoping something works
I am not going to right a guide m. There are stickies and somebody actually made a very noon friendly explanation the other day on here somewhere. Sorry don't know where at the moment.
If there is a specific part or something in particular you don't get let me / us know.
Moral of the story is a once a computer is set up with fastboot properly it is very simple.
jus to add on the post above. the instruction to install the factory images are on the same page where you downloaded the image in question.
and there is something to be wary of : flashing the factory image will WIPE the phone CLEAN (except what's on the usb storage o/c).
albundy2010 said:
Factory images are not to be installed with ROM manager/recovery.
They are factory images that are installed with fastboot.
Your solution is a rather simple but may seem complex to you at first. If that makes sense.
First screw all those one click/ ROM manager crap.
Either download the SDK and get the platform tools add on ( quides are all the over the place). Or use one of those zips people make that include fastboot.exe and a driver or whatnot.
Boot the phone into the bootloader. Connect it to the PC. Open a command prompt in the directory with fastboot.exe and the factory images....
Type in fastboot devices. If your serial comes up just follow the commands in the quide. Re root if you want.
What you where attempting to do reminds me of kids in the arcades just smashing buttons and hoping something works
I am not going to right a guide m. There are stickies and somebody actually made a very noon friendly explanation the other day on here somewhere. Sorry don't know where at the moment.
If there is a specific part or something in particular you don't get let me / us know.
Moral of the story is a once a computer is set up with fastboot properly it is very simple.
Click to expand...
Click to collapse
Smashing buttons and hoping something works?
That's not very nice, or fair!
If you take the trouble to read my post, and the linked previous posts, you will see that I am trying my best to follow the instructions given on this forum, where I hoped to find knowledgeable professionals who contribute their valuable time free of charge to help noobs like me.
So far I have followed the instructions, only to get something other than the result described. This is why I am asking for your help to understand the recovery log, so that I can work out for myself what went wrong, and what I should change next time to get it right.
At this point in the journey I am still unsure about backup. I have "backed up" using the nexus root tool kit, which is a Nandroid back up, and I have "backed up" using ROM manager, but Titanium Back-Up does not recognise the backups and wants me to "back up" some more. After all this is over will I be able to clear out all the dross that my phone memory is accruing? Is there any point backing up Apps like "Google Earth" when I can easily download them from the Play Store after I have my new OS? etc... etc...
Anyway, I am going to try again, this time with the new JRO03L image, and this time I shall do it Command Line style instead of the "one click crap", as you recommend, my friend. I'll let you know how I get on.
MS