Well long story short somehow I messed up my build.prop in a process of flashing vendor. Device still boots just fine but I get the annoying "There’s an internal problem with your device. Contact your manufacturer for details" notification every time I reboot.
So my question is:
Is anybody kind enough to upload stock/working build.prop?
Thanks
EDIT: Flashing stock vendor fixed the problem.
Related
Soft bricked G3 with a lost IMEI number
Hey guys I have 2 major problems for my phone.
1) I was trying to flash Marshmallow 30B stock ROM yesterday, so I was told to install a few files. New system file, new modem file, new boot file and SuperSu BETA v2.65. I tried and tried many times yesterday, but unfortunately it didn't work. So I was like "okay fine, let's just use some custom ROM from XDA."
I chose the XenonHD 6.0 Experimental ROM and copied into my internal storage along with my gapps they recommended. I booted up into recovery mode, backed up the installed ROM and factory reset it. I went to flash my ROM first then my gapps. But then halfway flashing the log display showed this:
HTML:
unmount /system failed: No such volume found
updating partition details...
Then it ended saying it was successful and it continued on flashing the gapps and so on. Surprisingly no "unmount /data failed or anything, just the system that is acting up. After finishing flashing all the file, I went to reboot my device. At first it showed the LG logo as usual, then the screen became black. I went online and search all about this unmount system problem, and all they say is that I have to wait for about 10 minutes then the Android logo will come on. So I waited for 15 minutes? (I have an iPad mini beside me counting down the minutes). I came back the whole phone is still black screen, the whole screen is turned off, not idle blank screen. I started to freak out and I took out the battery and put it back again and went into recovery mode.
2) Another problem is this IMEI number loss, I don't know how I got lost this information. I'm not sure if my EFS file is corrupted or not. I realized it because I was receiving no cell signal while I was in the city central. Unfortunately I don't have a backup of the EFS file ( I don't even know if I have it ).
Please help me solve these problems. It's happened for a few days now.
mrchuajason said:
Hey guys I have 2 major problems for my phone.
1) I was trying to flash Marshmallow 30B stock ROM yesterday, so I was told to install a few files. New system file, new modem file, new boot file and SuperSu BETA v2.65. I tried and tried many times yesterday, but unfortunately it didn't work. So I was like "okay fine, let's just use some custom ROM from XDA."
I chose the XenonHD 6.0 Experimental ROM and copied into my internal storage along with my gapps they recommended. I booted up into recovery mode, backed up the installed ROM and factory reset it. I went to flash my ROM first then my gapps. But then halfway flashing the log display showed this:
HTML:
unmount /system failed: No such volume found
updating partition details...
Then it ended saying it was successful and it continued on flashing the gapps and so on. Surprisingly no "unmount /data failed or anything, just the system that is acting up. After finishing flashing all the file, I went to reboot my device. At first it showed the LG logo as usual, then the screen became black. I went online and search all about this unmount system problem, and all they say is that I have to wait for about 10 minutes then the Android logo will come on. So I waited for 15 minutes? (I have an iPad mini beside me counting down the minutes). I came back the whole phone is still black screen, the whole screen is turned off, not idle blank screen. I started to freak out and I took out the battery and put it back again and went into recovery mode.
2) Another problem is this IMEI number loss, I don't know how I got lost this information. I'm not sure if my EFS file is corrupted or not. I realized it because I was receiving no cell signal while I was in the city central. Unfortunately I don't have a backup of the EFS file ( I don't even know if I have it ).
Please help me solve these problems. It's happened for a few days now.
Click to expand...
Click to collapse
i don't claim to be an expert in this field, but there are two things that come to mind that you could look into, maybe ask more experienced ppl on those threads.
it sounds like some sort of partition problem, or corrupt data, maybe you flashed a bad file or a file for another rom.
you could try manually formatting drives in command terminal without mounting them
also unbricking might work too but if your hopes and dreams are in this phone then talk to someone who knows more than me because i wouldn't bet my bankroll on these just suggestions for you to look into. I feel like the guys that write those guides probably can answer your question better and with more confidence.
KronicSkillz said:
i don't claim to be an expert in this field, but there are two things that come to mind that you could look into, maybe ask more experienced ppl on those threads.
it sounds like some sort of partition problem, or corrupt data, maybe you flashed a bad file or a file for another rom.
you could try manually formatting drives in command terminal without mounting them
also unbricking might work too but if your hopes and dreams are in this phone then talk to someone who knows more than me because i wouldn't bet my bankroll on these just suggestions for you to look into. I feel like the guys that write those guides probably can answer your question better and with more confidence.
Click to expand...
Click to collapse
I don't quite know how to do it though but I've been thinking about unbricking my phone and restoring to factory state and start all over again. Do you mind posting a link for the instruction on how to do all this? Thanks
I have the same problem,and i resolve it,try this
http://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012
---------- Post added at 11:33 AM ---------- Previous post was at 11:31 AM ----------
I have the same problem,and i resolve it,try this
http://forum.xda-developers.com/lg-g...ables-t3282012
KronicSkillz said:
i don't claim to be an expert in this field, but there are two things that come to mind that you could look into, maybe ask more experienced ppl on those threads.
it sounds like some sort of partition problem, or corrupt data, maybe you flashed a bad file or a file for another rom.
you could try manually formatting drives in command terminal without mounting them
also unbricking might work too but if your hopes and dreams are in this phone then talk to someone who knows more than me because i wouldn't bet my bankroll on these just suggestions for you to look into. I feel like the guys that write those guides probably can answer your question better and with more confidence.
Click to expand...
Click to collapse
mimivg said:
I have the same problem,and i resolve it,try this
http://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012
---------- Post added at 11:33 AM ---------- Previous post was at 11:31 AM ----------
I have the same problem,and i resolve it,try this
http://forum.xda-developers.com/lg-g...ables-t3282012
Click to expand...
Click to collapse
This was the ROM I initially wanted to flash. I think something went at flashing the Modem causing my phone to have this unmount /system problem.
To whom may help me solve the issues I am facing,
My phone is stuck on the 'Setup wizard has stopped working' and I am not able to flash the original stock rom. Looking up the Setup wizard problem, I came across many posts but none helped. I suspect that the system files of my phone are corrupt. I can't exactly explain why, but it happened. I was trying to uninstall an app (apex launcher) which I had converted to system app. In the end, I had to do a factory reset through recovery.
On booting, I was shown the previously mentioned message and I can't go past it. I can't slide down the notifications nor click any of the soft keys. I tried every solutions posted by other users. This makes me suspect that the system files has become corrupt, and thus the Settings app cannot be opened.
I am new to flashing. I tried to flash the stock rom (RUU - 2gb zip) I found for my a55ml DTUL Europe J15, but it doesn't work. Maybe I need the recovery.img file for it to work? I need some guidance on this one. Can someone send me this recovery.img file?
My phone is rooted (kingroot), bootloader locked, S-ON. And, I can't detect it on ADB. Note: the phone is NOT on bootloop, and boots properly until the 'Setup wizard has stopped working'. I left the phone for flashing at a repair shop, but they tell me they are still trying.
And so, I seek help from anyone who can help me or point me towards someone else who can.
Hey guys, been reading through the threads and not really finding a clear answer or solution to this problem. This is a completely stock sprint sph-l710. I started getting this box with yellow lettering overshadowing the primary display of which I've learned indicates the phone is in 'factory mode'. I thought performing a factory reset would fix this but it did not. I noticed when you boot the phone in recovery mode I see the efs error. I am thinking the underlying issue is with fixing the efs problem. Now that I have reset the phone I no longer have data network access, im guessing because of this factory mode. I am new to this and not real understanding of the lingo everyone uses. From what I've read Im worried im going down a rabbit hole if i start tinkering. I am looking for clear instructions to repair what I think is corrupted software (I'm guessing the operating system software). The instructions I've seen seem to skip steps that are probably rudimentary to everyone else but leaves me without a starting place. I have downloaded oden but i am not certain again without precise instructions that I am not going to permanently mess up my phone.. there appear to be a number of variations of this device and i want to make sure the instructions I get will work on mine. I will take any advise on getting this resolved. I am not opposed to rooting the phone either if that fixes the problem (no idea how to do this, never tried, but some threads on here I think I can follow to do it safely). With that said, different threads also seem to indicate (emphasize 'seem to') that team win recovery can fix this but there are no clear responses regarding my issue of a solid fix. Thank you for any help
timbow4 said:
Hey guys, been reading through the threads and not really finding a clear answer or solution to this problem. This is a completely stock sprint sph-l710. I started getting this box with yellow lettering overshadowing the primary display of which I've learned indicates the phone is in 'factory mode'. I thought performing a factory reset would fix this but it did not. I noticed when you boot the phone in recovery mode I see the efs error. I am thinking the underlying issue is with fixing the efs problem. Now that I have reset the phone I no longer have data network access, im guessing because of this factory mode. I am new to this and not real understanding of the lingo everyone uses. From what I've read Im worried im going down a rabbit hole if i start tinkering. I am looking for clear instructions to repair what I think is corrupted software (I'm guessing the operating system software). The instructions I've seen seem to skip steps that are probably rudimentary to everyone else but leaves me without a starting place. I have downloaded oden but i am not certain again without precise instructions that I am not going to permanently mess up my phone.. there appear to be a number of variations of this device and i want to make sure the instructions I get will work on mine. I will take any advise on getting this resolved. I am not opposed to rooting the phone either if that fixes the problem (no idea how to do this, never tried, but some threads on here I think I can follow to do it safely). With that said, different threads also seem to indicate (emphasize 'seem to') that team win recovery can fix this but there are no clear responses regarding my issue of a solid fix. Thank you for any help
Click to expand...
Click to collapse
Odin will flash the factory firmware for you. Get firmware from sammobile. Look for sph L710 device, and firmware with NJ2 in the name. Put phone in download mode, (power off then hold power+home+volume down) plug in phone to pc. Wait till Odin says added. Click AP in odin, select firmware you downloaded, click start. When it's done, unplug phone, remove battery, put it back in and reboot.
This may not fix your efs partition, but it's the first thing to try.
Odin
I found the thread for nj2 firmware here
issue still persists
Hey Madbat, thank you so much for reaching out to me and giving me the advise. Installing the firmware through odin was really easy. Thank you for that! However, it did not fix the issue. When the phone came back up it still has the exact same problem. I am going to attach a couple pictures to show you what i am seeing... Really appreciate your time and help!
hell, sorry it says im a new user and wont let me post the pictures...
timbow4 said:
Hey Madbat, thank you so much for reaching out to me and giving me the advise. Installing the firmware through odin was really easy. Thank you for that! However, it did not fix the issue. When the phone came back up it still has the exact same problem. I am going to attach a couple pictures to show you what i am seeing... Really appreciate your time and help!
hell, sorry it says im a new user and wont let me post the pictures...
Click to expand...
Click to collapse
Sorry, I never had that issue. Maybe someone else will chime in with experience on the efs partition. That's not a triband s3 is it? (Sph l710t?) T at the end means triband. Second thought, I don't think the firmware would have flashed if it was triband.
How did you wipe your efs?
Its not a tri band. Just SPH-L710. Wish this forum would let me post the pictures of what my phone is doing.. Since the firmware doesnt correct the issue I would think then its a problem with the operating system itself. I have been scouring the web and have found various threads specifically about efs repairs but they entail doing things that seem awful complicated. And i dont know if those things work on my model phone. Maybe rooting the phone gets deep enough to over write or repair the issue. Is there not a way to restore the operating system itself maybe or is that what a replacement ROM does? I am thinking of trying my hand at rooting the phone and seeing what happens. One thread indicated TWRP would backup and restore the EFS file. Im thinking if it backs up a corrupt efs file what good is that, maybe it fixes it too. Found an excellent video on XDA for rooting the S3. Hopefully it or I dont make it worse. Love to get this one fixed but i guess the reality is the phone is old. Thank you for the input
timbow4 said:
Its not a tri band. Just SPH-L710. Wish this forum would let me post the pictures of what my phone is doing.. Since the firmware doesnt correct the issue I would think then its a problem with the operating system itself. I have been scouring the web and have found various threads specifically about efs repairs but they entail doing things that seem awful complicated. And i dont know if those things work on my model phone. Maybe rooting the phone gets deep enough to over write or repair the issue. Is there not a way to restore the operating system itself maybe or is that what a replacement ROM does? I am thinking of trying my hand at rooting the phone and seeing what happens. One thread indicated TWRP would backup and restore the EFS file. Im thinking if it backs up a corrupt efs file what good is that, maybe it fixes it too. Found an excellent video on XDA for rooting the S3. Hopefully it or I dont make it worse. Love to get this one fixed but i guess the reality is the phone is old. Thank you for the input
Click to expand...
Click to collapse
Backing up and restoring it won't help. You already installed a new operating system ( that's what the firmware is).the efs is part of your radios. If I remember correctly it contains your imei and other important things specific to your phone.
You may be out of luck there dude. Don't know how you wiped your efs.
Rooting this phone is simple. Just flash TWRP with Odin. Download the Twrp image from their site. Same as flashing the firmware, only you select recovery instead of AP in odin and select the Twrp image.tar instead of the firmware tar.
https://dl.twrp.me/d2spr/
Use the top on the page. (Newest)
And then use twrp to flash either SuperSU, or Magisk.
Done.
Flashing a custom rom will not fix your issue. You need a working efs. Flashing any operating system will not fix it (you already flashed the whole operating system).
Twrp can restore an efs, but only if you have a working one to backup first. You were right about backing up yours now and restoring will do nothing.
Has it ever been activated?
Prior to this, every once in awhile when i changed a battery out and turned the phone on it would have a pop-up screen tell me something was bad and the phone needed to be reset (something along those lines) and i always just turned the phone back off and on and it booted up fine each time. That may have been an indicator that something, file or system file maybe was corrupted. Then a few week ago when it booted up it started doing this whole thing. Prior to me factory restoring the phone here recently it was completely functional but since the restoration it will no longer connect me to the network. If you goto settings and click on some system features it will turn the network on for that specific function (temporarily) but does not give me any other access. It tells me that the network works but it being blocked (maybe because of the factory mode issue). The wifi works and i can make and receive calls. Still manageable but very annoying. Im going to try your instructions with installing TWRP. If i am successful then maybe i can also get into the system files and possibly restore the broken one.. Thanks again
update
So I have successfully rooted the phone by intstalling TWRP ver 3.2.1 and using TWRP to flash SuperSU ver 2.82. I also installed root explorer to get access to system files. I gained access to the EFS folder and it is empty. So now I'm not understanding if the folder is completely empty how does the phone still work at all? More research led me to a XDA developer that put together a program called EFS Professional which is supposed to backup and restore efs or imei data. Really slick program, basically takes the complication out of locating and backing up the EFS information yourself. (I would include a link but I still cant..) It includes an ADB shell and the ability to make some changes to the phone including directly turning off factory mode . It also had me install an application called BusyBox Pro which is also a very handy tool for getting access to system files. What I don't understand is that the EFS Professional program seems to locate the efs information on my phone and backups it up and then restores it from said backup however when I look at the efs folder its empty. Perhaps not all the efs information is located in the efs folder. And of course since that folder is empty the function of turning factory mode off fails because it cant find the files. I have found a few threads that has very simple instructions once you have super user access you can go right into the efs folder to factory mode and simply turn it off. Mine is empty.. So again the problem continues. Possibly with access to the ADB shell and more help from folks on here I can figure out a way to restore my efs information. I don't know if the efs information can be used from a another same model phone, I'm guessing not if it has a specific imei identification. Im working hard on this but still unsolved. I know way more at this point then I did but I think I still know just enough to be dangerous. Thankfully my phone is still functional at this point..
Ok, So Here's The Deal.. The Thing.. The WTF
So I had an older version of the Scorpion ROM installed and working fine for a while and wanted to change it up. I downloaded the newest TWRP. Both image and installer.zip, newest Magisk and RR 7.
I flashed the latest stock and you know, followed all the proper steps and after I flashed RR 7, it wouldn't boot up. (Not the issue) as others have had the same issue with RR 7. I left a post about that on the RR 7 thread and went about reflashing stock and proceeded to find a different ROM to check out.
No matter what I try to flash: Lineage, Scorpion, RR 7, dotOS the same thing happens... Everything flashes like it should, but then it won't boot, AND THEN every time I boot back to TWRP to try something else the haptic feedback vibration thing on the pixel 3 xl goes banana sandwich crazy and won't shut off until I reboot to fastboot to flashall to start over. LOL
And not only that but when I jump back to TWRP to try to flash something else stored on the phone, it says the storage is empty and there are nothing available in the menu. And I couldn't get a screenshot but there were some errors that have popped up in twrp as well...
Could This Be An Issue WITH TWRP itself? Because it does it with every single ROM I have flashed today. It's very strange. I have never ran into any issues like this when flashing ROMs, Kernals, etc.
I'm lost. Any help would be awesomely appreciated.
UPDATE: It now vibrates constantly in TWRP and when I reflashed to factory it did the corrupt software screen so I gave it a good ole' factory rest and then it was is stuck in a loop at the G while conecting and disconnecting to the USB over and over and over... now back to corrupt software screen.
I guess I'm just going to have to reflash Stock and just leave it.
Update 2: Still Give The Corrupt Software Thing After Performing FlashAll - soooooooooooooooo
Slo-mo Designs said:
Ok, So Here's The Deal.. The Thing.. The WTF
Could This Be An Issue WITH TWRP itself? Because it does it with every single ROM I have flashed today. It's very strange. I have never ran into any issues like this when flashing ROMs, Kernals, etc. I'm lost. Any help would be awesomely appreciated.
UPDATE: It now vibrates constantly in TWRP and when I reflashed to factory it did the corrupt software screen so I gave it a good ole' factory rest and then it was is stuck in a loop at the G while conecting and disconnecting to the USB over and over and over... now back to corrupt software screen.
I guess I'm just going to have to reflash Stock and just leave it.
Update 2: Still Give The Corrupt Software Thing After Performing FlashAll - soooooooooooooooo
Click to expand...
Click to collapse
Couple of things. Yes there was an issue with v3.2.3-4 TWRP and the vibrator, but that is separate from your boot issues. Go to the dedicated TWRP thread. As for your updates, 1) an FDR just deletes your data and so would not solve your issue. and 2) Guessing you removed the -w switch from the flash-all script or you would not be getting the corrupt software screen. Run the script again with the wipe switch in place, allowing it to wipe your partitions and start over. You've already deleted all your data with the FDR so it won't matter. Best of luck!
Always late to the party.
v12xke said:
Couple of things. Yes there was an issue with v3.2.3-4 TWRP and the vibrator, but that is separate from your boot issues. Go to the dedicated TWRP thread. As for your updates, 1) an FDR just deletes your data and so would not solve your issue. and 2) Guessing you removed the -w switch from the flash-all script or you would not be getting the corrupt software screen. Run the script again with the wipe switch in place, allowing it to wipe your partitions and start over. You've already deleted all your data with the FDR so it won't matter. Best of luck!
Click to expand...
Click to collapse
So yeah... I just now logged back on and saw your response [I have had notification issues on everything from Reddit to FB since I have had the 3XL]
About the response, I have had the issue with it showing the corrupt software screen a bunch when flashing new stuff. The reason I perform the Factory Slap is because it allows me to enter the menu where I have the option to "Boot from ADB" or whatever it says, sideloading seems to be the only way I can make progress when it starts giving the corrupt error.. The reason I didn't perform the full wipe but I can't remember exactly why now since that was over a month ago.
But I finally got it fixed, and I was going to repost because I had found a way to prevent the vibration thing from happening in TWRP but by the time I got around to posting, the new update had fixed it. Lol
Like in title.
I have nexus 7 with stock rom 6.0.1 MOB30D.
Everything is ok it works good. But I can’t restart it. When I do he start to boot loop when loading apps.
When it’s done 56/56 apps he restart and do it again... and again. I think the problem is that in the past I was trying to use custom roms and use repartition (zip file) to increase system partition. And I didn’t undo this process. But I don’t want to use custom rom because I can’t use Netflix... :/ so... now I don’t know how to fix this. I can turn on my tablet ONLY when the system is new and turn on first time. Second time he just boot loop. .
Sorry for bad English.
Victrim said:
Like in title.
I have nexus 7 with stock rom 6.0.1 MOB30D.
Everything is ok it works good. But I can’t restart it. When I do he start to boot loop when loading apps.
When it’s done 56/56 apps he restart and do it again... and again. I think the problem is that in the past I was trying to use custom roms and use repartition (zip file) to increase system partition. And I didn’t undo this process. But I don’t want to use custom rom because I can’t use Netflix... :/ so... now I don’t know how to fix this. I can turn on my tablet ONLY when the system is new and turn on first time. Second time he just boot loop. .
Sorry for bad English.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=76278047&postcount=19 - is it the script you had used for repartition? If so, note... "The script will create a backup of your original gpt partition table and a log file in the root of internal storage. If you have any issues, post the log."
Well, post the log.
If you had erased the original log(s) or if you had used a different script/zip then provide more info and do sysrepart-log.zip from https://forum.xda-developers.com/showpost.php?p=79898852&postcount=69