Database Users

Take control of your HTC CDMA HERO

I am starting this thread to provide guide to newbies (still anyone left?) for enabling them to get following
1. How to root HTC HERO SPRINT CDMA? Post: #2
2. How to backup SD card (along with nandroid backup)? Post: #3
3. How to partition SD card to get it ready for A2SD? Post: #4
4. How to install preferred ROM? Post: #5
5. How to install a custom kernel and get Overclock working? Post: #6
6. FAQ section covering Post: #7
A. How to upgrade 2GB micro-sd to 16GB micro-sd, with out hassle
B. SWAP and Dalvik-cache on SD. What can go wrong?
C. How to flash adhoc update zips?
D. How to take screenshot of phone?​Idea of this thread is to link new comers to corresponding detailed thread and not to repeat the thing here. Threads are already available for each activity above, but for a new comer, it is difficult to understand the link among them. First few posts will be updated regularly to try to make it as easy as possible for new comers.
First post is reserved for basics, explaining the over all concept. This will be followed by four more post explaining steps for each one.
Before starting, why do we need to do this? What will we get out of this, if you are a regular phone user?
Get Power to install more application
By default Android phone (OS version till 2.1, not 2.2 and later) does not allow you to install applications on SD card. SD card can be used for storing data, not application. This limits your capability to install more and more applications / games If you follow procedure four, all market applications will automatically install in SD Card.​
Overclock
All mobile phone processors speeds are configurable. Step 5 and 6 will allow you to either overclock your phone, which will increase the speed or under some critical condition, you can also reduce speed to increase battery life.​
Connect your Laptop/PC with internet through Phone
Wireless tether, which allows you to use your phone as modem.​
Use adware application without ads
Some applications requires special permission like AdFree. After installing AdFree, you can enjoy ad enabled freewares with out ad ​
If you do not foresee any requirement for above mentioned points, you can live without root.
Credits are mentioned in next set of posts as it will be actually linking to actual post. Along with link, I will build FAQ, which shall list known questions and answers.
Special credits:
1. regaw_leinad: His ROOT 2.1 thread never gave me a chance to ask a question. Gave me the required confident to root my phone.
2. nfinitefx45: For guiding my first flashing and partitioning. Even though information is available in this forum, but it is scattered. It doesn't give enough confident for a newbie to start. He just guided me with steps / links. Some of the points in this thread are based on his comments.

1. How to root HTC HERO SPRINT CDMA?
Following thread by regaw_leinad is an excellent thread providing step by step procedure.
http://forum.xda-developers.com/showthread.php?t=694572
Known issue faced:
1. Ensure that you are not running sprint update 2.27.651.6. It is explained in first and second post. If you are already running 2.27.651.6, follow second post in that thread and then follow first.
2. If you are planning to use custom Kernel and over clocking, it is suggested to use recovery image mentioned just after step 10 in that post. It will ask you to loop back to step #9. Just follow.
If you are thinking, what will you loose by downgrading to 2.27.651.5, custom ROM installation procedure will take care of same.

How to backup SD card (along with nandroid backup)?
If you want to install applications in SD card, you need to partition your SD card. This will lead to complete data loss.
Steps mentioned in the thread above will create a backup of your phone in SD card. It is advisable to keep a copy of the same in some other safe location. This will be handy, if it is required for recovery.
Option #1: Easiest way is to switch off your phone. Pull micro-sd card, mount it in your PC using a card reader. Perform a copy.
Option #2: Through phone menu (Settings -> Connect to PC -> Default connection type -> Disk drive), prepare SD card data data transfer using unmount SD card and copy data from SD card to PC. This is also safer option. This option might not work starting Android 2.2, since unmounting SD card will force close all application installed in SD card. If you are using A2SD, it works as A2SD uses different partition. Read here
In both cases, you need to ensure that you have copied/backed up /nandroid/ directory of your SD card. If you are planning to perform partition, back complete SD card to your PC.
Now you are ready for partition.

