Iffalcon 55k2a android tv stuck at boot screen. help! - General Questions and Answers

I own an iffalcon 55k2a android tv running oreo.
Suddenly yesterday the TV restarted while i was tinkering around the developer settings (i clicked on show pointer location) and from then on TV is not turning ON.
Stuck at Android booting screen. Tried entering recovery screen but showing android icon with ERROR as text. I didn't find any hard reset buttons on the TV.
Please help. How can i force reset the TV.

Please help me do a factory reset

Guys if there is any way to hard reset the android tv please help.

firoz3321 said:
I own an iffalcon 55k2a android tv running oreo.
Suddenly yesterday the TV restarted while i was tinkering around the developer settings (i clicked on show pointer location) and from then on TV is not turning ON.
Stuck at Android booting screen. Tried entering recovery screen but showing android icon with ERROR as text. I didn't find any hard reset buttons on the TV.
Please help. How can i force reset the TV.
Click to expand...
Click to collapse
Were you able to solve this issue?

firoz3321 said:
Guys if there is any way to hard reset the android tv please help.
Click to expand...
Click to collapse
If you connect a pc using adb, does it get any response to the TV?
Or, try this process to reflash/update the firmware, it should return to default settings. Just make sure you find the correct software for your specific tv then use this method to flash the firmware that you downloaded.
https://forum.xda-developers.com/android/general/iffalcon-tv-india-rom-links-t3892518
Sent from my SM-S767VL using Tapatalk
---------- Post added at 02:01 AM ---------- Previous post was at 01:44 AM ----------
prakash iyer said:
Were you able to solve this issue?
Click to expand...
Click to collapse
Check my post above if you are having issues, flashing the firmware via the manual update process might solve your issues.
Sent from my SM-S767VL using Tapatalk

Sorry for late response. I got my motherboard replaced as The technician was also unable to update.

I just got into the same trouble here, is there no alternative other than replacing the motherboard, cause my warranty is over just 10 days back. :'(

naveennamani said:
I just got into the same trouble here, is there no alternative other than replacing the motherboard, cause my warranty is over just 10 days back. :'(
Click to expand...
Click to collapse
Read this thread again, notice how no one was able to solve this issue in this thread, then carefully consider your question again.
The parts for these TV's are inexpensive.
Sent from my SM-S767VL using Tapatalk

I got it working without replacing the motherboard :good: , thanks

naveennamani said:
I got it working without replacing the motherboard :good: , thanks
Click to expand...
Click to collapse
You didn't have exactly the same issue for the same reasons, you got lucky.
Why don't you post how you got working, that way anyone that comes here looking for answers will find some potentially useful information instead of a thread full of posts that doesn't really help them find answers/solutions? All these other users didn't get anything useful out of this thread, maybe you can change for future visitors.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
You didn't have exactly the same issue for the same reasons, you got lucky.
Why don't you post how you got working, that way anyone that comes here looking for answers will find some potentially useful information instead of a thread full of posts that doesn't really help them find answers/solutions? All these other users didn't get anything useful out of this thread, maybe you can change for future visitors.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Yeah I'm sorry, I'm about to post how I solved.
I got into exactly the same problem, I've the same IFFALCON 55K2A TV, recently it got OTA update to the Oreo version, so I was just experimenting with the developer options, and clicked on the show pointer option in the developer settings, then the device restarted and stuck in the loading screen. When I tried to enter into recovery mode, it shown android icon with "error" text and the device restarted and stuck in the loading screen again.
At first, I downloaded the Oreo update from the following link, which was mentioned by you in this thread.
https://forum.xda-developers.com/android/general/iffalcon-tv-india-rom-links-t3892518
http://www.mediacenter.tcl.eu/uploads/common/MT58_Android O_V551.zip
I installed this update, but the same problem repeated. It got stuck in the loading screen.
As I observed this is a zip file with the update. but I've seen some threads where it was mentioned to use signed .pkg files than the zip files. After searching a bit, I found a thread
https://forum.xda-developers.com/android/general/iffalcon-tv-india-rom-links-t3892518/page6
and I got a v544 of the Oreo update whereas the OTA update is of v551.
https://drive.google.com/uc?id=1lr8sGZ7OF_Nylm6yWnrNrka9L_NplNS_&export=download
So, I installed this downgraded version, and I noticed that, when I installed this version, after installation finish, a screen was shown indicating the device memory is being erased which didn't happen when I installed v551.
After that, the setup screen came and the device turned ON after setup is complete.
I exactly don't know the reason for this behavior, but I assume that the developer settings kind of messed with the bootloader, and when I first updated with v551, it didn't effected the bootloader, and when I downgraded it restored the bootloader to the proper settings. If anyone understand what the problem might be, you can enlighten me.
I hope this answer helps someone out.

