Develop Bugs

[Recovery] ClockworkMod 3.2.0.0 (R4c) Modded for Internal media [UPDATED 10/6]

{
"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"
}
ClockworkMod Recovery - Modified for Motorola Xoom​
OK, so this recovery will skip /data/media (Internal storage) when performing nandroid backups and also when you perform a factory reset.
This means that we can now perform nandroid backups without backing up our internal media and removing it everytime you want to do a backup.
Thanks to Bigrushdog and MadIndustries for helping out with the concept of the solution for skipping /data/media.
Also thanks to Koush and all the other developers that have contributed to clockworkmod, without you guys the android world would be completely different.
Thanks also to everyone in #xoom that tested this.
The source code for all changes etc are available through the github repository. The two other projects that have been modified to make this recovery possible can also be viewed through my github account.
Even though this recovery has been tested, I am not liable for any loss of data or any damages done by this recovery.
==============================================
General Notes
When I refer to /data/media, this is the same as /sdcard when the xoom is booted into honeycomb. So any data that is stored in here should be untouched by this recovery.
If you encounter a problem with the filesystem on /data like it has become corrupt, place a blank file called "eraseData" (without the quotes) in the clockworkmod folder on your external sdcard. This will revert to the old way of formatting /data. NOTE: by doing this you will lose everything that you have in /data/media.
Versioning of recovery images:
At the moment I don't have a version number as such, instead each recovery image is timestamped in the format of DDMMYY-HHYY. So the file recovery-solarnz-120511-2030.img was produced on 12 May 2011 at 8:30 PM. This versioning is also shown in recovery when it starts.
==============================================
Downloads
SLOW DOWN AND RELAX
Make sure you download the correct version depending on how you want to flash. I have seen at least two xooms bricked now because they have tried to flash the zip file through fastboot.
Recovery Zip (solarnz-R4c-100611-1150) FLASHED THROUGH CWM
MD5: 1ad409db4030635734b27df02b7e7c1a
Recovery Image (solarnz-R4c-100611-1150) FLASHED THROUGH FASTBOOT
MD5: 20575d4b62bf697f77abca9093877ea3
==============================================
Installation Instructions
Method 1 Flashing through CWM
Download the recovery zip file
Place the recovery zip on the sdcard where clockworkmod can read it.
Reboot into recovery using "adb reboot recovery" or any other method
In recovery, select flash zip from sdcard and select the recovery zip you downloaded
Sit back and relax while recovery flashes the new recovery and reboots into it.
Click to expand...
Click to collapse
Method 2 Without CWM
Download the recovery image (not the zip file)
Pull up your command prompt, then
Code:
adb reboot bootloader
fastboot flash recovery recovery-solarnz-XXXXXX-XXXX.img
fastboot reboot
Let your Xoom boot up. Then to check out your shiny new recovery,
Code:
adb reboot recovery
Click to expand...
Click to collapse
Also, you can grab Rom Manager or QuickBoot from the market for easy access to recovery.
==============================================
Changelog
Code:
[url=http://bit.ly/k7cZxJ]3.2.0.0 (R4c-100611-1150)[/url]
- Rebuilt recovery, the previous recovery was built off of bad device files.
[url=http://dl.dropbox.com/u/13093938/XDA/Recovery/recovery-solarnz-R4b-060611-1300-cwm.zip]3.2.0.0 (R4b-060611-1300)[/URL]
- Disabled partitioning the sdcard as per request.
[url=http://dl.dropbox.com/u/13093938/XDA/Recovery/recovery-solarnz-R4-050611-1515-cwm.zip]3.2.0.0 (R4-050611-1515)[/URL]
- Included changes from koush's sources upto clockworkmod 3.2.0.0
- Implemented Advanced backup. This allows you to choose what partitions you want to backup.
[url=http://dl.dropbox.com/u/13093938/recovery-solarnz-120511-2030.zip]3.0.2.8 (120511-2030)[/url]
- Fixed mounting the sdcard for some users
[url=http://dl.dropbox.com/u/13093938/recovery-solarnz-080511-1630.img] 3.0.2.8 (080511-1630)[/URL]:
- Modified to skip /data/media or /sdcard in nandroid backups.
- Modified formatting /data to remove directories and folders so we can keep media.
- Place a file called eraseData in the clockworkmod directory on your EXTERNAL sdcard to revert to the normal restoration method.

Great job guys!!!!
Sent from my HTC HD2 using XDA Premium App

You da man solarnz! Also, you can grab step 1 from my 3.1 thread. That zip will flash recovery from recovery! Mods, please unsticky my Recovery thread and lock and replace with this one. This is recovery we will support going forward.

Win
Sent From My Evo

Great job folks!!!
We've gotten used to BRD's awesome formatting of his posts and super clear instructions, would be real nice if we can get this on the new sticky

bigrushdog said:
You da man solarnz! Also, you can grab step 1 from my 3.1 thread. That zip will flash recovery from recovery! Mods, please unsticky my Recovery thread and lock and replace with this one. This is recovery we will support going forward.
Click to expand...
Click to collapse
might be a stupid question but just to clarify: we would obviously not want to flash any recoveries in rom manager thus not having any need for rom manager at at this point correct?

jland22 said:
might be a stupid question but just to clarify: we would obviously not want to flash any recoveries in rom manager thus not having any need for rom manager at at this point correct?
Click to expand...
Click to collapse
Rom manager is still nice as you can quickly reboot to recovery etc from it. It also allows you to select the operation to do in recovery and then restart it will automatically restart and perform the action.
If you flash recovery from Rom Manager, you will end up with the official 3.0.2.5 recovery from Koush that doesn't contain the method of skipping /data/media

bigrushdog said:
You da man solarnz! Also, you can grab step 1 from my 3.1 thread. That zip will flash recovery from recovery! Mods, please unsticky my Recovery thread and lock and replace with this one. This is recovery we will support going forward.
Click to expand...
Click to collapse
What's the difference between this and the one on bigrushdog thread. (3.1)
Sent from my Xoom using XDA Premium App

lokko21 said:
What's the difference between this and the one on bigrushdog thread. (3.1)
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
No difference, BRD used this modified 3.2.8 in his first step on that thread. But this will be the go-forward recovery from now on.

What folder do i need to flash this too?

b0ricua said:
No difference, BRD used this modified 3.2.8 in his first step on that thread. But this will be the go-forward recovery from now on.
Click to expand...
Click to collapse
Gotcha so I'm cool, thanks.

ok just flashed, looks good

Solarnz, thanks for formatting the OP and adding clear instructions!!
You da man!

very cool, but would it be complicated to just make an "exclude" menu before backing up? That way people can just exclude whatever they want ...

thanks to everyone who contributed. We dont always think about how great CWM is and all the wonderful things it does for us until we dont have it anymore I didnt like the feeling of walking around with that stock recovery

running into a problem. I have a wifi only xoom. I had the old 3.0.2.8 recovery installed which i still had after 3.1 update no problems with it at all. I just flashed the 3.0.2.8 one using fastboot but now when i reboot into recovery. All i see is the android with the exclamation mark i do not see clockwork. I have reflash more then once with no luck still.
Edit: wanted to add that if i flash the clockwork from Rom manger which i see is the version 3.0.2.5 i am able to do a adb reboot recovery into recovery with no problems.
Edit2: for some reason the zip flashing in the old recovery works fine and updated to the new recovery. no clue why fastboot is not working. I tried fastboot 5 times every flash said it finished fine but it boots with a android and a exclamation mark. only the zip flashing in recovery works for me.

maybe this is a stupid question, but i dont even see a "media" folder on my xoom. there are folders for music and video. i have my own folder for movies, one for comics, ect. do i have to create a media directory and move everything into it in order to make sure that it doesnt get included? and if so, where does it go?

Prod1702 said:
running into a problem. I have a wifi only xoom. I had the old 3.0.2.8 recovery installed which i still had after 3.1 update no problems with it at all. I just flashed the 3.0.2.8 one using fastboot but now when i reboot into recovery. All i see is the android with the exclamation mark i do not see clockwork. I have reflash more then once with no luck still.
Edit: wanted to add that if i flash the clockwork from Rom manger which i see is the version 3.0.2.5 i am able to do a adb reboot recovery into recovery with no problems.
Edit2: for some reason the zip flashing in the old recovery works fine and updated to the new recovery. no clue why fastboot is not working. I tried fastboot 5 times every flash said it finished fine but it boots with a android and a exclamation mark. only the zip flashing in recovery works for me.
Click to expand...
Click to collapse
Ok, I'm assuming you are on android 3.1 without a modified kernel.
The issue you are having is that with the default boot image, it flashes back the stock recovery every single time you reboot.
Code:
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
(Thanks Berzerker7)
ltracte said:
maybe this is a stupid question, but i dont even see a "media" folder on my xoom. there are folders for music and video. i have my own folder for movies, one for comics, ect. do i have to create a media directory and move everything into it in order to make sure that it doesnt get included? and if so, where does it go?
Click to expand...
Click to collapse
Ok. on our xooms, /sdcard is actually a symlink (think of a shortcut) to /data/media.
So when I say /data/media, you can think of /sdcard (the internal storage).

random one again - will this be available via ROM Manager? it's still 3.0.2.5 there
thanks!

E: can't mount /sdcard/update.zip
or error mounting /sdcard
anyone has encountered this problem plz?
thks

Stuck on ANDROID logo boot anim after HBOOT flash

hey y'all
Was following this thread: on Alternative HBOOTs
tried the following:
I followed instructions on Apharev homepage and flashed the 'bravo_alphaspl-sense.img'
Downloaded the necessary PB99IMG zipfile and saved it to SD card
now phone goes silver ANDROID logo that reflects passing light after splash image - looks like this (only in silver):
{
"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"
}
but won't load my homepage afterwards
HELP

What Rom are you using? perhaps there is not enough space on /system for the Rom now with your new hboot. Try flashing the stock hboot.
Sent from my HTC Desire using XDA App

Not to state the obvious but did you
1. Reinstall rom after changing hboot - necessary i believe
2. Install correct rom for hboot
If this fails you could re-flash to your previous hboot and reinstall whatever flavour of rom you were using
hope this helps
Jamadant

Yeah I'm pretty sure all that's happened is you installed a HBOOT that has different partitions for System, Data and Cache. Therefore you just need to reinstall the ROM. Simply boot into recovery (Turn the phone off, hold volume down and press power, use the volume keys to navigate to RECOVERY and press the power button) From there you need to go into "mounts and storage", wipe everything APART FROM YOUR SDCARD and then install a new ROM.
Hope that helps

Thanks all but the problem is that I longer have the Reflex S ROM on my phone (I removed it due to space).
I tried pushing it to phone via adb but not enough space
I tried to pull the nandroid backup from phone via adb (to free up space for pushing ROM to phone) but no luck
This is the command I used:
adb pull /clockworkmod/backup/2011-07-19.10.12.47/ C:\
but this gives me an error that /clockworkmod/backup/2011-07-19.10.12.47/ does not exist
???
Anyone know of an easier way
I have attached the adb logcat as well

herb1 said:
Thanks all but the problem is that I longer have the Reflex S ROM on my phone (I removed it due to space).
I tried pushing it to phone via adb but not enough space
I tried to pull the nandroid backup from phone via adb (to free up space for pushing ROM to phone) but no luck
This is the command I used:
adb pull /clockworkmod/backup/2011-07-19.10.12.47/ C:\
but this gives me an error that /clockworkmod/backup/2011-07-19.10.12.47/ does not exist
???
Anyone know of an easier way
I have attached the adb logcat as well
Click to expand...
Click to collapse
You can't restore nandroid after you've changed hboot. Hboot partition sizes have changed and chances are that you do not have enough space on them to restore the information on the original partitions.

paul.c said:
You can't restore nandroid after you've changed hboot. Hboot partition sizes have changed and chances are that you do not have enough space on them to restore the information on the original partitions.
Click to expand...
Click to collapse
I'm aware of that but I want to pull the nandroid backup to make space to push the ROM to phone via adb
what commands can I use

Why you want adb to copy clockworkmod backup.... just open your SD card from window explorer and .. copy paste on your C drive and delete from your SD card

managed to access SD card from Recovery by mounting as USB
cut & pasted the nandroid backup to my laptop,
copied the Reflex ROM over to SD & installed
but now stuck on splash screen

herb1 said:
managed to access SD card from Recovery by mounting as USB
cut & pasted the nandroid backup to my laptop,
copied the Reflex ROM over to SD & installed
but now stuck on splash screen
Click to expand...
Click to collapse
Configured sd card for reflex rom correctly? You need stock hboot or cm7 hboot to run reflex s (remember to downloaded corresponding version).

I've formatted my sd card, made it a gold card
trying to install Reflex S 2.1.2 ROM as per NeoPhyte's instructions (with Radio)
Do I flash the stock HBOOT after ROM install?
I'm quickly running outta ideas...me thinks I might have to go back to unrooted stock ROM
this will teach me not to fcuk around with my phone AGAIN

herb1 said:
I've formatted my sd card, made it a gold card
trying to install Reflex S 2.1.2 ROM as per NeoPhyte's instructions (with Radio)
Do I flash the stock HBOOT after ROM install?
I'm quickly running outta ideas...me thinks I might have to go back to unrooted stock ROM
this will teach me not to fcuk around with my phone AGAIN
Click to expand...
Click to collapse
Do I flash the stock HBOOT after ROM install?
Not if you have changed your hboot from stock!?!!!! Have you changed your partition tables yet? If you have flash cm 7

herb1 said:
I've formatted my sd card, made it a gold card
trying to install Reflex S 2.1.2 ROM as per NeoPhyte's instructions (with Radio)
Do I flash the stock HBOOT after ROM install?
I'm quickly running outta ideas...me thinks I might have to go back to unrooted stock ROM
this will teach me not to fcuk around with my phone AGAIN
Click to expand...
Click to collapse
One has to flash hboots always BEFORE installing a rom.

Can you not use fastboot its much more reliable!?

Nice guide how to use adb/fastboot:
http://androidforums.com/desire-all...stboot-windows-published-17th-may-2011-a.html

thanks for all the advice
I've been unable to use my phone for the past few days and I'm considering the following options (getting REAL desperate here):
* should I flash the stock ROM? (I've been on the Net, looking for similar situations and 90% of peeps recommend flash the stock ROM)
* flash the HBOOT for Reflex S, then install Reflex S ROM (as per recommendations above)?
The thing is (with option 2); I can't get into adb shell as phone does not detect in Recovery or at splash screen (where I'm at at the moment)...
I've even tried Android Flasher but it does work either!!!
MatDroiD...I know (with your skill & experience) that you can help...please, I need my phone back!!!

You don't have to go into adb shell to flash a new hboot, you can do it in fastboot mode, but you have to have s-off!!! (I assume you have, as you stated before that you followed the instruction on alpharev). To use fastboot you have to have the fastboot.exe (you'll find a download linke if you do a quick search). And then you can flash the correct hboot by following the instruction on alpharev
"1) Nandroid backup in recovery.
2) Verify the MD5SUM of the file you downloaded against the one in the table.
3) Flash HBOOT with your phone in fastboot mode (Back+POWER) -> 'fastboot flash hboot bravo_alphaspl.img' (change into the correct filename for the HBOOT you downloaded)
4) 'fastboot reboot-bootloader'
5) 'fastboot erase cache'
6) Boot recovery, wipe everything and restore."
Hope this helps...

