Related
I have a rooted GT-P6210 that was working perfectly fine and last night I updated Busy Box Free from Google Play. Busy Box Free reported an error with the install and shortly after I noticed that my Wi-Fi would no longer connect. It just reports "Error" after trying to connect to Wi-Fi.
I tried re-rooting my device but that didn't fix my Wi-Fi issues. I researched everywhere I could think of to unroot my device but all the threads seem to refer to guides that I don't see and firmware links that no longer work. I managed to find a copy of Odin3-v3.04 (not sure if that is the right version) but I still don't have instructions on how to do it nor do I have the firmware that I need.
I decided I would try going back to factory settings by powering off the device and booting into system recovery. I have done a wipe data/factory reset multiple times but Wi-Fi still doesn't work and I don't even know if that removed the root job I did.
When I plug my device into my PC and run Samsung Kies it reports that I have the latest firmware PDA:LA3 / CSC:LA3 (XAR)
So I am stuck and not sure what to do at this point. I have a pretty useless device that won't connect to Wi-Fi. I don't know if I wait around for ICS and install that if it will fix my problem.
Is there anyone that could help me restore my device to factory settings with actual guides, and provide working links to the firmware I would need?
Thanks for your help,
Bryson
I have an identical problem - albeit with a P6200 supplied by UK mobile network "3"
Busybox tried to update itself from 1.20.0 to 1.20.1 (using "Smart Install")
For whatever reason it failed. From then on, the Wifi wouldn't turn on - the button in the pop-up panel (can't remember what it's called!) going from grey to greyed-out green while trying to connect, and eventually giving up and dropping back to grey again - in control panel the Wifi section then just says "Error".
Also Tethering no longer works... clicking on "Portable Wi-Fi hotspot" gives me "Turning on..." in grey for 15-20 secs and then "Error"
I've not tried a factory wipe/reset or anything yet. Any suggestions?
Many thanks!
I have also had this issue with my Galaxy Tab 7 Plus (GT-P6210) since Monday evening.
When I noticed the problem I was going to try and restore a backup. During that process is when I noticed that I no longer had root access.
This morning I had a friend look at my device and he noticed that the 'Auto Update' was active. I thought I had that deactivated but apparently not. I’m wondering if an update was pushed out that destroyed root and as a result messed with the Wifi access. So far I haven’t gone any further than this.
Those of you having a similar issue, have you also lost root access? I wonder if re-rooting if that would solve the problem?
Kyazuh
I started having the exact same issue two days ago, I've done countless factory resets and same deal, wifi comes up with error when trying to turn on.
I'm using an international p6200
PDA: P6200LUBKL1
Phone: P6200LUBKL1
CSC: P6200LUUBKL2
I've search everywhere for that firmware to try and do a re-install with Odin, but I cant find it.
Update: Just done a full factory reset, and still no Wifi.
Would a full firmware flash sort it? I've found the correct firmware for my UK "3" network P6200 here:
http://forum.xda-developers.com/showthread.php?t=1517934
This is for flashing with Heimdall:
http://forum.xda-developers.com/showthread.php?t=755265
... though I've never used Heimdall - or even flashed a ROM TBH - so a bit hesitant to give it a go......
Update 2:
Just flashed with stock firmware and Odin - all back to normal, Wifi working!!
After much searching around I was finally able to find the correct original firmware for my TAB:
P6200LUBKL1
I found it on a Chinese site: (I cant post links yet lol )
With Google translator, I was able to download the file and flash the TAB using Odin3, everything worked perfectly, and Wifi is working fine again!!
I also had this problem after trying to update busybox,only I also had a random SoD issue that had me constantly rebooting my device. The only thing that managed to fix it was to Odin back to stock. I'm reluctant to root it again, but at least the problem is gone...
If you open the zip that you use to root this device, you will see that it is basically a binary called su and one script that move it to your device and set permissions. If you want to remove the root, you only have to delete this single file,
In some devices is not as easy, what the script do on our update package must be done with exploits, but the result is the same: move su to some folder on PATH, and set permissions.
That is it, there is no chance to be root fault, seems like some problem with busybos. Actually people like to blame root a lot
The same exact thing has happened to me with my P6210. When I put the device to sleep, I usually turn off wifi. This time I forgot and when I woke it up yesterday evening, the BusyBox updater was open. It failed, of course, and now my wifi won't turn on. No MAC or IP address.
EDIT: Used Odin to return to stock. Rerooted (but did not install CWM) and then installed Superuser, updated su binary. Then installed Busybox Installer which then installed Busybox. Stayed away from Busybox, which seems to have been the source of the problem on my device.
my bad..
Just updated Busybox to version 1.20.1 myself using the smart updater without any issues. Got message it installed correctly and wifi still works even after rebooting.
edit: One difference between me and the op is that I didn't use Google Play to update Busybox I used the apps smart install through the app itself.
Model GT-P6210 with LA3 build.
Could someone try to uninstall busybox?
Sent from my DROIDX using Tapatalk 2
I tried to uninstall busy box still no wifi.
In recovery mode I tried to reinstall my previous load from the file I had on my SD Card. Again no luck.
I'm willing to do a wipe on mine and put the original firmware back on. Has anyone done this with P2610? I have been looking through the forums and I have seen a lot for the P2600 but not much for P2610.
Thanks
Kyazuh
Do you have root still? I can give you a copy of my /system/bin and /system/xbin. As you are about to flash it new i think it could worth the shot.
Sent from my DROIDX using Tapatalk 2
Yesterday after I flashed with the stock Rom, wifi was working fine, I rooted the tablet again installed busybox again and have not experienced wifi issues as of yet.
leodfs using RootChecker it showed that I did not have root access anymore.
isalas16 did you flash from the SD Card using the recovery mode? Or did you use a desktop program like Odin or Heimdall? Also do you have the name of the stock ROM file that you used?
I'm on the newb side of things here and I want to make sure I'm using the right process and files.
Thanks
Kyazuh
leodfs, could u send me theses files, I m with the same problem....my gt-p6210 (brazil)....no wifi, ill try fixit...
thanks....
Kyazuh said:
leodfs using RootChecker it showed that I did not have root access anymore.
isalas16 did you flash from the SD Card using the recovery mode? Or did you use a desktop program like Odin or Heimdall? Also do you have the name of the stock ROM file that you used?
I'm on the newb side of things here and I want to make sure I'm using the right process and files.
Thanks
Kyazuh
Click to expand...
Click to collapse
I used Odin3 the filename of the firmware I used is P6200LUBKL1_b.it168.com.tar
VitaZora said:
The same exact thing has happened to me with my P6210. When I put the device to sleep, I usually turn off wifi. This time I forgot and when I woke it up yesterday evening, the BusyBox updater was open. It failed, of course, and now my wifi won't turn on. No MAC or IP address.
EDIT: Used Odin to return to stock. Rerooted (but did not install CWM) and then installed Superuser, updated su binary. Then installed busybox installer which then installed Busybox. Stayed away from busybox, which seems to have been the source of the problem on my device.
Click to expand...
Click to collapse
That did the trick for me. Uninstalling busybox and factory reset did not work. Flashed stock with Odin.
So it look like the JB OTA update is here for the USA. Mine is rooted, and has already download the update, but I haven't applied it yet, as I'm rooted and I don't know if I have to do something special first.....
Any one have any info on this?
Same Boat !!
Me too in same boat with P3113.See the post below yours :crying: Hope experts replies soon.
I went ahead and installed it on my daughters tab. CWM protected itself, and root. I'm still poking around, but thus far no issues beyond it says "update failed" but clearly didn't.
I'm wondering if I should remove CWM and unroot it first...
Run a nandroid real quick, back it up to your computer, and let 'er rip. Like I said, it's working perfectly for me. Then again my daughter is 7, so losing all her data isn't really a problem.
Updated with Root ?
sheepdog elite said:
Run a nandroid real quick, back it up to your computer, and let 'er rip. Like I said, it's working perfectly for me. Then again my daughter is 7, so losing all her data isn't really a problem.
Click to expand...
Click to collapse
So if i understand correctly , you allowed the OTA with root and it wiped data ? I am suprised it installed with Custom recovery !!!
I have over 200 user apps. Will i retain those Apps (dont mind data being wiped)
No, it didn't wipe data. I wasn't worried about it "if" it did, because it's my daughters, and I have TIBU for all her games from like last week.
Just to be perfectly clear. NOTHING went wrong. It installed the new O.S., booted fine, said the update failed, but the update didn't fail. Probably because CWM preserved root, and bootloader, so verification failed.
I ran it..... It updated thru CWM... Once done said update failed, but I had a new agreement to agree too. Sys info says its running 4.1.1.
If I have and issue, ill update here.
Failed for P3113
Based on your experience thought I would try too... Unfortunately failed miserably... I have Cwm 6.0.2.3 and attached is the crash log... Maybe some experts can give their views..
I guess I'll post my successful config just for the sake of comparison.
I'm currently running CWM 6.0.1.1. The tab was rooted with a file called gtab2_jellybean_rooter (think I got it from XDA, but i'm not positive) and had no other modifications/roms/etc.
If you're running any sort of ROM you're definitely boned, gotta wait for a ROM update. Beyond that, I'm not really sure what to say
To do the proper update, you should un-root and then re-root once done. That way you get the full support with your update if needed.
I am rooted, running CWM 6.0.2.3. I accepted the update and hit the install thinking that it would fail just as it does on a rooted SIII. The notification said the install had failed, but as others here have indicated, it appears as though the install was successful. I retained root and all seems to be normal; with one exception: It appears that the Tab no longer "sleeps" but shuts down completely. Regardless of whether I turn it off with the power button (short press) or if the screen simply goes to sleep, I have to long press the power button and it goes through a full boot.
Is anyone else experiencing this? Is there a setting I am missing? I am not a noob at rooting, etc. as I have been doing it since my OG Droid on Verizon, but it surprised me when the update seemed to install (even Google Now is working), and I am stumped about this "shut down" that seems to happen.
I experienced the same thing. I was rooted and had installed CM10, went back to original backup, using latest CWM. I hit system update and it downloaded the update, asked me to continue. CWM asked me if I wanted to install unsigned zip, I accepted, and it went through. At first boot it said update failed, but like everyone else, it went through. I have had no issues at all. My tab goes to sleep correctly.
Have peace in mind.
I finished updating (unfortunately, the battery was 9%, so I had to wait for an hour to charge before doing anything) and I got "failed" error like everybody got, but the system shows 4.1.1 and the performance is improved, and I applied root again.
Good evening guys!
Alright so I have this huge mess on my i535 right now where the signal for CDMA (bars) and mobile internet is just total crap.
It all started I guess when I had my phone on CM 10.2 (stable) when the signal would NEVER go past 3x. I thought that was just some error on the phone. The way I flashed the CM 10.2 was some bullcrap because I wasn't getting a certain instruction right where SuperSU/User was playing some Whack-A-Mole game where it would pop in and pop out. Because of all this bullcrap I didn't even think to use EZ Unlock to unlock the bootloader, although I think I didn't see it in the Play Store at the time and some of the Youtube videos I was watching didn't mention it. Eventually all was well though, and although 3x was slow looking back, the ROM was really stable with some minor crashing.
Earlier this past week though, I was tired and clicked away on an update to CM 10.2.1 and then another Cyanogenmod update pops up to the CM 11 snapshot. Just trying to get notifications to go away and I dirty flashed it to CM 11 by the Cyanogenmod updater and got an "Update 7" error when installing it, so I just went back into my downloads folder and re-flashed it to 10.2.1. Being in CM 10.2.1, I wasn't getting anything in terms of reception and later found out the problem was that the SIM wasn't checked under mobile networks in the settings tab, but this had resulted in my phone not getting mobile data past 1x.
Now fast forward to today and I update my CWM because of the "Update 7" error and re-flashed it to CM 11, only to find that there were times that the bars would go up to 5 and the LTE would flair up, but then it would crash down; I messed with both the Global LTE (there was a little more successes in this one in terms of the number of time LTE and better bars popped up, but didn't use it because I was scared to see if I was gonna get charged with Data Roaming) and Regular CDMA LTE (kept having 1x and bars would go up and down...), which is where it's at right now.
Okay, so then I re-flashed it to Verizon's 4.3 (finally Verizon is giving us i535 some love! right?) in an attempt to clean flash it but I had put in the VRALEC bootchain in first and softbricked me out of the recovery partition where it gave me that "Take back to Verizon store" yellow triangle warning and it was stuck for a long time at the Verizon logo until I odin'd a stock recovery 6mb tar and w00t, my phone is back, BUT I still have the same figity signals as the CM 11 and all. At this point though, my triangle count is at 4. Also in this state, my Google Play was acting hell-ish (I also got this in CM 11 too, but didn't care too much for it before); I kept getting this "Error retrieving... [RPC:S-3]" when trying to install apps and I did force stop and clear the info, but it wouldn't work. I've also gotten the RPC:S-7 too. Right now, after my mobile and signal bars being finicky as hell, it's sort of stabilized for 4 minutes (longest it's been ) to 4/5 bars with 4G LTE, but I don't know how long this will stay for.
So being very descriptive and maybe loosing some of you, here's the questions for the tl;dr for the questions.
- How can I get this reception to stabilize? It's never been this bad when my phone was stock around here. (now done with this long blob, the 1x has appeared again!)
- Any other ways on getting that RPC:S-3/S-7 in Google Play Store to go away?
- I'm planning on going to CM 11, once it gets a stable release. Kitkats are too irresistible, pun intended... Can someone please set the stone in how I should go about rooting and unlocking the bootloader? Some of the guides I used months ago were a little outdated, and I'm concerned that the old practices are over with.
Rezey said:
Good evening guys!
Alright so I have this huge mess on my i535 right now where the signal for CDMA (bars) and mobile internet is just total crap.
that the old practices are over with.
Click to expand...
Click to collapse
As I understood, you flash a stock 4.3 rom? Stock 4.3 rom locked the bootloader so no more CM11 or any custom rom for you unless you need to flash safestrap, but after this you only can flash TW custom rom. OK, now back to your issue. Since you already on factory stock rom, I would do a factory reset, the Odin a full factory 4.3 stock rom again with a PIT file and I think you should be back to normal unless CM10 is really messup your efs (a few people have this issue when flashing CM rom).
buhohitr said:
As I understood, you flash a stock 4.3 rom? Stock 4.3 rom locked the bootloader so no more CM11 or any custom rom for you unless you need to flash safestrap, but after this you only can flash TW custom rom. OK, now back to your issue. Since you already on factory stock rom, I would do a factory reset, the Odin a full factory 4.3 stock rom again with a PIT file and I think you should be back to normal unless CM10 is really messup your efs (a few people have this issue when flashing CM rom).
Click to expand...
Click to collapse
Hey, thanks for the reply!
A little update; last night I used SUA.exe with Kies drivers which re-flashed it with the factory Verizon's 4.3 and factory reset it, but now my phone will not get any sort of internet bands up and it's stuck on voice roaming which lead me to put my phone on airplane mode so that hidden charges wouldn't sneak up on me. I've even set my Mobile Network options to CDMA-LTE-EVO, but it will not get off of it.
I was just about to go onto one of the other threads and just re-root my phone, until you had told me about the locked bootloader... I'll look more into the safestrap, but this is irritating.
As with the PIT file, do I have to Odin all the VRALEC and other (I've seen a couple of odin to stock and I know rooting requires this) bootchains, to PIT file, and then 4.3? I'm not sure how that step goes... And if it did mess up my efs, what's my next step? I mean I think the i535 might be under warranty, but I'm at 4 triangle counts and I can't get those away unless if I get root permission, but I feel like having a locked bootloader might restrict me from rooting my phone, but I can be just worrying too much...
I wanna also put another update that I did flash the phone with a 16gb pit (which my phone is) file I found on another thread, but it still did not do anything. When I did use the pit file I had some security error on my phone which was in ODIN mode the first time and ODIN just kind of stood there, so then I closed it out and did again, to find that the error popped up again, but I ODIN ran through another flash. I had re-partition checked too...
I did a Wipe2 because I couldn't get the Dalvik cache cleared through Samsung's recovery partition, so I'm probably gonna get my phone rooted in the next hour and put another update because with root I'm gonna at least triangle away my phone.
Rezey said:
I wanna also put another update that I did flash the phone with a 16gb pit (which my phone is) file I found on another thread, but it still did not do anything. When I did use the pit file I had some security error on my phone which was in ODIN mode the first time and ODIN just kind of stood there, so then I closed it out and did again, to find that the error popped up again, but I ODIN ran through another flash. I had re-partition checked too...
I did a Wipe2 because I couldn't get the Dalvik cache cleared through Samsung's recovery partition, so I'm probably gonna get my phone rooted in the next hour and put another update because with root I'm gonna at least triangle away my phone.
Click to expand...
Click to collapse
You still don't under stand 4.3 rom. Once you on it the way to go back to stock rom is using full stock 4.3 and pit file. No boot chain, no once click root etc...If you want to root, you need to use saferoot. Let see if you can get back to a normal 4.3 stock with locked boot loader first. Check out this link. http://forum.xda-developers.com/showthread.php?t=2586319 . Just follow it and see if you can get back to a normal phone and there is a link on that thread for you to use saferoot to root.
buhohitr said:
You still don't under stand 4.3 rom. Once you on it the way to go back to stock rom is using full stock 4.3 and pit file. No boot chain, no once click root etc...If you want to root, you need to use saferoot. Let see if you can get back to a normal 4.3 stock with locked boot loader first. Check out this link. http://forum.xda-developers.com/showthread.php?t=2586319 . Just follow it and see if you can get back to a normal phone and there is a link on that thread for you to use saferoot to root.
Click to expand...
Click to collapse
Actually I used the Verizon utility tool from that very thread to clean root back to 4.3 and had Google Play connection error, Voice-roaming only, and no mobile data whatsoever.
I also just did saferoot on my phone and triangle'd away all my counters but yet still nothing. Did I fry my sim card? And with voice roaming always on, won't this put charges on my bill?
HI,
I've updated the Verizon version of the Galaxy Note Pro 12.2 and I really don't like it. There's too many instability issues that I haven't seen before! I rely heavily on the S-Note and it keeps crashing on me after a few minutes when it is opened up. I can write for a bit but then it just stops working and brings me back to the home screen. The other problem is the SD Card. I never had an issue with it before, but I am now! Sometimes it goes missing when I go into a file manager looking for a document. And it occasionally freezes up!
Oh, and the best part? I like the fact that Samsung has added the "Galaxy Apps" in this Lollipop version like it is on my Galaxy Note 4 (SM-N910F), BUT IT'S ALL IN DUTCH LANGUAGE!!!
And this is suppose to be an American model with the preference language set US English?? Go figure...
I never had this problem before with KitKat 4.4.2, and I want it back!
Now I've tried using ODIN 3.10.7, 3.07, and 3.09, but I can't get it to connect. It keeps saying "added!! removed!!" when I try to use Home-Volume Down-Power" to reboot in Odin mode.
So does anyone have any suggestions on how I can downgrade?
Did you use the OTA 5.1.1 version that was pushed out by Verizon? I took it last week and this beast is way more stable, no crashes, the SD Card works properly (I have a 128GB card) and no language problems. Try resetting your tablet and getting the OTA (again).
tdetroit said:
Did you use the OTA 5.1.1 version that was pushed out by Verizon? I took it last week and this beast is way more stable, no crashes, the SD Card works properly (I have a 128GB card) and no language problems. Try resetting your tablet and getting the OTA (again).
Click to expand...
Click to collapse
No, I didn't get it by OTA. I did it through KIES. I'm an American ex-pat living in the UK for the past few years and I had this shipped to me from family back in Florida. It doesn't seem that the OTA would work at all and the only way I could get the update is through KIES.
As for resetting, that's what I was trying to do. When I do a "factory" reset, it puts 5.1.1. back on again plus the Verizon repair app is not giving me any joy since it's doing the same and placing lollipop 5.1.1, which is why I'm going through ODIN mode to place the original ROM back onto it that I've downloaded from SamMobile's website. However, as I mentioned, Odin on all versions are giving me "ADDED!! REMOVED!!".
What I really find so strange is that the Verizon Update/Repair app will re-flash with no problem; but when trying to use Odin, it won't connect. Can someone give me a clue on what's going on with that??
It would also mentioned I'm using Odin on Windows 7 64 bit and I've used separate computers so that the drivers for KIES and Verizon Update App doesn't clash, yet I'm still getting the same messages from Odin.
OR am I missing something else??
By the way, Sammy's Galaxy Apps is still in Dutch!!
sjbrother said:
No, I didn't get it by OTA. I did it through KIES. I'm an American ex-pat living in the UK for the past few years and I had this shipped to me from family back in Florida. It doesn't seem that the OTA would work at all and the only way I could get the update is through KIES.
As for resetting, that's what I was trying to do. When I do a "factory" reset, it puts 5.1.1. back on again plus the Verizon repair app is not giving me any joy since it's doing the same and placing lollipop 5.1.1, which is why I'm going through ODIN mode to place the original ROM back onto it that I've downloaded from SamMobile's website. However, as I mentioned, Odin on all versions are giving me "ADDED!! REMOVED!!".
What I really find so strange is that the Verizon Update/Repair app will re-flash with no problem; but when trying to use Odin, it won't connect. Can someone give me a clue on what's going on with that??
It would also mentioned I'm using Odin on Windows 7 64 bit and I've used separate computers so that the drivers for KIES and Verizon Update App doesn't clash, yet I'm still getting the same messages from Odin.
OR am I missing something else??
By the way, Sammy's Galaxy Apps is still in Dutch!!
Click to expand...
Click to collapse
Did you ever get this figured out? I, myself, am having a terrible time with the lollipop upgrade on my 905V. I've tried to ODIN back to 4.2.2 with no luck. ODIN fails every time I try to push one of the older versions to the tablet.
I am like you where I had to use ODIN to upgrade to 5.1.1. I was rooted and I had done a few other things which required me to factory reset a couple times after using ODIN to install an original factory package.
It is possible we are S.O.L. There is simply no DEV support for a device few people have, I don't expect much.
My only shot to try next is to see if putting one of the older versions in a specific folder will give me an option in Kies to revert back.
There is always a chance someone will come along with the answer we need.
Lollipop haywire
I to have the Verizon Note Pro and recently did the update to lollipop and is having a horrible experience... The system seems to be unstable all my apps are crashing a lot... Ive tried to revert back to 4.2.2 using Odin as well but no luck. Ive factory reset numerous times... Ive even reinstalled lollipop several times, with no luck. If any one has any insight on what this problem is or have anyway of going about fixing the crashing, please let me know...
Has this ever been figured out? When I first got my NP 12.2 on verizon I rooted it, but then I OTA updated it, like a dummy, to 5.1.1. I want to flash back down to 4.4 or whatever version it WAS so I can root 4.4 then update to a 5.1.1 or 6.0.1 rooted rom. * Any help would be appreciated.
In the same boat
Any help on this? I would really like to downgrade my NP12.2 to Kitkat to root it.
I pretty much a novice to Android, but have 20+ years with PC and MAC. This doesn't seem like it should be that big of a deal. Thanks for any help!
First; I hate to be a double poster, but I'm on the back page of How to Upgrade to 5.0.1 and Keep Root. My apologies. I've spent several days trying to solve this and have no answers.
I did the 5.0.1 "Keep Root" when it first came out, but it acted buggy and unpredictable. I just got a Note 4, and hate that I can't root it, so I decided to try to resolve the problems with my S4. I re-did the process, as stated and it seemed to work fine. I downgraded, rooted, and upgraded to 5.0.1. Then the trouble started. I installed the "Stock" Kernel, Modem, and Recovery. When I rebooted; it gave me a nasty message like: "AT&T has discovered unauthorized software on your phone." and froze up. I booted back into download mode, re-flashed the NB1 file, and it seemed to work, except for no Wi-Fi. When I tried to re-flash the OC4 with Flashfire, it acted like it was going to do it, but only booted into the recovery screen. I've tried close to a hundred different combinations, but no joy.
It allows me to root the NB1 and install Flashfire, but cant get it above 4.3. I installed a terminal emulator APK file and checked my bootloader status and it shows OC4. If my understanding is correct; I'm screwed. Is there any way to get past this and upgrade to ANY working ROM that will allow Wi-Fi and be fairly stable?
BTW; I'm on AT&T.
Thanks in advance!
As far as I'm concerned, ODIN just puts back your phone to its original state. Have you tried following the guide on how to install a custom Lollipop ROM? You gotta flash a rootable NB1 firmware and then continue with the process explained in the thread.
Here, take a look and tell me how it goes http://forum.xda-developers.com/galaxy-s4-att/general/how-to-installed-custom-lollipop-rom-t3135396
Crash and Burn
Crash and burn. NB1 wouldn't think of loading with Odin. Fails almost immediately.
Thanks for the help, though. Any other ideas?
Here's a screenshot of my phone parameters.
http://dl-1.va.us.xda-developers.co....png?key=Hy1bNEcEPo2F55Cm_pjqYg&ts=1450058617
Guess it won't upload my photo...