Ok, so I tried running through Adam Outler's guide on rooting the Note 2 with the "CASUAL(R515b) No You Verizon!" method. It seemed to fail a couple of times but then it started going well. All until I got to about the last fourth of the process. Everything froze with the phone suspended in download mode. So, I unplugged everything to try again but lo and behold, the phone will not boot up anymore. It's not even a bootloop, it just shows the screen that says, "Samsung Galaxy Note 2" for a split second and then goes blank. It will do this indefinitely until I pull the battery.
I have always rooted my phones before and never had a problem like this. I have absolutely no idea how to fix this.
The phone originally was originally on the vramc3 framework and was completely stock.
Here is the pastebin (xda doesn't want me to post links so just eliminate the dashes: h-t-t-p-:-/-/pastebin.com/PuKkZghE
Please Please Please advise!
Solomon386 said:
Ok, so I tried running through Adam Outler's guide on rooting the Note 2 with the "CASUAL(R515b) No You Verizon!" method. It seemed to fail a couple of times but then it started going well. All until I got to about the last fourth of the process. Everything froze with the phone suspended in download mode. So, I unplugged everything to try again but lo and behold, the phone will not boot up anymore. It's not even a bootloop, it just shows the screen that says, "Samsung Galaxy Note 2" for a split second and then goes blank. It will do this indefinitely until I pull the battery.
I have always rooted my phones before and never had a problem like this. I have absolutely no idea how to fix this.
The phone originally was originally on the vramc3 framework and was completely stock.
Here is the pastebin (xda doesn't want me to post links so just eliminate the dashes: h-t-t-p-:-/-/pastebin.com/PuKkZghE
Please Please Please advise!
Click to expand...
Click to collapse
Fortunately its only a softbrick. If the phone posts (ie displays the Samsung Galaxy Note 2 screen) it should be salvageable with little difficulty. Verify that you can boot download mode (power off, vol down+home while powering on). Follow a guide for returning to stock, using odin to flash a stock image. This will get you back in business. Are you certain you were using the correct casual for your firmware revision?
apacseven said:
Fortunately its only a softbrick. If the phone posts (ie displays the Samsung Galaxy Note 2 screen) it should be salvageable with little difficulty. Verify that you can boot download mode (power off, vol down+home while powering on). Follow a guide for returning to stock, using odin to flash a stock image. This will get you back in business. Are you certain you were using the correct casual for your firmware revision?
Click to expand...
Click to collapse
Ok, I was able to get it into download mode. I'm downloading the stock image right now. Yeah I 'm definitely sure that I used the right casual for my firmware. It's my friend's phone and he just bought it a week ago so he would definitely be on the most recent firmware. I'll update with how everthing goes after I try to flash the stock image. Are there any other methods for rooting it once I get it back to stock?
Solomon386 said:
Ok, I was able to get it into download mode. I'm downloading the stock image right now. Yeah I 'm definitely sure that I used the right casual for my firmware. It's my friend's phone and he just bought it a week ago so he would definitely be on the most recent firmware. I'll update with how everthing goes after I try to flash the stock image. Are there any other methods for rooting it once I get it back to stock?
Click to expand...
Click to collapse
You seem convinced that you had the right casual, but I'm not. I dont want to sound like I'm calling you out I just want to make sure we're on the same page. My note 2 which I purchased last week from BestBuy came with LL4 (second to latest revision), so the No You Verizon wouldnt have worked, I needed Back Atcha Verizon. Which firmware you had when you tried to use CASUAL also impacts which stock image you need to flash to return to stock. As long as you are absolutely sure you were on MC3 then this is all moot. I dont know of another way to root, I would imagine there is one but you will have to search around. CASUAL is the way to go though, so I suggest we troubleshoot this and get that method to work.
apacseven said:
You seem convinced that you had the right casual, but I'm not. I dont want to sound like I'm calling you out I just want to make sure we're on the same page. My note 2 which I purchased last week from BestBuy came with LL4 (second to latest revision), so the No You Verizon wouldnt have worked, I needed Back Atcha Verizon. Which firmware you had when you tried to use CASUAL also impacts which stock image you need to flash to return to stock. As long as you are absolutely sure you were on MC3 then this is all moot. I dont know of another way to root, I would imagine there is one but you will have to search around. CASUAL is the way to go though, so I suggest we troubleshoot this and get that method to work.
Click to expand...
Click to collapse
Ok, the phone is now working. Thank God! I'm pretty sure I got the right one, I'm currently looking at the About Phone section on Settings and it lists the build number as JZ054K.1605VRAMC3. That would mean that I need the No You Verizon one right?
Solomon386 said:
Ok, the phone is now working. Thank God! I'm pretty sure I got the right one, I'm currently looking at the About Phone section on Settings and it lists the build number as JZ054K.1605VRAMC3. That would mean that I need the No You Verizon one right?
Click to expand...
Click to collapse
Indeed. Try CASUAL again and report back with any specific errors you encounter.
just a heads up, but make sure you have all anti-virus and/or security programs disabled before running casual.
Related
I have a Galaxy Note i717 from AT&T that I rooted. Worked great.
Yesterday I upgraded to ICS via Kies. Worked great.
Then I proceeded to root it again using odin.
Unfortunately even after all the things done it now will not boot up at all.
All I get is the S a m s u n g logo. I can put it into boot mode and the computer see's it but nothing more.
If anyone can point me to any rom/bootloader/ etc. I would be most grateful.
Or just let me know what to do and where to get roms. I did search and there are many for the i700.
I guess I need a bootloader and rom right?
Sorry folks. Point me somewhere else will have to get another phone.
T h a n k s ...
Others would tell you to look in the dev section for the stock rom (its usually called something like "in case of brick) I've had issues issues getting it to work but Im certain it was user error as to why it didn't work for me. But another option that I think could work would be to get your phone into download mode and run the ics upgrade thru kies again. You'll lose everything in your phone but I think it'll get your phone up and running again. But before you do any other that...did you make a nandroid back of? Or have you downloaded any roms to your phone because if you did you can just enter cwm and reflash any rom you may have or just flash your backup, backups are so important when doing these sort of things, saves a lot of head aches.
Edit: after reading your post again it says your phone messed up after rooting, try and re run the root file thru Odin, I kinda sorta remember reading something similar to this were people had issue trying to root. I'll try and find the thread.
Sent from my SAMSUNG-SGH-I717 using xda premium
this happened due to rooting with the Gingerbread method...so using Nash reply run/reinstall your Official ICS...and to root....
see My Links in red in my signature...go the GNote Super page....you should see what is being used to root the Official ICS...I used it and lots others, there prob more methods out there, but I found this is the easiest and more proven method....
Cant miss the info on GNote page regarding Rooting.
so to recap...since your believe you have bricked your phone...
use the method Nash replied to you with...put into download mode....run the official ics, you will need the model, serial number of your phone...
let us know how it works out for you...
mpanwar said:
I have a Galaxy Note i717 from AT&T that I rooted. Worked great.
Yesterday I upgraded to ICS via Kies. Worked great.
Then I proceeded to root it again using odin.
Unfortunately even after all the things done it now will not boot up at all.
All I get is the S a m s u n g logo. I can put it into boot mode and the computer see's it but nothing more.
If anyone can point me to any rom/bootloader/ etc. I would be most grateful.
Or just let me know what to do and where to get roms. I did search and there are many for the i700.
I guess I need a bootloader and rom right?
Sorry folks. Point me somewhere else will have to get another phone.
T h a n k s ...
Click to expand...
Click to collapse
And once you're rooted and all fixed up, enter cwm and create a backup. These are great because no matter what you do to your phone as long as you can enter cwm you'll always be able to fix your phone via backup.
Sent from my SAMSUNG-SGH-I717 using xda premium
I wanted to mention, I'm not sure how you updated thru kies originally (legit update or emergency update) the method you'll be using this time (if you choose to fix thru kies) is the more or less emergency method. I wanted to mention this because when your in download mode and connect your phone to your PC and run kies, kies will try to connect to your device but will time out over time...it took me 2 days of Q and A before I realized kies won't connect with phone in download mode, but that's OK. Once phone is connected click tools/firmware upgrade and initialization, and as bigjoe said youll than need to input model and serial numbers (all caps) than click OK. You'll have a few prompts afterwards but yo basically on your way to a running phone.
Sent from my SAMSUNG-SGH-I717 using xda premium
Brick = nothing at all happening on phone.
Samsung logo = bad flash (corrupt file used)
Brick can sometimes be revived with a JTAG device.
Samsung logo means re download file, re read instructions and relevent thread, and redo your work.
Don't be too anxious -you will fix it.
I suggest using Kies upgrade > emerency firmware method. Download mode is the key.
If you are with Rogers, the following is useful.
http://forum.xda-developers.com/showthread.php?t=1657262
I went through the exact same problem with someone else's Note that I was upgrading, subsequently flashing.
The above process bring the phone back to 100% stock gingerbread.
Thanks All and Resolved.
eugenekim618 said:
If you are with Rogers, the following is useful.
http://forum.xda-developers.com/showthread.php?t=1657262
I went through the exact same problem with someone else's Note that I was upgrading, subsequently flashing.
The above process bring the phone back to 100% stock gingerbread.
Click to expand...
Click to collapse
Thanks all for the replies.
I was able to go to DEV Section and get the full AT&T ICS Rom. Used ODIN to get it back to factory ICS.
Then (with great care ) re-rooted it using ICS root stuff. I have it all in case anyone else needs this route. Else follow instructions above.
Thanks all. I think for now ICS is where this will stay. In fact Gingerbread was good enough except for not being able to use Chrome.
mpanwar said:
Thanks all for the replies.
I was able to go to DEV Section and get the full AT&T ICS Rom. Used ODIN to get it back to factory ICS.
Then (with great care ) re-rooted it using ICS root stuff. I have it all in case anyone else needs this route. Else follow instructions above.
Thanks all. I think for now ICS is where this will stay. In fact Gingerbread was good enough except for not being able to use Chrome.
Click to expand...
Click to collapse
great, can you put solved in the title...thx
So I rooted my HTC Rezound a months ago, since ICS didn't launch when I wanted it to lol..Any way I decided I want to unroot my phone so I can trade it in on a new one. I followed the guidelines a user posted on XDA to the T and I keep getting either a message failed my version is newer or older than the one im installing? I did however download a ICS fake update before I rooted and wasn't sure if that has anything to do with it. As of right now I am stuck in the Bootloader screen I can not do anything. Please help, I need this phone for work since I am supposed to be On Call everyday. If you need any numbers from the bootloader screen I am sure I have them memorized lol.
Could always flash a working rom get to the home screen and use odin to go back to stock or go into download mode and use odin then too if you can get there.
tehsprayer said:
Could always flash a working rom get to the home screen and use odin to go back to stock or go into download mode and use odin then too if you can get there.
Click to expand...
Click to collapse
Odin and download mode are for Samsung devices .
krayz22 said:
So I rooted my HTC Rezound a months ago, since ICS didn't launch when I wanted it to lol..Any way I decided I want to unroot my phone so I can trade it in on a new one. I followed the guidelines a user posted on XDA to the T and I keep getting either a message failed my version is newer or older than the one im installing? I did however download a ICS fake update before I rooted and wasn't sure if that has anything to do with it. As of right now I am stuck in the Bootloader screen I can not do anything. Please help, I need this phone for work since I am supposed to be On Call everyday. If you need any numbers from the bootloader screen I am sure I have them memorized lol.
Click to expand...
Click to collapse
Are you able to select any options from the boot loader screen? (Using the power button)
My Verizon Samsung Galaxy S4 (Model # SCH-I545) is stuck at an error screen with a yellow triangle in the middle and a picture of a phone on the left and a picture of a computer on the right. It also reads: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I JUST purchased this phone and the latest update was installed. I attempted to root the phone but after researching I found there is no current solution. I searched more and found a thread (that i can't post because I am a noob): I followed the instructions hoping to remove the update and return to stock, however the process did not work and Odin failed. Even though Odin was through, my phone still showed a line like it was downloading. I tried everything to reboot my phone, but could not find a way to do it, so I pulled the battery. Now, I cannot get past this screen. Is there anything I can do to fix this awesome blunder?
P.S. I am prepared for the scoldings I plan on getting...
I literally just posted the same question. Any help would be appreciated if you can figure it out. Ill return the favor if i can get any information :good:
If you took the latest update I'm not sure what the answer is because I haven't been willing to take the update.
If you were in mdk before the yellow triangle then all you have to do is Odin the mdk kernel.
I'd imagine if you are on the latest then odining the latest would take care of it also but again, I won't take the latest so I can't say for sure
sent from my blu vzw gs4
Thanks Jakemkv, I will update you as I get more info. I will also be looking at your thread, you can bet.
Dubbsy, where can I find that new mdk Kernel?
richardawood said:
Thanks Jakemkv, I will update you as I get more info. I will also be looking at your thread, you can bet.
Dubbsy, where can I find that new mdk Kernel?
Click to expand...
Click to collapse
Im on a search for the updated kernel as well. At least there is someone in the same boat as i am.
richardawood said:
My Verizon Samsung Galaxy S4 (Model # SCH-I545) is stuck at an error screen with a yellow triangle in the middle and a picture of a phone on the left and a picture of a computer on the right. It also reads: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I JUST purchased this phone and the latest update was installed. I attempted to root the phone but after researching I found there is no current solution. I searched more and found a thread (that i can't post because I am a noob): I followed the instructions hoping to remove the update and return to stock, however the process did not work and Odin failed. Even though Odin was through, my phone still showed a line like it was downloading. I tried everything to reboot my phone, but could not find a way to do it, so I pulled the battery. Now, I cannot get past this screen. Is there anything I can do to fix this awesome blunder?
P.S. I am prepared for the scoldings I plan on getting...
Click to expand...
Click to collapse
If the phone was running ME7 then you can ONLY flash ME7 again (at least right now).
Grab the image from this thread...
http://forum.xda-developers.com/showthread.php?t=2357235
and flash it using Odin.
Thank You
That worked great! I am back up in running and waiting patiently w/ the rest of us that updated... THANK YOU!!!!!! :highfive:
Thanks
I can't thank you enough. The S4 is my first Android phone and after 3 weeks, the USB connection on the phone broke and I finally got my new one today. While I was setting up SuperSU/Titanium Backup/ROM Manager, I guess the phone downloaded the ME7 update in the background and I told it to install (stupid me). This will teach me from rushing to get my phone back to the state it was in. (Not that I can do that now because I need SuperSU before I can install ROM Manager). Hopefully once I can get ROM Manager back, I can restore my MDK backup with all my custom settings and apps. I think I will make a visit to the VZ store tomorrow and see if they can revert back to the MDK version. I will make up some lame excuse of why I don't want to be on this new release.
This leads to my question of, is there a way to disable or remove the apk file that controls the software updates?
Thanks again for saving my life!!!
Once you take me7 update theres no going back unless you get a different phone. When someone gets the me7 ota rooted you can rename/remove sdm.apk and itll keep your phone from downloading new updates. I would say freeze as well but some users reported their phones updating even with it froze. When the me7 bootloader/recovery situation gets resolved there wont be much reason to go back to mdk anyway since people will start creating roms with it as the base.
SCH-I545 using Tapatalk 2
Thanks
hexitnow said:
Once you take me7 update theres no going back unless you get a different phone. When someone gets the me7 ota rooted you can rename/remove sdm.apk and itll keep your phone from downloading new updates. I would say freeze as well but some users reported their phones updating even with it froze. When the me7 bootloader/recovery situation gets resolved there wont be much reason to go back to mdk anyway since people will start creating roms with it as the base.
SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the information about the sdm.apk. When I debloated my phone I used the adb shell to remove most of the *.apk packages that I did not want. This was of course after I took a full Titanium Backup and ROM Backup.
Sounds good and I will not waste my time going to Verizon today.
You make a really good point about not going back to the mdk, but rather move forward with the technology and updates. This leads me to some more questions once I have root again:
1. Is my mdk rom backup totally useless at this point?
2. If yes to 1, since my mdk rom contained all my apps/customized settings, do I have to manually download everything and reconfigure?
3. If no to 2, how would I go about getting the app/customized settings back, Titanium Backup?
4. If yes to 2, if I go about downloading everything manually and configuring, will the new root remove all these settings?
I am sure I will have more questions so thanks in advanced
PS: I think I figured out what caused my USB port to stop working. I take my phone with me when I run so I think some sweat got in from my arm band and corroded the connections. I tried cleaning them with rubbing alcohol and compressed air, but still no dice. If connected to a computer or wall charger, it will charge, but a computer will not detected it. So my guess is there is damage to the board allowing whatever communication is needed to work with a computer.
Hi,
I need help guys.
I have S4 and I was trying to mess with it and now I don't have it at all. (pic 1)
the Samsung logo and unlock lock icon are as far as my phone goes now, and after that u cant even power it off u have get battery out. (pic 2)
I am able to go to download mode (pic 3)
and I was able to get to there (up+menu+power key), but now I cant even go there. I get black screen when I am trying to do it. (pic 4)
Thanks for your time,
Ps. Help me
Did you flash a ROM? In you pictures it appears that you can still get to recovery, is that true? What steps did you take for root? We need more information.
answer
Eeiden said:
Did you flash a ROM? In you pictures it appears that you can still get to recovery, is that true? What steps did you take for root? We need more information.
Click to expand...
Click to collapse
I was trying to flash rom, I was trying to make in international phone so it could work in Europe with out any Verizon build in stuff, just pure Samsung.
I can go do download mode, I was able to go for recovery before. That why there is the 4th picture, in stead of regular recovery a had that "teamwin" screen. Now when I press up menu and power is saying its going to recovery boot but then it resets it self and going back to Samsung unlock icon screen and just stays there...
You hold volume down + power to get to download mode. Then connect to a pc and download the all in one tool found in the development thread. Ignore the messages about having your phone in USB debugging and tell it to flash twrp 2.6.0.0. If it doesn't take In download mode, try rebooting your phone while it tries to flash twrp.
If that doesn't work flash stock with Odin and re-root and unlock the phone.
Sent from my SCH-I545 using xda app-developers app
I'm having the exact same problems right now. I tried flashing a 4.3 i9505 rom and now I can't get back into recovery and I can't boot into the OS. I can get into download mode and use ODIN, but I don't know what to do from there. I tried using the All-In-One tool to install TWRP, but it just says Device Not Found. I also tried flashing the stock sch-i545 kernel in ODIN, and it completed successfully, rebooted, and its still doing the same thing. Is there some other way that I've missed to return to stock? I'm kinda bummin here.. but thats what comes with the territory I suppose. Any help you can offer would be greatly appreciated. Thanks.
Found the factory image thread. Going to follow instructions. Will report back.
it works but not completly
So guys going back to my problem I was trying to do everything like lahma69 was trying too...
in odin was error that device not found, all off that...
but what I did, I look more online and I found this one guy...
and what I did in download mode I use odin, and in PDA selection I use this file stockroms(dot)net/file/GalaxyS4/SCH-i545/VRUAMDK_NoWipe.tar.zip
now boom... its kinda works... I am back with my os, I got the android root.
but some things are not right... my phone is very hot, maybe because its charging its self for the first time in weeks.
more important is Whats is happening right now, in boot menu I get errors, no commands, it was not able to do factory reset until I went into os and did it over there... and I cant do software update from Verizon... it goes to root and its trying but then gets error and going back to os...
and I am worry about that file that I download...
so we got little progress and lahma69 I can at least operate os and I have back stock root...
but until we will not going to make it 100% hold on with what I did...
U cant flash a rom thats not made specifically for the verizon variant (i545). The i9505 is the international version of the phone. Hence your phone not booting. Youre going to have to flash the stock mdk firmware through odin and start over (reroot, etc).
SCH-I545 using Tapatalk 2
sannek, I actually got it back up and running doing the same thing you did. I flashed the factory image in this thread: http://forum.xda-developers.com/showthread.php?t=2301259
I haven't noticed any problems yet. I'm fixing to reroot and flash my nandroid. I will let you know if I run into any problems.
I know you can't typically flash a i9505 rom on a verizon gs4, but the author of a i9505 4.3 rom gave me some instructions to try in order to get it working. I'm inserting a 4.3 ramdisk into a 4.2 AOSP ktoonsez verizon gs4 kernel, and replacing the boot.img in the 4.3 i9505 rom. I now know that I had accidentally inserted the wrong version kernel, and thats what caused my problems.
lahma69 said:
sannek, I actually got it back up and running doing the same thing you did. I flashed the factory image in this thread: http://forum.xda-developers.com/showthread.php?t=2301259
I haven't noticed any problems yet. I'm fixing to reroot and flash my nandroid. I will let you know if I run into any problems.
I know you can't typically flash a i9505 rom on a verizon gs4, but the author of a i9505 4.3 rom gave me some instructions to try in order to get it working. I'm inserting a 4.3 ramdisk into a 4.2 AOSP ktoonsez verizon gs4 kernel, and replacing the boot.img in the 4.3 i9505 rom. I now know that I had accidentally inserted the wrong version kernel, and thats what caused my problems.
Click to expand...
Click to collapse
lahma69 were u able to do software upgrade on your phone?
and I am happy for you, mine still have same problems like I mentions up there, I still get error and no command in root and I cant get software update... as soon I will be able to figure this out that will mean that my phone is 100% able to go back to Verizon that's one thing but then I will now for future because really want to make this phone a Europe compatible phone...
SaNNeK said:
lahma69 were u able to do software upgrade on your phone?
and I am happy for you, mine still have same problems like I mentions up there, I still get error and no command in root and I cant get software update... as soon I will be able to figure this out that will mean that my phone is 100% able to go back to Verizon that's one thing but then I will now for future because really want to make this phone a Europe compatible phone...
Click to expand...
Click to collapse
My phone seems to be at 100%. I never do software updates through Verizon so I would not know if thats working or not. After I flashed the stock image in ODIN and rerooted my device, I immediately flashed TWRP through Goomanager and reflashed my nandroid (Eclipse TW rom.) Everything is running well and my phone isn't warm. Why are you trying to do a software update? I think there is an update now that can't be rooted, so you definitely don't want to do that...
I tried several things to get the i9505 4.3 rom running on my device. You can get an idea of what I did by reading this thread: http://forum.xda-developers.com/showthread.php?t=2253528&page=779 Scroll down to post #7785 and that is mine. I never did get it to boot... Let me know if you need anything else.
root problem and upgrate
So I did exactly how xda web site was saying about going back to stock and all of that.
It worked, I can run to os and I have original root.
Still have couple of problems,
1.when u in recovery I see error and no command right below android guy. also I see new info in yellow color, below regular blue recovery screen option. (pic1)
2. information in yellow color is follow: (pic 2)
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the csc-code:VZN
successfully applied multi-CSC.
never see in before, don't know what to do..
3. I cant do regular Verizon software update. S4 resets it self and goes to recovery where is trying to do update but ends um saying error and then is going back to os and its saying that update was not that and that there were no changes applied...(pic 3)
I still need your help guys...
SaNNeK said:
So I did exactly how xda web site was saying about going back to stock and all of that.
It worked, I can run to os and I have original root.
Still have couple of problems,
1.when u in recovery I see error and no command right below android guy. also I see new info in yellow color, below regular blue recovery screen option. (pic1)
2. information in yellow color is follow: (pic 2)
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the csc-code:VZN
successfully applied multi-CSC.
never see in before, don't know what to do..
3. I cant do regular Verizon software update. S4 resets it self and goes to recovery where is trying to do update but ends um saying error and then is going back to os and its saying that update was not that and that there were no changes applied...(pic 3)
I still need your help guys...
Click to expand...
Click to collapse
Did you see what I said about doing Samsung software updates? The rooting threads for the Verizon GS4 say that the new VRUAME7 OTA update can't be rooted. After flashing the stock image from oden, why don't you reroot your device according to http://forum.xda-developers.com/showthread.php?t=2290798 and then install Goomanager, click the menu key, click "Install open recovery script" and that will install TWRP recovery. From there, flash a verizon rom of your choice and all should be well, no? I only use TWRP so I can't give you any input on other recoveries. Make sure you didn't somehow get updated to VRUAME7.
township japinove
lahma69 said:
My phone seems to be at 100%. I never do software updates through Verizon so I would not know if thats working or not. After I flashed the stock image in ODIN and rerooted my device, I immediately flashed TWRP through Goomanager and reflashed my nandroid (Eclipse TW rom.) Everything is running well and my phone isn't warm. Why are you trying to do a software update? I think there is an update now that can't be rooted, so you definitely don't want to do that...
I tried several things to get the i9505 4.3 rom running on my device. You can get an idea of what I did by reading this thread: http://forum.xda-developers.com/showthread.php?t=2253528&page=779 Scroll down to post #7785 and that is mine. I never did get it to boot... Let me know if you need anything else.
Click to expand...
Click to collapse
Well I am not that good with all of it... I don't know a lot of meanings of all this like TWRP, Eclipse TW rom, or what you said u did on post #7785
so I am just trying to be able to make it run like new, and then if I do that I will try to work on my s3 and practice on that...
I am beginner in it... plus my English abilities are not that great, so I really don't know which root is the best or how to do it with out messing up entire phone. I love to dig into it, and my s4 was just laying broken for past month and I worked on in today with you guys and its almost working... I almost made claim from insurance for new phone but this one starts working today..
and looks like everything is fine with it
except root errors and no commands ,I cant wipe cash because its crashing and restarting and I cant do that software update, and I have that manual multi csc note in recovery system like I mention just on top with pictures...
SaNNeK said:
Well I am not that good with all of it... I don't know a lot of meanings of all this like TWRP, Eclipse TW rom, or what you said u did on post #7785
so I am just trying to be able to make it run like new, and then if I do that I will try to work on my s3 and practice on that...
I am beginner in it... plus my English abilities are not that great, so I really don't know which root is the best or how to do it with out messing up entire phone. I love to dig into it, and my s4 was just laying broken for past month and I worked on in today with you guys and its almost working... I almost made claim from insurance for new phone but this one starts working today..
and looks like everything is fine with it
except root errors and no commands ,I cant wipe cash because its crashing and restarting and I cant do that software update, and I have that manual multi csc note in recovery system like I mention just on top with pictures...
Click to expand...
Click to collapse
Whats your build number in Settings -> About Phone ?
lahma69 said:
whats your build number in settings -> about phone ?
Click to expand...
Click to collapse
jdq39.i545vruamdk
Working progress
SaNNeK said:
jdq39.i545vruamdk
Click to expand...
Click to collapse
so when I will learn how to fix my phone to 100%.
Then I will experiment with it and try to learn and install more roots if I will learn how to fix first... so I will not panic like I did this time... I was just completely lost, and I need to take is step by step... don't get me wrong... I love doing that kinda stuff I build my first pc when I was 10 years old... back on old good windows 95
SaNNeK said:
so when I will learn how to fix my phone to 100%.
Then I will experiment with it and try to learn and install more roots if I will learn how to fix first... so I will not panic like I did this time... I was just completely lost, and I need to take is step by step... don't get me wrong... I love doing that kinda stuff I build my first pc when I was 10 years old... back on old good windows 95
Click to expand...
Click to collapse
Do you currently have root? To check, you can run the "SuperUser" app. If you don't have it, download it from the Play store. After installing it, run it, and a box should pop up asking you for superuser permissions. Click "Grant." If a message pops up that says something like "Superuser has been granted superuser permissions," then you have root. If you don't have root, you need to get it. Follow the instructions at http://forum.xda-developers.com/showthread.php?t=2290798 . After performing those instructions, and verifying you have root, you need to download an application called "Goomanager" from the play store. After installing and opening it, click your "Menu" key (bottom left hand corner of your phone.) A menu will pop up. Click "Install open recovery script." Click Yes or Ok to all the pop up messages. After that completes, you will have TWRP recovery installed. Your recovery is what you boot your phone to in order to flash new roms, kernels, etc. In order to boot into recovery, turn off your phone completely, click and hold your volume up button, and power on your phone (while still holding volume up.) You should see some tiny blue text pop up in the top left hand corner of your screen that saying "Opening recovery" (or something to that effect.) Once you see that text, you can let go of volume up, and you will boot into TWRP. Let me know if you get this far...
And by the way, for the love of God, do not do any Samsung system updates.
lahma69 said:
And by the way,for the love of God, do not do any Samsung system updates.
Click to expand...
Click to collapse
And thats the most important part, because if you do you will lose root and your ability to customize your phone. In layman's terms? You will be re-VZ-navigated.
I am having a similar issue. Got the "Samsung Custom" boot screen with no boot to the OS after clean wipe and install of Hyperdrive 7. Since then I have been troubleshooting the issue and have tried many things including the "No-Wipe Factory Image". Once complete I am still getting the Samsung Custom boot screen and no loading of the OS.
Any ideas as to what I can try.
Thanks in advance,
Tony
lahma69 said:
Do you currently have root? To check, you can run the "SuperUser" app. If you don't have it, download it from the Play store. After installing it, run it, and a box should pop up asking you for superuser permissions. Click "Grant." If a message pops up that says something like "Superuser has been granted superuser permissions," then you have root. If you don't have root, you need to get it. Follow the instructions at http://forum.xda-developers.com/showthread.php?t=2290798 . After performing those instructions, and verifying you have root, you need to download an application called "Goomanager" from the play store. After installing and opening it, click your "Menu" key (bottom left hand corner of your phone.) A menu will pop up. Click "Install open recovery script." Click Yes or Ok to all the pop up messages. After that completes, you will have TWRP recovery installed. Your recovery is what you boot your phone to in order to flash new roms, kernels, etc. In order to boot into recovery, turn off your phone completely, click and hold your volume up button, and power on your phone (while still holding volume up.) You should see some tiny blue text pop up in the top left hand corner of your screen that saying "Opening recovery" (or something to that effect.) Once you see that text, you can let go of volume up, and you will boot into TWRP. Let me know if you get this far...
And by the way, for the love of God, do not do any Samsung system updates.
Click to expand...
Click to collapse
as my understanding its not.. I just did that no wipe recovery...
sorry I was out of town today... so I assume I will have to do root but which one is the best? there is so many different ones...
I was simply messing around with my old Verizon GN2, because I need a phone to use in the absence of my htc one M9. I went to flash the "stock" version of the bootloader (the bootloaderbaseline2.tar) before I went in to do any real damage and the phone rejected it. The phone screen read the error message "wrong magic string" and the odin display reported that it dropped out after sboot.bin. Just curious whether you guys and your wisdom would have any insight in the matter? I would really prefer not to have to go out and buy another phone.
Also, woohoo for a first post on the forums.
Cordially,
Nixon
logannixon.la said:
I was simply messing around with my old Verizon GN2, because I need a phone to use in the absence of my htc one M9. I went to flash the "stock" version of the bootloader (the bootloaderbaseline2.tar) before I went in to do any real damage and the phone rejected it. The phone screen read the error message "wrong magic string" and the odin display reported that it dropped out after sboot.bin. Just curious whether you guys and your wisdom would have any insight in the matter? I would really prefer not to have to go out and buy another phone.
Also, woohoo for a first post on the forums.
Cordially,
Nixon
Click to expand...
Click to collapse
Are you flashing the full firmware or just bootloader? What options did you have checked and where (in what slot, PDA?) did you put the file to run it? What version are you on, 4.4.2; 4.3? Have you unlocked it before?
bigmike35 said:
Are you flashing the full firmware or just bootloader? What options did you have checked and where (in what slot, PDA?) did you put the file to run it? What version are you on, 4.4.2; 4.3? Have you unlocked it before?
Click to expand...
Click to collapse
I had this phone rooted before, but it wasn't playing well with what my sister wanted it for. So, I flashed a stock image and it rebooted into its stock form. That was two ish years ago. The bootloader was never unlocked. When I brought it back out to begin tinkering, a lot of guides said to flash the stock bootloader (the bootloaderbaseline2 file) and to repartition it before going ahead with something like CASUAL. Considering my sister used it as a daily driver for quite a while, it was probably on 4.3 or whatever the last update Verizon handed out was. I do remember checking to see whether or not it had any available updates and it said it was completely up to date. When I set it up to repartition and flash the BB2 file, it was in the bootloader slot. The Odin flash then failed at the sboot.bin output and the phone proceeded to slide into the good old "connect to Kies" screen. I tried several attempts to get the BB2 file to stick (putting it in all the slots and trying it without partition and auto reboot), but all were to no avail. I have since flashed multiple firmwares in the PDA slot with only the root66_vzw_stock_system.tar.md5 version completing. However, it now displays the "Device firmware is not from verizon. Please bring it into a Verizon store for help." I know the verizon reps will be useless, so I asked you beautiful people.
The only odin boxes that I played with were the top three.
Also, thanks for responding. I appreciate it.
Nixon
logannixon.la said:
I had this phone rooted before, but it wasn't playing well with what my sister wanted it for. So, I flashed a stock image and it rebooted into its stock form. That was two ish years ago. The bootloader was never unlocked. When I brought it back out to begin tinkering, a lot of guides said to flash the stock bootloader (the bootloaderbaseline2 file) and to repartition it before going ahead with something like CASUAL. Considering my sister used it as a daily driver for quite a while, it was probably on 4.3 or whatever the last update Verizon handed out was. I do remember checking to see whether or not it had any available updates and it said it was completely up to date. When I set it up to repartition and flash the BB2 file, it was in the bootloader slot. The Odin flash then failed at the sboot.bin output and the phone proceeded to slide into the good old "connect to Kies" screen. I tried several attempts to get the BB2 file to stick (putting it in all the slots and trying it without partition and auto reboot), but all were to no avail. I have since flashed multiple firmwares in the PDA slot with only the root66_vzw_stock_system.tar.md5 version completing. However, it now displays the "Device firmware is not from verizon. Please bring it into a Verizon store for help." I know the verizon reps will be useless, so I asked you beautiful people.
The only odin boxes that I played with were the top three.
Also, thanks for responding. I appreciate it.
Nixon
Click to expand...
Click to collapse
So it it on 4.4.2 then since all updates are up to date? If that is the case, you can only root using towel root. You can downgrade to 4.3 or 4.2.1 but you would need to send it in ($75) i believe or try the method here that is posted. If it is still on 4.3 i believe you can flash the 4.2.1 firmware and then run root running casual (disable firewall and antim virus else wont complete). Then find Beanstown thread and download the zip for the updated wifi/bootloader for 4.3 with ND7 radio (zip somewhere as well) to upgrade completely to newest radio/images (so it would be a 4.2.1 or 4.3 stock with complete root and unlocked). Then install TWRP and roms
bigmike35 said:
So it it on 4.4.2 then since all updates are up to date? If that is the case, you can only root using towel root. You can downgrade to 4.3 or 4.2.1 but you would need to send it in ($75) i believe or try the method here that is posted. If it is still on 4.3 i believe you can flash the 4.2.1 firmware and then run root running casual (disable firewall and antim virus else wont complete). Then find Beanstown thread and download the zip for the updated wifi/bootloader for 4.3 with ND7 radio (zip somewhere as well) to upgrade completely to newest radio/images (so it would be a 4.2.1 or 4.3 stock with complete root and unlocked). Then install TWRP and roms
Click to expand...
Click to collapse
So, for the moment, is there any way to get it back to stock? I was trying to go the custom recovery route in the beginning, but I now just need a phone that works. I'm pretty sure it's the bootloader firmware that is preventing the device from booting completely. Thanks for all your help.
Nixon
logannixon.la said:
So, for the moment, is there any way to get it back to stock? I was trying to go the custom recovery route in the beginning, but I now just need a phone that works. I'm pretty sure it's the bootloader firmware that is preventing the device from booting completely. Thanks for all your help.
Nixon
Click to expand...
Click to collapse
You can see if you can flash the full Verizon firmware. Should be able to find it here or on Samsungs website.
bigmike35 said:
You can see if you can flash the full Verizon firmware. Should be able to find it here or on Samsungs website.
Click to expand...
Click to collapse
So the stock Verizon firmware will repair the broken bootloader? I'll give it a go. Thanks for the info.
Just a quick update. I flashed the stock firmware for 4.4.2 and everything went over swimmingly. The phone now boots all the way into the Verizon boot splash screen. It then sits there and will not progress. I've tried wiping cache and factory resetting, but it still hangs on the Verizon splash screen. Any pointers?
Thanks again,
Nixon
Another side update. It's still held up on the Verizon boot splash screen, but the led is now pulsing. *Shrugs in confusion
Nixon
logannixon.la said:
Another side update. It's still held up on the Verizon boot splash screen, but the led is now pulsing. *Shrugs in confusion
Nixon
Click to expand...
Click to collapse
Ya i have had that issue before, but I did what you did is to wipe cache, data, factory and that normal let me get a full boot in.
bigmike35 said:
Ya i have had that issue before, but I did what you did is to wipe cache, data, factory and that normal let me get a full boot in.
Click to expand...
Click to collapse
Yeah, I've tried the factory reset and wipe cache, it still gets caught in the Verizon boot loop. I'm not particularly sure what that else to do. The 4.4.2 stock md5 is the only one that will stick in Odin.
logannixon.la said:
Yeah, I've tried the factory reset and wipe cache, it still gets caught in the Verizon boot loop. I'm not particularly sure what that else to do. The 4.4.2 stock md5 is the only one that will stick in Odin.
Click to expand...
Click to collapse
are you flashing it with the PIT file as well?
bigmike35 said:
are you flashing it with the PIT file as well?
Click to expand...
Click to collapse
I think I tried with and without, but I'll give it a shot.
logannixon.la said:
I think I tried with and without, but I'll give it a shot.
Click to expand...
Click to collapse
Ya put that in the PIT tab and firmware in PDA. When it finished, does it say complete or done (box turns green, near top left?)
Also, maybe try another firmware/version?
bigmike35 said:
Ya put that in the PIT tab and firmware in PDA. When it finished, does it say complete or done (box turns green, near top left?)
Also, maybe try another firmware/version?
Click to expand...
Click to collapse
I tried the pit to no avail. Currently wiping again just for fun. Not sure if it helps, but the system recovery screen reads this