Database Info

[REQUEST] Need Help Fixing Clockwork Recovery

I've seen a couple threads that Clockwork is wiping Wimax on newer phones or hboot? Can someone please explain the problem to me so I can fix it and Unrevoked works again?

Koush said:
I've seen a couple threads that Clockwork is wiping Wimax on newer phones or hboot? Can someone please explain the problem to me so I can fix it and Unrevoked works again?
Click to expand...
Click to collapse
Hi Koush, I'm sure someone else can chime in on the specifics of unrevoked with the new hboot.. as far as I know unrevoked just doesn't work on hboot 2.02 yet.
As a slight aside if you're going to be updating CWM, the two main issues with clockwork right now IMO are:
1) Wimax partition is not backed up when you do a nandroid
2) Seems to be some inconsistencies with wiping dalvik and possible cache
Hope those things can be fixed so that we can go back to using CWM!

I also noticed yesterday that CWR says signatures are invalid that ARR verifies without any trouble.

posguy99 said:
I also noticed yesterday that CWR says signatures are invalid that ARR verifies without any trouble.
Click to expand...
Click to collapse
You can turn off signature checking in CWR. ARR is using the old Cupcake/Donut sig checking which has a few security bugs in it.

bump... 10chars

I have had the problem, I am not able to use 4g any more since last update I did with Clockworkmod.
Let me know what you would like me to do to help you out.

The only changes I need done to Clockwork recovery is to get some sort of confirmation with wiping dalvik cache and battery stat.
I like Clockwork the way it is as far as not touching with Wimax at all. I have more problem with 4g connecting when restoring nandroid with other recovery that suppose to backup wimax partition.
I have never had a problem with my 4G once I go back to Clockwork recovery. Easy way for me to fixed my 4G again was to repeat Toast method number 2 and just use Clockwork recovery that don't touch the wimax.

Koush said:
I've seen a couple threads that Clockwork is wiping Wimax on newer phones or hboot? Can someone please explain the problem to me so I can fix it and Unrevoked works again?
Click to expand...
Click to collapse
Koush....
As one of the devs that actully helped find the issues I will point you to the thread that discusses the problem
http://forum.xda-developers.com/showthread.php?t=843342
However it will not fix unrevoked not working on the new evos. But It would be nice to have recovery options again.
thanks for your help...

Another issue is apparently that the wimax secure keys are not backed up in the CW nandroid. So if something goes awry you cannot restore them. Apparently the alternative recovery does backup the keys.
Sent from my PC36100 using Tapatalk

Koush said:
I've seen a couple threads that Clockwork is wiping Wimax on newer phones or hboot? Can someone please explain the problem to me so I can fix it and Unrevoked works again?
Click to expand...
Click to collapse
Anything in the works? Just curious...

Koush - this isn't related to the 4G - but it's been an ongoing problem that we have with wiping dalvik and cache. I have physically checked via ADB after choosing to wipe dalvik (/data/dalvik-cache) and it's still there. After a few times of wiping it finally works.

The issue seems to be that with new hboots (2.02/2.10) on the Evo that partition information has changed.
I'm still running cwm though and for me it's OK, I'm on hw v003, hboot 2.10 - I think the issue might be with 004 models.

thefredelement said:
The issue seems to be that with new hboots (2.02/2.10) on the Evo that partition information has changed.
I'm still running cwm though and for me it's OK, I'm on hw v003, hboot 2.10 - I think the issue might be with 004 models.
Click to expand...
Click to collapse
+1 it is the partitions, not all new phones come with the new partition set up though. The new hboots are backward compatible but you can't use the new phones with the old hboots.
Swapping out the kernel with the new recoveries kernel should do the trick (i think)
Sent from my PC36100 using XDA App

Miss using CWM, so I'm hoping this gets resolved soon!

http://pastebin.chiznillen.net//view.php?id=19
Koush that's from my hboot 2.10 Evo.
This is from a .97 hboot:
http://pastebin.chiznillen.net//view.php?id=20
Cheers.

