Hello guys this is my first time posting in here, the thing is, I hardbricked my Moto G4 and I can't make it work, it reboots each 5-6 seconds endlessly... any help or advice? I'm beyond desperate :/
Thank you in advance.
Here's a video to show you guys:
https:// youtu.be/_v5FErFl4rk
Just to clarify what in the video:
1)You have your device in the bootloader mode, connected to your computer via USB?
2)I see from your bootloader the bootloader version is B1:06, and the baseband is ending in 62.01R (suggesting June 2017 or Sept 2017 stock firmware)
3)Are you pressing Start, and then it fails to boot, sending you back to the bootloader screen, or is the device rebooting itself without you touching anything?
4)Can you tell us what happened before this happened, was anything being flashed?
echo92 said:
Just to clarify what in the video:
1)You have your device in the bootloader mode, connected to your computer via USB?
2)I see from your bootloader the bootloader version is B1:06, and the baseband is ending in 62.01R (suggesting June 2017 or Sept 2017 stock firmware)
3)Are you pressing Start, and then it fails to boot, sending you back to the bootloader screen, or is the device rebooting itself without you touching anything?
4)Can you tell us what happened before this happened, was anything being flashed?
Click to expand...
Click to collapse
First of all, thank you for your reply!
1) Yes, it's connected to my laptop via usb
2) Do you recommend me download the june 2017/sept stock firmware?
3) Yes, the device is rebooting itself without touching anything
4) I tried to change the logo.bin and messed up my phone, because I UNINSTALLED everything (idk how, but I uninstalled the twrp recovery and system files, yes, i'm stupid!) and then I tried to install everything and then it happened, infinite loop`.
Would you recommend me to change the baterry? maybe it's the reason why it keeps rebooting itself (if you see in the video, there's a blinking light)
letitrrain said:
First of all, thank you for your reply!
1) Yes, it's connected to my laptop via usb
2) Do you recommend me download the june 2017/sept stock firmware?
3) Yes, the device is rebooting itself without touching anything
4) I tried to change the logo.bin and messed up my phone, because I UNINSTALLED everything (idk how, but I uninstalled the twrp recovery and system files, yes, i'm stupid!) and then I tried to install everything and then it happened, infinite loop`.
Would you recommend me to change the baterry? maybe it's the reason why it keeps rebooting itself (if you see in the video, there's a blinking light)
Click to expand...
Click to collapse
Thanks for the clarification.
a)Can you remember what stock firmware you had previously on your device? I see from your baseband you're in the LATAM (Latin America) region so I'd like to get the matching firmware for your device. In theory, we do have stock ROMs here https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 and the NPJS25.93-14-13 firmware has been shown to flash onto LATAM devices. I'm just not sure if this build is eligible for OTA updates for LATAM (because Motorola has a habit of releasing different firmware builds for particular regions), but it's definitely an option.
b)The auto-reboots are an odd symptom, that's true. Maybe worth checking the battery connection to the motherboard before considering the battery. The blinking LED might be related to firmware issues however.
c)Can I just ask clarification on 'tried to install everything' please? Was that with a fastboot flash of a stock firmware or was it via TWRP and restoring from a TWRP backup before the uninstall?
Probably the first thing to try might be a firmware flash, though it's a tad tricky if the device keeps rebooting like that... Can I ask you if the power button is okay or is it sticking sometimes?
echo92 said:
Thanks for the clarification.
a)Can you remember what stock firmware you had previously on your device? I see from your baseband you're in the LATAM (Latin America) region so I'd like to get the matching firmware for your device. In theory, we do have stock ROMs here https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 and the NPJS25.93-14-13 firmware has been shown to flash onto LATAM devices. I'm just not sure if this build is eligible for OTA updates for LATAM (because Motorola has a habit of releasing different firmware builds for particular regions), but it's definitely an option.
b)The auto-reboots are an odd symptom, that's true. Maybe worth checking the battery connection to the motherboard before considering the battery. The blinking LED might be related to firmware issues however.
c)Can I just ask clarification on 'tried to install everything' please? Was that with a fastboot flash of a stock firmware or was it via TWRP and restoring from a TWRP backup before the uninstall?
Probably the first thing to try might be a firmware flash, though it's a tad tricky if the device keeps rebooting like that... Can I ask you if the power button is okay or is it sticking sometimes?
Click to expand...
Click to collapse
1) Honestly, I don't really remember, I used the had the stock firmware.
2) Yes, i'm pretty sure the battery is kinda disconnected, but I don't want to touch anything because i'm sure i'll mess up again
3) I tried to install "everything", i mean, I downloaded the stock rom and the commands (minimal adb and fastboot, rsd lite, etc) and i'm pretty sure I erased everything from the back up, included the TWRP folder.
* The button is Ok, isn't "sticking" at the moment.
Thank you so much! I'm downloading the files you sent to me through the link, maybe the firmware stock I "previously" installed wasn't the right one.
PS: Whenever I tried to run the comands previously, this error appears :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Related
Hello,
I was cleaning my closet today and found my long forgotten Galaxy S4. I turned it on and a update notification poped (for 4.4.2), so far so good. The updated installed successfully and everything is wroking fine, however I can't turn Wifi on anymore. It worked just fine before the update!
So far I've tried doing the following:
I'v taken the battery out, both after shutting down the device and while the device is on.
I've factory reseted the device.
I've re-flashed the same official build using odin.
I've rooted the device to check wpa_supplicant.conf permissions and they seem to be fine (system:wifi)
I've flashed Wifi-fix kernel.
None of the above helped. I still can't turn it on. When I click the toggle or swipe the switch in settings it hangs a bit, stays dark then automatically goes back off on it's own.
Any help would be appreciated!
m.alkhalel said:
Hello,
I was cleaning my closet today and found my long forgotten Galaxy S4. I turned it on and a update notification poped (for 4.4.2), so far so good. The updated installed successfully and everything is wroking fine, however I can't turn Wifi on anymore. It worked just fine before the update!
So far I've tried doing the following:
I'v taken the battery out, both after shutting down the device and while the device is on.
I've factory reseted the device.
I've re-flashed the same official build using odin.
I've rooted the device to check wpa_supplicant.conf permissions and they seem to be fine (system:wifi)
I've flashed Wifi-fix kernel.
None of the above helped. I still can't turn it on. When I click the toggle or swipe the switch in settings it hangs a bit, stays dark then automatically goes back off on it's own.
Any help would be appreciated!
Click to expand...
Click to collapse
strange issue after OTA / full package Odin flash
it reminds me kernel mismatch, as seen in this root procedure - http://forum.xda-developers.com/galaxy-s4/general/root-how-to-obtain-root-permissions-t2862768
Maybe this image is incorrect or something.
Try different one.
th3cr0w said:
strange issue after OTA / full package Odin flash
it reminds me kernel mismatch, as seen in this root procedure - http://forum.xda-developers.com/galaxy-s4/general/root-how-to-obtain-root-permissions-t2862768
Maybe this image is incorrect or something.
Try different one.
Click to expand...
Click to collapse
Thanks for the reply. That's the exat same tutorial I used to root my device (so I can check permissions of the wifi config files). I flashed a the official build image after that so the kernel shouldn't be the problem?
Btw I downloaded the image from sammobile and the md5 was correct!
Edit:
Here's what logcat says:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
m.alkhalel said:
Hello,
I was cleaning my closet today and found my long forgotten Galaxy S4. I turned it on and a update notification poped (for 4.4.2), so far so good. The updated installed successfully and everything is wroking fine, however I can't turn Wifi on anymore. It worked just fine before the update!
So far I've tried doing the following:
I'v taken the battery out, both after shutting down the device and while the device is on.
I've factory reseted the device.
I've re-flashed the same official build using odin.
I've rooted the device to check wpa_supplicant.conf permissions and they seem to be fine (system:wifi)
I've flashed Wifi-fix kernel.
None of the above helped. I still can't turn it on. When I click the toggle or swipe the switch in settings it hangs a bit, stays dark then automatically goes back off on it's own.
Any help would be appreciated!
Click to expand...
Click to collapse
I had the same issue with my S4. Had.Had to get the mobo changed.Luckily it was within the warranty period.
50103 said:
I had the same issue with my S4. Had.Had to get the mobo changed.Luckily it was within the warranty period.
Click to expand...
Click to collapse
Did they write the cause in the repair quote?
Two ways of sorting this one.
1/ Flash a stock firmware which will fix your GSM and LTE modems along with the baseband. You'll wipe your internal storage but that's the way to go if you want a clean start.
2/ Flash the right GSM and LTE modems along with the baseband. Good if you want to keep your existing rom and not wipe you internal storage however -
It is essential to run the same versions for the Modem and Non-Hlos files as the chips talk to each other while the phone operates.
MODEM.bin = firmware for GSM Interface
NON-HLOS.bin / Firmware for LTE & WiFi Interfaces
here's where I got my modem and LTE modems from:
http://forum.xda-developers.com/showpost.php?p=50965837
Regards,
David.
duxxyuk said:
Two ways of sorting this one.
1/ Flash a stock firmware which will fix your GSM and LTE modems along with the baseband. You'll wipe your internal storage but that's the way to go if you want a clean start.
2/ Flash the right GSM and LTE modems along with the baseband. Good if you want to keep your existing rom and not wipe you internal storage however -
It is essential to run the same versions for the Modem and Non-Hlos files as the chips talk to each other while the phone operates.
MODEM.bin = firmware for GSM Interface
NON-HLOS.bin / Firmware for LTE & WiFi Interfaces
here's where I got my modem and LTE modems from:
http://forum.xda-developers.com/showpost.php?p=50965837
Regards,
David.
Click to expand...
Click to collapse
Read OP, please.
If my solution doesn't work I can only think of hardware issues. Btw - a thanks for responding is always welcome.
Hi all,
Here's my story. I have a US T-Mobile Galaxy S5. I wanted to try Lollipop as the new Touchwiz wasn't available yet for my device in early April. So hearing that it is very fast I chose CM12 and used their guide for the S5. I had a little trouble (Heimdall didn't work for some reason), but I successfully used Odin to install the custom recovery (TWRP). Then I was able to wipe and install the CM12 nightly image just fine using TWRP.
Since then I realized that my Gear 2 is only partially compatible with CM12. I've yet to find a thread that shows specific steps to get it working well with CM12, only partially, and many have had trouble even getting partial functionality. And now that Lollipop Touchwiz is available for my phone, I'd like to switch to that.
Last weekend I tried just that. I took a second backup of my CM12 build, then restored my backup from touchwiz 4.4. When I booted to it, the phone was severely crippled. The menu bar and navigation drawer were missing, and the home button did not work at all. I performed a factory reset, and it seemed to be working fine again. Next, I tried an OTA update to 5.0. That didn't work: the phone realized it had been tampered with and told me to use Kies. So I installed Kies, and attempted the update there. After some wrestling with it, I finally got the update to 5.0 started. It finished successfully (so it said anyway) but the phone failed to boot up. It was stuck on the Samsung logo screen for quite a long time. There was some blue text about recovery and I was panicking thinking somehow TWRP screwed up my ability to update w/ Kies. I tried rebooting and could not get into recovery or the OS no matter what. I tried Kies' emergency options only to have it not recognize my phone as compatible. So I went to download mode and installed TWRP again using Odin. Then I was able to boot into recovery, and I restored the backup of CM12 I took before I started all this (thank God I did that).
So now I'm back on CM12 with everything working fine, except of course my watch. I did not expect the restore back to Samsung software to be more difficult than going to CM12.
Can anyone see what I did wrong?
I gather I can install a stock rom with Odin. But all the links I find for this download take me to some sketchy download site that crawls at 50 K/s unless you pay. Am I missing something? Kies downloaded the update in a matter of minutes. Maybe that is still somewhere on my system, and I can use that w/ Odin?
bump
Have a look here for a stock ROM for your model S5 (Example, mine is the G900F)
http://forum.xda-developers.com/showthread.php?t=2715487
If there isn't one, you'll need to do the slow-ass download from sammobile dot com, then use ODIN to flash it
*Detection* said:
Have a look here for a stock ROM for your model S5 (Example, mine is the G900F)
http://forum.xda-developers.com/showthread.php?t=2715487
If there isn't one, you'll need to do the slow-ass download from sammobile dot com, then use ODIN to flash it
Click to expand...
Click to collapse
Thanks. That thread is such a mess. I searched for "G900T" and "T-mobile" but couldn't find it. I will use sammobile then. I wasn't sure before whether to trust it. Having a senior member here vouch for it helps a little.
pianowow said:
Thanks. That thread is such a mess. I searched for "G900T" and "T-mobile" but couldn't find it. I will use sammobile then. I wasn't sure before whether to trust it. Having a senior member here vouch for it helps a little.
Click to expand...
Click to collapse
That's where everyone gets them from, there and samsung - updates dot com
Both sites are banned here for linking to, but not because they are dodgy, just because the owners refused to adhere to XDA rules
They are safe to download from
so frustrating
I downloaded the lollipop stock image from sammobile, and installed with Odin. Odin reported success just like Kies did, and also just like the Kies process, my phone is still stuck in the recovery boot loop. It says RECOVERY BOOTING... in blue at the top and shows the Samsung logo powered by android. What a mess.
Is there something I can do from here to fix this?
Try flashing the PIT file along with the stock ROM, that will repartition the phone then flash the ROM, sounds like something got corrupted using KIES maybe
Double check that this is in-fact the exact model phones PIT file first or you could end up with an even worse brick
http://forum.xda-developers.com/showpost.php?p=52767244&postcount=16
More PIT files here
http://forum.xda-developers.com/showthread.php?t=2737448
There's a video of someone using PIT with ODIN on a different phone, but steps are the same
https://www.youtube.com/watch?v=4qtbEevn1VA
Basically you want it looking like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks again for your help. I think for now I will stick with 4.4 touchwiz. I hear bad things about the touchwiz 5.0 battery life. I simply restored from the TWRP backup I used when I started all this lollipop experimentation, then did a factory reset. I should have my watch working again later tonight.
Okay, so here's my predicament:
Updating my S4 to 5.0.1 failed, so I flashed it with the proper one, but I accidentally clicked Nand Reset All, and now, this get's funny, I can't write or flash any official updates or anything, it get's to this:
Nand Reat/Write failed.
BUT HOLD THE HORSES, THERE'S MORE:
My phone says: There as a problem with the firmware, please use recovery in Kies and try again.
And it says a bunch of stuff on the top left.
If you need screenies, I am happy to provide a full video.
EDIT:
So, I got this little error now:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I never tried repartitioning, but I'm going to do some more research on this error, and see if I can't find a solution
Predated said:
Okay, so here's my predicament:
Updating my S4 to 5.0.1 failed, so I flashed it with the proper one, but I accidentally clicked Nand Reset All, and now, this get's funny, I can't write or flash any official updates or anything, it get's to this:
Nand Reat/Write failed.
BUT HOLD THE HORSES, THERE'S MORE:
My phone says: There as a problem with the firmware, please use recovery in Kies and try again.
And it says a bunch of stuff on the top left.
If you need screenies, I am happy to provide a full video.
EDIT:
So, I got this little error now:
I never tried repartitioning, but I'm going to do some more research on this error, and see if I can't find a solution
Click to expand...
Click to collapse
For Re-Partition you require a PIT file. The PIT file has to be specific to the internal storage of your phone.
So the first flash (the one with nand erase all) was successful and any subsequent flash failed?
GDReaper said:
For Re-Partition you require a PIT file. The PIT file has to be specific to the internal storage of your phone.
So the first flash (the one with nand erase all) was successful and any subsequent flash failed?
Click to expand...
Click to collapse
Really? Damn, well, I guess I could grab it, but I now don't see the firmware issue and now see the S4 Bottscreen, but now I can't boot anymore, I'm thinking of reinstalling adb toget rid of this pesky libsub error.
I'll update soon.
I don't know wht I did, but it works, and it's updating now to the newest firmware. I'll update when I wake up on how I fixed it.
This is what I used to restore it to it's normal capacities:
Guys, Kies 3 has a way of re-flashing your device to the latest official firmware for a certain model with a certain Samsung serial number, i.e. even if your device is bricked and Kies 3 cannot detect it, you enter it's model and Samsung serial number and Kies 3 will download and flash the firmware for you, all you need to do is open Kies 3, power up your device and connect it to your PC, you will then open Tools menu and select Firmware Upgrade and Initialization, if Kies 3 can detect your phone it will show you the version of the firmware that will be downloaded and flashed then you will proceed as instructed (very simple procedures), if not you will be asked to enter just your model (for example GT-N8000) and your Samsung Serial Number (usually starts with R can be found on the sticker under the battery) then it will show you the latest official firmware for your device and if you proceed it will download and flash it for you, but be careful (this will be noted by Kies 3 too) you should get a full backup of your phone as it may wipe out everything on the internal storage in the process if it's required (i.e. a bricked phone to the extent of wrong partitioning that lead to loss of imei), needless to say this process depends on your internet connection (it downloads prerequisite files and firmware files which are relatively large), from little experience I have, it's best that you use the conventional official method for any product rather than unconventional ways at the beginning to solve any problem related to any product, if it doesn't help then try your best with any other method that might help you (by the way I tried this with more than one model of Samsung smart phones, tablets and notes and it always ends up solving the problem, in some cases with my friends devices reviving the device again after being totally bricked), hope this helps .
Note: all devices I used this method with were original devices straight from Samsung (International Versions, Unbranded & Unlocked), so the firmware comes straight from Samsung (no modifications done by operators / carriers) so I'm not sure if it will work for other devices (Fake Cloned, Locked or Branded devices with carriers specific settings)
Link at:
Cant post yet.
It's good to know this.
Unfortunately there are a lot of Frankenstein S4s out there. What this means is that the phone has been repaired with mismatched parts from other S4 models, and this may lead to apps reporting a wrong phone model and other errors.
GDReaper said:
It's good to know this.
Unfortunately there are a lot of Frankenstein S4s out there. What this means is that the phone has been repaired with mismatched parts from other S4 models, and this may lead to apps reporting a wrong phone model and other errors.
Click to expand...
Click to collapse
Yeah, but mine's bought from my phone company and never broke internally, no hardware damage or anything like that, but it now bricked itself again, so I ran into another problem, it doen't show up in emergency recovery in Kies, I don't see the phone. Hmm, 'll keep trying and update the thread when I've figured this out.
Predated said:
Yeah, but mine's bought from my phone company and never broke internally, no hardware damage or anything like that, but it now bricked itself again, so I ran into another problem, it doen't show up in emergency recovery in Kies, I don't see the phone. Hmm, 'll keep trying and update the thread when I've figured this out.
Click to expand...
Click to collapse
Why are you trying to flash a 4.4.2 rom? You said you were on 5.0.1 (or at least your tried to flash that) so you probably can't flash a 4.4.2. rom.
Download a Lollipop rom and try flashing it again.
Lennyz1988 said:
Why are you trying to flash a 4.4.2 rom? You said you were on 5.0.1 (or at least your tried to flash that) so you probably can't flash a 4.4.2. rom.
Download a Lollipop rom and try flashing it again.
Click to expand...
Click to collapse
I was on 4.4.3 for a while, but it's fixed guys, I got it, with 5.0.1 rom, thanks guys!
Hey!
With the new root / unlock that I managed to get on my F800L, I was wondering if anyone thinks it would be possible to get the US996 ("unlocked") ROM working on my phone? (note: it's a spare that i got for free, so I'm happy to try, even if it means I might brick it)
I'll be honest, I have no idea what I'm doing, but I've already started trying, and I thought I'd managed to do it, until the phone started rebooting on me.
To start, I downloaded the US996 deODEXd ROM from here, and installed it, via TWRP. After that, I wiped data, and advance wiped dalvik/data/cache, before installing SuperSU. I then re-wiped dalvik & cache (I was basically re-doing step 4 onwards in the twrp+ section of me2151's Dirtysanta unlock and root guide, from what I could remember...) After that, I rebooted to bootloader, flashed the boot2.img from that guide, and rebooted.
...and it started up fine, and I got to the setup wizard (where it now tells me that it's a US996, instead of F800L).
The problem starts here. If I rush through the wizard, I can complete it and get into the operating system, and I can see what the problem is (if not, it reboots and I have to start the wizard again). There's an "android is upgrading" progress bar in the notification menu. Once that completes, the phone reboots. Apart from that, it seems like everything else works............... as far as I can tell, because the phone reboots after 15 seconds or so, and it gets quicker each time I reboot... although if I go into fastboot, and wipe userdata, I can start from the wizard, again.
I've managed to get a 4G (LTE) Signal, made a short call to check it worked & wifi seems to be working. I managed to turn developer options, and adb debugging on, too, so I can reboot into recovery. (I tried re-flashing supersu, like in the guide, to see if it did anyhting, but no (I don't know if it should, but like i said, I have no idea what I'm doing)).
Anyone have any ideas that I could try? Or is it likely not going to work, and I'm an idiot for trying? (it's cool, I know, I embrace it)
I'm assuming that if there's a way to stop it from trying to upgrade, permanently, then it might stop rebooting? but, obviously... I have no idea what I'm doing, so if there's a way to do that, I don't know how.
Thanks!
Update: Managed to install stock H918 onto my F800L and it works perfectly. Same method as above.
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi, Is it working perfectly yet?
I want to try also on my F800L..
Dear ad,
How to root/unlocked the F800L variant?
I want to try also on my F800L.
Thanks!
I'm wondering if this will work on my Sprint 997
Could someone post detailed steps on how to do this? I have the F800L version and would like to flash a US rom on it. Mainly because my vaoicemail doesn't work, some of LG's apps ignore the system language and still show Korean, etc..
any news???? can i install a custom rom based on h918 variant on my f800l????
is it fully functional?, can u make a tutorial step by step please, there was so very few topic about F800l variant, it would be awesome if u could help.
Does this work on a f800k?
Sent from my LG-F800K using Tapatalk
I have do step by step in the instrustion dirty santa to unlock/root my f800l but i stuck at the step type id in terminal on phone, nothing to show, i repeat from step 1 for many times but it too, please help me. Sorry for my bad English
JvvB126 said:
Update: Managed to install stock H918 onto my F800L and it works perfectly. Same method as above.
Screenshot:
Click to expand...
Click to collapse
Please help me how to do it
Is F800K possible?
Hello All!
Need some assistance here. I bought a used non-rooted stock VZW SM-G975U.
I attempted to flash U1 firmware that I downloaded from FirmwareFiles, but forgot to use the Patched Odin. (Oops, I am a bit of an Android Noob). End goal was to be able to use the phone with US Cellular since they require an SM-975U1, which I still don’t know if flashing will fix....
I received a “256 warning” and it failed to flash, or so I thought.
Now, the phone boots fine, but I am unable to get the device to be recognized - in any fashion - with W7 or W10, tried multiple computers, factory reset, multiple cables, new drivers etc. I have spent days on this...
I recently, today, allowed a brand new VZW pushed OTA update, but it still won’t recognize on any of my PC’s.
Did I soft-brick this phone?
How can I fix without a USB connection and not being rooted?
Thanks so much.
You cannot flash any firmware without know the info of your device first. I recommend u install an info app for Samsung devices (Phone INFO ★SAM★) and share with us some pictures to know if u have a Franki.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I couldn't get the screenshots to properly upload, since I am still a new member without 10 posts. However, I have the "Phone INFO ★SAM★" App installed now.
Product Code: SM2G975UZWAVZW
Firmwares CSC Code: XAA
Active CSC Code: VZW
Available CSC Codes: ATT, BST, CCT, CHA, GCF, SPR, TMB, TMK, USC, VMU, VZW, XAA, XAS
CSC Country: USA/US
Bootloader Version: G975USQU2BSGJ
PDA Version: G975USQU2BSGJ
CSC Version: G975UOYN2BSGJ
Baseband Version: G975USQU2BSGJ
Firmware Status: Official
Kernel Version: 4.14.78-16507756 64-bit
Let me know if there is anything else that I need to provide. I am curious if the OTA update would have updated or "rebuilt" the Kernel, I was hopeful that it would, and fix my problem.
Thanks!
(For those who don't know, G975U is the model number of all of the US carrier versions of the Galaxy S10+. The G975U1 is the model number of the same device, but sold by Samsung SIM unlocked and with no carrier bloatware. Firmware is 100% interchangeable among any of those models.)
Well, seems all is ok there. You can try:
1. Install the latest drivers for Samsung (in ur PC).
2. Factory reset ur device.
3. Download, install and apply the last update via WIFI.
4. Active the developer options -> HOW?
5. Tick there "USB Debugging" and conect it to ur PC (to see if it recognize your device).
6. ... if not... I dunno what to do more. Sorry.
*Patched ODIN: HERE
Thank you, Joku.
I have went through all of those steps, no luck. I’ve tried three different Win10 machines, and did a fresh install of Win10, still no luck. As a last resort, I fresh installed Win7 on a computer, still can’t get any recognition at the PC or the phone, only charge.
I also took the phone up to a PC repair shop to rule out me from being the problem, the tech plugged it into his PC and said, “strange, normally android phones prompt you with a notification to choose the type of transfer or charge when connected to a PC”.
I bought the phone used, not sure where to go from here.
The phone itself seems to work great, other than I can’t get it to connect to my PC. I don’t understand what’s happening.
Maybe the USB port is bad?
Did you try putting your phone in download mode and seeing if your computer recognizes the S10+?
Did you perform a factory reset from the phone settings or while the phone was booted into recovery mode?
Hey jhs,
Thanks, I did try both of these things, no luck.
I am going to take the phone to a service center, something else must be going on.