Related
OK. So I hard bricked my Boost LG Volt 2 (LS751).
I tried a hard reset with no luck.
I am looking for a rom, stock, custom, rooted or not, that will work with a boost Volt 2.
I know how to flash a rom using the LG Flash Tool, given appropriate .dll and .tot files.
If other methods are easier please let me know how to use them, roughly.
Me too
I am having this same problem! Need stock rom. I can't believe there isn't one out there. I really hope someone can help.
I have stock build prop and update zip
I have the stock prop build and dump file
Need know if I made the file flashable
Build.prop
Jaywill2020 said:
I have the stock prop build and dump file
Need know if I made the file flashable
Click to expand...
Click to collapse
Think you can send me the stock build.prop? Email is [email protected]
.prop file
Can I flash my bricked phone using the .prop file?
chrispenn said:
OK. So I hard bricked my Boost LG Volt 2 (LS751).
I tried a hard reset with no luck.
I am looking for a rom, stock, custom, rooted or not, that will work with a boost Volt 2.
I know how to flash a rom using the LG Flash Tool, given appropriate .dll and .tot files.
If other methods are easier please let me know how to use them, roughly.
Click to expand...
Click to collapse
I did this too. Mine is on its way back from LG. They repaired it free of charge add it's still under warranty. I did a factory reset through recovery mode as to erase any traces that i rooted it and they had no clue. It's been about a week and I'll have it back in a couple days. Good luck!
try this one. worked for me. stylo has the same chip as volt 2 (LS751)
http://forum.xda-developers.com/android/development/guide-how-to-root-lgls770-5-1-1-t3184649
Build.prop
Jaywill2020 said:
I have the stock prop build and dump file
Need know if I made the file flashable
Click to expand...
Click to collapse
Can you email me the stock build prop?
Can u upload the files many ppl could really use it
i also need build.prop.
Jaywill2020 said:
I have the stock prop build and dump file
Need know if I made the file flashable
Click to expand...
Click to collapse
can you please upload the files you have somewhere? even if its just the update.zip please?
there is too many files there
i heard that they make from these files flashable firmware
and there is one for the ls751
any one have idea how to deal with this ?
this is the link :
opensource.lge(dot)com/osList/list?curPage=2&m=Mc001&s
stock tot zv4 ls751
http://xda-android-free.blogspot.in/2016/05/ls751-volt-2stock-tot-rom-lg-volt-2.html
gdeepp said:
http://xda-android-free.blogspot.in/2016/05/ls751-volt-2stock-tot-rom-lg-volt-2.html
Click to expand...
Click to collapse
Why would someone pay you for a password to this file? No one even knows if it's an actual tot file for this device.
hiiiiii
creativetrendz said:
Why would someone pay you for a password to this file? No one even knows if it's an actual tot file for this device.
Click to expand...
Click to collapse
i use this dear
gdeepp said:
i use this dear
Click to expand...
Click to collapse
Yea, sure...
just so you guys know, i beleive that downgrade from ZV4 to ZV5 bricks the phone.
Thank you
onmyroute said:
try this one. worked for me. stylo has the same chip as volt 2 (LS751)
http://forum.xda-developers.com/android/development/guide-how-to-root-lgls770-5-1-1-t3184649
Click to expand...
Click to collapse
It worked for my Virgin Mobile. Thank you!
مرحبا
i am having rom
your ls751 is on zv4 or zv5?
A2017G B02 successfully flashed and booted on A2017U (using update.zip). WiFi/Bluetooth and GPS working. Only broken piece is the cellular.
There are a few more color choices in themes but no 'Android Stock' theme. And a glove mode which would likely be useful here in northern Canada.
This should be good news for development as there appears to be only the modem differentiating the ROMs.
Now to see how well I can return to A2017U [UPDATE] Returning to A2017U I had to delete my call logs. The database version was newer in the A2017G, and it created a launcher crash loop. I used titanium backup to delete the call logs.
Don't do this. You could quite likely brick. But if you're going to anyway:
Point 1 : If this doesn't make sense to you, don't do it; you're in over your head.
Get a backup of ALL of your partitions using dd.
I copied the A2017G B02 update.zip to the root of my SD card, and flashed the recovery.img from that update.zip overtop of TWRP from within TWRP using dd. Refer to Point 1. Booted the phone to system, went to updates, and did the factory update from root of SD card. Remember, you will be stock A2017G which means no root/TWRP. You will have to use the method here assuming you now have an A2017G to get TWRP back on the device. I then flashed my NON-HLOS.bin from the backup I made earlier over modem partition.
The launcher sucks more than the stock one on A2017U as there is no menu button.
I believe you could just flash system.img (system.new.dat) and boot.img to get the same experience as that's the only two I flashed to return to A2017U (I had to flash NON-HLOS.bin back to A2017U).
Really good to know, so it should be also possible reversely and a ray of hope to unlock the G version somehow
Nice work! I guess this answers my questions as to whether the flash would unlock the different bands not included on the north American variant
Someone flash the U version to G please since the U version is a lot better than G atm haha
cctbrkr said:
Nice work! I guess this answers my questions as to whether the flash would unlock the different bands not included on the north American variant
Click to expand...
Click to collapse
Well, that would be part of the modem part, which isn't the same. The only way to get that to happen would be to use the QC recovery tools that let you tinker in the actual modem bits.
rikin93 said:
Someone flash the U version to G please since the U version is a lot better than G atm haha
Click to expand...
Click to collapse
Unfortunately, we can't do that well since there aren't any U factory images yet. It would have to be cobbled together from backups people make of all the different partitions, and even then it would have to be done via a bootloader unlocked version, which is only the U model.
Com' on ZTE -- release those factory images.
Hmm so that still sounds promising. Obviously we won't get hands on the recovery tool though?
jkuczera said:
A2017G B02 successfully flashed and booted on A2017U (using update.zip). WiFi/Bluetooth and GPS working. Only broken piece is the cellular.
There are a few more color choices in themes but no 'Android Stock' theme. And a glove mode which would likely be useful here in northern Canada.
This should be good news for development as there appears to be only the modem differentiating the ROMs.
Now to see how well I can return to A2017U
Click to expand...
Click to collapse
Can you try something before you switch back? If you have a good router (ac, multiple streams, 5ghz) can you check your link speed? You can use an app like aida64 to spit that info out in the network tab. The reason I ask, is because 2017U (actual models not software) reports 433Mbps being the max, while 2017G reports 866Mbps. We are trying to figure out if the US model got the cheaper wifi chip or if they screwed up the code.
test878 said:
Can you try something before you switch back? If you have a good router (ac, multiple streams, 5ghz) can you check your link speed? You can use an app like aida64 to spit that info out in the network tab. The reason I ask, is because 2017U (actual models not software) reports 433Mbps being the max, while 2017G reports 866Mbps. We are trying to figure out if the US model got the cheaper wifi chip or if they screwed up the code.
Click to expand...
Click to collapse
Yepper
jkuczera said:
Yepper
Click to expand...
Click to collapse
Nice to know that it's just a software thing.
Can you also try going far from your router, into an area with low signal, and turn on the "Signal Boost" option? Would be interesting to see if that's another software thing.
xtermmin said:
Nice to know that it's just a software thing.
Can you also try going far from your router, into an area with low signal, and turn on the "Signal Boost" option? Would be interesting to see if that's another software thing.
Click to expand...
Click to collapse
From the graphic on 'signal boost', it's for cellular (telephony) only. Wifi is not pictured or mentioned.
jkuczera said:
From the graphic on 'signal boost', it's for cellular (telephony) only. Wifi is not pictured or mentioned.
Click to expand...
Click to collapse
Ah, bummer, thanks for checking.
Wonder if there's a way to obtain the NON-HLOS.bin modem from a 2017U unit...
xtermmin said:
Wonder if there's a way to obtain the NON-HLOS.bin modem from a 2017U unit...
Click to expand...
Click to collapse
Just flashed the modem.img from my A2017U backup and now telephony is working as well.
jkuczera said:
Just flashed the modem.img from my A2017U backup and now telephony is working as well.
Click to expand...
Click to collapse
Holy snap, Chief post steps and where you got these files, wanna give it all try old.
jkuczera said:
Just flashed the modem.img from my A2017U backup and now telephony is working as well.
Click to expand...
Click to collapse
So, you're running the 2017G with the U modem?
DrakenFX said:
Holy snap, Chief post steps and where you got these files, wanna give it all try old.
Click to expand...
Click to collapse
With root, you should be able to dd or cat out all of the partitions from a root shell. Then you can backup all of the partitions as they exist in flash (blank space and all).
TeutonJon78 said:
With root, you should be able to dd or cat out all of the partitions from a root shell. Then you can backup all of the partitions as they exist in flash (blank space and all).
Click to expand...
Click to collapse
Only problem I have is not knowing their extension , I know how to use "dd" but isn't a issue dumping without the right extension? (.img, .bin, etc) and I meant I How-To guide for others users if they wanna try.
TeutonJon78 said:
So, you're running the 2017G with the U modem?
Click to expand...
Click to collapse
Yes
DrakenFX said:
Holy snap, Chief post steps and where you got these files, wanna give it all try old.
Click to expand...
Click to collapse
Refer to updated OP
DrakenFX said:
Only problem I have is not knowing their extension , I know how to use "dd" but isn't a issue dumping without the right extension? (.img, .bin, etc) and I meant I How-To guide for others users if they wanna try.
Click to expand...
Click to collapse
DD does not care about file extensions. It also doesn't care if you should flash to the wrong partition and permanently brick your device.
jkuczera said:
Just flashed the modem.img from my A2017U backup and now telephony is working as well.
Click to expand...
Click to collapse
Where did you take the modem.img from for the a2017u?
manu7irl said:
Where did you take the modem.img from for the a2017u?
Click to expand...
Click to collapse
Code:
adb shell
su
dd if=/dev/block/bootdevice/by-name/modem of=/sdcard/modem.img
and to pull to your adb directory
adb pull /sdcard/modem.img
Or use " modem_a2017u.img " To knowlage is from a2017u
DrakenFX said:
To knowlage is from a2017u
Click to expand...
Click to collapse
Could you post it here please.
manu7irl said:
Could you post it here please.
Click to expand...
Click to collapse
Will be easier for you just to pulled using your a7 using the command line from previous post.
So I tried to root my phone and screwed it up (it was stuck on the Samsung boot screen).
Then I installed TWRP to try and recover it, but being the idiot I am I just ended up deleting the OS.
Now I don't know what to do, please help me.
Edit:
I have managed to fix this with the help of a user below!
What I did (for other users having this issue):
I downloaded the firmware for my device from Updato (link here).
Then used Odin 3 (version 3.12) and loaded the downloaded firmware into the AP slot.
I had to plug my device into the wall to allow it to charge (connecting it directly to my PC did not work), then I booted it up (it was stuck in the Samsung logo screen for a long while, but then it went into the setup).
DNeeded said:
So I tried to root my phone and screwed it up (it was stuck on the Samsung boot screen).
Then I installed TWRP to try and recover it, but being the idiot I am I just ended up deleting the OS.
Now I don't know what to do, please help me.
Click to expand...
Click to collapse
Use ADB file transfer using the fast boot command line. Then download a flashable zip rom and push it to your device then flash, you also want to get gapps if you want to have Google play.
Sent from my iPhone using Tapatalk
doughmay said:
Use ADB file transfer using the fast boot command line. Then download a flashable zip rom and push it to your device then flash, you also want to get gapps if you want to have Google play.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Hi man.
I'm sorry, but I am a real noob and not sure where to download a "flashable zip rom" from.
DNeeded said:
Hi man.
I'm sorry, but I am a real noob and not sure where to download a "flashable zip rom" from.
Click to expand...
Click to collapse
I'm very worried about this.
Also other solutions say to download the right firmware for my region from websites like SamMobile but my country isn't listed anywhere.
Sorry if I am giving unneeded information, but I am seriously stressed over this.
DNeeded said:
I'm very worried about this.
Also other solutions say to download the right firmware for my region from websites like SamMobile but my country isn't listed anywhere.
Sorry if I am giving unneeded information, but I am seriously stressed over this.
Click to expand...
Click to collapse
Did you search for SM-P355 ?
What country do you need for?
tys0n said:
Did you search for SM-P355 ?
What country do you need for?
Click to expand...
Click to collapse
Yes and my country is New Zealand.
DNeeded said:
Yes and my country is New Zealand.
Click to expand...
Click to collapse
Yeah, can't find anything either. You're sure it's SM-P355?
Can you go to download mode and check model number?
tys0n said:
Yeah, can't find anything either. You're sure it's SM-P355?
Can you go to download mode and check model number?
Click to expand...
Click to collapse
Just did and it says:
Product name: SM-P355
Click to expand...
Click to collapse
DNeeded said:
Just did and it says:
Click to expand...
Click to collapse
Maybe it's imported from another country then. I really don't know.
Do you remember what csc it had before wipe?
You can probably flash firmware from any country as long as it's unbranded. (not carrier specific)
I've done it a lot on all my phones to get the latest updates faster. I've had no problems at all.
tys0n said:
Maybe it's imported from another country then. I really don't know.
Do you remember what csc it had before wipe?
You can probably flash firmware from any country as long as it's unbranded. (not carrier specific)
I've done it a lot on all my phones to get the latest updates faster. I've had no problems at all.
Click to expand...
Click to collapse
No idea what the CSC was.
I will try installing another regions firmware.
You think I'll be able do that and then use Kies emergency firmware recovery to reinstall the original firmware? (Sorry if that doesn't make sense, again I don't really know what I am doing).
Appreciate your help mate.
tys0n said:
Maybe it's imported from another country then. I really don't know.
Do you remember what csc it had before wipe?
You can probably flash firmware from any country as long as it's unbranded. (not carrier specific)
I've done it a lot on all my phones to get the latest updates faster. I've had no problems at all.
Click to expand...
Click to collapse
Hey! I just managed to download the firmware from Updato and I am very relieved to let you know that I was able to boot up the tablet and it worked successfully!
All my files are gone, but that's alright, I deserve that for being and idiot and screwing up in the first place!
Just some final questions: Since the firmware region is "Indonesia", what exactly does this mean?
From my Google searches I see that firmware region doesn't mean much, just a few settings are different (such as having the language automatically on Indonesian). Is this true, or will I encounter any issues regarding this, since I am in a different region?
I appreciate your help and advice! You are a very good person and a valuable member of this community.
Thank you!
Good you got it going, and thank you for your kind words
You're right. It's mainly just small regional differences and as long as the phone/tablet isn't locked to specific carrier it usually works just fine with any csc.
I got the Verizon Note 8 and flashed the T-Mobile firmware using the carrier change tutorial here. It has all the T-Mobile branding but it still has traces of Verizon:
1. download mode has CSC of VZW
2.settings -> about phone service provider SW ver it says TMB/TMB/VZW
How do I get those 2 changed to TMB so it is 100% like a phone that came from T-Mobile?
The 3rd code is the original CSC for the phone & can't be changed.... well unless you have root you can try.
Why do you want to change it? It won't really affect anything.
Do have root that doesn't break the Knox flag?
Generally yes but I don't know what variant you have. Assuming you have a US U variant then no but the current root method has other drawbacks to be considered.
shouren04 said:
Generally yes but I don't know what variant you have. Assuming you have a US U variant then no but the current root method has other drawbacks to be considered.
Click to expand...
Click to collapse
Us 950U
What other drawbacks?
bogdi1988 said:
Us 950U
What other drawbacks?
Click to expand...
Click to collapse
Read disclaimer 3 for SamFAIL, you'll have decide if they are drawbacks for you.
shouren04 said:
Read disclaimer 3 for SamFAIL, you'll have decide if they are drawbacks for you.
Click to expand...
Click to collapse
Thanks! I'll look! If I end up rooting, how do I get the other 2 variables changed in the CSC?
bogdi1988 said:
Thanks! I'll look! If I end up rooting, how do I get the other 2 variables changed in the CSC?
Click to expand...
Click to collapse
I'm not sure exactly, I never looked into it much. IIRC you have to edit nv files in the efs folder. Mine is TMB/TMB/XEF, I never cared really as there's no reason to try & change it. The first 2 are all that really matters.
If you follow the guide correctly you can completely change your phone to a different carrier. I got my Note8 from Xfinity, canceled service and got it unlocked. I followed the guide here and now have a phone with firmware exactly the same as a Verizon Note8, no traces of the Xfinity firmware.
hann1balk1ng said:
If you follow the guide correctly you can completely change your phone to a different carrier. I got my Note8 from Xfinity, canceled service and got it unlocked. I followed the guide here and now have a phone with firmware exactly the same as a Verizon Note8, no traces of the Xfinity firmware.
Click to expand...
Click to collapse
You misunderstood my question . I already have that and followed the guide but there is still a small remnant of the old carrier. Look in your about section on your phone.
Everything looks fine, wanna take a screenshot and show me what youre talking about?
See attached
bogdi1988 said:
See attached
Click to expand...
Click to collapse
This last CSC code is hardcoded in the device to show where was originally bought it will never change without root.
Easy fix if you're rooted....but not worth rooting if that's all you want to change....however you could root, then change the value and then return to stock unrooted and the setting will stick.
Sent from my SM-N950U using XDA-Developers Legacy app
louforgiveno said:
Easy fix if you're rooted....but not worth rooting if that's all you want to change....however you could root, then change the value and then return to stock unrooted and the setting will stick.
Sent from my SM-N950U using XDA-Developers Legacy app
Click to expand...
Click to collapse
How do I change it if I root? That was my initial plan - root, fix, unroot.
bogdi1988 said:
How do I change it if I root? That was my initial plan - root, fix, unroot.
Click to expand...
Click to collapse
Edit the 3 letter code in the sales_code.dat (the one in the carrier folder phone is)
Example i have a tmobile branded phone to change i would navigate to /system/omc/TMB/etc and in the "etc" folder open sales_code.dat with text editor and change the 3 letter code to what you want.
louforgiveno said:
Edit the 3 letter code in the sales_code.dat (the one in the carrier folder phone is)
Example i have a tmobile branded phone to change i would navigate to /system/omc/TMB/etc and in the "etc" folder open sales_code.dat with text editor and change the 3 letter code to what you want.
Click to expand...
Click to collapse
Thank you!
Does that also fix the bootloader info? When you go into download mode, it shows VZW there also.
bogdi1988 said:
Thank you!
Does that also fix the bootloader info? When you go into download mode, it shows VZW there also.
Click to expand...
Click to collapse
I don't know about that....maybe someone else can answer...
bogdi1988 said:
Thank you!
Does that also fix the bootloader info? When you go into download mode, it shows VZW there also.
Click to expand...
Click to collapse
This information is stored in the EFS partition as this code is the original provider of the phone.
You can change it but is a bit risky losing IMEI.
I dont know how. This might help
https://forum.xda-developers.com/showthread.php?t=2670084
And this
https://forum.xda-developers.com/galaxy-s8/how-to/switch-to-carrier-firmware-100-t3609487
louforgiveno said:
Edit the 3 letter code in the sales_code.dat (the one in the carrier folder phone is)
Example i have a tmobile branded phone to change i would navigate to /system/omc/TMB/etc and in the "etc" folder open sales_code.dat with text editor and change the 3 letter code to what you want.
Click to expand...
Click to collapse
Have you tried that & does it actually change the 3rd CSC? Cause that's not the way to change it that I'm aware of. My sales_code.dat is TMB but my 3rd CSC has always been XEU.
bogdi1988 said:
How do I change it if I root? That was my initial plan - root, fix, unroot.
Click to expand...
Click to collapse
I could be wrong but I don't think you can root, make changes, then unroot & keep the changes.
---------- Post added at 12:56 PM ---------- Previous post was at 12:52 PM ----------
holifo said:
This information is stored in the EFS partition as this code is the original provider of the phone.
You can change it but is a bit risky losing IMEI.
I dont know how. This might help
https://forum.xda-developers.com/showthread.php?t=2670084
And this
https://forum.xda-developers.com/galaxy-s8/how-to/switch-to-carrier-firmware-100-t3609487
Click to expand...
Click to collapse
The 3rd CSC is stored in the EFS partition but it's not the ones in /efs/imei, I believe the third CSC is stored in the nv files & I think the 3rd CSC is the same as what shows up in download mode.
I still don't understand why the OP wants to change this, it won't really affect anything.
Need Oeminfo(C567) backup with TWRP BLA-A09
thanks
oeminfo is useless
salland said:
oeminfo is useless
Click to expand...
Click to collapse
for what it is useless?
if you have, share
Oeminfo
geogsm_1 said:
for what it is useless?
if you have, share
Click to expand...
Click to collapse
Nobody is going to share a backup containing their oeminfo containing their IMEI or serial numbers.
revjamescarver said:
Nobody is going to share a backup containing their oeminfo containing their IMEI or serial numbers.
Click to expand...
Click to collapse
and it is bad then I should not share? the experience?
Sharing oeminfo
geogsm_1 said:
and it is bad then I should not share? the experience?
Click to expand...
Click to collapse
Anything that contains that information should never be shared unless you don't care that your device could be "cloned" using that information. It's generally not a good idea.
revjamescarver said:
Nobody is going to share a backup containing their oeminfo containing their IMEI or serial numbers.
Click to expand...
Click to collapse
geogsm_1 said:
and it is bad then I should not share? the experience?
Click to expand...
Click to collapse
And not just that. Your unlock code is calculated based on the IMEI in oeminfo, if it changes so does your unlock code.
And as it is now (Not sure if this is the case of C567 too), you can only get an unlock code if oeminfo is intact, as it's generated using your IMEI.
So don't use someone elses oeminfo if you still want to be able to unlock.
revjamescarver said:
Anything that contains that information should never be shared unless you don't care that your device could be "cloned" using that information. It's generally not a good idea.
Click to expand...
Click to collapse
It doesn't use the info in oeminfo for your phones actual IMEI. That's in one of the nv partitions.