Hi all.
I wanted to thank all of the devs and modders on this device forum for all your hard work and feedback.
I have the unlocked/software updated/rooted/deodexed system, now I am wondering if your custom kernels will be compatible with the
system update? I tried the AdrenalineInjector sans Fugo option, ummmm.....nope. Didn't like that at ALL lol.
Let's hear it for Nandroids.
I have, well, more than my share of Nandroids and working TWRP recovery, so I am confident to the point of reckless with experimental flashes/mods. I have just tweaked out my DeOdexed system with the power boot menu, and just finished customizing my launcher, homescreen, apps, etc.
That being said, I am doing yet one more Nandroid of this one and trying both aaarrrggghhhs kernel (I apologize for the misspell) and shabby's p's and q's kernel.
I will post an update of either "woohoo!!" or "nnnyohhhhhh..."
Keep the mods coming, I am ready to try them all!
drakeheart77
drakeheart77 said:
Hi all.
I wanted to thank all of the devs and modders on this device forum for all your hard work and feedback.
I have the unlocked/software updated/rooted/deodexed system, now I am wondering if your custom kernels will be compatible with the
system update? I tried the AdrenalineInjector sans Fugo option, ummmm.....nope. Didn't like that at ALL lol.
Let's hear it for Nandroids.
I have, well, more than my share of Nandroids and working TWRP recovery, so I am confident to the point of reckless with experimental flashes/mods. I have just tweaked out my DeOdexed system with the power boot menu, and just finished customizing my launcher, homescreen, apps, etc.
That being said, I am doing yet one more Nandroid of this one and trying both aaarrrggghhhs kernel (I apologize for the misspell) and shabby's p's and q's kernel.
I will post an update of either "woohoo!!" or "nnnyohhhhhh..."
Keep the mods coming, I am ready to try them all!
drakeheart77
Click to expand...
Click to collapse
You didn't like the adrenaline injector? I just flashed that and I really don't see any negative effects so far.
What didn't you like about it?
None that work completely. You can flash arrrghhh's kernel if you'd like. You can overclock up to 1.89 GHz and underclock down to 96 MHz ... but it will break your wifi until the kernel gets updated. I'm not sure how long that will take though. Other than that, everything else works perfectly fine on it. Other than that, I believe a few options are in the works, but nothing's been finaled yet.
It wasn't that I didn't like Adrenaline, it's that it wouldn't boot lol. I don't think I did a proper clean before installing, plus my question is since my system is already deodexed, would it do more harm than good?
As far as the kernel goes, I both am not put out yet slightly perturbed by the wifi issue. Whenever a custom ROM does come our way, kernel devs will have to be leery of that little bug...could delay a port to our system a bit. I don't really OC for any reason, but many users do and will want a working kernel. MY desire for a kernel is one that is ready for wifi tethering for root users....Net-something lol i forgot the term.
Sent from my XT897 using xda premium
Please don't post question threads in the Development sections as they have no place there and we have a Q&A section designed for all your questions.
Thanks
AvRS
drakeheart77 said:
As far as the kernel goes, I both am not put out yet slightly perturbed by the wifi issue. Whenever a custom ROM does come our way, kernel devs will have to be leery of that little bug...could delay a port to our system a bit. I don't really OC for any reason, but many users do and will want a working kernel. MY desire for a kernel is one that is ready for wifi tethering for root users....Net-something lol i forgot the term.
Click to expand...
Click to collapse
The only reason the wifi won't work on the update with the old kernels is because of the changes the update made. Any ports should have that issue resolved prior to release, and once stable depending on what gets updated I doubt we'll run into kernel/wifi issues although I cannot guarantee that. I know the current OTA made changes to the modem drivers which I'm sure is part of the reason the kernels are incompatable.
I know when I was running the OTA and broke my wifi and tried restoring the stock boot.img (with original oem kernel) it wouldn't even boot the updated system. They're almost like two completely different softwares with the same UI lol.
How do we get new updated stock boot and recovery images? I rely on restoring pre-update Nandroids for whatever flub I may have yet to pull off lol. Anything I can do to help.
Sent from my XT897 using xda premium
drakeheart77 said:
It wasn't that I didn't like Adrenaline, it's that it wouldn't boot lol. I don't think I did a proper clean before installing, plus my question is since my system is already deodexed, would it do more harm than good?
As far as the kernel goes, I both am not put out yet slightly perturbed by the wifi issue. Whenever a custom ROM does come our way, kernel devs will have to be leery of that little bug...could delay a port to our system a bit. I don't really OC for any reason, but many users do and will want a working kernel. MY desire for a kernel is one that is ready for wifi tethering for root users....Net-something lol i forgot the term.
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
Did you replace the update binary?
Sorry for the laziness on my replies. All I did was cache/dalvik wipe and success.
However I do need some help, I am uploading to Dropbox my non-rooted system and boot images. How do I share the links to my DP URL?
Also, where do I locate the stock recovery? Wouldn't the recovery be the same, because it wasn't a total ROM/system revamp? if that is the case then shabby has posted links for stock system and boot.
Sent from my XT897 using xda premium
Oh btw the files are for the 77.1.80 system update and NO root, and completely bare and odexed.
Sent from my XT897 using xda premium
http://db.tt/7p2Gv4cl
System
http://db.tt/qzu66AyF
System md5
http://db.tt/T2N0vYne
Stock recovery
http://db.tt/gbnt0Ddg
Boot
http://db.tt/oz8QPkP8
Boot md5
Sorry they are not clickable links, just copy & paste until I figure out the process lol.
Hope these files help!!
Sent from my XT897 using xda premium
drakeheart77 said:
http://db.tt/7p2Gv4cl
System
http://db.tt/qzu66AyF
System md5
http://db.tt/T2N0vYne
Stock recovery
http://db.tt/gbnt0Ddg
Boot
http://db.tt/oz8QPkP8
Boot md5
Sorry they are not clickable links, just copy & paste until I figure out the process lol.
Hope these files help!!
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
Seeing as its been a while since I have had to do anything manually (so spoiled these days!)
I know I can use fastboot to push the img for the recovery, but how do I go about getting the system/boot flashed over?
Thanks!
EDIT: TBQH, never had to deal with .win files...
Hammerfest said:
Seeing as its been a while since I have had to do anything manually (so spoiled these days!)
I know I can use fastboot to push the img for the recovery, but how do I go about getting the system/boot flashed over?
Thanks!
EDIT: TBQH, never had to deal with .win files...
Click to expand...
Click to collapse
You need the TWRP recovery installed. If you've never used it before, you'll need to make a backup in order to generate the correct folders necessary. The directory will be either on your memory card (/external1) or internal memory (/sdcard). The folder path will be TWRP/BACKUPS/**your**phone's**serial**number**/
Inside that folder, create a folder and name it "stock backup" or whatever you want to name it. Then put the *.win and the *.md5 files in there. Put the stock recover in whatever folder you have your adb installed.
Reboot to recovery.
Restore the boot and system partitions from this backup (will show as "stock backup" or whatever you named it)
Once the restore is complete, back out to the main menu ... go to reboot -> choose bootloader
Flash your stock recovery ( fastboot flash recovery **whatever you named your recovery file**.img )
I typically flash this twice one right after the other just in case
Reboot your system ( fastboot reboot )
From there you should be all set.
drakeheart77 said:
http://db.tt/7p2Gv4cl
System
http://db.tt/qzu66AyF
System md5
http://db.tt/T2N0vYne
Stock recovery
http://db.tt/gbnt0Ddg
Boot
http://db.tt/oz8QPkP8
Boot md5
Sorry they are not clickable links, just copy & paste until I figure out the process lol.
Hope these files help!!
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
Thanks for the files Drake!
However, I must be missing something because I flashed that system file and when I go to about phone it shows 7.7.1Q 8/3/12 not 7.7.80.
I'm pretty sure I flashed it right because I lost root and got back a bunch of the stupid Sprint stuff that I had removed and got your spiffy boot logo. I'm thinking about doing the OTA update from this baseline with stock recovery and then reinstalling twrp and re-running root.
*edit*
And that just put me back to infinite reboots again. I'm going to delete the stupid update from cache again and cut my losses for now, I've been up 22 hours so perhaps a fresh look tomorrow will help.
Not sure about the update not being there...don't know if that is system-specific or not all I know is that I made that back-up after the update was installed. Please leave any other feedback thank u for the reply. I may try and post a new system file.!
Sent from my XT897 using xda premium
Were u looking at the Build # or SW Version in "settings/about phone"?
The only thing simple is the belief in simplicity.
Also u cannot install Any OTA updates with ANY custom recovery on this phone. Stock recovery is necessary that's why I posted the image.
The only thing simple is the belief in simplicity.
afidel said:
Thanks for the files Drake!
However, I must be missing something because I flashed that system file and when I go to about phone it shows 7.7.1Q 8/3/12 not 7.7.80.
I'm pretty sure I flashed it right because I lost root and got back a bunch of the stupid Sprint stuff that I had removed and got your spiffy boot logo. I'm thinking about doing the OTA update from this baseline with stock recovery and then reinstalling twrp and re-running root.
*edit*
And that just put me back to infinite reboots again. I'm going to delete the stupid update from cache again and cut my losses for now, I've been up 22 hours so perhaps a fresh look tomorrow will help.
Click to expand...
Click to collapse
I'm having/had the same exact results.
Just got the phone today, rooted it, installed CWM, then decided to do the update not realizing the issue that would cause. Of course it failed in CWM and then I got into a reboot loop.
Flashed TWRP, restored the files listed here, got me back to a bootable ROM. Then, downloaded the update, told it to apply, shuts down,...bam,...boot loop. :silly:
All I want to do is get back to a completely stock (unlocked bootloader is fine), so I can update to 7.7.80, then mod & tweak from there.
This phone is so dang frustrating after coming from an Epic which was pretty brainless to flash. This Photon is kicking my butt..
Finally got past it, not sure how...then I fubar'd it again by trying to do the 1% & toggle mods. Ugh...so frustrating..
Just putting this out there, may not be true for all phones, but with my Q I got a lot of boot loops restoring backups from my external sd card, the ones I restored from internal storage worked okay. Obviously it could be corruption with the backups/sd card as well. With the toggles make sure you flash the toggles for the updated systemui and framework files and not the stock system files if you have taken the ota update. In other words make sure you match the version of the mods to your current software version. I found this phone very frustrating from a modder's perspective at first, I have really come to love the qwerty and hardware over time... the Snap Dragon s4 is fast!
Sent from my XT897 using xda app-developers app
Related
ok, so i've read what i think i need to root and install a custom ROM (i think i want to try eagles blood 2.8 first http://forum.xda-developers.com/showthread.php?t=1124522)
just got my G2x on Monday and it has GB 2.3.3 but i have not checked if it has an update and not sure i want to update it first, but that is my question.
should i do an update first before i do anything else or does it even matter? i mean i will root, then do a backup, then install the ROM, right? so it shouldnt matter if the phone is the latest and greatest from LG or T-Mobile as i will be overwriting it anyway...at least that is how i think it works
also i have seen where people are saying to wipe everything (or at least a few folders), how is that done? just delete what is in the folders or is there a tool to wipe said data?
No OTA updates are available, but is unnecessary anyway. Also, no need to root if you want to flash these roms as they already have root access. Flash clockworkmod (search for the thread on that) then flash the rom you want. All the instructions are there.
Sent from my LG-P999 using xda premium
thanks, i didnt even want to try the update, but since you said there isnt one, i tried and sure enough, i have the latest already
OTA=over the air? i've seen that one a few times, some new acronyms here i need to learn
this is what i was going to do first
http://forum.xda-developers.com/showthread.php?t=1255214
1st Root your phone. Then Flash cwm thru nv flash. This is the only way if you want to manually boot into recovery
Sent from my LG-P999 using XDA App
chrisram88 said:
1st Root your phone. Then Flash cwm thru nv flash. This is the only way if you want to manually boot into recovery
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
No need to root before nvflashing cwm.
Yes, OTA is "over the air". And just so you know, make sure you follow those nvflash steps EXACTLY as written. What you are choosing to flash, however, is the completely stock (although rooted) version of android 2.3.3 that you already have on your phone. This is fine, but after you get cwm you can flash any custom rom you find within the development section as well. I recommend at least choosing cm7 because the stock rom sucks.
Sent from my LG-P999 using xda premium
e4e5nf3nc6 said:
No need to root before nvflashing cwm.
Yes, OTA is "over the air". And just so you know, make sure you follow those nvflash steps EXACTLY as written. What you are choosing to flash, however, is the completely stock (although rooted) version of android 2.3.3 that you already have on your phone. This is fine, but after you get cwm you can flash any custom rom you find within the development section as well. I recommend at least choosing cm7 because the stock rom sucks.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
gotcha, so that thread is the one i need to follow?
http://forum.xda-developers.com/showthread.php?t=1056847
This one. It's actually linked as the first step in your thread. This is the important one. Read it over a couple times first, and maybe watch some videos too.
Everything after that step in your thread is basically how to flash a custom rom. They are just choosing a rooted version of stock as their example.
Sent from my LG-P999 using xda premium
root first if you want to backup any of the apps on the phone.
i rooted , clockworked , backed up the phone then copied the int and ext sd roms to my pc. installed titanium and backed up all the apps in the stock rom i thought i might want to keep. ( mostly the nova demo and need for speed) . copy your rom contents over so if you mistakenly format your sd card you can still return the phone to stock. ( don't ask i did it ) tryed cm7 stable. liked it but had sleep of death issues. returned the phone to stock . messed with the stock apps and root explorer backed everything up again. and now im ruing weapon r and love it. no stutter and smooth as a hot knife going thru butter and no sleep of death! and USB works every time. even love the loader he used.
ok followed the steps here
http://forum.xda-developers.com/showthread.php?t=1060715
then here (which is actually referenced first in the above thread)
http://forum.xda-developers.com/showthread.php?t=1056847
and then here (which is done after you do the stuff in the above thread)
http://forum.xda-developers.com/showthread.php?t=1255214
i put eagles blood 2.8 on it and it seems to be doing ok.
couple of things, dont know if this is a theme issue, but it no longer says 4G, it has a letter H instead
also i moved the notification bar to the bottom but cant remember where to change that back to the top
that looks good. don't for get to copy off the internal and external sd chips and keep that data safe. when you made your backup in clockwork it stored it on the internal chip. titanium by default i be leave uses the external. if any thing goes wrong, as long as you have access to those backups and can boot to clockwork you can get your phone working.
dodgefan67 said:
ok followed the steps here
http://forum.xda-developers.com/showthread.php?t=1060715
then here (which is actually referenced first in the above thread)
http://forum.xda-developers.com/showthread.php?t=1056847
and then here (which is done after you do the stuff in the above thread)
http://forum.xda-developers.com/showthread.php?t=1255214
i put eagles blood 2.8 on it and it seems to be doing ok.
couple of things, dont know if this is a theme issue, but it no longer says 4G, it has a letter H instead
also i moved the notification bar to the bottom but cant remember where to change that back to the top
Click to expand...
Click to collapse
The h is the same as 4g. There are mods to change those icons that can be found on xda. As far as the status bar, I think that setting is located somewhere in the tablet tweaks menu.
Sent from my LG-P999 using xda premium
e4e5nf3nc6 said:
The h is the same as 4g. There are mods to change those icons that can be found on xda. As far as the status bar, I think that setting is located somewhere in the tablet tweaks menu.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
yes in the tablet tweaks, thanks
but now i have a bigger problem. i dont seem to have any network access now, 4g, 3g, edge, nothing. i can make calls and send texts, but no data. should i start a new thread?
dodgefan67 said:
yes in the tablet tweaks, thanks
but now i have a bigger problem. i dont seem to have any network access now, 4g, 3g, edge, nothing. i can make calls and send texts, but no data. should i start a new thread?
Click to expand...
Click to collapse
Occasionally on cm7 based roms data will drop out and u need to reboot to bring it back...if u haven't already, try a reboot.
Sent from my LG-P999 using xda premium
JuEv0splash said:
Occasionally on cm7 based roms data will drop out and u need to reboot to bring it back...if u haven't already, try a reboot.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
DOH! yup that was it, reboot brought it back. thanks!
so like i posted before it shows an H instead of 4G so i'm assuming that stands for HSPA?
Yeah that's it. How are you liking the rom? Bear in mind that now you have root access you can do all sorts of customizations. You can flash kernels that allow for overclocking or underclocking, use titanium backup (recommended) to preserve all apps and app data, modify boot animations and status bar icons, basically anything you want. Enjoy!
Sent from my LG-P999 using xda premium
im liking it so far, and yeah i understand about root access, i've done linux admin and use debian at home, so im really liking this, its kind of like running debian now instead of ubuntu or mint, getting rid of all the junk that gets piled on top of the pure OS!
im sure i will try other ROMs as well and maybe other kernels. do those install the same way? using ROM Manager?
dodgefan67 said:
im liking it so far, and yeah i understand about root access, i've done linux admin and use debian at home, so im really liking this, its kind of like running debian now instead of ubuntu or mint, getting rid of all the junk that gets piled on top of the pure OS!
im sure i will try other ROMs as well and maybe other kernels. do those install the same way? using ROM Manager?
Click to expand...
Click to collapse
Yea you flash it in recovery.
Sent from my LG-P999 using XDA App
now that yore rooted and have clockwork you can flash things safely
just remember to backup, and to wipe the davik cache its in advanced menu.
try weapon r and then add the update new clip to it , its smooth and no bugs so far fro me.
Hey, so lkranser and I have made a great discovery tonight.
lkranser's recovery partition was erased due to some of my advice to him.
So I cat'd my recovery partition (/dev/block/mmcblk1p16) into a recovery.img file, and he was able to cat that recovery image file that I created into his recovery partition.
So now the question is how can we use this to our advantage and get CWM on /dev/block/mmcblk1p16, and get it to come up with holding both volume buttons and the power button, as this is the way it works on every other phone.
Idea guys, this thread is a place to throw out some serious ideas to get this to work. Please don't ask for any how-to's for this here.
jimbridgman said:
Hey, so lkranser and I have made a great discovery tonight.
lkranser's recovery partition was erased due to some of my advice to him.
So I cat'd my recovery partition (/dev/block/mmcblk1p16) into a recovery.img file, and he was able to cat that recovery image file that I created into his recovery partition.
So now the question is how can we use this to our advantage and get CWM on /dev/block/mmcblk1p16, and get it to come up with holding both volume buttons and the power button, as this is the way it works on every other phone.
Idea guys, this thread is a place to throw out some serious ideas to get this to work. Please don't ask for any how-to's for this here.
Click to expand...
Click to collapse
a few things.
1. it was not anything you did that made me wipe recovery, it was just me being a complete idiot
2. basically I think we need to figure out how to modify what you cat'd over. then we can pull an image from a similar device that has a true cwm recovery and edit what we need to like the specific partitions in order for it to work on our phone. then we can just cat it over and bingo! working full cwm.
3. why is it that stupid things I do always end up leading to great discoveries on here. this is like the 3rd time it has happened.
so any ideas on how to mount that file in a way we can actually look at it.
---------- Post added at 09:39 PM ---------- Previous post was at 09:22 PM ----------
Some more stuff I found: http://www.clockworkmod.com/rommanager
That has official cwm recovery builds for all supported devices. many have images, I think all the ones with unlocked bootloaders. those images would be flashed with fastboot, or probably could be cat'd over like we did.
others have flashable zips (all the moto devices) and i think those are all the ones with lockked bootloaders. I don't have tie to dig into what they really do right now, but i appears that they just copy some files for recovery to /etc and other places suggesting those devices have a different recovery method
I still think the biggest priority is figuring out how to see the contents of the images with our recovery stuff and those for other devices.
I can tell you what happened to me the other day, I was getting ready to to use RSD as I was bootlooped and went to boot into fastboot but accidentally booted into BP tools and when it booted it booted to CWM. So I tried it a couple of times with the same exact results. Fluke, IDK ??? Havent been in trouble since to try it again!
JRW 28 said:
I can tell you what happened to me the other day, I was getting ready to to use RSD as I was bootlooped and went to boot into fastboot but accidentally booted into BP tools and when it booted it booted to CWM. So I tried it a couple of times with the same exact results. Fluke, IDK ??? Havent been in trouble since to try it again!
Click to expand...
Click to collapse
what is BP tools even
Sent from my MB865 using xda premium
lkrasner said:
what is BP tools even
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I've wondered the same thing????
JRW 28 said:
I've wondered the same thing????
Click to expand...
Click to collapse
it never does anything for me. it just boots normally into the os. that is why it is going to cwm if you have it set on boot. it did that for me too
lkrasner said:
it never does anything for me. it just boots normally into the os. that is why it is going to cwm if you have it set on boot. it did that for me too
Click to expand...
Click to collapse
Yea but even on a normal boot I could never get past the red moto screen, tried several times hopi g to get into CWM and not have to RSD back.
Just wierd that normal boot wouldn't work but BP tools did?
The only difference I could see is an app called CQATest in the drawer. Has many different tests available. About 50+
Sent from my MB865 using xda premium
made a major breakthrough. my internet is down though so I can't really keep working on it or post details, but I should by tomorrow. stay tuned. stupid Comcast.
EDIT: I'm back up. So basically I figured out how to separate the kernel and ramdisk of both our boot and recovery images. it did not work to re-combine them, but it may still be useful for building cyanogenmod to be able to have our straight kernel. PM me if you wan't more detail.
That said, it did not do exactly what I wanted, but I think at this point we should be able to simply build cwm according to the guides for it. I am doing it right now, and it is in the final build process, so I will let you know how it all turns out.
So, I got it built successfully, but i won't boot. it seems to be the same problem I had before with the stock one. it is way smaller when It is all put back together. around 5 MB instead of 9.
Any ideas why? it appears motorola does not use the standard recovery stuff
lkrasner said:
made a major breakthrough. my internet is down though so I can't really keep working on it or post details, but I should by tomorrow. stay tuned. stupid Comcast.
EDIT: I'm back up. So basically I figured out how to separate the kernel and ramdisk of both our boot and recovery images. it did not work to re-combine them, but it may still be useful for building cyanogenmod to be able to have our straight kernel. PM me if you wan't more detail.
That said, it did not do exactly what I wanted, but I think at this point we should be able to simply build cwm according to the guides for it. I am doing it right now, and it is in the final build process, so I will let you know how it all turns out.
Click to expand...
Click to collapse
Yeah I already have a perl script to do all the separation, but it still puts the kernel into several files, and not just single kernel file with a few separate .ko files.... If you found something that I haven't, then that is awesome.
Here is the script that I use to pull it out of the boot.img:
https://dl.dropbox.com/u/45576654/unpack-bootimg.pl
lkrasner said:
So, I got it built successfully, but i won't boot. it seems to be the same problem I had before with the stock one. it is way smaller when It is all put back together. around 5 MB instead of 9.
Any ideas why? it appears motorola does not use the standard recovery stuff
Click to expand...
Click to collapse
I suspected that might be the case.
jimbridgman said:
I suspected that might be the case.
Click to expand...
Click to collapse
any ideas why.
Sent from my MB865 using xda premium
jimbridgman said:
Yeah I already have a perl script to do all the separation, but it still puts the kernel into several files, and not just single kernel file with a few separate .ko files.... If you found something that I haven't, then that is awesome.
Here is the script that I use to pull it out of the boot.img:
https://dl.dropbox.com/u/45576654/unpack-bootimg.pl
Click to expand...
Click to collapse
mine gave me a ramdisk.cpio.gz and a kernel.gz, I didn't extract that. it was also a pearl script, so probably the same one.
Sent from my MB865 using xda premium
I know I have posted here way to many times. But I want to get this to work.
It seems motorola has done more weird **** to their recovery partitions. Normally you can use certain scripts and binaries to separate a boot or recovery image (they follow the same format) into the ramdisk and kernel. That SHOULD be all that is in them. you can then modify the ramdisk to your liking, or use the kernel with cwm or the like to make it work. However it seems there is more to our image than just the ramdisk and kernel. when I extract them and repack them it seems to work fine, but the result is 5.5MB instead of 9.4MB with no modifications.
Does anyone have any idea what the deal is with that? I think if we can figure out that part we should be able to get a true custom recovery.
P.S. are you sure we cannot replace our boot.img with this same copying method? That is if we could even figure out how to modify it. Is there a hardbrick risk in trying? if so, Any volunteers?
EDIT: so our boot image will unpack and repack to the same exact size, so I think that means we could theoretically edit the ramdisk if that would do any good. the question still remains whether the phone checks its signature on boot or only upon flash
Anyway to test if it checks on boot or flash?
Sent from my MB865 using xda premium
Harrison85 said:
Anyway to test if it checks on boot or flash?
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I can make a small change that would make it un verified then someone could copy it over and see if it boots. the problem is I am not 100% sure we would be able to restore to the original if it would not boot. I am 99% sure we would be fine, but I don't want to risk bricking completely. My guess is jim will know if it is safe to test or even worth trying, but if you want to be the guinea pig just tell me and I'll send you instructions.
By all means throw Me instructions and I will give it a shot right now
Sent from my MB865 using xda premium
Nevermind. I was sort of wrong. Both images separate just fine and can be recombined, but extracting the ramdisk seems to not extract the whole thing, it is much smaller when it is repacked. therefor you cannot really edit it at all.
Any ideas why?? I think it is just Moto being a pain in the ass as usual.
lkrasner said:
Any ideas why?? I think it is just Moto being a pain in the ass as usual.
Click to expand...
Click to collapse
That is it in a nutshell. They pack their boot image in a different way from all other phone manufacturers, and not in a standard way for android. That is why Moto has their own "special" non-standard bootloader. They use a bitblast to package the boot image files, on top of the standard tgz, so the important files are "zip blasted" on top of the others in "superbit blocks", so there is not much we can do, unless we can de-a-line them, but that is not something I even want to start poking at.
I felt this warranted its own thread, and is pertinent to development. So here's to my first thread in the development section!
As you know, the Charge is getting an update to its Gingerbread stock ROM, titled FP5.
I was one of the lucky ones to get it early, so I pulled it out of cache and uploaded it to Dropbox.
So here it is:
http://db.tt/feigCZuH
If you want to try it:
You need to be fully stock before you can use this. This includes being on RFS. Then download, rename to update.zip, place on root of SD, and flash on the stock recovery.
To Root (assuming starting at stock FP5):
Download the CWM flashable root zip, found at http://androidsu.com/superuser/ (its rude of me to hotlink it). Download the whole package for ARM, not just binary (get 3.0.7-efghi-signed). Put it on your SD card.
NOTE: Most of us Charge users have found that SuperSU (Chainfire's replacement for Superuser) is much more stable on this device. I personally recommend SuperSU, but if you want to keep using superuser, it's your call. Installation instructions will be the same, just Google SuperSU and download the zip rather than Superuser.
Then, get the CWM recovery, and flash it via Odin. Uncheck "auto reboot". Unplug your device and boot to CWM, mount /system, then flash the SU zip (I would wipe cache and dalvik just to be safe).
Your device will boot and be rooted, however the CWM recovery will be overwritten. Get root explorer and search for "install-recovery.sh" (in /system/etc) Change permissions, delete, rename, or otherwise maim the script.
Finally, reflash CWM in Odin. Your device will boot and be rooted, with CWM Recovery, with in the stock FP5 ROM. Feel free to debloat to your pleasing.
You want a video tutorial? You're hard to please.
http://youtu.be/DXSmONvpkSQ
the introduction is VERY off sync. Please don't turn the volume up and scare the crap out of yourself. Sorry, I can't make it available on mobile, something about copyright infringement.
I'll be making an Odin next week, since a user requested it. Just have to wait until I get back from vacation... EDIT: Odins are already available. None from me.
Sent from my SCH-I510 using xda premium
I look forward to see how the Tweaked version of FP5 goes & if anything will be of use to dwitherell.
Thanks for posting FP5. :victory:
kvswim said:
I felt this warranted its own thread, and is pertinent to development. So here's to my first thread in the development section!
As you know, the Charge is getting an update to its Gingerbread stock ROM, titled FP5.
I was one of the lucky ones to get it early, so I pulled it out of cache and uploaded it to Dropbox.
So here it is:
http://db.tt/feigCZuH
I have no idea of you need to rename it to update.zip or anything like that, so if someone smarter than me could advise, that would be helpful
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
Thank you so much for uploading this Kvswim! Hopefully the developers can use your update to make an update of their own like Tweaked! :good:
kvswim said:
I have no idea of you need to rename it to update.zip or anything like that, so if someone smarter than me could advise, that would be helpful
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
You do need to rename it to update.zip before you flash it with the stock recovery
kvswim said:
I was one of the lucky ones to get it early, so I pulled it out of cache and uploaded it to Dropbox.
Click to expand...
Click to collapse
Thank you sir, can't wait to try it on my charge when it comes back from samsung...unless they send me back a nexus
has anyone tried it yet? I'm assuming it will work on tweaked 2.x?
I tried to flash it via CWM (before realizing that I needed to rename it to "update.zip"), but got "installation aborted". I did revert back to RFS first though.... I guess I'll try it again...
You most likely have to be full stock to use it.
jco23 said:
has anyone tried it yet? I'm assuming it will work on tweaked 2.x?
I tried to flash it via CWM (before realizing that I needed to rename it to "update.zip"), but got "installation aborted". I did revert back to RFS first though.... I guess I'll try it again...
Click to expand...
Click to collapse
You have to be 100% stock FP1 stock recovery
OK, so first off thanks kvswim for getting this out there so fast
Secondly, I'm out and about for a wee bit, but once I'm back at my computer (mid next week) I'll get to work. I'm not sure how long it'll take, but I always assume it'll take a while.
I would also like to put out a request. The last update I did I went through and updated every theme in tweaktools along the way. That took a LONG time, so I was wondering if there were any interested in assisting the theme update process. This will obviously not be relevant until I have the base all finished up, but if you feel you have some of the necessary know-how and are interested feel free to PM me. Most of the themes were made by folks that no longer have the device, which is why I updated everything last time. If I get a few takers I'll make a thread to keep things all organized as far as who is doing what, that way proper credit can be given to those that lend a hand.
Also, no worries if there is no interest/time to help. I have no issue doing it, it'll just take a bit longer.
Carry on.
I can probably make an Odin of this next week if anyone wants it.
Also dwith, I can't help you at all with the themes, I would need to walk through it at least once first. Never taken apart a theme.
Sent from my SCH-I510 using xda premium
Does this include improved radios? Will there be new radios we could flash before Tweaked gets updated?
Yes, there are radio updates in this. However I can't pull radios only until next week, and even then I'll need someone to help me.
Sent from my SCH-I510 using xda premium
kvswim said:
I can probably make an Odin of this next week if anyone wants it.
Also dwith, I can't help you at all with the themes, I would need to walk through it at least once first. Never taken apart a theme.
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
Yes Odin please.
Sent from my SCH-I535 using xda premium
Cool. I have no problem with waiting. I edited the fingerprint line in build.prop so I won't be hassled by the update. My phone runs fine.
You can only dump the LTE radio, you won't be able to get a dump of the CDMA radio.
imnuts said:
You can only dump the LTE radio, you won't be able to get a dump of the CDMA radio.
Click to expand...
Click to collapse
Is there a new kernel with FP5 & will you update your own kernel fork with it? I found out that http://opensource.samsung.com has FP5 as SCH-I510-VZW_GB_Opensource_Update2.zip available.
I've returned to stock and then taken the OTA and can't seem to keep my root or cwm recovery. sooo im going to have to edit my build prop until there is a root fix for this.
buhlerbuhler said:
I've returned to stock and then taken the OTA and can't seem to keep my root or cwm recovery. sooo im going to have to edit my build prop until there is a root fix for this.
Click to expand...
Click to collapse
There's a certain file that checks if your recovery "needs" to be overwritten by stock, and all you need to do is change permissions on that file. For the life of me I can't remember what it is though.
I would imagine that would help you with your root too.
Sent from my SCH-I510 using xda premium
kvswim said:
There's a certain file that checks if your recovery "needs" to be overwritten by stock, and all you need to do is change permissions on that file. For the life of me I can't remember what it is though.
I would imagine that would help you with your root too.
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
install-recovery.sh
Sent from my SCH-I510 using xda app-developers app
Reilly1812 said:
install-recovery.sh
Sent from my SCH-I510 using xda app-developers app
Click to expand...
Click to collapse
In /system/etc/
I installed paranandroid and gapps but it was the wrong gapps which caused it to error out during install. so now I have the correct gapps on my SD card but do not know how to access it through my phone since I have no recovery. How do I get gapps back on phone so I can get into recovery?
damn....
PHUCK! ok now I'm really freaking out... flashed gapps and says framework as stopped. wont let me past the front screen saying touch android to begin...
1Android said:
PHUCK! ok now I'm really freaking out... flashed gapps and says framework as stopped. wont let me past the front screen saying touch android to begin...
Click to expand...
Click to collapse
OK, don't panic yet! Basic questions first:
Did you flash a recovery like CWM (Clockworkmod) before trying to flash the rom?
Are you able to get into recovery mode via volume up+power+home?
Why dont you reflash the ROM and then do the right Gapps? That way you wont have any screwed up files at all. If you really screwed it up just Odin back to stock and start again.
just flash the rom over the top then flash the right gapps
I went into panic mode and my head went cloudy. I kept olding down volume instead of volume up. Got into recovery and just doing a restore for now till I can make sure I have all the right files...
thanks guys for answering so quickly.
1Android said:
I went into panic mode and my head went cloudy. I kept olding down volume instead of volume up. Got into recovery and just doing a restore for now till I can make sure I have all the right files...
thanks guys for answering so quickly.
Click to expand...
Click to collapse
Good, now when that's done, lets get you up and running with paranoid. It is alot easier, and generally safer to flash through CWM on the phone itself then through odin on your desktop or even the odin app. What method were you using? And more importantly did you do a IMEI backup?
Haven't done the imei backup yet. Need to though asap. I always flash through cwm but once I installed the wrong gapps (didn't even think of grabbing a JB gapps until after I got my phone into recovery and restored) I had no idea how to get into recovery. Once I found the goo manager in system settings I was able to get into recovery. Tried flashing another gapps file (which again was the wrong file) which is where I really freaked out with my framework and setup no working. Was able to clear my head and remember the volume UP not down. I'm restored now and will leave it on synergy till I do my imei backup. Haven't even looked into it to be honest. Is it difficult? Is paranandroid really much better as far as battery life to worry about taking the time to do it?
Sent from my SCH-I535 using xda app-developers app
1Android said:
Haven't done the imei backup yet. Need to though asap. I always flash through cwm but once I installed the wrong gapps (didn't even think of grabbing a JB gapps until after I got my phone into recovery and restored) I had no idea how to get into recovery. Once I found the goo manager in system settings I was able to get into recovery. Tried flashing another gapps file (which again was the wrong file) which is where I really freaked out with my framework and setup no working. Was able to clear my head and remember the volume UP not down. I'm restored now and will leave it on synergy till I do my imei backup. Haven't even looked into it to be honest. Is it difficult? Is paranandroid really much better as far as battery life to worry about taking the time to do it?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
The IMEI is very easy to do, especially if your running Synergy. There are 3 methods in the link I'll attach. The first uses any terminal emulator app (free in play store) and simply typing in a code: su (enter) then: reboot nvbackup (enter)...done! Then there is the next way to create a second easier to install if something were to happen way using a Synergy recovery zip. You must do the first method first or the zip way will backup the wrong IMEI. On the link there is another link to the Synergy Key zip file (its right in the directions with HERE in bold as the link). Download zip, run it in recovery ONCE to create the backup, thats it! The synergy backup can then be used on other roms. Overall its super easy, I spent 2hrs researching and 5 min creating the backup. IT really is as simple as that, just do it in order. As far as paranoid goes, I don't have hands on with it, too many bugs for me to bother with it yet, but yes it generally should use less battery due to JB's unmatched efficiency.
Here's the link: (only need to read the first page for making the backups, read further to restore which hopefully won't be needed!)
http://forum.xda-developers.com/showthread.php?t=1852255
I will look into it tomorrow. Thank you so much for your help!! Very much appreciated.
I need/want a fully functional Rom without a bunch of bugs. Might stay with synergy till some bugs can be worked out.
Sent from my SCH-I535 using xda app-developers app
Is there such thing as a guide like this one but that is up to date and with working links? I want to flash a new ROM onto my phone, but the guides I've found here and elsewhere have broken links, or use language that I don't understand, or skip vital steps. I've been working on this for four hours straight and I haven't gotten a single guide to work, or get stuck, or something else that's really dumb. For someone who has worked on computers for the last 17 years this is extremely frustrating. I'm very new to the android modding scene and apparently it's not just a community, but an entirely different culture and I'm feeling a bit shocked and confused. I have like 30 tabs open with guides, info, different ROMs, different ways to do it, etc and the more I learn the less I understand how to do this :/ I just want to get my phone working with a ROM that's very similar to stock Sense but without the crappy bloatware and memory issues. Miktouch is the one I thought I wanted, but apparently hasn't been updated in almost a year, and bulletproof/doubleshot is confusing. I can't even figure out how to root and get S-Of... Gah!
Please help.
This guide is confusing and skips steps or lacks real explanations.
Thank you.
First thing you want to do is root your phone, this is done by unlocking you bootloader through the HTC dev website. There is a tutorial that is stickyed in the developer section called something like root from any bootloader. I suggest to read that a bit.
Once you followed those steps and unlocked your bootloader you can decide if you want to remove all security flags (highly recommend this, but some find it difficult) in the same guide it explains what radio s-off is and links you to the jbear site to do the wire trick (needs Linux) (or find weekendstoshort for a way to do it in windows)
Feel free to ask more questions but all answers should be found in these xda threads and jbear site, no need to Google anything for this
Sent from my Nexus 4 using xda premium
I hope so...I'll give it another go tomorrow. I'm still quite frustrated at it. I wish I knew someone who had done it and could show me in person.
GiftigDegen said:
I hope so...I'll give it another go tomorrow. I'm still quite frustrated at it. I wish I knew someone who had done it and could show me in person.
Click to expand...
Click to collapse
MikTouch is optimized stock... So updating it farther would take it a direction we wasn't going with it.
Bulletproof is even older. We don't have much here... But what's here is solid
Sent from my Nexus 4 using Tapatalk 4 Beta
First timer here as well (although long time computer user/programming familiar so I might have a better understanding of some things than you) and I was able to fully unlock, S-OFF, and load up a JB rom to my phone using the guide right on this site (http://forum.xda-developers.com/showthread.php?t=1801106) and some help from some online friends that have done this kind of thing before. I found all links to be working, and pretty much all steps to be covered. The I guess hardest part was the permanent S-OFF using the wire trick. I had to burn an Ubuntu live cd and boot a laptop with it, but I was even able to get that step done. A little frustrating with the timing, I think it took me about 8 tries until it finally unlocked. The only thing I think I initially missed was wiping all 3 caches, so I did a dirty flash that got stuck on the boot screen. After I wiped and loaded again, no problems. If you'd like any additional help, I get pretty bored at work, so find me on aim or gchat, or just shoot me a PM here, I think I should get notified
Good luck, it's not as bad as I thought it would be
Also I haven't personally tried it, but feel free to peruse this thread as well: http://forum.xda-developers.com/showthread.php?t=1696373
Note you'll need to have already achieved HTCDev unlocked and be rooted to use this (covered in that first link)
Hope that helps!
PsychoPhreak said:
First timer here as well (although long time computer user/programming familiar so I might have a better understanding of some things than you) and I was able to fully unlock, S-OFF, and load up a JB rom to my phone using the guide right on this site (http://forum.xda-developers.com/showthread.php?t=1801106) and some help from some online friends that have done this kind of thing before. I found all links to be working, and pretty much all steps to be covered. The I guess hardest part was the permanent S-OFF using the wire trick. I had to burn an Ubuntu live cd and boot a laptop with it, but I was even able to get that step done. A little frustrating with the timing, I think it took me about 8 tries until it finally unlocked. The only thing I think I initially missed was wiping all 3 caches, so I did a dirty flash that got stuck on the boot screen. After I wiped and loaded again, no problems. If you'd like any additional help, I get pretty bored at work, so find me on aim or gchat, or just shoot me a PM here, I think I should get notified
Good luck, it's not as bad as I thought it would be
Also I haven't personally tried it, but feel free to peruse this thread as well: http://forum.xda-developers.com/showthread.php?t=1696373
Note you'll need to have already achieved HTCDev unlocked and be rooted to use this (covered in that first link)
Hope that helps!
Click to expand...
Click to collapse
I'm following the first guide you linked. So far it's working I just flashed CWmod on and I loaded it according to the instructions in the guide "After fastboot finishes, disconnect your MT4GS, go into bootloader, and go to “RECOVERY.” You should now be in ClockworkMod Recovery 5.0.2.7. The first thing I would do in CWM Recovery is make a backup of your stock ROM for safe keeping. "
But I forgot to d/c my phone. It still loaded CWmod and I navigated to backup/restore and clicked it. Right now my phone has the clockwork logo in the middle but it didn't give me any prompts after selecting backup/restore. What's it doing? It's been doing this for like 5 minutes. Should I be worried that I forgot to d/c the cable and whatnot?
Thanks
GiftigDegen said:
I'm following the first guide you linked. So far it's working I just flashed CWmod on and I loaded it according to the instructions in the guide "After fastboot finishes, disconnect your MT4GS, go into bootloader, and go to “RECOVERY.” You should now be in ClockworkMod Recovery 5.0.2.7. The first thing I would do in CWM Recovery is make a backup of your stock ROM for safe keeping. "
But I forgot to d/c my phone. It still loaded CWmod and I navigated to backup/restore and clicked it. Right now my phone has the clockwork logo in the middle but it didn't give me any prompts after selecting backup/restore. What's it doing? It's been doing this for like 5 minutes. Should I be worried that I forgot to d/c the cable and whatnot?
Thanks
Click to expand...
Click to collapse
I wouldn't worry, and I'm not entirely sure what it's trying to do, perhaps the possibility of USB storage is throwing it off. At this point I'd say just try to disconnect it, pull the battery, and start back up into recovery, but without the USB attached this time. I imagine then you'll be fine and able to backup the stock image like they say for safe keeping.
One more dummy question (tech support for many years, always check the simple stuff first...) you do have SOME SD card in there right?
PsychoPhreak said:
I wouldn't worry, and I'm not entirely sure what it's trying to do, perhaps the possibility of USB storage is throwing it off. At this point I'd say just try to disconnect it, pull the battery, and start back up into recovery, but without the USB attached this time. I imagine then you'll be fine and able to backup the stock image like they say for safe keeping.
One more dummy question (tech support for many years, always check the simple stuff first...) you do have SOME SD card in there right?
Click to expand...
Click to collapse
Yeah, 32gb =)
booted into recovery, clicked on bacup/restore...still just showing the logo in the middle.
(PS any mods out there listening, I'd love to have that 5 minute restriction removed =D )
Okay, so the select button changes from power to the scroll pad once in recovery...good to know.
GiftigDegen said:
booted into recovery, clicked on bacup/restore...still just showing the logo in the middle.
(PS any mods out there listening, I'd love to have that 5 minute restriction removed =D )
Okay, so the select button changes from power to the scroll pad once in recovery...good to know.
Click to expand...
Click to collapse
NVMD....You got it now.
strapped365 said:
MikTouch is optimized stock... So updating it farther would take it a direction we wasn't going with it.
Bulletproof is even older. We don't have much here... But what's here is solid
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Using CWM to flash Miktouch now. Hopefully it works... =D
Just remember, if you are "S-On" you're going to need to fastboot flash boot boot.img after your ROM is thru flashing or you will hang up at the boot animation.
strapped365 said:
MikTouch is optimized stock... So updating it farther would take it a direction we wasn't going with it.
Bulletproof is even older. We don't have much here... But what's here is solid
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
K. First impressions:
When I restart the phone, the first thing it does is force stop Gmail and Youtube several times. Is this supposed to happen?
Also, I'm extremely impressed with the speed of the restart. It's at LEAST twice as fast as stock.
And, Genius button doesn't work even after installing the patch linked to on your website (universal.zip).
WeekendsR2Short said:
Just remember, if you are "S-On" you're going to need to fastboot flash boot boot.img after your ROM is thru flashing or you will hang up at the boot animation.
Click to expand...
Click to collapse
Thanks Weekends. I did that and it's installed, though I fastboot flash boot boot.img before I used CWM to flash the rom. Does that make a difference? Do you think doing it that way will fix the force close mentioned above?
If there's not a fix for the gmail/youtube force closes, is it possible to do bulletproof with s-on? Thoughts? I really want to stick as close to stock MT4GS but with as solid a system as possible.
Flashing boot image before ROM will overwrite kernel
Wipe all
Flash ROM
Flash boot
Reboot
Sent from my Nexus 4 using xda premium
demkantor said:
Flashing boot image before ROM will overwrite kernel
Wipe all
Flash ROM
Flash boot
Reboot
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Another noob question. How do I wipe all?
Also, when I use CWM to install Mikrom it atuo restarts and loads up. Then do I restart again and go fastboot the new kernal?
Thank you all for how much help you have given me.
At the end of the updater-script there must be a reboot command, but being this ROM is based of stock you may not need to flash the kernel anyway.
Best methods for wiping is one of bluex's superwipe scripts or with fastboot
fastboot erase system -w
But being you are s-on that command may fail.
But always do a wipe data/factory reset, wipe cache, and wipe dalvik in recovery.
It also good practice to make a nandroid of current ROM before you flash anything
Sent from my Nexus 4 using xda premium
demkantor said:
At the end of the updater-script there must be a reboot command, but being this ROM is based of stock you may not need to flash the kernel anyway.
Best methods for wiping is one of bluex's superwipe scripts or with fastboot
fastboot erase system -w
But being you are s-on that command may fail.
But always do a wipe data/factory reset, wipe cache, and wipe dalvik in recovery.
It also good practice to make a nandroid of current ROM before you flash anything
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Mmkay, working doing this now.
Quick question, hopefully someone can give me a link, but I'd love the install the depaginated app drawer, genius fix and menu wake up mods for this, but the links are broken (dev-host times out). Any help?
See weekends mirror thread
Sent from my Nexus 4 using xda premium