Develop Bugs

[HOWTO] Create a GoldCard - Bypassing the RUU/SPL CID check to Root/Downgrade

If you are stuck on a ROM you don't like (t-mobile/asian carrier etc.) you can use this howto to create a goldcard to bypass the CID checks so you can downgrade and root your Hero.
01. Download QMAT 5.06 here
It’s a demo version so will only run for 10 minutes.
02. Format your SD card to FAT32. Please keep in mind some brands of SD cards do not work.
03. Use adb to run this command: adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
04. Copy the SD card cid code displayed after the adb command.
05. Start Qmat and Click on Cyptoanalysis Tools > Crypto Toolbox.
06. Look at the bottom, there is a text box (beside the “Reverse String” button) enter the SD card cid code you got earlier.
Click on the “Reverse String” button, the result is reversed…
Example: 532600bd227d9c0347329407514d5402
07. Copy the reversed SD card cid code.
08. Go to QMAT goldcard site here to generate your goldcard (yes it says for G1 but works for our Hero too).
09. Enter your email. For the correct SD card cid code, you need to replace the first 2 characters to 00.
Example: From “532600bd227d9c0347329407514d5402” to “002600bd227d9c0347329407514d5402”
10. Click Continue and you will receive the goldcard.img in .zip format in your email.
11. Go to your email, download the zip file and save it to a directory and unzip it to goldcard.img
12. Download HxD Hex Editor from here
13. Install and launch HxD Hex Editor program. (make sure you use "Run as Administrator" under Vista and win 7)
14. Go to Extra tab > Open Disk. Under Physical disk, select Removable Disk (Must be your SD card), uncheck “Open as Readonly), click OK.
15. Go to Extra again, Open Disk Image, open up goldcard.img which you’ve saved/unzipped earlier.
Now, you should have two tabs, one is your removable disk, the other is goldcard.img. Press OK when prompted for “Sector Size” 512 (Hard disks/Floppy disks), click OK.
16. Click on goldcard.img tab. Go to Edit tab > Select All, edit tab again > copy.
17. Click on the “removable disk” tab. Select offset 00000000 till offset 00000170 (including the 00000170 line), click on Edit tab and then Paste Write.
18. Click on File > Save. now you can exit the program.
19. Reboot your phone with this SD Card (now GoldCard) inside
20. Use the Official HTC RUU to downgrade to 2.73.405.5 (which you can get here) from which you can fastboot boot and/or root your phone with flashrec.
Done.
Credits:
Original heads up by tangzq with link to this
That site used the XDA Sapphire goldcard howto here
And apparently myself and XDA as this builds on the HTC knowledge from the old days (here)
In any case, enjoy your new found freedom

Holy ****znit it works! Downgrading!!!!!

Hmm. I've followed the guide and successfully skipped the CID lock check of the device and flashed it to version 2.73.405.5 WWE. Problem is, I can't seem to get the device to boot into recovery mode after using flashrec (I did download and flash it just fine). the recovery mode (home + power) booted the device but it hangs at the boot screen where it says HERO. Any idea?
Edit: Ah. a little bit of the update. while the buttons do not work, i can use adb shell reboot recovery; however, after using flashrec, it still shows the old recovery screen ?
Edit2: confirmed, recovery flasher doesn't work now im using the SEA rom
I'll try the RUU_Hero_HTC_WWE_1.76.405.6_WWE_release_signed_NoD river.exe rom later

I had the same issue with Recovery Flasher I couldn't to boot into recovery. I was also unable to downgrade to the 1.7 roms due to a bootloader version error, arghhh. Anywho, managed to work my way round it, i'll explain below. I've got a T-Mobile G2 updated to the latest rom (so no root access).
I first followed the instructions on making a goldcard and then flashed the 2.73.405.5 WWE rom fine.
Now make sure you have the cm-hero-recovery.img (http://content.modaco.net/dropzone/modacopatchedrecovery-1.0.zip) on the root of your sdcard. Aswell as Instant Root (http://neilandtheresa.co.uk/Android/) now install Instant Root on the phone. It should pop up with a notification "instant root was sucessfully" or along those lines. (If you have a problem installing Instant Root make sure Settings>Applications>Unknown Sources is checked)
Instant root then allows for root access with adb shell using the following 2 commands:
1) adb shell
then
2) su
the icon should change from a $ to #.
Now flash the recovery image with the following command:
1) flash_image recovery /sdcard/cm-hero-recovery.img
This shouldn't take that long once completed it will go back the # prompt example below.
# flash_image recovery /sdcard/cm-hero-recovery.img (I typed this)
flash_image recovery /sdcard/cm-hero-recovery.img (this pops up)
# (this shows the flash completed)
Now pull out your usb cable and battery, turn on the phone with the battery in place while holding the home button and it should boot into the custom recovery .
Well, I hope this helps someone and I didn't just waste my time . Oh, thanks for posting the goldcard instructions.

it worked!!!
Thanks so much! I did the exact process before (see other thread) but I must have missed something. Following this process exactly is what did it. I am guessing something about the reboot and the RUU is where i went wrong before.
I can confirm this works on the 2.73.707.9 ROM

Yaaahaaaayyhaahhahahaahaayyyyyyyyyyyy!!! I feel so happy for all you guys who had this problem (although I myself did not!!)

I kind of half gave up at 6:00 am yesrterday and i just woke up (1
:27pm) and followed the instructions here and BAM! got a working nandroid backup and a custom rom \o/!!! thanks to all of you!

so it's tested and proven for 2.73.707.9?great!

umm ... guys.. if u dont mind me asking...... why do we need it?
do we have hero versions which cant be rooted with any methods?

dying4004 said:
umm ... guys.. if u dont mind me asking...... why do we need it?
do we have hero versions which cant be rooted with any methods?
Click to expand...
Click to collapse
yup, we couldn't root certain asian carrier roms and t-mob rom and they couldnt downgrade so the where stuck, until now....

