Database Users

Can't turn on Wifi on GT-l9505

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.

[Q] Trying to go back from CM12 to Touchwiz

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.

GPS has gone whack

Hey guys,
Have been running a 4.4 ROM for a while (900i) and I finally bit the bullet and installed Phoenix Rom (900F).
It worked fantastically (aside from the NFC). I did notice the GPS failed to hookup. This was a problem so I restored my kitkat backup. However....
The GPS now no longer works!!? I download an original Kitkat Rom for my provider (optus) off Sammobile. Flashed with it with Odin and still it fails to connect.
Googling has led me to no immediate resolutions. I flashed 4.4 stock again with Odin and did a 5.0 Lollipop update OTA in hope that it would fix things.
It hasn't worked thus far. Was hopefing someone would know what was going on or could provide me with some guidance.
Cheers.

Tried a full factory reset from recovery / android settings after flashing the stock ROM ?

*Detection* said:
Tried a full factory reset from recovery / android settings after flashing the stock ROM ?
Click to expand...
Click to collapse
Yep. Still no dice.

Only other thing I can think of is to grab the correct PIT file for your model S5, flash that and a stock ROM at the same time using ODIN
If it still doesn't work after that, it sounds like a hardware issue
You say your phone is the G900I? And you flashed a G900F ROM to it?
Other than that, make sure other devices can get a GPS lock, make sure it's not just the weather stopping it working

*Detection* said:
Only other thing I can think of is to grab the correct PIT file for your model S5, flash that and a stock ROM at the same time using ODIN
If it still doesn't work after that, it sounds like a hardware issue
You say your phone is the G900I? And you flashed a G900F ROM to it?
Other than that, make sure other devices can get a GPS lock, make sure it's not just the weather stopping it working
Click to expand...
Click to collapse
Not exactly sure where to get the correct PIT file to flash.
I'll try disabling all weather settings though, didn't think of that one. Cheers

http://forum.xda-developers.com/showpost.php?p=52329647&postcount=2
Scroll down and choose your model S5 PIT, Extract to .pit, add to PIT section, and flash with the stock ROM in AP or PDA section as normal
And I meant the weather outside stopping the phone seeing the satellites, heavily cloudy days can cause problems sometimes, but check settings, connections, location, is set to high accuracy

*Detection* said:
Tried a full factory reset from recovery / android settings after flashing the stock ROM ?
Click to expand...
Click to collapse
*Detection* said:
Only other thing I can think of is to grab the correct PIT file for your model S5, flash that and a stock ROM at the same time using ODIN
If it still doesn't work after that, it sounds like a hardware issue
You say your phone is the G900I? And you flashed a G900F ROM to it?
Other than that, make sure other devices can get a GPS lock, make sure it's not just the weather stopping it working
Click to expand...
Click to collapse
*Detection* said:
http://forum.xda-developers.com/showpost.php?p=52329647&postcount=2
Scroll down and choose your model S5 PIT, Extract to .pit, add to PIT section, and flash with the stock ROM in AP or PDA section as normal
And I meant the weather outside stopping the phone seeing the satellites, heavily cloudy days can cause problems sometimes, but check settings, connections, location, is set to high accuracy
Click to expand...
Click to collapse
Damn... 'Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again' :crying:
This is what I ran:
{
"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"
}
EDIT: Running it again. Appears to be running. I think my USB hub died which is why it 'failed'. Installing applications now and will post back as to whether the GPS is working or not.
I actually have a place to be which is why I'm desperately trying to fix things.
Unfortunately it hasn't fixed the GPS. I'll have to print out the Google Maps instructions.
EDIT 2: Tried this:
Open Phone, as if you were going to make a phone call and dial -
*#9090# (*#197328640# if that doesn't work)
Menu, select Key Input, enter Q
Menu, select Key Input, enter 0000
wait for the next menu. (It takes a while.)
UMTS->COMMON->NV REBUILD->NV REBUILD->SYSTEM->PROTOCOL->GPS->IMS
or, if you don't have UMTS:
UE SETTINGS & INFO->SETTING->SYSTEM->NV REBUILD->ALL
Click to expand...
Click to collapse
No cigar. Will to another factory reset when I have a chance.
EDIT 3: Did another factory reset through the menu and it said location set my GPS. I nearly fell over!

We're working. Thanks for all your help *Detection*

Great!

