Develop Bugs

[Q] Another unroot/s-off problem

Im hoping someone can point me in the right direction here.
Clearly I did something wrong. I could use a little direction here to get back
to factory state phone. I have a "factory phone" without root and stock apps but
S-OFF and I need to get back to S-ON
1) Rooted using Rage/Gfree method for temp root/s-off/perma root
2) Wanted to roll back(please don't ask why)
3) Tried to follow step 1a) on http://forum.xda-developers.com/showthread.php?t=835971
4) Receive following message
-- Installing: SDCARD:/stock_root.zip
E:Board does not support mtd utils.E:Failure at line 344:
write_raw_image PACKAGE:boot.img BOOT:
Installation aborted.
5) Recovered from clockwork backup
5) Went to step 1b successfully
6) Followed step 2 successfully
7) Phone patched itself OTA(step 3)
8) checked bootloader to find S -off
Steps I have taken
1) Regain temp root using rage
2) copied gfree back to phone
3) from terminal "# ./gfree -s on"
4) "#sync"
5) Reboot into bootloader to find S-OFF *sigh*
Bootloader items
VISION PVT SHIP S-OFF
HBOOT-0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
**Amendment* I don't have the gfree partition backup that gets created the first time you root

brandonmcgrew said:
Steps I have taken
1) Regain temp root using rage
2) copied gfree back to phone
3) from terminal "# ./gfree -s on"
4) "#sync"
5) Reboot into bootloader to find S-OFF *sigh*
Bootloader items
VISION PVT SHIP S-OFF
HBOOT-0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
**Amendment* I don't have the gfree partition backup that gets created the first time you root
Click to expand...
Click to collapse
You have the regular bootloader (not the eng one), so the fact you have S-OFF still means your "gfree -s on" didn't work. You need to try that again, and look for what error messages were produced at the time.

You have the regular bootloader (not the eng one), so the fact you have S-OFF still means your "gfree -s on" didn't work. You need to try that again, and look for what error messages were produced at the time.
Can you give me the steps for that. I got temp root with rage and ran the s-on and sync commands. do you want the output from that???

brandonmcgrew said:
Can you give me the steps for that. I got temp root with rage and ran the s-on and sync commands. do you want the output from that???
Click to expand...
Click to collapse
Yes, please post up the output from when you run "./gfree -s on", that's the bit that sounds like it's failing.

# export PATH=/data/local/bin:$PATH
# cd data
# cd local
# ./gfree -s on
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x000138b4 (80052)
Section index for section name string table: 41
String table offset: 0x000136fb (79611)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x00000a14 (2580)
-- size: 0x000000cc (204)
Kernel release: 2.6.32.17-g9ab3677
New .modinfo section size: 204
Attempting to power cycle eMMC... OK.
Searching for mmc_blk_issue_rq symbol...
- Address: c029c72c, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc029c000
Kernel memory mapped to 0x40001000
Searching for brq filter...
- Address: 0xc029c72c + 0x34c
- 0x2a000012 -> 0xea000012
Patching and backing up partition 7...
Done.
#

Well that's odd, that looks liked it worked ok.
What about if you try the stuff at http://forum.xda-developers.com/wik...ion#3._.28OPTIONAL.29_Verify_you_did_it_right to verify that S-ON has been set ?

Ok at this point I decided to get back to a spot where I felt comfortable. So I permarooted using rage/Gfree. I have also installed Clockwork and done a nandriod. So at this point here is my status. Perhaps you can help me get back to factory
1) Factory Stock w/OTA
2) Root
3) gfree verify
gfree verify_cid returned:
@CID: 11111111
OK
gfree verify_secu_flag returned:
@secu_flag: 0
OK
gfree verify_simlock returned:
@SIMLOCK= 00
OK
At this point I can't do anymore today but if you could/would give me a little help getting back to factory stock no root s-on simlock on I would REALLY appreciate it.

I'll do my best not to derail, but I cannot even install the stock ROMs anymore, and I think it is because of the version of CWR I am running. Since I wanted CM7, I had to install CWR 3.x. Is it safe to assume that any Android 2.3 ROM needs CWR 3.x, and any Android 2.2 or previous required CWR 2.x?

OK I finally got back to working on this and got a FIX!
See previous post(s) to get caught up......done ok GOOD
**THIS REQUIRED ADB TO BE WORKING**
**IF YOU TAKE THESE STEPS BELOW I TAKE NO RESPONSIBILTY IF SOMETHING GOES CRAZY AND YOU BRICK YOU PHONE. IM A NEWB TO THIS SO THIS IS JUST WHAT I DID**
Where I left off is I was Stock OTA rooted using the gfree/rage method. I had Clockwork installed and a nice nandroid backup(Such a good feeling). Copied backup to computer
1) Followed steps to a tee downgrade from OTA -->http://forum.xda-developers.com/showthread.php?t=831398
2) With a fresh preOTA phone I unmounted my sdcard
3) Formatted SDCard(no idea if this helped but made me happy)
4) Copied Visionary R14 to root of sdcard-->http://android.modaco.com/content/h...m/320722/19-nov-r14-visionary-one-click-root/
5) Enabled Unknown Sources install from Manage application
6) Installed File Manager from Market
7) Used File Manager to install Visionary
8) TempRoot using Visionary
9) Downloaded latest gFree from -->http://www.thinkthinkdo.com/trac/project1/raw-attachment/wiki/gfree/gfree_02.zip
10) unzip gfree_02.zip
11) open command prompt
12) enter following commands to confirm you have root
adb shell
$ su
**on phone should see superuser prompt...press allow**
if you see a "#" you got temp root
# exit
$ exit
13) Push gfree to phone
c:\adb push gfree_02 /data/local
c:\adb shell
$ su
# cd /data/local
# chmod 777 gfree
14) Set S-On
# ./gfree -s on
15) Set CID
# ./gfree -c TMO010
# exit
$ exit
16) Power off
17) Boot phone to bootloader (Hold Power +Vol Down) and confirm
VISION PVT SHIP S-ON
HBOOT-0.82.0000
MICROP-0425
RADIO -26.02.01.15.M2
eMMC-boot
18) Reboot Device. ALL DONE!!!
**If you want you could temproot again and remove all files copied for gfree to /data/local or you could do a factory reset from the bootloader**

