Hi,
I flashed the Google 4.3 S4 Rom and used TWRP 2.5.0.2 and Goo with instructions I found on the boards.
- I am a Canadian (Rogers/FIDO) S4
- I used the 4.3 ROM Deodexed
So now the problems:
1) I originally installed it and it was constantly stuck on 'Samsung Galaxy S4' Screen, couldn't proceed barely got into recovery and reflashed; this worked and it booted google and i realized why this happened is because i accidentally erased my data.
2) The second time, I simply turned off my phone and turned it back on, again i was stuck on 'Samsung Galaxy S4' Screen, no way of doing anyhing except turnging off the phone and trying again and again to get to recovery, I then flashed to 4.3 again off the external.
3) I simply tried to open facebook and the phone booted and went on to the 'Samsung Galaxy S4' Screen and is stuck again! Even when I reboot through Team Win Recovery v2.5.0.2 to System I get the same boot loop.
I am super frustrated with this, what can I do and at this point I'm getting to the point where I would like some help to go back to stock. I would also like some input as to why this is happening if anyone has any suggestions or help it would be greatly appreciated.
Thank You.
notorious99 said:
Hi,
I flashed the Google 4.3 S4 Rom and used TWRP 2.5.0.2 and Goo with instructions I found on the boards.
- I am a Canadian (Rogers/FIDO) S4
- I used the 4.3 ROM Deodexed
So now the problems:
1) I originally installed it and it was constantly stuck on 'Samsung Galaxy S4' Screen, couldn't proceed barely got into recovery and reflashed; this worked and it booted google and i realized why this happened is because i accidentally erased my data.
2) The second time, I simply turned off my phone and turned it back on, again i was stuck on 'Samsung Galaxy S4' Screen, no way of doing anyhing except turnging off the phone and trying again and again to get to recovery, I then flashed to 4.3 again off the external.
3) I simply tried to open facebook and the phone booted and went on to the 'Samsung Galaxy S4' Screen and is stuck again! Even when I reboot through Team Win Recovery v2.5.0.2 to System I get the same boot loop.
I am super frustrated with this, what can I do and at this point I'm getting to the point where I would like some help to go back to stock. I would also like some input as to why this is happening if anyone has any suggestions or help it would be greatly appreciated.
Thank You.
Click to expand...
Click to collapse
Have you try using Odin to go back to stock?
shizs14 said:
Have you try using Odin to go back to stock?
Click to expand...
Click to collapse
I am not sure what that is, but I can try to search it, could you point me in the right direction as to how to do that?
notorious99 said:
I am not sure what that is, but I can try to search it, could you point me in the right direction as to how to do that?
Click to expand...
Click to collapse
Rule #1. Learn Odin before attempting anything on Samsung phones
notorious99 said:
I am not sure what that is, but I can try to search it, could you point me in the right direction as to how to do that?
Click to expand...
Click to collapse
You need to read these threads and make sure to read the threads linked in these threads that have to do with your phone...
http://forum.xda-developers.com/showthread.php?t=2301762
and
http://forum.xda-developers.com/showthread.php?t=2312444
You can use the forum's search function to help you find specific information. Good luck.
agreed, odin should be the first thing any noob should learn.
Scott, you da man...
scott14719 said:
You need to read these threads and make sure to read the threads linked in these threads that have to do with your phone...
http://forum.xda-developers.com/showthread.php?t=2301762
and
http://forum.xda-developers.com/showthread.php?t=2312444
You can use the forum's search function to help you find specific information. Good luck.
Click to expand...
Click to collapse
So I flashed a different rom (4.2.2 google) and I tested turning my phone off and then on again, and SAME issue, it boot loops at the S4 screen, what is the deal with that specifically? does anyone have any ideas?
notorious99 said:
So I flashed a different rom (4.2.2 google) and I tested turning my phone off and then on again, and SAME issue, it boot loops at the S4 screen, what is the deal with that specifically? does anyone have any ideas?
Click to expand...
Click to collapse
Which google rom 4.2.2? there are a few, meaning where did you get the rom?
Which kernel did you use?
you say you have this...both roms require a certain kernel. Depending on whose rom you flashed.
I am a Canadian (Rogers/FIDO) S4
- I used the 4.3 ROM Deodexed
TheAxman said:
Which google rom 4.2.2? there are a few, meaning where did you get the rom?
Which kernel did you use?
you say you have this...both roms require a certain kernel. Depending on whose rom you flashed.
I am a Canadian (Rogers/FIDO) S4
- I used the 4.3 ROM Deodexed
Click to expand...
Click to collapse
THE ROM
Google Edition 4.2.2 - v1.3 - http://d-h.st/Lm8
posted here: http://forum.xda-developers.com/showthread.php?t=2341376
MY KERNEL as it is on my phone currently is:
Baseband: 1337MVLUAMDJ
Kernel: 3.4.0-Google-Edition, [email protected]#1,
Build Number: JDQ39.1337
AND I'm using TWRP Custom
-----------------------------------------
notorious99 said:
THE ROM
Google Edition 4.2.2 - v1.3 - http://d-h.st/Lm8
posted here: http://forum.xda-developers.com/showthread.php?t=2341376
MY KERNEL as it is on my phone currently is:
Baseband: 1337MVLUAMDJ
Kernel: 3.4.0-Google-Edition, [email protected]#1,
Build Number: JDQ39.1337
AND I'm using TWRP Custom
-----------------------------------------
Click to expand...
Click to collapse
Ok, now we're cooking, thanks for the info...
I haven't tried that rom yet, I am going to d/l it and give it a shot. Be back shortly.
ODIN back to stock, and start over from there, and take care to flash/erase properly. backup user apps/data if you can (there are non-root options) and restore when you finish flashing 4.3 and are sure its stable.
Ok..back...I flashed this rom I booted with the kernel supplied in rom. Hmm..it is kernel related for sure. Have you posted the issue in that roms thread? May want to give that a shot.
I'm on canadian S4 aswell and I also flashed the 1.3 Google edition but flashed faux kernel. Works like a charm.
Sent from my SGH-I337 using Tapatalk 4 Beta
Thank you to all you guys. I successfully used odin to get back to stock. I still have no idea why I had so many problems but will try the Google Rom again when I feel more comfortable.
Thanks again!
notorious99 said:
Thank you to all you guys. I successfully used odin to get back to stock. I still have no idea why I had so many problems but will try the Google Rom again when I feel more comfortable.
Thanks again!
Click to expand...
Click to collapse
Proper wiping steps is key when changing ROM bases. Do a factory reset, wipe both caches, format /system, and if coming from TW, format the internal also.
Here is a post by TeamWin on wiping for Roms. Formatting Data is not part of "normal" wipe process. It wipes your internal sd.
http://teamw.in/whattowipe
These guys are far above me. But my preferred method is to "Wipe" System/Data/Both Caches. I actually do it twice. I know many say no need, but I do. I did this for many years on previous phones and never had issues. If on Nightlies or incremental updates did not wipe unless OP said to.
rugmankc said:
Here is a post by TeamWin on wiping fro Roms. Formatting Data is not part of "normal" wipe process. It wipes your internal sd.
http://teamw.in/whattowipe
These guys are far above me. But my preferred method is to "Wipe" System/Data/Both Caches. I actually do it twice. I know many say no need, but I do. I did this for many years on previous phones and never had issues. If on Nightlies or incremental updates did not wipe unless OP said to.
Click to expand...
Click to collapse
The internal wiping isn't necessary, but it does get rid of TW folders that you don't need if switching to AOSP.
I think you could delete them individually as opposed to formatting entire internal with other rom backups/kernels/gapps etc. I also have music/pics on internal too. Also, I like some will go back and forth btwn aosp and tw. So, I would want to keep them. I never did that, but read about some having issues after Formatting Data
All IMHO--
rugmankc said:
I think you could delete them individually as opposed to formatting entire internal with other rom backups/kernels/gapps etc. I also have music/pics on internal too. Also, I like some will go back and forth btwn aosp and tw. So, I would want to keep them. I never did that, but read about some having issues after Formatting Data
All IMHO--
Click to expand...
Click to collapse
You're right, it's an overkill. Just my OCD nature kicks in sometimes.
+1
I understand OCD hence my wiping twice--hey sometimes 3x
Monk has nothing on me, If you are familiar with that tv show--
I am OCD thru and thru--
Related
Hey,
So I flashed a custom rom on my AT&T Galaxy S IV. Everything seems to be working fine.
Until, I hold on my power menu than click on Reboot my phone. When I do that, my phone shuts down and reboots but it's always stuck in the Samsung Custom Screen. The max I have waited is 30 minutes for it to work. But it never does.
I'm running TWRP Recovery Mode.
I tried every roms in the AT&T Section. All of them seems to have that problem. I also used ktoonsez kernel. Nothing at all.
With stock AT&T rom everything seems to be fine.
I was wondering if it's happening to you guys as well. If you can try, please hold into your power button and reboot your phone clicking on reboot.
Thank you!
I have that happen sometimes, but if I go into recovery when that happens and fix permissions it boots up fine after.
Sent from my SGH-I337 using Tapatalk 4 Beta
Flash a different kernel.
Period
your welcome
TehZam said:
Hey,
So I flashed a custom rom on my AT&T Galaxy S IV. Everything seems to be working fine.
Until, I hold on my power menu than click on Reboot my phone. When I do that, my phone shuts down and reboots but it's always stuck in the Samsung Custom Screen. The max I have waited is 30 minutes for it to work. But it never does.
I'm running TWRP Recovery Mode.
I tried every roms in the AT&T Section. All of them seems to have that problem. I also used ktoonsez kernel. Nothing at all.
With stock AT&T rom everything seems to be fine.
I was wondering if it's happening to you guys as well. If you can try, please hold into your power button and reboot your phone clicking on reboot.
Thank you!
Click to expand...
Click to collapse
make sure you flashed the correct ktoonsez kernal..one for aosp, one for touchwiz
And flash Loki Doki patch if required, although you'd probably get the 'software not compatible' error if Loki was missing.
KonoeKyon said:
I have that happen sometimes, but if I go into recovery when that happens and fix permissions it boots up fine after.
Sent from my SGH-I337 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I'll try and post back to you!
TheAxman said:
Flash a different kernel.
Period
your welcome
Click to expand...
Click to collapse
If you don't mind me asking, what kernel are you using?
mixlex said:
make sure you flashed the correct ktoonsez kernal..one for aosp, one for touchwiz
Click to expand...
Click to collapse
I have used the Touchwiz kernal.
blyndfyre said:
And flash Loki Doki patch if required, although you'd probably get the 'software not compatible' error if Loki was missing.
Click to expand...
Click to collapse
Tried that and done that, no go.
________________________________________
Thank you everybody for the help.
what procedures are you using for all of this? is there a specific guide you are following?
xBeerdroiDx said:
what procedures are you using for all of this? is there a specific guide you are following?
Click to expand...
Click to collapse
So at first I used this [ROOT] Root Samsung Galaxy S4 with Motochopper. Same problem.
Went back to stock and used this
[ROOT[RECOVERY] Loki + TWRP + Motochopper CASUAL-R527b release:27May13. Same problem encountered.
Went back to stock and did it again using Same problem with this one as well.
It happens with every custom rom besides the stock rom and Cyanogenmod Rom. I can't even reboot to do anything .
Thanks for the help guys, I greatly appreciate it.
There is something else happening, does this happen on a backup you may have?
You do have a backup correct? It is rule #1
TheAxman said:
There is something else happening, does this happen on a backup you may have?
You do have a backup correct? It is rule #1
Click to expand...
Click to collapse
Yes, I do have a backup. It happens to every custom ROM that I have encountered with.
Stock & Cyanogenmod roms work fine when rebooting.
Would you mind sharing what kernel you are using? I jused used faux kernel. Same thing.
i meant more like what procedures are you using when you wipe and flash? your issue is not related to root method or a particular custom recovery.
xBeerdroiDx said:
i meant more like what procedures are you using when you wipe and flash? your issue is not related to root method or a particular custom recovery.
Click to expand...
Click to collapse
Sorry for the confusion, I used your guide!
I have the solution.
I can bet that when you wiped your phone you didnt just factory reset on twrp you WIPED the whole partition.
So when TWRP made another one it messed up thats why it doesnt work after a reboot.
I am 1000000% sure of this.
So go back to stock then factory reset through STOCK recovery and then install rom and factory reset click the icon on the left not the one on the right that makes you type 'yes'
TWRP doesnt format the partition correctly for our phones.
and the fact that the bootloader is still locked messes things up.
I am 1000000% sure of this.
are you really sure?
j/k, perfect.
TheAxman said:
I am 1000000% sure of this.
are you really sure?
j/k, perfect.
Click to expand...
Click to collapse
yep I am that sure haha.
jetlitheone said:
I have the solution.
I can bet that when you wiped your phone you didnt just factory reset on twrp you WIPED the whole partition.
So when TWRP made another one it messed up thats why it doesnt work after a reboot.
I am 1000000% sure of this.
So go back to stock then factory reset through STOCK recovery and then install rom and factory reset click the icon on the left not the one on the right that makes you type 'yes'
TWRP doesnt format the partition correctly for our phones.
and the fact that the bootloader is still locked messes things up.
Click to expand...
Click to collapse
Your method worked! Thank you very much, I greatly appreciate it.
I have a Canadian S4 and rooted using the twrp method and then installed the vigin google play edition rom. Everything worked fine at first when I installed it but i was fiddling around after in twrp and thought i should format the internal storage and start completely fresh and now if I install any rom including my original backup the device will boot up into the system fine for the first time but if the device resets after that it just hangs on the galaxy S4 logo and i have to reboot into recovery and flash again. Any ideas on how i could fix this? Thanks!!!
Try this, in twrp go into advanced wipe and wipe dalvik cache, cache, system, data and android secure. Then flash your nandroid.
I don't have a nandroid I have a twrp backup
Jaygrippa said:
I don't have a nandroid I have a twrp backup
Click to expand...
Click to collapse
That is a nandroid.
Dont use TWRP for the S4
From what I have experience and I believe others have as well, if you used TWRP to format where you had to type yes, you are pretty much screwed trying to get things working properly again. Maybe it is certain phones, sd cards, roms, who knows, but after I typed yes in TWRP to format everything, I could flash a rom but couldnt restart and things were buggy. I had to use odin to flash back to stock, re-root and flash the rom again. Now everything is 190% considering my battery life went from 6 hours to 28 with medium usage.
I have always loved TWRP on my other phones, but for the S4, its more frustration and using with caution than its worth.
Another word of caution, use windows to fix your phone. Im on linux and its too much of a pain in the ass to use odin/heimdall to go back to stock for newbs. On windows I went to stock and rooted again in no time.
Good luck!
jd1639 said:
That is a nandroid.
Click to expand...
Click to collapse
After doing that stuff in twrp should I flash right back to my backup of stock touch wiz or straight into the ROM of my choosing? Whenever I would have to reflash I would have to format he internal memory or it wouldn't work
Ya I did the thing where I typed yes... Crap ya its my first time doing all this stuff so you suggest I Re do all of the rooting stuff and then flash my backup I made?
Jaygrippa said:
Ya I did the thing where I typed yes... Crap ya its my first time doing all this stuff so you suggest I Re do all of the rooting stuff and then flash my backup I made?
Click to expand...
Click to collapse
You might have to. I had the same problem today where if the phone rebooted I would just get a black screen. I ended up using Odin with the stock rom, reinstalling twrp and then restoring my backup. I'm pretty sure it was a rom I flashed that caused the initial problem and only Odin would clear things up.
Start Over
Jaygrippa said:
Ya I did the thing where I typed yes... Crap ya its my first time doing all this stuff so you suggest I Re do all of the rooting stuff and then flash my backup I made?
Click to expand...
Click to collapse
Actually its going back to stock, then rerooting. All I did was follow androidrootz guide here:
http://www.androidrootz.com/2013/06/how-to-unroot-unbrick-galaxy-s4.html
After that, motochopper back to get root and followed this guide to install OUDHS recovery:
http://forum.xda-developers.com/showthread.php?t=2291956
This worked for me, at least for now. Hope it can help you out.
ericchaffey said:
Actually its going back to stock, then rerooting. All I did was follow androidrootz guide here:
http://www.androidrootz.com/2013/06/how-to-unroot-unbrick-galaxy-s4.html
After that, motochopper back to get root and followed this guide to install OUDHS recovery:
http://forum.xda-developers.com/showthread.php?t=2291956
This worked for me, at least for now. Hope it can help you out.
Click to expand...
Click to collapse
Hey thanks a bunch ill try that out later. I am at work right now and i can still use my phone on the rom i have just as long as i dont reset it. Ill try all of this out when i get home and see if that works. Thanks for everyones help
Now the only problem is i have to find a Fido ROM
Jaygrippa said:
Hey thanks a bunch ill try that out later. I am at work right now and i can still use my phone on the rom i have just as long as i dont reset it. Ill try all of this out when i get home and see if that works. Thanks for everyones help
Click to expand...
Click to collapse
A couple other notes, to avoid other possible problems, use the original samsung cord when connecting to your computer. Switching USB ports can help if there are transfer or other issues. Its pretty easy and straight forward if everything works out well, but there are so many gawt dayum variables that minor issues can cause problems, though may never manifest.
Hopefully this works and please post some results to help the same in need.
ericchaffey said:
A couple other notes, to avoid other possible problems, use the original samsung cord when connecting to your computer. Switching USB ports can help if there are transfer or other issues. Its pretty easy and straight forward if everything works out well, but there are so many gawt dayum variables that minor issues can cause problems, though may never manifest.
Hopefully this works and please post some results to help the same in need.
Click to expand...
Click to collapse
Ya thinks i will, now im just in the process of finding a rom for Fido, they are owned by rogers so im not sure if the rogers rom will work, This android stuff is so stressful its my first android phone so i hope all goes well!
Jaygrippa said:
Ya thinks i will, now im just in the process of finding a rom for Fido, they are owned by rogers so im not sure if the rogers rom will work, This android stuff is so stressful its my first android phone so i hope all goes well!
Click to expand...
Click to collapse
I get firmware from sammobile.com. You have to register but it's free. You'll download a zip. Use 7-zip to extract the .tar.md5 file from it. Use that in Odin, PDA.
jd1639 said:
I get firmware from sammobile.com. You have to register but it's free. You'll download a zip. Use 7-zip to extract the .tar.md5 file from it. Use that in Odin, PDA.
Click to expand...
Click to collapse
ya even they dont have a specific "Fido" firmware...
Anyone know if I can just use the Rogers ROM its pretty much the same company
Jaygrippa said:
Anyone know if I can just use the Rogers ROM its pretty much the same company
Click to expand...
Click to collapse
It'll work. It'll just put their bloatware on and the boot animation will be theirs
Reflashed
Ok so i reflashed to the stock rom using odin and bam it works again, im just wondering what is a good way now too root, and install the same rom i had
This will have everything you need http://forum.xda-developers.com/showthread.php?p=42320391
Thanks everyone for your help, I got my phone back up and running stock, then i rooted using CF- Autoroot and installed twrp again. I then reinstalled the rom i wanted to use and everything is in tip top order
Jaygrippa said:
Thanks everyone for your help, I got my phone back up and running stock, then i rooted using CF- Autoroot and installed twrp again. I then reinstalled the rom i wanted to use and everything is in tip top order
Click to expand...
Click to collapse
Glad to here it. Have fun.
Dear Friends,
I just bought a Sprint S4, and despite my half a decade experience of flashing custom ROMs and such, I seem to run into a whole lot of issues with this phone that I cannot solve or get past.
So some background first, on what's happened and been done to the phone:
1. Bought the phone (don't recall the original firmware), but Rooted it via the QBKing method.
2. Flashed TWRP 6.1 something from the GooManager
3. Have a Class 10 SD 64Gig SD Card that I formatted via S4, so I assume it's in the ExFat format?
4. Downloaded Sacs, put the ZIP on the SD
5. Booted into TWRP, Wiped, Data, Dalvik, Cache, and System
6. Tried Flashing Sacs ZIP from SD, Errored out: Something like: Flash failed, unable to read the Zip file. And some verbiage for Partition
7. I can't Mount my SD or INTERNAL via Recovery. Can read them from the Recovery file Manager, but nothing shows up on the computer, unrecognized drivers (worked fine for the same phone, later, when it was on, so I know it was the drivers that was the issue)
8. Ran straight for Odin after that, but after trying SEVERAL TARs and etc, the phone would NOT begin flashing with Odin even :'(! (Could still enter Download Mode)
9. After HOURS of trying VARIOUS Odin versions and TARs, I found a One-Click EXE with Odin Packaged with the MDC Rooted firmware this FINALLY brought the phone back to life!!
Now the issues remaining that I need your expert help and advice on:
1. Since the phone coming back to life, I went STRAIGHT for Sacs ROM again! MD5 checked it, everything looked good. Put it both on SD and Internal.
2. Made Backups of the MDC ROM
3. Tried Flashing and ran into the similar error that you saw in Step 6 from the Backgroun
4. Downloaded Stock, DeOdexed MF9 ZIP, downgraded TWRP to a stable version, and tried Flashing again and Step 6 repeated. Tried VARIOUS ROMs this way, same issue. Error flashing, something about Partition, and Couldn't read Zip. All these Zips were MD5 Sum CHECKED!
5. The lack of mounting issue as USB drives from Recovery continues
6. Then a FREAK discovery was, when the ZIP failure occurred, I opted for Flash Dalvik and Cache and tried Installing right after that, and BOOM! Sacs starts Flashing !!!
7. I broke Sacs quick, restoring things from Titanium Backup, and when I tried restoring my latest MDC Backup, it recovered with a black screen and bootloops, and NO recovery entry AGAIN :'(!! (I think I may have backed up Recovery with that Nandroid and restored)
8. So I repeated the One-Click again, the phone restored again... this time in FACTORY MODE :-/?? I ignored, and restored to an older MDC backup, which worked!
9. I downloaded TriForce MF9, this time, tried flashing and failure again with Failed Flashing, error reading Zip. And on and on it goes :'(! I can't run Odins with MF9, I can't flash ROMs, I can't mount my INTERNAL AND SD in Recovery and am just straight bummed :'(!!
I have a few hunches:
- Format SD Card as Fat32, using this one app. But I think you lose 32 gig space from your card, right? Also, why doesn't Internal storage mount from Recovery :-/?
- Maybe a I just have bad or corrupted sectors in my Internal AND External storage devices?
In either case, please treat me as a NOOB, and chime in with your thoughts and experience on what you think could be happening? I appreciate ALL your help in advance, thanks for your time !
I would try a new recovery, I have always had problems with the newer TWRPs, I recommend 2.5.0.2 or CWM
^ that, and do you have to update to mf9 before flashing an mf9 rom? That might be helpful. Are you just dirty flashing rom over rom in your attempts, that could be an issue. Wiping and factory resetting before flashing the Rom may help.
Just tossing out random ideas.
Edit: just realized I missed #5 in the first half. Sorry, and missed the stock deodexed part lol.
Sent from my SPH-L720
xchampx13 said:
I would try a new recovery, I have always had problems with the newer TWRPs, I recommend 2.5.0.2 or CWM
Click to expand...
Click to collapse
Yes Sir, I sure did downgrade TWRP, including the version you mentioned.
HPferoxCraft said:
^ that, and do you have to update to mf9 before flashing an mf9 rom? That might be helpful. Are you just dirty flashing rom over rom in your attempts, that could be an issue. Wiping and factory resetting before flashing the Rom may help.
Just tossing out random ideas.
Edit: just realized I missed #5 in the first half. Sorry, and missed the stock deodexed part lol.
Sent from my SPH-L720
Click to expand...
Click to collapse
Also a yes, Sir. MF9 kept failing, that is, it wouldn't be read by Recovery. Odin would fire the Tar either . No dirty flashing... almost EVER !
Any other ideas, guys ? Desperately need help here !
ProFragger said:
Yes Sir, I sure did downgrade TWRP, including the version you mentioned.
Also a yes, Sir. MF9 kept failing, that is, it wouldn't be read by Recovery. Odin would fire the Tar either . No dirty flashing... almost EVER !
Any other ideas, guys ? Desperately need help here !
Click to expand...
Click to collapse
Why dont you just go to stock mdc and download the update and just do a normal ota?
Take your sd card out and try flashing it from your phones storage
Sent from my SPH-L720 using XDA Premium 4 mobile app
ROMANTiC KiD said:
Why dont you just go to stock mdc and download the update and just do a normal ota?
Click to expand...
Click to collapse
That's one of my plans RomanticKid, but I'm flashed to Page Plus, wondet if the OTA will still work? I get notifications for the updates though, next time I Odin EXE, assuming that also leaves me with stock recovery, I will give it a shot. Thanks for your idea...
churchey thanks for your idea as well, tried it, I get the Zip and fail flash error ! Appreciate all the help guys, keep it coming !
churchey360 said:
Take your sd card out and try flashing it from your phones storage
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just ran into a bunch of problems. Man.. You need to be careful what you flash. Not everything is on the up and up. Steer clear of this website and their firmware. ------> http://galaxys4root.com/galaxy-s4-stock-firmware/ Unless you are intrigued by complex remote spyware. You'll be amazed with the phoney updates that inject things like a note 3 keyboard, Android device manager, and a bogus samsung hub. All of which will show AT THE BOTTOM, NOT THE TOP of your google play "all" list as installed apps.... but not in your installed apps list. They show as installed, but incompatible with your device. Go figure. Somebody had complete control of my device. It took me a minute to figure it out. Then finding a legit source of firmware here. ----->http://samsung-updates.com/device/?id=SPH-L720 I was able to get legit again. But not after encountering the problems you are having. I had to go in and manually delete a few partitions that did not belong and stayed after flashing anything. Once I did that... I flashed the MF9 firmware from samsung.updates.com (the second site I just listed above) and everything is legit now. No phoney updates. No bogus apps. Everything is perfect just like it came when I took it out of the box. Beware.... MANY of these ROM's have b.s. injected into them, and so do some of the firmwares. Take caution bro. I'd be happy to answer any questions if there are any.
Sleepycloud said:
I just ran into a bunch of problems. Man.. You need to be careful what you flash. Not everything is on the up and up. Steer clear of this website and their firmware. ------> http://galaxys4root.com/galaxy-s4-stock-firmware/ Unless you are intrigued by complex remote spyware. You'll be amazed with the phoney updates that inject things like a note 3 keyboard, Android device manager, and a bogus samsung hub. All of which will show AT THE BOTTOM, NOT THE TOP of your google play "all" list as installed apps.... but not in your installed apps list. They show as installed, but incompatible with your device. Go figure. Somebody had complete control of my device. It took me a minute to figure it out. Then finding a legit source of firmware here. ----->http://samsung-updates.com/device/?id=SPH-L720 I was able to get legit again. But not after encountering the problems you are having. I had to go in and manually delete a few partitions that did not belong and stayed after flashing anything. Once I did that... I flashed the MF9 firmware from samsung.updates.com (the second site I just listed above) and everything is legit now. No phoney updates. No bogus apps. Everything is perfect just like it came when I took it out of the box. Beware.... MANY of these ROM's have b.s. injected into them, and so do some of the firmwares. Take caution bro. I'd be happy to answer any questions if there are any.
Click to expand...
Click to collapse
Sorry to hear of your problems brother, indeed, such a pain and disappointing to go through this crap when all you want to do is enjoy the custom ROM goodness . ..
I think the key thing for me to do and understand is cleaning and or deleting partitions that you spoke of... but you'll see, I have so many issues that I keep hitting the wall one way or another . ..
I would LOVE your help if you can make some GTALK time for me?
My address is [email protected]
Appreciate your help in advance!
I just hit you up on hangouts bro.
Sent from my SPH-L720 using Tapatalk
---------- Post added at 01:11 AM ---------- Previous post was at 01:05 AM ----------
I will say this... Your problem could be entirely different than mine. There are other choices besides firmware that will fix many problems. Remapping yhe partitions with PIT files which are also flashed with odin. I wanted to be sure, so I manually deleted partitions, then flashed the good firmware I mentioned above.
Sent from my SPH-L720 using Tapatalk
Sleepycloud said:
I just hit you up on hangouts bro.
Sent from my SPH-L720 using Tapatalk
---------- Post added at 01:11 AM ---------- Previous post was at 01:05 AM ----------
I will say this... Your problem could be entirely different than mine. There are other choices besides firmware that will fix many problems. Remapping yhe partitions with PIT files which are also flashed with odin. I wanted to be sure, so I manually deleted partitions, then flashed the good firmware I mentioned above.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Hey bro... thanks for your request. .. I actually don't like Hangouts and still use Talk so I didn't get any requests . ..
Can I send you a request somewhere? Appreciate your help!
Just send it from talk. I'll get it. Its the same thing. I see you on there and it says message delivered.
Sent from my SPH-L720 using Tapatalk
Sleepycloud said:
Just send it from talk. I'll get it. Its the same thing. I see you on there and it says message delivered.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
I never got it man... may I have your Gmail to message you? Thanks!
Running an Australian N9005.
I was running Temaseks unofficial CM11 build just fine. Got bored and wanted to go back to a more Samsung styled phone.
Decided to flash X-Note. As I'd used it before CM11. It worked fine then.
Attempted to flash X-Note but it wouldn't boot, stuck at initial screen with the Kernel warnings at the top of the screen. Was told it was because I hadn't got the new 4.4 bootloader.
I was told to follow the instructions here: http://forum.xda-developers.com/showpost.php?p=46223545&postcount=2
Which I did.
Using these download links and instructions: http://forum.xda-developers.com/showthread.php?p=49931269
That fixed the boot issue. I suppose I'm not on the 4.4 bootloader.
However when I booted up the stock Polish ROM, the initial Samsung Setup Wizard would crash at the end of the setup and force me back to the start of the setup. Tried ignoring it and just flashing the custom recovery and then XNote. Same issue, the setup wizard in XNote crashes as well.
Someone then told me I should try repartitioning the device using a PIT. I don't know what that is, but it was suggested.
Using this ROM: https://mega.co.nz/#!QVwlVDgJ!QyAxmDMcsIA-56cX_28Ua2aPZLcJATVvdM07LOs0V10
And this PIT: http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77
Completes successfully.
Same issue............... That being a third separate ROM (official? at that)....
Samsung Setup Wizard crashes...
I even tried flashing XNote and removing the setup wizard just to get past it. That fixes it for about 10 minutes or so. After about 10 minutes of use the phone freezes and I have to hold the power button to force it to restart. If I leave the phone off, it still freezes, as soon as I try to unlock it it freezes and need to force restart.
I really don't know what to do now... Any help guys? I'm trying my best here...
Please, if you need any more information, please ask.
Might not help, but have you wiped your phone clean using custom recovery ( data,cache, dalvik, internal sd ) before flashing xnote or factory reset on recovery when on stock?
Do you have reactivation lock enabled?
Sent from my fingers to your face using my Samsung Galaxy Note 3!
hey_joe said:
Might not help, but have you wiped your phone clean using custom recovery ( data,cache, dalvik, internal sd ) before flashing xnote or factory reset on recovery when on stock?
Click to expand...
Click to collapse
Yes.
nicholaschum said:
Do you have reactivation lock enabled?
Click to expand...
Click to collapse
No.
This has puzzled me, not sure why it's still acting up especially after re-partitioning and flatlining everything.
radicalisto said:
This has puzzled me, not sure why it's still acting up especially after re-partitioning and flatlining everything.
Click to expand...
Click to collapse
Yes indeed. I'm very confused...
So... I don't want to get ahead of myself, but my phone seems to have sorted itself out...
I decided to just send it back to the carrier to get it replaced. So I decided to just flash the official Firmware again. (I accidentally left repartition ticked)
Once it started I thought... Oh ****... But I was sending it back anyway so who cares. (the carrier said they will just swap it for me if they can see it not working)
So I let it finish and turn it on to see what happens, run through the setup to make sure it still crashes at the same spot so I can show them... and it doesn't crash... wtf?
So I flash the custom recovery and XNote... And it seems to be working now. Now freezing, no nothing... I... I don't know...
Crazy, least it appears somewhat sorted lol
radicalisto said:
Crazy, least it appears somewhat sorted lol
Click to expand...
Click to collapse
So far, yeah... I think I got the runt of the litter or something... Haha
Reynbow said:
So far, yeah... I think I got the runt of the litter or something... Haha
Click to expand...
Click to collapse
Just out of curiosity, as I see you have an AU model, did you buy it from Kogan? -- Reason I ask is that they used HK firmware on some models and HK models have issues flashing normal firmware (similar to the issue you had)
radicalisto said:
Just out of curiosity, as I see you have an AU model, did you buy it from Kogan? -- Reason I ask is that they used HK firmware on some models and HK models have issues flashing normal firmware (similar to the issue you had)
Click to expand...
Click to collapse
Not from Kogan, no. From Optus. Pretty standard.
Hey, so I'm fairly new to the whole rooting and customizing Android, so please forgive me if I come accross "ignorant" or generally childish. I bought a galaxy note 3 the other day and researched what rooting did. After getting convince that rooting was "awesome," I actually managed to root. I also played with some Xposed modules because they were fairly simple and cool. After more research, I found out that Verizon had a locked bootloader which prevented me from using any other roms? I also read that verizon/att users can use safestrap but i couldn't exactly find some specifics for it. So whats the disadvantages of safestrap? Do specific roms have to be used?
Another concern, I'd like to get a faster rom than stock touchwiz, but i'd also like to find a rom that can use ART runtime as well as maintaining a nice multi window feature. I tried XHaloFloatingWindow and another xposed module, and I can't say I was pleased with them compared to the touchwiz one. I'd also like to maintain S-pen features? Does anybody know of any roms that may come close to fitting most of these topics?
Final, completely random question, The lg g3 has this lockscreen widget where when it rains out, drops of water will cover/slide down the entire lock screen on top of your notifications. I thought this was awesome, but wasn't sure if it was possible to get on a note 3.
Anyways, Hope to get some simple answers
ATalkingRock said:
Hey, so I'm fairly new to the whole rooting and customizing Android, so please forgive me if I come accross "ignorant" or generally childish. I bought a galaxy note 3 the other day and researched what rooting did. After getting convince that rooting was "awesome," I actually managed to root. I also played with some Xposed modules because they were fairly simple and cool. After more research, I found out that Verizon had a locked bootloader which prevented me from using any other roms? I also read that verizon/att users can use safestrap but i couldn't exactly find some specifics for it. So whats the disadvantages of safestrap? Do specific roms have to be used?
Click to expand...
Click to collapse
Safestrap is as close to a custom recovery as we'll get, right now. Due to our bootloader, stock based rom are all we can use. However, we are not stuck with one rom. Check in the dev threads for roms compatible with your device. Also check the dev and general threads for more info on rooting, safestrap, and how to flash roms.
Another concern, I'd like to get a faster rom than stock touchwiz, but i'd also like to find a rom that can use ART runtime as well as maintaining a nice multi window feature. I tried XHaloFloatingWindow and another xposed module, and I can't say I was pleased with them compared to the touchwiz one. I'd also like to maintain S-pen features? Does anybody know of any roms that may come close to fitting most of these topics?
Click to expand...
Click to collapse
Art not available for us. Only stock based. See my recommendation above for other roms. There are a few with some pretty cool features and add-ons!
Final, completely random question, The lg g3 has this lockscreen widget where when it rains out, drops of water will cover/slide down the entire lock screen on top of your notifications. I thought this was awesome, but wasn't sure if it was possible to get on a note 3.
Anyways, Hope to get some simple answers
Click to expand...
Click to collapse
Not sure about this one...
Not sure about your specific questions, as I don't use multiwindow or the other features you listed. But I thought I would point out, what method of root did you use? Make sure of what system your running at this point. beans or kitkat? You will have to select a rom based on that. Or vice versa, re-root if you find a rom that you prefer thats running different android version. Either one will run safestrap obviously, since there are roms for each. You will find pros and cons to each. The con that I'm currently experiencing on kitkat that has me thinking about going back is I can't seem to find a modem that will get me decent reception so I'm assuming at this point that its kitkat thats causing it. Just something more for you to research. Being new to it, you've got ALOT of material to read about. But if you've already rooted, sounds like you've got a decent idea of the process. For me, tutorial videos were a life saver
LeftyGR said:
Safestrap is as close to a custom recovery as we'll get, right now. Due to our bootloader, stock based rom are all we can use. However, we are not stuck with one rom. Check in the dev threads for roms compatible with your device. Also check the dev and general threads for more info on rooting, safestrap, and how to flash roms.
Art not available for us. Only stock based. See my recommendation above for other roms. There are a few with some pretty cool features and add-ons!
Not sure about this one...
Click to expand...
Click to collapse
Alright so perhaps you can help me with just a few more concerns. I researched roms and such. I successfully downloaded safestrap, made a backup of my stock rom and put it on mycomputer. I also made a backup with titanium backup before that and it is also on the computer. I am looking at hyperdrive or jasminerom for the note 3. On there, it explains normal directions to install, but then it says to flash with odin, but when I read something about a tutorial how to install cutom roms on a website "Galaxynote3root" (I can't post the URL yet, says i'll be spamming) , it explained nothing of odin. What is odin? is it mandatory? Does my phone have it by default? hm.... Also i have a build number of NC4, does that build not work with NC2? sorry for inconvenience or annoying noobish questions. Thanks if you respond
So being on Kitkat, did you use the beans method that installed a rom with root basically built in already? And by saying you downloaded safestrap, is it successfully installed? When you boot the phone, do you get the safestrap bootup screen allowing to go into recovery?
If you've already gotten that far, your pretty well set to install either of those roms.
LeftyGR said:
Safestrap is as close to a custom recovery as we'll get, right now. Due to our bootloader, stock based rom are all we can use. However, we are not stuck with one rom. Check in the dev threads for roms compatible with your device. Also check the dev and general threads for more info on rooting, safestrap, and how to flash roms.
Art not available for us. Only stock based. See my recommendation above for other roms. There are a few with some pretty cool features and add-ons!
Not sure about this one...
Click to expand...
Click to collapse
scott_65 said:
So being on Kitkat, did you use the beans method that installed a rom with root basically built in already? And by saying you downloaded safestrap, is it successfully installed? When you boot the phone, do you get the safestrap bootup screen allowing to go into recovery?
If you've already gotten that far, your pretty well set to install either of those roms.
Click to expand...
Click to collapse
Well i rooted my phone via towelroot. I got safestrap hooked up and installed, so in other words when i reboot, yes it does have the splash screen. I am on kitkat as well. but do i need to install some sort of odin or something? sorry
I think as long as the rom's op says it's based on nc2 or nc4, you should be good. You should not need to worry about odin, since you're already on kk.
Since you're new, I'd suggest not touching the stock slot. It gives you a fall back if something goes wrong. Make sure you understand using safestrap, and start trying some stuff out.
---------- Post added 30th July 2014 at 12:00 AM ---------- Previous post was 29th July 2014 at 11:58 PM ----------
scott_65 said:
So being on Kitkat, did you use the beans method that installed a rom with root basically built in already? And by saying you downloaded safestrap, is it successfully installed? When you boot the phone, do you get the safestrap bootup screen allowing to go into recovery?
If you've already gotten that far, your pretty well set to install either of those roms.
Click to expand...
Click to collapse
Sounds like he rooted the nc4 with towelroot, cuz he started on nc4. And sounds like ss is working for him, if he's made a backup.
LeftyGR said:
I think as long as the rom's op says it's based on nc2 or nc4, you should be good. You should not need to worry about odin, since you're already on kk.
Since you're new, I'd suggest not touching the stock slot. It gives you a fall back if something goes wrong. Make sure you understand using safestrap, and start trying some stuff out.
Click to expand...
Click to collapse
Okay thanks, that boosts my confidence a bit! I'm just afraid of bricking my phone, as any noobie should be.
ATalkingRock said:
Okay thanks, that boosts my confidence a bit! I'm just afraid of bricking my phone, as any noobie should be.
Click to expand...
Click to collapse
Good man.
If you find something that you don't know or understand, search that thread for an answer. Then ask if you don't find an answer. And always try to give any other details you think might help.
As long as you remember search is your friend first...then ask...you will almost always find people to help you out!
LeftyGR said:
Good man.
If you find something that you don't know or understand, search that thread for an answer. Then ask if you don't find an answer. And always try to give any other details you think might help.
As long as you remember search is your friend first...then ask...you will almost always find people to help you out!
Click to expand...
Click to collapse
alright alright I'm very sorry for this final question as I actually have tried to search for this but only got comparisons between titanium backup and safestrap. So, if I were to make a titanium backup right now, after the fact that i made a safestrap backup or installation, will that effect anything? I'm really really sorry if these questions are beyond beginner, I just like to play it safe.
ATalkingRock said:
alright alright I'm very sorry for this final question as I actually have tried to search for this but only got comparisons between titanium backup and safestrap. So, if I were to make a titanium backup right now, after the fact that i made a safestrap backup or installation, will that effect anything? I'm really really sorry if these questions are beyond beginner, I just like to play it safe.
Click to expand...
Click to collapse
Nope. Tibu backs up specific apps and it's associated data and stores it on sd. When you open tibu, it gets it's info from files it stores on sd. Recovery backs up your entire rom environment, but doesn't actually touch sd card user space.
This is why tibu is so helpful. Everything pops up that you had backed up, even on a new rom.
I'm not familiar with the towelroot method. Only the old Kingo for jb, or the beans method for kk. Sounds like your good to go for any KK roms, and Lefty seems familiar, good deal. Not sure how old you are or how far back your computer knowledge goes, so this may do you no good. Odin doesn't go on your phone, it goes on your computer. I always think of it as the old school DOS, or like now when you boot to command prompt if windows isn't working. Its like a back door when your phone operating system isn't working, or if you need to make changes to part of the system that would otherwise need to be running to make those changes FROM the phone. Its flashes the changes TO the phone from your computer instead.
I'm rambling. Its too early. Anyhow, glad your getting things moving along. You can try roms in various rom slots, but you may have issues. I had some roms work well, others not well at all. The ones that have problems, they seem to work better in the stock slot. So you have to wipe the stock slot and flash it there. No big deal, just don't goof up, flash it all at once. If you pause, take a potty break and the battery dies, whatever, don't forget, you have no operating system at that point. Thats when Odin would come into play
LeftyGR said:
Nope. Tibu backs up specific apps and it's associated data and stores it on sd. When you open tibu, it gets it's info from files it stores on sd. Recovery backs up your entire rom environment, but doesn't actually touch sd card user space.
This is why tibu is so helpful. Everything pops up that you had backed up, even on a new rom.
Click to expand...
Click to collapse
Alright so quick update. I successfully installed both roms into slots 1 and 2 respectively. Everything went okay, I rebooted system, but the screen just stayed black. They aren't loading, i still can go back to stock rom. But uhm any idea as to why this is occuring? Could it be the NC4/NC2 build things?
In the hyperdrive rom for the note 3, it says it will work with verizon and also states that after the initial reboot after flashing the rom, there will be a 10 minute wait until it actually boots up. I'd say i've waited 15 minutes and nothing has shown up. So I'm assuming something went wrong. Perhaps i should try to reflash it?
EDIT: I read the directions further ahead and managed to flash a file via odin for the first time, now im getting a rom's boot animation which is good. I hope this'll work !
Edit 2: I successfully installed it and booted it up, everything went okay, I restored my titanium backup and then titanium prompted me to restart. I restarted, and now its bootlooping android.process.acore or something like that is crashing everything =/
ATalkingRock said:
Alright so quick update. I successfully installed both roms into slots 1 and 2 respectively. Everything went okay, I rebooted system, but the screen just stayed black. They aren't loading, i still can go back to stock rom. But uhm any idea as to why this is occuring? Could it be the NC4/NC2 build things?
In the hyperdrive rom for the note 3, it says it will work with verizon and also states that after the initial reboot after flashing the rom, there will be a 10 minute wait until it actually boots up. I'd say i've waited 15 minutes and nothing has shown up. So I'm assuming something went wrong. Perhaps i should try to reflash it?
EDIT: I read the directions further ahead and managed to flash a file via odin for the first time, now im getting a rom's boot animation which is good. I hope this'll work !
Edit 2: I successfully installed it and booted it up, everything went okay, I restored my titanium backup and then titanium prompted me to restart. I restarted, and now its bootlooping android.process.acore or something like that is crashing everything =/
Click to expand...
Click to collapse
uh oh now my stock rom is bootlooping as well. i in trouble
ATalkingRock said:
uh oh now my stock rom is bootlooping as well. i in trouble
Click to expand...
Click to collapse
What did you flash in odin?
LeftyGR said:
What did you flash in odin?
Click to expand...
Click to collapse
In JasmineRom's instructions it says to flash a file called unified_KK_Firmware_RE.tar.md5. After flashing it, it booted up to the new rom.But seemingly once i restarted after titanium backup restored everything it crashed. I then cleared all the cache and data through a factory reset in the safestrap settings and it started up normally. Am I not going to be able to restore my things through titanium? I would send you a link to the odin flash file, but I can't until I have a certain number of posts
ATalkingRock said:
In JasmineRom's instructions it says to flash a file called unified_KK_Firmware_RE.tar.md5. After flashing it, it booted up to the new rom.But seemingly once i restarted after titanium backup restored everything it crashed. I then cleared all the cache and data through a factory reset in the safestrap settings and it started up normally. Am I not going to be able to restore my things through titanium? I would send you a link to the odin flash file, but I can't until I have a certain number of posts
Click to expand...
Click to collapse
No need. I know what you're saying. So flashing that file shouldn't have been really necessary, given you're already on nc4. But it doesn't hurt and should not have caused what you described. So you have roms in stock, slot 1, and slot 2? Which ones bootloop?
For tibu, I would uninstall, reboot, reinstall. Somehow it didn't like you doing that.
LeftyGR said:
No need. I know what you're saying. So flashing that file shouldn't have been really necessary, given you're already on nc4. But it doesn't hurt and should not have caused what you described. So you have roms in stock, slot 1, and slot 2? Which ones bootloop?
For tibu, I would uninstall, reboot, reinstall. Somehow it didn't like you doing that.
Click to expand...
Click to collapse
Alright so as we speak right now, I have slot 1 with jasminerom and stock which should be the untouched stock rom of course. I have a backup through safestrap of that. I will uninstall titaniumbackup and reinstall and see if that works?
edit: sorry I feel as though I'm being unclear as I can hardly comprehend my own messages. Before, both slot 1 and stock were bootlooping. This bootloop came after titanium backup promted me to restart. But when i cleared the cache through the factory reset, the slot1 rom started to work agin (jasminerom), I haven't tried stock rom to see if it works yet. I'm currently on jasminerom about to re-restore my apps through titanium backup like you said.
LeftyGR said:
No need. I know what you're saying. So flashing that file shouldn't have been really necessary, given you're already on nc4. But it doesn't hurt and should not have caused what you described. So you have roms in stock, slot 1, and slot 2? Which ones bootloop?
For tibu, I would uninstall, reboot, reinstall. Somehow it didn't like you doing that.
Click to expand...
Click to collapse
alright i finished re-restoring through titanium backup. Once it finished it provided a notification saying "batch complete, 66 elements failed" Right now all my apps are here and everything is seeming to work. Should I restart to see if it bootloops again?
ATalkingRock said:
alright i finished re-restoring through titanium backup. Once it finished it provided a notification saying "batch complete, 66 elements failed" Right now all my apps are here and everything is seeming to work. Should I restart to see if it bootloops again?
Click to expand...
Click to collapse
You should be ok. How many apps did you try to restore, if 66 failed?