Trying to use cyanogenmod installer: We couldn't talk to your phone - T-Mobile Samsung Galaxy S II SGH-T989

Hello community,
I'm a noob trying to flash a ROM. Since cyanogenmod made it easy with their installer, that's what im trying. I did everything correctly including downloading recovery software and installer but when i hit "Begin," installer gives me an error:
We couldn't talk to your phone
I tried different USB cable, port, restarting computer, restarting phone normally and removing battery (some treads recommended this) and still no luck. I also disabled anti virus too.
here is the support token:
Support token: 112540a6-3081-49a3-9e7d-03fe931f7d21
Help, please. I have lived with this crap stock samsung for 2 years and want free of it.
Much thanks.

rfjfj said:
Hello community,
I'm a noob trying to flash a ROM. Since cyanogenmod made it easy with their installer, that's what im trying. I did everything correctly including downloading recovery software and installer but when i hit "Begin," installer gives me an error:
We couldn't talk to your phone
I tried different USB cable, port, restarting computer, restarting phone normally and removing battery (some treads recommended this) and still no luck. I also disabled anti virus too.
here is the support token:
Support token: 112540a6-3081-49a3-9e7d-03fe931f7d21
Help, please. I have lived with this crap stock samsung for 2 years and want free of it.
Much thanks.
Click to expand...
Click to collapse
And you are sure you can copy files to and from your phone? Did you also make sure you have the Samsung ADB drivers installed? I have not tried this method but I'm sure ADB is involved somehow and gonna play a big part in getting the recovery onto the phone which will allow you to install Cyanogenmod.
Otherwise, do it the "hard" way. It might be easier that way than to wait for someone to figure out your problem.

For me manually entering download mode, and hitting retry made it work.
I don't recommend,using any mods people, I did so, camera wasn't workin,random crashes,and lost IMEI, don't bother,go with official.
Thanks to kies I got my note 2 back..I will never ever bother with cyan mod anymore.

Related

[Q] Can't get phone to re-root, please help

Previously I had installed on my phone (I believe, but could be mistaken) a Twilight Kernel and Hurricane v1.6 Rom. Well, I had nothing but problems with the rom, and put up with them for some time, just because I didn't have time to go through and find a rom I liked and flash it. I decided to do just that yesterday.
Apparently my mind broke and I did something wrong (probably numerous things). I had first attempted to put the shiney new CWM9 with Shadow Kernel on, rather, I made the mistake of trying to just put the Shadow Kernel on after having done a full (triple) wipe on my phone. I got the boot loop for the kernel since there was no rom (duh) loaded. Okay, no problem, I'll toss a rom on the SD and boot into CW3 and flash it? Yeah, not so much. I got a short "Samsung" logo boot loop and could not get into CW3 after that.
So, I Odin'd it back to EL30, thinking I'll just start from fresh, right?
Wrong.
Next in the series of mistakes I made, I forgot that I had already downloaded and installed the Samsung drivers (don't ask, my brain was apparently on leave yesterday) and attempted to re-install them. They did not like this and would not progress and I had to End Process the install from Task Manager. I then uninstalled the drivers completely fearing that I may have corrupted them by trying to re-install and then EP'ing them.
I then re-installed them, or so I thought. Plug phone in and start again with One Click Root. Fail. The script couldn't find my device.
Hours of searching and trying different things later, script still couldn't find my device, though I now have both the phone recognizing there is a USB connection, and the computer has stopped yelling at me that there are no drivers (I believe it finally gave up and installed the Windows drivers for it). But still can't get it rooted or do anything but stock stuff.
So..
1:Samsung drivers won't install, running Windows 7-64 Ultimate; error at end of install just states: "The MMS InstallWizard was not successfully installed SAMSUNG USB Driver for Mobile Phones v1.3.450.0."
2hone previously recognized USB Debug mode, but no longer. Will only Recognize standard USB connection, and with the connection made to PC, the script will not recognize the device.
3:adb for all intensive purposes does not appear to be loading..per the message from the script "Root was not obtained after 60 seconds. Make sure the phone is connected and that adb is working. If adb shell isn't root, reboot the phone and try the script again." I've rebooted numerous times, but I'm pretty certain that since it's not going into Debug, it's just not being recognized.
I have even tried Gingerbreak with no luck, just continuously sits on the rooting screen, but never proceeds (upwards 45 minutes I let it go).
Please please please please help me fix all the mistakes I did and get this thing working again and get the damned drivers installed proper.
(Baseband-S: D700.0.55.EL30, Kernel version 2.6.35.7, Build number: Gingerbread.EL30)
Note* I am happy with any root/kernel/rom at this point, I don't care, I just want the damned thing rooted again.
And of course after I finally cave and post for help, I find the thread where it clearly states OneClick Root no longer works for Gingerbread...so we'll add that into the mistakes I made...
Question still stands, how do I get this rooted again?
Qbking77 youtube him...
Or I could do it for you remotely via teamviewer... either way
Sent from my SPH-D700 using xda premium
AtrophiedAnnie said:
And of course after I finally cave and post for help, I find the thread where it clearly states OneClick Root no longer works for Gingerbread...so we'll add that into the mistakes I made...
Question still stands, how do I get this rooted again?
Click to expand...
Click to collapse
If you are up and running EL30 just Google How to Root Samsung Epic on EL30 and a qbking77 youtube video will pop up and all the links are there as well for the files you need. If you are not up and running then you need to go into the Roll Up sticky thread in Development and click on How to Restore a semi-bricked Samsung Epic....all links are there for that including 64bit drivers.
Sent from my SPH-D700 using xda premium
Found it all, getting it working now. Thanks all. We'll chalk this up to ...noobi-ness....(ignoring that I've been rooted and doing this for a year now... >.> )
AtrophiedAnnie said:
Found it all, getting it working now. Thanks all. We'll chalk this up to ...noobi-ness....(ignoring that I've been rooted and doing this for a year now... >.> )
Click to expand...
Click to collapse
Sounds more like serious root rust to me. Gotta keep up...lol. Samsung tries to make it harder to root...that works for 5 minutes around here...LOL.
Sent from my SPH-D700 using xda premium
IT'S DONE!!! Again thank you both so much1