[Q] about to flash eng hboot

here are my phone specs
pvt ship s-off
hboot 0.82.0000
microp-0425
radio 26.03.02.26m
emmc-boot
sep 2 2010, 17:59:38
is there anything i should change?
only reason i ask is cause i have bricked a phone before and i think it was due to wrong hboot/radio combo (mt3g 1.0)
btw i rooted via rage root temp and gfree method
all help/tips is appreciated!

8. Install the engineering hboot (if you really want to)
8.1. download engineering hboot
Download the appropriate HBOOT for your phone:
T-Mobile G2: vision.hboot-0.76.2000.zip (md5sum 7669AE12DC2FAA10AE555A164980EFD0)
HTC Desire Z: vision.hboot-0.84.2000.zip (md5sum 2CE1BDD5E4C1119CCFCECB938710D742)
HTC Desire HD: ace_glacier.hboot-0.85.2007.zip (md5sum df4fd77f44993eb05a4732210d2eddc6)
Note that the md5sums are for the actual hboot img contained within the zip file, not the for the zip file itself. Note also that the dz, g2, and dhd each use their own version of the engineering boot, as the phones are partitioned differently. (If you have previously installed the wrong HBOOT for your phone, you may need to reflash everything after partition 18)
8.2. Copy the files to the phone
Connect the phone to the USB of your PC. The phone will stay connected during the complete procedure.
Make sure that you do NOT turn on USB storage. There has to be a sdcard in the phone and it has to be mounted to the phone!
Unpack the engineering hboot zip files to a directory on your PC.
Open a terminal (or command window) on your PC and change the current directory to where the file is on your PC and execute these commands:
$ adb push hboot-eng.img /data/local/tmp/
8.3. Install the engineering hboot
Please make sure that you type or better copy/paste the following commands exactly, and in exactly this order. Especially the dd-command is very critical!
In the terminal (or command window) on your PC execute these commands:
$ adb shell
$ su
# dd if=/data/local/tmp/hboot-eng.img of=/dev/block/mmcblk0p18
# sync
8.3.1. Check the md5sums of the installed hboot
As it is very important that the hboot was installed correctly we recommend to check the md5sums of the partition. In the root shell (indicated by the #) that you got in the Temporary root section execute the following commands:
# /system/xbin/busybox md5sum /data/local/tmp/hboot-eng.img
# /system/xbin/busybox md5sum /dev/block/mmcblk0p18
We call these two md5_1 and md5_2 in the next section
If md5_2 does not match md5_1: First DON'T REBOOT and second run for help at the #G2ROOT IRC channel on freenode.
If md5_2 matches md5_1: You are fine, Reboot your phone by executing the following command in the root shell (indicated by the #):
# reboot

thats relavent section of wiki for you follow it .... although putting eng hboot puts you at risk of bricking your phone while flashing radio . stock hboot atleast doesnt let you to flash wrong radio

You don't need eng hboot to change the radio. Read this http://forum.xda-developers.com/showthread.php?t=970809

Is this method safe, or are there many problems with md5?

Cant get S-OFF

So I followed step by step 3 times now on trying to get s-off on my G2. Did visionary temp root, downloaded s-off rooting files, copied .ko and .img files to sdcard, downloaded terminal emulator and entered in these:
su
cd /sdcard
insmod /sdcard/wpthis.ko
then i see an error which in every step by step says is correct then from there i...
dd if=/sdcard/hboot.eng.img of=/dev/block/mmcblk0p18
after that finishes i type
sync and hit enter
When i go into hboot it still says s-on
Any ideas? thanks.
2.2
Kernel - 2.6.32.17-g814e0a1
[email protected] #1

dvno said:
So I followed step by step 3 times now on trying to get s-off on my G2. Did visionary temp root, downloaded s-off rooting files, copied .ko and .img files to sdcard, downloaded terminal emulator and entered in these:
su
cd /sdcard
insmod /sdcard/wpthis.ko
then i see an error which in every step by step says is correct then from there i...
dd if=/sdcard/hboot.eng.img of=/dev/block/mmcblk0p18
after that finishes i type
sync and hit enter
When i go into hboot it still says s-on
Any ideas? thanks.
2.2
Kernel - 2.6.32.17-g814e0a1
[email protected] #1
Click to expand...
Click to collapse
my idea: don't use visionary.
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
^^^gfree/rage. much easier, much less likely to cause problems. since you're on a G2, you don't need to worry about downgrading from 1.72, you should just be good to go

Thanks man, i'll try that.

[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.

[Q] Stuck at boot screen with S-ON

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.