Hi guys/girls,
I picked up an I777 SGS II the other day and decided to extend my development of the SGS boot screen MOD to it and was able to port it the same day as not much has changed in the way the param.lfs operates. I know this works just fine on the AT&T I777 SGS II in which the param.lfs calls for logo_att.jpg but if it fails, you can always re-flash a stock param.lfs to restore the boot screen which I have also included. I have written this for (I897, I9000, T959, T959V, I9100 and now I777). Per XDA's rules, I'll just attach the RAR package as an upload at the bottom of this post.
If you appreciate my work, just tap THANKS, SUBMIT THIS TO PORTAL or DONATE me a drink or two if you are feeling generous. Here is the read me in case you don't want to open it with an additional text editor:
Thanks to Entropy512 for the stock param.lfs dump...
Code:
Brought to you by MOBILETECHVIDEOS.COM and CONNEXION2005 of XDA-Developers.COM
If the instructions below don't make sense to you,
JUST DON'T DO IT!
[B][COLOR="Red"]Prerequisites: ROOT & BUSYBOX...[/COLOR][/B]
To change logo again, repeat the whole process!
=========================================================
| Instructions |
| ------------ |
| 1. Open Odin |
| 2. Boot Phone into Download Mode |
| 3. In Odin PDA select "SGS2_custom_param_lfs.tar" |
| 4. Click Start |
| 5. Reboot from recovery... |
| You will have a logo draw fail! DONT WORRY! |
| 6. Rename the Picture you want to use to " logo.jpg " |
| 7. Run "MobileTV_SGS2_BootScreen.bat" from PC, follow |
| instructions. Keep phone screen ON, allow SU request. |
| 8. Reboot and Enjoy! |
=========================================================
NOTE about custom images!
480 x 800 and UNDER 100 kB
REMEMBER, THIS SCRIPT INSTALLS THE LATEST BUSYBOX INSTALLER, THIS MEANS IF YOU DIDN'T HAVE BUSYBOX INSTALLED, YOU MUST OPEN THAT INSTALLER AND ACTUALLY INSTALL BUSYBOX. IT INSTALLS AN APK TO USE TO INSTALL BUSYBOX, IT DOES NOT ACTUALLY INSTALL BUSYBOX ITSELF DURING THE SCRIPT.
ONLY USE THE LATEST BUSYBOX BY STERICSON TO ENSURE THIS WORKS BEST. IF YOU DON'T WANT TO USE THE SCRIPT FOR THE LATEST VERSION, BE SURE TO DOWNLOAD THE LATEST FREE INSTALLER OR DONATE VERSION IN THE MARKET BY STERICSON.
If the script doesn't work for you, it should if you have ADB installed, a rooted device plus the latest BusyBox (no offense but it's user error otherwise) just use root explorer to paste your logo_att.jpg in /mnt/.lfs AFTER running the custom param file via ODIN.
I'll get a video up for this model soon on how to do this without any product placement so it's XDA approved.
Reserved...one...
Reserved...two...
Just tried to do this, got an error when it tried to install busybox (already installed, that's ok), but then I get this error:
cp: can't create '/mnt/.lfs/logo_att.jpg': File exists
I didn't get an the SU request either
connexion2005 said:
Reserved...one...
Click to expand...
Click to collapse
Does the ori Galaxys2 hellcat script work on this one?
Sent from my GT-I9100
dekkon said:
Just tried to do this, got an error when it tried to install busybox (already installed, that's ok), but then I get this error:
cp: can't create '/mnt/.lfs/logo_att.jpg': File exists
I didn't get an the SU request either
Click to expand...
Click to collapse
Sounds like you didn't flash the custom_param file with ODIN.
Is this a custom splash screen? If I'm correct
Sent from my SAMSUNG-SGH-I777 using XDA App
connexion2005 said:
Sounds like you didn't flash the custom_param file with ODIN.
Click to expand...
Click to collapse
Out of curiosity, what does the custom_param file do?
Change logo.jpg to be writable?
Good work dude
Entropy512 said:
Out of curiosity, what does the custom_param file do?
Change logo.jpg to be writable?
Click to expand...
Click to collapse
It changes logo_att.jpg to be writeable in this case for the I777. But yes I've removed the file via hex-editing which is the only way to allow for a new one to go in it's place. Fortunately for us Samsung has not changed anything since I discovered this loophole way back in the Captivate days.
clown_luv said:
Is this a custom splash screen? If I'm correct
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
That's correct... The first one you see when powering on. I refer to the other one as the boot animation. For reference the kernel screen is only in between the boot screen and the boot animation is only changeable during a compilation of the kernel. This tutorial would be way to involved which is why I never made it.
@connexion2005
I got My SGS2 last Sunday. Nice to see familiar folks coming from SGS.
Awesome work as always... It worked like a charm. Thanks!
I've attached my logo file in case someone is interested.
Con can you show us the pic used and this will not affect my kernel correct?
Sent from my SAMSUNG-SGH-I777 using XDA App
Custom Boot Splash!
Awesome work Josh...Thanks for bringing this over to the AT&T version of the SGSII for us! You have some good stuff going on over at MTV (No pun intended) keep up the good work for all the phones...Hope to see more coming soon for this one!
Thanks! More coming soon as you'd expect including full JTAG support (will take some work though as surprisingly they changed the board from the SGS I9100!)
So con I flash in Odin and what is the splash screen pic? ? ( just wanna know and what slot PDA?
Sent from my SAMSUNG-SGH-I777 using XDA App
connexion2005 said:
Thanks! More coming soon as you'd expect including full JTAG support (will take some work though as surprisingly they changed the board from the SGS I9100!)
Click to expand...
Click to collapse
I think there are a number of hidden under-the-hood changes - NFC is not the only one.
If you've opened the device up - Is there an Si7409 (FM chip) or not? If not, I'll give up on trying to probe for it.
Another difference is that even though the MAX8997 PMIC Samsung uses in our phone has a battery charger, in the I777, Samsung has offloaded charging to a separate chip (MAX8922). Which means we don't get all of the charge current control hacks available to the I9100 unless there's some way to restore control to the 8997. (not likely)
I have opened up to begin research, documentation and produce repair possibilities for JTAG. At the time I was ONLY looking for JTAG interfacing though so I didn't pay any other attention. I put it back together but I'll check again when I'm done and maybe make a tear down thread with detailed pics for people to download and zoom in on.
EDIT: One good thing is that most of the internal hardware are interchangeable (flex cable assemblies and what not). I'm also going to see if the front housing w/ lcd and center button from the I9100 swaps over to it to allow use with I9100 roms. I know the ROM's load and run fine they just don't have the correct button mapping obviously. I personally like my i9100 much better with the center button than the i777...
clown_luv said:
So con I flash in Odin and what is the splash screen pic? ? ( just wanna know and what slot PDA?
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
Read the OP. You pic whatever one you want. I've included 3 in the base package but literally you can put whatever you want to name logo.jpg in the folder you run the batch script from. I advise less than 100KB in size although that's been dis-proven in the past anyhow.
No-Go...
I have tried three times and no go...I am getting everything to work perfectly but no image is producing. I have tried one of your logos and got the same results. Following the OP to the 'T' (I know you have heard that all to often...But this time its true) I'm not getting any error or failings to occur. Image is copying to the sdcard root but it seems its not passing it to the blank .lfs portion of the phone.
Is the file for the logo supposed to be logo.jpg or logo_att.jpg? Here is the excerpt from your script.
echo Preparing to copy new boot screen...
adb shell su -c "busybox cp -r /mnt/sdcard/logo.jpg /mnt/.lfs/logo_att.jpg"
Related
Hi,
I just realised that I'm going to post this, hopefully to get some help getting the frame buffer issue working. I'm not giving up on it, but it just doesnt seem fair to sit on this any longer since it works, besides the GUI glitches.
As i said before, the S7 kernel does not support framebuffering, which makes the GUI in the recovery a bitt messy. When you move up / down in the menu, it switches between selecting an item on top and an item on the bottom (you'll see 4 menus in total, but the ones on each horizontal line is a mirror).
This means that it starts by using the lower one, and it uses the top one next, then it goes back to the lower one. Boot it up and you'll probably see what I mean. This shouldnt cause any problems with the recoverys operation anyhow.
If you want to enter adb in linux you will have to get a copy of usb_modeswitch and run the following line in order to get adb to recognize the device:
sudo usb_modeswitch -W -v 12d1 -p 1031 -V 12d1 -P 1035 -M "5553424370ab71890600000080010a1106000000000000000 0000000000000" -s 20
This will switch the huawei s7 usb device into adb mode.
Also i take no responsibilites of bricks or other problems caused by using this recovery. Its truly for learning usage only.
My credit list would be to long if I where to include all forums that I've visited to get more information about this device, but if you feel like you deserve credit, let me know and i'll add you, otherwise, thanks to all people posting information about android devices, i could never have done it without you.
Ofcourse i have to thank the creators of clockwork mod, and also the people who wrote the repack-image.pl and unpack-image.pl scripts
Thanks to my wife who put up with me sitting and messing around with this for almost a week, giving her not the attention that she deserved, and thanks to all users of the S7 tablet out there.
h***://rapidshare.com/files/438781673/recovery.img.zip (not allowed to post links yet)
The shortcut key for entering recovery is menu + send, if anyone wonders.
Hope you'll enjoy it as much as I did.
Works great. Ill research a bit to see if i can help
Sent from my Ideos S7 using XDA App
Sorry for qwestion, but... How can i put it into device? Via fastboot on cmd, or somehow other?
Sent from my Ideos S7 using XDA App
I hope we can get a 2.2 rom
sorry, but it working not fully...
its have errors to open nandroid-mobile.sh
and its cant format SDcart to partitions ext2 and ext3...
or maybe i doing something wrong
GvoZdik said:
sorry, but it working not fully...
its have errors to open nandroid-mobile.sh
and its cant format SDcart to partitions ext2 and ext3...
or maybe i doing something wrong
Click to expand...
Click to collapse
You're right, I noticed now that I the wrong ramdisk in the image that was released. I have several of them for which I use to debug the framebuffer stuff, and I forgot to use my own build.
I'll upload the correct one sometime this weekend.
Sorry.
Sent from my HTC Desire using Android Tablet Forum App
thanx, thats a great work anyway...
Sent from my S7 using XDA App
thanks perivarlura for your support!
perivarlura said:
You're right, I noticed now that I the wrong ramdisk in the image that was released. I have several of them for which I use to debug the framebuffer stuff, and I forgot to use my own build.
I'll upload the correct one sometime this weekend.
Sorry.
Sent from my HTC Desire using Android Tablet Forum App
Click to expand...
Click to collapse
The ui glitches even more now that the misc partition handled and the nandroid script is running. I guess i need to get this fixed before i release it, or it will just be a mess.
I have spent days looking for threads so this neewb is about to break something. Well maybe not. I have my daughters Eris 2.1 and am trying to root it for her. I have tried several times with different methods. The issue is that I can get into recovery mode after every 1 click app but nothing I try will let me toggle to unzip to SD, or toggle to anything for that matter, volume wont do it and all track ball will do is let me select reboot. Man my DX was easy compared to the one click method.
HELP PLEASE,
If the trackball is having trouble scrolling, I'd install the trackball-optional custom recovery so you can use other buttons to scroll. There are instructions for doing this here:
http://androidforums.com/eris-all-things-root/214240-amon_ra-1-6-2-custom-recovery-trackball-not-required.html
It sounds like you fall into "Scenario 2" which says you should follow the same method as "Scenario 1" to get rooted using the trackball-optional recovery.
I'll give it a shot, The help is much appreciated,
I am been trying to help him to get this thing to add the Custom Recovery, but every root format has not worked at all. Most are outdated or there are files missing. Specially on the link provided above. The download for the scripts no longer has Root_1 or Root_2, it has a bunch of other stuff there for gscript. Found an link on Droidforums for gscript for rooting and the scripts don't work.
Any complete instructions anywhere?
popfan said:
I am been trying to help him to get this thing to add the Custom Recovery, but every root format has not worked at all. Most are outdated or there are files missing. Specially on the link provided above. The download for the scripts no longer has Root_1 or Root_2, it has a bunch of other stuff there for gscript. Found an link on Droidforums for gscript for rooting and the scripts don't work.
Any complete instructions anywhere?
Click to expand...
Click to collapse
popfan,
I am not aware that any of the above links or files are missing... Can you point-out / tell me specifically which files you cannot access / download / link-to?
The root_part1 and root_part2 files are part of erisuser1's (bftb0's) Universal Root for Dummies! thread that I do reference in my AF thread, but these should still be up, active, and available.
So, I'm not sure if you are speaking about becoming rooted or installing a my trackball-optional custom recovery.
Let us know.
Cheers!
Im sure my kid has shuned me for leaving her Eris with someone so thanks to everyone for the help. Pop is helping me out and after moving file at the point where it says to open and look to see root 1 and root2 they are not there and there are a ton of other stuff. Also the pick look different than on the thread like the app has been updated. Also when doing the ball recovery there is no tools folder to be found. I'm sure pop wont touch it again till tomorrow so any other help / advice is more than welcome or it may cost me my Dx
malloneem said:
Im sure my kid has shuned me for leaving her Eris with someone so thanks to everyone for the help. Pop is helping me out and after moving file at the point where it says to open and look to see root 1 and root2 they are not there and there are a ton of other stuff. Also the pick look different than on the thread like the app has been updated. Also when doing the ball recovery there is no tools folder to be found. I'm sure pop wont touch it again till tomorrow so any other help / advice is more than welcome or it may cost me my Dx
Click to expand...
Click to collapse
LOL, sorry, didn't make/see the connection between your two posts .
Okay, let's try something new here...
Just a week or so ago, I re-packed jcase's 1-click rooting app to include my trackball-optional recovery image in lieu of the original recovery that his app includes.
So, let's have you re-root using the new 1-click app (all credit to jcase, both for his app and his threads both here http://forum.xda-developers.com/showthread.php?t=742228 and over at AF http://androidforums.com/eris-all-things-root/139178-universal-1-click-eris-app-apk-no-pcs-no-scripts-needed-easy.html).
Since you've already used the 1-click app before, then all you'll have to do is grab my new "trackball-optional" version:
https://sites.google.com/site/scaryalienware/downloads/one-click-tbo.apk
MD5 sum: 15763b51cf707c027cc73bc117e1fc39
(the "tbo" in the name stands for "trackball optional" ).
Just follow the same process you did before while running the 1-click app and you should end-up with my trackball-optional recovery installed.
Let me know how it goes (you'll be the first besides me that I know of that has tried it; the user that I created it for to test has not yet responded, LOL).
Cheers!
I tried this link below. It no longer has the root_1 and root_2 in it.
http://www.megaupload.com/?d=774XYFRA
I did use your "updated" 1-click app with tbo and it worked great.
Thanks!!
Too bad this phone was not as easy as my captivate.
popfan said:
I tried this link below. It no longer has the root_1 and root_2 in it.
http://www.megaupload.com/?d=774XYFRA
I did use your "updated" 1-click app with tbo and it worked great.
Thanks!!
Too bad this phone was not as easy as my captivate.
Click to expand...
Click to collapse
Glad that jcase's repackaged app worked for you. I'll update my documentation to make this available to others.
Also, re. the above Megaupload link...it works just fine for me (from my PC and from my Droid X) and includes all of the aforementioned root_part1/2 files.
I think you've fallen prey to a truncated download, which is not uncommon with Megaupload in my experience. This is also why is important to double-check the file sizes and MD5 checksums of files that you download so that you know you got the whole-shebang; notice that erisuser1 did include the MD5 in his thread for this file:
- Download gscript.zip (MD5 92796a8c6e61e8f1ee36e315c0acae7d)
I've often found it helpful to use a different browser other than the stock browser (like Opera Mini) when doing downloads via my Eris since the stock browser does seem to have more issues (timeouts perhaps) than it should.
Cheers!
Thanks to all this tuff till you hooked us up but now on to nightmare 2
I downloaded CyanogenMod7.1.0 RC1 [2.3.5 GingerBread NIGHTLY]
from this thread http://forum.xda-developers.com/showthread.php?t=944430&highlight=ROM
Got it up but it has no market so I can not get to titanium, boot loader or anything... It says to flash google apps after the rom but now Im back to the trackball / volume key issue because it's all in titanium. ??? I did a factory reset and it came back up as the new ROM, ???
EDIT UPDATE!!!!
Sorry for the hassle all, the "green" start call button works as the down after the download.. All is well.. I think..
Again thanks to you all, If I hear of any good deals on an Eris I will know why.
You need to download GAPPS to your sdcard. That is why you don't have market.
http://forum.xda-developers.com/showthread.php?t=944430&highlight=ROM
Its just below link for the rom and save it to your sdcard. Go ahead boot into recovery and wipe data, daliv-cache, cache; Flash Rom again, then flash gapps and reboot.
Some weeks ago, I decided to overclock my Ace: CyanogenMod-7.1.0-RC1-Cooper-KANG plus ClockWorkMod4. Got the overclocking kernel from ketut.kumajaya and started to play with frequencies while watching CSI Las Vegas.
In general, it's stupid idea to multitask things like this. In my case, I accidentally ticked checkbox "Set at boot", set the frequency to around 870 MHz and my phone rebooted. I have gone into the bootloop, tried almost everything:
-reinstallation of CyanogenMod
-reinstallation of some other ROM i have found on my disk
-cleaning caches, wiping etc
Without sucess of course
I have decided to check, what exactly happened with my phone, so connected it to PC and started logcat. There was a lot of errors related to files on /data partition - it did not mount for some reason. I was able to access shell from Recovery, but it did not helped me too much - /data partition was entirely broken.
I realized that Samsung uses its own filesystem for /data - RFS and I had no tools to work with it - at least did not find them. In such case, I have unpacked one of the older firmwares and found, that it contains files for soome partitions, but not for the /data.
Next steps were fairly simple - go to sammobile.com, download firmwares for my Ace and check, if it contains /data (data.rfs). Eventually found one, flashed it and my phone went back alive.
Don't know if this is best method, but at least it was interesting to investigate
Thnkx for dis info. All d noobs should read dis before flashing d oc kernel.
Sent from GT-S5830 using Grif's Cyanogenmod
domnic79 said:
All d noobs should read dis before flashing d oc kernel.
Click to expand...
Click to collapse
I think, that most of them will read this after the catastrophe...
Regards
SetCPU has a "Safe Mode" flashable zip file
Sent from my GT-S5830 using XDA App
EmoBoiix3 said:
SetCPU has a "Safe Mode" flashable zip file
Click to expand...
Click to collapse
In general, overclocking means that system can work in an undeterministic manner. Especially an overclocked processor can write some garbage to flash - in my case it was /data partition.
Can't belive that any "Safe Mode" could help - if you play with fire, you should be ready for some burns
Regards
Pawel
p.stradowski said:
In general, overclocking means that system can work in an undeterministic manner. Especially an overclocked processor can write some garbage to flash - in my case it was /data partition.
Can't belive that any "Safe Mode" could help - if you play with fire, you should be ready for some burns
Regards
Pawel
Click to expand...
Click to collapse
It reverts the CPU speed back to 787Mhz .
Sent from my GT-S5830 using XDA App
EmoBoiix3 said:
It reverts the CPU speed back to 787Mhz .
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
exactly. it disable/revert the "set on boot" function that cause bootloop
Everyone knows the risks and there are more than enough warning messages floating around highlighting the BLATANT ramifications of over clocking. Call me harsh, but isn't this what we DIDN'T want to see cluttering the forums? Let this be a lesson to anyone else who decides to flash the kernel.
Sent from my GT-S5830 using Tapatalk
well some people need to learn the hard way. some will never learn until the day their devices blown to smithereens on their faces.
jimbo.levy said:
Everyone knows the risks and there are more than enough warning messages floating around highlighting the BLATANT ramifications of over clocking. Call me harsh, but isn't this what we DIDN'T want to see cluttering the forums? Let this be a lesson to anyone else who decides to flash the kernel.
Click to expand...
Click to collapse
completely agrees
an0nym0us_ said:
well some people need to learn the hard way. some will never learn until the day their devices blown to smithereens on their faces.
Click to expand...
Click to collapse
yeah i see LOT OF people just bricking devices and then search for solutions.. but i see that many people search Google and see something and do it on device without confirming that it works or not...
in my opinion rom manager seriously should include warning or some mechanism to warn user that there device is not at all supported.. is there any?? just confirming as i haven't installed that ACE KILLER
madman_amit said:
completely agrees
yeah i see LOT OF people just bricking devices and then search for solutions.. but i see that many people search Google and see something and do it on device without confirming that it works or not...
in my opinion rom manager seriously should include warning or some mechanism to warn user that there device is not at all supported.. is there any?? just confirming as i haven't installed that ACE KILLER
Click to expand...
Click to collapse
Rom manager says ace is supperted in cm7 roms. Bt 99% people bv bricked their fones using this app. So even if it shows samsung galaxy ace in d list, dont use it.
Sent from my GT-S5830 using Grif's CyanogenMod
Dont jus say thanks, use d 'Thanks' button. [XDA-RULE]
EmoBoiix3 said:
It reverts the CPU speed back to 787Mhz .
Click to expand...
Click to collapse
It is good option to have such tool handy, but one can understand, that overclocking can hit the phone in more complex way. This was my case - overclocked system damaged partition /data.
My message is that overclocking is dangerous and one should be prepared for any results including bricking.
Comparing this with usual process of installing new firmware, recovery, bootloaders etc, overclocking is far more dangerous because of uncertainity generated by the unstable processor.
Regards
Hello,
I think I also broke my /data
p.stradowski said:
...
Next steps were fairly simple - go to sammobile.com, download firmwares for my Ace and check, if it contains /data (data.rfs). Eventually found one, flashed it and my phone went back alive...
Click to expand...
Click to collapse
I've tried to download many firmwares, but cannot find any containing that precious data.rfs.
Is there some specific version or link you could give me please ?
Thank you so much !
Hi again,
Answering to myself : S5830XWKPO v2.3.3 makes the trick.
Bye
similar bootloop for CM7.2 perhaps with similar solution?
Hi,
I am having a similar bootloop problem for CM7.2.
I have Odin installed, but I don't think sammobile firmware page currently stocks the appropriate files. Clicking on the links for the files just links to mediafire, invalid or deleted files. for some of those files.
I do however have some backups I made with nandroid which may be incomplete: These are all of the files generated.
cache.rfs.tar data.rfs.tar nandroid.md5 system.rfs.tar
I also just installed Android Developer Tools for Linux.
Can I use any of these things especially data.rfs.tar in Odin to fix my phone.
I just interested in how you loaded the data.rfs.tar into Odin, because I have read it is very sensitive to file order, and Odin is a good canditate mechanism for bricking my phone.
I have CW5 installed. My phone can go into download mode, and I can see corresponding COM ports in Odin.
Sorry I have not posted on the most appropriate topic, but I am interested in the way you solved your problem with logcat, and then flashing data.rfs.tar
BTW: I also found this package somewhere: I think its the whole gingerbread stock rom. Simply adding the zip to the SDCARD and trying to install from SDCARD, after clearing cache etc. wont do anything. Yet on the other hand none of these files are any good for Odin either.
~/Desktop/android_device_samsung_cooper-gingerbread$ ls
AndroidBoard.mk BoardConfig.mk init.gt-s5830.rc liblight recovery sec_key.kl ueventd.gt-s5830.rc
Android.mk camerashutter kernel overlay recovery.fstab sec_touchscreen.kl unzip-files.sh
AndroidProducts.mk device_cooper.mk libaudio prebuilt recovery_kernel setup_fs UsbController.cpp
bdaddr_read egl.cfg libcopybit qwerty.kl recovery.rc setup-makefiles.sh vendor
bluedroid extract-files.sh libgralloc ReadMe sec_jack.kl system.prop vendorsetup.sh
I wonder if anyone knows the best way to get this format of ginger bread to unzip and expand off the sdcard?
Thanks so much for any help, It would be much appreciated (even if the help is just the suggestion that I should repost under a different forum topic).
p.stradowski said:
Some weeks ago, I decided to overclock my Ace: CyanogenMod-7.1.0-RC1-Cooper-KANG plus ClockWorkMod4. Got the overclocking kernel from ketut.kumajaya and started to play with frequencies while watching CSI Las Vegas.
In general, it's stupid idea to multitask things like this. In my case, I accidentally ticked checkbox "Set at boot", set the frequency to around 870 MHz and my phone rebooted. I have gone into the bootloop, tried almost everything:
-reinstallation of CyanogenMod
-reinstallation of some other ROM i have found on my disk
-cleaning caches, wiping etc
Without sucess of course
I have decided to check, what exactly happened with my phone, so connected it to PC and started logcat. There was a lot of errors related to files on /data partition - it did not mount for some reason. I was able to access shell from Recovery, but it did not helped me too much - /data partition was entirely broken.
I realized that Samsung uses its own filesystem for /data - RFS and I had no tools to work with it - at least did not find them. In such case, I have unpacked one of the older firmwares and found, that it contains files for soome partitions, but not for the /data.
Next steps were fairly simple - go to sammobile.com, download firmwares for my Ace and check, if it contains /data (data.rfs). Eventually found one, flashed it and my phone went back alive.
Don't know if this is best method, but at least it was interesting to investigate
Click to expand...
Click to collapse
hello! i had your problem with my ace and i could not find a solution at first but after a while i had worked out a solution. i find this one a bit easier to follow for noobs NOT guaranteed to work. also you will lose ALL DATA
1.flash stock through odin (2.3.5 reccomended)
2.wipe/factory reset
3.flash this: https://docs.google.com/file/d/0B-eHBmC1vSXGc1BRSWlqRW1Nc28/edit - this will root your device
4.afterwards flash this: https://docs.google.com/file/d/0B-eHBmC1vSXGeWNBOXhCVjZTRkk/edit - this will give you cwm
5.turn off then boot into recovery again.
6.wipe data/factory reset, cache, dalvik cache, mount and format system
7. install this ROM: https://docs.google.com/file/d/0B-eHBmC1vSXGVU1TSjdpUlF4MDg/edit
8.boot up your phone. it will take about 5 minutes to boot again, and you will have xperiatized rom. you can now flash whatever rom you like or go back to stock. i hope i have helped you and if i have please hit thanks
Hi,
Thanks for your help and interest.There is no chance that that will work in my situation since I have never succeeded in flashing the stock android from the samsung website. In fact, I have never been able to flash anything with Odin at all. I tried uninstalling and reinstalling Samsung drivers. Uninstalling Kies etc, using specific Samsung data cable. No measure I took was able to satisfy the condition that Odin could flash a ROM onto my Samsung gts-5830, which made me sad for a while.
Also thanks for granting permission to share googledocs files. Unfortunately I was unable to download Root.zip from google docs. Due to following error, but given I can't flash stock Android, the downloading the files will not help anyway. (Browser gives error message
###
# corresponding URL for that Root.zip:
# has resulted in too many redirects. Clearing your cookies for this site or allowing third-party cookies may fix the problem. If not, it is possibly # a server configuration issue and not a problem with your computer.
###
Please read this carefully :
- BASE ROM by Kibuuka AOSP ICS 4.0.4
- PORT ROM from Mazda Team Dirt PARANOIDANDROID v0.2.1 for Supersonic aka HTC Evo 4G and Xylograph ParanoidAndroid for HD2
All the Credit and Donate go to :
1. Mazda [Team Dirt] (http://forum.xda-developers.com/showthread.php?t=1714415)
2. Molesarecoming aka PARANOIDANDROID (http://forum.xda-developers.com/showthread.php?t=1717079)
3. Xylograph
3. Kibuuka (you know where to find him)
4. Nop (you know where to find him)
5. TheManii (you know where to find him)
Please do me a favour, hit the THANKS button at least for above name list.
As usually, I take no credit at all for this rom because this is not my work, I'm not build this from the source, all I do is take the 2 rom, combine it, then try to make it boot on my device.
The rom from Mazda was made for running on HTC Supersonic, if running on DS5 sure it will have much problem and bugs.
All I can do just fix as much as I can, I'm not have experience in build rom, so do not expect too much on this rom.
I just want to share, not intend anything by making this, just have fun and feel excited when others ICS rom can running on my old device.
So lets have fun.
Not work
camera
Temporary work
wifi tether (use barnacle wifi tether from playstore)
headphone (use toggle headset2 from playstore, thanks to machbe 1984)
How to
Nandroid back up before flash.
Wipe cache and dalvik cache, factory reset from streakmod recovery
Flash rom
Factory reset from dell recovery
Be patience, phone need longer time to boot up, if it stuck on boot animation, press and hold power button untill phone shutdown and reboot again. This time will boot up.
Download link
http://www.mediafire.com/download/7eq27tblav0qdjt/ParanoidAndroid_Streak.zip
How to have tablet ui
HOW TO MAKE ANY ICS ROM HAVE TABLET UI
Thanks to Veisen for his awesome work, you can follow his thread
http://forum.xda-developers.com/showthread.php?t=1767955
Tools
- Winrar or 7zip
- dex2jar
- hex workshop
- services.jar from ICS rom
How to
- extract services.jar from ICS rom (system/framework)
- use winrar to extract classes.dex from services.jar
- use dex2jar to compile classes.dex [ d2j-dex2jar classes.dex ]
- the result "classes_dex2jar.jar", use winrar to open and extract WindowManagerService.class form classes_dex2jar.jar\com\android\server\wm
- open WindowsManagerService.class in hex workshop, choose replace icon from menu bar, fill the pop up with
Find : 8E0009000A000000821B9900781D36061C36072A2A2A2A1506
Replace : 930009000A000000871B99007D1D36061C36072A2A2A2A1506 8617046E8B
click ok, then choose replace all, after that choose replace icon from menu bar again, fill the pop up with
Find : B11C36061D3607A7FF8B
Replace : B11C36061D3607A7FF86
click ok, then choose replace all
- save WindowManagerService.class
- replace WindowManagerService.class by winrar in classes_dex2jar.jar without compression
- use jar2dex and create new dex file [ d2j-jar2dex classes-dex2jar.jar ]
- rename it to classes.dex
- use 7zip to replace your classes.dex in services.jar
- copy the mod service.jar back to your rom or phone
- in build.prop change density to 128 and reboot.
Now you have tablet phone
I have tested it and the result are
- dpi 128 [phone not work, data and wifi work well]
- dpi 240 [everythings work well]
Feel free to try use other phone.apk and post the result here.
Intriguing concept!
... too bad I cannot flash it. (using ClockworkMod 6.0.1.0)
tried redownloading 3x
Crinos512 said:
Intriguing concept!
... too bad I cannot flash it. (using ClockworkMod 6.0.1.0)
tried redownloading 3x
Click to expand...
Click to collapse
Try use streakmod?
Sent from my Dell Streak using Tapatalk 2
Anybody success flash it ? I'm afraid there is bad upload.
Sent from my PC36100 using Tapatalk 2
Crinos512 said:
Intriguing concept!
... too bad I cannot flash it. (using ClockworkMod 6.0.1.0)
tried redownloading 3x
Click to expand...
Click to collapse
i have flashed it successfully by both StreakMod 0.3.2.8 and ClockworkMod 5.0.2.7
it has some interesting changes
i hope it will be better and better (such as camera and languages)
Yep, was able to flash it too. Preferred the CM9 ROM though! To each his own, I guess!
i always thought that this rom is nice... and ... it is nice..
My friend not believe that my old device can run paranoid android, same like his galaxy note untill I show him. He always laugh at me, said my ds5 is old enough and I should replace it with something new. Ha....this time I beat him
Sent from my PC36100 using Tapatalk 2
nom051205 said:
My friend not believe that my old device can run paranoid android, same like his galaxy note untill I show him. He always laugh at me, said my ds5 is old enough and I should replace it with something new. Ha....this time I beat him
Sent from my PC36100 using Tapatalk 2
Click to expand...
Click to collapse
streak 5 maybe old but it is still competitive hardware... and its large screen always beat others ( <5inch of course)
though i find it nowadays large screen is standard among south koreans...
Crinos512 said:
Intriguing concept!
... too bad I cannot flash it. (using ClockworkMod 6.0.1.0)
tried redownloading 3x
Click to expand...
Click to collapse
Unless OP silently updated, I cannot confirm this.
What I mean is that it installed fine for me with CWM 6.0, though the way it mounts isnt the preferred way long term.
If anything it shouldnt be compatable with streakmod as it's using the newer format/mount syntax (it's rather complicated in how recoveries read the update scripts).
GApps is also included in it, perhaps you should remove it and point users to a Gapps package, either mine or the 'official' CM one.
ParanoidAndroid is a source based rom isnt it?
We do (preferrably) need a source port instead of a hackport as the rom still thinks it's an EVO
Perhaps when Kibuuka gets AOSP more closer to working 100%, we'll have more people building from source instead of hackports.
Unlike the S7/S10 CM9 ports (and this port of paranoidandroid), all the ICS based ones are currently hackports.
The S5 is terribly slow compared to the S7, it has the ram and nand space to run the newest roms, but the cpu is simply overwhelmed by new apps/stuff.
It's still plenty usable, but 1st gen snapdragons simply cant compare to 3rd/4th gen snapdragons (and their equivilent Exynos/Tegra chips).
It doesnt make it useless though, I still use my S5 ocasionally even though my S7 is pretty much better in every way (except size)
Edit: after reviewing this rom with Quadrant, it seems that the IO score is unusually low. This might explain why my S5 seems so slow with it installed, if it really is IO bottlenecked it could be bottlenecking the entire system.
The other scores are comparable with AOSP/ICS, but PA is signifigantly slower even though I did a fac reset before installing.
Hmm.. it seem that baseband ignorance patch is not working.. it gives blink to the light panel... lol... i am using 366bb to see how the call quality goes and it seems fine.. is there anyway to make the ignorance patch work? I pretty much like this rom and the lags is almost gone too..
TheManii said:
Unless OP silently updated, I cannot confirm this.
What I mean is that it installed fine for me with CWM 6.0, though the way it mounts isnt the preferred way long term.
If anything it shouldnt be compatable with streakmod as it's using the newer format/mount syntax (it's rather complicated in how recoveries read the update scripts).
GApps is also included in it, perhaps you should remove it and point users to a Gapps package, either mine or the 'official' CM one.
ParanoidAndroid is a source based rom isnt it?
We do (preferrably) need a source port instead of a hackport as the rom still thinks it's an EVO
Perhaps when Kibuuka gets AOSP more closer to working 100%, we'll have more people building from source instead of hackports.
Unlike the S7/S10 CM9 ports (and this port of paranoidandroid), all the ICS based ones are currently hackports.
The S5 is terribly slow compared to the S7, it has the ram and nand space to run the newest roms, but the cpu is simply overwhelmed by new apps/stuff.
It's still plenty usable, but 1st gen snapdragons simply cant compare to 3rd/4th gen snapdragons (and their equivilent Exynos/Tegra chips).
It doesnt make it useless though, I still use my S5 ocasionally even though my S7 is pretty much better in every way (except size)
Edit: after reviewing this rom with Quadrant, it seems that the IO score is unusually low. This might explain why my S5 seems so slow with it installed, if it really is IO bottlenecked it could be bottlenecking the entire system.
The other scores are comparable with AOSP/ICS, but PA is signifigantly slower even though I did a fac reset before installing.
Click to expand...
Click to collapse
You named it hackport was exactly what I did, honestly this is the first step of porting rom (make it can boot up then see how stable it run) after that there are others step more, I skipped it
I think when the base rom hit something like beta stage, there should be a lot of changes, on that time better to port from the beginning again to hv a better result
On supersonic, we used to put Papasmurfs script (found in HTC supersonic forum) then should hv good result, I hv tried it and rom show much better performance, but browser and gmail fc. (I choose I/O scheduler = SIO).
Sorry for the "Evo" things show up
I hv changed the strings.xml on values folder but always stuck when compile framework-res.apk.
Tried every method and apktool (apktool1.4.2/apktool1.4.3/apktool1.4.3.1/apkmanagers for ics/new aapt from android sdk) found on google still no go.
Sent from my PC36100 using Tapatalk 2
If you simply use pull the our AOSP build's drivers, I'd imagine that rebuilding shouldnt be too difficult as all the hard work is making the drivers work.
It would be similar to a hackport in that you dont build everything, but it means you dont have to worry about missing those strings
We'd lose device specific stuff like dock detection, but those dont work in the first place.
Kibuuka already has the device tree up on his git repo, you could prob just use that and it'd work with a couple changes at most (hopefully, and under the assumption that you can compile android in general)
AFAIK the 'official' apktool doesnt work on API15 apks, it only supports up to API14 (4.0.1-4.0.2).
Someone's supposedly made a mod to support API15, but I havnt tried it.
Hi good work i flashed the rom and it works perfect on my ds5 but just one problem the lights for the 3 softkeys on the ds5 stays on even when you turn the screen off did i do something wrong? Please advice thanks
That's problem on every ics rom for dell streak
SULEY1 said:
Hi good work i flashed the rom and it works perfect on my ds5 but just one problem the lights for the 3 softkeys on the ds5 stays on even when you turn the screen off did i do something wrong? Please advice thanks
Click to expand...
Click to collapse
use rootdim and select night mode #1 or #2 or #3 :good:
How to change at 160dpi?
ikimradio said:
How to change at 160dpi?
Click to expand...
Click to collapse
Use LCD modder. But the dial stops working for me after sometime on that.
ikimradio said:
How to change at 160dpi?
Click to expand...
Click to collapse
goto..
settings > paranoid settings > hybrid settings > global density
and change it to your preferrence...
disable hybrid mode in case the homescreen look big...
i am currently on 120dpi and i have no problem with the dial not working... all works so far...
---------- Post added at 11:36 AM ---------- Previous post was at 11:34 AM ----------
ncik said:
Use LCD modder. But the dial stops working for me after sometime on that.
Click to expand...
Click to collapse
if you really use this rom.. dont use lcd modder.. use the built in dpi changer..
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.