Here's a post with partition info from newer Evos (late hardware version 003 and 004 that came with hboot 2.02+)
http://forum.xda-developers.com/showthread.php?t=883636

I've not run into the cache wiping issues but then I have an older EVO so I may just be hardware blessed.
The only concern for me is the 4G RSA keys. I like that generally it's not touched, but an advanced option for the occasional backup would be very welcome (especially with a beta WIMAX in CM6 just around the corner).

Justin.G11 said:
I've not run into the cache wiping issues but then I have an older EVO so I may just be hardware blessed.
The only concern for me is the 4G RSA keys. I like that generally it's not touched, but an advanced option for the occasional backup would be very welcome (especially with a beta WIMAX in CM6 just around the corner).
Click to expand...
Click to collapse
for this I hopped over to RA and just did a nandroid and saved the wimax image on my computer then gmailed it to myself.

thefredelement said:
for this I hopped over to RA and just did a nandroid and saved the wimax image on my computer then gmailed it to myself.
Click to expand...
Click to collapse
Smart option!!
although adding it to clockwork would still be awesome.

leenypost said:
Smart option!!
although adding it to clockwork would still be awesome.
Click to expand...
Click to collapse
I agree, I think primarily though cwm has to be setup for the new partitions on 003/004 phones that shipped with hboot 2.02+.

[Recovery][2011/06/11] Latest Unofficial ClockworkMod (4.0.0.2)

This is the latest ClockworkMod 4.x Recovery image for the CDMA Hero. I compiled it myself using the code from the CyanogenMod repository. While I don't specifically know of any reason it should be considered unstable, you should realize this is built from bleeding-edge code.
Do NOT flash this if you don't know what it is or what you're doing. You should have a working knowledge of how to get back to a stable recovery through the bootloader if something goes wrong. You have been warned.
Download
Pulled for the time being until the nandroid issue is fixed.​
Other Links
ClockworkMod source code
GPL kernel source code
My Android downloads​

jasonmaloney said:
This is the latest ClockworkMod 3.x Recovery image for the CDMA Hero. I compiled it myself using the code from the CyanogenMod repository. While I don't specifically know of any reason it should be considered unstable, you should realize this is built from bleeding-edge code.
Do NOT flash this if you don't know what it is or what you're doing. You should have a working knowledge of how to get back to a stable recovery through the bootloader if something goes wrong. You have been warned.
Download
> recovery-clockwork-3.0.1.4-heroc.img
> GPL kernel source
PS: it boots at 691
Click to expand...
Click to collapse
any chance of getting this as a HERCIMG.zip?

jasonmaloney said:
This is the latest ClockworkMod 3.x Recovery image for the CDMA Hero. I compiled it myself using the code from the CyanogenMod repository. While I don't specifically know of any reason it should be considered unstable, you should realize this is built from bleeding-edge code.
Do NOT flash this if you don't know what it is or what you're doing. You should have a working knowledge of how to get back to a stable recovery through the bootloader if something goes wrong. You have been warned.
Download
> recovery-clockwork-3.0.1.4-heroc.img
> GPL kernel source
PS: it boots at 691
Click to expand...
Click to collapse
Nice work. I had thought about building this and modifying where the confirm_format string gets passed to confirm_selection to show the mount point being formatted. This would help to avoid accidentally formatting the wrong partition by rolling down one when you are making your selection. This only happened to me once, but it was a major pita. I was fortunate to have a recent backup.
Does this include building the mount and storage menu from fstab (Change I92796ec9)?

Whoa. Very nice. I've downgraded to 2.5 since 3.0 couldn't flash some zip files. Does this one correct that?

oohaylima said:
Whoa. Very nice. I've downgraded to 2.5 since 3.0 couldn't flash some zip files. Does this one correct that?
Click to expand...
Click to collapse
+1 Does this handle both scripting codes. Edify and amend, if so that would be great.
Sent from my HERO200 using XDA App

