Hey Guys
I'm a experienced flasher but I have ran into a issue with flashing roms on my Note 3. I had recently just been running stock rooted rom (basically I rooted my phone the day it came out with Sprint and never have update anything). So when I noticed that ny son's note 3 (note rooted) got an update recently, I decided to look for an updated base and broadband for my phone, which I thought I had found. So after so help with figuring out which update I needed to do, I figured NH7 was the latest. Finally got my phone updated or so it appeared.
So this week I've been trying desperately to update to MOAR S5 PORT (NE5 based I believe) I followed the instructions carefully and tried all 3 versions. All failed. So I restored my phone. Tonight I tried flashing flashing Pac-man rom. Same thing happened. Failed during install.
Can you guys take a look at my setup and tell me what may be wrong? Doing a clean install each time.
Sent from my SM-N900P using XDA Premium 4 mobile app
UPDATED 10/24/2014:
I had to reflash all the Note 3 stock tar's in order. Then root with Chainfire Auto Root. Then install Clockwork MOD Recovery. Now I can flash roms.
shaun0207 said:
Hey Guys
I'm a experienced flasher but I have ran into a issue with flashing roms on my Note 3. I had recently just been running stock rooted rom (basically I rooted my phone the day it came out with Sprint and never have update anything). So when I noticed that ny son's note 3 (note rooted) got an update recently, I decided to look for an updated base and broadband for my phone, which I thought I had found. So after so help with figuring out which update I needed to do, I figured NH7 was the latest. Finally got my phone updated or so it appeared.
So this week I've been trying desperately to update to MOAR S5 PORT (NE5 based I believe) I followed the instructions carefully and tried all 3 versions. All failed. So I restored my phone. Tonight I tried flashing flashing Pac-man rom. Same thing happened. Failed during install.
Can you guys take a look at my setup and tell me what may be wrong? Doing a clean install each time.
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Wipe wipe Wipe and when it fails to flash then restart recovery And it will flash then ....
So wipe 3 times. Then when it fails. Reboot to recovery and flash again? Do I need to wipe again before flashing?
Sent from my LGLS990 using XDA Free mobile app
shaun0207 said:
So wipe 3 times. Then when it fails. Reboot to recovery and flash again? Do I need to wipe again before flashing?
Sent from my LGLS990 using XDA Free mobile app
Click to expand...
Click to collapse
Any time you wipe the system partition, you MUST restart TWRP recovery before flashing the rom of your choice,.. or it'll fail every time.
Ok. I will try that noq
Sent from my SM-N900P using XDA Premium 4 mobile app
shaun0207 said:
Ok. I will try that now
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my SM-N900P using XDA Premium 4 mobile app
shaun0207 said:
Ok. I will try that noq
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Let us know how it goes. Happy flashing.
So I wiped everything. Tried to install and it failed. So i go to reboot to recovery and it ask me about superuser. But it doesnt install because their is no OS. REBOOT to recovery and it fails again
Do I need to format data?
Actually I dont even see a option in TWRP to format data
I wonder if I should try a dirty flash?
I would odin flash a full stock nh7. To get you all the way to nh7. I see you are still at nab on one. I had problems when they weren't all the same. I could be wrong.... I'm a noob. lol
Then, root with chanfires autoroot. Install your recovery. Then, flash your rom of choice.
NOTE: I said nh7.... but, if the rom you want to use isn't, then odin to nab or whatever the rom you want to run is. I don't know about downgrading, could make a brick.... lol
Research everything I said before you do anything! Or wait for someone to correct what's wrong with what I said! I take no responsibility for what you do to your phone!
one of your issues is you updated wrong! unless you were on nc5 you shouldnt jump right to nh7. you have to update in order to insure no issues. so if oyu were nqb or ever mi3 you need to go in order mi3>nab>nc5>nh7
Chainfires auto root.....http://download.chainfire.eu/362/CF-Root/CF-Auto-Root/CF-Auto-Root-hltespr-hltespr-smn900p.zip
Here is Supersu download.....so when you check to see if you have root.....it will all be good.......http://download.chainfire.eu/578/SuperSU/UPDATE-SuperSU-v2.14.zip
Odin v3.07.......http://forum.xda-developers.com/showthread.php?t=1738841
now you can try to go back to stock and flash whichever you are going to flash........or you can do a reflash of whatever you want....I have notice a losss of root also too.
also make sure to look into all those fixes for security patches xda has for our phone......download and scan with bluebox security and search for any open links that have a fix here on xda........
this happened to me the other weekend and it took an afternoon to dig all resources to figure out why and what i needed to do........I started rooting with a samsung moment......
I am back to stock.....no complaints.....but only did to get home before i go back to a rom.......hope we have helped....
Thanks guys. I will try all of these
shaun0207 said:
Thanks guys. I will try all of these
Click to expand...
Click to collapse
to get updates to stick via odin. remove sd card too. and when you update each version. boot to stock recovery wipe phone. flash again. what i do on each update. never had a single issue.
shaun0207 said:
Do I need to format data?
Click to expand...
Click to collapse
Yes you have to do that.. Also I believe you have to be in twrp 2.8 for kitkat I was having problems too until I installed the new Twrp!
bigkev904 said:
Yes you have to do that.. Also I believe you have to be in twrp 2.8 for kitkat I was having problems too until I installed the new Twrp!
Click to expand...
Click to collapse
I dont see a new TWRP. All I see is version 2,8
I installed all the updates back to back. I have TWRP installed and I'm on NH7 now. But I cant get root. Chainfire Auto took me back to stock recovery and I'm not rooted. So I flashed TWRP via Odin and flashed ChainFire Superuser v.2.14 and I'm still not rooted. All thought it say it worked. So WHen I reboot, what do I need to do then? I have SU installed
Ok guys. After flashing all the Roms in order via ODIN. I finally have NH7 working and rooted.
I just tried wiping system, data,dalvik and cache. Then I immediately rebooted to recovery and tried to flash MOAR V1. and Pac-man rom. Both failed.
One thing Im noticing in recovery is that the system is not mounted in when wiping. So I tried wiping with and without system being mounted and got the same result. One thing Im not sure about with flashing for the note is if the Data should be formatted before installing? However I dont see that option in TWRP.
This is the only phone Ive had this much trouble with when it came to flashing.
Any ideas?
Sent from my SM-N900P using XDA Premium 4 mobile app
Related
I have an AT&T Note that I rooted using the Odin method. I was running stock ICS and I know the root worked because I was able to install Google Now and it worked fine.
So I decided I wanted to try a different ROM. I just wanted to install bigfau's cleaned up stock rom found here. I put the zip file on my phone, booted into CWM, did a wipe, found the zip, said it installed fine and then I rebooted. At boot it just sits at the Samsung screen. I let it sit for 30 minutes, still nodda.
So I grab odin and flash back to stock ICS. Use the same method to root and I try a different ROM. This time the Pure Stock ICS from bigfau, same problem.
Odin back to stock, root, and I try parandoidandroid found here - same problem.
Do it all again and try a ROM from another site called HYFR Only One, which is a SGS3 based rom. Same deal.
The only thing I can get it to do is ODIN to stock. Am I missing something?
(I have another rooted galaxy note that I do not have any issues with flashing roms but it was already rooted when I got it.)
berdo said:
I have an AT&T Note that I rooted using the Odin method. I was running stock ICS and I know the root worked because I was able to install Google Now and it worked fine.
So I decided I wanted to try a different ROM. I just wanted to install bigfau's cleaned up stock rom found here. I put the zip file on my phone, booted into CWM, did a wipe, found the zip, said it installed fine and then I rebooted. At boot it just sits at the Samsung screen. I let it sit for 30 minutes, still nodda.
So I grab odin and flash back to stock ICS. Use the same method to root and I try a different ROM. This time the Pure Stock ICS from bigfau, same problem.
Odin back to stock, root, and I try parandoidandroid found here - same problem.
Do it all again and try a ROM from another site called HYFR Only One, which is a SGS3 based rom. Same deal.
The only thing I can get it to do is ODIN to stock. Am I missing something?
(I have another rooted galaxy note that I do not have any issues with flashing roms but it was already rooted when I got it.)
Click to expand...
Click to collapse
Rooted has nothing to do with flashing a ROM, having CWM or TWRP will give you the cap to flash a ROM.
I have used these Recovery types for flashing:
Touch CWM: http://forum.xda-developers.com/showthread.php?t=1584576
TWRP: http://forum.xda-developers.com/showthread.php?t=1647575
After you have CWM of some type ensure you are doing a clean wipe, this is how I perform my wipes:
1. Download to sdcard
2. Reboot to CWM-based Recovery
3. Wipe data/factory reset
4. Wipe Cache partition
5 Go into advanced> Wipe Dalvik Cache
6. Go into> Mounts & Storage
a. Format /data
b. Format /system
c. Format /cache
Install rom & Reboot
After the first boot up let it sit for a few min to build...then do your set ups.
btw there is a Q&A section.
bigjoe2675 said:
Rooted has nothing to do with flashing a ROM, having CWM or TWRP will give you the cap to flash a ROM.
I have used these Recovery types for flashing:
Touch CWM: http://forum.xda-developers.com/showthread.php?t=1584576
TWRP: http://forum.xda-developers.com/showthread.php?t=1647575
After you have CWM of some type ensure you are doing a clean wipe, this is how I perform my wipes:
1. Download to sdcard
2. Reboot to CWM-based Recovery
3. Wipe data/factory reset
4. Wipe Cache partition
5 Go into advanced> Wipe Dalvik Cache
6. Go into> Mounts & Storage
a. Format /data
b. Format /system
c. Format /cache
Install rom & Reboot
After the first boot up let it sit for a few min to build...then do your set ups.
Click to expand...
Click to collapse
I apologize if I did not make this clear but I have Rom Manager installed and CWM was updated to the latest version. I would reboot into CWM, do a factory reset, wipe cache, dalvik caceh, install rom and reboot. It would just sit at the samsung screen. I did not go into mounts and storage and do that but I will now. The process I use on my AT&T note is the same process I used on my Rogers note and I am able to install any ROM i want on my rogers note.
I have flashed roms probably over 100 times since my samsung captivate. I just didn't know if the note had another step involved. Like S-Off on HTC phones for example.
I have been using the standard version of cwm but I am trying the touch version now. Will update.
Same problem. I am uploading a video to youtube now. I will post in a minute or so.
did you check if bootloader is unlocked?
berdo said:
Same problem. I am uploading a video to youtube now. I will post in a minute or so.
Click to expand...
Click to collapse
U have busy box installed?
Sent from my SAMSUNG-SGH-I717 using xda premium
animatechnica said:
did you check if bootloader is unlocked?
Click to expand...
Click to collapse
elry567 said:
U have busy box installed?
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Animatechnica - It is my understanding that the bootloader is not locked on the Galaxy Note. I have not seen anything about unlocking the bootloader in any thread on the i717.
elry567 - do not have busy box installed - never saw anything requiring it to be installed. I will try that as well.
Well this time I got a status 7 error in CWM which can be a lot of different things. I am up to date on CWM, the rom I know works for the galaxy note (I am running it on my other one AND I have seen video of it working on an AT&T branded Note) so I don't know. I did a google search on the error and everything I found does not seem to apply. It is really starting to piss me off. Any help is appreciated.
Here is the video, sorry about my cam skills but you get the gist. I took this video with a i717r that is running the rom I want to install on the phone in the video.
Are you entering recovery with the phone off then using the buttons, or flashing from rom manager?
You should be doing it by the button method.
rangercaptain said:
Are you entering recovery with the phone off then using the buttons, or flashing from rom manager?
You should be doing it by the button method.
Click to expand...
Click to collapse
Done both, doesn't seem to make a difference. I will definitely use the button method from here on out though.
Try using TWRP? It seems CWM doesn't want to work for you, so try using TWRP instead.
Sent from my SAMSUNG-SGH-I717 using xda premium
Zwarx said:
Try using TWRP? It seems CWM doesn't want to work for you, so try using TWRP instead.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
HOLY F&(%*&G $&!t twrp may have worked. I had to go full back to 100% stock with 3e recovery and 0 flash counter. Use a new root method, flash twrp via goo app and so far so good.
Seriously I do not know who you are but I could kiss you. I wonder why CWM wouldn't work? I have used it to load custom roms on just about every other android phone I have had.
OH well, consider this solved.
Zwarx said:
Try using TWRP? It seems CWM doesn't want to work for you, so try using TWRP instead.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
+1
berdo said:
HOLY F&(%*&G $&!t twrp may have worked. I had to go full back to 100% stock with 3e recovery and 0 flash counter. Use a new root method, flash twrp via goo app and so far so good.
Seriously I do not know who you are but I could kiss you. I wonder why CWM wouldn't work? I have used it to load custom roms on just about every other android phone I have had.
OH well, consider this solved.
Click to expand...
Click to collapse
Sir, he is one of many, that is part of this great Community the GNote. As you can see we just provide the tools and point you to the way we went...it is up to you to get it going, and you did by the see of it....slap a thanks to all these that posted in your thread, (not me) due to the fact, I have seen threads go viewed many times that have no one replies to it, but not around here....
glad it worked out..
bigjoe2675 said:
+1
Sir, he is one of many, that is part of this great Community the GNote. As you can see we just provide the tools and point you to the way we went...it is up to you to get it going, and you did by the see of it....slap a thanks to all these that posted in your thread, (not me) due to the fact, I have seen threads go viewed many times that have no one replies to it, but not around here....
glad it worked out..
Click to expand...
Click to collapse
Done.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Credits: Our thanks to Samsung-Updates.com for posting MI3/MI5.
Until I have time to clean this up I figured I would post this now and we'll update it later.
It's more important to make sure people have this while testing new things.
Samsung-Updates.com has posted MI3 here:
http://samsung-updates.com/details/14398/Galaxy_Note_3_Sprint/SM-N900P/SPR/N900PVPUBMI3.html
MI5 Link:
http://samsung-updates.com/details/14398/Galaxy_Note_3_Sprint/SM-N900P/SPR/N900PVPUBMI5.html
As usual we're putting it up on Rwilco's repository. I am not doing anything with them though for a few reasons.
1) At the moment neither I or rwilco12 have a device to test with.
2) Given the issues with Knox I am leary in doing anything without addressing #1.
Link to Stock ROMs:
http://www.rwilco12.com/downloads.php?dir=Files/Devices/Samsung Galaxy Note 3 (SM-N900P)/Stock ROMs/
Download, flash in Odin/Heimdall. This current version will wipe your data.
TESTED AND WORKING - Great Work bud!
Any other DL links? Its not downloading anything.. On either link. Thanks
EDIT: Might be on my end I think it is working now. I already did something and messed it up. Very easy fix but I cant believe the n00b mistake I did lol. Oh well
Edit 2: Last one lol but link did work and was able to restore. Thanks!
problem
For some reason im stuck at the sprint boot screen after using this any ideas?
ok its fine just takes longer to fully restart than gn2 did
humdrum2009 said:
For some reason im stuck at the sprint boot screen after using this any ideas?
ok its fine just takes longer to fully restart than gn2 did
Click to expand...
Click to collapse
Yellow Sprint screen? I'm stuck at that one as well... How long did you have to wait?
Have you guys tried wiping data in stock recovery after the full Odin restore?
lmemma16 said:
Have you guys tried wiping data in stock recovery after the full Odin restore?
Click to expand...
Click to collapse
I don't think this is Kies version so it should wipe.
Sent from my SPH-L900 using Tapatalk 4
I'll have a how to video up as soon as it's all said and done. I got my Note 3 two days ago!
Couple questions
I am roped with TWRP but want to reinstall the stock ROM again but keep my recovery and hopefully root.
Will this allow that? I'd so how do I flash it?
Also saw this was MI3 if I do flash this can I update to MI5 again after?
Sent from my SM-N900P using Tapatalk now Free
miguelfp1 said:
Yellow Sprint screen? I'm stuck at that one as well... How long did you have to wait?
Click to expand...
Click to collapse
lmemma16 said:
Have you guys tried wiping data in stock recovery after the full Odin restore?
Click to expand...
Click to collapse
Mine was stuck on the yellow sprint screen. I went in the stock recovery and wiped data, and after that it loaded up perfect. So if you are stuck on the sprint screen, try that and it might help you.
Here is a Direct link hosted on my server nice and fast
http://storagecow.eu/index.php?dir=Xda/Galaxy+Note+3/Sprint/Stock+ODIN/
does anyone know if your rooted and run this m13 will it allow you to update to m15 afterwards
xoreactionzox said:
does anyone know if your rooted and run this m13 will it allow you to update to m15 afterwards
Click to expand...
Click to collapse
Exactly my question hopefully someone can chime in.
EJerVJerO said:
Exactly my question hopefully someone can chime in.
Click to expand...
Click to collapse
ok i went ahead an tryed to restore to stock with this because some how my sprint apps got removed when i was messing with root
anyways it worked i ran it in odin as pda with only auto reboot and f reset time check which worked perfectly besides it was a upgrade an not a restore like i thought so my sprint apps are still gone
although it did let me update to m15 with out getting a your device is modified error
xoreactionzox said:
ok i went ahead an tryed to restore to stock with this because some how my sprint apps got removed when i was messing with root
anyways it worked i ran it in odin as pda with only auto reboot and f reset time check which worked perfectly besides it was a upgrade an not a restore like i thought so my sprint apps are still gone
although it did let me update to m15 with out getting a your device is modified error
Click to expand...
Click to collapse
How did you get it to upgrade to m15?
Tar works great. Checked phone version about 3 hrs later and it is m15 for those wondering.
---------- Post added at 07:54 PM ---------- Previous post was at 07:53 PM ----------
bigmase23 said:
How did you get it to upgrade to m15?
Click to expand...
Click to collapse
I didnt do anything. i just restored with this Tar and evidently it is already m15 as i didnt press any update buttons.
bigmase23 said:
How did you get it to upgrade to m15?
Click to expand...
Click to collapse
After using the tar it takes a minute to boot up once it did I went thru the setup like a new phone the first time it didn't do it booted from where it left off but sense I factory reset the second time it was like a new start up
Anyways I just connected my wifi and skipped everything else went to system update clicked to check for updates an it was already downloading the 19mb m15 update
Sent from my SM-N900P using xda app-developers app
i tried flashing the rooted MI5 from freeza and im stuck at the sprint screen. would using this file along with ODIN finally make my phone start working again?
I would try to wipe an flash the rooted rom again then if nothing put ur phone in download mode an flash this tar in Odin an it will restore u to stock like new
Sent from my SM-N900P using xda app-developers app
xoreactionzox said:
I would try to wipe an flash the rooted rom again then if nothing put ur phone in download mode an flash this tar in Odin an it will restore u to stock like new
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
i redownloaded the rom twice and have had the same result. I am using TWRP. i think ill use odin, update the ROM though OTA and reroot and install TWRP again. don't know why my phone is being dumb and not booting the ROM, just bought this beast and i wanna play around with it
Hey guys, I need help.
I consider myself fairly adept at handling rooted devices, but I have not been following development for the GS4 for the last several months and have been running the last release of Synergy before their hiatus.
I was going to try out something different. I always enjoyed Beanstown's Jelly 'Beans', and thought I would try Build 7.
Now I am stuck at the Samsug Galaxy Boot Logo and it never goes to the Custom Boot Screen.
WORSE...I managed to break my recovery...so it will not boot their either.
Only mode I can boot to is Download.
Maybe I am just blind but I searched and could not find any Odin flashable recoveries...does anyone have one? Is there a rooted MDK file out there that I can flash via Odin?
Someone please help
Did you do the proper wipes when flashing the new rom? There arent any odin flashable recoveries for the s4. I would probably use the no wipe mdk image to recover (wont lose any user data) since you have no custom recovery to flash something with. Youll have to start over but youll have a working phone at least.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Yes...I always wipe well when I am flashing. Almost every problem I have ever had going back to the Droid 1 was from a Dirty Wipe. I also tried searching for issues and warnings before moving forward...but did not find anything with my searches.
So just to be sure I have this right...start with this
http://forum.xda-developers.com/showthread.php?t=2301259&highlight=mdk
Then re-root as I did originally
http://forum.xda-developers.com/showthread.php?t=2290798
Then I can reflash CWM Recovery from Rom Manager? Will it automatically flash loki'd version?
Finally once there...can I just flash Beantown's Jelly Beans Build 7 or do I need to update the radios first? Can I use the just the MJ7 modem from the post below or do I need other parts updated too?
http://forum.xda-developers.com/showthread.php?t=2487298
Thanks all!
jbg25 said:
Yes...I always wipe well when I am flashing. Almost every problem I have ever had going back to the Droid 1 was from a Dirty Wipe. I also tried searching for issues and warnings before moving forward...but did not find anything with my searches.
So just to be sure I have this right...start with this
http://forum.xda-developers.com/showthread.php?t=2301259&highlight=mdk
Then re-root as I did originally
http://forum.xda-developers.com/showthread.php?t=2290798
Then I can reflash CWM Recovery from Rom Manager? Will it automatically flash loki'd version?
Finally once there...can I just flash Beantown's Jelly Beans Build 7 or do I need to update the radios first? Can I use the just the MJ7 modem from the post below or do I need other parts updated too?
http://forum.xda-developers.com/showthread.php?t=2487298
Thanks all!
Click to expand...
Click to collapse
Yeah looks like you got everything in order. Rom manager or rom toolbox will auto loki the recoveries. No need to update radios when flashing beans either. Itll already have the radios included unless your wanting to flash the mj7 radio seperately then I believe youll be ok doing that. I havent done alot of reading on the newest radios.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Back up and running with stock rooted MDK and CWM Recovery.
Now to try and flash a ROM.
jbg25 said:
Back up and running with stock rooted MDK and CWM Recovery.
Now to try and flash a ROM.
Click to expand...
Click to collapse
good deal just saw your pm was gonna say flash mdk odin but it looks like you found it
beanstown106 said:
good deal just saw your pm was gonna say flash mdk odin but it looks like you found it
Click to expand...
Click to collapse
Thanks for getting back to me! :good:
I am up and running...but with but not with 'Beans' Build 7 ... I have tried everything...and no matter what it stalls at the SGS4 Splash Screen and never progresses.
I thought maybe it was the new recovery I flashed ( CWM Touch Recovery 6.0.4.4) .... BUT I got Hyperdrive to install and boot. So maybe my SGS4 just doesn't like Beans...which sucks cause I ran that almost exclusively on my SGS3.
jbg25 said:
Thanks for getting back to me! :good:
I am up and running...but with but not with 'Beans' Build 7 ... I have tried everything...and no matter what it stalls at the SGS4 Splash Screen and never progresses.
I thought maybe it was the new recovery I flashed ( CWM Touch Recovery 6.0.4.4) .... BUT I got Hyperdrive to install and boot. So maybe my SGS4 just doesn't like Beans...which sucks cause I ran that almost exclusively on my SGS3.
Click to expand...
Click to collapse
Try TWRP 2.5.0.2.
Most of the devs use it.
Sent from my SCH-I545 using xda app-developers app
Mightycaptain said:
Try TWRP 2.5.0.2.
Most of the devs use it.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I downloaded and installed the latest TWRP 2.6.3.0 from DsLNeXuS's Recovery Tools App as Goo Manager is not finding a recovery for my device.
Still no good...nothing I do makes Beans Build 7 work ....
jbg25 said:
I downloaded and installed the latest TWRP 2.6.3.0 from DsLNeXuS's Recovery Tools App as Goo Manager is not finding a recovery for my device.
Still no good...nothing I do makes Beans Build 7 work ....
Click to expand...
Click to collapse
Go here. Get 2.5.0.2
http://techerrata.com/browse/twrp2/jfltevzw
Instructions
http://teamw.in/project/twrp2/181
At the bottom of the page.
Edit;
Or flash this in recovery
http://forum.xda-developers.com/showthread.php?p=45006486
I would reboot to recovery after flashing to make you got it on the right version.
Then make sure you can still boot back to your rom.
Then go back to recovery
Wipe
Factory reset.
Advanced
Check system, Data, davlik and cache
Wipe
Go back to main screen
Install
Fund your rom to flash.
Sent from my SCH-I545 using xda app-developers app
Me too. I tried the [ROM][TW4.3]STOCK-ROOTED-MJ7-AROMA-LOKI'd ROM with CWMR. Wiped Dalvik. Cache, Ractory Rest/Data. Seemed to install fine but then hung at "Custom". Fortunately I was able to a Nandroid Restore but not sure where this went wrong. Finally got TWRP to install after several failed GooManager attempts over the past month. May CWMR is the problem.
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
I have a note 2 that I kept stock for a long time. And decided to root it about a week ago. I used the latest casual one click root. And it seemed all dandy initially until i went between a few different roms and it decided it wanted to shut off randomly and not boot back up past the note 2 screen on its own. But the odd part was it booted while connected to the wall or to the computer. So I flashed to 4.1.2 stock via odin and the issue still remains. I can only use it fine on charger. Is there something else im missing on flashing back to stock?
Sent from my SCH-I605 using XDA Free mobile app
Hmm when you installed 4.3 did you do so wiping everything could be an app causing the problem. Try it from brand new with no apps installed and see if that helps. Could be also a radio issue as well.
Sent from my XT1060 using Tapatalk
Yeah I wiped everything. Actually used odin twice to revert to stock 4.1.2. I tried a few cm nightlies before it began. Is there anything else I should flash on top of whats already been done?
Sent from my SCH-I605 using XDA Free mobile app
mddcflimsreal said:
Yeah I wiped everything. Actually used odin twice to revert to stock 4.1.2. I tried a few cm nightlies before it began. Is there anything else I should flash on top of whats already been done?
Sent from my SCH-I605 using XDA Free mobile app
Click to expand...
Click to collapse
I've found that even after using ODIN to go back to stock 4.1.2, that there's still leftover data on the phone from custom ROM's. I've read where others had the same issue. I don't know why Odin doesn't seem to fully wipe everything ... but this has been my personal experience.
The way I've fixed this (and all this may not be necessary).. . is that after Odin'ing back to stock 4.1.2, I boot into stock recovery, then do a full factory reset and wipe cache. Then I booted into the stock Rom and used the bypass setup trick (touch the left side of the screen right above Emergency... then right side, then left, then right again, and then volume up... this should bypass setup to save time).
Then went into phone's settings and performed a factory reset from within the stock Rom too...
Finally... (because I'm a bit OCD... so this is probably not necessary), but I ODIN'd back to stock 4.1.2 one more time and then proceeded with using CASUAL again to root /unlock the bootloader).
I know this is a pain in the butt... but this has worked for me. Maybe others will have some better suggestions.
(Edit : Forgot to mention that if you're not wanting to return to stock to start over again... check out this thread (http://forum.xda-developers.com/showthread.php?p=53624921) on how to flash a stock recovery for the purposes of doing a proper data wipe... then can you odin your custom recovery back to the device without having to fully restore to stock... this can be a real time saver. Please make sure to thank the OP for the helpful info).
So in the end I tried to reset from stock recovery and wipe cache. Than do a reset from the settings and the issue presisted. But now I have root and recovery as well. So I may give a rom a try.
Sent from my SCH-I605 using XDA Free mobile app
mddcflimsreal said:
So in the end I tried to reset from stock recovery and wipe cache. Than do a reset from the settings and the issue presisted. But now I have root and recovery as well. So I may give a rom a try.
Sent from my SCH-I605 using XDA Free mobile app
Click to expand...
Click to collapse
This is totally a guess, but I'm thinking that you may have a battery problem... and it's just a coincidence that these problems started happening around the same time that you rooted. You may try replacing the battery to see if that fixes things.... (you can get one pretty cheap off ebay or Amazon).
Yeah thats odd. I had bought another battery from a phone store I use to work at and have no issues now, back on 4.1.1 rooted.
Sent from my SCH-I605 using XDA Free mobile app
mddcflimsreal said:
Yeah thats odd. I had bought another battery from a phone store I use to work at and have no issues now, back on 4.1.1 rooted.
Sent from my SCH-I605 using XDA Free mobile app
Click to expand...
Click to collapse
Cool. Hopefully you'll have no more problems with it for a while.
:thumbup: