Anyone flashed jmz kernel with new firmware? - HTC Desire 610

So I was using an old fw with jmz kernel and as a device, it worked great with minimal bugs but found out today I wasn't receiving a lot of phone calls and texts. After rebooting I got all my missed calls & messages!
So obviously I have to make a change. I just ran the newest ruu. I'm wondering if anyone is actually using JMZ still and if so what type of behavior are you experiencing?
I know I can buy s-off but I still can't justify $25. Plus sometime in the next six months I'm getting a new phone and I think if I go with HTC I'll need to pay another 25 for s-off (think that's how it works?)
Thanks.

KLit75 said:
So I was using an old fw with jmz kernel and as a device, it worked great with minimal bugs but found out today I wasn't receiving a lot of phone calls and texts. After rebooting I got all my missed calls & messages!
So obviously I have to make a change. I just ran the newest ruu. I'm wondering if anyone is actually using JMZ still and if so what type of behavior are you experiencing?
I know I can buy s-off but I still can't justify $25. Plus sometime in the next six months I'm getting a new phone and I think if I go with HTC I'll need to pay another 25 for s-off (think that's how it works?)
Thanks.
Click to expand...
Click to collapse
I've been using JMZ kernel for 8 months straight, combined with a stock asia rom that has all htc and google bloat removed and then deodexed. I have not had any problems at all, but for the last six months I am using a JMZ kernel that I compiled myself from his sources. I don't think that has made any difference but there are 3 versions of his source on his github so the 1 I compiled may be a little different. I also set up a phone fore a freind who wanted to keep running stock kernel but with a modified stock asia rom. We just extracted the JMZ kernel zip then boot to twrp(to keep his stock recovery in place we did this buy putting the phone in fastboot mode, then with TWRP****.img file in your fastboot directory run
fastboot boot TWRP****.img
which reboots the phone to TWRP without flashing it). Then from TWRP do a full backup for safety and to be able to return to full stock easily. While still in TWRP connect to the phone via ADB and run
adb push \path_to_extracted_jmz_kernel\system\lib\modules /system/lib
(this just adds modules from jmz kernel to you system so it can load propery)
I don't think this step is nesesary but next from in TWRP we did Advanced Fix Permisions to ensure the modules we just added have the corect permisions set.
Now you can boot to JMZ kernel (without flashing it and keeping stock kernel and recovery on your phone)when you want to make changes to your system that will stick after reboot (like sdcard fix,wifi tethering fix,supersu,xposed) by putting your phone in fastboot mode then with the boot.img extracted from JMZ kernel in your fastboot directory run
fastboot boot boot.img
this will reboot running JMZ kernel and when you make changes to the system then reboot the changes will stick but you reboot back to stock kernel.
Hope this helps someone
MiniBlu

MiniBlu said:
I've been using JMZ kernel for 8 months straight, combined with a stock asia rom that has all htc and google bloat removed and then deodexed. I have not had any problems at all, but for the last six months I am using a JMZ kernel that I compiled myself from his sources. I don't think that has made any difference but there are 3 versions of his source on his github so the 1 I compiled may be a little different. I also set up a phone fore a freind who wanted to keep running stock kernel but with a modified stock asia rom. We just extracted the JMZ kernel zip then boot to twrp(to keep his stock recovery in place we did this buy putting the phone in fastboot mode, then with TWRP****.img file in your fastboot directory run
fastboot boot TWRP****.img
which reboots the phone to TWRP without flashing it). Then from TWRP do a full backup for safety and to be able to return to full stock easily. While still in TWRP connect to the phone via ADB and run
adb push \path_to_extracted_jmz_kernel\system\lib\modules /system/lib
(this just adds modules from jmz kernel to you system so it can load propery)
I don't think this step is nesesary but next from in TWRP we did Advanced Fix Permisions to ensure the modules we just added have the corect permisions set.
Now you can boot to JMZ kernel (without flashing it and keeping stock kernel and recovery on your phone)when you want to make changes to your system that will stick after reboot (like sdcard fix,wifi tethering fix,supersu,xposed) by putting your phone in fastboot mode then with the boot.img extracted from JMZ kernel in your fastboot directory run
fastboot boot boot.img
this will reboot running JMZ kernel and when you make changes to the system then reboot the changes will stick but you reboot back to stock kernel.
Hope this helps someone
MiniBlu
Click to expand...
Click to collapse
Wow! That's really clever. So essentially you're just borrowing the kernel as a tool to make the system s-off, make changes, then go back to stock. I've gotta do this when I have a chance. Hopefully you'll be around if I have questions. Thanks.
EDIT-Thing is though. with the exception of tethering I can get everything else working without using the kernel. KK sdcard fix doesn't stick but I found one to flash in recovery and it's working for me. Same thing with busy box and flashing in recovery is the only way I know of to get SU working.
Is there anything else useful I might be missing?
Turns out the bugs (missed phone calls) were related to the kernel. I thought it might be the audio jack but after lots of testing i narrowed it down.

KLit75 said:
Wow! That's really clever. So essentially you're just borrowing the kernel as a tool to make the system s-off, make changes, then go back to stock. I've gotta do this when I have a chance. Hopefully you'll be around if I have questions. Thanks.
EDIT-Thing is though. with the exception of tethering I can get everything else working without using the kernel. KK sdcard fix doesn't stick but I found one to flash in recovery and it's working for me. Same thing with busy box and flashing in recovery is the only way I know of to get SU working.
Is there anything else useful I might be missing?
Turns out the bugs (missed phone calls) were related to the kernel. I thought it might be the audio jack but after lots of testing i narrowed it down.
Click to expand...
Click to collapse
su can be installed by the above method but apart from that, only really to install exposed framework and modules.
The tethering fix can also be done from twrp, you just boot to twrp, press MOUNT and check box System, connect to it via adb ,"adb pull" the file you need to edit,edit it with notepad++,"adb push" the file back to the phone,run Advanced Fix Permisions in twrp, then Reboot and edited file will stick.
The method I descibed in last post is best suited to people in other regions who can't get RUU as it leaves original kernel and recovery in place so all you need to do is restore the original twrp backup of system partition and lock bootloader and your all good to get ota updates. And no red text at boot.
MiniBlu

MiniBlu said:
su can be installed by the above method but apart from that, only really to install exposed framework and modules.
The tethering fix can also be done from twrp, you just boot to twrp, press MOUNT and check box System, connect to it via adb ,"adb pull" the file you need to edit,edit it with notepad++,"adb push" the file back to the phone,run Advanced Fix Permisions in twrp, then Reboot and edited file will stick.
The method I descibed in last post is best suited to people in other regions who can't get RUU as it leaves original kernel and recovery in place so all you need to do is restore the original twrp backup of system partition and lock bootloader and your all good to get ota updates. And no red text at boot.
MiniBlu
Click to expand...
Click to collapse
Xposed now has the option to flash in recovery (after v2.5 something, I think) Never had problems with that.
However, I didn't even think about mounting system in recovery then editing the text. That's smart. I don't use tethering but wanna try this.
So since I can run the ruu which means no red text, I can write to ext sd, and whenever I want to make changes I can use mount in twrp--is there any reason to buy s-off?
Edit-- would I be able to edit the text and reboot to recovery THEN mount system and fix permissions?
I'm just wondering because I'm not sure exactly when changes made to the system get changed back...
Does it happen when we boot into the ROM, meaning if I boot recovery the changes haven't been reversed?
Or do they go away as soon as I boot to recovery, meaning there's nothing new to save?
***I know its not critical. Using my Mac to make the changes is easy enough but for future modifications it does save time.
Thanks for the info

KLit75 said:
Xposed now has the option to flash in recovery (after v2.5 something, I think) Never had problems with that.
However, I didn't even think about mounting system in recovery then editing the text. That's smart. I don't use tethering but wanna try this.
So since I can run the ruu which means no red text, I can write to ext sd, and whenever I want to make changes I can use mount in twrp--is there any reason to buy s-off?
Edit-- would I be able to edit the text and reboot to recovery THEN mount system and fix permissions?
I'm just wondering because I'm not sure exactly when changes made to the system get changed back...
Does it happen when we boot into the ROM, meaning if I boot recovery the changes haven't been reversed?
Or do they go away as soon as I boot to recovery, meaning there's nothing new to save?
***I know its not critical. Using my Mac to make the changes is easy enough but for future modifications it does save time.
Thanks for the info
Click to expand...
Click to collapse
The changes made to /system aren't wriiten to disk at all so they will be gone when you reboot to recovery. But you can edit the file and save it to /sdcard, then in twrp use Advanced File Manager to copy the file from /sdcard to /system.

MiniBlu said:
The changes made to /system aren't wriiten to disk at all so they will be gone when you reboot to recovery. But you can edit the file and save it to /sdcard, then in twrp use Advanced File Manager to copy the file from /sdcard to /system.
Click to expand...
Click to collapse
Didn't even think of that. Thanks again!
...But what I'd need to do is basically replace the file completely, right? Never done anything like that in recovery. Everywhere else it'll say something like "This file already exists, would you like to overwrite it?" Doubt TWRP will give that heads up...have you ever made modifications in this manner?

KLit75 said:
Didn't even think of that. Thanks again!
...But what I'd need to do is basically replace the file completely, right? Never done anything like that in recovery. Everywhere else it'll say something like "This file already exists, would you like to overwrite it?" Doubt TWRP will give that heads up...have you ever made modifications in this manner?
Click to expand...
Click to collapse
Yes. Its the same as when you do it with adb. It just overwrites the file. You can always rename the original with a .orig extension first so you have original file backed up.

MiniBlu said:
Yes. Its the same as when you do it with adb. It just overwrites the file. You can always rename the original with a .orig extension first so you have original file backed up.
Click to expand...
Click to collapse
I tried it and it worked! This is really cool. Makes me wonder what else could modified. Thanks again!

I seem to have ran into a problem. I am rooted, and everything. but, once I modified this file and fixed permission I am now spammed with "unauthorized device"
Help?

Related

[Q] Any fixed e3d camera rom?

