Kernel Source - For Easy Cloning NCB/ND2 - Sprint Galaxy S 5 General

Nothing incredible here, just thought I'd do this to make it easy for anyone that wants to tinker with the kernel source.
I uploaded it without any changes, and will leave the master branch untouched so it can just be easily cloned​
NCB Kernel Source
git clone [email protected]:sleshepic/SM-G900P_kernel.git​
ND2 Kernel Source​git clone [email protected]:sleshepic/SM-G900P_kernel_ND2.git​​
Once more progress is made i'm sure we'll move the thread, until then, hope this helps make it one step easier getting kernel builds going.
noticed we're using the 4.7 toolchain for this one.
and here's the Readme that comes with for Ref.
################################################################################
1. How to Build
- get Toolchain
From android git server , codesourcery and etc ..
- arm-eabi-4.7
- edit Makefile
edit "CROSS_COMPILE" to right toolchain path(You downloaded).
EX) export CROSS_COMPILE= $(android platform directory you download)/android/gcc/prebuilts/linux-x86/arm/arm-eabi-4.7/bin/arm-eabi-
Ex) export CROSS_COMPILE=/usr/local/toolchain/arm-eabi-4.7/bin/arm-eabi- // check the location of toolchain
$ export ARCH=arm
$ make msm8974_sec_defconfig VARIANT_DEFCONFIG=msm8974pro_sec_klte_spr_defconfig SELINUX_DEFCONFIG=selinux_defconfig
$ make
2. Output filesS
- Kernel : arch/arm/boot/zImage
- module : drivers/*/*.ko
3. How to Clean
$ make clean
################################################################################​

This should fill in the rest to make a boot.img.
mkbootimg info:
Code:
page_size=2048
kernel_size=8014824
ramdisk_size=1760068
base_addr=0x00000000
kernel_addr=0x00008000
ramdisk_addr=0x02000000
tags_addr=0x00000100
cmd_line="console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3"
Stock Ramdisk repo: https://github.com/garwynn/SM-G900P_NCB_Ramdisk

garwynn said:
This should fill in the rest to make a boot.img.
mkbootimg info:
Code:
page_size=2048
kernel_size=8014824
ramdisk_size=1760068
base_addr=0x00000000
kernel_addr=0x00008000
ramdisk_addr=0x02000000
tags_addr=0x00000100
cmd_line="console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3"
Stock Ramdisk repo: https://github.com/garwynn/SM-G500P_NCB_Ramdisk
Click to expand...
Click to collapse
Thanks Garwynn, now we're cooking with gas.

Well this is new...

That's not good.
Sent from my SM-G900P using XDA Premium 4 mobile app

So.. Wut happened?
Sent from my SPH-L710 using XDA Premium 4 mobile app

eloko said:
So.. Wut happened?
Sent from my SPH-L710 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nothing necessarily, just noticed some possible security implementations in the kernel source. It actually built fine with it deactivated.
On a side note, have a zImage and boot.img made. Tested last night but had to start debugging recovery a Lil before we start flashing roms and kernels it seems. So have a rooted deodexed update zip, and kernel, just need to get em to flash now... huge thanks to Garwynn for help along the way

sleshepic said:
Nothing necessarily, just noticed some possible security implementations in the kernel source. It actually built fine with it deactivated.
On a side note, have a zImage and boot.img made. Tested last night but had to start debugging recovery a Lil before we start flashing roms and kernels it seems. So have a rooted deodexed update zip, and kernel, just need to get em to flash now...
Click to expand...
Click to collapse
I'll be in touch with you later today. Want to pick up where we left off but think we need to temporarily look at recovery again. And I need to do some reading in these forums to see where things stand (rooting, recovery, flashes, etc.) as I haven't touched anything post-Knox, even on my S4.

OK, testing time. Since it's not at the top of the thread I have to add here.
Warning: Your device, your responsibility. By choosing to flash you inherently and solely accept the risks of said flash.
I'm doing these by Odin because most folks know how to flash in there AND it's an easy recovery process.
So, here are the links...
NCB Stock Kernel (for restore/recovery)
Flash test in Odin, if it hangs at splash screen for more than 30 seconds, consider it hung.
Go back to download mode and flash stock kernel.
Any feedback that could be provided would be greatly appreciated.
At this point I need a verifiable boot before anything else.
Thanks!

garwynn said:
OK, testing time. Since it's not at the top of the thread I have to add here.
Warning: Your device, your responsibility. By choosing to flash you inherently and solely accept the risks of said flash.
I'm doing these by Odin because most folks know how to flash in there AND it's an easy recovery process.
So, here are the links...
NCB Stock Kernel (for restore/recovery)
NCB Source-Built Kernel (Garwynn Test #1)
Flash test in Odin, if it hangs at splash screen for more than 30 seconds, consider it hung.
Go back to download mode and flash stock kernel.
Any feedback that could be provided would be greatly appreciated.
At this point I need a verifiable boot before anything else.
Thanks!
Click to expand...
Click to collapse
Will integrate into OP when I get a chance, this is great. We're movin
Sent from my SM-G900P using XDA Premium 4 mobile app

Removing test link as it doesn't flash. I'm going to spend time on this over the weekend.

So I tried your kernel here and it hung, I have a big problem now. I try and load that stock kernel image into odin and I get the message the MD5 hash is invalid.

xSLAYERx said:
So I tried your kernel here and it hung, I have a big problem now. I try and load that stock kernel image into odin and I get the message the MD5 hash is invalid.
Click to expand...
Click to collapse
Dont worry I wouldnt say its a big issue yet. Ive had many scary flashes already with this phone (kernels via odin and philz, recovery flashes, rom flashes etc) with many hung screens and failed attempts and all have been rectified by a restore in recovery. So I will say backups are key.
Will look into a re-upload
Edit: re-uploading
Edit2: re-uploaded. Thanks garwynn!

Hmm, same link for the stock kernel? getting same error.
sleshepic said:
Dont worry I wouldnt say its a big issue yet. Ive had many scary flashes already with this phone (kernels via odin and philz, recovery flashes, rom flashes etc) with many hung screens and failed attempts and all have been rectified by a restore in recovery. So I will say backups are key.
Will look into a re-upload
Edit: re-uploading
Edit2: re-uploaded. Thanks garwynn!
Click to expand...
Click to collapse

xSLAYERx said:
Hmm, same link for the stock kernel? getting same error.
Click to expand...
Click to collapse
Just uploaded one more time. Know this is the right one because I flashed from here again to check.
If still doesn't work let me know and I'll ask rwilco12 to look into a possible server issue.

Yeah, still not working. Not sure whats going on. Im downloading stock firmware now but its gonna take me 2hrs. im not too worried yet as I can just pull the kernel from that or flash the whole damn firmware if I need to. I should have made a backup before I screwed with this but didnt think I would have problems restoring the stock kernel.
garwynn said:
Just uploaded one more time. Know this is the right one because I flashed from here again to check.
If still doesn't work let me know and I'll ask rwilco12 to look into a possible server issue.
Click to expand...
Click to collapse

xSLAYERx said:
Yeah, still not working. Not sure whats going on. Im downloading stock firmware now but its gonna take me 2hrs. im not too worried yet as I can just pull the kernel from that or flash the whole damn firmware if I need to. I should have made a backup before I screwed with this but didnt think I would have problems restoring the stock kernel.
Click to expand...
Click to collapse
Alt source: https://www.dropbox.com/s/qltmamcyrm2hvhj/SM-G900P_NCB_Kernel.tar.md5

xSLAYERx said:
Yeah, still not working. Not sure whats going on. Im downloading stock firmware now but its gonna take me 2hrs. im not too worried yet as I can just pull the kernel from that or flash the whole damn firmware if I need to. I should have made a backup before I screwed with this but didnt think I would have problems restoring the stock kernel.
Click to expand...
Click to collapse
Thank you for testing Slayer! Sorry you didnt have a backup. Maybe try the DB link?

Nope, still not working through the dropbox link either. I dont get it. You said you restored using this file. what the heck.
garwynn said:
Alt source: https://www.dropbox.com/s/qltmamcyrm2hvhj/SM-G900P_NCB_Kernel.tar.md5
Click to expand...
Click to collapse

I find it very odd that I could flash the non-working kernel but cant flash the stock kernel. freakin mysterious man.
xSLAYERx said:
Yeah, still not working. Not sure whats going on. Im downloading stock firmware now but its gonna take me 2hrs. im not too worried yet as I can just pull the kernel from that or flash the whole damn firmware if I need to. I should have made a backup before I screwed with this but didnt think I would have problems restoring the stock kernel.
Click to expand...
Click to collapse
---------- Post added at 01:11 AM ---------- Previous post was at 01:04 AM ----------
Okay weird I just ressurected my phone with the stock kernel you uploaded. I was using odin 3.07 and it wouldnt take the kernel image, and so it worked with odin 1.85. weird eh.
sleshepic said:
Dont worry I wouldnt say its a big issue yet. Ive had many scary flashes already with this phone (kernels via odin and philz, recovery flashes, rom flashes etc) with many hung screens and failed attempts and all have been rectified by a restore in recovery. So I will say backups are key.
Will look into a re-upload
Edit: re-uploading
Edit2: re-uploaded. Thanks garwynn!
Click to expand...
Click to collapse

Related

Desperately trying to get Fascinate unbricked!

I have a huge problem.
I rooted my wife's (yea...my wife's...) Fascinate last night. The root method I used worked like a charm. I installed ROM Manager. Again...no problem. Flashed ClockWork Mod no problem as well. I selected "reboot to recovery" to do a nandroid as I've done on numerous other phones. In fact, ALL of this I've done on numerous times on half a dozen different phones.
When it rebooted, instead of it being in Nandroid, it was in the regular stock recovery. My stomach sank...lol
It would just reboot...that's it. Is there a loop with the fascinate? How do I get out of it if so?
At one point, the phone wouldn't do ANYTHING...all that would happen when I plugged it in was a little computer and cell phone would pop up on the screen. No recovery, no nothing. So, after lots of digging and reading, I found the files here that I thought I'd need to reflash the system using odin. I got the /system file, the kernal and the recovery. I flashed the kernal...worked perfectly. Flashed the recovery...again, perfect (and recovery is back but still in a reboot loop...) When I try the .tar.md5 system file, it says md5 is invalid so I changed it to a straight .tar file and it worked all the way up to the very end, then it stops. That's it.
I just need the phone to work again for my wife. I don't care if I even flash a new custom rom (which I can't fine one of that works!) or if it's just simply restoring the stock system files.
ANY AND ALL HELP GREATLY appreciated, guys. Thanks!!
To get to cwm, you have to select "apply update.zip" from stock recovery. This is how fascinate and a few other galaxy s cwm works. Also don't ever delete the update.zip file from sd card.
But to start out....
Step 1: Start with Odin:
http://forum.xda-developers.com/showthread.php?t=782204
A. Flash system and pit together
B. Flash kernel
C. Flash recovery
*Important note: in Odin, always use PDA!!!! Using phone will cause huge issues.
Step 2: Flash cwm:
http://dl.dropbox.com/u/458252/CWMrecovery.tar
*note: this is an Odin file, again flash using PDA
Your phone will end up stock, rooted and with cwm.
That's very interesting. Here's why:
A) It tried to flash the update and the update failed.
B) My Vibrant didn't require this step.
So...as I was typing that, I had the tar.md5 downloading again. Apparently 4th time was a charm because it worked and I'm back up and running.
Thank you all SO MUCH for the STUPID fast replies. Very very cool!!!
Rooting aside if you want to just fix it, I can help you with that. Nothing more though. Interested?
Sent from my SCH-I500 using XDA App
rmp5s said:
That's very interesting. Here's why:
A) It tried to flash the update and the update failed.
B) My Vibrant didn't require this step.
So...as I was typing that, I had the tar.md5 downloading again. Apparently 4th time was a charm because it worked and I'm back up and running.
Thank you all SO MUCH for the STUPID fast replies. Very very cool!!!
Click to expand...
Click to collapse
What do you mean for the "stupid fast replies"?
tats_06 said:
What do you mean for the "stupid fast replies"?
Click to expand...
Click to collapse
I think he means that your replies were just as fast as geeknik's kernel. The only other interpretation is that although your replies were quite quick, unfortunately they were also stupid. But thats obviously not true, so it must be the former. ;-P
Sent from my SCH-I500 using XDA App
I think some of us are showing our ages, "stupid" is the new "awesome."
Sent from my SCH-I500 using XDA App
Hey dont worry i had same problem
http://www.mobilephonenews.info/and...fascinate-restore-is-it-really-that-easy.html go here and follow instructions!!!
then update phone manually to get latest update!! might take a few times or many times because it failed to get update many times but eventually youll get it!!
goodluck
Sherwood, in his case he needs all Odin files, not just system.
Fallingup was first to put this up, credit to his post!
Download:
Odin: http://dl.dropbox.com/u/458252/Odin%...in3 v1.3.exe
Odin Restore file for /system: http://dl.dropbox.com/u/458252/Odin%...System.tar.md5
Odin Restore file for kernel: http://dl.dropbox.com/u/458252/Odin Files/Stock-i500-VZW-Kernel.tar.md5
Odin Restore file for recovery: http://dl.dropbox.com/u/458252/Odin%...covery.tar.md5
PIT file for use in Odin Restores: http://dl.dropbox.com/u/458252/Odin%...00-VZW-pit.pit
Yea...I mean it's almost stupid how fast I got good, meaningful, educated replies.
In other words, you guys kick ass. Thanks again!!
similiar issue, please help me out.
spent 90% of the last few days of my life trying to "unbrick" my phone. i kno some of you will argue that its not really bricked but hell, a screen lighting up does not mean its more useful than a brick. anyway my problem is as follows:
the one and only thing my phone will boot to is download mode. absolutely no recovery. i have flashed via odin the stock modem system and recovery files countless times, sometimes successfully sometimes with error. even when doing so succesfullly the phone gains absolutely no functions. still download mode or black screen. only real thing i can mention that may have led to this issue is that i flashed stock kernel over voodoo lag fix without doing anything to it first. Please help.
Thanx
aabfalter said:
spent 90% of the last few days of my life trying to "unbrick" my phone. i kno some of you will argue that its not really bricked but hell, a screen lighting up does not mean its more useful than a brick. anyway my problem is as follows:
the one and only thing my phone will boot to is download mode. absolutely no recovery. i have flashed via odin the stock modem system and recovery files countless times, sometimes successfully sometimes with error. even when doing so succesfullly the phone gains absolutely no functions. still download mode or black screen. only real thing i can mention that may have led to this issue is that i flashed stock kernel over voodoo lag fix without doing anything to it first. Please help.
Thanx
Click to expand...
Click to collapse
sam problem here, i can get to cwm recoery and thats it. someone please help
justin94 said:
sam problem here, i can get to cwm recoery and thats it. someone please help
Click to expand...
Click to collapse
I had the same problem when I flashed the non-voodoo over voodoo and spent hours trying to fix the boot loop. I followed the instruction here http://forum.xda-developers.com/showthread.php?t=782204 but still running into the boot loop (recovery mode) then I flashed with the file from here via ODIN http://adrynalyne.us/files/kernels/DI01package3.tar.md5 and it restored my phone back to factory. From there you would have to do the root procedure again. Hope this helps.
anyone know where to get the update zip besides the dropbox link thsat has been dead forever??? every site i hunt on post that link. is there anywhere else to get it. both my pc get c++ runtime floating point errors when i open odin so i cannot flash with that. so i want to use the update zip but cannot find it
The update.zip to get to clockwork??
http://sharesend.com/g2jbl
First time I've ever hosted a file so let me know it if works lol.
Sent from my SCH-I500 using XDA App
This could be one of the rosiest phone ever to unbrick, unless you are a noon of coarse.
Sent from my DROIDX using XDA App
tswtech2 said:
anyone know where to get the update zip besides the dropbox link thsat has been dead forever??? every site i hunt on post that link. is there anywhere else to get it. both my pc get c++ runtime floating point errors when i open odin so i cannot flash with that. so i want to use the update zip but cannot find it
Click to expand...
Click to collapse
There is no update.zip method to unbrick. You will need to re-download a working copy of Odin or figure out how to make Odin work to do a factory restore with it.
Download the di01 complete package and use pda in odin to restore it.
http://forum.xda-developers.com/showthread.php?t=867648

CyanogenMod 7 for Nexus S - Running on Captivate [Unstable/Alpha]

I have got CM7 to boot on my Captivate using some of the same methods used to boot the stock Gingerbread ROM. I have had a lot of questions about it, so I figured I would post what I did in one location and once I (and others) start to play more, findings can be posted here.
I take credit for nothing... All I did was switched around a couple files to boot CM7 instead of GB.
Requirements
You must be root on your phone
Your /data must be converted in Ext4 by Voodoo lagfix or another Ext4 lagfix.
You must have proceed to complete backups before
Some busybox installation is also useful for tar.
Another Important note
Be absolutely 100% sure you have access to the download mode using the 3 buttons combination.
If you don't, it will be extremely difficult (even if in theory not impossible) to to flash another kernel back.
Steps:
1: Download CM7 dump to SDCARD:
2: Run the following via ADB
Code:
adb shell
su
cd /data
mkdir gingerbread
cd gingerbread
busybox tar zxvf /sdcard/CM7.tar.gz
busybox cp -a /efs efs
sync
reboot recovery
3: Flash attached "I9020_reoriented_alpha_1223.zip" via CWM Recovery
Watch CyanogenMod 7 boot on your phone!
How do I get back?
This is a dual-boot setup... Everything is still intact that you were running before this.
All you have to do is download and flash your previous kernel via ODIN. Once you do this, the phone will reboot into Froyo. Simply reinstall the I9020_reoriented_alpha_1223.zip and your back on CM7 again, just like you left it. MAGIC!
What's about this port:
- It uses the Nexus S kernel compiled from sources by supercurio that has been reoriented for the Captivate by xcaliburinhand
- It runs the exact /system image release, that I pulled from a CM7 alpha .zip file posted in the NS forums.
Which filesystem?
This is simply a mod of supercurio's early gingerbread preview, so it runs on Ext4. no RFS at all, the kernel don't support RFS.
Does everything work ?
No; will update as I discover more of what does and doesn't work.
KEEP IN MIND
CyanogenMod ROMs do not come with any Gapps and using this method, you will not be able to access CWMrecovery to flash the Gapps files floating around. I hope to have an answer to getting Gapps installed with ease by late tonight.
For now; I'm going back to work,
Thanks for all the devs who did this hard work in such a short period of time... please donate to them. I have contributed nothing thus far!
DOWNLOADS:
Dropbox: CM7.tar.gz
Dropbox: I9020_reoriented_alpha_1223.zip
Reserved for OP
What a tease. Atleast say whether or not stuff works.
I am interested though.
b0bfath3r said:
What a tease. Atleast say whether or not stuff works.
I am interested though.
Click to expand...
Click to collapse
+1
please report anything not working with this rom.
Uploading files to cut down on the amount of directions... had to manually add AT&T APN, but I was getting good network upload/download and voice... haven't tried much more than that, just got it booted about 2am last night and had to go to work at 8am... so I flashed back to GB; will be right back on this as soon as I get home this evening.
inneyeseakay said:
Uploading files to cut down on the amount of directions... had to manually add AT&T APN, but I was getting good network upload/download and voice... haven't tried much more than that, just got it booted about 2am last night and had to go to work at 8am... so I flashed back to GB; will be right back on this as soon as I get home this evening.
Click to expand...
Click to collapse
curious to see your results for
WIFI, GPS, Accelerometer???
also could you post link for the CM7 dump.
bames said:
curious to see your results for
WIFI, GPS, Accelerometer???
also could you post link for the CM7 dump.
Click to expand...
Click to collapse
More than likely... anything not working on Gingerbread won't be working here either... these ports are going to be using the same kernel, for now.
What modem did you use?
I have been using JK4....
...Download links are live!
The dump will have the look and the feel. The kernel is like the engine.
Sent from my SGH-I897 using XDA App
msm903 said:
The dump will have the look and the feel. The kernel is like the engine.
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
...and we're dropping a Corvette engine into a Camaro... both V8 w/lots of similarities; a lot of things bolt up, but it will take some tweaking to get everything working perfect.
inneyeseakay said:
...and we're dropping a Corvette engine into a Camaro... both V8 w/lots of similarities; a lot of things bolt up, but it will take some tweaking to get everything working perfect.
Click to expand...
Click to collapse
very well explained
inneyeseakay said:
...and we're dropping a Corvette engine into a Camaro... both V8 w/lots of similarities; a lot of things bolt up, but it will take some tweaking to get everything working perfect.
Click to expand...
Click to collapse
Pretty sure they moved to the nexus s kernel source and just bolting mods on now, breaking stuff on the way...
We have full source for the Nexus S, kinda confused as to why they are so bent on using AOSP and porting code over to make it the same kernel... seems like a lot of extra work for no reason to me.
Gapps
I'm testing a method I came up with to install gapps right now, it might take a while but hopefully it'll be quick and easy. I'll report back if/when I get results.
This dual boot thing is MADNESS!!! (In tone of 300) hahaha.... Gotta try this when I get home.!
My i897 just need VolUp+Pwr to enter Recovery mode,
and VolDn+Pwr to enter Download mode.
To get out of any trouble,
don't flash any bootloader, and exclude(delete) any bootloader inside any update(whatever).zip
Normally you don't need to flash or update bootloader.
However, if your phone lack of 3butt comb.,
flash a i9000 bootloader then you will have better access to Recovery and Download mode.
If anyone wanna try this NS rom,
be sure to make backup of /efs.
It store your imei, product code and all identification data,
and this partition use RFS which NS doesn't use.
johan8 said:
My i897 just need VolUp+Pwr to enter Recovery mode,
and VolDn+Pwr to enter Download mode.
Click to expand...
Click to collapse
This won't work when running this ROM
johan8 said:
If anyone wanna try this NS rom,
be sure to make backup of /efs.
It store your imei, product code and all identification data,
and this partition use RFS which NS doesn't use.
Click to expand...
Click to collapse
If you read the first post, you will see that a backup of efs is created in the ADB commands.
Haven't has a chance to check the market yet, I've been out. I should be home before too long.
Sent from my GT-I9000 using XDA App
so I tried it.. but no Gapps installed. no market. I guess i need to do soem more research.
msm903 said:
so I tried it.. but no Gapps installed. no market. I guess i need to do soem more research.
Click to expand...
Click to collapse
Read the first post... It's all stated right there...
Working on it now... been fighting with an SMS problem for the last two hours; come to find out it's a network/carrier issue, not ROM related. Ugh...

how to upgrade to froyo while retaining personal data using .zip file

so i finally decided to make the jump and give my epic some froyo love. i spent the majority of my weekend figuring out the best way to do this and wanted to share what i learned especially since this forum gave me invaluable information, scripts, and files that i pieced together to get my phone upgraded to my liking.
my phone was running a bone stock DI18 with the exception of removing a few sprint bloatware apps. what i wanted to do is install froyo DK28 while retaining my call log, text messages, 200+ apps, etc. the best way to do this is to use the DK28 zip file found here and applying it at boot. i tried flashing with odin at first but backing up and importing my old files would have been too much work.
a lot of people had problems with the update tripping up just like this--including me. so here is the workaround i came up with.
first i installed clockworkmod recovery 2.5.1.0 according to this guide. next i cracked open the DK28 zip and found the script that runs the update. it is found in META-INF > com > google > android > updater-script. i found the code with all of the asserts in it and removed the code that checked for the bloatware that most people uninstall. i also removed code that checked for the boot screen animation because that tripped my update up as well.
from there i zipped the package back up, loaded it to my sd card, and booted into clockworkmod recovery. then i went to "Install zip from sdcard", made sure that signature verification was disabled, and then chose the modified DK28 zip from the sdcard. and that's it! once it was done applying the changes i had a fresh froyo upgrade with all my personal information intact.
after that i converted the filesystem to ext4 and flashed a new rom--system only. but what you do after installing the update is up to you of course.
i'll include the "updater-script" file that i modified in case you don't want to go thru the code line by line yourself. the whole package is too large to upload with it included so you will still have to unzip this attachment, download the DK28 update, unzip the update, and replace the file by yourself but this might make it a little easier. i hope this helps someone!
this didnt work for me, nor did installing the original update.zip.
what didn't work? was there an error message?
when trying to apply the update.zip with clockworkmod recovery mode, it runs it, doesnt finish and returns to the menu. When I try it with the stock recovery mode, it errors out saying signature verification failed.
djcslice said:
when trying to apply the update.zip with clockworkmod recovery mode, it runs it, doesnt finish and returns to the menu. When I try it with the stock recovery mode, it errors out saying signature verification failed.
Click to expand...
Click to collapse
Disable signature verification in clockwork?
Also you should post this is development too! I'm sure they'll make a ot of use of this
Sent from my SPH-D700 using XDA App
djcslice said:
when trying to apply the update.zip with clockworkmod recovery mode, it runs it, doesnt finish and returns to the menu. When I try it with the stock recovery mode, it errors out saying signature verification failed.
Click to expand...
Click to collapse
do you have a bone stock version of eclair DI18? mine was with the lone exception being that i removed some of the sprint bloatware. i'll update my post because i probably should have mentioned that. there might be something in that updater-script that needs to be removed or modified to work with your setup. that's the only thing i can think of.
A_Flying_Fox said:
Also you should post this is development too! I'm sure they'll make a ot of use of this
Click to expand...
Click to collapse
i'm still pretty green here... did i post this in the wrong section?
A_Flying_Fox said:
Disable signature verification in clockwork?
Also you should post this is development too! I'm sure they'll make a ot of use of this
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I did make sure signature verification was disabled in clockwork.
n3k said:
do you have a bone stock version of eclair DI18? mine was with the lone exception being that i removed some of the sprint bloatware. i'll update my post because i probably should have mentioned that. there might be something in that updater-script that needs to be removed or modified to work with your setup. that's the only thing i can think of.
i'm still pretty green here... did i post this in the wrong section?
Click to expand...
Click to collapse
Mine is bone stock with the exception of having been rooted with clockwork and then unrooted with clockwork.
n3k said:
first i installed clockworkmod recovery 2.04 according to this guide.
Click to expand...
Click to collapse
I want to clarify for everyone that you used the version 2.04 of the all-in-one which has clockworkmod version 2.5.1.0.
DiGi760 said:
I want to clarify for everyone that you used the version 2.04 of the all-in-one which has clockworkmod version 2.5.1.0.
Click to expand...
Click to collapse
good catch! thanks i will update that
Do apps stay in as well? I will odin back to di18 just to get back the apps i cant get in dj28 lol
Sent from my SPH-D700 using XDA App
A_Flying_Fox said:
Do apps stay in as well? I will odin back to di18 just to get back the apps i cant get in dj28 lol
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
yes i think so. i saw them there but didn't test them. i had a few issues with some of the apps after i converted to ext4 and used cwm to advance restore the frankenstein rom's system underneath my data. i'm pretty sure that is what caused the problems with the apps. not the initial upgrade itself. i think i have a backup i can restore to check. i'll get back to you on that one

Unable to flash back to stock! Help please?

So, I'm trying to flash back to stock, (either GB or ICS, at this point it doesn't really matter), and PC Odin fails to flash every time it tries to write the factoryfs.img
The only way I can get myself back to a working device is if I do a battery pull, go back into download mode, re-flash CWM and do a recovery back into CM9.
I have tried mobile Odin as well, and again, the flash fails when it reaches factoryfs.img. Are my partitions all screwed up? If so, how can i fix that?
Thoughts? Help? Thanks!
What rom were you on?
Jade Eyed Wolf said:
So, I'm trying to flash back to stock, (either GB or ICS, at this point it doesn't really matter), and PC Odin fails to flash every time it tries to write the factoryfs.img
The only way I can get myself back to a working device is if I do a battery pull, go back into download mode, re-flash CWM and do a recovery back into CM9.
I have tried mobile Odin as well, and again, the flash fails when it reaches factoryfs.img. Are my partitions all screwed up? If so, how can i fix that?
Thoughts? Help? Thanks!
Click to expand...
Click to collapse
You may have a partial brick then same as per this thread
I hope I am wrong and you solve your problem ASAP without any damage
Best of luck
Note_E said:
What rom were you on?
Click to expand...
Click to collapse
IMILKA's CM9 nightly.
Jade Eyed Wolf said:
IMILKA's CM9 nightly.
Click to expand...
Click to collapse
Well there is your problem. Has nothing to do with lpy like the fear mongers blindly think. Toss another one due to CM9...
And like I mention above, it's really weird, I can CWM and still use my device just fine, but if I want to flash new firmware, it freaks out. All I can do is re-flash Chainfire's CWM recovery and restore back to where I was...
Note_E said:
Well there is your problem. Has nothing to do with lpy like the fear mongers blindly think. Toss another one due to CM9...
Click to expand...
Click to collapse
Yeah, I didn't think it had anything to do with LPY, because I still had the same issue when trying to go back to KKA.
Jade Eyed Wolf said:
And like I mention above, it's really weird, I can CWM and still use my device just fine, but if I want to flash new firmware, it freaks out. All I can do is re-flash Chainfire's CWM recovery and restore back to where I was...
Click to expand...
Click to collapse
Beginning of emmc corruption. Not fried just yet. Some recover with pit file then flashing stock gb
Good luck to you bro
Note_E said:
Beginning of emmc corruption. Not fried just yet. Some recover with pit file then flashing stock gb
Click to expand...
Click to collapse
See, that's what I was thinking too... Where can I get the correct .pit file though? I have stock KKA already downloaded; that's what I've been using for a while now for any time I have had to flash back to GB stock for whatever reason.
I have the pit file from the LP1 leak, but I don't want to use that, A) because it was from a leaked firmware, and B) because it looks like it was for the 32gb model, and mine is the 16gb.
This is the one I have: "Q1_20110919_32GB.pit"
Oh and apparently I have one called "u1_02_20110310_emmc_EXT4.pit" but since i have NO idea what that was from or what it's for, I'm not likely going to try that either...
Jade Eyed Wolf said:
I have the pit file from the LP1 leak, but I don't want to use that, A) because it was from a leaked firmware, and B) because it looks like it was for the 32gb model, and mine is the 16gb.
This is the one I have: "Q1_20110919_32GB.pit"
Oh and apparently I have one called "u1_02_20110310_emmc_EXT4.pit" but since i have NO idea what that was from or what it's for, I'm not likely going to try that either...
Click to expand...
Click to collapse
Looking now. I one you need is around here somewhere
Jade Eyed Wolf said:
I have the pit file from the LP1 leak, but I don't want to use that, A) because it was from a leaked firmware, and B) because it looks like it was for the 32gb model, and mine is the 16gb.
This is the one I have: "Q1_20110919_32GB.pit"
Oh and apparently I have one called "u1_02_20110310_emmc_EXT4.pit" but since i have NO idea what that was from or what it's for, I'm not likely going to try that either...
Click to expand...
Click to collapse
Hope this helps
Princeomi said:
Hope this helps
Click to expand...
Click to collapse
I'll give that a try. Thanks!
Just foud one in another thread http://forum.xda-developers.com/showpost.php?p=26009909&postcount=22
I was going to flash stock LC1 via pc odin cos I'm currently on LPY and I'd like to go back to GB. And I think I should ask before flashing that will it work and should I do something else than just hit lc1 in pda and flash?
Sent from my GT-N7000 using xda premium
Princeomi said:
Hope this helps
Click to expand...
Click to collapse
Sadly, those files are packaged in .7zip format. I'm at work right now, and I don't have the admin rights to install 7 zip just to extract it. Can you re-pack and post here in a regular .zip file please?
Jade Eyed Wolf said:
Sadly, those files are packaged in .7zip format. I'm at work right now, and I don't have the admin rights to install 7 zip just to extract it. Can you re-pack and post here in a regular .zip file please?
Click to expand...
Click to collapse
Here it comes
cs_allu said:
I was going to flash stock LC1 via pc odin cos I'm currently on LPY and I'd like to go back to GB. And I think I should ask before flashing that will it work and should I do something else than just hit lc1 in pda and flash?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Just flash it, if its a 3 file package put all the 3 files in their respective place, if its one file, put it in pda and flash and also make sure Kies is not running in the background
Well, at least this time the stock flash worked insofar as it completed. However, when the device reset, it went ahead saying "Installing packages" and such, and then it error'ed out saying something like there was invalid argument and it couldn't do something, then I was landed back at the stock recovery. I selected to reboot the system, and now I'm stuck at the Samsung boot animation; just keeps running indefinitely... What now?
Jade Eyed Wolf said:
Well, at least this time the stock flash worked insofar as it completed. However, when the device reset, it went ahead saying "Installing packages" and such, and then it error'ed out saying something like there was invalid argument and it couldn't do something, then I was landed back at the stock recovery. I selected to reboot the system, and now I'm stuck at the Samsung boot animation; just keeps running indefinitely... What now?
Click to expand...
Click to collapse
Hold power button and try to keep rebooting.

[Q] Installed kernel, phone is f*cked up...

Hey guys,
I've known about this whole modding thingy going on for android phones, and i've decided to give it a shot myself.
I took a backup of everything (copied everything.. didn't use any app for that. not too smart of me..)
Anyway,
I looked around and decided to install Hells Core kernel on my phone, along with Cyanogen Mod.
So after installing the SDK on my computer, unlocking the phone, rooting the phone with SuperSU and Clockwork Mod,
I got to installing the kernel.
I put it on my phone, rebooted into recovery mode, reset all data (dalvik cache and all..)
then I installed the kernel from a zip file I put on the phone, and it all went smoothly.
However, when I reboot my phone - it's all messed up!
The screen is all half yellow, and half is just black - not even text.
In the yellow part, you can hardly tell that it's the first welcome screen - because the text is too big to fit the screen.
Anyway, the whole phone is fk3d up.
I just wanna put it back to the original stock kernel and rom...
How do I do that now?
Thanks a lot guys..
This is urgent >_<
Just flash cm again without doing any wipes. It'll get rid of the kernel
Sent from my Nexus 5
jd1639 said:
Just flash cm again without doing any wipes. It'll get rid of the kernel
Sent from my Nexus 5
Click to expand...
Click to collapse
I haven't got CM on my phone,
and I can't connect it to the computer because it needs get past the welcome screen - which I can't click on any buttons!
****EDIT ****
nvm, I managed to do it
I used android toolkit, and now the computer can access the phone's internal memory.
Thanks!
***** EDIT #2 ******
Nop, doesn't work yet...
when I copy the other kernels zip's, everything seems okay
but when I reboot my nexus to install from the recovery mode, the zip are corrupted - and when I access from my computer it shows they're 0 bytes.
as if nothing was copied..
What can I do ???
***** EDIT #3 ******
Well, managed to get the phone to work!
Not getting anywhere near Hellscore now..
What I did was run 'install zip from sideload', and then from the pc I used 'adb sideload <FRANCOROCKS>.zip', and that worked
Phone's now up and running, installing my apps again.. lol
Scared to change the ROM though.. after all this >_<
capzul said:
I haven't got CM on my phone,
and I can't connect it to the computer because it needs get past the welcome screen - which I can't click on any buttons!
****EDIT ****
nvm, I managed to do it
I used android toolkit, and now the computer can access the phone's internal memory.
Thanks!
***** EDIT #2 ******
Nop, doesn't work yet...
when I copy the other kernels zip's, everything seems okay
but when I reboot my nexus to install from the recovery mode, the zip are corrupted - and when I access from my computer it shows they're 0 bytes.
as if nothing was copied..
What can I do ???
***** EDIT #3 ******
Well, managed to get the phone to work!
Not getting anywhere near Hellscore now..
What I did was run 'install zip from sideload', and then from the pc I used 'adb sideload <FRANCOROCKS>.zip', and that worked
Phone's now up and running, installing my apps again.. lol
Scared to change the ROM though.. after all this >_<
Click to expand...
Click to collapse
Because you did all this the wrong way. Learn and study before flashing anything, it's not about some simple zip flash. that simple zip file can brick your phone if flashed without knowledge.
hells core kernal is not a CM based kernal that's why you got broken screen. there is a separate thread for cm based kernals. do flash a custom rom like Mahdi slimkat etc they offer great features but only after fully understanding what you are doing
hassi4042 said:
Because you did all this the wrong way. Learn and study before flashing anything, it's not about some simple zip flash. that simple zip file can brick your phone if flashed without knowledge.
hells core kernal is not a CM based kernal that's why you got broken screen. there is a separate thread for cm based kernals. do flash a custom rom like Mahdi slimkat etc they offer great features but only after fully understanding what you are doing
Click to expand...
Click to collapse
Well, I flashed the kernel before I put the ROM, so this happened with HC kernel on stock ROM.
:X
you probably flashed the wrong version of the kernel
You did get the CM Version of Hells Core, right?
This happens to me all the time, just reflash the Roms .zip and you'll be fine.
Sorry to say that, but from your comments it's obvious that you messed up with wrong kernel's version and is not a fault of this specific kernel.
Also the zero kb downloads show bad downloads on your side again.
Sent from my ONDA A9 Core4
capzul said:
Hey guys,
I've known about this whole modding thingy going on for android phones,
Click to expand...
Click to collapse
Lol
Sent from my Nexus 4 using Tapatalk

Categories

Resources