How to get partition your SD card for getting it ready for A2SD?
1.What is A2SD?
As mentioned in first post, by default Android phone (OS version till 2.1, not 2.2 and later) does not allow you to install applications on SD card. SD card can be used for storing data, not application. This limits your capability to install more and more applications / games If you follow procedure four, all market applications will automatically install in SD Card.
2. Why does it require partition?
By default all your SD cards will have FAT16 or FAT 32 partition. To run application through SD card you need EXT3 or EXT4 partition. In addition, it is advisable to provide some SWAP partition to OS, which will enable it to store data of running application in SD card.
3. Why will it lead to data loss?
Standard procedure will format SD card and re-partition it. It means you will loose data. Commercial tools are available to re-partition without data loss, but I have not tried it in recent past. If required do a google.
4. What is the procedure?
Critical : BACKUP YOUR SD CARD TO YOUR COMPUTER. Steps are in the post 2 of this thread.
Following steps are taken from http://forum.xda-developers.com/showpost.php?p=6292446&postcount=1
Step #1: Reboot into recovery. Post #9 explains the same
You will get into Android System Recovery.
Step #2: select Partition sdcard
To move up/down, you need to rotate TRACKBALL. To select the option, press TRACKBALL.
You will get into Partition sdcard menu.
Step #3: select Partition SD
Step #4: It is menu driven. Just follow instruction. I have allocated 64Mb for swap, 1024Mb for EXT and rest for data. It is not advisable to allocate more than 1024Mb for EXT.
After this step you will get back to Partition sdcard menu. Now you need to change your partition type to EXT3.
Step #5: select SD:ext2 to ext3
Step #6: As most of the ROMs are not supporting EXT4 (especially Sprint Stock ROM), do not upgrade SD:ext3 to ext4
Step #7: Press the back button on the phone to go back to the main menu.
Step #8: Select Reboot system now.
This will reboot your system. You would have lost all your SD card data. Now you are ready to flash new ROM.
Step #9: Select If you had taken backup of your data earlier, you can restore them now. In particular, to flash your ROM, you need to copy ROM ZIP file to root directory of your SD Card..
Steps for those struggling with partition option (ie step #4):
Step #4.1:
Partition sdcard?
Press HOME to confirm.
any other key to abort.
Click to expand...
Click to collapse
press HOME button
Use trackball or volume-keys
to increase/decrease size.
HOME to set (0=NONE) :
Swap-size = 32 MB
Click to expand...
Click to collapse
Using TRACKBALL select 64 MB.
Press HOME to set.
Ext2-size = 512 MB
Click to expand...
Click to collapse
Using TRACKBALL select 1024 MB.
Press HOME to set.
FAT32-size = Remainder
Continue partitioning?
Press HOME to confirm.
any other key to abort.
Click to expand...
Click to collapse
Press HOME.
It will take few minutes.
Your card is ready (with out data ).

How to install preferred ROM?
Next step is to flash a custom ROM. I successfully flashed ROM available in thread http://forum.xda-developers.com/showthread.php?t=703267
It is based on Sprint 2.27.651.6 STOCK. You need to download HeroCSprint_2276516-xxxxxxxxxxxxx from that thread.
Step #1: Download required ROM. Ex: Sprint 2.27.651.6 STOCK Deoxed w/A2SD Update 3 has HeroCSprint_2276516-... Size of the ROM will be approx 100 MB to 150 MB
Step #2: Copy downloaded ROM to root directory of SD card. It shall be available in /sdcard/. For copying, you can use the steps followed to copy files from PC to phone which you were rooting the phone by getting into adb shell. Keep the file as ZIP file only. Do not unzip.
Step #3: Reboot your phone in recovery mode as mentioned in post #9
Step #4: From Android system recovery screen select Wipe option. Rotate TRACKBALL to highlight the required option and press TRACKBALL to select
Step #5: You need to wipe data, dalvik-cache. If you are already having A2SD, you shall wipe SD:ext partition.
Select them one by one and press HOME button to wipe data.
Step #6: Go back to main menu by pressing BACK button
Step #7: Select Flash zip from sdcard
Step #8: Select the just copied ROM from the list of zip files.
Step #9: Press HOME button confirm flashing
Step #10: It will install ROM. Once completed system will go back to main menu.
Step #11: Reboot by selecting Reboot system now option.
Enjoy your new ROM.

How to install a custom kernel?
It turned out to be simpler that what I thought.
Step #1: Download required kernel.
With Sprint 2.27.651.6 STOCK Deoxed w/A2SD Update 3 ROM mentioned above, DarchKernelv4 710mhz with Free Memory Tweak For Infinitefx Kernel is found to be working.
Click to expand...
Click to collapse
Step #2: Copy the zip file Infinitefx_v4_710_M.zip to root directory of sdcard.
Step #3: Reboot you phone in recovery mode. Refer to post #9
Step #4: From Android system recovery screen select Wipe option. Rotate TRACKBALL to highlight the required option and press TRACKBALL to select
Step #5: You need to wipe dalvik-cache. As you are only updating kernel, you need not wipe data and ext partition.
Select them one by one and press HOME button to wipe data.
Step #6: Go back to main menu by pressing BACK button
Step #7: Select Flash zip from sdcard from menu using trackball
Step #8: Select the zip file copied into sdcard in step #1.
Step #9: Press HOME button
It is advised to once again wipe dalvik-cache post kernel flash.
Step #10: From Android system recovery screen select Wipe option. Rotate TRACKBALL to highlight the required option and press TRACKBALL to select
Step #11: You need to wipe dalvik-cache. As you are only updating kernel, you need not wipe data and ext partition.
Select them one by one and press HOME button to wipe data.
Step #12: Go back to main menu by pressing BACK button
Step #13: Reboot the phone by selecting 'Reboot Phone' option
Your phone is ready. 710 Kernal will by default set the clock speed as 710Mhz. You can adjust the speed by using market applications.

Frequently asked questions.
A. How to upgrade from 2GB to 16GB micro-sd
Step #1: Ensure you are using RA 1.6.2 as recovery image. It will be the last line in your phone, when you are in recovery mode (Check Post #9). Lower and upper versions are being reported as having some issue as on this date. If you are having any other version, Flash RA 1.6.2
Step #2: Take nandroid back up on you phone on old SD card and save it in your PC. (Post #2)
Step #3: Nandroid would have saved backup of your phone in SD card. Mount your SD card in your PC and take complete backup of your SD card's FAT32 partition.
Step #4: Prepare your new SD card as mentioned in post #3.
Step #5: Once you prepared your new SD card, mount it in your PC.
Step #6: Restore your backed up copy of old SD card to new SD card(on FAT32 partition)
Step #7: Boot your phone in recovery mode.
Step #8: Perform a nandroid restore. You need to restore from new SD card.
Step #9: Reboot your phone. You shall be up and running now using your new SD card.
B. SWAP and Dalvik-cache on SD. What can go wrong?
1. Enable Dalvik-cache on SD card, only if you have at least CLASS-4.
2. Enable swap on SD only if you have at least CLASS-6.
SWAP / Dalvik-cache might perform frequent read-write on your SD card, which might impact its life.
C. How to flash adhoc update zip
If you come across instruction to flash some zip file,
1. Copy that file to your /sdcard/ (root directory of SD card).
2. Reboot you phone in recovery mode. Refer to post #9. Then follow the instruction from Step #7 in this post. (ie. You need to perform Flash zip from sdcard)
D. How to take screenshot of phone
1. Connect your phone to PC
2. Ensure PC has ANDROID SDK installed
3. Goto tools directory of Android SDK.
4. Execute a batch file called DDMS
5. Select your device.
6. Then from menu, goto Device, Screen Capture (or Ctrl+S)
7. Save the screenshot
8. Detailed steps can be found at how-to-take-screenshots-of-android-device or at how-to-capture-screenshot-on-android-phones

How to remove default applications?
Even though steps are simple, it is advised to follow it under expert guidance. You shall know what you are doing and do it properly.
Step #1: Get into android SDK tools directory to access adb program. You should have learnt it by now. (Or refer to post #2 and ensure adb devices lists your device)
Better to keep a backup of application you are going to remove.
Step #2: Reboot your phone in recovery mode (Post #9). Expert might state it is not required, but will prefer this way.
Step #3: Enter following set of commands one by one in command prompt.
md c:\backup\AfterRootAPKBackup\
adb shell mount -v /system
adb pull /system/app/ c:\backup\AfterRootAPKBackup\
adb shell umount -v /system
Click to expand...
Click to collapse
First command will create a directory in your PC to keep backup.
Second command will mount internal ROM and make it available for you to play.
Third command will make a copy of all installed applications.
Fourth command will unmount the internal ROM.
Your mobile shall still be in recovery mode.
Step #4: List contains application, I have removed 20 days back and my mobile is still working without any issue. To remove them get into adb shell first.
adb shell
Click to expand...
Click to collapse
You are in adb shell prompt, which shows #
Step #5: Enter following set of commands one by one in adb # prompt.
mount -v /system
cd /system/app/
rm Sprint*
rm Stock*
rm HtcFacebook.apk
rm HtcFootprints.apk
rm HtcFootprintsWidget.apk
rm HtcMusic.apk
rm HtcRingtoneTrimmer.apk
rm Field*
rm Face*
rm Flickr*
rm amazonmp3.apk
rm com.htc.MusicWidget.apk
rm com.htc.StockWidget.apk
cd /
sync
umount -v /system
reboot
Click to expand...
Click to collapse
First command mounts the internal ROM for read/write.
Second command gets you into application directory.
All rm commands removes unwanted applications. Ensure android is case sensitive and you shall respect upper and lower case. Run these command at your own risk.
cd / brings you back to root directory.
sync ensures that it is actually deleted. It is advisable to wait for few (5 to 10) sec between sync and umount command
umount command mounts it back.
reboot command reboots your mobile.
Step #6: You can reboot your mobile by typing following in command prompt
adb shell reboot
Click to expand...
Click to collapse

How to reboot into recovery mode
Simple option:
Step #1: Turn phone off
Step #2: Hold Home button while pressing power on, you'll get to the recovery screen
Complex option:
Step #1: Goto android SDK tools directory in command prompt.
Step #2: In command prompt type
adb shell
Click to expand...
Click to collapse
Step #3: In '#' prompt of adb shell, type
reboot recovery
Click to expand...
Click to collapse
Command reboot recovery will reboot your phone into recovery mode. Simple reboot will reboot it in normal way.

Being a noob yourself you probably shouldve checked out the sticky threads at the top of every forum. There is a wiki already for this kind of stuff...Maybe this could be combined into the wiki? Perhaps? You should be able to modify the wiki with your info. Good info either way.

sekarpdkt said:
Simple option:
Step #1: Turn phone off
Step #2: Hold Home button while pressing power on, you'll get to the recovery screen
Complex option:
Step #1: Get into adb shell.
Step #2: reboot recovery
Command reboot recovery will reboot your phone into recovery mode. Simple reboot will reboot it in normal way.
Click to expand...
Click to collapse
another way to do this is through fast boot, which i personally use, or the app quick boot
for installing custom rom remember wiping, kernel-make sure it's for your build lol

VinceOB said:
Being a noob yourself you probably shouldve checked out the sticky threads at the top of every forum. There is a wiki already for this kind of stuff...Maybe this could be combined into the wiki? Perhaps? You should be able to modify the wiki with your info. Good info either way.
Click to expand...
Click to collapse
Great suggestion but Wiki is down.

danbula said:
Great suggestion but Wiki is down.
Click to expand...
Click to collapse
Uggggh does that page EVER stay up?

Great how-to. Thank you for your time and effort.

nwkenning said:
Great how-to. Thank you for your time and effort.
Click to expand...
Click to collapse
Thanks for comment. If you have steps for those two missing points, let me know. Will update.

Nice job! I expect to link to this info often when helping out the new folks. I was one once and was guilty of not reading as much as I should have. I think they get intimidated by having a question and then seeing 1,800 posts! Yes, the search button is there but, you know..... This would have helped me a bunch.

Great idea. Thanks for the work. This would have come in quite handy when I was first getting started. I think I read for 3 weeks before I tried my first root and rom.

I read that it is a good idea to wipe dalvik after flashing a new kernel

Wiki is always down
So it seems
Sent from my HERO200 using XDA App

great writeup, thanks. bookmarked, wiki can be cluttered sometimes.

CWM 5.5.0.4 for Gtab--NVFLASH only (BETA from team DRH)

THIS IS NOT CWM FLASHABLE. YOU MUST USE NVFLASH
Edit: It has come to my attention that the CWM is 5.5.0.2. This error has since been corrected. Sorry folks. I'm an idiot.
Hey, i hope this doesn't bother anyone but i compilied and easy zip for NVFLAshing the new CWM.
Thanks Fosser, Team DRH, and the BishopofTechnology (all of whoms work this is, i just put it in one place)
Included is the NVflashable info, the drivers for APX, and the new version of CWM.
Do this @ your own risk, i'm not responsible for any problems (i did test it three times, with each version of CWM, if that counts for anything)
Step 1) Get into APX mode (power + Vol-) [the screen will go black. that's what you want
Here's what the Bish says:
Step 2) Connect the GTab to the PC via the USB cable.
if your PC loads the USB driver and connects to the GTab, SKIP to the “Using NVFlash” section.
if the WINDOWS PC fails to load the driver, just click through Start/Control Panel/Device Manager and find “APX” listed in the devices with a yellow “!” (exclamation point) on the icon.
Select the APX item and find the “Update Driver” button and click it.
When it asks where to search, choose the “local computer” manual selection choice and tell it to Browse to the "Flash USB Drivers".
If you go back to Device Manager after the Windows install has completed, it will show the nVidia USB drivers near the top of the USB device list.
Click to expand...
Click to collapse
Step 3) Run the "nvflash_gtablet.bat"
A CMD prompt will pop up, let it do it's thing (don't stop or unplug during). Give it about a minute or until the CMD prompt disappears. You will the get a message that says "Entering NvFlash recovery mode / Nv3p Server"
At this point is should be okay to restart your tab. I'm running Flashback and had no problems staring up.
If you want to check the new CWM, hold the power + Vol+ when restarting and it should put you into recovery.
CONGRATS! You have the new recovery in preparation for ICS.
Once again, none of this is my work--i just put it into a convenient place.
Thanks again to all the Devs and enthusiasts. You make the Gtab worth having!
Edit 1:
Here is the MD5 check: 3DD468C48A3515E6E5A1C1236FF5068E
Edit 2:
The update recovery is with the normal sized Recovery.
Edit 3: 1) It seems this version partitions the external sd card when you choose to partition sd card. 2) choose zip from internal sdcard seems to use the internal memory 3) "FORMAT SDCARD" will FORMAT MICROSD CARD! YOU WERE WARNED