Putting a 100$ bounty for someone to fix my phone (SGH-i317M)

I am at my wits end to try to repair my phone. It is softbricked and responds to download mode only.
I've had chat with xda members and read threads on it:
http://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096
http://forum.xda-developers.com/galaxy-note-10-1/help/help-help-unbricking-galaxy-note-10-1-t2872125
and many others. in the end, my phone is still stuck with the NAND Write Start error with odin.
I know it happened after i tried creating a backup of my phone in recovery mode (phone was rooted with cf auto root and had a version of CWM on it). CWM gave me a warning about possibly bricking the phone, i agreed to the warning beacuse it always worked in the past, but when i rebooted, it was bricked this time.
this phone is not dead but samsung won't fix it beacuse it is rooted. I refuse to throw it away. I have read many people have it this error since kitkat 4.4 so surely there is a fix somewhere. I am hoping somebody will be more resourceful/experienced than i am.
I have tried changing to several different USB ports, without a hub, using original cables (bunch of different ones too) in many many different order and fashion. I tried enough variation to be convinced it is statistically impossible that all my hardware that was previously working for flashing has stopped working all at once. aka - it is not a usb port or data cable problem
may be related to data charging port on the phone though I highly suspect it given how it started.
I tried different roms, different versions of odin, i tried depackaging and repackaging roms, i simply do not know what to do anymore.
i tried reflashing with kies but kies just dies on me.
i tried flashing it with adb but adb won't even connect. when i plug the phone windows recognizes it and usb driver seems to work ok (not getting an error)
I have uninstalled and reinstalled drivers several times, rebooting in between installs. no difference.
i tried flashing different bootloaders as well as entire roms, no difference
I tried changing the pit file but that failed as well (odin couldn't even write the pit so my phone is not dead even if i failed pitting it)
i have access to both windows and ubuntu linux if it makes a difference.
Here are the terms of the bounty:
Price : 100$ (payable by paypal from eniac0 @ "some google mail domain starting with gm"
goal : find a fix that works on the latest firmware for SGH-i317M (Rogers, Canada)
how : i don't know but i need to be able to reproduce it. I am not new to flashing but anything advanced will need to be explained clearly.
I don't really know how this sorts of request usually turns out but i am serious. you even got my google mail address to bill me up if i fail to pay.
have you given a look at this thread? http://forum.xda-developers.com/showthread.php?t=2711825 it might give you some ideas to help you out. also did you try flashing a new recovery to see if you could at least get it to boot to that?
dont care about the bounty just trying to toss something out there that may help you
Did you ever try flashing the stock recovery - JUST the stock recovery - through Odin?
If not, grab the recovery.img and make your own tarball for Odin in Linux.
Hopefully that will flash and get you closer.
eniac0 said:
I am at my wits end to try to repair my phone. It is softbricked and responds to download mode only.
...
i have access to both windows and ubuntu linux if it makes a difference.
Click to expand...
Click to collapse
Since you mentioned Ubuntu, you can also try using heimdall instead of odin... http://glassechidna.com.au/heimdall/ . Unfortunately, I think it may be a hardware problem?
Since you are willing to pay to have it fixed, if all else fails, you can always send it off to http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-note-jtag-brick-repair/. It will actually be cheaper than what you are offering to pay ~$40 + shipping
good luck
Thanks all for your help, I've messed around and gotten no closer. I'm beginning to lean on a hardware failure, perhaps from the usb data port either that or the way bootloaders are packaged in kitkat 4.4 is different. which is why initially this thread gave me hope: http://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096 but i tried far too many times now to believe I'm going to succeed. In fact, I've gotten confused as to what i tried, in which order, with which rom. I'm basically trying anything and that's a recipe for bricking the phone for good. so i've stopped.
I'll also thank kozmo21 for the link to the repair shop. i was unaware this existed, as a last resort I'll be sending them my phone. If it turns out they are able to repair it, I'll honor my word and give you something for having been part of the solution.
eniac0 said:
I am at my wits end to try to repair my phone. It is softbricked and responds to download mode only.
I've had chat with xda members and read threads on it:
http://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096
http://forum.xda-developers.com/galaxy-note-10-1/help/help-help-unbricking-galaxy-note-10-1-t2872125
and many others. in the end, my phone is still stuck with the NAND Write Start error with odin.
I know it happened after i tried creating a backup of my phone in recovery mode (phone was rooted with cf auto root and had a version of CWM on it). CWM gave me a warning about possibly bricking the phone, i agreed to the warning beacuse it always worked in the past, but when i rebooted, it was bricked this time.
this phone is not dead but samsung won't fix it beacuse it is rooted. I refuse to throw it away. I have read many people have it this error since kitkat 4.4 so surely there is a fix somewhere. I am hoping somebody will be more resourceful/experienced than i am.
I have tried changing to several different USB ports, without a hub, using original cables (bunch of different ones too) in many many different order and fashion. I tried enough variation to be convinced it is statistically impossible that all my hardware that was previously working for flashing has stopped working all at once. aka - it is not a usb port or data cable problem
may be related to data charging port on the phone though I highly suspect it given how it started.
I tried different roms, different versions of odin, i tried depackaging and repackaging roms, i simply do not know what to do anymore.
i tried reflashing with kies but kies just dies on me.
i tried flashing it with adb but adb won't even connect. when i plug the phone windows recognizes it and usb driver seems to work ok (not getting an error)
I have uninstalled and reinstalled drivers several times, rebooting in between installs. no difference.
i tried flashing different bootloaders as well as entire roms, no difference
I tried changing the pit file but that failed as well (odin couldn't even write the pit so my phone is not dead even if i failed pitting it)
i have access to both windows and ubuntu linux if it makes a difference.
Here are the terms of the bounty:
Price : 100$ (payable by paypal from eniac0 @ "some google mail domain starting with gm"
goal : find a fix that works on the latest firmware for SGH-i317M (Rogers, Canada)
how : i don't know but i need to be able to reproduce it. I am not new to flashing but anything advanced will need to be explained clearly.
I don't really know how this sorts of request usually turns out but i am serious. you even got my google mail address to bill me up if i fail to pay.
Click to expand...
Click to collapse
Have you tried going to sammobile and download the newest firmware and only flashing that in odin?
Use CF auto root. Put the phone in download mode and flash it in Odin. I soft bricked my phone and it fixed it.
Also this guy had great walk through videos on how to do everything you need.
http://www.rootjunky.com/samsung/samsung-galaxy-note-2/
If it works to fix your phone. Keep your money. I'll take the karma points for putting you on the correct path.
Sent from my SHIELD Tablet using XDA Free mobile app
ShrekOpher said:
Use CF auto root. Put the phone in download mode and flash it in Odin. I soft bricked my phone and it fixed it.
Also this guy had great walk through videos on how to do everything you need.
http://www.rootjunky.com/samsung/samsung-galaxy-note-2/
If it works to fix your phone. Keep your money. I'll take the karma points for putting you on the correct path.
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
More than likely its a bootloader issue my phone did that and all i did was flash the bootloader then it worked again but hes done so much idk what he needs now that's y i said to try a firmware to see if that helps
Download toolkit and select option to push file into phone.
Download a ROM of your choosing, push it into your phone, restart in recovery mode and select file.
Update?
Did you get it fixed? Just my two cents, in case you didnt, I had a similar problem and alll I did to fix it was flash the JediMasterX2 ROM with CWM and everything worked out.

[Q] Unsure if my LG G3 is fixable, please say it is

Ok, so lets start with hello you wonderful smart people
I did something very stupid and I'm really hoping there is a solution to my foolishness.
I have an LG G3 LS990, I had previously rooted and all was well. However, I decided I would flash a custom ROM after staying up all night. And in doing so I managed to take the steps terribly wrong, and I formatted the phone completely.
Along with this, I didn't realize at that moment that the phone was being it's finicky self, and had decided not to register as connected through ADB, and only connect enough to charge...
So, I've looked at pretty much everything that has to do with unbricking an LG G3 and it seems that without USB connectivity, I am pretty much boned. But I still have hope.
Basically where I'm at now is, I can turn the phone on, but all I see is the LG loading screen and nothing else happens until the battery dies, if unplugged.
I can use the volume up + plug in micro USB to reach the firmware upgrade screen, but I am unable to make either of my computers (windows 8.1 laptop/windows 10 desktop) register that it's connected through USB.
From what I can tell, the volume down + power, release at loading screen, repress volume down + power method doesn't seem to do anything besides turn on the phone and freeze at the loading screen.
So what I'm asking, essentially, is: Is there a magic method of making my computer recognize my shell of a phone that I haven't seen? because once I can do that, the firmware upgrade stock flash option becomes viable.
Thanks in advance for any help you guys and gals can give.
xSandmanx59 said:
I have an LG G3 LS990, I had previously rooted and all was well. However, I decided I would flash a custom ROM after staying up all night. And in doing so I managed to take the steps terribly wrong, and I formatted the phone completely.
Along with this, I didn't realize at that moment that the phone was being it's finicky self, and had decided not to register as connected through ADB, and only connect enough to charge...
So, I've looked at pretty much everything that has to do with unbricking an LG G3 and it seems that without USB connectivity, I am pretty much boned. But I still have hope.
Basically where I'm at now is, I can turn the phone on, but all I see is the LG loading screen and nothing else happens until the battery dies, if unplugged.
I can use the volume up + plug in micro USB to reach the firmware upgrade screen, but I am unable to make either of my computers (windows 8.1 laptop/windows 10 desktop) register that it's connected through USB.
From what I can tell, the volume down + power, release at loading screen, repress volume down + power method doesn't seem to do anything besides turn on the phone and freeze at the loading screen.
So what I'm asking, essentially, is: Is there a magic method of making my computer recognize my shell of a phone that I haven't seen? because once I can do that, the firmware upgrade stock flash option becomes viable.
Thanks in advance for any help you guys and gals can give.
Click to expand...
Click to collapse
Hah! I did this once not too long ago on another LG device. Easy to make a mistake when you're tired.
You'll need to use the key combo to get to TWRP (should be Power + Down). TWRP is capable of transfer through ADB and it will also recognize an external SD card if you put one in it. That would eliminate a few steps with checking drivers and such. So you can then move the ROM and Gapps to the internal SD card and install from there.
epidenimus said:
Hah! I did this once not too long ago on another LG device. Easy to make a mistake when you're tired.
You'll need to use the key combo to get to TWRP (should be Power + Down). TWRP is capable of transfer through ADB and it will also recognize an external SD card if you put one in it. That would eliminate a few steps with checking drivers and such. So you can then move the ROM and Gapps to the internal SD card and install from there.
Click to expand...
Click to collapse
Thank you for the response. It's a surprisingly easy error indeed. Since I posted this, I figured out the key press you mentioned and have been trying ROM after ROM intended for my phone specifically, yet all of them will end one of 3 ways.
I get a black screen with itty bitty little text saying fastboot mode and restart.
I get everything ready and I boot up, it loads until about the wifi set up and then it will either freeze for a couple seconds and go to a black screen which requires a battery pull.
Or, I get a bsod with the options of volume up = dload and volume down = reboot.
So far I've tried candy5, CM 12.1/11, blisspop, paranoid android, cloudy, and dirty unicorn.
Not sure what I'm doing wrong with these. I use TWRP to wipe everything except external sd, install from there, reboot, and repeat.
I fixed it!! thanks to http://forum.xda-developers.com/sprint-lg-g3/development/rom-stock-zv6-base-odex-deodex-t2949087
this ROM is the only one I could find that worked. I'd still love to be able to upgrade to L but it seems like all of the 5.x roms crash during setup. Not sure what this is due to, but I have a working phone, so I'm not too upset by it.
If anyone has any info on why all the lollipop ROMs are having trouble on here I would appreciate it much.
Well it WAS fixed.... All was fine and well until there was a software update, I clicked install, it tried to reboot, and now I'm stuck in a custom recovery boot loop. I still can't connect to either of my PCs by USB and using my SD card to flash ROMs isn't doing anything now, just boots straight into TWRP every time, after full wiping and re-flashing several times now I'm really not sure how to fix this one.
Update:
Got past the bootloop from another thread on here which had a flashable fix. Now that I did that I'm actually able to use 5.x ROMs it seems. Currently working on Blisspop 3.5, once I get GAPPS to flash correctly, I think I aughta have a working Lollipop phone
Make sure you are using the correct TWRP for your device, having Bumped, as needed. Also, make sure you use the correct version of Gapps; it matters based on the version of Android your ROM is based upon.
Good luck and enjoy!
Good points. From what I can tell I have gotten everything to remain stable now. Blisspop 3.5 and the CM 12.1 GAPPs from http://wiki.cyanogenmod.org/w/Google_Apps seem to be the winning combo. The GAPPs that was listed in the Blisspop thread as the "best" seems to be the reason that my previous flash attempts were crashing upon boot. It might be one of the 86 different apps that were included in there rather than the simple 12 of the CM 12.1 GAPPs.
Either way. I've had no issues now except for the previous issue of USB debugging simply refusing to work. I have installed the latest drivers for LG devices and have tried every article's suggestions I could find on how to make my phone be recognized. I've also tried a few different root required apps that are supposed to fix issues of USB connections. None of them seem to do anything. I've also tried different cords, different plugs and different computers. But it seems like the only kind of USB recognition for my phone is when it's off it can charge. It won't charge while it's on unless I've charged it a minimum of 2% while it was off (regardless of the current battery level) and it can't be recognized as a USB device at all.
Any advice for this? Thanks in advance.
xSandmanx59 said:
Good points. From what I can tell I have gotten everything to remain stable now. Blisspop 3.5 and the CM 12.1 GAPPs from http://wiki.cyanogenmod.org/w/Google_Apps seem to be the winning combo. The GAPPs that was listed in the Blisspop thread as the "best" seems to be the reason that my previous flash attempts were crashing upon boot. It might be one of the 86 different apps that were included in there rather than the simple 12 of the CM 12.1 GAPPs.
Click to expand...
Click to collapse
It seems like the trend with ROM publishers is to not update some of those details in the threads; in the VZW variant, I know the BlissPop title still reads 5.0.x when they have been on 5.1 for some time.
I have tried a bunch of packages and have been using the Slim Gapps zero package + the DPI mod for a while now. They work great; there is even a tutrorial on how to roll your own if you like to have somewhere between 12-86.
xSandmanx59 said:
Either way. I've had no issues now except for the previous issue of USB debugging simply refusing to work. I have installed the latest drivers for LG devices and have tried every article's suggestions I could find on how to make my phone be recognized. I've also tried a few different root required apps that are supposed to fix issues of USB connections. None of them seem to do anything. I've also tried different cords, different plugs and different computers. But it seems like the only kind of USB recognition for my phone is when it's off it can charge. It won't charge while it's on unless I've charged it a minimum of 2% while it was off (regardless of the current battery level) and it can't be recognized as a USB device at all.
Any advice for this? Thanks in advance.
Click to expand...
Click to collapse
Some troubleshooting questions:
I think your OS may not supported for Android SDK. Have you ever had it recognized on these machines through ADB before? Windows takes like 5 years to get to the point where most of the drivers work.... I know it's possible in Win7 at this point, but I wouldn't expect it to work in 8.1 or Win10. Someone else who uses it may be able to help with that.
What are the driver's requirements? These are more variables associated with Windows...
Have you enabled USB debugging in the ROM, via the Developer menu? Many ROMs still have this hidden by default.
What version of the Android SDK/Studio are you running?
Have you added the platform-tools to the SDK, as required?
Can you get ADB to recognize the device when you connected and are in TWRP?
epidenimus said:
It seems like the trend with ROM publishers is to not update some of those details in the threads; in the VZW variant, I know the BlissPop title still reads 5.0.x when they have been on 5.1 for some time.
I have tried a bunch of packages and have been using the Slim Gapps zero package + the DPI mod for a while now. They work great; there is even a tutrorial on how to roll your own if you like to have somewhere between 12-86.
Some troubleshooting questions:
I think your OS may not supported for Android SDK. Have you ever had it recognized on these machines through ADB before? Windows takes like 5 years to get to the point where most of the drivers work.... I know it's possible in Win7 at this point, but I wouldn't expect it to work in 8.1 or Win10. Someone else who uses it may be able to help with that.
What are the driver's requirements? These are more variables associated with Windows...
Have you enabled USB debugging in the ROM, via the Developer menu? Many ROMs still have this hidden by default.
What version of the Android SDK/Studio are you running?
Have you added the platform-tools to the SDK, as required?
Can you get ADB to recognize the device when you connected and are in TWRP?
Click to expand...
Click to collapse
Thank you for the response. I have noticed that a few small things are not so frequently updated in the copy/paste updates of the ROM threads. But that's to be expected =P Anyways, to answer your questions:
What are the driver's requirements? These are more variables associated with Windows...
I'm not entirely sure about this one. I know I found the drivers on the LG website for my LS990 model and I also installed a few others including older/latest/various models to test if any of them would work. I'm running windows 8.1 currently and the ls990 seems to have a little less support as the PC suite for LG doesn't include this model in their driver list.
Have you enabled USB debugging in the ROM, via the Developer menu? Many ROMs still have this hidden by default.
Yes, it's been a long running issue on stock, stock rooted, and blisspop all with debugging on. I was able to connect to both of my computers for a long while until one day it just stopped. It was much worse than it is now. For a few days, then it decided to charge up to about 4% when I plugged it in with no battery and then put the battery back and waited for about 3-4 hours. Then I could turn it on long enough to selectively power down and it would then charge while powered off. Over the past couple days I've been able to plug it in and reboot to get it charging again... So bothersome. As for USB debugging, not sure when it stopped exactly but I assume it was around the same time (2 months ago)
What version of the Android SDK/Studio are you running?
I have the latest version of android studio from their website.
Have you added the platform-tools to the SDK, as required?
Yes, I believe so. I'm not 100% on the SDK stuff.
Can you get ADB to recognize the device when you connected and are in TWRP?
No. There is no response from my computer at all during any of the stages of driver and twrp and studio installations. Nothing is listed in my device menu either.
Beyond this, today my phone ran out of battery while I was out and about and then has refused to charge by any method. Then I finally got it to turn on to power down etc so it would charge about 3 hours later. Once I was able to boot back up I went out to smoke and came back to my phone somehow automatically flashing a different version of blisspop that had something about user_modified in the file name which then unloaded all of my saved layouts and whatnot. After about 20 minutes of reorganizing it went black, and has since been locked in a bootloop which has survived full wipes and re-installations of the previous version of blisspop I had been using. I just downloaded the latest version for ls990 once more, and I'll report back with whether or not that fixed the issue at hand.

No OS will install properly, odin won't work, need help with TWRP on N5110

This is my first post, so please forgive any mistakes I make with a post.
My wife's Galaxy Note 8.0 tablet was being stupid, it would refuse to properly use the internet from our Asus router, would connect but apps would insist there was no connection. Was getting tired of that crap so I decided to install a custom ROM, since samsung can be kind of jackasses abandoning most their devices after one major update, was only running Kitkat for crying out loud. I had done so before, but issues arouse. For one, I had great difficulty finding a proper TWRP for some stupid reason, NO ONE seamed to know where to get a well working version. I found one, but it messed everything up, it seems to work just fine but any ROM I install has massive issues with the Google apps, they crash eternally and continuously so I can do literally nothing, can't even get past first setup. I came across talk that it was old TWRP to blame, that it has issues with newer OS's like the lollipop I was trying to install, and FINALLY managed to find a newer version of TWRP, but freaking Odin keeps hanging on it's install, gets to "Nand write start" then stops doing anything. I have tried different cables as well as different computers, does jack crap so far to help. My backup I made in TWRP doesn't even work, when I restore the result is nothing but a boot loop. I am trying to find a stock os to restore it to (mostly) original condition, but it is absurdly difficult for some stupid reason to find, found one all in one exe that didn't work for a damn. I was hoping there might even be a way to install the newer TWRP from with TWRP itself. Can anyone help me with any part of this?
First things first. Calm down.
Do you have Samsung Smart Switch installed on your pc? If not, do so.
Connect your note 8.0 to your pc, select the 'more' button and then Emergency software recovery and initialization. Let that run is course. It can take a while.
See if that helps.
kge420 said:
First things first. Calm down.
Do you have Samsung Smart Switch installed on your pc? If not, do so.
Connect your note 8.0 to your pc, select the 'more' button and then Emergency software recovery and initialization. Let that run is course. It can take a while.
See if that helps.
Click to expand...
Click to collapse
Sorry, but you are going to have to be a little more specific. I installed Switch, but connecting an off device obviously does nothing, should I install and let it boot into a broken ROM again, where gapps crashes, and connect it then?
If your main isues are with GApps try clearing the cache in the play store app, check the date and time on your device.
I literally just got my Note 8 up and running after suffering these same issues you describe. My thread on this:
http://forum.xda-developers.com/galaxy-note-8-0/help/note-8-0-stuck-screen-t3218608
I'll try my best to help you. I received some good advice and I 'd like to help someone as a show of appreciation.
We'll get this straight!
Thanks, pretty much.
kge420 said:
If your main isues are with GApps try clearing the cache in the play store app, check the date and time on your device.
I literally just got my Note 8 up and running after suffering these same issues you describe. My thread on this:
http://forum.xda-developers.com/galaxy-note-8-0/help/note-8-0-stuck-screen-t3218608
I'll try my best to help you. I received some good advice and I 'd like to help someone as a show of appreciation.
We'll get this straight!
Click to expand...
Click to collapse
None of what you said really made sense, I could not get to ANYTHING AT ALL that was not Odin or TWRP. But that link you had gave me the name for the stock os, I searched that and flashed it and now everything is great. So thanks, sort of. You even mentioned that method not working for you I think in that thread, but it did for me, so yeah.
All good then.

Zenfone 5z brick-ish..?

Hello everyone. I am stuck in a bit of a draining situation. and I really hope that some of you, may be able to help.
I have 3 kids with each their phone, all of them have been registered to Googles Family Link service. Recently the account that managed them all got suspended for being hijacked and therefor it broke their terms, and now 4 accounts are locked. Google will not help me, to release the accounts the kids have, so they can use their phones again. So I tried following a guide on bypassing the log in prompt after a factory reset on this specific device. It happily activated the tap talk function, but when I try to open Google Assistant, nothing happens. I've tried looking it the settings of Tap Talk to find any clues, but to no avail.
I have searched for different variations of the same procedure on Youtube and Google and I can't seem to get further than described..
I then decided to try unlocking the bootloader or re-flashing the stock firmware, hoping to wipe the existing system completely. The re-flashing part, well. I found the Asus Zenfone Flash tool, but I am not too sure what to do. The guide seemed a bit confusing to me, so I tried the Bootloader, since I used to flash and root all my phones back when HTC was big. I have installed Quallcomms drivers, Asus-android_USB drivers, generic Android Usb drivers and restarted the pc to make sure that was done right.
The phone however is another problem. I haven't been able to enable usb-debugging thanks to Family Link preventing access to Dev-mode, before I did the Factory reset. I can read the phone's name on the ADB update option, when I boot it to stock recovery. But any commands, makes it hang with "waiting for any device", which, from what I understand, is a driver related issue. So I have updated the drivers as each guide has descibed.
My plan was to install the latest Lineage Rom, so I have the most recent files for that.
So now I ask you. I have downloaded Rom files, Gapps, 2 types of recovery img files, but for now, I am stuck and sad and I need a Yoda in this matter. The entire situation is probably solved with a simple click or command that I am not aware of.
If you need any further info I will do my best to help. My kindest and biggest thanks to anyone that provide some help.
Kind regards
Johnny

Categories

Resources