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
Related
i am stuck. i tried to flash super charged hatka 320 dpi and i have gone in the wrong direction because my dna doesnt boot up properly. after super hatka gets past the boot i am able to get to the lock screen and once i swipe to unlock, it says unfortunately settings have stopped working. my launcher doesnt work. i cant operate the phone what so ever except for looking at the settings. when i get a text message i can reply, but thats pretty much it. i have experience in rooting and flashing the htc g2, gs2, and the gnexus. but this htc dna is something different and i am having extreme difficulties. i can go into much more detail if someone has the moment to help me out
Maybe if you try to re-install the Rom will all be ok....it might solve the problem...did you do a proper wipe before flashing...and did you create a nandroid backup if so restore it in Recovery and then flash the Rom again...if. not first do a proper wipe and then reflash the Rom....I use viperdna so I don't know if you have after the install to flash any kernel,fix or something???check it first and then procceed with the other things..hope to helped yiu
Sent from my HTC Droid DNA
If you came from another ROM or Stock, Factory Data Reset from recovery is advised ... you could also try flashing another custom ROM to get moving
Djmk4 said:
Maybe if you try to re-install the Rom will all be ok....it might solve the problem...did you do a proper wipe before flashing...and did you create a nandroid backup if so restore it in Recovery and then flash the Rom again...if. not first do a proper wipe and then reflash the Rom....I use viperdna so I don't know if you have after the install to flash any kernel,fix or something???check it first and then procceed with the other things..hope to helped yiu
Sent from my HTC Droid DNA
Click to expand...
Click to collapse
i have tried to reinstall it, same problem. this happenes when aroma was finishing the install of the rom
<..simmer down..>
.
..
removing old init.d files...
sqlite3 exists
set_perm:some changes failed
installation failed
error
senseless slim super charged hatka dna v2.1.0
install failed
installer status: 7
i want to install a different rom, idc what rom, but i cant download anything, i tried chrome and iE but none of them will download any roms. does anyone have an alternate link to a rom that isnt linked here on xda?
and i was coming from stock. i certainly wiped cache and factory reset before flashing the rom. i used flash image gui to flash the bootimg and then wiped everything in cwm, the flashed module zip and then flashed the rom. thats pretty much what i did, i do appreciate your replies
dj2muchxx said:
i have tried to reinstall it, same problem. this happenes when aroma was finishing the install of the rom
<..simmer down..>
.
..
removing old init.d files...
sqlite3 exists
set_perm:some changes failed
installation failed
error
senseless slim super charged hatka dna v2.1.0
install failed
installer status: 7
i want to install a different rom, idc what rom, but i cant download anything, i tried chrome and iE but none of them will download any roms. does anyone have an alternate link to a rom that isnt linked here on xda?
Click to expand...
Click to collapse
What's happening mate...really can't help you...the only thing I suggest to write exactly what you wrote here in hatka's Rom thread...maybe the dev that made the Rom....can help you or someone might had the same issue
Sent from my HTC Droid DNA
What recovery are you using? I had an issue with twrp at first and switched to cwm touch. And no issues. I've had issues though by going back after getting stuck at boot and wiped then installed Rom with full wipe. But if its an error not installing might try fastboot flashing a different recovery
Sent from my HTC6435LVW using xda premium
dj2muchxx said:
and i was coming from stock. i certainly wiped cache and factory reset before flashing the rom. i used flash image gui to flash the bootimg and then wiped everything in cwm, the flashed module zip and then flashed the rom. thats pretty much what i did, i do appreciate your replies
Click to expand...
Click to collapse
I think it might be a problem with the download I will fix it later today
Sent from my HTC6435LVW using xda app-developers app
fixed
i may have had a bad download. i was using the 320 dpi senseless rom, my phone was unusable like i had stated, but i managed to get it running.
here is what i did to fix it:
in the settings, i linked my dna with my google account, and as i expected, i received play store notifications about updates, so i chose the notification and it took me to a fully functioning play store.
i downloaded apex launcher and it installed properly. pressed the home button and it automatically set itself as the default launcher and bam! my dna was beginning to function.
downloaded xda app and went to the super charged thread and downloaded the slim version of the rom instead of the senseless rom.
flashed the boot.img, flashed the modules, then flashed the slim rom and i didnt get any errors or failed messages this time.
i dont want to point fingers and i would never do that here on a fantastic community, but the senseless rom was giving me issues, maybe it just needs some more work. anyways phone is functioning like normal now, everything works and the battery is outstanding so far.
thank you to those for the advice. i was getting ready to call it quits and send this thing back to amazon wireless.
MustafaHadaKing said:
I think it might be a problem with the download I will fix it later today
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
i think it was just the rom, if u need a guinea pig to test out your rom or anything, im in. i am enjoying super charged hatka very much:good:
There were two main roms I wanted to try after I finally S-OFF'd my phone yesterday. Hatka Supreme 1.1.0 and Carbon. Neither of these worked and I'm glad that I backed up my S-OFF rooted stock rom. Hatka Supreme, the guy states its best to use Beast Mode kernal with the rom, which I flashed after I installed the room, and it just randomly reboots at the splash screen/a few seconds after getting into Android, so I restored my stock and everything worked fine. Next, I tried Carbon, and it just sat there at the carbon flash screen for like 20 minutes, so again, I had to restore to stock. Is there something I'm doing wrong? Is there a difference between Original Android Development and Android Development? Should I be looking at the original or what? I'm really lost, I'm going to try another rom, hopefully someone replies to this before it finishes downloading. Thanks for the help.
EDIT: I'd rather just sit and wait to see if someone replies before I waste time downloading another rom...any help would be appreciated.
rejectedjs said:
There were two main roms I wanted to try after I finally S-OFF'd my phone yesterday. Hatka Supreme 1.1.0 and Carbon. Neither of these worked and I'm glad that I backed up my S-OFF rooted stock rom. Hatka Supreme, the guy states its best to use Beast Mode kernal with the rom, which I flashed after I installed the room, and it just randomly reboots at the splash screen/a few seconds after getting into Android, so I restored my stock and everything worked fine. Next, I tried Carbon, and it just sat there at the carbon flash screen for like 20 minutes, so again, I had to restore to stock. Is there something I'm doing wrong? Is there a difference between Original Android Development and Android Development? Should I be looking at the original or what? I'm really lost, I'm going to try another rom, hopefully someone replies to this before it finishes downloading. Thanks for the help.
EDIT: I'd rather just sit and wait to see if someone replies before I waste time downloading another rom...any help would be appreciated.
Click to expand...
Click to collapse
Did you do a full wipe? System, factory reset, dalvik?
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
Did you do a full wipe? System, factory reset, dalvik?
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
It's probably your recoverys fault. On my last DNA I had nothing but failures. Once it took at least 30 times to get a Rom installed. Never solved the issue on that phone. I just soffed my new DNA yesterday, installed the newest cwm touch and flashed 4 different roms with no problem. Try re-flashing cwm touch.
pio_masaki said:
Did you do a full wipe? System, factory reset, dalvik?
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
Yes, still the same thing, I'm not saying I didn't do that the first time though, that's like the basics of installing a rom.
str8upx said:
It's probably your recoverys fault. On my last DNA I had nothing but failures. Once it took at least 30 times to get a Rom installed. Never solved the issue on that phone. I just soffed my new DNA yesterday, installed the newest cwm touch and flashed 4 different roms with no problem. Try re-flashing cwm touch.
Click to expand...
Click to collapse
Do you think its TWRP's fault? After I found out there was no way to mount USB storage in TWRP I wanted to switch to CWM, but sadly I don't know how.
rejectedjs said:
Yes, still the same thing, I'm not saying I didn't do that the first time though, that's like the basics of installing a rom.
Do you think its TWRP's fault? After I found out there was no way to mount USB storage in TWRP I wanted to switch to CWM, but sadly I don't know how.
Click to expand...
Click to collapse
You could use the goomanager from the play store or use fastbook flash recovery cwm.img
Edit: for the touch version of cwm fastboot is required.
str8upx said:
You could use the goomanager from the play store or use fastbook flash recovery cwm.img
Edit: for the touch version of cwm fastboot is required.
Click to expand...
Click to collapse
I would rather use goomanager, because it seems easier, but the only thing it seems to be able to download is the twrp image. How would I set it to cwm?
I have canvas 2 running on suvi6 Jupiter rom i have some prob with this when i reboot some icon on home screen will disappear, i found that those apps which r installed on ext sd card its icon will disappear from home screen, but apps working in apps list, only icon from home screen disappeared.
Other problem is that while incoming a call i cannot see full picture of caller becoz half screen is black and half picture can be seen.
Please help me
Sent from my Micromax A110 using xda app-developers app
rejectedjs said:
I would rather use goomanager, because it seems easier, but the only thing it seems to be able to download is the twrp image. How would I set it to cwm?
Click to expand...
Click to collapse
Sorry I was mistaken, goomanager installs twrp not cwm.
Fastboot is easy to use, I'm at work so I can't to a step by step til I get home later. You should be able figure it out but if not I will help when I get home.
str8upx said:
Sorry I was mistaken, goomanager installs twrp not cwm.
Fastboot is easy to use, I'm at work so I can't to a step by step til I get home later. You should be able figure it out but if not I will help when I get home.
Click to expand...
Click to collapse
I don't know if you knew this already but I s-offed using moonshine, is that a problem? I installed cwm and tried installing hatka again and it did the same thing, restart like every three seconds into android. I don't know what to do anymore.
kundan.lohar said:
I have canvas 2 running on suvi6 Jupiter rom i have some prob with this when i reboot some icon on home screen will disappear, i found that those apps which r installed on ext sd card its icon will disappear from home screen, but apps working in apps list, only icon from home screen disappeared.
Other problem is that while incoming a call i cannot see full picture of caller becoz half screen is black and half picture can be seen.
Please help me
Sent from my Micromax A110 using xda app-developers app
Click to expand...
Click to collapse
Pretty sure you're in the wrong forum.
From my S-Off BadSeed DNA
rejectedjs said:
There were two main roms I wanted to try after I finally S-OFF'd my phone yesterday. Hatka Supreme 1.1.0 and Carbon. Neither of these worked and I'm glad that I backed up my S-OFF rooted stock rom. Hatka Supreme, the guy states its best to use Beast Mode kernal with the rom, which I flashed after I installed the room, and it just randomly reboots at the splash screen/a few seconds after getting into Android, so I restored my stock and everything worked fine. Next, I tried Carbon, and it just sat there at the carbon flash screen for like 20 minutes, so again, I had to restore to stock. Is there something I'm doing wrong? Is there a difference between Original Android Development and Android Development? Should I be looking at the original or what? I'm really lost, I'm going to try another rom, hopefully someone replies to this before it finishes downloading. Thanks for the help.
EDIT: I'd rather just sit and wait to see if someone replies before I waste time downloading another rom...any help would be appreciated.
Click to expand...
Click to collapse
I'm no expert, but when u flashed hatka, did u reboot into the system before flashing beast mode kernel? Flashing a kernel in the same recovery session is a no no. Also, beast mode is not compatible with carbon, fyi.
Sent from my HTC6435LVW using Tapatalk 4 Beta
kelvinnotcalvin said:
I'm no expert, but when u flashed hatka, did u reboot into the system before flashing beast mode kernel? Flashing a kernel in the same recovery session is a no no. Also, beast mode is not compatible with carbon, fyi.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
I did that the first time, and thats when I started experiencing it, so I figured that was the problem. So I restored to stock, and then just tried flashing the rom and booting, still same thing, rebooting every 5 seconds. Sometimes I'm able to get into settings, scroll up and down a few times, and then it reboots.
EDIT: If I remember correctly, I didn't even flash beast mode kernel after I flashed carbon.
rejectedjs said:
EDIT: If I remember correctly, I didn't even flash beast mode kernel after I flashed carbon.
Click to expand...
Click to collapse
If you had you never would have seen the carbon boot animation I don't think, just a white scrambled screen.
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
If you had you never would have seen the carbon boot animation I don't think, just a white scrambled screen.
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
What exactly is the problem I'm experiencing here? x.x Of all roms I REALLY wanted to try Hatka, why me...
rejectedjs said:
What exactly is the problem I'm experiencing here? x.x Of all roms I REALLY wanted to try Hatka, why me...
Click to expand...
Click to collapse
I've had the same sort of thing happen to me when we first started working with CM. I had to lock up and run the RUU then unlock again, started flashing normally again after that.
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
I've had the same sort of thing happen to me when we first started working with CM. I had to lock up and run the RUU then unlock again, started flashing normally again after that.
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
You mean you want me to go back to pure stock and soff all over again?
rejectedjs said:
You mean you want me to go back to pure stock and soff all over again?
Click to expand...
Click to collapse
I don't want you to do anything, in was just saying what I did to correct it when it happened to me.
And no, I didn't day s-on, I said relocked, the RUU won't run on an unlocked device. Locked and son are different.
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
I don't want you to do anything, in was just saying what I did to correct it when it happened to me.
And no, I didn't day s-on, I said relocked, the RUU won't run on an unlocked device. Locked and son are different.
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
I've never had so many problems just trying to flash a Rom before, this is crazy...I'm seriously at a loss about what to do other than stay on rooted stock
bump?..I really want some help..
Did you figure it out? I'd do what pio said. He's kind of amazing. He's a very smart man who most likely knows what he's doing
Sent from my HTC6435LVW using xda app-developers app
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.
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
Soooo.... I rooted my Samsung Galaxy S4 (SCH-I545), then I decided to install a custom ROM since the default TouchWiz rom is slower than a turtle stuck in a pile of wax. I installed Safestrap 3.71 (TWRP v2.6.3.1) and by mistake flashed my stock rom. Now my phone won't boot into any ROM since that is corrupt, but it still boots into recovery (that's a good thing I suppose). I have tried a number of Safestrap compatible roms (omni, cm, beanstalk) but they either end up giving me a black screen or a very weird looking pixelated blue/cyan screen. I have to remove the battery to reboot my phone. I tried using adb to wipe the data aswell but nothing works beyond recovery.
I have to rely on adb to push and pull data to and from the phone.
I was hoping if anyone had any idea what I should try to do next?
Probably best just to restart by flashing the stock firmware back to it with Odin.
Make sure you don't try to downgrade the firmware vs what you have now, as that can create a lot more issues than you want to deal with.
Snake2k said:
Soooo.... I rooted my Samsung Galaxy S4 (SCH-I545), then I decided to install a custom ROM since the default TouchWiz rom is slower than a turtle stuck in a pile of wax. I installed Safestrap 3.71 (TWRP v2.6.3.1) and by mistake flashed my stock rom. Now my phone won't boot into any ROM since that is corrupt, but it still boots into recovery (that's a good thing I suppose). I have tried a number of Safestrap compatible roms (omni, cm, beanstalk) but they either end up giving me a black screen or a very weird looking pixelated blue/cyan screen. I have to remove the battery to reboot my phone. I tried using adb to wipe the data aswell but nothing works beyond recovery.
I have to rely on adb to push and pull data to and from the phone.
I was hoping if anyone had any idea what I should try to do next?
Click to expand...
Click to collapse
Have you cleared cache?
If you are not able to flash a custom rom, I would recommend you to flash a stock rom and begin from new. Also if you are on Android 4.4 you cannot use any recovery.
Sent from my GT-I9505 using XDA Premium 4 mobile app
es0tericcha0s said:
Probably best just to restart by flashing the stock firmware back to it with Odin.
Make sure you don't try to downgrade the firmware vs what you have now, as that can create a lot more issues than you want to deal with.
Click to expand...
Click to collapse
I'm just gonna give the Hyperdrive ROM a go, if that doesn't work, I'll definitely just go back to Stock I suppose and see what happens next. Thanks!
ikuni123 said:
Have you cleared cache?
If you are not able to flash a custom rom, I would recommend you to flash a stock rom and begin from new. Also if you are on Android 4.4 you cannot use any recovery.
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yep I cleared everything, weird problem lol. Its not 4.4 cus Verizon never released any for their S4s, but I'll definitely just head back to stock after I give Hyperdrive a chance Thanks!
Snake2k said:
I'm just gonna give the Hyperdrive ROM a go, if that doesn't work, I'll definitely just go back to Stock I suppose and see what happens next. Thanks!
Yep I cleared everything, weird problem lol. Its not 4.4 cus Verizon never released any for their S4s, but I'll definitely just head back to stock after I give Hyperdrive a chance Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2634408
According to that, only 13 is supported. I dunno if the that thread hasn't been updated or whatever, but something to consider.