Database Info

CM7 rc1

Quick question guys... I was reading that cm7 RC 1 can be installed by only rooting your phone and then using rom manager. Is this true or are there other steps required? I know there used to be other things that needed to be done but maybe with the new RC is got easier?
Thanks for the help
Sent from my LG-P999 using XDA App

phantasybm said:
Quick question guys... I was reading that cm7 RC 1 can be installed by only rooting your phone and then using rom manager. Is this true or are there other steps required? I know there used to be other things that needed to be done but maybe with the new RC is got easier?
Thanks for the help
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Well, even though you could do it with only ROM manager and root it is highly recommended that you flash CWM recovery just in case anything goes bad you can always bring the recovery and reflash or restore.
Sent From My Stock G2x

^^^^^ agreed. The plain-jane method of rooting/RomManager/CWM works but if something happens where you can't get into RomManager (aka bootloop) then your SOL.
Do yourself a favor and spend 3 seconds and NVFlash. You only have to do it once and you will be forever able to save your skin if something goes bad.

Thanks guys.
So I root first (already done), NVFlash (done some reading but still not 100% sure what exactly this does or how to do it) and then set up cement recovery?
Sent from my LG-P999 using XDA App

I haven't used the rom manager app once on the g2x.
G2x with CM7 and faux kernel. NONSENSE!!!!

tackleberry said:
I haven't used the rom manager app once on the g2x.
G2x with CM7 and faux kernel. NONSENSE!!!!
Click to expand...
Click to collapse
me neither, lol and to the other guy nvflash u want because say your phone goes into a bootloop what u gonna do? u cant do nothing but pull battery out then when u turn your phone on it just keeps bootlooping not letting u into the phone ever, well thats what would happen if u got a bad download or flashed the wrong thing by accident , dude accidents do happen, rom manager is what they call a fake flash, ..........now nvflash really puts recovery on your phone it over writes your stock recovery, and if your going into a bootloop u can pull battery put back in then hold vol down and power and bingo your in recovery, it looks the same as rom managers recovery, but with this one u can actually get into it and if your bootlooping u would just restore a nandroid or reflash another rom and your good, ....kinda a failsafe i live by it and dont use rom manager , and if u want to see your backups and rename them use astro zip in market its free too

sarni84 said:
....kinda a failsafe i live by it and dont use rom manager,
Click to expand...
Click to collapse
That is all you need to know... NVflash is the only way to go if you absolutely want to be sure you can save your phone...
I don't know why people question that...
Sent from my butt using XDA Premium App

http://forum.xda-developers.com/showthread.php?t=1054492
How to setup and use NVflash.
Thanks for the heads up. I was just about to dive in with Rom Manager alone. REALLY don't need new problems.

According to Cyanogenmod's wiki you can flash recovery from ROM Manager, it says nothing about this NVFlash. I did this and rebooted into Clockwork and flashed CM7 RC1, and now I can't get back into Clockwork, just the default one, and ROM Manager can't execute anything, I can't connect to wifi and, I get various Force Close messages at start up. So is the wiki lying to me?

Do NOT question nvflash! You need this... nvflash makes the clockwork recovery permanent.. If you only flash through rom manager it only makes the recovery temporary and the next time you reboot you will lose recovery
Sent from my LG-P999 using XDA App

jonnyboyca said:
Do NOT question nvflash! You need this... nvflash makes the clockwork recovery permanent.. If you only flash through rom manager it only makes the recovery temporary and the next time you reboot you will lose recovery
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
It made a huge difference. Things are running much more smoothly now that I used nvflash and reinstalled CM7.1-RC1.

Awesome enjoy
Sent from my LG-P999 using XDA App

jonnyboyca said:
Do NOT question nvflash! You need this... nvflash makes the clockwork recovery permanent.. If you only flash through rom manager it only makes the recovery temporary and the next time you reboot you will lose recovery
Click to expand...
Click to collapse
It's almost like people don't read the threads about rooting. Every one that I read said, in no uncertain terms, you NEED to use NVflash if you want permanent root....
Sent from my butt using XDA Premium App

The thing is there is incomplete information all over the place and it changes constantly, and it's difficult to keep up on what is needed or not. Cyanogen's wiki doesn't say it's needed, and I figured that meant the problems with ROM Manager and Clockwork had been resolved in the most recent versions.

