yashsingh1/xdaforums huggingface dataset:
[Sony Xperia E1] Kizoky:
BUMP

Though I suppose everyone are now using Illuminated ROM, I updated my Debloater to V3

After having the phone for 12 months and a half year, and having KitKat on it since last year August, I finally realised what was causing the phone to not working normally after Factory Reset

V3:

-Removed ANTHal, CABL service from the Debloater

-Removed Dummy apps from the Debloater

-Removed must-need apps from the Debloater

ANTHal and CABL is not necessary to have, you can disable it or Hibernate it with Greenify without no problems

If you need more RAM, you need to decrease the Dalvik, by Default it is around 200
[Sony Xperia E1] mire777:
I know that you say that "QUESTIONS ABOUT

HOW TO USE THIS WILL BE

IGNORED" , but when i click "install zip" from CWM(locked bootloader) nothing happens, what im doing wrong?
[Sony Xperia E1] Kizoky:
That was meant for dummies who can't use Recovery

I don't know. are you using V2 or V3?
[Sony Xperia E1] mire777:
I'm using V3.

"philz touch 6.58.4

clockworkMod v6.0.5.1

I go to: install zip>choose zip from/storage/sdcard1>E1KKDebloaterV3.zip

Then it say:

Calculating md5sum

finding update package

opening update package

installing update...

E: installation aborted.
[Sony Xperia E1] Kizoky:
If you try to use V2

Does it say the same?
[Sony Xperia E1] mire777:
V2 works , thanks :)

Should i now do factory reset?
[Sony Xperia E1] Kizoky:
V2 is buggy

If I have time I will try and repair V3
[Sony Xperia E1] mire777:
Thanks, i don't have problems for now..
[Sony Xperia E1] Kizoky:
ow, I made a huge mistake

I made a folder in the .zip folder, that's why you guys can't flash it
[Sony Xperia E1] mire777:
Oh, thanks. I fix this... :)

I only left photo widget, email app, weather and fm radio.

Don't know why you add them to the list?

Thanks, phone is now faster..
[Sony Xperia E1] Kizoky:
I added them because I consider those apps useless
[Sony Xperia E1] Kizoky:
Update:

Fixed the V3 debloater after nearly 4 months :eek:

Added Mire777's V3 version, which excludes some apps you find not a bloatware
[Sony Xperia E1] iamraghavgupta:
some other appsa

thanks it worked great on D2105

Can you add another file with completely removing the following:

Account Manager

Back up & restore

File Commander

Google Search

Jive

LIV Sports

Movies

Setup Guide

Sony LIV

Tags

Xperia Lounge

Xperia Wallpapers

YouTube

Album (if possible)

TrackID

Initial Boot Setup

Live Wallpaper Picker

Location-based WiFi

Mirror

PhotoEditor

Update Center

Update Service

Walkman

Podcast

sony mobile communication

all the apps together forms a great chunk. We have good alternatives available for the above like es file explorer for file manager, and poweramp or any other for music etc..

Basically, the end would be rom with only the following:

PlayStore

Messaging

Phone

Camera

Calendar

Contacts

Settings

Alarm & Clock

Google Settings

Calculator

Downloads

FM Radio

for reference, i am quoting the locations of some of the files as it is there in the script:

AntHalService.apk

com.infibeam.allthingsd.apps.spinr.apk

com.msmpl.livsportsphone.apk

com.sony.smallapp.mirror.apk

com.sonyericsson.xhs.apk

com.sonyliv.apk

LiveWallpaperPicker.apk / LiveWallpapersPicker.odex

LocationBasedWifi.apk

SemcPhotoEditor.apk

sneiaccountmanager.apk

UpdataCenter.apk

w-button-control.apk

Youtube.apk

the above in (System /app)

The following in (System/priv-app)

Baackup-wizard.apk

BackupRestoreConfirmation.apk / BackupRestoreConfirmation.odex

filecommander.apk

SemcAlbum.apk

SemcMusic.apk

SemcVideo.apk

TagGoogle.apk

Velvet.apk
[Sony Xperia E1] Kizoky:
Will do. However, I would be very careful If I were you

