Develop Bugs

[Q] Play Store stopped working, no other thread helped me

Alright,
I'll first start by telling you my story so you guys can retrace what I may have done wrong during the process. I'm a noob but I made a lot of research before posting here and I'm posting because it's been 2 days of trying to make things work with no results.
My goal was to root the phone and install CM10 so I flashed CWM in download mode and I rebooted in recovery. Then, I installed the zip package (CWM-SuperUser-v3.1.3) and rebooted. I transfered CM10 (The ROM dates from 30/09 so I guess this is a pretty recent version, I tried others anyway) on the root of the phone and I rebooted in recovery. When I tried to run the zip package from the internal sd card, I got an error message. All I can remember is that it was looking like this: assert failed: getprop("ro.product.device")
I did a lot of research on google for this error and everybody was suggesting to flash a stock ROM and start all over. At this point, I was getting a little frustrated because I had done a factory reset for nothing so I decided to abandon the project and wait for the upcoming Jelly Bean update.
I rebooted the phone and when after I entered my google informations, Google+ always stopped working but the operation completed. I went to the Play Store and always got a server error message. It was working an hour before so I started to fear something was going on. In fact, it's been like this for two days and it never worked again. I made many factory wipes and I tried to flash a stock ROM with Odin. Odin is always giving me an error message: Complete(Write) operation failed. All threads completed. (succeed 0 / failed 1)
I tried with an earlier version of Odin as a guy in a thread was suggesting, didn't work either. I changed USB port, everything! The only solution I think could work would be to get the Play Store APK file and flash it with Odin but I'm unable to find it.
PS: I also tried to clear data/cache of Google services and Google Play Store. Somebody somewhere suggested to clear Google framework or something like that but I don't have this in my application manager. Guess this could be indicating that some stuff is missing?
I'm very disappointed right now.. I assume that I was in a bit of a rush by trying to root my phone a single week after I got it but I honestly think I did everything right... I really need your help!

First, you need root access. Second, you need an app like Root explorer. Third, you need to edit the build.prop. More specifically, the line "ro.product.device"
Edit that so it reads d2att
Reboot. Should be good after that.
You may need to be on a stock, rooted ROM, maybe not.

mrhaley30705 said:
First, you need root access. Second, you need an app like Root explorer. Third, you need to edit the build.prop. More specifically, the line "ro.product.device"
Edit that so it reads d2att
Reboot. Should be good after that.
You may need to be on a stock, rooted ROM, maybe not.
Click to expand...
Click to collapse
I got root access. Second, root explorer is an app on my computer? Cause I can't get access to the Play Store so this could be a problem for the moment... Third, alright, what do I change in there?

System/build.prop/ro.product.device
Change that to d2att.
Root explorer is an app for your phone, not your computer.
---------- Post added at 08:43 PM ---------- Previous post was at 08:37 PM ----------
http://db.tt/vgBjRVTR
Try upgrading cwm to 6.0.1.2. I've heard some have had good results with this. That link is for ROM Manager, which you just need root for.

If I understand correctly, you think something I did modified this parameter so the phone isn't recognized as a d2att anymore? For the play store, would it help to rerun gapps?
I'm I able to do the modification without root explorer? How do I install the app without play store?
EDIT: I just found a thread where a guy with a Bell phone (also I747 and from Canada) had a problem with this also. It seems it was written d2can (probably for Canada) instead of d2att. He was getting the problem while installing cm10 but I still don't see what this could have to do with three market?
Could you just give me a little more info about modifying this. At least a link? I'm a noob I told you

pelteux said:
If I understand correctly, you think something I did modified this parameter so the phone isn't recognized as a d2att anymore? For the play store, would it help to rerun gapps?
I'm I able to do the modification without root explorer? How do I install the app without play store?
EDIT: I just found a thread where a guy with a Bell phone (also I747 and from Canada) had a problem with this also. It seems it was written d2can (probably for Canada) instead of d2att. He was getting the problem while installing cm10 but I still don't see what this could have to do with three market?
Could you just give me a little more info about modifying this. At least a link? I'm a noob I told you
Click to expand...
Click to collapse
What he's saying is that you need to modify that particular file (ro.product.device) in your phone. For that you need to use something like "Root Explorer."
You don't need to get it from the play store; you can get it on the internet also just seach google for it. "root explorer.apk" and load it.
Just google it, install root explorer and mod the file...it's easy. It takes longer to explain than to do it.

