So, this is just a pristine (as "untouched" as possible) image of the Norwegian telenor one.
What I have done:
I've extracted everything, deodexed it, and put everything, excluding all useless junk, in here. Nothing is edited or removed.
All I've added is SuperSU, busybox and ES File explorer. And changed /system/etc/customization/settings/config.prop so the phone is in US English on first boot. (Well, that's the only thing I've edited)
Only files that aren't deodexed are playstationcertified.odex and com.android.nfc_extras.odex. There's no .jar-files for them so...
I copied playstationcertified.odex to com.playstation.playstationcertified.odex since AndroPlus mentioned something about it somewhere. Don't know how important this is.
What kernel should I use with this?
I'd recommend AndroPlus' work any day. It's awesome! So head over and hit that thanks-button for him to show how awesome you think it is!
http://forum.xda-developers.com/showpost.php?p=56439759&postcount=1
If you do use one of his 27-and-on-kernels you can format /system and /cache as F2FS.
Do not format /data as F2FS though. Do not do it. The phone won't boot if /data is formatted as F2FS.
Don't know why not.
If this bricks your phone or whatever else problem arises, I'm not responsible or of much help.
All I can vouch for is it runs fine on my D6603 Z3 phone. With /cache and /system formatted as F2FS.
(Also runs fine with /cache and /system as ext4, if you're wondering)
Does it work with a locked or unlocked bootloader?
It works with an unlocked bootloader. Don't know if it works with a locked one, mine is unlocked.
Here you go:
shrunk-D6603_23.0.1.A.5.77_R12B_Telenor.zip
Here are the files that have been removed:
http://www.mediafire.com/download/vybrb0k5l0s5coy/removed.zip
They're just collected in a zip-file with various folders that tells you where they belong. So you can just take what ever you feel is missing and put it "back" in place in the shrink-zip above.
Here is the original (but still deodexed) thing in one big chunk:
http://www.mediafire.com/download/85evwwlu7fn7vul/23.0.1.A.5.77_Telenor.zip
Just for the sake of the challenge, here is as small as I manage to squeeze it. Just about 1GB on the phone after first installation (420MB as a download).
1. The background is "black" on boot. You need to touch and hold the screen, choose "themes", and select the one theme there is. There is no longer any automation-process that does this on first boot.
2. You need to set language yourself. Go to "settings", "language and keyboard", and change it to the language of your preference.
3. You now have a small ROM on your phone!
http://www.mediafire.com/download/0ei9bjbb8dfn99c/small-D6603_23.0.1.A.5.77_R12B_Telenor.zip
"But I need this and that program, can't you add..."
You do it! Just put what ever program you have or want in to /system/app on the phone (that is, in the zip-file). Some programs needs to be in /system/priv-app (they will force close on you until you put them in /system/priv-app - to really confuse you, playstation app has to be in /system/etc/product/applications, or it won't work. Why I have no idea...).
"But nothing happens when I hit the search bar on top..."
I removed Google Search. If you want it you can put it in /system/priv-app.
"I want to add wallpapers and ringtones"
Here you go. Just add ringtones and wallpapers to their respective folders and zip up, then install just like you'd install a ROM.
http://www.mediafire.com/download/5f5745fo5jlu4qb/add-ringtones-wallpapers.zip
Gonna give this a go later..
Just wondering, if you have already done the drm restore method listed in androkernel thread do you lose it when you flash a rom via zip? Is there anyway to get the drm fix to work on this rom?
Thanks!
Guitarfreak26 said:
Gonna give this a go later..
Just wondering, if you have already done the drm restore method listed in androkernel thread do you lose it when you flash a rom via zip? Is there anyway to get the drm fix to work on this rom?
Thanks!
Click to expand...
Click to collapse
No, I haven't. My point is generally just to make a "pristine" ROM. That is, I've removed what I don't think is needed (I'll upload the "leftovers" in a zip, after doing some more work), but other than that, this is just the way the original ROM was.
With added root and a file explorer.
But it's not that hard to add the stuff from that zip-file. They're just a few files that are extracted to overwrite some files in /system. Just open up the drm-zip and you'll see. The script for DRM doesn't do anything other than just extract (and overwrite) the files inside the zip. So if you want, you could just try to add those files to this and make that happen yourself.
What's the process for getting it as f2fs? Total novice with file systems but saw you guys talking about it in the kernel thread? Is it a case of installing it then converting in twrp?
Sent from my iPhone using Tapatalk
Has anybody tried this on locked bootloader?
The OP says they don't know since they have unlocked bootloader.
Thanks
@Verbato, please for next build i request 2 things, 1. Please remove the wipe internal storage upon flashing, 2. Please add the clock and calendar back, i think many users feel the way i do saying the clock and calendar are vital system apps that were removed, thanks for your work, the rom is smooth and fast with f2fs
corpsegrinder62 said:
@Verbato, please for next build i request 2 things, 1. Please remove the wipe internal storage upon flashing, 2. Please add the clock and calendar back, i think many users feel the way i do saying the clock and calendar are vital system apps that were removed, thanks for your work, the rom is smooth and fast with f2fs
Click to expand...
Click to collapse
Whats the best way to set it up with f2fs? Op said he will release a zip soon with missing apps etc
Guitarfreak26 said:
Whats the best way to set it up with f2fs? Op said he will release a zip soon with missing apps etc
Click to expand...
Click to collapse
The easiest way i done it is i used androplus kernel v27 with multirom twrp 2.8.5, flash with fota if u need to. Go to wipe, advanced wipe, tick which partition you want, eg. System, click change/repair file system - F2FS, do it with system and cache, just be warned - it will wipe both /data and /data/media so backup first. Last step is flash rom zip, sit back, relax, and enjoy f2fs partition, you should notice apps launch tons faster after doing it. Cannot format /data to f2fs though as op mentioned, system and cache only.
@Corpsegrinder Sure, no problem. If it's annoying you, the wiping of /data, I can just send you a new updater-script. It's inside of META-INF. If you download the first file over you'll find calendar and clock in /system/app. They're called "SemcClock.apk" and "SemcCalendar.apk".
I'll remark out the /data-wipe and add clock+cal in the next update.
Updated. No deletion of any data in... data. Added calc and calender. Will put in some work to make it even smaller. Means quicker, means less CPU-usage, and so less battery usage.
corpsegrinder62 said:
just be warned - it will wipe both /data and /data/media so backup first
Click to expand...
Click to collapse
Not any more.
Working on making it a slight bit smaller/quicker/etc.
Root and recovery
Hi. I really appreciate your work putting a debloated rom together for us.
I'm quite new to Z3 roms and feel quite overwhelmed by all the technical info in the various threads. Do you know if/how I can flash this with TWRP and keep the phone rooted?
I did the downgrade/giefroot/recovery process that doesn't need to unlock bootloader, so I'm sitting on the .93 build for now.
KnuckleSnackwich said:
Hi. I really appreciate your work putting a debloated rom together for us.
I'm quite new to Z3 roms and feel quite overwhelmed by all the technical info in the various threads. Do you know if/how I can flash this with TWRP and keep the phone rooted?
I did the downgrade/giefroot/recovery process that doesn't need to unlock bootloader, so I'm sitting on the .93 build for now.
Click to expand...
Click to collapse
Download and pre-root .77 with PRFCreator, flash it through recovery, re-flash recovery itself, switch off and then on again (dnt reboot)
I really like this since i hate bloatware. Is there any chance to get a lollipop version with minimal to no bloatware?
Will this work on the D6616?
any link for AndroPlus kernel? link in OP not working. thank you.
Related
THIS WILL NO LONGER BE MAINTAINED and is officially killed
go here if you want rw access and get the version without a kernel.(assuming you have a kernel installed that has aufs support)
IF YOU FLASHED THE UPDATE.ZIP THAT WAS ON THIS PAGE...PLEASE DO THE FOLLOWING:
You need to remove the init script and static busybox that were installed on your device. You have to do this in recovery mode since your rw access is not real.
Download the version linked to above and place it at the root of your sdcard.
open rom manager
select boot to recovery
boot to recovery while plugged in to computer
then from computer:
Code:
adb shell
mount /system
mount /data
rm /system/etc/init.d/99sysrw
rm /data/bin/busybox
umount /system
umount /data
exit
and from the phone:
flash BlaY0's update.zip you put on the sdcard
Really cool for your contributions.
I have no clue what you said, though. Will I be able to uninstall system apps with this? I'm guessin not as you were mostly speaking of partitions.
Lemme guess, brings ext2/3 etc together for something?
wow, best news that I have heard all day.
Ah! Thank you so much. I was just asking about this a couple weeks ago.
Sent from my T-Mobile myTouch 3G Slide using XDA App
does this mean that we can use metamorph now?
sorry if its a stupid question
Hayzie said:
Really cool for your contributions.
I have no clue what you said, though. Will I be able to uninstall system apps with this? I'm guessin not as you were mostly speaking of partitions.
Lemme guess, brings ext2/3 etc together for something?
Click to expand...
Click to collapse
No, You will not be able to uninstall apps with this (at least I don't think). It doesn't actually let you write to the /system partition, it just creates an overlay.
And No it does not even look for an ext partition, it just uses the data partition.
rodriguez27 said:
does this mean that we can use metamorph now?
sorry if its a stupid question
Click to expand...
Click to collapse
Don't really know, I haven't tried. Bear in mind however since it is on your data partition, space could be an issue. Any files changed would then be stored in /data/sysrw.
thanks for the quick info
I'm gonna try this out with Android Commander. With this I should be able to remove apps and delete files without restarting into recovery and mounting everything. Right?
dumfuq said:
No, You will not be able to uninstall apps with this (at least I don't think). It doesn't actually let you write to the /system partition, it just creates an overlay.
Click to expand...
Click to collapse
apparently I was wrong.
as a test I did...
Code:
rm system/app/com.amazon.mp3.apk
while the phone was booted and it worked!
Even after a reboot I do not have com.amazon.mp3.apk installed
It worked for me too, I used android commander booted and running and removed out of /system/apps android.tether.apk, mytouchmusic-signed.apk, and twitter.apk. I had a force close when I removed one thing (I am sure it was running in the background)
They all were gone after a reboot too, I was also able to update adfree just fine.
Any way this can be built into roms?
Thanks for the hard work!
dumfuq said:
No, You will not be able to uninstall apps with this (at least I don't think). It doesn't actually let you write to the /system partition, it just creates an overlay.
And No it does not even look for an ext partition, it just uses the data partition.
Don't really know, I haven't tried. Bear in mind however since it is on your data partition, space could be an issue. Any files changed would then be stored in /data/sysrw.
Click to expand...
Click to collapse
Hey dumfuq, thanks for this! Great idea on porting this badboy! One question though... from what I understood from the source thread is that will use the EXT. Partition for data if you have it right? So it won't break a2sd? I think I understood that correctly. Plus you need your kernel and that should make it work on any rom. I assume it won't overwite the OC kernel either. I'm excited to try this one out but I'm in the middle of rebuilding my rom so I can make a new backup (my old corrupted finally). I will test out as much as I can and let you know if different roms work. I should be done reinstalling by tomorrow (i have like 200 apps, lol!). This might turn out to be a good way to skip nandroiding and wiping all together if it turns out to work properly with a2sd/a2fat32... don't ya think?
sino8r said:
Hey dumfuq, thanks for this! Great idea on porting this badboy! One question though... from what I understood from the source thread is that will use the EXT. Partition for data if you have it right? So it won't break a2sd? I think I understood that correctly. Plus you need your kernel and that should make it work on any rom. I assume it won't overwite the OC kernel either. I'm excited to try this one out but I'm in the middle of rebuilding my rom so I can make a new backup (my old corrupted finally). I will test out as much as I can and let you know if different roms work. I should be done reinstalling by tomorrow (i have like 200 apps, lol!). This might turn out to be a good way to skip nandroiding and wiping all together if it turns out to work properly with a2sd/a2fat32... don't ya think?
Click to expand...
Click to collapse
This version is not the same as blayo's for the legend. It is closer to the desire one (although I used info from both).
Mine will not even try to detect an ext partition at this point, it just uses the data partition regardless of what is available.
Also nothing at all will get overwritten with this unless you happen to have an /system/etc/init.d/99sysrw file. It doesn't copy the kernel or modules, instead it just assumes you have a supported version . The only thing this update.zip does is add the script into init.d.
dumfuq said:
This version is not the same as blayo's for the legend. It is closer to the desire one (although I used info from both).
Mine will not even try to detect an ext partition at this point, it just uses the data partition regardless of what is available.
Also nothing at all will get overwritten with this unless you happen to have an /system/etc/init.d/99sysrw file. It doesn't copy the kernel or modules, instead it just assumes you have a supported version . The only thing this update.zip does is add the script into init.d.
Click to expand...
Click to collapse
I see... so basically, only cm based roms will work. Well, eventually, most us will move to cm based roms once bluetooth and a few minor bugs are worked out. Well, thanks for the info!
sino8r said:
I see... so basically, only cm based roms will work. Well, eventually, most us will move to cm based roms once bluetooth and a few minor bugs are worked out. Well, thanks for the info!
Click to expand...
Click to collapse
I haven't used them, but I think the newer sense roms support init.d scripts so you should be all good.
Working great on Fenix 2.0 with one of dumfuqs OC kernals...thank you much for this.
V2 is posted. It is essentially BlaY0's script for legend. I've only tested with no ext partition, but hopefully if you have one it will use it to store sysrw.
dumfuq said:
V2 is posted. It is essentially BlaY0's script for legend. I've only tested with no ext partition, but hopefully if you have one it will use it to store sysrw.
Click to expand...
Click to collapse
just so you guys now, v2 probably doesn't work for people with who want it on the ext. Blay0 fixed his though (to support non ext users), so I'll give it a look here soon.
Both versions do not work on stock kernel. Am I missing something? Should I use dumfuq kernel or cyanogenmod kernel in order to use this?
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
WHAT!!?? My slide has finally lost it's parasite, com.amazon.mp3 you are toast now. You and your friends kickback, talkback, soundback, twitter... not sure what else I erased, oh genie widget. Thanks dumfuq!! You are the man
Everyone that does this, make sure to check cyanogen's wiki on making a barebones rom so you don't delete something you actually need (of course you did make a nandroid before doing this so no need to worry if you do).
You won't actually delete anything... overlay just makes you (and system) think it is deleted.
flash a different rom on it or do I have to do anything to the current settings. I'm a total noob, its my first android phone.
In settings>about phone>
firmware version = 2.2
kernal version = 2.6.32.9
build number = nero v4.1 twiz edition by Team whiskey
(does build number indicate the current rom?)
I read around this forum and it said that you should ask if you're not compeletely sure about something (or else it could brick!?). So do I just follow the rom flash guide and everything should be ok or do I have to change any settings or permissions of the current rom to make it work?
Also does flashing a rom delete all the apps and their associated cache/settings/etc? Anything I can use to back this stuff up so if I plan to go to a different rom, everything can come with me without any problems? (I guess it would take pretty long to download/install everything and synchronize the settings every time I flash a new rom).
Thanks in advance.
Yes build number indicates rom
Most roms wipe your phone
Download titanium backup from the market to backup apps but don't use it to restore system apps
Before you do anything, please check both guides in my signature. It will help you a lot.
This is what I would do (after you read). These steps basically are giving you a new phone.
Titanium Backup and nadroid backup
move all files (internal/external to pc) (not needed, but can't hurt)
format both internal and external cards (not needed, but may help)
download new rom, move to sdcard/
reboot into CWR
factory wipe, wipe data, wipe dalvik
flash new rom
wipe data/dalvik (not a factory wipe)
reboot... wait 10 minutes (dont touch the phone)
reboot
restore apps with Titanium Backup
reboot
enjoy
As far as roms go, I love Trigger 2.7.1. It's pretty amazing. There are newer 2.2.1 roms out, but they are not perfect yet, great roms, but not like Trigger yet.
s15274n said:
Before you do anything, please check both guides in my signature. It will help you a lot.
This is what I would do (after you read). These steps basically are giving you a new phone.
Titanium Backup and nadroid backup
move all files (internal/external to pc) (not needed, but can't hurt)
format both internal and external cards (not needed, but may help)
download new rom, move to sdcard/
reboot into CWR
factory wipe, wipe data, wipe dalvik
flash new rom
wipe data/dalvik (not a factory wipe)
reboot... wait 10 minutes (dont touch the phone)
reboot
restore apps with Titanium Backup
reboot
enjoy
As far as roms go, I love Trigger 2.7.1. It's pretty amazing. There are newer 2.2.1 roms out, but they are not perfect yet, great roms, but not like Trigger yet.
Click to expand...
Click to collapse
+1 great advice here and also a fellow trigger user. Only thing I would add is to use the overstock version... love it myself.!
Sent from my SGH-T959 using XDA Premium App
Thanks guys, I will follow those steps and install trigger. Btw, don't know a lot of the xda terminology yet, what does overstock mean and what are the differences compared to the normal non overstock? Thanks.
btw "download new rom, move to sdcard/" means the internal storage right, not my external microsd card?
as to the overstock its just a specific version of the trigger 2.7.1 rom. You will find the link in the trigger post here
http://forum.xda-developers.com/showthread.php?t=921453
look for this section
Code:
Download
>>>>>>Download Trigger 2.7.1<<<<<<
Like the rom? Hit Thanks or Donate!
Check Sums - Trigger 2.7.1
MD5: 2D5E180456E0FEDABB7D4DAE7CCD52EE
SHA-1: 2DF446330B998C7FAB777A2231A20C32DA108BA1
>>>>>>Download Trigger 2.7.0 => 2.7.1 Upgrade<<<<<<
[B]
>>>>>>Download Trigger 2.7.1 w/OverStock Kernel<<<<<<[/B]
I will refrain from answering your other question as I am still in the learning process myself and dont want to mislead you.
^ it is a kernel in the development section. It is essentially a stock kernel (not overclocked) so its very stable... the benefit is that it converts the file system to EXT4 (Trigger already does this) and that is a LOT faster.
It also has Voodoo Color (put your brightness at full and be in awww of your screen).
It also has Voodoo Sound (AMAZING quality from your headphones... requires the app from the market, free).
It also has BLN.... since our phone doesnt have LED for notifications, you can use this app to know when you have a notification, it lights up the buttons (ie, home, menu, etc). Also a free app, and a paid version with more features.
SO.... yeah, essentially a stock kernel with a LOT of very cool features. It is also what I run with Trigger.
edit, forgot, it also has a ram hack to free up more ram....
ok cool i'll go with the overstock then. So when I plug in the phone and enable the usb storage, on my computer it shows two drives. One is my external microsd card and one is the phones drive. I have to put the rom on the root of the phone's drive right?
Correct, that would be scard/ if you were using a file system on your phone to move the file. But yes, move to internal root folder.
edit, please read the guides!
s15274n said:
edit, please read the guides!
Click to expand...
Click to collapse
cant stress that enough. I did exactly that, followed his guides and even though I messed up it was well after I was finished and it answered all of my questions and saved me a lot of hassle.
I got everything to work. Thanks again for the help guys, I really appreciate it.
Nice. Well, that didn't take long. Enjoy.
s15274n said:
Nice. Well, that didn't take long. Enjoy.
Click to expand...
Click to collapse
And welcome to the Trigger club... Hope you enjoy your stay.
thanks again guys. So I'm on my second day with this trigger rom and I've encountered some bugs, but I can't post in the developer section until i get 10 posts
1) I can't save images from the browser or download
2) The gallery loads insanely fast, but I have an image that is very high res yet when I zoom in to that image it still looks pixelated and not the same quality as when I viewed it in my previous rom. Its the same picture so that hasn't changed, I don't know why its not giving a high res view when zooming in.
Hello all devs, I have a suggestion that I think many people that cant unlock the bootloader will think very nice.
The sugestion is that the devs if they time to make a version like JJs hybrid rom for locked bootloaders.
I have also tried the Miui rom, and I removed the format script and boot.img and it booted fine without any major problems.
So my sugestion is that the devs makes their roms for stockkernel for people with locked bootloader, and makes a deletion script that removes all the files from the old rom.
Devs, what do you think about my idea?
Thats not possible to remove format script...
If you dont format system partition, it will be overloaded with applications and frameworks from Old and New ROM... the two ROM appz might not share the same sign keys... that would result in Bootloop or Series of FCs on install...
jjdoctor said:
Thats not possible to remove format script...
If you dont format system partition, it will be overloaded with applications and frameworks from Old and New ROM... the two ROM appz might not share the same sign keys... that would result in Bootloop or Series of FCs on install...
Click to expand...
Click to collapse
Here are a solution that I think maybe works:
First create a homemade format script that removes all the stuff on partiation, but it doesnt run the format options, it just deltes everything manually from recovery.
And then just remove the format script from the roms zipfile and remove the boot.img too.
Then just resign the zip file with sign by enyblock.
Thats should work, maybe somebody can try it?
DevStaffAndroid said:
Here are a solution that I think maybe works:
First create a homemade format script that removes all the stuff on partiation, but it doesnt run the format options, it just deltes everything manually from recovery.
And then just remove the format script from the roms zipfile and remove the boot.img too.
Then just resign the zip file with sign by enyblock.
Thats should work, maybe somebody can try it?
Click to expand...
Click to collapse
thats practically not possible either...
MIUI, CM9 have different appz and framework...
applications aside, who has enough time to write a delete script for more than a thousand lib and other system files?..
I am trying to find out the files that don't load on statup after installing a flashable zip on Locked bootloaders... that is better way of finding a solution..
jjdoctor said:
thats practically not possible either...
MIUI, CM9 have different appz and framework...
applications aside, who has enough time to write a delete script for more than a thousand lib and other system files?..
I am trying to find out the files that don't load on statup after installing a flashable zip on Locked bootloaders... that is better way of finding a solution..
Click to expand...
Click to collapse
But isnt there a way to just remove all folders using recursive deletion, isnt that the easiest way to make a deletion script?
And then just remove the format script and boot.img.
With my my solution ive managed to run the miui based on offcial semc ics on my Xperia Ray it worked fine.
Me: Hmm.. What is this thread?
Self: Looks to be someone requesting something from Developers.
Me: Oh - that's nice. Did they say please?
Self: Yeah looks like they kinda did. But looks like they posted it in Development!!!
Me: DOH! Is there any actual development taking place?
Self: No! It's just a discussion thread!
Me: :facepalm: Well looks like it needs to be moved to General.
Self: Hope they learn their lesson.
jerdog said:
me: Hmm.. What is this thread?
Self: Looks to be someone requesting something from developers.
Me: Oh - that's nice. Did they say please?
Self: Yeah looks like they kinda did. But looks like they posted it in development!!!
Me: Doh! Is there any actual development taking place?
Self: No! It's just a discussion thread!
Me: :facepalm: Well looks like it needs to be moved to general.
Self: Hope they learn their lesson.
Click to expand...
Click to collapse
hahahahahahahaha
you make my day hahahaha
This is why most custom ROMs require custom kernel
Needs unlocked bootloader
(actually hybrom does not contain a boot image.Thus, when you install hybrom you don't mess with your boot image at all.BUT recovery from nAa is installed in /system and while system is formated during the installation of hybrom,recovery messes with it self.That's why unlocked bootloader and a custom kernel with recovery is necessary for now to install hybrom)
Click to expand...
Click to collapse
Source: http://forum.xda-developers.com/showthread.php?t=1373435
It means, that if Recovery is installed in /system folder, and you want to install custom ROM, which (mostly) replaces the system folder, Recovery would be removed and would end up in complete stop with bootloop.
If Recovery is installed in the kernel, then the whole /system partition can be removed without affecting the Recovery at all.
Also, stock kernels have quite low functionality, that's why it is not widely used.
Someguyfromhell said:
This is why most custom ROMs require custom kernel
Source: http://forum.xda-developers.com/showthread.php?t=1373435
It means, that if Recovery is installed in /system folder, and you want to install custom ROM, which (mostly) replaces the system folder, Recovery would be removed and would end up in complete stop with bootloop.
If Recovery is installed in the kernel, then the whole /system partition can be removed without affecting the Recovery at all.
Also, stock kernels have quite low functionality, that's why it is not widely used.
Click to expand...
Click to collapse
But I restored my nAa CWM backups several times and that as I know formats the system before the restore..
Yeah, about the boot.img, can we dont just mod the chargemoon to load the rom?
Or charger?
DevStaffAndroid said:
Yeah, about the boot.img, can we dont just mod the chargemoon to load the rom?
Or charger?
Click to expand...
Click to collapse
Loading the ROM is not the problem, it is the functionality.
Modifying stock kernel can be done, but if you want to make it work, you have to unlock bootloader to install it also.
Someguyfromhell said:
Loading the ROM is not the problem, it is the functionality.
Modifying stock kernel can be done, but if you want to make it work, you have to unlock bootloader to install it also.
Click to expand...
Click to collapse
But I mean the roms that are built for stockkernel like some of the miui roms?
Skickat från min Xperia ray via Tapatalk 2
Depreciated!! See this thread for the new recommended package. All of my instruction below is still valid, just use the new package from thread linked here.
http://forum.xda-developers.com/showthread.php?t=3234422
~~DISCLAIMER~~Flashing roms, kernels, and mods come with NO guarantee, NONE, ZILCH, NADA . . Do NOT use this package if you do not grasp and understand this concept. You have been warned.
This is a recovery flashable that will extract your boot.img, unpack all pieces, modify fstab.shamu to disable forced encryption, repackage, and flash boot.img back to system. It does NOT actually unencrypt your device. More on that later.
It will work on ANY kernel for this device, regardless of whether it is the stock kernel, or a custom ROM kernel. Also to date, it has shown to work on any version of android . . it is essentially future proof (unless google throws us a major curve ball in the future and radically alters how encryption is triggered at first boot).
Why use this? Who is this package for?
-If you are running 100% Stock Rom, but have a recovery installed and wish to unencrypt your storage. No root needed.
-Running a custom kernel you like, but it forces encryption and you want to change that.
-Currently unencrypted but want to flash a rom that uses FORCEENCRYPTION by default (cyanogenmod12).
-Just bored and want to toss the dice and see what happens.
That is pretty sweet right? Now you can flash anything and as long as you flash this afterwords, you wont have to worry about booting a rom and seeing that dreaded "Encrypting" screen anymore.
What doesn't this do?
-Well, to be blunt . . it does NOT actually UNENCRYPT your device. You will have to bite that bullet on your own, but I will offer some advice on that front later.
Changelog:
03/30/2015
Remove my ill advised attempt to auto patch nightlies, not possible
01/12/2015
Initial Build/Release
Includes fully working patch to initrd, specifically fstab.shamu to revert FORCEENCRYPTION by default.
Buglist:
Auto patch support removed, would never work anywayaddon.d support not currently working - fix is to flash this package with every nightly to preserve unencryption
How to download and install?
Download - NO_FORCE_ENCRYPT_shamu_v1.0-signed.zip
Reboot Recovery - TWRP only has been tested as working
Select "Install" and navigate to where ever you stored that file . . likely /sdcard/downloads/
Take a deep breath and wait for it to finish.
TADA . . done. Reboot and Profit!!
NOTE: You can feel free to flash this as part of a line of other packages.
Example: You are already unencrypted and want to flash Cyanogenmod 12 (assumes you have all packages downloaded already)
-TWRP factory reset (optional but recommended when coming from another rom)
--TWRP's built in factory reset function does quite well, but if you are like me and want a clean slate . .
---TWRP>Wipe>ADVANCED WIPE> and check System, Data, Cache (will leave internal storage intact). This is recommened specifically in conjunction with switching GApps.
-Install> and select all packages at once. I recommend the following order . . Rom, then my Kernel Patcher, then SuperSU (optional), then GApps last.
That was certainly easy right? Well the truth is, unless you are already unencrypted . . nothing will be different. You will still be encrypted. Bummer right? But that is where these next steps come in. They will give you the options available to reach the fabled unencrypted status!!
Below are the only three options I know of unencrypt once you are running a patched kernel. Select one below that works for you.
~~WARNING~~
The below methods WILL erase EVERYTHING from data, including your INTERNAL STORAGE. Backup all important files, pictures, etc before proceeding. You have been told!!
-Go to Android>Settings>Backup & restore>Factory data reset (may not work properly with a custom recovery installed)
-Reboot to recovery and go to TWRP>Wipe>FORMAT DATA . . type "yes" to confirm
-Reboot to bootloader and type . .
Code:
fastboot format userdata
[note - I originally said to use the fastboot erase userdata function. This caused a recovery bootloop. Switching to "format" instead solved this issue. Thanks @aussie1234 for pointing this issue out to me]
Edit: make sure you boot android first after unencrypting before going into recovery. This will allow the proper creation of multiuser partitions, otherwise, twrp will not use the proper /data/media/0/ as root of storage.
Some may notice there is an experimental addon.d included. This NOT WORKING YET. DO NOT TRY AND USE IT. Not quite sure yet where in the chain it is broken, but that will be a problem for another day. In theory it should, but . . read the "disclaimer" at the top of this post. The idea here is to be able to flash nightlies as they roll out without having to re-apply this patch manually every time. This function is NOT supported on Stock Roms. If you try it and it works, let me know. Do NOT come yelling to me that it did not work and crying that you are now encrypted again. No whiner babies allowed.[REMOVED: didn't work and caused conflicts with some packages]
At the core of this tool is a script build by @dk_zero-cool which can be found . . [DEV][INITRD][2013-10-25] Injector - An Android Ramdisk Injection Tool
Ultimately, this package is as much his as it is mine. It is his magic script that did the hard part, I just put it to work in a new way.
Please don't share this package directly, link them back here if needed. That way, they can get proper support and instruction for its use.
Also thanks to @rascarlo . . his github made it easy to find what needed modded.
Nice! Now just to double check, im unencrypted so if i flash cm12 and this cm12 wont encrypt my phone while still using cm's kernel?
That is correct. In my tests it has worked just fine that way.
Edit: In fact, I just tested this exactly and works as expected.
On a side note, I can confirm that addon.d support does NOT work - do not attempt it. I updated the OP to reflect this and add a stronger warning. Right now you MUST flash this everytime you flash a rom that forces encryption.
Just what the doctor recommended for a flash-addict like my self....
Thanx :silly:
. . . uploaded from a hand-held Killer WHALE
Works like a charm much alohas bradah hixanthus
So say I flash a ROM. I want to do ROM, kernel, your boot.IMG, the gapps followed by a factory reset/erase user data if I understand correctly?
Example : DirtyUnicorns then leankernel your zip and then gapps
bmwh0r3 said:
So say I flash a ROM. I want to do ROM, kernel, your boot.IMG, the gapps followed by a factory reset/erase user data if I understand correctly?
Example : DirtyUnicorns then leankernel your zip and then gapps
Click to expand...
Click to collapse
Well if you flash lean, don't bother with my flashable, as lean is already set for no force encryption isn't it?
hlxanthus said:
Well if you flash lean, don't bother with my flashable, as lean is already set for no force encryption isn't it?
Click to expand...
Click to collapse
I'm not sure anymore. Will look. I tend to break things when flashing because I don't read closely. On my vzw note 3, I was well known to break everything. Kinda scary now that I have a nexus lol
Yes you're correct. I wonder why I can't get decrypted then?
bmwh0r3 said:
I'm not sure anymore. Will look. I tend to break things when flashing because I don't read closely. On my vzw note 3, I was well known to break everything. Kinda scary now that I have a nexus lol
Yes you're correct. I wonder why I can't get decrypted then?
Click to expand...
Click to collapse
Just do the factory rest then if already encrypted unless data is removed it will stay encrypted
Sent from my Nexus 6 using Tapatalk
hlxanthus said:
Well if you flash lean, don't bother with my flashable, as lean is already set for no force encryption isn't it?
Click to expand...
Click to collapse
bmwh0r3 said:
I'm not sure anymore. Will look. I tend to break things when flashing because I don't read closely. On my vzw note 3, I was well known to break everything. Kinda scary now that I have a nexus lol
Yes you're correct. I wonder why I can't get decrypted then?
Click to expand...
Click to collapse
hlxanthus said:
Below are the only three options I know of unencrypt once you are running a patched kernel. Select one below that works for you.
~~WARNING~~
The below methods WILL erase EVERYTHING from data, including your INTERNAL STORAGE. Backup all important files, pictures, etc before proceeding. You have been told!!
-Go to Android>Settings>Backup & restore>Factory data reset
-Reboot to recovery and go to TWRP>Wipe>FORMAT DATA . . type "yes" to confirm
-Reboot to bootloader and type . .
Code:
fastboot erase userdata
Edit: make sure you boot android first after unencrypting before going into recovery. This will allow the proper creation of multiuser partitions, otherwise, twrp will not use the proper /data/media/0/ as root of storage.
Click to expand...
Click to collapse
https://github.com/imoseyon/leanKernel-shamu/commit/58ac4f97d882414bdea35d0d1ef0cd6f9027a3bb
Yes, lean kernel doesnt force encryption. If you are currently on lean kernel, so one of the three methods to unencrypted from above (quoted from my OP)
This worked great for me! Thank you SO much!
jtorress said:
This worked great for me! Thank you SO much!
Click to expand...
Click to collapse
It really is that simple isn't it? Glad it was of help!!
Mine is encrypted n6 running cm12 nightly .
So flashing this will format my storage or just data partition ?
I dont wanna loose my personal data's :/
This will not wipe anything. The package only turns an encryption forced kernel into a no force encryption kernel. It is then up to you to follow one of the three options from my OP to reach actual unencryption status.
But you can relatively easily do it, though it will take a little time. Boot to recovery, flash my package, and then create a nandroid backup. Then backup the entirety of your internal storage to your PC or OTG storage device. Once that is done, do one of the 3 methods to unencrypt. Once you do that, boot android (this step is important as it builds proper multiuser partitions) then restore data to your internal storage. Then boot back to recovery and restore your nandroid backup. That will take you back to the exact point you were before but now unencrypted.
I did all steps,but it still shows me that I'm encrypted. What am I doing wrong?
indigo888 said:
I did all steps,but it still shows me that I'm encrypted. What am I doing wrong?
Click to expand...
Click to collapse
Walk me through in your own words what you did. Maybe we can figure out where you went wrong.
hlxanthus said:
Walk me through in your own words what you did. Maybe we can figure out where you went wrong.
Click to expand...
Click to collapse
I flash package and made nandroid backup in recovery.Then made factory reset and boot Android till welcome select language. Then switched off into recovery and restored backup....
And when you say you did a factory reset, how did you do that? A twrp factory reset will not work as it leaves the internal storage in tact. I am very explicit on the 3 ways to do this part (at least I thought I was).
hlxanthus said:
And when you say you did a factory reset, how did you do that? A twrp factory reset will not work as it leaves the internal storage in tact. I am very explicit on the 3 ways to do this part (at least I thought I was).
Click to expand...
Click to collapse
I did it from menu/settings/backup and reset.
indigo888 said:
I did it from menu/settings/backup and reset.
Click to expand...
Click to collapse
Might be worth trying the other two methods as well. TWRP's format data method and the fastboot userdata method are pretty thorough. Should get you up and running
I have a Nabi 2 and I am fairly new at this. I tried to root using the jmzrootpackage path and was able to install twrp 2.2.2.1. even though installation had some fails and differed from the tutorial. I did not update the product version with OTA updates and it is at version 1.0. Now with twrp installed OTA updates do not work. So, I am trying to go with a fresh start and recover it to stock so I can do OTA updates and re-root. However, I am not sure how to do this. I tried following this tutorial http://forum.xda-developers.com/showthread.php?t=2074501, but this links to the downloads are broken.
Thank you for any help you may offer.
Okay somewhat figured it out
I updated twrp using this guide here http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119 .
Then, luckily I found another user with a Nabi 2 with Disney that was in a similar situation and followed the guide there http://forum.xda-developers.com/nabi-2/help/nabi-2-disney-return-to-stock-dummies-t3212480 .
Now I am updated to 4.4.2 KitKat and it seems I am up to date on the OTAs since it is not showing any new updates available. I also did not install SuperSU when it asked at the end of my stock recovery because it wanted to root my Nabi when I need it to be unrooted for potential OTAs.
I guess I am moving onto figuring out how to remove all the bloatware.
Okay, since I did not install SuperSU I am guessing I did not root it at all. Is there a process to root with SuperSU or do I have to restore with the stock again. I wanted the Nabi 2 to be a pure android tablet as possible, so I deleted as many non-Gapps as possible. I am left with the usual Nabi ones that are not removable without root. So should I live with the Nabi Apps or root it and remove them. Any tradeoffs once rooted?
BlueMarble said:
Okay, since I did not install SuperSU I am guessing I did not root it at all. Is there a process to root with SuperSU or do I have to restore with the stock again. I wanted the Nabi 2 to be a pure android tablet as possible, so I deleted as many non-Gapps as possible. I am left with the usual Nabi ones that are not removable without root. So should I live with the Nabi Apps or root it and remove them. Any tradeoffs once rooted?
Click to expand...
Click to collapse
You don't necessarily need "root". You can delete what you want through TWRP.
You can root by downloading the zip
https://download.chainfire.eu/696/supersu/
Then install the zip in TWRP. There aren't really any bad trade offs to have root, at least as far as losing functionality.
As far as TWRP goes. It actually can handle a lot of the OTA's just not all of them.
aicjofs said:
You don't necessarily need "root". You can delete what you want through TWRP.
You can root by downloading the zip
Then install the zip in TWRP. There aren't really any bad trade offs to have root, at least as far as losing functionality.
As far as TWRP goes. It actually can handle a lot of the OTA's just not all of them.
Click to expand...
Click to collapse
I was able to delete some in /data/apps. It was grouped with some Gapps and personally downloaded apps. There were some apk files that I could not find through twrp's file manager. For example, there is a Cinderella ebook apk that I cannot find along with other Nabi apps. I checked /system and only came upon an empty /bin folder. Also, did not see any /vendor folders either. Nothing in addon_res as well.
Thanks aicjofs, your posts have been helpful along the way.
BlueMarble said:
I was able to delete some in /data/apps. It was grouped with some Gapps and personally downloaded apps. There were some apk files that I could not find through twrp's file manager. For example, there is a Cinderella ebook apk that I cannot find along with other Nabi apps. I checked /system and only came upon an empty /bin folder. Also, did not see any /vendor folders either. Nothing in addon_res as well.
Thanks aicjofs, your posts have been helpful along the way.
Click to expand...
Click to collapse
In TWRP look in the mount tab and make sure "addon" is mounted(checked)
Then look under just /addon in the root.
Edit: same applies to "system", make sure it's mounted. That's why those directories are empty.
aicjofs said:
In TWRP look in the mount tab and make sure "addon" is mounted(checked)
Then look under just /addon in the root.
Edit: same applies to "system", make sure it's mounted. That's why those directories are empty.
Click to expand...
Click to collapse
Thank you, you are the man! They were mostly in /system/priv_apps. However after deleting everything with fuhu attached to it, the parent mode home screen has droid icons for all the deleted nabi apps. They cannot be moved to a trash can.
BlueMarble said:
Thank you, you are the man! They were mostly in /system/priv_apps. However after deleting everything with fuhu attached to it, the parent mode home screen has droid icons for all the deleted nabi apps. They cannot be moved to a trash can.
Click to expand...
Click to collapse
There is an app cache you can clear that will probably remove them. I do not know which one though.
aicjofs said:
There is an app cache you can clear that will probably remove them. I do not know which one though.
Click to expand...
Click to collapse
I was able to clear them by going to Settings>Apps>All>Launcher>Clear Data. Google Play, Google Folder, and Settings were left over, including a small nabi launcher on the bottom. I tried to see if I could get rid of the Parent mode home screen. It seems to be tied to the Launcher system app and requires a root. I deleted a Launcher2.apk before and the system did not fully boot and I had to restore. I also tried to use some App disabler/feezers but Launcher did not show up in either.
Decided to install Nova launcher over it. It is still in the background running, but Nova has automatically replaced it.