I tried the following:
followed EddyOS guide to install RUU as PB99IMG.zip (as per FAQ)
got this message (which is different from EddyOS post)
SD Checking
Loading...[PB99DIAG.zip]
No image!
Loading...[PB99DIAG.nbh]
No image or wrong image!
Loading [PB99IMG.zip]
everything else goes fine, then get this displayed (after pressing YES to update device)
Update in progress...
Do not power off your device
can not roll back hboot version
[1] Bootloader - Bypassed
[2] Radio V2 - OK
[3] Radio Cust - OK
[4] Boot - OK
[5] Recovery - OK
[6] System - Failed-PU
[7] Userdata - OK
[8] Splash1 - OK
Partition update fail!
Update fail!
I chose not to reboot the device & booted into Recovery
Got a black screen with htc phone overlapped with red triangle & exclamation mark
Press volume UP & POWER and ended up in Android system recovery <3e> with limited recovery options (reboot system/apply sdcard:update.zip/wipe data/wipe cache)
Message displayed at bottom
'E:Can' open /cache/recovery/command'
Chose to reboot phone and observed that white HTC splash loaded with silver ANDROID flashing boot animation afterwards
Phone eventually loaded to what looks like Oxygen lockscreen
Unlocked screen and phone went into setup (keyboard, wifi, sync, etc)
At last SKIP, app forced closed
Screen went black, except for signal meter, battery, time (in top right corner)
Removed battery and volume DOWN & POWER to boot into Recovery
same result

herb1 said:
thanks for all the advice
I've been unable to use my phone for the past few days and I'm considering the following options (getting REAL desperate here):
* should I flash the stock ROM? (I've been on the Net, looking for similar situations and 90% of peeps recommend flash the stock ROM)
* flash the HBOOT for Reflex S, then install Reflex S ROM (as per recommendations above)?
The thing is (with option 2); I can't get into adb shell as phone does not detect in Recovery or at splash screen (where I'm at at the moment)...
I've even tried Android Flasher but it does work either!!!
MatDroiD...I know (with your skill & experience) that you can help...please, I need my phone back!!!
Click to expand...
Click to collapse
The thing is with option 2... is that you don't listen lol USE FASTBOOT
Like i've previously said it's much more reliable, you get mixed results from P99IMG method

BigMrB said:
The thing is with option 2... is that you don't listen lol USE FASTBOOT
Like i've previously said it's much more reliable, you get mixed results from P99IMG method
Click to expand...
Click to collapse
I'm going to try something:
Installing this ROM = RUU_Bravo_Froyo_HTC_WWE_2.09.405.8_Radio_32.43.00.32U_5.09.00.20_release_140022_signed
hope it works

Messed up kernel install

I wanted to try Merruk's kernel so I download the 4 files that are to be used. I flashed KernelUpdate.zip first and rebooted twice. A friends required urgent help so i didnt continue the process. After waking up in the morning, I decided to continue the process. I flashed the next file i was supposed to after formatting /cache and Dalvik cache.
Now i cant boot. The phone stay stuck at the galaxy y splsh screen. I can boot into recovery. It says /cache/recovery/log cant be open. Also, it cant mount /cache/recovery/last_log
Cant open /cache/recovery/last_log
I have ADB but it seems I didnt enable the USB debuggin option. If that was possible, I could have flashed a stock kernel and tried again.

