Develop Bugs

Storex Ezee'TAB901 root JB 4.1.1

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!

[Guide]Unlocking Android Protection Code Without Reset Or Root

THIS METHOD WILL NOT WORK IN NEWER VERSIONS OF ANDROID
Click to expand...
Click to collapse
1.Please note that by using this method you can unlock phone without losing any data.
2.This must not be used for any illegal purpose.
3.I do not hold any responsibility of any phones bricked using this method(though it is tested)
.
.
Requirements
Links
1.Download Android Multi Tools- Click Here
2.Universal Adb Drivers - Click Here
Click to expand...
Click to collapse
.
.
Now lets begin
1.First unpack the tool.
2.Then install the adb driver.
3.Turn on your phone and connect it to pc via data cable.
4.Now press 1 to check if your device is connected properly.
5.Now if you have pin,password or face-lock please press 2.
6.If you have pattern lock then press 3.
7.Device will reboot and it will be unlocked.
8.If it still shows pattern,pin or password enter window simply simply give any to unlock.
Click to expand...
Click to collapse
.
.
Other action that can be done by this program are below
.
Choice detail
1.check device for check connection of device to pc.
4.reset gmail for reset gmail login after try many time wrong unlock
5.wipe data for reset all data to factory setting.
6.reboot for reboot device to normal mode or exit from adb shell.
7.check device on fastboot mode for check connection of device to on fastboot mode.
8.wipe data / cache on fastboot mode for erase user datat and cache on fastboot mode to resolve freeze,stuk on boot logo or slow down device. That is often found in the cpu spreadtrum sc6280/sc8810.
9.exit fastboot mode for reboot your pc or exit fastboot.
0.go to command promt for entering dos promt.you can use command in this soft folder and can return to the main program by type exit
s.software info for info cpu inside,firmware version and etc.
H.hardware info for determine the ic number of gsensor,touch screen,camera,wifi and more
Click to expand...
Click to collapse
.
.
.
thanks for reading this post
Written By
Pranto Roy
XDA
Click to expand...
Click to collapse

Links
1.download android multi tools- http://d-h.st/rCh
2. universal adb drivers - http://adbdriver.com/upload/AdbDriverInstaller.exe

prantoroy said:
Links
1.download android multi tools-
2. universal adb drivers -
Click to expand...
Click to collapse
thanks
my younger bro face this problem yesterday and today i got ans
will try and update

Jpjayesh said:
thanks
my younger bro face this problem yesterday and today i got ans
will try and update
Click to expand...
Click to collapse
Sure Please Update

Thnks
Sent from my HTC One X using xda app-developers app

chrisb906 said:
Thnks
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
hmm. . . gud
share it!!

Unfortunately, I was not at my work machine.
Pranto Roy said:
1.Please note that by using this method you can unlock phone without losing any data.
2.This must not be used for any illegal purpose.
3.I do not hold any responsibility of any phones bricked using this method(though it is tested)
.
.
.
.
.
.
.
.
.
Click to expand...
Click to collapse
Hello to everyone!
This description is very good, but unfortunately I can not help of mind. The Freetab 2099 tablet is set, the OSD, I forgot, offered through the recovery gmail account, but the machine is not connected to the Internet, and it can not be solved. The Windows XP felimeri the machine, but only shows an empty folder adb driver installation, and Total Commander, however does not see downloaded from the manufacturer's website drivers installed, but not working this solution, a multitool can not find device. Maybe a factory reset would solve the matter but has not yet been described find or install a new rom that is. Img extension of the manufacturer's side, but I do not know bekepcsolni debug mode on the machine, it does not allow the zárképrnyőről to move on.
If anyone knows a solution to my problem, thanks in advance.
Hello, Valer

Tiszaba said:
Hello to everyone!
This description is very good, but unfortunately I can not help of mind. The Freetab 2099 tablet is set, the OSD, I forgot, offered through the recovery gmail account, but the machine is not connected to the Internet, and it can not be solved. The Windows XP felimeri the machine, but only shows an empty folder adb driver installation, and Total Commander, however does not see downloaded from the manufacturer's website drivers installed, but not working this solution, a multitool can not find device. Maybe a factory reset would solve the matter but has not yet been described find or install a new rom that is. Img extension of the manufacturer's side, but I do not know bekepcsolni debug mode on the machine, it does not allow the zárképrnyőről to move on.
If anyone knows a solution to my problem, thanks in advance.
Hello, Valer
Click to expand...
Click to collapse
Seriously Man.
Didn't Understood A Word.
Give Details and Only Ask The Main Question

