[Q] Can't get to recovery... - Verizon Galaxy Note 3 Q&A, Help & Troubleshooting

Hi guys,
I'm having trouble getting into CWM recovery. When I try to boot into if from Rom Manager it gives me an error that says, "System software not authorized by verizon wireless". After filling my pants I figured out how to get past that and boot up my phone, but I don't know what to do from here. Any thoughts?
I'm running stock 4.4.2 Rooted
Thanks!

Retail devices can only use safestrap. Developer editions can use custom recoveries. Sounds like youre on a retail device.

waxcatharsis said:
Hi guys,
I'm having trouble getting into CWM recovery. When I try to boot into if from Rom Manager it gives me an error that says, "System software not authorized by verizon wireless". After filling my pants I figured out how to get past that and boot up my phone, but I don't know what to do from here. Any thoughts?
I'm running stock 4.4.2 Rooted
Thanks!
Click to expand...
Click to collapse
bmwh0r3 said:
Retail devices can only use safestrap. Developer editions can use custom recoveries. Sounds like youre on a retail device.
Click to expand...
Click to collapse
Like my buddy @bmwh0r3 stated, sounds like you're on a Retail device.
Check out this thread by @az_biker that walks you through all the things you need to know.

Shaggy Kobain said:
Like my buddy @bmwh0r3 stated, sounds like you're on a Retail device.
Check out this thread by @az_biker that walks you through all the things you need to know.
Click to expand...
Click to collapse
Yes I have a retail version rooted using the towelroot method. So I can just install Safestrap and move on from there?

waxcatharsis said:
Yes I have a retail version rooted using the towelroot method. So I can just install Safestrap and move on from there?
Click to expand...
Click to collapse
Correct. Make sure you grab SafeStrap 3.75B04 and you will be good to go :good:

Shaggy Kobain said:
Correct. Make sure you grab SafeStrap 3.75B04 and you will be good to go :good:
Click to expand...
Click to collapse
Great, I'll try that! Thanks guys!

Success! Only thing is I still need to do the workaround to boot up my phone(hold down home, volume down and power). Once I do that I'm able to boot into recovery or system. Do I need to remove CWM through some further process or is something else causing that?

I would start over. Odin the stock tar and pit files. Root again and follow the instructions in the safestrap thread. Be re device you can only use the touchwiz roms

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bmwh0r3 said:
I would start over. Odin the stock tar and pit files. Root again and follow the instructions in the safestrap thread. Be re device you can only use the touchwiz roms
Click to expand...
Click to collapse
I was afraid of that...

bmwh0r3 said:
I would start over. Odin the stock tar and pit files. Root again and follow the instructions in the safestrap thread. Be re device you can only use the touchwiz roms
Click to expand...
Click to collapse
100% agree. Nothing like taking the chance that all is ok, just to get everything set up, issues show their ugly heads, and you end up starting from scratch anyway.
At this point, you're basically at square one, just do it right and save a ton of headaches down the road

az_biker said:
100% agree. Nothing like taking the chance that all is ok, just to get everything set up, issues show their ugly heads, and you end up starting from scratch anyway.
At this point, you're basically at square one, just do it right and save a ton of headaches down the road
Click to expand...
Click to collapse
As I mentioned earlier, I used the towelroot method to get root originally. Can you point me towards a thread that has the most current method to gain root on the Note 3?

waxcatharsis said:
As I mentioned earlier, I used the towelroot method to get root originally. Can you point me towards a thread that has the most current method to gain root on the Note 3?
Click to expand...
Click to collapse
If you're on NC4, towelroot is the most current.

thegamerdarkseid said:
If you're on NC4, towelroot is the most current.
Click to expand...
Click to collapse
Great, so to be clear you recommend unrooting and rooting again?

waxcatharsis said:
Great, so to be clear you recommend unrooting and rooting again?
Click to expand...
Click to collapse
Are you already rooted? Explain fully, are you still trying to use clockwork mod or have you gotten rid of that and trying safestrap?

thegamerdarkseid said:
Are you already rooted? Explain fully, are you still trying to use clockwork mod or have you gotten rid of that and trying safestrap?
Click to expand...
Click to collapse
I have root and safestrap now. I didn't remove CWM I just installed safestrap. It works fine but I am getting an error message that says "system software not authorized" on boot that I have to bypass by pressing volume down, home and power at the same time. It's really a minor inconvenience so I'm not too worried about it but if there's a simple fix I'd like to do that.

