Related
My sister have a Galaxy Player 50 with eclair...this PMP seems to be the same as the galaxy 3 (same resolution...and some other things) so can I flash lestatious or other rom on it ?
This hardware is not a phone...but maybe ?
Maybe I can try to flash...but if the pmp become soft bricked...it's over since i can't found an galaxy's 50 firmware...
Darius, I'm stuck with a brick galaxy player. I can try to flash with a galaxy 3 firmware if you want
Do you know how to make a dump of your device so you can share with me the original firmware?
http://forum.xda-developers.com/showthread.php?p=14493414
I don't know...but I'll try to find
Thanks!
I tried the firmware of galaxy 3, but didn't work
I dont think that its possible, first of all, despite being an android device, it doesnt have radio features, gsm 3g etc, only wifi, there are features that our phone does not support
Anyone found a solution for this yet? Not being able to test this device to it's full potential is really frustrating. Games are laggy and apps just do not run smooth on this one.
Has anyone tried z4root on this? I did and it freezes at "acquiring root shell".
@fedeff: how did you brick it?
Darius_AWS said:
My sister have a Galaxy Player 50 with eclair...this PMP seems to be the same as the galaxy 3 (same resolution...and some other things) so can I flash lestatious or other rom on it ?
This hardware is not a phone...but maybe ?
Maybe I can try to flash...but if the pmp become soft bricked...it's over since i can't found an galaxy's 50 firmware...
Click to expand...
Click to collapse
First root using One click root.
Give these commands in Terminal emulator
su
mount
Check for system partition.Suppose it is stlx (x=6,7,8 etc depending on system partition)
give this command to dump system...
dd if=/dev/block/stlx of=/sdcard/factoryfs.rfs
Copy it from sdcard and upload. I need to check it then i can help u out.
arunmcops said:
First root using One click root.
Give these commands in Terminal emulator
su
mount
Check for system partition.Suppose it is stlx (x=6,7,8 etc depending on system partition)
give this command to dump system...
dd if=/dev/block/stlx of=/sdcard/factoryfs.rfs
Copy it from sdcard and upload. I need to check it then i can help u out.
Click to expand...
Click to collapse
I'd gladly try it as long as Samsung gives me firmware, don't want to end up with a nice looking little brick here.
Is there any way that that an installer/firmware file could be saved in the device for backup purposes or something?
anon3524 said:
I'd gladly try it as long as Samsung gives me firmware, don't want to end up with a nice looking little brick here.
Is there any way that that an installer/firmware file could be saved in the device for backup purposes or something?
Click to expand...
Click to collapse
factoryfs.rfs is ur firmware backup....
@arunmcops: Thanks for the instructions. If someone try this and upload it'd be great for me.
@anon3524: I accidentally reseted the device to factory, trying to fix a problem with wifi (it suddenly stopped working one day).
arunmcops said:
factoryfs.rfs is ur firmware backup....
Click to expand...
Click to collapse
Ok, I am down to do this process you just explained as long as you or anyone explains to me how to recover the device with this "factoryfs.rfs" in case it gets bricked. You'd have to explain with detail how to grab this file and what to do with it etc. Also, if you could give further details on the initial process, that'd be great since a few things are unclear (to a brave noob like me).
Other than that, I am willing to try it to see the results.
BRING IT OON! *warface*
@arunmcops - I've got one of these, so have uploaded the file you wanted here - sorry, not allowed to post links yet:
dl.dropbox.com/u/6491656/Samsung/factoryfs.tar.gz (please don't flash this, its not a full rom)
I haven't made any changes to the base firmware other than renaming a couple of the phone.apk's to .old (cell standby was eating battery, and this device doesn't have a sim).
For fun, i've also uploaded a dmesg log
dl.dropbox.com/u/6491656/Samsung/dmesg.log
One other thing, i think the partition layout might be slightly different on this (might be wrong, don't have the phone) in that the internal sd card is mounted as /sdcard and the external one is /sdcard/sd.
Hope this helps!
Chris
@ctaylr Thanks for uploading the file.
I tried to load it using Odin, but it get stuck while uploading the file. The device is detected, but I think it's not transfering anything.
Is it possible to restore it form sd card?
fedeff said:
@ctaylr Thanks for uploading the file.
I tried to load it using Odin, but it get stuck while uploading the file. The device is detected, but I think it's not transfering anything.
Is it possible to restore it form sd card?
Click to expand...
Click to collapse
Hi...thats probably because it isn't intended as a flashable rom. Its just a dump of the stock firmware so that arunmcops asked to see to see if it had any resemblance of the galaxy 3 f/w, to see what we'd have to do to get a working custom ROM on this device..
Please don't attack it with any kind of Norse God ...especially until there is a confirmed route back to stock. All thats contained in the files is what you have on your device already - so there is also absolutely no point (for now).
If your having trouble with your device now, you could try doing a factory reset or playing about in Kies - i've fixed my device once after I got curious and flashed a custom ROM on here (which fyi completely messed it up - something like E:multi_csc: error: open /efs/imei/mps_code.dat because we dont have an IMEI code on this device) and then got it back working again - unfortunately i can't remember exactly what I did. Otherwise if this doesn't work I'll see if i can make a working stock package for Odin.
@ctaylr, yes I'm having problems with my device. It got soft bricked. I couldn't make it work using Kies. The only thing I can do is to start it in Download mode. If you can make a working package for oding that'd be great
This might help
http://forum.xda-developers.com/showpost.php?p=9515709&postcount=14
Thanks!
@fedeff Ok. i'll have a look over the weekend and see if i can make something that flashes.
Quick questions
1) do you have the 8gb or 16gb version?
2) have you tried going into recovery utils and doing a "wipe data/factory reset?" - you can do this by holding down home, volume down and volume up while turning the unit on - i seem to remember this fixed it for me, but it probably depends on how far Odin got while flashing. If your unit is already bricked, i can't see it doing much further harm
Thks
ctaylr said:
@fedeff Ok. i'll have a look over the weekend and see if i can make something that flashes.
Quick questions
1) do you have the 8gb or 16gb version?
2) have you tried going into recovery utils and doing a "wipe data/factory reset?" - you can do this by holding down home, volume down and volume up while turning the unit on - i seem to remember this fixed it for me, but it probably depends on how far Odin got while flashing. If your unit is already bricked, i can't see it doing much further harm
Thks
Click to expand...
Click to collapse
1) I have the 8gb version
2) By doing "wipe data/factory reset" is how I got it soft bricked. (the device wifi suddenly stopped working, and I thought that would help) After that it kept entering in the recovery mode. Then I tried to flash it with odin, now the only thing I can do is enter the download mode
Thanks again for helping me!
News?
Hi! I also like the others I am interested because my Galaxy player has 50 brick and I need someone to do dump the firmware so I can flash through odin! Please would you be my salvation and many other who have this player and would like to fix without waiting for the assistance of a month
Waiting for an answer I greet and thank all users who want to help me
sorry if English is not correct, but I'm using google translator (I'm Italian)
EDIT:
listen to me: http://forum.xda-developers.com/showthread.php?t=726673 This is the guide on how to get the dump of your fimrware if someone kindly did this process with its galaxy player 50 and then upload the file . tar obtained would help all
I don't think it is as simple as that.
If you fully read that topic above, it tells you. That will ONLY tarball the files in the /system folder. It doesn't dump the the bootloaders, efs or produce the initrd, which is also part of the firmware.
In fact that backup is exactly what i linked to earlier here, and doesn't flash properly through Odin. I don't know Odin very well (i use a ZTE Blade and clockworkmod normally ) but i'm going to take an educated guess it needs all of this information to successfully flash the player, and trying to flash without all of that probably won't work so well.
If i'm wrong, please let me know and i'll do what i can to help.
ctaylr said:
I don't think it is as simple as that.
If you fully read that topic above, it tells you. That will ONLY tarball the files in the /system folder. It doesn't dump the the bootloaders, efs or produce the initrd, which is also part of the firmware.
In fact that backup is exactly what i linked to earlier here, and doesn't flash properly through Odin. I don't know Odin very well (i use a ZTE Blade and clockworkmod normally ) but i'm going to take an educated guess it needs all of this information to successfully flash the player, and trying to flash without all of that probably won't work so well.
If i'm wrong, please let me know and i'll do what i can to help.
Click to expand...
Click to collapse
ok then I'm sorry I read the topic in a hurry and did not realize that you can not do what I say but re-reading now I understand!
ctaylr what do you advise me to do then? wanted to try an get into recovery and restore but I think the 3 keys are disabled enters only download ..
Google traductor sorry
Hello, and hope this is the right place to post this.
So, without any knowledge about all this smatphone/android stuff, I finally got one by a really good price. An ot-983.
Some friends conviced me to root it. I found a way to do it and noticing all the bloatware from it's original carrier (this phone was carrier unlocked when bought) I decided to clean up a bit.
I ended up cleaning a lot of stuff that I simply didn't use from a \custapp\ folder in there.
Thing is, a day latter I got a notification of a firmware update and I just said yes.
The said update failed, complaining it seems about the lack of some of the deleted bloatware.
Now, here's when the lack of thinking shows.
Wondering about it, I decided to look around options and found the factory reset.
Being a new and mostly empty phone, I did it (wiped clean the sd too),
And there, it went all into hell!
After reboot, it can't get my wireless anymore (have to use a static ip workaround for it...)
Root Checker says it's not properly rooted (using the same rooting technique as the first time doesn't fix it)
superuser still seems to be working, altho it crashes now and then with some errors about permissions.
also, can't get BusyBox working because it says there's no su binary and I can't download an update for it.
In short, I guess I need to get this phone to it's basics, if possible unbranded.
I don't really know what I need for that, but here I am, reaching at you that might help
I guess I need a stock rom and a way to flash it.
I'd appreciate a lot any help on getting whatever it is needed.
*cheers
root alcatel ot 983
ahkronn said:
Hello, and hope this is the right place to post this.
So, without any knowledge about all this smatphone/android stuff, I finally got one by a really good price. An ot-983.
Some friends conviced me to root it. I found a way to do it and noticing all the bloatware from it's original carrier (this phone was carrier unlocked when bought) I decided to clean up a bit.
I ended up cleaning a lot of stuff that I simply didn't use from a \custapp\ folder in there.
Thing is, a day latter I got a notification of a firmware update and I just said yes.
The said update failed, complaining it seems about the lack of some of the deleted bloatware.
Now, here's when the lack of thinking shows.
Wondering about it, I decided to look around options and found the factory reset.
Being a new and mostly empty phone, I did it (wiped clean the sd too),
And there, it went all into hell!
After reboot, it can't get my wireless anymore (have to use a static ip workaround for it...)
Root Checker says it's not properly rooted (using the same rooting technique as the first time doesn't fix it)
superuser still seems to be working, altho it crashes now and then with some errors about permissions.
also, can't get BusyBox working because it says there's no su binary and I can't download an update for it.
In short, I guess I need to get this phone to it's basics, if possible unbranded.
I don't really know what I need for that, but here I am, reaching at you that might help
I guess I need a stock rom and a way to flash it.
I'd appreciate a lot any help on getting whatever it is needed.
*cheers
Click to expand...
Click to collapse
pls i need you to explain to me carefully , step by step how you rooted the alcatel ot 983 , pls i have searching for the past weeks on google without results , pls help me , pls explain carefully , thanks in advance , i will be so happy if you help , thanks again in advance
mohamm said:
pls i need you to explain to me carefully , step by step how you rooted the alcatel ot 983 , pls i have searching for the past weeks on google without results , pls help me , pls explain carefully , thanks in advance , i will be so happy if you help , thanks again in advance
Click to expand...
Click to collapse
I simply downloaded the drivers from alcatel website
and then used the root package from here: <can't post outside links. it's a thread on error-soft dot net
Followed the instructions on the .txt included and it worked.
After that I think I had to install Superuser app (from live store)
be careful. My problems came from deleting some stock apps included and then doing a firmware update.
so, don't delete stuff around if you're thinking in doing the upgrade.
I need original stock alcatel ot 983 rom
hi guys
I bricked my ot 983 after flashing with different alcatel models rom
can some one please give me a copy of original stock rom for alcatel one touch 983
please
my email [email protected]
maybe your handheld is a brand new and nobody mod it yet
be patient bro and keep searching in google with any keyword
help me make tutorial on youtube
ahkronn said:
I simply downloaded the drivers from alcatel website
and then used the root package from here: <can't post outside links. it's a thread on error-soft dot net
Followed the instructions on the .txt included and it worked.
After that I think I had to install Superuser app (from live store)
be careful. My problems came from deleting some stock apps included and then doing a firmware update.
so, don't delete stuff around if you're thinking in doing the upgrade.
Click to expand...
Click to collapse
bro i dont know much about android stuff , but pls can you make a tutorial on youtube like this you can help me and millions out there for rooting the phone , ps help and thanks so much in advance
ahkronn said:
I simply downloaded the drivers from alcatel website
and then used the root package from here: <can't post outside links. it's a thread on error-soft dot net
Followed the instructions on the .txt included and it worked.
After that I think I had to install Superuser app (from live store)
be careful. My problems came from deleting some stock apps included and then doing a firmware update.
so, don't delete stuff around if you're thinking in doing the upgrade.
Click to expand...
Click to collapse
Where did you get the upgrade from ?
My story is like this: rooted, uninstalled some bloat from system and after a factory reset I'm stuck in the initial setup wizard (after completing almost all stages from setup it crashes at the end, after connecting at the google account - tryed to ignore that step but either way it crashes). Fastboot works but adb don't.
I do have another identical phone Alcatel One Touch OT-983 but with no root, with no modifications. Is there a way to backup the original/stock image and flash it over the malfunctioning one and restore it??
I tried with the proprietary upgrade tool from Alcatel but no succes as it close saying I don't need an upgrade because it's the last version of software installed in my phone. I thought even to broke intentionally the rom but I'm afraid that the upgrade utility from Alcatel will let me down, as I read that another users didn't managed to complete successfully the upgrading process. Is there a way to trick the system that has a previous version of Android?
Thank you for taking your time to read this and hope someone has an idea to solve our problem.
Have a nice day guys, you can contact me at puiocku at gmail dot com.
Have someone this stock rom (for Alcatel One Touch 983 (Valencia)) ???
Here is a Alcatel OT-983 rom, not sure which country it is from: https://www.dropbox.com/s/g2ljtrpqru3uihm/rom 983.zip?m
Here is my o2 uk backup rom: http://www.mirrorcreator.com/files/C4VEKHEI/OT-983_backup_uk.rar_links
this .zip file contains the boot.img, system.img and recovery.img
Someone needs to create a clockwork mod recovery for our phones now.
here is the sourcecode for this phone: http://www.mirrorcreator.com/files/85KDRTYP/OT_983_20130103.7z_links
Can't get to recovery
I have a bricked rooted OT 983, by error i installed a ZTE Blade's CM9 ROM and now i can't get my phone to recovery by using ADB that is the only way, i have downloaded the stock ROM but i don't know how to install it. :crying: PLEASE HELP!!!!!!!!!!!!!!!!!!!!
i done the same
Please help!! my phone is stuck on
jrdsetupwizard has stopped
cant get past setup screen
Possible solution for getting back original ROM on "stuck" phone
ryanraven said:
i done the same
Please help!! my phone is stuck on
jrdsetupwizard has stopped
cant get past setup screen
Click to expand...
Click to collapse
I recently "semi bricked", if my Alcatel OT983, if that's possible. It would not boot fully and got stuck on the "jrdsetupwizard has stopped" screen.
Here's what I did. The issue with getting the Alcatel One Touch Upgrade software to work appears to be getting the correct USB Driver installed. There are a number of potential USB drivers. This phone needs the driver in the Alcatel One Touch Upgrade. The stock Windows one or the one used for rooting the phone using instructions from the errorsoft website from the oneofgod will not work with this upgrade procedure.
1. Download the Alcatel One Touch Upgrade software and install on your machine. Open up the folder where the software is installed.
Look inside the folder that is called USB Driver and look inside the appropriate folder for your type of Windows machine 64bit or 32bit (x86) and install that driver for USB - that is the correct one for the upgrade
2. Run the upgrade software whilst connected to the internet. Connect your phone when it is off. You should just get the Android icon i.e. not charging or anything else. The icon should just stay there all the time the process takes place.
3. The upgrade will download. It's when the process gets to about 70% that the phone the starts upgrading. It will take a few moments but when it starts progressing into the late 70s and 80s you should be well on the way. At least that's how it went for me and I got my phone back!
Hope this helps.
to Hajj_3 :
Tanks for share the ROM.. I need it to recover my friends phone..
I just got this phone, not looking to root it yet as theres no option for a custom rom yet.
didnt want to start a new thread as theres not really any section for this phone yet.
Everything was fine until i installed the firmware update. Now applications cannot access the mic. Some complain about it being in use by another app. others like video editor or sound recorder will record, but the video recorder there is no file, and sound recorder crashes when you hit stop.
Alcatels website is useless, wasnt working yesterday, today it is but cant find any contact details incase its a bug in there firmware. Everything works fine except for that. Which is annoying because i use RTA software and now it doesnt as it cant access the mic.
any ideas?
Hi guys,
I've rooted my phone with abd and udpate.zip a long time ago, and it was fine till some days ago it stopped from receiving calls and the home button does nothing when pressed, although in recovey mode it works.
I've done a hard reset, reflashed the recovery.img, system.img and boot.img I've found in this post with fasboot, but did not solve the problem.
I've tried a firmware update with Alcatel's own software but it just keeps saying my firmware is updated already. I've also tried to edit the proinfo file, but I don't know what to change in the file. You can see more about that method here: http://forum.gsmhosting.com/vbb/9772370-post8.html
My guess is that the files that are corrupted and preventing me from receiving calls are somewhere else than those img's I've flashed. Has anybody got a FULL backup of his rom (e.g. Rom Manager) so I can recover the phone completely?
Thanks!
upgrade software
bussand said:
I recently "semi bricked", if my Alcatel OT983, if that's possible. It would not boot fully and got stuck on the "jrdsetupwizard has stopped" screen.
Here's what I did. The issue with getting the Alcatel One Touch Upgrade software to work appears to be getting the correct USB Driver installed. There are a number of potential USB drivers. This phone needs the driver in the Alcatel One Touch Upgrade. The stock Windows one or the one used for rooting the phone using instructions from the errorsoft website from the oneofgod will not work with this upgrade procedure.
1. Download the Alcatel One Touch Upgrade software and install on your machine. Open up the folder where the software is installed.
Look inside the folder that is called USB Driver and look inside the appropriate folder for your type of Windows machine 64bit or 32bit (x86) and install that driver for USB - that is the correct one for the upgrade
2. Run the upgrade software whilst connected to the internet. Connect your phone when it is off. You should just get the Android icon i.e. not charging or anything else. The icon should just stay there all the time the process takes place.
3. The upgrade will download. It's when the process gets to about 70% that the phone the starts upgrading. It will take a few moments but when it starts progressing into the late 70s and 80s you should be well on the way. At least that's how it went for me and I got my phone back!
Hope this helps.
Click to expand...
Click to collapse
The problem is, the upgrade software link doesn't work anymore :\.
ht tp: // ww w1. alcatelonetouch.com/global-en/ support/download/one_touch_ 983.html
(remove of spaces, im a new user so they won't let me post one)
Is there anyway someone can find a link for it because i have been searching for ages and haven't found one.
http://www.alcatel-mobilephones.com/global-en/support/download/one_touch_983.html
Hi, just recently some student tablets started to drop in my shop with problems, the latest one was an Indipad 10" made by LGS Caribbean, that is ALL the info I know about it since there are no labels anywhere in the tablet or the box, my guess is a generic Chinese re-branded tablet and it looks like is running ICS 4.0.1 but can't be sure since is locked with a number password. The client brought the tablet in cause her child was playing with it and activated the password screen lock and of course the child doesn't remember what he typed in. :silly:
I'm either looking to unlock the tablet, factory reset it or re-flash stock rom.
I already tried using the volume +/-/power combo for the recovery but it takes me to the android boot error screen, so I guess it has no recovery installed or it was deleted on purpose by the company. Also tried entering a lot of failed passcodes to see if it brings the account recovery option, but is a no go.
Did a Google search to see if I could also find a rom to flash on it but since I'm limited on the info about it nothing has come up.
Many thanks for any help.
No one?
Same thing right here. But i can tell you it is running android 4.0.4, and the build number is: crane_m1003h6-eng 4.0.4 IMM76D 20120921. Of course as you may know the 20120921 is the date so my guess is that it depends on how many updates those tablets have received already. Anyway, the recovery works, cus i have one in here working and you can access recovery from inside android(when you go to factory reset it gives you an option to do so, i did and it works perfect). But again just like you said, It wont work using hardware buttons. I was trying to find someone who can contact me from LGS Carribean but no luck at all. Just nothing, i have a working INDIPAD at this moment and thats how im telling you whats the firmware version and build. Like you said on your post, its an issue dealing with generic tablets it really is. I have not found even a similar enough firmware for the tablet to flash, but i can confirn you can use LiveSuitPack to flash them. Only issue is that i havent found a firmware to do so lol.... And ive look just about everywhere. Im going to run USB deview to check what the real hardware is and brand, if im able to find something ill let you know M8
Many thanks, client called in today and told her I'm still looking for a solution. Will wait for what you find.
Did you get this resolved?
Not yet, @home atm, so I'll check tomorrow for an update.
Seems we still on the black
Yes we are, so far i can tell you the processor is an A10, so its an A10 device. It shows as T10a for manufacturer, but so far thats all i can tell you. There might be a way to pull the firmware image from a working Indipad so that we have something to flash on the password protected ones. But for now, we are all waiting on something
Have same issue
enelyam said:
Yes we are, so far i can tell you the processor is an A10, so its an A10 device. It shows as T10a for manufacturer, but so far thats all i can tell you. There might be a way to pull the firmware image from a working Indipad so that we have something to flash on the password protected ones. But for now, we are all waiting on something
Click to expand...
Click to collapse
My mother-in-law is an English teacher and has several students with the same issue with a password they forgot or they locked the tablet on accident. I haven't been able to factory reset, but when you mentioned T10a, a quick Google search led me to show that EKEN makes T10a tablets.
I hope I'm not leading you down a rabbit trail, but here is their support site with manuals and firmware downloads
Also, searching on XDA apparently there is a way to get CWM on the EKEN T10a and instructions to flash to their latest ROM.
I haven't had a lot of experience with flashing ROMs, but I have flashed my personal devices before. So please let me know if this is possible in any way. I wouldn't want to mess something up. Well, I hope this helps.
mofongoloco said:
My mother-in-law is an English teacher and has several students with the same issue with a password they forgot or they locked the tablet on accident. I haven't been able to factory reset, but when you mentioned T10a, a quick Google search led me to show that EKEN makes T10a tablets.
I hope I'm not leading you down a rabbit trail, but here is their support site with manuals and firmware downloads
Also, searching on XDA apparently there is a way to get CWM on the EKEN T10a and instructions to flash to their latest ROM.
I haven't had a lot of experience with flashing ROMs, but I have flashed my personal devices before. So please let me know if this is possible in any way. I wouldn't want to mess something up. Well, I hope this helps.
Click to expand...
Click to collapse
Sweet, I'll do a hardware comparison tomorrow with EKEN T10a and see if they are identical devices (at least from the outside), if they match I'll just try that. The device is a brick atm so it doesn't matter trying to experiment with it.
mofongoloco said:
My mother-in-law is an English teacher and has several students with the same issue with a password they forgot or they locked the tablet on accident. I haven't been able to factory reset, but when you mentioned T10a, a quick Google search led me to show that EKEN makes T10a tablets.
I hope I'm not leading you down a rabbit trail, but here is their support site with manuals and firmware downloads
Also, searching on XDA apparently there is a way to get CWM on the EKEN T10a and instructions to flash to their latest ROM.
I haven't had a lot of experience with flashing ROMs, but I have flashed my personal devices before. So please let me know if this is possible in any way. I wouldn't want to mess something up. Well, I hope this helps.
Click to expand...
Click to collapse
OMG!!! IT WORKED!!!
Downloaded the T10A Firmware from the EKEN site, followed the steps and now the tablet is up and running perfectly!!! :victory:
Many thanks for your detective work
Omegadrive said:
OMG!!! IT WORKED!!!
Downloaded the T10A Firmware from the EKEN site, followed the steps and now the tablet is up and running perfectly!!! :victory:
Many thanks for your detective work
Click to expand...
Click to collapse
Awesome! I'm so glad I was able to help. I will go ahead and get mine done.
Its funny, but i have that firmware on my computer. Didnt even know why before this post. Now that i see your posts i realize i have flashed those tablet before using Eken firmwares lol.... Thanks a lot guys
What firmware worked for you? Im asking because i downloaded one of them and when i try to turn the tablet on it will keep booting up and wont flash the new firmware.
enelyam said:
What firmware worked for you? Im asking because i downloaded one of them and when i try to turn the tablet on it will keep booting up and wont flash the new firmware.
Click to expand...
Click to collapse
The one for T10A, version "T10 G-SENSOR6225".
I also had a bit of a problem at first trying to boot it into flash mode, but what I did was go to the device manager in Windows and saw that there where 2 copies of the special driver that the "LiveSuitPack_version_1.09_20111101.exe" installs, one with the checkmark like they said, the other I assumed was the tablet connected, so I deleted the one with checkmark and tried again, this time it went through and started the flashing process which took less than 2 minutes.
Straight after attaching the cable, and whilst still holding down the volume+ button, start pressing the tablet power button repeatedly. This (slightly frenzied) procedure puts the tablet into update mode.
Click to expand...
Click to collapse
That was the tricky part, to make it boot into flash mode, it has to be fast between connecting and starting to press the buttons, I took like a 1 second delay between the two things.
Also, got to point out I didn't do the CWM or the root mod, just did the firmware flash cause that's what the client wanted.
Its allright buddy, and thanks. Thing is that i was trying to update it as it said on the Ekken website. But the tablet didnt accept the SdCard update at all. I told you it should be done using LiveSuit and yet i was afraid of bricking the device using LiveSuit ha ha.... Thanks a lot guys, case solved. It took all of us to do so but hey, we made it!!!!
Hi, i have same indiPAD only camera front, i tried flash another rom EkenT10-6225-20120815.rar but touch not work good, works inverted and camera not work.
Im trying download firmware from server eken but very slow, can you shared anoter server please?
thanks
Pulian said:
Hi, i have same indiPAD only camera front, i tried flash another rom EkenT10-6225-20120815.rar but touch not work good, works inverted and camera not work.
Im trying download firmware from server eken but very slow, can you shared anoter server please?
thanks
Click to expand...
Click to collapse
Their server is kinda slow but I use Free Download Manager to download big files and speed up the download.
Also remember this was an experiment and it worked by chance, so no guarantee that it will for every indiPad out there, specially if the manufacturer changes the hardware, you should check the hardware info on the tablet just to make sure we are talking about the same tablet model or you could brick your device.
thanks bro, i know about rom experimental, i think same tablet from Puerto Rico, indiPAD, same eken t10a.
Can you tell me please what file worked on your tablet? i see some files
sun4i_crane_m1003h6-t10a-mc32x0-20121012.rar 274256 KB
t10.rar 200563 KB
t10_2axis_6225.rar 208067 KB
t10_3axis_7660.rar 208078 KB
t10a-mc32x0-20121012.rar 274256 KB
And maybe possible did backup rom from working tablet too. If you can and have one piece we can dump rom.
Pulian said:
thanks bro, i know about rom experimental, i think same tablet from Puerto Rico, indiPAD, same eken t10a.
Can you tell me please what file worked on your tablet? i see some files
sun4i_crane_m1003h6-t10a-mc32x0-20121012.rar 274256 KB
t10.rar 200563 KB
t10_2axis_6225.rar 208067 KB
t10_3axis_7660.rar 208078 KB
t10a-mc32x0-20121012.rar 274256 KB
And maybe possible did backup rom from working tablet too. If you can and have one piece we can dump rom.
Click to expand...
Click to collapse
t10_2axis_6225.rar is the one I used.
The only working tablet I had was the one flashed, the client already picked it up yesterday, so sorry.
First a few disclaimers to explain why I'm here.
- My secondary intention with this question is finding some answer as generic as possible to also help other people. Of course my primary intention is fixing my own issue, but the biggest part of it from what I can tell in the past 8 hours have been finding ROM files. All links are broken, except for 4.1.2 and none of those worked for me. In fact, they bricked my phone pretty hard.
- I'm on a mac. It's a nightmare finding tools for the mac, but I doubt any of them would really be any use for my case, one reason why I didn't even bother going for a windows vm. Another one is I'm traumatised by installing and running VMs. Finally this is for the challenge and learning a bit more.
- I've being trying to fix this through lots of research in the past 8 hours and I do know a few bits about going around and doing things (so sad this guide had no repercussion so far). But clearly, I'm dumb enough to brick my phone twice with no backups. At least could figure it out the first time (I had more time in hands as well). Please consider this. This means I've tried a lot of stuff you may wanted to advise, but it also mean I may have missed something obvious in the middle.
Okay...
By "bricked" I mean:
1. I can't go through the same process I did before to flash any CM image. CWM won't flash CM11 and CM12 recovery complains my bootloader isn't 4.4.
2. Both CWM and twrp recoveries should allow touch. None work, so I an't use twrp.
3. Battery keeps getting low and I've got no clue how to charge it to full again or even see how much it is at without installing twrp, which keeps getting uninstalled randomly at reboots, despite all of this topic about a solution. `fastboot getvar battery-voltage` doesn't show it. The mac script (which I was about to write myself based on op) also doesn't seem to help. In my case, I've removed the `./fastboot` because I've got it on my shell path.
I believe (1) happened, as I said on the disclaimer, right after I've flashed one of those 4.1.2 ROMs. By "flashed" I mean running the BAT file which mostly works on mac. ECHO of course wouldn't show the messages of progress there, but all fastboot commands do run.
And I also believe if only I could find 4.4 stock ROM files they might work or, at least, bring bootloader back to where it was so I could install CM12 again. And as far as I could notice without having Windows to try, no windows tool would really help here. That RSD Lite for instance, looks like it's just a GUI to run fastboot commands.
Above ALL
I just wanted to find a ROM stock file which I could fastboot flash into xt925 to reset it as hard as possible from zero and that the link will probably not break in the future for whoever may need it.
I figured THIS shouldn't be too hard to find, even for mac only, but it has been.
PS: Being able to fix the battery thing is also very important and quite a relevant follow up on the question! Right now I'm stuck with a ROM file that might work, but got no battery to try! ( 10 hours debugging now... )
only one stock kitkat rom for XT925 ! i'll upload this for you !
You know, if this works I'll have to, at least, go through some of your 187 posts and find a dozen or so to thank you way more than once!
I've now downloaded [this one](http://forum.xda-developers.com/showpost.php?p=63163078&postcount=6), which [he also posted again later on](http://forum.xda-developers.com/showpost.php?p=63272842&postcount=2), hoping it will do it! If it does, I'll try to upload in this post, as it looks like XDA hosted files last for much longer than anything else.
Only problem for flashing anything now is I can't seem to get enough battery!
I've got the Oukitel WP16 which a 64 bit and has an octa-core MediaTek Helio P60 MT6771V on Android 11. Actually a pretty decent rugged phone. Originally tried to root it through fastboot and bricked it about 2 weeks after getting it. For the life of me, I couldn't bring it back to life. Finally after 4 months of it just sitting in a drawer, I went about flashing it to bring it back to life a little differently than I was before and it stuck. Very thankful that it was working again because in those months I had destroyed 3 of your average break if you touch them phones. However me being me, getting it going again wasn't enough. So I gave rooting it a try again. Got it! Rooted with Magisk. Now because I have one of those devices I believe is under rated and under developed, I can't find any kind of development done on it whatsoever and want to build/port TWRP so I'm able to try a GSI ROM. My problem is that every tutorial I read or watch has nothing like what is my stock ROM. Either names of files are different or I find the files in other folders, I've got more folders than what I'm trying to port, and, I would need to double check again, but I wanna say that I've even found them in different partitions. So my question is, what do I do? Like fstab is not in the recovery but in something else. That something else that has fstab in it, my port doesn't have that folder at all. And there are others like that. I've tried several, I repeat SEVERAL different tutorials and cannot figure out what to do. I know it's beyond the capabilities of the tool, but I even tried one of those Hovatek port tools. Obviously didn't work because of the kernel. So to say I'm lost is an understatement. This isn't the first phone I've tried this with. Had another 64 bit with the same chipset that actually had a unofficial TWRP built for it. But when it came to try to port a ROM, I was left with files in different folders and things that weren't in the ROM i was trying to port. I eventually just have up because I kind of had to since scuba diving with the phone here in the Mexican Caribbean finally took it's toll on the phones external hardware. But yeah, back to my only question. What do I do in this situation? I'm mainly concerned about it because this WP16 has a night vision camera on it which I use quite often and don't want to lose that. Recovery has nothing to do with the camera but the ROM I'd like to port will. So figuring out what to do with the recovery could eventually lead me to my answer with the ROM. Anyway, kind of a long winded explanation just to get to what may seem like a simple question to some. Any help would be greatly appreciated.
finnroth69 said:
I've got the Oukitel WP16 which a 64 bit and has an octa-core MediaTek Helio P60 MT6771V on Android 11. Actually a pretty decent rugged phone. Originally tried to root it through fastboot and bricked it about 2 weeks after getting it. For the life of me, I couldn't bring it back to life. Finally after 4 months of it just sitting in a drawer, I went about flashing it to bring it back to life a little differently than I was before and it stuck. Very thankful that it was working again because in those months I had destroyed 3 of your average break if you touch them phones. However me being me, getting it going again wasn't enough. So I gave rooting it a try again. Got it! Rooted with Magisk. Now because I have one of those devices I believe is under rated and under developed, I can't find any kind of development done on it whatsoever and want to build/port TWRP so I'm able to try a GSI ROM. My problem is that every tutorial I read or watch has nothing like what is my stock ROM. Either names of files are different or I find the files in other folders, I've got more folders than what I'm trying to port, and, I would need to double check again, but I wanna say that I've even found them in different partitions. So my question is, what do I do? Like fstab is not in the recovery but in something else. That something else that has fstab in it, my port doesn't have that folder at all. And there are others like that. I've tried several, I repeat SEVERAL different tutorials and cannot figure out what to do. I know it's beyond the capabilities of the tool, but I even tried one of those Hovatek port tools. Obviously didn't work because of the kernel. So to say I'm lost is an understatement. This isn't the first phone I've tried this with. Had another 64 bit with the same chipset that actually had a unofficial TWRP built for it. But when it came to try to port a ROM, I was left with files in different folders and things that weren't in the ROM i was trying to port. I eventually just have up because I kind of had to since scuba diving with the phone here in the Mexican Caribbean finally took it's toll on the phones external hardware. But yeah, back to my only question. What do I do in this situation? I'm mainly concerned about it because this WP16 has a night vision camera on it which I use quite often and don't want to lose that. Recovery has nothing to do with the camera but the ROM I'd like to port will. So figuring out what to do with the recovery could eventually lead me to my answer with the ROM. Anyway, kind of a long winded explanation just to get to what may seem like a simple question to some. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Your device already have TWRP [Firmware version: OUKITEL_WP16_RU_V04_20220621 ] but you not need Custom Recovery for install GSI. Use stock recovery.
About GSI with a night vision camera support so is much expensive solving that. You can try but need very experience and patience of the tests and solutions.
lopestom said:
Seriously? Thank you! I'm guessing the link is gonna be in 4pda being that it's Russian? I've spent a month searching and haven't found anything whatsoever. And since I don't read Russian, I always overlook 4pda even though it's been a great resource in the past. And yes, I'm aware you don't "need" custom recovery for GSI's. It does make things a little easier for me though.
Click to expand...
Click to collapse
The recovery issue will be solved since there is a recovery out there. That still doesn't solve the mystery and problem i have of files being in different places though. In that case what do I do if the files isn't in the same place in the port as it is in the stock, or the other way around? Add the stock file to the same folder it is in for the port? Or should I make a new folder in the port that's name is the same as in the stock? If neither, what do I do?
finnroth69 said:
Seriously? Thank you! I'm guessing the link is gonna be in 4pda being that it's Russian? I've spent a month searching and haven't found anything whatsoever. And since I don't read Russian, I always overlook 4pda even though it's been a great resource in the past. And yes, I'm aware you don't "need" custom recovery for GSI's. It does make things a little easier for me though.
Click to expand...
Click to collapse
No! Search my repository in the github in the release option.
finnroth69 said:
The recovery issue will be solved since there is a recovery out there. That still doesn't solve the mystery and problem i have of files being in different places though. In that case what do I do if the files isn't in the same place in the port as it is in the stock, or the other way around? Add the stock file to the same folder it is in for the port? Or should I make a new folder in the port that's name is the same as in the stock? If neither, what do I do?
Click to expand...
Click to collapse
As I wrote before, it is very difficult to solve issues like the original stock ROM camera. There are even one or two people who managed to get this to work.
Now what you don't understand: If you want a Custom ROM, use GSI and adapt, solve, analyze and test by changing some stock ROM files in GSI. You must understand that you need experience and time. You can even compile a Custom ROM - any GSI - specifically for your device. So you just need to have the source code of your device, have the GSI source code and know how to compile the file so that you can do the tests. Again, you must understand that you need experience and time.
If you haven't researched what is GSI and still think that Custom ROMs portability that happened before until Android 7.1 then look, read and update yourself.
In your questions, be as detailed as possible. You write a lot of parts and you scramble the words.
As for having GSI normally I already wrote where there is an instruction to install and you follow. As for TWRP, look it up on my github.
As for solving something in the GSI, if you managed to install it and still used the phh options to try to fix any bad part, then it is only you who will be able to solve any error/adaptation/bug/extra installations that there.
Trust me when I say I understand what you're saying. I have done some testing I have watched tutorials, I have studied. but everything that I have seen is basically switching a file from a folder on the stock ROM to a folder in the ported ROM with the same name as what's in the stock ROM, and possibly adding a little script to something. What I'm trying to figure out is what I asked. Fstab is not in recovery on my phone's stock ROM. It is in something else. But fstab is in and a part of recovery for TWRP. So even though there might be a TWRP for my phone doesn't help me to know if I should be creating that same folder that's in my stock ROM in the ported one for fstab or other files that are like it. I have downloaded the TWRP from your profile and I've gone to the 4pda and discovered that you're the dev who ported it with and without encryption. Nice work and thank you! I would like to move beyond being a flash baby though. So I'm simply trying asking that one specific question to help me learn because it is something I am lost on. Whether it is to port recovery, port a ROM, or whatever, I don't know what to do when the location of the files I need to port from the stock aren't matching with the with the location of the files in the port itself. Fstab is just one example. I'm gonna send you a friend request. Later when I fire up my laptop, I'll take screenshots to physically show you exactly what I mean. Please be patient and don't get upset at me for trying to learn. As well as please take your time in responding. It's no rush since I've got a business to run and this is something I'm trying to teach myself on the side. It really is something I'm lost on, and if I'm lost on it, how many others has it confused as well?
As for the camera app issue. We can forget I asked that also. I understand completely what you're saying about it being far beyond my reach right now. Thank you for the heads up on that.
Mr. Lopestom can you please help me with your recovery images? I cannot seem to get any of them to boot. I've tried the with script found on 4pda, without that script, I've tried flashing an empty vbmeta, but nothing is getting the images to boot. See attachment for script I'm talking about. Attachment only shows me running it, but I have tried without.
What sense does it make to flash an empty VBMETA ? You typically pull the existing VBMETA and pass this file to Fastboot what rewrites 2 bytes in that file.
finnroth69 said:
Mr. Lopestom can you please help me with your recovery images? I cannot seem to get any of them to boot. I've tried the with script found on 4pda, without that script, I've tried flashing an empty vbmeta, but nothing is getting the images to boot. See attachment for script I'm talking about. Attachment only shows me running it, but I have tried without.
Click to expand...
Click to collapse
The problem is not in the vbmeta file. You can use this one if you can: Post in thread 'Looking for a walkthrough on installing a custom ROM on a BLU G90 PRO' https://forum.xda-developers.com/t/...om-rom-on-a-blu-g90-pro.4253737/post-85180967
The big fact is that the company put a recovery.img stock file inside /vendor/etc/ and you should know how to deal with it. So only removing this recovery.img and repacking modified vendor.img made by u; install that in your device so you can have TWRP.
jwoegerbauer said:
What sense does it make to flash an empty VBMETA ? You typically pull the existing VBMETA and pass this file to Fastboot what rewrites 2 bytes in that file.
Click to expand...
Click to collapse
I'm not sure to be honest with you. Like I told lopestom, I'm just trying to teach myself as I can in my free time. A lot of what I do is imitate what I see or read. While reading post about flashing twrp i had read something about flashing an empty vbmeta file.