Pranto Roy said:
Seriously Man.
Didn't Understood A Word.
Give Details and Only Ask The Main Question
Click to expand...
Click to collapse
The "Freetab 2099" table host forgot the password and can not login. The Android Multi Tools does not recognize your computer, Windows can only see empty folders. How to factory reset the computer to do?

Tiszaba said:
The "Freetab 2099" table host forgot the password and can not login. The Android Multi Tools does not recognize your computer, Windows can only see empty folders. How to factory reset the computer to do?
Click to expand...
Click to collapse
If The Computer Doesn't Recognize It Install Drivers.
Without Identifying Its Not Possible.

Pranto Roy said:
If The Computer Doesn't Recognize It Install Drivers.
Without Identifying Its Not Possible.
Click to expand...
Click to collapse
Hello!
The Adb Driver Installer does not recognize the machine, so I installed the manufacturer's website for official drivers. Only one folder is empty, or whatever it may be copied, "The device is not responding or is not connected."

Tiszaba said:
Hello!
The Adb Driver Installer does not recognize the machine, so I installed the manufacturer's website for official drivers. Only one folder is empty, or whatever it may be copied, "The device is not responding or is not connected."
Click to expand...
Click to collapse
I'll Get The Drivers

ts, i tried to used the tool the the .exe recognize my device it shows the serial number but when i tried to unlock using otion 2 or 3 it doesn't work i got skk mobile a1 device it has somewhat like ios GUI

ghepier said:
ts, i tried to used the tool the the .exe recognize my device it shows the serial number but when i tried to unlock using otion 2 or 3 it doesn't work i got skk mobile a1 device it has somewhat like ios GUI
Click to expand...
Click to collapse
If It Recognized Ur Device It Will Work
And Please Add Details
Eg. What Error Message etc.

Hi there, i have tried to use the following software but it doesnt work
so basically I have a samsung G3 i9300T and I know the pattern code but i still want to try out.
firstly when i ran the Multi-tool, it doesn't recongized my phone. So i realized i have to turn on USB debugging in order to let the software to detect my phone.
So i have turned the usb debug mode on and it finally picks up my phone.
Press 1 and it has my serial number, good, good. Then I go to option 3 as you mentioned in order to unlock pattern lock.
It reboots, and the pattern lock is still sitting on screen. So i tried to swipe anywhere on the pattern lock but it doesnt allow me to go further unless i input the right code.
Now i am wondering what could went wrong?

Fossil_Sioux said:
Hi there, i have tried to use the following software but it doesnt work
so basically I have a samsung G3 i9300T and I know the pattern code but i still want to try out.
firstly when i ran the Multi-tool, it doesn't recongized my phone. So i realized i have to turn on USB debugging in order to let the software to detect my phone.
So i have turned the usb debug mode on and it finally picks up my phone.
Press 1 and it has my serial number, good, good. Then I go to option 3 as you mentioned in order to unlock pattern lock.
It reboots, and the pattern lock is still sitting on screen. So i tried to swipe anywhere on the pattern lock but it doesnt allow me to go further unless i input the right code.
Now i am wondering what could went wrong?
Click to expand...
Click to collapse
That Is The Exact Process
I'll test it On S3

Didn't work on Motorola XT901
Thanks for supplying such a tool, unfortunately I tried it and had the same result has Fossil_Sioux on a Motorola XT901. Phone is recognized and when I select option 2 it reboots, but the lock screen is still displayed. I enter in any random pin and it just prompts me to try again. Any suggestions?

thanks
thanks for your time in posting this information because i find it very helpful

Nice
Nice thread...thnx man.

Devill007 said:
Nice thread...thnx man.
Click to expand...
Click to collapse
Thanks

Urgent Help Needed!