jonnyboyca said:
Do NOT question nvflash! You need this... nvflash makes the clockwork recovery permanent.. If you only flash through rom manager it only makes the recovery temporary and the next time you reboot you will lose recovery
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Same **** I said in cm7 rrc thread. Yet I get laughed at and ridiculed.
U arr correct
Sent from my LG-P999 using Tapatalk

KeithLM said:
The thing is there is incomplete information all over the place and it changes constantly, and it's difficult to keep up on what is needed or not. Cyanogen's wiki doesn't say it's needed, and I figured that meant the problems with ROM Manager and Clockwork had been resolved in the most recent versions.
Click to expand...
Click to collapse
That's why I advocate, when in doubt, research some more. I didn't get the feeling that info was incomplete, everything I read said nvflash for permanent root and you can bet that the threads where people were asking for help because they were in a bootloop the first question asked was did you use nvflash... maybe cyanogen just figured that everyone already got recovery with nvflash, because you should have, and THEN it is safe to use RM...
Sent from my butt using XDA Premium App

[q] do not use rom manager - help!

I read the posts, but maybe I did not understand?
I downloaded CWM and installed via the Android Market. Then I see the icon is named ROM Manager (whoops, is this already bad). I hit the "Flash ClockworkMod Recovery" button. Then I used up/down volume and power to boot into CWM and did a backup from there.
So am I screwed?
Is the backup good?
Can I use the CWM that I have as long as I boot into it?
Please, I have not been able to understand exactly what the "DO NOT USE ROM MANAGER" means. If I just boot is that ok?
I guess you can tell I'm new but I have a lot of software experience - just not in this environment - maybe I'm moving too fast for my knowledge (I think so now!).
AT&T Galaxy S II Skyrocket, SGH-i727, 2.3.5

Funny, I just posted a very similar question just minutes before you in the FAQ thread.
Huge red letters "dont use Rom Manager!" but the first step for every rom or kernal seems to be "boot into cwm..."
I'm sure someone will point out how dim we are soon.

rhtufts said:
Funny, I just posted a very similar question just minutes before you in the FAQ thread.
Huge red letters "dont use Rom Manager!" but the first step for every rom or kernal seems to be "boot into cwm..."
I'm sure someone will point out how dim we are soon.
Click to expand...
Click to collapse
Now would be a good time to read:
http://forum.xda-developers.com/showthread.php?t=1311081
As you can see, CWM is included in the kernel you flash, and thus there is no need for ROM manager. It doesn't play nice with this device anyway, and is just unnecessary imo.

Use the recovery not rom manager itself...
Sent from my SAMSUNG-SGH-I777 using XDA App

rcklss1 said:
Use the recovery not rom manager itself...
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
So the OP is fine if he uninstalls Rom Manger even though he used it to flash CWM Recover? That seems a lot simpler then the cwm injected kernal method I just did.
Install rom manger, flash CWM, uninstall rom manger... flash roms all day. Would that work?

rhtufts said:
So the OP is fine if he uninstalls Rom Manger even though he used it to flash CWM Recover? That seems a lot simpler then the cwm injected kernal method I just did.
Install rom manger, flash CWM, uninstall rom manger... flash roms all day. Would that work?
Click to expand...
Click to collapse
No.
What part of "Don't use rom manager" don't you understand?

rhtufts said:
Funny, I just posted a very similar question just minutes before you in the FAQ thread.
Huge red letters "dont use Rom Manager!" but the first step for every rom or kernal seems to be "boot into cwm..."
I'm sure someone will point out how dim we are soon.
Click to expand...
Click to collapse
ROM MANAGER IS NOT CWM.
CWM is in the KERNEL (well, to be specific, in the initramfs of the kernel) on nearly all Samsung devices.
ROM Manager is an app that tries to install CWM, but FAILS to do so correctly on our device. CWM versions installed by ROM Manager DO NOT WORK PROPERLY on the I777.

ok heres the deal the cwm you booted into was probably rom manager cwm. so here are the next steps to take. question is are you using a custom kernel that has cwm installed? when you rooted your device did you have cwm installed? i also noticed you were using a skyrocket. when i rooted my wifes SR I did the all in one package. My opinion is just unistall rom manager and reflash cwm. then reboot into cwm and make a nandroid backup. although in theory your backup you did with rom manager is good forever unless you delete the file under /clockworkmod/backup.
miui+siyah = beast

OP, if you ****ed up probably the easiest step of the process(after all in one of the stickies it says DO NOT USE ROM MANAGER, as so), rooting your phone is not for you.
Either that or you're trolling.

