Related
OK, here is ClockworkMod Recovery for our beloved A500
NOTE:
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 or usb storage. This will revert back to actually formatting /data.
WARNING: by doing this you will lose everything that you have in /data/media.
Installation:
use adb (PC):
adb push recovery-thor2002ro-rev1.*.img /sdcard
adb push itsmagic /data/local
from terminal (TABLET):
su
chmod 755 /data/local/itsmagic
mount -o rw,remount /system
rm /system/etc/install-recovery.sh
mount -o ro,remount /system
dd if=/sdcard/recovery-thor2002ro-rev1.*.img of=/dev/block/mmcblk0p1
./data/local/itsmagic
"recovery-thor2002ro-rev1.*.rar" - is for flashing normally with the normal method...
"update-recovery-thor2002ro-rev1.*.zip" - flashed from recovery and press reboot/power off(v1.1 don't use "Advanced" -> "Reboot Recovery" only buttons in the main menu) after its flashed(don't try to flash from any other recovery other than mine, will not work)
Acer Recovery Installer APP thanks to Euclid's Brother http://forum.xda-developers.com/showpost.php?p=14818316&postcount=109
Video installation guide by cfcoleman
http://www.youtube.com/watch?v=cuf74JP5Jgw
Changelog:
1.1:
skips /data/media in backup/restore/format of /data
integrated "itsmagic"
additional option in advanced to run itsmagic manually
itsmagic is run on every restart/poweroff or recovery as a precautionary measure
ability to use usb storage in recovery for backups and restores...(has a priority system in place if usb stick is present on mount its used as a "sdcard", if not it falls back to microsd card), unmount and mount will also trigger this.
1.2:
flexrom backup & restore
bct + ebt + pt + gp1 backup(basically the first sectors of the flash that sc2k told you to backup when itsmagic got released...)
retrieve uid
itsmagic run at startup
usb keyboard fix
1.3.2:
fixed background disappearing
removed itsmagic from reboot/poweroff, not needed itsmagic is run at startup...
fixed flexrom not being present in advanced restore menu
1.3.3:
fixed back disappearing in Mounts and Storage menu
1.3.4(still in testing...):
added sync before md5 generation
sync and unmount of /sdcard after succesful backup
sync and unmount of /sdcard at reboot/poweroff
Thanks to sc2k for testing this.
Even though this recovery has been tested, I am not liable for any loss of data or any damages done by this recovery.
tnx for this!!
great!!
thor2002ro said:
OK, here is ClockworkMod Recovery for our beloved A500
Includes:
skips /data/media in recovery/restore/format of /data
integrated "itsmagic"
additional option in advanced to run itsmagic manually
itsmagic is run on every restart/poweroff or recovery as a precautionary measure
ability to use usb storage in recovery for backups and restores...(has a priority system in place if usb stick is present on mount its used as a "sdcard") if not it falls back to microsd card), unmount and mount will also trigger this.
NOTE:
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 or usb storage. This will revert back to actually formatting /data.
WARNING: by doing this you will lose everything that you have in /data/media.
Installation:
remove /system/etc/install-recovery.sh if present
dd the image to mmcblk0p1
run itsmagic
TO DO:
flexrom backup & restore
bl + bct backup
retrieve uid
Thanks to sc2k for testing this.
Even though this recovery has been tested, I am not liable for any loss of data or any damages done by this recovery.
Click to expand...
Click to collapse
1.before we dd the image to mmcblk0p1 ，do we have to install itsmagic first
u said u had integrated itsmagic in that recovery，but how do we run that itsmagic，from where？
2. what is the “bl” and “bct” stand for？
3. is “to do……” what we can do or something else ？i cant understand it sorry。
I am all over this but please add more thorough instructions. Thanks
Awesomeness, that is all
Sent from my ADR6400L using XDA Premium App
Yea tend to agree sounds awesome. But if we could have a more clear set of instructions. So people don't brick their tablet.
Sent from my PC36100 using XDA Premium App
to do means things he wants to add to or fix in this release.
What does dd stand for?
ibila said:
to do means things he wants to add to or fix in this release.
What does dd stand for?
Click to expand...
Click to collapse
Well thanks for explaining what to do means...
dd is the termed used to dump this image to a particular block in this case block 0p1
ibila said:
to do means things he wants to add to or fix in this release.
What does dd stand for?
Click to expand...
Click to collapse
o ,I see
"dd" is a command in linux, it can write a img to a partition or block
in this case, we can use that command like this:
dd if=/sdcard/recovery-thor2002ro-rev1.1.img of=/dev/block/mmcblk0p1
thor2002ro said:
Even though this recovery has been tested, I am not liable for any loss of data or any damages done by this recovery.
Click to expand...
Click to collapse
hmm... you could not find a smaller font?
Dexter_nlb said:
hmm... you could not find a smaller font?
Click to expand...
Click to collapse
lol not very nice though.
updated instructions...
anybody know how to do it from Windows? (no DD)
Dan2552 said:
anybody know how to do it from Windows? (no DD)
Click to expand...
Click to collapse
dd is on the tablet not windows...
thor2002ro said:
updated instructions...
Click to expand...
Click to collapse
Where are the "updated instructions"
Crsdr37 said:
Well thanks for explaining what to do means...
dd is the termed used to dump this image to a particular block in this case block 0p1
Click to expand...
Click to collapse
Hmmm there is maybe a tiny one in a million chance that your not the only participator in this thread so who knows...maybe this explanation was not for you but for kimcai.
Sorry if i just burst your bubble
docfreed said:
Where are the "updated instructions"
Click to expand...
Click to collapse
OP
10char
ibila said:
OP
10char
Click to expand...
Click to collapse
Doh! Thanks
Dexter_nlb said:
hmm... you could not find a smaller font?
Click to expand...
Click to collapse
its called "the fine print"
thor2002ro said:
updated instructions...
Click to expand...
Click to collapse
what can we do in your modified recovery？
This tutorial is made to help those getting an Iconia for the first time as well as those who lost/didn't backup before going to custom ROMs.
We will try to help you using more than one variant #1, #2 etc to backup and restore your tablet. If you're new stick to the #1s in the first post. If you know a little Android and a little Linux, head to the second post.
Acer does not provide any full-restore ROMs at the moment so your best option is to create your own backup in case something goes wrong.
The ultimate goal is to help users restore their OTA (over the air) update function, aka. get the OS as fresh and clean as it was the day it came out of the factory.
Help us help you! The parts of the tutorial that aren't ready or require your attention are marked in RED. If you got:
A new tablet, never flashed with a custom rom, share your original backup with US, you will need it anyway once you decide to experiment!
A new tablet, never updated, share your Firmware and "Operated Countries" (on the back of the box) so we know what stock ROM belongs to which countries or continent.
Knowledge and the will to share it!
Before you start!
Don't be afraid of rooting, it will not break your OTA (un-rooting is a piece of cake) updates and it is essential to do a proper backup!
Back up your user files from music to documents and save games or you might lose them!
When everything fails > Privacy > data reset is a good way to start fresh. Best to use it when trying something new.
Always unfreeze/restore system APKs like telephony etc before formatting/soft resetting (not to be confused with turning on and off again) your tablet.
Any .zip on the micro-sd card will be automatically flashed on POWER & VOL-
Save Acer Recovery Installer, Root, your favorite file explorer on your desktop
Droid Explorer (PC app) can be a great tool to install apps from your PC
Before attempting to OTA update: un-root, make sure all system apps are in place, remove micro-sd, factory reset (some have reported success after these)
Unbricking
Get the right firmware (Full Package, thanks Vache), for your tablet, decrypt it and extract the update.zip
Put it on your micro-sd card. Shut down. Boot with power and VOL - pressed and it will automatically get flashed.
What firmware is right for my country?
Full Package Acer_A500_0.000.00_1.016.01_COM_GEN1
CWM Backup Acer_A500_0.000.00_1.016.05_COM_GEN1 - Provided by flyinghighaero
Update zip Acer_A500_0.000.00_1.105.01_EMEA_GEN3 - Provided by bpivk
EU: AT, BE, CY, CZ, DK, EE, FI, FR, DE, GR, HU, IE, IT, LV, LT, LY, MT, NL, PL, PT, SK, SI, ES, SE, GB, IS, LI, NO, CH, BG, RO, TR.
Full Package Acer_A500_0.000.00_1.104.02_COM_GEN1:
USA
Full Package Acer_A500_0.000.00_1.104.05_COM_GEN1
Canada
Acer_A500_0.000.00_1.112.01_EMEA_CUS7 - Not available
Germany
Acer_A500_0.000.00_1.016.04_COM_GEN1 - Not available
Thailand - Probably Asia, needs confirmation
Full Package Acer_A500_0.000.00_1.104.03_COM_GEN1
Taiwan - Probably Asia, needs confirmation
Acer_A500_1.105.01_EMEA_GEN3 - Not available
reports of Netherlands and Mexico - hard to tell what EMEA means to Acer
Acer_A501_1.309.02_COM_GEN1 - Warning, this is an European ROM for A501 !!! - thanks captainpaella
Did your tablet come with one of the following firmwares or maybe another one? (Settings > About tablet), tell us what countries/continent it is for by checking the back of the box for the "Operated Countries" label and posting it below:
Acer_A500_0.000.00_1.013.01_EMEA_GEN1
Acer_A500_0.000.00_1.104.04_COM_GEN1
Acer_A500_0.000.00_1.016.02_COM_GEN1
Creating a backup with Acer Recovery Installer #1
Root
Acer Recovery Installer
Install clockwork mod:
select "ClockworkMod Recovery rev1.3.4 by thor2002ro"
click "Install Recovery Image"
click "Yes" when asked to backup the current image!!!
Reboot into CW recovery from the app or with VOL- & POWER
Create a full backup: "backup and restore" -> "Full Backup"
If your backup is a fresh stock-only (no previous custom roms flashed) one, please share it. It's located on your micro SD in clockworkmod/backup/[current date] <= This is the CWM folder we need!
Don't forget to restore the original recovery image to be able to install futher updates. Unrooting might be necesary depending on Acer.
Restoring to defaults via CWM #1
Full restore in CWM: "backup and restore" -> "Full Backup"
Enter Acer Recovery Installer and restore recovery.img!
Aditional restoring info
Remember: un-root, remove micro-sd, factory reset if it doesn't work.
Also don't have modified, removed or frozen system apps, wi-fi module, build.prop or any other OS file!
"dd" method in the second post is practical if you'll want to downgrade from a FW that has no root yet - still needs testing (eg. if you update to a future 3.2 you won't be able to go back to 3.1 or 3.0.1 until 3.2 is rooted, because CWM needs root, here's where ADB and "dd" can really come in handy!)
Available backups:
Updates of original Acer_A500_1.016.01_COM_GEN1
CWM backup successfully used by me, containing: Stock 1.016.01_COM_GEN1 OTA updated to 1.139.02. 1.139.02 is a "dud" - a FW update taken down by ACER that breaks updates; to solve this issue flash the update.zip(1.139.05) with the default acer bootloader (restore the original recovery.img from Acer Recovery Installer to get the default acer bootloader)
1.141.05 provided by Thor - Restore with "dd", see post 2!
Please provide your own CWM folder or flexrom, boot, recovery and system.img, full dumps (p1, p2, p3... description for this method below)
Do not provide
system.zip containing system/app files
3.1 ROMs - the purpose here is to know if OTA is working
What worked for me:
Done with CWM!
Un-root, restore to stock, remove micro-sd - probably not all necesary but it worked for me.
First of all I flashed to my default rom: Acer_A500_0.000.00_1.016.01_COM_GEN1 from Acer's server, didn't have a backup.
I installed acer recovery installer, rooted and then CWM restored 1.139.02. This firmware is probably Acer's mistake as it is not available anymore, nor can you OTA update from it.
Then I entered Acer Recovery Installer, restored the original recovery.img, un-rooted and restored to factory defaults.
Placed Acer_A500_1.016.01_1.139.05_COM_GEN1 on my micro SD and rebooted into Acer's recovery (PWR&VOL-) installed with no issues.
After the reboot 4.010.22 was available! Started the download, removed the micro-sd(probably wasn't necessary) and the tablet rebooted and installed the update properly!
Voila, 3.1 (4.010.22, kernel 2.6.36.3) with the help of CWM!
This is all the Info I was able to gather about a full restore. Put it to good use and be productive - tell us your results!
Additional backup and recovery methods
Creating a backup via ADB #2
If you're uncomfortable with ADB, this should work with Terminal Emulator +/- Busybox too. Just skip to step 4.
Or you can try the automatic backup tool, just fire it up and follow the instructions. Root and 1GB on the external SD required.
Get ADB + Java both for x32 even if you have windows on 64 bit!
Get the Iconia A500 USB drivers
Run SDK Manager from "C:\Program Files (x86)\Android\android-sdk" and let it download it's junk. I've no idea how much of it you'll need.
Go to "C:\Program Files (x86)\Android\android-sdk\platform-tools"
Create a text file that will contain "cmd" and save it.
Rename your text file ADB.bat and create a shortcut on the desktop for convenience
Root then go to Settings > Applications > Development > USB debugging
Open your adb shortcut, connect the tablet and type "adb shell"
"$" will show up, meaning that you are logged in as an User
type "su", accept the superuser request on your tab
"#" you're now Admin and can issue backup commands.
Backup the first 0x680000 bytes of mmcblk0 and all partitions (except cache + data) with dd:
dd if=/dev/block/mmcblk0 bs=512 count=13312 of=/mnt/external_sd/dumps/mmcblk0_start
dd if=/dev/block/mmcblk0p1 of=/mnt/external_sd/dumps/p1
dd if=/dev/block/mmcblk0p2 of=/mnt/external_sd/dumps/p2
dd if=/dev/block/mmcblk0p3 of=/mnt/external_sd/dumps/p3
dd if=/dev/block/mmcblk0p5 of=/mnt/external_sd/dumps/p5
dd if=/dev/block/mmcblk0p6 of=/mnt/external_sd/dumps/p6
dd if=/dev/block/mmcblk0p7 of=/mnt/external_sd/dumps/p7
Thanks sc2k!
Restoring to factory defaults via Terminal #2
Root
Install Terminal Emulator, Busybox installer and Acer Recovery Installer
Copy system.img, flexrom.img, boot.img, recovery.img in /mnt/sdcard
Run (flash system.img last, it will lock down your tablet and you won't be able to flash the other .img files):
/data/data/com.interphaze.AcerRecoveryInstaller/files/itsmagic
dd if=/mnt/sdcard/flexrom.img of=/dev/block/mmcblk0p6
dd if=/mnt/sdcard/boot.img of=/dev/block/mmcblk0p2
dd if=/mnt/sdcard/recovery.img of=/dev/block/mmcblk0p1
dd if=/mnt/sdcard/system.img of=/dev/block/mmcblk0p3
Restoring to factory defaults via ADB #3
Get ADB + Java both for x32 even if you have windows on 64 bit!
Get the Iconia A500 USB drivers
Run SDK Manager from "C:\Program Files (x86)\Android\android-sdk" and let it download it's junk. I've no idea how much of it you'll need.
Go to "C:\Program Files (x86)\Android\android-sdk\platform-tools"
Create a text file that will contain "cmd" and save it.
Rename your text file ADB.bat and create a shortcut on the desktop for convenience
Root then go to Settings > Applications > Development > USB debugging
Open your adb shortcut, connect the tablet and type "adb shell"
"$" will show up, meaning that you are logged in as an User
type "su", accept the superuser request on your tab
"#" you're now Admin and can issue flashing commands.
Install Acer Recovery Installer
Copy system.img, flexrom.img, boot.img, recovery.img in /mnt/sdcard
Run (flash system.img last, it will lock down your tablet and you won't be able to flash the other .img files):
/data/data/com.interphaze.AcerRecoveryInstaller/files/itsmagic
dd if=/mnt/sdcard/flexrom.img of=/dev/block/mmcblk0p6
dd if=/mnt/sdcard/boot.img of=/dev/block/mmcblk0p2
dd if=/mnt/sdcard/recovery.img of=/dev/block/mmcblk0p1
dd if=/mnt/sdcard/system.img of=/dev/block/mmcblk0p3
I hope many people who just bought their tablet will come here and post the recovery files asap they got it...
I need to return with 01.139.04
If you use the Acer Recovery Tool from the market, would that do the same thing to take you back to stock?
link
Please, always run itsmagic BEFORE any dd operation.
@Bec07: Please swap the commands in your guide.
Restoring to factory defaults via ADB #2
In Step 7 where are the files located that I'm supposed to be copying? Can't find them?
They're supposed to be in /clockwork mod on your micro-sd car, provided you've don a backup. Or you can download them.
@haakuturi
No, I've tried even if you can download the update, it will fail installing. Tried with pre 3.1 updates.
@sc2k
Thanks, fixed. But don't the checksums change after we flash the partitions?
sanaell said:
I hope many people who just bought their tablet will come here and post the recovery files asap they got it...
I need to return with 01.139.04
Click to expand...
Click to collapse
Don't you remember your initial firmware?
Could you check it when close to an iconia stocking shop?
Great tutorial... Thanks
So, a question... If the Restore function in CWM doesn't restore properly, does it backup properly? That is, if I manually restore the files that CWM made when it backed up, will it restore properly or did the backup miss something?
I don't think it backs up properly either. At least not by all checksum standards.
My backup is CWM and I can't restore it with "dd" no matter what. Thor's works but I suspect it's not CWM.
Scrap that! CWM works just fine!
Bec07 said:
I don't think it backs up properly either. At least not by all checksum standards.
My backup is CWM and I can't restore it with "dd" no matter what. Thor's works but I suspect it's not CWM.
Click to expand...
Click to collapse
Well that's bloody annoying... :/
If I'd known that, I'd have manually backed up my stock ROM...
Tell me about it...
I think I flashed 15-20 times in the past 3 days. Haven't managed to make OTA work for 3.0.1 and now they're all down and I can't see 3.1 either...
can i do the "proper" backup from within the tablet with something like connectbot that has sdcard writing permissions without rooting?
Probably with terminal emulator and busybox too
Bec07 said:
Don't you remember your initial firmware?
Could you check it when close to an iconia stocking shop?
Click to expand...
Click to collapse
I think that was 1.016.01 but I do remember the first update I got was 1.139.04 pushed by OTA
THailand
I'm not aware of any problem with the backup/restore with CWM. I'll try to do some testing to see. The boot, recovery images from CWM should work with the dd command, but the system and data are compacted in a YAFFS2 format and cannot be used with the dd command.
I know the initial version did not run itsmagic automatically, so the checksum of boot would be off after a restore, but that was fixed.
Not sure if this helps but my a500 came with Acer_A500_1.105.01_EMEA_GEN3.
I live in the Netherlands and i have a backup which contains flexrom system and boot.img as well as the update.zip to get it to version Acer_A500_1.141.01_EMEA_GEN3
Download here.
Iconia Build Number
Mine is Acer_A500_1.141.01_EMA_GEN3, I bought the tablet on México.
sanaell said:
I think that was 1.016.01 but I do remember the first update I got was 1.139.04 pushed by OTA
THailand
Click to expand...
Click to collapse
Are you sure, it was 01 because I know mine was 01 and I'm from EU. Wasn't it 02?
spaanplaat said:
Not sure if this helps but my a500 came with Acer_A500_1.105.01_EMEA_GEN3.
.
Click to expand...
Click to collapse
Can you guys look on the back of your box, there should be a sticker "Operated Countries" that should list in what other countries the same firmware version is for.
I suspect EMEA should cover EU, Middle east and Asia, but I've got no idea why there are also separate versions
Thanks!
Flashed a rooted stock Android 4.2 ROM, root appeared to be broken so i figured rather than be late for work i'd flash my nandroid backup i did beforehand. Now recovery can't find the backup location, and under any file explorer it appears as '0' which i have to select first to view the files. Because of this CWM can't see the backup folder. HELP
That's because of the 4.2 multi-user feature, it needs to separate files of multiple users somehow, so it just moves all your files to "0" subdirectory. If you add another users, they will have their own folders.
It should be okay to just move /data/media/0/TWRP to /data/media/TWRP, either via TWRP's file manager or via adb shell while in recovery:
Code:
mv /data/media/0/TWRP /data/media/
Tasssadar said:
That's because of the 4.2 multi-user feature, it needs to separate files of multiple users somehow, so it just moves all your files to "0" subdirectory. If you add another users, they will have their own folders.
It should be okay to just move /data/media/0/TWRP to /data/media/TWRP, either via TWRP's file manager or via adb shell while in recovery:
Code:
mv /data/media/0/TWRP /data/media/
Click to expand...
Click to collapse
Thank you for your help but I'm using clockworkmod recovery. What do i need to change in that command to suit CWM?
Matty Matt said:
Flashed a rooted stock Android 4.2 ROM, root appeared to be broken so i figured rather than be late for work i'd flash my nandroid backup i did beforehand. Now recovery can't find the backup location, and under any file explorer it appears as '0' which i have to select first to view the files. Because of this CWM can't see the backup folder. HELP
Click to expand...
Click to collapse
Haha, I thought I was the only one! I thought I had partitioned my card somehow. I basically did the same thing as you. I also am running CWM. Its making Rom flashing almost impossible for me, I can only select & flash files from the SD "O". All my nandroids are on the regular SD selection. Did you ever find you answer Matt.?
Sent from my Nexus 7 using Tapatalk 2
This is the latest 2.1 for ZTE OPEN C, to install download extract to /sdcard/clockworkmod/backup use .50 recovery to install by choosing restore, navigate to /sdcard/clockworkmod/backup/new_2.1 then let .50 recovery restore 2.1, reboot and enjoy 2.1
in recovery mode
backup and restore > restore from /external_sd > new_2.1 > yes restore
https://drive.google.com/folderview?id=0B_6NtXCtTLkHeGgzcDVwWnZWR2c&usp=sharing
my roms use stock kernel, comes from Open_C_upgrade_Tool: http://alturl.com/2bpns
vampirefo said:
This is the latest 2.1 for ZTE OPEN C, to install download extract to /sdcard/clockworkmod/backup use .50 recovery to install by choosing restore, navigate to /sdcard/clockworkmod/backup/new_2.1 then let .50 recovery restore 2.1, reboot and enjoy 2.1
in recovery mode
backup and restore > restore from /external_sd > new_2.1 > yes restore
https://drive.google.com/folderview?id=0B_6NtXCtTLkHeGgzcDVwWnZWR2c&usp=sharing
Click to expand...
Click to collapse
Thank you so much vampirefo, I am loving this build so far!
KUPOinyourWINDOW said:
Thank you so much vampirefo, I am loving this build so far!
Click to expand...
Click to collapse
This is the best build of Firefox OS I have ever used, omg. I don't know what it's like for you, but I can't find many bugs.
thanks man
overall i like it
the only negative is when unstick App Transition, opening/closing app/setting becomes very slow (in 1.4 i did unstick to make it faster/smooth)
2.1 works well, however 1.4 is more refined, closer to being released, Once 2.1 gets closer to being released it will be the preferred firefox version.
vampirefo said:
..in recovery mode
backup and restore > restore from /external_sd > new_2.1 > yes restore
Click to expand...
Click to collapse
It can't find the folder.
Unmounted and mounted the external_sd didn't help.
What's going wrong?
Thanks for the build!
But could you please explain how to use .50 recovery?
I am trying to flash it to my open c with:
adb push cw_recovery_50.img /sdcard/cwm.img
But I get:
failed to copy 'cw_recovery_50.img' to '/sdcard/cwm.img': Read-only file system
YemSalat said:
Thanks for the build!
But could you please explain how to use .50 recovery?
I am trying to flash it to my open c with:
adb push cw_recovery_50.img /sdcard/cwm.img
But I get:
failed to copy 'cw_recovery_50.img' to '/sdcard/cwm.img': Read-only file system
Click to expand...
Click to collapse
You don't have to adb push the recovery to sdcard, use fastboot to boot recovery.
fastboot boot cw_recovery_50.img
or to install recovery
fastboot flash recovery cw_recovery_50.img
happyass**** said:
It can't find the folder.
Unmounted and mounted the external_sd didn't help.
What's going wrong?
Click to expand...
Click to collapse
do you have a micro sdcard installed? did you extract the backup in correct place?
vampirefo said:
do you have a micro sdcard installed? did you extract the backup in correct place?
Click to expand...
Click to collapse
Well I've got an sdcard in it which I used on 1.4. Or do I need to initialize it or do anything in particular? I even did 'format' of the recovery menu..
happyass**** said:
Well I've got an sdcard in it which I used on 1.4. Or do I need to initialize it or do anything in particular? I even did 'format' of the recovery menu..
Click to expand...
Click to collapse
Unless you have used recovery to make a backup, then you need to create all the folders, if you have used recovery to make a backup, folders would have been created except for new_2.1, which is made when you extract 2.1.
if you don't have /clockworkmod/backup folders on your sdcard you need to make them, then in /clockworkmod/backup extract 2.1
in recovery mount external_sd
then post output of
adb shell ls /external_sd/
adb shell ls /external_sd/clockworkmod/backup/
Thanks for the tip!
I managed to get .50 recovery working, but now when I am restoring from external_sd it says:
Error while restoring /system!
YemSalat said:
Thanks for the tip!
I managed to get .50 recovery working, but now when I am restoring from external_sd it says:
Error while restoring /system!
Click to expand...
Click to collapse
That usually means bad download, you may need to redownload 2.1.
vampirefo said:
That usually means bad download, you may need to redownload 2.1.
Click to expand...
Click to collapse
I re-downloaded it and it now falls with hash mismatch for system.ext4.tar.a
I tried formatting the sd card with .50 recovery but it still gives that error.
Is there any way to do the update via fastboot by any chance?
No, your sdcard is bad, if you have room on internal sdcard, make folders and extract 2.1 there.
sent from my kingSing T1 via taptalk
vampirefo said:
No, your sdcard is bad, if you have room on internal sdcard, make folders and extract 2.1 there.
sent from my kingSing T1 via taptalk
Click to expand...
Click to collapse
I just did an adb push to the card:
adb push new_2.1 /sdcard/clockworkmod/backup/new_2.1/
But when I'm in .50 recovery - it does not see the new_2.1 folder. It only sees the one it created earlier when I did a backup.
Any idea what the heck could be wrong? xP
No ideal without looking at your sdcard.
sent from my kingSing T1 via taptalk
vampirefo said:
No ideal without looking at your sdcard.
sent from my kingSing T1 via taptalk
Click to expand...
Click to collapse
Sorry about all the stupid questions, just the last one - can it be done via 'zip install' in recovery by any chance? Or does it have to be through restore?
The version I uploaded is restore only, you could make a zip install if you want, use Google to find info how to build cwm installation zip.
sent from my kingSing T1 via taptalk
Ok, thanks for the help!
I'll post the zip here if I succeed in making one.
I have jamal2367's [AOSP] official 4.4.2 - S4 Google Edition ROM installed (final R1.2) a SGH-1337M.
The other day it started getting stuck on boot; the blue, red, yellow, green circles just continually go in and out without anything else happening. I have booted into CWM Recovery (v6.0.4.4) and done a wipe cache partition and wipe dalvik cache but it did not help.
Can anyone provide advice/steps on how to copy the data (mostly pics and WhatsApp history) off this phone? SMS history would also be nice but not necessary.
toggly said:
I have jamal2367's [AOSP] official 4.4.2 - S4 Google Edition ROM installed (final R1.2) a SGH-1337M.
The other day it started getting stuck on boot; the blue, red, yellow, green circles just continually go in and out without anything else happening. I have booted into CWM Recovery (v6.0.4.4) and done a wipe cache partition and wipe dalvik cache but it did not help.
Can anyone provide advice/steps on how to copy the data (mostly pics and WhatsApp history) off this phone? SMS history would also be nice but not necessary.
Click to expand...
Click to collapse
I would make a backup in your recovery and then flash the rom you had installed. See if that helps.
Edit: You didn't try to update. I changed my comment saying you had tried.
1. Download Aroma File Manager
2. Put a external sd into your phone.
3. Boot into the custom recovery and flash the Aroma file.
4. It will boot into a file browser and you can copy all the files from internal to your external.
ps it's possible that your custom recovery already has a filemanager build in. Then all these steps are obsolete.
I boot into AROMA Filemanager but I can't see anything on the internal SD card (see attachment).
Any ideas? Does that folder icon mean the "sdcard" folder is encrypted?
toggly said:
I boot into AROMA Filemanager but I can't see anything on the internal SD card (see attachment).
Any ideas? Does that folder icon mean the "sdcard" folder is encrypted?
Click to expand...
Click to collapse
Is it encrypted? Then probably it won't work. In that case just reflash the rom you are on without wiping.
toggly said:
Does that folder icon mean the "sdcard" folder is encrypted?
Click to expand...
Click to collapse
Lennyz1988 said:
Is it encrypted? Then probably it won't work. In that case just reflash the rom you are on without wiping.
Click to expand...
Click to collapse
I don't know, that's why I am asking what that icon means?
You say CWM is working, so you can just adb pull everything you need. Applications usually save data in a directory under /data/data or /sdcard/Android/data.
You should find the directories you want with adb shell, then you can adb pull them, then if you reflash your rom you can adb push them back into the same locations. Also, depending where they are saved, your pictures will most likely not be deleted when you reflash your rom. Better safe than sorry though.
If you don't have adb you'll have to download the binary, or you can install the entire Android SDK. Which operating system do you use?
toggly said:
I don't know, that's why I am asking what that icon means?
Click to expand...
Click to collapse
The icons means that it's symlinked. If it's not encrypted then you should find the data. It can be in an other place then where you are looking. Try looking in /data/media or some other maps in /data
Or just flash the rom you are currently on without wiping.
soldier9599 said:
You say CWM is working, so you can just adb pull everything you need. Applications usually save data in a directory under /data/data or /sdcard/Android/data.
You should find the directories you want with adb shell, then you can adb pull them, then if you reflash your rom you can adb push them back into the same locations. Also, depending where they are saved, your pictures will most likely not be deleted when you reflash your rom. Better safe than sorry though.
If you don't have adb you'll have to download the binary, or you can install the entire Android SDK. Which operating system do you use?
Click to expand...
Click to collapse
Adb won't work unless he already has authorized adb when his device was booted.
toggly said:
I boot into AROMA Filemanager but I can't see anything on the internal SD card (see attachment).
Any ideas? Does that folder icon mean the "sdcard" folder is encrypted?
Click to expand...
Click to collapse
You need to mount partitions to see the contents.. Go to Aroma File Manager Settings and check the option "Moumt automatically partition on boot".. then restart your recovery and flash again the Aroma File Manager
Lennyz1988 said:
Adb won't work unless he already has authorized adb when his device was booted.
Click to expand...
Click to collapse
I've had devices where the first thing I did with them was unlock bootloader, fastboot flash recovery, and then go into recovery and adb sideload, all without booting the system.
peppe130 said:
You need to mount partitions to see the contents.. Go to Aroma File Manager Settings and check the option "Moumt automatically partition on boot".. then restart your recovery and flash again the Aroma File Manager
Click to expand...
Click to collapse
That did the trick, thanks!!
Nothing
soldier9599 said:
I've had devices where the first thing I did with them was unlock bootloader, fastboot flash recovery, and then go into recovery and adb sideload, all without booting the system.
Click to expand...
Click to collapse
Yes and I believe that. But from version 4.2.2 android forces rsa encryption. So you need to boot into your rom and enable it. Unless the custom rom/kernel has disabled it, but I haven't seen any that have.