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] Error When Trying to Flash new Rom

I have Full Root to my phone and am trying to flash new roms. I have tried Rom Manager App and Recovery Boot Process and neither works. I get an error than zip file is bad. I have android Version 2.2
Software #3.70.651.1
When I use ROM Manager and Flash Clockwork Mod, It's says HTC Evo (CDMA). Does the CDMA version stop me from flashing Mods?
PLEASE HELP...

Don't use Rom Manager to flash. If you've tried flashing manually through recovery and you still get errors, try Amon Ra. You can flash it through Rom Manager. Go into Amon Ra, go ahead and do a nandroid backup as backups made with ClockworkMod won't work with Ra, then wipe and flash.
Also, what is the exact error you're getting? And no, CDMA has nothing to do with it.
(from... Evo/MIUI/Tapatalk)

I did a ROM Backup on ROM Manager. How do I do a Nandroid Backup? and How do I use Amon Ra? Sorry for being totally ignorant to these facts, but I am a complete newbie at this.

The new clockword can't flash certain roms because the scripting has changed. The best way to do it is going to be this way. Open up rom manager, scroll down to the bottom where it says "flash alternate recovery" then click the flash button for amon ra 2.3.. After the has completed reboot into recovery. (turn phone off then hold power and volume down, then select recovery) that will take you to amons recovery. Go to to the backup/restore menu (using the volume keys to navigate, and power button to press "enter" then click then perform a nandroid backup. I would select everything but android secure and sd-card ext. (they take up tons of space) then you will have succesfuly performed a backup of your current setup. I would get used to doing all your flashing through recovery, its much more stable. (recovery is the menu u were just in to perform the backup) Put the zip file of your rom you want to flash on the root of your sd card (not in a folder) Go back into recovery, enter the wipe menu, at least wipe data/factory reset, cache, and dalvik cache. Then go to install zip from sd card, select your rom zip, and click flash, it will then flash the rom for you. hope this helps

corey140 said:
I did a ROM Backup on ROM Manager. How do I do a Nandroid Backup? and How do I use Amon Ra? Sorry for being totally ignorant to these facts, but I am a complete newbie at this.
Click to expand...
Click to collapse
Before starting, try to have at least 50% battery and have the rom on the root of your SD card - not in any folders.
The backup you did in Rom Manager is the same as a nandroid backup. If you've already "flashed alternate recovery" in Rom Manager, then power the phone down. Hold down the volume down button and power button at the same time until the phone turns on to a white screen with skating Androids. This is the bootloader/hboot. Check the top and make sure it says ship s-off at the top (if it says s-on then you aren't fully rooted). Assuming you're s-off, use the volume buttons to move up/down the menu. Highlight the option that says "recovery", then press the power button to choose it. Your phone will show the white HTC Evo screen then boot to recovery. From there (using the volume and power buttons like you did before), choose backup/restore, then nandroid backup. Leave the first three options checked then do your backup. When that finishes, go ahead and backup your wimax. Go to the nandroid backup screen, uncheck the first three options with the power button, then check only wimax. Do the backup again. Then go to the wipe menu. Wipe everything in the list except the SD card. When that's finished, go back, then install zip from SD card. Choose zip from SD card, then use the volume up button to go all the way to the bottom. Highlight the rom you want to flash and press the power button. Confirm with the power button, then let it flash. Then reboot.
(from... Evo/MIUI/Tapatalk)

I really appreciate the help plainjane & jeffm922? Two last questions, hopefully. I am trying this just after rooting my phone about a week ago. I keep seeing things about radios and wimax and kernels, and gingerbread, and other stuff I never heard of...LOL. 1st Question, do I need to download a certain type of radio or wimax or kernels for certain roms??? and 2nd Question, with me only having Version 2.2,which I gues is Froyo, do I only have the capabilities to download Roms for Froyo or doest that change depending on what Rom I install? SORRY AGAIN FOR MY IGNORANCE ON THE MATTER, BUT I'll NEVER KNOW UNLESS I ASK.
THANKS In ADVANCE