oohaylima said:
Whoa. Very nice. I've downgraded to 2.5 since 3.0 couldn't flash some zip files. Does this one correct that?
Click to expand...
Click to collapse
No. Devs need to update their zips to use edify.
jaybob413 said:
Nice work. I had thought about building this and modifying where the confirm_format string gets passed to confirm_selection to show the mount point being formatted. This would help to avoid accidentally formatting the wrong partition by rolling down one when you are making your selection. This only happened to me once, but it was a major pita. I was fortunate to have a recent backup.
Does this include building the mount and storage menu from fstab (Change I92796ec9)?
Click to expand...
Click to collapse
It should, since it was merged in before I synced. I think it does, because it has an option now to format /recovery from within recovery.

jasonmaloney said:
No. Devs need to update their zips to use edify.
Click to expand...
Click to collapse
Sweet. Jumping feet first then!

This is cool to see some sort of ongoing type thing for recovery. Can I say that while I love some of the flexibility of clockwork, like being able to browse for zips or USB mount, I cannot stand scrolling to verify I want to wipe or flash. It could be 2 or 3 no's and be tolerable. I don't know what others think or how easy that is to change, but that 1 thing made me go back to RA.
[dpeeps74]

my phone does not like the download link, any chance somebody could mirror that?

il Duce said:
my phone does not like the download link, any chance somebody could mirror that?
Click to expand...
Click to collapse
1+
Sent from my HTC Hero CDMA using Tapatalk

Thanks for this.
Flashed with fastboot.

Whoaaa, what does format /recovery do exactly? I ALMOST hit that by accident...

Rooster85 said:
any chance of getting this as a HERCIMG.zip?
Click to expand...
Click to collapse
Here you go...
I do not take any credit for this, except for packaging it as HERCIMG.zip. All credit goes to original developer(s), jasonmaloney and anybody else who may be directly/indirectly involved in making the recovery image available.

andythegreenguy said:
Here you go...
I do not take any credit for this, except for packaging it as HERCIMG.zip. All credit goes to original developer(s), jasonmaloney and anybody else who may be directly/indirectly involved in making the recovery image available.
Click to expand...
Click to collapse
Sweet, now I don't need a mirror. It was the wierdest thing, the DL link from xda went to my browser, which made "www.masterjason.blah" look like a bunch of symbols and crap, took forever to load the page and no DL link, now I'm good to go, ty.

il Duce said:
Sweet, now I don't need a mirror. It was the wierdest thing, the DL link from xda went to my browser, which made "www.masterjason.blah" look like a bunch of symbols and crap, took forever to load the page and no DL link, now I'm good to go, ty.
Click to expand...
Click to collapse
Yup mine did the same one of the five times I retried it...
Thanks "GreenAndy" for the herocimg
Sent from my HTC Hero CDMA using Tapatalk

il Duce said:
Sweet, now I don't need a mirror. It was the wierdest thing, the DL link from xda went to my browser, which made "www.masterjason.blah" look like a bunch of symbols and crap, took forever to load the page and no DL link, now I'm good to go, ty.
Click to expand...
Click to collapse
+1
Sent from my HERO200 using XDA App

You are welcome! All thanks should go to jason... I am just the messenger .

Yea no doubt all appreciation go to u jasonm!
Sent from my HTC Hero CDMA using Tapatalk

Has anyone tested mounting/unmounting/backing-up/restoring sd-ext[3|4] with this?

Seems to be play nice with firerat's v1.5.6

[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.

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

[TWRP] Who wants TWRP on ARIES?

Step 1) From the root of your android device tree:
Code:
mkdir -p .repo/local_manifests
curl http://teamacid.github.com/manifests/sgh-t959v/TWRP/twrp.xml > .repo/local_manifests/twrp.xml
Step 2) Wait for noiphonehere to update his tree to include my commit, the sync your device tree to match his
OR (for the impatient)
Cherry pick my commit yourself:
https://github.com/fbis251/android_...mmit/fe504f4d7602432d5de97585698af963aafdd0ab

