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] Rooted Kitkat 4.4.2 -> 4.4.4 freezes S5

I can find several how-to's about moving from rooted 4.4.2 to 4.4.4 and stay rooted. But none of them work. Either I can get 4.4.4 to run, but can't root it (towel root won't do 4.4.4, I know that), or I can root 4.4.2, but applying an NI2 kernel leaves me staring at the Sammy S5 splash screen. No Sammy animation, no VZW red screen of boredom, nothing. I tried wiping cache and doing an FDR. No change. What am I doing wrong???

Tried CF Auto Root?
It'll trip KNOX, but if you're not bothered, it should work

The certainly is an option. Noway this S5 will ever see the inside of a VZW store.
I am, however, baffled as to why following the how-to's utterly fails. I have an extensive collection of flashable files, thanks to how-to's that say "use these files from Sammobile", and the ones that have them coming androidfilehost, and on and on. Worse, I have no idea if, for example, all of the NCG files are really the same thing with a different name or not. Meaning I'm really doing the same series of steps with only the names changed. Odin never says FAIL!, finds the device, it validates the md5 checksum, does its magic, and says PASS!. NTL, the phone either bootloops or otherwise doesn't do what it should. At the moment, wiping cache and doing a reset doesn't clear the problem (the S5 stops at the power-up splash and doesn't do so much as the Samsung animation).
Either all of the how-to's are bogus, which seems unlikely, the files listed below are all somehow defective but have good MD5 checksums (also unlikely), or there is something really odd about my phone. The only thing I can think of is I'm doing all of this without an SD installed. I can't see how that would be a problem. I can't imagine the SIM is a bad actor (I do get the right phone number after doing an FDR, BTW). So what's up?
Because things are so wonky, I'm a little uncomfortable with trying CF Auto Root, only to find I managed to brick the phone because of whatever weirdness seems to lurk somewhere in this project.
For laughs and grins, here's the collection to date:
{
"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"
}

Ahh, your S5 is on Verizon ?
Bootloaders are locked on those phones, so you won't be able to root or custom recovery using ODIN
Towelroot for 4.4.2 ROMs prior to June 2014 will work

This is, indeed, an SM-G900V from VZW. The how-to's (links follow) are for the same device. Odin works, to the point where 4.4.4 and 5.0 are functional. Even the WiFI problem, discussed earlier, takes "only" an FDR to put it right. Towelroot works for 4.4.2. What doesn't work is carrying rooting forward to 4.4.4 or, ideally, 5.0 (sure would be nice to extend to 5.1).
http://forum.xda-developers.com/showpost.php?p=55495211&postcount=1
http://www.droidviews.com/update-verizon-galaxy-s5-android-5-0-lollipop-retain-root/
http://androidbiits.com/root-verizon-samsung-galaxy-s5-sm-g900v-android-4-4-4-kitkat/
http://forum.xda-developers.com/ver.../safely-upgrade-root-4-4-4-nha-volte-t2879348 [ADDED]
Again, either all of these items are bogus, I'm doing something wrong, or the phone is not 100% healthy.

Success! I've at least left 4.4.2 behind for rooted 4.4.4. This is the how-to I followed:
http://forum.xda-developers.com/showpost.php?p=55495211&postcount=1
As best I can tell, the moment of actually rooting has the phone thinking it's running 4.4.2, thanks to the kernel, but it's somewhat in the 4.4.4 world, too. At least that's my ill-informed guess about how/why this hack works.
Of course, now it's on to trying to retain root under 5.0. At least, should 5.0 tank, I now know how to get back to a rooted 4.4.4.

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!~

[I337M] Samsung S4 Nand Reset Failure. [Thanks Samsung]

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!

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