corey140 said:
I really appreciate the help plainjane & jeffm922? Two last questions, hopefully. I am trying this just after rooting my phone about a week ago. I keep seeing things about radios and wimax and kernels, and gingerbread, and other stuff I never heard of...LOL. 1st Question, do I need to download a certain type of radio or wimax or kernels for certain roms??? and 2nd Question, with me only having Version 2.2,which I gues is Froyo, do I only have the capabilities to download Roms for Froyo or doest that change depending on what Rom I install? SORRY AGAIN FOR MY IGNORANCE ON THE MATTER, BUT I'll NEVER KNOW UNLESS I ASK.
THANKS In ADVANCE
Click to expand...
Click to collapse
Certain roms do require the latest radios, etc. If it does, there will be info in the directions for the rom (usually in the first couple posts). If you do need to flash a radio update, when you reboot from recovery you will see a black screen with an Android in a box or a phone with a down arrow... don't freak out and pull the battery - this screen is part of the radio update. Let it run and it will take you back to recovery when it's finished. If you do pull the battery, you will most likely brick your phone.
There are Gingerbread roms and Froyo roms - you can flash either. Just be sure to read all of the information given on the first page of the thread so you don't miss any info & always do a backup and you'll be fine.
(from... Evo/MIUI/Tapatalk)

OK tried flashing SNS v1.3.zip the exact way the instructions you gave me tell me to. It says same thing as it did when I used ROM Manager.
1. Finding update package...
2. Opening Update Package...
and then here it goes
3. Can't open /sdcard/SNS v1.3.zip
(bad)
Installation aborted
What am I doing wrong or not doing at all? I downloaded this Rom off of the following thread [ROM]UPDATE!(4/28/11) SmoothnSexy V1.3, Gingerbread-ish looking Froyo/SENSE
from this site.

Also noticed this when doing fastboot PC36DIAG.zip
Is this correct?

HAve a buddy with an evo, his is doing exacly the same thing..... helllppp