bgraves said:
AT&T Galaxy S II Skyrocket, SGH-i727, 2.3.5
Click to expand...
Click to collapse
*kicks to the Skyrocket forums*

Red5 said:
*kicks to the Skyrocket forums*
Click to expand...
Click to collapse
Reading through this made me confused. But to the OP. Mod Manager is fine. You can use that to install CWM recovery. Just be sure to chose the T-Mobile SGSII version of CWM when it asks.
DO NOT USE ANY OF THE ROMS IN MOD MANAGER THOUGH. They are built for the SGSII phones. You can however use Rom Manager for all other options such as installing roms through SD, fixing permissions, and booting up into CWM, etc.

stevehkim said:
question is are you using a custom kernel that has cwm installed? when you rooted your device did you have cwm installed? i also noticed you were using a skyrocket. when i rooted my wifes SR I did the all in one package. My opinion is just unistall rom manager and reflash cwm. then reboot into cwm and make a nandroid backup. although in theory your backup you did with rom manager is good forever unless you delete the file under /clockworkmod/backup.
miui+siyah = beast
Click to expand...
Click to collapse
Using the stock kernel. I rooted with DooMLoRD_v3_ROOT-zergRush-busybox-su. So I can do the uninstall and then reflash CWM. Do you have a URL handy for the reflash? Don't want to make another error.
and thanks, your reply is very helpful.

creepyncrawly said:
No.
What part of "Don't use rom manager" don't you understand?
Click to expand...
Click to collapse
Probably the part about what else he's supposed to do. If I knew, I'd tell him. I assume he should read the whole thread in dev about how to get CWM installed through recovery but I'm just a novice. You might have been more helpful but I see that a lot of you are too busy hanging out in in dark closets having sex with your phones... tin foil hats and all. I know it's a pain answering the same questions over and over. I've provided support on a lot of boards and on a lot of subjects. When I got tired of typing the same answers, I started keeping them all in a text file so I could copy and paste them, links and all. That way, the info is spread all over the place and new users don't have to resort to finding the single "needle in the haystack." I know the L33T (do they still use that term? It's been about 20 years since i've seen it... probably for the good) love to repeatedly type "DO A SEARCH." Why not just help. If you don't want to and only want to maintain being L33T... do it elsewhere. You serve no function other than stroking yourself. I hate the "slam the noob" mentality. We were all one at some point. Merry Christmas.

The confusion here is that the OP posted this in the i777 forum. The i777 CANNOT use Rom manager to flash recovery and they have to use a cwm injected kernel.
The OP needs to learn where to read about his phone and remember what model he has.
Sent from my HTC PH39100

[RECOVERY] ClockWorkMod Recovery [Updated 7/22/12 - New Info]

EDIT: Koush is working hard on compiling CWM6 for all the newer devices. He already has a working version for the international S3 up so we should be looking at getting it here shortly. Notable differences, 720p support. Once it is official for us I will post it. If it is fully functional I will remove everything except my port, and the stock option that way people are not confused, but can still have some preference if need be.
Edit 2: When pushing a new recovery do it TWICE before using. I know mine works fine. My version should display as v.5.8.4.5
Edit 3: ROM Manager does NOT work with any recovery except the official recovery by Koush. You CAN boot into recovery via ROM Manger on the others, but that is it.
I am not responsible for your newly formed brick! I am also not an ADB expert, please search if you need help! ROM Manager DOES work with this version, you must install recovery manually first, then use ROM Manager to boot into recovery. Since we don't have any custom ROM's yet I can't say it works to install them.
Use whatever method you are comfortable with to push this, be it ADB or Terminal Emulator. CWM Standard can be installed via ROM Manager. The direct link for the Touch version is posted below to avoid purchase costs. Not superseding paying, Koush specified that pushing the recovery manually is free of charge.
Terminal Emulator commands: (Thanks - pdinphx)
Remember to change the name of the recovery, OR change the command line to reflect the name of the recovery! (Replace recovery.img with the appropriate img file name.)
$ su
# dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
# reboot recovery
Click to expand...
Click to collapse
Lastly, DO NOT donate to me for this, PERIOD. This is none of my work, all I did was push a couple buttons.
Credit: Koush for Recovery Builder (and for the Official Sprint Version)
Samsung for everything essentially
And everyone who made a tutorial for Terminal Emulator and/or ADB that people might be using.
All Recoveries:
Touch - My CWR Touch Port
Stock Recovery - from Sammy's update (this is the stock Android recovery)
CWM Recovery Official Standard: http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.8.4.9-d2vzw.img
CWM Recovery Official d2spr Touch http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.4.9-d2spr.img