naveennamani said:
Yeah I'm sorry, I'm about to post how I solved.
I got into exactly the same problem, I've the same IFFALCON 55K2A TV, recently it got OTA update to the Oreo version, so I was just experimenting with the developer options, and clicked on the show pointer option in the developer settings, then the device restarted and stuck in the loading screen. When I tried to enter into recovery mode, it shown android icon with "error" text and the device restarted and stuck in the loading screen again.
At first, I downloaded the Oreo update from the following link, which was mentioned by you in this thread.
https://forum.xda-developers.com/android/general/iffalcon-tv-india-rom-links-t3892518
http://www.mediacenter.tcl.eu/uploads/common/MT58_Android O_V551.zip
I installed this update, but the same problem repeated. It got stuck in the loading screen.
As I observed this is a zip file with the update. but I've seen some threads where it was mentioned to use signed .pkg files than the zip files. After searching a bit, I found a thread
https://forum.xda-developers.com/android/general/iffalcon-tv-india-rom-links-t3892518/page6
and I got a v544 of the Oreo update whereas the OTA update is of v551.
https://drive.google.com/uc?id=1lr8sGZ7OF_Nylm6yWnrNrka9L_NplNS_&export=download
So, I installed this downgraded version, and I noticed that, when I installed this version, after installation finish, a screen was shown indicating the device memory is being erased which didn't happen when I installed v551.
After that, the setup screen came and the device turned ON after setup is complete.
I exactly don't know the reason for this behavior, but I assume that the developer settings kind of messed with the bootloader, and when I first updated with v551, it didn't effected the bootloader, and when I downgraded it restored the bootloader to the proper settings. If anyone understand what the problem might be, you can enlighten me.
I hope this answer helps someone out.
Click to expand...
Click to collapse
Yes, when I posted that link, I specifically stated that they needed to find the correct firmware and then I said to flash the firmware using the "instructions" in the link that I posted, I did not say to use the firmware linked in the guide from that thread.
Btw, the thread that you said you "found" is the exact same thread that I posted for them to use as instructions, the firmware you found must have been posted in another post somewhere in that thread.
The "show pointer" setting is meant for developers, it is something they use when developing the test builds of the firmware before the completed version is finalized. Part of its function is it displays information in the status bar detailing where the screen has been touched when this setting is enabled on a phone or tablet, but TV's do not have a status bar and most, if any, don't have touch functionality. When you enabled the setting, it was trying to display information in a status bar(a status bar that your TV doesn't have) and it was trying to detect, interpret and display touch input(touch input that it has no way of detecting because the TV has no touch related hardware). This creates a soft-brick scenario, which is what causes the device to bootloop after enabling the "show pointer" setting.
Sent from my SM-S767VL using Tapatalk

Sir Naveen namani Sir, please help me i am also facing the exact same issue my number is 8097703151 or 9699280535.

Tajammul163 said:
Sir Naveen namani Sir, please help me i am also facing the exact same issue my number is 8097703151 or 9699280535.
Click to expand...
Click to collapse
Just read their post and do the same thing they did.
Sent from my SM-S767VL using Tapatalk

Tcl iffalcon stuck on booting
Droidriven said:
Just read their post and do the same thing they did.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Naveen namani sir, i have 1 doubt v544 signed pkg file should be extracted or copy paste as it in the pendrive and it is should plugin in the first usb port?

Tajammul163 said:
Naveen namani sir, i have 1 doubt v544 signed pkg file should be extracted or copy paste as it in the pendrive and it is should plugin in the first usb port?
Click to expand...
Click to collapse
You don't need to extract anything from that pkg file. Put as it is in the formatted pendrive, I plugged the pendrive in second USB port, the update will take atleast 20min, and it doesn't show any progressbar kind of status, so just wait till the update process completes and the TV restarts

Thanks a lot for your help. Technician came and told me to change the motherboard, But i have tried your method and installed the OS. Really really helpful. we should not believe TCL/IFFalcon technicans, They cheat and they charge too much for their service and there is no proper rate card. Once again thanks a ton for your post.

Related

[Q] Help in returning to stock rom

So i'm looking for a little help.
A little while back I used this thread : [GUIDE] TF300T Unlock/Root/Flash for Factory JB Devices (newbie friendly)
To help me install this custom rom : [ROM][TF300]|Mar 28| Energy™ -.¸¸.·´¯ Official JB 4.2.1 Stock or Themed ¯´·.¸¸. -
onto my girlfriends TF300T tablet
and I have this : [RECOVERY][TF300T/TG] TWRP 2.5.0.0 Touch Recovery! [2013-4-9] on there as well
but I can't remember if this was part of the unlock/root/flash process or not, so i'm not sure if it used it during the process or if I added it shortly afterword
now its been while since I have done it but then the tablet started to restart randomly while she was using it.
so I figured no biggie maybe an app got messed up or something, and so I told her to back up her pics, exc she wanted off the unit
and I could look at reinstalling the apps or just taking the unit back to factory rom
about a week later it started to reboot more often randomly
and now it is to the point where it will not make it into the rom
now I can make it into the boot selection where I can choose RCK (for the TWRP), USB, or the other 2 options
and I know I can make it into the TWRP tool as well and it does not repeatedly boot from there, so i'm sure its a rom issue and not a hardware issue, but I could still be wrong
the unit is currently charging so I have not had a chance to try for the usb connection option or anything else yet
hopefully the usb option will work so I can try to recover the pics, exc before taking the unit back to factory
now in the process I know I have unlocked the unit, I believe I have done the min root but have not fully rooted the unit if that makes sense
so i'm just wondering if I will half to fully root (and how do I do that if I do since I can't make it into a rom)
how do I clear the rom that has gone bad
how do I install a factory rom (how do I tell which is the lastest rom, and which one is needed for my unit)
and then I should be good from there
if you need any more info please let me know and maybe some instructions on how to get to that info
in the process of putting the energy rom onto it, I spent a week of reading, researching, and figuring out which way would probably be the safest for me to do, plus the easiest for me to understand
now that it has been so long I have been reading and researching again, I just need that nudge that gets me in the right direction
i'm sure i'm not the only one that has had this issue with a rom, and i'm also sure there is a guide out there already that goes over how to put it back to a factory rom
just for some reason i'm either over looking it or not finding it
allusion said:
So i'm looking for a little help.
A little while back I used this thread : [GUIDE] TF300T Unlock/Root/Flash for Factory JB Devices (newbie friendly)
To help me install this custom rom : [ROM][TF300]|Mar 28| Energy™ -.¸¸.·´¯ Official JB 4.2.1 Stock or Themed ¯´·.¸¸. -
onto my girlfriends TF300T tablet
and I have this : [RECOVERY][TF300T/TG] TWRP 2.5.0.0 Touch Recovery! [2013-4-9] on there as well
but I can't remember if this was part of the unlock/root/flash process or not, so i'm not sure if it used it during the process or if I added it shortly afterword
now its been while since I have done it but then the tablet started to restart randomly while she was using it.
so I figured no biggie maybe an app got messed up or something, and so I told her to back up her pics, exc she wanted off the unit
and I could look at reinstalling the apps or just taking the unit back to factory rom
about a week later it started to reboot more often randomly
and now it is to the point where it will not make it into the rom
now I can make it into the boot selection where I can choose RCK (for the TWRP), USB, or the other 2 options
and I know I can make it into the TWRP tool as well and it does not repeatedly boot from there, so i'm sure its a rom issue and not a hardware issue, but I could still be wrong
the unit is currently charging so I have not had a chance to try for the usb connection option or anything else yet
hopefully the usb option will work so I can try to recover the pics, exc before taking the unit back to factory
now in the process I know I have unlocked the unit, I believe I have done the min root but have not fully rooted the unit if that makes sense
so i'm just wondering if I will half to fully root (and how do I do that if I do since I can't make it into a rom)
how do I clear the rom that has gone bad
how do I install a factory rom (how do I tell which is the lastest rom, and which one is needed for my unit)
and then I should be good from there
if you need any more info please let me know and maybe some instructions on how to get to that info
in the process of putting the energy rom onto it, I spent a week of reading, researching, and figuring out which way would probably be the safest for me to do, plus the easiest for me to understand
now that it has been so long I have been reading and researching again, I just need that nudge that gets me in the right direction
i'm sure i'm not the only one that has had this issue with a rom, and i'm also sure there is a guide out there already that goes over how to put it back to a factory rom
just for some reason i'm either over looking it or not finding it
Click to expand...
Click to collapse
Its very simple to return to stock. But first, do you have the tablets drivers installed on your pc?
---------- Post added at 06:16 AM ---------- Previous post was at 06:14 AM ----------
And do you have fastboot?
if you are talking about the android sdk tools
yes that is installed on my computer from the first time I did the tablet
and I went ahead and did the updates for it as well
and tried plugging the unit in with the fastboot and confirm it shows up in device manager
bump
hope you didn't forget about me crazynitro
allusion said:
bump
hope you didn't forget about me crazynitro
Click to expand...
Click to collapse
sorry, i got caught up with some school work. i could walk you through the process, if you want.
if you could please, any links, post, exc you want me to read ahead of time please post
anything you need me to verify or check on please let me know
gf starting to be up my butt about her tablet, lol
but yes any help is more then appreciated
allusion said:
if you could please, any links, post, exc you want me to read ahead of time please post
anything you need me to verify or check on please let me know
gf starting to be up my butt about her tablet, lol
but yes any help is more then appreciated
Click to expand...
Click to collapse
Lol okay. Theres actually a more simple way.
1. Download the latest asus firmware.
2. Extract the zip file
3. Flash it like a normal rom.
If you cant use this method then you'll have to use fastboot. Here's a link but if you need any help, just ask : http://www.androidauthority.com/transformer-pad-tf300t-restore-stock-firmware-108016/
how do I check the sku according to that guide if i'm not able to load into the android os
that only shows if you can load into the os
would the box have that?
or now looking at the options that I should assume its is a US sku lol
crazynitro said:
3. Flash it like a normal rom.
Click to expand...
Click to collapse
lol, and how do I do that using the twrp?
can't find any detailed instructions on using twrp on flashing a rom, especially the stock one
i'm sure there is a set of detailed instructions cause I swore I saw one once
but i'm not able to find it again
cause I thought besides using the install part there were things I had to clear as well for it to work
oh and yeah the download link for fastboot is no long working in the one guide you gave me to follow so not sure if I already have what it is talking about
allusion said:
lol, and how do I do that using the twrp?
can't find any detailed instructions on using twrp on flashing a rom, especially the stock one
i'm sure there is a set of detailed instructions cause I swore I saw one once
but i'm not able to find it again
cause I thought besides using the install part there were things I had to clear as well for it to work
oh and yeah the download link for fastboot is no long working in the one guide you gave me to follow so not sure if I already have what it is talking about
Click to expand...
Click to collapse
Its simple lol. When you download the firmware from asus, its usually in a .zip form. In it, there is another zip file. Copy that zip file onto your tablet and flash it with twrp.
crazynitro said:
Its simple lol. When you download the firmware from asus, its usually in a .zip form. In it, there is another zip file. Copy that zip file onto your tablet and flash it with twrp.
Click to expand...
Click to collapse
what about having to clear anything? I could of swore the instructions showed going to 2 or 3 spots for clearing data or info or something from the unit
allusion said:
what about having to clear anything? I could of swore the instructions showed going to 2 or 3 spots for clearing data or info or something from the unit
Click to expand...
Click to collapse
Yes. You have to do a factory reset first.
and how do I do that lol, and what happens when I don't do that first
is this tablet now dead since the step of doing the reset was not complete? cause now I can not access twrp and it just sits there with the asus logo and the swirling dots
when I try to access the usb option all I have is rck, android and wipe, rck just gives a failure shortly after trying
allusion said:
lol, and how do I do that using the twrp?
can't find any detailed instructions on using twrp on flashing a rom, especially the stock one
i'm sure there is a set of detailed instructions cause I swore I saw one once
but i'm not able to find it again
cause I thought besides using the install part there were things I had to clear as well for it to work
oh and yeah the download link for fastboot is no long working in the one guide you gave me to follow so not sure if I already have what it is talking about
Click to expand...
Click to collapse
If you want to use twrp, download the us stock firm ware. when you open it, you'll see a file that looks like this: "US_epad-user-10.6.1.15.3". copy that file onto your tablet and flash it like a normal rom. haha
For fastboot, if you have the android sdk, then you already have fastboot so you dont have to download fastboot again.
---------- Post added at 03:36 PM ---------- Previous post was at 03:32 PM ----------
allusion said:
is this tablet now dead since the step of doing the reset was not complete? cause now I can not access twrp and it just sits there with the asus logo and the swirling dots
when I try to access the usb option all I have is rck, android and wipe, rck just gives a failure shortly after trying
Click to expand...
Click to collapse
if you tried installing the newest firmware, you wont see the usb icon when you press power and volume+ it automatically enters fastboot. you dont have to select anything
---------- Post added at 03:39 PM ---------- Previous post was at 03:36 PM ----------
allusion said:
and how do I do that lol, and what happens when I don't do that first
Click to expand...
Click to collapse
if you cant enter twrp, then you dont have to worry about the factory reset you can flash the stock rom using fastboot.

[Q] Nexus 5 Bootloop

So let me start by saying I am 100% a noob, and I have read many threads trying to get to the bottom of my problem to no avail. I am sorry if there is a solution for my problem somewhere, I've been working on this issue for 24 hours and have yet to find it.
My girlfriend was apparently using google maps on here relatively new phone (running 5.0.1) and it crashed. Upon restarting it was stuck on the coloured dots screen for several hours. She has not installed any third party apps, only those from the playstore and not too many of them at that.
I tried factory reset and received a bunch of errors about failing to load the E:// or something like that. The phone still would not boot up.
I downloaded minimal fastboot thinger on my windows 8.1 laptop and tried to flash a new image of 5.0.1 on it, IIRC I received errors about E:// again
Got Wugfresh NRT and tried TWRP wiped all (still saw some stuff about E:// failing to mount and such) then tried to unroot flash stock with soft brick/bootloop checked.
Still bootlooped for over an hour when I started it up.
Tried flashing 4.4.4 instead. It worked. Phone booted up. Gallery/Camera do not work however at this point. Tried updating to 5.0.1.... phone restarted bootloop for 8 hours and counting.
Flashed 4.4.4 again, Followed Full Driver Installation Guide in NRT exactly. Tried Flash Stock + Unroot with Device is on/Normal checked this time instead. Now it has been colored dots screen for about 20 minutes.
So I can load 4.4.4 but no matter how I've tried to install lollipop 5.0.1, it stays on booting screen forever.
What do?
Thank you so much in advance and apologies for being a noob.
EDIT: More googling today. Looks like my E:/Persist partition is corrupted or something, trying to figure out how to repair it right now.
Anjo_Smash said:
So let me start by saying I am 100% a noob, and I have read many threads trying to get to the bottom of my problem to no avail. I am sorry if there is a solution for my problem somewhere, I've been working on this issue for 24 hours and have yet to find it.
My girlfriend was apparently using google maps on here relatively new phone (running 5.0.1) and it crashed. Upon restarting it was stuck on the coloured dots screen for several hours. She has not installed any third party apps, only those from the playstore and not too many of them at that.
I tried factory reset and received a bunch of errors about failing to load the E:// or something like that. The phone still would not boot up.
I downloaded minimal fastboot thinger on my windows 8.1 laptop and tried to flash a new image of 5.0.1 on it, IIRC I received errors about E:// again
Got Wugfresh NRT and tried TWRP wiped all (still saw some stuff about E:// failing to mount and such) then tried to unroot flash stock with soft brick/bootloop checked.
Still bootlooped for over an hour when I started it up.
Tried flashing 4.4.4 instead. It worked. Phone booted up. Gallery/Camera do not work however at this point. Tried updating to 5.0.1.... phone restarted bootloop for 8 hours and counting.
Flashed 4.4.4 again, Followed Full Driver Installation Guide in NRT exactly. Tried Flash Stock + Unroot with Device is on/Normal checked this time instead. Now it has been colored dots screen for about 20 minutes.
So I can load 4.4.4 but no matter how I've tried to install lollipop 5.0.1, it stays on booting screen forever.
What do?
Thank you so much in advance and apologies for being a noob.
Click to expand...
Click to collapse
If I can bet it must be a corrupted persist partition. Lollipop will not boot if its gets corrupted but kitkat will do. If you could tell what is the actual error you see in twrp or cwm recovery then we could identfy the actual problem. But I am 90% sure the mount error is about persist partition.
bitdomo said:
If I can bet it must be a corrupted persist partition. Lollipop will not boot if its gets corrupted but kitkat will do. If you could tell what is the actual error you see in twrp or cwm recovery then we could identfy the actual problem. But I am 90% sure the mount error is about persist partition.
Click to expand...
Click to collapse
You are correct sir I literally just identified that as the problem 5 minutes ago. Now the question is how do I fix it.
Anjo_Smash said:
You are correct sir I literally just identified that as the problem 5 minutes ago. Now the question is how do I fix it.
Click to expand...
Click to collapse
I made a thread about it. Here it is http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
bitdomo said:
I made a thread about it. Here is it http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
Click to expand...
Click to collapse
I'm actually looking at that right now! Downloading Java and Android SDK atm. Of course still a little shaky on a couple terms in your guide hopefully I can sort it out. Really confused as to how Google Maps on a vanilla nexus 5 could corrupt a partition like that, its all google endorsed and official. They should be fixing my phone not me lol.
Anjo_Smash said:
I'm actually looking at that right now! Downloading Java and Android SDK atm. Of course still a little shaky on a couple terms in your guide hopefully I can sort it out. Really confused as to how Google Maps on a vanilla nexus 5 could corrupt a partition like that, its all google endorsed and official. They should be fixing my phone not me lol.
Click to expand...
Click to collapse
If you want to make it quick then allow me to join to your pc through teamviewer. Send your ID and Passowrd to my e-mail: [email protected]
If you try to do it alone and you face a problem then I might not be here, because it is already past 11:30pm here.
bitdomo said:
If you want to make it quick then allow me to join to your pc through teamviewer. Send your ID and Passowrd to my e-mail: [email protected]
If you try to do it alone and you face a problem then I might not be here, because it is already past 11:30pm here.
Click to expand...
Click to collapse
Thanks for the offer. I'll try on my own and get back to you maybe tomorrow if I can't get it down.
Alright so I am definitely having problems running adb shell. even if I change the directory in cmd to my adb.exe location (android\android-sdk\platform-tools) I keep getting the error adb shell is not a recognized blah blah blah....
NVM got it working. Whenever I get frustrated enough to make a post I end up finally finding a solution.
ALRIGHT I have Lollipop up and running thanks to your guide on fixing persist partition. Thank you so much! Question: I have a nexus 5 and it does not have an sd card. I'm not sure how to proceed in doing the steps you described involving mac addresses. I did use a hex editor and make those files, but not sure where to put them in my phones internal storage, and how to direct adb to said location. Any help with that?
Anjo_Smash said:
ALRIGHT I have Lollipop up and running thanks to your guide on fixing persist partition. Thank you so much! Question: I have a nexus 5 and it does not have an sd card. I'm not sure how to proceed in doing the steps you described involving mac addresses. I did use a hex editor and make those files, but not sure where to put them in my phones internal storage, and how to direct adb to said location. Any help with that?
Click to expand...
Click to collapse
Just copy them to the root of your internal storage, then follow the guide.
I mean you just open the phone's internal storage from your PC and you dont open any folder. You just copy it there.
The guide is for nexus 5, but some people refer to the internal storage as sdcard too. I know it is a bit confusing. Thanks to point it out. I will make clear in my guide now.
AH I see ok I will do that tonight. Ran in to another problem though it may be related to the mac address thing I haven't done yet, not sure how that all works. The phone randomly restarts every few minutes and it won't connect to the carrier either. Also if it matters I left the boot loader unlocked for now until the phone is working properly, if that affects anything.
Anjo_Smash said:
AH I see ok I will do that tonight. Ran in to another problem though it may be related to the mac address thing I haven't done yet, not sure how that all works. The phone randomly restarts every few minutes and it won't connect to the carrier either. Also if it matters I left the boot loader unlocked for now until the phone is working properly, if that affects anything.
Click to expand...
Click to collapse
The lock state of the bootloader does not matter, but this random reboots after a few minutes is something to worry about. Your phone should not do that after formating persist partition.
bitdomo said:
The lock state of the bootloader does not matter, but this random reboots after a few minutes is something to worry about. Your phone should not do that after formating persist partition.
Click to expand...
Click to collapse
Should I try formatting it again?
Anjo_Smash said:
Should I try formatting it again?
Click to expand...
Click to collapse
Give another try formating persist, but I am here now. So, if you want I can do everything for you through teamviewer. You just have to send the log in informations to my email address.
bitdomo said:
Give another try formating persist, but I am here now. So, if you want I can do everything for you through teamviewer. You just have to send the log in informations to my email address.
Click to expand...
Click to collapse
Ok I'm going to install team viewer then.
bitdomo said:
Give another try formating persist, but I am here now. So, if you want I can do everything for you through teamviewer. You just have to send the log in informations to my email address.
Click to expand...
Click to collapse
I'm all set up, so let me know when you are available friend, thanks for your help.
Anjo_Smash said:
I'm all set up, so let me know when you are available friend, thanks for your help.
Click to expand...
Click to collapse
I am here, send the login infos -> [email protected]

Help, I can't get past the WIFI screen and I can't flash a new rom on this phone

Hello guys,
I need your assistance with this issue. I got this Boost Mobile LG LS770/Stylo phone from eBay and when I wiped/restored it to clean everything from the other person, the phone still wants me to enter the information from the previous person before I can use it. Of course that is not an option. I tried.
Also, since I am unable to get to the Android OS, I cannot put it in debug mode either. So I tried a few things to no avail. This is what I have done so far:
Put the phone in ADB mode via recovery - Done, but I am unable to sideload anything. I get this error.. "* cannot read 'sideload' *"
Put the phone in download mode "Fireware Update" - Done, and I can see my port as COM3, but when I run the next step, I get a message that says... "Hello, my name is LAF....." and nothing happens.
I tried using the LG one click root tool, but that requires the phone to be in USB debug mode and like I said before, I am unable to even get to the welcome screen in android. I can't get past wifi setup in reality, I can't even skip it.
I have been at this all day today. Can you please help me out? I really appreciate any help you can provide.
Thanks
You need a USB-OTG cable and some files. If you have a USB-OTG i'll reply with what you'll need to do. Also, have you contacted the eBay member letting them no they FRP screwed you and you basically own a brick now?
revulv said:
You need a USB-OTG cable and some files. If you have a USB-OTG i'll reply with what you'll need to do. Also, have you contacted the eBay member letting them no they FRP screwed you and you basically own a brick now?
Click to expand...
Click to collapse
I have OTG cable... Can you help me out??
revulv said:
You need a USB-OTG cable and some files. If you have a USB-OTG i'll reply with what you'll need to do. Also, have you contacted the eBay member letting them no they FRP screwed you and you basically own a brick now?
Click to expand...
Click to collapse
Thank you for your response. I have one. Please go ahead with the steps.
revulv said:
You need a USB-OTG cable and some files. If you have a USB-OTG i'll reply with what you'll need to do. Also, have you contacted the eBay member letting them no they FRP screwed you and you basically own a brick now?
Click to expand...
Click to collapse
Also, I forgot to respond to your question. I did contact the eBay guy or lady that sold it to me, but since I'm the one that did the wipe, they are not taking responsibility and I get it. I just would like to be able to use the phone and not waste the money I spent on it. I really appreciate any help you or others can provide.
Have OTG cable & flashdrive
revulv said:
You need a USB-OTG cable and some files. If you have a USB-OTG i'll reply with what you'll need to do. Also, have you contacted the eBay member letting them no they FRP screwed you and you basically own a brick now?
Click to expand...
Click to collapse
I am stuck in the same boat, bought what appears to be a brick. Would be most grateful if I could get the files/procedure you mentioned as well.
Sorry guys!
https://www.youtube.com/watch?v=xNSBbpVOmb4
Thank you for the suggestion , but this method does not work. I have already tried this and after the tool went through all the steps, it still asks for the previous account. I have found on some other forums that LG patched this flaw a few months ago and it is no longer possible to bypass FRP Factory Reset Protection. I guess I have a rock until someone can figure out how to bypass this "Feature", which in my opinion should be illegal because it forces people to buy devices from carriers only and you can no longer sell your phone online to anyone, as you cannot give them the account.
webmanny said:
but this method does not work..
Click to expand...
Click to collapse
It didn't work for me either... the last security patch disabled user from the settings menu. I did find a way after many hours of work.
Basically once I got to settings I clicked unknown sources and then enabled USB debugging and oem unlock. After that I flashed twrp and then a rooted system image. After that I used http://androiding.how/bypass-google-account-verification-on-lg-g4-g3-and-others and it worked
Sent from my HTC One M9 using XDA-Developers mobile app
bigp951 said:
Basically once I got to settings I clicked unknown sources and then enabled USB debugging and oem unlock. After that I flashed twrp and then a rooted system image. After that I used http://androiding.how/bypass-google-account-verification-on-lg-g4-g3-and-others and it worked
Click to expand...
Click to collapse
How did you get to settings? I am only able to get to the accessibility to turn on the voice stuff.
webmanny said:
How did you get to settings? I am only able to get to the accessibility to turn on the voice stuff.
Click to expand...
Click to collapse
I honestly don't remember. I'll try to figure it out and get back to you. I think it was through the keyboard. I returned the phone already so I do t have it on front of me.
Look for anything with terms of service. Once you're on the internet you can download the settings app that everyone uses on the internet.
Sent from my HTC One M9 using XDA-Developers mobile app
Web trust me i went crazy with this for 3 days. My friend gave me his Stylo from work to unlock and i had this same issue. Flashed back to 5.1.1e,i,j, using kdz files and all the exploits that these guys are using have been shut down. If your on MM forget it. The only thing that worked for me was that tool i linked in the other thread. I hope your wrong on the virus part, ill check my laptop, but your the first person to mention that. Either way i flashed back to 5.1.1 from MM, used the tool, rebooted and it worked i signed in with his gmail.
sshafranko said:
Web trust me i went crazy with this for 3 days. My friend gave me his Stylo from work to unlock and i had this same issue. Flashed back to 5.1.1e,i,j, using kdz files and all the exploits that these guys are using have been shut down. If your on MM forget it. The only thing that worked for me was that tool i linked in the other thread. I hope your wrong on the virus part, ill check my laptop, but your the first person to mention that. Either way i flashed back to 5.1.1 from MM, used the tool, rebooted and it worked i signed in with his gmail.
Click to expand...
Click to collapse
I understand and I apologize if I sounded like I was shutting your advise down. That was not my intention. I was just stating what my virus tools detected and my experience. Regardless, I decided to ignore the virus warning and let the tool run and do what the steps on the word document stated. It went through all the steps without issues and I got the same matching screen as in the tutorial document. However, after I reboot, I still get the same screen that reads, login with a google account previously associated with this device.
Now, the one piece I'm not sure I understand from your message above is the part about flashing to 5.1.1 from MM using kdz files. How can you flash the phone when you cannot get into the settings to enable usb debug mode? I have tried everything. I even downloaded a rom file image that I placed on an Micro SD card and tried running it from recovery to no avail.
Maybe you are correct and I am just missing a step. Would you mind expanding on the flashing 5.1.1 from MM part? Maybe what steps and files you had to use?
Also, I'm not sure I understand this portion of your message. You signed in with who's gmail?
sshafranko said:
i signed in with his gmail.
Click to expand...
Click to collapse
Thank you in advance for your assistance.
is there a software older than 5.1.1 that can be flashed to the device?
You can use touch assistant to get in to settings and then disable all google aps, works for me on lg stylo 6.0, PaulieP he is the person that found this method

Adb update! Plz help stuck in recovery! [Q&A],[SOFTBRICK/BOOTLOOP], QTAQZ3

Hello everyone, I have a tablet that is stuck in recovery and looks to me ADB is going to be the only way out here. Problem is ADB isnt recognizing my device, device manager named it MTP but computer says Android. I have tried changing the USB /VID ID that reads off what is displayed in Device manager not sure if I did it right running myself crazy really, read HRS of Android info Im a noob but a fast learner especially if I get a little bit of guidance. I have tried doing every and all factory hard resets tried different flash tools probably didnt work because my computer doesnt display the correct model. Im trying to learn python at the very moment new to all of this have only hrs of experience of this all. Somebody plz be ever so kind to help me out, thanks!
Device-State:Recovery/Bootloader
Ellipsis 8
QTAQZ3
Vendor:Verizon Wireless
Build:KTO49
4.2KitKat
samson716 said:
Hello everyone, I have a tablet that is stuck in recovery and looks to me ADB is going to be the only way out here. Problem is ADB isnt recognizing my device, device manager named it MTP but computer says Android. I have tried changing the USB /VID ID that reads off what is displayed in Device manager not sure if I did it right running myself crazy really, read HRS of Android info Im a noob but a fast learner especially if I get a little bit of guidance. I have tried doing every and all factory hard resets tried different flash tools probably didnt work because my computer doesnt display the correct model. Im trying to learn python at the very moment new to all of this have only hrs of experience of this all. Somebody plz be ever so kind to help me out, thanks!
?
Click to expand...
Click to collapse
You want help with a device but you don't tell us any kind of information about your device, how smart was that? What you need and how to do it can depend on what device model number you have.
Sent from my SM-S903VL using Tapatalk
SORRY
Droidriven said:
You want help with a device but you don't tell us any kind of information about your device, how smart was that? What you need and how to do it can depend on what device model number you have.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Not very smart at all sorry about that! I didnt disclose that, reason being the research i have done everybod turns there head when this crap device is mentioned. Yes I agree not worth time and energy but already invested so much time its worth it to me and also i have.
Ellipsis8
QTAQZ3/4.2Jellybean/KTO49
samson716 said:
Not very smart at all sorry about that! I didnt disclose that, reason being the research i have done everybod turns there head when this crap device is mentioned. Yes I agree not worth time and energy but already invested so much time its worth it to me and also i have.
Ellipsis8
QTAQZ3
4.2Kitkat
KTO49
Thanks!
Click to expand...
Click to collapse
samson716 said:
samson716 said:
Not very smart at all sorry about that! I didnt disclose that, reason being the research i have done everybod turns there head when this crap device is mentioned. Yes I agree not worth time and energy but already invested so much time its worth it to me and also i have.
Ellipsis8
QTAQZ3
4.2Kitkat
KTO49
Thanks!
Click to expand...
Click to collapse
are you using stock recovery or a custom recovery?
Click to expand...
Click to collapse
ayu321 said:
samson716 said:
are you using stock recovery or a custom recovery?
Click to expand...
Click to collapse
Stock
Click to expand...
Click to collapse
samson716 said:
ayu321 said:
Stock
Click to expand...
Click to collapse
Can you please tell me that what caused this problem ? what were you doing with the device? flashing roms ?
Click to expand...
Click to collapse
ayu321 said:
samson716 said:
Can you please tell me that what caused this problem ? what were you doing with the device? flashing roms ?
Click to expand...
Click to collapse
No I was literally doing nothing I was actually flashing my Samsung Device at that moment. From what I remember it occurred when I noticed at update to marshmallow updated then rebooted it. Ever since its been in this bootloop! Im not trying to root it put a custom rom on it just want it to function nothing special.
Click to expand...
Click to collapse
samson716 said:
ayu321 said:
No I was literally doing nothing I was actually flashing my Samsung Device at that moment. From what I remember it occurred when I noticed at update to marshmallow updated then rebooted it. Ever since its been in this bootloop! Im not trying to root it put a custom rom on it just want it to function nothing special.
Click to expand...
Click to collapse
You have soft bricked your phone . The only way to fix it is it flash its stock rom. If you are new to this stuff I would suggest you to read this article carefully and if you have any doubts , ask me.
https://www.maketecheasier.com/android-root-custom-recovery-and-roms/
Click to expand...
Click to collapse
samson716 said:
Hello everyone, I have a tablet that is stuck in recovery and looks to me ADB is going to be the only way out here. Problem is ADB isnt recognizing my device, device manager named it MTP but computer says Android. I have tried changing the USB /VID ID that reads off what is displayed in Device manager not sure if I did it right running myself crazy really, read HRS of Android info Im a noob but a fast learner especially if I get a little bit of guidance. I have tried doing every and all factory hard resets tried different flash tools probably didnt work because my computer doesnt display the correct model. Im trying to learn python at the very moment new to all of this have only hrs of experience of this all. Somebody plz be ever so kind to help me out, thanks!
Device-State:Recovery/Bootloader
Ellipsis 8
QTAQZ3
Vendor:Verizon Wireless
Build:KTO49
4.2KitKat
Click to expand...
Click to collapse
Where did this problem start? Did you cause this by modifying, attempting to root or flashing the device with something that caused this?
If so, about your only option is to use your device's flashtool to flash the stock firmware. If your device's stock firmware isn't available then you might be out of luck repairing your device. If this is the case then your only other option might be getting someone that has a device exactly like yours that is rooted and getting them to pull copies of the various .img files needed for your device then using adb shell to dd those .img files on your device. But, to be honest, I don't think this is gonna happen for you. You probably will have to take the device to a repair shop. It will probably be cheaper to just buy another tablet because the cost of repair will probably be more than what you paid for the device.
Sent from my SM-S903VL using Tapatalk
ayu321 said:
samson716 said:
You have soft bricked your phone . The only way to fix it is it flash its stock rom. If you are new to this stuff I would suggest you to read this article carefully and if you have any doubts , ask me.
https://www.maketecheasier.com/android-root-custom-recovery-and-roms/
Click to expand...
Click to collapse
Okay not sure which Flash tool to use nor get my stock rom I dread to say but i dont think there is one available. Its a generic tablet its made by Quanta. Not sure how to put it in a download mode either I assume ADB is the only way to transfer any files.
Click to expand...
Click to collapse
Your device probably uses SPFlashtool or fastboot.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Where did this problem start? Did you cause this by modifying, attempting to root or flashing the device with something that caused this?
If so, about your only option is to use your device's flashtool to flash the stock firmware. If your device's stock firmware isn't available then you might be out of luck repairing your device. If this is the case then your only other option might be getting someone that has a deuce exactly like yours that is rooted and getting them to pull copies of the various .img files needed for your device then using adb shell to dd those .img files on your device. But, to be honest, I don't think this is gonna happen for you. You probably will have to take the device to a repair shop. It will probably be cheaper to just buy another tablet because the cost of repair will probably be more than what you paid for the device.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Its pretty easy to fix a soft bricked device , even if stock rom isnt available , any rom compatible with his device can fix the issue .
ayu321 said:
Its pretty easy to fix a soft bricked device , even if stock rom isnt available , any rom compatible with his device can fix the issue .
Click to expand...
Click to collapse
To be compatible, the ROM typically has to be ported and that usually requires the stock firmware or stock source from the device that the ROM is being ported over to. 99% of the time you can't just flash a ROM from a different model number, even if the CPU is the same, there's quite a bit more to it than that. The android operating system is built for the specific hardware it is installed on, the two devices would have to be exactly the same and have the exact same components, any differences in hardware make he firmwares incompatible.
For this particular device, I doubt the stock firmware or stock source code area available, even if it were, porting another ROM wouldn't be necessary because if it were available it could just be flashed with that instead of porting a ROM.
About the only time a ROM from a different model number can be used without any porting or edits being made is when the devices are exactly the same device just rebranded with a different "name".
But thanks for trying to tell me something that you thought I didn't know, now it seems I've told you something that you didn't know.
Sent from my SM-S903VL using Tapatalk
samson716 said:
ayu321 said:
Okay not sure which Flash tool to use nor get my stock rom I dread to say but i dont think there is one available. Its a generic tablet its made by Quanta. Not sure how to put it in a download mode either I assume ADB is the only way to transfer any files.
Click to expand...
Click to collapse
1.Search for your tablet's root package , download it and move it to your tablet's sd card. Then enter your recovery mode by pressing power button+ Home button+ Volume button at same time for 10sec. Once entered , go to option "apply update from sd card" and select the root package you downloaded. (CONGRATS YOU HAVE ROOTED YOUR PHONE!)
2.Search for your tablet's 'custom recovery' , download it and flash it through odin tool(pc) .
3.Final Step ! BASED ON THE RECOVERY YOU FLASHED THESE STEPS MAY DIFFER , SO REPLY ME IF YOU SUCCEED IN FLASHING CUSTOM RECOVERY
Click to expand...
Click to collapse
ayu321 said:
1.Search for your tablet's root package , download it and move it to your tablet's sd card. Then enter your recovery mode by pressing power button+ Home button+ Volume button at same time for 10sec. Once entered , go to option "apply update from sd card" and select the root package you downloaded. (CONGRATS YOU HAVE ROOTED YOUR PHONE!)
2.Search for your tablet's 'custom recovery' , download it and flash it through odin tool(pc) .
3.Final Step ! BASED ON THE RECOVERY YOU FLASHED THESE STEPS MAY DIFFER , SO REPLY ME IF YOU SUCCEED IN FLASHING CUSTOM RECOVERY
Click to expand...
Click to collapse
Odin is for Samsung devices, not other devices.
The device they are repairing is not a Samsung device. They have this device and a Samsung device. The issue on this device occurred while they were in the process of flashing their Samsung device.
I know you're trying to help but don't post anything unless you are absolutely certain that you know what you're talking about.
In this case, you didn't and that can easily lead to a hard bricked device because they followed your instruction.
Stick to answering questions about devices you personally have dealt with, don't go assuming that you understand someone else's device. They are all different, the methods, tricks and tools for one won't necessarily work on another.
You understand android somewhat but judging by your posts, you don't understand the differences in devices and methods. But you will after you've been here a while.
Sent from my SM-S903VL using Tapatalk
---------- Post added at 10:39 PM ---------- Previous post was at 10:32 PM ----------
DO NOT USE ODIN ON YOUR DEVICE!!!
Odin is only for Samsung devices.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Where did this problem start? Did you cause this by modifying, attempting to root or flashing the device with something that caused this?
If so, about your only option is to use your device's flashtool to flash the stock firmware. If your device's stock firmware isn't available then you might be out of luck repairing your device. If this is the case then your only other option might be getting someone that has a device exactly like yours that is rooted and getting them to pull copies of the various .img files needed for your device then using adb shell to dd those .img files on your device. But, to be honest, I don't think this is gonna happen for you. You probably will have to take the device to a repair shop. It will probably be cheaper to just buy another tablet because the cost of repair will probably be more than what you paid for the device.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
thankyou so much for the fast responses much appreciated to take your time to explain. Okay i have a question what would be the course of detailed action to preform getting any and all missing .img's it may need. Also i know its a crazy question but would i be able to preform this in store with the displayed tablet that matches mine? How difficult is something like this, and is there any other methods at all I can try to boot past this bootloader. And now that i remember correctly from reading others this happened when I upgraded to 5.1 or 5.0 thank you everybody once again!
samson716 said:
thankyou so much for the fast responses much appreciated to take your time to explain. Okay i have a question what would be the course of detailed action to preform getting any and all missing .img's it may need. Also i know its a crazy question but would i be able to preform this in store with the displayed tablet that matches mine? How difficult is something like this, and is there any other methods at all I can try to boot past this bootloader. And now that i remember correctly from reading others this happened when I upgraded to 5.1 or 5.0 thank you everybody once again!
Click to expand...
Click to collapse
No, you wouldn't be able to get it from a tablet in the store, it's a rather involved process that requires connecting the device to PC, it also requires rooting the device and flashing a custom recovery, and that's all before you actually get to where you can pull the files. It'll take a couple of hours,or more to do it.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
No, you wouldn't be able to get it from a tablet in the store, it's a rather involved process that requires connecting the device to PC, it also requires rooting the device and flashing a custom recovery, and that's all before you actually get to where you can pull the files. It'll take a couple of hours,or more to do it.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Is there absolutely anything i can try, just a long shot in the dark?
samson716 said:
Is there absolutely anything i can try, just a long shot in the dark?
Click to expand...
Click to collapse
The only other option is pretty risky. You can try a firmware from another device that has the same CPU and hardware as your device, you'd have to compare specs. It would have to have the same CPU, same screen resolution, same camera(front and rear), same amount of RAM, same amount of internal storage, same accelerometers, etc.. It has to have all the same components that yours has.
Sent from my SM-S903VL using Tapatalk

SM-G955U1. XAA version. Bootloop problem, any help?

MY BAD, PLEASE MOVE THIS TO THE CORRECT SECTION. I'M REALLY SORRY.
Hello!, my mother bought this phone for her in the US and from day 0 it has been having problems. She couldn't use wifi or bluetooth for example, and sometimes it just kept restarting till it worked again, but without any connectivity functions, except mobile data.
I tried to fix this updating the phone using Samsung Smart Switch to the last build (AQL1) but now the phone is stuck on the boot screen no matter what I do.
Tried flashing with Odin, it worked, but the phone is still on boot loop. I read somewhere in this forum that you can install an older version of the bootloader to take the phone out of this hell and I did it, using the build AQK2 bootloader but no luck, same problem.
Also, the phone doesn't have USB debugging enable nor OEM unlock either. I can access both recovery and download mode though.
At this point I'm out of ideas, can someone help me with this one?
Thanks in advanced.
fefin
fefin said:
MY BAD, PLEASE MOVE THIS TO THE CORRECT SECTION. I'M REALLY SORRY.
Hello!, my mother bought this phone for her in the US and from day 0 it has been having problems. She couldn't use wifi or bluetooth for example, and sometimes it just kept restarting till it worked again, but without any connectivity functions, except mobile data.
I tried to fix this updating the phone using Samsung Smart Switch to the last build (AQL1) but now the phone is stuck on the boot screen no matter what I do.
Tried flashing with Odin, it worked, but the phone is still on boot loop. I read somewhere in this forum that you can install an older version of the bootloader to take the phone out of this hell and I did it, using the build AQK2 bootloader but no luck, same problem.
Also, the phone doesn't have USB debugging enable nor OEM unlock either. I can access both recovery and download mode though.
At this point I'm out of ideas, can someone help me with this one?
Thanks in advanced.
fefin
Click to expand...
Click to collapse
Have you reached out to Samsung yet?
Mr. Orange 645 said:
Have you reached out to Samsung yet?
Click to expand...
Click to collapse
Thanks for answering. Where I live there is not a single Samsung Service, only at like 1800km from here, that's why I'm trying to solve this by myself but seems that this is a hard one... I hope someone can help me to deal with this as it was a big investment :/
Thanks again!, if someone knows a way to help please tell me.
fefin
fefin said:
Thanks for answering. Where I live there is not a single Samsung Service, only at like 1800km from here, that's why I'm trying to solve this by myself but seems that this is a hard one... I hope someone can help me to deal with this as it was a big investment :/
Thanks again!, if someone knows a way to help please tell me.
fefin
Click to expand...
Click to collapse
I mean have you called or emailed Samsung?
Mr. Orange 645 said:
I mean have you called or emailed Samsung?
Click to expand...
Click to collapse
No I haven't, I will give a try soon through web chat.
I mean, this shouldn't be happening, it's a brand new phone, all over the internet are people with the same problems as me and looks like so far there is no solution.
Maybe it's a faulty phone/hardware? My knowledge is not enough in this matter.
See you!,
Federico.
I need a couple things from you
1. What model does it say on the back of the phone i understand you posted it in the header but please for safety sake .
2. Go into download mode for me so i can see what carrier it lists
3. Try wiping data cache in recovery
Sent from my SM-G955U1 using XDA-Developers Legacy app
allenjthomsen said:
I need a couple things from you
1. What model does it say on the back of the phone i understand you posted it in the header but please for safety sake .
2. Go into download mode for me so i can see what carrier it lists
3. Try wiping data cache in recovery
Sent from my SM-G955U1 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Thanks for answering!, here it goes:
1. It says SM-G955U1
2. Carrier: XAA
3. Done, still the same.
An update from my last post:
After a few bootloops the FRP screen showed up, as the phone can't use wifi yet I managed to access using mobile data and enabled the USB debugging, but after trying to enable wifi the phone froze and went on bootloop again, so still the same but with the USB debugging enabled. I'm currently on the build AQK2.
Thanks again, and I hope we can fix this.
Update 2:
I cleared the cache, after a few bootloops the phone actually boots (gets to the lock screen), and it restarts again while the message "Android is starting" is loading, so now it's a different type of bootloop I guess. It does the same even in safe mode.
I will turn it off for now.
fefin said:
Thanks for answering!, here it goes:
1. It says SM-G955U1
2. Carrier: XAA
3. Done, still the same.
An update from my last post:
After a few bootloops the FRP screen showed up, as the phone can't use wifi yet I managed to access using mobile data and enabled the USB debugging, but after trying to enable wifi the phone froze and went on bootloop again, so still the same but with the USB debugging enabled. I'm currently on the build AQK2.
Thanks again, and I hope we can fix this.
Update 2:
I cleared the cache, after a few bootloops the phone actually boots (gets to the lock screen), and it restarts again while the message "Android is starting" is loading, so now it's a different type of bootloop I guess. It does the same even in safe mode.
I will turn it off for now.
Click to expand...
Click to collapse
Ok i want you to do a couple things for me
1.Download this file http://updato.com/firmware-archive-select-model?record=F837B5F2EC0611E7A5F9FA163EE8F90B this is the latest update for the G955U1
2. extract the zip file using 7zip so you have 5 .tar.md5 files
3. go to the CSC_OYM_G955U1OYM2AQL1_CL12513005_QB15986651_REV00_user_low_ship_MULTI_CERT.tar.md5 and right click on the file and goto 7-zip and then click open archive
4. you will see a file called DREAM2QLTE_USA_SINGLE.pit i want you to extract it to the folder you have Odin in if not quick search forums for it
5. Open odin and go to the the pit tab it will do a pop up just click ok and ignore
6. click the pit button and find the pit file that you extracted and select it
7. now go to options tab
8.check to make sure you have auto reboot, re-partition, and f reset timer checked
9.Load BL,AP,CP,CSC in respective slots on right side
10. click start and let the phone flash, as soon as it is done hold volume up bixby and power button wait for recovery to load and wipe data and factory reset.
11. reboot and let it boot if you are still in a bootloop after these steps pm me and i will help you the last way i know how to fix these phones.
allenjthomsen said:
Ok i want you to do a couple things for me
1.Download this file http://updato.com/firmware-archive-select-model?record=F837B5F2EC0611E7A5F9FA163EE8F90B this is the latest update for the G955U1
2. extract the zip file using 7zip so you have 5 .tar.md5 files
3. go to the CSC_OYM_G955U1OYM2AQL1_CL12513005_QB15986651_REV00_user_low_ship_MULTI_CERT.tar.md5 and right click on the file and goto 7-zip and then click open archive
4. you will see a file called DREAM2QLTE_USA_SINGLE.pit i want you to extract it to the folder you have Odin in if not quick search forums for it
5. Open odin and go to the the pit tab it will do a pop up just click ok and ignore
6. click the pit button and find the pit file that you extracted and select it
7. now go to options tab
8.check to make sure you have auto reboot, re-partition, and f reset timer checked
9.Load BL,AP,CP,CSC in respective slots on right side
10. click start and let the phone flash, as soon as it is done hold volume up bixby and power button wait for recovery to load and wipe data and factory reset.
11. reboot and let it boot if you are still in a bootloop after these steps pm me and i will help you the last way i know how to fix these phones.
Click to expand...
Click to collapse
Sadly it didn't work. The phone is still loading till "android is starting" sign and then restarting again.
I will write you so you can help me through pm, could this be a faulty hardware?
I'd like to know the other solution too.
I will tell you all what todo as a last resort.
IF YOU CHOOSE TO DO THIS I TAKE NO RESPONSIBILITY IF YOUR DEVICE STOPS WORKING OR DOES NOT TURN ON!!!
Follow all previously said steps i outlined but when you go into the options tab select nand erase all also then flash device.
Sent from my SM-G955U1 using XDA-Developers Legacy app
try installing PartCyborgRom
@fefin -Sorry to hear that you're having issues - But I'd like to clear one thing up - Your comment that this is an issue "all over the internet" sim isn't true... I don't know how many Millions of S8 / S8+ have been sold - But your post is the first that I've ever heard of anything like this... I concur with the recommendation that you call or Chat with Samsung Technical Support - Preferably before you find the phone completely unable to Boot into Download Mode - Get Samsung to help you - or you may risk voiding the warranty if Samsung determines that you are ultimately responsible for the state of the phone ??
Sent from my SM-G955W ??
allenjthomsen said:
I will tell you all what todo as a last resort.
IF YOU CHOOSE TO DO THIS I TAKE NO RESPONSIBILITY IF YOUR DEVICE STOPS WORKING OR DOES NOT TURN ON!!!
Follow all previously said steps i outlined but when you go into the options tab select nand erase all also then flash device.
Sent from my SM-G955U1 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Thanks for your help! Much appreciated.
DR25 said:
try installing PartCyborgRom
Click to expand...
Click to collapse
Thanks for your suggestion, I will look into it.
shaggyskunk said:
@fefin -Sorry to hear that you're having issues - But I'd like to clear one thing up - Your comment that this is an issue "all over the internet" sim isn't true... I don't know how many Millions of S8 / S8+ have been sold - But your post is the first that I've ever heard of anything like this... I concur with the recommendation that you call or Chat with Samsung Technical Support - Preferably before you find the phone completely unable to Boot into Download Mode - Get Samsung to help you - or you may risk voiding the warranty if Samsung determines that you are ultimately responsible for the state of the phone
Sent from my SM-G955W
Click to expand...
Click to collapse
Thanks for answering!, sorry for my late response.
Well, if you check samsung's official forum there are a few threads with 15+ pages of people complaining about wifi issues (https://us.community.samsung.com/t5/forums/v3_1/forumtopicpage/board-id/GS8QA/thread-id/862/page/1 and https://us.community.samsung.com/t5/forums/v3_1/forumtopicpage/board-id/GS8QA/thread-id/30601/page/1) about bootloop problems, (https://us.community.samsung.com/t5...id/GS8QA/thread-id/3920/highlight/true/page/1) also there is a post on another webpage talking about bootloops on this model and how to fix them (https://thedroidguy.com/2017/12/sol...p-issue-s8-turns-screen-remains-black-1079013).
I know it's not representative, as you said, millions of phones has been sold, but what I meant when I said "all over the internet" is that you can easily find people with this same problem. This shouldn't be happening, not on any phone even less on such an expensive phone.
I think the phone is officially dead, I took it to a well known local technician and even him couldn't fix it. My nearest official samsung service is 1600km away. On the other hand, my aunty got for herself an S8 and it's working perfect, so it's just bad luck for my mom I guess.
The phone had issues since she bought it (wifi and bluetooth didn't worked at all, but she is not really a tech person so she thought it was fine), the phone was working with some bootloops from time to time and after a while it fell from and got a little crack on the top but it didn't change the behavior of the phone, it was still ****ed up. That's the thing, because of the crack I'm pretty sure they won't take it back or even try to fix it (for free at least), they will say the problem is because of the fall. I'd been reading a lot about this and seems that I'm pretty screwed D:
I will sell the phone for parts. At least I will recover 60% of the initial investment.
fefin said:
That's the thing, because of the crack I'm pretty sure they won't take it back or even try to fix it (for free at least), they will say the problem is because of the fall. I'd been reading a lot about this and seems that I'm pretty screwed D:
I will sell the phone for parts. At least I will recover 60% of the initial investment.
Click to expand...
Click to collapse
If you have some 'proof' the problem existed, before the crack, and can prove when the crack occurred, or reasonable determinate approximation, small claims court will vindicate you, and Samsung will have to pay.
Sad to say would take a little time of yours to get them there, but it is an easy process, and with reasonable ability to determine/evidence those two things, a sure win.
But still a PITA.

Categories

Resources