Hello....I bricked my I927 when I accidently formatted my efs partition when using EFS professional .....my phone boots in download mode.....but only boots till samsung logo screen.....I tried various things like installing stock GB and ICS through odin and installing custom firmware but phone boots onle till samsung logo and then lights up with sone stange colored thin lines and screen goes off.....In TRWP I get a "unable to mount preload" error whenever I try to install somethiing.....I suspect that the EFS partiton is corrupted and needs to be repartioned....I had backupped the efs folder when my phone was working before.....its in a tar format.....I read somwhere that someone made a recovery.zip out of his backedup EFS.IMG and flashed it with CWM solved his problems which were exactly similar to mine.....can somebody on the forum make a recovery.zip for I927 with update binary and script so that I can add the backedup EFS image to it and flash it with CWM? Please.....this would also help many others who are facing similar issues.....and also what do I do regarding the "unable to mount preload" error? I need to repartition and tried to install hemdall.....but get the common .dll error even after following all the instructions and installing C++ 2010.....

Hi, k one thing after the other.
Do you have repartitioned anything?
Do you have adb in place and does adb works when in TWRP?
The easiest thing would be to connect by adb then mount /efs and then restore the efs backup. The good is that you will have a good chance to recover your device. Maybe you need to reformat /efs but that depends.
Which timezone do you live? Maybe a Teamviewer session would be helpful?
.

Thank you for your reply sir...
THANKS FOR THE REPLY SIR....YES I WAS ABLE TO GO INTO CWM RECOVERY AND CONNECT THE PHONE WITH MINIMAL ADB FASTBOOT.....AND AFTER SPENDING ALMOST 2 DAYS CONTINUOUSLY TRYING TO FIND THE PROBLEM USING GOOGLE, I TRIED DIFFERENT COMMANDS ON ADB TO GET EFS BACK OJ THE PHONE....BUT WITH NO SUCCESS...... MY EFS BACKUP IS IN TAR FORMAT......IT WAS MADE USING GALAXYSIMUNLOCK BY SPOCKY.....I LATER TYPED IN 'ADB MESG'.....OR SOMETHING SIMILAR TO THAT COMMAND, AND FOUND OUT THAT ALL THE PARTITIONS ON mmcblk0 were mangled up with strange letters.....for eg, p1, p2, p3 and so on had strange characters written next to them.....SO I TRIED TO RE-PARTITION THE WHOLE THING WITH SDPARTED......AND IT RE-PARTIONED THE SYSTEM (AROUND 7000MB).....MMCBLK01 (AROUND 500MB).....AND ANOTHER THING I CANT REMEMBER NOW.....BUT WHEN IT FINISHED THE JOB, IT GAVE ME A mmcblk02 ERROR.....AND WHEN WHEN I CHECKED MY PHONE ON CWM SCREEN, IT GAVE ME A LIST OF CACHE ERRORS.....AND WHEN I SWITCHED OFF THE PHONE AFTER THAT IT REFUSED TO POWER ON.....IT WAS NOT EVEN GOING INTO DOWNLOAD OR RECOVERY MODE.....BATTERY HAD ENOUGH POWER....SO ITS NOT BATTERY FAULT......I SUPPOSE THAT SINCE THE PARTITIONS WERE FORMATTED THE PHONE BECAME COMPLETELY DEAD......CAN YOU TELL ME IF THERE IS ANY WAY WHERE I COULD GET THE COMPUTER TO RECOGNIZE MY PHONE USING A 'DEAD PHONE USB FLASH' OR SOMETHING.....AND THEN FLASH A BLANK BOOTLOADER AND THEN WRITE CWM?
I LIVE IN INDIA SIR.....+5.30 GMT.....I DO NOT KNOW ANYTHING ABOUT TEAMVIEWER.....IS IT AN ANDROID APP? CAN YOU EXPLAIN MORE IN DETAIL SIR?
PLEASE LET ME KNOW HOW TO GET THE COMPUTER TO RECOGNIZE THE PHONE AGAIN......

Well.. that sounds not that good...
Teamviewer (www.teamviewer.com) is an easy to use and free remote control software for your PC (it runs on both Linux and Windows). We could do a remote control session if you like. I can try to help but cannot promise anything.
I live in Germany: GMT +1. Send me a PM if you want to give that a try. Next Monday. Tuesday or Thursday would be possible on my site. At least for getting a short overview.
.