Hi there , i've had the same problem when installing a custom rom like PopWiz Telstra or other rom don't no why but this fix works for me every time :
Install latest rooted TW (original Samsung Touch wiz rom) like (Alexandr ROM )
Install from play store Shortcut Master or Phone Info
Open ‘Secret Code Explorer’ menu, scroll down to 27663368378 and launch it (select ‘Launch 0’, root is required).
Then select the latest menu option Hardware sensors
Then the latest option restore (rebuild) NVRAM (or something like that. I’m writing this from my memory )
Reboot the phone
Try GPS – it should work
I have just copy paste it from a site in works like a charm on g900f

Alright. I'm unhappy with the Optus Lollipop 5.0 stock. I can't install xposed because its odexed so I'm going back to the Phoenix 900F!
This time I'm going to install it with TWRP.
Will then go through the troubleshooting attempts in an attempt to have a GREAT rom with a fully functional GPS!~

E:ensure_path_unmounted failed to unmount /efs (device or resource busy)

So a quick backround. Phone is a S8 (SM-G950W). I disabled the Samsung keyboard with package disabler long ago since I used Google keyboard. I put my phone into ultra power-saving mode and it locked, and I couldn't unlock it because the Google keyboard gets disabled in ultra power-saving mode and the Samsung one was disabled by me.
I had no way to get back into my phone so I wiped it through the recovery menu..
So here's my issue. Everything works fine as before, except now when I boot into the recovery menu, it will say
E:ensure_path_unmounted failed to unmount /efs (device or resource busy) a few times among the normal text in the recovery menu.
I'm on stock Rogers most recent firmware and the phone has never been rooted or had anything except stock Rogers firmware on it. It was the first time I wiped the phone since getting it.
Any one have any insight how to fix it. It's not really affecting anything on the phone from what I can tell, it's just bothering me since it wasn't there before.
Everything still loads the same except for that message/error whatever It is appearing. All features work on the phone and recovery menu. I've spent hours searching and can't find anything
{
"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'm getting the same exact same error:
https://forum.xda-developers.com/galaxy-s8+/help/eensurepathunmounted-failed-to-unmount-t3708763
Have you had any luck with this issue? In my case, I have not done any changes to my system. I'm beginning to think that this error may have been introduced with a recent firmware update.
I have also attached a picture of my recovery screen along with a section of the recovery log that also shows the error message.
If anyone has the same firmware as mine, perhaps they can boot into recovery to see if they have the same error message.

I get this too. Rogers too.
I was having problems receiving MMS messages so decided to do a factory reset as per Rogers recommendation and noticed that.
Anybody found why this appear in recovery mode and also how to solve it...?

I've given up lol. It's either no one knows or no one cares to help. Either way I just live with it now since it doesn't seem to affect anything except my ocd.

your efs partition is messed up. this is where your imei and modem information is stored. fixing it without an EFS partition backup is going to be very difficult. this is why they tell you to back up when you root. https://forum.xda-developers.com/galaxy-s8/how-to/how-to-fix-imei-drk-issues-t3622559 the author of this thread has been helping people try and fix it. the thread is for s7 phones but he is helping with s8's as well.

djisgod said:
your efs partition is messed up. this is where your imei and modem information is stored. fixing it without an EFS partition backup is going to be very difficult. this is why they tell you to back up when you root. https://forum.xda-developers.com/galaxy-s8/how-to/how-to-fix-imei-drk-issues-t3622559 the author of this thread has been helping people try and fix it. the thread is for s7 phones but he is helping with s8's as well.
Click to expand...
Click to collapse
My phone has never been rooted. Nor has it ever had anything but stock firmware.
This issue is different than all the other efs issues. The phone operates and runs fine aside from that popping up when you load the recovery menu.

1) I bought an sm-9550 Hong Kong version with the firmware G9550ZHU1AQJ8
had the same mistake
E: ensure_path_unmounted failed to unmount / efs (device or resource busy)
2) then I patched the old firmware G9550ZHU1AQG6 and the error disappeared.
3) updated via OTA to the new firmware, the error returned
I understand this is a problem with a specific firmware, I think they will solve it.