Are you sure you cant enter download mode (HOLD power+home+volume DOWN)? Remove backcase if you have, remove the battery , keep aside for 5 min, then put it back and hold the download mode combination

DiGtal said:
I wanted to try Merruk's kernel so I download the 4 files that are to be used. I flashed KernelUpdate.zip first and rebooted twice. A friends required urgent help so i didnt continue the process. After waking up in the morning, I decided to continue the process. I flashed the next file i was supposed to after formatting /cache and Dalvik cache.
Now i cant boot. The phone stay stuck at the galaxy y splsh screen. I can boot into recovery. It says /cache/recovery/log cant be open. Also, it cant mount /cache/recovery/last_log
Cant open /cache/recovery/last_log
I have ADB but it seems I didnt enable the USB debuggin option. If that was possible, I could have flashed a stock kernel and tried again.
Click to expand...
Click to collapse
just flash back to stock via odin
i advise you not to use the "ext4.zip"
use only the system 1.0.8 zip <-- extract to sdcard

hitme987 said:
Are you sure you cant enter download mode (HOLD power+home+volume DOWN)? Remove backcase if you have, remove the battery , keep aside for 5 min, then put it back and hold the download mode combination
Click to expand...
Click to collapse
So THATS how you enter download mode
leodasal2 said:
just flash back to stock via odin
i advise you not to use the "ext4.zip"
use only the system 1.0.8 zip <-- extract to sdcard
Click to expand...
Click to collapse
Well, I flashed my backup and it rebuilt the /cache. All is fine. Thank you.
A new problem has risen. I was trying to flash Creed v4.0.
I had Merruk's Kernel.
I did a reset and tried flashing the ROM. It started wiping the /system partition and came across with an error in /boot(Error 7). Im guessing its due to the kernel. It aborted.
I tied again by doing a data reset again thinking that there might have be a random error in the wiping process.
It started cleaning /data. The progress bar never moved. I waited for 15 mins and did a battery pull. When i try to boot into the recovery mode, it stays at the Galaxy Y logo.
Dowload mode works. Adb doesnt detect my device though. I wonder why.

DiGtal said:
So THATS how you enter download mode
Well, I flashed my backup and it rebuilt the /cache. All is fine. Thank you.
A new problem has risen. I was trying to flash Creed v4.0.
I had Merruk's Kernel.
I did a reset and tried flashing the ROM. It started wiping the /system partition and came across with an error in /boot(Error 7). Im guessing its due to the kernel. It aborted.
I tied again by doing a data reset again thinking that there might have be a random error in the wiping process.
It started cleaning /data. The progress bar never moved. I waited for 15 mins and did a battery pull. When i try to boot into the recovery mode, it stays at the Galaxy Y logo.
Dowload mode works. Adb doesnt detect my device though. I wonder why.
Click to expand...
Click to collapse
There is no Creed 4 for galaxy y...re flash to stock and flash Creed 3.5

I cant boot into recovery. How do I use the download mode to do so?
Edit: I installed the correct drivers for my phone while it was trying to restart(it didnt ofcourse). I booted into download mode and connected odin. Odin is not showing any signs of it connecting to the phone.
Edit2: Got it working(v1.85). I need bootloader, CSC, Modem and phone tar balls. i downloaded 2 rar files but they dont have Phone and bootloader tar balls

DiGtal said:
I cant boot into recovery. How do I use the download mode to do so?
Edit: I installed the correct drivers for my phone while it was trying to restart(it didnt ofcourse). I booted into download mode and connected odin. Odin is not showing any signs of it connecting to the phone.
Edit2: Got it working(v1.85). I need bootloader, CSC, Modem and phone tar balls. i downloaded 2 rar files but they dont have Phone and bootloader tar balls
Click to expand...
Click to collapse
Hi. Make sure you have the the drivers installed correctly. Try the one from this thread. http://forum.xda-developers.com/showthread.php?t=961956 credits to SamHaLeKe. if you have an existing driver uninstall if first, reboot your pc then install the new one. you can download stock ROMS from this thread and its complete. http://forum.xda-developers.com/showthread.php?t=1465800 credits to Doky73. If everything is ok when your phone is in download mode ODIN should be able to detect it.

Thank you all!
You have been of great help.
My phone is running fine now.
Just waiting for Merruk's kernel to get overcloking capability.

DiGtal said:
Thank you all!
You have been of great help.
My phone is running fine now.
Just waiting for Merruk's kernel to get overcloking capability.
Click to expand...
Click to collapse
Nope. There is no stable overclocking capability yet and merruk is outdated. I recommend to use kuros kernel or savies rev 73

Phone Not booting
hitme987 said:
Nope. There is no stable overclocking capability yet and merruk is outdated. I recommend to use kuros kernel or savies rev 73
Click to expand...
Click to collapse
Hello,
I have same problem,When I want to Install Stock ROM with ODIN error shows ""
{
"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"
}
""
and when I go to "Android System Recovery" (vol up + home bot + power bot) and choose Wipe data/factory reset OR wipe cache partition, Error Show "Failed to mount /Cache (invalid argument) " & "Can't mount /cache/recovery/lastlog"
What should I do?

[Guide][CWM] No Brick/ Switching Rom/ CM7 Flashing

