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?
Hello XDA developers!
I hope you can help me with a serieus problem on my Nexus5 Device!
Let's tell you my little adventure with my Nexus5 :
First my Nexus5 Device worked perfectly, but then the radiobaseband and the sensors magically dissapeared!
https://db.tt/cdZiSukZ i've tooked some screenshots of it on dropbox.
Then I Flashed the factory image for my device by following this guide: http://forum.xda-developers.com/showthread.php?t=2513701
And it started to work perfectly, till now........
after about a week i watched a unspecified video on Google Chrome and the screen freezed ( not literally )
So I hold the power button and turn it off, turn it back on and i got a infinity bootloop.
So I flash again the official factory image and it can't flash my system?
its look like this;
trying to flash system.img....
FAILED
the rest of the process flash succesfull until it reach system.img
and a friend of mine therinsem tried to add a custom recovery and it didn't work, so we flashed again the factory image and it still FAILED,
to flash system.img the rest of the process work until it reach system.img.
now it doesn't even boot? it's only going straight into fastboot-mode
and if i press in fastboot-mode recoverymode than it shows nothing? ( i think because we tried to flash a custom recovery )
- iv'e tried on a bunch of diffrent windows laptop's
- i can't access the internal storage of the device
- i can still '' side-load'' I think
so this is my problem with the nexus5, does anyone have a solution?:crying:
Download the factory image again and make sure the md5 checks. Then try again
There's another thread around here somewhere with pretty much the same issue. Sounds like bad memory. From fastboot try:
Code:
fasboot format system
If that succeeds reflash the factory image. If that fails your most likely looking at RMA.
I wouldn't really since google will charge you twice for tampering with the imei
Sent from my Nexus 5
dicecuber said:
I wouldn't really since google will charge you twice for tampering with the imei
Sent from my Nexus 5
Click to expand...
Click to collapse
What? Who's taking about imei?
jd1639 said:
Download the factory image again and make sure the md5 checks. Then try again
Click to expand...
Click to collapse
Thank you for a answer! i will try it and will give a update status soon.
jd1639 said:
What? Who's taking about imei?
Click to expand...
Click to collapse
Judging from pictures, the stock imei is unknown. I'd refrain from rmaing it just yet
Sent from my Nexus 5
dicecuber said:
Judging from pictures, the stock imei is unknown. I'd refrain from rmaing it just yet
Sent from my Nexus 5
Click to expand...
Click to collapse
Sometimes it happens that you lose your imei. Flashing the factor image can bring it back. Nothing nefarious going on
dicecuber said:
Judging from pictures, the stock imei is unknown. I'd refrain from rmaing it just yet
Click to expand...
Click to collapse
Ummmmm? That's why where trying to help the OP recover. lol OP you can also run this and see what the output is:
Code:
fasboot getvar all
^someone suggested Op rma it. I suggested he refrain from doing that
Sent from my Nexus 5
theesotericone said:
Ummmmm? That's why where trying to help the OP recover. lol OP you can also run this and see what the output is:
Code:
fasboot getvar all
Click to expand...
Click to collapse
theesotericone said:
There's another thread around here somewhere with pretty much the same issue. Sounds like bad memory. From fastboot try:
Code:
fasboot format system
If that succeeds reflash the factory image. If that fails your most likely looking at RMA.
Click to expand...
Click to collapse
Thank you very much for the answers! i will setup my laptop again and will use your advice, to recover my device! ( that rhymes! )
Tomorrow i will give a update, i am going to sleep! good night folk!
tomaszcs said:
Thank you very much for the answers! i will setup my laptop again and will use your advice, to recover my device! ( that rhymes! )
Tomorrow i will give a update, i am going to sleep! good night folk!
Click to expand...
Click to collapse
Formatting system did not work.
I helped Tomasz doing this
I used Sunshine, got root and S-Off, flashed a wireless tether zip. Right after, 4G speeds plummeted and no websites would load. Saw the closest to going back was to RUU, couldn't get it to open the file (even in the SDK folder after I downloaded and installed all files). Finally flashed another ROM and wiped everything from my phone.
Still 99% of webpages won't load on 4G. If they do, it takes forever. Not sure if it's anything I did, but just wanted to ask before it turns out to be some huge coincidence with Verizon. Thanks for any help.
Yazzinit said:
I used Sunshine, got root and S-Off, flashed a wireless tether zip.
Click to expand...
Click to collapse
Which one?
Right after, 4G speeds plummeted and no websites would load.
Click to expand...
Click to collapse
Pretty good indicator for what's wrong?
Saw the closest to going back was to RUU, couldn't get it to open the file (even in the SDK folder after I downloaded and installed all files).
Click to expand...
Click to collapse
You have fastboot drivers installed on your PC?
Finally flashed another ROM and wiped everything from my phone.
Click to expand...
Click to collapse
Which one?
Still 99% of webpages won't load on 4G. If they do, it takes forever. Not sure if it's anything I did, but just wanted to ask before it turns out to be some huge coincidence with Verizon. Thanks for any help.
Click to expand...
Click to collapse
Flash CleanROM. It's just like stock only better: debloated and tweaked, tethering enabled and more...
Thanks for the reply.
The wireless tether zip I flashed was: http://forum.xda-developers.com/showthread.php?t=2708548
The ROM I'm currently on is: http://forum.xda-developers.com/showthread.php?t=2716306
- Nothing wrong with it, just don't like the stock look and loading webpages is still not working.
I have fastboot drivers and adb as well as the SDK toolbox on my PC. I've been able to do most things following guides and posts here, but I can't RUU. When I flashboot flash zip 0P6BIMG.zip it gives error: cannot open 0P6BIMG.zip. I guess I could buy an external SD card and reader, but was hoping to fix this tonight/tomorrow.
Trying to download CleanROM for the 5th time tonight. The download stops around 300-400MB and there's no other mirrors for it. Currently at 700MB, maybe this download will go through (on PC). I'm really just trying to fix my webpage issue and go back to stock (or CleanROM is fine if it's similar). I'm willing to even donate a little to someone.
Yazzinit said:
Thanks for the reply.
The wireless tether zip I flashed was: http://forum.xda-developers.com/showthread.php?t=2708548
The ROM I'm currently on is: http://forum.xda-developers.com/showthread.php?t=2716306
- Nothing wrong with it, just don't like the stock look and loading webpages is still not working.
I have fastboot drivers and adb as well as the SDK toolbox on my PC. I've been able to do most things following guides and posts here, but I can't RUU. When I flashboot flash zip 0P6BIMG.zip it gives error: cannot open 0P6BIMG.zip. I guess I could buy an external SD card and reader, but was hoping to fix this tonight/tomorrow.
Trying to download CleanROM for the 5th time tonight. The download stops around 300-400MB and there's no other mirrors for it. Currently at 700MB, maybe this download will go through (on PC). I'm really just trying to fix my webpage issue and go back to stock (or CleanROM is fine if it's similar). I'm willing to even donate a little to someone.
Click to expand...
Click to collapse
Scott's site is not mobile friendly, but he just put up a DevHost mirror:
http://forum.xda-developers.com/showthread.php?p=55135177
The download actually finished, I even checked the MD5 of my download vs. on his site, matched. Wiped and flashed it, got dialer.apk stopped working, hit ok, popped up again, hit ok, phone bootlooped with 3 colored android lights on screen. Rebooted manually, same error, then something like phone.apk or android.google.something stopped working, hit ok, boot loop again. Pretty much have no clue at this point.
Yazzinit said:
The download actually finished, I even checked the MD5 of my download vs. on his site, matched. Wiped and flashed it, got dialer.apk stopped working, hit ok, popped up again, hit ok, phone bootlooped with 3 colored android lights on screen. Rebooted manually, same error, then something like phone.apk or android.google.something stopped working, hit ok, boot loop again. Pretty much have no clue at this point.
Click to expand...
Click to collapse
That sounds as if you dirty flashed CleanROM over the GPE.
Did you wipe cache, Dalvik and data before flashing CleanROM?
If not, do it and reflash the rom.
I may have messed it up, it was late last night. I have TWRP on it after following guides since I somehow lost the OS while trying to RUU different ways. Can anyone confirm everything I need to wipe so that I can flash CleanRom without wiping it from my internal storage? Don't have an external SD card and it won't sideload for some reason (I get error: cannot open romname.zip).
Edit: That worked. Except now it says CleanROM 1.3 in my settings lol and I swear I downloaded 1.4, since it was from the developer's site directly.
You do not need to flash a tether zip on that ROM or any other custom ROM
Sent from my HTC One VZW using Tapatalk 4
You're right. At the time I just wanted to add tethering and not change anything or flash any ROMs. Beyond that point now lol. CleanROM looks fine and is working well, it just says 1.3 in settings when I know I downloaded 1.4 from the OP's site last night.
Yazzinit said:
You're right. At the time I just wanted to add tethering and not change anything or flash any ROMs. Beyond that point now lol. CleanROM looks fine and is working well, it just says 1.3 in settings when I know I downloaded 1.4 from the OP's site last night.
Click to expand...
Click to collapse
It's a typo. ?
Scrosler provided a zip to change the version number. I believe it's in post 2
berndblb said:
It's a typo. ?
Scrosler provided a zip to change the version number. I believe it's in post 2
Click to expand...
Click to collapse
You are correct and thank you for the kind reply, unlike another in that topic who took the same amount of time to be rude for no reason. Thanks to all for their help, looking good now and working good, and extra features to boot.
So i have a STOCK HTC_M8Wl and a while back I tried to update it and this happened. The phone is no longer activated I've wiped data and cache from recovery mode I can also get into bootloader mode. When I attempt to power on the phone it shows the HTC boot screen for a min then turns off and back on to the same screen and after a minute or two it goes to a black screen then displays the phone with a red triangle and exclamation point in the middle then stays there.
I've looked all around the Internet and found this problem commonly with rooted devices but my problem is that mines is not rooted and is 100% stock. Is there a way to fix this problem from my position please let me know because I would love to make a thread on this problem because I only found one and they never explained how to fix it. (I belive it was the problem as mines) also I don't know much about HTC phones I have worked with rooting android before.
My solution:
Thanks to izzaeroth and the thread he provided me I was able to revive my phone. The ruu zip file kept failing saying signature verification failed do to large img file. So I decided to try the 6.0 ruu exe file instead. (My pc does have drivers to detect the phone while it's in fastboot mode) I launched the exe and it extracted the ruu I plug in my phone and started the process. It flashed all partitions it did take a while to load but after the update the phone booted it began to optimize 226 apps after that it booted and done it finally was fixed.
did u power it off while trying to update? you might be able to use one of dottats fuu/ruu files to try and bring it back to life
Sent from my m8wl using XDA-Developers mobile app
izzaeroth said:
did u power it off while trying to update? you might be able to use one of dottats fuu/ruu files to try and bring it back to life
Click to expand...
Click to collapse
Yes I belive it did turn off while updating that's what I was told. But how do I fix it with the dottat file? I have OTA update files part 1 and part 2 but I always get the status 7 error.
-spektor- said:
Yes I belive it did turn off while updating that's what I was told. But how do I fix it with the dottat file? I have OTA update files part 1 and part 2 but I always get the status 7 error.
Click to expand...
Click to collapse
you need to go here: http://forum.xda-developers.com/showthread.php?t=2883845
you will need the marshmallow 6.0 file, you might have to use the zip version, option 2. read instructions carefully etc etc
Sent from my m8wl using XDA-Developers mobile app
izzaeroth said:
you need to go here: http://forum.xda-developers.com/showthread.php?t=2883845
you will need the marshmallow 6.0 file, you might have to use the zip version, option 2. read instructions carefully etc etc
Click to expand...
Click to collapse
I've downloaded the 6.0 zip file but when using method 2 it said the file was to big n I downloaded the file again to make sure the file downloaded correctly n then it was a signature or a verification issue flashing it via HTC fastboot didn't seem to work either, I can't currently do much do to no Internet connection. So I cant keep re-downloading files to check.
-spektor- said:
I've downloaded the 6.0 zip file but when using method 2 it said the file was to big n I downloaded the file again to make sure the file downloaded correctly n then it was a signature or a verification issue flashing it via HTC fastboot didn't seem to work either, I can't currently do much do to no Internet connection. So I cant keep re-downloading files to check.
Click to expand...
Click to collapse
hmm, where did it say file was too big? not sure on doing it thru adb commands as ive always used the sd card or fuu
izzaeroth said:
hmm, where did it say file was too big? not sure on doing it thru adb commands as ive always used the sd card or fuu
Click to expand...
Click to collapse
It said it in fastboot when ever it detected the file n I think it said the same when i tried it with adb/fastboot on windows pc
izzaeroth said:
hmm, where did it say file was too big? not sure on doing it thru adb commands as ive always used the sd card or fuu
Click to expand...
Click to collapse
The 6.0 run exe worked it took a while to update but it worked and finally got past the same screen and it started to optimize apps that took a good 30 min ill update this thread when I get wifi again thanks for your help
-spektor- said:
The 6.0 run exe worked it took a while to update but it worked and finally got past the same screen and it started to optimize apps that took a good 30 min ill update this thread when I get wifi again thanks for your help
Click to expand...
Click to collapse
awesome! glad u got it working
This is official Nougat firmware use this to update or just want to update
CP_N920VVRU3CQB9_N920VVZW3CQB9_CL10809541_QB12868949_REV00_user_low_ship.tar
BL_N920VVRU3CQB9_N920VVZW3CQB9_CL10809541_QB12868949_REV00_user_low_ship.tar
AP_VZW_N920VVRU3CQB9_N920VVZW3CQB9_CL10809541_QB12868949_REV00_user_low_ship.tar
CSC_VZW_N920VVRU3CQB9_N920VVZW3CQB9_CL10809541_QB12868949_REV00_user_low_ship.tar
https://www.androidfilehost.com/?fid=817550096634763863
JUSMEJOSE said:
This is official Nougat firmware use this to update or just want to update
CP_N920VVRU3CQB9_N920VVZW3CQB9_CL10809541_QB12868949_REV00_user_low_ship.tar
BL_N920VVRU3CQB9_N920VVZW3CQB9_CL10809541_QB12868949_REV00_user_low_ship.tar
AP_VZW_N920VVRU3CQB9_N920VVZW3CQB9_CL10809541_QB12868949_REV00_user_low_ship.tar
CSC_VZW_N920VVRU3CQB9_N920VVZW3CQB9_CL10809541_QB12868949_REV00_user_low_ship.tar
Will upload them tonight
Click to expand...
Click to collapse
waiting....
Please upload it.waiting..
link is up
JUSMEJOSE said:
link is up
Click to expand...
Click to collapse
thnx man u saved me a lot of headache with that upload :good:
JUSMEJOSE said:
link is up
Click to expand...
Click to collapse
I thought I saw a Google forms link on your signature 2 days ago asking who wants unlock? I filled the form. I hope to get a free unlock for my tmobile s7. It currently $70 on eBay. Been going up since last month. ?
---------- Post added at 01:45 PM ---------- Previous post was at 01:44 PM ----------
sevenalive said:
waiting....
Click to expand...
Click to collapse
Will this procedure clear data? Factory reset?
Can someone please confirm if this clears existing data? I thought Odin doesn't work in this case because of the locked bootloaded on Verizon?
ynag said:
Can someone please confirm if this clears existing data? I thought Odin doesn't work in this case because of the locked bootloaded on Verizon?
Click to expand...
Click to collapse
Yes, it probably will. If you are that worried about it, backup your data first. Odin will work even with the bootloader locked. Locked bootloader does not prevent you from loading official firmware.
gregcapps said:
Yes, it probably will. If you are that worried about it, backup your data first. Odin will work even with the bootloader locked. Locked bootloader does not prevent you from loading official firmware.
Click to expand...
Click to collapse
What app can we use to back up all data like apps sceen layout ect... since we don't have root on Verizon, I know we can't use titanium back up because we don't have root bit is their a similar app to do what that does
[email protected] said:
What app can we use to back up all data like apps sceen layout ect... since we don't have root on Verizon, I know we can't use titanium back up because we don't have root bit is their a similar app to do what that does
Click to expand...
Click to collapse
Not sure you'll be able to preserve that. I was referring to user data, not system data.
[email protected] said:
What app can we use to back up all data like apps sceen layout ect... since we don't have root on Verizon, I know we can't use titanium back up because we don't have root bit is their a similar app to do what that does
Click to expand...
Click to collapse
Helium or My Backup Pro, but they are limited without root, which means some data can be restored, but not all.
Sent from my SM-N920V using XDA-Developers Legacy app
JUSMEJOSE said:
This is official Nougat firmware use this to update or just want to update
CP_N920VVRU3CQB9_N920VVZW3CQB9_CL10809541_QB12868949_REV00_user_low_ship.tar
BL_N920VVRU3CQB9_N920VVZW3CQB9_CL10809541_QB12868949_REV00_user_low_ship.tar
AP_VZW_N920VVRU3CQB9_N920VVZW3CQB9_CL10809541_QB12868949_REV00_user_low_ship.tar
CSC_VZW_N920VVRU3CQB9_N920VVZW3CQB9_CL10809541_QB12868949_REV00_user_low_ship.tar
https://www.androidfilehost.com/?fid=817550096634763863
Click to expand...
Click to collapse
I extract and I get several files? None of them being .tar files. Does anyone have the 4 files to flash in odin? Am I the only one who didn't get the 4 files mentioned when extracting the Md5? Any help would be greatly appreciated.
Nobody?
patrickpingpong said:
Nobody?
Click to expand...
Click to collapse
You have to go in odin and select PDA and then add the entire md5 file! If you don't want to do it that way, then you have to download a zipping app like 7z or similar and create the .tar yourself.. Which is pointless unless you're planning on flashing 1 file like the boot.img for a reason or other.. The md5 file has all of the files that need to be flashed there's no need to unzip the files. Just flash as is!
If you're downloading from the OP then you need to unzip the file from the .zip because you can only flash .md5 or .tar.
MrMike2182 said:
You have to go in odin and select PDA and then add the entire md5 file! If you don't want to do it that way, then you have to download a zipping app like 7z or similar and create the .tar yourself.. Which is pointless unless you're planning on flashing 1 file like the boot.img for a reason or other.. The md5 file has all of the files that need to be flashed there's no need to unzip the files. Just flash as is!
Click to expand...
Click to collapse
Thanks. I have issue of my note saying "searching for signal" with full bars until i make a call. I dont think flashing the full file in Ap reset my modem to stock.
patrickpingpong said:
Thanks. I have issue of my note saying "searching for signal" with full bars until i make a call. I dont think flashing the full file in Ap reset my modem to stock.
Click to expand...
Click to collapse
Try flashing a modem only file then which is for that signal.. Also boot into recovery using the 3 button combo and clear your Cache after a flash..
MrMike2182 said:
Try flashing a modem only file then which is for that signal.. Also boot into recovery using the 3 button combo and clear your Cache after a flash..
Click to expand...
Click to collapse
I've cleared it after flash and no fix. Does anyone have a modem file I could use. Does it have to be from the same firmware version? Sorry just not really experienced just need to fix this phone it's killing me. I got it off Craigslist don't know the history of it I just know that flashing a fresh stock rom didn't fix the issue.
patrickpingpong said:
I've cleared it after flash and no fix. Does anyone have a modem file I could use. Does it have to be from the same firmware version? Sorry just not really experienced just need to fix this phone it's killing me. I got it off Craigslist don't know the history of it I just know that flashing a fresh stock rom didn't fix the issue.
Click to expand...
Click to collapse
Is it an actual Verizon phone? And do you know for sure that it's Verizon? Go into settings then about phone and tell me what model it says. If it says other than SM-N920V then it's not a Verizon one.. You can only flash firmware for a specific carrier.. Also check the APN settings too.. And about the modem no you don't have to use the same exact one from the same firmware version you can try a different one however I don't think that'll fix the problem.. Try checking the APN settings first.. Also if you just dropped a sim card into it without first giving Verizon the IMEI then it's not gonna work! You'll have to give them the IMEI and if the IMEI is bad the phone will never work at least not with Verizon.
MrMike2182 said:
Is it an actual Verizon phone? And do you know for sure that it's Verizon? Go into settings then about phone and tell me what model it says. If it says other than SM-N920V then it's not a Verizon one.. You can only flash firmware for a specific carrier.. Also check the APN settings too.. And about the modem no you don't have to use the same exact one from the same firmware version you can try a different one however I don't think that'll fix the problem.. Try checking the APN settings first.. Also if you just dropped a sim card into it without first giving Verizon the IMEI then it's not gonna work! You'll have to give them the IMEI and if the IMEI is bad the phone will never work at least not with Verizon.
Click to expand...
Click to collapse
It is indeed n920v clean imei through verizon prepaid. It gets apn through SIM card which is accurate I have signal T all times and internet/mms work. However when I boot my phone or randomly every so often it will say 'searching for service' throughout the day while still full having signal. During this time I don't receive calls/messages/internet notifications and it is stuck that way until I notice it and dial my voicemail which it then displays "Verizon wireless" and then all notifications come through.
patrickpingpong said:
It is indeed n920v clean imei through verizon prepaid. It gets apn through SIM card which is accurate I have signal T all times and internet/mms work. However when I boot my phone or randomly every so often it will say 'searching for service' throughout the day while still full having signal. During this time I don't receive calls/messages/internet notifications and it is stuck that way until I notice it and dial my voicemail which it then displays "Verizon wireless" and then all notifications come through.
Click to expand...
Click to collapse
Maybe try using this downgraded version from my Android File Host and flash it using odin but before flashing take the sim card out and after it's done flashing immediately do a factory reset by holding the power and volume down button and after the screen turns off and then back on select shut down and then boot into recovery and do the factory reset after it's finished put the sim card back in then turn it on and go through all the setup and see if it works.. Let the phone charge some first don't try doing this at 3% battery cause if it shuts down in the middle it can brick the phone. Not likely but it could.
https://www.androidfilehost.com/?fid=889764386195900074