I was on stock android version 4.2.2 with stock recovery and unrooted when I received the 4.3 version notification after updating the boot animation remained stuck on the X logo for hours and clearing cache,data from stock recovery didn't help it boot. I flashed the factory 4.2.2 image and it finally booted but I had no phone signal only wifi was working. On inspection I discovered that the baseband was 'unknown' and IMEI number, IMEI SV reset to zero. Strangely the baseband was being detected while in bootloader mode. I have tried both custom recoveries, flashed various roms through custum recovery as well as stock factory images right uptil kitkat. These are my findings:
All Android 4.2.2(and 4.2.1) based roms boot but with baseband unknown and IMEI 0 rendering the phone unable to make calls and send/receive text messages.
All Android 4.3 roms don't boot are stuck at boot animation(flashing old radios like 0.48 and other older versions didn't help)
All Android 4.4 roms also behave the same way as 4.3 i.e stuck at boot animation.
Bottom line is I am stuck on Android 4.2x with a non working radio IMEI=0.... My device is now a mere tablet with inability to be updated. I have seen many people with similar problems but all such threads remain unresolved. I don't know what bug in 4.3 has done this to my phone I even tried the 99 percent working unbrick method but to no avail. I am considering selling this phone at a big loss(cant do much because I am in Pakistan) if any experienced developer is able to help me with fixing my phone(if that's even possible) then I shall be really grateful. Otherwise its bye bye Nexus 4.
liquidmetal88 said:
I was on stock android version 4.2.2 with stock recovery and unrooted when I received the 4.3 version notification after updating the boot animation remained stuck on the X logo for hours and clearing cache,data from stock recovery didn't help it boot. I flashed the factory 4.2.2 image and it finally booted but I had no phone signal only wifi was working. On inspection I discovered that the baseband was 'unknown' and IMEI number, IMEI SV reset to zero. Strangely the baseband was being detected while in bootloader mode. I have tried both custom recoveries, flashed various roms through custum recovery as well as stock factory images right uptil kitkat. These are my findings:
All Android 4.2.2(and 4.2.1) based roms boot but with baseband unknown and IMEI 0 rendering the phone unable to make calls and send/receive text messages.
All Android 4.3 roms don't boot are stuck at boot animation(flashing old radios like 0.48 and other older versions didn't help)
All Android 4.4 roms also behave the same way as 4.3 i.e stuck at boot animation.
Bottom line is I am stuck on Android 4.2x with a non working radio IMEI=0.... My device is now a mere tablet with inability to be updated. I have seen many people with similar problems but all such threads remain unresolved. I don't know what bug in 4.3 has done this to my phone I even tried the 99 percent working unbrick method but to no avail. I am considering selling this phone at a big loss(cant do much because I am in Pakistan) if any experienced developer is able to help me with fixing my phone(if that's even possible) then I shall be really grateful. Otherwise its bye bye Nexus 4.
Click to expand...
Click to collapse
try this for reference http://blog.falcondai.com/2013/10/fixing-galaxy-nexuss-imei-number.html
But this post specifically required the IMEI number to be exactly the SAME as mentioned otherwise it says the method wont work and it also seems to be T-Mobile blocked IMEI or something I don't think this fix is for my issue(correct me if I am wrong I am a noob lol)
My IMEI issue seems to linked to the Android 4.3 update which has broken something and this problem seems quite common on Nexus 4 as I came across many threads with people with exactly the same issue as mine. All the replies given usually say wipe cache and/or flash factory image sadly the problem remains.
I am really disappointed at my decision to buy the Nexus 4(my year long experience with the Galaxy Nexus was without issues) I never expected Google to release an update that breaks radios of many users(just google this problem many seem to have exactly the same symptoms as mine but the problem remained unresolved) and then remain silent despite many complaining on their product support forums.
Seems the device is beyond repair like most affected Nexus 4 phones(some have luckily got fixed by themselves it seems and IMEI appeared again)
Guess I will have to sell it at a very low price. I am skeptical about buying even the Nexus 5 now should I run into another dreaded unfixable IMEI issue caused by Google's own update(just paranoia I guess)
If only someone comes up with some fix I guess that will help plenty of disappointed Nexus 4 owners.
liquidmetal88 said:
But this post specifically required the IMEI number to be exactly the SAME as mentioned otherwise it says the method wont work and it also seems to be T-Mobile blocked IMEI or something I don't think this fix is for my issue(correct me if I am wrong I am a noob lol)
My IMEI issue seems to linked to the Android 4.3 update which has broken something and this problem seems quite common on Nexus 4 as I came across many threads with people with exactly the same issue as mine. All the replies given usually say wipe cache and/or flash factory image sadly the problem remains.
I am really disappointed at my decision to buy the Nexus 4(my year long experience with the Galaxy Nexus was without issues) I never expected Google to release an update that breaks radios of many users(just google this problem many seem to have exactly the same symptoms as mine but the problem remained unresolved) and then remain silent despite many complaining on their product support forums.
Seems the device is beyond repair like most affected Nexus 4 phones(some have luckily got fixed by themselves it seems and IMEI appeared again)
Guess I will have to sell it at a very low price. I am skeptical about buying even the Nexus 5 now should I run into another dreaded unfixable IMEI issue caused by Google's own update(just paranoia I guess)
If only someone comes up with some fix I guess that will help plenty of disappointed Nexus 4 owners.
Click to expand...
Click to collapse
Your IMEI information should be on your box if you still have it. Now there has to be a tutorial out there somewhere to enter IMEI info for your phone. I know I found some stuff when trying to this to a Galaxy S3.... I would keep looking or contact Google for a RMA
Still no luck. Now flashing the just released Kitkat image, who knows it may work.
Edit: Still the same result.
Wonder why only 4.2.2 based roms boot but 4.3x and 4.4 based ones do not. I also don't get why baseband is detected in the bootloader mode but not within the OS.
And what is the process of this RMA thingy? Is it applicable for countries outside US? I am from Pakistan btw and got it from a local shop. Nexus 4 can't be bought from Play Store in my country
Any Luck yet?
liquidmetal88 said:
Still no luck. Now flashing the just released Kitkat image, who knows it may work.
Edit: Still the same result.
Wonder why only 4.2.2 based roms boot but 4.3x and 4.4 based ones do not. I also don't get why baseband is detected in the bootloader mode but not within the OS.
And what is the process of this RMA thingy? Is it applicable for countries outside US? I am from Pakistan btw and got it from a local shop. Nexus 4 can't be bought from Play Store in my country
Click to expand...
Click to collapse
Hi @[liquidmetal88] did you get any solution, exactly the same issue as yours. Please share if you have solved it, would be of great help
sambitshankar said:
Hi @[liquidmetal88] did you get any solution, exactly the same issue as yours. Please share if you have solved it, would be of great help
Click to expand...
Click to collapse
Am also facing this issue...only the 4.2.2 boots with no basebanc versiono no IMEI no. and doesn't detects any Sim card
Unlike Samsung phones, the imei cannot be re-injected into the phone's file system. People have had to return the phone to Google to have it fixed.
If you try to install a stock 4.3 or 4.4 ROM, the phone will not even boot to the desktop.
Related
I am one of the unlucky people who's radio was damaged by the 4.3 update meaning my IMEI=0 and baseband is unknown....since I am in Pakistan and got the phone from here i cant RMA the device...so I have an ipod touch device in which every function works except the phone function. I have got a seperate phone now but want to keep the radio less nexus 4 for other functions like browsing and games.
Now in Nexus 4 devices with the IMEI 0 problem only Android 4.2.2 boots while both Android 4.3 and 4.4 get stuck at the boot screen logo.
so my question is..is there some way I can get any kitkat rom to boot even if its without IMEI? Would any one be so kind enough to make a modified kitkat ROM that boots on Nexus 4s with IMEI=0 and baseband unknown problem?
and my second question is why is it that on Nexus 4s broken by the 4.3 update that have IMEI=0 and baseband unknown that ONLY 4.2.1/4.2.2 boots without phone ability but 4.3 and 4.4 do not boot at all remaining stuck at logo? Any possible explaination? Whats in the 4.2x ROMS that make it boot in such affected devices and whats in 4.3/4,4 that stops them from booting in IMEI=0 Nexus 4s?
I just looking to boot a kitkat ROM even if IMEI still remains zero.
I am a noob so go easy on me and I would really appreciate any help,suggestions or ANYTHING at all. Thanks.
Have you tried to simply reflashing the baseband or flashing the full factory image which have the baseband included? The instructions are in my signature.
eksasol said:
Have you tried to simply reflashing the baseband or flashing the full factory image which have the baseband included? The instructions are in my signature.
Click to expand...
Click to collapse
I have already done all the basic troubleshooting steps. i have flashed full factory images via fast boot many times only 4.2.2 boot with imei=O while 4.3 n 4.4 do not boot at all thats why m asking why only 4.2x boots n others do not n i will appreciate if someone can get kitkat to boot on my phone even if IMEI still remained zero.
I have also flashed again and again all the basebands(old and new) problem presists...baseband only shows in the bootloader mode while it remains unknown within android OS. All the threads I have seen of my problem remain unconcluded so I have little hope of ever restoring IMEI but I would like if atleast Kitkat boots somehow
liquidmetal88 said:
I have already done all the basic troubleshooting steps. i have flashed full factory images via fast boot many times only 4.2.2 boot with imei=O while 4.3 n 4.4 do not boot at all thats why m asking why only 4.2x boots n others do not n i will appreciate if someone can get kitkat to boot on my phone even if IMEI still remained zero.
I have also flashed again and again all the basebands(old and new) problem presists...baseband only shows in the bootloader mode while it remains unknown within android OS. All the threads I have seen of my problem remain unconcluded so I have little hope of ever restoring IMEI but I would like if atleast Kitkat boots somehow
Click to expand...
Click to collapse
Sorry, don't know what to tell you, but I think you're not the only one with similar issues. Have you tried with custom roms?
eksasol said:
Sorry, don't know what to tell you, but I think you're not the only one with similar issues. Have you tried with custom roms?
Click to expand...
Click to collapse
As many as I could but the pattern remains the same...all 4.2.2 ones boot without IMEI...while 4.3 and 4.4 custom ROMS simply do not....yes many people have had this exact same issue...many threads here too....one thing is common in these cases the issue started after updating to Android 4.3(guess some lethal bug in it that broke some Nexus 4 phones) but I wonder what stops a 4.3 ROM or a kitkat ROM from booting while facing this bug where as ALL 4.2.1 and 4.2.2 ROMS boot even though basebandvis unknown. I do hope such bugs dont occur in future updates in my country a nexus 4 without phone ability and inability to be updated is valueless and my hard earned cash has literally gone down the drain...may be I will sell it for parts or something.
first thing first.
ensure that you have an unlocked bootloader.
ensure that you have a custom recovery i.e cwm twrp
answer the following question, do you ever tried flashing a custom rom? i.e cm10.2
did you tried flashing baseband?
hassi4042 said:
first thing first.
ensure that you have an unlocked bootloader.
ensure that you have a custom recovery i.e cwm twrp
answer the following question, do you ever tried flashing a custom rom? i.e cm10.2
did you tried flashing baseband?
Click to expand...
Click to collapse
Bootloader is unlocked.....custom recovery is there.....have tried all cyanogen mod versions available for Nexus 4.....result is the same....4.2.2 ROMS(official factory images as well as custom ROMS) boot with IMEI=0 and baseband unknown.....while 4.3,4.4 ROMS are always stuck on boot animation...Having seen many threads on my problem it seems my IMEI problem is unlikely to be fixed( nope flashing different ROMS, clearing caches,flashing different radios via custom recovery or fast boot does not change any thing) Now I am tired of trying to fix the IMEI again and again I just want someone to help me boot any Kit kat ROM even if its without IMEI or just explain to me why Kitkat and 4.3 ROMS dont boot when IMEI= 0 while all 4.2 ROMS boot?
Kindly also explain why baseband version appears unknown within Android OS but is detected while in bootloader mode. Thanks
Exactly same situation here...
Very frustrated, this is not a new bug and new android versions are coming but this remains unsolved.
Nothing? Only 4.2.x is bootable???
PN.ItalyGirl said:
Nothing? Only 4.2.x is bootable???
Click to expand...
Click to collapse
i booted with imei=0 (no radio installed) however it took up to 40 mins on the 1st boot and took up to 15 on other ones.
to wait less, u can install 4.2.2 stock from factory image and let it boot. then u install custom recovery, and reboot back to fastboot mode. on fastboot mode u get a 4.4.2 stock factory image, extract it,extract image-occam-blabla.zip and copy the system image. then u type fastboot format system, fastboot flash system <path to system.img>.
then go to custom recovery and:
if using cwm:
go to advanced -> wipe dalvik cache
if twrp:
Wipe -> advanced wipe -> mark dalvik cache and cache and dismark others
then reboot and wait up to 15mins
Is there any way to restore the IMEI at all? Ive been looking for a long time now. Absolutely no luck.
Sorry to wake up this thread but i don't like to double post.
I have the same situation with my nexus 4, i assume the phone is bricked and stuck in Android 4.2. But i want to take some advantage of this bricked phone and use it for Android Auto in my car (with compatible AA Stereo), as an always on and dedicated to the car.
The problem is that Android 4.2 is compatible with nothing good today, so i want to update at least to lollipop or marshmallow.
Is there any way that i can flash a newer ROM (custom, stock, whatever) that works with an "IMEI unknown" phone? Because 4.2 is the only working ROM, others stuck in boot logo
Well when I look at the advanced radio settings I keep getting "imei: unknown" status at my nexus 4. Together with baseband unkown and all mobile connectivity seems wrong. I am currently running the stock run and not updated anything or done anything (heck I took great effort to "relock" it when I unlocked it to FIX this. (On top of this: loading takes ages, sometimes refusing to load till battery level drops below 10%).
I've tried flashing android 4.4 (but this creates the soft-brick looping while starting android).
I've tried factory reset,
I've tried hard reset
And I've tried the manual resets by flashing 4.2.2 back on.
In all combinations
What can be done, and how can I start using my mobile phone as a PHONE again? Anything but asking for a warranty (as I sadly void It when I had to downgrade from 4.3 to 4.2 to fix a bug introduced in 4.3 that prevented deep sleep)
From what I have read, you cannot run any rom that is newer than 4.2.2 if your phone has imei problems. The only way to fix the imei issue is to send it to LG.
audit13 said:
From what I have read, you cannot run any rom that is newer than 4.2.2 if your phone has imei problems. The only way to fix the imei issue is to send it to LG.
Click to expand...
Click to collapse
So I'm stuck? As my warranty is "void" because I "rooted" the phone to get 4.2.2 back on?
Great having to throw away a phone less than 5 months old. Last time I bought a smartphone it seems; I can't live with those stupid warranty rules rooting & modifying oses runs through my veins. I specifically bought the nexus (and thus stock android) for that.
PS: why is there a "5 minute wait" on UPDATING posts here?
pulli23 said:
So I'm stuck? As my warranty is "void" because I "rooted" the phone to get 4.2.2 back on?
Great having to throw away a phone less than 5 months old. Last time I bought a smartphone it seems; I can't live with those stupid warranty rules rooting & modifying oses runs through my veins. I specifically bought the nexus (and thus stock android) for that.
PS: why is there a "5 minute wait" on UPDATING posts here?
Click to expand...
Click to collapse
I don't know if that still affects your warranty, but you can unroot and re-lock the bootloader using the Nexus Rooting Toolkit or another method of your choosing...
Hello!
This is my first post, but I have found this forum incredibly helpful, and I am hoping to provide a little help myself (and maybe get a little along the way)
I just unboxed a new Nexus 7 (Amazon order within the last 7 days). My purpose for this particular device was to be a dedicated Nethunter device so that I can perform some work related functions with it.
After fiddling for about 2 days with not being able to get the darn thing rooted, I figured out that the lastest/official TWRP builds DO NOT work with the brand new Nexus 7's! This essentially renders things like NRT useless unless you happen to know that you need a very specific custom recovery - (thanks to another thread here on this forum) I figured out that I had to flash a custom multi rom version of TWRP in order to get the device rooted. The intersting thing, this thread was full of people with BRAND new nexus devices . . . not older (by older I mean 3 months or more)
Well, the problems continued. Once I got Nethunter going I was not able to get any external wifi card enabled. More searching as revealed that alot of people are having this issue with lollipop and that the general recommendation is to downgrade to KitKat.
Ok Ok . . so I decided to say "screw lollipop, I'll flash back to 4.4.4"
Yeah . . .well . . . no luck there. No matter what version of bootloader I flashed, and no matter which version of KitKat I tried, I couldn't get any of them to boot past the google initial boot screen. With the recovery mode complaining about not being able to mount /cache /recovery . . .etc - I tried flashing them several different ways and ever from different computers. I even tried downloading the stock images multiple different times.
So . .that brings me to the point of this. It appears that Nexus devices ordered in the last 60 days must have some type of hardware revision change that is making things pretty complicated
I am curious if anyone else is seeing strange things like this?
I can get a rooted version of 5.1.1 going no problem, but I am "stuck" with this weird issue with the external cards, and the weird issue where I cant downgrade.
Thanks for listening
Also, just to add real quick, this device is a 16GB wifi model. The bootloader is claiming a Hardware version of "Rev_E"
I dont have another Nexus 7 to look at, but I wasn't sure if Rev_E was of importance.
Thanks
Here is the issue. A friend of mine had gone a bought a Galaxy Sky SM-S320VL from TracPhone. And had been using the phone without any problems until a couple of weeks ago. Then he decided to do a Factory Reset. Instead of doing the software reset, from with in Settings, he went and did a HARD Reset without unlocking the google account. And guess what, he can't remember the account information for that phone. And came to me to reset the phone. (As I had to deal with this problem in the past with other people and their phones.)
I have downloaded the only stock rom I can find for this phone and flashed it with Odin3. But for some reason the flashing of the rom is never done. By this I mean, the phone downloads the rom as Odin sends it. Odin reports a Success with the flashing. But, when the phone reboots. The system has not been reset and FRP is still active.
I have flashed only the AP, and the phone reboots directly into setup and shows a message about an unauthorized Factory Reset.
I have flash all 4 files in the ROM set (BL, AP, CP, and CSC). and Odin states the flash was a success. The phone reboots, goes to recovery and states Starting System Update. Goes so far into the update, then stops and shows Erasing. After a short time of showing Erasing it reboots to setup. Where again the phone shows the message about authorized Factory Reset.
I have used Odin3 v3.9.0, v3.11.1, v3.11.2, v3.12.5. And I have updated to the latest USB drivers from Samsung.
So my question is this. Has anyone had come across this behavior before? And how can I get past this?
The phones particulars:
Name: Samsung Galaxy Sky
Model #: SM-S320VL(GP)
OS v: 6.0.1
Firmware #: S320VLUDU2APJ3
Model #, as reported by Downloader: SM-S320VL
Note: As a strange side effect of when I flash all 4 rom files. For some reason once the phone has failed the system update, erased and has reboot. I have complete access to the phones User data area from within my computer. But, I am unable to access the phone with adb.
Hey folks,
I'm having the exact same issue as the OP. Odin does a successful install on the phone but I get the unauthorized reset message and then Wifi does not work when prompted on the next screen.
Is there a tracfone version of the rom or a fix that anyone here knows of? Thanks!
@drasnah
I have yet to get any kind of reply from anyone on this. Either now one knows, and is not stating so, or doesn't care.
I have seen the wi- fi fix in another thread.
Modify /system/build.prop:
ro.securestorage.support=true to false
Hope that helps!
20eyes said:
I have seen the wi- fi fix in another thread.
Modify /system/build.prop:
ro.securestorage.support=true to false
Hope that helps!
Click to expand...
Click to collapse
First this is not a wi-fi problem it is a re-flashing of the rom problem.
Second, I do not have access, root or otherwise, to any of the system files on the phone.
Third, with the first two in mind this possible solution is of no help.
Fourth, Re-read my original post. I have given complete detailed information as to what I have access to and what I have done.
Can someone send me a download think for this phone i downloaded one but it won't flash it keeps failing
This device has been locked down by Tradphone and Samsung. It gives errors flashing even the correct stock firmware. It's a piece of garbage. NEVER buy anything from Tracphone. Garbage company. You'll never fix this issue. Only pushed updates will flash via software from sammy and tracphone that is built into the rom..
Curtis1973 said:
This device has been locked down by Tradphone and Samsung. It gives errors flashing even the correct stock firmware. It's a piece of garbage. NEVER buy anything from Tracphone. Garbage company. You'll never fix this issue. Only pushed updates will flash via software from sammy and tracphone that is built into the rom..
Click to expand...
Click to collapse
Not sure if that's correct? It depends on the firmware and odin version being used.
---------- Post added at 10:00 PM ---------- Previous post was at 09:58 PM ----------
Nate1k904 said:
Can someone send me a download think for this phone i downloaded one but it won't flash it keeps failing
Click to expand...
Click to collapse
Post more details on the error, screenshots, firmware and odin version used.
Need to know if works. Or if needing to settle for a different route.
The_WABBIT said:
Here is the issue. A friend of mine had gone a bought a Galaxy Sky SM-S320VL from TracPhone. And had been using the phone without any problems until a couple of weeks ago. Then he decided to do a Factory Reset. Instead of doing the software reset, from with in Settings, he went and did a HARD Reset without unlocking the google account. And guess what, he can't remember the account information for that phone. And came to me to reset the phone. (As I had to deal with this problem in the past with other people and their phones.)
I have downloaded the only stock rom I can find for this phone and flashed it with Odin3. But for some reason the flashing of the rom is never done. By this I mean, the phone downloads the rom as Odin sends it. Odin reports a Success with the flashing. But, when the phone reboots. The system has not been reset and FRP is still active.
I have flashed only the AP, and the phone reboots directly into setup and shows a message about an unauthorized Factory Reset.
I have flash all 4 files in the ROM set (BL, AP, CP, and CSC). and Odin states the flash was a success. The phone reboots, goes to recovery and states Starting System Update. Goes so far into the update, then stops and shows Erasing. After a short time of showing Erasing it reboots to setup. Where again the phone shows the message about authorized Factory Reset.
I have used Odin3 v3.9.0, v3.11.1, v3.11.2, v3.12.5. And I have updated to the latest USB drivers from Samsung.
So my question is this. Has anyone had come across this behavior before? And how can I get past this?
The phones particulars:
Name: Samsung Galaxy Sky
Model #: SM-S320VL(GP)
OS v: 6.0.1
Firmware #: S320VLUDU2APJ3
Model #, as reported by Downloader: SM-S320VL
Note: As a strange side effect of when I flash all 4 rom files. For some reason once the phone has failed the system update, erased and has reboot. I have complete access to the phones User data area from within my computer. But, I am unable to access the phone with adb.
Click to expand...
Click to collapse
J3 sm s320vl... tracfone root availability? Just bought phone hopefully got a good one to root? Or maybe someone knows who maybe be able to... please help
No updates? Interested, I have the same phone.
There is no solution for this phone. It will forever be a Trac-phone.
Yes, it nice to imagine what could had been. If there was a fix for the locked bootloader. Its encrypted, and is highly unlikely to be broken by anyone.
Do not flash the boot.image that some people have suggested
Although that method works on some devices such as the AT&T Samsung Galaxy S5. In this case flashing the boot.image from an unlocked device does nothing but places the phone into an even more precarious situation, that makes it unusable even as a Trac phone.
While its true that this very low budget phone could had been decent with a custom Rom ,
You will not be able to get it working.
I have one that belonged to my daughter a couple of years ago and I managed to get it boot into the system again.
Its only function is as a calculator, or preschool game, the cellular reception and Wifi connections are highly unstable and will not stay connected.
Now it serves as my nieces play toy. I would donate to some poor person at the Salvation Army it if it was useable.
By the way, for anyone reading this.
If you have an old phone that is useable. You could dramatically help a Homeless people, by gifting them with a phone especially, if it has some minutes on it.
This gift will help them schedule job interviews, doctors appointments , etc and you will feel good knowing that you helped someone in need.
I have done this before, and will be dropping off a Blu phone, and Kindle Tablet this week.
tsongming said:
There is no solution for this phone. It will forever be a Trac-phone..
Click to expand...
Click to collapse
It is possible to gain root on this device.
ashyx said:
It is possible to gain root on this device.
Click to expand...
Click to collapse
I have permissible SE Status but can not achieve root on this device. Also, I have not found that anyone has had success rooting this exact model.
To be clear my device is the 2016 TracFone Samsung Galaxy J3 Sky model : SM-S320VL
Build S320VUDU1APG2
Hardware Version S320 VL04
I have found reports of people with S320VLUDU2API3 stating that the were able to achieve root and then assumed that it must also be possible with S320VUDU1APG2.
I am usually the guy that can figure these things out, very often before others. But I have had no success gaining root on this device using published methods. Also, I have not seen one example of someone with this identical device who gained root.
You are apparently the Wizard of these Samsung phones, so if you know of a definite way to root it, please point me towards the solution. I would really appreciate it.
I would love to root this phone, get it working again, and gift it to lady who was beaten by her husband and she is now living in a homeless shelter with her two children. She could use a phone to help with her job search. She would appreciate it.
At the moment this phone can will not keep a signal and I can't attempt the build prop solution without root.
Thank you.
tsongming said:
I have permissible SE Status but can not achieve root on this device. Also, I have not found that anyone has had success rooting this exact model.
To be clear my device is the 2016 TracFone Samsung Galaxy J3 Sky model : SM-S320VL
Build S320VUDU1APG2
Hardware Version S320 VL04
I have found reports of people with S320VLUDU2API3 stating that the were able to achieve root and then assumed that it must also be possible with S320VUDU1APG2.
I am usually the guy that can figure these things out, very often before others. But I have had no success gaining root on this device using published methods. Also, I have not seen one example of someone with this identical device who gained root.
You are apparently the Wizard of these Samsung phones, so if you know of a definite way to root it, please point me towards the solution. I would really appreciate it.
I would love to root this phone, get it working again, and gift it to lady who was beaten by her husband and she is now living in a homeless shelter with her two children. She could use a phone to help with her job search. She would appreciate it.
At the moment this phone can will not keep a signal and I can't attempt the build prop solution without root.
Thank you.
Click to expand...
Click to collapse
See the thread below. Root was gained, albeit temporary. However I believe this is due to kernel panics which may be solved by a few build.prop edits. We had to do the same on the J327T1.
https://forum.xda-developers.com/galaxy-j3-2016/help/samsung-galaxy-j3-sm-s320vl-rooted-t3561762
Also if you firmware S320VUDU1APG2 then why not just update it to the firmware that has been reported to work?
I have found one these phones left on a table of a food truck area, screen was cracked - the device was only getting the android guy with triangle on it, I done some research and found the stock rom and flashed it with odin; as some have mentioned in comments above I also experienced wifi issue, so I thought I had installed incorrect rom - downloaded a different one this was a combination file that was the factory repair rom used for testing the device, but wifi worked - it wasn't a fully working telephone it didnt have the app store, well it really didnt have any apps, but I found I could copy over apk files from my PC to the device and then install them, so the phones not completely useless or junk --- it could be used for something. I myself am using that device as a security camera using IP CAM app works great. I was actually using this device for quiet some time as my roku tv remote, because my actual roku remote grown legs and walked off... i havent tried this, but I am sure you could install a launcher apk such as "apex launcher"
well i wasted enough of your time today...
Hey guys!
After few days trying to fix the problem on my Nexus 6P, I still can't make it run properly so I decide to create a new thread asking you guys and this is my last hope for it. I had been using stock android 6.0.1 until I decided to upgrade to OTA 7.1.1 because I hate the notification on the statusbar. My phone worked fine, everything was OK on 6.0.1. After upgrading to android 7.1.1, my phone couldn't get any mobile signal. It still can detect the simcard, the sim toolkit app still shows but I can't use the network. Everything else works properly just like before upgrading. I tried to flash stock 7.1.2 n2g47o image from google; some custom roms like chroma, pure nexus, ressurection remix, flyme, ... and also tried to select automatic band but it is still the same. When I select automatic or any other band, it shows "select [band] unsuccessful". The service state shows "radio off" and I can't turn it back on in *#*#4636#*#*. Please help me! Thank you guys a lot.
tbmoc96 said:
Hey guys!
After few days trying to fix the problem on my Nexus 6P, I still can't make it run properly so I decide to create a new thread asking you guys and this is my last hope for it. I had been using stock android 6.0.1 until I decided to upgrade to OTA 7.1.1 because I hate the notification on the statusbar. My phone worked fine, everything was OK on 6.0.1. After upgrading to android 7.1.1, my phone couldn't get any mobile signal. It still can detect the simcard, the sim toolkit app still shows but I can't use the network. Everything else works properly just like before upgrading. I tried to flash stock 7.1.2 n2g47o image from google; some custom roms like chroma, pure nexus, ressurection remix, flyme, ... and also tried to select automatic band but it is still the same. When I select automatic or any other band, it shows "select [band] unsuccessful". The service state shows "radio off" and I can't turn it back on in *#*#4636#*#*. Please help me! Thank you guys a lot.
Click to expand...
Click to collapse
Try the flash all bat with stock rom and then relock your boot loader
Sent from my Pixel XL using Tapatalk
Are you with verizon, 7.1.1 has images for verizon only and except, may flashing one of those will fix your issue and use the flash all bat to wipe completely your phone.
bennyboy2120 said:
Try the flash all bat with stock rom and then relock your boot loader
Click to expand...
Click to collapse
coremania said:
Are you with verizon, 7.1.1 has images for verizon only and except, may flashing one of those will fix your issue and use the flash all bat to wipe completely your phone.
Click to expand...
Click to collapse
Thank you guys and sorry for not saying, I flashed both 7.1.1 (NUF26N, Mar 2017, Verizon Only) and 7.1.2 (N2G47O, May 2017) with flash-all.bat follow the instruction here https://developers.google.com/android/images but it remains the same. I read on Nexus Community that Google developers released images that fix signal problems from Feb 2017. I'm downloading this 7.1.1 (NMF26F, Dec 2016. All carriers except Verizon) and will give it a try even when it was released on Dec 2016.
tbmoc96 said:
Thank you guys and sorry for not saying, I flashed both 7.1.1 (NUF26N, Mar 2017, Verizon Only) and 7.1.2 (N2G47O, May 2017) with flash-all.bat follow the instruction here https://developers.google.com/android/images but it remains the same. I read on Nexus Community that Google developers released images that fix signal problems from Feb 2017. I'm downloading this 7.1.1 (NMF26F, Dec 2016. All carriers except Verizon) and will give it a try even when it was released on Dec 2016.
Click to expand...
Click to collapse
Again try relock on the boot loader and tell me if it helps
Sent from my Pixel XL using Tapatalk
tbmoc96 said:
Thank you guys and sorry for not saying, I flashed both 7.1.1 (NUF26N, Mar 2017, Verizon Only) and 7.1.2 (N2G47O, May 2017) with flash-all.bat follow the instruction here https://developers.google.com/android/images but it remains the same. I read on Nexus Community that Google developers released images that fix signal problems from Feb 2017. I'm downloading this 7.1.1 (NMF26F, Dec 2016. All carriers except Verizon) and will give it a try even when it was released on Dec 2016.
Click to expand...
Click to collapse
Hope you will fix it, if you got no success may you try flashing back to 6.0.0
Edit: check you imei, I will hope for you it doesn't show 0, then may you're f****d without a backup of your efs partition.
bennyboy2120 said:
Again try relock on the boot loader and tell me if it helps
Click to expand...
Click to collapse
The guide has the re-lock part so I'm 100% sure I tried to re-lock the bootloader. Not only the Google guide but on other topics on xda and Nexus Community someone re-locked the bootloader and they fixed the problem. Therefor, I followed them to re-lock but still no service
coremania said:
Hope you will fix it, if you got no success may you try flashing back to 6.0.0
Click to expand...
Click to collapse
I also tried to flash back to 6.0.0 first release firmware and 6.0.1 to get vendor for chroma / purenexus , still the same
coremania said:
Hope you will fix it, if you got no success may you try flashing back to 6.0.0
Edit: check you imei, I will hope for you it doesn't show 0, then may you're f****d without a backup of your efs partition.
Click to expand...
Click to collapse
My imei still there, I also have EFS backup ;(
tbmoc96 said:
My imei still there, I also have EFS backup ;(
Click to expand...
Click to collapse
I guess you flashed the backup, apn reset? Or flashing lineage?
Edit: take a look here, maybe deleting via fastboot and restoring with twrp will help
http://www.theandroidsoul.com/fix-e...d-wifibluetooth-issues-restoring-twrp-backup/
Sadly this problem ends up to hardware on other threads, hoping not for you
coremania said:
I guess you flashed the backup, apn reset? Or flashing lineage?
Edit: take a look here, maybe deleting via fastboot and restoring with twrp will help
http://www.theandroidsoul.com/fix-e...d-wifibluetooth-issues-restoring-twrp-backup/
Sadly this problem ends up to hardware on other threads, hoping not for you
Click to expand...
Click to collapse
I lost the network right after I upgraded my phone through OTA ;( I flashed stock firmware right after that so I guess it's not come from EFS partition. I backed up all things with TWRP after I had finished the flash-all.bat process. I'm checking out the thread, maybe there's a way out?
Yesterday I brought my phone to Huawei service center in my country but they don't officially sell the Nexus 6P in my country so they didn't take the phone because they don't have anything to fix its problem.
I would try, seems that you got nothing to loose
I'm having the same problem.
I've tried everything you did and when I select automatic bands in 4636 it does successfully, but still no signal.
Also, when I search for network in the mobile settings it always error.
I noticed that my GPS also stopped working. I only can use apps like Maps if I'm connected to a Wi-Fi.
Since the GPS stopped working this makes me believe it's an antenna problem.
If I selected WDCMA Only my network goes to Global instead of what I've selected.
I have the xt1511 (US Nexus Version), but since Nexus is always unlocked I know it isn't a CDMA/GSM trouble.
My wife's 6P started doing this about a month ago where she would randomly lose service for a minute. Today she lost it completely and it seems like there is an issue internally with the radio. I've tried multiple sim cards, factory resets, flashing the latest factory image, trying an old radio version etc. It seems like there has to be some kind of defect. I would hang on to the phone just in case there ends up being a class action lawsuit. Her phone is exactly one year and one month old.
Im frustrated...
I bought my nexus 6p six months ago from a guy on ebay. I love the phone really, but one month later i had the battery problem, and i said well, it could happen, i bought a battery and changed it.
and yesterday, i lost signal. its dead. i tried everything in the forums, i locked it, got it back to stock. and nothing...
Now what?, we dont know if its a hardware problem or is it a software one.
Should I take it to a service center in the us? I have no warranty.
Update 06-12-17: so i kept readying and I saw someone solved the issue installing a factory image from febuary. I did it flashed it, then went into recovery and made factory reset. and it worked!!!! signal is backkkk! im soo happy!!!
Update 2 06-12-17: yeah i was happy, and soo i was going back to normal, i installed twrp, and root, phone boot up and again bye bye signal.
Update 06-14-17: Turns out that since I got to Colombia a month ago, this country has like a national IMEI list. Since I didn't subscribe my device the carrier blowies my phone and that why I had no service... Soo this ends my journey with the no service problem. They fixed it
Humanreflect said:
Im frustrated...
I bought my nexus 6p six months ago from a guy on ebay. I love the phone really, but one month later i had the battery problem, and i said well, it could happen, i bought a battery and changed it.
and yesterday, i lost signal. its dead. i tried everything in the forums, i locked it, got it back to stock. and nothing... Now what?, we dont know if its a hardware problem or is it a software one. Should I take it to a service center in the us? I have no warranty.
Click to expand...
Click to collapse
Is your phone a H1511 or 1512? You didn't mention it explicitly but you may have changed the LTE bands using a hidden menu. Apparently this is a known bug with the hidden menu itself. Several people have had luck flashing an older version of Chroma and switching the band back to Auto. There is a link to the ROM for the 6P in this Nexus Help Forum. If you never used this menu before, you may just be able to access the menu and try setting to Auto first before flashing the ROM. You should get a confirmation that AUTO mode is selected. You also didn't explicitly mention whether the phone worked properly for a while AFTER your battery repair, OR was a direct result of your repair... which could mean it was damaged.
v12xke said:
Is your phone a H1511 or 1512? You didn't mention it explicitly but you may have changed the LTE bands using a hidden menu. Apparently this is a known bug with the hidden menu itself. Several people have had luck flashing an older version of Chroma and switching the band back to Auto. There is a link to the ROM for the 6P in this Nexus Help Forum. If you never used this menu before, you may just be able to access the menu and try setting to Auto first before flashing the ROM. You should get a confirmation that AUTO mode is selected. You also didn't explicitly mention whether the phone worked properly for a while AFTER your battery repair, OR was a direct result of your repair... which could mean it was damaged.
Click to expand...
Click to collapse
In my case I have a 1511 and I've tried this Chroma fix. No success.
v12xke said:
Is your phone a H1511 or 1512? You didn't mention it explicitly but you may have changed the LTE bands using a hidden menu. Apparently this is a known bug with the hidden menu itself. Several people have had luck flashing an older version of Chroma and switching the band back to Auto. There is a link to the ROM for the 6P in this Nexus Help Forum. If you never used this menu before, you may just be able to access the menu and try setting to Auto first before flashing the ROM. You should get a confirmation that AUTO mode is selected. You also didn't explicitly mention whether the phone worked properly for a while AFTER your battery repair, OR was a direct result of your repair... which could mean it was damaged.
Click to expand...
Click to collapse
its the 1511 version. Yes the phone worked perfectly after the repair. I was in the US, and three weeks ago I came to colombia. Suddenly it stoped working a couple of days again. I tried the chroma rom. Selected the Auto band. but it did nothing, rebooted and everything but didnt work.
Earlier today i installed a older factory image and it work, i thought it was solved, then i flashed twrp, rooted and lost service again... tried the factory images again and nothing...
Humanreflect said:
Im frustrated...
I bought my nexus 6p six months ago from a guy on ebay. I love the phone really, but one month later i had the battery problem, and i said well, it could happen, i bought a battery and changed it.
and yesterday, i lost signal. its dead. i tried everything in the forums, i locked it, got it back to stock. and nothing...
Now what?, we dont know if its a hardware problem or is it a software one.
Should I take it to a service center in the us? I have no warranty.
Update 06-12-17: so i kept readying and I saw someone solved the issue installing a factory image from febuary. I did it flashed it, then went into recovery and made factory reset. and it worked!!!! signal is backkkk! im soo happy!!!
Update 2 06-12-17: yeah i was happy, and soo i was going back to normal, i installed twrp, and root, phone boot up and again bye bye signal.
Update 06-14-17: Turns out that since I got to Colombia a month ago, this country has like a national IMEI list. Since I didn't subscribe my device the carrier blowies my phone and that why I had no service... Soo this ends my journey with the no service problem. They fixed it
Click to expand...
Click to collapse
Well, I've just checked your latest update today.
What did you do to include your device in this national list? And how did you find out about this list? I need to check if Brazil has it as well. Do you still have signal without problem?
Thanks.
Debuffer said:
Well, I've just checked your latest update today.
What did you do to include your device in this national list? And how did you find out about this list? I need to check if Brazil has it as well. Do you still have signal without problem?
Thanks.
Click to expand...
Click to collapse
Hey, i went to my carrier. And they tol me it was blocked. And they un blocked it.
It was imei blocked because ut wasebt in that imei national list. Soo it didnt work with any carrier.
you've fixed your phone
Humanreflect said:
Im frustrated...
I bought my nexus 6p six months ago from a guy on ebay. I love the phone really, but one month later i had the battery problem, and i said well, it could happen, i bought a battery and changed it.
and yesterday, i lost signal. its dead. i tried everything in the forums, i locked it, got it back to stock. and nothing...
Now what?, we dont know if its a hardware problem or is it a software one.
Should I take it to a service center in the us? I have no warranty.
Update 06-12-17: so i kept readying and I saw someone solved the issue installing a factory image from febuary. I did it flashed it, then went into recovery and made factory reset. and it worked!!!! signal is backkkk! im soo happy!!!
Update 2 06-12-17: yeah i was happy, and soo i was going back to normal, i installed twrp, and root, phone boot up and again bye bye signal.
Update 06-14-17: Turns out that since I got to Colombia a month ago, this country has like a national IMEI list. Since I didn't subscribe my device the carrier blowies my phone and that why I had no service... Soo this ends my journey with the no service problem. They fixed it
Click to expand...
Click to collapse
I can not have a case if you are not resolve. Im vietnames my english very bad sory!. Help me