Hi, does anybody have any idea on how to root this? On their website they have an updater tool which says to get it into recovery you must push power and volume button only there is no volume button.. only physical button is a power button and then there is a reset hole in the back of the tablet. http://www.easypix.eu/smartpad750_en.html
I would like to at least root it and then see if there are any developers for this model.
Thanks.
I found a question from someone who has broken their same model tablet which was rooted, so it is possible.
You can get the proper windows drivers and connect to it through ADB. Using this method you can push clockwork mod touch, and the touch interface should work fine. You might have to use ADB terminals for keypresses as it starts though, I'm not sure how you would boot into recovery without a rom. But once in a rom, you can always select the reboot into recovery option.
do you have any guide for this, Im more just interesting in rooting it to start with. I think I figured out how to get it into some sort of recovery mode but windows wont let me install the recovery mode drivers so I cant do anything
bump
I just rooted it with unlockroot.com , It works for any tablet with the rockchip 2906 (Rk29).
Kevinjs said:
do you have any guide for this, Im more just interesting in rooting it to start with. I think I figured out how to get it into some sort of recovery mode but windows wont let me install the recovery mode drivers so I cant do anything
Click to expand...
Click to collapse
Hi there. Do you mind sharing the info how to get it into some sort of recovery mode . And with the tool from that web site. Was it difficult to do?
ADB does not find Easypix Smartpad EP750
Kevinjs said:
I just rooted it with unlockroot.com , It works for any tablet with the rockchip 2906 (Rk29).
Click to expand...
Click to collapse
It seems impossible for me, I installed the driver, now in the Windows device-manager you can find a "Class for rockusb devices" and there a "RK29 Device" but adb seems not fo find it.
While I see the device in my Windows device manager I pushed the Root-button from the unlockroot.com - tool, but after it tried to check via ADB there comes a popup "not detected any device ..."
Checking it with Ubuntu-Linux with the lsusb - command, this tablet has NO NAME, I can find the VendorID and the ModelID but after that, there is NOTHING , all other USB-Devices do have a name after its IDs, and trying to check via Davlik Debugging Monitor (ddms) you have to chose the name of your device,
but it is impossible to me, because I cannot chose NOTHING to use NOTHING with ADB ... has anybody an idea, how it may work, or has anybody a working ROM on his Easypix Smartpad EP750 which has root or at least a name ?
Maybe anybody has a working udev - entry for Linux ... pls post it here !!!
Under Windows I am able to flash the device with its own flashing-tool (RKBatchTool) but since now I did not find any ROM which I can flash instead of the original ROM - the latest I downloaded from Easypix-WebSite = 750_20120621 with Android 4.04 but no root-access,
I tried to flash a CM9, but the RKBatchTool told, that was no possible ROM for that device .....
ProJerem said:
It seems impossible for me, I installed the driver, now in the Windows device-manager you can find a "Class for rockusb devices" and there a "RK29 Device" but adb seems not fo find it.
While I see the device in my Windows device manager I pushed the Root-button from the unlockroot.com - tool, but after it tried to check via ADB there comes a popup "not detected any device ..."
Checking it with Ubuntu-Linux with the lsusb - command, this tablet has NO NAME, I can find the VendorID and the ModelID but after that, there is NOTHING , all other USB-Devices do have a name after its IDs, and trying to check via Davlik Debugging Monitor (ddms) you have to chose the name of your device,
but it is impossible to me, because I cannot chose NOTHING to use NOTHING with ADB ... has anybody an idea, how it may work, or has anybody a working ROM on his Easypix Smartpad EP750 which has root or at least a name ?
Maybe anybody has a working udev - entry for Linux ... pls post it here !!!
Under Windows I am able to flash the device with its own flashing-tool (RKBatchTool) but since now I did not find any ROM which I can flash instead of the original ROM - the latest I downloaded from Easypix-WebSite = 750_20120621 with Android 4.04 but no root-access,
I tried to flash a CM9, but the RKBatchTool told, that was no possible ROM for that device .....
Click to expand...
Click to collapse
How did u manage to flash through windows? i have one of these tablets that was handed out with some ****ty program that has been installed by a medical company to give out to patients , with a load of information about certain medical conditions, a load of ****e basically, i want to flash the original rom in order to wipe this crap program from it to allow me to use it as a normal tab . I managed to install the driver but cannot get it into any form of recovery mode in order for the device to show in the flashing program . Any help appreciated
hi i was wondering if you could let us no if it worked for you as i have 3 of them with pattern key lock and its saying im putting in the wrong email address which is the correct 1 and i can find any information to help me remove them.
First let's get the warnings out of the way:
This is a dangerous tool. It can render your device permanently unusable.
If you use it, your warranty will likely be void.
You accept all responsibility for the consequences.
This is not an official ZTE unlock tool. The official ZTE unlock tool is in another thread.
Acknowledgments
Special thanks to @rombdeta for providing the OEM programmer binary. This would not be possible without his help.
What is tuliptool?
This tool allows you to:
Check status of your boot loader
Unlock your boot loader
Lock your boot loader
Install a custom recovery
Install a custom boot image
NOTE WELL
The first rule of intelligent tinkering is to save all the parts.
Always backup your partitions before writing new contents, so that you can get back to where you started.
Never write both boot and recovery in one session. Always make sure that you can boot into the other partition in case something fails.
Locking and unlocking will erase all user data. Make sure you backup first!
The zip includes:
tuliptool for Linux
tuliptool for Win64
tuliptool for Win32
tuliptool for MacOS
Preparation
1. Extract the package.
You will find the binary files listed above. Note: This is a command line utility, so you must open a command prompt to run it.
2a. Setup for Linux
Create a file named /etc/udev/rules.d/99-qcom.rules with this content exactly as shown:
SUBSYSTEM=="usb", ATTRS{idVendor}=="05c6", GROUP="plugdev"
Ensure your login user is in the plugdev group.
2b. Setup for Win32/Win64
Download zadig.
Connect your device in EDL mode (see below).
Windows will want to install the Qualcomm USB driver. We won't be using it so you can cancel if you wish, but it won't hurt anything.
Run zadig. Find device 05c6:9008 and install the WinUSB driver for it.
Disconnect the device.
2c. Setup for MacOS
No setup should be necessary.
3. Download boot and/or recovery files to flash.
You will find these in other threads in this section.
Connecting in EDL mode
Via adb
This should work for all models, but you need adb access.
adb reboot edl
Via key combo
If you have a US model device (or the aboot from a US model device) you may use the key combo:
Power off and unplug the device.
Hold both volume buttons.
Plug device into your PC.
Wait about 3 seconds and release the buttons.
Note: There will be no feedback on the device -- no lights, no vibration, nothing. The only way to verify that the device is in EDL mode is that device 05c6:9008 is visible on the PC.
Usage: (un)locking
After some testing, it appears that the Axon 7 Mini is not locked in any way. In other words, unlocking seems to be completely unnecessary. This section is mostly provided for completeness.
tuliptool lock status
tuliptool lock unlock
tuliptool lock lock
Usage: reading boot/recovery
Note command line options have changed
tuliptool read boot
tuliptool read recovery
Usage: writing boot/recovery
Note command line options have changed
tuliptool write boot <filename>/I]
tuliptool write recovery <filename>
So, for example, to write a TWRP image, run:
tuliptool write recovery tulip-twrp-7.1-r1.img.
Multiple operations
This is a "one shot" tool. After performing an operation, it will reset the device with a 5 second countdown. If you wish do perform multiple operations (eg. backup, unlock, flash), simply hold down the volume buttons while the device resets and it should go back to EDL mode.
Download
tuliptool.zip
md5=58f34850005510b51a832d27a6bce607
Common problems
Device not found: first enter EDL mode, then run the tool.
Device is visible in device manager or lspci but cannot be found by the tool: connect directly to the PC, not through a hub.
Windows says bad file descriptor: the WinUSB driver is not installed.
Linux says permission denied: your login user is not in the plugdev group.
Why call it tuliptool?
Tulip is the device "code name" for the Axon 7 Mini (at least the US version).
first! it's nice to see someone working on the lesser-known devices for once, thanks love!
okay so on that note everything goes perfectly, right up until i try to actually run the tool lol. installing the driver through Zadig does fine, and from everything i can tell, the PC recognizes it. i mean, it's in EDL and everything. what's going wrong? running the tuliptool-win64.exe just opens and closes instantly, and opening a command prompt in the directory just tells me that tuliptool is not a valid command/operation blah blah blah. it's probably something simple but i'm kind of trying to get all over this so :good:
Perhaps try running it as administrator? I'm heading home from work and then I'll be taking a shot at this myself.
I just tried on a Windows 10 virtual machine and it works perfectly.
This is a commandline program so you open a command prompt and type eg:
tuliptool-win64.exe lock status
Meme Queen said:
first! it's nice to see someone working on the lesser-known devices for once, thanks love!
okay so on that note everything goes perfectly, right up until i try to actually run the tool lol. installing the driver through Zadig does fine, and from everything i can tell, the PC recognizes it. i mean, it's in EDL and everything. what's going wrong? running the tuliptool-win64.exe just opens and closes instantly, and opening a command prompt in the directory just tells me that tuliptool is not a valid command/operation blah blah blah. it's probably something simple but i'm kind of trying to get all over this so :good:
Click to expand...
Click to collapse
tdm said:
I just tried on a Windows 10 virtual machine and it works perfectly.
This is a commandline program so you open a command prompt and type eg:
tuliptool-win64.exe lock status
Click to expand...
Click to collapse
so it's gone past that, but now it fails to unlock with an unknown error. checking unlock status after returns "Failed to send programmer: failed to read packet". i have to unplug it and go back into EDL mode, and when i check the lock status, it says unlocked and not tampered. when i try to go ahead with flashing TWRP, it crashes with this:
Sending programmer...Connecting to programmer...log: [email protected] [email protected]
log: [email protected] [email protected]
log: Finished sector address 0
log: Finished sector address 0
log: Finished sector address 0
Writing recovery ...
terminate called after throwing an instance of 'std::runtime_error'
what(): No error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
I guess im stuck waiting for the update.zip because Zadig is refusing to install drivers. no matter what i do it will not install drivers. it keeps telling me "Remote Source Not Allocated: Driver install Aborted"
Hmm, looks like something strange is going on there. I'll take a look tomorrow.
Meme Queen said:
so it's gone past that, but now it fails to unlock with an unknown error. checking unlock status after returns "Failed to send programmer: failed to read packet". i have to unplug it and go back into EDL mode, and when i check the lock status, it says unlocked and not tampered. when i try to go ahead with flashing TWRP, it crashes with this:
Sending programmer...Connecting to programmer...log: [email protected] [email protected]
log: [email protected] [email protected]
log: Finished sector address 0
log: Finished sector address 0
log: Finished sector address 0
Writing recovery ...
terminate called after throwing an instance of 'std::runtime_error'
what(): No error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Click to expand...
Click to collapse
tdm said:
Hmm, looks like something strange is going on there. I'll take a look tomorrow.
Click to expand...
Click to collapse
thanks! if there's any information you want me to provide, just let me know.
I cannot get my device to boot into EDL mode, everytime I try it gets stuck on the splash screen. Can anyone help?
pxzei said:
I cannot get my device to boot into EDL mode, everytime I try it gets stuck on the splash screen. Can anyone help?
Click to expand...
Click to collapse
Yeah, try pressing the power button for 10 seconds, until the display turns off, hold down VOL + and enter recovery "power down" and try to enter edl again
Ok. Now ive retraced my steps and found that letting the qualcomm drivers install will not allow the WinUSB drivers to install in Windows 7. Once I told Windows update to not install the qualcomm drivers Zadig was able to install drivers successfully. Now that the drivers are installed, Device is in EDL (im assuming this because screen is black but my computer is recognizing the device), I run the Tuliptool and it keeps telling me "Device Not Detected" . I cant seem to get it to find the device but i can see it in Device Manager just fine. And it shows the WinUSB drivers are installed correctly, any insight on to what I may be doing wrong?
There won't be any lights or other indication that the phone is on when it's in EDL mode. But you should see the device in device manager, as USB id=05c6:9008. I don't normally run windows so I can't give detailed steps to find that.
You may need to have admin privileges to talk to USB devices, I'm not sure.
MrWhite0429 said:
Ok. Now ive retraced my steps and found that letting the qualcomm drivers install will not allow the WinUSB drivers to install in Windows 7. Once I told Windows update to not install the qualcomm drivers Zadig was able to install drivers successfully. Now that the drivers are installed, Device is in EDL (im assuming this because screen is black but my computer is recognizing the device), I run the Tuliptool and it keeps telling me "Device Not Detected" . I cant seem to get it to find the device but i can see it in Device Manager just fine. And it shows the WinUSB drivers are installed correctly, any insight on to what I may be doing wrong?
Click to expand...
Click to collapse
tdm said:
There won't be any lights or other indication that the phone is on when it's in EDL mode. But you should see the device in device manager, as USB id=05c6:9008. I don't normally run windows so I can't give detailed steps to find that.
You may need to have admin privileges to talk to USB devices, I'm not sure.
Click to expand...
Click to collapse
Device Shows connected and drivers installed under device manager.
Command prompt is being run as so:
Start --> type cmd ---> Right click on Command prompt ---> Run as Administrator
cd C:\users\admin\desktop\tuliptool
C:\users\admin\desktop\tuliptool> tuliptool-win64.exe lock status
Device Not Detected
---------- Post added at 03:59 AM ---------- Previous post was at 03:38 AM ----------
UPDATE:
I found that I had to use a USB 3.0 hub in order to get the phone to be detected.
Once detected I ran commands as followed.
tuliptool-win64.exe lock unlock
(The unlocking procedure said it failed, phone bootlooped three times, then it showed as unlocked when I ran the Lock status command)
tuliptool-win64.exe read boot
(This created the backup-boot.bin file in the directory)
Tuliptool-win64.exe read recovery
(This created a backup-recovery file in the directory)
tuliptool-win64.exe write boot
Its at this point here I get a Runtime Error as well. The entire process comes to a halt.
Thsnks, tried that, but no luck. It's still stuck on the splash screen.
Update: The device is running B09 7.1.1, The charger seems to be ZTE authentic. Single sim variant. If you need more info, let me know.
rombdeta said:
Yeah, try pressing the power button for 10 seconds, until the display turns off, hold down VOL + and enter recovery "power down" and try to enter edl again
Click to expand...
Click to collapse
tdm said:
This is not an official ZTE unlock tool. ZTE will likely be providing an official boot loader unlock in the coming few days. You should wait for that if you have any reservations about modifying your device.
[/B][/COLOR]
Click to expand...
Click to collapse
Awesome you got the tool out, I think I am going to wait for the 'Official' tool so if I ever need to send it in for repair in the next 2 years I can say 'well I used your tool' lol
Can't wait to see the roms @tdm, keep it up and I think the mini is going to get a lot more interesting.
I'd like to get a bloat removed(if any) and more lightweight faster rom on mine, maybe try the latest cyanogenmod or w/e they call it now and AOKP, etc.
New roms without MiFavor would be awesome too and ones that improve performance!
ZTE
@tdm, do you think zte will also be giving the official boot loader unlock soon? If not I will use yours that looks solid, but just thought I would ask first.
CRAFTER0302002 said:
@tdm, do you think zte will also be giving the official boot loader unlock soon? If not I will use yours that looks solid, but just thought I would ask first.
Click to expand...
Click to collapse
First post:
"This is not an official ZTE unlock tool. ZTE will likely be providing an official boot loader unlock in the coming few days. You should wait for that if you have any reservations about modifying your device."
Okay I've uploaded a new version of the tool with better error handling and better error messages (particularly for the Win64 version). I successfully wrote TWRP using the Win64 version. Please check the OP for the new link and download it again.
@Meme Queen and @MrWhite0429 please try again. I think the problem was that you didn't copy tulip-twrp-7.1.1.img to recovery.bin.
I can modify the tool to take a filename as a parameter if that helps with the confusion.
Edit: Also fixed a typo in the OP which had the wrong filename in the example. This may have been the source of the confusion.
tdm said:
Okay I've uploaded a new version of the tool with better error handling and better error messages (particularly for the Win64 version). I successfully wrote TWRP using the Win64 version. Please check the OP for the new link and download it again.
@Meme Queen and @MrWhite0429 please try again. I think the problem was that you didn't copy tulip-twrp-7.1.1.img to recovery.bin.
I can modify the tool to take a filename as a parameter if that helps with the confusion.
Edit: Also fixed a typo in the OP which had the wrong filename in the example. This may have been the source of the confusion.
Click to expand...
Click to collapse
as in rename to recovery.bin?
Yes, that.
MrWhite0429 said:
as in rename to recovery.bin?
Click to expand...
Click to collapse
hello, i am in a bootloop with my oneplus 6. wiped everything.
since then i tried using the msmdownload tool, but it's not recognizing the phone.
in the device manager the phone is currently being recognized under "kedacom usb device" as android bootloader interface. I tried doing an update to the drive and installing a quallcom drive, but always get an error message "The folder you specified doesn't contain a compatible software driver for your device. if the folder contains a driver, make sure it is designed to work with your computer". i downloaded a few windows program to force installation with no success. tried signing the .inf file of quallcom driver - same errorwhen i try again. when i write in cmd 'fastboot oem unlock' - it says that the device is already unlocked. when i try the command 'fastboot twrp.img' or fastboot boot it also fails. i even downloaded tool-all-in-one - doesn't help. when im making an uninstall of the android bootloader interface, after connecting the phone again - it automatically installs this driver again, even though i marked in the settings not to do that. all i get is a bootloader screen, nothing else.
p.s. new here so sorry if the thread is in the wrong place or something.
Hi All!
I have a Honda Connect audio system (39100-TB9-G61-M1)
After a navigation issue I updated the firmware on the device. The device updated correctly and rebooted. But, never started again.
I can flash the two file from usb after the device starting (ADA_usbdl_V0C.091.01_TV0X_04.zip and ADA_usbdl_V0E094001123_sec_14ada.zip)
But I can't flashing a file (AUD31CF.bin). The navi wrote: "There was a problem during the update. Please switch off the vehicle then restart to retry."
I restarted many times but nothings happened. the navi wont flash the file (AUD31CF.bin) and won't start.
What can I do whit this navi system?
Can somebody help me to recovering this system?
Rocco said:
Hi All!
I have a Honda Connect audio system (39100-TB9-G61-M1)
After a navigation issue I updated the firmware on the device. The device updated correctly and rebooted. But, never started again.
I can flash the two file from usb after the device starting (ADA_usbdl_V0C.091.01_TV0X_04.zip and ADA_usbdl_V0E094001123_sec_14ada.zip)
But I can't flashing a file (AUD31CF.bin). The navi wrote: "There was a problem during the update. Please switch off the vehicle then restart to retry."
I restarted many times but nothings happened. the navi wont flash the file (AUD31CF.bin) and won't start.
What can I do whit this navi system?
Can somebody help me to recovering this system?
Click to expand...
Click to collapse
!!!Update more information!!!!
I have a Fujistu FT0056A device. This device its a sat-nav in a Honda Civic.
The device is frozen. After a usb firmware flashing won't startet. Its in boot-loop. I tryed many solutions, but not working.
http://oi68.tinypic.com/w9jjvt.jpg
First time I tried to flashing from usb stick. I have thre original Honda flash file to tis device:
- For SH USB1 - AUD31CF.bin - I can't extract the bin file. Maybe this contain the boot and recovery images. - I can't flash with via usb stick. Its a error message... Maybe
this bin file contain the boot and the recovery images.
- For tegra EC/NC USB2 - ADA_usbdl_VL0.FFF.04_EXT_HFT_param02.zip - Flash zip file loaded up correctly to the device via usb stick.
- For Tegra USB3 - ADA_usbdl_V10096001123_sec_14ada.zip - Flash zip file loaded up correctly to the device via usb stick. This zip file contain a
"ADA_usbdl_10.096.00.1123.enc" file. Can't decrypt or extract. Its a password protected file. I not know whats the password...
I tried to downgrade, with older and upgrade with newer wersions, but not working....
Now I tried flashing via OTG USB on the USB-B system port
I can't find any driver to the device. I found many driver (apx ; nvidia shield ; toradex_usbpcdriver_32_64 ; universal naked drivers ; etc.) but the ****usb.inf file not
contains any record of this device, what they call it:
USB_Install, USB\VID_0955&PID_7102
USB_Install, USB\VID_0955&PID_7102&REV_0232
After the inf editing and With forced install, i can connecting the driver to the device with many "name":
NVIDIA USB Boot-recovery driver for Mobile devices"
NVIDIA Android Fastboot Device
NVIDIA Android Composite Device
Android Debug Bridge Interface
etc....
I found thre diferent driver dll version too:
WdfCoInstaller01009.dll
winusbcoinstaller2.dll
WUDFUpdate_01009.dll
-------------------------
WdfCoInstaller01009.dll
winusbcoinstaller2.dll
WUDFUpdate_01007.dll
------------------------
and
WUDFUpdate_01009.dll in another file size....
the device not aswered to the fastboot.
Fastboot devices
Cant find any device
Only the xiaomflash.exe can read a a devise serial:
015e8b67e833fc08
but, cant flash the device....
the virtualbox can read the device informations:
http://oi65.tinypic.com/jsjcys.jpg
After adding the usb and post settings in the virtualbox, i tried flashing the board wint ubuntu.
same as with windows. The device its in the ubuntu usb device list:
http://oi64.tinypic.com/2h2kqhg.jpg
but, if i like to flash the device, nothings happened. The flasher wait for the device...
http://oi63.tinypic.com/zwi52s.jpg
So.....
how can I find a solution for flashing this board?
Its any not public device driver to this device?
How can I flash the SH AUD31.bin?
Becouse i think the Tegra files loaded up correctly via USB stick. Now i must to give a "fastboot -w" command to the device, and then can booting correctly. I tried with
"fastboot -i 0x0955 -w command too". not working.
I think I must flashing the bin file with a eeprom félasher. I have eprom flasher, but the flasher can't flash this eeprom. find any eeprom flasher under 600$ for this
"25C512A" eeprom.
So.....
How can i unbrick tis device?
Any solution?
Thanks for the reply
Kind REgads,
Rocco
Rocco said:
!!!Update more information!!!!
I have a Fujistu FT0056A device. This device its a sat-nav in a Honda Civic.
The device is frozen. After a usb firmware flashing won't startet. Its in boot-loop. I tryed many solutions, but not working.
http://oi68.tinypic.com/w9jjvt.jpg
First time I tried to flashing from usb stick. I have thre original Honda flash file to tis device:
- For SH USB1 - AUD31CF.bin - I can't extract the bin file. Maybe this contain the boot and recovery images. - I can't flash with via usb stick. Its a error message... Maybe
this bin file contain the boot and the recovery images.
- For tegra EC/NC USB2 - ADA_usbdl_VL0.FFF.04_EXT_HFT_param02.zip - Flash zip file loaded up correctly to the device via usb stick.
- For Tegra USB3 - ADA_usbdl_V10096001123_sec_14ada.zip - Flash zip file loaded up correctly to the device via usb stick. This zip file contain a
"ADA_usbdl_10.096.00.1123.enc" file. Can't decrypt or extract. Its a password protected file. I not know whats the password...
I tried to downgrade, with older and upgrade with newer wersions, but not working....
Now I tried flashing via OTG USB on the USB-B system port
I can't find any driver to the device. I found many driver (apx ; nvidia shield ; toradex_usbpcdriver_32_64 ; universal naked drivers ; etc.) but the ****usb.inf file not
contains any record of this device, what they call it:
USB_Install, USB\VID_0955&PID_7102
USB_Install, USB\VID_0955&PID_7102&REV_0232
After the inf editing and With forced install, i can connecting the driver to the device with many "name":
NVIDIA USB Boot-recovery driver for Mobile devices"
NVIDIA Android Fastboot Device
NVIDIA Android Composite Device
Android Debug Bridge Interface
etc....
I found thre diferent driver dll version too:
WdfCoInstaller01009.dll
winusbcoinstaller2.dll
WUDFUpdate_01009.dll
-------------------------
WdfCoInstaller01009.dll
winusbcoinstaller2.dll
WUDFUpdate_01007.dll
------------------------
and
WUDFUpdate_01009.dll in another file size....
the device not aswered to the fastboot.
Fastboot devices
Cant find any device
Only the xiaomflash.exe can read a a devise serial:
015e8b67e833fc08
but, cant flash the device....
the virtualbox can read the device informations:
http://oi65.tinypic.com/jsjcys.jpg
After adding the usb and post settings in the virtualbox, i tried flashing the board wint ubuntu.
same as with windows. The device its in the ubuntu usb device list:
http://oi64.tinypic.com/2h2kqhg.jpg
but, if i like to flash the device, nothings happened. The flasher wait for the device...
http://oi63.tinypic.com/zwi52s.jpg
So.....
how can I find a solution for flashing this board?
Its any not public device driver to this device?
How can I flash the SH AUD31.bin?
Becouse i think the Tegra files loaded up correctly via USB stick. Now i must to give a "fastboot -w" command to the device, and then can booting correctly. I tried with
"fastboot -i 0x0955 -w command too". not working.
I think I must flashing the bin file with a eeprom félasher. I have eprom flasher, but the flasher can't flash this eeprom. find any eeprom flasher under 600$ for this
"25C512A" eeprom.
So.....
How can i unbrick tis device?
Any solution?
Thanks for the reply
Kind REgads,
Rocco
Click to expand...
Click to collapse
Hi there...
Did you ever manage to solve your issue ?
just wondering ^^ (I have a device that has the same issue, and trying to recover it see if I can hack it later... )
Thanks.