[Q] Stuck at boot screen with S-ON - G2 and Desire Z Q&A, Help & Troubleshooting

Hi, everybody!
As a long-time-lurker I find myself now in the position to need serious help. I'm completely new to flashing and all that stuff, so you can imagine how happy I was when I managed to unlock, root and install a custum rom on my TF700 tablet. When I proudly told that a friend of mine, he handed me his old, half-bricked (I assume) Desire Z, where he tried to do the same and... well it ended up pretty much FUBAR. But he said I can play around with it if I want and keep it if I get it running again. So much for motivation!
Sooo, the problem with the whole thing:
When booting the phone won't pass the HTC boot-screen.
What has been done to the poor phone:
The bootloader was unlocked
A custom recovery was installed
The version-info was altered (at least it shows version 1.00.000.0 in the RUU-updater)
He tried to install a custom rom while still being S-ON, which seems to be the cause of all the trouble.
What I have tried:
Different recovery-versions (at least THEY work fine)
Install the original ROM* with a RUU.exe-file (fails after sending it to the phone with Error [155] )
Install the original ROM* with fastboot and a zip (fails with an "remote: 99 unknown fail" error while info parsing)
Install the original ROM* with bootloader and a PC10IMG.zip on the SD-card (fails after reading the zip with invalid file or something like that)
Install the original ROM and different custom roms through the recovery (some seem to install fine but in the end is still freezes on the boot screen)
Tried the unlock/root/downgrade process following Strawmetal's all-in-one guide, with no success whatsoever.
Issues with the all-in-one-guide:
First of all, since the phone doesn't boot, I can only access the adb-tool when in Recovery (right now using CWM v5.8.1.0)
But already trying the first command (adb shell cat /dev/msm_rotator) I don't get the /dev/msm_rotator: invalid length-response, but cat: read error: Invalid argument instead.
Strangely enough, when entering the adb shell-command, the lines don't start with "$", but with "~ #".
So I thought, maybe temp root already has been activated. That's why I tried to continue with the creation of a goldcard. Didn't work either. Here is a copy of the process:
Code:
C:\platform-tools>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
SH0C3RT00139 recovery
C:\platform-tools>adb push misc_version /data/local/tmp/misc_version
adb server is out of date. killing...
* daemon started successfully *
211 KB/s (15837 bytes in 0.073s)
C:\platform-tools>adb push flashgc /data/local/tmp/flashgc
492 KB/s (712688 bytes in 1.414s)
C:\platform-tools>adb shell chmod 777 /data/local/tmp/*
C:\platform-tools>adb shell
~ # cd /data/local/tmp
cd /data/local/tmp
/data/local/tmp # ./misc_version -s 1.00.000.0
./misc_version -s 1.00.000.0
/sbin/sh: ./misc_version: not found
/data/local/tmp #
As for further inormation:
The bootloader shows this info here
Code:
****Unlocked****
Vision pvt ship s-on
HBOOT-0.85.0015
MICROP-0425
RADIO-26.10.04.03_M
eMMC-boot
Dec 20 2011,16:21:13
There is no option for System Info, but the Image CRC output is as follows:
Code:
osbl: 0x7EE4ED8C
amss: 0xB7A63815
hboot: 0x6659C31C
boot: 0x4CB9BC27
recovery: 0x97231AF1
system: 0x3B27E2FE
Also, I cannot flash single radio or hboot files with fastboot commands, because it gives me an remote: signature verify fail error every time.
So the question is: what should I do now? Any hope? Or did I just receive a nice paperweight? Any help is highly appreciated!
* tried the RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2_Radio_12.56.60.25_26.10.04.03_M_release_199043_signed and RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e_26.03.02.26_M_release_155556_signed roms, both as *.exe and extracted zip.

So for now the issue may be as simple as needing to flash the kernel from fastboot after flashing the ROM in recovery. Try a known stable ROM like cm7 and flash it from recovery. Then reboot to bootloader and flash the kernel in fastboot
fastboot flash boot boot.img
(Extract the boot image from ROM.zip)
Then reboot, if this works then good! From there I would highly recommend to go back to strawmetals guide and downgrade and gain true radio s-off via the gfree exploit.
More info and ROM links can be found here
http://forum.xda-developers.com/showthread.php?t=2348266
Happy flashing!
Sent from my Nexus 4 using XDA Premium 4 mobile app

Well... it really was as simple as that, for the most part! Thank you a lot, demkantor!
Flashing CW7 and the kernel afterwards worked without any issue. I did, however, ran into some difficulties afterwards. I'm just going to post them here, because any issue fed into Google usually leads to xda, so maybe it will help someone as noobish as I am, if he comes across this post.
I tried to follow Strawmetal's PDF-guide to downgrade after flashing CW7 and it went fine up to the point I needed to flash an old stock-rom. I think I tried pretty much every single one from shipped-roms, but neither the manual fastboot-method nor the automated bootloader-version worked. They still aborted before even starting to flash.
Well, after reading through different topics here, I stumbled upon one little, and yet incredible important piece of information that wasn't mentioned in the PDF. I needed to re-lock the bootloader with the
Code:
fastboot oem lock
command, because the bootloader was unlocked via HTCdev.
NOW the bootloader method worked like a charm.
The next thing that gave me some troubles was installing the PureKat Beta 4 rom. I knew I would need an updated recovery, so I went with 4ext touch v1.0.0.6 RC3. Turns out, it didn't work, because it apparently identified my phone as an "ACE" and aborted the installation, because the rom package is meant for the "Vision". Changing the recovery to TWRP 2.6.3.0 however did the trick.
Sooo... long story short:
I'm happy! Now I'm really considering flashing my 4X HD-phone too... XD

Glad it all worked! its always nice to see someone fix their issues by doing the research and then posting how they did it (so the next guy can learn) so great job! If you want a lot of info quick about the dz just go through that thread I linked as for the most part it will have all the important info you will need.
Happy flashing!
Sent from my Nexus 7 using XDA Premium 4 mobile app

hi shin-baka do u have any sound distortion problem in purekat beta 4 ?? coz I tried so many kitkat ROMs but the same problem comes out. reply plz.

Related

[Q] Desire Z with 2.42.405.2 Able to downgrade? ( i'm able to temproot )

Hi all
I have a European HTC Desire Z with this info:
Android 2.3.3
Sense 2.1
Build 2.42.495.2
Vision PVT Ship S-ON
Hboot-0.85.0013
MicroP-0425
Radio 26.10.04.03_M
eMMC-boot
Apr 11 2011,23:36:27
I am able to temproot this phone with the method provided here:
http://forum.xda-developers.com/showpost.php?p=15851661&postcount=1
using the code:
Code:
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
However the downgrading part fails on me.
After entering the bootloader menu is scans the SDCARD and finds the PC10IMG.zip
telling me: loading...[PC10IMG.zip], after that it's saying: Checking..[PC10IMG.zip].
After checking it just goes back to the Menu without asking me to update etc.
I did however changed the misc_version and followed the guide precisely.
I searched and found some Threads saying this version isn't rootable yet. though they were couple months old, and I am able to get temp root. it should be do-able right?
Can someone please confirm this and tell me how to, or what i'm doing wrong and let this baby free.
I followed the guide to the letter, without changing misc_version or anything, and I managed to downgrade and root without problems on first try. Same version as you, Desire Z bought in Poland.
Just be sure to grab the file for Desire Z and not for T-Mobile G2 and it should work
costipl said:
Just be sure to grab the file for Desire Z and not for T-Mobile G2 and it should work
Click to expand...
Click to collapse
What file are you referring to here?
Also, how is it possible to downgrade without changing the misc_version, i thought it was all about changing that in order to make it work haha.
Sorry, I think I misunderstood your post...
I did this to change misc_version:
Code:
$ adb push misc_version /data/local/tmp/misc_version
$ adb shell chmod 777 /data/local/tmp/misc_version
$ adb shell
# /data/local/tmp/misc_version -s 1.00.000.0
I assumed you changed the "1.00.000.0" to something else (while browsing the forum I found in some threads that people used a different value on DZ).
As for the file I was referring to, I meant the stock rom image - 1.34.405.5_PC10IMG.zip
Maybe you grabbed the file "PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09 b_26.02.01.15_M2_release_149459_signed.zip", which is for G2?
Other than that, I'm not familiar enough with the bootloader to be of any help.
costipl said:
Sorry, I think I misunderstood your post...
I did this to change misc_version:
Code:
$ adb push misc_version /data/local/tmp/misc_version
$ adb shell chmod 777 /data/local/tmp/misc_version
$ adb shell
# /data/local/tmp/misc_version -s 1.00.000.0
I assumed you changed the "1.00.000.0" to something else (while browsing the forum I found in some threads that people used a different value on DZ).
As for the file I was referring to, I meant the stock rom image - 1.34.405.5_PC10IMG.zip
Maybe you grabbed the file "PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09 b_26.02.01.15_M2_release_149459_signed.zip", which is for G2?
Other than that, I'm not familiar enough with the bootloader to be of any help.
Click to expand...
Click to collapse
I redownloaded the zip file and you just made my day i had a other zip from another thread. but with the exact same name.. maybe corrupted ? THANKS!
Radio's get flashed AFTER you flash your ROM, not before ;P
Remember to rename your PC10IMG.zip to something else after you're done rooting/installing a new ROM, cos if anything happens and your phone crashes and you need to enter recovery, having PC10IMG.zip on the root of your SD will ensure that you never get into recovery
Power + Vol Down boots into bootloader, and it automatically scans for updates, PC10IMG.zip being one of them. Only when there are no update files on SD root will it give you a choice of booting into Recovery to well, recover your phone

[Q] Rooting problems with Desire Z (Android 2.3.3)

I have a problem with my rooting procedure and my HTC Desire Z
After i put in the bold underlined command I get a message:
Failed to set prot mask (Inappropriate ioctl for devices)
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
I tried the Visionary+ method too but that doesnt work either - gets stuck on rooting device please wait screen.
SuperOneClick method didnt work too.
My phone has Android 2.3.3 installed by default so I tried GingerBreak but it was useless.
You need to downgrade. Don't use visionary ever
Sent from my HTC Vision using xda premium
follow this guide http://forum.xda-developers.com/showthread.php?t=1178912
-Nipqer
Thx for the answer. The downgrade like described in http://forum.xda-developers.com/showthread.php?t=1178912 did it.
Do I have to downgrade to unroot my phone back into stock? I used visionary perm root and I'm kind of scared something might happen to my phone. I mean everything is working fine. I'm running Virtuous Quattro ICS and everything feels ok. Does this apply or can I be directed elsewhere please.
Sent from my HTC Desire Z using xda premium
No one knows what the hell visionary does to your device.
I'd say flash a stock RUU, should remove all traces of root.
-Nipqer
help needed urgently for downgrading HTC G2
Nipqer said:
follow this guide http://forum.xda-developers.com/showthread.php?t=1178912
-Nipqer
Click to expand...
Click to collapse
help needed urgently ...
i followed the above forum but i got stuck in last step
....
Code:
> fastboot oem rebootRUU
Your phone should now reboot into a black screen with a gray/silver "HTC" logo on it.
Next we flash the Stock Rom. This may take a few minutes as it transfers the file to the phone then attemps to update (downgrade).
Code:
> fastboot flash zip StockRom.zip
In rare cases the flash stops and the user gets a warning to repeat the flash immediately - no panic, just run the " fastboot flash zip StockRom.zip" (only this command, not the rebootRUU one) again and it will work.
....
after this step some how i got error .. as per instructions i tried many times but no luck .. now my phone keep on restarting with four warning icons in corners with HTC icon ... any help will be appreciated ....
my phone mode is HTC G2
ooooh thats the strange ruu mode, its pretty easy to get out of.
first you need to turn your phone on, plug it in, open a cmd and run 'fastboot oem boot'
That'll get your phone up and running.
Then you need to download misc_version 0.4 push it to /data/local/tmp, get temp-root (run psneuter/fre3vo/zergRush) and run misc_version with:
./misc_version -r off
Then your phone will be back to normal.
-Nipqer

[Q]Help stuck on fastboot and cwm

Hi this might be a noobish question but i cant find the answer anywhare:
so here's the problem i was trying to fix a badly installed rom, so i wiped the phones storage I then tried to kick myself when i realized that i had just deleted my backup and all the data on the phones internal storage, so now i can only get onto fastboot and clockworkmod recovery 5.8.3.1.
So is there a way to flash a rom in fastboot usb, or mount the phones internal storage so i can copy in a rom zip?
I would be grateful for any help
There is an option in cwm to mount storage you can try that not sure if they work tho.
Sent from my HTC One X using XDA Premium HD app
malcovitch said:
There is an option in cwm to mount storage you can try that not sure if they work tho.
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
It will not work.
What you can do other than flashing a RUU is:
Boot to fastboot
fastboot boot CWM_recovery_full name.img
Once it boot to recovery
adb shell
adb push rom_name.zip /sdcard
It will take some times to finish as the rom_name.zip is big.
Once complete, you can flash the rom_name.zip as usual
To make it easier, change the rom_name.zip to update.zip, so you can
adb push update.zip /sdcard
Thank you I have done as you said but i must be doing something wrong because i get this error:
C:\Documents and Settings\me\Desktop\Android>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # adb push update.zip /sdcard
adb push update.zip /sdcard
/sbin/sh: adb: not found
~ #
(The update.zip is Android_Revolution_HD-One_X_5.1.0.zip)
do you think it could be a problem with my adb.exe or something on the phone?
did you do the "fastboot boot CWM_recovery_full name.img"
going to recovery via hboot will not work.
you need to fastboot boot recovery
and it is adb devices , not adb shell... sorry
see this : http://forum.xda-developers.com/showpost.php?p=25774374&postcount=24
yes that's how i got to cwm as below
C:\Documents and Settings\me\Desktop\Android>fastboot boot recovery-clockwork
-touch-5.8.3.1-endeavoru.img
downloading 'boot.img'...
OKAY [ 0.771s]
booting...
OKAY [ 0.010s]
finished. total time: 0.781s
C:\Documents and Settings\me\Desktop\Android>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # adb push update.zip /sdcard
adb push update.zip /sdcard
/sbin/sh: adb: not found
~ #
River825 said:
yes that's how i got to cwm as below
C:\Documents and Settings\me\Desktop\Android>fastboot boot recovery-clockwork
-touch-5.8.3.1-endeavoru.img
downloading 'boot.img'...
OKAY [ 0.771s]
booting...
OKAY [ 0.010s]
finished. total time: 0.781s
C:\Documents and Settings\me\Desktop\Android>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # adb push update.zip /sdcard
adb push update.zip /sdcard
/sbin/sh: adb: not found
~ #
Click to expand...
Click to collapse
my bad
C:\Documents and Settings\me\Desktop\Android>adb shell
change to
C:\Documents and Settings\me\Desktop\Android>adb devices
Then adb push rom.zip /sdcard
ok i think that worked but when trying to find the zip in cwm i just get "no files were found", but in the command prompt it looks like it was copied to the sd card:
C:\Documents and Settings\me\Desktop\Android>adb devices
List of devices attached
HT23WW118450 recovery
C:\Documents and Settings\me\Desktop\Android>adb push update.zip /sdcard
1586 KB/s (577044654 bytes in 355.290s)
That's wierd.
You mean that when you click "choose zip from sdcard" you have nothing in sdcard ?
yes clockworkmod says that the sd is empty.
I'm going to try again with a smaller file and maybe try and access the sd with a different recovery
River825 said:
yes clockworkmod says that the sd is empty.
I'm going to try again with a smaller file and maybe try and access the sd with a different recovery
Click to expand...
Click to collapse
No. It won't work as sdcard need to be manually mounted first.... that's why I said something about adb shell earlier.
I'll do the testing now:
my step will be:
fastboot boot xx-recovery.img
adb devices
adb shell
mount sdcard
open another cmd prompt
adb push xxx.zip /sdcard
will let you know in a short while
Just tested: this should be the correct way... I can see my xxx.zip when I choose : choose zip from sdcard
*you need to mount the sdcard first before adb push
thank you it worked fine I downloaded the zip to the sd and flashed the rom in cwm, but it didn't work and now i cant boot into recovery it just shows the revery screen for 1/2 a second, and reboots into the bootloader i tried flashing different recovery images but they didn't work.
Is there some way to wipe the phone recovery?
River825 said:
thank you it worked fine I downloaded the zip to the sd and flashed the rom in cwm, but it didn't work and now i cant boot into recovery it just shows the revery screen for 1/2 a second, and reboots into the bootloader i tried flashing different recovery images but they didn't work.
Is there some way to wipe the phone recovery?
Click to expand...
Click to collapse
Do:
fastboot erase cache
fastboot reboot-bootloader
Then press power once to go to hboot then select recovery. It should work.
Thank you
Thank you so much for all your advice i've just successfully flashed a rom and got my phone working again i was starting to fear for my phone.
Thanks again for all your help
ckpv5, when I try to follow your steps, I get "error: device not found" when doing adb shell in the command prompt? How do I fix that?
(My problem is that I formatted everything like an idiot in my phone and the internal sdcard seems to be unmounted or something like that)
Sam.Lambert said:
ckpv5, when I try to follow your steps, I get "error: device not found" when doing adb shell in the command prompt? How do I fix that?
(My problem is that I formatted everything like an idiot in my phone and the internal sdcard seems to be unmounted or something like that)
Click to expand...
Click to collapse
If you're on stock ROM, you don't have to do all the step, just simply flash RUU.
ckpv5 said:
If you're on stock ROM, you don't have to do all the step, just simply flash RUU.
Click to expand...
Click to collapse
I don't have the executable RUU for the Rogers handset, I only have a zip containing a bunch of img files and the executable RUU for the AT&T version (which didn't work, gave me ERROR [131]: Customer ID error or something like that).
Which the zipped RUU for the Rogers handset, I tried flashing the recovery_signed.img and boot_signed.img, relocking the bootloader and then flashing the system.img file but it would give me an error saying data length too large or something like that.
I really don't know what to do anymore
Sam.Lambert said:
I don't have the executable RUU for the Rogers handset, I only have a zip containing a bunch of img files and the executable RUU for the AT&T version (which didn't work, gave me ERROR [131]: Customer ID error or something like that).
Which the zipped RUU for the Rogers handset, I tried flashing the recovery_signed.img and boot_signed.img, relocking the bootloader and then flashing the system.img file but it would give me an error saying data length too large or something like that.
I really don't know what to do anymore
Click to expand...
Click to collapse
Which custom recovery is working for for your set ? Is the one from One X dev section works for you ? If it is not, I'm afraid unable to help you.
Which custom ROM that you use before the brick ?
ckpv5 said:
Which custom recovery is working for for your set ? Is the one from One X dev section works for you ? If it is not, I'm afraid unable to help you.
Which custom ROM that you use before the brick ?
Click to expand...
Click to collapse
Pretty much the only one available for the Evita One X (this one doesn't work if that's the one you are talking about http://forum.xda-developers.com/showthread.php?t=1594819):
http://www.modaco.com/topic/354009-interim-clockworkmod-recovery-for-the-s4-based-one-x/
Also, I wasn't able to succesfully flash a custom ROM, when I tried to it just kept giving me random status errors in CWM, I'm starting to think the problem is the hardware and not the software since every solution I try is giving me errors related to unable to install/transfer/blahblah
Sam.Lambert said:
Pretty much the only one available for the Evita One X (this one doesn't work if that's the one you are talking about http://forum.xda-developers.com/showthread.php?t=1594819):
http://www.modaco.com/topic/354009-interim-clockworkmod-recovery-for-the-s4-based-one-x/
Also, I wasn't able to succesfully flash a custom ROM, when I tried to it just kept giving me random status errors in CWM, I'm starting to think the problem is the hardware and not the software since every solution I try is giving me errors related to unable to install/transfer/blahblah
Click to expand...
Click to collapse
So it seems that yours is not on tegra but S4. You need to find a solution for your problem here : http://forum.xda-developers.com/forumdisplay.php?f=1538

[Q] Errors in running "fixsu.sh"

Dear all,
I'm trying to root my G2. I was following the instructions described in the Strewmetal's PDF file. It went very smoothly until I hit this issue. I was in the section of "[OPTIONAL] TEMP-ROOTING TO BACKUP". It went fine until the last command which is:
adb shell /data/local/tmp/fixsu.sh
I had the following error:
/data/local/tmp/fixsu.sh: cannot create /system/etc/passwd: I/O error
Unable to chmod /system/etc/passwd: I/O error
/data/local/tmp/fixsu.sh: cannot create /system/etc/group: I/O error
Unable to chmod /system/etc/Group: I/O error
cp: can't create '/system/bin/su": Invalid argument
I tried the previous commands a few times just in case, but it seems there are no issues with the previous commands.
It would be great if someone can shed some light here.
Thank you very much!
- kazs
well for the most part you will probably never need your back up so you can definitely skip this part if youd like
but if you must id go to freenode #g2root
youll get real time help from people who have seen it all - when your done make sure you post the problem and the fix so the next person who reads this will learn
demkantor, thank you very much for the reply. I actually skipped the section and went ahead. Then, I just completed the entire process according to the PDF file. It went fine everything. But, I think I had an issue after I enter:
# reboot
My G2 automatically started the reboot process with the white screen with green "htc" logo, but it stuck there. I waited 10 minutes, but it doesn't change.
Did I screw up?
well not necessarily, if you have a g2 and flashed the dz hboot then your emmc partitions are different and your current rom wont start up. same thing if you have a dz and flashed the g2 hboot.
if you followed either the xda wiki or the cyanogen wiki then everything should be just fine.
pull battery and wait a few seconds... reinstall
boot while holding volume down and write down everything you see here
(you may have to take out sdcard or at least remove the pc10img.zip from your card at this point)
you should see something very similar to this:
VISION PVT ENG S-OFF
HBOOT-0.76.200 (PC1010000)
MICROP-0425
RADIO-26.02.01.15_M2
eMMC-boot
Aug 20 2010, 16:15:01
then some options,
write down your screen and well see if your good
Thanks again for the quick reply. I really appreciate it.
It says:
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1010000)
MICROP-0425
RADIO-26.02.01.15_M2
eMMC-boot
Sep 8 2010,15:56:38
Is it good? If so, what should I do next?
Thanks!
you should be just fine, looks like you have the dz hboot.
next step would be to pick your rom, do something simple and known stable at first to make sure all is well and then move on and try a bunch
recommend elitemod cm7 (youll find this and many many others in the dev section, look for a compilation in the 2nd or 3rd post
boot into hboot holding volume and down
wait a second or two after image check completes (no pc10img.zip on sd card!)
now hit volume down and select recovery with the power button
(the guide you followed should have brought you to clockworkmod recovery)
in here toggle (with volume keys but select with trackpad) to mounts>usb mount
put your rom on sdcard ---- unmount
toggle to wipe options (wipe everything you can)
toggle to apply update from sd card (recommend to flash a superwipe script here)
flash rom
now reboot
in the future look into updating radio (lots of threads on this)
update to 4et touch recovery (my opinion way better)
try some roms
do full wipes and superwipes between flashes
always do a nandroid backup before you flash or wipe anything
most importantly have fun!
rooting a friends g2 as i am writing this (got it down to about 15mins!)
time to do all i recommend for myself now! - we are in the same boat!
Thank YOU very much! I just installed EliteMod & Kernel CM7 according to your recommendation and it's working just fine so far. I really appreciate your big help!
I will check for the radio update tomorrow (it's getting very late here...) and I will try other ROMs as well.
May I ask the last question at this time? So, my G2 is not rooted. Does it mean the phone is unlocked as well? I mean I have a plan to go to Asia in August and I would like to buy and use another SIM instead of my T-Mobile SIM over there. I'm sorry for the novice questions though...
Thanks!!!
i think you mean now that you are rooted...
anyway here is the best way to check your work:
5. Verify the success of gfree
You can verify the success of gfree by using gfree_verify.
Download gfree_verify.zip from gfree_verify_v01.zip (md5sum 8e3535fd720d19fa0aec4eb711b897c4)
Unzip gfree_verify_v01.zip to a place on your PC.
Open a terminal (or command window) on your PC and change the current directory to where the files are on your PC and execute these commands:
$ adb push gfree_verify /data/local/tmp
$ adb shell chmod 755 /data/local/tmp/gfree_verify
$ adb shell
In this shell:
Remark: When you run su for the first time in the adb shell make sure the the screen of the phone is unlocked. Because when you enter the command the Superuser app will show up and ask you if you want to grant superuser access to app Unknown (2000).
Check the Remember check box and click allow.
$ su
# cd /data/local/tmp
# stop ril-daemon
# ./gfree_verify
You should see the following output:
gfree verify_cid returned:
@CID: 11111111
OK
gfree verify_secu_flag returned:
@secu_flag: 0
OK
gfree verify_simlock returned:
@SIMLOCK= 00
OK
Start the interface layer again (IN THE ADB SHELL ON YOUR PC):
# start ril-daemon
Did it work? Here's what you're looking for:
@CID: 11111111 <--- this response means you have superCID!
@SIMLOCK= 00 <--- this means your simlock is off.
@secu_flag: 0 <--- this means your radio is S-OFF.
if simlock =00 then you can put in any simcard and use anywhere that supports the proper cellular bands
Thank you very much! I have confirmed that the simlock is off on my phone.
PS Sorry for the typo and that I confused you. I wanted to type "now", but typed "not"...

[Q] Desire Z - Upgrade to Android 4

Hi Everybody,
I know, that there are a lot of threats about this fact in the forum. But nothing will work for me, aspessially important links will not work anymore. Could anybody help me?
If I go to the bootloader (noise - and Power-On) there are the following informations written:
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-0425
RADIO-26.10.04.03_MeMMC-boot
Apr 11 2ß11,23:36:27
HBOOT
OK, on my cell is working a Android 2.3.3, so I have to root my cell and downgrade.
I tryed to do this with the following threat: http://forum.xda-developers.com/showthread.php?t=905261
1. I Tryed to create a GOLDCARD. I read this threat, got the CID of my cell with the the code
Code:
adb shell cat /sys/class/mmc_host/mmc2/mmc2:*/cid
. Now I should type this CID in a webformular at this link to reverse it. This formular is still working, but there is also a Excel-Tool on this page for downloading, which should do the same. So my CID like "035344534d49202010000073b900d494" was reversed to "00d400b9730000102020494d53445303".
This code I should input to this formular for creating a GOLDCARD, but it doesn't work anymore.
So I looked around and found this threat, where a goldcardcreator is downloadable.
In this zip-file is included a program named "SimpleGoldCard", which read a reversed CID from the cell. On a command-Line I typed in
Code:
gcard -c 00d400b9730000102020494d53445303 -r -o "GoldCard.img"
Than I putted in the sd-Card into the Card-Reader of my Desktop, formatted it, used the tool "HeX Editor", copyed (line) 00000000 to offset (line) 00000170 (including the 00000170 line) and pasted it to the SD-Card.
After that I hope to created a correct GoldCard.
2. After that I downloaded the files psneuter, PC10IMG.zip and root. But in this threat is written, that I have to extract "misc_version_01.zip". Where is this file? I searched in this forum and downloaded a file named like this. Are there Differences or is a special version needed? I copyed the PC10IMG.zip to the SD-Card and put this to the cell.
3. then I booted the cell again, connected it to the desktop and used the following commands to put the downloaded files to the cell
Code:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
After that I should get the # - symbol instead of the $ - symbol which means, that I rooted the phone. But here is my first problem, I didn't get the # - symbol, so I don't have the permission to start the next programms.
4. Normally I would do next the following commands and then to reboot and flash the older Firmware.
Code:
/data/local/tmp/misc_version -s 1.33.405.5
exit
adb reboot bootloader
But when I reboot, the bootloader is looking for the PC10IMG.zip, is loading and checking this ... and gives me the information
CID incorrect!
Update Fail!
Press <POWER> to reboot.
Well, this is the next big problem.
Cold anybody tell me, where my mistakes are? I read 2 days in the forum, tryed a lot to get the final result, but now I don't have the time anymore to continue in this way.
THanks a lot. with best regards, Speedy8
Mods please move to q&a
Always check the stickies
http://forum.xda-developers.com/showthread.php?p=43195539
Follow the threads linked here, don't use any other to root your phone, they will either be outdated or cause you trouble.
After following these threads if you still have issues post back and I'll try to help ya
Best of luck!
Sent from my Nexus 4 using xda premium
well ... I searched again today ... and found the following threat, which was working on my cell-phone.
And also at the cyanogenmod-page you can find the relevant things to root the Desire Z. You can find it here.
Now I will first install the latest cyanogenmod, which is for the Desire Z not the Android 4, but at the moment newer than 2.3.3.
Thanks for answering, my Questions are answered.
With best regards.

Categories

Resources