How would this work if we use recovery for custom kernels?

Let me figure out one thing at a time, lol. I am a newb dev. I know almost nothing about custom kernels aside from how to flash them on a device with an unlocked bootloader.

AtLemacks said:
Placeholder.
I am currently using the Recovery Builder Koush made for CWR. If anyone beats me to the punch, let me know because we don't need a thousand different CWR versions. I planned on building a touch version.
Click to expand...
Click to collapse
good luck with this, i've tried several recovery.img's on his builder site
none of them worked for me
since he doesn't have source (i still dont understand why) it might be a bit
do we have twrp for this?

I don't think we have any recoveries aside from the one you ported. You input the image from the update tar?

AtLemacks said:
I don't think we have any recoveries aside from the one you ported. You input the image from the update tar?
Click to expand...
Click to collapse
i didn't port that recovery, its the exact one from the e4gt team
i tried using the one from the stock image (in the sticky on this forum)
i think we might have better luck (although more work) getting TWRP going on this
we have source code with that, plus it has more features

True... Is anyone from TWRP getting the phone?
Took nearly 10 minutes but I got a recovery output img from the builder. I am about to jump off here really quickly though, I have to be up at 4:30am. I'll PM you the img and you can take a look.

invisiblek said:
i didn't port that recovery, its the exact one from the e4gt team
i tried using the one from the stock image (in the sticky on this forum)
i think we might have better luck (although more work) getting TWRP going on this
we have source code with that, plus it has more features
Click to expand...
Click to collapse
Just used TWRP today for the first time on my Prime. I really like it and was hoping it would come to this. My vote goes to TWRP. I'm no good with dev work but can try and help out if needed. I'm a good tester lol

Haro912 said:
Just used TWRP today for the first time on my Prime. I really like it and was hoping it would come to this. My vote goes to TWRP. I'm no good with dev work but can try and help out if needed. I'm a good tester lol
Click to expand...
Click to collapse
In my experience, never test what a dev wont test, lol. I'll gladly brick my phone as I have backups. I wouldn't push something I am not sure about onto you.

Just in case votes are being counted <wink> I vote TWRP.
Sent through mental telepathy...or my G-Nex

AtLemacks said:
In my experience, never test what a dev wont test, lol. I'll gladly brick my phone as I have backups. I wouldn't push something I am not sure about onto you.
Click to expand...
Click to collapse
If the dev won't put on it a phone they own then it won't go on mine. But if they have it and aren't having issues then I will test and see if I get any. 2 people never use their hone the same way.

http://goo.im/devs/birdman/twrp8.img
Sent from my r00ted SCH-I535 using Tapatalk 2

Mean Sixteen said:
Just in case votes are being counted <wink> I vote TWRP.
Sent through mental telepathy...or my G-Nex
Click to expand...
Click to collapse
I second this. I have never liked CWM. Rather have Amon Ra but this isn't an HTC phone. Lol.
Sent from my ADR6425LVW using xda app-developers app

For all you that like TWRP!! Here you go!​

Woo Hoo. Now if I could only make it Tuesday NOW so I could root mine and install TWRP.
Can't wait and I am guessing I will be able to flash a custom kernel by then.
Sent through Mental Telepathy...or my TF201

For those potentially still interested I will try to work on this more tonight and test it out. I had to work 5 hours late due to a big fire/hazmat call at a factory out here. I smell like peppermint now because it was a potpourri fragrance plant -_-... Post progress of my testing later.

appdroid said:
For all you that like TWRP!! Here you go!​
Click to expand...
Click to collapse
Can't wait to flash this tomorrow.
Sent from my Ally using XDA

NightxFall said:
Can't wait to flash this tomorrow.
Sent from my Ally using XDA
Click to expand...
Click to collapse
flash it just like cwm in the root thread
i'm going to update the thread on that too, thanks for reminding me

invisiblek said:
flash it just like cwm in the root thread
i'm going to update the thread on that too, thanks for reminding me
Click to expand...
Click to collapse
anybody have any luck with TWRP seeing internal sd contents?
**edit** or cwm for that matter?

Nope, testing right now finally. No luck even booting.

CWM backups show wrong date

Does anyone know why? Its done this since I first rooted and did my first back up.
Sent from my SCH-I535 using xda app-developers app

same here. i think thats just how CWM works.