rwon said:
HAve a buddy with an evo, his is doing exacly the same thing..... helllppp
Click to expand...
Click to collapse
Do you have Amon RA Recovery. Did you install it and when you hold the power and vol- button together, you get a white screen. At the top does it say S-OFF?
If so, then proceed to go to the recovery. If it is Amon RA, it will be green. If it is the latest version of clockwork (which you don't want to use), then, it's orange.
If it's green, then wipe cache, data, boot, system, dalvik cache, sd-ext (if you have it) and then flash your ROM.
ALWAYS MAKE A BACKUP FIRST from whatever Recovery you are using. Clockword(orange lettering), does not support Edify scripting, only Amend. If you have Amon RA(green lettering), it supports both edify and amend scripting.

I did this but it says skipping Wipe od SDEXT...
Could this be the problem?

says skipping Wipe of SDEXT...
not
skipping Wipe od SDEXT...

Something else to take into consideration, your SD card may need to be re-formatted as well. Try this:
Once you have Amon-RA installed, and you are booted into it, then connect the phone to your computer via the USB cable. Navigate to USB-MS Toggle and activate it, you should now be able to copy everything from the card to your computer (re-partitioning will erase everything on the card).
After you have backed up, you can use the partition SDCard menu to repartition and reformat your card. Or you can use the Wipe menu to just format the SDCard - though I would re-partition it just to ensure the file system on the card is truly reset. If you do re-partition, use 0 for a swap (most ROMs don't use it), use anywhere from 0-500MB for the ext (this will be mostly used by app2sd, and not a requirement of the ROM, so it is optional), and the rest of your card size for the remainder (this will be partitioned as FAT32, I believe).
Once that process is complete, you can copy your ROM back over to the card (USB-MS toggle) and try again.
I had similar issues with MY Evo (using the SD card that came with it), re-partitioning it worked like a charm in clearing out all of the problems I had been experiencing. Good Luck!
BigJohn

corey140 said:
I did this but it says skipping Wipe od SDEXT...
Could this be the problem?
Click to expand...
Click to collapse
That's not the problem. You are s-off correct? I've never heard of that rom, you got it from the Evo Development forums, right? Make sure it's compatible with your phone.
I've seen this problem before, so do a search and see what the solution was.
EDIT: Do what Big John said, that sounds like a likely culprit.
(from... Evo/MIUI/Tapatalk)

corey140 said:
I did this but it says skipping Wipe od SDEXT...
Could this be the problem?
Click to expand...
Click to collapse
SDEXT is just the EXT partition on the SD card (if there is one, see my previous post). What you are seeing is recovery just telling you that this partition doesn't exist.
BigJohn

Get aman ra for sure then do it all thru recovery
Sent from my PC36100 using Tapatalk

THANKS TO EVERYONE!!! Needed to Partition SD CARD and reflash ROM...WORKING GREAT NOW!!!

glad to hear

corey140 said:
THANKS TO EVERYONE!!! Needed to Partition SD CARD and reflash ROM...WORKING GREAT NOW!!!
Click to expand...
Click to collapse
I've had the same problem you are having and I'm about to try what everyone has suggested on your post. Question though... when you partition your SD does it delete everything on the SD card? And did you partition the SD before or after what everyone suggested? Thanks!

[Q] Phone Constantly Rebooting!

I was wondering if anyone can help me. I have looked at the other posts which relate to a very similar problem, but none of them have quite the same problem as me. Basically, all the phone will do is show the 'HTC Quietly Brilliant' loading screen and it is stuck in a reboot cycle. I can access the bootloader and I have tried to factory reset with no luck.
I was watching a YouTube tutorial on how to flash CM10 onto my One X (I do have ClockworkMod and all of that stuff installed already). Everything was going well, but the video only briefly (for maybe a second) mentioned the fact that you have to put the CM10 zip folder onto the phone storage before you flash the boot.img. I went on and followed the steps and tried to flash the boot.img, but as I said earlier, all the phone will do is reboot over and over again. I have charged it to full battery so this should not be a problem when I go to fix it.
I would be really grateful for any help on the subject as I contacted the person who made the tutorial, and he has not responded. Thanks in advance.

Havoc2510 said:
I was wondering if anyone can help me. I have looked at the other posts which relate to a very similar problem, but none of them have quite the same problem as me. Basically, all the phone will do is show the 'HTC Quietly Brilliant' loading screen and it is stuck in a reboot cycle. I can access the bootloader and I have tried to factory reset with no luck.
I was watching a YouTube tutorial on how to flash CM10 onto my One X (I do have ClockworkMod and all of that stuff installed already). Everything was going well, but the video only briefly (for maybe a second) mentioned the fact that you have to put the CM10 zip folder onto the phone storage before you flash the boot.img. I went on and followed the steps and tried to flash the boot.img, but as I said earlier, all the phone will do is reboot over and over again. I have charged it to full battery so this should not be a problem when I go to fix it.
I would be really grateful for any help on the subject as I contacted the person who made the tutorial, and he has not responded. Thanks in advance.
Click to expand...
Click to collapse
Have you placed the ROM's zip file in your phone's root?
If you haven't, go to fastboot and flash CWM 5.8.4.0 and then go into recovery > mounts and storage > mount USB. Now place your ROM into the storage and flash it via install zip from SD card. Don't forget to wipe data partition, cache partition and Dalvik cache.
If this wasn't your case, just try erasing data partition, cache and Dalvik cache again.
If it still doesn't work, try flashing another ROM.

Thank You!!!
SidDev said:
Have you placed the ROM's zip file in your phone's root?
If you haven't, go to fastboot and flash CWM 5.8.4.0 and then go into recovery > mounts and storage > mount USB. Now place your ROM into the storage and flash it via install zip from SD card. Don't forget to wipe data partition, cache partition and Dalvik cache.
If this wasn't your case, just try erasing data partition, cache and Dalvik cache again.
If it still doesn't work, try flashing another ROM.
Click to expand...
Click to collapse
Thank you so much. I had CWM 5.8.4.0 already, all I had to do was mount USB and put the CM10 zip on the phone storage! I also wiped the caches, the phone works better now than it ever has . Thank you so much again, really appreciate the help

Did I brick my SGS3 ? ^_^

All right, first thing first. Thanks to everybody for this amazing forum and all support.
Well. Here's my story:
1) Planned on installing CM10 nightly
2) Went to recovery (TWRP v2.2.0) and by mistake wiped everything :/ (Cache, Dalvik Cache, Factory Reset, System Internal Storage)
3) In effect i wiped everything including system.
4) Still have access to TWRP and download mode.
Does anybody have a clue how to fix that and install CM10 again?
PS.
1) internal storage does not mount under system (WIN7)
2) TWRP does not recognize microSDXC (32gbz) formated to either exFat or NTFS. (Tried 4 (four) of them)
Should i buy another micro sd like 2gb, format it to Fat32 and drop CM.zip there ? Or need i do something else?
Very respectfully.