Ok, I've already searched the forums, both in the Evo3D section and outside, I've also have within the last week tried many different sense roms, all of which had the exact same problem: my camera does NOT work.
The closest thing to working was mike1986's Android Revolution HD (so far). The camera app boots into the window that ask to choose between Done or run the Demo Video. The Demo Video sends ye off to the internet browser. Hitting Done goes straight to my problem.
The application opens into a black screen. Sometimes the backlight is on (noticed this is a 'feature' of the newer roms that has came out/updated within the last month). That's it. After hitting home to exit the application, I have noticed I get either dimmer horizontal strips of the screen or the screen has a ghost of the lighter portions of the screen image that slowly moves to the left. After a few seconds of this strangeness, the screen reverts back to normal. A few times I got the impression that the screen's dual layers having synchronization problems.
I'm about ready to give up and go back to the stock rom, maybe I'll even try the 'cleaned' versions before trying the rooted shooter stockers. If all else fails, I'll even try to use the full OEM installer and return the phone back to stock, if this is the only option left to get a working camera. I'd prefer to use a custom rom that allows undervolting/overclocking and has the fat trimmed off, but if I have to, I'll go back to stock rooted. ...now that I think of it, I started to have problems with the camera right after I applied the HTCDev Root method. And, yes I DID follow the instructions to the letter.
This is quite frustrating as I've have as yet to find a rom that has a working camera! I've already tried the following roms:
Shooter-Rewind-3D-RLS2.1+RLS3
WTSB_Evo3d_1.91
CleanROM_2.7
CleanROM_DE_1.2
Chogardjr3D-2.3.4-Stock
Chogardjr3D-Blue-v1.3
STEAL25_inbREDedROM_2.1clock
viperROM_RC1.3
viperROM_RC2_Rebuild_Test28
Android_Revolution_HD-Evo3D_CDMA_1.1.1 (current)
I haven't tried but already downloaded:
Gerbil-6-shooter_v.2.2.4
freEVO+3D+2.1
WTSB Hydro e3d 2.3 (want to try this one, but keep having problems downloading, the server keeps on downloading a 35kb index.html instead of the rom itself)
If the above roms fails, then I going to try reloading the rooted stock rom
shooter_2.08.651.2_cleaned_v0.4.2
Else one of these two...
Shooter_2.08.651.2_deodexed_rooted
Shooter_2.08.651.2_odexed_rooted
If all these fails, sigh, I gonna start over again with the full oem install...
PG85IMG_2.08.651.2.zip
And see if the camera still broken. If so, then gonna apply all OTA updates FIRST before applying the HTCDev root method again. This is the only thing I did not do before. If this doesn't work, I dunno what else to do then.
Any suggestions, rom-wise or camera-wise? I've been reading around and found a thread in the Amaze section that suggested that the camera problem might be kernel-level. Think this may also apply to the e3d?
I've been doing sleepless nights for the past 5 days already trying roms after roms and apk after apks. I'm about reaching the end of my thread (and patience) and figured it's time to ask the pros here on xda.
Thanks in advance...
-Lance (Lanaka)
Reserved for Fixed Post.
I forgot to upload my hardware/software specs. I'm out of time as I have to go to work, so I'll edit it onto this post during a slow period at work.
K here's my hardware/software specs:
---Hardware:
------Hardware Version: .. 0002
------Processor: ............ 1.2 GHz Qualcomm MSM8660 Dual-Core
------Memory: ............... 1GB
------Display: ................ 4.3 inch QHD resolution
------Main Camera: ........ 5Mpx*2
------Front Camera: ....... 1.3Mpx
---Software:
------Android Version: ..... 2.3.4
------HTC Sense version: 3.0
------Software number: .. Android Revolution HD 1.1.1 by mike1986
------Kernel version: ...... 2.6.35.14RCMIX-ACS-EVO3D-CR-V9-g98e7362-dirty
------------------------- [email protected] #6
------------------------- SMP PREEMPT Mon Oct 24 13:13:49 CDT 2011
------Baseband version: . 0.97.10.0808
------Build number: ........ 2.08.651.2 CL130920 release-keys
------Browser version: .... WebKit/533.1
------PRI Version: .......... 1.24_003
------PRL Version: .......... 10602
Bootloader:
------SHOOTER XC SHIP S-0N RL
------HBOOT-1.50.0000
------eMMC-boot
------Aug 7 2011,10:21:40
---Recovery:
------Team Win Recovery Project (twrp) v1.0.3
------Based on Android System Recovery <2e>
Any other information you need, lemme know and where/how get it.
Mahalo Much
-Lan
Infected eternity ROM works...
Sent from my 3vo
http://infectedrom.com/showthread.php/561-ROM-Eternity™-2.3.4?p=10369
Sent from my 3vo
nearly ALL the ROMs you posted, nay, all of them, work - if they didn't there would be a hellstorm in those threads. My guess is it has to do with how you're flashing the ROM. Since you have hboot 1.5, customized kernels (which contain camera stuffs) do not fully apply in a normal flash. You need to first fastboot usb INTO recovery and THEN flash the ROM. That should work. Also, update TWRP to 1.1.1. Of course you'll need to do a wipe as well. Hope this works for you.
You might also want to try one of the many superwipes.
User error. Camera works on roms. Maybe ur phone is broken
Sent from my PG86100 using XDA App
I'd go with what il Duce said. You have to flash the kernel seperately. If you do decide to go back to stock you can always add su and also remove what you don't want.
Sent from my PG86100 using XDA App
fsu311 said:
Infected eternity ROM works...
Click to expand...
Click to collapse
Ok, I'll give it a try next after the ones I've already downloaded. I'm a methodical type of guy (don't like leaving thing left undone).
il Duce said:
nearly ALL the ROMs you posted, nay, all of them, work - if they didn't there would be a hellstorm in those threads. My guess is it has to do with how you're flashing the ROM. Since you have hboot 1.5, customized kernels (which contain camera stuffs) do not fully apply in a normal flash. You need to first fastboot usb INTO recovery and THEN flash the ROM. That should work. Also, update TWRP to 1.1.1. Of course you'll need to do a wipe as well. Hope this works for you.
Click to expand...
Click to collapse
That's what I'm figuring. I start reading the original set of posts, then randomly check out a few posts in the middle, and then read the last 10%. The roms i've picked mostly had either minor issues caused by misflashing or other user errors. A few actually said had an issue or two but nothing that'd stop me from giving the rom a try.
Yup, that's the MO I've been using as instructed in the following thread:
http://forum.xda-developers.com/showthread.php?t=1239821
I'll go thru the step-by-step process I used and you can nitpick where I went wrong,
I've placed a copy of adb.exe, AdbWinApi.dll, fastboot.exe and TWRP's recovery.img into folder c:\adb\
A little tip here, as I play with windoze XP a lot, a trick I used to eliminate the need to cd so much with cmd.exe. I did this after the 3rd ROM!
I place a shortcut link to cmd.exe into this same folder with the above files and exes. Next I open the Properties window for this shortcut, I made the following changes:
Start In: c:\adb
Comment: Starts cmd.exe in adb folder.
What happen is that cmd will open its window with the c-prompt already IN the same directory as my android files. Also, when i mouse-over the shortcut icon, it will popup a message reminding me that this link starts cmd.exe in adb folder.
Then I do the following:
I connect the phone to the laptop using the usb cable, set the phone to disk drive mode. Once Windows recognizes the volume and mounts it, I type the following:
c:\adb>adb reboot bootloader
After the e3d reboots into hboot, I then type the following:
c:\adb>fastboot boot recovery.img
downloading 'boot.img'... OKAY [ 1.250s]
booting... OKAY [ 0.000s]
finished. total time: 1.250s
Once TWRP loads, I then switch to the phone (WITHOUT disconnecting the phone from the laptop). Here on, I use the keys on the phone to navigate to the necessary functions. The proceedure I used mirrors what Steel25 suggested in the following thread:
http://forum.xda-developers.com/showthread.php?t=1269610
I initially thought it was an overkill, but figured probably wouldnt hurt to be safe than sorry.
If the installed rom is something I liked, I nand it first...
I then enter the Wipe Menu proceed to hitting each of the following:
Wipe Cache
Wipe Dalvik Cache
Wipe Everything (Data Factory Reset)
Wipe Battery Stats
Then I go to Advanced/Format Menu and hit each of the following:
Format SYSTEM (/system)
Format DATA (/data)
Format CACHE (/cache)
Format SD-EXT (/sd-ext)
Then I go back to top menu and enter Install Zip Menu, and first I hit:
Wipe Cache and Dalvik Cache
Then I enable:
Reboot After Successful Flash
THEN I:
Choose Zip To Flash
(Navigate to where the rom or app zip is located and select it.) Here I take a break and let TWRP does it thingy and check back on the phone in 5 minutes or so.
After recovery reboots the phone back into system, I let the phone sit on the lockscreen for 10 minutes to let the rom complete it's init process. Then I skip thru the entire initial setup prompts (altho I enter NO for Tell HTC). I reboot phone back into system, let it sit for another 5 minutes on the lockscreen before I hit the Android Market app to trigger the process of linking the phone to my google account. I then let my account sync. Once my new email icon pops up on the notification bar, I check out the camera. By the time I've hit the 3rd rom, I've had read about the camera problem possibly being a kernel level issue, I've since then added this step....
Menu/Settings/About Phone/Software information/More
Here I took note on whether the Kernel version info has changed as well. (And for the most part, yes, the kernel information DOES change with each rom).
K, now ye can start thrashing me...
-Lan
Drewmungus said:
You might also want to try one of the many superwipes.
Click to expand...
Click to collapse
I'll try that, altho I've never used it before. Even when I had my e4g, I never heard of this one until I started my current research on the e3d. Any particular one you'd (or anyone else'd) recommend?
Sigh, lotta work rooting and flashing the 1.50 e3d, compared to the good ol' e4g! >8p HTC!
Mahalo Much!
-Lan
cajones42 said:
Maybe ur phone is broken
Click to expand...
Click to collapse
Gods! I certainly HOPE NOT! It'd be a real b!atch if this proves to be the case.
Seriously, tho. I'm thinking it'd probably not be the case as I had the phone and was playing with it stock and unrooted for nearly a week and during the whole time, the phone's camera worked with nary a problem. That's why as a check value, I'm going to restore the phone back to stock unrooted state AFTER I try the last 4 roms I still have en-queued. This doesn't include the cleaned/rooted stocker, the full/rooted stocker nor the full OEM stocker.
-Lan
unCoRrUpTeD said:
I'd go with what il Duce said. You have to flash the kernel seperately. If you do decide to go back to stock you can always add su and also remove what you don't want.
Click to expand...
Click to collapse
Ok, I'll try that next. Altho, I gonna have to read up on how to prepare the kernel for flashing separately. Am I correct in guessing that I probably could get away with making a copy of the zip file and deleting everything in it except for boot.img, then adb boot into recovery and set the flag for check sign off before flashing the custom zip I just made? If that's not correct, mind pointing me to the apropos thread? (...or tell me what I need to do for separate flashing?)
If all else doesn't work, that's what I intend with the stocker roms. SU, TI, RE. Then time for me to research on where what and how to root out all the bloat meself. I'll worry about that later cuz I no need do that IF i can get a pre-made rom and kernel to take root in me e3d!
Mahalo Much!
-Lan
You DON'T have to flash the kernel seperatly using the boot.img method with HBoot 1.50. As long as you access recovery from fastboot you can flash everything normally & the kernel will stick. Just sayin'
SketchyStunts said:
You DON'T have to flash the kernel seperatly using the boot.img method with HBoot 1.50. As long as you access recovery from fastboot you can flash everything normally & the kernel will stick. Just sayin'
Click to expand...
Click to collapse
except he's already doing that and running into problems...
@OP - man you are wordy lol. Just a simple FYI, when you're phone is running and you hook up to usb with the intention of running adb, DO NOT turn on disk drive, leave it as charge only. Also, the way to flash the kernel as a stand alone is pull the "boot.img" from the ROM zip, put in your path, and then "fastboot flash boot boot.img". Also, there's an app made by dev "joeykrim" called "flash image gui" that allows you to flash kernels (boot.img) from your OS and is known to work with hboot 1.5.
il Duce said:
except he's already doing that and running into problems...
@OP - man you are wordy lol. Just a simple FYI, when you're phone is running and you hook up to usb with the intention of running adb, DO NOT turn on disk drive, leave it as charge only. Also, the way to flash the kernel as a stand alone is pull the "boot.img" from the ROM zip, put in your path, and then "fastboot flash boot boot.img". Also, there's an app made by dev "joeykrim" called "flash image gui" that allows you to flash kernels (boot.img) from your OS and is known to work with hboot 1.5.
Click to expand...
Click to collapse
Ah, didn't know that, mebbe that's why I'm having problems. I'll try reinstall one of the earlier ROM and see if there's any difference. If that doesn't fly, I'll try the kernel separately. I went with hard drive mode cuz I got actual confirmation the device was loaded. Charge only, didn't get any indication that the pc seen the e3d, sigh, noticed the sense and adb interface is rather ...crude.
Heh, wordy, that's what you get when you have an English major for a mother and an English/Japanese Translation Specialist (aka Cultural Attache in the US Army) for a grandfather...
I'll give joeykrim's flash_gui a try too. Just downloaded it. Cross fingers for luck. (roll eyes at 1.50)
Thanks dude, if I could, I'd hit yer thanks button again for good measure.
EDIT: clicked the button again...
Update: Back to work on problem...
Been a while guys. Unfortunately, work becons (or more accurately, intruded). Had to deal with a bunch of sht from my job. Things gone to the dumps there. Well, enuff of that.
In meantime, with my phone being activated and in use, I tried to tether (teeether, hehe) my e4g to my e3d and noticed I'm also having wifi issues. What rang a bell is when I noticed my wifi tether issues disappeared after I turned off 3G. It's like, heeeeey, didn't I read something like this in xda??? After doing some researching (on xda, of course ) I've learned that this is also a kernel issue, most often because the new kernel was not properly flashed in conjunction to having the correct matched kernel modules (wifi, CAMERA, 3g/4g, etc.) installed as well. On reading these, I went 'hmmm...' Looks like all of these issues others and I that have been experiencing are all kernel/module misflashes (no thanks to hboot 1.50). Where I think I hit pay dirt is when I found a xda thread that actually explains in depth Flash Image GUI, which was also mentioned earlier in THIS thread (thanks, il Duce).
So, I have downloaded the apk, installed it. Downloaded a new ROM (Olympus Trinity XE Version IV) STRAIGHT to phone...
Oh, just remembered. I've noticed another possible cause of problems. I've originally downloaded the various files from xda and then either push it to phone or more often just enable hardrive mode and drag/dropped it into the phones sdcard directly. Normally, I check the md5 hash on download, but yesterday, I ALSO checked the md5 hash again after moving it to the phone. Meaning, I downloaded ROM to pc, then checked md5 hash, all good. Copied ROM to phone and then checked md5 hash again. NOT good. Somehow, it changed during the copy process. What prompted me to check was I also downloaded Flash Image GUI to pc and copied it to phone and then had phone try install it. It failed to "parse" file correctly, which tells me that the file may have been corrupted. I downloaded Flash Image directly to phone and tried again, and success! Suspicious now, I checked the md5 hash of all three copies of the apk. The laptop downloaded and the phone downloaded copies matched the source's md5, while the COPIED version did NOT match! Whaaa Daaaa FFF(bleep!)!!! I then checked the two copies of the ROM (pc downloaded and phone copied) and they DON'T match!
Sigh. I'm in a area that has poor 3G connection, while ironically, my laptop's 4G was good.
So, I bit the bullet and endured the nearly hour long download of the ROM directly to phone and double checked the hash (which matched the pc downloaded copy, the source didn't provide a hash). THEN I used the Flash Image GUI app to pull the kernel and modules and pop it into phone. Immediately rebooted phone into recovery. Well, tried. Wished Flash Image GUI gave the option to reboot directly into recovery or bootloader, like those 4-/5-/6-1 Reboot options offered in the various ROMs. Because it just simple did a reboot back into System.
I didn't want to take chance with problems with mismatched ROM/kernels (I was on Android Revolution 1.1.1 at the time), so I quickly turned to adb on my laptop and had it reboot phone into recovery.
Once in recovery, I immediately started doing my usual ROM change process. Wiped using every wipe option (except for sdcard) in TWRP (oh btw, I also updated it to 1.1.1 earlier) in both the standard wipe and advanced wipe menus. Once I did so, I then thought, hey where did Flash Image GUI dump the kernels into? Couldn't remember whether it was DATA or SYSTEM. But decided that with Flash Image GUI it's ain't no hassle to reflash the kernel again after the ROM is installed. Besides, read somewhere that some issues was resolved after reflashing the kernel again after the ROM, so wouldn't hurt to try anyway.
Will let ye know how it goes, TWRP is installing Trinity XE as I type this. Gonna continue the SOP by letting it sit for 7-10 minutes. Skip thru init setup. Reboot. Let sit for another 7-10 minutes. Relink my google account. Let first Sync finish. (Basically let it sit again for another 7 minutes). Reboot. Hit Market and download Flash Image GUI, and pay for it, it's well worth IT!!! Flash the ROM's kernel/modules again. Reboot. And hopefully it should be a-ok!
(cross fingers ...on both hands)!
-Lance
PS: Assuming it's fixed, I'm gonna edit the second post and reflag this thread as resolved. Will put what I did to get it fixed, including all necessary links and credits as expected. I know it's premature, but THANKS, I wouldn't have gotten even this far without you guys (and gals) on XDA!
PPS: Also chris.goodman's AnthraX Kernel thread was also quite informative. Mebbe I'll try a ROM that features AnthraX. Somehow, the thought of being over-clocked to ~1.52G sounds appealing!

[DEVs][Simple] Auto Kernel Install for S-ON Unlocked Devices with MainVer Fix

I have discontinued support for this since S-OFF is available.
New Update! Easier Than Ever!
How To Install You New Kernel!
With drellisdee's Main Version Fix
Instructions
DEVS: New versions are added. Two zips are attached. One is for flashing zImages, one is for flashing boot images.
Just put the contents up the updater script into your rom along with the kernel folder.
For the zImage one, put a zImage named "zImage" in the kernel folder. For a boot image, put a boot.img named "boot.img" in the kernel folder. Each zip has the appropriate scripting for that type of file. For a rom, it is likely you want the boot image version.
This fixes the main version so that will no longer be an issue with rom installations thanks to drellisdee
OLD NOTES: (Ignore )
-1)Flash the rom of your choice and the boot image distributed with it via a PH98IMG.zip. If it doesn't come with one, just move on.
0)Flash the kernel you want's zip file in recovery. Also make sure there are no existing PH98IMG.zip files on your sdcard
1)Download AutoKernelInstaller.zip attached to my post.
2)Extract the zip
3)If you want ziggy's kernel, move to step 4. If you want another kernel, find the zImage file in the kernel's zip folder and copy it to the kernel folder from my zip file. It should overwrite the zImage file in there now.
4)Run buildFlashable.bat
5)Flash the flashmeinrecovery.zip in recovery
6)My scripts in flashme.zip will perform all of the work to create a PH98IMG.zip and then will automatically reboot to HBOOT
7)Press the power button in HBOOT to select bootloader
8)Select Yes for installing the new boot.img
9)Done Your kernel is installed!
To users, you can now use this to flash your own kernels without needing someone else to make it a boot.img specific to a certain rom. You will still need to flash the kernel's zip file in recovery to get the extra stuff the kernel comes with, such as a wifi module. These steps are in addition to that process.
To devs, feel free to add this script to your kernel zip files so S-ON devices can use it without boot.img creation knowledge and so that you don't have to distribute hardcoded boot.img files.
Why is all this necessary? You most likely didn't have to jump through these hoops to install kernels on your other devices...
As most of you have figured out, installing kernels is a multi-step process on the Rezound. First, files for the system partition need to be flashed in recovery. Then a boot.img needs to be flashed that contains the kernel and the ramdisk.
Unfortunately, since the ramdisk changes from rom to rom, kernels cannot be distributed as boot.img files. Therefore, they are impossible to flash without conversion. If you have installed ziggy's kernel, you have probably used my premade flashables. Those are fine for now, until ramdisks begin to change from rom to rom. This flashable zip will insert a kernel into a rom's boot image and then package it into a PH98IMG.zip that is flashable from the bootloader (HBOOT) without fastboot,adb, or PC knowledge required. This saves a ton of work for the user and allows kernels to be compatible with ANY rom.
Click to expand...
Click to collapse
Returning to stock
http://forum.xda-developers.com/showpost.php?p=20990402&postcount=2
Good lookin out on all of this Con...you along with the other developers have been awesome in getting dev for the Rezound off the ground. Thank you!
Marcismo55 said:
Good lookin out on all of this Con...you along with the other developers have been awesome in getting dev for the Rezound off the ground. Thank you!
Click to expand...
Click to collapse
I am no dev. I have no idea how to make a kernel/rom (for the most part). I just know what with and why users struggle with things and I try to simplify and automate as much as possible. It is better to leave the "real" work for the devs so they don't have to waste time doing things that I can help with.
Just out of curiosity, does flashing that first file wipe the internal memory? Not the one with ROM and stuff on it, but the one where your TiBackups are stored and such, because after I flashed the kernel, all my Titanium backups were gone and the internal memory was wiped. I didn't lose anything because I made copies to my desktop computer, but if I hadn't, I would have lost all that stuff. Maybe I did something wrong, but I don't think so, because I followed instructions, and the kernel is installed and working fine.
Evo4gLI said:
Just out of curiosity, does flashing that first file wipe the internal memory? Not the one with ROM and stuff on it, but the one where your TiBackups are stored and such, because after I flashed the kernel, all my Titanium backups were gone and the internal memory was wiped. I didn't lose anything because I made copies to my desktop computer, but if I hadn't, I would have lost all that stuff. Maybe I did something wrong, but I don't think so, because I followed instructions, and the kernel is installed and working fine.
Click to expand...
Click to collapse
This flashable wipes nothing. It just creates a new flashable boot image from what is already on your device.
con247 said:
This flashable wipes nothing. It just creates a new flashable boot image from what is already on your device.
Click to expand...
Click to collapse
Any insight into what may have happened then? Because it was all there before I flashed the kernel, and then it was gone afterwards.
Did you do a data wipe or something? Did you install a new rom?
I actually had the same thing happen to me. Almost all my apps were missing one I installed the kernel. It was odd
sent from my newly unlocked Rezound
pwned3 said:
I actually had the same thing happen to me. Almost all my apps were missing one I installed the kernel. It was odd
sent from my newly unlocked Rezound
Click to expand...
Click to collapse
Fixed the issue. It was in the PH98IMG.zip it just happened to me also. Sorry guys! Files in 1st post are fixed!
complete noob!!!!!
CON247, you are a huge help with all this and I appreciate your work. Your step by step directions are helpful but sometimes still confusing for noobs. Are there step by step instructions for this that explains what each steps does and why it need to be done? I want to flash a kernel but I'm not sure how to perform all the steps listed here but wish to learn.
Even better knowing so much of this is being done by a fellow Wolverine fan.
Thanks Con. I knew it couldn't have been something I did...I've done my fair share of flashing and I hadn't done anything different, I just wanted to make sure it didn't happen to anyone without a copy of their files.
Sent from my HTC Rezound via Tapatalk
Thanks for the hard work on this, one question..what does boot into Hboot mean exaclty? this is not recovery right? is this remove the batter and hold down volume down and power boot thing?
thanks
---------- Post added at 04:17 PM ---------- Previous post was at 04:03 PM ----------
nvm got it
Yessir. It will ask you if you want to update then you hit yes
Sent from my ADR6425LVW using XDA App
Just had my first issue with mismatching ROM and boot.img.... all the current roms are based on the original kernal, so if a user has flashed Ziggy's kernal then flashed over any of the existing rom's, functionality becomes lost (such as Wifi in my case). The fix is easy just flash Ziggy's kernal and not touching the boot.img in hboot, but this did cause some confusion.
Anyway, this is a great idea, and I believed it should be stickied (and the title changed from [idea] to [boot.img Standard] !!!!
Found this from your reply on the other post and followed these instructions. I happened to get my issue fixed and I am back up and running! Thanks!
-mxair2001
Just noticed that the Amon Ra recovery has an option under the Developer menu option to build a boot image from a zimage. Anyone tried that, and does it also fix the ramdisk files too?
Marine6680 said:
Just noticed that the Amon Ra recovery has an option under the Developer menu option to build a boot image from a zimage. Anyone tried that, and does it also fix the ramdisk files too?
Click to expand...
Click to collapse
That would be awesome, but we can't flash the boot image from recovery. I have a newer version of this tool coming soon I think (assuming it works lol)
New version up. It is really easy now. It is only a few clicks.
Thank you for making this a little easier. I used it flawlessly to try ziggy's kernel again
sent from my newly unlocked Rezound
pwned3 said:
Thank you for making this a little easier. I used it flawlessly to try ziggy's kernel again
sent from my newly unlocked Rezound
Click to expand...
Click to collapse
Are the instructions clear enough? I wish this would get stickied. People who keep flashing a boot.img from the stock roms on a custom rom will eventually boot loop.

[Q] CleanROM (GB) 1.5.5 help please

Two questions:
1.
I followed Scott's directions to the "t" and I have two questions.
I'm using a Mac so I cannot flash the boot.img via his kick ass CleanFLASH tool.
So I manually rebooted into fastboot (after tripple checking that I had his boot.img in my SDK), then I ran the fastboot command via terminal and it completed successfully.
Wiped data/factory restored. Went back and manually wiped again....
Rebooted into recovery and flashed the CleanROM .zip file, then flashed his social and verizon add on's "before" my first boot.
Scott said to make sure you have the correct boot.img installed you could look on you SD for system/data and you should see a zipalign.log file. For the life of me I do not have that file.... When I could not find the file I reflashed all the files again and still did not see the zipalign.log file.
Is there a way to tell if I'm on the correct boot.img file by looking at the Kernel?
I'm coming from a rooted / stock install. Just wanted to give his ROM a try.
The Kernel I see in my settings/about phone is 2.6.35.13-g20c5d1d
I really just want to make sure I'm running the ROM kernel and not the stock since his has battery/performance tweaks.
2. Does anybody know if the built in stock screenshot (Power/Home) works with this ROM? Tried but it did not work.
Thanks a ton in advance!
_pank said:
Two questions:
1.
I followed Scott's directions to the "t" and I have two questions.
I'm using a Mac so I cannot flash the boot.img via his kick ass CleanFLASH tool.
So I manually rebooted into fastboot (after tripple checking that I had his boot.img in my SDK), then I ran the fastboot command via terminal and it completed successfully.
Wiped data/factory restored. Went back and manually wiped again....
Rebooted into recovery and flashed the CleanROM .zip file, then flashed his social and verizon add on's "before" my first boot.
Scott said to make sure you have the correct boot.img installed you could look on you SD for system/data and you should see a zipalign.log file. For the life of me I do not have that file.... When I could not find the file I reflashed all the files again and still did not see the zipalign.log file.
Is there a way to tell if I'm on the correct boot.img file by looking at the Kernel?
I'm coming from a rooted / stock install. Just wanted to give his ROM a try.
The Kernel I see in my settings/about phone is 2.6.35.13-g20c5d1d
I really just want to make sure I'm running the ROM kernel and not the stock since his has battery/performance tweaks.
2. Does anybody know if the built in stock screenshot (Power/Home) works with this ROM? Tried but it did not work.
Thanks a ton in advance!
Click to expand...
Click to collapse
I wish I could provide you with answers / specifics but it really does sound like you did everything right. So I wouldn't overly worry about it unless you don't feel like you're getting significant gains in battery life. As far as I remember screenshots do work. Hold power, tap home, find your SC in camera shots.
MrSmith317 said:
I wish I could provide you with answers / specifics but it really does sound like you did everything right. So I wouldn't overly worry about it unless you don't feel like you're getting significant gains in battery life. As far as I remember screenshots do work. Hold power, tap home, find your SC in camera shots.
Click to expand...
Click to collapse
Thanks, I was able to restore (I think) the boot.img from a Nandroid backup. After doing that in fastboot I just restored my stock ROM Nandroid (after wiping/factory restore/and wiping battery stats) and all seems well.
Thanks for taking the time to reply, it's appreciated

Phone won't boot; need to restore a deleted system file

Big problem with my I777 running stock Jellybean...
I deleted the wallpaper file from data\system\users\0 and now my phone will not boot. It powers on and gets to the lock screen, but won't allow me to slide to unlock. The phone isn't entirely unresponsive as the clock still updates every minute. But it won't do anything else.
I have my old wallpaper file handy on the computer, so I can surely copy it back to the phone. Question is: how?? I have USB debugging enabled so ADB is possible, but I have absolutely no idea how to use it. If I boot to system recovery the only option I get for ADB is sideload. I can execute ADB on my computer, it finds the device. But when I try to use the "push" command, ADB responds with "error: closed." I tried to use the "sideload" command (with a dummy file) just to see if ANY ADB command would work. "Sideload" works (the phone reports an error about the file being invalid), so I know the connection is fine.
Help appreciated, thanks. I'm stuck with a ****ty iPhone until this situation is resolved.
You're still on the stock kernel/recovery, so I'm not sure that you have any easy options. It is also relevant to know just how much information you want to recover.
File replacement:
Using desktop ODIN to flash a syiah kernel, then reboot to recovery:
You might then be able to adb-push the necessary item to /system, but this is a hack-approach to a problem better suited by a proper flash. <-- will retain all existing data & customization. Maybe worth a try, but I don't recommend it
Dirty-flash:
Using desktop ODIN to flash a syiah kernel, then reboot to recovery:
You will be able to flash a (custom) samsung-based firmware, which WILL overwrite /system, but will NOT overwrite your /data partition, likely allowing you to boot and properly back-up the stuff you want to keep, or even create a nandroid of the existing setup. <-- Will retain all existing data, will lose /system customisations. I have used this method.
Start-fresh:
Use desktop-Odin to flash the official firmware may be your only other option, which will retain everything in internal memory (photos, downloads, music, nandroid backups), but not messages, or any app data.
-Cyril
Mr. Barker said:
Big problem with my I777 running stock Jellybean...
I deleted the wallpaper file from data\system\users\0 and now my phone will not boot. It powers on and gets to the lock screen, but won't allow me to slide to unlock. The phone isn't entirely unresponsive as the clock still updates every minute. But it won't do anything else.
I have my old wallpaper file handy on the computer, so I can surely copy it back to the phone. Question is: how?? I have USB debugging enabled so ADB is possible, but I have absolutely no idea how to use it. If I boot to system recovery the only option I get for ADB is sideload. I can execute ADB on my computer, it finds the device. But when I try to use the "push" command, ADB responds with "error: closed." I tried to use the "sideload" command (with a dummy file) just to see if ANY ADB command would work. "Sideload" works (the phone reports an error about the file being invalid), so I know the connection is fine.
Help appreciated, thanks. I'm stuck with a ****ty iPhone until this situation is resolved.
Click to expand...
Click to collapse
cyril279 said:
You're still on the stock kernel/recovery, so I'm not sure that you have any easy options.
Click to expand...
Click to collapse
Well I do have CWM installed, but am curiously (and annoyingly) unable to boot to it now, for whatever reason. It boots to stock recovery instead, every time.
cyril279 said:
Using desktop ODIN to flash a syiah kernel, then reboot to recovery:
You might then be able to adb-push the necessary item to /system, but this is a hack-approach to a problem better suited by a proper flash. <-- maybe worth a try, but I don't recommend it
Click to expand...
Click to collapse
I think it's worth a try. I really would prefer to get my phone back working as it was, quickest way possible, because I've done a lot of heavy customization that would take many many hours to have to do over if I flash the official firmware again.
Could you please point me in the right direction of the syiah kernel, and proper instructions as to how to flash it? Would be much appreciated.
If it doesn't work out so hot, I'll try one of the other methods you mentioned. Thanks.
Mr. Barker said:
I think it's worth a try. I really would prefer to get my phone back working as it was, quickest way possible, because I've done a lot of heavy customization that would take many many hours to have to do over if I flash the official firmware again.
Could you please point me in the right direction of the syiah kernel, and proper instructions as to how to flash it? Would be much appreciated.
If it doesn't work out so hot, I'll try one of the other methods you mentioned. Thanks.
Click to expand...
Click to collapse
I would be glad to provide more detailed information, but I prefer to do so from a desktop computer, and I won't be near one for several days, so this may be a slow process unless one of our peers steps in to help.
In the meantime, you should gather:
-Odin 1.85 or 3.07
-A Siyah s2-v5.x or s2-v6.x .tar.md5 kernel (for the i777 or i9100)
The latter you can find at http://www.gokhanmoral.com
I will outline the process in a later post, explaining the purpose of each step.
Sure, I'm OK waiting a few days. I appreciate the help, I haven't done any flashing in quite some time and don't want to make a mistake, especially with all the important data that's at stake.
Thanks.
File Replacement Method
1) Use desktop Odin to flash Siyah kernel
-Installs a kernel that will allow you to perform a nandroid backup, and MAY allow you to adb push the missing file to the device.
-This WILL change the initial boot screen (can be corrected later, but does not affect the function of the firmware), and will notch the flash counter (simply doesn't matter).
2) Boot to recovery
3) Create nandroid backup
-If things go sideways, you have a snapshot of where you are. If you have to start from scratch, there are apps that can restore Apps, settings, and more, from a backup.
4) Adb push missing file to /data/path_file_belongs
5) Shell chmod XXX the missing file
-to correct file permissions; that 0.xml file has -rw------ on my device, which translates to 600 (I think)
6) Flash appropriate ajk kernel
-for stock jb, use "NoSwap" http://forum.xda-developers.com/showthread.php?t=2110542
-custom kernel that will boot stock rooted android.
7) Attempt Reboot into android
-If successful, reboot to recovery and perform another backup.
-If not successful, then we use a different method.
This is the trickier method of the three, but will retain all customization if it works. I have not tried it, and we're assuming that the missing file is actually the problem.
Please be sure that you are comfortable with all of the steps before attempting any of them. I will be able to provide step by step instructions, but not for several days.
Happy flashing,
-Cyril
Well, that was fun. Followed the instructions to a "t" and even learned some things. But, sadly, did not achieve the results I'd hoped for.
I was indeed able to push the wallpaper file over to data\system\users\0 and CHMOD it. But after flashing AJK "NoSwap" the phone shows the "Android is upgrading..." message, with "Starting apps." trying to process. But it doesn't. The little circle swirls a bit, then the screen goes black. The "Starting apps." message appears again, then the screen goes black again. And then it repeats this cycle forever. I eventually got irritated and yanked the battery.
So... *sigh*... what's my next best option?
The Nandroid backup completed successfully? If so, that's great, any APP customization is likely captured in the backup. How well they will restore is a different concern, but we need to get the device booted completely into android first.
Before moving onto the next step, lets reboot to recovery, clear cache and dalvik, and fix permissions. It's a bit of a shot in the dark, but I prefer to exhaust the possibility before abandoning this approach.
@Mr. Barker, You say that you've done a lot of heavy customization. What is the nature of the customization? app related? build.prop tweaks? I'm trying to determine how much might be lost by each of the next recovery methods.
@mrcook, what do you think of an attempt to dirty-flash cooked over a stock setup with corrupt /data?
cyril279 said:
Before moving onto the next step, lets reboot to recovery, clear cache and dalvik, and fix permissions. It's a bit of a shot in the dark, but I prefer to exhaust the possibility before abandoning this approach.
@Mr. Barker, You say that you've done a lot of heavy customization. What is the nature of the customization? app related? build.prop tweaks? I'm trying to determine how much might be lost by each of the next recovery methods.
@mrcook, what do you think of an attempt to dirty-flash cooked over a stock setup with corrupt /data?
Click to expand...
Click to collapse
I say wipe caches and fix permissions first. If that doesn't work format /system, and install a ROM of the same version of android.
After that if it's still not booting suck it up do a full wipe and start from scratch.
Sent from my SGH-S959G
@Mr. Barker
If the cache wipes / permissions fix doesn't help, then our next attempt is:
**this assumes that you were running stock Android 4.1.2 when the trouble began**
get i777UCMD8 cooked v2.2 onto a flashdrive, (or prepare it for sideload)
reboot to recovery
format /system
install cooked v2.2
attempt to boot into android
OK, I'll give it a try, thanks.
Hooray! All's well that ends well. Flashing i777UCMD8 cooked v2.2 got me up & running again, near-same as I had everything before. Just a little work to do to get it right back how I had it. Thanks a million, gents! :victory:
Two questions remain, for the moment:
+ How can I get the "AM/PM" to display on the notification bar? I'm in the US, and prefer to have this for the 12-hour clock. But using this ROM, it is omitted even when time is set to 12-hour clock.
+ How can I restore the default battery charging icon from the stock firmware? The one that comes bundled with this cooked ROM is needlessly flashy.
Mr. Barker said:
Hooray! All's well that ends well. Flashing i777UCMD8 cooked v2.2 got me up & running again, near-same as I had everything before. Just a little work to do to get it right back how I had it. Thanks a million, gents! :victory:
Two questions remain, for the moment:
+ How can I get the "AM/PM" to display on the notification bar? I'm in the US, and prefer to have this for the 12-hour clock. But using this ROM, it is omitted even when time is set to 12-hour clock.
+ How can I restore the black notification pull-down menu? This ROM sets it transparent by default, which doesn't work for me.
Click to expand...
Click to collapse
Am/pm is gone forever. I removed because I think it looks better without it. Use the sun. You'll get used to it after a couple days and never miss it.
To change the notification background go to the mods section of the installer, and just install the black notification background.
Sent from my SGH-S959G
mr-cook said:
Am/pm is gone forever. I removed because I think it looks better without it. Use the sun. You'll get used to it after a couple days and never miss it.
Click to expand...
Click to collapse
Oh, no, I was afraid you were going to say that. *sigh*
Unfortunately I will not get used to it, and will miss it. It's the little things that really matter to me, and this is one of them.
Is there absolutely no way I can add it back in? Maybe by editing or replacing a certain file? Or perhaps there's a notification bar replacement that will facilitate this need?
Also, how can I restore the default battery charging icon from the stock firmware? The one that comes bundled with this cooked ROM, I feel, is needlessly flashy.
Other than these two points, I am quite pleased with this ROM. Is it just me or does it run a little quicker than the stock one?
"needlessly flashy"
Simply asking 'how to change the icon' is sufficient, and inherently implies that you prefer something different.
Cooked v2.2 is definitely quicker than stock;
The premise of both cooked and shostock are that they have taken the stock firmware, and stripped it down of unnecessary junk, and run it over a well-optimized kernel for the best touchwiz experience that you could possibly have on this device.
If your firmware desires are different than what cooked v2.2 provides, then I suggest creating a nandroid backup, wiping /system, and giving shostock a try. It's the other touchwiz favorite for the i777, packaged with a different very good kernel, and also runs quicker than stock.
Mr. Barker said:
Oh, no, I was afraid you were going to say that. *sigh*
Unfortunately I will not get used to it, and will miss it. It's the little things that really matter to me, and this is one of them.
Is there absolutely no way I can add it back in? Maybe by editing or replacing a certain file? Or perhaps there's a notification bar replacement that will facilitate this need?
Also, how can I restore the default battery charging icon from the stock firmware? The one that comes bundled with this cooked ROM, I feel, is needlessly flashy.
Other than these two points, I am quite pleased with this ROM. Is it just me or does it run a little quicker than the stock one?
Click to expand...
Click to collapse
To close the loop, now your initial boot screen is a yellow triangle with an exclamation point? It doesn't affect the functionality of the firmware at all, but if you prefer to have the correct initial boot animation, then you'll need to follow an additional procedure.
Summary:
Nandroid-backup desired setup
Flash official stock-firmware to the device via Desktop-Odin (clears the warning)
Root & recovery via Framaroot/Mobile-Odin (a method that does NOT trip the custom-flash monitor)
Restore nandroid to return to the established custom setup
Procedure:
gather onto internal memory, or micro-sd:
-Framaroot
-Mobile Odin APK
-Mobile Odin flash kernel for i777
-Boot.img (extracted from your chosen firmware.zip)
boot to recovery
perform nandroid backup
^^ this MUST complete successfully
perform factory reset
boot to download mode
flash official UCMD8 using Desktop ODIN
^^ clears the custom-flash warning
install and use framaroot
^^ uses an exploit to establish and manage root access
install mobile Odin and the mobile Odin flash-kernel
^^ the method that will NOT trip the custom-flash monitor
flash the boot.img via Mobile Odin
^^ flashes the kernel and recovery of the firmware that you are going to restore
boot to recovery
restore nandroid backup
enjoy
-Cyril
If I am going to be restoring the nandroid backup, must I install & use the very same firmware that was installed when I made the backup? Or could I, say, simply flash the stock firmware and be done with it? (i.e. not use mobile odin to install a custom firmware afterwards) My point is, are nandroid backups firmware-specific?
If I opt to go the custom firmware route, how do I go about getting the boot.img file? Simply rename zimage, or ???
Before all this I've never flashed anything but stock firmware, and never had to create nor restore nandroid backups. So most of this is all new to me. But I enjoy the learning process.
Mr. Barker said:
If I am going to be restoring the nandroid backup, must I install & use the very same firmware that was installed when I made the backup?
Click to expand...
Click to collapse
Different custom firmwares may be structured differently, so for the lowest likelihood of compatibility issues, nandroid backups should be considered firmware specific.
Edit: As Mentioned below, a CWM nandroid will restore the entire backed-up firmware installation, which can be done over ANY firmware.
If the goal is to keep your App data across different firmwares, then a Titanium backup restoration may be what you're after. /Edit
Mr. Barker said:
[...]could I, say, simply flash the stock firmware and be done with it? (i.e. not use mobile odin to install a custom firmware afterwards)[...]
Click to expand...
Click to collapse
I don't think that the stock recovery allows to restore nandroid backups at all. The restrictive nature of the stock recovery is one of the more practical reasons to root the device & use a custom kernel.
Mr. Barker said:
If I opt to go the custom firmware route, how do I go about getting the boot.img file? Simply rename zimage, or ???
Click to expand...
Click to collapse
Mobile Odin will flash a zImage, no need to rename it. I didn't check to see that shostock or cooked use a zImage instead of boot.img.
cyril279 said:
Different custom firmwares may be structured differently, so for the lowest likelihood of compatibility issues, nandroid backups should be considered firmware specific.
Click to expand...
Click to collapse
?? I thought that because a nandroid copied (backup) and then formatted/recopied the 5 partitions (restore), that it didn't matter what firmware you had installed?

