Hello all, I've made a bit of a balls up and appear to have deleted the bootloader on my G3 (D855) when I tried to install TWRP. Every time I start the phone or try to get in to the bootloader I end up on the TWRP screen. I have ADB access but I have no idea where to start to recover from this. I think I may installed twrp-2.8.0.0_d855-signed.img instead over the bootloader. Is that even possible?
Any help or advise will be greatly appreciated.
Cheers,
Peter
I do the Same things first time i flash twrp.
Reflash à kdz with flashtool save me.
Tapatalked
Actually, its not what I thought. I've managed to get in to the original bootloader. So the question is why is it taking me to TWRP screen all the time?
LonPete67 said:
Actually, its not what I thought. I've managed to get in to the original bootloader. So the question is why is it taking me to TWRP screen all the time?
Click to expand...
Click to collapse
if u flashed it via flashify maybe u chose kernel.img instead of recovery
I think you're right, but how do I get do I fix it? I've manged to reflash a ROM and it says it worked but I always end up at the TWRP screen after a reboot.
LonPete67 said:
I think you're right, but how do I get do I fix it? I've manged to reflash a ROM and it says it worked but I always end up at the TWRP screen after a reboot.
Click to expand...
Click to collapse
You've reflashed a kdz?
Btw, this should be in Q&A not in development
Please do not post non development related threads in the development section
Questions belong in the Q&A section
Thread moved
Klyupp said:
You've reflashed a kdz?
Btw, this should be in Q&A not in development
Click to expand...
Click to collapse
I've got the kdz file but I'm not sure how I would do that via ADB?
LonPete67 said:
I've got the kdz file but I'm not sure how I would do that via ADB?
Click to expand...
Click to collapse
You don't. Flash with flashtool
Klyupp said:
You don't. Flash with flashtool
Click to expand...
Click to collapse
I've been trying the the last 2 days to sort this out but have come against a stone wall. I've tried on 3 PCs and I cannot get the phone connected via USB (other than with ADB or MTP). To clarify my situation (as my initial post is probably incorrect)....I have manged to "replaced" the Android OS with a TWRP. Every time I start the phone I end up on the TWRP screen. I can boot in to the stock recovery. I have the correct KDZ file and Flash Tool but can't connect to the phone to re-flash.
Please, any help will be greatly appreciated.
What does it say on the PC when you plug it in?
Is it picked up in Device Manager?
Can you get in download mode?
Yep, its picked up as "G3" but with no drivers. I've downloaded and installed the LG unified drivers without any luck. From other pots I think I should be seeing it as "LGE AndroidNet USB Serial Port"?
Download mode? Not sure what you mean.
LonPete67 said:
Download mode? Not sure what you mean.
Click to expand...
Click to collapse
Now I know what download mode is! And yes, I'm in download mode now. The drivers have loaded!! Going to try a reflash now.
Thank you everybody who helped, the phone is working again! Clearly what I thought I knew does not match what I actually knew!!
Related
I flashed Fulmic rom for my G3 D855 today. Everything was well when I discovered until I discovered, that camera app is not showing. The fix was to download the fix from Fulmics app and flash it via TWRP. I downloaded the fix and rebooted to install the fix. After reboot I got stuck in bootloop, when I try to access recovery, it goes to TWRP first logo and stays there. Nothing happens. When I try to access download mode, it shows the first download mode logo and stays there. Computer detects the phone in device manager as "LGE Android MTP Device". LGUP shows model as "Unknown". Cant do nothing more. Every help is appreciated.
Are you sure you flashed the fix ? Because it seems like you flashed something else that messed up your device
BrosseLi said:
Are you sure you flashed the fix ? Because it seems like you flashed something else that messed up your device
Click to expand...
Click to collapse
I downloaded the fix, then tried to install it via twrp. But twrp didn't start. So I ran AutoRec again to reinstall TWRP which seemed to go well. Forgot to mention this on first post. After reinstalling TWRP the problems occurred.
RobinNewToGalaxy said:
I downloaded the fix, then tried to install it via twrp. But twrp didn't start. So I ran AutoRec again to reinstall TWRP which seemed to go well. Forgot to mention this on first post. After reinstalling TWRP the problems occurred.
Click to expand...
Click to collapse
Autorec goes on STOCK untouched roms.
bender_007 said:
Autorec goes on STOCK untouched roms.
Click to expand...
Click to collapse
Yes, I know that now
But any idea how to fix it now?
RobinNewToGalaxy said:
Yes, I know that now
But any idea how to fix it now?
Click to expand...
Click to collapse
Let´s see:
-can´t enter twrp ?
-can´t enter download mode ? (volume up and connect to pc)
bender_007 said:
Let´s see:
-can´t enter twrp ?
-can´t enter download mode ? (volume up and connect to pc)
Click to expand...
Click to collapse
Can't enter twrp, just shows TEAMWIN logo with blue background and stripes. Nothing more happens.
Download mode text shows up, pc makes connection sound but I dont know what to do after that. I tried using LGUP but that showed that model is "Unknown".
Ah, try lg flash tool 2014 or lg flashtool (and a tot file), find a thread by hyelton (lg g3 get back to stock), this will help you
RobinNewToGalaxy said:
Can't enter twrp, just shows TEAMWIN logo with blue background and stripes. Nothing more happens.
Download mode text shows up, pc makes connection sound but I dont know what to do after that. I tried using LGUP but that showed that model is "Unknown".
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=1WgXuxDbmbc this video should help you if you can enter download mode
bender_007 said:
Ah, try lg flash tool 2014 or lg flashtool (and a tot file), find a thread by hyelton (lg g3 get back to stock), this will help you
Click to expand...
Click to collapse
I have tried this method also. Every time at 4% it says, error, remove battery and then reconnect and turn on phone. After that, connection with pc is lost.
Also, when I try to get to Download Mode, it should go then to Firmware update screen to? Am I right about that? If so, then it doesn't go to Firmware update screen.
But I tried it with a kdz I had in my computer and had used before. Downloading .tot file atm.
RobinNewToGalaxy said:
I have tried this method also. Every time at 4% it says, error, remove battery and then reconnect and turn on phone. After that, connection with pc is lost.
Also, when I try to get to Download Mode, it should go then to Firmware update screen to? Am I right about that? If so, then it doesn't go to Firmware update screen.
But I tried it with a kdz I had in my computer and had used before. Downloading .tot file atm.
Click to expand...
Click to collapse
did you change the port to com41?
oh, youre downloading the .tot file now, yeah just use the lg flash tool like the dude in the video says it should work if you can enter download mode and it detects the phone, just follow the steps i did it like 2 days ago
STM75 said:
did you change the port to com41?
oh, youre downloading the .tot file now, yeah just use the lg flash tool like the dude in the video says it should work if you can enter download mode and it detects the phone, just follow the steps i did it like 2 days ago
Click to expand...
Click to collapse
it seems to have stopped in LG Flash Tool, where it is saying "Waiting for connection". It has been so for 15 minutes now :crying:
RobinNewToGalaxy said:
it seems to have stopped in LG Flash Tool, where it is saying "Waiting for connection". It has been so for 15 minutes now :crying:
Click to expand...
Click to collapse
did you watch the whole video? try to remove the cable and then put it in a few sec
STM75 said:
did you watch the whole video? try to remove the cable and then put it in a few sec
Click to expand...
Click to collapse
i didn't find a video but a text and pics tutorial which also stated to remove the cable which i did. The "Waiting fo r Connection" text appears after I remove the cable.
RobinNewToGalaxy said:
i didn't find a video but a text and pics tutorial which also stated to remove the cable which i did. The "Waiting fo r Connection" text appears after I remove the cable.
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=1WgXuxDbmbc i sent it before too
STM75 said:
https://www.youtube.com/watch?v=1WgXuxDbmbc i sent it before too
Click to expand...
Click to collapse
Did everything same like in the video but it still stays in "Waiting.." status.
RobinNewToGalaxy said:
Did everything same like in the video but it still stays in "Waiting.." status.
Click to expand...
Click to collapse
are you using a original lg cable? maybe try a diffrent usb port? if youre using a 3.0 port it might not work.
STM75 said:
are you using a original lg cable? maybe try a diffrent usb port? if youre using a 3.0 port it might not work.
Click to expand...
Click to collapse
Original cabel yes, tried another one also. Tried another usb port to, for some reason, it doesn't go to download mode in one port.
RobinNewToGalaxy said:
Original cabel yes, tried another one also. Tried another usb port to, for some reason, it doesn't go to download mode in one port.
Click to expand...
Click to collapse
you changed the port to com41?
RobinNewToGalaxy said:
Original cabel yes, tried another one also. Tried another usb port to, for some reason, it doesn't go to download mode in one port.
Click to expand...
Click to collapse
Also it stays in download mode screen, not Firmware update screen. I don't know if this affects anything.
Hi guys,
i recently use layers for my xenonhd rom (lg f400LL)
and then i reboot then boom it goes bootloop
what i have to do?i hardbrick my phone recently and i fix that by doing the shorwire method
but rightnow i use LGUP but it says that:
http://imgur.com/KTK9Vrb
i can still access download mode but i have problems on accessing the twrp recovery because it always boot on the bootloop,i mean
i have problems on using hardware keys to access twrp.
Sir pls help me
Stiffmeistro said:
Hi guys,
i recently use layers for my xenonhd rom (lg f400LL)
and then i reboot then boom it goes bootloop
what i have to do?i hardbrick my phone recently and i fix that by doing the shorwire method
but rightnow i use LGUP but it says that:
http://imgur.com/KTK9Vrb
i can still access download mode but i have problems on accessing the twrp recovery because it always boot on the bootloop,i mean
i have problems on using hardware keys to access twrp.
Sir pls help me
Click to expand...
Click to collapse
I didn't had the same issue as you, but had a similiar one (phone didn't get discovered neither by LGUP nor LG Flash Tool). Yesterday I fixed it by following this guide:
http://forum.xda-developers.com/showthread.php?t=2785089
In particular the part where you change your device to COM41 in the device manager.
After you get it discovered by LG Flash Tool flash an official KDZ.
Reboot the phone and connect it to your Windows, allow the connection from the phone screen.
It should promt you to install drivers on the computer, do that (they are different from LG Drivers you download from the web mind you)
Now you can change your COM port back to 3 and everything should be fully discoverable by both LGUP and LG Flash Tool.
I think I replied to you on reddit (same photo) Have you tried plugging the phone in while in download mode ? Did you try installing drivers from the internet ? Coz thats how I fixed the same problem you have.
Fluffywolf said:
I think I replied to you on reddit (same photo) Have you tried plugging the phone in while in download mode ? Did you try installing drivers from the internet ? Coz thats how I fixed the same problem you have.
Click to expand...
Click to collapse
engmia said:
I didn't had the same issue as you, but had a similiar one (phone didn't get discovered neither by LGUP nor LG Flash Tool). Yesterday I fixed it by following this guide:
http://forum.xda-developers.com/showthread.php?t=2785089
In particular the part where you change your device to COM41 in the device manager.
After you get it discovered by LG Flash Tool flash an official KDZ.
Reboot the phone and connect it to your Windows, allow the connection from the phone screen.
It should promt you to install drivers on the computer, do that (they are different from LG Drivers you download from the web mind you)
Now you can change your COM port back to 3 and everything should be fully discoverable by both LGUP and LG Flash Tool.
Click to expand...
Click to collapse
Hey Bro'ssss
now i am stuck on the recovery
i always flash the rom but when i boot it always go to the recovery(twrp)
Stiffmeistro said:
Hey Bro'ssss
now i am stuck on the recovery
i always flash the rom but when i boot it always go to the recovery(twrp)
Click to expand...
Click to collapse
The method I'm describing uses Download Mode so it should work for you.. Try it and tell us the result
engmia said:
The method I'm describing uses Download Mode so it should work for you.. Try it and tell us the result
Click to expand...
Click to collapse
Thanks man its all ok now
i dont have time to explained what i did but it works
Many thanks to all of you
hey guys, LGUP will not see my phone at all(LGV10) its in download mode , but does not come up. its stuck on LG boot screen and wont go past it. any help would be appreciated... I am, or was rooted anyway, and trying to reflash again. need to in order to fix it now. thanx
1SouthernCanuck said:
hey guys, LGUP will not see my phone at all(LGV10) its in download mode , but does not come up. its stuck on LG boot screen and wont go past it. any help would be appreciated... I am, or was rooted anyway, and trying to reflash again. need to in order to fix it now. thanx
Click to expand...
Click to collapse
Just read over the thread, it's what it's here for.
Stiffmeistro said:
i dont have time to explained what i did but it works
Click to expand...
Click to collapse
You asked for other people's time to help you, but now you don't have time to explain how you made it work?
Yeah... there MIGHT be other people with the same problem, but why would you care to share.
What an as*hole you are. Another typical new buttuser ruining a great dev community.
exactly
leandeganis said:
You asked for other people's time to help you, but now you don't have time to explain how you made it work?
Yeah... there MIGHT be other people with the same problem, but why would you care to share.
What an as*hole you are. Another typical new buttuser ruining a great dev community.
Click to expand...
Click to collapse
Exactly, here I am running around in circles over this BOOST Stylo 2, just got it with MM 6.0.1 out of the box 2 days ago. I caught the 454.4mb update it has been trying to do! Got that baby downloaded! 1.02gb unzipped and renamed to kdz. Got a script for Terminal that will replace Kingroot's temp root with SuperSU but I am not going to attempt any further until I know LGUP will recognize and flash my .zip the bas****s deem not worth enough to put up for download on LG's site!
I got LGUP to recognize it in download mode, reads out LGLS775 but still says it cannot open it...............
His info on how he got it to work would prolly have solved this dillema..............
oh well
zach
ok had a LG G3 that's done this- as long as you can get download mode it should recover, YOU need to use the LG mobile support tool from LG website ( LG UP sees phone as unknown model ) run LG mobile Support tool and in option choose UPGRADE RECOVERY . follow instructions and allow to start process, it took 57 minutes to repair my phone - it will seem frozen anywhere from 0% to about 22% JUST WAIT IT OUT!! lg up / twrp flashes in 5 to 10 mins -- the LG m.s.t writes block by block and takes 1 hour +
so hints and info took 3 goes to find and start upgrade recovery - error on a couple of attempts. phone seems frozen around 10% and 15% of firmware upload -- go make a coffee drink it, go pee then come back and worry! A watched pot never boils!....
Stiffmeistro said:
Thanks man its all ok now
i dont have time to explained what i did but it works
Many thanks to all of you
Click to expand...
Click to collapse
please tell me how to solved your problem my D682 deivce is always opening on recovery but there is no recovery menu just android robot
I have same issue as op described .After unbrick my g3 f400s by short wire method i get error at 94% in tot method and red screen show these word error wrong qem =0 .After remove and put battery again mobile runing but without baseband and null imei .Plz help i need really help
Same here. LGUP Says it is not recognized, even if it says it's a LG G3 855... Trying the LG Mobile Support Tools -> UPGRADE RECOVERY using my Model/serial.
Downloading right now...
Hope it works.
I will tell you when/if I got it to work
Also: Stiffmeistro you're a ****...
---------- Post added at 03:33 AM ---------- Previous post was at 03:22 AM ----------
Sedado77 said:
Same here. LGUP Says it is not recognized, even if it says it's a LG G3 855... Trying the LG Mobile Support Tools -> UPGRADE RECOVERY using my Model/serial.
Downloading right now...
Hope it works.
I will tell you when/if I got it to work
Also: Stiffmeistro you're a ****...
Click to expand...
Click to collapse
It didn't. It's EVEN MORE broken :'(
I figured out how to get my PC to recognize my D851. Apparently all the LG software didn't like how many COM ports I have. As soon as I unplugged everything else from my PC, the software worked. In this case, it was LG Flash Tool 2014, but I couldn't get any of them to work before.
Try running LGUP as Admin!!! For me it worked!
Try running LGUP as Admin!!! For me it worked!
Thankx Bro Its Work
engmia said:
The method I'm describing uses Download Mode so it should work for you.. Try it and tell us the result
Click to expand...
Click to collapse
Hope someone can help me. I flashed a rom for a d855, d855g30 I think, and although I can access download mode all aps for flashing fail saying it's the wrong model number. Even the generic DLL file cant trick it. It still starts booting the rom but boot loops before entering. I no longer have twrp and when I try to do safe mode or factory reset I get a boot validation error or something similar. Just seem to be stuck. Im using a VS985.
One cause of LGUP "UNKNOWN"
While an old thread, it'll be found in searches. For anybody who gets "UNKNOWN" device with LGUP for the LG G3, I found that LGUP for the G3 is often distributed with the wrong DLL file. See the details here, post #11. After installing LGUP, make sure that the "model" subdirectory in the LGUP program directory is the same number as the processor in your phone, in my case c:\Program Files (x86)\LG Electronics\LGUP\model\8974 (was 8994 with the "LGUP for G3" I downloaded).
HTH
Hello community members,
TL;DR no adb, no fastboot, no flashmode, no QDloader (or similar) ... how to unbrick it?
I was trying to force Android to allow lower lcd backlight brightness levels by patching framework-res.apk and I had the edited zip file ready to flash. Then I realized that my Android 7 Ressurection remix ROM (thread) flashed Cyanogenmod recovery, which I don't like. So I decided to reflash TWRP 3.0.2 (link) ( edit: using "fastboot flash boot twrp.img", which was almost fatal mistake) and it has gone almost well. The phone started to boot into recovery mode everytime (and took a long time doing so). So I googled a bit and found this thread which lead me to this thread. I was looking forward to seeing my display brightness at lower than default values, so I probably skipped some security checks and texts with red color, so I flashed the zip with the boot.img replaced. After flashing I chose reboot and nothing happened since.
The problem is I flashed something that was not for my device (extracted boot.img to wrong mmcblk). The command that bricked my phone is (from META-INF/com/google/android/updater-script):
Code:
package_extract_file("boot.img", "/dev/block/mmcblk0p6");
After that it doesn't boot, doesn't light up LED (even when charging), doesn't get detected by PC in any state.
So I have no adb, no fastboot and no flashmode and not even a QDloader or similar mode.
Is there a way to unbrick it?
EDIT: How to unbrick it using JTAG interface? If I find somebody that has the required equipment, what data do I need to give them?
Hey there! Did you manage to solve the issue, because I just got into the same situation after the zip didn't save the corrected partitions but the initial ones... So i ended up without any signs of life in my phone
valkata752 said:
Hey there! Did you manage to solve the issue, because I just got into the same situation after the zip didn't save the corrected partitions but the initial ones... So i ended up without any signs of life in my phone
Click to expand...
Click to collapse
Nope, I found no solution ... even some kind of Qualcomm flashing mode via COM (serial port over USB) does not show up nowhere. I gave up and bought a used S5 mini, which is full of features I appreciate.
I'm gonna keep this Xperia M for some time if some solution comes up.
hi , can you boot into recovery ? ..if yes, i can maybe help
olibub said:
hi , can you boot into recovery ? ..if yes, i can maybe help
Click to expand...
Click to collapse
No, as I said, the phone does not react on anything. I would be able to put it back together if this was possible.
mik13ST said:
No, as I said, the phone does not react on anything. I would be able to put it back together if this was possible.
Click to expand...
Click to collapse
:/ this will be a problem... try look here http://rootmyandroid.org/how-to-unbrick-your-android-device-the-ultimate-guide.html/
and find this article "Unbrick any android device with Once Click Unbrick tool"
mik13ST said:
No, as I said, the phone does not react on anything. I would be able to put it back together if this was possible.
Click to expand...
Click to collapse
can you still access fastboot mode? anyway you need to know first what is exactly partition that you overwrite with boot.img :/
. That was really critical -_-
olibub said:
:/ this will be a problem... try look here http://rootmyandroid.org/how-to-unbrick-your-android-device-the-ultimate-guide.html/
and find this article "Unbrick any android device with Once Click Unbrick tool"
Click to expand...
Click to collapse
Nice looking tutorial, but I cannot find any download link for that One Click Unbrick Tool in that article. I doubt it would work, they are not explaining what it does.
Nicklas Van Dam said:
can you still access fastboot mode? anyway you need to know first what is exactly partition that you overwrite with boot.img :/
. That was really critical -_-
Click to expand...
Click to collapse
No, as I said. The partition that got overwritten was /dev/block/mmcblk0p6. It was overwritten by boot.img from LG OPTIMUS 3D that I link to in the main post.
here you can download unbrick tool https://forum.xda-developers.com/showthread.php?t=1153310
olibub said:
here you can download unbrick tool https://forum.xda-developers.com/showthread.php?t=1153310
Click to expand...
Click to collapse
I don't think this has any chance that it will work.
"This Software:
Will work on all Samsung devices which use Odin3"
Do you know how to use Flashtool?
If so, did you already attempt flashing a ftf via Flashmode (Hold VolDown)?
PhoenixTwoFive said:
Do you know how to use Flashtool?
If so, did you already attempt flashing a ftf via Flashmode (Hold VolDown)?
Click to expand...
Click to collapse
I know what Flashtool is. I know what ftf is. I used it once I think.
But the phone does not boot into flashmode as I mention in the main post.
I recently recoverd from a brick using the usual xfstk downloader asus flash tool ect... i think i quit the asus flash tool too early and it left me with a buggy android. my problem is. there is no bootloader! when i try get to it ( even through adb) theres nothing there! but theres a fully working android. I tried to use xfstk downloader again, and when it says "continuing to os" all it does is put me in android with no bootloader. I really want a way to fully wipe my device so i can start fresh again. Is this safe? is there a better way?
that's why i always recommend to use commands method to flash after xfstk. any ways enable developer option and usb debugging. then connect to pc and run command adb reboot recovery. most probably you will boot into recovery factory reset there and sideload latest firmware downloaded from asus website.
if you are rooted then you can flash bootloader via dd commands
sukhwant717 said:
that's why i always recommend to use commands method to flash after xfstk. any ways enable developer option and usb debugging. then connect to pc and run command adb reboot recovery. most probably you will boot into recovery factory reset there and sideload latest firmware downloaded from asus website.
if you are rooted then you can flash bootloader via dd commands
Click to expand...
Click to collapse
I tried to do the adb thing. and it just took me into the os
i am not rooted. is there any hope for me?
aceaidan said:
I tried to do the adb thing. and it just took me into the os
i am not rooted. is there any hope for me?
Click to expand...
Click to collapse
then do xfstk again and flash raw via commands
sukhwant717 said:
then do xfstk again and flash raw via commands
Click to expand...
Click to collapse
I know it sounds like allot, but can you tell me how to do these things. I'm a total noob and you sound like a nice guy.
sukhwant717 said:
then do xfstk again and flash raw via commands
Click to expand...
Click to collapse
Also the xfstk won't complete because when it says continuing to os. It just takes me back to android.
I recommend to use this guide
https://forum.xda-developers.com/showthread.php?p=68477856
It's the only way to get my ZE551ML run again.
After using xfstk, go forward without AsusFlashTool and do all steps manually as described in the guide. It helped me to get my bricked ZF2 run again with newest MM.
Good luck.
aceaidan said:
Also the xfstk won't complete because when it says continuing to os. It just takes me back to android.
Click to expand...
Click to collapse
here are few things you can do! wipeout ifwi on emmc. and then use latest MM ifwi on marshmallow. if still same open back panel of the phone disconnect battery connector and place small paper under connector leave it like 7 days and after that try xfstk again with original files
mobil_z said:
I recommend to use this guide
https://forum.xda-developers.com/showthread.php?p=68477856
It's the only way to get my ZE551ML run again.
After using xfstk, go forward without AsusFlashTool and do all steps manually as described in the guide. It helped me to get my bricked ZF2 run again with newest MM.
Good luck.
Click to expand...
Click to collapse
Can you please link me to the manual files for mm in stuck on the first stock android.
aceaidan said:
Can you please link me to the manual files for mm in stuck on the first stock android.
Click to expand...
Click to collapse
didnt get you point!
what does you mean by first stock android?
what files you are asking for MM?
what exactly you want to do?
aceaidan said:
Also the xfstk won't complete because when it says continuing to os. It just takes me back to android.
Click to expand...
Click to collapse
It may be a fault in some other guides by addressing in xfstk.
The right address is 0x80000807, some other guides show 0x800000807, one 0 too much!
The guide I linked to does it right.
sukhwant717 said:
didnt get you point!
what does you mean by first stock android?
what files you are asking for MM?
what exactly you want to do?
Click to expand...
Click to collapse
My acrossim running android 5.0 and I want my bootloader back and then I want the mm files like system.img ect... So I can get mm
aceaidan said:
So I can get mm
Click to expand...
Click to collapse
If you finally want to go to MM, you can install it directly if your phone is broken now. So you will get a very clean MM without messed up from updading from LP! Really recommend.
hey ,i have same problem with my asus zenphone 2 , had you got any perfect solution? please help!!
every time i tried to flash files using xfstk is show countinuing to os and then show error - enable to connect with device!!
Hi all,
After reading many posts i got a little confused and i'm not getting any result. Please help.
What i want?: Flash stock rom and later consider rooting, and flashing haden or lineagos. (already found guidance but..)
The issue?: It doesn't get recognized through USB with my PC. (drivers installed, cable connected but...)
My questions? (correct me if wished):
1) In Odin mode (which i enter) is the usb port enabled by default? or it depends on the phone configuration.
2) In recovery mode i still cannot see the phone through the USB so is it open by default on stock recovery?
3) Finally can i flash stock rom i downloaded from sammobile through SD card? i found that to be my last resort but i think odin actual proper way or not?
I first thought it was the cable...since is not the original but it seems not be the case...which leads me to think its the phone's usb port....but with the cable i can charge the phone although i cannot see it through my PC.
So bottom line if the answer to my questions are that is always open (accesible through usb port) then it HAS to be the cable right?
If last quesiton is possible then i will conclude my searchings to be ended for now.
Thanks to all the posts within this tree.
Findings
Is it normal that when boot to bootloader from stock recovery the ADB console keeps <waiting for device> while phone actually boots normaly?
I found that bootloader booting is accesible through fastboot independently from USB debugging option...
I'm considering buying official usb cable but store guy confirmed it works for data/power uses...
There definitely is a way to flash stock via TWRP, i once did that myself. However you need a dedicated tool on the PC to create a flashable zip, because the firmware can't be flashed by itself
Edit: i saw that you have FRP-lock enabled. Search for a guide on how to disable it and try again
verdugon said:
Is it normal that when boot to bootloader from stock recovery the ADB console keeps <waiting for device> while phone actually boots normaly?
I found that bootloader booting is accesible through fastboot independently from USB debugging option...
I'm considering buying official usb cable but store guy confirmed it works for data/power uses...
Click to expand...
Click to collapse
Are you on Samsung? If so, they don't have fastboot. Nor can you boot to bootloader. Do
Do you have the drivers installed? I have yet to see an unofficial cable not work for data transfer. Excepting damaged ones.
Light at the end of the tunnel!!!
PMFRTT said:
There definitely is a way to flash stock via TWRP, i once did that myself. However you need a dedicated tool on the PC to create a flashable zip, because the firmware can't be flashed by itself
Edit: i saw that you have FRP-lock enabled. Search for a guide on how to disable it and try again
Click to expand...
Click to collapse
Thanks PMFRTT!! I finally disabled FRP-lock and phone is usable again. I now will try to unlock OEM bootloader and enable USB debugging to see what happens. Thanks
Light at the end of the tunnel!!!
SnowFuhrer said:
Are you on Samsung? If so, they don't have fastboot. Nor can you boot to bootloader. Do
Do you have the drivers installed? I have yet to see an unofficial cable not work for data transfer. Excepting damaged ones.
Click to expand...
Click to collapse
Thanks @SnowFuhrer for your reply.
To answer your question yes its SMSUNG. I didn't know about that Thx.
The cable is brand knew but i noticed now that the phone is usable that is claims its on slow charge...may be my PC is quite old now....
Like i said i will try to unlock bootloader and make it accesible to odin to later see what to do.
verdugon said:
Thanks @SnowFuhrer for your reply.
To answer your question yes its SMSUNG. I didn't know about that Thx.
The cable is brand knew but i noticed now that the phone is usable that is claims its on slow charge...may be my PC is quite old now....
Like i said i will try to unlock bootloader and make it accesible to odin to later see what to do.
Click to expand...
Click to collapse
And to unlock the bootloader, just enable OEM unlock in the dev settings and it's ready to flash twrp. I remember when I got my Samsung and I was trying to fastboot unlock it lol.
Thanks to both of you! I will keep the thread on just in case...anyway may be it helps someone else.
verdugon said:
Thanks PMFRTT!! I finally disabled FRP-lock and phone is usable again. I now will try to unlock OEM bootloader and enable USB debugging to see what happens. Thanks
Click to expand...
Click to collapse
Good luck! Let me know how it went.