That happened to me I just downloaded the rom to a sd card from my old phone put it in my s3 and installed it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Hey thank you for quick answer. Do you know if there is any limitation for TWRP? It does not read my 32gb MicroSDXC.

Go into download mode and re flash then stock rooted rom.
Then install your twrp and try cm again.
Sent from my SGH-I747M using xda app-developers app

Personally, I would (try to?) use adb with the phone booted into TWRP to transfer the ROM you want to flash over to the phone's internal storage, and go from there.
If that's not a possibility for whatever reason, you'd be best off starting by reflashing a stock rooted image with Odin and going from there.

Well. First of all thank you all for all your help in support. Got it back to stock with root (Odin flash). However there is another small problem that i can't figure out. TWRP itself seem not to have access to anything. I mean it sees all / but after openning /sdcard or anything else all it sees is empty folders. It doesn't have an access to external sd either (when you check log it sees that it couldn't mount ext sd correctly [even if after boot to stock system it recognizes it witout any issues).
Any idea how to solve this problem? What has been tried:
1) Reflash recovery (TWRP 2.2 using ODIN)
2) moving all files to /
3) RootExplorer see files (cm.zip) after reboot TWRP doesn't
4) Installing GooManager (it crashes after granting supersu permissions)
Very Respectfully.

With all those problems, flash to stock rooted and start over. You will be better off in the long run. You may want to also format your external sd.
Don't flash twrp with Odin.
Rooted stock
Dl and use goo manager to get twrp

What about a stock kernel? Just my chime in
Sent from my SAMSUNG-SGH-I317 using xda premium

Allright small update.
1) ReFlashed to rooted stock (root66_ATT_I747UCDLK3.tar.md5)
2) Installed GooManager
3) Installed TWRP (using GooManager)
4) Downloaded lastest CM10 nightly (cm-10.1-20121218-NIGHTLY-d2att.zip) using GooManager
5) Flashed cm-10.1-20121218-NIGHTLY-d2att.zip from GooManager menu (FlashROM) - Wiped Dalvik & Cache
Now I'm stacked with CM boot splash for past 5 min hoping it just takes longer that it should.
Any ideas?
Very Respectfully.
EDIT:
Booting into recovery and performing factory reset fixes problem.
Thanks to everybody who helped.

widofmaker said:
Allright small update.
1) ReFlashed to rooted stock (root66_ATT_I747UCDLK3.tar.md5)
2) Installed GooManager
3) Installed TWRP (using GooManager)
4) Downloaded lastest CM10 nightly (cm-10.1-20121218-NIGHTLY-d2att.zip) using GooManager
5) Flashed cm-10.1-20121218-NIGHTLY-d2att.zip from GooManager menu (FlashROM) - Wiped Dalvik & Cache
Now I'm stacked with CM boot splash for past 5 min hoping it just takes longer that it should.
Any ideas?
Very Respectfully.
EDIT:
Booting into recovery and performing factory reset fixes problem.
Thanks to everybody who helped.
Click to expand...
Click to collapse
GJ take it sure and slow. Other than flashing stock/rooting form Odin I wouldn't flash anything form Odin. Once you have super user on your phone, leave Odin out and do everything from phone
That's the safest route and it gets easier from here. The countless hours you spent are much easier the more you do it. Shouldn't take more than 20 minute to backup and flash roms and new apps from now on

