Related
I followed the “how to root the HTC My touch slide (exploid method) (updated 01.26.11)” to the letter. (theunlokr.com)
Everything worked well until I got into clockworkmod Recovery
I then wipe data/factory reset in recovery mode
Then I installed zip from sd card ( I select slidemeroot2.zip)
After going through the process I get an “installation aborted” message
E: Failure at line 64 symlink busybox SYSTEM:xbin/zcip
(something to that effect. I'm out of town til tomorrow to verify the exact error)
Im very frustrated and afraid I may have bricked the phone
I had to turn the phone off and am scared of turning it back on until I have a fix
Please help
can you get into clockwork recovery???yes you tried to flash the wrong file
xoombie503 said:
can you get into clockwork recovery???yes you tried to flash the wrong file
Click to expand...
Click to collapse
Yeah i believe so.
After removing the battery last night i was able to get back into recovery i think
Will double check tomorrow when i get back home
What do you have in mind and how do i know the correct file to flash?
I'm just scared because it said during the method a few steps earlier: DO NOT REBOOT
I hope that i had past the stage where by rebooting it wont kill the phone
get a rom her http://forum.xda-developers.com/showthread.php?t=924793 preferably the stock spresso 2.2 froyo update and flash trough recovery by choosing zip from sd card...formatting cache/wipe dat factory reset before hand/ and dalvik cache etc.see if it works
xoombie503 said:
get a rom her http://forum.xda-developers.com/showthread.php?t=924793 preferably the stock spresso 2.2 froyo update and flash trough recovery by choosing zip from sd card...formatting cache/wipe dat factory reset before hand/ and dalvik cache etc.see if it works
Click to expand...
Click to collapse
Thnks so much will do that first thing when i get back in town tomorrow..
By the way this is with the assumption that by plugging my phone onto my computer via usb it will recognize my phone as a drive correct??
o btw im a newby at this, so that i understand correctly, i need to once in recovery cache wipe, then data factory reset before flashing the new room i would download. What is Dalvik cache etc..... is that another option i will see once in recovery?
xoombie503 said:
get a rom her http://forum.xda-developers.com/showthread.php?t=924793 preferably the stock spresso 2.2 froyo update and flash trough recovery by choosing zip from sd card...formatting cache/wipe dat factory reset before hand/ and dalvik cache etc.see if it works
Click to expand...
Click to collapse
i tried it but no luck....
i did the wipe data/factory reset, i did wipe cache partition, then install zip from sd card, then choose zip from sd card, then picked haxspresso.zip i downloaded, then it says deleting files, then copying files, then i get E: can't symlink /system/xbin/su
E:failure at line 73: symlink /system/bin/su SYSTEM:xbin/su
installation aborted
Please help... im going crazy..
This is only my second rooting
pvalery00 said:
i tried it but no luck....
i did the wipe data/factory reset, i did wipe cache partition, then install zip from sd card, then choose zip from sd card, then picked haxspresso.zip i downloaded, then it says deleting files, then copying files, then i get E: can't symlink /system/xbin/su
E:failure at line 73: symlink /system/bin/su SYSTEM:xbin/su
installation aborted
Please help... im going crazy..
This is only my second rooting
Click to expand...
Click to collapse
thats the kinda of stuff i saw when i had custom mtd partitions set up. that stuff happens as a result of not enough memory to write to. try flashing a custom cyanogenmod rom like cm6. they are almost half the size of any rom based off of stock
guitarist5122 said:
thats the kinda of stuff i saw when i had custom mtd partitions set up. that stuff happens as a result of not enough memory to write to. try flashing a custom cyanogenmod rom like cm6. they are almost half the size of any rom based off of stock
Click to expand...
Click to collapse
interresting because the first part of this message is
"no app2sd partition found. Skipping format of /sd-ext.
data wipe complete"
I wonder if this has anything to do with it...
Please let me know
guitarist5122 said:
thats the kinda of stuff i saw when i had custom mtd partitions set up. that stuff happens as a result of not enough memory to write to. try flashing a custom cyanogenmod rom like cm6. they are almost half the size of any rom based off of stock
Click to expand...
Click to collapse
you were so right!!!
i downloaded cmGinger 1.0_signed and flashed it and it worked
so what does this mean mtd partitions set up. Does this mean i can not get anyother rom or even the stock rom back in this fone??? how did u address it?
pvalery00 said:
you were so right!!!
i downloaded cmGinger 1.0_signed and flashed it and it worked
so what does this mean mtd partitions set up. Does this mean i can not get anyother rom or even the stock rom back in this fone??? how did u address it?
Click to expand...
Click to collapse
There is a thread in the dev section on how to setup custom mtd partitions. Basically you just assign memory where you want it. If you want stock roms you should assign the normal mtd setup (given in mtd partitions thread). Oh, you'll need s-off though. There is a guide for that too in the dev section. Its actually sticked at the top. Glad i could help
Sent from my T-Mobile myTouch 3G Slide using XDA App
Hey guys, got a strange problem here. I'm running MIUI-XJ 2.3.30 A2SD.
Had 8 apps to update via Google Play and 31mb internal left (over 600mb on sd-ext, too). In the middle of updating the apps I've got a Google Play crash followed by few other fc's, phone said my internal memory is too low to operate and such - so I tried the most obvious fix, which is of course rebooting the phone.
That was a mistake, apparently. Phone will not boot anymore - goes through the bootscreen and gets stuck on the yellow MIUI splash. It's not a bootloop, the phone just freezes and the only thing I can do is battery removal. Tried booting it up with no sd card as well, nothing seems to help though.
Is there anything I can do except full wipe via recovery? I had some important sms and spent quite a bit of time customizing the desktop, I'm not to keen on doing that again.
Is it possible to delete some apps via adb or something like that? Or is there a point in trying to install the rom again on top of my system?
Thanks in advance, help really appreciated!
Try clearing dalvik cache and cache from recovery and then boot. Thereafter clear some space or change your a2sd scheme.
Thanks for the answer! Makes me feel silly I did not think of that myself lol, sounds like an obvious solution.
Problem is, it still does not seem to help though - wiped /cache and dalvik-cache on data, sd-ext and system - still nothing, same problem persists. Stuck at MIUI bootanimation.
Any other ideas? I'm really kind of desperate to recover the data.
- Take a nandroid backup first. So you can start over if need be.
Some things to try
- Only flash ROM and see if it helps.
- Wipe data. Flash ROM fresh. Install Titanium Backup. With TB locate nandroid on sdcard and try to extract your data. Maybe restoring the launcher and messaging will do the trick. Not sure . Try. You can always start over.
- Fix permissions in recovery
There's an app called AROMA Filemanager that can be started from recovery and allows you to modify all phone partitions, all you need is to mount them before starting the app. Here it is:
http://forum.xda-developers.com/showthread.php?p=25911276
Tried flashing the ROM again on top of my system - no effect whatsoever, still gets stuck at bootanimation. Also, tried the permission fix as well as the RMD recovery "apk uid mismatches" fix. Still nothing.
Going to give the AROMA a try, having some problems right now though - using RMD recovery, no touch support. Trying to flash 4ext touch from fastboot somehow!
Thank you. Will keep you updated.
UPDATE//
Managed to get the AROMA up and running, deleted few apps from /data/apps, nothing to delete from /system really. /cache is cleared, so are all 3 dalvik-cache folders.
System still does not want to start.
Any ideas what might have happened? Seems like I'm running out of options and will have to do a clear install, after all.
You probably damaged some important system files so tho phone can't load system. The best solution is to restore some nand backup if you have, or to do a full wipe and start from scratch.
Sent from my HTC Desire using Flashes and Thunders
If that was the case, reflashing the ROM on top of my current system should fix the problem, while it didn't - right? Also, I find it hard to believe that "important system files" could have been damaged during routine Google Play apps update...
Than a full wipe and fresh install is inevitable...
Sent from my HTC Desire using Flashes and Thunders
Hi guys,
Newbie to the forum and android just need a bit of help as im pretty stuck at the moment and i dont know whats gone wrong.
I wanted to install Jelly Bread v5.0 or something other that the restricted phone carrier os on my phone when i got it (i wont mention just incase) so heres what i did.
rooted the phone using an update.zip from on this forum somewhere.
installed: signed_cwm-5.0.2.7-flashablezip-ext4only.zip
then installed: Jelly Bread v5.0
was ok for a while and working but then i wanted to play with other ROMS (in this case i now wanted to try cm-10.1.4-GT-S5660-gio++.zip)
I enter recovery, wipe data/factory reset, wipe cache, wipe dalvik cache, wipe batt stats
Then install cm-10.1.4-GT-S5660-gio++.zip
Then it hung for 35mins at loading blue circle screen.
I then took battery out and enter recovery, and attempt to wipe data/fatory reset and it says:
--Wiping data...
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/block/stl13
Formatting /Cache...
Formatting /sd-ext...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p2
Formatting /sdcard/ .android secure...
Data wipe complete
Also i cant wipe dalvik cache it just does nothing blinks 1 second then back to menu.
From here (silly me i forgot to backup) ive tried to flash a few stock roms but still getting boot loops and the same above errors.
Is there any way i can format and write /data and /sd-ext?
Anyone know what i can do to fix this please?
Thanks for any help in advance.
update
Hi guys,
Just an update.. have tried several stock ROMS via ODIN always flashing CWM and flashing custom ROMS but nothing with flash and reformat the /dev/stl13 block. im always getting this error and i believe its causing my boot loop issues.
I found this thread via google:
forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/
is there anybody on here that could guide me through using ADB shell to rebuild/reformat the /dev/stl13 block?
I dont feel confident enough to do it. (Have already installed shell on my laptop though)
This is driving me crazy trying to fix. My first android ROM flash gone wrong
(i got it working fine with Jellybread but wanted to try something else)
Any help appreciated.
Cheers
Richie
Got your PM, but this sort of discussion is best kept in public.
Be careful with that HTC-related thread, it's a different device, with a different set of tools and likely a different partitioning method.
Back to basics: have you tried flashing back to stock with Odin and formatting your /data and /cache partitions with the Samsung stock recovery?
AFAIK CWM5 is for Gingerbread (2.3.x). For anything above (CM10.1 is Jelly Bean 4.2.2), you need CWM6.
http://forum.xda-developers.com/showthread.php?t=1894456
Darkshado said:
Got your PM, but this sort of discussion is best kept in public.
Be careful with that HTC-related thread, it's a different device, with a different set of tools and likely a different partitioning method.
Back to basics: have you tried flashing back to stock with Odin and formatting your /data and /cache partitions with the Samsung stock recovery?
Click to expand...
Click to collapse
Hey dude,
Thanks for the reply.
I have tried flashing back to stock (latest from samfirmware) and it still wont let me mount data.
Although its giving me my orignial load screen (my carrier) but still boot loops.
Ive tried look for another stock ROM i can use but alot of the links are down/broke or withdrawn etc.
I note with stock recovery i just can't mount data but after i install CWM 5.0.2.7 ext4 only it cannot format ext to block stl13.
Could this possibly mean that my internal memory has failed or it just needs to be repartitioned?
Will continue to look for another stock rom that can hopefully fix the problem.
You don't care about the errors failing to mount in the stock recovery. It's expected since it isn't set to work with an ext4 partition.
Just run the format operations from the stock recovery.
Most "stock" ROMs released here were made to run on ext4 since performance was that much better and most CWMs built also run ext4, unless explicitly stated to run RFS.
I can't think of any tools to repartition the Gio, otherwise we would have been all over it back in the day to solve the /system space shortage.
Harakhti said:
AFAIK CWM5 is for Gingerbread (2.3.x). For anything above (CM10.1 is Jelly Bean 4.2.2), you need CWM6.
http://forum.xda-developers.com/showthread.php?t=1894456
Click to expand...
Click to collapse
Do you suggest to flash stock via Odin?
And then correct me if im wrong but to get to CM10,1 i go in this order after a stock flash:
1. Install CWM 6.0.3.2
2. run ext formatter
3. install ROM (in this case CM10.1??
Cheers for any help in advance.
Im quite new to Android.. but not new to flashing etc (BIOS, PSP's other devices etc) but this is my first android phone and i didnt like the Phone Carrier custom ROM and network lock. So attempted to try something else. Got Jellybread running fine but decided to have a look around. And now im phone less (well not really using my old nokia n97) but it is sooo painful! lol
I don't think my initial reply could have been much clearer. If you've been flashing these so called "stock" ROMs with CWM, they weren't entirely, completely stock.
1 - Flash original, unmodified Samsung ROM with Odin.
2 - Boot to recovery
3 - Clear user data (or however they named the format operations, I forget)
4 - Reboot
Only if those steps did not work then do we have to start poking around more.
Sent from my SGH-T889V using xda app-developers app
Darkshado said:
I don't think my initial reply could have been much clearer. If you've been flashing these so called "stock" ROMs with CWM, they weren't entirely, completely stock.
1 - Flash original, unmodified Samsung ROM with Odin.
2 - Boot to recovery
3 - Clear user data (or however they named the format operations, I forget)
4 - Reboot
Only if those steps did not work then do we have to start poking around more.
Sent from my SGH-T889V using xda app-developers app
Click to expand...
Click to collapse
Sorry man i had not read your reply before my previous post.
As stated in my previous post, I have flashed 2 stock ROM's from samfirmware via Odin and it passes.
On one of the ROMS (an NZ ROM) it gives me the error: E:format_Volume: rfs format failed on /dev/stl13
On the other ROM (The Aus ROM) it gives me the error: Unable to mount /data
On both im getting boot loop.
If the stock recovery refuses to format the /data and /cache partitions, I'm afraid you'll have to consider warranty service.
Otherwise, try dd'ing the RFS images I've already posted into place, but I'm not sure that this'll work.
Darkshado said:
If the stock recovery refuses to format the /data and /cache partitions, I'm afraid you'll have to consider warranty service.
Otherwise, try dd'ing the RFS images I've already posted into place, but I'm not sure that this'll work.
Click to expand...
Click to collapse
It formats the /cache partitions just not the /data as it cant mount it.
Warranty service? I will have to pay? as i have bought the phone 2nd hand and i dont think its under warranty.
I did see the other post and have downloaded "Samsung GT-S5660M Galaxy Gio - RFS format data and cache partition images to dd back into place"
But i cannot find the post again with the directions. Also when pushing these images from the SD card am i meant to be in stock recovery or RFS CWM?
Cheers Darkshado for all the help so far.
I had the explanation right below that download link here and a more detailed one here.
hmm doesn't look good eh?
Darkshado said:
I had the explanation right below that download link here and a more detailed one here.
Click to expand...
Click to collapse
Could it possibly be a physical hardware failure?
Could be, or some unusual partition table corruption. Problem is, I'm not even sure how the partition table is defined on the phone or if we can alter it...
Try the df command, it should give a listing of partitions on the phone.
Also try ls -l /dev/block/ to list all block devices and see what's there.
Maybe, just maybe parted as well? But by this point your odds aren't in your favor.
Good luck,
Darkshado
you can install a rom after downloading and flashing ext4 formatter.zip
Darkshado said:
Could be, or some unusual partition table corruption. Problem is, I'm not even sure how the partition table is defined on the phone or if we can alter it...
Try the df command, it should give a listing of partitions on the phone.
Also try ls -l /dev/block/ to list all block devices and see what's there.
Maybe, just maybe parted as well? But by this point your odds aren't in your favor.
Good luck,
Darkshado
Click to expand...
Click to collapse
Have been extremely busy with other projects and work lately and haven't had net the past week (so painful!)
but otherwise latest results are attached. Can you make anything of it? Does this look normal?
Cheers again.
Richie
Looks normal at first glance, though I don't have a Gio to compare with.
You could try and dig into how these phones are partitioned exactly and go from there, but you'll probably be on your own since most people who were interested in early MSM7227 devices have moved on.
Unless the underlying memory is defective, it's possible your only option left at this point is to try a JTAG repair.
However, depending on how much you'd be charged for such an operation locally, and taking into consideration the value of your typical used Gio (I've seen them go for 50$CAD in local classifieds)... You're probably better off cutting your losses and getting another phone.
Good luck,
Darkshado
Sent from my SGH-T889V using xda app-developers app
This is regarding a recently bought tablet Note 8. The current usage of /system partition is at above 75%. I have been trying to wipe/delete all system data in an attempt to have a 'fresh' OS once I install new stock ROM. In CWM recovery, I have even tried to format system partition (in addition to normal data reset, cache wipe and delvek cache wipe).
I installed the new stock ROM 4.4.2 in Download mode. Afterwards I checked and my system partition was still above 75% full. I do understand that system partition is normally read only. I am trying to work out if there is there any way where I can flash the stock ROM whilst completely removing the current system files.
Please offer any guidance or advice regarding this matter. Thanks!
Possible? Yes. Necessary? No.
The installation script for a ROM will almost always format the system partition before setting it up with the new ROM files, unless the developer is doing some special testing and you would know if that is the case.
ramjet73
Yes I think most custom ROMs would wipe system partition too. Though I want to install the stock ROM of Android 4.4.2. I have flashed the ROM about four times now, everytime trying different settings such as wipe/format system drive.
But I always end up with /system drive same size as before.
Thanks for the reply ramjet73.
S2 user said:
Yes I think most custom ROMs would wipe system partition too. Though I want to install the stock ROM of Android 4.4.2. I have flashed the ROM about four times now, everytime trying different settings such as wipe/format system drive.
But I always end up with /system drive same size as before.
Thanks for the reply ramjet73.
Click to expand...
Click to collapse
Depending on how you flash the stock ROM, Odin will flash a .img file to the system partition and completely replace its contents or an updater-script in a stock ROM zip file will format it and then copy all the included /system files to the empty partition.
In either case you cannot control what goes into the initial configuration of the system partition, only delete things that you don't need after it is flashed, unless you flash from a stock ROM zip file and delete items from that before you flash it.
There are scripting tools that can help with ROM "slimming" but I don't know if any are available for the Note 8.0 or not.
ramjet73
Hi,
my G3 and me have a small problem.
I wanted to update from official Cyanogenmod 12.1 to 13.0, backed up my data, etc.
First, there were tno Problems, but very fast battery drainage, and that my mSD card was now not "sdcard1" anymore but some numbers.
I tried fixing permissions in TWRP, had a bootloop. Updated TWRP (now 3.0.0 installed) and it worked somehow.
After one night it said process.acore quit unexpectedly. I had some crashes of the Google Play Services as well.
Then, it would boot, give me like 10 Seconds, and then jump to the boot screen of Cyanogenmod.
I tried to wipe data,system,dalvik. First there were problems with wiping dalvik, then there were problems with wiping system.
It says can't mount system: invalid argument. When looking around with twrp file explorer, the system folder is empty.
I would really appreciate your help!
You must check the partition type. Check if this as Ext4 or f2fs. In any case, try to repair the system of partitions from TWRP.
Okay, so:
Filesystem of /system is ext4
When trying to fix:
Repairing System using ef2fsck....
/sbin/e2fsck -fp /dev/block/mmcblk0p40 process ended with ERROR: 8
Unable to repair file system.
I assume it's because its ext4 and not f2fs?
btw I found something that may be important: when I try to wipe /cache, it takes forever.
Codagon said:
Okay, so:
Filesystem of /system is ext4
When trying to fix:
Repairing System using ef2fsck....
/sbin/e2fsck -fp /dev/block/mmcblk0p40 process ended with ERROR: 8
Unable to repair file system.
I assume it's because its ext4 and not f2fs?
btw I found something that may be important: when I try to wipe /cache, it takes forever.
Click to expand...
Click to collapse
Try to reinstall cyanogedmon 12.1 without wipes. Then, you enter again to the recovery and apply the wipes. I am not sure if for our model, cyanogedmon is compatible with the type of partitions f2fs and if is required a kernel with support for f2fs file system. You could try to changing the partitions (file system to f2fs), installing the rom and see if it starts but could cause a boot loop. Make a nandroid before making any changes.
cesarandres_8911 said:
Try to reinstall cyanogedmon 12.1 without wipes. Then, you enter again to the recovery and apply the wipes. I am not sure if for our model, cyanogedmon is compatible with the type of partitions f2fs and if is required a kernel with support for f2fs file system. You could try to changing the partitions (file system to f2fs), installing the rom and see if it starts but could cause a boot loop. Make a nandroid before making any changes.
Click to expand...
Click to collapse
Okay, i will try this tomorrow and then report back!
Thank you so far
Okay,
when trying to install the latest Snapshot of official CM, it just says ZIP File is corrupt. It said the same about an older build I still had on my PC.
When I try to flash the CM 13.0 build i had previously, TWRP just goes black and reboots (into recovery).
I also have to manually mount /system every time. If I try to mount /system again after dismounting it, it says 'failed to mount /system : Invalid Argument' .
This applies to all other partitions but the external SD Card.
When I try to change the file system to f2fs, it says OPeration successfull, but it didn't change anything, and the file system keeps being displayed as ext4.
Furthermore, i can't just 'Reboot Recovery' with TWRP- I have to take ot the Battery every time.
Codagon said:
Okay,
when trying to install the latest Snapshot of official CM, it just says ZIP File is corrupt. It said the same about an older build I still had on my PC.
When I try to flash the CM 13.0 build i had previously, TWRP just goes black and reboots (into recovery).
I also have to manually mount /system every time. If I try to mount /system again after dismounting it, it says 'failed to mount /system : Invalid Argument' .
This applies to all other partitions but the external SD Card.
When I try to change the file system to f2fs, it says OPeration successfull, but it didn't change anything, and the file system keeps being displayed as ext4.
Furthermore, i can't just 'Reboot Recovery' with TWRP- I have to take ot the Battery every time.
Click to expand...
Click to collapse
Why dont you start from the beginning.flash lp kdz through lg up then try installing cm 13.it might work for you.
jokerpappu said:
Why dont you start from the beginning.flash lp kdz through lg up then try installing cm 13.it might work for you.
Click to expand...
Click to collapse
I didn't want to lose my files
But it seems this is the only way soon- TWRP is giving me Error 7 when trying to flash CM 13.0. ....
:crying:
Codagon said:
I didn't want to lose my files
But it seems this is the only way soon- TWRP is giving me Error 7 when trying to flash CM 13.0. ....
:crying:
Click to expand...
Click to collapse
Which is your recovery version? If your recovery version is 3.0, you could try performing a downgrade of your recovery. If the errors persist, make an clean installation of the rom from LG Flash Tool (KDZ).
cesarandres_8911 said:
Which is your recovery version? If your recovery version is 3.0, you could try performing a downgrade of your recovery. If the errors persist, make an clean installation of the rom from LG Flash Tool (KDZ).
Click to expand...
Click to collapse
My Version is indeed 3.0. I had 2.8 before. Should I downgrade even further?
What would you recommend?
Besides:
I tried saving my files with the Terminal and [cp * /data/data/media/ /external_sd/Backup -r] and others, but it keeps giving me Zero-Byte Files.
Is this due to the Recovery version too?
You guys really are a big help! Thanks!
Codagon said:
My Version is indeed 3.0. I had 2.8 before. Should I downgrade even further?
What would you recommend?
Besides:
I tried saving my files with the Terminal and [cp * /data/data/media/ /external_sd/Backup -r] and others, but it keeps giving me Zero-Byte Files.
Is this due to the Recovery version too?
You guys really are a big help! Thanks!
Click to expand...
Click to collapse
I think that you try to save an empty folder. Use any backup applications to accomplish this. I have installed recovery twrp version 3 and I have no problem.
cesarandres_8911 said:
I think that you try to save an empty folder. Use any backup applications to accomplish this. I have installed recovery twrp version 3 and I have no problem.
Click to expand...
Click to collapse
Ok but doing it woth cp * /sdcard/WhatsApp it keeps doing the same.
The only thing that matters to me now are my WhatsApp Images
I was able to grab the chatlogs but not more.
Sometimes it even copies all pictures (Like 8.000 files) but all of them are 0-Bytes.
I will try the downgrade tomorrow.
Thank you so far!
Were you able to resolve this? I have an identical issue. I was playing CoC on my LS990 with CM13 before it went black and now it always boots in to twrp recovery 3.0. The only thing that mounts is the external sd card.
I've tried the following and all fail:
adb push cm13 and then install from recovery
adb sideload cm13
lg flash tool via firmware upgrade, roms:ZV4, ZV6, ZV8
Is the internal sd damaged? Please help XDA gods. Thanks