Develop Bugs

[Q] please help - did i brick my phone using exploid method

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

[Q] Unable to push files to sdcard after bootloop

I have been busy today with a nasty problem, i hope you anyone can help me out.
I was running JDROID's custom rom with great satisfaction, had it backupped. The trouble started when i downloaded an other rom and forgot to place the rom (.zip) on my sdcard before i flashed the boot.img via flashboot.
By that time i didnt knew how to use ADB commands, so i decided that i would forget about the new rom and i would restore my working backup. (im using CWM)
After restoring that backup a bootloop occured, so tried lots of things like wiping the cache. Also ive tried to restore the backup after lots of full wipes ect. Even installing JDROID's latest rom witch i had on my sdcard dindt help. Still had a bootloop.
I managed to use ADB when my phone was switched off, and i pushed a rom.zip to sdcard. But CWM cant seem to find it.
My question is this: in CWM there is an option to "mount USB storage". When i use it i get the message "unable to open ums lunfile". I have tried formatting the sdcard, whereby i deleted my backups still didnt work.
What whould you guys try next?

relock the bootloader and run an ruu appropriate to your cid

No files found after factory reset

I had a problem copying files from GN to PC. I though I could fix them formatting the sdcard.
So I've done a factory reset.
When it finished, at reboot the system (AOKP JB 3) was restored but the sd files were still there.
If I go to recovery to install some zip, it doesn find some folders and every file (I can see them mounting GN after boot).
CWR says "no flies found" when I try to open each folder.
What do you suggest?