rpavich said:
What he's saying is that you need to modify that particular file (ro.product.device) in your phone. For that you need to use something like "Root Explorer."
You don't need to get it from the play store; you can get it on the internet also just seach google for it. "root explorer.apk" and load it.
Just google it, install root explorer and mod the file...it's easy. It takes longer to explain than to do it.
Click to expand...
Click to collapse
Although your right on the file explorer to change the build.prop I'm not sure why you would advise trying to find ripped copy of a paid app. Aside from not supporting a good dev there is also the real consideration of finding an .apk that may have been modded and not in a good way. To each there own I guess. There are lots of free file explorers on the play store that will more than suffice to do the job such as es file explorer that is pretty popular.

jethro650 said:
Although your right on the file explorer to change the build.prop I'm not sure why you would advise trying to find ripped copy of a paid app. Aside from not supporting a good dev there is also the real consideration of finding an .apk that may have been modded and not in a good way. To each there own I guess. There are lots of free file explorers on the play store that will more than suffice to do the job such as es file explorer that is pretty popular.
Click to expand...
Click to collapse
You have a point; I wasn't aware that Root Explorer was a "paid only" app and I'd certainly not encourage him to not support the devs...I wasn't thinking.
My mistake; go with one of the free ones for now since you can't access the play store.

Crap, I forgot to add that you can access the play store from any computer, just Google play store and sign in with your Google credentials and find what you want and install it. It will auto download and install on your phone. I did this last night, bought and installed nova prime without opening play store on my phone.

If the store won't recognize your phone, how are you going to push the install to it?
Did you try the ROM Manager app i linked?