ddurandSGS3 said:
same here. i think thats just how CWM works.
Click to expand...
Click to collapse
Hmmm. Its only ever done it on my s III. Never did it on my og evo or HTC sensation. Maybe its the version of cwm. Is there an updated one? I have version 6.0.1.2 I know there's a touch version but I heard it was buggy.
Sent from my SCH-I535 using xda app-developers app

There is a bug in the RTC software for this phone. Until that but gets fixed (would have to be by Samsung or VZW) this isnt going to change.

Yeah it sucks but just rename your backups after they are done
Hit me up on Gtalk if u need help @musclehead84

musclehead84 said:
Yeah it sucks but just rename your backups after they are done
Hit me up on Gtalk if u need help @musclehead84
Click to expand...
Click to collapse
I believe if you rename the backup then you will have to remake the MD5 for that backup, which isnt really a big deal. Just wanted to toss that out there.

apacseven said:
I believe if you rename the backup then you will have to remake the MD5 for that backup, which isnt really a big deal. Just wanted to toss that out there.
Click to expand...
Click to collapse
i keep 2 renamed nandroids that i restore regularly and run them without any issues.

apacseven said:
I believe if you rename the backup then you will have to remake the MD5 for that backup, which isnt really a big deal. Just wanted to toss that out there.
Click to expand...
Click to collapse
U can rename them as long as u don't use special characters.
Sent from my SCH-I535 using xda premium

Install rom manager from the market and flash the latest recovery through that. Walla, they're back to normal. Only fixable by Samsung or vzw? Wtf do people get this stuff? This question gets asked every other day and there are STILL people who think its some unsolvable bug.

Imatoasta said:
Install rom manager from the market and flash the latest recovery through that. Walla, they're back to normal. Only fixable by Samsung or vzw? Wtf do people get this stuff? This question gets asked every other day and there are STILL people who think its some unsolvable bug.
Click to expand...
Click to collapse
That's the first I've heard this. I have the latest cwm touch and wrong dates show. Actually I keep seeing people use RM and the recovery isn't flashing right.
Sent from my S3 running Eclipse 2.1

same me
Same me as well,:crying:

I thought that was normal since those numbers are no where near a type of date, I just rename it once booted into ROM.
Sent from my SCH-I535 using XDA Premium App

i suffering same issue too

Imatoasta said:
Install rom manager from the market and flash the latest recovery through that. Walla, they're back to normal. Only fixable by Samsung or vzw? Wtf do people get this stuff? This question gets asked every other day and there are STILL people who think its some unsolvable bug.
Click to expand...
Click to collapse
This is not true. I dl'd my CWM thru RM and my dates are still wrong. Where do u get this stuff?

Imatoasta said:
Install rom manager from the market and flash the latest recovery through that. Walla, they're back to normal. Only fixable by Samsung or vzw? Wtf do people get this stuff? This question gets asked every other day and there are STILL people who think its some unsolvable bug.
Click to expand...
Click to collapse
That's incorrect. The date issue is still there regardless of how it's flashed in. Some people have reported issues with restoring after renaming. Consensus seams to be if you keep the default cwm assigned name and add your own to the end of it without any spaces, any reported issues dissappear.
Boom! Jellybomb biatch!

annoying for sure. I just rename the moment I am done and booted back up.

TWRP date is also wrong but you can rename them anything you want at time backup. :laugh:

The guy meant backup FROM RM, it allows you to rename the backup file before it gets created, then reboots into recovery and creates the backup.
please try to search for your problem before posting... I'm typically the last to complain about that, but geez us...

Seirÿu said:
The guy meant backup FROM RM, it allows you to rename the backup file before it gets created, then reboots into recovery and creates the backup.
please try to search for your problem before posting... I'm typically the last to complain about that, but geez us...
Click to expand...
Click to collapse
TWRP does everything rom manager does except download roms which have been seen to cause bricks. Backups are named before creation also but already booted into recovery. One stop shop. Easier wipe.

prdog1 said:
TWRP does everything rom manager does except download roms which have been seen to cause bricks. Backups are named before creation also but already booted into recovery. One stop shop. Easier wipe.
Click to expand...
Click to collapse
I got to jump on that one of these days to see what all the fuss is about, I'm just loving cwm touch too much! I assume when changing, your existing nandroids will become useless, so would make sense to copy onto your cpu incase they are needed down the road...?
Boom! Jellybomb biatch!

Working custom kernel(s) for Motorola Updated system?

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