Oh boy.
Almost done. But here are another tiny problems that just bother me and but I think they're solvable.
1) GooglePlay suddenly gives "No Connection" error, even though every other app that requires connection (Messenger, Browser) work just fine.
Have to mention that it worked for a while, installed couple apps (drop some more to install in queue and when I woke up - FAIL!)
Things done:
-Forced to stop
-ClearedData & Cache
Is there any other solution to fix it rather than reflashing gapps ?
2) The ExternalSD is mounted under PC as Internal Storage and vice versa.
When you click "Samsung -GHS-I747) in my computer it shows both with proper sizes but once you click them it opens the other.
No clue how to solve that one.
Very respectfully.

widofmaker said:
Oh boy.
Almost done. But here are another tiny problems that just bother me and but I think they're solvable.
1) GooglePlay suddenly gives "No Connection" error, even though every other app that requires connection (Messenger, Browser) work just fine.
Have to mention that it worked for a while, installed couple apps (drop some more to install in queue and when I woke up - FAIL!)
Things done:
-Forced to stop
-ClearedData & Cache
Is there any other solution to fix it rather than reflashing gapps ?
2) The ExternalSD is mounted under PC as Internal Storage and vice versa.
When you click "Samsung -GHS-I747) in my computer it shows both with proper sizes but once you click them it opens the other.
No clue how to solve that one.
Very respectfully.
Click to expand...
Click to collapse
1. you are flashing a version of gapps that is out of touch with your rom or you did not flash it correctly/cleanly. I remember no matter how many times I flashed gapps I wouldn't get it to sync. Backed all user apps to Titanium backup. Did a clean install from scratch, and wallah it worked. Last sort.
Without doing that though there is usually one that is compatible that is listed on your rom page. Flash that one. For me that is 10/22 but I remember it giving that same error for a while so I ended up flashing the previously compatible version before that which was 7/26. Goo.im might help here, I haven't used it myself. Once you find a working gapps version etc. Store your 'safe' builds in one folder
2. Not sure what you mean. When you click your phone you should see internal and external storage on your phone. They are what they say they are. People tend to piss on not being able to find the right file size and folder attributes on this phones usb mount. It is a common problem. Probably one of the few problems on the phone. Annoying but manageable

zetsui said:
2. Not sure what you mean. When you click your phone you should see internal and external storage on your phone. They are what they say they are. People tend to piss on not being able to find the right file size and folder attributes on this phones usb mount. It is a common problem. Probably one of the few problems on the phone. Annoying but manageable
Click to expand...
Click to collapse
1) Ended up reflashing gapps with goomanger (script to TWRP)
2) What i mean is that under phone it recognizes them perfectly. Just when I connect phone through USB to PC, my PC tends to mix them up. Just shows ExSD as Internal and Internal as ExSD. No biggy, just tried to fix as many tiny issues as possible before I hit deployment.
Very respectfully.

That is a known, and stated, issue with cm 10.1

[Q] Ext partition error. Unable to wipe data, install zips and restore backups

Okay, this error have been annoying me the whole day. I have a Xperia SL rooted with .55. Everything was working completely great. Today I just tryied to restore a backup with CWM recovery, and I got this error.
Code:
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p12
I can't wipe data and I can't install any MOD or ROM properly because of that.
The most strange thing is that I don't even have a ext sd slot. I don't know why I'm getting this error.
I've been searching for fixes and all I got was completely random fixes from people that mostly doesn't even know how did they fix it. Even though, those doesn't work for me.
* I figured out that when I go on FORMAT /DATA, after that, I can wipe data, and I can (re)install the room again without any error. The problem is after I reboot the system, the error comes back, and I need to format /data if I want to install anything again without errors.