Alright. Download tested and verified. this is deff 5.5.0.4!
sorry again folks

Anyone that is interested in installing this via CWM, I created a CWM flashable verison from fosser2's download. Here is a link to the "normal font" version http://dl.dropbox.com/u/36150173/CWMR5504_recovery.zip. If you want the "big font" version, all you have to do is open the zip, delete the recovery.img, rename the Team DRM/fosser2/plastikman supplied version to recovery.zip & then add it to the zip.
I have installed this on 2 of my gTabs (one gTab Comb v3.3, the other CCCv8) and did not had any issue installing it this way.
Just a few notes on this version; it does give you the ability to flash from both the internal sd & external sd but uses a different naming convention though..."sdcard" is the name used for the external microsd slot and "internal sd" is what we would normally call sdcard. This version also appears to have fixed the "reboot recovery" bootloop bug of cwm3.0.2.8 (or aleast bypassed it)...when I selected "reboot recovery" it did the same as "reboot system now" (as I was doing this I crossed my fingers hoping it wasn't going to bootloop me...yea..no bootloop).
CWMR is touch capable. You scroll/select in 3 different ways...you can either use the capacitive buttons (which have been remapped to...Search is "select", Home is "scroll up", Menu is "Scroll down" and Back is "back"), you can also use the on screen touch controls (back, up, down & return), or you can also swipe up and down to scroll up/down and swipe sideway to select.
Al
PS:
WARNING: This is the beta6 release. The op page over in the Slatedroid gTablet Laboaratory says that selecting repartition will only repartition the EXTERNAL SD. Two users have reported magic value mismatch after repartioning with this version. plastikman, who created it says he is looking into it.

So u can install from the older cwm that's in flashback like any other zip?
Sent from my SAMSUNG-SGH-I997 using XDA App

why does it only boot into CWM mod now? it would boot normally when i was on CWM 3.x.x.x

Yes but beware of repartition bug
lsu205 said:
So u can install from the older cwm that's in flashback like any other zip?
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
Yes you can. I installed on both mine from CWM 3.0.2.8.
Please note the warning I put on my previous post! It probably isn't a good ides to "repartition" with this version until plastikman finds the bug. If you need to repartition (which shouldn't be very oftern) you can always flash the old CWM (or stock recovery) via this version. The recoveries are so small that I keep a copy of each on the tablet just in case.

is the download ok i have try to unzip it and it gives me an error file is not a zip file

Alternate location
wuilly said:
is the download ok i have try to unzip it and it gives me an error file is not a zip file
Click to expand...
Click to collapse
You don't need to unzip it but it does need to be a vailid zip.
Yes, the download is OK from dropbox. I just redownloaded it to my PC & tested the archive. No erors found.
I also put it on mediafire...try this link http://www.mediafire.com/download.php?qg3n084hfu783i2 & see if it's any different for you.
Al
---------- Post added at 09:23 PM ---------- Previous post was at 09:15 PM ----------
jamcar said:
why does it only boot into CWM mod now? it would boot normally when i was on CWM 3.x.x.x
Click to expand...
Click to collapse
It shouldn't (and didn't for me). Are you sure you didn't select accidentally hit "reboot recovery" instead of "reboot system now" (since you were still in CWM3.0.2.8 untill you reboot)? If you did accidentally hit reboot recovery then it would have put you in a CWM bootloop.
There are 2 ways I've used to fixed a CWM bootloop (yes I've accidentally hit reboot recovery too)..one was is to use nvflash to format partition 7 (MSC) and the other way is to use CWM to flash stock recovery and then install CWM3.0.2.8 (for b/l1.2) via stock recovery. Formatting MSC is the fastest, but most people I suggest these fixes to choose to do the stock recovery route. If you want detailed instruction for either, let me know.
Al

Great work and thanks for putting in one spot. I'll probably wait till a ICS ROM is released with but must say that this is a great first step till we get it. Cant wait for 10" of ICS....my cappy luvs ICS...

J017373 said:
Edit 3: 1) It seems this version partitions the external sd card when you choose to partition sd card. 2) choose zip from internal sdcard seems to use the internal memory 3) "FORMAT SDCARD" will FORMAT MICROSD CARD! YOU WERE WARNED
Click to expand...
Click to collapse
What does the recovery do when you don't have a microSD card in the slot. The /etc/recovery.fstab file is setup to fall back to using the internal SD card like CWM-4.0.1.5 is. Does it work on the internal SD card if no external one is present?
---------- Post added at 09:23 PM ---------- Previous post was at 09:19 PM ----------
aabbondanza said:
and the other way is to use CWM to flash stock recovery and then install CWM3.0.2.8 (for b/l1.2) via stock recovery.
Click to expand...
Click to collapse
That procedure only works as a side effect. Simpler to wipe MSC directly. See post #3 of this thread.
Stash that zip file on you SD card, and if you accidentally select "Reboot recovery", just "flash" it to fix the always boots-to-recovery problem.

Just installed using CWM recovey and all is well. Just to test I took out my external sd card and when I went to update from sdcard it showed the content of the internal. So I am guessing that if one would decided to partition there internal sdcard they might need to pull there external out first. Then boot up recovery for there updates.

rajeevvp said:
What does the recovery do when you don't have a microSD card in the slot. The /etc/recovery.fstab file is setup to fall back to using the internal SD card like CWM-4.0.1.5 is. Does it work on the internal SD card if no external one is present?
---------- Post added at 09:23 PM ---------- Previous post was at 09:19 PM ----------
That procedure only works as a side effect. Simpler to wipe MSC directly. See post #3 of this thread.
Stash that zip file on you SD card, and if you accidentally select "Reboot recovery", just "flash" it to fix the always boots-to-recovery problem.
Click to expand...
Click to collapse
Just can't keep up with you raj...why did it take you 2 months to come up with the flashable msc format? Just kidding. I got the format msc from that very thread back in October. Everyone I've run into that is in a CWM loop I've given them the option of formating msc (via nvflash) or flashing stock recovery/then CWM. In every case they have always chosen to flash stock recovery & then flash 3028 (probably because most of the people I help are pretty new to the gTab). I think now they will choose the format via flash method. Thanks for the tip.
Just a question though. Exactly what is the CWM kernel writing to MSC to cause the loop? I assume it is the bootloader that checks for the rocker switch position & some mysterious bit on MSC to determine which kernel to load (but I'm just guessing). But if that is correct then why does flashing stock recovery, doing a normal boot & then flashing CWM fix the problem too (so I'm guessing I am wrong about my guess)? In any case can you explain why it works that way?
Al

When ahead and changed back. When trying to downgrade to a 2.2 rom ended up with a mix match error on boot up. Looked good for what it is. Expecially liked the touch option on it, but it needs some work.

nobe1976 said:
When ahead and changed back. When trying to downgrade to a 2.2 rom ended up with a mix match error on boot up. Looked good for what it is. Expecially liked the touch option on it, but it needs some work.
Click to expand...
Click to collapse
There are a couple of problems that I noticed with this version of CWM, and which might be responsible for your problems.
1. Roebeet's gtablet.cfg file which almost everybody uses to nvflash back to the 1.2 stock ROM has a bug in the system.img size calculation:
Code:
$ [B]fgrep size= roebeet.cfg[/B]
size=3145728
size=131072
size=2097152
size=131072
size=4194304
size=16777216
size=33554432
size=16777216
size=16777216
size=[B]259715200[/B]
size=0xFFFFFFFFFFFFFFFF
The second last line is the size of the "system" partition and it is misaligned. Every other partition is correctly rounded up to end at the gTablet's NAND flash erase size (128K). Compare with bekit's gtablet.cfg:
Code:
$ [B]fgrep size= bekit.cfg[/B]
size=3145728
size=131072
size=2097152
size=131072
size=4194304
size=16777216
size=33554432
size=16777216
size=16777216
size=[B]209715200[/B]
size=0xFFFFFFFFFFFFFFFF
Here all the partitions--including the last which uses the remaining available space--are rounded up to a 128K boundary. Looks like roebeet just added 50M to bekit's system.img size without rounding it up. The correct value should've been (using roebeet's system.img size as NUM):
Code:
$ [B]( NUM=$((259715200)); echo $(( (NUM + ((1<<17)-1)) & ~((1<<17)-1) )) )
[/B]259784704
--which brings us to problem no. 2:
2. The CWM-5.5.0.4 Beta 6 has a "cmdline" file containing NAND flash partition sizes which overrides the user's partition sizes read from the Partition Table. This is fine if the sizes are the same, but, a bad idea otherwise. In this CWM, the cmdline file sets "system" to be what we calculated above (259784704) but, which disagrees with the size in the PT (259715200).
Use the zip file in the attachment to empty the cmdline file out. This will cause the partition sizes to be read from the PT on the NAND flash.
My recommendation is that:
1. Users nvflash to 1.2 using either
a) the attached gtablet.cfg which has all the partitions correctly ending at 128K boundaries or
b) bekit's original gtablet.cfg. (This option is what I recommend. The "cache" partition is used for OTA updates and if it is much smaller than the "system" partition--like in roebeet's gtablet.cfg, then, depending on the size of the image, automatic updates might fail.)
2. Install the new CWM-5.5.0.4 Beta 6, and then immediately flash the attached zip file to empty out the cmdline file.

