Database Info

captivate cwm works on infuse.[sort of]

just to give you guys some more confidence i ran trusselo's super easy batch scritp on my dad's windows 7 box to hack 3e recovery.
you can look at my 3e thread in captivate general but do not attempt the kernel swap methods!
use trusselo's script on windows
if it fails or you are on a mac/linux machine then use the manual 3e fix after you root the device.
after i got 3e modded for self signed update.zip zip flashing like the old 2e recovery on 2.1 sgs phones i installed rom manager and chose the captivate cwm recovery. rebooted into recovery, reinstaled packages. phone rebooted, reistaled packages again and i was sucessfully in cwm. from there i was able to backup the stock rom and installed a .zip file that just changed my build.prop (taking baby steps) i could have spoofed the build.prop in many ways but it was for the sake of testing. the flash was successful. i booted up checked for the change and confirmed it was written to /system properly.
then i rebooted and restored the backup. there were some graphical errors including a broken progress bar and a splash screen that covers the menu when the restore is done so it is difficult to navigate, but it is something. success! the restored rom booted and the old build.prop was in place proving it was a successful restore.
tomorrow i will try a replaced vending.apk (market) and the build.prop as a market fix and post it in a thread if it works. if gtg465x doesnt mind i will try to build a rom off his deodexed rom if someone doesnt beat me to it.
i think we need a bounty to buy a dev phone for someone more knowledgable than me. i dont want to go all cowboy and brick this thing, the captivate had much more as far as backup plans so im being more cautious with this one. and even if i had a dev phone i wouldnt be of as much help as others around xda.

Chika Da China Da Chinese Chicken?
Dani897 said:
just to give you guys some more confidence i ran trusselo's super easy batch scritp on my dad's windows 7 box to hack 3e recovery.
you can look at my 3e thread in captivate general but do not attempt the kernel swap methods!
use trusselo's script on windows
if it fails or you are on a mac/linux machine then use the manual 3e fix after you root the device.
after i got 3e modded for self signed update.zip zip flashing like the old 2e recovery on 2.1 sgs phones i installed rom manager and chose the captivate cwm recovery. rebooted into recovery, reinstaled packages. phone rebooted, reistaled packages again and i was sucessfully in cwm. from there i was able to backup the stock rom and installed a .zip file that just changed my build.prop (taking baby steps) i could have spoofed the build.prop in many ways but it was for the sake of testing. the flash was successful. i booted up checked for the change and confirmed it was written to /system properly.
then i rebooted and restored the backup. there were some graphical errors including a broken progress bar and a splash screen that covers the menu when the restore is done so it is difficult to navigate, but it is something. success! the restored rom booted and the old build.prop was in place proving it was a successful restore.
tomorrow i will try a replaced vending.apk (market) and the build.prop as a market fix and post it in a thread if it works. if gtg465x doesnt mind i will try to build a rom off his deodexed rom if someone doesnt beat me to it.
i think we need a bounty to buy a dev phone for someone more knowledgable than me. i dont want to go all cowboy and brick this thing, the captivate had much more as far as backup plans so im being more cautious with this one. and even if i had a dev phone i wouldnt be of as much help as others around xda.
Click to expand...
Click to collapse
Very nice. I am gonna try as well. As long as CM is working I am comfortable pushing my luck a little.

Awesome! Can you post the files or the link to the thread with the files?

slider2828 said:
Awesome! Can you post the files or the link to the thread with the files?
Click to expand...
Click to collapse
just look in the captivate general stickies. i would post a link but there is stuff in there that doesnt apply because we dont have any kernels to flash, i dont want to confuse anybody and cause bricks because someone flashes a sgs kernel. i might make new write up.

Chika Da China Da Chinese Chicken?
I was going to run the PC batch script but the download link actually downloaded a CWM zip.
That's no PC script....no batch file to be found.
EDIT: I am an idiot. Disregard.

slappyjoker said:
I was going to run the PC batch script but the download link actually downloaded a CWM zip.
That's no PC script....no batch file to be found.
EDIT: I am an idiot. Disregard.
Click to expand...
Click to collapse
you think you're an idiot now wait till you read the directions!

Chika Da China Da Chinese Chicken?
Dani897 said:
you think you're an idiot now wait till you read the directions!
Click to expand...
Click to collapse
That was pretty classic. But hey, it sure did work.
1st. Test with CM. Adhoc WiFi Supplicant Zip. (Success)
2nd. Dunno yet.

yep working great
i am backing up in cwm as we speak

samsungcaptivates said:
i am backing up in cwm as we speak
Click to expand...
Click to collapse
So CWM doesn't work in the traditional sense yet?

bella92108 said:
So CWM doesn't work in the traditional sense yet?
Click to expand...
Click to collapse
it does but there seems to be a problem. not sure why, i had no issues flashing small mods for testing but people are having trouble flashing roms. besides that the restore process seems to give me some graphical bugs but works. as far as i can tell it works like it should but i wont discredit others claiming issues mounting the sd card.

