Hi,
I figured out how to get the init.d support on the Google Nexus 7 with some research. It works on ANY Kernel and ANY ROM (Including Stock ROM/Kernel !)
All you got to do, is to flash the zip from Recovery
How do I know if it worked ?
- If in /data/local/tmp/ there is a file 'init.d_log_test.txt' and inside is written the date, it worked.
Download Here
What does init.d do?
Pariah3000 said:
What does init.d do?
Click to expand...
Click to collapse
Allow you to adds script into /system/etc/init.d and those will run at device boot. It is useful for performance tweaks and stuff like it
OK. Flashed it an it installed. Super simple MOD and it works. Now what?
I found CPU Editor: http://forum.xda-developers.com/showthread.php?t=1584508 Looks interesting,
Anyone have suggestions of other hacks that take advantage of init.d?
Pariah3000 said:
OK. Flashed it an it installed. Super simple MOD and it works. Now what?
I found CPU Editor: http://forum.xda-developers.com/showthread.php?t=1584508 Looks interesting,
Anyone have suggestions of other hacks that take advantage of init.d?
Click to expand...
Click to collapse
A script that zipalign on boot would be useful
thank you so much!
Sent from my Nexus 7 using XDA Premium HD app
ozzy666 said:
thank you so much!
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
No problem
Envoyé depuis mon Nexus 7 avec Tapatalk
Hi, I flashed this on my stock (rooted and CWM) rom and then tried Jay's Buttery Goodness thing http://forum.xda-developers.com/showthread.php?t=1855100&page=29 leaving out flashing Moteley's 1.0.5b kernel with ramdisk as I thought I should already have init.d support so it should work without doing that - but it didn't. I had to flash the 1.0.5 kernel for it to work?
You can flash this on any kernel and it should work
Sent from my Nexus 7 using Tapatalk 2
The kernel needs init.d support, which I believe most ''aftermarket" ones do, if not all. Only ones that dont are usually the 100% stock ones.
You need to decompile the kernel, and edit a couple scripts to get it to work if it doesn't already. The kitchen will do it, but its kinda a pain if our don't know what to do.
Edit #1: Idk man. From ripping through your mod and having recently gone through all this. Pretty positive this won't work on a stock kernel unless it's modded. And the files are a little off from everything I've looked into doing my own homework on it.
Edit #2: I think I see what you did and I didn't know what that file actually was (used to it being named differently) and that this process was even possible. Believe your using "post boot" to run init.d, correct?
jamesst20 said:
You can flash this on any kernel and it should work
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
It's not working for me with stock kernel, however it does work with Motley, I haven't tried other kernels yet.
It does work with the stock kernel, you're doing something wrong
Sent from my Nexus 7 using Tapatalk 2
Which version of busybox is included? It may be an issue with ramdisk support rather than init.d support, as Jay's script depends on ramdisk. If I get time later I'll try it myself on your JRO03S ROM.
z1gackly said:
Which version of busybox is included? It may be an issue with ramdisk support rather than init.d support, as Jay's script depends on ramdisk. If I get time later I'll try it myself on your JRO03S ROM.
Click to expand...
Click to collapse
Yea, it must be the ramdisk thing as it works only after flashing the 1.0.5 Motley kernel with the stock ramdisk.
That was the step I was trying to cut out of Jay's instructions, I thought it might be ok to do that after flashing James' zip.
All I do is flash this, but will it work on a cleardroid rom stock, I'm running big boy kernel, if that helps. I guess I better just do a backup and try it out myself lol thanks guys
Sent from my Desire HD using xda app-developers app
---------- Post added at 08:07 PM ---------- Previous post was at 07:28 PM ----------
Thanks for your help, and work
Sent from my Desire HD using xda app-developers app
I just flashed this through recovery and now my Nexus 7 won't boot into anything (just sits at the Google screen) except the bootloader.
Here's what I have:
Team EOS nightly, #137
Faux 123 kernel, v012b8
TWRP recovery
So I downloaded the .zip file from the OP, and flashed it in recovery. Then wiped cache/dalvik. Hit reboot and it just sat at the Google screen, didn't come up to the boot animation. So I hold the power button until it restarts, and go into the bootloader. Then tried to go into recovery so I could factory reset and reflash the Team EOS rom/kernel, but it wouldn't go into recovery (just sat at the Google screen).
Next I thought to check to see if I'd be able to flash anything through my PC while in the bootloader. No go... 'fastboot devices' doesn't detect anything.
Any help that can be provided would be appreciated!
EDIT: A combination of powering off and booting back into the bootloader enabled fastboot to connect. Flashed the stock 4.1.2 image (downloaded straight from Google). Was able to get back in, flashed TWRP, flashed Team OES latest nightly, flashed GApps, flashed faux 123 kernel, booted up and did all of the initialization stuff.
Just booted back into recovery to install the Jamesst20 - init.d.zip file. Installed it, and rebooted. It's been sitting at the Google screen for a few minutes now, and at one point my PC detected it with ADB devices. I'll continue to wait and see if anything happens.
EDIT 2: Waited about 15mins and called it quits. This time I was able to go directly back into recovery, factory reset, install Team EOS zip, and then installed the Jamesst20 - init.d.zip file. Same issue, just won't work. So I confirmed it wasn't the faux 123 kernel causing the issue... wonder if the Team EOS ROM just doesn't like this init.d utility.
I believe the TeamEOS ROM already has init.d support, so I'm not quite sure why you would want to flash this with it anyway?
z1gackly said:
I believe the TeamEOS ROM already has init.d support, so I'm not quite sure why you would want to flash this with it anyway?
Click to expand...
Click to collapse
Eventually I kinda came to that conclusion too. But I still haven't found any documentation from Team EOS saying that they support init.d specifically for the N7 (they say they're using a stock or stock-variant kernel). What makes me think it does support init.d is that I've read most "aftermarket" ROMs/kernels support init.d
So I suppose the issue here for me is that this ZIP file caused a non-bootable device, despite being advertised for "ANY ROM/Kernel". If the developer here isn't concerned with this, I'll leave it alone. Otherwise I'd be happy to provide logs or whatever it would take to troubleshoot the problem.
Hi,
Well download my init.d zip, extract it and get the script from etc/init.d folder and place it on your device in system/etc/init.d. I think the script is called datetest or something like it. Don't forget to put 7777 permissions on the script in your device and then reboot. If /data/local/tmp/init.d_log_test.txt exist with the current date and time, init.d supports is already there
Sent from my Nexus 7 using Tapatalk 2
Good work I used this for badaman80 big boy kernel
Sent from my Inspire 4G using xda premium
Related
Heres the rooted version....
Rooted
Deodexed
Busybox installed
Crt off animation(cause stock is boring.. )
Installation:
1 Download zip
2 Boot into CWM
3 Wipe data, cache and dalvik cache
4 Choose zip from sd card
5 flash zip
6 reboot and let media scanner run and sit for a few and let it settlle and sync accounts.
7 Enjoy
To get video back flash stock kernel with sgs kernel flasher here:http://www.multiupload.com/PP69TXBEA5
UNPACK RAR AND FLASH ZIMAGE ONLY!
OKAY....I HAVE NOT PERSONALLY HAD THIS ISSUE, BUT TO BE SAFE, BEFORE FLASHING STOCK KERNEL , BOOT INTO CWM, SCROLL DOWN TO VOODOO AND DISABLE VOODOO LAGFIX. WHEN IT BOOTS YOU WILL HERE THE SEXY LADY DISABLING VOODOO. WHEN IT FULLY BOOTS BACK UP YOU SHOULD BE ABLE TO FLASH STOCK KERNEL WITHOUT ISSUES.
ONCE AGAIN, I AM NOT RESPONSIBLE IF YOUR PHONE SPONTANEOUSLY COMBUSTS...
Download Rom Here
Thanks going to try it out
Sent from my SGH-I997 using xda premium
Man you're fast. I just got the leak, didn't even have time to uncompress it.
Excellent. So if we flash the stock kernel and get video working again, what are we losing in the process? Sorry if this is a noobish question, I'm just now switching from galnet MIUI.
Shouldnt lose anything...and you will keep root also...
Sent from my SAMSUNG-SGH-I997 using xda premium
You gain video and hdmi back. You may have to make a slight change to one of the void files if you lose access to your CD card.
I see. Thank you for the help! I was told about this file before, but when I tried editing it last time I messed it up... don't you edit the last value to a different number or something? Do you know what number that is? Thank you guys for the help, I really do appreciate it, what with all these awesome leaks. :]
Truckerglenn said:
You gain video and hdmi back. You may have to make a slight change to one of the void files if you lose access to your CD card.
Click to expand...
Click to collapse
You will also lose your voodoo filesystem optimizations, init scripting support and the charginghacks/undervolt capabilities (if you like Entropy's kernel).
Well I enjoyed it for 5 minutes before going back to cm7 with thunder script but I still appericate the upload as something different always looking for my next rom fix.
Sent from my SGH-I997 using xda premium
You either change a 3 to a 2 or a 2 to a 1 forget which right now.
Go here for the correct fix for the SD Card: http://forum.xda-developers.com/showpost.php?p=19908483&postcount=24
Truckerglenn said:
You either change a 3 to a 2 or a 2 to a 1 forget which right now.
Click to expand...
Click to collapse
If you have flashed the stock kernel and want external SD: In vold.fstab, in the line that starts with dev_mount sdcard1, change from mmc2 to mmc1
I feel pretty dumb right now. I flashed the leak and then uses sgs kernel flasher to flash the stock kernel and my phone is now stuck at the Samsung splash screen upon reboot. I let it sit there for about 10 minutes. Now, I can't even get back to recovery mode. Could someone provide some advice?
Did u pull the zimage out of the rar fike? or did you flash the rar file?? i posted in op to unpack the zimage from the rar file...i know it works becaise i flashed the stock kernel and am runni.g it now....running great actually
Sent from my SAMSUNG-SGH-I997 using xda premium
devilock138 said:
I feel pretty dumb right now. I flashed the leak and then uses sgs kernel flasher to flash the stock kernel and my phone is now stuck at the Samsung splash screen upon reboot. I let it sit there for about 10 minutes. Now, I can't even get back to recovery mode. Could someone provide some advice?
Click to expand...
Click to collapse
Don't you have to convert you file system back before flashing the stock rom?
Yes, I unpacked the zimage file from the .rar and sgs kernel flasher rebooted the phone automatically after applying it.
---------- Post added at 09:09 PM ---------- Previous post was at 09:09 PM ----------
rxnelson said:
Don't you have to convert you file system back before flashing the stock rom?
Click to expand...
Click to collapse
I didn't realize that this used a different filesystem
No you dont...i didnt..runs great
Sent from my SAMSUNG-SGH-I997 using xda premium
devilock138 said:
I didn't realize that this used a different filesystem
Click to expand...
Click to collapse
Did you disable voodoo lagfix in recovery before flashing the stock kernel? Not doing that can cause issues, if I'm understanding this correctly.
You dont have to disable voodoo....all i did was flash thru sgs and it booted up fine...if you are stuck however then disabling voodoo might fix your problem
Sent from my SAMSUNG-SGH-I997 using xda premium
jscott30 said:
Did you disable voodoo lagfix in recovery before flashing the stock kernel? Not doing that can cause issues, if I'm understanding this correctly.
EDIT: Nevermind - I don't know what I'm talking about in this case. That's not it.
Click to expand...
Click to collapse
No, I don't believe I had any lagfixes.
I was running stock froyo with only root and cwm installed
I downloaded the .zip for the leak
booted into recovery and wiped data/cache/dalvik
flashed the leak
phone booted up fine
installed sgs kernel flasher from the market
extracted zimage file from the .rar in the op
used sgs kernel flasher to flash the kernel
phone rebooted and now stuck at samsung screen
I've pulled the battery and then tried to reenter recovery mode, but no dice
I am going to try unbrick through download mode and heimdal
Ok..well i didnt know you were coming from froyo...i dont know how flashing this from froyo would work since i cant even remember when i ran froyo last. I came from my catyrom....might need to be on gingerbread with gingerbread bootloaders ...
Sent from my SAMSUNG-SGH-I997 using xda premium
What is this?
Repacked recoveries with the kexec kernel that mkasick provides here.
Why do I need this?
In short, this allows you to use your recovery as a psuedo bootloader or boot menu.
Unless you are familiar with kexec, your probably don't need it. What it allows (follow mkasick's linked to guide) is a way to boot custom boot.img's from the sdcard from within your recovery partition. The first way the custom boot.img was booted was by flashing it to the recovery partition which was not signature checked. This is great, but you lose the use of the recovery partition.
By using these recoveries and mkasick's method of booting custom boot.img's from the recovery, we get to keep recovery and boot custom boot.img's.
How do I install?
Same as Invisiblek's method.
How did you repack the recovery.img?
Typically you can repack boot.img or recovery.img with relative ease. This is the case with the GSIII, but it requires more command line options added to mkbootimg than normal. Mkasick has outlined the way he accomplishes this in his Github repo for d2vzw kernel source with kexec patches. Give him thanks for this, I just am noting how he does this for others to use and reference below:
Code:
Pull recovery partition from device:
adb reboot recovery
adb root
adb shell 'dd if=/dev/block/mmcblk0p18 of=/tmp/recovery.img bs=256k'
adb pull /tmp/recovery.img
Merge Kexec kernel into image:
../cm/out/host/linux-x86/bin/unpackbootimg -i recovery.img
cp arch/arm/boot/zImage recovery.img-zImage
../cm/out/host/linux-x86/bin/mkbootimg --kernel recovery.img-zImage \
--ramdisk recovery.img-ramdisk.gz \
--cmdline "console=null androidboot.hardware=qcom user_debug=31" \
--base 0x80200000 --pagesize 2048 --ramdiskaddr 0x81500000 \
-o recovery.img
Attachments
Touch based CWM and TWRP, the raw kexec kernel, and I have included the mkbootimg binary that I compiled which allows for the --ramdiskaddr option, which was only added recently. My old versions would not work, and that option is absolutely needed or the image will not boot.
Thank you so much for this!
Sent from my SCH-I535 using xda app-developers app
Are there any kernels out there to use this great method on? Golly I really want to use this
ftmaniac948 said:
Are there any kernels out there to use this great method on? Golly I really want to use this
Click to expand...
Click to collapse
Can pickup invisiblek's overclock kernel over at rootz
Sent from my SCH-I535 using xda app-developers app
So we would we be able to reboot without losing invisible's kernel???
Sent from my SCH-I535 using Tapatalk 2
With twrp.
So I don't know about anyone else but I cannot get it to boot a kernel as when I flash the reboot script in twrp it won't reboot on its own.
Twrp has always seemed to have this issue.
Sent from my SCH-I535 using xda app-developers app
Oh my lord Suddenly going home to my galaxy sIII in a few days will be all the more exciting since i won't be waiting for a developer phone anymore
---------- Post added at 06:56 AM ---------- Previous post was at 06:37 AM ----------
And i know it probably sounds dumb to ask, but what exactly do we need to do to setup kexec so its working? I hate asking how to do it, and i don't think ive ever done it before but a simple 1.2.3.4.etc would be very helpful
and what do i do with mkbootimg.zip?
Does this give us the ability to backup/restore/flash roms/kernels?
Excuse my ignorance, but with this recovery/Kexec, does the Verizon version of the Galaxy S III support custom ROMs now? Can we get 4.1 on the Galaxy S III now?
Neverendingxsin said:
and what do i do with mkbootimg.zip?
Click to expand...
Click to collapse
I'm wondering this too. I know how to get CWM Touch installed, but do I then just flash that or what? I'm new to kexec but I really wanna get invisiblek's kernel installed.
thekendog said:
I'm wondering this too. I know how to get CWM Touch installed, but do I then just flash that or what? I'm new to kexec but I really wanna get invisiblek's kernel installed.
Click to expand...
Click to collapse
im in the same boat. CWM touch is easy to do, but that zip im kinda left going "uhhhh what?" haha
once i know how to use this kexec thing perfectly ill be good to go, but when it comes to learning i need easy help
Download VZW GS3 EZ recovery from the market. It does everything for you. There is a thread about it over on RootzWiki. I'm running invisiblek's kernel right now and all it took was a few taps.
thekendog said:
Download VZW GS3 EZ recovery from the market. It does everything for you. There is a thread about it over on RootzWiki. I'm running invisiblek's kernel right now and all it took was a few taps.
Click to expand...
Click to collapse
This maybe easier but this method allows you to keep recovery.
Sent from my SCH-I535 using Tapatalk 2
For those of you who have tried this have you put the device to any stress, compared benchmarks to that of stock? What about gaming, not a big gamer personally but that could be a good test.
Thanks
Sent from my SCH-I535 using Tapatalk 2
Neverendingxsin said:
Oh my lord Suddenly going home to my galaxy sIII in a few days will be all the more exciting since i won't be waiting for a developer phone anymore
---------- Post added at 06:56 AM ---------- Previous post was at 06:37 AM ----------
And i know it probably sounds dumb to ask, but what exactly do we need to do to setup kexec so its working? I hate asking how to do it, and i don't think ive ever done it before but a simple 1.2.3.4.etc would be very helpful
and what do i do with mkbootimg.zip?
Click to expand...
Click to collapse
Read the whole post. It shows others how I re packed the images. I used the mkbootimg to do so.
Does this have the OC kernel built in
Sent from my SCH-I535 using xda premium
Can someone create a walkthrough for things please?I would love to my recovery and invisible OC kernel
Sent from my SCH-I535 using xda premium
justinglock40 said:
Can someone create a walkthrough for things please?I would love to my recovery and invisible OC kernel
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
i made a guide on the kexec in one of my threads. Full step by step method with the invisiblek oc kernel.
http://forum.xda-developers.com/showthread.php?t=1771398
[GUIDE] [All-In-One] [Step-By-Step] Root, Custom Recoveries, ROMs, Kernels, and Kexec
Sent from my locked Verizon Samsung Galaxy S III
Dk if this got overlooked as most people don't even know what this is. Anyone else successfully get TWRP to work with Kexec? I flash the kexec zip to boot either from sdcard or emmc and either way, with the boot.img in both places, the phone doesn't autoreboot like on cwm, and then when I boot manually after, it just loads up stock kernel.
nosympathy said:
Dk if this got overlooked as most people don't even know what this is. Anyone else successfully get TWRP to work with Kexec? I flash the kexec zip to boot either from sdcard or emmc and either way, with the boot.img in both places, the phone doesn't autoreboot like on cwm, and then when I boot manually after, it just loads up stock kernel.
Click to expand...
Click to collapse
I also flashed the Kexec enabled TWRP rec, but for some reason I cant even see the zip files I leave on the sdcard, or root, or anywhere. Its weird.
Hey I'm looking for someone to point mebin the right direction with this. I've recently came back to my infuse after have the skyrocket which was pretty nice. While I had the skyrocket a senior member and awesome developer over there called "sk8erwitskil" had a recovery that was pretty cool. He told me in order to make this available on the infuse I need to take his source and compile in the cm10 repo. As im not to familiar with compiling and development, is there anyone willing to give this a shot?
Here is the link to the source if anyone is willing and I'm going to stay busy researching this myself.
https://github.com/sk8erwitskil/touch_recovery_cm10
Also, here is a link to original thread if anyone is wanting to check it out, I think it would be awesome to have this for the infuse
http://forum.xda-developers.com/showthread.php?t=1777970
Sent from my SGH-I997 using xda premium
mrwattz405 said:
Hey I'm looking for someone to point mebin the right direction with this. I've recently came back to my infuse after have the skyrocket which was pretty nice. While I had the skyrocket a senior member and awesome developer over there called "sk8erwitskil" had a recovery that was pretty cool. He told me in order to make this available on the infuse I need to take his source and compile in the cm10 repo. As im not to familiar with compiling and development, is there anyone willing to give this a shot?
Here is the link to the source if anyone is willing and I'm going to stay busy researching this myself.
https://github.com/sk8erwitskil/touch_recovery_cm10
Also, here is a link to original thread if anyone is wanting to check it out, I think it would be awesome to have this for the infuse
http://forum.xda-developers.com/showthread.php?t=1777970
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
The problems with custom recoveries is that they are built into the boot.img
With that said as soon as you flash a ROM and reboot your recovery will be replaced with whatever is in the ROM you just flashed (cwm)
So basically a recovery is a one time thing and you have to keep flashing the kernel after every ROM flash.
Back in the ICS days, there was twrp (also a touch recovery...and my favorite recovery) which had a special install script that basically opened up the boot.IMG and injected the recovery and did this automatically after every ROM flash. However, since the switch to mtd I have not been able to figure out how to get the script to work nor has anyone else
Basically what I'm getting at here is that anything besides cwm is pointless due to the fact that after flashing a ROM you lose the recovery. Not to mention your boot.IMG/recovery will quickly be outdated is there is always various kernel fixes going on
Sent from my SGH-I997 using Tapatalk 2
mg2195 said:
The problems with custom recoveries is that they are built into the boot.img
With that said as soon as you flash a ROM and reboot your recovery will be replaced with whatever is in the ROM you just flashed (cwm)
So basically a recovery is a one time thing and you have to keep flashing the kernel after every ROM flash.
Back in the ICS days, there was twrp (also a touch recovery...and my favorite recovery) which had a special install script that basically opened up the boot.IMG and injected the recovery and did this automatically after every ROM flash. However, since the switch to mtd I have not been able to figure out how to get the script to work nor has anyone else
Basically what I'm getting at here is that anything besides cwm is pointless due to the fact that after flashing a ROM you lose the recovery. Not to mention your boot.IMG/recovery will quickly be outdated is there is always various kernel fixes going on
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Mg was the injection the only big in jb? To have twrp I wouldn't mind flashing over and over
Sent from my IPhone using Tapatalk
mg2195 said:
The problems with custom recoveries is that they are built into the boot.img
With that said as soon as you flash a ROM and reboot your recovery will be replaced with whatever is in the ROM you just flashed (cwm)
So basically a recovery is a one time thing and you have to keep flashing the kernel after every ROM flash.
Back in the ICS days, there was twrp (also a touch recovery...and my favorite recovery) which had a special install script that basically opened up the boot.IMG and injected the recovery and did this automatically after every ROM flash. However, since the switch to mtd I have not been able to figure out how to get the script to work nor has anyone else
Basically what I'm getting at here is that anything besides cwm is pointless due to the fact that after flashing a ROM you lose the recovery. Not to mention your boot.IMG/recovery will quickly be outdated is there is always various kernel fixes going on
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
ok i understand this but this is cwm if that makes a difference. but if not i guess it was worth a shot. and is the whole thing with our roms being MTD the main issue with this or am i just lost and wishing upon a star?
Hi – I have a stubborn issue with my Blaze 4G not working on CM roms, I would appreciate any help you guys can provide. Below are the details:
I recently bought a T-Mobile Samsung Galaxy S Blaze 4G, and did the following:
- Rooted it using the following guide (it now has ICS)
- SIM Unlocked it using the following guide (now it works on other networks)
- Updated to CWM 6.0.3.8, since JB roms needs it
- Flashed the T769-UVLH5 modem, since CM support it
And now when I flash CM 10 stable or 10.2 nightly it gets stuck in booting and displaying the CM logo animation screen, after few minutes it reboots and does it all over again.
I remember when I upgraded to CM JB on my SGS3 I needed to flash a JB stock rom on it to get the new boot loaders for JB, but I saw no mention of this on this forum. What else am I missing?
Thanks.
TINGEA said:
Hi – I have a stubborn issue with my Blaze 4G not working on CM roms, I would appreciate any help you guys can provide. Below are the details:
I recently bought a T-Mobile Samsung Galaxy S Blaze 4G, and did the following:
-Rooted it using the following guide (it now has ICS)
-SIM Unlocked it using the following guide (now it works on other networks)
-Updated to CWM 6.0.3.8, since JB roms needs it
-Flashed the T769-UVLH5 modem, since CM support it
And now when I flash CM 10 stable or 10.2 nightly it gets stuck in booting and displaying the CM logo animation screen, after few minutes it reboots and does it all over again.
I remember when I upgraded to CM JB on my SGS3 I needed to flash a JB stock rom on it to get the new boot loaders for JB, but I saw no mention of this on this forum. What else am I missing?
Thanks.
Click to expand...
Click to collapse
You wiped data/cache/system? Reinstall it. Anyways use the new 6.0.4.4 recovery.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Somcom3X said:
You wiped data/cache/system? Reinstall it. Anyways use the new 6.0.4.4 recovery.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom. I have to admit that I forgot to do the wipes. but even after doing the wipes (data/system/ factory rest/ cach/devalk) and reinstalling the CM nightly, I still have the same issue.
as for recovery, I updated to the latest version using the rom manager, and according to the official site clockworkmod[dot]com[slash]rommanager (can't post links) I have the latest version for Blaze. how do you get the 6.0.4.4 on blaze?
I still feel it's a ICS vs JB bootloaders issue, but not sure how to proceed next.
Thanks!
TINGEA said:
Thanks Somcom. I have to admit that I forgot to do the wipes. but even after doing the wipes (data/system/ factory rest/ cach/devalk) and reinstalling the CM nightly, I still have the same issue.
as for recovery, I updated to the latest version using the rom manager, and according to the official site clockworkmod[dot]com[slash]rommanager (can't post links) I have the latest version for Blaze. how do you get the 6.0.4.4 on blaze?
I still feel it's a ICS vs JB bootloaders issue, but not sure how to proceed next.
Thanks!
Click to expand...
Click to collapse
No boot loaders man. This is before Samsung's complications.
Recovery is here.
http://d-h.st/AFu
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Thanks Somcom3X, but still didn't work. When installing the CM room in recovery 6.0.4.4 I get a bunch of getprop assert failures. This used to work on the previous version (6.0.3.8). Now the Rom won't install.
Also, I'm curious what did you mean by this is before Samsung's complications?
Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
TINGEA said:
Thanks Somcom3X, but still didn't work. When installing the CM room in recovery 6.0.4.4 I get a bunch of getprop assert failures. This used to work on the previous version (6.0.3.8). Now the Rom won't install.
Also, I'm curious what did you mean by this is before Samsung's complications?
Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
After 2011 samsung began installing software and counters to try and prevent people from rooting and installing custom firmwares.
knox is an example of this.
These devices don't have any of that complicated security.
You handy with odin? Your recovery is not right. Just to be clear, what is your model number?
If it is T 7 6 9, your good to go to odin. I'd recommend going back to stock, and then install a recovery and you should be good to go.
Somcom3X said:
After 2011 samsung began installing software and counters to try and prevent people from rooting and installing custom firmwares.
knox is an example of this.
These devices don't have any of that complicated security.
You handy with odin? Your recovery is not right. Just to be clear, what is your model number?
If it is T 7 6 9, your good to go to odin. I'd recommend going back to stock, and then install a recovery and you should be good to go.
Click to expand...
Click to collapse
Thanks again, I use the guide here to convert the image into a tar.md5 to flash using odin, but after flashing successfully I still have the same issue when installing the CM zip file in recovery, and yes it is the T-mobile Samsung Galaxy S Blaze 4G T769.
any other possible causes?
BTW - when I was flashing via Odin my upload phone screen was showing that I have a custom rom and the counter was 1.... do I need to fix that?
TINGEA said:
Thanks again, I use the guide here to convert the image into a tar.md5 to flash using odin, but after flashing successfully I still have the same issue when installing the CM zip file in recovery, and yes it is the T-mobile Samsung Galaxy S Blaze 4G T769.
any other possible causes?
Click to expand...
Click to collapse
SOLUTION:
The reason your stock recovery system keeps getting overwritten at Android startup is because of a script that is being run.* All you need to do is either rename this script or simply delete it.
Please keep in mind that if you restore your stock ROM, this script will be restored with it so you will have to rename or delete it again.* Do the following:*
1.
Make sure your device is powered on and running normally,
2.
Make sure you have rooted your device and that you have all of the necessary permissions in order to manipulate system files.*
3.
In the root file system go to \system\etc
4.
Find the file named install-recovery.sh and either rename it or, as I did, delete it.*
That’s all there is to it.*
Please keep in mind that you will need to flash your custom system recovery one more time after modifying the script file.* After that, reboot away and you will always be able to get back into your new system recovery.
Good Luck and Happy Tweaking.
Click to expand...
Click to collapse
Try that.
Found it here http://mark.candleshoreblog.com/201...-factory-stock-roms-at-android-system-reboot/
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Somcom3X said:
Try that.
Found it here http://mark.candleshoreblog.com/201...-factory-stock-roms-at-android-system-reboot/
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom3X - but I'm not sure this is needed for my case. I read the original blog post and my recovery does not get overwritten. I actually rebooted multiple times into CWM recovery and each time it is the same 6.0.4.4.
I also went into the /system/etc folder and there is no install_recovery.sh file.
to clarify, here is where I'm stuck now:
- when I use CWM 6.0.3.8 CM install completes successfully, but then CM will not boot, and will keep on cycling on the boot logo screen.
- when I use CWM 6.0.4.4 I can't start to install CM as it complained that my phone is not t769.
in all cases I'm using CM 10.2 nightly for T769.
Thanks for the help.
You should delete assert lines at the top of the zip's updater-script and it will let you flash it.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
I removed the assert lines from the updater script, and it was able to complete the install process afterwards, however when I booted the new CM 10.0 system it got stuck on the cyanogenmod boot logo. I made sure I do a system/data rest, cleared cash, and cleared devalk.
I do not think it's an issue with my recovery as I'm getting the same result as I did with the official 6.0.3.8.
Something else is going on.
Any ideas?
Thanks.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
TINGEA said:
I removed the assert lines from the updater script, and it was able to complete the install process afterwards, however when I booted the new CM 10.0 system it got stuck on the cyanogenmod boot logo. I made sure I do a system/data rest, cleared cash, and cleared devalk.
I do not think it's an issue with my recovery as I'm getting the same result as I did with the official 6.0.3.8.
Something else is going on.
Any ideas?
Thanks.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Tar back to stock GB. Upgrade to ICS. Then root and install cwm. Flash away
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Somcom3X said:
You should delete assert lines at the top of the zip's updater-script and it will let you flash it.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom3X - but this is more trouble than what I wanted to put in - I'll stick with the rooted stock ROM I have. I was hoping the process was a little more straight forward, similar to my SGS3.
thanks for all your help thus far!
Somcom3X said:
Tar back to stock GB. Upgrade to ICS. Then root and install cwm. Flash away
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Ok, my rooted ICS stock is acting up (random shutdowns and such), so I need to give this another try and get this phone to CM.
I tared back to stock GB, skipped the upgrade to ICS (was not able to upgrade via the ROM software update option), flashed CWMR (5.0.4.x) via Odin, upgraded to CWMR 6.0.4.5, installed CM 11 nightly, and then wiped data/factory rest and Dalvik .... and ....
it is still stuck on the boot screen....
I seriously would appreciate a silver bullet right now!
TINGEA said:
Ok, my rooted ICS stock is acting up (random shutdowns and such), so I need to give this another try and get this phone to CM.
I tared back to stock GB, skipped the upgrade to ICS (was not able to upgrade via the ROM software update option), flashed CWMR (5.0.4.x) via Odin, upgraded to CWMR 6.0.4.5, installed CM 11 nightly, and then wiped data/factory rest and Dalvik .... and ....
it is still stuck on the boot screen....
I seriously would appreciate a silver bullet right now!
Click to expand...
Click to collapse
Hmm. Go back to stock ics, flash a 10.2 recovery, then flash whatever you desire.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
What is a10.2 recovery? Is it a certain version of CWMR? And do I need to flash it via Odin? Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
TINGEA said:
What is a10.2 recovery? Is it a certain version of CWMR? And do I need to flash it via Odin? Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
It would be cwm 6.0.2.7
You can flash the img through a zip or by terminal on the phone.
Odin needs a tar'd recovery img
Sorry been very busy.
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=2577265
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Thanks Somcom3X - I looked all over this forum and the internet, and could not find a link for a 6.0.2.7 CWM for Blaze - I found it for other phones but not Blaze. can you please point me to a link if you happen to know of one. the official site does not have an archived list of previous versions.
as for the provided link, I did follow it through, and downloaded the recovery Tar (it was CWM 5.5.04) but that yielded the same results after installing CM 10 and 10.2 - stuck at boot screen logo. I'm reasonably confident now that it is not a recovery issue, as I flashed half a dozen different versions and none worked with CM 10, 10.2, or 11.... it has to be something else!
Thanks.
TINGEA said:
Thanks Somcom3X - I looked all over this forum and the internet, and could not find a link for a 6.0.2.7 CWM for Blaze - I found it for other phones but not Blaze. can you please point me to a link if you happen to know of one. the official site does not have an archived list of previous versions.
as for the provided link, I did follow it through, and downloaded the recovery Tar (it was CWM 5.5.04) but that yielded the same results after installing CM 10 and 10.2 - stuck at boot screen logo. I'm reasonably confident now that it is not a recovery issue, as I flashed half a dozen different versions and none worked with CM 10, 10.2, or 11.... it has to be something else!
Thanks.
Click to expand...
Click to collapse
I'm very sorry for the delay. Been very very busy.
https://www.dropbox.com/s/awp1zy4u3x34a2v/CWM-cm-10.2-Recovery-t769.zip
That is my personal 10.2 recovery. Works fine for me.
The author is me, but I was too lazy to change the lines.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Allright kids...with the release of a firewater S-OFF method for the VZW M8 apparently around the corner...I got a little antsy. I noticed we have no resources available when we do get the ability to play, so I decided to go ahead and put together a few things for those of you who will undoubtedly follow and want to start cooking your own ROMS.
Here's what I've got for you:
STOCK ROOTED/DEODEXED/BUSYBOX/INIT.D ENABLED/DEBLOATED ROM
So obviously, I can't test this yet. But I'd be astonished if it didn't work. This should be a fully rooted, fully flashable stock ROM you can use once we have S-off and a custom recovery. The boot.img has been modified to fix system write and add init.d support for all your scripting pleasures. All apks and jars have been deodexed and zipaligned.
In short, you should be able to use this for whatever creations you want out of the box once we are unlocked and running.
(not working yet, files for dev purposes only ATM)
ROM DOWNLOAD
Kernel Source
VZW-SPECIFIC/BLOAT APPS
This will be a separate .zip including all the stuff that just makes the ROM big and clunky. Devs can choose to re-add these to the ROM, but I will not distribute the bloatware with the stock ROM. If you want to grab an extra 500MB of crap...have at it.
DOWNLOAD HERE
COMPLETE PARTITION LIST
A full enumeration of the partitions on the VZW M8, along with their names. Useful for creating update scripts.
Gdoc
CSV
STOCK RECOVERY/HBOOT/BOOT IMAGE
Because when you play, you sometimes need to fix things. Very possible I will upload a full dump as time permits, but for now, here are the basics should you screw something up once the doors are open...
Recovery.img
Boot.img
Hboot.img
Hopefully, this will not be seen as a placeholder thread. I've got the stock deodexed/rooted just about done...I just need the proper update-binary to make it usable when we have the ability to flash stuff. I will be keeping this updated with goodies as they are to be found.
https://drive.google.com/folderview?id=0B0OpOqUNqeKkWXI2S0RScmM1S0k&usp=sharing
Here is the link to the full directory of resources that I am uploading to in Drive. The stock rooted is about 72% uploaded, and the apps package will follow...but I'm lazy and feel like taking a nap.
Apps are not a flashable at this time...but then again, that really doesn't matter because we can't flash anything yet. They're just there to be added to the base ROM to make it the full system dump. Once we can actually flash, I will begin cataloging which apps can be further removed without any detriment to the system.
I really look forward to the M8 S-Off. I think this is the phone I will get my hands dirty with.
chriskader said:
I really look forward to the M8 S-Off. I think this is the phone I will get my hands dirty with.
Click to expand...
Click to collapse
Nice.
Looks great!
Sent from my ASUS Transformer Pad TF300T using XDA Premium 4 mobile app
Awesome. Great prepping. Thanks.
Sent from my dlx using xda app-developers app
Nice work. Already downloaded the rooted stock image and the recovery, hboot and boot images. Nice to have them all in one spot.
Mike02z said:
Nice work. Already downloaded the rooted stock image and the recovery, hboot and boot images. Nice to have them all in one spot.
Click to expand...
Click to collapse
just flashed your boot.img from the rom and it would not boot
You have a working recovery already?
grimlocksmash said:
You have a working recovery already?
Click to expand...
Click to collapse
you dont need a recovery to flash kernel (boot.img). i extracted the boot.img from his rom and booted fastboot than executed the following command: fastboot flash boot boot.img ... when restarting phone it just boots to fastboot. i had to revert and reflash the stock boot.img then my m8 booted back up
grimlocksmash said:
You have a working recovery already?
Click to expand...
Click to collapse
Until I get s off, I can't test or troubleshoot anything.
Sent from my HTC6525LVW using xda app-developers app
digitalhigh said:
Until I get s off, I can't test or troubleshoot anything.
Sent from my HTC6525LVW using xda app-developers app
Click to expand...
Click to collapse
Its your lucky day, S-Off is here along with a CWM recovery.
chriskader said:
Its your lucky day, S-Off is here along with a CWM recovery.
Click to expand...
Click to collapse
LOL...I saw that minutes after posting. Of course it would drop while I was napping. I'm s-off and in recovery now...sideloading and testing now.
Aha...see the updater-script has some permissions errors. I wonder if it boots...
digitalhigh said:
LOL...I saw that minutes after posting. Of course it would drop while I was napping. I'm s-off and in recovery now...sideloading and testing now.
Aha...see the updater-script has some permissions errors. I wonder if it boots...
Click to expand...
Click to collapse
Let me know if you need help or are interested in a kang project
Sent from my HTC6525LVW using XDA Premium 4 mobile app
chriskader said:
Let me know if you need help or are interested in a kang project
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Add this to the OP if you would like Powered by Android splash screen
digitalhigh said:
LOL...I saw that minutes after posting. Of course it would drop while I was napping. I'm s-off and in recovery now...sideloading and testing now.
Aha...see the updater-script has some permissions errors. I wonder if it boots...
Click to expand...
Click to collapse
i wonder if i package the stock boot.img to your rom if it will boot lol. i tried taking just your boot.img and flashing it to stock and it would not boot
kwkw480 said:
i wonder if i package the stock boot.img to your rom if it will boot lol. i tried taking just your boot.img and flashing it to stock and it would not boot
Click to expand...
Click to collapse
Yes, I see the same thing. It's either getting broken being repackaged with kitchen, or it doesn't like removing the secure bits from default.prop. I'm working on it, but I'm also playing with like a dozen different things at the same time. It's like christmas!
digitalhigh said:
Yes, I see the same thing. It's either getting broken being repackaged with kitchen, or it doesn't like removing the secure bits from default.prop. I'm working on it, but I'm also playing with like a dozen different things at the same time. It's like christmas!
Click to expand...
Click to collapse
heard that! have a kernel going also... i got status 7 error . i have to work in the am but i dont wanna miss anything
I want to work on porting GPE.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
I would love to convert my vzw m8 to a super Cid GPE .. That's my goal. Can that be done using the resources for gsm after rooting and s-off? Or is there still a piece missing preventing that?
Sent from my HTC6525LVW using Tapatalk