waxcatharsis said:
I have root and safestrap now. I didn't remove CWM I just installed safestrap. It works fine but I am getting an error message that says "system software not authorized" on boot that I have to bypass by pressing volume down, home and power at the same time. It's really a minor inconvenience so I'm not too worried about it but if there's a simple fix I'd like to do that.
Click to expand...
Click to collapse
You really may not want to but it'll be best to start over as there's no telling what kind of problems having clockwork mod on a phone with a locked bootloader might bring down the line. Things may seem okay now with a minor inconvenience but you just never know.

thegamerdarkseid said:
You really may not want to but it'll be best to start over as there's no telling what kind of problems having clockwork mod on a phone with a locked bootloader might bring down the line. Things may seem okay now with a minor inconvenience but you just never know.
Click to expand...
Click to collapse
Alright. I can wipe my phone from safestrap but do you know if that will get rid of CWM also?

waxcatharsis said:
Alright. I can wipe my phone from safestrap but do you know if that will get rid of CWM also?
Click to expand...
Click to collapse
You SHOULD be able to perform a FACTORY RESET / WIPE from Android download, that will return your phone to OEM, unrooted (should remove CWM) and all your peronal files.
Then start the process from scratch, the NC4 Root link in my sig has links to the files you need to get back up and running.
This will give you peace of mind that no 'unknowns' are hanging around waiting to surface...

az_biker said:
You SHOULD be able to perform a FACTORY RESET / WIPE from Android download, that will return your phone to OEM, unrooted (should remove CWM) and all your peronal files.
Then start the process from scratch, the NC4 Root link in my sig has links to the files you need to get back up and running.
This will give you peace of mind that no 'unknowns' are hanging around waiting to surface...
Click to expand...
Click to collapse
Thanks Biker, I was at a function last night and couldn't get back to him.

Related

[Q] att galaxy s 4 cant get into recovery

