Hey,
I've tried rooting my SAmsung A5, however, I somehow cant access the teamwin/twrp menu.
I put the SUFile on my phones internal storage, USB DEBUG mode is on and OEM Mode as well-
I've flashed the twrp file with odin on the mobile successfully, however, now I'm stuck.
Whenever I press the volume up, homebutton and powerbutton after leaving the download mode the mobile just restarts the whole time and never accesses recovery mode until I release the keys and afterwards the phone just boots like usually, when I restart the phone and try to access the menu again a menu opens which says no command or something like that...
I also bricked the mobile after trying a few thing but restored it to stock firmware again, however, rooting still does not work..
can someone help me out?
MEHEYVISSE said:
Hey,
I've tried rooting my SAmsung A5, however, I somehow cant access the teamwin/twrp menu.
I put the SUFile on my phones internal storage, USB DEBUG mode is on and OEM Mode as well-
I've flashed the twrp file with odin on the mobile successfully, however, now I'm stuck.
Whenever I press the volume up, homebutton and powerbutton after leaving the download mode the mobile just restarts the whole time and never accesses recovery mode until I release the keys and afterwards the phone just boots like usually, when I restart the phone and try to access the menu again a menu opens which says no command or something like that...
I also bricked the mobile after trying a few thing but restored it to stock firmware again, however, rooting still does not work..
can someone help me out?
Click to expand...
Click to collapse
Sorry, you are in the a5 2017 forum not 2016. Anyway I think this should help you. DO NOT use the twrp files from there though. https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
Related
hi. I encountered a problem on my phone that doesn't boot properly.
When i tried to switch on my phone it showed at first the welcome msg "Samsung S4 mini gt-i9192" then after that, a pitch black screen, could not properly boot. But i learn that it does not turns off after the screen turns all black, i have to press the power button first to turn off the phone.
This problem started when i installed an app with some compatibility problems.
I wanted to root my phone hoping that can solve the problem, but then again a problem occurred when i tried to connect my phone to my laptop. It fails to install MTP usb device to my computer. I tried connecting it again provided that samsung kies was installed but again failed to connect my phone. Therefore i cant root my phone because i cant copy the files needed to root to my phone sd card.
I tried reinstalling kies, installing mtp drivers but nothing happened. I tried also restoring the previous boot image, restoring factory settings using recovery mode. But then problem still exist.
And fyi my phone can't mount any external sd card using recovery mode. And i think it was not in a debugging mode.
Phone: samsung s4 mini gt-i9192
firmware: i dont know
So basically, the problem is:
my phone wont boot,
i cant connect it to my pc
and i cant root it.
How should i root or even flash my phone when i cant connect to my computer? Do you have any idea on how to solve this problem? Any solutions or suggestions would be much appreciated. tnx.
champagneerantja
emzgames said:
snipped.
Click to expand...
Click to collapse
Have you tried putting the phone in download mode (Volume Down + Home + Power) and then connecting it your p,c , if not give this a shot it should pick up the drivers , once done , take out the usb cable hold the power the button to shut down and boot up .
since you have not mentioned your OS am assuming it is windows , try taking out Kies via some software like revo uninstaller which will remove all directories plus all registry entires then reinstall it if you really need it.
dovakinn said:
Have you tried putting the phone in download mode (Volume Down + Home + Power) and then connecting it your p,c , if not give this a shot it should pick up the drivers , once done , take out the usb cable hold the power the button to shut down and boot up .
since you have not mentioned your OS am assuming it is windows , try taking out Kies via some software like revo uninstaller which will remove all directories plus all registry entires then reinstall it if you really need it.
Click to expand...
Click to collapse
tried both yet still unable to connect.
emzgames said:
tried both yet still unable to connect.
Click to expand...
Click to collapse
dial *#0808# from your cell this would take you in usb settings, tick both mtp+adb , reboot , if they art already ticked uncheck them and check them again.
dovakinn said:
dial *#0808# from your cell this would take you in usb settings, tick both mtp+adb , reboot , if they art already ticked uncheck them and check them again.
Click to expand...
Click to collapse
im afraid i cant do this coz i cant boot my phone properly, up to welcome msg only then screen black out, but not power off.
emzgames said:
im afraid i cant do this coz i cant boot my phone properly, up to welcome msg only then screen black out, but not power off.
Click to expand...
Click to collapse
ohhh best take your cell to your nearest service center then . if you can't flash anything and usb is not getting detected i don't see any other option , maybe someone more experienced here can help.
dovakinn said:
ohhh best take your cell to your nearest service center then . if you can't flash anything and usb is not getting detected i don't see any other option , maybe someone more experienced here can help.
Click to expand...
Click to collapse
yah, thats what im thinking. i just brought this here hoping to solve this problem without going to a shop. thanks anyway.
aac. To me put your phone in download mode then use moborobo(a windows software) . Just open it and it will install the driver. If it dies not work then use adb installer . Remember you should have only any one of the software at one tim means either moborobo or kies or adb installer
Sent from my GT-I9001 using xda app-developers app
btw have you tried to boot the phone in safe mode ?? if it boots in safe mode it is still fixable without going to service center. power down , power up+ tap the menu button 3 or 4 times at THE same time to boot into safe mode if it boots into safe mode that means the hardware and OS is fine if it does not well then your out of luck.
dovakinn said:
btw have you tried to boot the phone in safe mode ?? if it boots in safe mode it is still fixable without going to service center. power down , power up+ tap the menu button 3 or 4 times at THE same time to boot into safe mode if it boots into safe mode that means the hardware and OS is fine if it does not well then your out of luck.
Click to expand...
Click to collapse
tnx man, but no luck..
Tried flashing a custom rom?
So I just got an LG G pad 10.1 VK700 from Verizon the other day. I rooted the device on the first day but never really added any additional apps or software.
Another member in the household was using the tablet and it asked if they wanted to accept the VZW Update for KitKat 5.0. They downloaded the update, and now the tablet is stuck in a bootloop at the Fastboot screen.
There are only 3 options I can select from this screen in the top left using the volume keys: RESTART, RESTART BOOTLOADER & POWER OFF. Any time I select either of the restart options, the screen just goes blank and hangs. I have to manually power off, and upon turning back on I am right back to this limited Fastboot menu.
Bottom left reads:
FASTBOOT MODE
PRODUCT_NAME - E9LTE_VZW
VARIANT - e9lte_vzw Toshiba 16GB
HW VERSION - rev_10
BOOTLOADER VERSION - N/A
BASEBAND VERSION - N/A
CARRIER INFO - N/A
SERIAL NUMBER - VZ7005xxxxxxx
SECURE BOOT - disabled
LOCK STATE - locked
I booted into Recovery mode, but any of the options I select from the System recovery menu send me right back to the Fastboot screen.
Is there anything to be done at this point?
UPDATE: Problem solved. Research into the other variants of the LG G Pad lead me to the the LG Mobile Support Tool, which you can find by googling B2CAppSetup.exe.
Now, if you are stuck in a Fastboot loop as I was, I ended up having to restart the device while holding down the Power + Volume UP & DOWN. This brought up a screen displaying a bar code and the device MSN and IMEI number. Using this number return to the LG Mobile Support tool and select Options>Upgrade Recovery. Even if your device is already plugged in via USB, the software will not recognize the device -- you may want to double check to make sure your device drivers were installed prior to this step. Input your IMEI number into the box and restart the device in to download mode. It took a few attempts due to the quick action of Fastboot, but I was finally able to access the menu while USB was plugged in to the device and restarting while holding the Volume + key. Now you can continue with the installation and you will be back into your tablet in no time.
I have access to the device via usb / fastboot, adb is not registering. If anyone has any suggestions on what I can try, please let me know. I do not have a backup or a version of the OEM ROM. Every effort so far just sends me right back to the Fastboot screen with 3 options. Anything I can run from command prompt using fastboot alone that would help in this situation? Any way to do a factory restore without having an actual OEM image?
Well im stuck at the verizon screen too but for a different reason
JRSwole said:
So I just got an LG G pad 10.1 VK700 from Verizon the other day. I rooted the device on the first day but never really added any additional apps or software.
Another member in the household was using the tablet and it asked if they wanted to accept the VZW Update for KitKat 5.0. They downloaded the update, and now the tablet is stuck in a bootloop at the Fastboot screen.
There are only 3 options I can select from this screen in the top left using the volume keys: RESTART, RESTART BOOTLOADER & POWER OFF. Any time I select either of the restart options, the screen just goes blank and hangs. I have to manually power off, and upon turning back on I am right back to this limited Fastboot menu.
Bottom left reads:
FASTBOOT MODE
PRODUCT_NAME - E9LTE_VZW
VARIANT - e9lte_vzw Toshiba 16GB
HW VERSION - rev_10
BOOTLOADER VERSION - N/A
BASEBAND VERSION - N/A
CARRIER INFO - N/A
SERIAL NUMBER - VZ7005xxxxxxx
SECURE BOOT - disabled
LOCK STATE - locked
I booted into Recovery mode, but any of the options I select from the System recovery menu send me right back to the Fastboot screen.
Is there anything to be done at this point?
UPDATE: Problem solved. Research into the other variants of the LG G Pad lead me to the the LG Mobile Support Tool, which you can find by googling B2CAppSetup.exe.
Now, if you are stuck in a Fastboot loop as I was, I ended up having to restart the device while holding down the Power + Volume UP & DOWN. This brought up a screen displaying a bar code and the device MSN and IMEI number. Using this number return to the LG Mobile Support tool and select Options>Upgrade Recovery. Even if your device is already plugged in via USB, the software will not recognize the device -- you may want to double check to make sure your device drivers were installed prior to this step. Input your IMEI number into the box and restart the device in to download mode. It took a few attempts due to the quick action of Fastboot, but I was finally able to access the menu while USB was plugged in to the device and restarting while holding the Volume + key. Now you can continue with the installation and you will be back into your tablet in no time.
Click to expand...
Click to collapse
Hello I have the exact same model I got 28th my g4 and successfully rooted with kingroot and used supersume to change it to supersu. Everything was perfect and running fine and I tried an entropy engine I use on my other rooted phone and it was not help so I disabled it and rebooted like I have with my other one before and it stuck at that horrible red screen lol. I haven't done anything else major to alter anything to do with the OS like installing an OTA and I can only get to the same screens as you. My problem is I don't have a PC and haven't in a very long time and if I get to one I wouldn't know where to start out, last computer I owned has a floppy disk lol but I don't see how I would need to re flash the entire OS because of an entropy engine hickup. If you or anyone know of a way to slap this thing back to reality I would highly appreciate it. I got very familiar with the android os and how it works but never had a PC to go beyond a basic root so technically I'm still a noob in a way. I only care to expand dual window to other apps if I get it fixed cuz I'm not gonna risk screwing with it any more now than I have to, my luck is too bad lol thanks in advance
dadrumgod said:
Hello I have the exact same model I got 28th my g4 and successfully rooted with kingroot and used supersume to change it to supersu. Everything was perfect and running fine and I tried an entropy engine I use on my other rooted phone and it was not help so I disabled it and rebooted like I have with my other one before and it stuck at that horrible red screen lol. I haven't done anything else major to alter anything to do with the OS like installing an OTA and I can only get to the same screens as you. My problem is I don't have a PC and haven't in a very long time and if I get to one I wouldn't know where to start out, last computer I owned has a floppy disk lol but I don't see how I would need to re flash the entire OS because of an entropy engine hickup. If you or anyone know of a way to slap this thing back to reality I would highly appreciate it. I got very familiar with the android os and how it works but never had a PC to go beyond a basic root so technically I'm still a noob in a way. I only care to expand dual window to other apps if I get it fixed cuz I'm not gonna risk screwing with it any more now than I have to, my luck is too bad lol thanks in advance
Click to expand...
Click to collapse
If you are stuck in this particular Fastboot loop without a computer I am afraid your options are going to be very limited. The only thing I can imagine that you would be able to try is restarting the tablet while holding down the Power + Volume Down keys to access the stock System recovery menu. You can try to use Factory data reset and Wipe cache to see if that can resolve the issue, but for me every attempt to perform actions from this menu brought me right back to the Fastboot screen. The only other way I could communicate to the device in this scenario was using command line, and even then I could only access fastboot and not abd.
I would highly advise getting at least a cheap older laptop with Windows if you plan on rooting any device, otherwise the dangers will far outweigh the benefits. I'm just hoping some development comes along for the VK700 G Pad 10.1, at least a TWRP or CWM release.
JRSwole said:
If you are stuck in this particular Fastboot loop without a computer I am afraid your options are going to be very limited. The only thing I can imagine that you would be able to try is restarting the tablet while holding down the Power + Volume Down keys to access the stock System recovery menu. You can try to use Factory data reset and Wipe cache to see if that can resolve the issue, but for me every attempt to perform actions from this menu brought me right back to the Fastboot screen. The only other way I could communicate to the device in this scenario was using command line, and even then I could only access fastboot and not abd.
I would highly advise getting at least a cheap older laptop with Windows if you plan on rooting any device, otherwise the dangers will far outweigh the benefits. I'm just hoping some development comes along for the VK700 G Pad 10.1, at least a TWRP or CWM release.
Click to expand...
Click to collapse
Thanks for your response, I have unfortunately tried that too and wipe cache, reset , all back to fastboot. I figured it would be impossible without a pc. Oh yea my stock recovery says modified in the top left corner, but anyway I can get access to a PC But honestly it's been awhile since I even needed to use one and don't know exactly where to start, like navigating around, and how to install what software on the pc. I can't find anyone that will walk me through it locally or online and every tutorial I find is missing some lil step I need. I know Android in detail but after basic root my experience hits a brick wall. I'm capable of more jus got to get broke in on a pc again. Now I only care to root for stuff like freezing apps, gesture control, and really want to use any app in dual window. Ain't screwing with any system tweaks again it was pointless lol I guess I need all the right files and hit up the pc...can't really do worse no??
Sent from my VS986 using Tapatalk
JRSwole said:
If you are stuck in this particular Fastboot loop without a computer I am afraid your options are going to be very limited. The only thing I can imagine that you would be able to try is restarting the tablet while holding down the Power + Volume Down keys to access the stock System recovery menu. You can try to use Factory data reset and Wipe cache to see if that can resolve the issue, but for me every attempt to perform actions from this menu brought me right back to the Fastboot screen. The only other way I could communicate to the device in this scenario was using command line, and even then I could only access fastboot and not abd.
I would highly advise getting at least a cheap older laptop with Windows if you plan on rooting any device, otherwise the dangers will far outweigh the benefits. I'm just hoping some development comes along for the VK700 G Pad 10.1, at least a TWRP or CWM release.
Click to expand...
Click to collapse
Oh yea I almost forgot I got side tracked earlier. I know there is already a twrp, I have 2 versions (2.8...something and the next version strait off twrp site. I was the one guy it wouldn't flash through flashify for but others claimed it did. God knows really, but I'm gonna wait till I have a PC of my own before I touch my g4 but man the ability to open any app in dual window is just too damn sweet...if I could only change that one word on build prop to false without all the other hassle
Sent from my VS986 using Tapatalk
JRSwole said:
Now, if you are stuck in a Fastboot loop as I was, I ended up having to restart the device while holding down the Power + Volume UP & DOWN. This brought up a screen displaying a bar code and the device MSN and IMEI number. Using this number return to the LG Mobile Support tool and select Options>Upgrade Recovery. Even if your device is already plugged in via USB, the software will not recognize the device -- you may want to double check to make sure your device drivers were installed prior to this step. Input your IMEI number into the box and restart the device in to download mode. It took a few attempts due to the quick action of Fastboot, but I was finally able to access the menu while USB was plugged in to the device and restarting while holding the Volume + key. Now you can continue with the installation and you will be back into your tablet in no time.
Click to expand...
Click to collapse
I tried following your recommendation, but the LGMobile Support Tool said the device wasn't plugged in no matter which combination of buttons I pushed while running the Upgrade Recovery option, and I wasn't able to figure out how to get to download mode either.
gnomesinrome said:
I tried following your recommendation, but the LGMobile Support Tool said the device wasn't plugged in no matter which combination of buttons I pushed while running the Upgrade Recovery option, and I wasn't able to figure out how to get to download mode either.
Click to expand...
Click to collapse
If your problem is from an OTA failing due to taking it while modded and you can get to fastboot the following command might fix it:
Code:
fastboot erase cache
That will delete the OTA zip and break the bootloop.
Hey guys, My moto Z Play died on me, and it doesn't budge from the AP Fastboot Flash Mode.
I can do the selections using the volume keys but nothing happens when I try to select one of the mode, including the Start, Recovery Mode, QCOM, Bootloader logs. It just gets stuck there until I restart the phone again to this mode using the power and volume down keys.
Only option that works in here is the restart bootloader option which pushes it back to the same screen.
The problem here is I the USB debugging was not enabled before this happened, so I am not able to detect the phone in either the Adb fastboot or in RSD lite.
Looks like its been hardbricked or the internal storage has been corrupted.
Any suggesstions to be able to flash the stock firmware to my phone.
PS: Its a verizon phone.
thanks
azeem.droid said:
Hey guys, My moto Z Play died on me, and it doesn't budge from the AP Fastboot Flash Mode.
I can do the selections using the volume keys but nothing happens when I try to select one of the mode, including the Start, Recovery Mode, QCOM, Bootloader logs. It just gets stuck there until I restart the phone again to this mode using the power and volume down keys.
Only option that works in here is the restart bootloader option which pushes it back to the same screen.
The problem here is I the USB debugging was not enabled before this happened, so I am not able to detect the phone in either the Adb fastboot or in RSD lite.
Looks like its been hardbricked or the internal storage has been corrupted.
Any suggesstions to be able to flash the stock firmware to my phone.
PS: Its a verizon phone.
thanks
Click to expand...
Click to collapse
The question is what did you do to the Verizon "unlocked bootlader" phone to get you to this point?
Hello.
I own a Note II which lately seemed to have some problems.
In the last few months, it used to restart somewhat spontaneously (it seemed that it rebooted when its processor or RAM were too busy, but this wasn't a rule). During one night it probably rebooted and next morning I found it stuck on the first boot screen (the one with "Samsung Galaxy Note II").
When stuck on the boot screen, if I press the power button for a few seconds, it turns off. If closed, it gets to the boot screen and gets stuck there when I press the power button. When plugged to power, it gets stuck at the screen with the empty battery that has a loading icon in the middle.
I manage however to get it into recovery mode, however, in this situation, it can't be seen by the PC, unless I put it in adb sideload mode. When stuck on the logo screen, it is seen as mtp device.
In the recovery mode screen, there are many errors (can't/failed to mount /efs, /system, /cache, /cache/recovery/last_recovery, /data, /data/log/recoverylog.txt, /cache, /cache/recovery/log, last_log, last_install.
In Windows, the PC doesn't recognize the model, however, in a virtual machine that runs Linux, it is correctly seen as Note II when in adb sideload mode, but Linux is not able to mount its storage.
I have also deleted cache, tried Samsung Kies and Note II Toolkit.
What I would like to do is recover the data on it. Do you think it is possible, and if yes, how?
Thank you.
Sounds like a failed memory chip to me.
any answer now?
i want get ROM-not2-7100
Can you make it more clean and what do you want ? I want help to you but i dont understand what are you talking about So can you have acces to twrp ?
same problem
hi
i have same problem
i can go download mode but cant go recovery mode
using odin to flash twrp and cwm it said pass but problem exist
DarkMountain said:
Can you make it more clean and what do you want ? I want help to you but i dont understand what are you talking about So can you have acces to twrp ?
Click to expand...
Click to collapse
No, I don't have access. What I want is to recover the files on it, if possible.
This may be a problem with the power button. if you can go into download by pressing only the menu button + volume down is because the power button is always pressed.
eton3 said:
This may be a problem with the power button. if you can go into download by pressing only the menu button + volume down is because the power button is always pressed.
Click to expand...
Click to collapse
No, I need to use the power button too.
calindiaconu said:
No, I don't have access. What I want is to recover the files on it, if possible.
Click to expand...
Click to collapse
Sorry i think your partitions broked. I think you cant recover your data. There is has only one solution. Odin and Format....
My device too has pc cant detect my phone. I tried different cable without samsung usb drivers. Pc succesfully detected the my device.
By the way i installed lg usb driver because of someone's phone is lg and they need format.
I think there's no way to recover your data now.
BTW what recovery are you using?
Hello,
my wife got a S21 FE (SM-G990B/DS VD2). Yesterday it started to reboot over and over out of a sudden, showing the samsung logo first, followed by the knox logo, then shutting off and on again. Tried several guides to enter Recovery or Download Mode. The only thing that worked was entering download mode by pressing Vol up, down and power while a USB-Cable is plugged in, but as soon as i press the vol up button to pass the "warning screen", it shows some phone specs for a couple of seconds, shuts off and starts bootlooping again. After some hours, the phone once entered recovery mode when it lied next to me for about an hour. Tried to wipe cache, but just got an error I can't remember right now. Hoped it fixed itself when it made it to recovery and just rebooted to see if it works again, but then it just keept bootlooping again.
Since then I couldn't figure out why it once booted to recovery on it's own nor why I can't force it to enter recovery by pressing vol up + on.
Still hope it's just a faulty update or bug, but feels very much like it's a hardware related issue. Replacing the phone won't be an issue, but I'd really want to save data on the phone as my wife didn't make any backups and really wants to keep the photos.
As I just found guides that included recovery or DL-Mode, which are both no valid options for my case, I'd be thankful for any ideas to fix the phone or at least gain access to files before replacing it.
So.. did anyone come across similar issues and found a solution to revive the phone or are there any "unpopular" ways to recover samsung phones out of this state?
Edit:
Turned off completely overnight, booted once to system, looped again and now it's working like nothing ever happened. Got no clue what caused it or why it is working again. Saved everything for the case it happens again.
Wouldn't trust that device anymore, but my wife wants to keep it.
¯\_(ツ)_/¯
I would just like to reply here and add my own potential fix and also would like confirmation that it would work.
So I have a SM-G996B in a boot loop which returns a 'fs_mgr_mount_all' error. Possible to reboot into recovery mode, cleared cache and restarted bootloader etc with the same boot loop. Powered off and connected to PC for Download mode for ODIN recovery but upon pressing volume up, it then restarts again so Download mode recovery is impossible.
I know however that Developer options and USB debugging was enabled on the device as well as unlocked boot loader. I was able to download the correct original stock OS based on the PDA , CSC and Android version.
I have then installed the latest ADB software on my PC and Samsung USB drivers.
By then rebooting into recovery mode, I have the option of 'Apply update from ADB'. I have then confirmed the device connects using the ADB devices command.
I would like to clarify one thing however. I want to keep the user data at all costs. By using the stock firmware and renaming as update.zip, will it use the HOME_CSC and not the CSC file? If not would it work if I open the zip and remove the CSC before re-zipping to make sure?
Thanks
Reebee said:
Hello,
my wife got a S21 FE (SM-G990B/DS VD2). Yesterday it started to reboot over and over out of a sudden, showing the samsung logo first, followed by the knox logo, then shutting off and on again. Tried several guides to enter Recovery or Download Mode. The only thing that worked was entering download mode by pressing Vol up, down and power while a USB-Cable is plugged in, but as soon as i press the vol up button to pass the "warning screen", it shows some phone specs for a couple of seconds, shuts off and starts bootlooping again. After some hours, the phone once entered recovery mode when it lied next to me for about an hour. Tried to wipe cache, but just got an error I can't remember right now. Hoped it fixed itself when it made it to recovery and just rebooted to see if it works again, but then it just keept bootlooping again.
Since then I couldn't figure out why it once booted to recovery on it's own nor why I can't force it to enter recovery by pressing vol up + on.
Still hope it's just a faulty update or bug, but feels very much like it's a hardware related issue. Replacing the phone won't be an issue, but I'd really want to save data on the phone as my wife didn't make any backups and really wants to keep the photos.
As I just found guides that included recovery or DL-Mode, which are both no valid options for my case, I'd be thankful for any ideas to fix the phone or at least gain access to files before replacing it.
So.. did anyone come across similar issues and found a solution to revive the phone or are there any "unpopular" ways to recover samsung phones out of this state?
Edit:
Turned off completely overnight, booted once to system, looped again and now it's working like nothing ever happened. Got no clue what caused it or why it is working again. Saved everything for the case it happens again.
Wouldn't trust that device anymore, but my wife wants to keep it.
¯\_(ツ)_/¯
Click to expand...
Click to collapse
Similar issue with same phone. In a bootloop after trying to root. None of the button combinations have worked for me, for the past several days.
Tried powering the phone off for the whole night.
When connected to the PC shows phone is in recovery mode via adb (blank screen though).
Want to know how to get into DL-mode, guaranteed.
Got to DL mode by pressing vol up + down + power + usb cable connected in PC and phone. However, couldn't do anything there, but maybe you can
Also, phone is still working and I still have no clue what was the problem and what fixed it.