I can't even complain about anything because if was going to, I should have done it before I goofed up. first strike was letting it goof the region. Fine. But what killed it was not flashing the image while moving to ics. It stayed at cleaning for like 40 minutes, and I turned it off. I'm certain I have the us version.
I am hoping someone can throw me a bone about what may have come after installing the image, as well as if there's some sort of command I can enter to push that skipped img file. Or if I can use the data from another one to fix this one. also if I can push something in adb to fetch the region. Or if there are gods, a region free update. Or a program that can flash via recovery and not in a normal boot.
I have a couple different versions of ics on the device, one wants a signature, and the other says something doesn't match and aborts it. Reading around I hear vaguely about how people with the same device managed to fix it, and the ones who have posted working links to drivers or zips, I have tried them to no avail. When the other one gets here, I'm hoping I can get the update zip from that and maybe click away at the screen until I get some type of results.
Also, is there any type of information on what hardware part all of this is stored on? Maybe I can replace that.
Maybe someone can point me in the right direction. Though, I'm sure someone might have shed light on some of it, and it's buried under a bunch of tablet s advice...
Related
So, heres my problem. I have 2 samsung fascinates. I screwed one up a while back and was able to pull it back together and get it into ICS on CM9 with all the proper files using Odin.
I recently got a second samsung fascinate and was attempting to flash the same files, through Odin, but was having trouble.
I was able to get CWR (I believe it was voodoo) onto the phone, but once in recovery mode and having cleared all cache's, wiped files, and factory reset, I still could not successfully instal the files from the SD card (the same ones that worked on the 1st fascinate)
SO
I downloaded another version (or so I thought), Pushed it through Odin, Odin said it passed and auto restarts the phone. The phone never comes back on.
In hindsight think that CWR somehow ended up being deleted from the phone (if thats possible without doing it on purpose) before what was pushed by Odin was actually pushed. The file might have been wrong, im not sure, I will post up the exact file name when I get home.
At this point, the phone is completely unresponsive,. No holding the volume, plugging it in, putting the battery in. Jig doesnt work, Heimdall Doesnt work, Fastboot doesnt work. No download mode, period. No lights, no vibration. Tried multiple batteries, tried assuming the screen was bad, tried multiple cables, tried plugging into wall and computer. Nothing.
Mac will not notice the device at all once its plugged in, however, PC notices and starts to wig out. I have to hold the power button down, while its plugged into the computer to allow for it to search for drivers
The driver is SEC S5PC110 TEST B/D notification.....I feel like this is for a phone other than the fascinate.
Either way, I try to download fascinate drives, or the driver its calling for, both being unresponsive.
Am I completely screwed? Or is the questions more that I found myself at the point the I have either deleted what was deemed "Un-deleteable" or do I need to take the board out and get a soldering iron?
Also, I know a developer, I have taken it to him and he looked at it and scratched his head......hopefully someone has some sort of solution. Thanks
What file did you try to flash?
I9100_APBOOT_I9100XXKP2_CL17109_REV02_eng_mid_ship.tar
This was the file I flashed. Again, in hindsight and based on what I was reading in the forum, it looked good. I have no idea what it actually is, and therfore should not have flashed it. But I was in read and repeat mode, so I didnt question much. If I can track down the exact thread I was in I will post it up as well.
Philveatch said:
I9100_APBOOT_I9100XXKP2_CL17109_REV02_eng_mid_ship.tar
This was the file I flashed. Again, in hindsight and based on what I was reading in the forum, it looked good. I have no idea what it actually is, and therfore should not have flashed it. But I was in read and repeat mode, so I didnt question much. If I can track down the exact thread I was in I will post it up as well.
Click to expand...
Click to collapse
thats what happens when you flash files for another
device to this one. there is a guide in the general section that has everything you needed. hopefully next time you do a bit more research before you get flash happy. at this point unbrickable mod is your only way out and that requires some microscopic soldering skills.
It looks like you flashed a bootloader for the Galaxy S2.
Interesting. It was in a fascinate forum talking about how to add ics to a fascinate phone.....hmm.
EDIT: Well I managed to get clockworkmod installed and everything; still having some issues with aspects of it, but in general I'm good. I'll probably make a dedicated thread to the device; if anyone wants to suggest a proper forum section, be my guest.
Ok, so I need some assistance on installing CWM or another recovery mode on my YourPad P4. I've already rooted and installed ROM Manager, but it could not find a compatible CWM version.
Now, first off I have also been unable to get an exact or better identification of this tablet other than it being sold as a "YourPad P4" and that it's model is MID; so I might also need help getting more details to better assist the finding of a compatible or working recovery.
Here is some information about it...
* Site purchased from/detail page:
http://www.yourstoreonline.net/yourpad_p4_new_android_40/id2040716/product.html
Don't worry, I got it for ~$100 (with the 1GB RAM upgrade), not the displayed price on the site!
* About tablet page info:
Model number: MID
Android version: 4.0.3
Kernel version: 3.0.8
[email protected] #2
Build number: 20120807-A721
Also, before I start messing with it I was going to make a nandroid backup to share for others...does nandroid backup firmware as well? I've never needed to restore a backup so I have no idea what goes into it and can't find a quick answer. I'd like to make a backup of a clean as possible system to share for anyone wanting it. Although I'm surprised that its not been mentioned on xda, I'd expect this tablet to have at least been asked about once considering it was mentioned on woot.
Thanks to anyone for any help, and I apologize if this should be in a different section. If so, could a mod please move it before any fuss is made.
And now, I'm off to bed (so I won't be responding/checking this for a few hours).
Not to sure about the rules for thread bumping, but I just wanna make sure this gets seen soon (as I'll be very busy and it will be hard to work on it next week and the the days that follow).
Also I thought it was worth mentioning now that only really mentions of this tablet I can find are in posts by me, ahahahahaha
EDIT: Oh, and I havn't verified I even have a recovery partition yet as I can't cat /proc/mtd
it's been about a week now and no response; I even posted it over here http://www.androidtablets.net/forum...cs-need-help-recovery-install-yourpad-p4.html
so bumping, if anyone at the very least knows some mystical other worldly site that somehow manages the chance of providing me an answer over the ever amazing xda; please post
tabletrepublic.com/forum/iview-760tpc-ployer-momo9/iview-760tpc-k-ployer-momo9-firmware-rom-releases-1610.html
Go here you will find all about all winner a10 tablet
Just go there and for cwm recovery 5
Select
3.) ClockworkMod Recovery
5 (for AllWinner A10 tablets) option.
Just read all step carefully
And do at your own risk me or xda is not responsible if you brick your device..
we all should be polite enough to press thanks for anyone who helped US.
AJ88 said:
tabletrepublic.com/forum/iview-760tpc-ployer-momo9/iview-760tpc-k-ployer-momo9-firmware-rom-releases-1610.html
Go here you will find all about all winner a10 tablet
Just go there and for cwm recovery 5
Select
3.) ClockworkMod Recovery
5 (for AllWinner A10 tablets) option.
Just read all step carefully
And do at your own risk me or xda is not responsible if you brick your device..
we all should be polite enough to press thanks for anyone who helped US.
Click to expand...
Click to collapse
Thanks alot for this, I'll definitely read it over a few times before attempting. Hopefully this will work out. Thread is still open for any other input, so anyone else coming here that can provide any additional help go ahead and post.
Well I still have been unable to get a recovery option going. I tried the link mentioned by AJ88 and it didn't work for me. Essentially the link boiled down to 2 simple adb commands and a custom recovery.img. First step was to "adb push recovery.img /data/", but I ran into a permission denied issue and could not figure out a way around it (didn't want to mess with chmod, but I did run the "fix permissions" script in the clockworkmod rom manager. So instead I just pushed the recovery.img to my sdcard. Next step was "adb shell "cat /data/recovery.img > /dev/block/nandg; sync""; so instead I went "adb shell" then su to make sure I didn't get any more issues, then just "cat /sdcard/recovery.img > /dev/block/nandg; sync". Rebooted and tried all combinations of key pressings to access recovery with no luck (even tried via adb). So any ideas on my next course of action?
youtPad P4 issues
Dear EarthBoundX5,
Please do not feel alone in what I might be perceiving as "buyer's remorse" as I also own this device and have begun to have issues with it functionality. Initially I was attracted to this device for what seemed a myriad of available functions and abilities, however I'm really starting to believe the old saying, "you get what you pay for".
My main issue at this point is when using the free Kindle app, after selecting my book, the screen goes completely blank and does NOT come back with the reading material I've selected. If I touch the back button, I get a brief flash of the screen showing the page that I'm on in the book, but after that nothing. I've tried rebooting the machine, currently trying a fresh install of the Kindle app, we'll see how that goes TODAY.
I also have another off-brand tablet, iBridge, which was purchased during the frustration period of waiting for YourStore . com to get their act together and send me the YourPad. Funniest part about it though is that the iBridge comes with a booklet thats 4x the size of the poorly written "booklet" that the YourPad people put out.
I'm sorry that I don't have a solution for your problem as I'm a complete newb with the tablet world, but wanted to at least touch base with you to let you know "you are not alone. I am here with you...." LOL
Found you with a google search for online help regarding YourPad, and it brought me to you, and this seems like the most helpful place I might have found in reference to oddball tablet issues. Take care, have a good day. and I'll check back in to notify regarding Kindle reinstall.
Well I've been waiting for a reply to either of my threads with no luck, so today I figured I'd just try again the method of manually setting up a recovery, and this time I just decided to try and hold every button I could while powering and and BAM RECOVERY MODE *****ES!!!!!! So guess either I must've just screwed up last time or something. Anyways, I'll edit the OP to reflect all this later...maybe start a dedicated thread with any quirks I figure out down the line using this tablet; and of course post my nandroid backup. When I setup my 2nd YourPad, I'll make sure to make backups of any files I may have had to change (ie, nandg, etc). The question is, what section would such a thread belong?
5lita5 said:
Dear EarthBoundX5,
Please do not feel alone in what I might be perceiving as "buyer's remorse" as I also own this device and have begun to have issues with it functionality. Initially I was attracted to this device for what seemed a myriad of available functions and abilities, however I'm really starting to believe the old saying, "you get what you pay for".
My main issue at this point is when using the free Kindle app, after selecting my book, the screen goes completely blank and does NOT come back with the reading material I've selected. If I touch the back button, I get a brief flash of the screen showing the page that I'm on in the book, but after that nothing. I've tried rebooting the machine, currently trying a fresh install of the Kindle app, we'll see how that goes TODAY.
I also have another off-brand tablet, iBridge, which was purchased during the frustration period of waiting for YourStore . com to get their act together and send me the YourPad. Funniest part about it though is that the iBridge comes with a booklet thats 4x the size of the poorly written "booklet" that the YourPad people put out.
I'm sorry that I don't have a solution for your problem as I'm a complete newb with the tablet world, but wanted to at least touch base with you to let you know "you are not alone. I am here with you...." LOL
Found you with a google search for online help regarding YourPad, and it brought me to you, and this seems like the most helpful place I might have found in reference to oddball tablet issues. Take care, have a good day. and I'll check back in to notify regarding Kindle reinstall.
Click to expand...
Click to collapse
I don't feel any buyer's remorse...yet at least, haha. If I end up having the same issues as you, maybe I'll change my mind; but I really don't see much wrong yet with this tablet. I mean, obviously its cheap and all, but for the poor man its fantastic. But ya, I HATE the YourStore, they took FOREVER to ship out the tablets. Anyways, for people like you, it really makes me thing I should take point on this tablet and start a dedicated thread.
In my attempt to root my phone, I have caused some major issues.
Specs:
Mytouch 3G (I guess 1.2 since it has the 3.5mm jack)
Current:
S-on
HBoot-1.76.007 (SAPP31000)
CPLD-13
Radio-2.22.23.02
I know I flashed the incorrect stuff from what I found in my research. I cannot use Fastboot because it does not allow remote. No recovery options
I tried following a direction to root, but the sapping file was on megaupload which is not there anymore, so I searched for another from a differant site. The whole issue is I kept getting the incorrect ones, so this happened.
The last one was way off, as you can tell from the above info. I believe I found a correct one, but a new issue arose. When trying to load it, it stay's on "Unzipping" for system. In this particular img, it is the first to be done. I thought it was a currupted file, so I got another from a different source. Same issue. Seems to do that with any I try, including those I got from this site. I am Guessing the incorrect version that got installed.
Only options I have is "Fastboot" and "Simlock". no recovery. The OS will not load and cannot do the home+power boot to get into recovery.
I have been trying to locate how to flash one item at a time from the goldcard I made, but with no luck, most of the links I find seem to be dead, or lacking in the detail I need.
Right now, my phone is useless, and any help would be most appreciated.
While I want to keep this thread open until it's fixed, I suppose the first question is "how to I flash the correct SLP from an SD card without anything else?"
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
Hey all,
I've never rooted a phone before so since I have a spare model, I figured I'd give it a go.
Hearing about this forum, I checked it out and was sent to the Sony site. I understand I needed to unlock the bootloader first, which I did and can confirm I get that alert as my phone starts about it not being safe.
Hint for future readers: don't do this in a virtual environment, I had issues doing this until I used an actual computer and not a VM (mods and folks with more experience: feel free to correct me on this or shed some light). To be clear, I have a separate host running Proxmox (Type I hypervisor) and was able to forward my USB connection to test with ADB and such. I do most things in a virtual environment to not mess up my physical computer.
This was all done last week. Well today, Monday, I decided to continue with my rooting excursion, only to run into the issue I am currently facing.
After many, many Google attempts and following whatever links in this, I finally found this link. Well, I was within a VM, downloaded the linked flashing tool, and ran the first two commands:
- adb devices
- adb reboot bootloader
After doing this, my phone turned off and I wasn't sure what to expect, so I pressed the Power button to see what would happen - nothing. So then I remembered that Friday I was having issues communicating with my mobile phone in the VM to unlock the bootloader in the first place, so I figured I'd try to move it to my physical computer....then I was stuck on a reboot cycle!
To be clear, my issue is that I am stuck on a boot loop. It prompts the error of the device being unsafe, waits 5 seconds, then displays the Sony splash screen. Rinse, wash, repeat; same thing.
I have a Sony Xperia XA1 (G3123) model.
Can anyone shed some light?
Am I screwed?
Please halp!
I dug around a bit more, found this link but the issue is that I cannot boot into anything, at least not that I'm aware of.
tryingToSurvive said:
I dug around a bit more, found this link but the issue is that I cannot boot into anything, at least not that I'm aware of.
Click to expand...
Click to collapse
have you tried installing a custom recovery?
this may help https://forum.xda-developers.com/xa1-ultra/development/g3221-built-sources-t3622886
keifus.rahn said:
have you tried installing a custom recovery?
this may help https://forum.xda-developers.com/xa1-ultra/development/g3221-built-sources-t3622886
Click to expand...
Click to collapse
Hey @keifus.rahn for following up.
I did find that thread after continued poking, which I am still checking now. And I eventually made a post on there just now discussing my current dilemma.
I downloaded the Flashtool but didn't understand how it worked, nor do I still yet. I tried debugging it and the issue is that the "java -version" call doesn't work within the directory's own structure. I do have java installed on my test Linux VM though.
Past that, I tried with the latest boot.img as well as the recovery.img that I found. I think that the build numbers are off, or maybe I am just not understanding where I am lacking.
You can look at the bottom of the last page for a breakdown of what I did:
https://forum.xda-developers.com/xa...21-built-sources-t3622886/page94#post80481385