Dani897 said:
it does but there seems to be a problem. not sure why, i had no issues flashing small mods for testing but people are having trouble flashing roms. besides that the restore process seems to give me some graphical bugs but works. as far as i can tell it works like it should but i wont discredit others claiming issues mounting the sd card.
Click to expand...
Click to collapse
Hmm, how long is the timeframe between when CWM is updated? I'd love to get rid of all this AT&T [email protected]# they litter my phone with, but I don't want to brick it... and lots of people seem to brick phones without CWM, haha

bella92108 said:
Hmm, how long is the timeframe between when CWM is updated? I'd love to get rid of all this AT&T [email protected]# they litter my phone with, but I don't want to brick it... and lots of people seem to brick phones without CWM, haha
Click to expand...
Click to collapse
you can use titanium backup to remove stuff. also there is odin/heimdall to flash "refuse" from h8rift. they work and are also the safety net unique to samsung phones.

Dani897 said:
you can use titanium backup to remove stuff. also there is odin/heimdall to flash "refuse" from h8rift. they work and are also the safety net unique to samsung phones.
Click to expand...
Click to collapse
Yeah I suppose, I am just hoping that CWM for Infuse will release quick along with new ROMs (Gingerbread? hehe)

bella92108 said:
Yeah I suppose, I am just hoping that CWM for Infuse will release quick along with new ROMs (Gingerbread? hehe)
Click to expand...
Click to collapse
"Release quick?" We've been waiting for weeks already

beatblaster said:
"Release quick?" We've been waiting for weeks already
Click to expand...
Click to collapse
Weeks? Didn't this phone hit stores 5/21? That was 8 days ago.

bella92108 said:
Weeks? Didn't this phone hit stores 5/21? That was 8 days ago.
Click to expand...
Click to collapse
Nah, 5/15. It's been 2 weeks today. Anyway.....

Hey anyone find a way to install cwm install packages using this update.zip?
It says it can't mount the sdcard when I try to install the .zip.
Anyone?

[RECOVERY] Modified 3e Recovery

Dani897 has already made a discussion of this, but I'm moving this information over as an official post in the Infuse 4G section as well.
This is from existz/untermensch's thread. I take no credit. See here for more info http://forum.xda-developers.com/showthread.php?t=909213
Making this modification will allow you to flash un-signed .zip files due to signature verification being turned off. (3e requires root)
* Download and extract the .zip
* Use a terminal emulator or ADB Shell and mount system as read/write.
* For backup purposes, use adb or root explorer to rename the current recovery file in /system/bin to recovery.orig
* Use a file manager (Root Explorer) and copy the new recovery file to /system/bin
* Reboot and your 3e (Froyo stock) recovery will no longer require signature checking.
You can now use this recovery or use the CWM from Captivate (posted in another thread here).
I am not responsible if this bricks your phone. This is easy cheese...just follow these steps.
Download:
3e Recovery w/o signature verification
Youtube video using Root Explorer from gtg465x (Make sure to Thank him!!)

You actually tested this on an Infuse?

DarkH2O said:
You actually tested this on an Infuse?
Click to expand...
Click to collapse
Yes. it is working on mine right now.

i already tested this days ago and cwm
except using truselos super easy batch script to make it even more easy for people to use.
http://forum.xda-developers.com/showthread.php?t=1086622
still there is disbelief. yes people it works! im not sure what trouble people are having flahsing roms but cwm and 3e can flash .zip files just fine. i expected to see some flashable mods and themes by now. i have successfully flashed files for testing purposes and im not too advanced of a user. i planed to post some things like a market fix and such but i have been disrtacted.

Dani897 said:
i already tested this days ago and cwm
except using truselos super easy batch script to make it even more easy for people to use.
http://forum.xda-developers.com/showthread.php?t=1086622
still there is disbelief. yes people it works! im not sure what trouble people are having flahsing roms but cwm and 3e can flash .zip files just fine. i expected to see some flashable mods and themes by now. i have successfully flashed files for testing purposes and im not too advanced of a user. i planed to post some things like a market fix and such but i have been disrtacted.
Click to expand...
Click to collapse
Dani, i completely agree. If you notice, I made mention of your testing at the top of the article.
Now that there is a dedicated thread, its much more likely to be realized that this works FINE. I think once I get a tester for the Odin package I slapped together to get us back to stock in case we brick, and get it successfully setup, i'll put a thread out and we can REALLY get to work on some ROMs.
So far, this phone's software is nearly identical to the Captivate, meaning we will just need to port from the Captivate and we will have a mass of ROMs in no time!