These steps can/cannot reduce the possibility of bricking your phone in flashing Custom Rom
Requirements:
CWM recovery
Common Sense
(if you have permanent cwm you dont need to download another just skip steps 1 and 2)
1. Go to recovery mode by pressing volume up + home button + power button (simultaneously)
{
"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. Apply update from sd card (use the volume up/down for scrolling up/down home button for selecting)
​
3. Select the cwm-madteam-galaxyY.zip then you will be directed to ClockWorkMod Recovery that looks like this
​
4. Go to mounts and storage then mount all (if mounted it will be displayed e.g "unmount/system")
it will be like these
unmount /system
unmount /cache
unmount /data
unmount /sdcard​
5. Go back then Wipe Data and Cache
6. Go to advanced
Wipe Dalvik Cache
Wipe Battery Stats
Fix Permissions​
7. Go back again go to mount and storage
tick all these BUT NOT FORMAT /SDCARD
Format /system
Format /cache
Format /data​
8. Repeat Step 4
9. Go back and go to install zip from sd then choose zip from sd select the Custom Rom you want to install.Wait till it succeeded.. :angel:
10. Then Wipe Data and Cache again for reducing possibility of Bootloop
11. Reboot :laugh::laugh: (first boot of custom roms can take up to 3-5 mins.)
These Are The Simple Steps in Flashing :
Many users are confused on How to flash the CyanogenMod
Here:
1. Flash back to Stock Rom
2. Go to Recovery Mode by pressing Volume UP + Home Button + Power Button (simultaneously), wait till the bootlogo occur before releasing keys.
3. Select Apply/Install update from SD card
4. Flash the cwm-madteam-galaxyY.zip
5. Go to Mounts and Storages then mount all of it.
6. Go back then Install zip from sdcard select the supported kernel For CM
7. Go back then select scroll down to Advance(d)
8. Select Reboot to Recovery then wait till it boots again to recovery (this time it will be automatically on CWM Recovery)
9. You can see at the bottom of the screen about Errors!, ignore it. just go to mounts and storages then Format /system /data and /cache, then Go back and Wipe Data and Cache
10. Go again to mounts and storages, then mount all.
11. Lastly, Flash your CyanogenMod and just Reboot.. Wait for it to bootup and Enjoy! :laugh:

Re: No Brick
tips to reduce brick:
have a brain- don't get too excited flashing something
learn how to read- read instructions carefully and follow all steps
odin's your best friend- if all else fails you know what to do
backup is your life savior- get ready for anything, you wouldn't want any text by yer girlfriend lost forevah
--------------------------------------------------------------
By staring at this post you have waived your right to privacy
Complaints will be trolled accordingly

deathnotice01 said:
tips to reduce brick:
have a brain- don't get too excited flashing something
learn how to read- read instructions carefully and follow all steps
odin's your best friend- if all else fails you know what to do
backup is your life savior- get ready for anything, you wouldn't want any text by yer girlfriend lost forevah
--------------------------------------------------------------
By staring at this post you have waived your right to privacy
Complaints will be trolled accordingly
Click to expand...
Click to collapse
:good::good:

Re: [Steps][CWM] No Brick
If the rom has getprop in updater script, then it'll not flash on empty partition.
Sent from my GT-I9100 using xda app-developers app

thanks ill try this one.i just got rooted a while ago :good:

zenxus31 said:
These steps can/cannot reduce the possibility of bricking your phone in flashing Custom Rom
Requirements:
CWM recovery
Common Sense
(if you have permanent cwm you dont need to download another just skip steps 1 and 2)
1. Go to recovery mode by pressing volume up + home button + power button (simultaneously)
View attachment 1845289​
2. Apply update from sd card (use the volume up/down for scrolling up/down home button for selecting)
View attachment 1845344​
3. Select the cwm-madteam-galaxyY.zip then you will be directed to ClockWorkMod Recovery that looks like this
View attachment 1845309​
4. Go to mounts and storage then mount all (if mounted it will be displayed e.g "unmount/system")
it will be like these
unmount /system
unmount /cache
unmount /data
unmount /sdcard​
5. Go back then Wipe Data and Cache
6. Go to advanced
Wipe Dalvik Cache
Wipe Battery Stats
Fix Permissions​
7. Go back again go to mount and storage
tick all these BUT NOT FORMAT /SDCARD
Format /system
Format /cache
Format /data​
8. Repeat Step 4
9. Go back and go to install zip from sd then choose zip from sd select the Custom Rom you want to install.Wait till it succeeded.. :angel:
10. Then Wipe Data and Cache again for reducing possibility of Bootloop
11. Reboot :laugh::laugh: (first boot of custom roms can take up to 3-5 mins.)
Click to expand...
Click to collapse
Link in hotfile is removed please provide another link

nachi9956 said:
Link in hotfile is removed please provide another link
Click to expand...
Click to collapse
updated

nachi9956 said:
Link in hotfile is removed please provide another link
Click to expand...
Click to collapse
Please Dont quote the whole post.
----------------------------------------------------------------------------------------------------------
[Guide] [RAM EXPANDER swap] Easiest Way To Increase Ram in Galaxy Y
Click to expand...
Click to collapse

Guys,
I think I know one more method...
First check whether the zip file contains any boot.img ...
If yes, then extract zip and copy that boot image to root of SD card ..
Then compress all files in zip...
Then flash rom zip and then flash boot.img .......
I think this method is also fine.....to flash rom without brick ......
Sent from my GT-S5360

[ROM][TMO][ODEXED/DEODEXED][4.4.2][HTC 1.57 OTA] Stock+ 5/20/2014

Stock+
The mission of this ROM is to keep fairly close to the stock experience while unlocking certain features and limitations.
Furthermore my plan is to remove useless or intrusive customizations done by the manufacturer or carrier.
The kernel will have few commits, but those that are there will be for stability, battery life.
Click to expand...
Click to collapse
FEATURES
Prerooted.
Deodexed.
APNs are unlocked.
Preload data is restored.
Zipaligned.
CarrierIQ removed
**Stock kernel until I get time to pull the latest source.**
wp_mod for stock kernel thanks to @flar2
Insecure ADB (Always runs as root).
Tether Enabled
Click to expand...
Click to collapse
INSTALL
Data wipe is not required if you are coming from stock, BUT if you do wipe data do it BEFORE flashing the ROM.
Wipe /data/... or not.
Flash with TWRP.
Go into APNs and change the Default from IPV6 to IPV4.
Click to expand...
Click to collapse
Again, Thanks to @flar2 for his wp_mod.
DOWNLOAD
Latest:
HTC 1.57 OTA
OLD:
Stock+v1.01 SHA1: bc39bda6f656e323ea725f77dca0c4a3212d1044
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Please do not PM me with images of farm equipment.

CHANGELOG:
1.01 -> 1.1 (unreleased)
Added init.d support.
Full write perms to external SD.
Rebuilt framework-res with the APN changes cooked in.
Email without exchange policy enforcement. (This will probably be a flashable option.)
1.0 -> 1.01
Fixed an issue with a symlink breaking wifi. Thanks to @Andromorphone for sitting on IRC for testing the fix for this with me.
1.0
Initial release.

Screenshots:
{
"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"
}
Click to expand...
Click to collapse

Thank you so much for this!!
EDIT: Are the links broken?
EDIT 2: Downloading now. Thanks again!
Sent from my HTC One M8

VolcanicSkunk said:
Thank you so much for this!!
EDIT: Are the links broken?
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
They were indeed. It's fixed now.
Annnd It's back to bed for me. I'll repost the mega mirror in the morning.

EDIT 2: This issue was solved. Did not brick my phone. Didn't want this post to scare anyone away from a great ROM.
Think I just bricked my phone flashing this. Downloaded, confirmed hash sum, flashed via TWRP 2.7.0.2. Now phone is stuck at HTC splash screen. No amount of holding the power button will turn it off.
EDIT: Got a tip that said to hold the power and volume down buttons under a light source to try to get it to boot to bootloader. No luck.

VolcanicSkunk said:
Think I just bricked my phone flashing this. Downloaded, confirmed hash sum, flashed via TWRP 2.7.0.2. Now phone is stuck at HTC splash screen. No amount of holding the power button will turn it off.
EDIT: Got a tip that said to hold the power and volume down buttons under a light source to try to get it to boot to bootloader. No luck.
Click to expand...
Click to collapse
Hold power button and volume up, untill the phone shuts off

LIL_ROOKIE said:
Hold power button and volume up, untill the phone shuts off
Click to expand...
Click to collapse
Got pretty much the same advice in a thread I made in Q&A. Thanks for the tip though. That's exactly what I had to do. Don't know if the light source makes a difference though.
Finally got it to work. I had to hold volume up + power under a light source to get the phone to reboot. When the screen turned black I changed to the volume down while still holding the power button. This booted me to HBOOT. Then I was able to select recovery and boot there just fine. I am now restoring to my stock backup.

VolcanicSkunk said:
Got pretty much the same advice in a thread I made in Q&A. Thanks for the tip though. That's exactly what I had to do. Don't know if the light source makes a difference though.
Finally got it to work. I had to hold volume up + power under a light source to get the phone to reboot. When the screen turned black I changed to the volume down while still holding the power button. This booted me to HBOOT. Then I was able to select recovery and boot there just fine. I am now restoring to my stock backup.
Click to expand...
Click to collapse
Well, that certainly should not have happened, I am downloading from the link right now. I'll see if I can reproduce the error.
*EDIT*
So, I just did both a dirty flash, and a flash with a /data/ wipe. (A FULL data wipe, sadly.)
Phone booted fine in both cases.
Are you flashing over from a completely stock ROM?
What is your s-off satatus?
If you didn't flash from a fullty stock ROM, and did not wipe /data/ then the system was probably choking on a different SQLite schema. Doing a /data/ wipe before flashing the zip should do the trick.

Fenny said:
Well, that certainly should not have happened, I am downloading from the link right now. I'll see if I can reproduce the error.
*EDIT*
So, I just did both a dirty flash, and a flash with a /data/ wipe. (A FULL data wipe, sadly.)
Phone booted fine in both cases.
Are you flashing over from a completely stock ROM?
What is your s-off satatus?
If you didn't flash from a fullty stock ROM, and did not wipe /data/ then the system was probably choking on a different SQLite schema. Doing a /data/ wipe before flashing the zip should do the trick.
Click to expand...
Click to collapse
Hmmm.... That's strange.
I am coming from the stock operating system. I haven't restored the preload data yet. That was one of the reasons I was flashing this (so I didn't have to restore it manually). I am S-Off using Dev Unlock, TWRP + SuperSU & Root, then Firewater.
Here is my flash process:
Download from link in OP with phone to internal storage (/storage/emulated/legacy/download/)
Confirm hash using Hash Droid from Play Store
Reboot to Recovery using Quick Boot from Play Store (TWRP 2.7.0.2)
Select Wipe
Select Advanced
Checked options for system, data, Dalvik cache, cache
Slid to wipe
Repeated wipe with same options
Pressed home button
Selected Install
Chose internal memory
Navigated to /download/
Installed ROM
Since I'm at work I stopped paying attention to the screen after that since last night I had successfully flashed ViperOneM8. I didn't like the UI changes to ViperOneM8, so I restored my stock TWRP backup.

