Related
So, this happened recently, and I fixed it. Link: http://forum.xda-developers.com/showthread.php?t=1735119
Well, outta no where, same basic issue, but with a twist.
This afternoon while I was asleep my GTab rebooted. It came back to the "Samsung Galaxy Tab 7.0 Plus" splash screen and is stuck. I *can* get into download mode, and I can almost get into recovery. When I try to go into recovery, it loads what looks like it will be recovery, then says:
# Manual Mode #
-- Updating Application
Then a minute or so later it reboots right back to the GT7+ splash screen and stays there...
Twist:
So, knowing what I did last time, I installed Odin and the Samsung drivers on my POS computer at home, booted into Download Mode, and did the "PDA" option with the correct FW (same as I used last time for the T869 from SamMobile, I saved all the files). It runs through just fine, gets to the end and the Tab reboots. It then goes into recovery and and does a few things (I believe it said it was deleting the cache and a few other processes). Then, lastly, it again says:
"# Manual Mode #
-- Updating Application
... followed by a reboot, and back to hanging on the boot logo.
Any ideas?!? Ironically, I put it on CL today to see if I can sell it for enough to cover a Nexus7. I woke up to an offer, and a bricked Tab. Figures.
Any thoughts/help are greatly appreciated. The sooner the better. lol
Is it possible that I need to flash a good recovery in Odin? If so, what's the procedure. and can someone link me to the one I would need for the US TMobile 4G version of the GT7+?
Also, since flashing the stock FW isn't fixing anything, and it seems like a possible Recovery issue, a friend at work is suggesting I choose the option in Odin to delete the partitions.
Thoughts??? (quickly)
Damn dude, again?
I think there is 3 or 4 threads about this on this forum and same amount on 7.7 forum. None come to a cause our solution, seems like people repeats some procedures and out of nothing it works again.
When it happened to me a let its battery drain fully to the point it won't turn on anymore let it this way for some time. Then fully charged, this is a little harmful to your bat, for the record. Then try to turn on, it will take some time but eventually it could enter on the system.
I think the data partition got corrupted.
Sent from my GT-P6210 using Tapatalk 2
Yup.
So, I tried the option in Odin to re0make the partition, and every time I try it fails with an error of "Can't Open Package" (or something along those lines).
I have reinstalled the FW through Odin no less than 10 times, nogo. The first time I open recovery after flashing, It says it is installing a package, clearing cache, etc, and the last line always says "-- Updating Application". After 10-15 seconds, that goes away and it reboots only to hang on the GT7Plus splash screen again. Then, any time I go into recovery after that first post-Odin instance, if says:
"# Manual Mode #
-- Updating Application
Should I be trying to reinstall Recovery? If so, what do I use (link)? Also, how do I do that in Odin...
I believe that for use remake partition you have to provide the pit file if your stock does not have it.
Anyway I did that also about 3 times, providing the pit and the md5, they flashed ok, but the problem was the same. Did you tried the battery thing? Some guy give a tip to start with the usb plugged.
Sent from my MB525 using Tapatalk 2
leodfs said:
I believe that for use remake partition you have to provide the pit file if your stock does not have it.
Anyway I did that also about 3 times, providing the pit and the md5, they flashed ok, but the problem was the same. Did you tried the battery thing? Some guy give a tip to start with the usb plugged.
Sent from my MB525 using Tapatalk 2
Click to expand...
Click to collapse
Where was that tip? Link?
Also, any one have that .pit file I can try with?
http://forum.xda-developers.com/showthread.php?p=28574760
Sent from my MB525 using Tapatalk 2
Hey buddy..
Which fw u using? T869 came shipped with 2 different, search for both of them and try each one...don't use repartition without the correct pit file...
Maybe not here but I google sgh-t869 factory and found a website with both tar
Sent from my Galaxy Nexus using xda app-developers app
statuzz said:
Hey buddy..
Which fw u using? T869 came shipped with 2 different, search for both of them and try each one...don't use repartition without the correct pit file...
Maybe not here but I google sgh-t869 factory and found a website with both tar
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I'm not sure which file it is that I'm using, I'll have to look at home in a couple of hours. This happened to me a few weeks ago (link in original post), and I flashed this FW with Odin and it recovered, and has been fine since (till now), so I know it's at least a usable FW. I'll try to find the other one today.
I just tried finding the stock pit file for the TMo SGH-T869, but I can't find it. Anyone have a link to it by chance? Also, once I get it, what do I do (options to choose) in Odin to flash it?... and do I do it at the same time as the FW?
Thanks for any help! I was really hoping to sell it in the next day or two to fund the Nexus7, so now I'm really frustrated.
ETA: Also, I let it completely die, to the point it wouldn't boot. Then charged it for a bit and booted. Same issue.
I think that if u find the pit file they should be flash at the same time...fw in pda and pit in phone...(this need to be check to confirm) after flashing.. reboot into factory recovery wipe everything and try to boot
Hopefully u fix that today
Sent from my Galaxy Nexus
When it happened to me, i flashed the pit first and at the same with stock with re partition checked, didnt help. I did everything that I could find and I feel like it only worked again by itself
You can look every single thread of this exact problem, the ones that got it back working can't really say how, they flash everything many times and it suddenly works.
The good things are that flash the stock ones don't increase you flash count, and as long as you can enter download mode you are not really s#%
Sent from my MB525 using Tapatalk 2
Thanks for the help...
Anyone have a link to the .pit for this model (T869)?
Also, I had a thought. When I go into Recovery, I get the following and then it reboots again:
# Manual Mode #
-- Updating Application
1. Is it possible that recovery is hosed, and overwriting it with a fresh version will allow me to wipe the device, set to factory and then boot? Maybe this is the issue?
2. Is it even possible to just flash a fresh copy of the recovery over whatever is there (or replace it)?
2.a. If it is possible, what file should I use, and do I do it though Odin? Anyone have a link to what I should use?
Thanks :good:
VisualOddity said:
Thanks for the help...
Anyone have a link to the .pit for this model (T869)?
Also, I had a thought. When I go into Recovery, I get the following and then it reboots again:
# Manual Mode #
-- Updating Application
1. Is it possible that recovery is hosed, and overwriting it with a fresh version will allow me to wipe the device, set to factory and then boot? Maybe this is the issue?
2. Is it even possible to just flash a fresh copy of the recovery over whatever is there (or replace it)?
2.a. If it is possible, what file should I use, and do I do it though Odin? Anyone have a link to what I should use?
Thanks :good:
Click to expand...
Click to collapse
The problem is that there's is not development for t869 so there's not much to look for...just factory images and root method
Sent from my Galaxy Nexus
Can anyone link me to the proper pit file? Also, in the linked thread a few posts back, there are a couple of files, will those work for this?
Can someone post the proper pit file for me so I can repartition? I'm doing this on my wife's phone because my internet at home is down till tomorrow...
Lastly, recovery. Since when I go into recovery it says "manual mode" then reboots, can I replace recovery only? Then I can wipe and whatnot in it and maybe that will do the trick. If so, can someone link me to the proper recovery and tell me how to do it in Odin? What happens if I watch the FW flash, then right after it completes the recovery portion, I unplug it? Bad?
VisualOddity said:
Can anyone link me to the proper pit file? Also, in the linked thread a few posts back, there are a couple of files, will those work for this?
Can someone post the proper pit file for me so I can repartition? I'm doing this on my wife's phone because my internet at home is down till tomorrow...
Lastly, recovery. Since when I go into recovery it says "manual mode" then reboots, can I replace recovery only? Then I can wipe and whatnot in it and maybe that will do the trick. If so, can someone link me to the proper recovery and tell me how to do it in Odin? What happens if I watch the FW flash, then right after it completes the recovery portion, I unplug it? Bad?
Click to expand...
Click to collapse
i think u should forget about the pit file, couz the firmware have the pit repackage with the tar, im gussing u will only need the pit file in case u want to change the phone partitions, try to get those 2 fw and try them :good:
That's why I'd like the pit file, so I can check the option in Odin to re-partition.
So, I have internet at home now. I have now tried again letting it completely die, then completely charge, same issue. I have also tried 2 different versions of the SGH-T869 firmware.
Any thoughts?
Also, given what I have done so far, I posted this yesterday, any thoughts?
"Lastly, recovery. Since when I go into recovery it says "manual mode" then reboots, can I replace recovery only? Then I can wipe and whatnot in it and maybe that will do the trick. If so, can someone link me to the proper recovery and tell me how to do it in Odin? What happens if I watch the FW flash, then right after it completes the recovery portion, I unplug it? Bad? "
Yes. Unplug is bad. Possibly fatal. you should be able to.find a stock recovery.img in a stock Odin.tar, flash it with heimdall. Recommend factory reset beforeand after doing so.
I dont know about tmobile tabs but international ones look to apply CSC files after displaying that manual mode message. Perhaps something has gone awry with a CSC,etc.
chrisrotolo said:
Yes. Unplug is bad. Possibly fatal. you should be able to.find a stock recovery.img in a stock Odin.tar, flash it with heimdall. Recommend factory reset beforeand after doing so.
I dont know about tmobile tabs but international ones look to apply CSC files after displaying that manual mode message. Perhaps something has gone awry with a CSC,etc.
Click to expand...
Click to collapse
Thank You. A few questions:
Would that stock recovery.img have to be model specific. i.e. for the SGH-T869, or could it be from any GT 7 Plus (or is it generic on all devices with HoneyComb)? I *think* from experience it has to be T869 specific, but it's worth asking.
Also, about Heimdall, where do I get that, and how do I use it to flash? I've heard of it, but never used it.
Lastly, about the CSC files. That makes sense seeing as what it's doing, so that *could* be the whole issue. How can I overcome that? Can I download and flash those files somehow? Do you have a link to them?
Thanks for the help everyone. I'm hoping that in doing all this, maybe whatever ends up fixing this will be a guide for everyone else having the issue...
OK, I saw a couple of you guys mention the 7.7 people having this issue, so I went there to research. If I am reading right, it *sounds* like this could be a solid mix of a data system being corrupted, and the stock recovery (Samsung e3?) being bad.
Someone mentioned that you can pull the stock recovery.img from a the firmware, make a .tar with only that, then flash that. Once that's done you can do a full wipe in recovery, flash the full FW, and hopefully be back in business.
I want to try this, and if it works, maybe we will have a proven solution for the people getting this issue. However, not only have I never created a .tar, I have especially never created a flashable .tar, so...
What do I do? Other than pulling the recovery.img from the FW, how do I do this?
I just got my hands on the sprint note edge (such an amazing device!) and i've been trying to root it with cf auto root but every time i flash with Odin, it fails with the progress bar on the phone only about halfway. Any suggestions? I'm on the latest firmware, nk1, which matches the version listed on the cf auto root site.
Thanks in advance
Edit:
HEY, YOU. YEAH YOU. READ THIS BEFORE YOU POST:
We figured out the solution quite a while back, but I know no one wants to read the entire thread, so here's a summary c/p'd from the end:
But to summarize, we've been able to get root by flashing CF auto root, letting it fail, then immediately flashing TWRP. To fix any issues encountered with xposed framework (stock sms not working, lagginess, installations taking forever, etc.), freeze with titanium/delete data for shealth, health services, and private mode, install securestorage module in xposed or use the equivalent option in Wanam, reboot, and unfreeze.
Click to expand...
Click to collapse
Now if you've tried this and you're still having issues, then post ahead. If you haven't tried this, or need help with specifics, read the thread. There's a post by me halfway through or so with 4 XDA links in it. If you want more info on the problem with xposed, check out those links.
jooniloh said:
I just got my hands on the sprint note edge (such an amazing device!) and i've been trying to root it with cf auto root but every time i flash with Odin, it fails with the progress bar on the phone only about halfway. Any suggestions? I'm on the latest firmware, nk1, which matches the version listed on the cf auto root site.
Thanks in advance
Click to expand...
Click to collapse
You may check out this thread: http://forum.xda-developers.com/note-edge/general/easy-steps-stock-odin-n915tuvu1anjl-sm-t2943993
Its for a Tmobile version, but it looks like they may have had the same issue, but figured it out... I haven't tried it yet, but am REAL close to giving it a shot. It looks to me that flashing TWRP after the fail, may be the key to making it successful? I have the Sprint model too, but am still on NJL build.
Does TWRP fully support the note edge yet? Some of those steps (disabling screen timeout) make it seem otherwise. I'm usually hesitant to go for workarounds rather than actual fixes... :/ tell me if you do try it out though.
Next1776 said:
You may check out this thread: http://forum.xda-developers.com/note-edge/general/easy-steps-stock-odin-n915tuvu1anjl-sm-t2943993
Its for a Tmobile version, but it looks like they may have had the same issue, but figured it out... I haven't tried it yet, but am REAL close to giving it a shot. It looks to me that flashing TWRP after the fail, may be the key to making it successful? I have the Sprint model too, but am still on NJL build.
Click to expand...
Click to collapse
I'm not sure about TWRP, but was going to try the Note 4 version. I updated to NK1 now, so may give it a whirl... Nah - You go first, lol. I'll post if I decide to go through with it.:good:
Next1776 said:
I'm not sure about TWRP, but was going to try the Note 4 version. I updated to NK1 now, so may give it a whirl... Nah - You go first, lol. I'll post if I decide to go through with it.:good:
Click to expand...
Click to collapse
Too Funny.. I heard the note 4 files where working from an undisclosed source.. I haven't powered mine on yet, Still waiting on a screen protector and case.. Lol
z31k said:
Too Funny.. I heard the note 4 files where working from an undisclosed source.. I haven't powered mine on yet, Still waiting on a screen protector and case.. Lol
Click to expand...
Click to collapse
to clarify, is that the SPRINT note 4 cf auto root files you're referring to?
Just checked. Sprint Note 4 cf auto root is for NIE. Is this even safe to try on the Edge?
jooniloh said:
to clarify, is that the SPRINT note 4 cf auto root files you're referring to?
Just checked. Sprint Note 4 cf auto root is for NIE. Is this even safe to try on the Edge?
Click to expand...
Click to collapse
That's what I was told.. Sprint note 4 auto root...
I would wait up if you feel uneasy about it.. lol
at least until they have a edge auto root. I may try the note 4 sometime next week when the screen protector comes in..
z31k said:
That's what I was told.. Sprint note 4 auto root...
I would wait up if you feel uneasy about it.. lol
at least until they have a edge auto root. I may try the note 4 sometime next week when the screen protector comes in..
Click to expand...
Click to collapse
There is an edge auto root. It just happens to be failing at the moment (for sprint anyways). There are workarounds for the T-Mobile auto root (which is also failing) but we're all too chicken here to try it on our new shiney Note Edges . . . Lol
jooniloh said:
There is an edge auto root. It just happens to be failing at the moment (for sprint anyways). There are workarounds for the T-Mobile auto root (which is also failing) but we're all too chicken here to try it on our new shiney Note Edges . . . Lol
Click to expand...
Click to collapse
Lmfao!!
OK. I wasn't too chicken... and should have been! HELP!!!!!
I attempted the ODIN flash with the proper CF that states that it is for the Sprint Edge... and now have a soft (I hope) bricked phone. The message I have on the screen right now is:
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Like I said.... HELP!!!!!
I'm not familiar with KIES but I guess I'll get that way....
Update: I am able to get into download mode... now now if I could just get my hands on a STOCK ROM to ODIN... ANYONE?
beejmeister said:
OK. I wasn't too chicken... and should have been! HELP!!!!!
I attempted the ODIN flash with the proper CF that states that it is for the Sprint Edge... and now have a soft (I hope) bricked phone. The message I have on the screen right now is:
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Like I said.... HELP!!!!!
I'm not familiar with KIES but I guess I'll get that way....
Update: I am able to get into download mode... now now if I could just get my hands on a STOCK ROM to ODIN... ANYONE?
Click to expand...
Click to collapse
Nope. That's what we all tried and it failed for us too. We're trying to figure out a fix or alternative to this. Anyways, to fix your device, take the .tar.md5 file found inside the CF auto root directory and open it with an archiver like 7zip. Extract the recovery.img to somewhere and run this tool on it. Then open up the odin included in CF auto root and choose the recovery.tar.md5 you created rather than the usual file. Flash in download mode and you're good to go.
jooniloh said:
Nope. That's what we all tried and it failed for us too. We're trying to figure out a fix or alternative to this. Anyways, to fix your device, take the .tar.md5 file found inside the CF auto root directory and open it with an archiver like 7zip. Extract the recovery.img to somewhere and run this tool on it. Then open up the odin included in CF auto root and choose the recovery.tar.md5 you created rather than the usual file. Flash in download mode and you're good to go.
Click to expand...
Click to collapse
If there is one thing I've learned in my many years on XDA... DON'T PANIC! Someone will help you. I didn't panic... You helped me hugely. Figured I'd go home and reactivate my Note 3... but didn't even have to do that. THANKS jooniloh! Many thanks...
beejmeister said:
If there is one thing I've learned in my many years on XDA... DON'T PANIC! Someone will help you. I didn't panic... You helped me hugely. Figured I'd go home and reactivate my Note 3... but didn't even have to do that. THANKS jooniloh! Many thanks...
Click to expand...
Click to collapse
No problem. Glad I could help. Now let's just hope for a stable root method soon! Out of curiosity, are you also on NK1? I wonder if anyone who didn't upgrade was able to get root successfully . . .
beejmeister said:
OK. I wasn't too chicken... and should have been! HELP!!!!!
I attempted the ODIN flash with the proper CF that states that it is for the Sprint Edge... and now have a soft (I hope) bricked phone. The message I have on the screen right now is:
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Like I said.... HELP!!!!!
I'm not familiar with KIES but I guess I'll get that way....
Update: I am able to get into download mode... now now if I could just get my hands on a STOCK ROM to ODIN... ANYONE?
Click to expand...
Click to collapse
Man, this is happening fast... I just got it done successfuly rooting my Sprint Edge. Don't freak, follow the instructions on this thread which works on Tmobile devices. I didn't install the SD card fix file yet, but may if I need it. You are basically starting at the FAIL point of that thread. Although you need the SU file on your phone, which you may be able to get it by putting it on a Microsd and accessing it from recovery that way. Good Luck, and don't panic, lol.
EDIT: See my post here : http://forum.xda-developers.com/note-edge/general/info-galaxy-note-edge-sm-n915-t2945942 for more details on what worked for me
jooniloh said:
No problem. Glad I could help. Now let's just hope for a stable root method soon! Out of curiosity, are you also on NK1? I wonder if anyone who didn't upgrade was able to get root successfully . . .
Click to expand...
Click to collapse
Yup! On NK1. Did the update yesterday when I first got the phone. Guess we're seeing a pattern here!
---------- Post added at 06:16 PM ---------- Previous post was at 06:15 PM ----------
Next1776 said:
Man, this is happening fast... I just got it done successfuly rooting my Sprint Edge. Don't freak, follow the instructions on this thread which works on Tmobile devices. I didn't install the SD card fix file yet, but may if I need it. You are basically starting at the FAIL point of that thread. Although you need the SU file on your phone, which you may be able to get it by putting it on a Microsd and accessing it from recovery that way. Good Luck, and don't panic, lol.
Click to expand...
Click to collapse
OK. Now I'll ask THE question: Next1776, are YOU on NK1?
Next1776 said:
Man, this is happening fast... I just got it done successfuly rooting my Sprint Edge. Don't freak, follow the instructions on this thread which works on Tmobile devices. I didn't install the SD card fix file yet, but may if I need it. You are basically starting at the FAIL point of that thread. Although you need the SU file on your phone, which you may be able to get it by putting it on a Microsd and accessing it from recovery that way. Good Luck, and don't panic, lol.
Click to expand...
Click to collapse
Can you tell me exactly what you did step by step? Also are you on the latest sprint firmware?
And what version of TWRP did you use?
beejmeister said:
Yup! On NK1. Did the update yesterday when I first got the phone. Guess we're seeing a pattern here!
---------- Post added at 06:16 PM ---------- Previous post was at 06:15 PM ----------
OK. Now I'll ask THE question: Next1776, are YOU on NK1?
Click to expand...
Click to collapse
NK1
---------- Post added at 06:12 PM ---------- Previous post was at 05:47 PM ----------
jooniloh said:
Can you tell me exactly what you did step by step? Also are you on the latest sprint firmware?
And what version of TWRP did you use?
Click to expand...
Click to collapse
I actually downloaded the Chainfire file yesterday for the SM N915P, but was still too chicken to try it. After I saw this thread today, I decided to go for it. All I basically did was follow the instructions in TEKHD 's thread for the SM915T.
-Dowloaded Chainfire's Sprint AutoRoot file, Unzipped it.
-Put phone in download mode, selcted the Chainfire's Sprint AutoRoot tar file and hit Start.
-ODIN flashed "FAIL".
-I then flashed a 2.8.0.0 TWRP file for the Note 4, which ODIN said was successful, but it would not boot into recovery (so don't do that).
-I flashed the 2.8.1.1 Tmobile TWRP file from TEKHD's thread, ODIN said success.
-Booted into recovery, adjusted settings for brightness in TWRP, (TWRP was acting really flaky, but I pressed on) I couldn't find the UPDATE-SuperSU-v2.16.zip file in recovery, (I put the file on my removable SD card) so I rebooted recovery, and this time was able to find the UPDATE-SuperSU-v2.16.zip, and flashed it.
-Wiped cache/ Dalvik Cache. Hit Reboot-> System, TWRP said it didn't appear to have root, do I want to root? Hit yes, go , whatever, it rebooted, let settle for a few minutes, and ROOT was born!
Hope that helps and I didn't miss something, but thats how it went down for me.
To sum it up, Follow TEKHD's Tmobile thread, with the exception of the Tmobile Chainfire file, (use the Sprint one obviously) I also did not flash the SD card fix from that thread.
Let me know if you have questions, but I will have to bug out for a while here until this evening...
Good Luck everyone!
Next1776 said:
NK1
---------- Post added at 06:12 PM ---------- Previous post was at 05:47 PM ----------
I actually downloaded the Chainfire file yesterday for the SM N915P, but was still too chicken to try it. After I saw this thread today, I decided to go for it. All I basically did was follow the instructions in TEKHD 's thread for the SM915T.
-Dowloaded Chainfire's Sprint AutoRoot file, Unzipped it.
-Put phone in download mode, selcted the Chainfire's Sprint AutoRoot tar file and hit Start.
-ODIN flashed "FAIL".
-I then flashed a 2.8.0.0 TWRP file for the Note 4, which ODIN said was successful, but it would not boot into recovery (so don't do that).
-I flashed the 2.8.1.1 Tmobile TWRP file from TEKHD's thread, ODIN said success.
-Booted into recovery, adjusted settings for brightness in TWRP, (TWRP was acting really flaky, but I pressed on) I couldn't find the UPDATE-SuperSU-v2.16.zip file in recovery, (I put the file on my removable SD card) so I rebooted recovery, and this time was able to find the UPDATE-SuperSU-v2.16.zip, and flashed it.
-Wiped cache/ Dalvik Cache. Hit Reboot-> System, TWRP said it didn't appear to have root, do I want to root? Hit yes, go , whatever, it rebooted, let settle for a few minutes, and ROOT was born!
Hope that helps and I didn't miss something, but thats how it went down for me.
To sum it up, Follow TEKHD's Tmobile thread, with the exception of the Tmobile Chainfire file, (use the Sprint one obviously) I also did not flash the SD card fix from that thread.
Let me know if you have questions, but I will have to bug out for a while here until this evening...
Good Luck everyone!
Click to expand...
Click to collapse
No need to flash the SD card fix. there's apps on the play store that will patch the necessary files for that (and you can delete the app afterwards). Interesting that the TMO twrp worked . . . Someone should try that with the SPRINT twrp 2.8.1.1 found here.
Edit: I tried repeatedly to flash both 2.8.1.1 and 2.8.1.0 versions of the SPRINT NOTE 4 twrp and odin consistently crashed on "File analysis".
Edit: I took the plunge and went with the tmobile method. Nothing went wrong. Everything seems to be working fine. The TMO Note 4 recovery is annoying though (two strips of white on both sides of the screen). I didn't have any issues with how it ran like Next1776 did though.
Edit: I'm experiencing some odd issues. The primary one is that anything I install through xposed or f-droid takes FOREVER to install. Anyone else getting this?
jooniloh said:
No need to flash the SD card fix. there's apps on the play store that will patch the necessary files for that (and you can delete the app afterwards). Interesting that the TMO twrp worked . . . Someone should try that with the SPRINT twrp 2.8.1.1 found here.
Edit: I tried repeatedly to flash both 2.8.1.1 and 2.8.1.0 versions of the SPRINT NOTE 4 twrp and odin consistently crashed on "File analysis".
Edit: I took the plunge and went with the tmobile method. Nothing went wrong. Everything seems to be working fine. The TMO Note 4 recovery is annoying though (two strips of white on both sides of the screen). I didn't have any issues with how it ran like Next1776 did though.
Edit: I'm experiencing some odd issues. The primary one is that anything I install through xposed or f-droid takes FOREVER to install. Anyone else getting this?
Click to expand...
Click to collapse
BUt just to confirm, jooniloh.... you do have confirmable root? Guess my clue should be that you are using xposed.... but just wanted to confirm before I went down the rabbit hole....
jooniloh said:
No need to flash the SD card fix. there's apps on the play store that will patch the necessary files for that (and you can delete the app afterwards). Interesting that the TMO twrp worked . . . Someone should try that with the SPRINT twrp 2.8.1.1 found here.
Edit: I tried repeatedly to flash both 2.8.1.1 and 2.8.1.0 versions of the SPRINT NOTE 4 twrp and odin consistently crashed on "File analysis".
Edit: I took the plunge and went with the tmobile method. Nothing went wrong. Everything seems to be working fine. The TMO Note 4 recovery is annoying though (two strips of white on both sides of the screen). I didn't have any issues with how it ran like Next1776 did though.
Edit: I'm experiencing some odd issues. The primary one is that anything I install through xposed or f-droid takes FOREVER to install. Anyone else getting this?
Click to expand...
Click to collapse
Awesome. Glad you are able to join the party!
I'm not having any issues right now. I have installed Xposed and Wanam without any issues so far. I did disable Knox and Secure storage with Wanam (under security hacks) as another poster suggested. Maybe also try wiping Cache and dalvik in recovery ? Hopefully we will have a stable custom recovery available soon. I say stable, but I guess this one is "stable" - its just not real pretty...
ON: Galaxy S3 4.4.2 Verizon(d2vzw) -->OK, I know you all may think I didn't read the other debrick threads, your wrong. I made this new thread because i HAVE tried endlessy every method of debrick on this forum and the internet, and no success. I was messing around with safestrap and decided to try and flash a rom called flashingdroid: for some reason. So i did as usual, boot into recovery(safestrap 3.75) and wipe current os and flash the new one. So i wiped my stock rom(after making a backup) and installed/flashed the new one(flashingdroid) and after seemingly a successful flash, i pressed reboot. Then it went downhill. One second after i pressed reboot, the screen flashed quickly, then shutoff, for good. I couldn't boot it or get into recovery or odin or ANYTHING. I tried the microsd method of debricking with minimal success. It will only give me one vibration, then black scree with that method. Nothing else has worked. I know this was a noob mistake somehow, but does anyone know any special tricks or something? Will a good jig maybe work? I have doubt verizon or samsung will accept it back(it was well rooted!). Please anything/anybody help! I really don't want to buy a new phone or jtag it. Thanks!:crying:
You may have read the debrick threads, but what you should have done from the beginning was read and pay attention to which forum you were in. You flashed a ROM for the International version of the S3 onto your Verizon S3. You almost certainly turned your phone into a shiny paper weight. JTAG may be your only hope. If you don't have one, check out mobiletechvideos.com. I'm not familiar enough with safestrap to know if that may have actually saved you since it is not a traditional recovery and I don't know if it touches all the partitions. In the future, research, research, and research, and pay very close attention to exactly what you are flashing onto your phone. For the Verizon S3, you should only flash ROMs from this sub-forum. And when using safestrap, you are restricted to only flashing ROMs with the same build number as what your phone is currently on in a stock condition.
Ok...Thanks
landshark68 said:
You may have read the debrick threads, but what you should have done from the beginning was read and pay attention to which forum you were in. You flashed a ROM for the International version of the S3 onto your Verizon S3. You almost certainly turned your phone into a shiny paper weight. JTAG may be your only hope. If you don't have one, check out mobiletechvideos.com. I'm not familiar enough with safestrap to know if that may have actually saved you since it is not a traditional recovery and I don't know if it touches all the partitions. In the future, research, research, and research, and pay very close attention to exactly what you are flashing onto your phone. For the Verizon S3, you should only flash ROMs from this sub-forum. And when using safestrap, you are restricted to only flashing ROMs with the same build number as what your phone is currently on in a stock condition.
Click to expand...
Click to collapse
Im kinda tired of my so confined locked bootloader and phone model anyways. Im going to purchase a $20 JTAG service off ebay, hope that works.
Root Wizard said:
Im kinda tired of my so confined locked bootloader and phone model anyways. Im going to purchase a $20 JTAG service off ebay, hope that works.
Click to expand...
Click to collapse
I'd be very careful with eBay, they tend to be junk. I've been an eBay member over 10 years and ran into a lot of it
Sent from my Nexus 5
Try MicroSD 16GB (2GB not work)
Confused About What's Possible for Modding a Stock Verizon S3
Can someone please steer me in the right direction? I have a Verizon Galaxy S3 running 4.4.2 stock. I recently rooted my phone, but I realize I am very limited as to any mods I can make due to the locked bootloader. Am I able to modify my OS in some way at all (Safestrap) to make my phone run better, or am I just too late in going about this? I've read so much on this subject, but the more I read, it seems the more confused I get. I want to be careful not to brick my phone and would love to see some precise directions on what I could do. Thanks a million for any help at all!
straykat said:
Can someone please steer me in the right direction? I have a Verizon Galaxy S3 running 4.4.2 stock. I recently rooted my phone, but I realize I am very limited as to any mods I can make due to the locked bootloader. Am I able to modify my OS in some way at all (Safestrap) to make my phone run better, or am I just too late in going about this? I've read so much on this subject, but the more I read, it seems the more confused I get. I want to be careful not to brick my phone and would love to see some precise directions on what I could do. Thanks a million for any help at all!
Click to expand...
Click to collapse
You should be able to install xposed but as far as mods your very limited to what you can do with it
Sent from my Nexus 5
ShapesBlue said:
You should be able to install xposed but as far as mods your very limited to what you can do with it
Sent from my Nexus 5
Click to expand...
Click to collapse
Hey, thanks a lot for that! As much as I've read, I've never heard of xposed. I'll research it and see what it takes and what it will do for my phone. If it helps at all, which I'm sure it will, that would be great. Thanks again for your reply!
straykat said:
Hey, thanks a lot for that! As much as I've read, I've never heard of xposed. I'll research it and see what it takes and what it will do for my phone. If it helps at all, which I'm sure it will, that would be great. Thanks again for your reply!
Click to expand...
Click to collapse
Your very welcome. That's what xda is all about. Helping others
Sent from my Nexus 5
XDA Forum - the best place for learning...
ShapesBlue said:
Your very welcome. That's what xda is all about. Helping others
Sent from my Nexus 5
Click to expand...
Click to collapse
ShapesBlue-
It's hard to compare this forum with the others. I believe the people here are the most knowledgeable and, like you, very helpful. Funny enough, or not, I posed a related question on another site (initials AC), and it took over 150 views and a week later before anybody offered a reply. Anyway, I can see there is lots of information on this forum about xposed, so now I'll go and learn as much as I can about it. Thanks again for your help!
Btw, here's a link for others like me who are clueless about xposed: http://forum.xda-developers.com/showthread.php?t=2299428
straykat said:
ShapesBlue-
It's hard to compare this forum with the others. I believe the people here are the most knowledgeable and, like you, very helpful. Funny enough, or not, I posed a related question on another site (initials AC), and it took over 150 views and a week later before anybody offered a reply. Anyway, I can see there is lots of information on this forum about xposed, so now I'll go and learn as much as I can about it. Thanks again for your help!
Btw, here's a link for others like me who are clueless about xposed: http://forum.xda-developers.com/showthread.php?t=2299428
Click to expand...
Click to collapse
I've been around the web going on nearly 20 years and I'd have to agree some are more helpful than others. I find xda to be a great resource for anything android or windows phone related. And yes I agree some are a lot more helpful than others. The guys and gals still lurking around the VZW S3 forums have been here since the beginning for this phone and even though mine is no longer active I still use it daily, mostly for games but will probably never give it up. It was my first true (I'm comparing it to the HTC thunderbolt) android phone
Sent from my Nexus 5
Can't Believe What I - did! - - - Need Help Rebooting Phone
ShapesBlue said:
I've been around the web going on nearly 20 years and I'd have to agree some are more helpful than others. I find xda to be a great resource for anything android or windows phone related. And yes I agree some are a lot more helpful than others. The guys and gals still lurking around the VZW S3 forums have been here since the beginning for this phone and even though mine is no longer active I still use it daily, mostly for games but will probably never give it up. It was my first true (I'm comparing it to the HTC thunderbolt) android phone
Sent from my Nexus 5
Click to expand...
Click to collapse
ShapesBlue-
I seem to have gotten into big trouble - I hope there's a solution. I learned all about Xposed and installed it along with about a dozen modules. Everything was working great, except the torch/flashlight... [I wanted that! ] so, I saw a download for a module on this forum to fix the flashlight... http://forum.xda-developers.com/xposed/modules/xposed-flashlight-fixer-fix-devices-t2867267 . Well, since doing that, I think I realized that I should have left the flashlight alone! When I tried to reboot after adding the module to xposed, I ended up in what i believe is a boot loop. The Samsung screen comes on, and then it gets stuck on the red Verizon screen. I never dreamed that a module installation could cause this; and I guess I figured if it ever happened I could get into recovery mode and restore everthing. Btw, I had done a complete backup of my phone using Titanium on my sd card.
So, here's what I can/can't do now. I can push "down-volume-button" + home + power to get to screen where you can download a cusom OS - then pushing volume-up-button goes to screen that says "Downloading...Do not turn off target!! (Nothing seems to happen from here.) - - - I cannot enter recovery mode by pressing "volume-up" + home + power keys. When I do that I get the big yellow triangle with message - System software not authorized...go to nearest Verizon store. hmmmm.... So, am I hard bricked or soft bricked? Do I have a way out? Thanks very much for any help with this!
straykat said:
ShapesBlue-
I seem to have gotten into big trouble - I hope there's a solution. I learned all about Xposed and installed it along with about a dozen modules. Everything was working great, except the torch/flashlight... [I wanted that! ] so, I saw a download for a module on this forum to fix the flashlight... http://forum.xda-developers.com/xposed/modules/xposed-flashlight-fixer-fix-devices-t2867267 . Well, since doing that, I think I realized that I should have left the flashlight alone! When I tried to reboot after adding the module to xposed, I ended up in what i believe is a boot loop. The Samsung screen comes on, and then it gets stuck on the red Verizon screen. I never dreamed that a module installation could cause this; and I guess I figured if it ever happened I could get into recovery mode and restore everthing. Btw, I had done a complete backup of my phone using Titanium on my sd card.
So, here's what I can/can't do now. I can push "down-volume-button" + home + power to get to screen where you can download a cusom OS - then pushing volume-up-button goes to screen that says "Downloading...Do not turn off target!! (Nothing seems to happen from here.) - - - I cannot enter recovery mode by pressing "volume-up" + home + power keys. When I do that I get the big yellow triangle with message - System software not authorized...go to nearest Verizon store. hmmmm.... So, am I hard bricked or soft bricked? Do I have a way out? Thanks very much for any help with this!
Click to expand...
Click to collapse
No problem. Your soft bricked and it seems your on the latest firmware, correct me if I'm wrong
4.4.2 NE1? If so you can use Odin to flash back to stock 4.4.2 and you should be ok
Sent from my Nexus 5
ShapesBlue said:
No problem. Your soft bricked and it seems your on the latest firmware, correct me if I'm wrong
4.4.2 NE1? If so you can use Odin to flash back to stock 4.4.2 and you should be ok
Sent from my Nexus 5
Click to expand...
Click to collapse
ShapesBlue-
That's great news!!! Thanks!
I believe my phone was on 4.4.3. A file I used in my rooting process using Towelroot was I535VRUDNE1_I535VZWDNE1_VZW; I used Odin before for the root procedure, so the program of course is on my PC. Is there a thread around with instructions how to flash back to the stock firmware? Thanks again a million for getting back to me!
straykat said:
ShapesBlue-
That's great news!!! Thanks!
I believe my phone was on 4.4.3. A file I used in my rooting process using Towelroot was I535VRUDNE1_I535VZWDNE1_VZW; I used Odin before for the root procedure, so the program of course is on my PC. Is there a thread around with instructions how to flash back to the stock firmware? Thanks again a million for getting back to me!
Click to expand...
Click to collapse
But of course. Check this out which should get you what you need
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my Nexus 5
Try kies
straykat said:
ShapesBlue-
That's great news!!! Thanks!
I believe my phone was on 4.4.3. A file I used in my rooting process using Towelroot was I535VRUDNE1_I535VZWDNE1_VZW; I used Odin before for the root procedure, so the program of course is on my PC. Is there a thread around with instructions how to flash back to the stock firmware? Thanks again a million for getting back to me!
Click to expand...
Click to collapse
Instead of odin, you could try using samasung kies 3 and use its emergencey firmware recovery tool which dl's and intalls the correct, latest firmware on your device.
What you do:
Install kies 3 on your computer.
Boot to odin mode on your phone.
Click on tools in kies.
Select emergency firmware recovery option.
Follow on screen directions.
Hope I helped!
ShapesBlue said:
But of course. Check this out which should get you what you need
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my Nexus 5
Click to expand...
Click to collapse
Shapes Blue & Root Wizard,
Thanks much for your replies. Is it possible for me, having had 4.4.3 on phone, to go to 4.3 instead of 4.4.2? Seems some people think that's an advantage, but I'm not sure. If I did do that, could I still run xposed?
Btw, RW, I tried using your idea, but when I was attempting to do the emergency Firmware Recovery, it asked for a computer code...??? So, that method doesn't seem to be a good route for me, but thanks for the tip!
You guys don't know how happy I am to have you come to the rescue! I've been using an old iPhone 4 for calls, etc.... during the day which I don't like at all! I'll be real glad to get back to AndroidLand. Thanks again!!!
straykat said:
Shapes Blue & Root Wizard,
Thanks much for your replies. Is it possible for me, having had 4.4.3 on phone, to go to 4.3 instead of 4.4.2? Seems some people think that's an advantage, but I'm not sure. If I did do that, could I still run xposed?
Btw, RW, I tried using your idea, but when I was attempting to do the emergency Firmware Recovery, it asked for a computer code...??? So, that method doesn't seem to be a good route for me, but thanks for the tip!
You guys don't know how happy I am to have you come to the rescue! I've been using an old iPhone 4 for calls, etc.... during the day which I don't like at all! I'll be real glad to get back to AndroidLand. Thanks again!!!
Click to expand...
Click to collapse
I'm 100% sure the last update on the VZW S3 was 4.4.2 NE1. As long as you can root the phone you should be able to run xposed without an issue
And no you cannot downgrade to anything other than what your currently on
Sent from my Nexus 5
---------- Post added at 06:51 PM ---------- Previous post was at 06:50 PM ----------
Root Wizard said:
Instead of odin, you could try using samasung kies 3 and use its emergencey firmware recovery tool which dl's and intalls the correct, latest firmware on your device.
What you do:
Install kies 3 on your computer.
Boot to odin mode on your phone.
Click on tools in kies.
Select emergency firmware recovery option.
Follow on screen directions.
Hope I helped!
Click to expand...
Click to collapse
Kies won't always work as it should
Sent from my Nexus 5
Still Not Up & Running...
ShapesBlue-
Believe-it-or-not, I still haven't been able to get my s3 back up & running. When I open Odin3 v 3.09 and try to flash the firmware 1534VRUDNE1 . . . . .tar.md5 , it doesn't successfully load to the s3. I've attached a screenshot showing the Odin screen. It show "All threads completed. (succeed 0 failed 1) - btw, when I click on the firmware file within Odin, nothing appears in the box to the right of the AP field; is that correct?
Thanks for any guidance you can provide.
straykat said:
ShapesBlue-
Believe-it-or-not, I still haven't been able to get my s3 back up & running. When I open Odin3 v 3.09 and try to flash the firmware 1534VRUDNE1 . . . . .tar.md5 , it doesn't successfully load to the s3. I've attached a screenshot showing the Odin screen. It show "All threads completed. (succeed 0 failed 1) - btw, when I click on the firmware file within Odin, nothing appears in the box to the right of the AP field; is that correct?
Thanks for any guidance you can provide.
Click to expand...
Click to collapse
I can't open it. It's in the newest word format docx. I personally haven't had to do this myself and it's been awhile since I've used Odin. Damn MS having to have all files in there own format
Edit: trying to download docs by Google and seeing if it opens
Sent from my Nexus 5
---------- Post added at 08:48 PM ---------- Previous post was at 08:40 PM ----------
straykat said:
ShapesBlue-
Believe-it-or-not, I still haven't been able to get my s3 back up & running. When I open Odin3 v 3.09 and try to flash the firmware 1534VRUDNE1 . . . . .tar.md5 , it doesn't successfully load to the s3. I've attached a screenshot showing the Odin screen. It show "All threads completed. (succeed 0 failed 1) - btw, when I click on the firmware file within Odin, nothing appears in the box to the right of the AP field; is that correct?
Thanks for any guidance you can provide.
Click to expand...
Click to collapse
Can you get into recovery?
I was able to open it once I downloaded docs by google. It's been so long since I used it though. I can't recall off hand how to use it to be honest
Sent from my Nexus 5
Hi,
So I was trying to root my phone and it all went wrong. I have rooted tons of phones before, but never a Samsung (never again).
The phone will show the Samsung Boot screen, but then it either goes black, with a flashing blue LED, or it boots itself into recovery.
When I use ODIN, the flash fails at "system.img.ext4" whenever I use just the AP field. If I load all the fields in, it fails at "xbl.elf"
I got the firmware file from SamMobile, so I don't think that is the issue, but who knows. It's as if the phone no longer has an OS on it. I also tried using SmartSwitch as well, but I have no idea what the S/N on this phone is. It was originally a Sprint phone and was working fine, but I could never find the S/N. It is nowhere on the phone itself, and was not listed when I typed #*06#. All I have is the IMEI.
Finally, when it is in recovery, there is a message at the bottom that reads, "dm-verity verification failed".
Sorry for the bullet point style here, I am on mobile. If anyone can assist, I would be very grateful!
ebercon said:
Hi,
So I was trying to root my phone and it all went wrong. I have rooted tons of phones before, but never a Samsung (never again).
The phone will show the Samsung Boot screen, but then it either goes black, with a flashing blue LED, or it boots itself into recovery.
When I use ODIN, the flash fails at "system.img.ext4" whenever I use just the AP field. If I load all the fields in, it fails at "xbl.elf"
I got the firmware file from SamMobile, so I don't think that is the issue, but who knows. It's as if the phone no longer has an OS on it. I also tried using SmartSwitch as well, but I have no idea what the S/N on this phone is. It was originally a Sprint phone and was working fine, but I could never find the S/N. It is nowhere on the phone itself, and was not listed when I typed #*06#. All I have is the IMEI.
Finally, when it is in recovery, there is a message at the bottom that reads, "dm-verity verification failed".
Sorry for the bullet point style here, I am on mobile. If anyone can assist, I would be very grateful!
Click to expand...
Click to collapse
I'm new to the s7. long time lg man
on lg ussally means either ure trying to flash a non signed image or downgrade a qfused bootloader anti rollback which sprint is good for.
in dl mode after fail its not showing anything about binary and stuff in red is it
TheMadScientist420 said:
I'm new to the s7. long time lg man
on lg ussally means either ure trying to flash a non signed image or downgrade a qfused bootloader anti rollback which sprint is good for.
in dl mode after fail its not showing anything about binary and stuff in red is it
Click to expand...
Click to collapse
It does say something about binary in there. Binary 3 I believe. I'll have to try again to get the error.
ebercon said:
It does say something about binary in there. Binary 3 I believe. I'll have to try again to get the error.
Click to expand...
Click to collapse
sounds the firmware u are flashing is older than what you have on the device hence the fail
try to find newer firmware and try flashing it
download
Download official nougat from sam mobile then flash with Odin. It will definitely solve your problem
amol6630 said:
Download official nougat from sam mobile then flash with Odin. It will definitely solve your problem
Click to expand...
Click to collapse
I may try this as well. I flashed the newest firmware I could find other than Nougat and I now have it booting all the way up and then after about a minute, it loops again. It is at least further along than before.
I just remembered one detail: The original issue began when I flashed a modified boot.img to the phone during a rooting attempt. Could this be what is still causing the issue and preventing a reformatting of the phone from solving the issue? So lost with this thing...
Try with latest firmware + pit file + tick re-partition
ebercon said:
I may try this as well. I flashed the newest firmware I could find other than Nougat and I now have it booting all the way up and then after about a minute, it loops again. It is at least further along than before.
I just remembered one detail: The original issue began when I flashed a modified boot.img to the phone during a rooting attempt. Could this be what is still causing the issue and preventing a reformatting of the phone from solving the issue? So lost with this thing...
Click to expand...
Click to collapse
Sorry to revive this thread but did this work cause its currently happening to me
If your phone is an original, S/N may be engraved in the back... it's a little bit hard to note but put a spotlight near it so that you can identify it better.
hhh ^^
Ok, got my new S8+ today. I have not had a Samsung device for quite a few years, but do remember how to use Odin. I downloaded TWRP, Odin 3.1.2 and put the phone in download mode. Got the pass in Odin and rebooted and got to TWRP without issue. Now came my dumbass move. On the opening screen, I did not press keep read only. I was then going to flash a ROM to customize the phone. When I rebooted, it took a dump. I can get as far as the Samsung screen and then it says something about not being able to verify with the box at the bottom that does a factory reset. I pressed that and it booted to TWRP with several lines of errors of trying to mount data. There is 0 data on the phone now. And now, when I am in TWRP, my pc only recognizes the phone as a twrp decive - no phone files or anything else. I am going to try to put Omega on the phone and see if it will rebuild it for me.
Anybody got anything to offer? I am such a dumbass!!!
Is there any place that I can get Odin tar file of a factory image? I have searched on google and in here and do not see any place to download it.
I still have my Nexus 6P, so am not down without a phone.
http://updato.com/firmware-archive-select-model?q=g955f has all the firmware you need, find the region of your phone and download.
peachpuff said:
http://updato.com/firmware-archive-select-model?q=g955f has all the firmware you need, find the region of your phone and download.
Click to expand...
Click to collapse
Thanks so much for this link. I am downloading a UK version as it will be in English. I am in the US and did not see anything better to download. Again, many thanks for the help.
wilbarger said:
Thanks so much for this link. I am downloading a UK version as it will be in English. I am in the US and did not see anything better to download. Again, many thanks for the help.
Click to expand...
Click to collapse
Isn't UK Exynos? Are you on an Exynos S8+? Also requested a mod move for the thread to the S8+ forum.
The Root said:
Isn't UK Exynos? Are you on an Exynos S8+?
Click to expand...
Click to collapse
Yes and Yes. I am still puzzled at TWRP wiping my files from the phone. I will wait a few days before adding it again. I have read a lot on the Samsung way of doing things as it has been so long since I had one. I am used to ADB/Fastboot methods of flashing. Oh well, live and learn.
Mod just moved it here from s8+