Deleting LiveWallpaper apk will most likely glitch the Home app, and you can't choose regular wallpapers (Yes, seriously)
[Sony Xperia E1] iamraghavgupta:
oh i didnt look into that. I didnt tested removing all that, since i was not able to get these linking of apps. Can you help in that.

Just remove everything except required by the above stated apps. Rest all is either not used, or there are better alternatives.

And you have made it so easy with this. Now the device has got a new life. Thanks again for the awesome work.
[Sony Xperia E1] Kizoky:
Check again. 2 versions of V4 made, one of them excludes removing FM Radio, Weather widget, Photo widget, and Sony E-mail app

Also, the DeSony-ization zip. Removes SemcAlbum, SemcVideo, SemcMusic, and filecommander :)

(Other apps that I didn't removed needs to stay in System to avoid any bugs, such as black wallpaper, or home crashes everytime)
[Sony Xperia E1] iamraghavgupta:
Thanks!, that works. But File Commander is not removed.

I ran it over my previously debloated device with v3, if it matters.

One more request if Can you create a zip that excludes only FM Radio, and not the other three. I want to keep only the FM Radio and not the rest three. Or remove FM Radio from v4?
[T-Mobile Samsung Galaxy S6 Edge] Rameda:
Hi I am trying to unlock my s6 edge through Tmobile. I am eligible for the unlock with 100 dollars prepaid and 15 days since I activated it.

They have been trying to unlock it but the apps says fail and the rep told me it's already unlocked. I haven't tried with a diff sim card but I wanna know if it's perm or just the 30 days if a diff sim card works?

edit: already tried with a non tmobile sim and it says the phone is still locked. Call tmobile to let them know and they said they will answer in 24 hours to solve the unlock problem.
[ONE Q&A, Help & Troubleshooting] master.peterm:
hey guys, I'm trying to fix my friend's oneplus. It is locked, with CM recovery. I don't wanna wipe it, and I know why it bootloops, he applied a theme and that is the reason it bootloops. I can only get it to recognize via adb in sideload. He didn't enable USB debugging in the developer settings. Is there any way to fix this or enable ADB (I can fix it if I get non sideload adb) without wiping?

--thanks!
[X 2014 Q&A, Help & Troubleshooting] YOUNG MAN.:
Hey,guys! I uesd fastboot to flash system,but it failed

code:

target max-sparse-size: 256MB

sending 'system' (256598 KB)...

OKAY [ 8.040s]

writing 'system'...

(bootloader) Failed to flash sparse image

FAILED (remote failure)

finished. total time: 18.249s

anyone can help me please?
[X 2014 Q&A, Help & Troubleshooting] libnijunior:
Try to use the mfastboot, because the system.img is to big to use the normal fastboot
[X 2014 Q&A, Help & Troubleshooting] YOUNG MAN.:
it failed too

code

target reported max download size of 536870912 bytes

sending 'system' (256089 KB)...

OKAY [ 8.035s]

writing 'system'...

(bootloader) Failed to flash sparse image

FAILED (remote failure)

finished. total time: 13.062s

and sometimes it shows

target reported max download size of 536870912 bytes

sending 'system' (256598 KB)...

OKAY [ 8.046s]

writing 'system'...

(bootloader) Failed to erase partition

FAILED (remote failure)

finished. total time: 13.224s
[X 2014 Q&A, Help & Troubleshooting] juliospinoza:
What version of boot loader do you have? If you already flashed the boot loader of 5.0.2 and you are trying to flash older system images that error appears.
[X 2014 Q&A, Help & Troubleshooting] YOUNG MAN.:
I Just bought this phone yesterday and it was 5.0 when i got it. Then i updated to 5.1 and the BL version is 60.14 now . I tried to back to 5.0 so it showed this error.

Do you have any way to solve this problem? My phone is bootloop now.

Thanx
[X 2014 Q&A, Help & Troubleshooting] JulesJam:
you really shouldn't downgrade unless you know what you are doing.

Is the bootloader unlocked? Can you get into bootloader mode?
[X 2014 Q&A, Help & Troubleshooting] YOUNG MAN.:
Yes,it is unlocked and i can get into fastboot mode .Is that bootlodader mode?
[X 2014 Q&A, Help & Troubleshooting] JulesJam:
Yes, they are synonyms. I would install Motorola Device Manager to your PC and let it attempt to repair your phone.

https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481

If it doesn't repair your phone, post back here.
[X 2014 Q&A, Help & Troubleshooting] YOUNG MAN.:
I installed Motorola Device Manager, what should i do next?
[X 2014 Q&A, Help & Troubleshooting] YOUNG MAN.:
I installed Motorola Device Manager and tried again, it still did't work.

code:

C:\Users\Alan\Desktop\ccc>fastboot flash system F:\XT1095\system.img_sparsechunk

.0

target max-sparse-size: 256MB

sending 'system' (256598 KB)...

OKAY [ 8.047s]

writing 'system'...

(bootloader) Failed to erase partition

FAILED (remote failure)

finished. total time: 13.217s
[X 2014 Q&A, Help & Troubleshooting] JulesJam:
Did it detect your device at all? Did it try to repair it?

If you are only trying to flash small sparsechunks, have you tried flashing using the latest version of fastboot from Root Junky's site?

http://rootjunkysdl.com/?device=Adb Fastboot Files
[X 2014 Q&A, Help & Troubleshooting] MrMeeseeks:
Go into developer options and enable OEM unlocking. Then try it.

Edit: Forgot you said you were bootlooped. Can you install the 5.1 image again?

Sent from my XT1095
[X 2014 Q&A, Help & Troubleshooting] YOUNG MAN.:
NO,It not detect my phone,it just search new software when i open it.

And I tried the latest version of fastboot,still failed
[X 2014 Q&A, Help & Troubleshooting] JulesJam:
Did you try RSDLite?
[X 2014 Q&A, Help & Troubleshooting] YOUNG MAN.:
it can't detect my phone
[X 2014 Q&A, Help & Troubleshooting] JulesJam:
When you are in recovery, what does

adb devices

show you? Of course when you open the cmd window you have to navigate to a folder where adb.exe and the other required files are stored in order to use adb commands.
[X 2014 Q&A, Help & Troubleshooting] YOUNG MAN.:
it shows View attachment 3294009

but in fastboot mode it shows View attachment 3294012

and my recovery is TWRP 2.8.60
[X 2014 Q&A, Help & Troubleshooting] JulesJam:
No I mean, connect your phone to your PC when you are in TWRP. Then open a command window. Then navigate to where adb.exe is stored - i.e, at the command prompt type in cd c:\[fill in the directory where adb.exe is stored]

then when you are at the proper directory, at the command prompt in the command window type:

adb devices

then hit enter.

It should return the serial number of your device.
[X 2014 Q&A, Help & Troubleshooting] YOUNG MAN.:
it shows this:

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

List of devices attached

device
[X 2014 Q&A, Help & Troubleshooting] YOUNG MAN.:
NO,my recovery is TWRP now ,and I can't flash the original recovery ,it failed.
[X 2014 Q&A, Help & Troubleshooting] YOUNG MAN.:
Please help me guys. Thx!!!
[X 2014 Q&A, Help & Troubleshooting] juliospinoza:
As I said is because you have a newer version of boot loader and you can't downgrade. You will have to wait till 5.1 release or flash the 5.0 TWRP file.
[X 2014 Q&A, Help & Troubleshooting] YOUNG MAN.:
But it worked before . I downgraded to 5.0 and used a while then it rebooted and it was bootlooped. So I tried to flash 5.0 again but it failed this time .And it failed the first time but it worked after i used another PC. But this time I changed 3 PC and it just keep fail.

And not just system.img , recovery.img also failed .

And when i tried wipe data/cache it shows this:

And when i tried flash a 5.0 TWRP file ,it failed
[X 2014 Q&A, Help & Troubleshooting] AGISCI:
It looks like your partitions are screwed up. Have you tried flashing gpt.bin first?
[X 2014 Q&A, Help & Troubleshooting] JulesJam:
Ok that is good - it means you can use adb commands to load a custom ROM to the phone and flash it. That will hopefully at least get your phone stable. Then you can try to flash back to stock if you want to.

First pick a custom ROM that is the right version for your bootloader (you are on lollipop correct?). To get the custom ROM on your phone, you put the zip file in the same directory where you have adb, open a command window and type this at the command prompt:

adb push [insert name of zip file] /sdcard

and hit enter. Obviously you don't put the brackets around the zip file name.

That will put the ROM zip on your sdcard. Then you can do a wipe of cache, data and system and then install the zip file.

I don't use custom ROMs so read up on them if you don't know much about them. I think with Cyanogenmod, you need to install the google apps separately b/c it is AOSP based, but again, read up on that if you don't already know about it.

Once you get your device stable, you can retry flashing back to stock through the bootloader. Just make sure you are using the most recent version of fastboot.

Also, did you ever make a nandroid backup? If so, is it stored on your phone or on your computer?

---------- Post added at 06:29 PM ---------- Previous post was at 06:27 PM ----------

I would not try to flash stock recovery. Stay with TWRP b/c then you can use adb commands.
[X 2014 Q&A, Help & Troubleshooting] YOUNG MAN.:
I tried to push the ROM into my sdcard as you said ,but my device seems like is read-only

code:

failed to copy 'F:\BaiduYunDownload\11111.zip' to '/sdcard/11111.zip': Read-only

file system
[X 2014 Q&A, Help & Troubleshooting] AGISCI:
Did you try flashing gpt like I mentioned?
[X 2014 Q&A, Help & Troubleshooting] JulesJam:
adb push F:\BaiduYunDownload\11111.zip /sdcard

You don't need to have the file name after /sdcard

---------- Post added at 07:21 PM ---------- Previous post was at 07:20 PM ----------

I would hold off on doing that until he sees if the custom ROM works. If you screw up flashing a partition table, you can really mess up your device.

He may need to do that but if he can just get the device stable, he may not need to do that.
[X 2014 Q&A, Help & Troubleshooting] YOUNG MAN.:
yeah,i did it. failed

code :

this is the 5.1 ota gpt

target max-sparse-size: 256MB

sending 'partition' (32 KB)...

OKAY [ 0.000s]

writing 'partition'...

(bootloader) This may take a few seconds, if a

(bootloader) different partition table is being

(bootloader) flashed since we need to backup

(bootloader) and restore a few partitions

(bootloader) Flashing primary GPT image...

(bootloader) Failed to write primary GPT.

(bootloader) Failed to program partition table

FAILED (remote failure)

finished. total time: 5.068s

this is 5.0 gpt

target max-sparse-size: 256MB

sending 'partition' (32 KB)...

OKAY [ 0.014s]

writing 'partition'...

(bootloader) Preflash validation failed

FAILED (remote failure)

finished. total time: 0.093s
[X 2014 Q&A, Help & Troubleshooting] YOUNG MAN.:
i didn't write the file name after /sdcard ,it just showed this in the error information

View attachment 3294819
[X 2014 Q&A, Help & Troubleshooting] JulesJam:
Ok something is really messed up here and it may be your partition table.

Remind me again - what did you start with and then what did you do to get to this point?

Also, I think you should use RSDLite b/c it has checks in it when you flash to make sure you don't flash a partition table/bootloader mismatch.
[X 2014 Q&A, Help & Troubleshooting] YOUNG MAN.:
I bought this phone 2 days ago and i unlocked bootloader immediately. Then I falshed the 5.1 ota zip by original recovery , after that i used fastboot flashed TWRP , then use TWRP rooted. It worked fine at first, but after i used a while , it rebooted and bootlooped. So i tried to using twrp wipe data/cache , it showed some information like E: Unable mount 'cache/' .Then I tried to flash the 5.0 stock and it failed like this . But after i changed anther PC,it worked . So I flashed twrp and rooted again . But the same problem happened , it was bootlooped again. So i did the same thing and it worked again. But after a while it bootlooped again . So i did the same job again and again. And the same problem happened again and again. Finally after it bootlooped , when i tried to flashing the 5.0 stock again, it failed, then i changed 3 PC but it just keep fail.

And i did flash some ROMs by TWRP during this period .
[X 2014 Q&A, Help & Troubleshooting] JulesJam:
So now you are on BL version 60.14, which is the 5.1 bootloader?

I just did this with my device to test it, I flashed back to 4.4.4 system, which put me in a bootloop. Then i got into fastboot, connected my device to my PC and then manually started MDM. MDM detected I had a messed up phone and repaired it.

See if you can do that - put your device into fastboot and then connect to your PC and manually start MDM. See if MDM will repair your phone.

I have stock recovery so that may be an issue for you since you have custom recovery.

BTW - I am sure there is a way to fix this through TWRP using an adb shell, but idk enough about it to instruct you how to do it.

It is possible that you need to flash the partition table that matches your bootloader version too. Did the Pure Edition get the 5.1 update yet? I see the 5.1 OTA zip on graffixnyc's site, but was this official?
[X 2014 Q&A, Help & Troubleshooting] AGISCI:
No 5.1 OTA is not official yet. That OTA is the beta which has some problems. Which means there isn't a factory image for 5.1 yet and won't be for a while. So if he can't get it unbricked through what you are suggesting... he will have to wait until 5.1 is really released and a firmware image is found and shared.
[X 2014 Q&A, Help & Troubleshooting] YOUNG MAN.:
When I connected my phone to my PC ,it didn't show this

View attachment 3294909

so which one should i open?

View attachment 3294910 View attachment 3294911

I tried MotoHelperAgent.exe ,it can't run , nothing happened after i click it.

And it not official, just a test version
[X 2014 Q&A, Help & Troubleshooting] JulesJam:
Yeah, that is what I was worried about. He cannot go messing with the partition table until he has the correct version for his bootloader. 60.14 is the 5.1 bootloader correct?

---------- Post added at 08:51 PM ---------- Previous post was at 08:48 PM ----------

I just go to All Programs and start it from there.

Is 60.14 the 5.1 bootloader or is it the 5.0.2 bootloader?
[X 2014 Q&A, Help & Troubleshooting] AGISCI:
I assume that 60.14 is the 5.1 bootloader because I am on 5.0 and my bootloader is 60.11.
[X 2014 Q&A, Help & Troubleshooting] JulesJam:
There is a 5.0.2 for the pure edition correct? Does anyone know that bootloader version?

Edited - no it doesn't look like there is.
[X 2014 Q&A, Help & Troubleshooting] AGISCI:
The XT1095 doesn't have 5.0.1 or 5.0.2.
[X 2014 Q&A, Help & Troubleshooting] JulesJam:
Ok well the problem you have is that your bootloader has been upgraded to 60.14 but we don't have the firmware for it, just the OTA.

You absolutely cannot flash a lower version partition table to your device - you must use the partition table that matches your bootloader version.
[X 2014 Q&A, Help & Troubleshooting] YOUNG MAN.:
The MDM can not help me either, what should i do?:crying::crying::crying:
[X 2014 Q&A, Help & Troubleshooting] YOUNG MAN.:
So I have to wait the 5.1 partition table ?

But why it worked before? My BL version was 60.14 too when I flashed 5.0 stock successfully .
[X 2014 Q&A, Help & Troubleshooting] AGISCI:
The only thing I think you can do is wait for 5.1 to be released and for a firmware to be leaked for it.[emoji53]
[X 2014 Q&A, Help & Troubleshooting] JulesJam:
Download mfastboot version 2 and see if that will work to flash the 5.0 system.img.

http://xdaforums.com/attachment.php?attachmentid=2427667

---------- Post added at 09:13 PM ---------- Previous post was at 09:12 PM ----------

Idk, try using mfastboot version 2 to flash the 5.0 system.img and see if it can do it.

---------- Post added at 09:16 PM ---------- Previous post was at 09:13 PM ----------

The other thing to try is to boot into TWRP and wipe system partition and then boot into fastboot and then use mfastboot version 2 to flash the 5.0 system.img.
[X 2014 Q&A, Help & Troubleshooting] YOUNG MAN.:
No,it failed too.
[X 2014 Q&A, Help & Troubleshooting] JulesJam:
Did you try wiping the system partition in TWRP before flashing using mfastboot version 2?
[X 2014 Q&A, Help & Troubleshooting] YOUNG MAN.:
failed..

And when i wiped system it showed this
[X 2014 Q&A, Help & Troubleshooting] YOUNG MAN.:
YES
[X 2014 Q&A, Help & Troubleshooting] JulesJam:
does fastboot erase system work?
[X 2014 Q&A, Help & Troubleshooting] YOUNG MAN.:
it showed

erasing 'system'...

(bootloader) Erase allowed in unlocked state

OKAY [ 0.094s]

finished. total time: 0.094s

is that work?

And after that flash system still fail
[X 2014 Q&A, Help & Troubleshooting] JulesJam:
What did it say when you tried to flash the 5.0 system.img after erasing?
[X 2014 Q&A, Help & Troubleshooting] YOUNG MAN.:
It worked now !!hahaha!! :victory::victory::victory::victory:

I clicked the Format Data button in TWRP and it worked!!!

Thanks those who tried to heip me!! thank you very much!!:laugh::laugh::laugh:
[X 2014 Q&A, Help & Troubleshooting] YOUNG MAN.:
It worked now:laugh::laugh::laugh:

Thanks a lot!!:good::good::good:
[X 2014 Q&A, Help & Troubleshooting] JulesJam:
OK just to be clear so if this ever happens to anyone we will know how to fix it - you booted into TWRP and clicked Wipe, then Format Data. Then after that, you were able to use fastboot to flash the 5.0 system.img?

---------- Post added at 09:56 PM ---------- Previous post was at 09:51 PM ----------

Also, I would not take the 5.1 OTA when it comes out. I would instead use Motorola Device Manager to update. The OTA is a patch and idk how it works if you have already upgraded your bootloader. MDM is like using RSDLite - it does a flash of the partition rather than patch.

Plus if you use MDM to update, then you will have a copy of the 5.1 fxz on your computer.
[X 2014 Q&A, Help & Troubleshooting] YOUNG MAN.:
Right!! And in my case, i can't flash anything by fastboot .it always shows (bootloader) Failed to erase partition.

So i think the key issue probably is that my phone's data partition got corrupted .

So I decided try to formatting data partition , it really worked!!:laugh::laugh:

And I'll never do anything that could update my bootloader version again!!

And really sorry about my terrible English.
[X 2014 Q&A, Help & Troubleshooting] JulesJam:
In general, it is OK to update your bootloader IF your bootloader is unlocked and there is a stock fxz available.
[X 2014 Q&A, Help & Troubleshooting] YOUNG MAN.:
Yeah, but i don't want to take any risk .

My Moto X 2013 was bricked because this ,now the same thing almost happens to my new moto x :eek:

Thanks anyway!:)
[X 2014 Q&A, Help & Troubleshooting] JulesJam:
What happened to your MX13?
[X 2014 Q&A, Help & Troubleshooting] YOUNG MAN.:
I flashed a lower version stock and I tried to ota...

So it was complete dead. It can't even got into fastboot.

Then I changed a main board to fixed it..

And it fell into the water a few days ago so I bought this phone.
[X 2014 Q&A, Help & Troubleshooting] JulesJam:
Glad I read this thread - I flashed a lollipop MX14 system.img to my MX13 and it really messed it up. Had to format the data partition to get it back to stock!
[X 2014 Q&A, Help & Troubleshooting] Raistlin1:
I am having the same problems as OP but my recovery is stock and I never tried flashing the leaked 5.1.

My completely stock rooted 5.0 kept turning off, safe mode worked so I decided to reset device. Device reset and it was back to original, I was doing something and then decided to factory reset from within the phone settings and that's when my phone went into an erasing boot loop. It just keeps trying to erase but thend fails and brings me to the android with triangle. I can get into recover from there but wiping device doesn't do anything, just reboots again and tries erasing but fails. I tried fastboot and mfastboot but they all fail with the same error the op had.

I cannot seems to get the 5.0 system image to flash using fastboot and mfastboot just hangs and says waiting. MDM sees the device and says it has the latest version.

Need some help, how can I wipe Dat like OP did in TWRP if I have the stock recovery?

Thanks
[X 2014 Q&A, Help & Troubleshooting] YOUNG MAN.:
You can boot TWRP without flashing it

fastboot boot recovery.img

then you can format data use TWRP

Ps :use TWRP 2.8.5 , this code can not boot 2.8.6 on my device