VolcanicSkunk said:
Hmmm.... That's strange.
I am coming from the stock operating system. I haven't restored the preload data yet. That was one of the reasons I was flashing this (so I didn't have to restore it manually). I am S-Off using Dev Unlock, TWRP + SuperSU & Root, then Firewater.
Here is my flash process:
Download from link in OP with phone to internal storage (/storage/emulated/legacy/download/)
Confirm hash using Hash Droid from Play Store
Reboot to Recovery using Quick Boot from Play Store (TWRP 2.7.0.2)
Select Wipe
Select Advanced
Checked options for system, data, Dalvik cache, cache
Slid to wipe
Repeated wipe with same options
Pressed home button
Selected Install
Chose internal memory
Navigated to /download/
Installed ROM
Since I'm at work I stopped paying attention to the screen after that since last night I had successfully flashed ViperOneM8. I didn't like the UI changes to ViperOneM8, so I restored my stock TWRP backup.
Click to expand...
Click to collapse
I'll try again following your process precisely. Perhaps dexopt is cowardly refusing to build the dalvik cache when /cache/ has been wiped. (This happens from time to time if there was a bad deodex.) I'll let you know how it goes.

Fenny said:
I'll try again following your process precisely. Perhaps dexopt is cowardly refusing to build the dalvik cache when /cache/ has been wiped. (This happens from time to time if there was a bad deodex.) I'll let you know how it goes.
Click to expand...
Click to collapse
Thanks so much for checking into it! I'll try it again tomorrow when I've got a lot more time on my hands. I'm just too used to flashing on the fly.

