Related
Forgive if there are similar threads about this topic.
I suffered from scrolling cwm so i tried this fix: http://forum.xda-developers.com/showpost.php?p=27830023&postcount=41
It worked excellent but when i lock my screen and unlock it again it starts flickering like shown in this video: http://youtu.be/P6fMxjFdpJE
I have tried to do factory resets both from recovery and flash an original firmware. Nothing works.
Is it possible to get this fixed or am i screwed?
Hi!
I've the same trouble like you!
Try this http://forum.xda-developers.com/showthread.php?t=1680738
For me it works well both the CWM recovery that hc 3.2 (no more flickering!)
brusarp said:
Hi!
I've the same trouble like you!
Try this http://forum.xda-developers.com/showthread.php?t=1680738
For me it works well both the CWM recovery that hc 3.2 (no more flickering!)
Click to expand...
Click to collapse
I just wanted to say the same. Flash the kernel from pershoot website, it should fix it.
brusarp said:
Hi!
I've the same trouble like you!
Try this http://forum.xda-developers.com/showthread.php?t=1680738
For me it works well both the CWM recovery that hc 3.2 (no more flickering!)
Click to expand...
Click to collapse
isimobile said:
I just wanted to say the same. Flash the kernel from pershoot website, it should fix it.
Click to expand...
Click to collapse
Thank you very much. I will try this when i get home from work.
It doesn´t work for me.
But I dont use 3G anyway so can I just go with P7510 firmware which works?
nicktaken said:
It doesn´t work for me.
But I dont use 3G anyway so can I just go with P7510 firmware which works?
Click to expand...
Click to collapse
Oh... i don't know that... mine is P7500... and works well both CWM and HC3.2 (with 3G and wifi connection)
brusarp said:
Oh... i don't know that... mine is P7500... and works well both CWM and HC3.2 (with 3G and wifi connection)
Click to expand...
Click to collapse
Alright I got it to work! I didn´t get it that I should flash the kernel in cwm so I flashed it in Samsungs recovery
nicktaken said:
Alright I got it to work! I didn´t get it that I should flash the kernel in cwm so I flashed it in Samsungs recovery
Click to expand...
Click to collapse
:highfive: :good:
brusarp said:
Hi!
I've the same trouble like you!
Try this http://forum.xda-developers.com/showthread.php?t=1680738
For me it works well both the CWM recovery that hc 3.2 (no more flickering!)
Click to expand...
Click to collapse
Got the same issue today after installing Task's ROM. The fix worked for me.. Thanks man.. :good:
nicktaken said:
Forgive if there are similar threads about this topic.
I suffered from scrolling cwm so i tried this fix: http://forum.xda-developers.com/showpost.php?p=27830023&postcount=41
It worked excellent but when i lock my screen and unlock it again it starts flickering like shown in this video: http://youtu.be/P6fMxjFdpJE
I have tried to do factory resets both from recovery and flash an original firmware. Nothing works.
Is it possible to get this fixed or am i screwed?
Click to expand...
Click to collapse
When you tried the fix noted above, I assume the screen didn't roll when you rebooted then into CWM recovery. At that point did you flash a ROM and THEN reboot to find the flicker after locking the screen, or did you do a reboot back into the same stock HC after flashing the bootloader and experience the problem?
I'm contemplating flashing this same bootloader because I have a rolling CWM5.5.0.4 right now and I want to stabilize it - but just so that I can root...not thinking about a ROM just yet...
Just to inform you all, i also had to flash a different bootloader after installing cm9 on my p7511, wich is in fact a 7510. For the records, pershoot made the new bootloader for exactly that issue, not backwards. But seems to work also.
What i deal now with, is that after flashing the uk ics for p7510 to my tab, the stock recovery doesn't recognize my sdcard. Can't mount sdcard...
Could be that a repartitioning with pit file will be necessary afterwards for us all.
Edit: thanks to the wise help of msedek, i know by now that my hind was totaly wrong. My mentioned point has to do with the Changes within stock recovery of ics, which have been made to prevent changes from there.
Getting more confident..
OK so it is sounding like this is definitely better. One more question:
I'm following the stickied root guide in General and that method uses CWM 4.0.0.4...I had reflashed that version. If I want to flash this boot loader should I flash 5.5.0.4 first? Or does it matter if I'm just trying to root right now?
EDIT: Flashed the bootloader which straightened out the recovery!! Successfully rooted after that. Downloaded root apps (ROM manager/Titanium/etc). Then turned off my screen - FLICKER CITY!
http://forum.xda-developers.com/showthread.php?t=1680738 <<< THIS fixed it. Load this kernel into the root of your tablet and flash it with CWM. Seems to have done the trick nicely and I'm exploring my newly rooted tab! My wife no longer wants to kill me either.
brusarp said:
Hi!
I've the same trouble like you!
Try this http://forum.xda-developers.com/showthread.php?t=1680738
For me it works well both the CWM recovery that hc 3.2 (no more flickering!)
Click to expand...
Click to collapse
This method don't work with new ICS firmware. I need a new kernel to work with new ICS firmware . I like the new firmware but i stuck with flickerscreen issue. Can sum 1 help ? Thanks.
I have the same Problem here.
Nothing is working for me, i have tried 2 diferent kernels and still flickering screen after tourning the screen off and on.
Please can anyone help me?
KeyF said:
I have the same Problem here.
Nothing is working for me, i have tried 2 diferent kernels and still flickering screen after tourning the screen off and on.
Please can anyone help me?
Click to expand...
Click to collapse
What ROM or firmware are you running? What exactly have you done with the device up to this point? Are you 3G or WiFi? Need more detail...
Flicker screen after screen lock\timeout
djmatt604 said:
What ROM or firmware are you running? What exactly have you done with the device up to this point? Are you 3G or WiFi? Need more detail...
Click to expand...
Click to collapse
I have the same problem on my P7500 3G and the minute i load the bootloader to fix CWM recovery rolling i get the screen flickering after lock screen.
Rom: ICS 4.0.4
Build Number: IMM76D.XXLQ8
BaseBand7500XXlQ8
Kernel: 3.1.10
Still stuck.
Hi guys,
Gtab 10.1 Wifi here. Fix didn't worked, somehow...
After installing official ics from Samsung and rooted, i had the same insane flicker issue. I followed this thread - http://forum.xda-developers.com/showthread.php?t=1680738 - , flashed new kernel, and now i cant pass Samsung Galaxy Tab logo for some reason, not even past half an hour.
Im in a dead end, even tried installing back CM9 but it also wont pass the splashing blue screen.
Any ideas?
cheers!
EDIT : After some reboots, finally managed to boot into ICS (CM9) but now i was pushed back to the step 1, where I don't have a working camera, but I have root access and non official ICS from Cyanogen. I am afraid re-doing all my work and get stuck again in the scrambled screen after it updates the kernel..
I'm I missing something, guys?
Hi there!
Are you still having problems?does this guide here work for you?:
http://forum.xda-developers.com/showthread.php?t=1555984
I've found something,the kernel flash package changes our devices' WiFi driver,that's why it doesn't work.
sorry for not giving a fix until tomorrow,it's sleep time here,I know my excuse will be accepted because you all care for basic human needs...
But please inform me if that guide(Pershoot's) has fixed your problem,thanks for that
brusarp said:
Hi!
I've the same trouble like you!
Try this http://forum.xda-developers.com/showthread.php?t=1680738
For me it works well both the CWM recovery that hc 3.2 (no more flickering!)
Click to expand...
Click to collapse
No it does not work for me.
I have a GT-P7500 with ICS with Build # IMM76D.XWLP6
Please direct me to the correct forum.
thanX
reXbeer said:
No it does not work for me.
I have a GT-P7500 with ICS with Build # IMM76D.XWLP6
Please direct me to the correct forum.
thanX
Click to expand...
Click to collapse
Hey guys i solve my problem today i desided to solve it anyway and now i am free from this **** ....
i just go to http://droidbasement.com/galaxy/roms/cm10/p4/ and download
bootloader.tar.md5
latest recovery.tar.md5
cm-10-20121112-EXPERIMENTAL-p4.zip
but before start anything first i format my tab memory then restart in download mode install bootloader.tar.md5 and recovery.tar.md5 ... volla ... reboot in recovery mode volla thats it all is now working perfect .... then i install cm-10-20121112-EXPERIMENTAL-p4.zip now my tab is free on madness ...
must try but first fully clean your tab ...
iff its really work then click on thanks button ...
Guys I am in dire need of some help. I have a VZW GS4 i545 and I flashed the new 'merged' version of PHilz touch for the GS4 only to find out it is non-Loki'd so now I am getting the error message "Software not authorized by Verizon".
I know I need to use Odin to get back but I don't know how to use it to replace the boot loader.
Can someone please tell me or point me to a step-by-step?
I've Googled this many different ways but I can't seem to find what I need.
Please help.
ktraub said:
Guys I am in dire need of some help. I have a VZW GS4 i545 and I flashed the new 'merged' version of PHilz touch for the GS4 only to find out it is non-Loki'd so now I am getting the error message "Software not authorized by Verizon".
I know I need to use Odin to get back but I don't know how to use it to replace the boot loader.
Can someone please tell me or point me to a step-by-step?
I've Googled this many different ways but I can't seem to find what I need.
Please help.
Click to expand...
Click to collapse
Just flash the no wipe mdk tar...you don't just flash bootloaders... It will replace recovery image which is what you need...you will have to re-flash a loki'd image after
jamesd1085 said:
Just flash the no wipe mdk tar...you don't just flash bootloaders... It will replace recovery image which is what you need...you will have to re-flash a loki'd image after
Click to expand...
Click to collapse
Jamesd1085, thanks for the reply.
But, how do I flash with the " Software not authorized by Verizon" message up?
I don't know how to get the phone back into download mode with that message up.
Your help is greatly appreciated.
ktraub said:
Jamesd1085, thanks for the reply.
But, how do I flash with the " Software not authorized by Verizon" message up?
I don't know how to get the phone back into download mode with that message up.
Your help is greatly appreciated.
Click to expand...
Click to collapse
Pull the battery then try to get into download mode again. Here's a thread with a guide. Make sure you get the mdk file and not another one as you'd end locking your phone up.
http://forum.xda-developers.com/showthread.php?t=2301259
Sent From My Verizon S4
ktraub said:
Jamesd1085, thanks for the reply.
But, how do I flash with the " Software not authorized by Verizon" message up?
I don't know how to get the phone back into download mode with that message up.
Your help is greatly appreciated.
Click to expand...
Click to collapse
To turn it off pull battery... After that you can boot into download mode by holding volume down and power button...after that you can flash via odin
Mistertac said:
Pull the battery then try to get into download mode again. Here's a thread with a guide. Make sure you get the mdk file and not another one as you'd end locking your phone up.
http://forum.xda-developers.com/showthread.php?t=2301259
Sent From My Verizon S4
Click to expand...
Click to collapse
Mistertac, thanks for the response. I pulled the battery and the phone booted into my custom ROM HyperDrive RLS 14, and I still have root.
I think I may have just hosed my recovery. While I'm waiting for the no wipe mdk to download (another 2 hours), is there nay way to just flash the recovery?
Your help is greatly appreciated.
ktraub said:
Mistertac, thanks for the response. I pulled the battery and the phone booted into my custom ROM HyperDrive RLS 14, and I still have root.
I think I may have just hosed my recovery. While I'm waiting for the no wipe mdk to download (another 2 hours), is there nay way to just flash the recovery?
Your help is greatly appreciated.
Click to expand...
Click to collapse
Well you can easily re install your recovery of choice still. Either with goo or rom manager.
Sent From My Verizon S4
Mistertac said:
Well you can easily re install your recovery of choice still. Either with goo or rom manager.
Sent From My Verizon S4
Click to expand...
Click to collapse
Mistertac, thank you very much!
I installed Goo manager and then used it to install TWRP.
The I rebooted to recovery and flashed the correct (loki'd) version of Philztouch.
Thank you again. I really appreciate it.
-Kev
ktraub said:
Mistertac, thank you very much!
I installed Goo manager and then used it to install TWRP.
The I rebooted to recovery and flashed the correct (loki'd) version of Philztouch.
Thank you again. I really appreciate it.
-Kev
Click to expand...
Click to collapse
Glad we could help. And even better that you flashed the Loki'd version of Philz or you'd be using Odin after all lol
Sent From My Verizon S4
Mistertac are you familiar with philz touch?...jw because last week I installed it and loved the ui and extra features but it wouldn't allow me to flash anything...I ended up having to use ROM toolbox to flash cwm touch 6.0.4.4...any Ideas...everybody seems to swear by Philz touch and I would rather use it...I tried toggling Loki support on and off it wouldn't flash regardless of settings
jamesd1085 said:
Mistertac are you familiar with philz touch?...jw because last week I installed it and loved the ui and extra features but it wouldn't allow me to flash anything...I ended up having to use ROM toolbox to flash cwm touch 6.0.4.4...any Ideas...everybody seems to swear by Philz touch and I would rather use it...I tried toggling Loki support on and off it wouldn't flash regardless of settings
Click to expand...
Click to collapse
Yes I use Philz. Are you flashing our device specific Philz zip or the unified jflte zip? Because some were having problems with the unified one
Sent From My Verizon S4
Mistertac said:
Yes I use Philz. Are you flashing our device specific Philz zip or the unified jflte zip? Because some were having problems with the unified one
Sent From My Verizon S4
Click to expand...
Click to collapse
Dunno...lol...I downloaded it from the philz touch op for jfltevzw...but I will have to look again...it was most recent version but I didn't see anything about a unified version...thanks for the heads up
jamesd1085 said:
Dunno...lol...I downloaded it from the philz touch op for jfltevzw...but I will have to look again...it was most recent version but I didn't see anything about a unified version...thanks for the heads up
Click to expand...
Click to collapse
Yea I'd grab the latest one from here..
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/jfltevzw
Sent From My Verizon S4
Mistertac said:
Yea I'd grab the latest one from here..
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/jfltevzw
Sent From My Verizon S4
Click to expand...
Click to collapse
Yeah I had the previous build from here...maybe just a fluke...Lil...I will try the new version...thanks
Hi,
I am trying to install a rom on my n7100 for a second time. Trying to move from DN3 to SOKP (http://forum.xda-developers.com/showthread.php?t=2700230).
I'm making a clean install. However, while installing from zip I'm getting a status 7 error. I researched all around and found that it is mostly because of the assert section. So i removed it and tried; same error.
I had philz recovery installed, moved to cwm, still same error.
Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2605730 , where someone flashed original firmware and then flashed new rom; did that, same error.
Tried toggling signature verification; same error.
Now my installation screen looked like this. Can anyone help me with it? I really dont know whats happening.
anmolgoel said:
Hi,
I am trying to install a rom on my n7100 for a second time. Trying to move from DN3 to SOKP (http://forum.xda-developers.com/showthread.php?t=2700230).
I'm making a clean install. However, while installing from zip I'm getting a status 7 error. I researched all around and found that it is mostly because of the assert section. So i removed it and tried; same error.
I had philz recovery installed, moved to cwm, still same error.
Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2605730 , where someone flashed original firmware and then flashed new rom; did that, same error.
Tried toggling signature verification; same error.
Now my installation screen looked like this. Can anyone help me with it? I really dont know whats happening.
Click to expand...
Click to collapse
tried flashing another rom?
anmolgoel said:
Hi,
I am trying to install a rom on my n7100 for a second time. Trying to move from DN3 to SOKP (http://forum.xda-developers.com/showthread.php?t=2700230).
I'm making a clean install. However, while installing from zip I'm getting a status 7 error. I researched all around and found that it is mostly because of the assert section. So i removed it and tried; same error.
I had philz recovery installed, moved to cwm, still same error.
Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2605730 , where someone flashed original firmware and then flashed new rom; did that, same error.
Tried toggling signature verification; same error.
Now my installation screen looked like this. Can anyone help me with it? I really dont know whats happening.
Click to expand...
Click to collapse
Delete some apps or unwanted ringtones from the rom zip then flash the rom..
try to use newest Milestone from SOKP, where is the file saved, on sd-card or internal memory ?
Make sure the ROM zip is completely downloaded/ copies to ur SD card .. An incomplete zip is a common cause of this error, also make sure u're on the latest version of whatever recovery u're using
Sent from my GT-I9300
Thank you guys for your help. yes jinayhvora I used the newer recovery and it worked like a charm.
However latest is not always better as last time while installing DN3 I couldnt get past the terms and condition. Then I downgraded to a previous version of philz recovery and it worked.
There is another problem though, when I restore the nandroid of DN3, it works fine, but when I restore backup of stock, I cant get past the samsung logo.
I thought the backup might be corrupt, but I re-flashed the stock firmware and took its backup; same problem.
Any ideas?
It DOES say in the Installation Instructions that they recommend using TWRP. There's usually a reason why when they say that.
es0tericcha0s said:
It DOES say in the Installation Instructions that they recommend using TWRP. There's usually a reason why when they say that.
Click to expand...
Click to collapse
:good::good:
es0tericcha0s said:
It DOES say in the Installation Instructions that they recommend using TWRP. There's usually a reason why when they say that.
Click to expand...
Click to collapse
Yes I agree; can you help me with the below problem though?
anmolgoel said:
There is another problem though, when I restore the nandroid of DN3, it works fine, but when I restore backup of stock, I cant get past the samsung logo.
I thought the backup might be corrupt, but I re-flashed the stock firmware and took its backup; same problem.
Any ideas?
Click to expand...
Click to collapse
anmolgoel said:
I re-flashed the stock firmware and took its backup; same problem.
Click to expand...
Click to collapse
what do you mean by this?
You flashed the stock then restored its backup? and still got stuck? well then maybe, it really is corrupted
Are you using TWRP or CWM now? Try wiping caches after restore. But I dunno DN3 refers to either. Is that stock based or other?
kermage said:
what do you mean by this?
Click to expand...
Click to collapse
Well, what I mean by this is: I flashed the stock firmware, rooted it, and then took a nandroid backup. I wanted to see if the problem was with restoring the previous copy I have, or with restoring the stock firmware in general.
And when I restored it after a wipe, it still got stuck at the samsung logo. So the problem is with restoring the stock firmware, which is weird. I was using the latest philz recovery, and the stock firmware was 4.3
kermage said:
You flashed the stock then restored its backup? and still got stuck? well then maybe, it really is corrupted
Click to expand...
Click to collapse
maybe
anmolgoel said:
Well, what I mean by this is: I flashed the stock firmware, rooted it, and then took a nandroid backup. I wanted to see if the problem was with restoring the previous copy I have, or with restoring the stock firmware in general.
And when I restored it after a wipe, it still got stuck at the samsung logo. So the problem is with restoring the stock firmware, which is weird. I was using the latest philz recovery, and the stock firmware was 4.3
maybe
Click to expand...
Click to collapse
well, take a new backup now and try if it works..then we can conclude..
I'm curious as to why you aren't using TWRP.
kermage said:
well, take a new backup now and try if it works..then we can conclude..
Click to expand...
Click to collapse
I'm not able to make out whether you're messing with me
the current rom (SOKP) is able to be restored; only problem with the stock rom.
es0tericcha0s said:
I'm curious as to why you aren't using TWRP.
Click to expand...
Click to collapse
because the backup was made in philz. From what I know, CWM and TWRP have different kind of backup files which cant be restored by the other.. let me know if I'm wrong..
Should I use TWRP to backup now.. You think it'll work better than philz?
es0tericcha0s said:
Are you using TWRP or CWM now? Try wiping caches after restore. But I dunno DN3 refers to either. Is that stock based or other?
Click to expand...
Click to collapse
sorry didnt see this post earlier.. I'm on philz, DN3 is ditto note 3 rom that I was using; it is stock based.
The backups are not compatible between the 2, but obviously this version of Philz isn't cooperating like it should and since the developer's for DU suggested TWRP, seems like that's next logical step in troubleshooting issues with backing up and restoring in general.
es0tericcha0s said:
The backups are not compatible between the 2, but obviously this version of Philz isn't cooperating like it should and since the developer's for DU suggested TWRP, seems like that's next logical step in troubleshooting issues with backing up and restoring in general.
Click to expand...
Click to collapse
Agreed.. Just to put it out there.. the first backup I made was through Online nandroid manager app, and the second one through philz..
I'll install and use twrp the next time I'm on stock... which I dont think i will be for a long time btw.. enjoying the irresistible ROMs out there
anmolgoel said:
Agreed.. Just to put it out there.. the first backup I made was through Online nandroid manager app, and the second one through philz..
I'll install and use twrp the next time I'm on stock... which I dont think i will be for a long time btw.. enjoying the irresistible ROMs out there
Click to expand...
Click to collapse
Ah. Never used the Online Nandroid one. Never saw the point and trust the actual recovery to be able to backup better. Less chance of issues.
Hopefully, you wonderfully knowledgeable people can help with this one!
I recently rooted my Galaxy S3 with no problems and decided to install a Custom ROM, (Omni version 4.4.2). Followed the instructions on a page that the forum won't allow me to post a link of and got to the point of installing the new ROM. It then came up with "Installation Aborted" and "Status 7".
I then found an explanation of how to sort out the problem of Status 7, at which point I attempted to put the edited version back onto my phone, only to realise that my computer and phone are no longer mounted and I cannot access the SD Card. I've tried disconnecting and re-connecting with no joy, because I'm stuck in ClockWorkMod it won't show up on my PC.
Now here's the moronic part... I completely missed the big bold lettering of "Before you install a custom ROM, PLEASE MAKE A BACKUP ROM!!!", so I cannot restore to another point.
Any suggestions and feel free to assume I'm a complete idiot when describing any fixes.
Powello1 said:
Hopefully, you wonderfully knowledgeable people can help with this one!
I recently rooted my Galaxy S3 with no problems and decided to install a Custom ROM, (Omni version 4.4.2). Followed the instructions on a page that the forum won't allow me to post a link of and got to the point of installing the new ROM. It then came up with "Installation Aborted" and "Status 7".
I then found an explanation of how to sort out the problem of Status 7, at which point I attempted to put the edited version back onto my phone, only to realise that my computer and phone are no longer mounted and I cannot access the SD Card. I've tried disconnecting and re-connecting with no joy, because I'm stuck in ClockWorkMod it won't show up on my PC.
Now here's the moronic part... I completely missed the big bold lettering of "Before you install a custom ROM, PLEASE MAKE A BACKUP ROM!!!", so I cannot restore to another point.
Any suggestions and feel free to assume I'm a complete idiot when describing any fixes.
Click to expand...
Click to collapse
Download another stock rom from sammobile switch phone off and flash it with odin then factory reset Done..
You can then start again... By the way status 7 is usually caused by wrong recovery or old recovery.
Use Odin install latest original firmware then root then install latest CWM to get rid of status 7 error
Sent from my GT-I9300 using Tapatalk
Do we have a repository for Sammy UK ROMs that isn't Sammobile? It's downloading painfully slowly.
http://live.samsung-updates.com/index.php?device=GT-I9300
Sent from my GT-I9300 using Tapatalk
boomboomer said:
http://live.samsung-updates.com/index.php?device=GT-I9300
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
You sir, are a gent. Thank you kindly. :good:
Thought we'd got the problem sorted but it seems to not like ArchiDroid, still waiting on the stock ROM to download as there are server problems.
Out of interest, would a KitKat recovery work on a 4.3 ROM?
Powello1 said:
Thought we'd got the problem sorted but it seems to not like ArchiDroid, still waiting on the stock ROM to download as there are server problems.
Out of interest, would a KitKat recovery work on a 4.3 ROM?
Click to expand...
Click to collapse
I had that, it was an older version of CWM causing the status 7, would TWRP help ?
kennyboy1978 said:
I had that, it was an older version of CWM causing the status 7, would TWRP help ?
Click to expand...
Click to collapse
We're all sorted, it was a 4.0.4 CWM installed with a 4.3 ROM. Upgraded CWM and we're good to go! I don't think he's brave enough to attempt a KitKat install after 6 hours of being stuck in CWM, haha.
Thanks again to all that posted. :victory:
As Kalavere says, all sorted! Looks like the key to Custom ROMS is make sure you have the latest CWM!
Thank you all for your help!
yeah this has occured with me when i rooted my s3
i've tried to install a rom but then and totally out of the blue it told me that installation aborted so i became very disappointed and didn't know what to do cuz i've already followed the instructions written in the site
i just tried to re-root my s3 with a different root file Which I've got from xda too and everything ran ok again so just re-root with another root file
Sent from my SM-G900F using XDA Premium 4 mobile app
[SOLVED]
Turns out CMW 6.0.4.7 will not flash to this device - solution was to use the app "Flashify" from the play store which simply and easily installed TWRP
Thanks joshm.1219!
[SOLVED]
I am at a complete loss for a fix. Short story is: I wasn't receiving any MMS, so I finally decided to ODIN back to stock and used this method so I could keep my data. Here's what happened next:
- ODIN passed but I couldn't get past the Verizon logo
- Tried several suggested fixes but the last resort one worked; I wiped data & factory reset (thus defeating the purpose of the no-wipe ODIN... w/e)
- Everything loads fine, TouchWiz works but I get a Factory Mode popup and can't lock my screen. (still can't lock my phone even now but will use this method if I think I'm stuck with TouchWiz)
- I use this method to unlock bootloader and root - root confirmed.
- Try to install CWM recovery or TWRP (btw, where the hell did GooManager go and why is it so hard to find now) and they say successful but I simply can't boot into them, just keep getting the factory recovery screen which won't let me flash any roms or any non-signed .zips
- MMS Still doesn't work!
- I call VZW in desperation and somehow they magically reset my account services and MMS works again! (I probably could have done this in the first place and not lost my ROM/Data and sanity if I'd known)
I have looked high and low for a solution but have found none. I also have been unable to find a REGULAR stock MDK file to flash on this phone - I can only find the NO-WIPE version which doesn't even allow you to keep your data. I'm confused and frustrated and would love some active help, I just can't find the right threads/posts/ect.
Thank you kindly for any advice.. I love my S4 and have been using PA, PAC, CM and other ROMS since the day I got it - I need that back! TouchWiz is just... I just don't like it.
Try this one.
http://www.rwilco12.com/downloads.p...Galaxy S4 (Verizon) (SCH-I545)/Stock ROMs/TAR
FernBch said:
Try this one.
link
Click to expand...
Click to collapse
Thanks for the original stock.. sadly I am still ending up with the Android System Recovery and despite installing CWM Recovery, I just can't get to it. I also still get the ridiculous Factory Mode popup.
Any ideas? I'm so sad :'(
From off it's either home+volume down+power or home+volume up+power. One boots into stock recovery the other will boot into CWM.
Hold all three until you see some small blue text in the upper left of the screen.
FernBch said:
From off it's either home+volume down+power or home+volume up+power. One boots into stock recovery the other will boot into CWM.
Hold all three until you see some small blue text in the upper left of the screen.
Click to expand...
Click to collapse
Thanks for the effort but I'm well aware of that. As I said in the OP, I've been using custom ROMs on this since day one - the issue is that I cannot boot into CMW Recover, despite having a successful install via the app.
Dumb question, which app are you using? I use RomManager to install CWM (up to 6.0.4.7) and I have a flashable zip of 6.0.5.0.
877
FernBch said:
Dumb question, which app are you using? I use RomManager to install CWM (up to 6.0.4.7) and I have a flashable zip of 6.0.5.0.
Click to expand...
Click to collapse
I'm using ROM Manager but it won't work. I'd love to try ODIN flashing the CWM Recovery if you have the file for my MDK build.
I may have it on my PC at home. When I get there (60-90 min) I'll look. If I do I'll post up to Dropbox and give you a link.
Ok, I've searched my HDD and I don't have the CWM file. What I do have is the MDK all-in-one root+recovery tool for the I545. I can put it up and upload it if the file isn't too large but I don't know if that'll help you.
CWM 6.0.5.0 flashable zip is in the CM11 thread but I don't know if the recovery image in the file is good for you, either
Just use Flashify to get TWRP
joshm.1219 said:
Just use Flashify to get TWRP
Click to expand...
Click to collapse
I was about to complain about your assumption that I knew what that was.. then I found it on the play store and it actually worked! Thank you so much - now here's to hoping I can find a nice stable 4.4.4 ROM to put back on here!
I'm still at a loss for why ROM Manager was unable to flash CWMR but I guess I don't _need_ to know, I am so happy this is a big step after 3 days of touchwiz hell!
voice.lex said:
I was about to complain about your assumption that I knew what that was.. then I found it on the play store and it actually worked! Thank you so much - now here's to hoping I can find a nice stable 4.4.4 ROM to put back on here!
I'm still at a loss for why ROM Manager was unable to flash CWMR but I guess I don't _need_ to know, I am so happy this is a big step after 3 days of touchwiz hell!
Click to expand...
Click to collapse
As far as I know, the latest CWM doesn't work on our devices.
joshm.1219 said:
As far as I know, the latest CWM doesn't work on our devices.
Click to expand...
Click to collapse
Well, that explains it - Thank you so much!
voice.lex said:
Well, that explains it - Thank you so much!
Click to expand...
Click to collapse
No problem :thumb:
This thread might be dead, but rather than starting a new one for what is probably a stupid question, I'll ask it here and see what happens. I've been having major trouble flashing any 5.0 rom on my MDK VZW S4....Seems like every ROM fails when flashing. I have a feeling my issue is an outdated version of TWRP (2.5.0.2), but I am very hesitant to update because it seems like everyone has been having issues with 2.8.1.0. With this being said, are you guys currently running the most current version of TWRP and would you mind advising which .img file worked via Flashify? Not sure whether to use the jfltexxx or jfltevzw...or if it even matters.
I'm sure I've left out pertinent information, but let me know what I'm missing and I'll update accordingly.
I've been using the latest version of TWRP 2.8.1.0 and running Euroskank Lollerpop with zero issues. Coincidentally, TWRP just got updated today to 2.8.3.0 which i have yet to flash but will do so shortly. I would recommend JFLTEVZW based on my usage. Not sure if the other variant works or not but it appears you have a verizon device so stick with JFLTEVZW.
760hacker said:
I've been using the latest version of TWRP 2.8.1.0 and running Euroskank Lollerpop with zero issues. Coincidentally, TWRP just got updated today to 2.8.3.0 which i have yet to flash but will do so shortly. I would recommend JFLTEVZW based on my usage. Not sure if the other variant works or not but it appears you have a verizon device so stick with JFLTEVZW.
Click to expand...
Click to collapse
Thank you very much for getting back to me. When you flashed 2.8.3.0, was it a .zip file from recovery or a .IMG through flashify or another app? Thanks again for your help!
swh969 said:
Thank you very much for getting back to me. When you flashed 2.8.3.0, was it a .zip file from recovery or a .IMG through flashify or another app? Thanks again for your help!
Click to expand...
Click to collapse
.IMG file, flashify is so simple!
Sent from my Nexus 7 using Tapatalk
760hacker said:
.IMG file, flashify is so simple!
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I'm going to give it a shot! Thanks again for your help.
Worked like a charm. Thanks @760hacker