h8rift said:
Dani, i completely agree. If you notice, I made mention of your testing at the top of the article.
Now that there is a dedicated thread, its much more likely to be realized that this works FINE. I think once I get a tester for the Odin package I slapped together to get us back to stock in case we brick, and get it successfully setup, i'll put a thread out and we can REALLY get to work on some ROMs.
So far, this phone's software is nearly identical to the Captivate, meaning we will just need to port from the Captivate and we will have a mass of ROMs in no time!
Click to expand...
Click to collapse
as soon as we get some kernel dev on this thing i agree. porting will be easy. thanks for the write ups too. are you planning to get a second phone? i would test if i had two of them. my captivate will go to my brother, if it weren't for that id have probably bricked it and begged some people to try making new odin packages for me to fix it.
i understand that after a brick the user hates not having the phone and may be very tempted to return it but it is helpful to everyone to try all you can to recover it. if mine bricks im using the insureance plan and saying it was stolen, then i will have a dedicated test phone.

I have an Atrix as well, but would prefer someone who may have already bricked to try this package that i wrote up this morning.
I dont mind someone wanting to swap.their phone...but i literally need about an hour or two of time with the brick's user and its very likely that we will have working Odin....and then you and i...as well as others... can do kernel and rom deving nearly immediately. We have source already, so we only need to test this safety net . PM me if you find someone who is bricked or is willing to test!!
-h8
Dani897 said:
as soon as we get some kernel dev on this thing i agree. porting will be easy. thanks for the write ups too. are you planning to get a second phone? i would test if i had two of them. my captivate will go to my brother, if it weren't for that id have probably bricked it and begged some people to try making new odin packages for me to fix it.
i understand that after a brick the user hates not having the phone and may be very tempted to return it but it is helpful to everyone to try all you can to recover it. if mine bricks im using the insureance plan and saying it was stolen, then i will have a dedicated test phone.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I997 using XDA App

I have a bricked Infuse im not sure what caused the crash. I was running stock rooted by the super one click method and was uninstalling an app when it went all black except the bottom keys. Doesnt do much of anything else now. I attempted an odin fix someone suggested to no avail. I can get into download mode still but nothing else. Id be willing to try anything to unbrick it .

it's working for me, I unzipped, put the file in my dropbox, downloaded the file on phone from dropbox, used root explorer to mount, (I'm already rooted) copied the file, went to system/bin, renamed the original, then pasted the new file, rebooted, flashed CWM to captivate, and rebooted into recovery, and it works. I still have my HTC Inspire, i'm on a 30 day run here to see if i like the infuse. So far it's the best GPS i've had, and i've had a lot of phones. I hate to think I spent 600 bucks on a another captivate. I had that phone as well, but so far i really like it.

Realityfalse said:
I have a bricked Infuse im not sure what caused the crash. I was running stock rooted by the super one click method and was uninstalling an app when it went all black except the bottom keys. Doesnt do much of anything else now. I attempted an odin fix someone suggested to no avail. I can get into download mode still but nothing else. Id be willing to try anything to unbrick it .
Click to expand...
Click to collapse
if you can get into download mode I personally would try running the captivate odin and see what happens, buts that's just me lol. I'm a risk taker lol.

What commands do you use in ADB to mount system as read/write?

budco2000 said:
if you can get into download mode I personally would try running the captivate odin and see what happens, buts that's just me lol. I'm a risk taker lol.
Click to expand...
Click to collapse
dont do that. you dont want the captivate param.ifs on here. you may loose download mode if the boot parameters get messed up. especially dont flash anything with bootloaders, that means no one click nad no 3-button fix roms. this may be similar to the galaxy s but there are atleast a few differences in hardware layout that would make that a bad idea. for instance this can run gps and camera during phone calls. the sgs cant so the way things comunicate on the board may be differet, it may also just be differences in the kernel or framework but we cant be sure.

Dani897 said:
dont do that. you dont want the captivate param.ifs on here. you may loose download mode if the boot parameters get messed up. especially dont flash anything with bootloaders, that means no one click nad no 3-button fix roms. this may be similar to the galaxy s but there are atleast a few differences in hardware layout that would make that a bad idea. for instance this can run gps and camera during phone calls. the sgs cant so the way things comunicate on the board may be differet, it may also just be differences in the kernel or framework but we cant be sure.
Click to expand...
Click to collapse
Yes. DO NOT DO that.
BTW, I just had a successful Odin flash with beatblaster! His framework-res was broken, and he flashed all stock partitions successfully. Hope to be posting it up to the masses in about an hour; After he does some initial checks now that he's back to stock to make sure everything is 100%!
Let's get this party started ....stay tuned!

h8rift said:
Yes. DO NOT DO that.
BTW, I just had a successful Odin flash with beatblaster! His framework-res was broken, and he flashed all stock partitions successfully. Hope to be posting it up to the masses in about an hour; After he does some initial checks now that he's back to stock to make sure everything is 100%!
Let's get this party started ....stay tuned!
Click to expand...
Click to collapse
yaaay
ok now we can get all crazy with few worries. good to hear!

Dani897 said:
yaaay
ok now we can get all crazy with few worries. good to hear!
Click to expand...
Click to collapse
Yes. That's a major hurdle.

h8rift said:
Yes. DO NOT DO that.
BTW, I just had a successful Odin flash with beatblaster! His framework-res was broken, and he flashed all stock partitions successfully. Hope to be posting it up to the masses in about an hour; After he does some initial checks now that he's back to stock to make sure everything is 100%!
Let's get this party started ....stay tuned!
Click to expand...
Click to collapse
Sweet! So the dump was good then it sounds like. So just to sum it all up, odin the pda tar and it restores and wipes EVERYTHING!
Woops! AND DEODEXED!!?!?

I'm pretty new to all of this, but here is how I did it. Make sure you have busybox installed!
Extract the "recovery" file to your phone's internal SD card.
On your phone, go into your terminal emulator.
Type in "su" and press enter.
Type in "cd /sdcard" and press enter.
Type in "mount -o rw,remount /dev/block/stl9 /system"
Type in "cp -f recovery /system/bin" and press enter.
Reboot your phone.
Maybe this will help someone. Maybe it's not even the right way to do this, and my phone will soon explode. I'm a pretty big noob with this, so someone let me know.
PS: If you brick your phone, it isn't my fault.

Hi I came from iPhone 4 and like 2days owning this infuse, I am trying to follow gtg465x to install his ROM, I am done with the rooting and his next step is to "install 3e recovery" now that I am here I am totally lost, I downloaded the file here my Questions are:
1.where do I extract the zip I donwloaded from here? From the SD card root?
2. What thing will I use Terminal emulator or ADB SHELL to make it read/write is that 2 an Android apps I'm lost here. I am trying to be careful, I searched and found too much post and way different doing this. So now I am confuse.
Can anybody tell me how it install 3e recovery the easy and idiot proof way, like I said I am new to android I really have no idea about everything, and most of them too are initial I don't even know what the initials means. Anyone? Thanks
Sent from my SAMSUNG-SGH-I997 using XDA Premium App

spirikitik said:
Hi I came from iPhone 4 and like 2days owning this infuse, I am trying to follow gtg465x to install his ROM, I am done with the rooting and his next step is to "install 3e recovery" now that I am here I am totally lost, I downloaded the file here my Questions are:
1.where do I extract the zip I donwloaded from here? From the SD card root?
2. What thing will I use Terminal emulator or ADB SHELL to make it read/write is that 2 an Android apps I'm lost here. I am trying to be careful, I searched and found too much post and way different doing this. So now I am confuse.
Can anybody tell me how it install 3e recovery the easy and idiot proof way, like I said I am new to android I really have no idea about everything, and most of them too are initial I don't even know what the initials means. Anyone? Thanks
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
Click to expand...
Click to collapse
I came from an iphone as well, about 2 weeks ago. I used the method posted in my previous reply. It worked for me, and has been doing fine so far. One thing you must do is make sure busybox is installed before you try it though. If you dont have busybox installed, none of the commands will work. Then just download "Terminal Emulator" from the market, and use that to give commands.
Sent from my SAMSUNG-SGH-I997 using XDA App

Cohdee said:
I came from an iphone as well, about 2 weeks ago. I used the method posted in my previous reply. It worked for me, and has been doing fine so far. One thing you must do is make sure busybox is installed before you try it though. If you dont have busybox installed, none of the commands will work. Then just download "Terminal Emulator" from the market, and use that to give commands.
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
What command? I really have no idea, can you give me step by step if you don't mind?
Sent from my SAMSUNG-SGH-I997 using XDA Premium App

ClockWorkMod 4+ for NS4G?

Does any one have a recovery.img of clockwork version 4 for the nexus s 4g?

http://forum.xda-developers.com/showthread.php?t=988686
NS4G version.

i have this one

ok hellcat i sent you an pm telling you how to use it

michaelpeerman said:
ok hellcat i sent you an pm telling you how to use it
Click to expand...
Click to collapse
You do realize it's the same thing I posted right?
All he did was put the .img in a zip file.
The instructions to flash it is to... well, if you're using his .zip which I don't recommend because a MD5 hash is missing. You can try downloading his file and verify it corresponding to that thread. You need to make sure the MD5 hash matches otherwise something could go wrong because you have a bad download.
1. Go to the page I linked, download a NS4G recovery with a color that you'd like on it.
2. Once its downloaded, put the img in your /sdk/tools/ folder.
3. Put your phone into bootloader mode.
4. Open command prompt
5. cd C:\wherever your sdk folder is
6. fastboot flash recovery ns4g-4002-color.img (replace color with the color you got)
E.G. if you downloaded the cyan one, it would be, fastboot flash recovery ns4g-4002-cyan.img
green? --- fastboot flash recovery ns4g-4002-green.img
and so forth.
7. reboot recovery
done.
Sent from my Transformer TF101 using XDA Premium App