I have a Att galaxy s4 i337 and I'm running black box ROM I don't know what happen but every time I try to go into recovery it brings up a yellow icon and its says Att found unsupported soft wear. Can some please help me fix this issue I tried flashing the stock tar file in Odin but it won't pass.I need some serious help. Can some assist me!
That sounds more like download mode. There are a bunch of quick boot/recovery apps in the play store. Those would be easiest.
Sent from my TARDIS
0p3nsrc said:
That sounds more like download mode. There are a bunch of quick boot/recovery apps in the play store. Those would be easiest.
Sent from my TARDIS
Click to expand...
Click to collapse
But the thing is I can get into download mode but not my recovery
swaggsexy said:
But the thing is I can get into download mode but not my recovery
Click to expand...
Click to collapse
0p3nsrc actually answers this.
Two steps: #1. Download an app like Quickboot and then #2. start that app and use it to reboot either recovery or download mode (your choice). It should work.
I have had the same problem of the "unauthorized software" in the past and got around it by doing the manual process to get into recovery.
That is #1. turn off phone
#2. hold Volume up and keep holding it while pressing power button to start the phone
#3. Keep holding power+Volume UP button until you see the recovery indications (small print on top left part of screen).
#4. RElease the power button but DONT let go of the volume up button until you're actually in recovery. . .
you may have to try it a few times in a row to get it going, but it eventually WILL get you into recovery!
markbc01 said:
0p3nsrc actually answers this.
Two steps: #1. Download an app like Quickboot and then #2. start that app and use it to reboot either recovery or download mode (your choice). It should work.
I have had the same problem of the "unauthorized software" in the past and got around it by doing the manual process to get into recovery.
That is #1. turn off phone
#2. hold Volume up and keep holding it while pressing power button to start the phone
#3. Keep holding power+Volume UP button until you see the recovery indications (small print on top left part of screen).
#4. RElease the power button but DONT let go of the volume up button until you're actually in recovery. . .
you may have to try it a few times in a row to get it going, but it eventually WILL get you into recovery!
Click to expand...
Click to collapse
It won't work its saying. In Lil orange writting on top left kernel fail don't know what to do!
swaggsexy said:
I have a Att galaxy s4 i337 and I'm running black box ROM I don't know what happen but every time I try to go into recovery it brings up a yellow icon and its says Att found unsupported soft wear. Can some please help me fix this issue I tried flashing the stock tar file in Odin but it won't pass.I need some serious help. Can some assist me!
Click to expand...
Click to collapse
Hay "sexy" what base are you?
MDL or MF3
your profile lacks your phone and its base
Sent from my SAMSUNG-SGH-1337 using xda app-developers app
No matter which galaxy I had (s i9000, s2 i777, or my current s4), I've always has issues with the button combo for recovery. The safest/easiest had always been the quickboot app.
To the OP: black box ROM is ONLY meant for the international s4 (i9500). Major difference in hardware from the att s4 is the octocore processor. You are most likely getting kernel failure due to the ROM/kernel combo. Not 100% sure, though. Aside from kernel fail, any other parts to the error message? Post a screenshot of your "about device" under system settings > more..
For example, mine:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my TARDIS
that is what im getting is kernel fail on the top left hand corner
andriod system erased
if i accidentally erased my system on my phone how can i get tht back on a att galaxy s4
swaggsexy said:
if i accidentally erased my system on my phone how can i get tht back on a att galaxy s4
Click to expand...
Click to collapse
Explain.... How did you erase your system? Furthermore, are you talking about: your whole phone, the /system directory, or your internal sdcard? I've seen some people on the xda forums using 'system' a little too open-endedly.
If you mean /system, you're only option is flashing a ROM, unless you had a nandroid backup, in which case, depending on your recovery, you'd be able to do an advanced restore of the backup.
The same holds true if the whole phone has been wiped.
Sent from my TARDIS
swaggsexy said:
that is what im getting is kernel fail on the top left hand corner
Click to expand...
Click to collapse
swaggsexy said:
if i accidentally erased my system on my phone how can i get tht back on a att galaxy s4
Click to expand...
Click to collapse
swaggsexy said:
It won't work its saying. In Lil orange writting on top left kernel fail don't know what to do!
Click to expand...
Click to collapse
swaggsexy said:
But the thing is I can get into download mode but not my recovery
Click to expand...
Click to collapse
swaggsexy said:
I have a Att galaxy s4 i337 and I'm running black box ROM I don't know what happen but every time I try to go into recovery it brings up a yellow icon and its says Att found unsupported soft wear. Can some please help me fix this issue I tried flashing the stock tar file in Odin but it won't pass.I need some serious help. Can some assist me!
Click to expand...
Click to collapse
Since you can't get into recovery, based on what you've described, this means that you 1) flashed a recovery that was NOT loki'd 2) flashed a boot.img that was NOT loki'd.
This is most definitely something that can be fixed, depending on what Firmware your device is on.
If you know FOR A FACT that you have the MF3 bootloader, then I can walk you through how to use Heimdall to flash the phone back to an "out-of-the-box" state with MF3 firmware on it.
Is the Heiman method good to bring bacc to stock
jakew02 said:
Since you can't get into recovery, based on what you've described, this means that you 1) flashed a recovery that was NOT loki'd 2) flashed a boot.img that was NOT loki'd.
This is most definitely something that can be fixed, depending on what Firmware your device is on.
If you know FOR A FACT that you have the MF3 bootloader, then I can walk you through how to use Heimdall to flash the phone back to an "out-of-the-box" state with MF3 firmware on it.
Click to expand...
Click to collapse
If u can that would be appreciated. And the only thing I did was out a new room black box rom and root nothing going else done to the phone
swaggsexy said:
If u can that would be appreciated. And the only thing I did was out a new room black box rom and root nothing going else done to the phone
Click to expand...
Click to collapse
are you 100% positive that you were on MDL firmware? as in, you DID NOT take the OTA update for MF3? if you are on the wrong bootloader then this will brick your device.
honestly it's safer, you could just take it to BestBuy and tell them it "turned off during an update" or that you just want it reset
jakew02 said:
are you 100% positive that you were on MDL firmware? as in, you DID NOT take the OTA update for MF3? if you are on the wrong bootloader then this will brick your device.
honestly it's safer, you could just take it to BestBuy and tell them it "turned off during an update" or that you just want it reset
Click to expand...
Click to collapse
I fixed everything I just took of the Md5 off the tar file and put into Odin and it flashed just fine. Thanks for the input guys
swaggsexy said:
I fixed everything I just took of the MF3 or the tar file and put into Odin and it flashed just fine. Thanks for the input guys
Click to expand...
Click to collapse
awesome, sounds good.
as long as you have a bootloader from any firmware PRIOR to MF3, then you can just flash loki-doki as a precaution, otherwise you'll need to use SafeStrap, and I have not looked into that as I personally have no need to

[Guide][P600 Only] - Guide to return to stock with links to files!