aabbondanza said:
why did it take you 2 months to come up with the flashable msc format?
Click to expand...
Click to collapse
Didn't think adb was going to be difficult for people who have no problem with nvflash...
Just a question though. Exactly what is the CWM kernel writing to MSC to cause the loop?
Click to expand...
Click to collapse
I looked at this sometime back and its complicated. I'll make a post on this later this weekend after I've looked at VS's newly posted 1.2 kernel patch.
I assume it is the bootloader that checks for the rocker switch position & some mysterious bit on MSC to determine which kernel to load (but I'm just guessing).
Click to expand...
Click to collapse
For "mysterious bit" substitute "string", but, you are correct.

Have a user over at slatedroid tried it & still got this error.
Magic value mismatch
Critical failure: Unable to start kernel.
Unrecoverable bootloader error (0x00000002)
Trying to get more info on exactly what he did to get the error.
Al

CWMR5504 Fixed
aabbondanza said:
Have a user over at slatedroid tried it & still got this error.
Magic value mismatch
Critical failure: Unable to start kernel.
Unrecoverable bootloader error (0x00000002)
Trying to get more info on exactly what he did to get the error.
Al
Click to expand...
Click to collapse
Thanks to rajeevp!!
Plastikman verified rajeevvp was correct and has issued an updated CWMR. Here it is in a flashable format http://dl.dropbox.com/u/36150173/CWMR5504_recovery.zip. He switched from using pershoot's kernel (which required the command line) to using the stock kernel. I tested the new version to install a rom, do a factory data reset, a wipe cache, a wipe dalvik & a fix permissions. All worked normally. Give it a try. I also corrected the links in my previous posts to point to the updated version.
Al

aabbondanza said:
Thanks to rajeevp!!
Plastikman verified rajeevvp was correct and has issued an updated CWMR. Here it is in a flashable format http://dl.dropbox.com/u/36150173/CWMR5504_recovery.zip. He switched from using pershoot's kernel (which required the command line) to using the stock kernel. I tested the new version to install a rom, do a factory data reset, a wipe cache, a wipe dalvik & a fix permissions. All worked normally. Give it a try. I also corrected the links in my previous posts to point to the updated version.
Al
Click to expand...
Click to collapse
Thank you. This worked well for me, since I was not inclined to do the nvflash thing. I was able to boot back into my Beasty+Clemsyn rom without incident. Tested by rebooting again and was able to boot into the rom with no issues.

aabbondanza said:
He switched from using pershoot's kernel (which required the command line) to using the stock kernel.
Click to expand...
Click to collapse
... and in the process also brought back the always-reboots-into-recovery problem, right? Whereas with the pershoot kernel "Reboot Recovery" would just reboot the tablet into the ROM?
BTW, the pershoot kernel doesn't need a cmdline file: craigacgomez's CWM-4.0.1.5 too has a pershoot kernel and its cmdline file is empty. As I mentioned before: if the cmdline file is empty, then the bootloader will construct a cmd line for the kernel.

to install the cwm recovery do I simply transfer the zip to the internal sdcard and flash zip from sdcard as if it were a rom?

[HOWTO] Unbrick your i9000 / Galaxy S

I've gotten into the habit of running all kinds of ROMs and sometimes they just blow up. Usually a reboot suffices but the last crash caused my phone to only bootloop and I couldn't get into recovery anymore, thankfully download mode still worked. This will focus on how to get your phone back to life, provided you can access download mode.
Steps this guide will walk you through:
Calm down a bit
Get everything you need to fix your phone
Do the magic
Boot your phone
Rejoice
Step 0: Backup
I can't stress this enough. Once you've really bricked your phone there's a chance you might not be able to access the data that's on there anymore. So, if there's stuff on your phone you care about, just backup it from time to time.
Step 1: Calm down
There's a myriad of exercises you can do to calm down, meditate, go for a walk/swim/jog, go to the gym, whatever works for you. Just chill out for a second because being in a completely panicked state is not going to help you to recover your phone.
Step 2: Get the tools in place
We need a few tools to fix your phone:
Heimdall version 1.3.1. DO NOT download 1.3.2 it has issues with uploading large files
Windows: https://github.com/downloads/Benjamin-Dobell/Heimdall/heimdall-suite-1.3.1-win32.zip
Mac: https://github.com/downloads/Benjamin-Dobell/Heimdall/heimdall-1.3.1-mac.dmg
Debian AMD64: https://github.com/downloads/Benjamin-Dobell/Heimdall/heimdall_1.3.1_amd64.deb
Debian i386: https://github.com/downloads/Benjamin-Dobell/Heimdall/heimdall_1.3.1_i386.deb
Heimdall package of 2.3.6/XWJVZ: http://www.mediafire.com/?3v35chw9a8a2wmw
CFRoot for 2.3.6/XWJVZ: http://download.chainfire.eu/130/CF-Root/SGS/CF-Root-XX_OXA_JVZ-v4.3-CWM3RFS.zip
Once you've downloaded everything:
Install Heimdall (run the installer)
On Windows the link I provided also includes the GUI
For Mac and Linux the link I provided only includes the command line binary, we don't want to use the GUI for this
Extract the Heimdall package of 2.3.6.tar.gz to a directory, you should end up with the following files:
boot.bin
cache.rfs
dbdata.rfs
factoryfs.rfs
firmware.xml << delete it, we're not going to need it
modem.bin
params.lfs
Sbl.bin
s1_odin_20100512.pit << delete it, we're not going to need it
zImage << delete it, we're not going to need it
Extract the CF-Root-XX_OXA_JVZ-v4.3-CWM3RFS.zip, this contains only one file: zImage, put it next to Sbl.bin
If the Heimdall installer asked you to reboot your machine but you didn't, do it now. That will make sure the drivers are loaded.
What we've done right now is set up your machine so that it's ready to flash your i9000 back to a Samsung release of Gingerbread. The astute reader might notice I'm telling you to delete the zImage (kernel) from the Heimdall package. This is true but we're replacing it with the one from CFRoot so you can flash a rooted stock instead of first flashing stock and then flashing CFRoot on top. Some people advice against this approach but it has never caused me issues.
Step 3: Do the magic
Now we're actually going to flash your phone. We're going to do this from the command line because the Heimdall GUI is a bit twitchy when it comes to flashing without a PIT-file. The command line has no such issue and will just download the PIT from your device and use that.
Windows:
Find out where Heimdall was installed (probaly %PROGRAMFILES%\Heimdall)
Copy all the files (zImage, Sbl.bin and so forth) into the directory where the heimdall executable is located
Go to the location of cmd.exe, right-click on it and select: Run as Administrator
Now cd to the directory Heimdall was installed
Issue a dir on the commandline to verify all the files (heimdall.exe and the rest) are there
Mac / Linux:
Heimdall was probably installed into /usr/bin so all you need to do is open a Terminal of your choice and see if running the heimdall command results in heimdall output or a command not found.
Open a Terminal
cd to the location of zImage, Sbl.bin and the other files from Step 2
Flashing:
Use the 3-button combo to put your phone into Download mode: Volume Down + Home + Power and connect your phone over USB to your computer.
Windows, issue the following command:
Code:
heimdall.exe flash --primary-boot boot.bin --cache cache.rfs --factoryfs factoryfs.rfs --dbdata dbdata.rfs --modem modem.bin --param param.lfs --secondary-boot Sbl.bin --kernel zImage
Mac / Linux, issue the following command:
Code:
sudo heimdall flash --primary-boot boot.bin --cache cache.rfs --factoryfs factoryfs.rfs --dbdata dbdata.rfs --modem modem.bin --param param.lfs --secondary-boot Sbl.bin --kernel zImage
If all went well you should get output similar to this:
Code:
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 0
Downloading device's PIT file...
PIT file download sucessful
Uploading KERNEL
100%
KERNEL upload successful
Uploading MODEM
100%
MODEM upload successful
Uploading FACTORYFS
100%
FACTORYFS upload successful
Uploading DBDATAFS
100%
DBDATAFS upload successful
Uploading CACHE
100%
CACHE upload successful
Uploading IBL+PBL
100%
IBL+PBL upload successful
Uploading SBL
100%
SBL upload successful
Uploading PARAM
100%
PARAM upload successful
Ending session...
Rebooting device...
Your device will now reboot. If it doesn't and stays at a black screen, just pull the battery, put it back in and turn it on.
Step 4: Boot your device
Just let the phone boot but don't unlock your SIM-card / use it. Once it's is done booting for the first time just shut it down and now boot into Recovery Mode: Volume Up + Home + Power.
From here you can go into the Mounts and Storage section and then into the Mount USB menu. Now your phone will make it's storage available over USB so you can recover files you've lost or upload a zip-file to flash a new ROM.
Step 5: Rejoice
Your phone is now back into a workable state with a fully functional Recovery so you can now start flashing your fancy ROMs again.
A few pieces of advice:
Before you flash anything else: data/factory reset and wipe your cache
Before you flash anything else: flash CM 9.1.0, twice. The first time will upgrade your Recovery to 6.x but will then bootloop so you need to flash it again.
If you want to flash a JellyBean ROM, flash CM 9.1.0 first. If you don't and try to upgrade from Gingerbread (2.3.6) to JellyBean in one go you'll probably end up with an invalid IMEI (no idea why this happens, it just does)
Good luck!

Hi,
Thanks for the guide, i got 90% there and the program closed. This is what I got:
Uploading KERNEL
100%
KERNEL upload successful
Uploading MODEM
100%
MODEM upload successful
Uploading FACTORYFS
100%
FACTORYFS upload successful
Uploading DBDATAFS
100%
DBDATAFS upload successful
Uploading CACHE
100%
CACHE upload successful
Uploading IBL+PBL
100%
ERROR: Failed to confirm end of file transfer sequence!
IBL+PBL upload failed!
Ending session...
Rebooting device...
Click to expand...
Click to collapse
Please HELP me
What do I do from here??

battznz said:
Hi,
Thanks for the guide, i got 90% there and the program closed. This is what I got:
Please HELP me
What do I do from here??
Click to expand...
Click to collapse
That one is in my experience either caused because you supplied a PIT-file or because you've got a funky version of Heimdall.

how about when the phone can't get to download mode :/
usb jig?

microMXL said:
how about when the phone can't get to download mode :/
usb jig?
Click to expand...
Click to collapse
try solutions in My Android Solutions
Use only ROM and solution for your model and Wipe x3
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card....
(Do remember to backup your contacts, data, images etc and also your EFS folder before flashing a ROM and make sure you have more than 50% battery charge before you attempt any sort of flashing.)

The link for Heimdall version 1.3.1. (Windows) you posted has no Installer inside.
I desparetely need to unbrick my Gaaxy S. Any solutions?

SpartanWarrior said:
The link for Heimdall version 1.3.1. (Windows) you posted has no Installer inside.
I desparetely need to unbrick my Gaaxy S. Any solutions?
Click to expand...
Click to collapse
try download from My Android Collections

Phone stuck in bootloop, possible corrupt internal memory?
HI,
Thanks for your post, as a noob I find posts like yours great as they are easy to follow, and have all the info in one spot.
I have followed everything that you said to do, however, when my phone reboots after cmd successfully finishes, it boots into recovery, and says the following:
[QUOTE]--Installing Package...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Successfully installed package.
--Copying media files...
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:Can't mount /sdcard
your storage not prepared yet. please use UI men
u for format and reboot actions.
Media files copy failed.
--Deleting files...
E:failed to mount /data (File exists)
E:delete_data_files:Can't mount /data
your storage not prepared yet. please use UI men
u for format and reboot actions.
--Updating filesystem...
verifying the filesystem. please wait.
already updated filesystem. finished
Succesfully updated filesystem.
--Wiping cache...
Formatting /cache...
Cache wipe failed.
--Applying Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/CHN/system/'.
Successfully applied multi-CSC.[/QUOTE]
If I hit "reboot system now" it comes up with the Galaxy S logo, then switches off, then repeats itself, the only way to stop it is to take the battery out. I can still access both recovery and download mode at this stage.
I bought this phone cheap off someone who had installed a custom ROM which had messed the phone. I am trying to get it working again, but I think I may only have made it worse . The phone is not recognizing any SDcard, or its own internal memory. When the phone was working, if you went into settings under memory it said "Internal: 0.00B free of 0.00B" and even though there was an SDcard in it, it said "Please insert SD card"
Any help would be much appreciated.
Thanks

mars777jd said:
E:failed to mount /data (File exists)
E:delete_data_files:Can't mount /data
your storage not prepared yet. please use UI men
u for format and reboot actions.
Click to expand...
Click to collapse
try to flash a Ezbase Rescue or Darky resurrection Kit from My Android Collections
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card....
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu>Settings>Applications>Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3

xsenman said:
try to flash a Ezbase Rescue or Darky resurrection Kit from My Android Collections
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card....
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu>Settings>Applications>Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3
Click to expand...
Click to collapse
Hi,
I tried EzBase Rescue, with the following result:
-- Copying media files...
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:Can't mount /sdcard
your storage not prepared yet. please use UI men
u for format and reboot actions.
Media files copy failed.
-- Wiping data...
Formatting /data...
E: format_volume: rfs format failed on /dev/block/mmcblk0p2
Formatting /dbdata...
Formatting /cache...
Deleting Meta Data
Data wipe failed.
-- Appling Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/CHN/system/'.
Successfully applied multi-CSC.
Click to expand...
Click to collapse
I will try the resurrection kit...

mars777jd said:
Hi,
I tried EzBase Rescue, with the following result:
I will try the resurrection kit...
Click to expand...
Click to collapse
Couldn't seem to find a link to the resurrection kit that worked properly. All other rescue packages either result with bootloop or the above error messages in recovery mode.

mars777jd said:
Couldn't seem to find a link to the resurrection kit that worked properly. All other rescue packages either result with bootloop or the above error messages in recovery mode.
Click to expand...
Click to collapse
you can try http://depositfiles.com/files/ro6fnlr38 or http://depositfiles.com/files/zay0if5x7 for Darky and a solution from My Android Solutions for
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card....
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu>Settings>Applications>Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3

well just for the record, mine didn't work neither with usb jig, now I have a pretty nice paperweight. *sighs*

microMXL said:
well just for the record, mine didn't work neither with usb jig, now I have a pretty nice paperweight. *sighs*
Click to expand...
Click to collapse
usb jig can only work when USB slot is not damaged or misaligned , check usb connection problems in My Android Solutions or read this thread

mars777jd said:
HI,
Thanks for your post, as a noob I find posts like yours great as they are easy to follow, and have all the info in one spot.
I have followed everything that you said to do, however, when my phone reboots after cmd successfully finishes, it boots into recovery, and says the following:
[QUOTE]--Installing Package...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Successfully installed package.
--Copying media files...
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:Can't mount /sdcard
your storage not prepared yet. please use UI men
u for format and reboot actions.
Media files copy failed.
--Deleting files...
E:failed to mount /data (File exists)
E:delete_data_files:Can't mount /data
your storage not prepared yet. please use UI men
u for format and reboot actions.
--Updating filesystem...
verifying the filesystem. please wait.
already updated filesystem. finished
Succesfully updated filesystem.
--Wiping cache...
Formatting /cache...
Cache wipe failed.
--Applying Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/CHN/system/'.
Successfully applied multi-CSC.
Click to expand...
Click to collapse
If I hit "reboot system now" it comes up with the Galaxy S logo, then switches off, then repeats itself, the only way to stop it is to take the battery out. I can still access both recovery and download mode at this stage.
I bought this phone cheap off someone who had installed a custom ROM which had messed the phone. I am trying to get it working again, but I think I may only have made it worse . The phone is not recognizing any SDcard, or its own internal memory. When the phone was working, if you went into settings under memory it said "Internal: 0.00B free of 0.00B" and even though there was an SDcard in it, it said "Please insert SD card"
Any help would be much appreciated.
Thanks[/QUOTE]
Same happens to me. Any idea on what's going on?

vindikleuk said:
it said "Internal: 0.00B free of 0.00B" and even though there was an SDcard in it, it said "Please insert SD card"?
Click to expand...
Click to collapse
explain what is your phone model, if you had lag fix applied before and what you had done and what is the exact message you are getting when you try to boot .
Need to know what is your phone model . Check Here to chose your forum/Guide by Version of your phone or you will have more problems by using wrong solutions due to different versions of Galaxy S
you can get a rescue kit from My Android Collections and or a solution from My Android Solutions
Need a guide, look into My Guides and Manuals
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card, after flashing and reboot , insert them back
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu> Settings> Applications> Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3

xsenman said:
explain what is your phone model, if you had lag fix applied before and what you had done and what is the exact message you are getting when you try to boot .
Need to know what is your phone model . Check Here to chose your forum/Guide by Version of your phone or you will have more problems by using wrong solutions due to different versions of Galaxy S
you can get a rescue kit from My Android Collections and or a solution from My Android Solutions
Need a guide, look into My Guides and Manuals
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card, after flashing and reboot , insert them back
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu> Settings> Applications> Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3
Click to expand...
Click to collapse
Well what happened is this:
I saw this phone going cheap on eBay by someone who said that they "had tried flashing a custom ROM, and now the camera won't work due to a memory error." I had successfully flashed CM7 to a Nexus One, so I wanted to see if I could fix it.
I don't know what ROM he tried to install, but at that point the phone still booted. I could use the phone and all functions that didn't need free memory (ie camera). I went into settings, and, like I mentioned, although there was a micro-SD card the phone reported "0.00B free of 0.00B Internal" and "Please insert an SD card" for external. I thought it may have been a problem with the SD card, so I formatted it on the computer. Same result.
I then proceeded to flash a known trusted stable ROM to the phone. I opted for CM9 with CWM for I9000. This is where I first ran into problems. I was using fastboot at the time, and always, after flashing anything I would get these results (see pics.) So I downloaded Odin, and after trying several different things from various wiki's and guides on xda and other sites, I believe I have successfully wiped any existing OS, and any custom recoveries.
The phone's model is GT-I9000. The SSN is I9000GSMH. I also have the IMEI and S/N. From my understanding, it was originally locked to Vodafone, and was unlocked by the previous owner.
So far I have tried flashing:
CM9
DarkyRom_10.2 Resurrection
ezbase gb
SGS_Rescue_kit-13-1-2012
plus a few different individual pda, csc, bootloader files.
I am again going to try DarkyRom_10.2 Resurrection, once I can get Odin to recognize my phone.
Is there any thing else I can try? Or should I try to sell my phone for parts?
I really appreciate everyone's help
Thank you so much

mars777jd said:
Is there any thing else I can try? Or should I try to sell my phone for parts? I really appreciate everyone's help
Thank you so much
Click to expand...
Click to collapse
you may need to repeat flash at least 3 times, first with 512 PIt and repartition, second with 803 Pit NO REPARTITIONING and finally a normal flash without PIT, use JVU or JVZ ROM

xsenman said:
you may need to repeat flash at least 3 times, first with 512 PIt and repartition, second with 803 Pit NO REPARTITIONING and finally a normal flash without PIT, use JVU or JVZ ROM
Click to expand...
Click to collapse
OK, I will try that, do you know where to find those?

mars777jd said:
OK, I will try that, do you know where to find those?
Click to expand...
Click to collapse
in My Android Collections

[Tutorial] LG Gpad v410 5.1 to 4.4 downgrade, root, & internal storage fix.

EDIT: If you are coming here for the first time, this guide should still work, but @PorygonZRocks has created a flashable zip that should deal with a lot of these issues automatically. You can check out his post here:
https://forum.xda-developers.com/showpost.php?p=75787067&postcount=699
This method will indirectly allow you to root the LG Gpad v410 after it has been upgraded to Lollipop 5.1.1. Yes. Rooting LG v410 Lollipop. It's through a downgrade, but it works.
It took a while to get working, but here's how I did it. The process is straightforward, but the details matter greatly. You will brick your device if you mess up. Please read everything *first* before you do anything. Be sure you understand the process. I'll try to explain what's going on along the way.
An external SD card is extremely helpful for this process. You *could* adb push everything, but that will tedious.
First, you need some files.
The 4.4.2 KDZ which is a TEST OS, but it can be rooted and it downgrades to a Bump'able bootlaoder:
http://forum.xda-developers.com/g-pad-10/general/kdz-lg-g-pad-7-0-v410-t3224867
The LG 2014 Flash Tool:
http://www.mediafire.com/download/fwrcd3pdj0svjtb/LG_Flash_Tool_2014.zip
Android LG Drivers:
https://www.androidfilehost.com/?fid=24052804347802528
Parted for Android. You can probably find it other places, but I found this file:https://dl.dropboxusercontent.com/u/84115590/LG%20G2%2016GB%20Solution/sdparted-recovery-all-files.zip
EDIT: There seems to be a lot of confusion here. My bad. All you need is the file named "parted" from this zip file - nothing else. Just put that one file in the root of your external SD card.
https://dl.dropboxusercontent.com/u/84115590/LG G2 16GB Solution/sdparted-recovery-all-files.zip linked from here: http://www.**********.com/your-32gb-lg-g2-shows-only-16gb-storage-space-heres-the-fix/
EDIT2: The dropbox link is down. I've attached the file directly.
The Candy5 ROM (This will potentially save you some manual steps. Somewhat optional, but highly recommended):
http://forum.xda-developers.com/g-pad-10/development/rom-candy5-g-pad-v410-lollipop-5-1-1-v2-t3111987
Flashify APK:
http://www.apkmirror.com/apk/christian-gollner/flashify/flashify-1-9-1-android-apk-download/
TWRP for the v410:
http://forum.xda-developers.com/g-pad-10/development/recovery-twrp2-8-5-0lgv400-410-t3049568
LG One Click Root:
http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
(You may use Purple Drake or whatever else you want. They all use the same root script as this does and the GUI is helpful for novices.)
Android SDK (specifically adb.exe. After installing go to SDK Manager and ensure that Android SDK Platform Tools is checked):
http://developer.android.com/sdk/index.html
For clarification below, when I have commands in "quotes" they are Windows commands. When they are in `backticks` they are commands that you run inside of ADB which actually run on your device....as root. Root can screw things up. Please be extra cautious. If you blame me for messing up your device I will laugh at you. But that's not gonna happen, right? Good. Let's go.
Now that you have everything, put it all into a folder where you can access it easily.
Install the LG Drivers.
Install Android SDK (or otherwise get adb.exe).
Extract all of the archives.
Move the KDZ to the LG Flash Tool 2014 folder.
Put the tablet into Download Mode by powering it off, holding VolUp, and plugging in the USB cable. Press VolUP when instructed. You must be in Download mode before continuing.
Run LGFlashTool2014.exe. Select the KDZ file. Click "CSE Flash". Click "Start". Select "English" and click OK. Do not change anything else.
WAIT for the flash to continue. If you really want to brick your device, here's a good opportunity.
The device will reboot into Android 4.4.2. You will only have 4GB of internal storage at this point. DON'T PANIC! We are fixing it.
Enable USB debugging.
Connect the device.
Install and run LG One Click Root. Wait for the device to be rooted before proceeding.
Copy the Flashify apk, TWRP image, and Candy5 ROM to your external SD card.
Install Flashify and flash TWRP to the recovery partition.
Use the Flashify menu to reboot in to recovery.
DON'T PANIC! You will get white vertical lines on the boot screen from now on. They only show up during boot animations. A small price to pay. This may be fixed at a later date. for the time being! Thanks to marcsoup's first post ever, we have a fix! Details below. PLEASE click this link and thank him!
Things get tricky here. Copy parted to your external SD card and then run "adb shell" from Windows to get a shell in TWRP.
In TWRP, unmount /data by tapping Mount > uncheck Data.
`cp /sdcard/parted /sbin/` This copies the parted binary to /sbin so it can be executed in the path. I had trouble running `/sdcard/parted`, but YMMV.
`chmod +x /sbin/parted` Make it executable.
`parted /dev/block/mmcblk0` Run parted against the internal mmc
`p` Prints the partition table.
`rm 34` Deletes partition 34 labeled "grow". This is the root of our problem. The KDZ apparently only creates a 4GB partition, I assume so the test build has maximum compatibility with all sized devices.
`rm 33` Deletes partition 33 "userdata"
`p` Print to verify
`mkpartfs` Create a partition and put a filesystem on it. If we only expand the partition it won't help us because the filesystem is still only 4 GB.
a) name: userdata
b) type: ext2 (the tool only supports ext2. This is ok for now.)
c) start: 3439MB (the end of part 32. IT MAY BE DIFFERENT FOR YOU!) Be sure you do not omit the MB part otherwise the offset will overwrite another critical partition.
d) end: 15.8GB (where "grow" ended above. IT MAY BE DIFFERENT FOR YOU!) Be sure you do not omit the GB part otherwise the offset will overwrite another critical partition.
`p` Verify. For me it did not name the partition properly. Gotta fix that.
(if necessary) `name 33 userdata` This is critical for mount to find it in /dev/block/platform/msm.sdcc.1/by-name/ on some/all ROMS.
`p`. Verify one last time. Compare it to my partition table in the attachments. If you want to brick, delete some random partitions here.
Flash Candy5 with TWRP. It's only 239 MB, so it will flash quickly. I do this because Candy5 will reformat mmcblk0p33 from ext2 to ext4 for you. It does this as part of it's system boot, apparently. If you install a different ROM that does not do this, you can reformat it by running `make_ext4fs /dev/block/mmcblk0p33`. If your ROM does not have make_ext4, it likely has some differnt method to make an EXT4 filesystem. `/system/bin/mke2fs -t ext4 /dev/block/mmcblk0p33` may work better. Just flash Candy5 and be done with it.
Tap Wipe > Swipe to Factory Reset.
Tap Reboot > System.
WAIT!!! It will take a minute for the ROM to start the first time. You will have white lines and and possibly a white screen. WAIT. It's moving the DEX files to cache, formatting a partition, creating default folders on the internal storage, and several other things. WAIT! When the screen goes dim or turns off then it's ready.
Cycle the display or turn it on. You should be at the Candy5 lock screen.
USB debugging is on by default. Run "adb shell".
`mount | grep userdata` Make sure mmcblk0p33 is mounted.
`df` Make sure /data is 11.3 GB (or whatever size it is on non-16GB devices).
HELL YEAH, you downgraded, rooted, and fixed the partition problem. Enjoy your tablet!
Thanks to dopekid313 for finding the KDZ.
Thanks to timmytim for Candy5.
Thanks to the creators of the root script, flashify, TWRP, and XDA for being so awesome.
Thanks to marcsoup for fixing a fix to the white lines.
Thanks to navin56 for the partition dumps. PLEASE thank his post!
White lines fix.
What we are going to do is flash the aboot partition with the stock image provided by navin56. I've removed the extra files from the dump, so simply download aboot.img.7z below. Unzip it using 7zip.
These commands are to be run in TWRP. Reboot to TWRP recovery and connect with "adb shell". All of the following commands will be run in ADB under TWRP. If you cannot figure out how to get here, please post in the thread and someone will help you. Onward:
If you do everything correctly then you don't have to reflash your ROM and you won't lose data. This process can be done any time after flashing the KDZ, even before you follow the steps above to resize the userdata partition. It's a completely separate process.
Unzip aboot.img.7z so you have the file named aboot.img. You should also make sure that aboot.img's MD5 sum is e97431a14d1cee3e9edba513be8e2b52. Do not flash the 7z file. Please.
Copy aboot.img to your external SD card. It should live at /sdcard/aboot.img
Boot to TWRP and run "adb shell"
`ls -al /dev/block/platform/msm_sdcc.1/by-name/` Let's make sure we are flashing the right partition. On my device "aboot" is /dev/block/mmcblk0p6. You should verify this on your device or you WILL brick your tablet.
`dd if=/dev/block/mmcblk0p6 of=/sdcard/aboot-fukt.img` Let's back up our current aboot partition before we go flashing things just in case there are unintended consequences later. Be sure you have the same partition that "aboot" referred to in the 4th step or you have just backed up the wrong partition.
`dd if=/sdcard/aboot.img of=/dev/block/mmcblk0p6` Be sure the file exists, is the correct aboot.img, and you are flashing the right partition. You have been warned!!
Reboot TWRP and enjoy your boot animations again.
If I missed anything, please let me know. As far as I know this is the very first tutorial that details what is necessary to accomplish this. Please hit the Thanks button on every thread that you visit to download files!
FAQ:
Q: Why do I only have 11.3 GB of space when my device is 16GB?
A: The entire internal SD card (eMMC) is 16 GB. Gotta have someplace to install the bootloader, recovery, android, the modem OS, the secondary bootloader, the cache, the resource and power manager, and all of the other partitions necessary for the table to operate. Please look at the second screenshot in the OP. All of those 33 partitions take up room on the internal card. Fortunately ALL of those partitions ONLY take up about 4.4 GB. Hence the 'userdata' partition is ~11.3 GB.