worked like a charm mike, wish i woulda thought of that but then i again im lazy as someone put it in another thread
i downloaded that from the same place you linked about 4 hours ago
ok zephk i was just giving him the actual file is all, either way it worked out in the end, and with your link someone can find the color of their choice

hellcatt said:
i downloaded that from the same place you linked about 4 hours ago
Click to expand...
Click to collapse
Yeah but its not the original link. It's also put in a .zip file. Just wanted to explain to him that both of them are the same. So regardless it should work. Just OP should check its MD5hash before actually fastboot flashing it.

Ok let me clear things up. Hellcat was wanting it on his phone so he contacted me asking me how to install so i advidsed him to use the one click method by shabby penquin just replace the recovery in his file with this one and rename it to recovery

yes and it worked perfectly, didnt change anything at all except the version of CWM. do you think we should contact shabby penguin to maybe update his file?

hellcatt said:
yes and it worked perfectly, didnt change anything at all except the version of CWM. do you think we should contact shabby penguin to maybe update his file?
Click to expand...
Click to collapse
Duh. What did you expect to be changed within Clockwork? That's why the latest is 3.0.2.4 for the NS. Recoveries don't get updated all of the time.
Most of the changes aren't even for the NS tbh.

zephiK said:
Duh. What did you expect to be changed within Clockwork? That's why the latest is 3.0.2.4 for the NS. Recoveries don't get updated all of the time.
Most of the changes aren't even for the NS tbh.
Click to expand...
Click to collapse
so what are you saying im not allowed to want to update from 3.1.0.1?
so the one for the ns4g which is what we are talking about that is version 4.0.0.2 that YOU posted a link to that is now on my phone doesnt exist? coulda fooled me. thanks for visiting zeph

hellcatt said:
so what are you saying im not allowed to want to update from 3.1.0.1?
so the one for the ns4g which is what we are talking about that is version 4.0.0.2 that YOU posted a link to that is now on my phone doesnt exist? coulda fooled me. thanks for visiting zeph
Click to expand...
Click to collapse
No? I'm just saying that when you update your recovery you shouldn't be expecting much changes to be coming from it. Clockwork Recovery only gets updated to 4.0.0.0+ to support new devices. That's why the official Clockwork Recovery that is supported by ROM Manager & Koush's current version for the Nexus S is at 3.0.2.4 and not 4.0.0.2.
And I never said it doesn't exist. Yeah I didn't mention "official support" but you should know what I meant. Don't pretend like you don't know what I'm speaking about.

i dont know what youre speaking about, im a self admitted android moron and lazy one click user remember? lol. in fact your directions a few posts back might as well be in Aramaic because i think i was doing that but it wasnt working.
remember im the free floating un braced barrel ceiling guy
all i know is i wanted the same version on my new ns4g that i had on my original and couldnt figure it out after a few hours. and if i knew it was as simple as what mike told me i wouldve done that when i rooted......but i didnt
and now i feel like an ass for bothering anyone about it now that i found this
https://market.android.com/details?id=com.joeykrim.flashimagegui

hellcatt said:
i dont know what youre speaking about, im a self admitted android moron and lazy one click user remember? lol. in fact your directions a few posts back might as well be in Aramaic because i think i was doing that but it wasnt working.
remember im the free floating un braced barrel ceiling guy
all i know is i wanted the same version on my new ns4g that i had on my original and couldnt figure it out after a few hours. and if i knew it was as simple as what mike told me i wouldve done that when i rooted......but i didnt
and now i feel like an ass for bothering anyone about it now that i found this
https://market.android.com/details?id=com.joeykrim.flashimagegui
Click to expand...
Click to collapse
Okay now I have no idea what you're talking about because you're talking irrelevance now. But anyway, the OP has what he looked for in this thread. Congrats. I only responded to give him his answer on that he was surprised that there wasn't much changes within the recovery.
Nothing is really ever changed in a recovery as it is 100% functional. The Clockwork Recovery version only really increases because of additional support of Clockwork recovery for other Android phones, tablets.

The truth about version of CWM and your ROM

There have been many people wondering whether or not the version of clockworkmod recovery will be compatible with certain roms. Clockworkmod has no affect on the ROM whatsoever so you can be on 5.0.2.7, touch recovery 5.5.0.4, touch recovery 5.8.1.3, etc. and you can install any rom from within those recoveries. It makes absolutely no difference what recovery you are on. Every recovery above CWM 3.0 uses edify scripting (which is what is needed for all roms above android 2.0). So if anyone tells you that you need a certain recovery to flash ICS or GB they are wrong. All Clockworkmods are compatible with ALL ROMS.

I concur. Ive tried all 3 and ive had no issues. I think some folks state to use certain ones because thats what they used and they didnt have any problems, so they keep telling everyone to do what they did.
As with any Rom load, all issues arise or dont arise based on how well you cleaned the slate before applying the ROM.
Dixit

Good to hear this re-affirmed. I am having problems flashing .zip's in CWM and know for sure it's not the version!