VolcanicSkunk said:
Thanks so much for checking into it! I'll try it again tomorrow when I've got a lot more time on my hands. I'm just too used to flashing on the fly.
Click to expand...
Click to collapse
Well, I did exactly the same thing as you did. I even went and downloaded the same rebooter app. The phone booted with no issue.
@Andromorphone Come back me up here. I KNOW you got it booting as well.

Whelp, I really must have done something screwy. Lol. Like I said, I'll try it again tomorrow (or late tonight if I get a chance). I'm just glad that everything works! I was hoping that no one else had the same problems I did. When I try it again I'll post back with my results. Hopefully it goes well without any hitches.

VolcanicSkunk said:
Whelp, I really must have done something screwy. Lol. Like I said, I'll try it again tomorrow (or late tonight if I get a chance). I'm just glad that everything works! I was hoping that no one else had the same problems I did. When I try it again I'll post back with my results. Hopefully it goes well without any hitches.
Click to expand...
Click to collapse
Ha! Figured it out. Disable zip signature verification. It looks like it didn't sign right but as long as the sha1 matches you should be fine.
*EDIT*
The link in the OP has a valid signature again.

Fenny said:
Well, I did exactly the same thing as you did. I even went and downloaded the same rebooter app. The phone booted with no issue.
@Andromorphone Come back me up here. I KNOW you got it booting as well.
Click to expand...
Click to collapse
indeed, flashed the initial v1.0 and subsequent version 1.01 and never had any issues booting. in fact it's working great, and very happy to be rid of carrierIQ and to have working tether.
Sent from my HTC One_M8 using Tapatalk

I am able to replicate this freeze several times.
Steps:
Downloaded ROM onto PC
Powered phone off
Ejected MicroSD card
Plugged MicroSD card into computer (USB 2.0)
Checked SHA1 hash via MD5 & SHA Checksum Utility 2.1
- Returned "SHA-1 Hash matched."
Transferred ROM to root of MicroSD card
Checked SHA1 hash again
- Returned "SHA-1 Hash matched."
Properly ejected MicroSD from PC
Reinserted MicroSD card into my M8
Booted phone and waited for it to settle
Connected phone to PC via stock USB
Confirmed Connection using "adb devices"
Rebooted phone to recovery using "adb reboot recovery"
In recovery performed the same wipe process outlined earlier
- Checked: Dalvik Cache, System, Cache, Data
- Repeated
Installed ROM from MicroSD card
Pressed Wipe Dalvik/Cache button
Phone rebooted to splash. Hung for 2+ minutes.
Rebooted to recovery via HBOOT.
Wiped again. This time included internal memory.
Installed ROM from MicroSD card
Received an Install Successful message
Pressed Reboot System
Received a warning there was no OS installed
Accidentally pressed reboot anyway
Prompted to install SuperSU since it wasn't detected (lol)
At hanging splash screen rebooted to HBOOT then recovery again
Performed single wipe
Installed from MicroSD card (again)
Install process took significantly longer than prior
Received Install Successful message
Pressed Reboot System
Screen froze while Reboot System button was highlighted
Phone booted through splash to boot animation
I am now sitting at the Welcome screen
I'm not sure if the fact that I was wiping a second time was causing some issue, but this was just a weird process. lol. After the first or second hang (I don't remember which) I exported the recovery log to the MicroSD card. I attached it to the post so hopefully it might shed some light as to what was going on.
Everything seems to have worked though. I'll go through the setup process and get back with you if there are or aren't any issues.
Thanks again for going through the same process I went through so I knew it was probably a fluke. Hopefully this is an isolated incident.
Anyway... :highfive:

VolcanicSkunk said:
*snip*
In recovery performed the same wipe process outlined earlier
- Checked: Dalvik Cache, System, Cache, Data
- Repeated
Installed ROM from MicroSD card
Pressed Wipe Dalvik/Cache button
Phone rebooted to splash. Hung for 2+ minutes.
Rebooted to recovery via HBOOT.
Wiped again. This time included internal memory.
Installed ROM from MicroSD card
Received an Install Successful message
Pressed Reboot System
Received a warning there was no OS installed
*snip*
Click to expand...
Click to collapse
Okay, I think there may be some sort of problem with TWRP and mounts/storage.
This tells me that your system partition was completely blank upon the last boot reboot:
/system | /dev/block/mmcblk0p45 | Size: 2641MB Used: 42MB Free: 2599MB Backup Size: 42MB
I have two working theories at the moment. The first is that IO was hanging when reading from your ext-sd, and then the system locked up IRQ style.
The second I think is more likely and involves the /system/ mount point. I wonder if after the second wipe, the /system/ partition was not actually mounted. It would mean that the script would flash to the tmpfs that is created for the root partition, and the files would go precisely nowhere.
The second could be proven by looking at the /data/preloads folder right after a non-booting scenario. If it exists and there are files there, then the data partiton mounted just fine, while the system partition did not.
*EDIT*
Battery is looking gooood.

Anyone not able to send or receive mms when apn switched to ip4/ip6?
Sent from my HTC One_M8 using Tapatalk

Same here
Sent from my HTC One_M8 using XDA Premium 4 mobile app