If anyone wants to use my work to create a flashable zip to make it easier for novices, please do so. My problem is solved and I don't have the time to create the zip. Please post any questions and I'll gladly answer them! I'm so stoked that we have a usable downgrade method now!

Thank You, Worked Great

Thanks for making this I was gonna do it but was to lazy lol and thanks for linking my thread and giving cred instead of just linking straight to the kdz thank you

grandamle91 said:
Thank You, Worked Great
Click to expand...
Click to collapse
Glad to be of help!
dopekid313 said:
Thanks for making this I was gonna do it but was to lazy lol and thanks for linking my thread and giving cred instead of just linking straight to the kdz thank you
Click to expand...
Click to collapse
Of course! If you hadn't obtained the firmware then we'd all still be looking for a solution. It pisses me off to no end when people try to take credit for other people's work. We all just need to realize and acknowledge that we are simply standing on the shoulders of those who did the work necessary for each of us to do our work.

I just noticed since we formatted the userdata it screws up TWRP. It won't mount Data and it says the settings are corrupted

grandamle91 said:
I just noticed since we formatted the userdata it screws up TWRP. It won't mount Data and it says the settings are corrupted
Click to expand...
Click to collapse
Is this after you've rebooted into Candy5 and the partition is reformatted as ext4 (or you've done so manually)? TWRP may not be able to mount an ext2 partition.
EDIT: I just tested this. Following my instructions and flashing to Candy5, TWRP sees mmcblk0p33 (userdata) as the full size and mounts it at /emmc.
For clarification, after you run the parted commands, it will mess with the partition table and TWRP will most likely not be able to see it to remount it - at least not until after a reboot. This is why you need an external SD card from which to install ROMs.