randomtask16 said:
Good to hear this re-affirmed. I am having problems flashing .zip's in CWM and know for sure it's not the version!
Click to expand...
Click to collapse
what issues are you having? right away the first thing i would try is downloading the rom again as you may have had a corrupted download.

From personal experience I have had a ton of issues before I ODINd the 5.5.0.4 recovery. Prior to that I was running the 5.8.1.3 and I was having a ton of issues flashing some of the roms. I don't have any proof of errors or anything but I'm certain that Appdroid will be willing to vouch for me right now.
~PsyCl0ne

I've tried them all without any major issues except for one. Flashing ROMS is one thing but the overall functioning of all the tools within seem to differ. Permissions for example work on some and not on others. They do differ overall but I agree flashing a ROM isn't an issue. Everyone has their preference and if a developer says to use a particular version, there is a reason. I'll ask you since your the expert, do the wipes and cache clears work the same way?
Sent from my SAMSUNG-SGH-I727 using xda premium

Maybe someone can tell me what's wrong with my setup, I'm on Superlite 5.0 with ROM Mgr v5.0.0.6. I can only boot into CWM (Touch 5.8.1.3) from ROM mgr and nothing else. It's not a major deal but I can't go directly to backup, restore e.g. like I used to with a GB rom.

bdbx18 said:
Maybe someone can tell me what's wrong with my setup, I'm on Superlite 5.0 with ROM Mgr v5.0.0.6. I can only boot into CWM (Touch 5.8.1.3) from ROM mgr and nothing else. It's not a major deal but I can't go directly to backup, restore e.g. like I used to with a GB rom.
Click to expand...
Click to collapse
I dont use Rom Manager, you wont find alot that use it for those functions either as its essentially passes that request off to CWM when its rebooted. So Id suggest just rebooting to recovery using the toggle panel in Superlite, then in the CWM touch, just backup, restore, do anything.
Dixit

bdbx18 said:
Maybe someone can tell me what's wrong with my setup, I'm on Superlite 5.0 with ROM Mgr v5.0.0.6. I can only boot into CWM (Touch 5.8.1.3) from ROM mgr and nothing else. It's not a major deal but I can't go directly to backup, restore e.g. like I used to with a GB rom.
Click to expand...
Click to collapse
Are you saying that if you power down and use the three-button combo it doesn't work? (ie volume up+volume down+power)
If this is the case you may want to try using Odin to flash recovery again (found in the Fix Soft Brick or in the rooting thread...)

skrambled said:
Are you saying that if you power down and use the three-button combo it doesn't work? (ie volume up+volume down+power)
If this is the case you may want to try using Odin to flash recovery again (found in the Fix Soft Brick or in the rooting thread...)
Click to expand...
Click to collapse
For my phone I don't have to hold power when booting up. I just hold both volume buttons till I see the recovery menu.
~PsyCl0ne
Sent from my SAMSUNG-SGH-I727 using XDA

PsyCl0ne said:
For my phone I don't have to hold power when booting up. I just hold both volume buttons till I see the recovery menu.
~PsyCl0ne
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
This is exactly how I get into recovery on my AT&T phone. Holding three buttons just causes it to reboot over and over again

skrambled said:
Are you saying that if you power down and use the three-button combo it doesn't work? (ie volume up+volume down+power)
If this is the case you may want to try using Odin to flash recovery again (found in the Fix Soft Brick or in the rooting thread...)
Click to expand...
Click to collapse
What I meant is that I used to do for e.g. 'Backup current rom' from ROM mgr, name it accordingly, and it will reboot into CWM and backup with that name. Now it just reboots to CWM main panel and sits there. Even the timestamp on the backup file is off.

PsyCl0ne said:
For my phone I don't have to hold power when booting up. I just hold both volume buttons till I see the recovery menu.
~PsyCl0ne
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
Oh yes, you're on rogers. I thought rogers users had to hold volume down only+power button to get into recovery (ie no volume up key involved). I've seen many rogers users say that...
---------- Post added at 10:20 PM ---------- Previous post was at 10:15 PM ----------
bdbx18 said:
What I meant is that I used to do for e.g. 'Backup current rom' from ROM mgr, name it accordingly, and it will reboot into CWM and backup with that name. Now it just reboots to CWM main panel and sits there. Even the timestamp on the backup file is off.
Click to expand...
Click to collapse
Oh! Now I get it. I have had weird issues with ROM Manager ever since I had this phone. Backup via ROM Manager worked a couple times on gb roms but then it started doing what you described. Ever since it started doing that I just backup from cwm, and then go back in with Root Explorer to re-name the files so I know what's what...

Can't you just boot straight to recovery from most roms as well as from rom manager if you were on a rom that didn't have that ability? I can't remember the last time I had to press buttons to get into recovery, I'm not saying it's not useful to know, but merely stating that it's highly unnecessary in most cases to ever have to touch the buttons for recovery.