[Q] mobile data not working and charging port broken

You've probably heard this song and dance before, but my phone only charges if I hold the connector a little to the left of the port of the phone. This is a phone issue, I've tried like 5 cables. I am rooted so I'm worried att will just turn me away if I go to a repair place. I am s-on. I'm hoping maybe this is something I can fix myself. Any ideas?
Secondly, today I noticed that my mobile data only works for browsing google. Only google's web results show up. If I click on a link from there, it won't work. Any other app does not work. I've tried a soft reset and rebooting several times, and no I don't have any proxies enabled. If anyone has the stock lollipop build.prop, I'd really appreciate that. Very strange issue that I've never heard of. Running elementalx kernel and stock rom.
siren_shadows said:
my phone only charges if I hold the connector a little to the left of the port of the phone. This is a phone issue, I've tried like 5 cables. I am rooted so I'm worried att will just turn me away if I go to a repair place. I am s-on. I'm hoping maybe this is something I can fix myself. Any ideas?
Click to expand...
Click to collapse
If you purchased the phone from AT&T, they will not deny warranty due to root, unlocked bootloader, etc. Folks here have had good success with warranty claims on modified phones with AT&T. If you look at AT&T's warranty terms, you will see that they changed a year or 2 ago. Modifying the software is no longer mentioned under the items that void the warranty. Only physical damage and water damage are now listed.
siren_shadows said:
Secondly, today I noticed that my mobile data only works for browsing google. Only google's web results show up. If I click on a link from there, it won't work. Any other app does not work. I've tried a soft reset and rebooting several times, and no I don't have any proxies enabled. If anyone has the stock lollipop build.prop, I'd really appreciate that. Very strange issue that I've never heard of. Running elementalx kernel and stock rom.
Click to expand...
Click to collapse
What happens if you just type in a URL, without going through Google search results?
redpoint73 said:
If you purchased the phone from AT&T, they will not deny warranty due to root, unlocked bootloader, etc. Folks here have had good success with warranty claims on modified phones with AT&T. If you look at AT&T's warranty terms, you will see that they changed a year or 2 ago. Modifying the software is no longer mentioned under the items that void the warranty. Only physical damage and water damage are now listed.
What happens if you just type in a URL, without going through Google search results?
Click to expand...
Click to collapse
ah, thanks. if I type in a URL, I get the same dns lookup error. seems YouTube, Instagram, and Google are the only things that work. play store does not work.
siren_shadows said:
ah, thanks. if I type in a URL, I get the same dns lookup error. seems YouTube, Instagram, and Google are the only things that work. play store does not work.
Click to expand...
Click to collapse
Did you make any recent changes that may have caused this, such as flashing the custom kernel?
redpoint73 said:
Did you make any recent changes that may have caused this, such as flashing the custom kernel?
Click to expand...
Click to collapse
yeah, I reinstalled elementalx. I'd love a stock build.prop and an insecure stock kernel if that's possible.
siren_shadows said:
yeah, I reinstalled elementalx. I'd love a stock build.prop and an insecure stock kernel if that's possible.
Click to expand...
Click to collapse
Did you modify build.prop?
redpoint73 said:
Did you modify build.prop?
Click to expand...
Click to collapse
yeah, but I deleted the values. I'm worried I may have deleted something I wasn't meaning to, though.
siren_shadows said:
yeah, but I deleted the values. I'm worried I may have deleted something I wasn't meaning to, though.
Click to expand...
Click to collapse
WNC just posted the 4.28.502 version of his ROM here: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
I assume the build.prop is stock; and kernel is insecure.
unfortunately, I am s-on.
siren_shadows said:
unfortunately, I am s-on.
Click to expand...
Click to collapse
s-off is only needed to flash firmware (and it sounds like you already have Lollipop firmware).
You can pull boot.img from the ROM.zip without even actually flashing the whole ROM.
build.prop, not sure if there is a similar way to do that (extract without flashing he whole ROM). Otherwise, flash the ROM, and extract/copy the build.prop for use on the fully stock ROM.
Or just flash the ROM and use it, WNC's work is always good. Its basically the stock ROM, just cleaned up.
redpoint73 said:
s-off is only needed to flash firmware (and it sounds like you already have Lollipop firmware).
You can pull boot.img from the ROM.zip without even actually flashing the whole ROM.
build.prop, not sure if there is a similar way to do that (extract without flashing he whole ROM). Otherwise, flash the ROM, and extract/copy the build.prop for use on the fully stock ROM.
Or just flash the ROM and use it, WNC's work is always good. Its basically the stock ROM, just cleaned up.
Click to expand...
Click to collapse
I'm not averse to using the ROM, I just don't want to lose my data or have any long boots/incompatibility issues. I used the latest OTA from the official att update.
siren_shadows said:
I'm not averse to using the ROM, I just don't want to lose my data or have any long boots/incompatibility issues. I used the latest OTA from the official att update.
Click to expand...
Click to collapse
You shouldn't have any long boot or imcompatibility issues. The ROM I linked is based on the same ROM you are on (AT&T Lollipop update) just with bloat removed and some performance enhancements. What you can do, if you want to keep the current stock ROM:
1) Download the ROM I linked
2) Unzip on your computer
3) Find boot.img, copy it to your fastboot folder. This should be the stock, insecure kernel
4) Connect phone to computer in fastboot mode
5) Flash boot.img with command: fastboot flash boot boot.img
Reboot the phone, and see if the data is working again. If not, you can try to restore the build.prop. I don't personally know of a way to pull this from the ROM similar to above for the kernel. So this may be a little convoluted, but just a thought:
6) Make a nandroid of the current setup
7) Flash the ROM by WNC
8) Use a file explorer to copy build.prop file to internal storage or the removable SD
9) Restore your nandroid (back to stock AT&T) that you just made in Step 6 above
10) Copy the build.prop from WNC's ROM to overwrite the one that you modified
11) If it doesn't work, you are no worse off since you have a nandroid snapshot of your current setup (won't lose any user data)
redpoint73 said:
You shouldn't have any long boot or imcompatibility issues. The ROM I linked is based on the same ROM you are on (AT&T Lollipop update) just with bloat removed and some performance enhancements. What you can do, if you want to keep the current stock ROM:
1) Download the ROM I linked
2) Unzip on your computer
3) Find boot.img, copy it to your fastboot folder. This should be the stock, insecure kernel
4) Connect phone to computer in fastboot mode
5) Flash boot.img with command: fastboot flash boot boot.img
Reboot the phone, and see if the data is working again. If not, you can try to restore the build.prop. I don't personally know of a way to pull this from the ROM similar to above for the kernel. So this may be a little convoluted, but just a thought:
6) Make a nandroid of the current setup
7) Flash the ROM by WNC
8) Use a file explorer to copy build.prop file to internal storage or the removable SD
9) Restore your nandroid (back to stock AT&T) that you just made in Step 6 above
10) Copy the build.prop from WNC's ROM to overwrite the one that you modified
11) If it doesn't work, you are no worse off since you have a nandroid snapshot of your current setup (won't lose any user data)
Click to expand...
Click to collapse
I've got some very bad news. I tried replacing the build prop with the one in the zip that you linked, and now my phone won't boot up. at all. can't even get into recovery.
siren_shadows said:
I've got some very bad news. I tried replacing the build prop with the one in the zip that you linked, and now my phone won't boot up. at all. can't even get into recovery.
Click to expand...
Click to collapse
Can you still get into bootloader?
sigh. was able to get into recovery. gonna restore. don't think i had a modified build.prop at that time either... hopefully my cable won't mess up before i copy the backup back onto my phone
redpoint73 said:
Do you mean you can't get into bootloader?
If so, that doesn't actually make any sense, bootloader is write protected with s-on. So there is no way this can be corrupted or over-written.
This seems scary. But just take a breath, as I don't think this is as bad as it looks.
What happened after you copied the file?
Does the screen come on at all?
Click to expand...
Click to collapse
i got a black screen after a reboot. but holding power and volume up did the hard reset and i had to really quickly press volume down. like a split second window
siren_shadows said:
sigh. was able to get into recovery. gonna restore. don't think i had a modified build.prop at that time either... hopefully my cable won't mess up before i copy the backup back onto my phone
Click to expand...
Click to collapse
You didn't need to move the backup off the phone.
Its not a bad idea to make a copy of the backup (in the event the one on internal storage gets wiped) to your computer.
But its also good to keep a backup either on internal storage or on the removable SD.
redpoint73 said:
You didn't need to move the backup off the phone.
Its not a bad idea to make a copy of the backup (in the event the one on internal storage gets wiped) to your computer.
But its also good to keep a backup either on internal storage or on the removable SD.
Click to expand...
Click to collapse
I was a genius and decided I would save space by moving onto my computer. However, I am restoring now. That'll fix my black screen issue, right?
siren_shadows said:
I am restoring now. That'll fix my black screen issue, right?
Click to expand...
Click to collapse
Yes, build.prop is part of the ROM, so the TWRP backup will put you back to where you were before trying to replace the build.prop file.
Odd, I wouldn't think that replacing the build.prop with the one for a nearly stock ROM (and same LP base) would render the phone unbootable into OS.
redpoint73 said:
Yes, build.prop is part of the ROM, so the TWRP backup will put you back to where you were before trying to replace the build.prop file.
Odd, I wouldn't think that replacing the build.prop with the one for a nearly stock ROM (and same LP base) would render the phone unbootable into OS.
Click to expand...
Click to collapse
who knows. My issue isn't fixed regarding mobile data, either. At least I have a usable phone tho!

Categories

Resources