when i install RLS 6 hyperdrive my phone starts fine but after one minute it restarts and again turns again on works fine for 30 seconds and again restart help!!!!
When posting something like this its good to know the beforehand so people know what led up to this. Did you wipe? What recovery you using? Did you follow the install instructions word for word?
SCH-I545 using Tapatalk 2
A couple of possibilities:
Make sure you wipe per the dev's recommendations prior to flashing.
Try installing with minimal mods and see if you can get it to boot. Once you flash, you can always dirty flash the same installer and pick a couple additional mods and see what's causing the issue. Some people noted they were having problems with the Walkman mod causing bootloops.
Check the MD5 of your download against what is in the OP. If you downloaded to PC then copied to SD card, check that the MD5 on the card matches that on the PC and what's online (some people had problems where the file was corrupted during transfer to phone).
Also making sure you have one of the most recent recoveries is a good thing to check. I believe I used TWRP 2.6.0.0 and it worked fine for me.
Finally, try using the stock kernel instead of stock optimized or a third party kernel. I can use stock or stock optimized, for example, but when I flash faux it bootloops about 80% of the time on my phone.
There is a good bit of info about the bootlooping issue on RLS6 in the original Hyperdrive thread. Start on page 472 and read on from there.
http://forum.xda-developers.com/showthread.php?t=2301724&highlight=bootlooping&page=472
hexitnow said:
When posting something like this its good to know the beforehand so people know what led up to this. Did you wipe? What recovery you using? Did you follow the install instructions word for word?
SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
yes i did man i swear !!!!
thanks
wontongo said:
There is a good bit of info about the bootlooping issue on RLS6 in the original Hyperdrive thread. Start on page 472 and read on from there.
http://forum.xda-developers.com/showthread.php?t=2301724&highlight=bootlooping&page=472
Click to expand...
Click to collapse
thanks but i dont think that my problem sir thanks !!! more help please?
Did you flash with twrp or cwm. Theres been a few people reporting bootloops when wiping/flashing with twrp. If so you might want to try cwm. Have been using cwm since the DX was the "it" phone. Got it on 4 devices now and have never had a single problem with it.
SCH-I545 using Tapatalk 2
i found the solution
hexitnow said:
Did you flash with twrp or cwm. Theres been a few people reporting bootloops when wiping/flashing with twrp. If so you might want to try cwm. Have been using cwm since the DX was the "it" phone. Got it on 4 devices now and have never had a single problem with it.
SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
the solution was not to install any audio mods and any players like the walkman just the samsung one thanks man !!
TWRP = bad news with HD6
Just want to say that TWRP and HD6 definitely are not playing nice together. CWM FTW!
dvdrsmth said:
Just want to say that TWRP and HD6 definitely are not playing nice together. CWM FTW!
Click to expand...
Click to collapse
I've installed HD6 twice on my phone using TWRP 2502. I followed Dev's installation instructions to the T and have had zero issues.
Includes inissac
reebz said:
I've installed HD6 twice on my phone using TWRP 2502. I followed Dev's installation instructions to the T and have had zero issues.
Click to expand...
Click to collapse
Good to know. I believe that I followed the dev instructions as well.
One time my uncle was over and I was telling him about a marital concern. He told me that I should probably not do what I had been doing and that there was probably a better way. I listened to him and life has been better. Life is full of choices.
dvdrsmth said:
Just want to say that TWRP and HD6 definitely are not playing nice together. CWM FTW!
Click to expand...
Click to collapse
I agree, like I said have been using it on multiple devices, for close to 3 years now and have never had a single problem. Tried out twrp a few weeks ago and didnt like it to much. To each his own though :thumbup:
SCH-I545 using Tapatalk 2
I have also been having difficulty with both bootloops and the phone freezing on the Samsung image and not booting past this point.
I did a full wipe including data with Twrp. After multiple attempts I'm considering switching to CWM. My question is how to I install CWM on a device without a functioning rom?
Does this require flashing back to stock with odin or is there an easier way?
Sent from my SPH-L900 using Tapatalk 2
rickt1152 said:
I have also been having difficulty with both bootloops and the phone freezing on the Samsung image and not booting past this point.
I did a full wipe including data with Twrp. After multiple attempts I'm considering switching to CWM. My question is how to I install CWM on a device without a functioning rom?
Does this require flashing back to stock with odin or is there an easier way?
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
You can flash CWM from within TWRP, just use ADB to copy the zip file onto your phone then flash, or alternatively you can use fastboot to flash a new recovery directly to the phone. Neither method needs a working ROM to accomplish.
Related
Hi everyone
I am trying to install a custom recovery on a Samsung galaxy note i717D from telus by flashing it from ODIN 3 v1.85, however, after it finishes installing, I reboot and try to go into the recovery, but instead it just loads up the stock recovery. Can someone PLEASE help me? Its driving me crazy! I tried multiple recoveries, with no luck
thanks
madmajd said:
Hi everyone
I am trying to install a custom recovery on a Samsung galaxy note i717D from telus by flashing it from ODIN 3 v1.85, however, after it finishes installing, I reboot and try to go into the recovery, but instead it just loads up the stock recovery. Can someone PLEASE help me? Its driving me crazy! I tried multiple recoveries, with no luck
thanks
Click to expand...
Click to collapse
1st which recovery r u trying to flash.
2nd if u r trying twrp i had issues with that. Flash cwm then if u want trwp flash the flashable version with cwm
Bradl79 said:
1st which recovery r u trying to flash.
2nd if u r trying twrp i had issues with that. Flash cwm then if u want trwp flash the flashable version with cwm
Click to expand...
Click to collapse
I tried the standard CWM and the touch CWM, it would flash normally in PDA mode through ODIN3 and it would say flashed successfully, but when I shut off the phone and try to enter the recovery mode, it just opens the standard android recovery instead
What OS r u using odin on?
Bradl79 said:
What OS r u using odin on?
Click to expand...
Click to collapse
Windows 8, but i dont think it's the problem because it works perfectly with my skyrocket i727. All drivers and Samsung kies are installed. My note is running stock ICS if it makes a difference.
madmajd said:
Windows 8, but i dont think it's the problem because it works perfectly with my skyrocket i727. All drivers and Samsung kies are installed. My note is running stock ICS if it makes a difference.
Click to expand...
Click to collapse
No that should not make a difference. Bc i did mine on gb and ucs stock without rooting. Did u run as administrator. And also where ru downloading the files from.
Bradl79 said:
No that should not make a difference. Bc i did mine on gb and ucs stock without rooting. Did u run as administrator. And also where ru downloading the files from.
Click to expand...
Click to collapse
I tried following this tutorial, which gave me the downloads: http://rootgalaxynote.com/galaxy-no...-on-att-galaxy-note-sgh-i717-belltelusrogers/
I also tried multiple other tuts with different files and still the same issue.
Bump
madmajd said:
Bump
Click to expand...
Click to collapse
Try this one. Let me know if it worked.
http://forum.xda-developers.com/showthread.php?t=1526431&highlight=cwm+touch
Download: http://thinkleet.de/cwm/cwm-i717-120305.tar.md5
Then flash this recovery if ur phone supposts it. Use cwm.
http://teamw.in/project/twrp2
One bump per day after 24 hours, amigo.
Anyway, you are either not following directions or have bad directions. As the phone reboots from Odin you are to pull the battery out.
rangercaptain said:
A bumbling pet day, amigo.
Anyway, you are either not following directions or have bad directions. As the phone reboots from Odin you are to pull the battery out.
Click to expand...
Click to collapse
I followed the directions exactly as mentioned, and plus I've done it like a hundred times on my other Skyrocket i727. But none of the tuts I went on said anything bout pulling out the battery tho
Bradl79 said:
Try this one. Let me know if it worked.
http://forum.xda-developers.com/showthread.php?t=1526431&highlight=cwm+touch
Download: http://thinkleet.de/cwm/cwm-i717-120305.tar.md5
Click to expand...
Click to collapse
I tried this one, didnt work unfortunately
After Odin flash while phone reboots you have to pull the battery or you just go back to stock recovery.
rangercaptain said:
After Odin flash while phone reboots you have to pull the battery or you just go back to stock recovery.
Click to expand...
Click to collapse
I've never pulled battery and haven't ever had issues installing recoveries through Odin. But it wouldn't hurt trying. Out of curiosity, what exactly does it say at the top when you boot into recovery?
Edit: just remembered that if you upgraded to ICS through via OTA, the system reverts back to stock recovery due to code that is imbedded in the ota version of the update. But this code does not exist in the update provided through Kies (what i used). This explains my not needing to do a battery pull during reboot.
Sent from my Samsung-SGH-I717 using xda app-developers app
Do you think I'm asking him to pull the battery for giggles? Watch and learn, grasshopper.
rangercaptain said:
Do you think I'm asking him to pull the battery for giggles? Watch and learn, grasshopper.
Click to expand...
Click to collapse
As I stated "I just remembered". Confirming your post. So nothing new learned for me lol. It's why I explained why a battery pull may be necessary IF the update was through OTA. If he went through kies, its due to some other reasons. Always best not to make assumptions that's why I asked the questions I did.
Hope y'all have a great Christmas!
Sent from my Samsung-SGH-I717 using xda app-developers app
Wait until all the new phones get opened today. The forum will be filled with fifty threads like this or the brick threads from wrong Roms!
MoJoe277 said:
I've never pulled battery and haven't ever had issues installing recoveries through Odin. But it wouldn't hurt trying. Out of curiosity, what exactly does it say at the top when you boot into recovery?
Edit: just remembered that if you upgraded to ICS through via OTA, the system reverts back to stock recovery due to code that is imbedded in the ota version of the update. But this code does not exist in the update provided through Kies (what i used). This explains my not needing to do a battery pull during reboot.
Sent from my Samsung-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
On the top it says "android system recovery" with no options to flash files or do a backup or anything, which means its the stock one.
MoJoe277 said:
As I stated "I just remembered". Confirming your post. So nothing new learned for me lol. It's why I explained why a battery pull may be necessary IF the update was through OTA. If he went through kies, its due to some other reasons. Always best not to make assumptions that's why I asked the questions I did.
Hope y'all have a great Christmas!
Sent from my Samsung-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
So you DO have to pull the battery out when it reboots after its done flashing?
madmajd said:
So you DO have to pull the battery out when it reboots after its done flashing?
Click to expand...
Click to collapse
Try it. If it works, great. If not, its only a couple seconds waisted. Worth a shot
Sent from my Samsung-SGH-I717 using xda app-developers app
Anyone have an idea why every time I install an aosp rom it glitches at the Samsung boot screen then just goes black and I have to pull the battery? I've installed clean, jelly beans and jedi Rom without issue. Any help is appreciated.
Update your twrp then try again. Make sure your doing full wipes and flashing gapps
Sent from my SCH-I605 using Tapatalk 2
hopesrequiem said:
Update your twrp then try again. Make sure your doing full wipes and flashing gapps
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Just updated my TWRP to 2.4 and did what you suggested with the wiping and same problem.
The Samsung Galaxy screen glitches to half way off the screen, then goes off, then comes back on then the whole thing goes black and nothing.
I'm going to try another rom and see if it still does it as well.
dudeicles said:
Just updated my TWRP to 2.4 and did what you suggested with the wiping and same problem.
The Samsung Galaxy screen glitches to half way off the screen, then goes off, then comes back on then the whole thing goes black and nothing.
I'm going to try another rom and see if it still does it as well.
Click to expand...
Click to collapse
Even with another ROM it doesn't seem to want to work. It's really weird, because any Touchwiz ROM works fine, it only does it on AOSP roms..... I'm hoping someone knows what the fix for this is.
dudeicles said:
Even with another ROM it doesn't seem to want to work. It's really weird, because any Touchwiz ROM works fine, it only does it on AOSP roms..... I'm hoping someone knows what the fix for this is.
Click to expand...
Click to collapse
Odin to stock then re unlock and try this all again? I'm not sure what else you can try. I flip between aosp and tw almost daily
Sent from my SCH-I605 using Tapatalk 2
The Note 2 that couldn't...
Sent from my SCH-I605 using Tapatalk 2
1ManWolfePack said:
The Note 2 that couldn't...
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Heh I think I can I think I can...I was thinken are you trying to flash the file that the post links to because thats not the right one you need to get the note 2 lte one tolte..just a though I downloaded the wrong one first but caught it
http://changelog.bbqdroid.org/#t0lte/cm10.1/next
in my experience, you need to do a factory wipe again AFTER you install or you will get a bootloop.
I think CM10.1 mentions that in their install process.
Acery said:
in my experience, you need to do a factory wipe again AFTER you install or you will get a bootloop.
I think CM10.1 mentions that in their install process.
Click to expand...
Click to collapse
Yeah it can't hurt even if they don't say that
Sent from my SCH-I605 using Tapatalk 2
Acery said:
in my experience, you need to do a factory wipe again AFTER you install or you will get a bootloop.
I think CM10.1 mentions that in their install process.
Click to expand...
Click to collapse
Would it help in any way to change to CWM when flashing my AOSP roms?
dudeicles said:
Would it help in any way to change to CWM when flashing my AOSP roms?
Click to expand...
Click to collapse
I would try cwm, I had a gs3 that couodnt flash anything with cwm but could with twrp, my note was the opposite, cwm was awful on it.
Just ran into something very interesting . When I installed Rom Manager and flashed the CWM recovery, I rebooted and my boot screen did the exact same thing it was doing installing AOSP roms. It would seem my problem may just be CWM.
dudeicles said:
Just ran into something very interesting . When I installed Rom Manager and flashed the CWM recovery, I rebooted and my boot screen did the exact same thing it was doing installing AOSP roms. It would seem my problem may just be CWM.
Click to expand...
Click to collapse
I've heard too many issues with cwm to even try it. Twrp has been flawless for me so why switch? If it ain't broke, don't fix it.
Sent from my SCH-I605 using Tapatalk 2
Ok, so update - Odin'd back to stock and re-rooted using the Casual method. I have the most recent TWRP installed and when i install the AOSP rom it does the exact same thing. I'm thinking about videotaping what the boot animation does and maybe someone can look at it and see what the cause may possibly be.
If anyone has any other suggestions i'm all ears. Again, any rom based on STOCK works without issue (Clean Rom, Jelly Beans and Jedi), but only AOSP roms (And CWM) crash the phone at "Samsung Galaxy Note II" screen on startup.
Thanks for the suggestions so far, just weird it's not working. I may have the single note 2 to never run AOSP roms. LOL
so... oddly enough i still have trouble installing AOSP roms. the only AOSP rom i have been able to install so far is Paranoid Droid. I am slowly trying each one just to see which one i can force to work. Am I the only person who can't just flash whichever rom I want whenever?
Anyone with other ideas on this? I was frequently flashing back and forth between TW and AOSP. The other day I tried to flash AOSP again and get a failed message in TWRP. Already using latest version of TWRP. I then restore a backup of TW. Download again, verify md5, get failed message again. And yes, I wiped everything...same thing I do everytime. Now I have tried to DL and flash multiple different AOSP roms and I get failed everytime. Decided to try CWM recovery and that just aborts. I have NO problems flashing TW roms though
Follow the advice to Odin back to stock and start over. Otherwise, get a replacement and tell them it's acting weird and slow haha.
Sent from my SCH-I605 using xda app-developers app
Same here!!
spydersilk said:
Anyone with other ideas on this? I was frequently flashing back and forth between TW and AOSP. The other day I tried to flash AOSP again and get a failed message in TWRP. Already using latest version of TWRP. I then restore a backup of TW. Download again, verify md5, get failed message again. And yes, I wiped everything...same thing I do everytime. Now I have tried to DL and flash multiple different AOSP roms and I get failed everytime. Decided to try CWM recovery and that just aborts. I have NO problems flashing TW roms though
Click to expand...
Click to collapse
I currently have a Tmobile Note 2. And i recently ran into the same issue. I think it started after installing a certain paranoid andrroid rom, which wrote OS folders differently from what i am normally used to seeing. The folders were 0, legacy, and obb. I also notice that it changed my device id to an SGH-i317, which is an ATT Note 2. The rom was a port from an ATT rom of course, but if it was for ATT, it wouldn't work on my device right? I installed GOOmanager, and flashed the OPEN INSTALL SCRIPT. Which it flashed the ATT version. Everything still worked. I flashed back to stock, and updated OTA. Still nothing. I've also noticed that, if i can open the zip file on my pc, it will work on my phone. For some reason, The AOSP files read invalid. While the Touchwiz roms open like a regular zip file.
Any help is appreciated. Hope some of this info helps.
Just realized i posted in the Verizon section. But i think you and I are the only two people with this issue...lol
slinky42 said:
I think it started after installing a certain paranoid andrroid rom, which wrote OS folders differently from what i am normally used to seeing. The folders were 0, legacy, and obb.
Just realized i posted in the Verizon section. But i think you and I are the only two people with this issue...lol
Click to expand...
Click to collapse
This is standard on 4.2.2 ROMs. It is related to the multi-user implementation.
slinky42 said:
I currently have a Tmobile Note 2. And i recently ran into the same issue. I think it started after installing a certain paranoid andrroid rom, which wrote OS folders differently from what i am normally used to seeing. The folders were 0, legacy, and obb. I also notice that it changed my device id to an SGH-i317, which is an ATT Note 2. The rom was a port from an ATT rom of course, but if it was for ATT, it wouldn't work on my device right? I installed GOOmanager, and flashed the OPEN INSTALL SCRIPT. Which it flashed the ATT version. Everything still worked. I flashed back to stock, and updated OTA. Still nothing. I've also noticed that, if i can open the zip file on my pc, it will work on my phone. For some reason, The AOSP files read invalid. While the Touchwiz roms open like a regular zip file.
Any help is appreciated. Hope some of this info helps.
Just realized i posted in the Verizon section. But i think you and I are the only two people with this issue...lol
Click to expand...
Click to collapse
Did you ever get your phone to install the AOSP Roms? Mine worked when l just let the phone sit. Now it works fine all the time.
Sent from my SCH-I605 using xda app-developers app
Currently have TWR recovery I flashed using goomanager but have been hearing bad thing about it. Can I just download Rom Manager from the play store and use it to flash clockwork or do I need to us another way to flash it ? Thanks !
If TWRP works fine for you then who cares what other people say or think about. I only run TWRP and have no issues with it.
Don't just go by what other people say, check out some videos on YouTube of ClockworkMod and see if it's for you. Very recently, an official CWM build appears to have become available so if you want to use that, it should be as simple as downloading ROM Manager and doing recovery setup.
I havent used TWR to flash anything yet just used it to to a backup of my stock rooted rom. Thanks for the replys.
mbh87 said:
If TWRP works fine for you then who cares what other people say or think about. I only run TWRP and have no issues with it.
Click to expand...
Click to collapse
I've ran both on multiple devices and i also prefer twrp. It's laid out nicer. Being able to wipe cache and dalvik in one shot or at least in one menu screen is way more convenient than them being separate options on separate screens.
sent from my Galaxy S4 using xda premium
+1 agree
Sent from my SCH-I545 using Tapatalk 2
I've had this 4-5 times now, with various ROMs, tried CM10.1, 10.2 most recently. Basically the phone randomly stops booting, I can get to the recovery fine, but booting to system gets stuck on the Galaxy S4 Logo screen. Tried dalvik / cache wipes, permission fix, nothing helps.
Firstly, unless I completely wipe data (full wipe including /data/media), I can't seem to be able to install a new ROM. If I dirty flash everything works fine, but if I do a factory reset, I will get stuck on the logo at boot. Then even after I have successfully installed a ROM, I will sometimes randomly get stuck on reboots, and nothing but another full wipe will fix this. Is this an issue with the TWRP recovery? or is my internal memory fudged and getting corrupt ?
edit: See my post here for details on what I've found so far, I may have fixed the problem but needs more testing http://forum.xda-developers.com/showthread.php?t=2397438&page=2
TWRP!!!!
SellswordShev said:
I've had this 4-5 times now, with various ROMs, tried CM10.1, 10.2 most recently. Basically the phone randomly stops booting, I can get to the recovery fine, but booting to system gets stuck on the Galaxy S4 Logo screen. Tried dalvik / cache wipes, permission fix, nothing helps.
Firstly, unless I completely wipe data (full wipe including /data/media), I can't seem to be able to install a new ROM. If I dirty flash everything works fine, but if I do a factory reset, I will get stuck on the logo at boot. Then even after I have successfully installed a ROM, I will sometimes randomly get stuck on reboots, and nothing but another full wipe will fix this. Is this an issue with the TWRP recovery? or is my internal memory fudged and getting corrupt ?
Click to expand...
Click to collapse
I'm having the same [email protected]#$%^& problem!!!! you're using TWRP aren't you?
i finished reading your post after I was done and saw that you ARE using TWRP...
thepianoman77 said:
I'm having the same [email protected]#$%^& problem!!!! you're using TWRP aren't you?
i finished reading your post after I was done and saw that you ARE using TWRP...
Click to expand...
Click to collapse
yep I was on TWRP 2.5.0.2, I just read that its got some stability problems with /data, just flashed v2.6 hopefully this fixes it
SellswordShev said:
yep I was on TWRP 2.5.0.2, I just read that its got some stability problems with /data, just flashed v2.6 hopefully this fixes it
Click to expand...
Click to collapse
oh dude.... I was on v2.6... I think we have an issue.
That is why I use cwm. Been using it for 3+ years on 4 different devices. Never have I had one problem with it.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
That is why I use cwm. Been using it for 3+ years on 4 different devices. Never have I had one problem with it.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
i had a very bad experience with CWM... never using it again man.... no way.
thepianoman77 said:
i had a very bad experience with CWM... never using it again man.... no way.
Click to expand...
Click to collapse
Lol ok :thumbup:
Sent from my SCH-I545 using Tapatalk 2
I've been using TWRP too. I panicked last night when I couldn't boot at all. I couldn't even get to recovery. I then tried the no wipe odin without luck. I finally got the stock odin image to work but I've been having serious issues with booting on this phone since I got it this weekend and it could be TWRP I suppose. I was using it on my note 2 with no issues. Very strange. I'm back to stock and running fine now.
Sent from my SCH-I545 using xda premium
Still having odd issues with TWRP after updating to 2.6, getting stuck on boot as before, and sometimes flashing a ROM will just fail and the data partition becomes read only, and I can't push anything to it till I reformat /data.
Going to try CWM today, really hope this is just a recovery issue. Are there any tests to check the health of on board memory? I am really hoping I don't have bad hardware here.
Im having the same issue just made a thread fir it guess I will delete since I found this. Hope someone figures it out. What root/ recovery method did you all use. Was it the auto script?
Sent from my SCH-I545 using xda premium
ruffneckZeVo said:
Im having the same issue just made a thread fir it guess I will delete since I found this. Hope someone figures it out. What root/ recovery method did you all use. Was it the auto script?
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
Root / recovery methods will be the same for everyone, regardless of what guide / thread you followed, in the end you will have a loki-patched recovery and kernel, as thats the only way to run unsigned images on these phones. Whats relevant here is which recovery and kernel you are using, as these are the only 2 things that could effect errors in the boot logo state (aka freezes before the ROM boot animations kick in). Ive been looking through various ROM threads of people reporting this issue and its pretty widespread, and usually is linked to recoveries rather than ROMs. If you can post your recovery + ROM here that would be helpful. Here is what I've done so far:
I was initially on TWRP 2.5.0.2, which had possible bugs that could corrupt /data, leading to failed flashes, and being unable to read/write from /data entirely (including /sdcard). After switching to 2.6.0.0 I was still getting stuck on the boot animation. (All of this running the CM10.2 ROM with the stock kernel here http://forum.xda-developers.com/showthread.php?t=2384470). Note I did not do a full wipe after switching to 2.6.0.0, so that recovery MAY still be ok if someone wants to test it out.
I am now running CWM (official installed off ROM Manager). After flashing this I did a full re-format (/system, /data (including /data/media), etc.). And so far I haven't had any problems, going to do some more fiddling / flashing tonight to try and see if its really fixed, but I know for sure that atleast the reboot bug is gone.
So my advice is to flash the official CWM recovery, do a full re-format using that recovery, and then re-install your ROM.
I had that same /data issue with TWRP. It worked perfect for a few months and then suddenly it happened. I enjoyed TWRP for the 10 minute backups and restores, but i'd rather put up with CWM's 30 minute backup and restores if that will mean it wont happen again. Currently running PhilZ Touch Recovery and its been perfect so far!
Monkz said:
I had that same /data issue with TWRP. It worked perfect for a few months and then suddenly it happened. I enjoyed TWRP for the 10 minute backups and restores, but i'd rather put up with CWM's 30 minute backup and restores if that will mean it wont happen again. Currently running PhilZ Touch Recovery and its been perfect so far!
Click to expand...
Click to collapse
Have you tried any 4.3 ROMs with the PhilZ recovery? There seem to be some issues there. Still that recovery may be a good solution for those on 4.2 having this problem. I'm gonna try and loki patch the official CWM touch tonight if I don't run into this bug again, using the volume buttons is so bloody painful lol.
SellswordShev said:
Have you tried any 4.3 ROMs with the PhilZ recovery? There seem to be some issues there. Still that recovery may be a good solution for those on 4.2 having this problem. I'm gonna try and loki patch the official CWM touch tonight if I don't run into this bug again, using the volume buttons is so bloody painful lol.
Click to expand...
Click to collapse
None of my ROMs are 4.3, but i know the one i'm using is soon to be updated, so i will know if it works or not when it gets updated to 4.3. But no issues on 4.2.2 ROMS as of yet with PhilZ.
Monkz said:
None of my ROMs are 4.3, but i know the one i'm using is soon to be updated, so i will know if it works or not when it gets updated to 4.3. But no issues on 4.2.2 ROMS as of yet with PhilZ.
Click to expand...
Click to collapse
is PhilZ a recovery?
thepianoman77 said:
is PhilZ a recovery?
Click to expand...
Click to collapse
Yes its a custom build of CWM maintained by an xda dev here http://forum.xda-developers.com/showthread.php?t=2322675
Im still having the issue with philz. Everything was fine for the first 4-5 weeks. Now about every 3rd reboot or if battery dies I have to wipe data and nandroid. Im running stock with several tweaks. Going to try and odin restore to stock re root snd install cwm tonight and see if that helps will report back
Sent from my SCH-I545 using xda premium
Alright, I'm almost 99% sure this problem is gone after I switched to the official CWM. I've tried everything from restoring nandroids to flashing TWiz / AOSP 4.2 and 4.3 ROMs, everything boots and reboots and /data is no longer getting corrupt. I also loki patched the official CWM touch recovery (the one on their site is not patched), and flashed + used it successfully. Its pretty simple to do this, just follow the guide here: https://github.com/djrbliss/loki and use this recovery: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.3.2-jfltevzw.img
The only issue I've been having is that when I reboot to recovery, it sometimes gets stuck and I have to do a battery pull and go back into recovery.
Sent from my SCH-I545 using Tapatalk 4
I'm having the same issue on TWRP 2.6. Tried with multiple ROMs. Everytime I reboot I have to format /Data. So frustrating. I will try CWM now.
So I had originally had TWRP/Hyperdrive on my phone, and switched to CWM/Cyanogenmod. I noticed now that I seem to have two different recoveries on my phone, because if I hold up+home+power I can go to a different version of CWM Recovery than if I use the Rom Manager app to boot into recovery. How would I rectify this? Would it involve wiping the /boot partition? I don't know where/how recoveries are stored so I don't understand how I can have two.
Doing a fresh install of a ROM has not resolved this by the way. And actually currently, I can't hold the buttons and boot into recovery at all, it gets stuck on the Samsung logo. I can only get into recovery via Rom Manager or Reboot options if I'm in android.
Markstache said:
So I had originally had TWRP/Hyperdrive on my phone, and switched to CWM/Cyanogenmod. I noticed now that I seem to have two different recoveries on my phone, because if I hold up+home+power I can go to a different version of CWM Recovery than if I use the Rom Manager app to boot into recovery. How would I rectify this? Would it involve wiping the /boot partition? I don't know where/how recoveries are stored so I don't understand how I can have two.
Doing a fresh install of a ROM has not resolved this by the way. And actually currently, I can't hold the buttons and boot into recovery at all, it gets stuck on the Samsung logo. I can only get into recovery via Rom Manager or Reboot options if I'm in android.
Click to expand...
Click to collapse
I would just Odin back to stock MDK and start fresh and choose whichever recovery suits you. I had to do the same a while back myself
Sent from my SCH-I545 using Tapatalk
Mistertac said:
I would just Odin back to stock MDK and start fresh and choose whichever recovery suits you. I had to do the same a while back myself
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I've done that so many times.
Markstache said:
I've done that so many times.
Click to expand...
Click to collapse
My fault ...I see where you adressed that in the last part of your post. I'm no expert either on how recoveries are stored and executed.
I would think though that flashing stock mdk would fix this as it did for me. I used ROM manager to install cwm then I flashed Philz and haven't had a problem since. Hope someone else can help you.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
My fault ...I see where you adressed that in the last part of your post. I'm no expert either on how recoveries are stored and executed.
I would think though that flashing stock mdk would fix this as it did for me. I used ROM manager to install cwm then I flashed Philz and haven't had a problem since. Hope someone else can help you.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
The only way to fix is to Odin back to factory image and start over.
Sent from my SCH-I545 using xda app-developers app
cbmggm said:
The only way to fix is to Odin back to factory image and start over.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Yea that's what I said before too but the op said they've done that many times with no luck...
Sent from my SCH-I545 using Tapatalk
cbmggm said:
The only way to fix is to Odin back to factory image and start over.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
That's what I would have figured would fix it, because I'm pretty sure that's supposed to wipe /boot, but I found out I cannot flash kernels on my phone for some reason and when having to fix softbricks while experimenting with why it doesn't work and flashing different kernels, I had to do that whole process so many times I can go from softbrick back to where I'm at now in about 20 minutes.
Is your device in factory mode when using touchwiz roms?
jamesd1085 said:
Is your device in factory mode when using touchwiz roms?
Click to expand...
Click to collapse
I have no idea what you mean, and I'm not using anything touchwiz based anymore.
Markstache said:
I have no idea what you mean, and I'm not using anything touchwiz based anymore.
Click to expand...
Click to collapse
OK...well try something real quick for me...use a root manager and open your efs folder...are the files still there...if not your efs folder has been formatted to the incorrect format... That would explain funky recovery issues and not being able to flash kernels...that's the only things I can think of
jamesd1085 said:
OK...well try something real quick for me...use a root manager and open your efs folder...are the files still there...if not your efs folder has been formatted to the incorrect format... That would explain funky recovery issues and not being able to flash kernels...that's the only things I can think of
Click to expand...
Click to collapse
It sure is there and has files in it.
What is that folder? Should I delete the contents?
Markstache said:
It sure is there and has files in it.
What is that folder? Should I delete the contents?
Click to expand...
Click to collapse
Definitely don't delete your efs folder. Actually it's good practice to back it up
Sent from my SCH-I545 using Tapatalk
Markstache said:
It sure is there and has files in it.
What is that folder? Should I delete the contents?
Click to expand...
Click to collapse
No!!!!...you will lose your number and all data capability...just wanted to make sure everything was still mounting properly... I'm at a loss as to what else could be causing your issues
Markstache said:
I have no idea what you mean, and I'm not using anything touchwiz based anymore.
Click to expand...
Click to collapse
I'd find someone like Philz or a TWRP compiler to ask if u haven't already gone that route. I'm sure one of them will know. Hopefully [emoji41]
Sent from my SCH-I545 using Tapatalk
Something just occured to me. When flashing back to stock with odin I always use the nowipe image because it's all I can find. I think that technically means boot was never wiped. Would that explain my phenomena? Also where to find stock that will wipe?
Markstache said:
Something just occured to me. When flashing back to stock with odin I always use the nowipe image because it's all I can find. I think that technically means boot was never wiped. Would that explain my phenomena? Also where to find stock that will wipe?
Click to expand...
Click to collapse
I've always used this one
http://forum.xda-developers.com/showthread.php?t=2289325
I'm not 100% if its no wipe as it doesn't say. But it you haven't tried this one yet may be worth a shot
Sent from my SCH-I545 using Tapatalk
Mistertac said:
I've always used this one
http://forum.xda-developers.com/showthread.php?t=2289325
I'm not 100% if its no wipe as it doesn't say. But it you haven't tried this one yet may be worth a shot
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
^^^this should fix you up...but backup everything you can to external SD or computer...when it says full wipe its no joke
Mistertac said:
I've always used this one
http://forum.xda-developers.com/showthread.php?t=2289325
I'm not 100% if its no wipe as it doesn't say. But it you haven't tried this one yet may be worth a shot
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
So I flashed that one via Odin, followed the guide to root and everything step by step, and now that I'm back on stock kernel and want to install CWM Recovery, I downloaded Rom Manager and hit install recovery and it says everything worked but if I boot into recovery it's just the android stock recovery.
EDIT: Another thing I thought of. Could the fact that at one point I used this method to install CWM recovery on my phone have caused there to be two different recoveries running parallel?
http://galaxys4root.com/galaxy-s4-r...on-att-or-verizon-galaxy-s4-sgh-i337sch-i545/
UPDATE: Using this method I installed the latest version of CWM Recovery Touch but Rom Manager still thinks the normal version is installed, though now if I hit reboot to recovery from the app it actually takes me to the touch instead of a separate one. Is the app dumb or do I still have an issue? Also I cannot install kernels without tripping the count and having my phone tell me I need to go to a verizon store.
http://wiki.cyanogenmod.org/w/Install_CM_for_jfltevzw
Markstache said:
So I flashed that one via Odin, followed the guide to root and everything step by step, and now that I'm back on stock kernel and want to install CWM Recovery, I downloaded Rom Manager and hit install recovery and it says everything worked but if I boot into recovery it's just the android stock recovery.
EDIT: Another thing I thought of. Could the fact that at one point I used this method to install CWM recovery on my phone have caused there to be two different recoveries running parallel?
http://galaxys4root.com/galaxy-s4-r...on-att-or-verizon-galaxy-s4-sgh-i337sch-i545/
UPDATE: Using this method I installed the latest version of CWM Recovery Touch but Rom Manager still thinks the normal version is installed, though now if I hit reboot to recovery from the app it actually takes me to the touch instead of a separate one. Is the app dumb or do I still have an issue? Also I cannot install kernels without tripping the count and having my phone tell me I need to go to a verizon store.
http://wiki.cyanogenmod.org/w/Install_CM_for_jfltevzw
Click to expand...
Click to collapse
ROM manager may actually be the issue.
And as far as installing kennels I've never had an issue myself. The last link you posted is about flashing the md2 kernel in order to root the phone. Do you mean that?? Or installing say a KToonsez kernel after you're already rooted and have your custom recovery?
Sent from my SCH-I545 using Tapatalk
Mistertac said:
ROM manager may actually be the issue.
And as far as installing kennels I've never had an issue myself. The last link you posted is about flashing the md2 kernel in order to root the phone. Do you mean that?? Or installing say a KToonsez kernel after you're already rooted and have your custom recovery?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
As in installing a KT kernel after rooting and having a custom recovery and ROM on my phone. Right now I have three 3/22 nightly cyanogen up and running but as soon as I install kt it trips the Verizon security and on have to flash back to stock kernel to use my phone. Booting into Odin and canceling out to restart does not let me get past the yellow triangle