Try flash .ftf with flashtool. Wipe all.
Sent from my LT26i using Tapatalk 2

drixjp said:
Okay, this error have been annoying me the whole day. I have a Xperia SL rooted with .55. Everything was working completely great. Today I just tryied to restore a backup with CWM recovery, and I got this error.
Code:
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p12
I can't wipe data and I can't install any MOD or ROM properly because of that.
The most strange thing is that I don't even have a ext sd slot. I don't know why I'm getting this error.
I've been searching for fixes and all I got was completely random fixes from people that mostly doesn't even know how did they fix it. Even though, those doesn't work for me.
* I figured out that when I go on FORMAT /DATA, after that, I can wipe data, and I can (re)install the room again without any error. The problem is after I reboot the system, the error comes back, and I need to format /data if I want to install anything again without errors.
Click to expand...
Click to collapse
Wrong section. Questions don't belong in the General Section. As for your problem, the best solution would be to just flash a stock ftf as mentioned by m1st3r1

m1st3r1 said:
Try flash .ftf with flashtool. Wipe all.
Sent from my LT26i using Tapatalk 2
Click to expand...
Click to collapse
I tryed that thousands of time already and no lucky. I wanna try to format(fat32) it using my computer. The problem is that my computer doesn't recognize my cellphone as a external hard drive. I can read the files inside but it's still being detected as a celphone. And like that I can't use my hard drive tools on it.
Sent from my LT26ii using xda app-developers app

drixjp said:
I tryed that thousands of time already and no lucky. I wanna try to format(fat32) it using my computer. The problem is that my computer doesn't recognize my cellphone as a external hard drive. I can read the files inside but it's still being detected as a celphone. And like that I can't use my hard drive tools on it.
Sent from my LT26ii using xda app-developers app
Click to expand...
Click to collapse
why you wanna try to format in PC? if u format (regularly) in PC , it will only format your sdcard (mnt\sdcard). the mmcblk0p12 is the \system partition. u need to somehow format it first, via fastboot, or try via cwm to format \system.
and give more explanation bout the condition of your phone.. ie: rom, kernel, locked/unlocked bootloader.
i too, once, messed up my \data partition (which it's mmcblk0p14). i fixed that by using fastboot

m1st3r1 said:
why you wanna try to format in PC? if u format (regularly) in PC , it will only format your sdcard (mnt\sdcard). the mmcblk0p12 is the \system partition. u need to somehow format it first, via fastboot, or try via cwm to format \system.
and give more explanation bout the condition of your phone.. ie: rom, kernel, locked/unlocked bootloader.
i too, once, messed up my \data partition (which it's mmcblk0p14). i fixed that by using fastboot
Click to expand...
Click to collapse
Like i said, it's a. 55 rooted with stock Rom. Boot loader unlock alowed: yes. I tryed every kind of fix in cwm already and nothing works.
Something I never tryed is via fastboot. How do I proceed with that?
Sorry, my android life just started yesterday, I don't have much knowledge
EDIT: Ok I solved. Actually it's not like a fix, it's just like putting a silver tape to handle the problem. For some reason I'm able to advance restore system backup via CWM recovery. Every time that I do that, my CWM recovery is fully functional again, i can install mod, rom, etc. But, when I reboot into system again, the problem comes back, but I can still use my android without any problems, I just can't install anything via CWM recovery. So basically, now, every time that I want to install something in recovery, first I need to advanced restore system, and than install the rom, mod or whatever. Than I backup again in case I want to install anything else in the future, to repeat the same procedure with the last backup.
I was just having some problems when I was trying to restore the system with a md5 missing error... something like that. I solved this problem by just creating a file.txt in the backup folder and than renamed it to nandroid.md5. Magically it was fixed.
Sent from my LT26ii using xda app-developers app