/data not mounted
Edit: nevermind. The partition 33 was still ext2. I had to run make_ext4fs /dev/block/mmcblk0p33 and now I am able to mount /data. Thanks.
Thanks for taking the time to help us.
I followed the steps and till 33 I am good. But once I am in Candy5, I am not able to adb shell (adb not recognizing device eventhough usb debugging is on). I rebooted to recovery and adb works there. But my /data partition is not enabled in TWRP. I am not able to check it either under Mount in TWRP.
Code:
mount | grep userdata
is empty
Code:
df
does not show data

I tried this and my tablet bootlooped. I was able to get into fastboot and restore. I would GREATLY appreciate it if someone who has the time, would kindly donate their valuable time to into making an exe zip or something.

gridironbear said:
I tried this and my tablet bootlooped. I was able to get into fastboot and restore. I would GREATLY appreciate it if someone who has the time, would kindly donate their valuable time to into making an exe zip or something.
Click to expand...
Click to collapse
At what point did it bootloop? What was the last step that you took before rebooting?

Zip
I would really appreciate a zip file as I have never been savvy with adb and for whatever reason it doesn't want to work on Windows 10.

drumm3rb0y said:
I would really appreciate a zip file as I have never been savvy with adb and for whatever reason it doesn't want to work on Windows 10.
Click to expand...
Click to collapse
A zip file for what part? The only part that requires ADB directly is to fix the internal storage. You absolutely have to flash the KDZ and then root before you can do anything. If you are on 5.x then you have no possible way to root, much less flash a zip file.
If you tell me what exactly you are having issues with I will try to help.

fatbas202 said:
A zip file for what part? The only part that requires ADB directly is to fix the internal storage. You absolutely have to flash the KDZ and then root before you can do anything. If you are on 5.x then you have no possible way to root, much less flash a zip file.
If you tell me what exactly you are having issues with I will try to help.
Click to expand...
Click to collapse
The adb part is the part im having issue with. Everything else is flashed already. I was wondering if you could make a zip for the adb part so I can just flash it through twrp.

thanks for the great help. it did work perfectly to regain the lost space.
what about white lines ? is there any solution for that problem ?
I have tried flashing back stock recovery extracted from kdz, dd' but didn't help.
Now i am thinking of flashing back the aboot.bin extracted from original kdz or i can dump ".img" from another working device. (i have 4 similar devices)
what is your opinion i m not a developer and i need your advise. should i go ahead and which partition should i dd ? aboot or abootb or boot ?
regards

shahidmianoor said:
thanks for the great help. it did work perfectly to regain the lost space.
what about white lines ? is there any solution for that problem ?
I have tried flashing back stock recovery extracted from kdz, dd' but didn't help.
Now i am thinking of flashing back the aboot.bin extracted from original kdz or i can dump ".img" from another working device. (i have 4 similar devices)
what is your opinion i m not a developer and i need your advise. should i go ahead and which partition should i dd ? aboot or abootb or boot ?
regards
Click to expand...
Click to collapse
I have no solid evidence of this, but I suspect that the white lines are caused by a display driver issue where when the bootloader hands over control of the display to the kernel it doesn't get reinitialized properly. I have no ideas as to how to get rid of that at the moment but if I stumble across something I'll be sure to post here.
While I'm not an Android developer, I've been a Linux admin for 10+ years and have a lot of experience with Android devices. I'd be really hesitant to go flashing things ad hoc. While Download Mode may save you if you flash the wrong thing, I'm not entirely sure what the limitations that you may run in to with a locked bootloader are.
After having this device for months on 5.x and FINALLY being able to downgrade and run custom ROMs with root, not seeing a boot animation is a pittance to pay. But I'll keep looking.

i have same problem entered in TWRP but when ADB sheel thorough DP tools it didn't connect to my device. i m also using windows 10

Do I need to Re-mount Data ? I press format data button at TWRP and mount data. It looks work great.
After all process, it shows 16Gb total at storage, 11.04GB available. it works perfectly.
I need the stock V41010d, so I reflash the stock rom rooted at [ROM][STOCK](V410 ONLY)KOT49I.V4101d | 4.4.2 | Rooted + Busybox
Now, my Gpad is at stock V41010d, but I have a question about the boot screen, is it still with white lines and white screen? Any method to fix it?