Thank you sir,
Thanks for the reply Sir.....I believe using teamviewer requires a internet connection with good amount of data.....I have an extremely slow 2G internet connection here in India.....I searched google to find some solution for the bricked I927......and came across many posts where people have used the 'unbrick.img' which was specifically made for their samsung phone models on their SD cards to resurrect their dead phones.....The method involves creating a 'unbrick.img' with emmc files extracted from another working I927 and then writing the image on an external SD card with some linux commands or win2image software and then inserting the SD card into the dead phone and switch it on by which it goes to download mode.....once in download mode I can flash CWM or TWRP and also flash stock firmware through odin and recover the phone.....Since your a developer who is well versed in things pertaining to this, can you make a unbrick.img file for the I927 and upload it here Sir? It will be very helpful for others also on the samsung glide subforum, as there is no proper 'hard unbrick' thread for the glide on xda......Ill be very grateful and thankful to you for all your help Sir.....

alvcross said:
Thanks for the reply Sir.....I believe using teamviewer requires a internet connection with good amount of data.....I have an extremely slow 2G internet connection here in India.....I searched google to find some solution for the bricked I927......and came across many posts where people have used the 'unbrick.img' which was specifically made for their samsung phone models on their SD cards to resurrect their dead phones.....The method involves creating a 'unbrick.img' with emmc files extracted from another working I927 and then writing the image on an external SD card with some linux commands or win2image software and then inserting the SD card into the dead phone and switch it on by which it goes to download mode.....once in download mode I can flash CWM or TWRP and also flash stock firmware through odin and recover the phone.....Since your a developer who is well versed in things pertaining to this, can you make a unbrick.img file for the I927 and upload it here Sir? It will be very helpful for others also on the samsung glide subforum, as there is no proper 'hard unbrick' thread for the glide on xda......Ill be very grateful and thankful to you for all your help Sir.....
Click to expand...
Click to collapse
Ok I have made one. It want to say it was VERY hard to find the correct instructions to do so and therefore I'm absolutely not sure if that will work for you!
Test it if you like but again: I have no idea if that would damage anything more than it is now!
See --> http://forum.xda-developers.com/cap...od-unbrick-debrick-hard-bricked-i927-t3285505
If it worked for you (would be like a miracle) then please report back!
If it does NOT work for you please report back, too!
thanks
xdajog
.
UPDATE:
Besides the link I posted --> Could you please also try the following:
1) Power on your device and directly after that:
2) Press and hold down Vol Up + Vol Down (both the same time)
3) You should see a warning message like the attached one which is the APX mode
4) you need to release the vol buttons immediately after you see the APX mode otherwise it will continue to the non working download mode.

Does teamviewer require internet connection with a lot of data?
Thanks for the reply Sir.....I believe using teamviewer requires a internet connection with good amount of data.....I have an extremely slow 2G internet connection here in India.....I searched google to find some solution for the bricked I927......and came across many posts where people have used the 'unbrick.img' which was specifically made for their samsung phone models on their SD cards to resurrect their dead phones.....The method involves creating a 'unbrick.img' with emmc files extracted from another working I927 and then writing the image on an external SD card with some linux commands or win2image software and then inserting the SD card into the dead phone and switch it on by which it goes to download mode.....once in download mode I can flash CWM or TWRP and also flash stock firmware through odin and recover the phone.....Since your a developer who is well versed in things pertaining to this, can you make a unbrick.img file for the I927 and upload it here Sir? It will be very helpful for others also on the samsung glide subforum, as there is no proper 'hard unbrick' thread for the glide on xda......Ill be very grateful and thankful to you for all your help Sir.....

alvcross said:
Thanks for the reply Sir.....I believe using teamviewer requires a internet connection with good amount of data.....I have an extremely slow 2G internet connection here in India.....I searched google to find some solution for the bricked I927......and came across many posts where people have used the 'unbrick.img' which was specifically made for their samsung phone models on their SD cards to resurrect their dead phones.....The method involves creating a 'unbrick.img' with emmc files extracted from another working I927 and then writing the image on an external SD card with some linux commands or win2image software and then inserting the SD card into the dead phone and switch it on by which it goes to download mode.....once in download mode I can flash CWM or TWRP and also flash stock firmware through odin and recover the phone.....Since your a developer who is well versed in things pertaining to this, can you make a unbrick.img file for the I927 and upload it here Sir? It will be very helpful for others also on the samsung glide subforum, as there is no proper 'hard unbrick' thread for the glide on xda......Ill be very grateful and thankful to you for all your help Sir.....
Click to expand...
Click to collapse
Uhm do you have read my above post??
.

