Related
Hey all,
I have a CWM backup of my current rom and have backups of apps and data but am stuck at a bootloop.
As I have read countless articles, it seems my error is because I have a locked bootloader(not actually sure). Though, I only tried to flash
clockcycle's wiped v20d cwm backup file. It failed part way saying it couldn't write to /system.
Since then, I haven't been able to fully enter CWM. just see the red triangle with the droid guy on his back.
I have read Cmahendra's unbricking guide but it doesn't work as I have installed JB and even the tips to unplug, wait 10s and reopen the program to flash again it still won't work. Still stops at 15% saying error connecting to the phone.
There is a similar thread which had this exact problem which said to
use the online method to recover your phone since I had already installed JB. I edited the hosts file to remove the fake offline server and opened up the b2CAppsetup.exe, clicked on customer support,
entered my model LGP769BK and my S/N and it began to start the process and 'analyze' then crashed and said "updating is not possible any longer due to a fatal error while the LG mobile phone software Update"
I've tried to search this out myself and not waste any space but I'm at loss here. If anyone has any help, it would be much appreciated
as I don't have a phone while this is not working.
I've tried all the ways to to hard reset, master reset and still I get the droid guy on his back. I can get to S/w mode like all the other posts say to do but none of those fixes seem to work for me. Am I missing something?
Do I have any options here? I have kind of read that I should just unlock the bootloader but I don't think that applies in my case as I can't turn on my phone fully.
edit: for the online method(LG support tool), it basically cancels when it goes to the 'downloading' phase --> this is what I've seen as most of the answers but doesn't work
Upon further reading,
many seemed to need to replace their u-boot and x-loader
I did so and installed fastboot using Lelus' script here:
http://forum.xda-developers.com/showpost.php?p=41768774&postcount=1
I used option 6 which allowed me to flash the u-boot and x-loader from p760(works with my 769 and others as it says in the options) for JB
I'm not sure if I needed this as I don't have an unlocked bootloader.
I'm not sure of commands in fastboot but I ran
fastboot devices and it showed something
I also ran: fastboot flash recovery recovery.img
and I put one of my cwm backups in the "yours" folder
After I activate fastboot, it brings me to the C:\fastboot\yours folder
I assume this is for me to put my intended files in but I'm unsure if I should use my cwm backup or something else?
After it flashed the recovery img, I sent a fastboot reboot command
but it still went back to the droid lying down with a red triangle.
As some of you may see, I'm not too great with this but I feel like I'm close. Does anybody have an idea of what I should be doing?
should I flash an update.zip?
I don't know many commands but hopefully this gets me going in the right direction.
PLEASE HELP ME!!!!
I guess your cmw restore formatted your system but couldnt load the new system
the recovery you run with a locked bootloader uses a technique called 2nd init which i think is somewhere stored in the system partition. so when the recovery formatted the system, it lost itself too.
I've had a similar problem. the way out would be booting into the SW upgrade mode--switch off the device, remove the battery, remove the usb cable. press the volume up button and connect the phone to the computer. wait for a couple of seconds and then insert the battery.
you should be in the SW upgrade mode
now use the B2C client. if it gives an option to upgrade, use that otherwise, go to the customer support menu and press recovery phone
I have already done earlier. It may have gotten lost in my frenzy of information. I have put the phone into software mode, as you said, and it won't work either; There's no option to click upgrade because it's JB(V20D) and when I click recovery phone and enter my imei, LG mobile support tool(B2capp.exe) analyzes and then has a 'fatal error'
Since I flashed the new u-boot and x-loader my screens are all backwards/mirrored. Maybe the tool flashed an unlocked u-boot and x-loader if that's possible.
Is a recovery possible by fastboot?
I have a clean and full copy of my cwm recovery as well as apps and data backed up, I just need to get this phone in working order
shockah486 said:
I have already done earlier. It may have gotten lost in my frenzy of information. I have put the phone into software mode, as you said, and it won't work either; There's no option to click upgrade because it's JB(V20D) and when I click recovery phone and enter my imei, LG mobile support tool(B2capp.exe) analyzes and then has a 'fatal error'
Since I flashed the new u-boot and x-loader my screens are all backwards/mirrored. Maybe the tool flashed an unlocked u-boot and x-loader if that's possible.
Is a recovery possible by fastboot?
I have a clean and full copy of my cwm recovery as well as apps and data backed up, I just need to get this phone in working order
Click to expand...
Click to collapse
If you fastboot flash the u-boot and x-loader from p769(ICS) it should go thru with the offline flash detailed in cmahendras guide.
http://forum.xda-developers.com/showthread.php?t=2085344
Use the KDZ_FW_UPD.zip from this thread
Or try this
Remove all of the stuff you have downloaded for this. Download the original B2C client from LG's site and use that
Tablechair said:
If you fastboot flash the u-boot and x-loader from p769(ICS) it should go thru with the offline flash detailed in cmahendras guide.
Click to expand...
Click to collapse
Thanks.I'll try this. if I have the ICS bootloader, does that mean I'll have to flash the V10G kdz? or can i do the v20d kdz
dhruvbatra205 said:
http://forum.xda-developers.com/showthread.php?t=2085344
Use the KDZ_FW_UPD.zip from this thread
Or try this
Remove all of the stuff you have downloaded for this. Download the original B2C client from LG's site and use that
Click to expand...
Click to collapse
I have the updated kdz fw upd .zip from the unbrick and root thread as well as downloaded a new, official B2C client but they all still hang at the download part during phone recovery.
Tablechair, that did the trick.
Is this because the tool we use to flash for the offline method doesn't recognize the x and u-boot loaderse of JB?
After I installed the ICS boot loaders, my software upgrade mode wasn't mirrored anymore.
I did as tablechair and flashed the V20D.
Does anyone understand why this problem happened in the firstplace? Maybe I didn't get a full copy of clockcycle's backup cwm
or should I have not flashed his recovery in the first place since I didn't have an unlocked bootloader?
Again thank you for all your help and if anyone can provide answers to my other supplemental questions, that'd be great.
Off to root and probably unlock bootloader to be sure.
edit: I can't find the thanks button. but thank you very much tablechair. much appreciated. Hope this can help someone else
p.s. also big thanks to those who made the fastboot program for p769(Artas182x and sguerrini97). really an invaluable tool as I now know.
shockah486 said:
Tablechair, that did the trick.
Is this because the tool we use to flash for the offline method doesn't recognize the x and u-boot loaderse of JB?
After I installed the ICS boot loaders, my software upgrade mode wasn't mirrored anymore.
I did as tablechair and flashed the V20D.
Does anyone understand why this problem happened in the firstplace? Maybe I didn't get a full copy of clockcycle's backup cwm
or should I have not flashed his recovery in the first place since I didn't have an unlocked bootloader?
Again thank you for all your help and if anyone can provide answers to my other supplemental questions, that'd be great.
Off to root and probably unlock bootloader to be sure.
edit: I can't find the thanks button. but thank you very much tablechair. much appreciated. Hope this can help someone else
p.s. also big thanks to those who made the fastboot program for p769(Artas182x and sguerrini97). really an invaluable tool as I now know.
Click to expand...
Click to collapse
Things don't always go according to plan, maybe his Clockworkmod backup was made from the touch version and he didn't have artas182x second init recovery installed. So when the cwm failed the first time, did you try to restore your cwm backup?
kuma82 said:
Things don't always go according to plan, maybe his Clockworkmod backup was made from the touch version and he didn't have artas182x second init recovery installed. So when the cwm failed the first time, did you try to restore your cwm backup?
Click to expand...
Click to collapse
Not yet. having problems flashing a kdz again. I've tried the 2 different software modes, as well as setting emerg and diag but still getting stuck at 15% again.
Do i have to replace my uboot and xloader with the ICS ones every time I want to use the offline flash method?
edit: yup, after replacing with ICS loaders again i'm able to flash using software upgrade. will update on whether I can restore cwm
kuma82 said:
Things don't always go according to plan, maybe his Clockworkmod backup was made from the touch version and he didn't have artas182x second init recovery installed. So when the cwm failed the first time, did you try to restore your cwm backup?
Click to expand...
Click to collapse
I realized I misread your question. When I flashed before the incident, it failed to write to system and I didn't restore my other folder. I rebooted and it was all missed up. Anyway, now that I've got everything back and now with an unlocked bootloader, i was able to recover my old image. However, data isn't working so I have to find the radio to flash as I recall reading in other threads.
Can someone explain in laymen terms why this is? recap, i was on unlocked bl rooted jb and I flashed my old cwm backup when I was rooted but had a locked bl. My apps and messages were all there but the radio was different. I'd understand if I was going from ICS to JB but I was on JB both times. The only difference being a locked BL. It's got to be something about the Radio from p760 or V20B that didn't work on my earlier backup or something like that because the layout status bar is different with a "data" button and showing H instead of 4g(which are the same afaik).
Since, I restored to my backup from after my bootloader unlock and root so data is working showing 'H' with the different layout
Also, I had problems backing up and restoring until I noticed that it works better when I power off the phone and do the manual commands to enter recovery as opposed to using the app to send me to recovery(where I incurred /system backup errors).
My last question is which cwm recovery should I use? I currently have the one for a locked bootloader installed as per Artas182x's website. On that post he has a link for an unlocked bootloader recovery on the xda forums but that thread was updated to not working. Are there any disadvantages to me using a locked bootloader cwm recovery?
I don't think I have any option but to try it as I want to flash CM10.1 for p769. I also read that if your bootloader is unlocked, you can download the cwm from the googleplay. If this is true, can I just install over or should I uninstall the Artas182x locked bootloader one????
update: have to remove l9 recovery by deleting the appropriate system folders and then flash the appropriate .img through adb commands
Help.
shockah486 said:
I realized I misread your question. When I flashed before the incident, it failed to write to system and I didn't restore my other folder. I rebooted and it was all missed up. Anyway, now that I've got everything back and now with an unlocked bootloader, i was able to recover my old image. However, data isn't working so I have to find the radio to flash as I recall reading in other threads.
Can someone explain in laymen terms why this is? recap, i was on unlocked bl rooted jb and I flashed my old cwm backup when I was rooted but had a locked bl. My apps and messages were all there but the radio was different. I'd understand if I was going from ICS to JB but I was on JB both times. The only difference being a locked BL. It's got to be something about the Radio from p760 or V20B that didn't work on my earlier backup or something like that because the layout status bar is different with a "data" button and showing H instead of 4g(which are the same afaik).
Since, I restored to my backup from after my bootloader unlock and root so data is working showing 'H' with the different layout
Also, I had problems backing up and restoring until I noticed that it works better when I power off the phone and do the manual commands to enter recovery as opposed to using the app to send me to recovery(where I incurred /system backup errors).
My last question is which cwm recovery should I use? I currently have the one for a locked bootloader installed as per Artas182x's website. On that post he has a link for an unlocked bootloader recovery on the xda forums but that thread was updated to not working. Are there any disadvantages to me using a locked bootloader cwm recovery?
I don't think I have any option but to try it as I want to flash CM10.1 for p769. I also read that if your bootloader is unlocked, you can download the cwm from the googleplay. If this is true, can I just install over or should I uninstall the Artas182x locked bootloader one????
update: have to remove l9 recovery by deleting the appropriate system folders and then flash the appropriate .img through adb commands
Click to expand...
Click to collapse
Although I might be late, I have the same problem and the same phone and I really need help. I have a soft bricked phone lg optimus l9 and I had the same problems that you had exactly... Which is weird exept I don't have Clock Work Mod or anything ... If you get this I would really appreciate some help. Thanks
yup me too
I finally got software upgrade to work with my lg p769 that was security error cuz i still haven't unlocked the bootloader, if i knew what a good job lg and T-Mobile did in locking it i would have waited and got a g3 that my buddy rooted in like 5 min and unlocked the boot....
What worked for me is this LG FLASH TOOL 2014 THREAD ON XDA
http://forum.xda-developers.com/showthread.php?t=2797190
flashed both the 20H and 20D successfully i uninstalled everything lg in the control panel first though.
Hope this works for you cuz i was struggling on and off for a month to get this far lol
the 2014 tool ultimately worked for me too, once I fixed a couple things. I had rooted and forgotten to unlock, so it was at Security Error, and it would also disconnect at 15% .. in the 2014 tool, I had to install all the updates even though I'm in windows 7 or it would keep doing it. All good now.
I have been trying all these methods and I am still not able to get in the S/W upgrade mode. The only thing I am getting from the device is being able to put it fastboot mode (The inverted one). I really want to revive this phone
Thanks in advance for any help given
Liger878 said:
I have been trying all these methods and I am still not able to get in the S/W upgrade mode. The only thing I am getting from the device is being able to put it fastboot mode (The inverted one). I really want to revive this phone
Thanks in advance for any help given
Click to expand...
Click to collapse
Hey, it's been ages since I have done any of this but IIRC, if you can get into fastbood mode u can still get into software mode,
- turn phone into fastboot mode
- open the software upgrader thing as you normally do
- maybe switch emerg to diag or something like that
- this part is where it's slightly different than the normal way(same program but u select a different option than the default 1st option on
I think if yoiu look through the tutorials it does mention an alternative method for getting into software mode
in one instance in my past, i had to reflash the ICS boot drivers so the software installer would recognize that
the flashing of the ICS boot drivers is done through fastboot. Should be a post in my history where I asked a question regarding this.
Sorry for the chaos but maybe this will help you get in the right direction since I don't know any of your phone history and what you've done etc
best of luck mate
shockah486 said:
Hey, it's been ages since I have done any of this but IIRC, if you can get into fastbood mode u can still get into software mode,
- turn phone into fastboot mode
- open the software upgrader thing as you normally do
- maybe switch emerg to diag or something like that
- this part is where it's slightly different than the normal way(same program but u select a different option than the default 1st option on
I think if yoiu look through the tutorials it does mention an alternative method for getting into software mode
in one instance in my past, i had to reflash the ICS boot drivers so the software installer would recognize that
the flashing of the ICS boot drivers is done through fastboot. Should be a post in my history where I asked a question regarding this.
Sorry for the chaos but maybe this will help you get in the right direction since I don't know any of your phone history and what you've done etc
best of luck mate
Click to expand...
Click to collapse
Thanks, Never tried switching to DIAG before but I will try it and let you know what is the outcome.
Hopefully you find the thread that states the exact steps bc that is off the top of my head and over a year ago by memory . GL bud
Liger878 said:
Thanks, Never tried switching to DIAG before but I will try it and let you know what is the outcome.
Click to expand...
Click to collapse
Hey, I have been trying it with the fastboot but it keeps timing out and not allowing me to finish. One thing I should let you know is that, ever since I had put the device in fastboot, I am not able to get back the S/W upgrade mode. Dont know if that will help in seeing what my problem is or if you want me to explain everything from the beginning again, I am more than happy to.
Have you followed the steps that I linked to in the first 3 posts of this thread?
Follow the steps to flash the ICS bootloaders in fastboot and then you can do the fastboot trick for getting the software to recognize your device.
Right now your phone has the JB boot loader on it and is thus not recognized by the software.
recap:
step 1: flash the ICS bootloaders in fastboot (look at the linked thread in post 2)
step 2: use the software in emerg or diag mode but sitll follow the same steps as the tutorial. I think my earlier posts should explain precisely.
if you dont flash the ICS bootloaders, it won't be recognized by the KDZ installer
I exhausted everything by this point so im relying on this forum.
If anyone knows a way to install custom recovery on this phone or just some info in general would be appreciated..
Here's more detailed specs:
LG K8 (K350n)
SoC MediaTek MT6735
CPU Quad-core 1.3 GHz Cortex-A53
GPU Mali-T720
1.5GB Ram
Android 6.0
Help me xda , you're my only hope
Laitas said:
I exhausted everything by this point so im relying on this forum.
If anyone knows a way to install custom recovery on this phone or just some info in general would be appreciated..
Here's more detailed specs:
LG K8 (K350n)
SoC MediaTek MT6735
CPU Quad-core 1.3 GHz Cortex-A53
GPU Mali-T720
1.5GB Ram
Android 6.0
Help me xda , you're my only hope
Click to expand...
Click to collapse
I don't have a solution for you, but I can tell you what I've tried (I have the K350N also) and what doesn't work, for me anyway, so that you don't have to waste a week trying them yourself and get extremely frustrated like I did.
You need a scatter file, so that tools for MTK chips can copy your phone's boot and recovery images. One for the MT6735 exists but is not for the K8 and won't work. Supposedly you can create your own by using block info given by MTK Droid Tools, and manually editing the scatter file, but even the latest version (2.5.3d) does not support the MT6735 and does not give the info needed.
SP Flash Tool needs correct address info (which is gotten from a scatter file), it doesn't seem to take it from your phone. Without it, you'd not be able to pull the correct parts which make up your boot.img and recovery.img, so it's useless without the exact scatter file for your phone (whether it's the same SoC or not).
If you can get Miracle Box to stay connected to your phone, you can try its "Read" function. That didn't work for me, even after dozens and dozens of tries and messing about with different drivers.
Your best bet is probably to try using ADB to get the block/address/size info of the internal partitions, and editing that into a scatter file. Also, apparently the K8 uses a "standard Android" header, not MTK header like older MediaTek chipsets do. (Not quite sure what it means, but knowing so will probably be useful).
That's what I plan to try anyways, and if I manage to do it, I'll post again.
Aerieana said:
I don't have a solution for you, but I can tell you what I've tried (I have the K350N also) and what doesn't work, for me anyway, so that you don't have to waste a week trying them yourself and get extremely frustrated like I did.
You need a scatter file, so that tools for MTK chips can copy your phone's boot and recovery images. One for the MT6735 exists but is not for the K8 and won't work. Supposedly you can create your own by using block info given by MTK Droid Tools, and manually editing the scatter file, but even the latest version (2.5.3d) does not support the MT6735 and does not give the info needed.
SP Flash Tool needs correct address info (which is gotten from a scatter file), it doesn't seem to take it from your phone. Without it, you'd not be able to pull the correct parts which make up your boot.img and recovery.img, so it's useless without the exact scatter file for your phone (whether it's the same SoC or not).
If you can get Miracle Box to stay connected to your phone, you can try its "Read" function. That didn't work for me, even after dozens and dozens of tries and messing about with different drivers.
Your best bet is probably to try using ADB to get the block/address/size info of the internal partitions, and editing that into a scatter file. Also, apparently the K8 uses a "standard Android" header, not MTK header like older MediaTek chipsets do. (Not quite sure what it means, but knowing so will probably be useful).
That's what I plan to try anyways, and if I manage to do it, I'll post again.
Click to expand...
Click to collapse
Well i spend best part of this morning trying to a different aproach , i managed to find a ROM file (in kdz format, whitch woulve been useless for mtk tools anyway) whitch i extracted for a Recovery.img and tried to port the various recovieries with no awail for now. From what i've seen the filesystem inside the rom is a mess some of the files have the MTK headers others have the android ones and I'm trying to make this work entirely by trial and error.. If I'll manage to boot into the recovery I'll let you know. Wish me luck
Ok I managed to make a port from K10 that actually boots to recovery. I'll post updates as I work on it (all trial and error~)
Maybe you will get more luck than me. SuperSu fails to install somethign about failing to decompress ramdisk
Here is the Recovery : https://www.mediafire.com/?xopqenbvgrswgxm
I booted into it using fastboot boot xxx.img command from adb
As I am complete noob when it comes to android modding I'm surprised what I achieved thus far
Laitas said:
Maybe you will get more luck than me. SuperSu fails to install somethign about failing to decompress ramdisk
Here is the Recovery : https://www.mediafire.com/?xopqenbvgrswgxm
I booted into it using fastboot boot xxx.img command from adb
As I am complete noob when it comes to android modding I'm surprised what I achieved thus far
Click to expand...
Click to collapse
what K8 do you have? MTK or Qualcomm Version?
Laitas said:
Maybe you will get more luck than me. SuperSu fails to install somethign about failing to decompress ramdisk
Here is the Recovery :
I booted into it using fastboot boot xxx.img command from adb
As I am complete noob when it comes to android modding I'm surprised what I achieved thus far
Click to expand...
Click to collapse
how you extract the recovery img from the kdz? thanks.
tomi.gutierrez.i said:
how you extract the recovery img from the kdz? thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2600575
Was using this . At this point only thing left is to wait for SuperSU update as it doesnt work on K8 yet
Laitas said:
http://forum.xda-developers.com/showthread.php?t=2600575
Was using this . At this point only thing left is to wait for SuperSU update as it doesnt work on K8 yet
Click to expand...
Click to collapse
i flash the image you give, and it cant mount system, so it cant flash supersu, the lg k10 have the same problem that this recovery (it might be for the port), so we have to wait a super su version for lg k10 and k8 and a functional TWRP
Laitas said:
Maybe you will get more luck than me. SuperSu fails to install somethign about failing to decompress ramdisk
Here is the Recovery : LINK
I booted into it using fastboot boot xxx.img command from adb
As I am complete noob when it comes to android modding I'm surprised what I achieved thus far
Click to expand...
Click to collapse
Can you please show me how to install this recovery on my LG K8 (K350z)
and did you have any luck rooting this phone
all i want is Xposed installed and working but apparently i need root and recovery to install it
Yasser Da Silva said:
Can you please show me how to install this recovery on my LG K8 (K350z)
and did you have any luck rooting this phone
all i want is Xposed installed and working but apparently i need root and recovery to install it
Click to expand...
Click to collapse
I need the same thing like you :c
I dont know how to root my LG K8 in order to install Xposed
Have u found a way to root a lg k8
Maveroik said:
I need the same thing like you :c
I dont know how to root my LG K8 in order to install Xposed
Click to expand...
Click to collapse
Have u found a way to root a lg k8
Declan nalced said:
Have u found a way to root a lg k8
Click to expand...
Click to collapse
Nope man :'c
Laitas said:
Maybe you will get more luck than me. SuperSu fails to install somethign about failing to decompress ramdisk
Here is the Recovery : xxxxxxxxxxxxxxxx
I booted into it using fastboot boot xxx.img command from adb
As I am complete noob when it comes to android modding I'm surprised what I achieved thus far
Click to expand...
Click to collapse
did u managed to unlock your bootloader? From the strategy of rooting HTC, LG also need a bootloader unlock before you having some privilege in flashing recovery... or rooting...
hackwilliam said:
did u managed to unlock your bootloader? From the strategy of rooting HTC, LG also need a bootloader unlock before you having some privilege in flashing recovery... or rooting...
Click to expand...
Click to collapse
That was step 1 you have to go to fastboot form adb and unlock it from there
I've got the k8 us375 model today and its running 6.0 with an update waiting to install. I'm sure it won't matter much but I'm going to avoid updating anytime soon.
With little research into the device I'm reading people trying kingroot and getting stuck with a semi brick and error. From what I've read about marshmallow is the root needs to be accepted from the boot.img which also needs to be insecure.
So unlocking the bootloader is first.
Second is modifying the kernel and
Then recovery needs to be made so that superSu can be flashed.
I'm no expert but neither am i a newbie to this process, however I'm a little rusty. If anyone knows a better way to describe the processes needed please enlighten me. I'll be away from my PC till this weekend but have a laptop i can tinker with tonight. Until i completely understand what needs to be done I'll continue to do research. Thanks
Sent from my LGUS375 using Tapatalk
justlovejoy said:
If anyone knows a better way to describe the processes needed please enlighten me.
Sent from my LGUS375 using Tapatalk
Click to expand...
Click to collapse
I've been trying to root my k8 (k350n) - european version the last few weeks... so far i got:
(here i try to post a url i can't yet... you can find my topic on chinaphonearena - i describe everything there - search "lg k8 k350n twrp" on google - it will be the second result)
the twrp boots but i'm afraid it's not a perfect port so it migth not handling the partitions well... i mean when i try to install supersu i think it cannot find the boot.img (it seems to find but can't patch it).
The newest supersu supposed to patch the boot.img automatically so i believe the only thing we should manage to get a working twrp...
if you want to try i have to warn you that sometimes when i mess with the twrp i have to make a hard reset the get my phone working again. When you boot to the twrp it asks if you want to make your system writeable - you don't have to do that in order to install supersu - however if you allow twrp to make your system writeable you might lose data (i only lost data if i did a format in the twrp but only writeability doesnt clear data in my case...)
edit1:
so i found that supersu can only patch boot images compress by "gzip". The boot im. of our k8 is compress using "lz4" method. I also realized that my twrp works so far as the supersu tries to decompress the boot image... so
We either wait till supersu deals with lz4 or if we could somehow take (dump to pc) the boot image in fastboot "re"compress to gzip - flash back to the device - restart twrp (not boot to android yet - which obviously would not work), install supersu - restart to fastboot take the boot image "re"compress to lz4 and flash the patched boot.img back to the device.
well it's just an idea which actually stucks at dumping the image without root and who knows what other reasons...
or if we knew what tweaks needs to be done to the boot image and we could just make it on pc and flash it in fastboot (i have the stock boot image - i have the whole firmware actually)...
Any advice would be appriciated
Here we go guys...
http://forum.xda-developers.com/lg-k10/how-to/twrp-root-lg-k8-k350n-t3475807
I actually had to return it. It was brand new in the box but the imei was linked to a delinquent account and I couldnt activate it. I'm subscribed if anything.
i know this is a newer phone but i'm still pretty surprised i haven't been able to find anyone that's rooted it yet. i've been all over the internet it seems. this is the :
Samsung Galaxy J3(6)
SM-J320VPP
Android 6.0.1 Marshamllow
Verizon pre-paid plan/network
i see lots of videos and guides for other j320f or j320p (close but no cigar) and nothing works. what i've tried so far:
- Dev mode enabled, USB debugging and OEM unlocked.
- any/all 1 click root apps. none worked, and i'd like to avoid these anyway unless you know it works 100% for my version. at this point i'll try anything.
- recovery / flash superSU. only i haven't even gotten past flashing a recovery. i've tried several different versions of Odin with several different versions of recovery .tar's and for each combination i've tried Odin simply fails. big red FAIL button in upper left corner. sadness. this seems like what i need help with. i have SuperSU downloaded so if i can just get a custom recovery working for my phone i'm hoping it's a simple process from there of booting into the custom recovery and then installing the SuperSU. presto.
is there no hope? is there no tested, confirmed working recovery that i can flash to my phone using Odin? i've tried Odins 3.07, 3.09, and 3.11.1. various custom recovery .tars but the only one i know for sure is the J2 version official from TWRP's website (yes i know it says J2 but someone on another thread said it's similar enough to someone ELSE's model "j320f" or something so i gave it a shot) the other recovery .tars i tried are suspect since they had generic names "recovery.tar" and were downloaded from links provided in many different "guides" that i've googled.
internet, you have failed me. thus do i issue this challenge to all those mighty phone hackers of the land. come forth and slay the evil giant that is my phone's ludicrous security (seriosuly how is this even a thing still in 2016. my phone can do so much more, so much better but for these shenanigans).
thanks so much in advance!
EDIT: not sure about the bootloader. i may be a complete idiot. yes. ok. i'm onto something. gonna post this anyway for any other poor soul that has this version phone, but i think Odin's probably failing because the bootloader is still locked. and Samsung doesn't make this easy like motorola or HTC. T_T. once more into the fray! i'll see if i can't track down a method for unlocking the bootloader on my phone. should i return victorious i'll go ahead and share my steps with the rest of the class.
EDIT2: there is no waking from this nightmare. i dig and dig and dig and can find no root. *sigh*
-- i've got android studio installed. and the java SDK platform-tools which contains the adb.exe, fastboot.exe, etc.
-- something i should explain here: in all these guides whenever there's a step that requires the phone to be connected to the PC, it simply says to, you know...connect your phone. but MY phone by default only uses the cable for battery charging. i have to (on my phone) swipe down from the top, select the "connected for charging" message bringing up "Use USB For" options, then select "Transferring media files" option. THEN my phone shows up both in my windows explorer and displays as a device when i run "adb devices".
--when i run "adb reboot bootloader" this does the same thing as holding down pwr/home/vol down - phone boots up into a blue (teal?) background with a large down arrow in center, below that it says "downloading...do not turn off target". in the upper left are several lines of system font style text:
ODIN MODE
PRODUCT NAME: SM-J320VPP
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP LOCK: OFF*
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, H1, R1, A1, P1*
SECURE DOWNLOAD: ENABLE
*the R's above may be A's or vice versa...hard to read font. sorry
--but as soon as i've rebooted into this mode, my phone disappears from adb devices' list of devices attached. regardless when i run the "fastboot oem unlock" command from the adb shell on my PC at this point i get the infamous "waiting for any device" message and then, of course, nothing....forever. i've also installed PDAnet but i think it's hitting the same road block where my phone is only using the cable for battery charging and i can't toggle that option from ODIN MODE. there's also a "USB Configuration" choice under development options on the phone that has the same options as "Use USB for" but this doesn't stick when booting into ODIN MODE. sadness. i need to retire my brain thoughts at this point. will post TL;DR. you're a saint of geeks if you've made it through my WoT to here.
EDIT3: just an observation - the only thing (so far) that will detect my phone in ODIN MODE is ODIN itself. is there a way to use ODIN to unlock the bootloader?
TL;DR: i think odin is failing when attempting to flash because of locked bootloader. need help with unlocking bootloader first? phone defaults to use USB cable for charging only so i CAN change that to MTP while phone is on normal and then run "adb reboot bootloader" but then phone vanishes from adb devices list once it reboots (and cable is then only charging). thus, cannot run "adb fastboot oem unlock" cuz it hangs displaying "waiting for any device" -- can i unlock the bootloader on this phone? or did i buy a phone that's IMPOSSIBLE TO ROOT!?!?
I have the same problem! I need to root it to install the Patch to change from CDMA to GSM! Because I tried without root and it tells me "E: Signature verification failed"
Thanks
Still nothing?
This is starting to look hopeless
we need the stock recovery.img to be able to mod it and flash it through odin. the recovery for the verizon version does not match so odin wont allow it. i asked on sammobile and they said verizon only releases ota on the device. so idk what to do. perhaps someone with knowledge on this will help.
so far what ive figured out our situation is:
we need root to get root.
more specifically we need root to pull the recovery and then mod that recovery with twrp and use twrp to gain root. The root methods that worked for the other variant SM-J320P dont appear to work for ours, probably due to having android 6.0.1
till we get root we are stuck. the rest is easyish
News?
There is nowbody that had been rooted his J3 Verizon yet?? We need help with this trouble!
In this forum (http://forum.xda-developers.com/android/help/galaxy-j3-sm-j320vpp-configuring-cdma-t3414049) Sergio said:
" try root with this root is only for Snapdragon 410 MSM8916
http://forum.gsmhosting.com/vbb/f723...t1994-1946985/ "
The J320VPP has a "1.2 GHz, Quad-Core". There is no place that sais it's a "Qualcomm Snapdragon 410 Msm:8916" processor. You think this suggestion could work?
NerdmastaX said:
we need the stock recovery.img to be able to mod it and flash it through odin. the recovery for the verizon version does not match so odin wont allow it. i asked on sammobile and they said verizon only releases ota on the device. so idk what to do. perhaps someone with knowledge on this will help.
so far what ive figured out our situation is:
we need root to get root.
more specifically we need root to pull the recovery and then mod that recovery with twrp and use twrp to gain root. The root methods that worked for the other variant SM-J320P dont appear to work for ours, probably due to having android 6.0.1
till we get root we are stuck. the rest is easyish
Click to expand...
Click to collapse
I think I've managed to get the recovery.img with KIES... However flashing the image I've extracted doesn't work but if anyone is ready to help me port a recovery I might try !
Whusky said:
I think I've managed to get the recovery.img with KIES... However flashing the image I've extracted doesn't work but if anyone is ready to help me port a recovery I might try !
Click to expand...
Click to collapse
im gonna try and do a reflash with kies and grab that file myself, ill work a bit on it because i love this phone but no basic root is driving me insane. if you can beat me to posting tell me how you got the file, otherwise ill post here once i find out. I'm not a top of the line developer but i can work my way around and try my best since nobody else is offering to help.
wish me luck.
sorry for the double post but got the files via the verizon software assistant no problem. it ended up in C:\Users\YOURNAME\AppData\Roaming\Verizon_AR\SM-J320VPP_J320VPPVRU1APC3_FACTORY for me, and even decrypted and unzipped itself for me, now we just need to mod a custom thingy into those files and we can work towards rooting. so as i sit here and watch my phone finish flashing back to factory i will look into how we can mod the recovery. if someone is capable of doing it faster i can upload the files very quickly as its only 1.4 gb
well turns out verizon locks the flashing with signature verfication. so unless verizon changes or root is found for marshmellow there will be zero possible root for this phone.
NerdmastaX said:
sorry for the double post but got the files via the verizon software assistant no problem. it ended up in C:\Users\YOURNAME\AppData\Roaming\Verizon_AR\SM-J320VPP_J320VPPVRU1APC3_FACTORY for me, and even decrypted and unzipped itself for me, now we just need to mod a custom thingy into those files and we can work towards rooting. so as i sit here and watch my phone finish flashing back to factory i will look into how we can mod the recovery. if someone is capable of doing it faster i can upload the files very quickly as its only 1.4 gb
Click to expand...
Click to collapse
Hi I'm currently rooted with TWRP 3.0.2 recovery and mabey this might help http://forum.xda-developers.com/general/help/samsung-galaxy-j3-sm-j320fn-how-to-root-t3369511
Sparko612 said:
Hi I'm currently rooted with TWRP 3.0.2 recovery and mabey this might help http://forum.xda-developers.com/general/help/samsung-galaxy-j3-sm-j320fn-how-to-root-t3369511
Click to expand...
Click to collapse
verizon blocks flashing of modified recoveries. so unless someone finds a root exploit for marshmallow we will have no luck.
Has the kingroot method worked for root on your device ??
NerdmastaX said:
we need the stock recovery.img to be able to mod it and flash it through odin. the recovery for the verizon version does not match so odin wont allow it. i asked on sammobile and they said verizon only releases ota on the device. so idk what to do. perhaps someone with knowledge on this will help.
so far what ive figured out our situation is:
we need root to get root.
more specifically we need root to pull the recovery and then mod that recovery with twrp and use twrp to gain root. The root methods that worked for the other variant SM-J320P dont appear to work for ours, probably due to having android 6.0.1
till we get root we are stuck. the rest is easyish
Click to expand...
Click to collapse
Hi to all, im new here and i am having the exact same problem! You say that there has to be a root specifically for the 6.0.. So i found that in the Chainfire page they have this https://download.chainfire.eu/986/CF-Root/CF-Auto-Root/CF-Auto-Root-j3lteusc-j3lteusc-smj320r4.zip already (i dont know if i can post links, so if i cant, sorry), it is marshmallow but the model is J320R4, so i was wondering if this could be the solution. i'll be waiting here for a response, i seriously love this phone :c
MetAJFA said:
Hi to all, im new here and i am having the exact same problem! You say that there has to be a root specifically for the 6.0.. So i found that in the Chainfire page they have this https://download.chainfire.eu/986/CF-Root/CF-Auto-Root/CF-Auto-Root-j3lteusc-j3lteusc-smj320r4.zip already (i dont know if i can post links, so if i cant, sorry), it is marshmallow but the model is J320R4, so i was wondering if this could be the solution. i'll be waiting here for a response, i seriously love this phone :c
Click to expand...
Click to collapse
No, this is not the solution. When using a utlity like CF Auto Root, it must be specific to your model / carrier. Trying to install that will do 1 of 2 things.
1) Just fail in Odin
or
2) Soft brick your device
Since VZW doesn't bother to put out the full firmware files to reflash the device, it's not worth attempting without having the backup plan of the original firmware to flash via Odin.
an twrp is already available for j320p u can try to root your device using it
es0tericcha0s said:
No, this is not the solution. When using a utlity like CF Auto Root, it must be specific to your model / carrier. Trying to install that will do 1 of 2 things.
1) Just fail in Odin
or
2) Soft brick your device
Since VZW doesn't bother to put out the full firmware files to reflash the device, it's not worth attempting without having the backup plan of the original firmware to flash via Odin.
Click to expand...
Click to collapse
Understood, thank very much you for clearing that out. Since all this is pretty much a kick in the butt, do you think there will be some kind of solution to this or should we just lose hope? :/
can Someone here help me with this.
someone wrote:
I have the same problem, I already got 4G LTE data with the correct APN and also I change to lte/gsm with the help of a network app and with commands in adb shell :
pm clear com.android.providers.telephony
settings put global preferred_network_mode 9
settings put global preferred_network_mode1 9
settings put global preferred_network_mode2 9
Click to expand...
Click to collapse
but i dont know how to initiate this adb mode in the phone. anyone?
anyone fix ?
i have few units J320VPP same problem .. searching for service .
That's a Verizon device with a locked bootloader, you cannot try twrp or modified files meant for 320f or other models on this one.
Sent from my SM-N920G using Tapatalk
So has anyone found any luck with this device? It's driving me crazy not having root
EDIT: no longer need this. It is possible to make your own...
There is a chance that I may not have fried my V10 by shorting the test point, but to test that I need a full Nougat dump (something I can not believe I didn't make from my own phone -- I only have a full MM dump).
If there is someone that has rooted Nougat AND flashed all the Nougat partitions (v30b_update.zip and full_nougat.zip), and is willing to do a full dump, please let me know.
It is preferable if you have access to Linux because you will need to null out some partitions that have private data, and it is much easier to explain how to do it on Linux.
Lastly, this image will be 64gigs uncompressed, but it compresses very well.
Thanks,
-- Brian
Wish I can help, but mine is not rooted..
Hopefully I can bring my phone back to life (one way or another) so I can continue on. I got my board of eBay, but it was more dead than my current board.
runningnak3d said:
Hopefully I can bring my phone back to life (one way or another) so I can continue on. I got my board of eBay, but it was more dead than my current board.
Click to expand...
Click to collapse
That sounds bad. Hopefully someone will upload it.
if i can downgrade it , ill re upgrade to rooted nougat and get a dump but i dont know how to dump and dont have the image for downgrade.
@runningnak3d There's a guy selling one in General. Perhaps you can get a dump off of him?
@runningnak3d I currently have one V10 that I cannot get past the Checking Updates screen in the setup wizard on Nougat (with TWRP) which I am considering performing a KDZ wipe and another that went black screen after I flashed MM (also with TWRP). If I do a KDZ wipe on the first one, I could do a dump for you but I would have to look up how to. You are also welcome to buy the board from the second V10 from me but I'm unsure if you can revive it.
Thanks all, but everything I needed to make my own was staring me in the face.
-- Brian
i will help if i can , but didnt have root yet
@runningnak3d I'm in a need of a Nougat dump for H901, to make a bootable sdcard. Could you share yours or guide how to make one from nougat kdz?
Due to messing the aboot partition (while trying to shut the "big cores" off) the phone does not boot, nor enter download mode. On powering on, it only vibrates. QPST does not work with the phone put into 9008, it returns "target may be unstable". Before that, the phone was rooted, with bootloader unlocked, updated to nougat via the recovery, with the ZIPs.
Any help would be greatly appreciated
Be glad to, and it is easy, but you need dd. If you use Windows, there may be some program that can do something similar, but I haven't used Windows in years. You can always install a very basic Cygwin environment...
* Insert 64gig SD card
* Dump KDZ
* dd if=PrimaryGPTxxxxxx of=/dev/mmcblk0
The xxxxx above is because I can't remember what it gets dumped as, but it will be obvious.
Once you have the partition table on the sdcard, get a list of the partitons:
* gdisk -l /dev/mmblck0
Then proceed to flash the rest of KDZ onto their individual partitions.
For example, I believe that modem was partition 1, so:
* dd if=modemxxxxx of=/dev/mmcblk0p1
Repeat for every partition from the KDZ except system (unless you want to fully boot from the SD card). Also, you can flash recovery with TWRP, and then you can boot from the SD card to recovery and then you only need to flash your aboot partition, so you don't have to use download mode to flash the entire KDZ.
Let me know if you need me to clarify anything.
EDIT: If you do boot to recovery from the SD card, you will need to make sure to flash the correct device. When you go into an adb shell, you will have two mmcblk devices (mmcblk0 and mmcblk1). I don't remember which will be which, so to be safe flash the aboot partition on both...
-- Brian
@runningnak3d Thank you for your reply! I have Ubuntu 17 as a bootable DVD. Does the sdcard have to be formatted in a specific filesystem before doing this? Another question I have, is that the sdcard shows up as dev/sdd for me but it also shows that dev/sdd1 exists on it, so to which should I dd the GPT table to?
I tried to dev/sdd and wrote the rest of KDZ to the partitions, but the phone has not booted (its 64gb sd hc class 10 card). After dd-ing the PrimaryGPT, the terminal mentions that backupGPT is corrupted and that MBR is protective on the sdcard. Also, GParted shows "unknown" for each partition, and modem partition shows up as fat16 one.
Perhaps I should try different nougat KDZ? the phone's sticker under battery says it's H901, so was written in the phone under settings menu (phone also had t-mobile bloatware) and in LGUP when updating to MM, yet the motherboard has VS990 written on it.
My phone said vs990 on the board as well, so that isn't the issue. You need to flash a few partitions from the phone that aren't in the KDZ ... you will have to get someone to dump them for you.
The only place I had them was on an SD card that I have already wiped since I don't have a v10 anymore.
I will have to look in SBL1 to get you a list that you will have to ask for.
They are all just firmware, and contain nothing specific to a users phone, so anyone with a rooted Nougat phone can safely dump them for you.
Please bear with me. I am currently trying to revive my H910 and I order an H918 that I am going to use to help someone with, but I will try to get you the info ASAP.
H901 VS990 board 9008 brick help
@runningnak3d Hey, you seem like an expert at unbricking V10s. I have a H901 that has vs990 motherboard in it. It bricked while I was updating through LG Bridge. I now only have access to qualcomm 9008 mode.
From my understanding, there are 2 ways to solve this. QFIL or booting from dump image through sdcard. The qfil way didn't work for me, since there aren't any compatible .mbn files and xml for VS990 owners. So my only other option is getting to download mode via sdcard method, and I need the dump files for that. If I do what you've told @Mr_pringle, would my phone enter download mode? What exactly would I have to do? Thanks
@N3XTN3XUS What version were you on, and what version did LG Bridge try to update you to?
runningnak3d said:
@N3XTN3XUS What version were you on, and what version did LG Bridge try to update you to?
Click to expand...
Click to collapse
mm to nougat. Do you have the dump img for mm by any chance?
Unfortunately you are going to have to roll your own with the instructions I gave above.
In order to do that, you need to find out what model you should be flashing. I know you said your board said VS990, I am sitting here looking at my dead board, and it says VS990 on it as well, so H901 Nougat *should* have worked for you. I don't have any idea where you should start looking, but you do need to know that before making an SD card or even if you make a perfectly good card, it won't work
-- Brian
I am currently trying to root my LG Rebel 3 [L158VL] (Android 7.0)
I've been reading all around and I've installed ADB and Fastboot on my system (Windows 10 Pro 64-bit) however I have not been able to enter fastboot on my phone. If anyone could help me out and walk me through this. I've also been looking into using Lineage OS but they don't seem to support my device (not surprising as it's a Tracfone from Wal-Mart) and I was wondering if there was a version I could use on my phone, I'd appreciate if anyone could help me with that. However, I mostly need help with fastboot.
Any help or advice you can provide will be great, thank you in advanced
- Grey
UPDATE: 11/29/2018 8:34PM
I have tried several other methods but my phone absolutely refuses to boot into fastboot or the bootloader. It's like it's locked and I would like to know if there is a way to unlock/allow my device to boot into what I want it to.
Wasting your time
Tracfone has removed the fastboot and download modes. You still have EDL mode. Adb reboot EDL. However youd still have to unlock the bootloader or have some kind of patched system.img in order to avoid a brick. I cant recall the thread but it did mention the possibility of changing the partition table amd flashing a .laf which is your download mode/bootloader/fastboot.
I also read somewhere where it might be possible to flash using python but that may have been in the files that were from the CIAhttps://github.com/troydo42/CIA-Hacking-Tools mobile security exploits. Tracfone is verizon based so if you could manage to flash it somehow then you should be able to load a verizon rom. Please anyone feel free to expand or correct me.
deshaney said:
Tracfone has removed the fastboot and download modes. You still have EDL mode. Adb reboot EDL. However youd still have to unlock the bootloader or have some kind of patched system.img in order to avoid a brick. I cant recall the thread but it did mention the possibility of changing the partition table amd flashing a .laf which is your download mode/bootloader/fastboot.
I also read somewhere where it might be possible to flash using python but that may have been in the files that were from the CIAhttps://github.com/troydo42/CIA-Hacking-Tools mobile security exploits. Tracfone is verizon based so if you could manage to flash it somehow then you should be able to load a verizon rom. Please anyone feel free to expand or correct me.
Click to expand...
Click to collapse
I think I might remember the thread your're talking about. it required that you used a patched version of lg up that unlocks the dev features and let's you flash the partitions in any order you want. I believe lg up requires the phone to be in download mode but I can't say for sure
Is there away to self root the LG rebel 3?
I want to self root it so I don't have to use my work computer to do so