Related
Anyone got a way to fix recovery so I can wipe dalvik and ext? re-flashed recovery with cm and armon no fix 0o any ideas? - also nand restore and backup does not work anymore
xillius200 said:
Anyone got a way to fix recovery so I can wipe dalvik and ext? re-flashed recovery with cm and armon no fix 0o any ideas? - also nand restore and backup does not work anymore
Click to expand...
Click to collapse
Broken SD? Any interesting error messages?
billquinn1 said:
Broken SD? Any interesting error messages?
Click to expand...
Click to collapse
nope tried other SD and the error messages I get are for example: Error: Run "wipe dalvik" via adb!
XD this is why this question is confusing because I can't see anything out of the ordinary
How do you wipe dalvik via adb didn't think it had the option do you have to use shell in adb?
xillius200 said:
nope tried other SD and the error messages I get are for example: Error: Run "wipe dalvik" via adb!
XD this is why this question is confusing because I can't see anything out of the ordinary
How do you wipe dalvik via adb didn't think it had the option do you have to use shell in adb?
Click to expand...
Click to collapse
I can't try this right now but I think it would be
adb remount
adb shell
#mount -a
#rm /system/sd/dalvik-cache/*
May be easier to use a root file explorer (SUFBS) and just delete every thing on system/sd and then boot to recovery and wipe and repair everything. You did try "repair ext" right?
billquinn1 said:
I can't try this right now but I think it would be
adb remount
adb shell
#mount -a
#rm /system/sd/dalvik-cache/*
May be easier to use a root file explorer (SUFBS) and just delete every thing on system/sd and then boot to recovery and wipe and repair everything. You did try "repair ext" right?
Click to expand...
Click to collapse
XD ill try that with the shell and yeah tried repair ext etc. same error as dalvik cache etc.
Yeah that command for the wipe dalvik worked with adb thanks for that
XD thanks for your help seems that both sd cards that I tried being my luck -_- don't have a ext partition wth happened to them I don't know but fixed both of them now the system recovery didn't want to create them had to creat them through adb but everything is working now
Thanks for your help billquinn1 - Very much appreciated
Hi,
I found the --update_package=SDCARD:update.zip command that, when written to /cache/recovery/command can let the recovery auto-execute the flash.
I searched for other commands but did not found a thing (xda, google)...
Isn't it an index somewhere on what commands can be executed?
I hope there is some others... isn't it?
Thx
Not sure I fully understand...
Do you want the commands available in recovery shell?
If so, it's all busybox... but perhaps I misunderstand?
I think its not busybox. Ill try to express myself better:
The file cache/recovery/command can have recovery commands that will be auto executed on next boot into recovery.
What are they? Any list?
The only one i know is --update-package which flash an update.zip
Sent from my Nexus One
Bump!
Come one, someone has to know.
Please, that could really be helpfull for all ROM cookers
Since you have the AOSP code, have you tried searching through it ?
britoso said:
Since you have the AOSP code, have you tried searching through it ?
Click to expand...
Click to collapse
From the stock recovery I can see:
--update_package=root: path - verify install an OTA package file
--wipe_data - erase user data (and cache), then reboot
--wipe_cache - wipe cache (but not user data), then reboot
But what about custom recoveries?
Do they have other commands?
I see no other commands from koush's repository @ github and just wanted to be sure.
My main question is: is there recovery commands for nanbackup?
This is a basic question that is annoying because it highlights how much I don't really understand.
What is actually wiped using the different recoveries and should I prefer one over the other?
Details:
I have been using Amon_RA 1.5.2 for quite some time and it is fine. But recently I had to revert to a sense rom to get the newest PRL (60677) since I wasn't getting SMS. When reverting, it made me wonder where this update was kept that it wasn't removed during my wipe, and also, are there other things hanging around which should be cleaned up?
My current root file structure looks like this (ND=not a directory):
acct
cache
config
d
data
default (ND)
dev
etc
init (ND)
init.goldfish (ND)
init.heroc (ND)
init (ND)
mnt
..../asec
..../sdcard
..../secure
proc
root
sbin
sd-ext
sdcard
sys
system
*I had been messing with Apps2SD though it is not currently used on this set up. Should explain the multiple SD card mnts.
Amon_RA 1.5.2 Wipe Menu
Wipe
Wipe data/factory reset :: Wipe /data and /cache
Wipe Dalvik-cache :: Wipe Dalvik-cache both on /data and ext
Wipe SD:ext partition : Wipe the ext partition on your sdcard
Wipe battery stats : Wipe the battery stats in /data
Wipe rotate settings : Wipe the sensor settings in /data
Clockwork 2.5.0.7 Wipe Menu
wipe data/factory reset
wipe cache partition
Additional Clockwork 2.5.0.7 Mounts and Storage Menu
format boot
format system
format data
format cache
format sdcard
format sd-ext
Any clarification would be much appreciated by me, and I assume the community. Thanks.
--------------------------------------------------------------------
A different thread discussing general difference between Amon_RA and Clockwork
I can't provide much help technically, but I wanted to point out clockwork 2.5 also has a Wipe Dalvik Cache option under the Advanced menu.
I'd definitely like some more technical information too, but I can provide what I've read and observed.
Factory reset wipes data AND cache.
Wiping boot and system happen already when flashing a rom and wiping either will require you to nandroid or reflash the rom. Many roms seem to suppress the messages or something.
[dpeeps74]
mtnchkn said:
Details:
I have been using Amon_RA 1.5.2 for quite some time and it is fine. But recently I had to revert to a sense rom to get the newest PRL (60677) since I wasn't getting SMS. When reverting, it made me wonder where this update was kept that it wasn't removed during my wipe, and also, are there other things hanging around which should be cleaned up?
Click to expand...
Click to collapse
The radio itself, PRL, PRI, and profile, are all stored in a deeper part of the phone than recovery or bootloader, if I remember right it's hardcoded into the dialer function of the phone (NOT in the .apk or ROM), so they stick no matter what you wipe or flash. As for what's different between the 2 recoveries, they both do basically the same thing, but CWM has more wipe options and is newer code, also when flashing zips from CWM you can actually select them inside of folders from your sd, whereas with amon ra it must be on the root of your sd. Also, in amon ra there is an option to "fix UID mismatches" which could be helpful if your device goes crazy but I've never had to use it. CWM has a fix permissions option, but you can also do that from TE, so again, not much use to me personally. I use 2.5.0.1 because it will flash both amend and edify zips, it's green, and doesn't give me the error code that 2.5.0.7 did. I have used every recovery available for the heroc. Also, the 3x versions of CWM have even more options and wipe options. The other sucky thing about CWM is the fact that wipe sd is right next to wipe cache in mounts so people sometimes wipe the wrong one. That is why tte one in the main menu is the one to use for wiping cache. Also, wipe and format are the same thing, different words. Feel free to pick them both apart, I think clockwork has much better functionality, even though the UI kinda blows compared to amon ra. YMMV.
You shluld give RA.1.7 a try
Yea it's Me Again With The
Modified Hero
Wow, this is exactly what's been on my mind lately... I've been looking at the ClockworkMod thread in dev lol.
I just switched from Amon_RA 1.7 to CWM 3.0.2.4 last night. I decided that since I'm trying CM7 for the first time, I would also try a new recovery. Il Duce summed up the differences nicely. What I found comforting was that nandroid backups made in one recovery can be recovered in other recoveries, you just have to move your backups to the appropriate location on the SD card.
I think they're about equal. Amon_RA has a nice interface, and I much prefer the press Home to confirm instead of CWM's. With CWM, you could choose a "Format /system" or something and you are only presented with a "Yes - wipe" confirmation, which doesn't actually tell you what you're wiping. And like Il Duce said, that could easily wipe the sdcard instead of cache. But with CWM you can make your SD card less cluttered and put zips in different folders.
If you're not using Firerat's mod, there's no reason not to just try them all
If you are using Firerat's mod, it's just a bit more troublesome.
laie1472 said:
You shluld give RA.1.7 a try
Yea it's Me Again With The
Modified Hero
Click to expand...
Click to collapse
My phone doesn't handle anything that is OC, which makes me weary of 1.7 since I thought it was OC'ed.
Is it?
mtnchkn said:
My phone doesn't handle anything that is OC, which makes me weary of 1.7 since I thought it was OC'ed.
Is it?
Click to expand...
Click to collapse
darch-ra 1.7 is capped at 691.
mtnchkn said:
My phone doesn't handle anything that is OC, which makes me weary of 1.7 since I thought it was OC'ed.
Is it?
Click to expand...
Click to collapse
IIRC it is OC'ed to 768 MHz.
c00ller said:
IIRC it is OC'ed to 768 MHz.
Click to expand...
Click to collapse
no that's godspeed. 1.7 works fine on my phone, which dies over 729, which means 1.7 isn't 768, it's probably 691, but most def it's not higher than 729.
So what is a good download link for the image, since the only 1.7 I can find on the forums is the 'unofficial mirror of Darch 1.7' which gives me an error when I try flashing (says there is no image)?
il Duce said:
no that's godspeed. 1.7 works fine on my phone, which dies over 729, which means 1.7 isn't 768, it's probably 691, but most def it's not higher than 729.
Click to expand...
Click to collapse
mtnchkn said:
So what is a good download link for the image, since the only 1.7 I can find on the forums is the 'unofficial mirror of Darch 1.7' which gives me an error when I try flashing (says there is no image)?
Click to expand...
Click to collapse
my dropbox
http://dl.dropbox.com/u/5669105/darchra.img
il Duce said:
my dropbox
http://dl.dropbox.com/u/5669105/darchra.img
Click to expand...
Click to collapse
I really apprecaite the link but I get the same error as I did last time I was flashing a darch image
Code:
flash_image: not found
will try it again later with adb.
mtnchkn said:
I really apprecaite the link but I get the same error as I did last time I was flashing a darch image
Code:
flash_image: not found
will try it again later with adb.
Click to expand...
Click to collapse
I wonder if that means the command is "not found" or if it's saying the .img is not found. If it's the latter, make sure you put quotes around the file path if there are spaces, e.g,
flash_image recovery "C:\Android Folder\recovery.img"
If it's the first, then you're right, it should work in adb shell.
mtnchkn said:
I really apprecaite the link but I get the same error as I did last time I was flashing a darch image
Code:
flash_image: not found
will try it again later with adb.
Click to expand...
Click to collapse
Make sure the recover img. Is named.
recovery-heroc-RA-1.7.img
And make sure its not
img.img.
Sometimes the file is not named correctly. Also make sure the img. Is on the root of your sd/card and not in any folder. Good luck
Yea it's Me Again With The
Modified Hero
Turns out I was missing flash_image command. I am going to include the solution below for others, but bottom line, everything is fine now and am running 1.7. If someone has a download for CW 2.5.0.1 which someone mentioned, post it too. Also, here is 1.5 if anyone needs it
http://dl.dropbox.com/u/1759357/recovery-heroc-RA-1.5.zip
I came across this post, which pointed to a flash_image file here. So I copied that into my tools folder, then...
Code:
>cd C:\android-sdk-windows\tools
C:\android-sdk-windows\tools>adb devices
List of devices attached
HT041HF00432 device
C:\android-sdk-windows\tools>adb root
adbd is already running as root
C:\android-sdk-windows\tools>adb remount
remount succeeded
C:\android-sdk-windows\tools>adb push flash_image /system/bin
851 KB/s (26172 bytes in 0.030s)
C:\android-sdk-windows\tools>adb shell chmod 0755 /system/bin/flash_image
C:\android-sdk-windows\tools>adb shell flash_image recovery /sdcard/recovery-heroc-RA-1.7.img
C:\android-sdk-windows\tools>adb shell reboot recovery
So now I have a new recovery.
my phone is crazy. can't download anything using play store.
not enough memory. but at close look the phone will not mount cache partitaion.
anybody pls help. all roms the same
Anybody?
I get error code 498 in lgp 990 custom rom.
but in miui rom the android core process is forced closed
Error code 498 is related to cache partation.
but in miui is android core process that is forced closed all the time
There is no cache mounted on the phone.
And it doesnt metter which rom ja choose. it's all the same. some rom says it isn't enough memory.
Help please. i think it's got to do with cwm. it's just wrong. it's v 6.0.1.5 i think. there was never problem with 5.0.0.7
Formating cache will not create cache partation in cwm. please resolve problem
Try command:
mke2fs /dev/mmcblk0p2
from terminal emulator or adb shell and reboot your phone.
Check if your cache is mounted with command:
mount | grep cache
Worked for me.
Sent from my LG-P990 using xda app-developers app
asmerito said:
Try command:
mke2fs /dev/mmcblk0p2
from terminal emulator or adb shell and reboot your phone.
Check if your cache is mounted with command:
mount | grep cache
Worked for me.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
No such file and not working. i cecked cahce with link2sd and it's unreadeble as N/A
I'm not sure where is the problem but i think it got to do with cwm. that program has f my phone.
Even before some roms wouldnt work properly exept muiu or wuiu i dont know what rom is called.
But even now that rom wont work as before after installing djmango i am terible at spelling and knowing names.
but do get good analasys anyway.
i did install long ago new ics upgrade which was no difference in rom and maybe there was the problem (bootloader
) this is just a guess but my money is on cwm
problem solved. Cmw 5.0.2.0 working by downgrade
Hi,
I know this is a strange requset.
Because my Nexus 6 is stuck at Google logo and can't boot into system or TWRP.
This is begin at when I try to flash 5.11 OTA(TWRP flashable) file.
After install without error, I have stuck at Google logo.
Then I notice that my system is rooted, noforce encrypt and use F2FS filesystem.
I gusee that the problem is new kernel didn't support F2FS, so I flashed Zen kernel with fastboot.
This step let me can boot in to system normally, but I still can't get into TWRP.
Because I want to fix TWRP, so I tried fastboot erase cache.(This is big mistake.....I should backup all file before try this command)
After fastboot erase cache, I still can't get into TWRP, and I lose system again.(Stuck at boot Animation)
I think it is cause by "fastboot erase cache" didn't create F2FS filesystem cache partition.
Does someone can help me that give me a F2FS filesystem cache partition img file?
I just want to get into system and backup all file.
Then do a full factory reset, hope this can bring back my TWRP.
chowtom said:
Hi,
I know this is a strange requset.
Because my Nexus 6 is stuck at Google logo and can't boot into system or TWRP.
This is begin at when I try to flash 5.11 OTA(TWRP flashable) file.
After install without error, I have stuck at Google logo.
Then I notice that my system is rooted, noforce encrypt and use F2FS filesystem.
I gusee that the problem is new kernel didn't support F2FS, so I flashed Zen kernel with fastboot.
This step let me can boot in to system normally, but I still can't get into TWRP.
Because I want to fix TWRP, so I tried fastboot erase cache.(This is big mistake.....I should backup all file before try this command)
After fastboot erase cache, I still can't get into TWRP, and I lose system again.(Stuck at boot Animation)
I think it is cause by "fastboot erase cache" didn't create F2FS filesystem cache partition.
Does someone can help me that give me a F2FS filesystem cache partition img file?
I just want to get into system and backup all file.
Then do a full factory reset, hope this can bring back my TWRP.
Click to expand...
Click to collapse
do fastboot format cache then fastboot format userdata. Then TWRP should work.
Thanks for quick reply,
That is what I want to do.
But it will wipe all my data, so I want to get into system and backup data before do fastboot format userdata.
danarama said:
do fastboot format cache then fastboot format userdata. Then TWRP should work.
Click to expand...
Click to collapse
chowtom said:
Thanks for quick reply,
That is what I want to do.
But it will wipe all my data, so I want to get into system and backup data before do fastboot format userdata.
Click to expand...
Click to collapse
Oh I see.
Have you tried adb access whilst bootloop?
Failing that, another option would be edit the ramdisk to change the /cache mount to ext4. I imagine the kernel you have has set it as f2fs
I'll happily format my cache as f2fs and take a nandroid of it to create a cache image, but im not sure if that would be fastboot flashable?
danarama said:
Oh I see.
Have you tried adb access whilst bootloop?
Failing that, another option would be edit the ramdisk to change the /cache mount to ext4. I imagine the kernel you have has set it as f2fs
I'll happily format my cache as f2fs and take a nandroid of it to create a cache image, but im not sure if that would be fastboot flashable?
Click to expand...
Click to collapse
Try it and I can know is flashable or not.
I have tried adb access, adb can connect my device, but can't access sdcard,
Code:
/system/bin/sh: cd: /sdcard: No such file or directory
/system/bin/sh: cd: /storage/sdcard0: No such file or directory
chowtom said:
Try it and I can know is flashable or not.
I have tried adb access, adb can connect my device, but can't access sdcard,
Code:
/system/bin/sh: cd: /sdcard: No such file or directory
/system/bin/sh: cd: /storage/sdcard0: No such file or directory
Click to expand...
Click to collapse
You can try /data/media/0 for sdcard
Nandroid isnt in .img format.
I've just dd'd a cache.img and fastboot flashed that. Lets see if it boots. If it does, I'll format it and dd it again.
Edit > Well it booted (though it is optimising now)...
I'll try and format and dd the image for you, though not sure it will work. Do I need a special version of TWRP to format F2FS?
danarama said:
You can try /data/media/0 for sdcard
Nandroid isnt in .img format.
I've just dd'd a cache.img and fastboot flashed that. Lets see if it boots. If it does, I'll format it and dd it again.
Edit > Well it booted (though it is optimising now)...
I'll try and format and dd the image for you, though not sure it will work. Do I need a special version of TWRP to format F2FS?
Click to expand...
Click to collapse
https://twitter.com/dhacker29/status/568070387306766336
This one can format F2FS, but I am not sure TWRP will check kernel support F2FS or not.
And I can't access /data/media via adb.
Code:
[email protected]:/ $ cd data
cd data
[email protected]:/data $ cd media
cd media
/system/bin/sh: cd: /data/media: Permission denied
chowtom said:
https://twitter.com/dhacker29/status/568070387306766336
This one can format F2FS, but I am not sure TWRP will check kernel support F2FS or not.
And I can't access /data/media via adb.
Code:
[email protected]:/ $ cd data
cd data
[email protected]:/data $ cd media
cd media
/system/bin/sh: cd: /data/media: Permission denied
Click to expand...
Click to collapse
Yeah I found that one eventually and it let me format.
Now I just need to find somewhere to upload a 256MB image
danarama said:
Yeah I found that one eventually and it let me format.
Now I just need to find somewhere to upload a 256MB image
Click to expand...
Click to collapse
MEGA or Google driver?
chowtom said:
MEGA or Google driver?
Click to expand...
Click to collapse
Dev-host.
---------- Post added at 10:40 AM ---------- Previous post was at 10:17 AM ----------
Had to go Mega in the end
Here you go:
https://mega.co.nz/#!UoF0RIpA!ew9AYAqn-C2vxxO8VMjXnp1jOM8eD6JqXdsrEyJimGM
Not sure it will work though.
danarama said:
Dev-host.
---------- Post added at 10:40 AM ---------- Previous post was at 10:17 AM ----------
Had to go Mega in the end
Here you go:
https://mega.co.nz/#!UoF0RIpA!ew9AYAqn-C2vxxO8VMjXnp1jOM8eD6JqXdsrEyJimGM
Not sure it will work though.
Click to expand...
Click to collapse
It works!!!
Huge thanks for your help.
Now I can start to backup my data.:laugh:
chowtom said:
It works!!!
Huge thanks for your help.
Now I can start to backup my data.:laugh:
Click to expand...
Click to collapse
wow, that was surprisingly easy.
Well dd copies at block level, so it *should* have worked, but I've never really tested it before.
Finally, I recover my data and didn't lost any one.
The step what I do is:
1. Use fastboot to flash cache img which provided by danarama.
2. Reboot to test, result is System ok and TWRP still fail.
3. Boot to system and backup all data with MTP.
4. Use fastboot erase userdata to factory reset my Nexus 6.
5. After step 4, I can get into TWRP. Redo the Convert to F2FS procedure.
6. Reboot to system and skip all initial SETUP. Copy all sdcard data to nexus 6 by MTP.
7. Back to TWRP, restore the data partition(F2FS) which backup a weekago.
8. Reboot to test, both System and TWRP boot correctlly.