1927 wouldn't boot.....Help.
Ohhhh Thank you.....thank you.....thank you for your kind reply Sir.....how good of you to take all your precious time to help me.....I greatly appreciate all your hard work Sir.....wonderful...*.I wanted to download your img file to try it out and when I read the reply of brother Bubor, that the I927 woudnt boot from the SD card when the bootloader is bricked, I was very disappointed. Like I said before, I have a very very slow internet connection with very less data left....and according to brother bubor's reply I doubt this will work....It looked like he was sure that it wont work....I tried to get into APX mode as the link that brother bubor posted had mentioned, but no luck, as the phone is not going into APX mode.....I remember that when I was trying to get to the APX mode the first time, the computer flashed a notification that the APX driver was not successfully installed.....but after that I tried the method more than a dozen times, but the computer was not recognizing the phone to go into APX mode.....Does the phone go into APX mode when the full internal phone system is formatted? I tried your second method on trying to get to APX mode, but nothing happens.....the computer is not recognizing the phone.....The battery had about 30% power in it when the phone got bricked 2 weeks ago.....Dont know if the battery drained all these days of not using the phone.....And even if I get to the APX mode, I have no idea how to proceed from there to repartition the internal phone system and get back download mode.....In the link that brother bubor posted the person who made the thread has made some files to be used when one gets into APX mode.....The PIT and emmc files which are necessary for repartitioning the system and getting the bootloader work are found in that zip file.....But that zip file is for the I9103 Galaxy R.....there isnt something like that available for the I927 yet.....And is brother bubor sure that the unbrick.img file wont work on the I927?

Give it a try with my unbrick image.
we all don't know.
.

xdajog said:
Give it a try with my unbrick image.
we all don't know.
.
Click to expand...
Click to collapse
Hi @alvcross: any update on this?
have you tried the SD card unbrick?
You said you cannot open the APX mode but what happens when you press the buttons for accessing the APX mode?
Try it even if you see a blank screen and then connect your Cappy with USB to your computer --> you should get a message about a missing driver or similar.
If that works I tell you how to proceed.

xdajog said:
hi @alvcross: Any update on this?
Have you tried the sd card unbrick?
You said you cannot open the apx mode but what happens when you press the buttons for accessing the apx mode?
Try it even if you see a blank screen and then connect your cappy with usb to your computer --> you should get a message about a missing driver or similar.
If that works i tell you how to proceed.
Click to expand...
Click to collapse
im so sorry that i was missing in this thread for a long time now sir.....i have had some issues at home and they have been sorted out lately.....yes sir.....i tried the sd card unbrick image....but my nothing happens.....when i try to hold volume up+power+home buttons and insert usb cable into my computer it says installing drivers and then says drivers failed to install....and nothing happens further.....can you help sir?

alvcross said:
im so sorry that i was missing in this thread for a long time now sir.....i have had some issues at home and they have been sorted out lately.....yes sir.....i tried the sd card unbrick image....but my nothing happens.....when i try to hold volume up+power+home buttons and insert usb cable into my computer it says installing drivers and then says drivers failed to install....and nothing happens further.....can you help sir?
Click to expand...
Click to collapse
Ok so you may try to install the special apx drivers now. Unfortunately I'm on vacation right now so I cannot upload them elsewhere. I come back to you next week.
Sent from my LG-H815 using XDA-Developers mobile app

xdajog said:
Ok so you may try to install the special apx drivers now. Unfortunately I'm on vacation right now so I cannot upload them elsewhere. I come back to you next week.
Sent from my LG-H815 using XDA-Developers mobile app
Click to expand...
Click to collapse
Oh yes Sir....Ill be waiting for the special apx driver package from you....Thank you so very much Sir.....God bless you.....

alvcross said:
Oh yes Sir....Ill be waiting for the special apx driver package from you....Thank you so very much Sir.....God bless you.....
Click to expand...
Click to collapse
No guarantee ! [emoji121]
Sent from my LG-H815 using XDA-Developers mobile app