Update: I tried updating to last CWM and .. same problem.
It looks like every folder is empty (but they aren't).

[Q] (Status 7 + sd-ext won't mount) Failed to install MIUI, Status 7 on other ROMS

I've been very frustrated lately, and I don't want to go and do something like unroot and clear my
phone without "professional" input. So thanks for your attention.
I have been running albinoman's Jellybean RC3 since it's release. It's been working well for me
but I wanted to try the new MIUI 2.11.9 for my Incredible.
I downloaded and tried installing it through ROM Manager; I wiped the data, cache, and dalvik cache.
It got to the part where it was installing MIUI, then:
Code:
Creating symlinks
symlink: some symlinks failed
E:Error in /somedirectory/blahblah/somezipfile.zip
(Status 7)
Installation aborted.
So I cursed it and restored my JB backup.
Then it said something like this in the final part of the restore:
Code:
Restoring sd-ext...
No sd-ext found. Skipping backup of sd-ext
sd-ext won't mount and isn't visible in cmrecovery. But oddly enough, all of my files can be found in Astro, under sdcard1.
When I booted up, I got the immediate messages that apps like Talk, Email,
and Exchange Services had stopped working. So I disabled them to stop the messages. Facebook wouldn't start, and
ANY app that deals with media fails to load, i.e. Instagram, Camera, Music, Gallery, etc.
(EDIT: Recently I got Google Play to download apps after Fixing Permissions in cmrecovery)
I tried the re-downloading and re-installation of MIUI, and even a fresh RC3, all in CMrecovery, w/ and w/out wipes.
I would've let the failed install go, but it's too frustrating not being able to access my media.
Please Help

Hypherism said:
I've been very frustrated lately, and I don't want to go and do something like unroot and clear my
phone without "professional" input. So thanks for your attention.
I have been running albinoman's Jellybean RC3 since it's release. It's been working well for me
but I wanted to try the new MIUI 2.11.9 for my Incredible.
I downloaded and tried installing it through ROM Manager; I wiped the data, cache, and dalvik cache.
It got to the part where it was installing MIUI, then:
Code:
Creating symlinks
symlink: some symlinks failed
E:Error in /somedirectory/blahblah/somezipfile.zip
(Status 7)
Installation aborted.
So I cursed it and restored my JB backup.
Then it said something like this in the final part of the restore:
Code:
Restoring sd-ext...
No sd-ext found. Skipping backup of sd-ext
sd-ext won't mount and isn't visible in cmrecovery. But oddly enough, all of my files can be found in Astro, under sdcard1.
When I booted up, I got the immediate messages that apps like Talk, Email,
and Exchange Services had stopped working. So I disabled them to stop the messages. Facebook wouldn't start, and
ANY app that deals with media fails to load, i.e. Instagram, Camera, Music, Gallery, etc.
(EDIT: Recently I got Google Play to download apps after Fixing Permissions in cmrecovery)
I tried the re-downloading and re-installation of MIUI, and even a fresh RC3, all in CMrecovery, w/ and w/out wipes.
I would've let the failed install go, but it's too frustrating not being able to access my media.
Please Help
Click to expand...
Click to collapse
Status 7 refers to an error in the rom zip file. Try redownloading it and flashing it again. If it still errors, go to the roms thread and see if others are having the same issue. I no one else has the issue, try flashing TWRP recovery and then flashing the rom with it. Seems some newer roms work better with twrp than with cwm.
The sd-ext thing is normal. You will only have an sd-ext if you specificaly partitioned your sdcard to have one. If you dont have one, cwm will still check and report its backup status, ie "backing up/restoring sd-ext, no sd-ext found, skipping backup/restore of sd-ext".
So are you saying you cant flash any rom or restore a backup without having fc's and app issues?

cmlusco said:
Status 7 refers to an error in the rom zip file. Try redownloading it and flashing it again. If it still errors, go to the roms thread and see if others are having the same issue. I no one else has the issue, try flashing TWRP recovery and then flashing the rom with it. Seems some newer roms work better with twrp than with cwm.
The sd-ext thing is normal. You will only have an sd-ext if you specificaly partitioned your sdcard to have one. If you dont have one, cwm will still check and report its backup status, ie "backing up/restoring sd-ext, no sd-ext found, skipping backup/restore of sd-ext".
So are you saying you cant flash any rom or restore a backup without having fc's and app issues?
Click to expand...
Click to collapse
Thanks cmlusco, for posting.
I just downloaded a fresh .zip of miui for inc off their site, then transferred and installed it all while in TWRP recovery. I got the same Status 7
error, and had to restore my my newest JB backup.
Yes. I can't install new roms, even a fresh jellybean rc3. When I restore, it works, but I still have app issues, and I frequently recieve this error:
"Unfortunately, the process android.process.media has stopped"

Hypherism said:
Thanks cmlusco, for posting.
I just downloaded a fresh .zip of miui for inc off their site, then transferred and installed it all while in TWRP recovery. I got the same Status 7
error, and had to restore my my newest JB backup.
Yes. I can't install new roms, even a fresh jellybean rc3. When I restore, it works, but I still have app issues, and I frequently recieve this error:
"Unfortunately, the process android.process.media has stopped"
Click to expand...
Click to collapse
It must be an error in the rom file then, probably in the updater script. If you shoot me a link i will download it and see if i can get it to work.
Try formating everything in the mounts and storage menu except emmc and sdcard, and then do your restore. Sometimes wiping just data and cache arent enough.

I tried flashing it, and also got status 7. Gonna take a look and see if i can fix it.

cmlusco said:
It must be an error in the rom file then, probably in the updater script. If you shoot me a link i will download it and see if i can get it to work.
Try formating everything in the mounts and storage menu except emmc and sdcard, and then do your restore. Sometimes wiping just data and cache arent enough.
Click to expand...
Click to collapse
Yeah. Formatted everything in the wipe menu of TWRP except sd and emmc. Tried and failed to install the ROM with the same error.
Restored. Then re-installed cmrecovery to check by formatting in it's mounts and storage menu, but I got the same result.
Let me know how your install goes. I have a bad feeling it isn't the rom file.

Hypherism said:
Yeah. Formatted everything in the wipe menu of TWRP except sd and emmc. Tried and failed to install the ROM with the same error.
Restored. Then re-installed cmrecovery to check by formatting in it's mounts and storage menu, but I got the same result.
Let me know how your install goes. I have a bad feeling it isn't the rom file.
Click to expand...
Click to collapse
After messing with this for a few hrs im sad to say i give up. It has multipul errors, every time i fix one a new one pops up. The updater-script had numerous errors and the system folder is missing a bunch of files.

cmlusco said:
After messing with this for a few hrs im sad to say i give up. It has multipul errors, every time i fix one a new one pops up. The updater-script had numerous errors and the system folder is missing a bunch of files.
Click to expand...
Click to collapse
Thanks for spending time to assist me regardless. I'll figure something out. Though I'm open to anyone else that might some insight or
information regarding this issue.
It's beyond frustrating to me.

Well, fixed all my problems. I just installed Tiny's cm 10. Everything seems golden. Camera's working, gallery's available.:good:
Thanks for narrowing the problem down to the ROM, I know you put some time into that.
Resolved,
Hypherism

[Q] Need HELP

Hi,
I am running Carbon Mod Nightly Rom, I was looking at the Volume Blaster Mod (http://forum.xda-developers.com/showthread.php?t=2563209) to raise the volume up on the external speaker. I edited the file system/etc/snd_soc_msm/snd_soc_msm_2x. Somehow I screwed the file up after editing. After I edited it and rebooted, it gets stuck at the Carbon Logo and doesn't go any further :crying:. I have a nandroid backup, but I didnt backup until after I edited the file (before reboot). So I'm wondering can I or how do I replace the edited file (snd_soc_msm_2x) with the original file. I have the original file on the SD card in the phone. I went into the TWRP Recovery and into file manager, but I could not locate the location of the edited file from within there (system/etc/snd_soc_msm/snd_soc_msm_2x). Can someone please help me restore this one file so that my phone will boot up or tell me how would be the best way of getting my phone up and working again ASAP. Oh, I have tried exploring the backup created with Nandroid Backup Manager, well I found the file thats corrupted and opened it with File manager, select all- then delete, then pasted the contents from the working file, and then try to save, and I get an error "Operation Failed". So any help would be greatly appreciated.!!
Thanks in Advance

If you cant see files in /system, you just need to mount it first. Otherwise, just dirty flash the same rom.

DocHoliday77 said:
If you cant see files in /system, you just need to mount it first. Otherwise, just dirty flash the same rom.
Click to expand...
Click to collapse
Dirty Flash? I'm new to all this, so I need some help with the slang. I can explore the contents of the Nandroid backup, are there anyway possible to delete a file in the Nandroid backup and replace it with another file?? If I can do that, then I can replace the corrupted file and then restore from backup. I just dont want to reflash the clean ROM and then have to manually restore all my apps, sms and photos...
If I flash the backup Rom that has the corruted file, and before reboot, can I use the file manager to pull the clean file from the external card and replace the one that corrupted in the root folder. If I can do this, then it should boot normally. Otherwise if I boot with the corrupted file it gets hung after it processes all the apps. (Gets hung on Starting Apps).

I figured it out!!! What I did was I went into recovery, and selected the recovery nandroid backup file that was corrupted. Instead of restoring all the available options, I unchecked System. So it restored everything but the system data. The system data already installed was from the newly installed rom that was working, so by leaving the system unchecked it didnt install the corrupted system from backup! I hope I explained this where you can understand it.
Thanks for all the help DocHoliday77!! I'm just glad that worked and I dont have to manually install everything back over!!
:victory: