Related
Hello,
I want to ask someone if there is a way to delete some texts when the device is powered on?
I have a problem that when I power on my device under the text "smart mobility" I got a message like this one: "Test only, Not for sale" .... so is there a way to delete this **** from the system ?
Thanks
using advanced config tool, you can find out the 2 (or 3) .gif files that are used in the startup animation. one of them will have that text. You just have to replace it with another.
Im not 100% sure that the smart mobility one can be changed but its a good place to start.
ASK768 said:
using advanced config tool, you can find out the 2 (or 3) .gif files that are used in the startup animation. one of them will have that text. You just have to replace it with another.
Im not 100% sure that the smart mobility one can be changed but its a good place to start.
Click to expand...
Click to collapse
The smart mobility logo is not an image per say. It is embedded in the "splash" area within the rom. It can be changed but not as simply as changing .gif files.
If the text you are seeing is on the first boot screen (the Smart Mobility screen) you won't be able to remove it through Advanced Config. The startup animation is the second boot screen (typically the HTC logo or some other animation). Are you seeing the text on the first boot screen for sure? If so, I can give you a new .nbh file to flash with CustomRUU that will give you just the Smart Mobility logo.
hi - does that nbh file exist? i've got a similar problem and have tried flashing different roms but the "test only" persists.
thanks in advance.
hi,
After spending many time trying to root my storex tab 901 I bought in france (Already installed on 4.1.1 with google play), Iwas finnaly able to root it using adb and command line.
to do so:
- Download attached file
- Download from google SDK usb_adb_driver
- Go to your device parameters-> USB -> enable debbuging mode
- create a c:\root folder on your windows XP computer then Extract the zip file attached into it.
- Plugin your device to the computer, when prompted for driver, use google sdk USB_ADB_Driver
- When done, open a windows terminal command line
- type: c:
- type: cd \
- type: cd root
- type: cd rootkit
- type: go.cmd
If everything goes well, your tablet should reboot. you can try installing the free app from google store called "Root checker" to confirm your device is properly rooted.
Also, if you lost the original rom and live suite, here is the link to download the latest build from storex web site:
(I will post the link later when I find it)
JB 4.2.2
CAUTION: USE THIS ROM AS YOUR OWN RISK.......Be sure you have the official rom in case it is not working for you. It appears that even though you have the same tablet Reference, depending on when you buy it, hardware might be a bit different and most likely you will take the risk of having a unusable Touch screen or wifi...
I found out you can fully use your Ezee Tab 901 4.2.2
you can install rom from Manta MID 13.
You will be able to install the rom using Livesuite.
Gain:
- Android 4.2.2
- Root Access out of the box
- Play store installed.
Everything will be working
For the link type in google:
MID13 Android 4.2.2 Jelly Bean - Manta Multimedia Info
select google link called: manta.info.pl
select the link catshare or 4shared.
Start live suite 1.7, select the download img file, do a format when prompted. You done.
When the tablet restart, go to the parameter icon, and change language to French or english
Procedure on the Ezee tab 901 with livesuit:
- completly turn off the tablet, unplug cable
- start livesuite and select the downloaded image file
- keep the VOL- button pressed and plug the usb cable
- without releasing the VOL- button press the Power button 6 times.
- You should hear windows sound saying a USB device has been plugged
- if windows request it, install the driver from Livesuitefolder\usbdriver
- Livesuite should automatically start the flashing process.
- when prompted, "Format device" press YEs.
- When it s 100% you tablet should reboot.
Done.
Note: I did not invent anything, thanks to the good work of MANTA team members. I just found out this rom works on my tablet out of the box.
Hi,
Thanks for sharing these tips. I'm gonna try to update to 4.2.2, hoping this is going to fix some problems with this tablet.
I've been looking a lot for information about how to update ezee tab 901, so you did definitely a great work !
edit : iflash went well, but touch screen is not responding anymore. Any idea of how to solve it ?
Thanks.
samus64 said:
Hi,
Thanks for sharing these tips. I'm gonna try to update to 4.2.2, hoping this is going to fix some problems with this tablet.
I've been looking a lot for information about how to update ezee tab 901, so you did definitely a great work !
edit : iflash went well, but touch screen is not responding anymore. Any idea of how to solve it ?
Thanks.
Click to expand...
Click to collapse
Hi,
did you try going into recovery mode and factory reset? (shutdown tabel completely and keep press on volume+key then press power button)
in the menu, using vol+/- scroll down to wipe factory reset and validate by pressing the power key.
Let me know how it goes.
btw, are you sure your tablet is a Ezee tab 901 and not 971?
Cheers
Hi,
Yes I've got 901 and not 971 (written on the back of the device). I tried factory reset , but still the same problem. However, I flashed again with the original rom, and then touch screen went functional again but the wifi switch is kinda "broken" : it's impossible to turn on wifi from the Settings menu.
I returned the tablet where I bought it, seems there's a sort of material problem with it :/
samus64 said:
Hi,
Yes I've got 901 and not 971 (written on the back of the device). I tried factory reset , but still the same problem. However, I flashed again with the original rom, and then touch screen went functional again but the wifi switch is kinda "broken" : it's impossible to turn on wifi from the Settings menu.
I returned the tablet where I bought it, seems there's a sort of material problem with it :/
Click to expand...
Click to collapse
Im sorry to hear that, i dont think something is broken, i had the same issue with a memup tablet, even though it was a same reference, some model had different hardware, sonlike you after testing multiple rom i had only touch s creen and no wifi ( wifi switch went back to off when i tried to turn it on) or on other rom, i had working wifi but no touch screen.
I hope they will replace your device...
Cheers
pierrottls31 said:
Im sorry to hear that, i dont think something is broken, i had the same issue with a memup tablet, even though it was a same reference, some model had different hardware, sonlike you after testing multiple rom i had only touch s creen and no wifi ( wifi switch went back to off when i tried to turn it on) or on other rom, i had working wifi but no touch screen.
I hope they will replace your device...
Cheers
Click to expand...
Click to collapse
Yep the wifi switch is exactly what i've got on this storex. Thanks for your help anyway. Ho and by the way, I properly rooted it with you first tuto
Cheers.
Fast custom ROM 4.2.2 by TOxico for Ezee tab 901
Guys,
I manage to find a very fast and usable rom for our tablet: (THanks to Toxico.) this rom will change your life.
All information and download are in the thread here:
http://forum.xda-developers.com/show...php?p=42274265
It should basically work on any A13 device with livesuit (tested on my Ezee tab 901 and on my 704CET mem up)
This rom comes with no TS driver, but there is all explanation and download to install the needed driver.
note: you might loose the camera though. I encourage you to read the full thread before going further and flash your tablet.
If you want to know the driver used on your tablet, run a adb shell and type lsmod (You will have a list of loaded/used driver.)
Dont be scared, everything is written in the toxico's thread
My only advice, if you dont know how to use adb, do not try it, this is not that easy.
I hope this will help.
Best regards.
As usual do it at your own risk and even more: make sure you have the original rom... just in case
Tutorial for 971.
Hi there,
Does anyone know a tutorial like this one but for the 971??
My brother-in-law wasn't using is so I'm thinking in tweaking it to see how it gets.
MaedaKeiji said:
Hi there,
Does anyone know a tutorial like this one but for the 971??
My brother-in-law wasn't using is so I'm thinking in tweaking it to see how it gets.
Click to expand...
Click to collapse
Hi, sorry i cant help you, it looks like the 971 is using a10 cpu, sôit can be different.
If you know what you are doing, u can try to backup your original firmware and test the solution i have provided from toxico in py post above. But there is no warranty it s going to work.
Any case, donnot forget google is your friend
Good luck
Unfornetly it seems google doens't like this tablet...
I'll see what I can do with some backups and all.
Thanks anyway!
I am writing this because I couldn't seem to find a guide to solve my issue of my Galaxy Nexus being completely bricked. It was literally dead, or so I thought. The first part of this guide will tell you how to recover from the following situation:
Before we begin, here are the names of the programs and files used:
Odin3
Android ADK
CF-Root-GGN_YAKJU_ICL53F-v5.1
Stock Galaxy Nexus ROM
OMAP
Situation 1:
The first situation is where your screen has gone completely black. You can't boot into anything and nothing is displayed on the screen. Your computer no longer recognises the device. It is literally a brick. If you are in this situation, please follow the solution 1 and 2 else skip to situation 2.
Solution to situation 1:
I was googling everywhere for a solution to this and it appeared that it was not a common problem and those who did face the problem simply returned their phone on warranty. It is now an old phone but I still like it (will be upgrading to nexus 5 in the next few weeks). I didn't want to waste such a good phone and just have it sit there so I researched.
My solution to this problem is omap. I would post a link but unfortunately I do not have the permissions (for the download link I will be uploading later).
Please note that I do not take any credit for any program used in this guide and I am simply putting together several other guides so that future users who have this problem can access them all in one place.
Here is the step by step guide:
1) Open OMAPFlash. Navigate to usb_drv_windows. *Right click on omap_winusb.inf and click install*.
2) Navigate to usb_drv_android. *Right click on android_winusb.inf and click install*.
*Note: On Windows 8 (8.1), you will have to allow all certificates to be installed.
3) Double click on the omap4460_tuna_hs_pro.bat and run it accordingly. You will have to disconnect the device and remove battery. Connect the device and then count to 5. Re-insert the battery.
4)Omap will now start doing its thing and you will be given situation 2.
Situation 2:
This situation is where you have a phone connected to a yellow exclamation mark which is connected to a computer. Mind my ASCII Art, but here is what it looks like: [] - - /_\ - - [ ]. You can't do anything with this either but ODIN (google it) will pick it up. This is a good thing. You won't be able to boot into recovery mode or download mode which makes it hard to flash a ROM to it or fastboot it. You will need CF-Root-GGN_YAKJU_ICL53F-v5.1 (Google it). Here is the step by step guide:
Solution To Situation 2
1) Open ODIN3. Select the CF-Root-GGN_YAKJU_ICL53F-v5.1 as the PDA file. If your phone is not being recognised (should say added! in the log), simply disconnect device, remove battery, reconnect device and then place battery back in and hold down the power + vol up + vol down buttons.
2) Press start. The log will start filling up and it should say DONE! You now have bootloader.
3) Now you will need to find the stock ROM for the galaxy nexus (google it). Now you will need to extract that the contents into your adb file (from the android sdk installation which hopefully you have,
4) Put your device into bootloader mode. Run the fastboot flash-all batch file that should be included with the custom ROM.
5) Your phone will now start doing stuff and constantly rebooting in and out of bootloader mode.
6) You should now have the stock ROM installed.
Again, I am sorry that I cannot post links but I do not have permissions due to lack of posts. I know this is an old phone but this guide may still be useful to someone. Also, feel free to ask any questions or point out any mistakes I have made.
no need that android adk. setup correctly adb & fastboot just enough. i think this type of threads already here..
* yeah.. but no sticky guide. maybe good to go. better make ' how to prevent gnex from bricks'
omap flash.exe ~
http://forum.xda-developers.com/galaxy-nexus/general/bricked-gnex-brought-to-life-t1760787
odin ~
http://forum.xda-developers.com/galaxy-nexus/general/guide-restore-to-stock-unbrick-galaxy-t2065470
I probably already know the answer to this but I want to make sure: can this procedure be applied to the Verizon Toro?
Update: Phone isn't responding to this fix... It was a long shot maybe in a week or two it'll turn on...
I'll write up a tutorial for us Toro kids... Thank you guys!
Sent from my VS980 4G using Tapatalk
Hi guys,
I hope i am in the right place...
I have an android system installed in my Mitsubishi, but the local importer of the system, has "locked" the system by removing the Google play app, file manager and all ability to make any changes.
Is there a way I can add back the Google play so i can add a few apps to the system? The system has a USB port.
FLY AUDIO MODEL G8023H19
Thanks,
goamir said:
Hi guys,
I hope i am in the right place...
I have an android system installed in my Mitsubishi, but the local importer of the system, has "locked" the system by removing the Google play app, file manager and all ability to make any changes.
Is there a way I can add back the Google play so i can add a few apps to the system? The system has a USB port.
FLY AUDIO MODEL G8023H19
Thanks,
Click to expand...
Click to collapse
no not really
without a file manager
I was going to say - put a file manager app on to the usb - I would have provided you with a file manager app
wait for usb files to show up and install app but
a file manager would be needed to show the USB and install an app manually anyway
I mod android and I have my own rom but I can't think of anyway other than....
having another type of app store on there
This unit has a full thread on 4pda.
http://4pda.ru/forum/index.php?showtopic=671390
You should find all your answers there. Since googling it only returns results in Russian I presume it is a unit only sold there.
Installing APK
Hi,
Did you manage to install an APK?? Or did you get any answers regarding this issue?
Just an idea because I don't have this in my car:
connect it to a laptop, and use "adb" tool to install the APK files you wish.
Question is, how would you root it after that, and whether converting apps into system apps would work in order to install play-services and play-store.
In order to fetch the APK files from a normal device, you can use my app :
https://play.google.com/store/apps/details?id=com.lb.app_manager
Can I reply here?
Sent from my MI 2S using Tapatalk
goamir said:
Hi guys,
I hope i am in the right place...
I have an android system installed in my Mitsubishi, but the local importer of the system, has "locked" the system by removing the Google play app, file manager and all ability to make any changes.
Is there a way I can add back the Google play so i can add a few apps to the system? The system has a USB port.
FLY AUDIO MODEL G8023H19
Thanks,
Click to expand...
Click to collapse
have you managed to do something with it?
alicenir said:
have you managed to do something with it?
Click to expand...
Click to collapse
Hello Goamir,
Does this android work properly with the 2016 mitsubishi outlander can you use your original gps antenna, rear & side view camera are you able to get your cars A/c settings etc on the screen? If not can anyone recommend a proper android system?
I managed to activate developer options
Today I managed to activate developer options in my car (Mitsubishi Outlander) by going to input devices -> Voice input, I played a bit with it, I set the default to English and downloaded offline recognition, afterwards I pressed the small question mark in the upper corner and there it tells you that you don't have google services, there's a button there that suggest to install it, I pressed it and later I noticed that I have developer options (not sure which step actually enabled it, If someone can repeat it step-by-step and tell it will be great).
Anyhow now i'm stuck again since I can't connect usb and push apk, I tried with male-male usb but it didn't worked.
If anyone got any idea please share.
Details I have on the device:
When you reboot it and long press the screen it takes you to fastboot mode, when you hold volume up in the steering wheel it takes you to recovery .
The model I have is Flyaudio G8508
jon
hi, did you find a solution for the flyaudio g8 in the outlander here in israel? i am looking to root or flash a rooted firmware
thanks so much
jon
Solution for Israel's flyaudio
We have a solution to unlock FlyAudio G8 for Mitsubishi and hyundai from Israel.
If you want to unlock contact with me by PM.
FlyAudio for Israel Hyundai and Mitsubishi v.2016-06-04.
Hello,
For Israel Hyundai and Mitsubishi.
Firmware includes :
Amaze filemanager v3.0.1
Waze v4.7.0.1
AC3 Video Player v3.0.0
Chrome Browser Google v51.0.2704.81
SWE Browser
SpotifyMusic v5.7.0.781
Nobex
1. Download firmware from: h**ps://ufile.io/ac836 ( download link expires on 13 October 2016 )
2. Copy the file to USB flash.
3. Restart Android and press Home + Back buttons together.
4. Do an auto update.
Do it on your own risk !
eNjOy.
not working on outlander. recovery mode don't see a rom file on usb flash
The same issue for me.
When try to load from USB i get message "Ensure the storage Device Have Package"
you can use this one(haven't tested it) - h**ps://uploadfiles.io/07b58
But keep in mind that it's quite old one.
Today I managed to fetch the latest fup update file, it seems like the vendor update utility fetch it from some dropbox account but I didn't managed to get the url just to get the downloaded file.
You can find it here - h**ps://ufile.io/1cf01 , you can follow 4pda guide on how to add apk files.
The same issue for me.
When try to load from USB i get message "Ensure the storage Device Have Package"
16th September 2016 03:15 PM
Click to expand...
Click to collapse
The unit is "Pickey" when it comes to the use of different DOK's
please make sure you format the DOK to FAT32 first
than if not working please try another DOK it should identify and work.
Unfortunately not working. Disk-On-Key formatted with different cluster sizes, tried use different flash devices - FLyAudio don't see the firmwares
try this 4pda.ru*forum*index.php?showtopic=671390&st=980
.
replace * by /
I am trying to contact someone from Russian forum for the solution they already have experience. Will update.
I saw today how tech entering the recovery mode. I think it was like that:
long press on power - after blink press home then touch on screen when it is green , then enter the code :1630
I will try to update today.
Any news?
Hi,
I got my system on my Mitsubishi updated - unfortunately i payed for it...
Still if I could help in this forum I will.
I can install any app and have full access to google play.
However some option are still missing.
e.g. when i connect my PC to the system it is not show at all.
i was thinking i could somehow create a full system backup (image) and then turn the backup to an update file.
If anyone can offer a way to enable the use option, that is that my system would appear on my pc i could try it.
I have developer option and usb debugging on via an app i downloaded.
If i can do it in any other way I can try.
Another thing i was thinking of is to create a full backup and later restore, from the recovery mode but there are only option for update in the recovery mode.
Is it possible to allow/add the restore/backup option ?
Nexus 7 (2013) multiple "Unfortunately..." after motherboard swap / image reflash
Hello all - I'm hoping someone can provide some assistance / suggestions...
A few months ago, my son's tablet went for a quick swim (dropped into the toilet ) Unfortunately, I wasn't at home (on a business trip) to immediately power it down and pull the battery. I'm not sure if it was turned off / back on / off again or what, but it was quickly put into a bag of rice to try and minimize the damage until I came home to review.
Inspection of the tablet confirmed it was dead - no response to either buttons or plugging in the charger. Found the ifixit how-to, and after obtaining some tools I popped the back case off to see what was what. Disassembly revealed an nice scorch mark on the underside of the motherboard, right where the main chip was, so it was pretty obvious what the failure was.
I decided that I'd give repairing it a go, and bought a replacement motherboard from ebay a couple of weeks ago. Swapping the board over was no problem, and I was happy to see that after letting it charge fully, it booted up and went into the 'Setup' routine.
However, this is where the problems started - as it was working through the setup (language / wifi / copy apps/data from other device etc) there were numerous "Unfortunately, xxx has stopped" messages. I kept 'ok'ing them, and the tablet made it to the point where it was starting to download the saved apps etc from the playstore before it rebooted.
When it powered back up, the 'Unfortunately" pop ups were worse than before, so after doing some searching I decided to try flash a factory image (razor-mob30x) , as per the link on the Nexus help forum. The flash seemed to work (no errors in fastboot mode, laptop was communicating with the tablet) but the pop ups were still as plentiful as before. I have tried the flash multiple times, even going back to lollipop, but with no real improvement. The last thing I tried tonight was to start the recommended flash process from step 1, re-downloading and installing all the required programs, but without success.
I'm not sure what else to try, as the factory image reflash should erase all the installed files.
My only thought is maybe trying to sideload the correct gapps / play services / etc in fastboot mode?
Any suggestions appreciated,
Roadie73
Update..
So, because I'm a glutton for punishment, I've been playing with the N7 again this evening...
Grabbed my old laptop, and went through the complete routine again - loading adb and fastboot onto the laptop, then the N7 factory image - and ended up with basically the same result - the tablet will look like the files have taken, but almost immediately after restarting and loading to the blue set up screen, the "Unfortunately..." messages start again.
I was able to get all the way through the set up, and have it copy and start to download the files off the tablet I was using previously, but the pop ups persisted, and it gets to a point where it is looking for a google play services update, and the process comes to a screeching halt.
I found another 'How To" and tried sideloading a rescue OTA update, which might be a little better, but the messages persist....
I'm almost wondering if it's worth reflashing the factory image back to whatever the N7 shipped with, and then trying updates from there, as it seems to be the play services / store / apps that is the issue.
The other strange thing is that when I sign in with my google account, it shows as a Nexus 7 2012, even though it's a 2013 - might the original software on the replacement motherboard have been corrupt?
Still trying...
Roadie73 said:
it shows as a Nexus 7 2012, even though it's a 2013 - might the original software on the replacement motherboard have been corrupt?
Click to expand...
Click to collapse
Interesting, please post the output of the 2 commands...
boot the Nexus in fastboot mode (when off press power+vol.dn)
connect it to your PC
on PC run:
fastboot getvar all
fastboot oem gpt-info
If you can, also attach logs...
download get-logs.zip to a FAT32 flash drive
connect the flash drive to your N7 with OTG adapter
download TWRP to your folder with fastboot and adb apps
boot the Nexus in fastboot mode (when off press power+vol.dn)
on PC run: fastboot boot twrp-3.1.0-0-flo.img
when TWRP is up, go: install/select-storage/usb-otg/get-logs.zip/flash
logs.tgz will be saved on the flash drive
attach logs.tgz here
It's simpler if you have TWRP already installed. You can also use get-logs.zip from internal storage.
Hi k23m,
I ran the two commands you suggested (getvar all and oem gpt-info) , and grabbed the outputs of both as screen captures and dumped them into a ppt file (which I can't seem to attach - there is no 'manage attachments' option I can see )
I installed TWRP on the N7, but was unsuccessful in creating / grabbing logs.tgz file - which might have to do with the USB connector on the N7 being flaky - if the otg cable wasn't held in exactly the right way it wouldn't recognize the flash drive.
If I can figure out how to add the attachment I will in a separate post, or I can always email it to you direct.
Thanks,
Roadie
Hello k23m,
Finally ad a couple of minutes to play with the N7 again - copied the get-logs file over to the tablet (that was behaving for once).
Unfortunately, despite copying the file off the N7 onto the laptop, a *.tgz file can't be attached. So I did the next best thing and copied the screen caps into an excel doc, which is one of the valid extension.
Please see the attached file - I had a look at the output, but it means nothing to me...
Thanks,
Roadie
added 'logs.tgz' file run previously - please rename from *.xls
Hopefully it might provide some insights into why the N7 is mis-behaving.
Thanks,
Roadie
The logs are OK.
Roadie73 said:
when I sign in with my google account, it shows as a Nexus 7 2012, even though it's a 2013
Click to expand...
Click to collapse
If you have followed the factory image installation instructions and you see the error messages before setup's initial sign in, then your hardware is faulty.
If it happens after sign in, then perhaps Google has corrupt account data ("it shows as a Nexus 7 2012"). Try a new account. Try a custom ROM with Gapps.
Ok, thanks.
Just tried a factory reflash as per the link, but fastbooted the individual files (boot / recovery / system / userdata / cache) separately as from what I have read using the 'flash-all' batch file has intermittent results.
Looked like the files loaded in successfully, but I'm still getting the "Unfortunately.." messages popping up on the initial sign in screen for set-up
So, based on k23m's assessment above, it sounds like it's a hardware problem
As far as I know the touch screen is ok (it's responsive in all areas, as far as I can tell). The daughterboard is not the original (that took a swim) - it was swapped out of another N7 when the charging port started to spread (and that tablet was issue free) So it looks as if the issue is in the replacement motherboard.
I guess I could try removing and reinstalling it, on the off chance it's a flaky connection somewhere.
I will also check to see if there was any sort of gaurentee / replacement policy for the replacement mobo, but it sounds like I'm out of luck
Any other suggestions / checks I can perform to see if I can narrow down where the issue lies?
Thank you,
Roadie