xdajog said:
No guarantee ! [emoji121]
Sent from my LG-H815 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes Sir....I understand....

alvcross said:
Yes Sir....I understand....
Click to expand...
Click to collapse
Ok could you please try these driver package here: http://forum.xda-developers.com/galaxy-nexus/development/adb-fb-apx-driver-universal-naked-t1379875
Follow the instructions there for installing
The next step (if the driver would work for you) will be to flash a working PIT to your device to make sure you are using the correct partitions.
Afterwards we will flash the bootloader (may absolutely brick your device if not done correctly) and then --> if all goes fine --> you should be able to flash in download mode whatever you want to.
So it is still a long way to go and I need to check all the steps first before actually we can proceed.
That may take longer so do not expect that this will be something in the next days.. sorry.
Update:
If the above universal driver do NOT work for you: Test these one here View attachment apx_driver_samsung.zip
.

Thanks for the speedy reply Sir......Ill do as you said and let you know Sir......thank you.....thank you.....thank you Sir....

wooowwww......windows installed the drivers for the phone and it shows up as "NVIDIA usb boot-recovery for mobile devices." But when I open minimal adb and fastboot and type 'adb devices' the phone doesn't show up in the 'list of devices attached'....the line after 'list of devices attached' is just empty.....Also the phone doesnt show up in odin....what should I do next Sir?