Alright,
I was able to install file explorer, open build.prop and do the modification. I rebooted in CWM and tried to install CM10, same error : assert failed: getprop("ro.product.device") == "d2att" || getprop("ro.build.product"") == "d2att E: Error in /emmc/cm-10-20210930-1849-SKANK-d2att.zip
(Status 7)
Installation aborted.
I modified the two lines where "d2can" was written instead of "d2att". I would be more eager to get my market back for now...

pelteux said:
Alright,
I was able to install file explorer and open build.prop to do the modification. However, I am unable to save the document as it give me the error: Error occured when trying to save the file. It will not be saved.
What can I do about this?
Seriously, I am a bit sceptical about this modification... I guess it could help to install CM10 but, will I get access to my market..?
Click to expand...
Click to collapse
This should allow Odin to work properly. Your post said that Odin wouldn't work because of an error. This should correct error so that Odin works.

Nice! The phone is softbricked now! Nothing appears after The galaxy S3 logo. The phone seems to be running since I hear it connect to the computer via usb but nothing appears. What do I do now..............................................

mrhaley30705 said:
Your post said that Odin wouldn't work because of an error.
Click to expand...
Click to collapse
Yes but the "d2att" error was on CWM. Now I can't access the phone at all since it seems to be softbricked.
Here is what I see when I try to flash the stock firmware into Odin. No error message but nothing completes anyway...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALEM_I747ATTALEM_I747UCALEM_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
EDIT: Now, I obviously need to do an adb pull to get build.prop and change the line the way it was before. I absolutely have no clue how to do this. Any advice would be welcome.

Is there a blue box lit up, says something like "com"in it? If not, Odin does not see your phone.

Odin always sees my phone, this is not the case. I always see the COM:5 while in download mode.

http://forum.xda-developers.com/showthread.php?t=1903516
Toward the end of the first post is a section on Odin. Try those things.

Odin is currently the least of my problem... The modification I made in the build.prop softbricked the phone so I try to bring it back!

Flashing the stock ROM should do that for you.

I think he can't flash a rom cause he gets an error in odin or it doesn't take cause it doesn't recognize the proper device id because of the messed up build prop? Not sure, not too familiar with odin.
Here is what I see when I try to flash the stock firmware into Odin. No error message but nothing completes anyway...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALEM_I747ATTALEM_I747UCALEM_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
Click to expand...
Click to collapse
With cwm 5.5.0.4 I believe it has access to external sd card. What would happen if you downloaded the same CM10 version you originally flashed to your phone on your computer and extracted the build prop and put it on your external sd card(if you have one and an adapter) along with a cwm flashable version of twrp recovery(which i have), flashed twrp and rebooted recovery, then used twrp's built in file explorer to replace the messed up build prop with the original, that should give you a booting phone. The only catch is that you would have to a battery pull and manually boot into recovery, not sure what pulling the battery would do, wouldn't want to mess up your phone more....anyone think this will work?

[Q] manual 4.1.2 Jelly Bean update fails please help.

hi, i've tried manually updating my s3 to 4.1.2 with the multi window feature through odin but it fails. here is the log. I would really like some help
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXELKC_I9300OXXELK4_I9300XXELKC_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/031> Odin v.3 engine (ID:31)..
<ID:0/031> File analysis..
<ID:0/031> SetupConnection..
<ID:0/031> Complete(Write) operation failed.
<ID:0/031> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/031> Removed!!

Do you have a sprint s3? If so you have the wrong file and should download the one located here. Otherwise you're in the wrong section

i do have sprint. the one in that link you've posted looks like its for rooted phones or will root my phone. I have and dont want either.

Look a little closer. Theres a rooted and an unrooted version. Both are identical with the exception that one has root, the other one doesnt.
Edit:
Heres a direct link to the unrooted version
http://rwilco12.com/Files/Devices/S...nrooted/SPH-L710_MD4_1130792_Stock_Nodata.exe

is it this? if so do i install both files or just the tar.md5. file.

JustMikeOnlyMike said:
is it this? if so do i install both files or just the tar.md5. file.
Click to expand...
Click to collapse
You only need one. I recommend the exe. It's an odin one click and takes the guesswork out of using regular odin

sorry for being semi oblivious and hope im not bothering BUT. .with that exe. file, it will update my phone and allow me to multi task right?
also will these same steps work for the installation on odin?
"In ODIN window you have to click on 'PDA' and then browse your PC for the '.tar.md5′ file you've extracted at step 2. That's the Android 4.1.2 XXELKC firmware update file and you have to load it into ODIN.
Don't change any default ODIN options and make sure that 'Re-Partition' option box is not enabled, as if it is, then you need to disable it.
Press the 'Start' button to begin the Android 4.1.2 XXELKC update on your Galaxy S3. Do not press any other buttons and simply wait for the install process to finish."

JustMikeOnlyMike said:
sorry for being semi oblivious and hope im not bothering BUT. .with that exe. file, it will update my phone and allow me to multi task right?
also will these same steps work for the installation on odin?
"In ODIN window you have to click on 'PDA' and then browse your PC for the '.tar.md5′ file you've extracted at step 2. That's the Android 4.1.2 XXELKC firmware update file and you have to load it into ODIN.
Don't change any default ODIN options and make sure that 'Re-Partition' option box is not enabled, as if it is, then you need to disable it.
Press the 'Start' button to begin the Android 4.1.2 XXELKC update on your Galaxy S3. Do not press any other buttons and simply wait for the install process to finish."
Click to expand...
Click to collapse
Yes that's the newest update with MultiWindow. And when I said it takes the guesswork out I mean you don't have to worry about what boxes to tick or slots to load. There is only one button in the one click and its "start". And thats all you have to worry about pressing (after you put the phone in download mode of course)
Hope I answered your question
See here for an pic of what the one click looks like. (Altho yours will differ slightly)

im still a little confused. So when i have my phone in download mode and connect it to my pc, i just push start? i dont have to load the exe. file into "Bootloader, PDA, Phone, or CSC" ? i ask this because id be shocked if odin found the exe. automatically for me and loaded it lol.

JustMikeOnlyMike said:
im still a little confused. So when i have my phone in download mode and connect it to my pc, i just push start? i dont have to load the exe. file into "Bootloader, PDA, Phone, or CSC" ? i ask this because id be shocked if odin found the exe. automatically for me and loaded it lol.
Click to expand...
Click to collapse
You got it. Your exactly right. And it's not that odin finds the file and loads it. The one click is a special made file with the firmware and odin program combined into one.

alright thanks alot man i appreciate the quick replies and hope this works.

JustMikeOnlyMike said:
alright thanks alot man i appreciate the quick replies and hope this works.
Click to expand...
Click to collapse
Yup np. Don't expect any problems the one clicks are very reliable. And should any problems occur just come back here or shoot me a pm.

JustMikeOnlyMike said:
i do have sprint. the one in that link you've posted looks like its for rooted phones or will root my phone. I have and dont want either.
Click to expand...
Click to collapse
Please be very careful as to what you try to load onto your device. The file you originally attempted to use was for the International S3 if by any chance it would have worked you would own a very expensive paper weight right now.
Transmitted with a portable device using Xparent Blue Tapatalk 2

s4 mini won't boot

I have a Samsung S4 Mini on the Verizon network (SCH-i435). I restarted my phone this morning and it took a much longer than usual to boot. My screen showed the Verizon logo for about 5-10 minutes and when the phone finally booted I was greeted with the utility to set up the phone (pick language, setup email, etc. etc.). I was confused because I had done this already a few months ago when I bought the phone. I skipped the steps and I was greeted with the stock home screen (all my custom shortcuts and widgets were gone). All my marketplace apps were still installed, but some of them had been reset (had to reconfigure waze, winamp, etc). My best guess is that there was an OTA update or some security patch that reset everything. Finally I got things running again the way I liked them. I was using my phone and suddenly it went dead. I tried to restart it but nothing showed on the screen. Oddly enough the phone just vibrates over and over again, but the screen remains black. No matter what I do I can't boot it. The only way I could stop it from vibrating was to pull out the battery. Is there any hope to recover this phone? Thanks.

Did you try to enter recovery mode?

Yes, I followed the instructions on the manufacturer site. I held down the home button, up volume, and powered the device on. A small bit of text appeared for a split second, it was so fast I couldn't read it. It disappeared and the screen went black and the same vibrate pattern started up again.

I got a video camera and managed to capture the text that was being displayed. Here is a screenshot...
It looks like...
MMC: mmc_read fail
Movinaand Checksum Confirmation Fail
Any hope of fixing this?

I asked for recovery cause it was easier to reset to factory the phone. If that's not working, i don't know if there's hope for it to enter download mode, for manual flashing with odin.

I'm able to get into download mode. Is there a ROM I can flash with? This S4 Mini is the Verizon phone so it is the SCH-i435, I didn't think there were any custom roms I could use with this phone.

Stock rom.
Try http://www.sammobile.com/firmware and see if your firmware is there.

Download this for KitKat: http://www.sammobile.com/firmwares/download/31291/I435VRUBNE1_I435VZWBNE1_VZW.zip/
Download this for Jelly Bean (If you had KitKat DO NOT flash the Jelly Bean) :
http://www.sammobile.com/firmwares/download/27312/I435VRUAMK5_I435VZWAMK5_VZW.zip/
If you don't know what you had, flash the KitKat one.
Download Odin, Extrect the downloaded file, Press PDA in Odin and insert the extracted tar.md5 file. Make sure your phone is read with the "COM:**" and start. For detailed info, search on google. Good Luck.

RoyaLKurTx3 said:
Download this for KitKat: http://www.sammobile.com/firmwares/download/31291/I435VRUBNE1_I435VZWBNE1_VZW.zip/
Download this for Jelly Bean (If you had KitKat DO NOT flash the Jelly Bean) :
http://www.sammobile.com/firmwares/download/27312/I435VRUAMK5_I435VZWAMK5_VZW.zip/
If you don't know what you had, flash the KitKat one.
Download Odin, Extrect the downloaded file, Press PDA in Odin and insert the extracted tar.md5 file. Make sure your phone is read with the "COM:**" and start. For detailed info, search on google. Good Luck.
Click to expand...
Click to collapse
Thanks for the links. I got the files you said and googled for tutorials. I found quite few and followed the instructions., but I keep getting the error message.... There is no PIT partition. Here is the Odin readout...
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I435VRUBNE1_I435VZWBNE1_I435VRUBNE1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas? I googled around for a bit but didn't find anything. Is there a PIT file specific for the SCH-i435?

droid2501 said:
Thanks for the links. I got the files you said and googled for tutorials. I found quite few and followed the instructions., but I keep getting the error message.... There is no PIT partition. Here is the Odin readout...
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I435VRUBNE1_I435VZWBNE1_I435VRUBNE1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas? I googled around for a bit but didn't find anything. Is there a PIT file specific for the SCH-i435?
Click to expand...
Click to collapse
I am not sure since this is the first time for me with experience with that phone...
In Odin, make sure Auto Reboot and F. Reset Time check boxes are only two that are selected. DO NOT SELECT ANY OTHER OPTION! Click the AP/PDA button and select that file you downloaded earlier with extension I435VRUBNE1_I435VZWBNE1_VZW.tar.md5 Click the CSC button and select file with CSC in its name. Ignore if there is no such file. Click the PIT button and select the .pit file. Ignore if there is no such file. (You should have this file, do it if you are having that error) Now, once you are ready, hit the START button to begin the flashing process.
If you have any other problems please ask.

RoyaLKurTx3 said:
(You should have this file, do it if you are having that error)
Click to expand...
Click to collapse
Where do I get this file from? I looked at many Odin tutorials but none of them seem to say where I can get it. My phone is dead so if it's something that I need to extract/transfer from my phone then I'm out-of-luck.
I think I'll just contact Verizon and see if my phone is under warranty and if they can send me a new one. It may be easier than combing the web for a tutorial that more fully explains what this PIT file is and why I need it.
In the future should I disable Verizon OTA updates? I suspect a error during the update is what caused this problem in the first place.

droid2501 said:
Where do I get this file from? I looked at many Odin tutorials but none of them seem to say where I can get it. My phone is dead so if it's something that I need to extract/transfer from my phone then I'm out-of-luck.
I think I'll just contact Verizon and see if my phone is under warranty and if they can send me a new one. It may be easier than combing the web for a tutorial that more fully explains what this PIT file is and why I need it.
In the future should I disable Verizon OTA updates? I suspect a error during the update is what caused this problem in the first place.
Click to expand...
Click to collapse
The file should be one of the extracted files in the file you have downloaded from my links. If the file is not there, then most probably Verizon modded the phone to not be able to flash via Odin Mode.
The error during the update may have happened because of low battery, making your phone shut down during the update, which is serious.
You can check yourself if your phone is under warranty (excluding the warranty period)
-Just go to download mode and you will see: KNOX WARRANTY VOID: [if it is 0x0, than it you are still under warranty, but if it says 0x1, you are not.]
Yeah, you should go to the place you have bought the phone from, if none of the above steps worked for you.
Good Luck.

I looked at the links you sent me and I searched the samsung site but I could not find that PIT file. I bought it back into my local Verizon store and they gave me a new S4 Mini. The tech didn't say much about why it broke, he only said that it was still under warranty so I was covered. To avoid something like this happening again I wanted to disable updates on my new S4 Mini. I rooted my new phone, purchased Titanium Backup, and Froze SDM. Is there anything else I have to do?

droid2501 said:
I looked at the links you sent me and I searched the samsung site but I could not find that PIT file. I bought it back into my local Verizon store and they gave me a new S4 Mini. The tech didn't say much about why it broke, he only said that it was still under warranty so I was covered. To avoid something like this happening again I wanted to disable updates on my new S4 Mini. I rooted my new phone, purchased Titanium Backup, and Froze SDM. Is there anything else I have to do?
Click to expand...
Click to collapse
You got the same version of your previous phone?

Yes, that's all they would do for free. They did offer me a Droid Turbo for and extra $100.00 but I really don't like the large phones they're coming out with these days so I declined.

Then you shouldn't get OTA Updates. I don't think that it was needed since the problem you got earlier was because of a faulty firmware from Verizon, which is unlikely or your phone had no battery while your phone was updating.

SM-T211 wifi + bluetooth not working after root and bloatware removal

Hi all, new guy to the forums. After rooting my T211 (4.1.2) via Odin and with TWRP and SuperSU, I started to remove some of the bloatware that Samsung sticks on the tabs. everything was working great until I rebooted one day and then the wifi and bluetooth stopped working. I've flashed the 4.4.2 in preperation to flash a custom rom, but it seems no matter what I do, the wifi and bluetooth issue remain. Can anyone help me with a zip to reinstall the wifi and bluetooth? or an instruction on how to do it? I have the 4.1.2 rom as well as the kitkat rom from italy and a few custom roms. If I knew how to make a flashable zip and which apks and such to use I would be happy to do it myself. Any help would be greatly appreciated. Thanks in Advance, James.

Bump
Bump

Tried just re flashing stock nonrooted bloated os back on?
---------- Post added at 03:41 AM ---------- Previous post was at 03:41 AM ----------
With odin of course and use the pit file for a full reformat wipe

Flashing stock rom
Trying it now. I'm a bit of a idiot, when I was trying to flash the stock rom, I forgot to unzip and wondered why I was getting an error...haha. I wanted to try a dirty flash just in case it worked but no kewpie doll. Trying it with the pit file now. fingers crossed.

Ugh...no luck. here's the read out from Odin. Not sure whats going wrong yet. Maybe not the right pit file.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T211XXAML1_T211OXXAML2_T211XXAML2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Yea double check the pit file is for your model tablet

LT02.pit, this is the one that keeps getting reccomended in all the posts I've read. Says its for the T210 but it is supposed to be the same?

This is very frustrating thought I had it fixed. Wifi button turned on...bluetooth button turned on...just kept scanning. then both shut off and wont stay on

So after reflash they still do it?

yeah, they still do it. puzzling that it turns on but only scans and has no connection.

Using a file manager with root access, delete the following 2 directories:
/data/misc/bluedroid
/data/misc/wifi
Then, reboot.
Can't promise it will work, but it may.

Cool, gonna give it a try in a bit.

Any luck?

well, yes and no... after loading up root browser, I navigated to /data/misc. I don't have a bluedroid directory. I have a bluetooth and a bluetoothd and I have a wifi and a wireless directory. I deleted the first three and rebooted. I then was able to turn on the wifi and it recognized my router and connected...for about 10 seconds then shut off again and wouldn't turn on again. So, I think we're on the right track but not quite there yet. The fact that it did work even if temporarily was encouraging.

If it were me, I would go to sammobile.com and download the full firmware package for your region and flash it with Odin. That will ensure that you have a matching set of firmware (boot, radio, system, etc.) It will not wipe your data. If it works correctly after that, then you can reinstall your custom recovery and whatever rom you want.
Sent from my SM-G920V using Tapatalk

well, that didn't work either. Still has the same problem. I went into twrp and wiped everything except the external sd card. then with Odin, flashed 4.1.2 rom for UK and wifi will not turn on. Scratching my head now

Any other ideas?

Try using Heimdall with a full firmware package. You'll have to extract the firmware package (change the filename ending with ".tar.md5" to ".tar" and use 7-zip to extract it.
Then open up Heimdall, go to "Utilities -> Download PIT -> Destination File" and pick a location and name for the pit file.
Following this step, go to "Flash -> Options -> PIT" and browse to the pit file.
You will then have to go through the process of adding each partition that you want to flash, browsing to the location of the firmware package, and then flashing it.
I've done this several times, although I have not tried with "Repartition".
You will probably want to flash "SYSTEM", "MODEM", "KERNEL", and "RECOVERY" at a minimum. That said, it would be a *good* idea to use all the files inside the firmware package.
I'd upload packages I've made for my own convenience, but I'm unclear about their legal situation. I think I can get away with PMing links around though. Maybe.
EDIT1: Please post the output from the "Status" box if it fails.

Apologies for not responding sooner. Been busy with work, will try this soon and post results. Thanks

Can't get Heimdall to work. All I get is its not a valid win32 application. I refuse to give up on this, I know it's a software issue so there has to be a way to fix it. ...pulling my hair out though.

Could use a little advice on ROM flashing/Odin not working

I'm flashing the Stock ROM for verizon 5.1.1 on my used (but new to me) Galaxy Note 4. The .tar.md5 file once extracted is appx. 4gb. It is the correct file for the model and build. It is currently the same ROM (attempting to fix something as noted at bottom).
N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar.md5 from sammmobile.
I have tried with Odin 3.11.1, 3.10.7, 3.10.6 - once each...I ran each in Administrator Mode on Wdws 7. The same thing happens with each as below.
Only Auto Reboot and F. Reset Time (the defaults checked off) are checked in the Options Tab.
The Log window currently shows:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
(the 3.10.6 version noted the file name as above here in the process, but not the other versions)
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
All appears fine on the phone. It just stays on "downloading", and Odin stays at the above.
As it stays there and does nothing, I am at least able to pull the battery and start it. I've done a factory reset before starting just to make sure it's all clean to start (not that it's necessary). Thankfully, it didn't brick it when nothing worked.
I'm doing this as a last attempt to remove an error in 5.1.1 that causes Setttings to crash then trying to view Google accounts and still keep 5.1.1 in case I can ever figure out the bootloader/root thing.
I am new to this. Am I missing something obvious?
Other details...the download mode does indicated Odin enabled (high speed), so it's set for use. All else is legit. This is a newly purchases used phone.

jecilop said:
I'm flashing the Stock ROM for verizon 5.1.1 on my used (but new to me) Galaxy Note 4. The .tar.md5 file once extracted is appx. 4gb. It is the correct file for the model and build. It is currently the same ROM (attempting to fix something as noted at bottom).
N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar.md5 from sammmobile.
I have tried with Odin 3.11.1, 3.10.7, 3.10.6 - once each...I ran each in Administrator Mode on Wdws 7. The same thing happens with each as below.
Only Auto Reboot and F. Reset Time (the defaults checked off) are checked in the Options Tab.
The Log window currently shows:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
(the 3.10.6 version noted the file name as above here in the process, but not the other versions)
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
All appears fine on the phone. It just stays on "downloading", and Odin stays at the above.
As it stays there and does nothing, I am at least able to pull the battery and start it. I've done a factory reset before starting just to make sure it's all clean to start (not that it's necessary). Thankfully, it didn't brick it when nothing worked.
I'm doing this as a last attempt to remove an error in 5.1.1 that causes Setttings to crash then trying to view Google accounts and still keep 5.1.1 in case I can ever figure out the bootloader/root thing.
I am new to this. Am I missing something obvious?
Other details...the download mode does indicated Odin enabled (high speed), so it's set for use. All else is legit. This is a newly purchases used phone.
Click to expand...
Click to collapse
Try re-downloading the .tar file. Make sure you have ADB debugging enabled. Did you extract the .tar file from the .zip?
You'll want to uncheck auto reboot because you're best served to do a factory reset before your first boot.

douger1957 said:
Try re-downloading the .tar file. Make sure you have ADB debugging enabled. Did you extract the .tar file from the .zip?
You'll want to uncheck auto reboot because you're best served to do a factory reset before your first boot.
Click to expand...
Click to collapse
Thank you for the input.
I will redo the download. It appeared fully successful the first time as the zip extract did work (thus the " The .tar.md5 file once extracted is appx. 4gb") file inside. Should the .md5 NOT be on the end? This is what was contained in the zip file: N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar.md5
Oddly enough, my searches on this do NOT return specifics with plenty saying .tar/.tar.md5 - either one.
I can remove the .md5 and open/extra the .tar file and see the appropriate files inside that one. I think this is the semi-OBVIOUS part I did not know.
Can you confirm, I should be using the .tar file in this case with Odin and not the .tar.md5?
In case I haven't been clear:
* Downloaded a .zip file containing a .tar.md5 file. This does not work for me on Odin.
* With .tar.md5, I cannot extract anything (I'm using Winrar-not 7zip-for this extension).
* If I remove the .md5 leaving only .tar, I can open the .tar file and see the image files and such in this one.
* I think this .tar is what I should be adding, but again I am new to this and the instructions I saw online mentioned adding the .tar.md5 file. (instructions found here: https://androidmtk.com/flash-samsung-stock-rom-using-odin ).
I'm sorry if this is a "duh" question, but I really don't know. I'm new to flashing this but not completely new to rooting. I am in Dev mode (build tap 7 times) with USB debugging and install from unknown sources. And I do have the correct ADB sdk tools and drivers and such. In fact, I'm playing with the commands that at least let me backup apps and data onto a PC right now. (I'm really missing using Titanium backup right now!)
Thanks for your help and the advice about the auto reboot. I know about the factory reset, but I didn't think about this being unchecked to allow that. I'm watching some good vids on rooting the VZ model and getting close to braver to try it, but not quite there yet. I'd just really like to be able to modify what sync in my accounts right now!