I created a spot on my website for the stock Odin Tar's that I use for the P600.
I posted the US / XAR Region Stock Odin. I also posted the ML1 Asian base I used as well.
As I gather newer ones I will put them up and updated this thread.
Although this guide is written for the p600 it would, in theory work on any P60x device so long as you have the proper Odin files!
Note: This will not "untrip knox"!!!!!!!!
Here is the download page on my site:
MOD EDIT: Link removed as domain has expired. Thread closed until new links can be installed
Enjoy!​
Currently Hosted:
P600UEUBMK1_P600XARBMK1_XAR (Shipped US ROM / XAR Region)
P600ZTUBML1_P600ZZTBML1_BRI (Asian Based ROM / BRI Region)
Other Odin Tar resources: Sammobile. Must be a member but they have tons of them.
How to Return to stock
This mini guide assumes the following...
You were able to root and or install a custom recovery or ROM therefore the drivers are installed on your PC for the tablet. So here we go...
Download Odin from the links in the OP
Extract the the .md5 file from the zip file you downloaded above.
Boot tablet into "Download" mode. You can do this by holding Power and Volume - (down) when the device is shut off. I note on this device it can be a little trickier so you may have to try a couple times. You should now see this on your tablet
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Connect Tablet to PC using known good USB Cable
Start Odin and Press the "AP" button to load the tar.md5 file. This may take a minute as it is also calculating the MD5 to ensure you have a good file. A bad file means bad issues and it wont let you flash it (good fail safe).
Once Odin sees the Tar and loads it completely AND Odin sees the tablet press the Start button to begin. Can takes about 5 to 10 minutes so be patient. Do NOT check or uncheck mark ANY other Options in Odin unless you know what you are doing!
Once it complete you will have a factory image on your tablet. Yay!
But we are not done. You may also want to, at this point, reboot to recovery and do a full data wipe. This method of Odin leaves the SD card and user data intact. To get into recovery hold Power and Volume + until you see the stock Android recovery. Select format Data, reboot. Boom, your tablet is like brand new!
Guided added!
I am not the best technical writer so if you need help understanding what I am saying dont hesitate to ask!
Bumped so people can find this...
Mods moved it so no one looking will actually see it...
scrosler said:
Bumped so people can find this...
Mods moved it so no one looking will actually see it...
Click to expand...
Click to collapse
I'm glad you bumped it. I still haven't tried to install any custom ROM in this tablet, but this post will sure come in handy soon!
Vexelius said:
I'm glad you bumped it. I still haven't tried to install any custom ROM in this tablet, but this post will sure come in handy soon!
Click to expand...
Click to collapse
Indeed!
What happens if I failed to root (according to TWRP) and am stuck in the Samsung splash screen? I was obviously able to install TWRP so hopefully that is enough for Odin to get me back to stock
Will this work?
kaneelias said:
What happens if I failed to root (according to TWRP) and am stuck in the Samsung splash screen? I was obviously able to install TWRP so hopefully that is enough for Odin to get me back to stock
Will this work?
Click to expand...
Click to collapse
If you can see samsung screen you can odin back to stock.
The directions I posted should hold true about getting to Odin / Download Mode
Thanks for this guide, I agree, it should definitely be in the development section.
Hello
So will I get the OTA updates after this? How do I untrip knox?
thanks
Thanks for this Scott and a great ROM!!!!
Sent from my SAMSUNG-SGH-I317 using Tapatalk
tahrang said:
Hello
So will I get the OTA updates after this? How do I untrip knox?
thanks
Click to expand...
Click to collapse
Yes, this is returning you to stock like when you turned it on for the very first time.
No one knows how to untrip knox.
Is it Knox that blocks the ota updates, or is it the rooting itself?
starfall42 said:
Is it Knox that blocks the ota updates, or is it the rooting itself?
Click to expand...
Click to collapse
Not sure. Never tried to Ota with KNOX.
Maybe ask in the Q/A forums.
Just to be safe, and If I do this the tablet will be as if it was completely new, right? I'm going to exchange it for another one and I want to be sure it's as new. Are there any flash counters or stuff like that I should be worried about?
Sent from my Nexus 5
So when a system update comes out we could use these directions to flash the stock rom with out loosing data, apps, settings, etc? Then be able to get the stock OTA?
Coming from the Nexus world, This is a bit different. Google seems to have no interest in the 10 inch sector though, so here we are.
Never have we had a tablet so heavily defended with so many issues. 6 tablets and this one stands out.
Via my Note 3
Tripping out?
scrosler said:
Note: This will not "untrip knox"!!!!!!!!
Click to expand...
Click to collapse
I think I understand what you are saying, but I'm new to Android, and would appreciate a sanity check::cyclops:
1. Knox "trips" (i.e. opens a fusible link in the hardware) if you root the tab and (or?) boot with a non-factory ROM. Once it trips, it cannot ever be "untripped", even if you return to a factory ROM image. (Hence the emphatic statement in the quote.)
2. Question: If a tablet is currently, and has always been, unrooted and stock, will using Odin and these instructions with a factory ROM trip knox? For example, to upgrade to the factory KitKat image
3. Follow-up question: If I flash KitKat as above, can I return to the original release by following your guide, again without tripping knox?
Thanks for the guide and software, and for your help.
iTelegraph said:
I think I understand what you are saying, but I'm new to Android, and would appreciate a sanity check::cyclops:
1. Knox "trips" (i.e. opens a fusible link in the hardware) if you root the tab and (or?) boot with a non-factory ROM. Once it trips, it cannot ever be "untripped", even if you return to a factory ROM image. (Hence the emphatic statement in the quote.)
2. Question: If a tablet is currently, and has always been, unrooted and stock, will using Odin and these instructions with a factory ROM trip knox? For example, to upgrade to the factory KitKat image
3. Follow-up question: If I flash KitKat as above, can I return to the original release by following your guide, again without tripping knox?
Thanks for the guide and software, and for your help.
Click to expand...
Click to collapse
1. As far as anyone knows, Knox cannot be untripped.
2. If you Odin a FACTORY IMAGE it WILL NOT trip Knox. Only custom roms/rooting trips AFAIK.
3. I'm not 100% sure as I haven't tried, but I think I've seen discussions where the bootloader wasn't changed so you could go back. Again, I'm not 100% sure. Maybe we could get clarification from someone who tried.
Sent from my SM-P600 using Tapatalk

