Hello Xda community,
Alright after exhausting all other options i have decided to turn to our community in hopes that i can come to some sort of resolution for this matter. Okay i own a Sophix Tab-840g past warranty my problem is my software was causing freeze and reboots i left it that way for a while because it wasn't bothering me. So i waited long enough for them to make a new firmware and i upgraded, however upon doing so i was not able to use the touchscreen. Also, i have no back up...... was a bad move in retrospect. I did some research and found that that the freezing was due to the actual firmware and many people had tried to update running into the same situation where the touchscreen stopped working.
The only difference between when i did it and when they did it is the company had there older firmware available still. That is no longer that case they only have the new firmware and after calling they no longer have old software available. Other people reverted back and atleast there tablet worked, however I CANNOT get the old firmware ANYWHERE........in there guide they talk of the use of update "update-tab840-v02-20130315.img" when using there batch program. The only firmware available is the new one “upgrade-tab840-v03-20130607" i'm looking for the older update "update-tab840-v02-20130315.img" to fix my tablet or a way to fix this touchscreen hard reset is out of the option i have already done this method a couple times, i tried installing from sd, and from the computer all with the same error. Thank you so much for reading this and also for any help i procure. I will be uploading the version of my firmware i have no and the old one if i get it so this can the fix for this dreaded problem with so few forums talking of a fix.
Thank you,
Captainsploof
P.S. having trouble uploading firmware at this point keeps saying page unavailable during upload 8/18/2014
Related
Hello folks,
Generally loving my Vibrant, of course hungry for Froyo. I have two Vibrants, the first I've been using and have modded it with root and other enhancements. I gave the other phone to a friend as a gift, but when I wanted to root theirs using the same method I've used on multiple occasions, it would NOT boot into the recovery mode. I use the UP + DOWN push, plus the power button. No dice, just get the cheesy "come together" Tmobile screen, I tried up, down, waited for the Samsung to flash twice, no dice. It was not that complicated on my phone and I can continue to do so. I have looked up threads and there is suspicion that T Mobile disabled this on later vesrions? This version was shipped to me slightly after my own, within a week or so.
It would be disheartening if I couldn't root and make his phone more efficient to deal with the battery hog issues as well as other enhancments. Maybe I'm doing it wrong but I've treid multiple combinations and never get into the utility/recovery screen.
Any thoughts on this? I tried rooting before that with the Ryan one click lag fix, and it seemed to indicate it was done,b ut then Iwhen I opened ROM manager, it said it was not rooted yet. Then when I tried the one click app fix again, it mentioned it couldn't because soemthing about the SD card mounting,etc. I could put the stock PIT file on it via ODIN could I not? But I dont' want to go to all that hassle if it's something else. Is there a another app solution that can root for you? I can mount and drag the update zip there, but can't get tot he screen to reinstall packages.
Hopefully TMobile isn't stripping this down so we can't customize and it's something else but I'm trying all combinations short of doing the hokey pokey.
Thanks in advance!
Kelly
Samsung Vibrant
Apparently either Samsung or Tmobile are having the option disabled via the normal ways to get into recovery. There are numerous other threads regarding this throughout the forums detailing other peoples experiences regarding this.
Take a look here for one:
http://forum.xda-developers.com/showthread.php?t=771247
Join the club. I'm on my third vibrant with this same issue. I am returning it this week for a refund. My first....and last samsung phone.
thank you guys, I was afraid of that. one of the phones greatest assets was it's hackability. Froyo had better do something with battery consumption, speed, etc, or this phone will be a great screen and not much more. boo to hardware lockdowns! let the hackers hack and if you want to void the warranty, do it. I'll see about this ADB mode, I'm wondering if someone can create an app that would successfully root so ROM manager will work. I wonder why the one click fix lag app, which supposedly roots, did not. It seems like an overall lock down on this access?
At any rate, I'll try the other options but it's looking like more and more, my buddy will be a slave to Samsung release timeframe, and thats assuming froyo and updates will fix significant bugs and improve battery life.
thanks again guys! I'll keep trying.
And what about the download mode, can you get in it?
not sure, you mean the little digging android feller? I will try that, I gave the phone to my friend but sent him the page in this thread earlier regarding multiple attempts to get into either / or mode. would that actaully help install the packages aka root the phone? I only used that last time to reinstall via Odin, the T Mobile factory build because it was soft bricked due to a bad lag fix that froze the phone on the Samsung logo.
download mode , can that get it rooted? Or just wanting to know if all hardware access has been blocked?"
not sure, you mean the little digging android feller? I will try that, I gave the phone to my friend but sent him the page in this thread earlier regarding multiple attempts to get into either / or mode. would that actaully help install the packages aka root the phone? I only used that last time to reinstall via Odin, the T Mobile factory build because it was soft bricked due to a bad lag fix that froze the phone on the Samsung logo.
download mode , can that get it rooted? Or just wanting to know if all hardware access has been blocked?
Yeah, that the digging guy. It won't help you to get rooted, but i can't get in download mode, so if you can advise me how can i do that, i appreciate
So I have an Optimus T 509 Titanium. I was informed there was an update so i downloaded it. I told it yes to update. Now it seems to be stuck. It displays the LG Logo Then displays the updating screen briefly before immediately Re-Booting.It does this continuously.
Does anyone know what might have happened or how to fix it. The phone is completely stock no mods, not rooted. Hard Reset does not work and emergency mode does. I tried KDZ updater but i get a model ID error when trying the Optimus 500. I spent most of the day looking for the proper one every time I tried one of these http://csmg.lgmobile.com:9002/csmg/b2c/client/ezlooks_model_list.jsp?model=LGP509 Using the instructions here http://forum.xda-developers.com/showthread.php?t=865479 i got an error.
Edit's: changed the title to be more specific. The update in question was the v10L update i do believe. Got another one. It seems that a antivirus program called look out cause the problem. It seems the program also prevents rooting the phone.
Looks like it's LG's fault. If I were you I'd have it warranty repaired.
On a side note, I think that's a boot loop. I'm no expert, so others may be able to help in a while.
Gonna have it replaced. But this seems like something that should be addressed, I see multiple accounts of OTA causing brick on this phone. Since I can't use the LG Update either(for some reason my isp blocks it same with M$ Live services).. so this is, aside from rooting the phone the only way to get updates for me. I mainly think my failure was because of lack of availability of stock firmware. It also seems theres no way to get stock back without a factory firmware either. I'm all for tweaking but not if i can't fix it if something goes wrong.
Hi
There is no specific forum related to this device so I am posting it over here.
I bought LG VU II (F200L) in perfectly working condition, it almost new. After installing LG PC suite and connecting it said new firmware update is available so I proceeded which was done successfully but since then touch screen is not working properly.
Usually it responds ok but main issue is back button is not working anymore, and sometimes when I press power button to unlock screen it responds very weird and not so responsive as well as sometimes doesnt responds or opens apps that I havent even clicked.
I tried to restore, emergency restore, LG Flash tools and used correct KDZ files to flash roms successfully but nothing seems to resolve this issue.
I made some research and the only thing I could find related was Mirror screen which I am not even sure if its the same thing.
Any help will be highly appreciated.
Do a downgrade if you can. If you can't take the phone to a service, much better if you have a warranty.
omega96 said:
Do a downgrade if you can. If you can't take the phone to a service, much better if you have a warranty.
Click to expand...
Click to collapse
The ROM which was running properly before was also JB updated but strangely it was for F200S. I restored its cwm backup but still same problem.
Cant find any KDZ of ICS for VU II or F200 all over internet, all are JB. So I am unable to find any tutorial or files to downgrade it.
After reading and reading and reading I am officially stuck hopefully someone or @stifilz can help. Hoping that i just missed something after reading too much info.
UK Sony Tablet S region changed when ICS came out for early update from US. Decided do JB update yesterday the flasher V3 got up to the end of data transfer part and tablet froze up and all coms went. left it for a while but nothing. After a hard switch off it hung at the sony logo. Got into recovery and did factory reset to try clear any issues or so i thought. Still hung at logo. Downloaded various ICS files and renamed to update.zip and tried to reflash. They all fail with the E: Prohibit error, occasionally error failed to mount system1.
I've attached my recovery log if anyone can help sort this il be a happy man.
TIA
After reading http://forum.xda-developers.com/showthread.php?t=2433323 I am starting to think a lot of these topics go unanswered and point to a flaw in the flasher, my region.prop is also missing and can only presume the tablet requires this for an update and the factory reset removes the root so cannot push another .prop over. So for all intents and purposes the tablet be fooked. I really do hope I am wrong but if i am right then why is this flashing tool still available after so many screw ups.
Well the screw up your are referring to is your own as if you had done your research you would know that trying to flash jb to the tablet s and not the xperia s will mess the tablet up as pointed out in numreouse posts and questions. so the reason people don't reply is that the questions have all ready been answered serveal times and the warings are there
rooted lighting wildfire on unoffical j.b from benni
and sony XTS rooted stock j.b thanks djrbliss
I presumed I had done enough reading beforehand as the tool said Sony Tablet S so seemed the right tool for the job. I've flashed many things over the years and never screwed one up so this is bit of a shock to the system, My first reaction to your reply was to reply don't be smart then my second was to go check tool again, then third was ah f*#k. 26 letters in the alphabet and sony had to call the next model an S too. I cant say i keep up with tablet technology so thought they same thing pre flash,I didnt expect my tablet to be replaced in market so quickly after i bought one. Oh well lesson learnt now the question is wtf can be done if anything. If i send in for repair do they spot this instantly and try hammering me for a heavy bill to fix. Its under guarantee but they do say software issue they wont touch it.
I did read a lot about these problems but only reference i can find was today on page 36 of the flasher tool post. I blame mondays and my obvious lack of cognitive skills on them.
dex9mm said:
Well the screw up your are referring to is your own as if you had done your research you would know that trying to flash jb to the tablet s and not the xperia s will mess the tablet up as pointed out in numreouse posts and questions. so the reason people don't reply is that the questions have all ready been answered serveal times and the warings are there
rooted lighting wildfire on unoffical j.b from benni
and sony XTS rooted stock j.b thanks djrbliss
Click to expand...
Click to collapse
Can it be fixed?
nkxtc said:
I presumed I had done enough reading beforehand as the tool said Sony Tablet S so seemed the right tool for the job.
Click to expand...
Click to collapse
I read this article and made the same mistake:
androidadvices.com/sony-tablet-steps-update-latest-jellybean-firmware-click
I should have read the details better. I commented to the article that I bricked my device but it was apparently deleted...
The important thing I would appreciate knowing is if the tablet is completely unfixable. I just spent $150 on a new tablet but was hoping i could at least recover my tablet S and give it away.
soilchemist said:
I read this article and made the same mistake:
androidadvices.com/sony-tablet-steps-update-latest-jellybean-firmware-click
I should have read the details better. I commented to the article that I bricked my device but it was apparently deleted...
The important thing I would appreciate knowing is if the tablet is completely unfixable. I just spent $150 on a new tablet but was hoping i could at least recover my tablet S and give it away.
Click to expand...
Click to collapse
Now thats why i thought it was ok i read that site first too rather than here. Too much reading after the event not before. So who are these idiots at androidadvices.com? The advice below is from that site and is what got me to reset tablet. Now i'm even more annoyed at this.
Note: Just in a rare case if the device doesn’t boot up or show the home screen then long press the power button to turn off and then re follow the instructions.
nkxtc said:
After reading and reading and reading I am officially stuck hopefully someone or @stifilz can help. Hoping that i just missed something after reading too much info.
UK Sony Tablet S region changed when ICS came out for early update from US. Decided do JB update yesterday the flasher V3 got up to the end of data transfer part and tablet froze up and all coms went. left it for a while but nothing. After a hard switch off it hung at the sony logo. Got into recovery and did factory reset to try clear any issues or so i thought. Still hung at logo. Downloaded various ICS files and renamed to update.zip and tried to reflash. They all fail with the E: Prohibit error, occasionally error failed to mount system1.
I've attached my recovery log if anyone can help sort this il be a happy man.
TIA
Click to expand...
Click to collapse
Naming the file update.zip does not help as we can not see what is fully going on. Anyway it fails due to a messed up vendor. This would make sense as JB files would mess them up. Then it switches partition and that also fails due to vendor, but a slightly different error.
Anyway installing 0042 should work as they do not rely on vendor files. This is HoneyComb 3.2.1R2 and it is ROOTABLE. From there you can use flasher again. See my signature for links
EDIT:
4shared.com/zip/m-xXuCCv/signed-nbx03_001-ota-0042001.html
4shared.com/zip/03dah__B/signed-nbx03_001-ota-0042001.html
4shared.com/zip/8nuDXOQZ/signed-nbx03_001-ota-0042001.html
Hey thanks for getting back to me its appreciated. Tried all three files you sent link for. None worked it gives the prohibit/sku error. I've attached recovery files of each files attempt if you like to look at it. I've looked through a lot of your other posts and a few very similar ones as this and come to conclusion its damaged beyond repair and am tempted to use the warranty and chance my luck as its got few month left. Unlocked bootloader or the legendary files you have mentioned in another post would be useful but doubt we get to see either soon.
edit
Here's a shot in the dark...As tablet was originally a UK model and was changed for ICS is there any possibility that it has somehow defaulted back to UK and file signed-nbx03_003-ota-0042.001.zip would help. Its only thing i think ive not tried but cant find that version anywhere. Idea popped in head last week as there was a lot of reference to sku error being a region specific problem but then it went away until just now.
stifilz said:
Naming the file update.zip does not help as we can not see what is fully going on. Anyway it fails due to a messed up vendor. This would make sense as JB files would mess them up. Then it switches partition and that also fails due to vendor, but a slightly different error.
Anyway installing 0042 should work as they do not rely on vendor files. This is HoneyComb 3.2.1R2 and it is ROOTABLE. From there you can use flasher again. See my signature for links
EDIT:
4shared.com/zip/m-xXuCCv/signed-nbx03_001-ota-0042001.html
4shared.com/zip/03dah__B/signed-nbx03_001-ota-0042001.html
4shared.com/zip/8nuDXOQZ/signed-nbx03_001-ota-0042001.html
Click to expand...
Click to collapse
nkxtc said:
Hey thanks for getting back to me its appreciated. Tried all three files you sent link for. None worked it gives the prohibit/sku error. I've attached recovery files of each files attempt if you like to look at it. I've looked through a lot of your other posts and a few very similar ones as this and come to conclusion its damaged beyond repair and am tempted to use the warranty and chance my luck as its got few month left. Unlocked bootloader or the legendary files you have mentioned in another post would be useful but doubt we get to see either soon.
edit
Here's a shot in the dark...As tablet was originally a UK model and was changed for ICS is there any possibility that it has somehow defaulted back to UK and file signed-nbx03_003-ota-0042.001.zip would help. Its only thing i think ive not tried but cant find that version anywhere. Idea popped in head last week as there was a lot of reference to sku error being a region specific problem but then it went away until just now.
Click to expand...
Click to collapse
Sorry should have mention (but thought you would notice) they were the same file. Ok that is failing for the same reasons. Seems it is pretty messed up. You tried a factory reset yet? If not you may have some adb access on the boot logo???
Here comes a rant
stifilz said:
Sorry should have mention (but thought you would notice) they were the same file. Ok that is failing for the same reasons. Seems it is pretty messed up. You tried a factory reset yet? If not you may have some adb access on the boot logo???
Click to expand...
Click to collapse
I did notice but i eternal optimist and sorta hoped they different files even though filesize gave it away plus I already had that file from your links in sig but wouldnt be first time a company names files the same but different regions. Factory reset did numerous times now.
Didnt realise could get adb from logo screen so got hopes up again when lo and behold there in device manager was MTP device. After couple hours messing with it and getting lots of errors saying no driver etc I figured out putting hardware id in different adb usb driver inf files (USB\VID_054C&PID_05B3&REV_0100) would give me a working driver or so I thought. The PC decided after few minutes to give yellow exclamation and driver no longer works. Persevered with it until got driver stable but from command prompt adb says no devices in list.
Now all this happened early hours since 3am so not having greatest amount of patience (4hours not bad) i took a huff turned everything off and said [email protected]#k it ive had enough. This aint ever gonna work im resigned to this fact.
Now i may have not read one tiny part of the AIO tool which turned out to be biggest mistake i made in all this however for anyone else unfortunate to have a blonde moment would it not be possible to put some sort of checker in the tool to determine what is actually attached to be flashed based on hardware ID or something before any system changes occur. Having flashed many many devices from phones to consoles each and every one has a check of some sort before hand.
However putting that aside I think its disgraceful how Sony have treated this tablet and how locked down it actually is. This pains me but the £300 wouldve been better on a damn ipad.
@stifilz appreciate help you tried to give mate
Hi Guys, first of all thank you in advance for any answer you could give! it will be much appreciated!
Now, before anything I know there should be hundreds of posts about this issue but I was unable to find one that could apply to my scenario. But if you know any post that could be what I'm searching please just point me in the right direction :good:
Now, here is the problem:
We bought this cheap chinese tablet with andrioid 4.2.2 for my mother and it seemed to work pretty slow and some apps where not working correctly, there where a lot of adds even when she was not on an application, they just popped out on the main menu screen, and, when trying to register Instagram it displayed a message stating that there where too many users registered in the device. I tried to root the tablet because found that it could be because some temp files but it showed that it was already rooted... So my guess is that whoever installed the OS, did it with a "hacked" version of it.
Up to this point I have tried to do a hard reset but the issue is still going because it is still the hacked version of the OS, and I havent been able to find a way to completely wipe out the OS and install a fresh new version of Jelly bean 4.2.2
Can it be done with the device conected to a PC? or can it be done with a flashed memory card?
I know finding the firmware for a chinese tablet will be a major pain in the ass but, is there a version that could work for different models? (this is a Mobix MBX7 Plus, found the website mobix.com.ve but there is just no helpful info whatsoever)
Anyway, I hope you guys can help. Sorry for the somewhat long post
Again, thank you!!
Update!!!
I found info that could lead to the correct firmware, the CPU is an Allwinner Cortex A20, but Im still not sure if this format process is just like a PC, where you need drivers or everything is on the OS