sk8erwitskil said:
There have been many people wondering whether or not the version of clockworkmod recovery will be compatible with certain roms. Clockworkmod has no affect on the ROM whatsoever so you can be on 5.0.2.7, touch recovery 5.5.0.4, touch recovery 5.8.1.3, etc. and you can install any rom from within those recoveries. It makes absolutely no difference what recovery you are on. Every recovery above CWM 3.0 uses edify scripting (which is what is needed for all roms above android 2.0). So if anyone tells you that you need a certain recovery to flash ICS or GB they are wrong. All Clockworkmods are compatible with ALL ROMS.
Click to expand...
Click to collapse
You are absolutely correct. That is why I have not required any specific recovery, but told people what I use. yours . But, there is a caveat, since flashing a full rom requires reliable wipe operations from the recovery, it appears to be a hit or miss. That is why, I have specified the requirement that whatever recovery you use, use the recoveries built-in Format /system, /cache and /data, I am not going to do it within my update script.
BTW, thanks for the recovery, it cuts down a bunch of time trying to test, build..

Funny you say CWR makes no difference. I disagree. The kernel works different in different versions of cwr
With
Clockwork Touch aka recovery-clockwork-touch-5.8.1.3-hercules
I cant adb remount it gets stuck in Read only.
With
v 5.0.2.6 I have no issues
Flashing files in one ver the other may cause issues for some phones.. As we have seen every phone is handling the ICS flash different.
I have had better luck with the older CWR

mhx said:
Funny you say CWR makes no difference. I disagree. The kernel works different in different versions of cwr
With
Clockwork Touch aka recovery-clockwork-touch-5.8.1.3-hercules
I cant adb remount it gets stuck in Read only.
With
v 5.0.2.6 I have no issues
Flashing files in one ver the other may cause issues for some phones.. As we have seen every phone is handling the ICS flash different.
I have had better luck with the older CWR
Click to expand...
Click to collapse
Nope..read the OP again...he is talking about the linkage of ROM and recovery. They are unrelated...

mohan_kr said:
Nope..read the OP again...he is talking about the linkage of ROM and recovery. They are unrelated...
Click to expand...
Click to collapse
i beg to differ, mhx makes a valid point. The op may be true for gb, but for ics i too have noticed better flashes, and things "stuck better" with 5.0.2.6. I can't even get fix permissions to work on anything past 5.0.2.7

icenight89 said:
i beg to differ, mhx makes a valid point. The op may be true for gb, but for ics i too have noticed better flashes, and things "stuck better" with 5.0.2.6. I can't even get fix permissions to work on anything past 5.0.2.7
Click to expand...
Click to collapse
I've flashed multiple ICS roms multiple times on multiple CWM (touch and non) recoveries, and I've never had a single issue.

icenight89 said:
i beg to differ, mhx makes a valid point. The op may be true for gb, but for ics i too have noticed better flashes, and things "stuck better" with 5.0.2.6. I can't even get fix permissions to work on anything past 5.0.2.7
Click to expand...
Click to collapse
If the OP was talking about different features of a particular recovery, then yes there is point to it. He is talking about flashing a ROM with edifying scripting support for the skyrocket, which should work regardless of the version of the base android platform for our device, if of course the ROM creator has put the rights bits in the script for that particular ROM.

[Q] Boot Looping - ANY custom rom

I have unlocked my TF700. I was able to root the stock rom with Kangaroot with no problem. I then tried to load a custom rom, and got stuck in boot loop. I was trying Stable CM10, then I went on to try 5 other nightlies in reverse (from current as of yesterday) order. All have the same problem. I have cleared Cache Partition and Davlik Cache multiple times. I can flash to the stock rom from ASUS site and get through boot with no problem. Each time I do that I need to re-flash CWM. I've since also tried Clean and LiquidSmooth. Nothing gets past boot animation. I've let all attempts sit there for at least 10-15 minutes just to be sure it wasn't just slow.
Any idea where to start in troubleshooting?
CWM Log shows:
Code:
ClockworkMod Recovery v6.0.2.7
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
init.svc.recovery=running
init.svc.mishelp=restarting
init.svc.adbd=running
service.adb.root=1
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
I:Can't format unknown volume: /external_sd
I:Can't partition non-vfat: datamedia
I tried without the microsd card in as well.

I'd make sure the latest 4.1 is installed.
Push TWRP thru ADB
Download A ROM zip to the external card
Boot to custom recovery
Then try installing a ROM from TWRP after backing up
Hope this might help you.

Thats OK said:
I'd make sure the latest 4.1 is installed.
Push TWRP thru ADB
Download A ROM zip to the external card
Boot to custom recovery
Then try installing a ROM from TWRP after backing up
Hope this might help you.
Click to expand...
Click to collapse
Well after trying CM10 Stable, 2 nightlies, Liquid Smooth, all through TWRP (which is way better than CWM in my book now), I was able to get past boot with CleanRom. Unfortunately it doesn't look like wifi works, nor bluetooth, or full screen resolution Maybe because the rom is meant for Nexus 10. Oddly it shows the liquidsmooth loader and options too.
[Edit] Wifi and bluetooth started working after another reboot. After that I was able to switch over to CM10 Nightly. Still no full resolution, but better than broken. Yay for TWRP.