Best method to root on 4.2.2?

My phone was rooted and I did a factory reset to send it to have the screen repaired. I lost root and I get the message "com.android.phone not responding" all the time if I restart the phone but it works fine. Someone told me to use Odin to wipe the phone and get rid of that message. After I do that, what tool should I use to root on 4.2.2?
Need MORE info. What was the Original firmware/ what firmware do you have right now? You said 4.2.2 but which one? MDB? MDL? or MF3?
MDB and MDL you can do a lot note with and use motochopper + Loki bootloader bypass. MF3 patched the exploit and can only use safestrap recovery.
Read some of the threads once you find which firmware you have and/or on right now. If your stock, then beware it will AUTO UPDATE you without your consent. So find out what you have and need to do quickly.
RockRatt said:
Need MORE info. What was the Original firmware/ what firmware do you have right now? You said 4.2.2 but which one? MDB? MDL? or MF3?
MDB and MDL you can do a lot note with and use motochopper + Loki bootloader bypass. MF3 patched the exploit and can only use safestrap recovery.
Read some of the threads once you find which firmware you have and/or on right now. If your stock, then beware it will AUTO UPDATE you without your consent. So find out what you have and need to do quickly.
Click to expand...
Click to collapse
Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Looks like it's MDL?. So I guess motochopper then. Mine cannot auto update fortunately. It fails every time. I've had it like that for a while but now I really want to root it again. I think it's because of that error I get on start-up that the update fails.
SRCP said:
Thanks.
Looks like it's MDL?. So I guess motochopper then. Mine cannot auto update fortunately. It fails every time. I've had it like that for a while but now I really want to root it again. I think it's because of that error I get on start-up that the update fails.
Click to expand...
Click to collapse
I had a similar situation, and the AT&T updates would fail at ~28%, even though I never approved the updates (my guess is that after I've said no more than 3 time, they did it anyways?). At that point I was stuck, and to make things worse, the WiFi was working only in my house, but no data over the ATT network, just voice. Even reflashing with ODIN didn't resolved the problem.
Had to bite the bullet and get the phone replaced by the warranty. I hope this doesn't happen to anyone else,
SRCP said:
Thanks.
Looks like it's MDL?. So I guess motochopper then. Mine cannot auto update fortunately. It fails every time. I've had it like that for a while but now I really want to root it again. I think it's because of that error I get on start-up that the update fails.
Click to expand...
Click to collapse
Since it is MDL firmware just use Motochopper + Loki and you will have a custom recovery (TWRP or CWM YOUR CHOICE). Then flash ANY custom ROM on your phone. You can have the best of BOTH worlds. You can flash a updated firmware ROM like ShoStock for the Touchwiz based Roms or a AOSP based ROMs. NO need to update firmware from ATT. In fact you lose what you can do with your phone if you do.
If you REALLY want to update to ATT newest firmware you can download the STOCK MDL firmware from samfirmware. Flash it which will make your phone PURE STOCK firmware and recovery. Then you will be able to update from ATT. The reason it fails is because you are rooted and probably custom recovery already?
Thanks. Well, I had it rooted but it seems like I lost root when I did something, I don't remember but I think it's when I factory reset it to send it to be repaired. It still says custom when I turn restart it but I am not rooted. I'm not very knowledgeable at this, I just follow guides step by step. I used an old method to root, it was an automated tool, can't remember the name. Anyway, in my current custom, non-rooted state, sgould I do something first before using motochopper?
SRCP said:
Thanks. Well, I had it rooted but it seems like I lost root when I did something, I don't remember but I think it's when I factory reset it to send it to be repaired. It still says custom when I turn restart it but I am not rooted. I'm not very knowledgeable at this, I just follow guides step by step. I used an old method to root, it was an automated tool, can't remember the name. Anyway, in my current custom, non-rooted state, sgould I do something first before using motochopper?
Click to expand...
Click to collapse
If you got it repaired does it have the same firmware version on it? Got to menu, settings, more, about device and look for the last three characters of your baseband. What are they?
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
If you got it repaired does it have the same firmware version on it? Got to menu, settings, more, about device and look for the last three characters of your baseband. What are they?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, that pic is recent. I got it repaired months ago.

VS980 TWRP bootloop after botched lollipop OTA while rooted like a dummy

So yeah. As the title says I had a rooted VS980 on 4.4.2 with some bloat removed and I accidently hit the wrong button when prompted for the upgrade, I was in a hurry. yes, I'm a moron, and yes, I know this is probably wasting someone's valuable time and I thoroughly apologize for my n00bishness
having said that, I have tried to go through various tuts but none of them seem to be working. yes, it's likely that I am simply doing it wrong, but whatever the case I am stuck with my phone in a bootloop always returning to the TWRP recovery. I believe that means it is soft bricked so I'm hoping this can be fixed fairly easily with the right direction and some patience for my ignorance. I can't seem to get it into download mode with turning it off, holding the volume+ button and plugging it in, it just goes to twrp. :'(
my hope is to get a rooted lollipop. if that is not possible then I would be fine with going back to stock or possibly even a custom rom if it's not too awfully complicated. honestly, I'm at a point where I'm beginning to accept that I probably shouldn't be screwing around with it too much and will likely bite the bullet and just keep my phone stock since there are really only a few minor irritants that make me want to root it.
any help is very much appreciated.
anybody? pretty please? any ideas at all?
Deviouz1 said:
anybody? pretty please? any ideas at all?
Click to expand...
Click to collapse
I have the same problem.. take a look at my post in this section... right under yours... I have links posted to the only method to fix it and also a good question that could help you out as well
a.perkins89 said:
I have the same problem.. take a look at my post in this section... right under yours... I have links posted to the only method to fix it and also a good question that could help you out as well
Click to expand...
Click to collapse
actually, it doesn't look to be the same problem. i dont have download mode, but i do have recovery. it boots to twrp like a champ. what i think i really need is how to get the flash file VS98011A_01.zip on my phone via ADB Sideload, specifically when i cant get the drivers to work.
i've tried the following drivers:
LG_VZW_United_WHQL_v2.14.1.exe
LG_VZW_United_WHQL_v2.20.0.exe
LGUnitedMobileDriver_S50MAN310AP22_ML_WHQL_Ver_3.10.1_3.10.1.0
I may very well be mistaken about what needs to happen, i'm no expert, obviously, but from everything ive read any of those should have worked. i think if i can get the right flash on the phone i should be able to flash it via twrp no?
I"ll help
You need to adb sideload xdabbebs download mode restore and flash back to stock. Here is an excellent guide on adb sideloading, download xdabbeb restore download zip and put it where it tells you to. http://forum.xda-developers.com/showthread.php?t=2559200
Jaqueezzzy said:
You need to adb sideload xdabbebs download mode restore and flash back to stock. Here is an excellent guide on adb sideloading, download xdabbeb restore download zip and put it where it tells you to. http://forum.xda-developers.com/showthread.php?t=2559200
Click to expand...
Click to collapse
awesome,thanks you, i'll try that!
Deviouz1 said:
awesome,thanks you, i'll try that!
Click to expand...
Click to collapse
Just so you know it talks about flashing a ROM, but just use the zip you need insted, because it's the same principal.
Step 9 Fails.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i just happened to have a brand new data cable, tried again with same result so its not media related unless there is an issue with the plug itself, but it's charging and the Device manager shows the correct name ie VS980, it just has a yellow bang on it and i cant find a driver that changes that.
read some more and found others with the same issue apparently which led me to here: http://forum.xda-developers.com/showthread.php?t=2715408
which is where i found the "download mode restore" file you mentioned(i didnt see it in the thread you provided), but without the ability to get adb usb command to work i dont see how i can use it.
any ideas?
Put the zip on usb otg and flash it.
_____________________________________Read more write less and be smart
siggey said:
Put the zip on usb otg and flash it.
_____________________________________Read more write less and be smart
Click to expand...
Click to collapse
awesome, ty sir. i happened to have one of those laying around from when i cracked my screen on my old one and couldnt interact with the screen. took a while to find it buried but i have it and i have successfully been able to access a thumb drive. i think that might be all i need.
will report back though regardless.
ok, now i'm rrrrrEEAALLYY freakin confused...
successfully flashed (via the install section of twrp with usb otg thumbdrive mounted.)
xdabbeb_vs98028a_bootstack.zip
and
xdabbeb_vs982.5_1.1.0.zip
from
http://forum.xda-developers.com/verizon-g2/development/xdabbeb-s-vs982-5-v1-0-0-t2975551
but when i reboot, it goes directly to twrp still.
wat? :'(
ok, installed this:
VS980 39A Firmware
from here:
http://forum.xda-developers.com/verizon-g2/development/vs98039a-stock-fw-t3051560
rebooted, went straight to twrp again.
installed
Restore to 100% stock
from the same page.
rebooted. it went into an upgrade screen that errored and then rebooted before i got a chance to write down the error. but when it came back up, it started "android is upgrading".
so it looks like this may have worked. again, will update the success/failure when i know for sure, but thanks for the help yall. i really do appreciate it.
WOO-FREAKIN-HOOOO!!!
at the setup wizard now.
Deviouz1 said:
ok, installed this:
VS980 39A Firmware
from here:
http://forum.xda-developers.com/verizon-g2/development/vs98039a-stock-fw-t3051560
rebooted, went straight to twrp again.
installed
Restore to 100% stock
from the same page.
rebooted. it went into an upgrade screen that errored and then rebooted before i got a chance to write down the error. but when it came back up, it started "android is upgrading".
so it looks like this may have worked. again, will update the success/failure when i know for sure, but thanks for the help yall. i really do appreciate it.
Click to expand...
Click to collapse
Same problem! stupid Ota grrrrr
Your fix worked for me also. Only used the two files listed above and wiped dalvik after flashing both, one after the other with no reboot in between. Many thanks.
thecadman99 said:
Same problem! stupid Ota grrrrr
Your fix worked for me also. Only used the two files listed above and wiped dalvik after flashing both, one after the other with no reboot in between. Many thanks.
Click to expand...
Click to collapse
sweet, i'm glad someone else found it useful.
Yep, now another problem though. ..no mobile data. .. working on it.
I'd suggest flashing the files in post 12 (I didn't and am having TONS of problems)
So I really didn't get a fix- still working on it.
I have no download mode, and not way to get the serial port to display in device manager, so the LG Mobile support tool won't see my phone....
thecadman99 said:
Yep, now another problem though. ..no mobile data. .. working on it.
I'd suggest flashing the files in post 12 (I didn't and am having TONS of problems)
So I really didn't get a fix- still working on it.
I have no download mode, and not way to get the serial port to display in device manager, so the LG Mobile support tool won't see my phone....
Click to expand...
Click to collapse
Is your baseband recognized by chance?
Deviouz1 said:
Is your baseband recognized by chance?
Click to expand...
Click to collapse
Nope... its UNKNOWN
And I have not download mode
And I have not cdc serial showing up when connected
And TWRP and Root are gone
I'm starting a new thread for help- I've been working on this for 2 days lol.
Thanks for the reply!

