Related
Why oh why can I not get anything to boot on my gosh darn incredible? I've tried everything except making it all work.
I want so badly to get something to boot, but alas it never happens. Stuck at the white screen is as far as I ever get. I don't even get the satisfaction of seeing a bootloop, at least then I'd be seeing some sort of progress. Its disheartening. I've tried all kinds of roms and system dumps to no avail.
There must be something I'm doing wrong, what?
Sent from my ADR6300 using XDA Premium App
Do wipe data and cache before flashing?
Yeah. I did manage to get a boot loop with the huashan gingersense leak. So some progress.
Sent from my ADR6300 using XDA Premium App
Give more detail, and I might be able to help. What steps are you taking to port the ROM?
You need a kernel from your device at least. You also need to change some entries in build.prop and rename the init.devicename.rc to your device's name and not the original ROM's. Then you need to replace any device specific drivers and libs with ones from your device. And then, it still might not work. There's a lot going on here.
I'm assuming that by 'porting' you mean taking an existing ROM from another device and making it work on yours. The word has a different meaning also, which is take AOSP/CM/whatever and make it work on a device that it doesn't currently work on.
gnarlyc said:
Give more detail, and I might be able to help. What steps are you taking to port the ROM?
You need a kernel from your device at least. You also need to change some entries in build.prop and rename the init.devicename.rc to your device's name and not the original ROM's. Then you need to replace any device specific drivers and libs with ones from your device. And then, it still might not work. There's a lot going on here.
I'm assuming that by 'porting' you mean taking an existing ROM from another device and making it work on yours. The word has a different meaning also, which is take AOSP/CM/whatever and make it work on a device that it doesn't currently work on.
Click to expand...
Click to collapse
Thanks I've swapped the boot.img, changed the build.prop, didn't rename the init file I instead copied over it. Copied the wifi modules, all the missing libs, the usr folder, bin folder, etc folder, and xbin.
Problem is when I change the libs it never gets past the splash, but when I change just the boot.img it'll boot loop.
And yes I mean from one device to another.
Sent from my ADR6300 using XDA Premium App
Mr. Rager said:
Thanks I've swapped the boot.img, changed the build.prop, didn't rename the init file I instead copied over it. Copied the wifi modules, all the missing libs, the usr folder, bin folder, etc folder, and xbin.
Problem is when I change the libs it never gets past the splash, but when I change just the boot.img it'll boot loop.
And yes I mean from one device to another.
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
Personally, I wouldn't copy entire folders over. I also wouldn't copy the boot.img over. I'm not saying that it won't work in some cases. It might. I've always swapped the kernels inside the boot.img, and renamed the device specific init file. Then, I would compare the init files from an existing ROM for my device with the init files from the ROM that I'm trying to port and see if there are any lines that are device-specific. If the init file is trying to start up something that doesn't exist on my device, then it doesn't make sense to keep that line. On the other hand, there might be a line that changes something for that ROM that IS needed.
This same thing kind of goes with the libs and other files too. You might have one lib that relies on another lib being there. And it might need a particular build of that lib. And other files might call certain libs. This is one reason that building from source generally works better over the long run than trying to get one device's ROM to work on another.
You have device specific and ROM specific things going on at the same time, so wholesale copies tend to miss one or the other. Plus it's nice to dig in and get an idea about what's going on.
Also, if you can get adb access while it's booting, grab a logcat. It might give you an idea about what is failing.
I re-did the boot.img by replacing the kernel and renaming (in this case) init.hua_shan.rc to init.inc.rc. It gets past the "HTC Incredible" splash. So, that's a plus.
I did get a logcat, as I always do when I flash a new rom that hasn't been tried before. I use pastebin so take a 'gander' at it if you will.
From the looks of it Alsa, bouncycastle, and audio libs are having problems. Oh, and the bootanimation.zip didn't get dumped from the Huashan, but it's no big deal.
http://pastebin.com/VVxufgQL
Oh, and thank you for the help you have provided thus far.
Mr. Rager said:
I re-did the boot.img by replacing the kernel and renaming (in this case) init.hua_shan.rc to init.inc.rc. It gets past the "HTC Incredible" splash. So, that's a plus.
I did get a logcat, as I always do when I flash a new rom that hasn't been tried before. I use pastebin so take a 'gander' at it if you will.
From the looks of it Alsa, bouncycastle, and audio libs are having problems. Oh, and the bootanimation.zip didn't get dumped from the Huashan, but it's no big deal.
http://pastebin.com/VVxufgQL
Oh, and thank you for the help you have provided thus far.
Click to expand...
Click to collapse
Did you also change the ro.board.platform parameter in build.prop so that it matches the chipset name originally on your device?
Also, the next time you flash this ROM, dump the recovery log file before you reboot. This may show you errors encountered during the flash which were not shown in the normal output. A common error is porting a large ROM - such as Desire HD's - to a device with a small system partition in comparison. A workaround is to remove unneeded apps under system/app to reduce size of the ROM.
You may also want to try the Porting option in my Android Kitchen, it does the renaming, kernel and driver modifications for you.
dsixda said:
Did you also change the ro.board.platform parameter in build.prop so that it matches the chipset name originally on your device?
Also, the next time you flash this ROM, dump the recovery log file before you reboot. This may show you errors encountered during the flash which were not shown in the normal output. A common error is porting a large ROM - such as Desire HD's - to a device with a small system partition in comparison. A workaround is to remove unneeded apps under system/app to reduce size of the ROM.
You may also want to try the Porting option in my Android Kitchen, it does the renaming, kernel and driver modifications for you.
Click to expand...
Click to collapse
I've had a busy past couple of days, but I'll check into the recovery dump and see what's up. I did change the ro.board.
I was trying to abstain from your porting tools, no offense, only so I could do it manually. Just trying to gain more experience, I guess, and learn. Your kitchen is excellent. I use to set up my environment and deodex among other things. The porting tool, though greatly eases the pain and shorten the manual labor ( yes lazy America) , take the learning curve out, a bit. But I guess I could take a look at the script to see what's going on too. Lol.
EDIT#1 - So I just tried to flash my rom. However, it wouldn't, because for some reason my phone is very particular about how one copies files over to the sd card. For one, you have to have the phone booted up, MIUI GB latest in my case, and mount usb storage. If I mount it through recovery, it corrupts my sd card, too bad I wish I knew that earlier. It's a PITA really...Ubuntu...
But, as phone WAS:
Hboot - 0.92
Radio - 11.19
Ship S - OFF
I tried copying and flashing through recovery. Fail as usual. So, I was gonna boot up into MIUI and try to copy from there, and got the infamous 5-vibe and twinkle.
I tried several times to boot into MIUI, but after many battery pulls, I figured out something ODD. In the bootloader the first couple of times it skipped the scanning process, then it started scanning again. Upon further inspection:
Hboot - still 0.92
Radio - still 11.19
Ship S - ON <---NOT A TYPO
Why? I haven't a clue. I tether my phone, so I got it booted, yay, but to do it, my sd card has to be removed and my usb plugged in, then turn on. So, my next edit will be a progress update. AFTER I s-off again ( that sounds kinda dirty, lol ), and re-format my sd. Also, my phone thinks it's charging...ITS UNPLUGGED. Lol, infinite-charging batteries, it's the future...
Sent from my ADR6300 using XDA Premium App
So...Good news is I got another incredible with amoled screen
Bad news I got another incredible with nothing on it, or rooted :-( But I rooted it before I even activated it with *228
But, alas, I still have all of my work on my computer. I managed to back it up before my phone crapped out. Plus I kinda get to start from the beginning so I can be more observant, and particular.
So, back to work...will update tonight.
Edit 1 - So after some more tinkering I've managed to fix some issues, but others have popped up namely the HTC Sim card authentication, which I have no idea about, yet, bouncycastle.jar is being stubborn by not fiding its classes, and libaudioflinger.so is failing to link to libsystem_server.so which in turn fails the link to libandroid_servers.so. Same three problems as before it seems.
Here's a pastebin of the logcat.
http://pastebin.com/QYde7fuQ
I'll keep tinkering about and see what I can come up with. Hopefully I'm closer to getting this thing booted up than I think.
Hi Everyone,
Since our wonderful Froyo roms came out, I've noticed that the bootup sound has vanished, and essentially been removed from the kernels. I've been trying to figure out a way to kludge it back in, but I haven't had any luck.
I looked at what the CM roms have done for this, and it appears that somehow they have a "stagefright" command line utility that lets them play mp3 files from shell scripts. Unfortunately, I can't seem to find a similar utility that works on a touchwiz based rom (like Superclean or Blackhole). I even tried to "borrow" the binary from JT's CM6 beta, but no luck there - when run, it complained about not being able to link, which I suspect is because a bunch of libraries are different between the two roms.
So I'm asking if any of you developers might know how or be able to build a stagefright tool like the one that appears in CM6, but so that it will work on a TW based rom? If I could get ahold of that, I think I can make boot sounds work again.
Thanks!
Have you tried to odin the stock eb01 zimage? I know for a fact that supports it.
You can find the stock md5 file in adryns ec01 thread. And you can extract those files and use heimdall to flash only the zimage.
Not sure if it still supports it after flashing a different rom.. I'm away from my computer or ide try it. Also if you have voodoo enabled make sure to disable it before doing anything.
Sent from my SCH-I500 using XDA App
When I installed Kaosinate either v2 or v3 (I don't think v4), it didn't have a bootanimation in there.
Instead of any SAMSUNG or anything like that, I watched the raw boot process, text and all (like I've seen in maybe a Linux system before on bootup).
It looked a lot like a logcat dump while booting up.
I want that back, and I haven't found a ROM or a mod to do so, at all.
Someone seemed to think that init.rc would need to be modified to make it happen, but I want to find out how!
I've searched around and someone is still trying to find this in the Nexus One forums, and was satisfied with a custom bootanimation (which I am not)
http://forum.xda-developers.com/showthread.php?t=646279
I am wondering if I would be able to modify a flashable .zip with the init.rc from Kaosinate v3, and then throw it into jt's CM 6.2.0 ROM that I'm using, and find any success?
Has anyone else looked into, desired, or completed this process?
You need to rebuild the kernel to enable it. It requires some code changes as well as a few config changes. I also don't know if you can use boot animations after making the changes.
So it is a situation where I need to use a specific kernel then..
I think that this is what it looks like, when this guy gets Android on his iPhone, and you watch the boot process.
Good shot of it at like 1:52:
http://www.youtube.com/watch?v=5yO2KQHkt4A
Yeah, it is kernel specific, and by default, the stock Samsung source does not support what you want, so you'd have to make a few edits and also change some config options related to the changes as well.
Can you let us know if your out there using tmobile UK atrix, please!
Swyped from 'mount' Olympus
Bump
Swyped from 'mount' Olympus
nitrox1 said:
Can you let us know if your out there using tmobile atrix, please!
Swyped from 'mount' Olympus
Click to expand...
Click to collapse
i just ordered a unlock code for my atrix from cellunlock.net. its been 2 days as of now. i have tmobile us, still tmobile though lol
stratax said:
i just ordered a unlock code for my atrix from cellunlock.net. its been 2 days as of now. i have tmobile us, still tmobile though lol
Click to expand...
Click to collapse
Thank you for your reply. But I'm really looking for the UK Tmobile, sbf, or understanding of it.
Ps check out our uk orange thread, for a much cheaper unlock, and within 10 min!
Swyped from 'mount' Olympus
Bump
Swyped from 'mount' Olympus
im using a t-mobile uk atrix, got it yesterday
karl0ss said:
im using a t-mobile uk atrix, got it yesterday
Click to expand...
Click to collapse
Have a look in the about phone part and post up if you can
system version
Baseband version
Build number
system version - Version.4.2.23.MB860.T-Mobile.en.GB
Baseband version - N_01.92.00R
Build number - OLYEM_U4_2.2.3
any idea how i can root it? side loading apps seems to work without any hacks, as I was able to install some apks I had laying around on my dropbox, and I have installed some using Android Commander...but I can't work out how to root it, does GingerBreak NEED a real sd card inserted to work?
karl0ss said:
system version - Version.4.2.23.MB860.T-Mobile.en.GB
Baseband version - N_01.92.00R
Build number - OLYEM_U4_2.2.3
any idea how i can root it? side loading apps seems to work without any hacks, as I was able to install some apks I had laying around on my dropbox, and I have installed some using Android Commander...but I can't work out how to root it, does GingerBreak NEED a real sd card inserted to work?
Click to expand...
Click to collapse
Yep, it's worked on all the orange roms, and devices. Give it a whirl.
But before you flash a new rom over your stock tmobile, could you help us get you original sbf up on the forum. You will need to be rooted to do it.
It will help you in the long run, so if you have a problem you can return to your stock
Swyped from 'mount' Olympus
nitrox1 said:
Yep, it's worked on all the orange roms, and devices. Give it a whirl.
But before you flash a new rom over your stock tmobile, could you help us get you original sbf up on the forum. You will need to be rooted to do it.
It will help you in the long run, so if you have a problem you can return to your stock
Swyped from 'mount' Olympus
Click to expand...
Click to collapse
I have no problem doing that atall, i'm glad to help as much as I can...
so just to confirm, GingerBreak will only work with a sd card inserted, as I have tried it and it doesn't seem to do anything, but I don't have a sd card inserted atm..
how would i go about backing up the sbf afterwards? also what does sbf stand for?
thanks.
edit - just redone GingerBreak with a sd card and i can confirm I am now rooted..
can i not do any of the hacks around at the moment? as they all report versions im not on? e.g.
1.42_deodex_OlympusCamera.zip
1.57_deodex_OlympusCamera.zip
1.83_deodex_OlympusCamera.zip
also, what is deodex?
Strange, it's running a newer rom than the orange atrix, being as both orange and t-mobile are one of the same now, you would have thought orange would have had a update to the 2.2.3?
SBF means system binary file. basically its a completely stock system image. Flashing it thru RSDlite (software flashing application from motorola), will completely return your phone to stock.
Deodex: Basically, Android uses a a java based virtual machine as the bases for running programs. This virtual machine is called Dalvik. A .dex file contains the cache used by the Dalvik VM (called Dalvik-cache) for a program and is stored inside the .apk. A .odex file is an optimized version of the .dex file which gets stored next to the .apk as opposed to inside the .apk. This process is done by default to system apps. Deodexing is the process of converting the .odex files back into .dex to be stored inside the .apk so that things can be more easily modified. So a deodexed rom is one that has been through the deodexing process. Deodex can just as easily be called Unodex or any other pre-fix you wish to use.
http://www.addictivetips.com/mobile/what-is-odex-and-deodex-in-android-complete-guide/
For rooting check here.
http://forum.xda-developers.com/showthread.php?t=1046626
should be very easy, but you must have a sd card.
We are then after a couple of files off your phone, and a little information? Are you game?
Do you have any knowledge of using ADB?
If not have a look here to start, but goggle will be your friend on this.
http://android-dls.com/wiki/index.php?title=ADB
We're after a request for a firmware, we need to submit the following files (using adb pull):
/system/default.prop
/system/build.prop
/system/etc/motorola/bp_nvm_default/File_GSM
about phone > weptop version
Then we can hopefully grab your sbf, so we can use it for restoring the phone, if there's mistakes made.
Have to say I don't know about modding your phone, you'll have to try.
But that's why sbf, is important.
As devs have got around bootloader, I would get used to your phone, while roms like vanilla android, miui, and cm7, get ported over.
lonegunman said:
Strange, it's running a newer rom than the orange atrix, being as both orange and t-mobile are one of the same now, you would have thought orange would have had a update to the 2.2.3?
Click to expand...
Click to collapse
True but have you seen how much more the phone is to TMO renewal customers, compared to Orange renewal.
But looks like it could be a very good sbf to grab.....
Bump
Swyped from 'mount' Olympus
This guy was able to get our orange sbf in minutes so take a look: http://modmymobile.com/forums/659-motorola-atrix-4g-general/562049-atrix-firmwares-superthread.html
Edit didnt see u already posted about pulling those files woops
Hey guys, attached is the build.prop and default.prop file, the third folder you listed doesn't exist, or at least I can't see it...
www(.)mediafire(.)com/?1ducdwtg246qz57
webtop version -OSHWT_U1_6.54.0
so once you guys help me make a SBF, I can somehow then put Clockwork recovery on there and flash one of the custom roms?
thanks
karl0ss said:
Hey guys, attached is the build.prop and default.prop file, the third folder you listed doesn't exist, or at least I can't see it...
www(.)mediafire(.)com/?1ducdwtg246qz57
webtop version -OSHWT_U1_6.54.0
so once you guys help me make a SBF, I can somehow then put Clockwork recovery on there and flash one of the custom roms?
thanks
Click to expand...
Click to collapse
Yep you should be clear to go forward, just remember no way to rerun to stock at the moment.
I've forwarded this information to daywalker04 who seems to be able to find these sbf's, and it could take a while, the web site he uses is a couple of posts up.
flashing at the moment is mainly themes at the moment rather than roms
Will post sbf on the orange uk thread in general.
Plus pm you a copy, if and when we get it.
Swyped from 'mount' Olympus
karl0ss said:
Hey guys, attached is the build.prop and default.prop file, the third folder you listed doesn't exist, or at least I can't see it...
www(.)mediafire(.)com/?1ducdwtg246qz57
webtop version -OSHWT_U1_6.54.0
so once you guys help me make a SBF, I can somehow then put Clockwork recovery on there and flash one of the custom roms?
thanks
Click to expand...
Click to collapse
I wish I had that flex version.
It doesn't appear to be on Motorola's system yet. Sometimes they take a while to catch up.
Here is an alternate method to find flex file.
Be sure to set Android USB debugging mode on your device to OFF. Then make sure you have the latest Moto drivers installed on your machine. If you can connect to Motorola Software Update using Windows OS and try to run a software update--- it will not succeed because there is no update for T-Mobile UK.
When it searches for an update it will store the necessary info in a file called MSU.txt (this is the file needed) in the Motorola Software Update program directory. Then you can find the flex version.
That file is on your computers directory, rather than your phone.
Swyped from 'mount' Olympus
nitrox1 said:
Thank you for your reply. But I'm really looking for the UK Tmobile, sbf, or understanding of it.
Ps check out our uk orange thread, for a much cheaper unlock, and within 10 min!
Swyped from 'mount' Olympus
Click to expand...
Click to collapse
oh haha sorry. just recived mine and it took 3 days for $20
Hello XDA-san
This is my first time working with cygwin and Android Kitchen and I wanted to make sure I didn't miss anything that will royally brick my s4. I have attached screenshots of my journey for reference.
I started with the stock ROM from you know where, version 4.4.2 (i337MOYAFNC1) and proceeded to remove the KNOX bootloader (using instructions from SilviuMik). I skipped the last step where it is re-md5, to continue on to the kitchen..
Using the de-knoxed tar file, I created a working folder for the ROM in the kitchen. It started unpacking, everthing went well. When i was prompted to choose if I wanted to extract the CSC, I said no.. because the DiskInternals Linux reader was giving me an error saying along the lines of cant read disk..
From my working folder, I proceeded to root & busybox, all went well. I then deodexed both the system apps and framework, all went well.
lastly, I made a build from the working folder. Selected all default options while doing so (see pictures) , signed the freshly minted rom and voila.
If the repacking was successful there is not much to fear about.
(You may want to lookup if there is any dependents (in the rom) by using the removed knox bootloader (atleast remove the knox apks I guess)
the CSC is really nothing important:
A common short code (CSC) is a short telephone number, usually consisting of five digits, that is used to address SMS and MMS messages from a cellular telephone. Common short codes may also be called mobile short codes or short numbers. Each common short code is designed to be unique to each operator.
Click to expand...
Click to collapse
Just include the one from the stockrom. btw, I have successfully manually unpacked the CSC file a year ago or so with simg2img, it only contained crap (samsung only files for altering behavior in TW rom and bloatware), the hidden partition or preload partition may also contain unwanted crap btw
So go ahead and flash it, your phone will not get bricked by this in any way.
broodplank1337 said:
If the repacking was successful there is not much to fear about.
(You may want to lookup if there is any dependents (in the rom) by using the removed knox bootloader (atleast remove the knox apks I guess)
the CSC is really nothing important:
Just include the one from the stockrom. btw, I have successfully manually unpacked the CSC file a year ago or so with simg2img, it only contained crap (samsung only files for altering behavior in TW rom and bloatware), the hidden partition or preload partition may also contain unwanted crap btw
So go ahead and flash it, your phone will not get bricked by this in any way.
Click to expand...
Click to collapse
Hi broodplank1337, thhank you for your reply
So would it be better to go into my newly minted zip file and hunt down the knox apks / dependencies? Or should I flash the ROM then use root browser to get rid of them?
I found this list "
Delete the files in the following files in this order.
/system/app/KNOXAgent.apk
/system/app/KNOXAgent.odex
/system/app/KLMSAgent.apk
/system/app/KLMSAgent.odex
/system/app/KnoxAttestationAgent.apk
/system/app/KnoxAttestationAgent.odex
/system/app/KNOXStore.apk
/system/app/KNOXStore.odex
/system/app/ContainerAgent.apk
/system/app/ContainerAgent.odex
/system/lib/libknoxdrawglfunction.so
/system/app/ContainerEventsRelayManager.apk
/system/app/ContainerEventsRelayManager.odex
/system/app/KNOXStub.apk <--- delete if you have, some will not
Delete the following folders
/system/containers
/system/preloadedkiosk
/system/preloadedsso
/system/etc/secure_storage/com.sec.knox.store
/data/data/com.sec.knox.seandroid
/data/data/com.sec.knox.store
/data/data/com.sec.knox.containeragent
/data/data/com.samsung.android.walletmanager
The French Tickl3r said:
Hi broodplank1337, thhank you for your reply
So would it be better to go into my newly minted zip file and hunt down the knox apks / dependencies? Or should I flash the ROM then use root browser to get rid of them?
I found this list "
Delete the files in the following files in this order.
/system/app/KNOXAgent.apk
/system/app/KNOXAgent.odex
/system/app/KLMSAgent.apk
/system/app/KLMSAgent.odex
/system/app/KnoxAttestationAgent.apk
/system/app/KnoxAttestationAgent.odex
/system/app/KNOXStore.apk
/system/app/KNOXStore.odex
/system/app/ContainerAgent.apk
/system/app/ContainerAgent.odex
/system/lib/libknoxdrawglfunction.so
/system/app/ContainerEventsRelayManager.apk
/system/app/ContainerEventsRelayManager.odex
/system/app/KNOXStub.apk <--- delete if you have, some will not
Delete the following folders
/system/containers
/system/preloadedkiosk
/system/preloadedsso
/system/etc/secure_storage/com.sec.knox.store
/data/data/com.sec.knox.seandroid
/data/data/com.sec.knox.store
/data/data/com.sec.knox.containeragent
/data/data/com.samsung.android.walletmanager
Click to expand...
Click to collapse
Oh I thought you were building an odin rom? zip you say?
Anyways, just remove em from the system folder and test it's result. You can always test roms without damaging your device at any time, read: it's impossible for a ROM to brick a phone, the thing that can brick it is the kernel, but only if using a kernel from an other device or so.
so don't be afraid to test it, if it doesn't work just continue your work. if it works, good joob
broodplank1337 said:
Oh I thought you were building an odin rom? zip you say?
Anyways, just remove em from the system folder and test it's result. You can always test roms without damaging your device at any time, read: it's impossible for a ROM to brick a phone, the thing that can brick it is the kernel, but only if using a kernel from an other device or so.
so don't be afraid to test it, if it doesn't work just continue your work. if it works, good joob
Click to expand...
Click to collapse
One caveat to this, and this mostly applies to Verizon and AT&T users, but if you have upgraded to KitKat and kept root using SuperSu's survival mode and your planning to test a rom using Safestrap, you better make sure that the su binary is in xbin and bin (.ext/.su) and that the Superuser.apk is in /system/app. Also make sure that the permissions are set correctly for su (chmod 06755 chown 0.0) and have busybox in the rom as well, or at least have busybox install in the updater-script and make sure everything symlinks correctly.
The best thing to do when testing roms to avoid having to worry about losing root is to download Chainfire's SuperSu zip and flash it after you flash your rom you're testing (but before it reboots into the rom for the first time) the reason I even mention all of this is because currently we (Verizon and AT&T users) have no way to root a device thats taken a complete 4.4.2 OTA.
Surge1223 said:
One caveat to this, and this mostly applies to Verizon and AT&T users, but if you have upgraded to KitKat and kept root using SuperSu's survival mode and your planning to test a rom using Safestrap, you better make sure that the su binary is in xbin and bin (.ext/.su) and that the Superuser.apk is in /system/app. Also make sure that the permissions are set correctly for su (chmod 06755 chown 0.0) and have busybox in the rom as well, or at least have busybox install in the updater-script and make sure everything symlinks correctly.
The best thing to do when testing roms to avoid having to worry about losing root is to download Chainfire's SuperSu zip and flash it after you flash your rom you're testing (but before it reboots into the rom for the first time) the reason I even mention all of this is because currently we (Verizon and AT&T users) have no way to root a device thats taken a complete 4.4.2 OTA.
Click to expand...
Click to collapse
Seriously? wow, thanks for mentioning, I can't believe what a pricks Verizon and AT&T are. Same count for Samsung that handles knox regulation in the USA (while not in other countries). In the USA you get pretty much screwed by the carriers and manufacturers the hard way.
In The Netherlands (where I live) it's even illegal to sell smartphones that are not unlocked by default. and the only thing a carrier may do is adding a CSC (Consumer Software Customization) package. This should be in the USA as well!
In the USA companies get to private / independent it seems. they should be regulated by national government rules. instead of making their own. (this keeps the crap like the problem you described away)
But Samsung should be regulated as well, there is no chance that will happen (south-korea), and their phones will contain more and more backdoors / suspicious daemons / methods of screwing you and so on, because who checks it, no one. Oh yes only someone, the NSA that adds even more of this stuff, like a VPN Interceptor, which no one is waiting for as well.
Anyways, life (or actually companies) is (are) a *****. Only strict regulation could solve this, but who still believes in regulation after seeing what the NSA all did, they broke like every single rule and forced companies to merge their crap (most likely, or a huge payment, but no single company actually likes that)
- NSA 'was allowed' to break in all PC's because that where outside the USA. that just ridiculous but true
- NSA applied their 'jizz' to all super famous apps like Facebook.
Even though it sounds like I say USA is the culprit thats not true, The netherlands have BREIN, which is the anti piracy company.
This asshole tim kuik has,
a. destroyed the piratebay for the whole world (even though it's recuping soon)
b. have done a million requests on removing uploaded movies (on newsgroups)
I really went OT all the way at this reply xd but you get my point :good:
The product gets made, then infected by the creator, then gets forced to merge nsa crap. after that it goes to the carrier which installs even more crap.
there is not a single bit of freedom left
Thank you both for these tips. Being a rather unexperienced cook, I would have never thought of these important details mentioned above.
it really is a shame how tightly service provider have our collective balls in a grasp..
broodplank1337 said:
Seriously? wow, thanks for mentioning, I can't believe what a pricks Verizon and AT&T are. Same count for Samsung that handles knox regulation in the USA (while not in other countries). In the USA you get pretty much screwed by the carriers and manufacturers the hard way.
In The Netherlands (where I live) it's even illegal to sell smartphones that are not unlocked by default. and the only thing a carrier may do is adding a CSC (Consumer Software Customization) package. This should be in the USA as well!
In the USA companies get to private / independent it seems. they should be regulated by national government rules. instead of making their own. (this keeps the crap like the problem you described away)
But Samsung should be regulated as well, there is no chance that will happen (south-korea), and their phones will contain more and more backdoors / suspicious daemons / methods of screwing you and so on, because who checks it, no one. Oh yes only someone, the NSA that adds even more of this stuff, like a VPN Interceptor, which no one is waiting for as well.
Anyways, life (or actually companies) is (are) a *****. Only strict regulation could solve this, but who still believes in regulation after seeing what the NSA all did, they broke like every single rule and forced companies to merge their crap (most likely, or a huge payment, but no single company actually likes that)
- NSA 'was allowed' to break in all PC's because that where outside the USA. that just ridiculous but true
- NSA applied their 'jizz' to all super famous apps like Facebook.
Even though it sounds like I say USA is the culprit thats not true, The netherlands have BREIN, which is the anti piracy company.
This asshole tim kuik has,
a. destroyed the piratebay for the whole world (even though it's recuping soon)
b. have done a million requests on removing uploaded movies (on newsgroups)
I really went OT all the way at this reply xd but you get my point :good:
The product gets made, then infected by the creator, then gets forced to merge nsa crap. after that it goes to the carrier which installs even more crap.
there is not a single bit of freedom left
Click to expand...
Click to collapse
The NSA can screw a cow. USA is Freedom? Like hell. I live here and am starting to become ashamed of my country. I hate the government, more directly this president. Anyway, whats a VPN Interceptor? Sounds scary..
But about the OP, can you build an Odin tar with the older Bootloaders in and newer system images to remove knox warranty and allow users to upgrade without screwing themselves? Last i checked, you needed a way to sign the tar file to match with the current bootloader checking.
broodplank1337 said:
the CSC is really nothing important:
Click to expand...
Click to collapse
CSC is "Country/Carrier Specific Config", not "common short code"
While it's not so important, skipping it may produce many side effects in normal work.
The common way to deal with CSC is extract it and pre-integrate into system - that's what stock recovery is doing upon first boot after flash.
sorg said:
CSC is "Country/Carrier Specific Config", not "common short code"
While it's not so important, skipping it may produce many side effects in normal work.
The common way to deal with CSC is extract it and pre-integrate into system - that's what stock recovery is doing upon first boot after flash.
Click to expand...
Click to collapse
This doesn't always work. I used to try this with rooted dump/repacks for S4, N2 and E4GT and we got mixed results not including Samsung's cache.img. In Sprint's case this defaulted the carrier to XAS, an internal use only code that doesn't fully enable everything for Sprint. I don't recall if this was on images with a blank data.img only or "nodata" cases as well.
garwynn said:
This doesn't always work. I used to try this with rooted dump/repacks for S4, N2 and E4GT and we got mixed results not including Samsung's cache.img. In Sprint's case this defaulted the carrier to XAS, an internal use only code that doesn't fully enable everything for Sprint. I don't recall if this was on images with a blank data.img only or "nodata" cases as well.
Click to expand...
Click to collapse
I've did it on GT-I9100, GT-I9300, SHV-E210K, GT-N7100, SHV-E330S. It worked always. Sometimes CSC is multi-CSC where you have to choose correct version.
I didn't use operator-specific models. So probably some additional steps required. But anyway, CSC from cache partition is simply copied to system by recovery. To be more precise, you can check command file in cache.img - this is where "magic" happens
Hi devs, i first time cooked prerooted deodexed rom from stock 4.4.2 rom using cygwin and andriod kitchen. every thing went well. my only question is can i remove modem from output zip as i don't want to use that modem.
Got status 7 error installation aborted.
navdeepavi said:
Got status 7 error installation aborted.
Click to expand...
Click to collapse
go to advanced > show log in recovery
As a follow up to the status 7 error, I spent quite a while figuring out what caused it and how to solve it. I posted this on another thread but ill quote myself here.
The status 7 failed to mount /preload error and why it happens:
Lets take a minute to go over why this happens and what it means. First what is /preload anyways? Well lets take a look at how it gets mounted, consider mount points below:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/hidden", "/preload");
We can infer from the point arguements that /preload is the mount point for the "hidden" partition. Well then what is this "hidden" partition then you ask? Well hidden contains some useless crap Samsung uses to verify integrity of the system partition when in recovery
So the idea is to wipe data/factory reset in recovery followed by making sure to flash hidden.img.ext4 prior to cache.img.ext4. I think my inclusion of cache.img.ext4 on accident in the first tar is the root of the cause so ive uploaded a new one that doesnt contain it so it wont fail at step 1.
So essentially you cant flash a a full-wipe or no-wipe Odin tar to go back. You have to use a custom made Odin tar. Also for people getting the status 7 error where /preload fails to mount after flashing cache the solution is to boot into stock recovery and factory data reset followed by flashing hidden.img.ext4 via Odin or Heimdall.
Click to expand...
Click to collapse
OK
So I managed to create a flashable
.zip of I337MVLUFNE1:
Rooted, Deodexed, Knox-Free,
Zipaligned, Debloated, KT Kernel!
Will post link here if you guys want!
Adizzzle said:
OK
So I managed to create a flashable
.zip of I337MVLUFNE1:
Rooted, Deodexed, Knox-Free,
Zipaligned, Debloated, KT
Will post link here if you guys want!
Click to expand...
Click to collapse
oh sweet, sure ill gladly test it out
ty!
go habs GO
The French Tickl3r said:
oh sweet, sure ill gladly test it out
ty!
go habs GO
Click to expand...
Click to collapse
http://www.androidfilehost.com/?fid=23501681358539374
It has a TMO KT kernel so you may need a
different kernel depending on your device.
It's debloated, but only lightly.
I have a heavily debloated version uploading.
Adizzzle said:
http://www.androidfilehost.com/?fid=23501681358539374
It has a TMO KT kernel so you may need a
different kernel depending on your device.
It's debloated, but only lightly.
I have a heavily debloated version uploading.
Click to expand...
Click to collapse
awesome ty
i have the i337m with telus, and if i remember correctly, I had to use the TMO kernel when I flashed the maple leaf ROM a while back
The French Tickl3r said:
awesome ty
i have the i337m with telus, and if i remember correctly, I had to use the TMO kernel when I flashed the maple leaf ROM a while back
Click to expand...
Click to collapse
Yeah it was made for a Telus I337M
The only thing missing is the APN.
Made with ArchiKitchen.