You've installed Cleanrom for the Nexus 10 on your TF700? I'm surprised that it boots at all. Why don't you install the one for the Tf700?

I read this yesterday and felt dumb for not knowing what Kangaroot was. :S
@OP: you've taken an immense risk, and are darned lucky to get out of this with only a malfunctioning device and not a brick. Next time, read up a bit.
Sent from a comfortable chair from the outer ring of Purgatory. The red guy asked me to say 'hi'.

sbdags said:
You've installed Cleanrom for the Nexus 10 on your TF700? I'm surprised that it boots at all. Why don't you install the one for the Tf700?
Click to expand...
Click to collapse
I thought I was downloading the TF700 version. When it loaded, however, it said Nexus10. I've not been able to find one that is for the TF700 on Scott's site. I really like how it guides the user through install options, which more Roms had this. Helps us noobs.

ngMondo said:
I thought I was downloading the TF700 version. When it loaded, however, it said Nexus10. I've not been able to find one that is for the TF700 on Scott's site. I really like how it guides the user through install options, which more Roms had this. Helps us noobs.
Click to expand...
Click to collapse
OK, here is the correct Cleanrom for tf700 http://forum.xda-developers.com/showthread.php?t=2049274

MartyHulskemper said:
@OP: you've taken an immense risk, and are darned lucky to get out of this with only a malfunctioning device and not a brick. Next time, read up a bit.
Click to expand...
Click to collapse
So that I can avoid the risk later, what was it that I did wrong as you see? Or are you referring to the Nexus10 build of CleanRom? If so, its the only one I found, and the page I downloaded from said it was TF700.

Scott no longer makes or supports CleanROM for the TF700 (or Nexus 7 for that matter), I do He has removed it from his site.
I don't know how you did it but somehow you got confused and downloaded and flashed CleanROM for the Nexus 10.
You have now given me an idea, seeing as you guinea pigged it and it booted
SO an indirect thank you!!

Wow my friend,
You really did dodge a bullet there!
Looks like the Nexus drivers and framework must be close.
Interesting...

sbdags said:
Scott no longer makes or supports CleanROM for the TF700 (or Nexus 7 for that matter), I do He has removed it from his site.
I don't know how you did it but somehow you got confused and downloaded and flashed CleanROM for the Nexus 10.
You have now given me an idea, seeing as you guinea pigged it and it booted
SO an indirect thank you!!
Click to expand...
Click to collapse
So, oddly enough the "correct" version of CleanRom 3.2.2 doesn't boot, but the Nexus 10 one did. Tried wipe and everything right before and after, 3 times... no dice.

ngMondo said:
So, oddly enough the "correct" version of CleanRom 3.2.2 doesn't boot, but the Nexus 10 one did. Tried wipe and everything right before and after, 3 times... no dice.
Click to expand...
Click to collapse
Well I suspect you have also managed to flash the Google Nexus 10 bootloader or some part of a kernel. I have no idea how to help you, but what is certain is you currently can't use any roms designed for the TF700 .....

sbdags said:
Well I suspect you have also managed to flash the Google Nexus 10 bootloader or some part of a kernel. I have no idea how to help you, but what is certain is you currently can't use any roms designed for the TF700 .....
Click to expand...
Click to collapse
Well, I think I've redone bootloader and kernel multiple times by now. I was actually about to ask you if there was a specific kernel option I should choose in the CleanRom installer, but it looks like I'm up and running again. I tried the DeOdexed version about 4 times with no luck. The Odexed version worked the first time through. So far everything looks to be working (wifi, bluetooth, dock, sd, gapps, etc).

Buhohitr had mentioned in another thread that TWRP has an option to wipe the eMMC (internal card erase) without hurting the recovery partition.
Last resort however if the system is a mess.
If all is at least running a new version of CROMi I'd just sit tight.
I am kind of curious to see if you have any more problems with user incurred shutdown and reboots.

ngMondo said:
So that I can avoid the risk later, what was it that I did wrong as you see? Or are you referring to the Nexus10 build of CleanRom? If so, its the only one I found, and the page I downloaded from said it was TF700.
Click to expand...
Click to collapse
Yeah, I was referring to flashing the N10 build. You were lucky, my friend. The TF700 makes one expensive paperweight. My remark seems to have gotten your feathers ruffled a bit: I did not mean it that way. Sorry if I offended you in any way.
sbdags said:
You have now given me an idea, seeing as you guinea pigged it and it booted
SO an indirect thank you!!
Click to expand...
Click to collapse
Opportunism FTW!