Galaxy Grand Prime LTE (SM-S920L) / Lollipop 5.0.2 / Straight Talk

I just got one of the new Straight Talk Grand Prime variants from Walmart. I can't find ANYTHING on the model (SM-S920L) AT ALL. Anyone else get this model? I'm desperately seeking the stock recovery.tar for this phone as i attempted to flash a CWM recovery without backing up the stock firmware. Needless to say this didn't work and i was left with "recovery is not Seandroid enforcing"., when i attempt to boot into recovery.
HELP!!!!!
http://www.walmart.com/ip/Straight-Talk-Samsung-Prepaid-Galaxy-GRAND-Prime-LTE-S920C-Smartphone/46716301
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have this SAME model. Im rooted with KING ROOT but cant find a custom recovery.
hondais1 said:
I have this SAME model. Im rooted with KING ROOT but cant find a custom recovery.
Click to expand...
Click to collapse
I just tried king root and it failed. I have the same model
I'll upload the version of KINGROOT that I have. Give me a few hours
Deejaydark said:
I just tried king root and it failed. I have the same model
Click to expand...
Click to collapse
That's odd...Kingroot worked like a charm for me as well. Do u have super su installed?
I think you're right. I think it has to be the newest version of King Root that doesn't use the kinguser app anymore(version 4.6.2). Oh! And I've submitted the files needed to fashion a custom recovery but haven't heard back yet. I will keep u guys posted.
Hydro_Axis said:
That's odd...Kingroot worked like a charm for me as well. Do u have super su installed?
Click to expand...
Click to collapse
Got it now
Hydro_Axis said:
I think you're right. I think it has to be the newest version of King Root that doesn't use the kinguser app anymore(version 4.6.2). Oh! And I've submitted the files needed to fashion a custom recovery but haven't heard back yet. I will keep u guys posted.
Click to expand...
Click to collapse
Finally, something is beginning to Surface on this model. Can you by chance upload the pit file? I bricked while I ventured into the unknown....every flash attempt fails....can't even do smart switched recovery. Hell, this model isn't even in Samsung's database.
adrwill2000 said:
Finally, something is beginning to Surface on this model. Can you by chance upload the pit file? I bricked while I ventured into the unknown....every flash attempt fails....can't even do smart switched recovery. Hell, this model isn't even in Samsung's database.
Click to expand...
Click to collapse
is this what your looking for? I know what u mean about not being able to find anything. I'd imagine its because the manufacture date is 6/15. This variant is still very new. I'm willing to do whatever i can to help get the ball rolling though.
Regards
Hydro_Axis said:
I think you're right. I think it has to be the newest version of King Root that doesn't use the kinguser app anymore(version 4.6.2). Oh! And I've submitted the files needed to fashion a custom recovery but haven't heard back yet. I will keep u guys posted.
Click to expand...
Click to collapse
Hydro_Axis said:
is this what your looking for? I know what u mean about not being able to find anything. I'd imagine its because the manufacture date is 6/15. This variant is still very new. I'm willing to do whatever i can to help get the ball rolling though.
Regards
Click to expand...
Click to collapse
Thanks for that! Except now I need a stock rom. I'm going to look into that one. Sounds like a task....I just want to get this puppy to work again.
Grand Prime sm-s920L
I am stuck in recovery mode and I have taken the battery out for a few and stick it back in and still stuck in recovery mode. How can I get out of this?
Same boat, but I am stuck in Odin mode. Made the mistake of trying to flash TWRP on it. Cannot find a the right one to reflash the ROM. I see many for other versions, but not ours.
Their isn't a custom recovery for this particular LTE version, I've seen one individual say.he got it to work with TWRP but he has to be bull****ting...their is the stock rom already posted to the forums tho if you can get it to were your able to flash it...I see that CWM has its own custom recovery builder on their site now I was wondering if that would actual work???
Medfordite said:
Same boat, but I am stuck in Odin mode. Made the mistake of trying to flash TWRP on it. Cannot find a the right one to reflash the ROM. I see many for other versions, but not ours.
Click to expand...
Click to collapse
http://forum.xda-developers.com/gra...sm-s920l-straight-talkverizon-galaxy-t3252413
this is the link that someone has with the stock firmware. I got mine out of recovery by trying to odin the pit file but failed and it still booted back where i had my device. good luck
SM-S920L Rooted
Hello, i got my device to take ROOT in about an hour.
Here is the list of programs i used:
~Samsung USB Driver for Mobile Phones for Windows
~SuperSU apk v2.46
~Superuser apk v3.1.3
~One Click Root for Windows
~Kingo Root for Windows
~KingRoot for Windows
~Root Check apk
step 1. run as administrator: SamsungUSBDriver.exe (Windows)
step 2. Install Superuser.apk v3.1.3 (Android) does not require ROOT
step 3. run as administrator: One Click Root.exe (Windows) ROOT Will Fail
step 4. run as administrator: Kingo Root.exe (Windows) Root Will Fail
Step 5. run as administrator: Kingroot.exe (Windows) Device ROOTED
Step 6. Install SuperSU apk v2.46 (Android) Update Binary Normal
Step 7. Enjoy
That is an unnecessarily convoluted path to rooting this device. KingRoot apk v4.5.0 can literally root this phone is less than 5 minutes and SuperSU-ME Pro can replace KingRoot in a further 5 minutes.
Wonder if there's actually anyone making progress towards obtaining the Rom for this model.
Doubtful. There is zero interest in this variant.
Gahhh nooo, dont say that. Here's hoping an anon comes and saves the day sometime soon.
Hydro_Axis said:
I just got one of the new Straight Talk Grand Prime variants from Walmart. I can't find ANYTHING on the model (SM-S920L) AT ALL. Anyone else get this model? I'm desperately seeking the stock recovery.tar for this phone as i attempted to flash a CWM recovery without backing up the stock firmware. Needless to say this didn't work and i was left with "recovery is not Seandroid enforcing"., when i attempt to boot into recovery.
HELP!!!!!
http://www.walmart.com/ip/Straight-Talk-Samsung-Prepaid-Galaxy-GRAND-Prime-LTE-S920C-Smartphone/46716301
Click to expand...
Click to collapse
mr hydro i have this phone model too.. i love it but i bricked mine from messing with the build.rop fiel... if you see this reply i need you to post a full partition back up of your /system, /boot, /recovery folders or watever.. i was going to ry to flash in folders to fix my phone

Categories

Resources