Related
Does anyone have any experience with this Manager? It looks like it might be interesting alternative.. perhaps not yet, but.....
Sent From my Two Tin Cans & String Device on The Wookie Network
shaggyskunk said:
Does anyone have any experience with this Manager? It looks like it might be interesting alternative.. perhaps not yet, but.....
I have used TWRP. I was on CWM Touch, downloaded and installed the TWRP from google play. Rebooted into recovery, created backups to internal and external, and flashed SkyICS 4.2f6 by Seanz. I followed OP instructions on how to flash. Did not have any problems and it was very easy to use.
Used TWRP and flashed several MODS without any hitch. All I did was reboot into recovery selected the zip files and swipe to install, did not even had to wipe cache or anything. I am not sure if this is the correct way but I was able to flash 8 other MODS doing this.
Here is what don't like:
I wanted to install the same rom but to do a clean wipe since the rom had several updates. I rebooted into recovery to TWRP, did OP flashing instructions which were:
-reboot into team win recovery
-wipe system
-factory data reset
-then go to mounts and choose external sd
-no go back and find the rom by choosing install zip
-swipe to confirm
-then install the radio you downloaded
and when complete reboot phone
-at this point everything will be settling and caching
which may or may not seem laggy.... and yes that white line is normal
its a battery representation mod
-im sure youll be eager to update busybox immediatly but let me tell you no
first open super user app.. find preferences and update user binary
hit it twice giving it root permissions
now .. is when to update busy box through the provided installer
-after you have done this
-power down phone
reboot into recovery and flash the latest update
and email package only
However, I was not able to reboot into recovery. I have a Samsung Skyrocket but was not able to put the phone into recovery mode by pressing and holding the power, volume up, and volume down buttons. The phone kept vibrating but the Samsung screen wont come up. Frustrated, I rebooted the phone, downloaded CWM, updated to Touch and proceeded to flash using CWM with no problems.
At this point i'm hesitant on using TWRP. I am not even sure if ODIN supports it. I'm afraid that if i'm on TWRP and brick my phone, I will not be able to use ODIN.
Good luck and please press thanks if this was useful.
Using SeanZ SKYICS Dragon 4.2F6-2.2A
on Samsung Skyrocket
Click to expand...
Click to collapse
RAVEN6 said:
shaggyskunk said:
Does anyone have any experience with this Manager? It looks like it might be interesting alternative.. perhaps not yet, but.....
I have used TWRP. I was on CWM Touch, downloaded and installed the TWRP from google play. Rebooted into recovery, created backups to internal and external, and flashed SkyICS 4.2f6 by Seanz. I followed OP instructions on how to flash. Did not have any problems and it was very easy to use.
Used TWRP and flashed several MODS without any hitch. All I did was reboot into recovery selected the zip files and swipe to install, did not even had to wipe cache or anything. I am not sure if this is the correct way but I was able to flash 8 other MODS doing this.
Here is what don't like:
I wanted to install the same rom but to do a clean wipe since the rom had several updates. I rebooted into recovery to TWRP, did OP flashing instructions which were:
-reboot into team win recovery
-wipe system
-factory data reset
-then go to mounts and choose external sd
-no go back and find the rom by choosing install zip
-swipe to confirm
-then install the radio you downloaded
and when complete reboot phone
-at this point everything will be settling and caching
which may or may not seem laggy.... and yes that white line is normal
its a battery representation mod
-im sure youll be eager to update busybox immediatly but let me tell you no
first open super user app.. find preferences and update user binary
hit it twice giving it root permissions
now .. is when to update busy box through the provided installer
-after you have done this
-power down phone
reboot into recovery and flash the latest update
and email package only
However, I was not able to reboot into recovery. I have a Samsung Skyrocket but was not able to put the phone into recovery mode by pressing and holding the power, volume up, and volume down buttons. The phone kept vibrating but the Samsung screen wont come up. Frustrated, I rebooted the phone, downloaded CWM, updated to Touch and proceeded to flash using CWM with no problems.
At this point i'm hesitant on using TWRP. I am not even sure if ODIN supports it. I'm afraid that if i'm on TWRP and brick my phone, I will not be able to use ODIN.
Good luck and please press thanks if this was useful.
Using SeanZ SKYICS Dragon 4.2F6-2.2A
on Samsung Skyrocket
Click to expand...
Click to collapse
That's quite strange... I've been using TWRP 2.2.0 for a while now, and I have no problems. I can boot into Recovery mode with up/down and power with ease, as well as through a ROM.
Click to expand...
Click to collapse
Unless you typed it wrong, the problem seems to be you're holding power down along with the volume buttons. I've never had to do that after the phone vibrates telling me its powering up
Power down the phone, then power it back on, then immediately press and hold both volume buttons only. Just a thought.
I've been using twrp for awhile now to flash skyics. Never an issue getting to recovery.
Edit. Odd that cwm works for you but twrp doesn't. Maybe Odin back to stock and do it all over again?
I've flashed using either method. As long as it works, right?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
TWRP rulez
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
ConfusingCurve said:
RAVEN6 said:
That's quite strange... I've been using TWRP 2.2.0 for a while now, and I have no problems. I can boot into Recovery mode with up/down and power with ease, as well as through a ROM.
Click to expand...
Click to collapse
It is strange. Now that I am back on CWM Touch, I can enter recovery using up/down and power. I'll wait a while before I reinstall TWRP.
Click to expand...
Click to collapse
I personly don't like TWRP it still has issues for me as well. I have had to flash more then once cuz it did not take. I went back to touch and it flashes every time on the first shot. It looks cool but still needs work.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
User error
Twrp works fine.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
RAVEN6 said:
shaggyskunk said:
Does anyone have any experience with this Manager? It looks like it might be interesting alternative.. perhaps not yet, but.....
I have used TWRP. I was on CWM Touch, downloaded and installed the TWRP from google play. Rebooted into recovery, created backups to internal and external, and flashed SkyICS 4.2f6 by Seanz. I followed OP instructions on how to flash. Did not have any problems and it was very easy to use.
Used TWRP and flashed several MODS without any hitch. All I did was reboot into recovery selected the zip files and swipe to install, did not even had to wipe cache or anything. I am not sure if this is the correct way but I was able to flash 8 other MODS doing this.
Here is what don't like:
I wanted to install the same rom but to do a clean wipe since the rom had several updates. I rebooted into recovery to TWRP, did OP flashing instructions which were:
-reboot into team win recovery
-wipe system
-factory data reset
-then go to mounts and choose external sd
-no go back and find the rom by choosing install zip
-swipe to confirm
-then install the radio you downloaded
and when complete reboot phone
-at this point everything will be settling and caching
which may or may not seem laggy.... and yes that white line is normal
its a battery representation mod
-im sure youll be eager to update busybox immediatly but let me tell you no
first open super user app.. find preferences and update user binary
hit it twice giving it root permissions
now .. is when to update busy box through the provided installer
-after you have done this
-power down phone
reboot into recovery and flash the latest update
and email package only
However, I was not able to reboot into recovery. I have a Samsung Skyrocket but was not able to put the phone into recovery mode by pressing and holding the power, volume up, and volume down buttons. The phone kept vibrating but the Samsung screen wont come up. Frustrated, I rebooted the phone, downloaded CWM, updated to Touch and proceeded to flash using CWM with no problems.
At this point i'm hesitant on using TWRP. I am not even sure if ODIN supports it. I'm afraid that if i'm on TWRP and brick my phone, I will not be able to use ODIN.
Good luck and please press thanks if this was useful.
Using SeanZ SKYICS Dragon 4.2F6-2.2A
on Samsung Skyrocket
Click to expand...
Click to collapse
If you install goo manager and install the recovery script from the haptick bottom left button, the easiest way to start from recovery is from goo manager or from from manager without the annoying recovery start with the power and volume up + down. Twrp is the smoothest way of flashing , back up and recovery.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
TWRP 2.2 is awesome. Very easy to use and full of features. I have used it to install several updates of SKY ICS 4.2F and CM9 nightlies for my Skyrocket with out a hitch. I prefer it to my older recovery (Clockworkmod Touch Recovery v5.8.1.3 )
For users that can't get into recovery from a complete power down, it would appear that you have a bad TWRP install and/or you are not using the proper key combinations. I suggest the following:
How to Install TWRP via GooManager?
1. Install the GooManager app from Market (Play Store) or install from SD card.
2. Open GooManager
3. Tap menu and hit Install OpenRecoveryScript
4. Tap Yes
5. Verify that the filename displays your device's code name and hit Yes
6. The file will download and your device will install the recovery automatically.
How to boot into recovery only?
1. Unplug USB
2. Take the battery out and place it back.
3. Hold both Vol up + Vol down buttons, press the Power button
4. Release the Power button after one beep.
Another vote for TWRP. First discovered via Rev. Kyle on my HP Touchpad.
Install using GooManager and does everything I want it to do.
Sent from my SAMSUNG-SGH-I727 using xda premium
mindmajick said:
User error
Twrp works fine.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I don't think so.. it's not difficult to use it just doesn't always work. I really liked having a file manager on board though.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Its worked for me on every rom every time. Used it to flash everything under the sun.
User error.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mr_magoo said:
I personly don't like TWRP it still has issues for me as well. I have had to flash more then once cuz it did not take. I went back to touch and it flashes every time on the first shot. It looks cool but still needs work.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
User error I've flashed a ton of ROMs 100% of the time it works all of the time
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Illnevertell said:
User error I've flashed a ton of ROMs 100% of the time it works all of the time
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
User error is not it several people have had issues with twrp. If so then explain to me what I did wrong? I wipe everything and install just like I do with touch. It never fails with touch but has at least twice with twrp. Maybe it doesn't like my phone ... But don't be trying to say I'm doing something wrong I been flashing for a long time..
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
you could of had the infamous "sticky power button" , seems more than one user is having this prob and blame it on the recovery, cwm or twrp, or a bad flash.
if you get the vibration, but does not enter in recovery or dl mode, or bootloops, could be sticky power button.
mr_magoo said:
U r a putz. User error is not it several people have had issues with twrp. If so then explain to me what I did wrong? I wipe everything and install just like I do with touch. It never fails with touch but has at least twice with twrp. Maybe it doesn't like my phone ... But don't be trying to say I'm doing something wrong I been flashing for a long time..
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Maybe you aren't waiting long enough for the install to settle.
Hes not being "a putz".. just because other people have the same problem doesnt mean its not user error or misinformation. I mean, come on.. i read these threads religiously and have given up correcting all the misinfo that gets shared as fact.
Don't take it personally.. I've been flashing a long time too. AND I've committed user errors. No one is immune. Impatience is usually the biggest err. You know why i don't help people as much as i used to? Its the insulting posts and threats that come with telling someone the right way to fix something.
Edit: "user error" is not an insult. But please refrain from calling people names. THAT is insulting.
Edit2: have you ever read the skyics threads? Plenty of errors are reproduced there.. and usually its "user err". Gets confusing for the devs.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Works perfectly for me since I flashed it a few weeks ago
mindmajick said:
Maybe you aren't waiting long enough for the install to settle.
Hes not being "a putz".. just because other people have the same problem doesnt mean its not user error or misinformation. I mean, come on.. i read these threads religiously and have given up correcting all the misinfo that gets shared as fact.
Don't take it personally.. I've been flashing a long time too. AND I've committed user errors. No one is immune. Impatience is usually the biggest err. You know why i don't help people as much as i used to? Its the insulting posts and threats that come with telling someone the right way to fix something.
Edit: "user error" is not an insult. But please refrain from calling people names. THAT is insulting.
Edit2: have you ever read the skyics threads? Plenty of errors are reproduced there.. and usually its "user err". Gets confusing for the devs.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Very well. I'm sorry if I offended you. I got a little defensive. It still wasn't user error with twrp though.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Wow! You are ok. Really. Sorry for the rant too.. I've just run into quite a few unstable folks around here.
I truly respect and appreciate the apology.. thank you is all i can say.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Today I tried to do my first root/custom rom and using the Guide put together by DroidStyle (who has also been very helpful in making me understand what I'm dealing with). The rooting wasnt a problem as when I finished that I was able to restart and the phone worked fine.
I then put Beans Custom stock on my External SD (4 gigs) and used a APK installer on my phone to install EZ Recovery. I selected the first selection right across from CWM and clicked flashed which said it was successful, and then did reboot recovery.
I then went to do a Nandroid Backup which seemed to go well until it threw an error saying it was skipping apps and something about "SD/Android_Secure". I did search the forums and it seems these shouldn't be a problem so I continued. I then went to the Wipe Data and that said it completed successfully. Finally I chose the install .zip from sd and I selected the BeanCustomStock which was sitting in the root directory of my external SD card.
After that said it was successful, I then chose reboot system from the menu but then when it restarts I seem to have a problem. It just comes back to the recovery screen and says theres an error with the SD card:
Error processing ROM Manager script. Please verify that you are performing the backup, restore, or ROM installation from ROM Manager v4.4.0.0 or higher.
I am hoping I am just overlooking something or its a simple fix. I would really appreciate any help anyone can give me as Im pretty clueless as what to do next.
Thanks!!
Hey. I'm pretty sure it's because you flashed the 5.8.4.5 CWM. You have to make sure you're using a kexec-enabled recovery (6.0.1.0) in order for the boot process to occur. So just flash the other CWM in EZ recovery.
damasta22 said:
Hey. I'm pretty sure it's because you flashed the 5.8.4.5 CWM. You have to make sure you're using a kexec-enabled recovery (6.0.1.0) in order for the boot process to occur. So just flash the other CWM in EZ recovery.
Click to expand...
Click to collapse
When I was doing the flash/boot recovery I did select the CWM there. Will the kexec-enabled recovery (6.0.1.0) be on the drop down menu or do I have to put it there? And if so how?
I'm heading off to work right now but when I get home, I'd love to give another go. Thankfully with the guide on the forum each time I messed up I was able to get back to a working one (the first time I almost had a panic attack ).
Thanks for the quick response
You have to select cwm 6 in the drop down menu in the ez recovery app, then select flash...reboot recovery.
droidstyle said:
You have to select cwm 6 in the drop down menu in the ez recovery app, then select flash...reboot recovery.
Click to expand...
Click to collapse
Seems that was the problem. Selected CWM 6 amd the rest went easily. Thanks again. Any tips or suggestions on what to do now that I have Beans Build 7?
Thanks!
Be sure to log into Dropbox to get your 50gb upgrade!
Sadly I already have dropbox . Any other apps? I am going to have to flip through the threads in the theme section and grab some nice apps and such.
Sent from my SCH-I535 using xda app-developers app
Khishawn said:
Sadly I already have dropbox . Any other apps? I am going to have to flip through the threads in the theme section and grab some nice apps and such.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
You will still get the extra dropbox space...I did!!!
You were right. I double checked today and my drop box changed to 50 gigs! I also discovered the google now which pretty awesome. The voice works perfectly but seems glitchy with any searches I type as sometimes it doesn't do anything and I have to go back to the home screen.
After looking around it seems Google now is still in development?
Sent from my SCH-I535 using xda app-developers app
Khishawn said:
You were right. I double checked today and my drop box changed to 50 gigs! I also discovered the google now which pretty awesome. The voice works perfectly but seems glitchy with any searches I type as sometimes it doesn't do anything and I have to go back to the home screen.
After looking around it seems Google now is still in development?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
yes google now is still early in its development, but better than s-voice imo.
Hi, I've searched and can't find an answer. I've managed to root my Infuse and got Infinitum rom installed. It was working great until just this evening when Clockworkmod updated (sorry, I can't find the version number). It went into a boot loop. It took me a bit, but I managed to get it out of the boot loop and back to stock, now it's rooted again with Infinitum running again.
I'm trying to get back to a recovery point that I do have on the phone, but I can't get the phone to boot to recovery no matter what I do. When I try using the vol and power buttons combination or from ROM manager I get the same thing. It goes past the stock Samsung logo into the Galaxy S/Cyanogen(mod) logo, but freezes there.
I can, of course, take the loss of my setup and redo everything manually. I would really prefer to be able to get that backup back. I'm also concerned should I ever need to get into recovery mode for any other reason. My guess is that I need to downgrade the CWM version, but I haven't been able to find how to do it.
Can anyone give me any help? Please let me know if there's info that I can give that would be useful...I'm noobie, I know!
VyCariously said:
Hi, I've searched and can't find an answer. I've managed to root my Infuse and got Infinitum rom installed. It was working great until just this evening when Clockworkmod updated (sorry, I can't find the version number). It went into a boot loop. It took me a bit, but I managed to get it out of the boot loop and back to stock, now it's rooted again with Infinitum running again.
I'm trying to get back to a recovery point that I do have on the phone, but I can't get the phone to boot to recovery no matter what I do. When I try using the vol and power buttons combination or from ROM manager I get the same thing. It goes past the stock Samsung logo into the Galaxy S/Cyanogen(mod) logo, but freezes there.
I can, of course, take the loss of my setup and redo everything manually. I would really prefer to be able to get that backup back. I'm also concerned should I ever need to get into recovery mode for any other reason. My guess is that I need to downgrade the CWM version, but I haven't been able to find how to do it.
Can anyone give me any help? Please let me know if there's info that I can give that would be useful...I'm noobie, I know!
Click to expand...
Click to collapse
There are many layers to your questions.
You may need to read a bit more to get a better understanding.
Here is two points I can offer that may be helpful.
1. Don't use ROM Manager for the Infuse.
2. To downgrade a cwm version, you will need to flash a GB or FROYO kernel in download mode via heimdall or odin. You can also use any one of the return to stock that is flashed in download mode also.
If you think you lost recovery, try flashing the kernel for the rom you were running in cwm, if you can get back into cwm again.
qkster said:
There are many layers to your questions.
You may need to read a bit more to get a better understanding.
Here is two points I can offer that may be helpful.
1. Don't use ROM Manager for the Infuse.
2. To downgrade a cwm version, you will need to flash a GB or FROYO kernel in download mode via heimdall or odin. You can also use any one of the return to stock that is flashed in download mode also.
If you think you lost recovery, try flashing the kernel for the rom you were running in cwm, if you can get back into cwm again.
Click to expand...
Click to collapse
I believe you about the ROM Manager. Too late, unfortunately. I'll take it off.
I had the phone back to stock with Odin. I went through all of the steps that I went through to first root it and install Infinitum. I had red cwm at the time. I just can't seem to get into it now. I don't think I lost it, I'm just unsure of how to get to it, since it freezes at the cm startup. I can just power off from there after I give up waiting, and it will boot to ICS normally when I power it on normally. I have Titanium Backup Pro, and it can access the nandroid backup that I have to get the apps and data. I was just hoping to recover the whole setup. I had an issue last weekend (oops to me) when I tried to install a JB rom where it went into a boot loop. I recovered everything after backtracking like I did tonight, and was hoping to be able to do the same. Is there any hope, do you think, if I go back and return to stock and start over from the beginning again? If not, I'll just suffer and redo the whole thing.
By the way, I really appreciate you answering. I've been lurking for a few weeks, and realize that you know a LOT about these phones.
VyCariously said:
I believe you about the ROM Manager. Too late, unfortunately. I'll take it off.
I had the phone back to stock with Odin. I went through all of the steps that I went through to first root it and install Infinitum. I had red cwm at the time. I just can't seem to get into it now. I don't think I lost it, I'm just unsure of how to get to it, since it freezes at the cm startup. I can just power off from there after I give up waiting, and it will boot to ICS normally when I power it on normally. I have Titanium Backup Pro, and it can access the nandroid backup that I have to get the apps and data. I was just hoping to recover the whole setup. I had an issue last weekend (oops to me) when I tried to install a JB rom where it went into a boot loop. I recovered everything after backtracking like I did tonight, and was hoping to be able to do the same. Is there any hope, do you think, if I go back and return to stock and start over from the beginning again? If not, I'll just suffer and redo the whole thing.
By the way, I really appreciate you answering. I've been lurking for a few weeks, and realize that you know a LOT about these phones.
Click to expand...
Click to collapse
Okay, so next question. I've been reading and searching and reading some more. I can get the phone back to stock and work up again, but I still reach a point where it will freeze on the Samsung/CM startup screen. In reading the Infinitum Project thread, I found this (yes, it's pretty easy to find):
"Recovery/CWM messed up?
Here is how to fix it...
1) Download uclb3 heimdal by qkster
2) open the program
3) put phone in download mode
4) click flash (leave program open when finished DO NOT CLOSE)
5) after it finishes and your phone reboots, put the phone back in download mode and reconnect to PC
6) click flash bootloader on the heimdal program you left running
7) flash, let reboot and your recovery problems should be gone"
I used that to get back to stock before...doesn't that remove the root? Do I have to go through all that, then the bootloaders, and then go back and root all over again to get back to a working CWM? I'm sorry to ask so many questions, but it seems that I've done most of this already, though I admit to not doing the flash for the bootloader. I'm just unclear since it says "your recovery problems should be gone" at the end of that, like I have to do nothing more.
That does remove root access. However, root isn't really necessary, at least for the stock ROM, if you have no intentions of staying stock. The ROM .zips you'll subsequently flash are pre-rooted. After you Heimdall back to stock, and flash it again with "flash bootloaders" selected, then use Heimdall to flash this kernel:
http://d-h.st/6KA
That'll flash both a new kernel and CWM Red recovery. It'll take a few minutes to boot up the first time, as it's installing the lagfix. Once it boots up, just shut it down and boot back up in recovery. From there, you can do whatever you need to do.
VyCariously said:
Okay, so next question. I've been reading and searching and reading some more. I can get the phone back to stock and work up again, but I still reach a point where it will freeze on the Samsung/CM startup screen. In reading the Infinitum Project thread, I found this (yes, it's pretty easy to find):
"Recovery/CWM messed up?
Here is how to fix it...
1) Download uclb3 heimdal by qkster
2) open the program
3) put phone in download mode
4) click flash (leave program open when finished DO NOT CLOSE)
5) after it finishes and your phone reboots, put the phone back in download mode and reconnect to PC
6) click flash bootloader on the heimdal program you left running
7) flash, let reboot and your recovery problems should be gone"
I used that to get back to stock before...doesn't that remove the root? Do I have to go through all that, then the bootloaders, and then go back and root all over again to get back to a working CWM? I'm sorry to ask so many questions, but it seems that I've done most of this already, though I admit to not doing the flash for the bootloader. I'm just unclear since it says "your recovery problems should be gone" at the end of that, like I have to do nothing more.
Click to expand...
Click to collapse
As Apex pointed out, each time we bring the phone back to stock, we lose root access and all the previous setup. It's a fact of flashing.
No big deal though, rooting is easy and is not really needed. What is needed is the insecure kernel with cwm. The link Apex gave you is the same as the posted kernel in post #2 of the thread. That kernel will give you the cwm. Review that thread if you haven't yet.
Flash the heimdall uclb3 repartition package. Immediately after it successfully boot your phone, don't close the program. check the bootloader box and put the phone back into dl mode and flash it again to get your gb bootloaders...
then flash the kernel.
review my how to thread if you need to.
Andros11 also made a how to for JB if you want to live vicariously.
gl
qkster said:
Andros11 also made a how to for JB if you want to live vicariously.
gl
Click to expand...
Click to collapse
Thanks guys
It's been a crazy busy week and I just didn't have time to deal with the phone. I've been dealing with stock gingerbread. It's getting kind of annoying, though, it seems less stable than the custom ICS that I had on it before. Not sure when I'm going to have time to play with it again and try to get it to where I want it. I think I'm going to try to totally wipe all of the old stuff out of the memory before I do it again, though. There's something that wasn't allowing me to do what you guys are telling me to do successfully. I'm also thinking of finding a GS2 and just selling the Infuse, not because of my confusion, but because the GS2 was what I was originally looking for anyway.
I'll try to get this one set up first, though, as it's just a matter of me being obsessive about it.
qkster, I'll look into the JB, too, lol.
qkster said:
As Apex pointed out, each time we bring the phone back to stock, we lose root access and all the previous setup. It's a fact of flashing.
No big deal though, rooting is easy and is not really needed. What is needed is the insecure kernel with cwm. The link Apex gave you is the same as the posted kernel in post #2 of the thread. That kernel will give you the cwm. Review that thread if you haven't yet.
Flash the heimdall uclb3 repartition package. Immediately after it successfully boot your phone, don't close the program. check the bootloader box and put the phone back into dl mode and flash it again to get your gb bootloaders...
then flash the kernel.
review my how to thread if you need to.
Andros11 also made a how to for JB if you want to live vicariously.
gl
Click to expand...
Click to collapse
Hey I am not the Infuse user... But I faced similar problem in my xperia some days back after updating the recovery.
I was also not able to enter recovery at boot time using my usual volume down way...
What the change was the new recovery checks for tap on the screen (repeatetive) instead of volume down button...
Not sure if it will work or not for you... But you can give a try...
Hit thanks if it works
Sent from my MT11i using xda app-developers app
XperiaNeoVNoob said:
Hey I am not the Infuse user... But I faced similar problem in my xperia some days back after updating the recovery.
I was also not able to enter recovery at boot time using my usual volume down way...
What the change was the new recovery checks for tap on the screen (repeatetive) instead of volume down button...
Not sure if it will work or not for you... But you can give a try...
Hit thanks if it works
Sent from my MT11i using xda app-developers app
Click to expand...
Click to collapse
I didn't get a chance to try it, sorry! I ended up wiping my phone totally back to stock Gingerbread with nothing on the sd card, either, and starting all over again. It seems to be working really well this time (fingers crossed). RemICS-UX is pretty much awesome
VyCariously said:
I didn't get a chance to try it, sorry! I ended up wiping my phone totally back to stock Gingerbread with nothing on the sd card, either, and starting all over again. It seems to be working really well this time (fingers crossed). RemICS-UX is pretty much awesome
Click to expand...
Click to collapse
No probs...
:thumbup:
Sent from my MT11i using xda app-developers app
Okay, I've been running CM10 M1, and was ready to upgrade to M2 tonight.
I decided I'd go ahead and flash over to CWM 6.0.1.2 Touch while I was at it, as I would rather use a touch recovery.
Using the guide here in the first post...
http://forum.xda-developers.com/showthread.php?t=1840414
It says...
YOU MUST BE RUNNING A CUSTOM RECOVERY:
Also see his EZ-Recovery for VZW Galaxy S3 app for the easiest way to load any custom recovery you want. Please note the Touch CWM 5.8.4.9 available in the app doesn't play nice with CM10. Don't use it. I personally recommend using the CWM (non-touch) versions such as 6.0.1.2. If you prefer 6.0.1.2 Touch and want to flash it using the EZ-Recovery app using the "custom" option, simply flash this file using the app.
Click to expand...
Click to collapse
This is the file it has you download.
http://goo.im/devs/invisiblek/i535/recoveries/cwm-6.0.1.2-touch.img
Using that link you get an error,
The file you requested was not found
Lets see if we can find that for you...
Click to expand...
Click to collapse
I then backed up to this URL
http://goo.im/devs/invisiblek/i535/recoveries/
And downloaded...
cwm-6.0.1.2-touch.tar.md5
http://goo.im/devs/invisiblek/i535/recoveries/cwm-6.0.1.2-touch.tar.md5
I flashed it using Custom mode on EZ Recovery, and after rebooting into recovery, I get the "could not do normal boot" error screen, and can't do anything other than pull the battery.
I DID do a backup right before this, so what would be the best way for me to unscrew this?
Thanks for help ahead of time.
I'm pretty sure you're soft bricked. I don't think restoring your nandroid would fix this.
Follow Step #6 in droidstyle's guide(linked in my sig) and use the rooted version and start over.
For future reference .md5 files are to be flashed in Odin. That's where you went bad, flashing that md5 file thru the EZ Recovery.
Once you're back to where you were before it got fubar'd, here's the touch recovery that you can flash in EZ Recovery, https://www.dropbox.com/s/aqnnl5j8xc2u0ah/recovery-clockwork-touch-6.0.1.2-d2vzw.img (If this doesn't work I may need to re-share it. Just lemme know if it doesn't)
Thank you sir, I figured it was something like that. I'm downloading all of the files now, the rooted version is 1.5GB, so it'll be awhile.
I wonder why they haven't fixed that link in the post I quoted.
I'll post back here when I'm back on.
One more question for now, can I just get back to stock rooted, and then restore my nandroid backup, and then upgrade to M2?
Also, your download above went fine, let you know if it flashes fine.
Got it all ready to go, just one last quick question.
Isn't there a way to just flash the correct recovery via ODIN and bypass all this other stuff?
Tickle me pink, I did some googling and found this...
http://www.theandroidsoul.com/official-clockworkmod-cwm-recovery-for-verizon-galaxy-s3-guide/
Which lead me to this...
http://forum.xda-developers.com/showthread.php?t=1837605
I followed those steps instead, and flashed the correct recovery, got right back into CM10. Hope this helps someone else in the future.
How is cm10-m2? I'm thinking about jumping ship from synergy for a bit while we wait for a vzw/jb leak.
Sent from my SCH-I535 using Tapatalk 2
*edit-god damn auto correct.
I used CM10 M1 from the day after I got my phone, really had VERY few issues.
M2 so far is faster, very little lag. Battery life seems as good if not better (I had very good battery life on M1).
M1 was stable enough to run for a month, with just an occasional SOD a couple of times a week, but M2 seems to be more refined. I'm also running JUSTUNBean's Inverted GAPPS, which work perfect with it.
http://forum.xda-developers.com/showthread.php?t=1797292
Needless to say, it is damned good man. Give it a shot. Nice that a rom is this refined this early on.
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