tianci86 said:
so it's tested and proven for 2.73.707.9?great!
Click to expand...
Click to collapse
CONFIRMED! it works on 2.73.707.9 , just got 2.73.405.5 , im so happy , thanks soo much guys your the best

My Hero..... lol
Thanks, I thought I would be owned by T-Mobile for ever after the ROM update
Now I'm back to the HTC default ROM (NOT T-Mobile G2 Touch!!!), cup of coffee time before Rooting flashing etc and remaining from now on faithful to Paul and the MoDaCo ROM

hey guys!
i have a question
im a owner of an tmobile g2 touch and want to have the new firmware of the htc hero can i use this hack to update to the newest firmware because at the moment it says if i want so update: error this rom is not for your device, and so on..
thx !
bye
sry for my english im from germany

gyounut said:
hey guys!
i have a question
im a owner of an tmobile g2 touch and want to have the new firmware of the htc hero can i use this hack to update to the newest firmware because at the moment it says if i want so update: error this rom is not for your device, and so on..
thx !
bye
sry for my english im from germany
Click to expand...
Click to collapse
ja das stimmt

thx jesterz
successfully update singapore hero 2.73.707 to 2.73.405, rooting in a while...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

d0s said:
I had the same issue with Recovery Flasher I couldn't to boot into recovery. I was also unable to downgrade to the 1.7 roms due to a bootloader version error, arghhh. Anywho, managed to work my way round it, i'll explain below. I've got a T-Mobile G2 updated to the latest rom (so no root access).
I first followed the instructions on making a goldcard and then flashed the 2.73.405.5 WWE rom fine.
Now make sure you have the cm-hero-recovery.img (http://content.modaco.net/dropzone/modacopatchedrecovery-1.0.zip) on the root of your sdcard. Aswell as Instant Root (http://neilandtheresa.co.uk/Android/) now install Instant Root on the phone. It should pop up with a notification "instant root was sucessfully" or along those lines. (If you have a problem installing Instant Root make sure Settings>Applications>Unknown Sources is checked)
Instant root then allows for root access with adb shell using the following 2 commands:
1) adb shell
then
2) su
the icon should change from a $ to #.
Now flash the recovery image with the following command:
1) flash_image recovery /sdcard/cm-hero-recovery.img
This shouldn't take that long once completed it will go back the # prompt example below.
# flash_image recovery /sdcard/cm-hero-recovery.img (I typed this)
flash_image recovery /sdcard/cm-hero-recovery.img (this pops up)
# (this shows the flash completed)
Now pull out your usb cable and battery, turn on the phone with the battery in place while holding the home button and it should boot into the custom recovery .
Well, I hope this helps someone and I didn't just waste my time . Oh, thanks for posting the goldcard instructions.
Click to expand...
Click to collapse
Did it last night and got it working, used the AMON Hero recovery image instead and partitioned my sd card without going through the manual adb solution.
Cheers

could this be adapted for the sprint hero?

Sprint Hero support request strongly seconded, i am desperate to get my CDMA Hero rooted.

have you guys tried using thesame method and got anywhere? I mean, from what I know is that you can't even boot in to recovery mode right? have you guys tries the adb method to boot into rec mode at least?

Aces!!!!
Worked on Indian 2.73.720 like a charm.
Thanks.

[Q] Help Rooting 2.2.1 - I've tried that edition.

I, for the life of me, being a compute tech since the mid 90's, can't root this mytouch g3 slide. I have android 2.2.1 installed, I know I know, I hate it when people don't RTFM, I have tried the following:
(USB Deugging is on, charge mode only when plugged in, full android SDK kit installed and working. PDAnet drivers installed, I have superoneclick 1.9 computer see the phone fine, Goldcard works perfectly.)
1. I've tried Cyanogenmod's instructions (wiki.cyanogenmod.com/wiki/TMobile_myTouch_Slide:_Full_Update_Guide)
-Nothing happens after 2nd to last command line of step 8
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. I have tried this "New way to downgrade from 2.2 to 2.1" (http://forum.xda-developers.com/showthread.php?t=1108316)
-4a. , It does not give me the option to "hit vol up to update"esrpimg" just flashes error no image found error messages:
3/ I have tried ULTRA EASY ROOTER (http://forum.xda-developers.com/showthread.php?t=999121)
same problem as #2's problem, just error messages.
4. And I have tried this: "How-To [Root][NewLinks] The myTouch 3GS if you updated to Offical 2.2.1 and lost root" (http://forum.xda-developers.com/showthread.php?t=1025336)
-Everything goes smooth until I type in this line "chmod 04755 *" which I get a bank carraige return, and I can type to my hearts content, nothing happens, can't exit, etc, have to CRTL + C to get out out of it. similar problem as #1's problem. I have tried again and again and again.
Help.

Make a goldcard and install the img from the bootloader.
Then try again.
sent from my MT3GS running CM7 nightly

thanks for the reply poormanq45. I did make a goldcard, maybe it doesn't like my MicroSD card? Which image do you want me to install from the bootloader? Which instructions should I be following?
Which set of instructions talk about having a swap partition as your 3rd partition on the SD card?
poormanq45 said:
Make a goldcard and install the img from the bootloader.
Then try again.
sent from my MT3GS running CM7 nightly
Click to expand...
Click to collapse

I don't remember which img I used. IIRC there are three different ones. Just try each one until one works.
It's possible that your MicroSD card isn't capable of being a goldcard. I had to try two different ones
sent from my MT3GS running CM7 nightly

My Stock 2.2.1 Process
My warranty replacement came with stock 2.2 and all of the tutorials here and elsewhere fell short. I did notice a lot of the other guides were based on "if you upgraded to 2.2"; that did not completely apply in my situation. I to am an industry professional with 14 years experience and am a stickler for detail. I had the gold card created on a SanDisk 2gb micro sd acquired from Walgreen's. I had followed all the steps in order, but the update on the first reboot never happened, it never asked and selecting the update.zip failed signature verification. I knew S-ON was set (which is the whole problem) but the guides I saw to disable it required you already be rooted (which I wasn't).
This past week I did something different. Using the official HTC MyTouch 3G Slide Froyo installer (not selecting anything just having RUU opened) I copied the folder structure (a crazy GUID looking thing) that was in my %TEMP% directory to another location. I closed out of the installer and went to that copied folder. I moved the existing "rom" file and copied the 2.1 "ESPRIMG" image there and renamed it to rom.zip. I then executed the RUU from that folder. It being an HTC official rom did allow the RUU to complete and the slide was officially downgraded to 2.1. After the reboot I verified the ROM was the older version and went ahead with what I was used to.
After that; some of my previous attempts to root were evident because I already had the "#" prompt in the adb shell. Regardless, I did repeat some of the documented steps (just in case my eyes deceived me) from the exploid method (what I used on my previous phone that was an original build). I originally flashed the CM 7.03 while the goldcard (2gb) sd was still in there. I then installed my 32GB card, then hit a nightly, then hit a few more older CM builds (had issues with sd-ext, couldn't find the original guide i used to set it up - new card as well). I did format boot, data, system, sd-ext, and the cache from the clockworkmod recovery screen before settling on CM 7.1 RC 1
If you find it necessary to create the sd-ext partition, format the fat partition in windows, format the other two in the shell. I do not recommend logging (app sync) on the first rom. Build the sd-ext first; re-rom, before doing all the account/app setup. While the phone is USB debugging mode you can use DriodExplorer to shortcut some things (especially if u have all your apks in a backup folder on your computer). I do not recommend using certain busy-box commands from the DriodExplorer terminal. The output can be out of sync at times. I have a 32gb SD and have about 29.3G on FAT, 896MB on SD-EXT (ext3 file system), and the rest on cache. After that Simple2Ext will allow for you to tell CM7 to use the SD-EXT. I do not use .android secure (the froyo apps2sd) because that causes issues when using the fat partition as disk in windows and you have something like a theme installed. Because of themes, games, and other apps I am now using 62% of the sd-ext partition. And an earlier comment I saw on the thread is right. The partition order is FAT, SD-EXT, CACHE. Where the guide is I don't recall.
Also note: If you are doing ADB commands and notice it often says the process is stale; uninstall the HTC sync (this does not affect the drivers, drivers are installed as a pre-req before HTC Sync is installed).
My only outstanding issue is the radio version might have been affected; it's not showing a version number on my info app. So I need to find a guide on verifying/upgrading the radio (one that does not involve installing the htc froyo rom).

Stuck... help.
First of all, sorry I can't past in links to the images, because I need a minimum of eight posts.
-----
Okay, I have made sure my phone has 25MB free. (it told me I needed this)
I have Turn USB Debugging on.
The phone is set to charge mode only.
The phone is plugged in and drivers installed. PDANet is not running.
I've tried it with a goldcard in it and out of it.
tagr.org/ScreenShot084.jpg
I Downloaded "T-Mobile_myTouch_3G_Slide_Software_Update_2.15.531.3.exe" from here the website, (I can't post the links)
I ran setup, and left it open while I went to the temp folder and copied it all out to another location.
I went to the NEW location and deleted "rom.zip" and replaced it with the 140 MB "ESPRIMG.zip" into that folder and renamed it rom.zip
In the new folder, I ran "ARUWizard.exe", agree, agree, okay, etc.
All goes okay, I get to this screen:
tagr.org/ScreenShot091.jpg
I say next, About two minutes into it, the phone reboots, put the HTC logo on it. Then on the computer, I get to this screen:
tagr.org/ScreenShot089.jpg
The phone is stuck on the "HTC" logo when the USB is plugged in. When USB is unplugged, the screen turns to this:
tagr.org/ScreenShot090.jpg
Stuck meaning, can't reboot, turn off, etc. So I have to pull the battery. When it turns on, all seems okay, it's still at 2.2.1 though.
Thoughts?

What the... why could I post pics my first post, but not my third...new policy?
eckre said:
First of all, sorry I can't past in links to the images, because I need a minimum of eight posts.
Click to expand...
Click to collapse

Okay I've figured it out and wrote up a NEW Guide: http://forum.xda-developers.com/showthread.php?t=1189485
No goldcard is needed, no console typing ADB shell etc. blah blah blah, so easy now.

[Q] Dinc corrupt primary file system *serious software help needed*

to start off with here is the problem list:
1) any rom, ruu, etc loaded will not boot past htc screen and if they do it boot loops 5 seconds into the animation.
2) clockwork reads error, E: /dev/block/xxxxxxxxxxx and cant mount data or cache partitions.
3) when doing a cat of mounts there are only five items instead of the 20 an unrooted stock phone possesses.
so in short i am asking for ideas maybe i have not tried "be creative here" to recover or reinstall "in my opinion the best fix" the whole main file system. just as if it was merely hardware blank from the factory. maybe push over new /dev, /system, /data, /cache etc etc as i believe the file system is corrupted and missing directories.
thanks for your time and thoughts...
*edit* i have been trouble shooting with the brilliant guys over at incredibleforum as well and thus whats lead me to my question here. so the back story, everything i've tried already, findings, and pictures are already posted here (not to violate TOS just for reference):
incredibleforum . com/forum/htc-incredible-rescue-squad/10812-boot-loop-after-exhausting-ever-possible-fix-my-head-experiance-help.html

Have you tried to ruu to stock froyo, and then do a factory reset thru hboot? Also when you say you ruu'd before did you do the PB31IMG.zip ruu or the ruu exe, or did you try both? Also have you at some point gotten the 5 vibes of death while booting?

i have done the ruu's both in hboot pb31img and via the exe while i booted into hboot. and i've never gotten nor heard of the five vibes. but exploring the file system there are directories missing for some reason. so i'm figuring the ruu's and roms aren't installing certain files due to not having a place to put them.

Sounds bad to me. I know they say if it turns on its not bricked, but if an ruu cant write to the partitions you will probably never be able to find a way to either. Hey im not an expert though by any means. Hope some one can help you figure it out.

the ruu cant write to the partitions because they don't seem to exist or the mounts for those directories. thats why i'm interested in finding a way to rewrite the partitions back to factory. there is a way because the phone wasn't built with this file system on it so there is a way to write /dev /system /cache /data etc.. maybe even a way to pull it off a stock phone and write to this one?? i can adb shell and view all of the files so i know its accessible. and hboot and recovery both work and can flash successfully. come on xda don't let me down i know there are some really brilliant and creative minds out there who think this is an easy fix to them.

tophkr said:
the ruu cant write to the partitions because they don't seem to exist or the mounts for those directories. thats why i'm interested in finding a way to rewrite the partitions back to factory. there is a way because the phone wasn't built with this file system on it so there is a way to write /dev /system /cache /data etc.. maybe even a way to pull it off a stock phone and write to this one?? i can adb shell and view all of the files so i know its accessible. and hboot and recovery both work and can flash successfully. come on xda don't let me down i know there are some really brilliant and creative minds out there who think this is an easy fix to them.
Click to expand...
Click to collapse
which hBOOT do you have? have you tried to reinstall the hBOOT?
http://pvillecomp.com/?page_id=4
after you reinstall hBOOT then try to ruu with the .exe

synisterwolf said:
which hBOOT do you have? have you tried to reinstall the hBOOT?
http://pvillecomp.com/?page_id=4
after you reinstall hBOOT then try to ruu with the .exe
Click to expand...
Click to collapse
+1 for reflashing hboot.
An ruu is ment to program the phone as if it were strait off the line never touched. It should create the file structure and partitions if they dont exist. What bothers me about your problem is that flashing roms or dooing ruu's compleet sucessfully without error. If the ruu cant write to these partitions it should stop and give an error, not just continue as if everything is ok. So to me it seems its writing to them fine but then for some reason cant read from them. Same for flashing a rom if it cant mount the partitions it should halt and give an error.

cmlusco said:
+1 for reflashing hboot.
An ruu is ment to program the phone as if it were strait off the line never touched. It should create the file structure and partitions if they dont exist. What bothers me about your problem is that flashing roms or dooing ruu's compleet sucessfully without error. If the ruu cant write to these partitions it should stop and give an error, not just continue as if everything is ok. So to me it seems its writing to them fine but then for some reason cant read from them. Same for flashing a rom if it cant mount the partitions it should halt and give an error.
Click to expand...
Click to collapse
well you have have a partition that has blocked write access so when RUU reads it, it works but when it try's to write it skips it.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i currently have .92 installed but i've gone back as far as .77 due to it being the development copy with full fastboot and adb capabilities. but i will try to reflash hboot .92 and then run ruu from computer while still in hboot.. worth a shot

You could try this. Sounds like your issue. Post 3.
http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/page__st__20

tried that and i'm guessing the correct partitions are no longer there because i recieve this:
Error: /dev/block/mmcblk0: unrecognised disk label
and get that with every partition in the mmcblk catagory

ok so i have a question based on a possible cause to this problem.. if the prebious owner had flashed a droid incredible 2 rom insted of a DINC rom.. i know that can cause issues flashing the wrong roms.. how would you go about fixing that?

tophkr said:
ok so i have a question based on a possible cause to this problem.. if the prebious owner had flashed a droid incredible 2 rom insted of a DINC rom.. i know that can cause issues flashing the wrong roms.. how would you go about fixing that?
Click to expand...
Click to collapse
Did you try the link on the last page?
Sent from my sexy assistant. (AMOLED HTC Incredible)

synisterwolf said:
Did you try the link on the last page?
Sent from my sexy assistant. (AMOLED HTC Incredible)
Click to expand...
Click to collapse
the link to using parted to fix the partition format.. yes but those folders do not exist. when i show a list of my mounted partitions cache, data, system and a few others don't show up in the list at all. so because they don't exist anymore i don't know what partitions to remake or what folders need to go in them, which to mount etc.

So when you run the RUU's and PBIMG's they complete successfully without error?
also on a kind of related note, have you looked into booting a rom from your SD card or internal storage? Its not a fix or anything just merely might give you the satisfaction that your phone can boot a rom lol though it might not be by the traditional or standard means

nope i've never looked into how to boot a rom from internal storage. could you supply a link to instructions as this might be a temp fix while i continue to try and fix this.
and yes when i run them they compleate with no errors. only errors appear when looking in recovery.

tophkr said:
nope i've never looked into how to boot a rom from internal storage. could you supply a link to instructions as this might be a temp fix while i continue to try and fix this.
and yes when i run them they compleate with no errors. only errors appear when looking in recovery.
Click to expand...
Click to collapse
I would try a Google or XDA search because I've never tried it myself. Last I remember punk.kaos did it back when I had an Eris and I think more recently conap did it with the Incredible. Sorry I couldn't be of more help :/

i'm going to look into it but i've never heard of it being done except on the hd2 and hd7 using ram loading. but thanks for the ideas

[GUIDE] Booting an Android System when only Recovery is at your disposal

This guide and the linked ZIP package are for use with the HTC Desire Z.
Version 1.0.1
Provided by Catherall
== Boot CyanogenMod 7.1 from Recovery ==
Your phone may be in a state where Android cannot start any more, even restoring a system backup might be impossible. Then it would be great to have a handy way to boot a full CyanogenMod system anyway.
With the simple to follow commands in this guide you can boot CyanogenMod 7.1 from recovery.
What you need:
Custom recovery like one of the following:
--- ClockworkMod Recovery version 5.0.2.7
--- 4EXT Recovery TOUCH v1.0.0.4 RC3
--- Other recovery with similar kernel might work
SD card (~ 800MB free)
CyanogenMod 7.1 system and boot files on SD card
All needed files are contained in the zip package:
Boot_from_SD_v1.0.1.zip (md5: d8d3332dda267fd3f6f03ba7023c6d72)
http://dl.dropbox.com/u/64675947/android/Boot_from_SD_v1.0.1.zip
Extract all files from the downloaded zip file to your SD card.
The resulting directory structure looks like this:
Code:
SD card --+-- update.zip
|
'-- BootManager --+-- README.txt
|
'-- rom8 --+-- boot.img
+-- data.img
+-- log.img
+-- name
+-- system.img
'-- .android_secure
Boot into Recovery:
Shutdown your phone completely and remove battery for about 3 seconds.
Boot your phone into HBOOT by pushing Volume down and Power at the same time for about 5 seconds.
In the HBOOT" menu use Volume down to select Recovery and engage with Power.
You are in Recovery now.
Start Android system from Recovery:
Use Volume down and Volume up to select "apply update from sd card" and engage with Trackpad button. Confirm "install" by selecting "Yes - Install .." and engage with trackpad.
Installing update.zip only starts the Android system from the SD card, nothing will be installed on your phone!
When CyanogenMod is starting the CyanogenMod logo appears.
If you have a black screen then push Power once or twice until the screen is visible.
The default language of the system is "German". Select another language using "menu" button / "Einstellungen" / "Sprache & Tastatur" / "Sprache auswählen" - change to your prefered language and hit the home button.
Congratulations, you have a full working CyanogenMod 7.1, rooted, with terminal emulator and working network.
For installing new applications:
* Put the according APK file on the SD card
* Install the app by opening the APK file with the installed app "File Manager"
== Technical Remarks and Background Information ==
Testing for a fried ROM:
(as provided by amidabuddha in http://forum.xda-developers.com/showthread.php?p=18016711 ):
Connect your phone to the computer, boot into recovery and use the following adb commands:
Code:
adb shell
dmesg | grep mmc0
If the output contains the following strings then your emmc (internal memory) is corrupted, your "chip is fried":
mmc0: failed to get card ready
mmc0: reinit card
mmc0: Starting deferred resume
mmc0: Deferred resume failed
Files contained in the ZIP package:
update.zip: Flashable "install" file that can be used in custom recoveries. It contains the kernel boot files and uses chroot to initialze the Android system by executing /init from the boot files
system.img, data.img, log.img, cache.img: Loop files of system, data, devlog and cache partition of CyanogenMod 7.1
When you "install" update.zip in recovery then the contained /META-INF/com/google/android/updater-script starts up. All necessary files are copied to the boot RAM disk and the shell script startsystem.sh is executed.
The script startsystem.sh mounts the Android partitions from SD card and starts up Android using the following command:
Code:
chroot /tmp/boot.img-ramdisk /init
This starts the android system (using init) with the new root on the path /tmp/boot.img-ramdisk.
Side effects of using chroot:
The phone appears as "recovery" when using "adb devices".
Using adb shell connects to /bin/sh of recovery.
You cannot use adb to install apps. As a workaround put the apk file on the SD card and install it simply by opening it with the app "File Manager"
This guide has been tested on the following Recoveries so far:
ClockworkMod Recovery 5.0.2.7 (kernel 2.6.35.14-cyanogenmod-g9e5cdf1)
ClockworkMod Recovery 3.0.2.4 (kernel 2.6.32.28-cyanogenmod-g4f4ee2e)
4EXT Recovery TOUCH v1.0.0.4 RC3 (kernel 2.6.35.13-cyanogenmod-g4dc0bbe)
4EXT Recovery v2.2.7 RC5 (kernel 2.6.35.13-cyanogenmod-g4dc0bbe)
As chroot is used to boot up the Android system it is important that the recovery kernel is compatible to CyanogenMod 7.1.
You can find your recovery kernel version by booting into recovery and using adb with the following command:
Code:
adb shell uname -r
== Feedback and Questions ==
For feedback and questions visit Freenode IRC channel #G2ROOT.
You can use the web interface at http://webchat.freenode.net/ .
After login change channel using "/join #G2ROOT".
When there is real need for the linked zip package and this guide then both will be improved.
Packages for other phones can be provided. When you have another phone then get in touch with me.
== Credits ==
Guhl (inital idea and support)
#G2ROOT freenode IRC channel ("These guys are awesome!")
Inioch (testing on a HTC Desire Z phone with a "fried" / read-only emmc)
karsten95 and coldsun15 (testing)
Nipqer (testing)
amidabuddha (fried rom check)
== Thanks ==
During my work I was supported by
#virtuousrom freenode IRC channel ("Excellent!")
Many other people, you know who you are!
P.S. If this guide does not work for you then follow the advice of Ego_UK:
"Jump three times, then turn around and say abracadabra. Maybe this helps"

I had the exact same idea as this, I knew it would work well, I just couldn't be arsed to do it
Well done man, so many people would find this helpful, this should be sticked in the development forum!
Sent from my HTC Vision using XDA

Very nice, you should PM a mod to sticky this.

well done, but how can i boot to the normal system? and when i want to boot to this system, should i do this again?

Could this be used to have tons of free ram? Boot from the SD card and not have anything installed in the ROM of the phone? As in, format all the phone's partitions (everything under "/" ) and have, say, 368mb of ram? That'd be sick nasty.

Can this be ported to be used with EVO 4G?

nickeedoo said:
Could this be used to have tons of free ram? Boot from the SD card and not have anything installed in the ROM of the phone? As in, format all the phone's partitions (everything under "/" ) and have, say, 368mb of ram? That'd be sick nasty.
Click to expand...
Click to collapse
Do a nandroid backup and find out

Nice guide !
catherall said:
Boot into Recovery:
Shutdown your phone completely and remove battery for about 3 seconds.
Boot your phone into HBOOT by pushing and at the same time for about 5 seconds.
In the HBOOT" menu use to select Recovery and engage with .
You are in Recovery now.
Click to expand...
Click to collapse
That bit should be "Volume Down" instead of "Power Down"
Sent from my Desire Z running CM7.

nickeedoo said:
Could this be used to have tons of free ram? Boot from the SD card and not have anything installed in the ROM of the phone? As in, format all the phone's partitions (everything under "/" ) and have, say, 368mb of ram? That'd be sick nasty.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Galaxy Nexus using Tapatalk 2 Beta-4

Booting to phone system: Just power on your phone.
PJ.C said:
well done, but how can i boot to the normal system? and when i want to boot to this system, should i do this again?
Click to expand...
Click to collapse
Just boot your mobile phone as usual (power on your phone) and you are in your Android system as installed in /system partition. update.zip does not install anything permanently, it just uses init from a modified kernel, mounts partitions from SD card and boots CyanogenMod 7.1
When you want to boot again from SD card you have to go into Recovery and "install" update.zip to boot.
Best regards,
Catherall

Do not use /system ROM as ram
nickeedoo said:
Could this be used to have tons of free ram? Boot from the SD card and not have anything installed in the ROM of the phone? As in, format all the phone's partitions (everything under "/" ) and have, say, 368mb of ram? That'd be sick nasty.
Click to expand...
Click to collapse
First, I do not recommend to use the ROM as ram. Some emmc might get stuck in "read only" mode when used that way
When you need more "RAM" for system you could use a swap partition or file.
However, with booting from SD card you can have a system partition with more than say 368MB. If you want to use that on a full working phone I recommend to use the app "BootManager" from Google Play. They have done a good job to boot from SD card on phones with working ROM partitions.
In fact I used their applications have 9 different ROMs on my phone installed (8 on SD card) ready to boot when ever I want.
Best regards,
Catherall

nickeedoo said:
Could this be used to have tons of free ram? Boot from the SD card and not have anything installed in the ROM of the phone? As in, format all the phone's partitions (everything under "/" ) and have, say, 368mb of ram? That'd be sick nasty.
Click to expand...
Click to collapse
cjward23 said:
Sent from my Galaxy Nexus using Tapatalk 2 Beta-4
Click to expand...
Click to collapse
crestofawave said:
Click to expand...
Click to collapse
Sorry about that Catherall. @nickeedoo this is for people with phones that have the dreaded EMMC issue. If your phone works there is no advantage or performance gains when using this method.
Sent from my Galaxy Nexus using Tapatalk 2 Beta-4

Porting to another HTC phone
ngh55 said:
Can this be ported to be used with EVO 4G?
Click to expand...
Click to collapse
Yes, this should be possible within an hour when I have somebody to test it together with me.
When you have a phone where you want to port the software then just come over to the freenode IRC channel G2ROOT and we will do it together. Then we can also make a posting on the according XDA section.
Web interface: http://webchat.freenode.net - channel #G2ROOT
Best regards, Catherall

I'm also going to express my apologies and I hope this wasn't taken seriously / in an offensive way.
But yeah, it's for people who have issues with their eMMC chip's.

Lol at the picture. Alright, I'm not totally sure how all this works yet, so this is me learning!

nickeedoo said:
Lol at the picture. Alright, I'm not totally sure how all this works yet, so this is me learning!
Click to expand...
Click to collapse
I don't have much grasp of how this works, but I'll put my little linux knowledge to best use.
So...recovery shares the same build blocks of a full-fledged linux operating system, like Android. It has it's own kernel, ramdisk, yadda yadda. "chroot" is a unix (also a linux) command that changes the apparent root directory for a given process. This is very useful for a number of cases, like testing an app in a virtualized environment which in other cases would have been sub-optimal, or for compatibility. As such, in our case the "given process" is the Android system itself. You basically change the root directory of the linux system (recovery) and then initialize Android on top of it.
If anyone knows more about how this works, then please do tell as I'm quite interested myself!

How it works
crestofawave said:
I don't have much grasp of how this works, but I'll put my little linux knowledge to best use. ...
If anyone knows more about how this works, then please do tell as I'm quite interested myself!
Click to expand...
Click to collapse
You pretty got the picture. The script update.zip uses the underlying kernel to chroot the new Android system. This is "simply" done by calling init (the starting point of the Android system) in the kernel files of the new booting system, which are contained in update.zip. They mount all partitions from SD card and boot the system.
Furthermore all interfering processes from recovery are set on hold using
Code:
kill -STOP <process id>
Otherwise recovery would respond on key strokes and block the screen.

@catherall I sent a sticky request for this thread. Might be a good idea if you do as well.

catherall said:
Yes, this should be possible within an hour when I have somebody to test it together with me.
When you have a phone where you want to port the software then just come over to the freenode IRC channel G2ROOT and we will do it together. Then we can also make a posting on the according XDA section.
Web interface: http://webchat.freenode.net - channel #G2ROOT
Best regards, Catherall
Click to expand...
Click to collapse
I like that idea, I'm going to #g2root tomorrow to see if the newest cm nightly can be ported for this.
EVO-4G powered by FherraZ-Mod

[GUIDE][XS/XSL]One time re-partitioning for Marshmelow ROM flashing

A Marshmellow based AOSP ROM was recently released by billchen1997. To flash it, re-partitioning of the partition table is required.To do so, following procedure can be used.
Note: This procedure doesn't work with nAOSP 6.0 ROM released by mickybart now, please find the appropriate instructions in ROM thread.
Do make a note of few things though:
Internal storage which can be accessed via PC by selecting "File transfer"option manually after connecting.
Recovery for Me was retained since I had flashed it in fota partition, hence I would recommend flashing recovery in fota partition before hand.
Performing them on PC would be convenient as some calculations are required.
Wiping all partitions before hand is recommended.
Text formatting conventions are used in the code sections to depict different meanings:
Bold : States the commands to be entered on adb.
Italic : States what values, usually which varies user to user, has to be entered at the place.
Underlined : States output shown by a certain command preceding it.
Repeated x/y/z are variables.
As pointed out by @GjorgiDxc, the phone is not directly encrypted. We need to encrypt it manually. To do so, flash only the ROM, without gapps or root, boot into ROM and encrypt the phone. More details can be found here. Encrypting data would make data partition inaccessible in TWRP.
Procedure:
Take backup of Your apps as well as the data from the internal storage (Photos, Music, Video etc) as it will all be wiped.
Boot into TWRP.
Goto mount option and untick all partitions.
On PC, using adb, type out the following commands,
Print the current partition table. Note down the starting cylinder of partition 14, It will be needed further.
Code:
[B]adb shell
fdisk /dev/block/mmcblk0
p[/B]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now delete the sdcard(15) and data(14) partition.
Code:
[B]d
15
d
14[/B]
Create new data partition which uses remaining space.
Code:
[B]n[/B]
[U]First cylinder (xxx-yyyyyy, default xxx): [/U] [I]You have to enter the start cylinder of partition 14 as read in partition table earlier.[/I]
[U]Last cylinder or +size or +sizeM or +sizeK (zzzzz-yyyyyy, default yyyyyy):[/U] [I]Enter the yyyyyy value.[/I]
Print and write the modified partition table. Note down the "Blocks" value of partition 14 here.
Code:
[B]p
w[/B]
Code:
[U]Command (m for help): [/U][B]t[/B]
[U]Partition number (1-14): [/U][B]14[/B]
[U]Hex code (type L to list codes):[/U][B] 83[/B]
One of the two paths can be followed here now. It depends on which filesystem is required for data partition, ext4 or f2fs. For ext4, follow the first subsection and for f2fs, second one.
Now the calculation needs to be done for ext4 file system. From the "Blocks" value of partition 14, subtract 16, since we have to leave 16384 bytes and each block equals 1024 bytes (16*1024=16384).
For Me, the "Blocks" value of partition 14 was 29161464. Hence, my final value was 29161464-16=29161448. Now divide the solution by 4.
Therefore, 29145080/4=7290362. Consider it as final_size. This many blocks will be allocated for the data partition. This needs to be done since the partition needs to be made using blocks size.
Now we format the data partition such that it acquires the space and as well as leaves the trailing 16384 bytes. This creates a data partition with ext4 type, allocation unit as 4096 and size in blocks as final_size.
Code:
[B]mke2fs -t ext4 -b 4096 /dev/block/mmcblk0p14[/B] [I]final_size[/I]
For f2fs file system, simply run the following command, no need of any calculation:
Code:
[B]mkfs.f2fs -r 16384 /dev/block/mmcblk0p14[/B]
Code:
[B]exit
adb push -p pure_aosp_marshmallow_r1.zip /tmp/[/B]
Now on phone, in TWRP, Flash the ROM via install option, and done!
Notes:
First Reboot is long.
If after boot it says encryption failed, let it reset the phone. Then it will work properly.
For root, flashing Update zip of SuperSU from here works.
Wiping data via TWRP menu will allocate the trailing 16384 bytes to it too, so it is not to be done.
For gapps, flash Pico gapps from here. Then after reboot and login, go to Settings, Apps>Settings icon at top right> App permissions. Now in each permission, open the permission, select show system from options and enable the permission for all system apps.
If You get error like "Error retrieving information from sever.[RPC:C:S-7:AEC-7 CDY7-E3OJ-V2TKC]" in Google Play Store and are not able to install any app, then log out and log in again into Your google account via settings.
If You copy a file and want to access it via TWRP, mount data partition and go to /data/media. Although data won't mount if You encrypt Your phone.
Credits to @SystemR89 for his tutorial as base and billchen1997, @mickybart for his instructions and TWRP.
Calculations are not needed now since micybart has modified the TWRP to leave trailing 16384 bytes at end. The TWRP can be found here.

Thanks for your guide friend. What is difference between this method and your previous method http://forum.xda-developers.com/showthread.php?p=64433804 ? I think your previous method is easier and it's not confusing.
BTW I wiped /data in twrp and I don't have any problem

@Mirhawk so what are you saying Friend? What will be the difference we get than your instruction.will it solve my battery not charching problem.?actually I used mickybarts recovery last time.so was that OK or I have to flash the official twrp to do the job

pejman97 said:
Thanks for your guide friend. What is difference between this method and your previous method http://forum.xda-developers.com/showthread.php?p=64433804 ? I think your previous method is easier and it's not confusing.
BTW I wiped /data in twrp and I don't have any problem
Click to expand...
Click to collapse
The earlier one allocated less space for user. Yeah, I agree, this one is a bit more complicated than previous one, but it is as per some of the instructions provided by billchen1997. Wiping /data with previous process works, but as it wouldn't with this process. I will have to test that if it will work.
nageswarswain said:
@Mirhawk so what are you saying Friend? What will be the difference we get than your instruction.will it solve my battery not charching problem.?actually I used mickybarts recovery last time.so was that OK or I have to flash the official twrp to do the job
Click to expand...
Click to collapse
As said above, it will allocate more usable space for user. Well, modifying of partition should not affect Your offline charging. I used the TWRP by SdtBarbarossa, if it makes any difference.

Why were you saying storage is not accessable via PC? Internal storage shows up fine for me via PC. The only issue I have is with recovery, but there should be a fix to the recovery by mickybart (he is maintaining TWRP) to recognize the new repartitioning, so I can live with that.

GjorgiDxc said:
Why were you saying storage is not accessable via PC? Internal storage shows up fine for me via PC. The only issue I have is with recovery, but there should be a fix to the recovery by mickybart (he is maintaining TWRP) to recognize the new repartitioning, so I can live with that.
Click to expand...
Click to collapse
You are able to save in internal storage using PC? And if You save a file, does it show up in /storage/emulated/0?
All I get is blank window when I open "Xperia S" icon in windows explorer.
Never mind, forgot to select the option for file transfer. Will update that now.

Mirhawk said:
You are able to save in internal storage using PC? And if You save a file, does it show up in /storage/emulated/0?
All I get is blank window when I open "Xperia S" icon in windows explorer.
Click to expand...
Click to collapse
Yes I can. I think after creating partiton14 you should type
t
14
c
I think I did that, but anyway yes i can see the whole 27GB of storage on the computer, and thats how i flash gapps. I flash rom via /tmp and gapps after it boots up. Also maybe you've missed this, but you have to toggle "File tranfer" in the notification shade, the default is "Charging cable" and it doesn't display the internal storage. Pull down notifications, tap on the one bellow USB debugging and select the second option. I'll post some screenshots maybe later, I'm doing some battery testing atm.

GjorgiDxc said:
Yes I can. I think after creating partiton14 you should type
t
14
c
I think I did that, but anyway yes i can see the whole 27GB of storage on the computer, and thats how i flash gapps. I flash rom via /tmp and gapps after it boots up. Also maybe you've missed this, but you have to toggle "File tranfer" in the notification shade, the default is "Charging cable" and it doesn't display the internal storage. Pull down notifications, tap on the one bellow USB debugging and select the second option. I'll post some screenshots maybe later, I'm doing some battery testing atm.
Click to expand...
Click to collapse
Yeah, thanks, the notification doesn't show up on lock screen.
I don't think there is any need to type "c" after creating partition, since it converts the partition to fat32 and it is not needed here.

Mirhawk said:
Yeah, thanks, the notification doesn't show up on lock screen.
I don't think there is any need to type "c" after creating partition, since it converts the partition to fat32 and it is not needed here.
Click to expand...
Click to collapse
I never knew that, still no issues with doing that
So you've missed the notification? You're able to see storage now right?

@Mirhawk try this if it works.connect device to PC.then select file transfer.then goto settings developer option and turn off the USB debugging.it worked for me

Mirhawk said:
You are able to save in internal storage using PC? And if You save a file, does it show up in /storage/emulated/0?
All I get is blank window when I open "Xperia S" icon in windows explorer.
Never mind, forgot to select the option for file transfer. Will update that now.
Click to expand...
Click to collapse
I'm able to access all 27GB in my device and PC. I did everything exactly like you instruction http://forum.xda-developers.com/showpost.php?p=64433804&postcount=1487 till item 4, then I went to wipe menu in twrp and ticked /data partition then pressed on "Repair or change file system" then pressed on resize, then it changed and shows all 27GB then I choose EXT4 then wiped all partitions on my device by twrp, then I did rest of your instruction

Screenshots
 @Mirhawk

GjorgiDxc said:
I never knew that, still no issues with doing that
So you've missed the notification? You're able to see storage now right?
Click to expand...
Click to collapse
nageswarswain said:
@Mirhawk try this if it works.connect device to PC.then select file transfer.then goto settings developer option and turn off the USB debugging.it worked for me
Click to expand...
Click to collapse
Yup, it works for Me, just had to unlock the screen to get notification.
pejman97 said:
I'm able to access all 27GB in my device and PC. I did everything exactly like you instruction http://forum.xda-developers.com/showpost.php?p=64433804&postcount=1487 till item 4, then I went to wipe menu in twrp and ticked /data partition then pressed on "Repair or change file system" then pressed on resize, then it changed and shows all 27GB then I choose EXT4 then wiped all partitions on my device by twrp, then I did rest of your instruction
Click to expand...
Click to collapse
Yeah, it would work that way since the 16384 bytes are left outside the data partition end border in the older procedure. Here, we leave the 16384 bytes inside the end boundary of the data partition. My screenshots after following this procedure with size are attached.

Mirhawk said:
Yup, it works for Me, just had to unlock the screen to get notification.
Yeah, it would work that way since the 16384 bytes are left outside the data partition end border in the older procedure. Here, we leave the 16384 bytes inside the end boundary of the data partition. My screenshots after following this procedure with size are attached.
Click to expand...
Click to collapse
We both did the same but why I lost about 1GB rather than you?

pejman97 said:
We both did the same but why I lost about 1GB rather than you?
Click to expand...
Click to collapse
In the previous method, more than 16384 bytes are left out. There 16384 cylinders*bytes_per_cylinder are left out. Hence there is a difference in size.

Mirhawk said:
In the previous method, more than 16384 bytes are left out. There 16384 cylinders*bytes_per_cylinder are left out. Hence there is a difference in size.
Click to expand...
Click to collapse
Thanks for your instructions it's clear at the the beginning. Now there is no way to use old p15 in this rom until doing like this to use all storage size. That's clear now. So, can I leave about 1G as mmcblk0p15 with vfat system just to flash an update and gapps in the future? Cause all data partition will be wiped if we reset the device.

Can anyone help me? When I try adb in PC, i receive this message: device not found.
I have the phone with TWRP and connected by Usb to the PC.
In the past, i increased the partition for lollipop without problems.
What am i doing bad??
Update:
If I connect the phone with lollipop instead TWRP i can access to the phone without problems. Adb found my de vice attached.

hi, thanks for the detailed instructions. is there any way (command) fo format as f2fs instead of ext4?

jgilalonso666 said:
Can anyone help me? When I try adb in PC, i receive this message: device not found.
I have the phone with TWRP and connected by Usb to the PC.
In the past, i increased the partition for lollipop without problems.
What am i doing bad??
Click to expand...
Click to collapse
Just connect your device to PC and open command. Write (adb devices) if the device doesn't detect while youre device is connected to PC go to advance menu in twrp and open side load and swipe then press cancel then your device should be detected by this command (adb devices)

Ok. I'm gonna try. Thanks