terentev said:
1) I bought an sm-9550 Hong Kong version with the firmware G9550ZHU1AQJ8
had the same mistake
E: ensure_path_unmounted failed to unmount / efs (device or resource busy)
2) then I patched the old firmware G9550ZHU1AQG6 and the error disappeared.
3) updated via OTA to the new firmware, the error returned
I understand this is a problem with a specific firmware, I think they will solve it.
Click to expand...
Click to collapse
This confirms my theory that it was introduced with a recent firmware update. I suspect that anyone who is using a recent official firmware would see the same error message if they went into recovery mode. This appears to affect at least the S8/S8+ and Note 8 based on others who have also reported it. I recently upgraded my firmware to G955WVLU2AQK7 which has the November 1st security patch and the error message is still there. Hopefully, Samsung will address this eventually since any error message involving the efs partition is not very reassuring to see.

Title101 said:
This confirms my theory that it was introduced with a recent firmware update. I suspect that anyone who is using a recent official firmware would see the same error message if they went into recovery mode. This appears to affect at least the S8/S8+ and Note 8 based on others who have also reported it. I recently upgraded my firmware to G955WVLU2AQK7 which has the November 1st security patch and the error message is still there. Hopefully, Samsung will address this eventually since any error message involving the efs partition is not very reassuring to see.
Click to expand...
Click to collapse
I'm running AQK3 (latest g950u release on VZW) and my rom is based off it to and no reports of this. Just providing more data points

Title101 said:
This confirms my theory that it was introduced with a recent firmware update. I suspect that anyone who is using a recent official firmware would see the same error message if they went into recovery mode. This appears to affect at least the S8/S8+ and Note 8 based on others who have also reported it. I recently upgraded my firmware to G955WVLU2AQK7 which has the November 1st security patch and the error message is still there. Hopefully, Samsung will address this eventually since any error message involving the efs partition is not very reassuring to see.
Click to expand...
Click to collapse
Same here. Updated and it's still there.

partcyborg said:
I'm running AQK3 (latest g950u release on VZW) and my rom is based off it to and no reports of this. Just providing more data points
Click to expand...
Click to collapse
AQK3 appears to be the October security update. Just to confirm, are you saying that you're not seeing the error message?
FYI, there appears to be a newer update for your rom (BQK5) that contains the November security update: https://www.sammobile.com/firmwares/galaxy-s8/SM-G950U/VZW/download/G950USQU2BQK5/199426/

Title101 said:
AQK3 appears to be the October security update. Just to confirm, are you saying that you're not seeing the error message?
FYI, there appears to be a newer update for your rom (BQK5) that contains the November security update: https://www.sammobile.com/firmwares/galaxy-s8/SM-G950U/VZW/download/G950USQU2BQK5/199426/
Click to expand...
Click to collapse
AQK4 was November. I'm aware of the latest version, but uninterested in losing the ability to roll back

partcyborg said:
AQK4 was November. I'm aware of the latest version, but uninterested in losing the ability to roll back
Click to expand...
Click to collapse
I'm just going with the information that SamMobile has on their website. With the version you are running, are you seeing the error message in recovery or not?

Title101 said:
I'm just going with the information that SamMobile has on their website. With the version you are running, are you seeing the error message in recovery or not?
Click to expand...
Click to collapse
As I said in my first post, no.
I would also caution you against ignore that kind of error, as loss of efs can render your phone permanently inoperable if you do not have a backup to restore from. efs holds critical and sensitive information like your imei

Same issue here with my galaxy s8+. I'm with Bell btw.

Has anyone found a solution to this?

Same issue here, on AT&T in the U.S.

S8 Verizon with BQL1 has same issue

Same issue here on TMO S8+ with phone freezing and restarting, no solution in sight.

I have the same problem. S8+ AT&T US.
I could be wrong, but after reading the log a bit, it looks like the commands that are trying to run do not have permission to do what they want to do. Then the instructions seem to fall back to a fail safe version and some of them don't run either because the efs folder is already there. Maybe that's why on the recovery page it says busy, because it is trying to execute commands that it can't, then everything seems to go through anyway and the phone still works. Perhaps the instructions that are running in the log are off a count. Just an idea. First post too, but I've been an avid reader for a while.
My log talks about having issues with permissions. I also think I might have flashed something wrong when I first got the phone because it never hesitates to boot right into android after I flash new software. It never has any wait time on first boot. I have been on oreo beta 2 and 4 and am now back to stock waiting for an update.

[HELP] Hardbricked Moto G4 Infinite loop/Reboot

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"
}