Hello,
Thanks for the great work. unfortunately I am facing some difficulty, starting from step# 16 "Things get tricky here", how to run"adb shell in TWRP?
also can I use minimal_adb_fastboot_v1.1.3_setup.exe as mentioned in the link in the OP http://www.droidviews.com/your-32gb-lg-g2-shows-only-16gb-storage-space-heres-the-fix/ ?
also I noticed the path have been used includes 'parted' folder, but the folder I have after unzipping the parted zip called 'sdparted-recovery-all-files', do I rename the folder to 'parted' instead?
please help and excuse my broken English.

I'm also having trouble with the adb shell step. When my device is powered on normally, adb commands work. However, in TWRP mode my computer can't recognize the tablet, mount properly, and copy over parted. All the steps have been identical to this point. Any ideas?

iphone5sf said:
Do I need to Re-mount Data ? I press format data button at TWRP and mount data. It looks work great.
After all process, it shows 16Gb total at storage, 11.04GB available. it works perfectly.
I need the stock V41010d, so I reflash the stock rom rooted at [ROM][STOCK](V410 ONLY)KOT49I.V4101d | 4.4.2 | Rooted + Busybox
Now, my Gpad is at stock V41010d, but I have a question about the boot screen, is it still with white lines and white screen? Any method to fix it?
Click to expand...
Click to collapse
You shouldn't need to remount or format data. The parted command nukes the filesystem and creates a new one formatted as ext2. At this point the running kernel has the old partition table loaded and won't know that the partition has been extended. Simply flash Candy5 and reboot at this point and it will reformat the userdata partition.
See above for the white lines during the boot animation. Known issue, no fix in sight, doesn't really matter.
nmnm4alll said:
Hello,
Thanks for the great work. unfortunately I am facing some difficulty, starting from step# 16 "Things get tricky here", how to run"adb shell in TWRP?
also can I use minimal_adb_fastboot_v1.1.3_setup.exe as mentioned in the link in the OP http://www.droidviews.com/your-32gb-lg-g2-shows-only-16gb-storage-space-heres-the-fix/ ?
also I noticed the path have been used includes 'parted' folder, but the folder I have after unzipping the parted zip called 'sdparted-recovery-all-files', do I rename the folder to 'parted' instead?
please help and excuse my broken English.
Click to expand...
Click to collapse
You only need the sdparted-recover-all-files.zip from that site. "parted" is not a folder, but the binary (without a file extension) inside of that zip file. Copy that file to /sbin and you are in business.
zmali1 said:
i have same problem entered in TWRP but when ADB sheel thorough DP tools it didn't connect to my device. i m also using windows 10
Click to expand...
Click to collapse
summonholmes said:
I'm also having trouble with the adb shell step. When my device is powered on normally, adb commands work. However, in TWRP mode my computer can't recognize the tablet, mount properly, and copy over parted. All the steps have been identical to this point. Any ideas?
Click to expand...
Click to collapse
I'd recommend installing the SDK and pulling the drivers from that. Alternatively, you can try the drivers here: https://github.com/koush/UniversalAdbDriver.
Technically, when I ran the "parted" commands I was actually booted in to rooted 4.4.2 from the KDZ; I wasn't actually in TWRP. It's just not a very recommended way of going about it. I explained how to run all of this from TWRP, but there's no technical reason that you *can't* run this from Android. You just *shouldn't* because you can't cleanly unmount the filesystem and it theoretically could cause filesystem corruption. I just figured that I don't care about that partition getting corrupted since it's getting wiped out.

ME176C/CX detailed guide on dual-booting linux

Greetings,
i did go through dual-booting linux on our device kind of process and spend a bit of time, trying to figure out the correct steps.
Was not easy, for a newbie like me, i dont know much about linux itself, most of the inscrutions are written in "foreing language" for me, so here is more of a detailed guide.
This guide is only for installation on the SDCARD, i did not try out internal storage
!!! Im not responsible for anything that happens during/using these steps, you and only you are responsible to what happens, use with caution !!!
Requirements:
Unlocked bootloader: https://forum.xda-developers.com/t/...6c-boot-for-asus-memo-pad-7-me176c-x.3780225/
Installed TWRP: https://forum.xda-developers.com/t/...p-3-3-1-for-asus-memo-pad-7-me176c-x.3745190/
Both of these guides are made step by step, so there should be no questions about this
First of all, go to https://images.postmarketos.org/bpo/v22.12/asus-me176c/ , there are 3 different types of UI, the kernel itself should be the same, but i dont know for sure myself
Phosh - very well working on our device, missing a bit of RAM to launch firefox stable for example
Plasma-mobile - i found this one was very hardware heavy, it takes quite alot of more storage aswell, i do not recommend this for our device
Sxmo - this one did boot up just fine, but i wasnt able to get more testing as my hardware inputs were not recognized by the software, i do not recommend this one
There are multiple software version, i did try only the latest one
Possible to try out the lower (outdated) versions yourself
After downloading these files, you should have 2 of the .xz archives, unpack them somewhere, i did put them into the same folder, but thats just my own preference
After unpacking them, you should have
XXX-asus-me176c-bootpart.img
XXX-asus-me176c.img
XXX are reference to date of the build
To have ourself things easier, we will rename both of these build and leave only the "asus-me176c.img/asus-me176c-bootpart.img", you can leave them named as theyre, but it will take you a bit more time in the terminal
After that, we will move one of our images (the non-bootpart one) to the internal storage of the device.
Make sure, to have enough space available. I have the 8GB version and it was kind of struggle for me to install the plasma-mobile version.
I did also try moving that file to USB-OTG and SDCARD, but i had some problems with USB-OTG in TWRP and SDCARD gets wiped when you install the OS.
So, please, use internal storage for the file, the OS IS NOT GOING TO GET INSTALLED ON YOUR INTERNAL STORAGE IN THIS WAY, WE ARE GOING TO INSTALL IT ON A SDCARD.
After moving our file to the internal memory, we will go and reboot our tablet to fastboot mode
when powered off, press volume down + power on, release power when screen lights up
in the custom bootloader menu, using volume keys (power one does not work), we select Fastboot (power down to move and power up to select)
Our phone should boot into fastboot mode, we go and connect our phone to the computer
after connecting the phone, we go to the folder where our xxx asus-bootpart.img is located, go ahead and SHIFT+RIGHTCLICK on empy space in the folder, select Open a terminal/powershell window here
in the terminal/powershell we type in command " fastboot flash APD asus-me176c.img "
let the command process, after its done, go and type in " fastboot reboot-bootloader "
our phone gets rebooted into the bootloader, with volume keys once again, select RECOVERY
when our device gets booted to TWRP, go to Mount -> Tick ESP
anywhere on your PC, open up the default text editor, paste in:
title postmarketOS
volume 80868086-8086-8086-8086-000000000007
linux /vmlinuz-edge
initrd /intel-ucode.img
initrd /initramfs
# Comment this out to get more output on screen while booting
options console=null
this text is only used for the latest version of the OS, for lower versions, please follow https://wiki.postmarketos.org/wiki/ASUS_MeMO_Pad_7_(asus-me176c)
select the file type as "every files" instead of text document
name it pmos.conf and save it anywhere you like
at your computer, download MiniDiskPartition tool, or other partition tool
partition your sdcard using the selected tool
i have 32GB sdcard, i did partition my sdcard roughly 8GB with FAT32 for file sharing between android/linux/windows and the rest with EXT4 for the Linux itself
i believe the partition size for Linux doesnt matter aslong as its over 4GB, the installation itself should resize the partition on sdcard itself, depending on how it needs, BUT im still not 100% how this works
connect your phone to the computer
in TWRP go to MOUNT and tick ESP
in the folder where you saved the pmos.conf, open up a terminal (once again SHIFT+RIGHTLICK and open terminal/powershell here)
type in " adb push pmos.conf /esp/loader/entries/ " , press enter
in TWRP go to Advanced and go to Terminal
type in " df "
then you should see your partitions, we are looking for one that belongs to /external_sd/ , usually dev/block/mmcblkX0Y (X and Y are not specified), it should have it written at the end
mine was " /dev/block/mmcblk0p1 " YOURS CAN BE DIFFERENT! in the original guide, they specify, it can be also SDXY (XY belongs to any number)
after we find our partition that belongs to /external_sd/ , we go into the terminal in TWRP and type in:
dd if=/PATHTOYOURIMGFILE/ of=/PATHTOYOUREXTERNALSDCARDPARTITION/ bs=4m
i did have the IMG file in my internal storage, therefore my command was:
dd if=/sdcard/asus-me176c.img of=/dev/block/mmcblk0p1 bs=4m
make sure to use the bs=4m instead of bs=4M (as specified in the original guide), otherwise you will get "illegal number" error
after this, you should wait! The file is 1,6 - 2,4 GB, it takes time
your result should appear in the terminal
if your installation was succesfull, you can go in TWRP to REBOOT and select BOOTLOADER
you should have postmarketOS option available in the bootloader boot options, select it
you should boot your postmarketOS now
if you didnt, you probably didnt follow the guide correctly, read the steps once again
if you couldnt install the postmarketOS and youre sure you did follow the steps correctly, contact me on XDA (preferably make a comment under this thread)
Original thread:
ASUS MeMO Pad 7 (asus-me176c) - postmarketOS
wiki.postmarketos.org