alvcross said:
wooowwww......windows installed the drivers for the phone and it shows up as "NVIDIA usb boot-recovery for mobile devices." But when I open minimal adb and fastboot and type 'adb devices' the phone doesn't show up in the 'list of devices attached'....the line after 'list of devices attached' is just empty.....Also the phone doesnt show up in odin....what should I do next Sir?
Click to expand...
Click to collapse
nvidia apx isnt fastboot/adb device. You can found tool on nvidia site ( more info https://ac100.grandou.net/nvflash ), this tool can read and write whole flash.
Before you could use nvidia's tool, you must send an uniq blob to your phone. APX mode is useless without this blob.
This blob is uniq for every phone.

Help rooting a BLU Dash M

I need some assistance trying to find a method to root my Dash M (which appears to be extremely rare to find a rooting method for).
I already tried framaroot (tool I used to root my tablet before) and Kingroot and such, but none were able to do it (and all google searches led to videos on rooting a BLU Dash 5.0 or another device from the Dash range, which isn't what I needed).
The Dash M is running Android 5.1 and custom build BLU_D030U_V16_GENERIC 28-01-2016 15:41
If anyone could help it'd be very much appreciated c:

Unlock OEM in developer mode and try it whit Kingroot

AnarchyPhoenix746 said:
I need some assistance trying to find a method to root my Dash M (which appears to be extremely rare to find a rooting method for).
I already tried framaroot (tool I used to root my tablet before) and Kingroot and such, but none were able to do it (and all google searches led to videos on rooting a BLU Dash 5.0 or another device from the Dash range, which isn't what I needed).
The Dash M is running Android 5.1 and custom build BLU_D030U_V16_GENERIC 28-01-2016 15:41
If anyone could help it'd be very much appreciated c:
Click to expand...
Click to collapse
I have a Blu Advance 5.0, from the same exact family. In May, they had an OTA sent out to it to update the security. And little did I know, that meant no more root. Before the OTA to V06, I was on V04, and was able to root with Kingroot in less than a minute, perfectly. After the update, nothing good came of it.
For the past months I've tried hundreds of things to flash custom roms and recoveries (which I figured it out eventually) and then it crashed, due to a "damaged OTA". This meant that it couldn't update because I was rooted.
So here's the solution... If there's any older versions of your model or chipset (AKA Mediatek D030UX, D030U {MT6580}), download that firmware to your computer desktop as a (.zip) file. Then download the SP Flash Tool (Smart phone flash tool) from their website, and plug your phone into your computer via Media Transfer (MTK).
If you already have developer's options enabled, skip this.
- Go into your settings, go all the way down to "About Device", and find where it says "Build Number" (which will most likely have the phone brand in the file name). Tap on that about 8 times until it give a toast notification saying "Developer's Mode Enabled".
After you get that done, go back into your regular setting and now there should be a box above your "About Device" button that says "Developer Options". Tap that, then turn them on (press OK/YES if a prompt pops up) and then select the following options ,if available.
-OEM Unlock
-USB Debugging
Now plug your phone into a computer and install the drivers for your phone (it should do it automatically) and launch the SP Flash Tool that you had downloaded (extract to desktop before you launch, or it will show "error"). Now open the SP Flash tool and click on the "Scatter Loading" button. Navigate to your desktop, and find the firmware folder you downloaded. Click on that, then click on "Firmware", and it should bring up a .TXT file (Scatter file) with the desired firmware version you want. Click on it and press open.
A chart will appear in the space below with all the things the firmware has built in. All of them should be checked. Take out your battery now (from your phone) and plug the phone in without the battery. Wait for the model on the left to name your device, and click on the drop down list above the chart, it should give 3 options. Firmware Upgrade, Download only, and Format All + Download. Press Format All + Download. The bar at the bottom will turn a few colors, depending on what it's doing.
Now you're done! It's flashed. From that version, try to figure out a way of rooting it.
WARNING: Flashing erases all data on device, please backup to an external storage (SD CARD), before attempting this, in case you brick your device.
Sent from my RCT6873W42M using XDA Labs
---------- Post added at 03:04 AM ---------- Previous post was at 02:56 AM ----------
TechTeen17 said:
I have a Blu Advance 5.0, from the same exact family. In May, they had an OTA sent out to it to update the security. And little did I know, that meant no more root. Before the OTA to V06, I was on V04, and was able to root with Kingroot in less than a minute, perfectly. After the update, nothing good came of it.
For the past months I've tried hundreds of things to flash custom roms and recoveries (which I figured it out eventually) and then it crashed, due to a "damaged OTA". This meant that it couldn't update because I was rooted.
So here's the solution... If there's any older versions of your model or chipset (AKA Mediatek D030UX, D030U {MT6580}), download that firmware to your computer desktop as a (.zip) file. Then download the SP Flash Tool (Smart phone flash tool) from their website, and plug your phone into your computer via Media Transfer (MTK).
If you already have developer's options enabled, skip this.
- Go into your settings, go all the way down to "About Device", and find where it says "Build Number" (which will most likely have the phone brand in the file name). Tap on that about 8 times until it give a toast notification saying "Developer's Mode Enabled".
After you get that done, go back into your regular setting and now there should be a box above your "About Device" button that says "Developer Options". Tap that, then turn them on (press OK/YES if a prompt pops up) and then select the following options ,if available.
-OEM Unlock
-USB Debugging
Now plug your phone into a computer and install the drivers for your phone (it should do it automatically) and launch the SP Flash Tool that you had downloaded (extract to desktop before you launch, or it will show "error"). Now open the SP Flash tool and click on the "Scatter Loading" button. Navigate to your desktop, and find the firmware folder you downloaded. Click on that, then click on "Firmware", and it should bring up a .TXT file (Scatter file) with the desired firmware version you want. Click on it and press open.
A chart will appear in the space below with all the things the firmware has built in. All of them should be checked. Take out your battery now (from your phone) and plug the phone in without the battery. Wait for the model on the left to name your device, and click on the drop down list above the chart, it should give 3 options. Firmware Upgrade, Download only, and Format All + Download. Press Format All + Download. The bar at the bottom will turn a few colors, depending on what it's doing.
Now you're done! It's flashed. From that version, try to figure out a way of rooting it.
WARNING: Flashing erases all data on device, please backup to an external storage (SD CARD), before attempting this, in case you brick your device.
Click to expand...
Click to collapse
You can download the tool at the bottom of this thread.
Sent from my RCT6873W42M using XDA Labs

Root BLU Dash M
AnarchyPhoenix746 said:
I need some assistance trying to find a method to root my Dash M (which appears to be extremely rare to find a rooting method for).
I already tried framaroot (tool I used to root my tablet before) and Kingroot and such, but none were able to do it (and all google searches led to videos on rooting a BLU Dash 5.0 or another device from the Dash range, which isn't what I needed).
The Dash M is running Android 5.1 and custom build BLU_D030U_V16_GENERIC 28-01-2016 15:41
If anyone could help it'd be very much appreciated c:
Click to expand...
Click to collapse
i know this is an old thread but.... i rooted mine (Dash M) with KingoRoot (look it up on Google)... i tried lots of stuff with no results, everything failed (i've already tried to root with KR in windows) but the only thing that worked was rooting with the android app in KR page... i felt really stupid after trying everything with no results when i've been using KR for other "hard phones".... either way, the only downside is that their SU manager displays all the time ads no matter where in the phone you are... but you can freeze the app to fix this and unfreeze it when you need to assign permissions....
BTW: its KingoRoot not kingroot (just in case)

HOW TO FIX AN ERROR OCCURRED WHEN UPDATING THE DEVICE SOFTWARE

When attempting to root, install a custom ROM, or even install the original firmware, you may encounter issues that are caused by a broken cord, a dead computer, or when the firmware you installed is corrupted or you have the incorrect version installed. However, covering all error messages in a single article is difficult. As a result, we're focusing solely on "An error occurred when updating the device software." Samsung Galaxy Smartphones exhibit this error. It happened to me on a Samsung Galaxy Note 10 Plus with One UI and Android 10, Android 11, and Android 12 firmware.
We have two options for fixing this: official and unofficial. The latter is suggested.
Unofficial Method
Using Frp HiJacker by Hagard
In this method, we will be using the unofficial application “Frp HiJacker by Hagard“.
1. First you need to download the application from this link.
2. Once downloaded please extract the zip archive and you will get a “.exe” file. Double click on it to install.
3. In the second installation window you will be asked to enter the password. Now enter “www.gsmhagard.com” as the password and complete the installation.
4. Once done connect your Samsung Galaxy Smartphone with your PC and open the “Frp HiJacker by Hagard” application.
Now if the box near “Port” is empty then please click the “Scan” button. Once done your phone will be detected by the application.
Else type your model number.
However, if the box is already filled automatically you are good to proceed.
5. Now select “Soft Brick Fixer” and click the “HIJACK IT!” button.
That’s it your Galaxy Smartphone will reboot and the error will be gone for good.
Official Method
This method uses the official Samsung “Smart Switch” PC application.
1. First please download and install the Smart Switch application on your Windows PC from this link and for MAC OS here.
2. Now open Smart Switch If your device is connected you will get the phone model on this screen. If your Galaxy Smartphone is already connected please press the 3 dots on the top right corner and you will get a dropdown.
3. Now tap on “Emergency Software Recovery “. If you are good to go your phone model will be listed in the window’s list.
If you can see your phone’s model there please select it and click “OK” and follow the onscreen steps to resolve the error.
However, if you are not able to see your phone model or not able to connect to Smart Switch In this case please click on the second option which is “Reinstall device driver “.
When you get the window please click “Confirm” to proceed with phone driver installation.
Continue from "Step-3" once the device driver installation is complete and you can connect your phone to the "Smart Switch."
If you are unable to connect your Galaxy Smartphone to Smart Switch or if your phone model is not listed under "Emergency Software Recovery," you should utilize the Unofficial approach.

This actually helped me. Say, I've noticed it also has "remove FRP". Can you please explain how to perform this operation, too?

AndroidDeveloperLB said:
This actually helped me. Say, I've noticed it also has "remove FRP". Can you please explain how to perform this operation, too?
Click to expand...
Click to collapse
Did you manage it to work?

Naksuhd said:
Did you manage it to work?
Click to expand...
Click to collapse
What do you mean?
It only solved the error. I still have FRP.
I have found this video though, and even though it looks quite dangerous (for the PC), I gave it a try.
I'm only half way there. I got to the point that I'm in the settings of the OS.
The video is here:
link

I had this exact same issue while trying to install twrp on my galaxy s7 edge, after a lot of searching I could'nt find any solutions. I ended up choosing an older version of twrp and uploaded that, which fixed the issue.

DanyBoi05 said:
I had this exact same issue while trying to install twrp on my galaxy s7 edge, after a lot of searching I could'nt find any solutions. I ended up choosing an older version of twrp and uploaded that, which fixed the issue.
Click to expand...
Click to collapse
Hey! Could you report which version of twrp you used? I ran into exactly the same problem with my galaxy s7 edge and would like to try your solution

Man! Thank you! Most readable guide. Tried others, but they are so convoluted, you wrote it so good, fixed soft brick on S10!