heard that idevice is kinda excited when seeing this haha

Nice.
I might add this.
Sent from Aries within the 1st Galaxy

Is it more of a personal preference or is TWRP better then CWM?
Edit .... is this simply to allow users to switch to TWRP if I build with CWM?

Have you guys heard of 4ext touch recovery?

Dwack said:
Is it more of a personal preference or is TWRP better then CWM?
Edit .... is this simply to allow users to switch to TWRP if I build with CWM?
Click to expand...
Click to collapse
TWRP includes a file manager in recovery, so if something goes horribly wrong and you need to replace a required init.d script file, you can actually do it without needing a computer for your ADB.
It also looks pretty. And is touch friendly. Friendly touch. Good touch. Mhmm.
But it's the file manager that makes me choose TWRP over CWM any chance I get.
Cooptx said:
Have you guys heard of 4ext touch recovery?
Click to expand...
Click to collapse
According to what its developer says at http://www.4ext.net/status_update.php we're unlikely to ever be supported.
Unlikely:
Older Samsung devices like:
Samsung Galaxy SII
Samsung Galaxy Note
Click to expand...
Click to collapse
Maybe we should focus on recovery options that actually work for our phone?

I was asking if you have ever heard of it. I wasn't asking for it

Theraze said:
TWRP includes a file manager in recovery, so if something goes horribly wrong and you need to replace a required init.d script file, you can actually do it without needing a computer for your ADB.
It also looks pretty. And is touch friendly. Friendly touch. Good touch. Mhmm.
But it's the file manager that makes me choose TWRP over CWM any chance I get.
According to what its developer says at http://www.4ext.net/status_update.php we're unlikely to ever be supported.Maybe we should focus on recovery options that actually work for our phone?
Click to expand...
Click to collapse
Well....
Nexus S has the same hardware we have....

http://forum.xda-developers.com/showthread.php?t=1646108
For all your file managing needs

i've used it. it's nice.

TWRP will be pretty awesome
I tried CWR Touch on my friends SGS2 and its a bit buggy. CWR is ok but TWRP makes it easier and has a file manager too!

It already is. If things go to plan tonight I might have a present for you guys .

@FBis251: Yo man, , sr that I thought u asked how was the TWRP kernel flashing man so I told u it was normal but just after flashing a ROM via TWRP, I knew what u asked It couldn't flash properly (or mayb just my compile got this not yours ^^)

daothanhduy1996 said:
@FBis251: Yo man, , sr that I thought u asked how was the TWRP kernel flashing man so I told u it was normal but just after flashing a ROM via TWRP, I knew what u asked It couldn't flash properly (or mayb just my compile got this not yours ^^)
Click to expand...
Click to collapse
After using your kernel, TWRP wouldn't backup or flash anything. Gonna go back to stock and work my way back up because I can't flash anything with CWM in it.
Sent from my SGH-T959V using xda app-developers app

Whoa weird. I've been able to restore/backup properly on mine. I need to mess around with the cm10.1 based version of it since all of my testing has been on team acid's aries cm9.
The JB kernel might be adding problems to TWRP, but on ICS it's still working fine, even flashing noiphone's cm10.1 build worked from TWRP.

Yeah I ran in to this last night trying to back and flash a new ROM. I could restore from an old back up, it was fine until it reached the recovery part then it freaked you out.
I had to one click.
Sent from my SGH-T959V using xda premium

johnadelic said:
Yeah I ran in to this last night trying to back and flash a new ROM. I could restore from an old back up, it was fine until it reached the recovery part then it freaked you out.
I had to one click.
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
Okay I know exactly what you mean and was able to replicate the issue. I'll try to see what's going on behind the scenes for this since a boot.img restore should only take a second or two when you recover from a backup.

Something about color/overlay image could not be applied (something like that) in adb shell adb logcat when u go into recovery with twrp.
Sent from my SGH-T959V using Tapatalk 2

Has anyone compiled a flash able yet?....just curious.
From my T959W running Illusion