yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] az0ik:
Great!!! Did you try to flash the new img file posted by erickreisbr?
[Upgrading, Modifying and Unlocking] GuiSouza:
yes, but without success :(

---------- Post added 16th March 2013 at 12:13 AM ---------- Previous post was 15th March 2013 at 11:44 PM ----------

I've got another problem, now my ADB does not recognize the device ... is something related to the boot.img? I checked the drivers and they are all installed correctly. The windows to show me a message saying that the device is ready to be used.

Only "fastboot devices" command from fastboot mode works. :(

Editing:

I re-flashed the boot.img and it works ^^
[Upgrading, Modifying and Unlocking] az0ik:
what boot.img did you flashed? do you have the link to download it?
[Upgrading, Modifying and Unlocking] GuiSouza:
here: https://www.dropbox.com/s/e7ixjm0h1n09gso/boot.img

:)
[Upgrading, Modifying and Unlocking] az0ik:
Thank you :good::good:

Hopefully erickreisbr could help us with another img file :confused:
[Upgrading, Modifying and Unlocking] GuiSouza:
u welcome ;)

all we need now is an image that works D:

My Shell don't work... but i think is because i don't have any system in my device

if anyone knows of the error and can help me, I'll be grateful:

"D:\Android\ADB>adb shell

- exec '/system/bin/sh' failed: No such file or directory (2) -"
[Upgrading, Modifying and Unlocking] GuiSouza:
hey guys, i don't know if help us, but look at this drop box... i think will help us

https://www.dropbox.com/sh/xtp4bf1lputhi1l/uKD3TmhlNe
[Upgrading, Modifying and Unlocking] erickreisbr:
Another system.img removed from my device

https://docs.google.com/file/d/0B5rQL4bfhfPRWWZZdm5IU0dLdUU/edit?usp=sharing
[Upgrading, Modifying and Unlocking] az0ik:
Thank you erickreisbr, but it did not work for me.
[Upgrading, Modifying and Unlocking] GuiSouza:
:( all times i tried to flash the system appears the same error.

D:\Android\ADB>fastboot devices

MSM7625ASKU3 fastboot

D:\Android\ADB>fastboot erase system

erasing 'system'...

OKAY [ 0.773s]

finished. total time: 0.776s

D:\Android\ADB>fastboot flash system system.2knand.img

sending 'system' (157430 KB)...

OKAY [ 39.371s]

writing 'system'...

FAILED (remote: flash write failure)

finished. total time: 52.901s

D:\Android\ADB>

I do not know what happened: (

---------- Post added at 05:00 PM ---------- Previous post was at 04:56 PM ----------

I've tried with every file "system.img" I have here and ALL show me FAILED
[Upgrading, Modifying and Unlocking] erickreisbr:
System.img follows another. This was extracted with onandroid script.

https://docs.google.com/file/d/0B5rQL4bfhfPRdjJLSDFhR3NsWHc/edit?usp=sharing
[Upgrading, Modifying and Unlocking] az0ik:
Oh my god... It Worked!!!!! Thank you so much erickreisber.... Best Sunday ever!!!!!! :victory::victory::victory::victory::good::good::good::good::good:
[Upgrading, Modifying and Unlocking] GuiSouza:
as i said, my device show me follow error:

D:\Android\ADB>fastboot devices

MSM7625ASKU3 fastboot

D:\Android\ADB>fastboot erase system

erasing 'system'...

OKAY [ 0.770s]

finished. total time: 0.773s

D:\Android\ADB>fastboot flash system system.yaffs2.img

sending 'system' (177152 KB)...

OKAY [ 44.293s]

writing 'system'...

FAILED (remote: flash write failure)

finished. total time: 57.838s

D:\Android\ADB>

I don't know what to do :(

---------- Post added at 04:25 PM ---------- Previous post was at 04:21 PM ----------

ADB does not recognize my device :/
[Upgrading, Modifying and Unlocking] erickreisbr:
Good ... and the root worked?

If yes, please extract the recovery for me ...

use the commands:

su

cat /dev/mtd/mtd6> /sdcard/recovery.img
[Upgrading, Modifying and Unlocking] GuiSouza:
pls guys, help me :I

my device no longer recognizes the ADB... i want to try flash with that sys.img too..

every time I try, with every sys.img, the SAME error appears :(

D:\Android\ADB>fastboot flash system system.yaffs2.img

sending 'system' (177152 KB)...

OKAY [ 44.293s]

writing 'system'...

FAILED (remote: flash write failure)

finished. total time: 57.827s

What i have to do?

---------- Post added at 02:17 AM ---------- Previous post was at 01:25 AM ----------

i tried to reinstall driver, sdk, but all without success :(

---------- Post added at 02:23 AM ---------- Previous post was at 02:17 AM ----------

Same error with all tasts :l

D:\Android\ADB>fastboot flash system System3.img

sending 'system' (188297 KB)...

OKAY [ 47.078s]

writing 'system'...

FAILED (remote: flash write failure)

finished. total time: 60.604s

D:\Android\ADB>fastboot flash system System1.img

sending 'system' (184597 KB)...

OKAY [ 46.153s]

writing 'system'...

FAILED (remote: flash write failure)

finished. total time: 59.678s

D:\Android\ADB>fastboot flash system System2.img

sending 'system' (177152 KB)...

OKAY [ 45.232s]

writing 'system'...

FAILED (remote: flash write failure)

finished. total time: 51.441s

D:\Android\ADB>fastboot flash system system.yaffs2.img

sending 'system' (177152 KB)...

OKAY [ 44.292s]

writing 'system'...

FAILED (remote: flash write failure)

finished. total time: 57.821s

D:\Android\ADB>fastboot flash system system.2knand.img

sending 'system' (157430 KB)...

OKAY [ 39.361s]

writing 'system'...

FAILED (remote: flash write failure)

finished. total time: 52.891s
[Upgrading, Modifying and Unlocking] GuiSouza:
after a lot time, finaly, ADB recognize again, but i have the same error with "write"

C:\Android\sdk\platform-tools>adb devices

List of devices attached

1234567890ABCDEF device

C:\Android\sdk\platform-tools>adb reboot bootloader

C:\Android\sdk\platform-tools>fastboot devices

MSM7625ASKU3 fastboot

C:\Android\sdk\platform-tools>fastboot flash system system.yaffs2.img

sending 'system' (177152 KB)...

OKAY [ 44.292s]

writing 'system'...

FAILED (remote: flash write failure)

finished. total time: 57.821s

C:\Android\sdk\platform-tools>
[Upgrading, Modifying and Unlocking] erickreisbr:
Use fastboot erase system before the flash
[Upgrading, Modifying and Unlocking] GuiSouza:
'-'

I'll give up guys :/

I can't figure out what happened with this device...

ADB recognize now, but always FAILED in "write step"

thanks for help o/
[Upgrading, Modifying and Unlocking] az0ik:
Here's the recovery.img https://www.dropbox.com/s/ec1hjl4u9fylbst/recovery.img :)
[Upgrading, Modifying and Unlocking] nuwapian:
recovery for BLU dash 3.5

you can use the same s12 recovery img it restored the 3e recovery for me and works normal
[Upgrading, Modifying and Unlocking] erickreisbr:
Perfect ... thank you ... now I'm trying to compile cwm
[Upgrading, Modifying and Unlocking] az0ik:
GuiSouza, easy man... Don't give up yet!!! :p We will help you out with this, the img file uploaded by erickreisbr worked perfect on my BD 3.5 and the besta part that its already rooted. Its really odd that you are getting the same error with this new img, but i am sure that if it worked on mine it sure will work and yours as well, just be patient.

Do you have skype? so that i can help you out? Let me know

Regards.
[Upgrading, Modifying and Unlocking] GuiSouza:
thanks man ^^

Erick helped me and we had a breakthrough with my phone.

my device is now accepting Rooted Recovery mode and also have access to Shell, now I feel lack little to finish the job :)
[Upgrading, Modifying and Unlocking] az0ik:
Great!!! :good: maybe you can restore through a working cwm for BD 3.5, Erick is working on it. Let me know if I can help you with anything, would be glad to do so.

Cheers!!!
[Upgrading, Modifying and Unlocking] GuiSouza:
so...

Look..

~ #

D:\Android\ADB>adb devices

List of devices attached

1234567890ABCDEF recovery

D:\Android\ADB>adb push system.tar /sdcard/system.tar

2330 KB/s (181107712 bytes in 75.892s)

D:\Android\ADB>adb push busybox /data/local/busybox

2251 KB/s (1062992 bytes in 0.461s)

D:\Android\ADB>adb shell

~ # chmod 777 /sdcard/system.tar

chmod 777 /sdcard/system.tar

~ # chmod 677 /data/local/busybox

chmod 677 /data/local/busybox

~ # /data/local/busybox tar -cvf /sdcard/system.tar /system

/data/local/busybox tar -cvf /sdcard/system.tar /system

tar: removing leading '/' from member names

system/

system/lost+found/

system/bin

~ # exit

exit

D:\Android\ADB>

What i have to do now ?
[Upgrading, Modifying and Unlocking] az0ik:
Erick, I've seen to lost my root access on my BD 3.5 did you experience this problem as well? If so please let me know what to do to solve it.
[Upgrading, Modifying and Unlocking] erickreisbr:
my root still works normally. you installed or removed anything?
[Upgrading, Modifying and Unlocking] az0ik:
I've installed the following apps that require root access: Busybox Free, Link2SD, RAM Expander, this last one i've uninstalled, because i kept getting an error. Probably this one messed up something that disabled root access.

Erick,

I have rooted the phone once again following this steps you provided with fenrixarena...

Everything working great now!!! One question, can you recommend me what app should i use to enable memory swap? I already tried ROEHSOFT RAMEXPANDER but did not work. Any other options that you might know??
[Upgrading, Modifying and Unlocking] eriickiller:
need help with boot.img

hi guys, i've flashed a wrong boot.img (from another clone) while trying to get root acces, i got ir, but now my phone don't show battery level, can't send sms, and another problems.

can someone extract a boot.img original for me?, thanks in advance!
[Upgrading, Modifying and Unlocking] fenrixarena:
If you look at the phone's system it was designed to already use a type of a page file. In order to use Ram Expander, a great idea if you format the sd card into partitions & create a larger page file for use as ram, you would have to add ext support on the boot.img & remove the phones programs to make it work. I don't build so you're SOL unless u do it yourself or find a really bored developer.

I still don't see the point in a recovery if nothings being replaced by a new rom, backups are pointless, unless you'll be building roms.
[Upgrading, Modifying and Unlocking] GuiSouza:
Hey man, i used this boot, try this...

https://www.dropbox.com/s/e7ixjm0h1n09gso/boot.img

---------- Post added at 09:19 AM ---------- Previous post was at 09:07 AM ----------

if don't work, the originals are here: https://www.dropbox.com/s/msabpgsjvstdd4x/s12_boot_recovery_bak.zip
[Upgrading, Modifying and Unlocking] erickreisbr:
[GUIDE] - Root Blu Dash 3.5 d170

English is not my native language so forgive me for spelling errors.

The tutorial consists of:

Install a recovery.img that enables the temporary root access on the device.

Upload the files su, busybox and superuser.apk system for the device

Install the recovery of the original Blu Dash 3.5

Required Files:

ADB drivers installed

32bits - http://www.mediafire.com/?21na032gnzbfza2

64bits - http://www.mediafire.com/?1hrwo325cb1ej2w

The driver can also be installed by SuperOneClick v2.3.3

File root_blu_dash_d170.exe - https://docs.google.com/file/d/0B5rQL4bfhfPRMXRJd0xoSi1sTlk/edit?usp=sharing

Starting

1. Run the file 'root_blu_dash_d170.exe' and not change the installation path.

2. Auto will run the root.bat. Only proceed if you are sure of what you are doing.

3. recovery will be installed with root access. And the phone will reboot. Unplug the USB cable. Switch power off and remove the battery.

Replace the battery and turn on holding power and vol+ for 15 seconds.

The device will turn on but will not start android, will stay with the BLU logo on the screen.

Connect the phone to the USB cable and continue.

4. The device will copy the necessary files and change permissions. Then will reboot into bootloader mode and install the original manufacturer's recovery.

5. After completing the android device will reboot normally.

6. Make sure the SuperUser is installed. And try to install terminal emulator and run the su command.

Thanks 'fenrixarena and az0ik' for helping me in the process. :good:

For those who used the boot Qsmart S12 to gain root access, boot follows the original Blu D170.

https://docs.google.com/file/d/0B5rQL4bfhfPRNi1SNklOX1N1Q3c/edit?usp=sharing
[Upgrading, Modifying and Unlocking] az0ik:
Excellent Guide Erick :good::good: We thank you for your time and dedication on making this possible.
[Upgrading, Modifying and Unlocking] eriickiller:
thank you gui, i will try today.

great tutorial Erick, chará :)
[Upgrading, Modifying and Unlocking] az0ik:
Thank you for the tip. I'm no developer, so I guess it would be quite some time until we have custom roms tha would enable such features on a BD 3.5 :rolleyes: Anyhow, thanks again!!!
[Upgrading, Modifying and Unlocking] estape11:
I follow all steps but when is copy system files say /system/app/superuser.apk fail directory, and phone restart and superuser is not installed and i download root checker and say "this phone is not rooted" i do any wrong? HELP
[Upgrading, Modifying and Unlocking] erickreisbr:
Let's try manually.

1 - plug the device into fastboot mode. (Power on holding power + vol -)

2 - Open the command prompt and use:

cd /ADB

fastboot erase recovery

fastboot flash recovery recovery_Qsmart-S12.img

3 - Turn off the phone, remove the battery, insert the battery

and turn on the holding power and vol + for 15s.

On display will be the BLU logo. Connect the phone.

execute commands:

adb push su /system/bin

adb push busybox /system/bin

adb push superuser.apk /system/app

adb shell chmod 6577 /system/bin/su

adb shell chmod 677 /system/bin/busybox

adb shell chmod 644 /system/app/superuser.apk

adb reboot-bootloader

fastboot erase recovery

fastboot flash recovery recovery_stock_blu.img
[Upgrading, Modifying and Unlocking] estape11:
Thanks for guide, i have a 1 question, in step 3 when i turn off my phone, i need wait to start or not?
[Upgrading, Modifying and Unlocking] erickreisbr:
No need to wait ... The appliance must be with the BLU logo on the screen so you can continue
[Upgrading, Modifying and Unlocking] fenrixarena:
Can u send me the playstore.apk as is not in a zip or anything to fenrixarena@gmail.com
[Upgrading, Modifying and Unlocking] estape11:
I have the same problem i cant get root :(
[Upgrading, Modifying and Unlocking] erickreisbr:
Where the problem is

occurring.?

Enviado do meu BLU DASH 3.5
[Upgrading, Modifying and Unlocking] pcrtljunior:
adb push su /system/bin --> OK

adb push busybox /system/bin --> OK

adb push superuser.apk /system/app --> OK

adb shell chmod 6577 /system/bin/su --> OK

adb shell chmod 677 /system/bin/busybox --> OK

adb shell chmod 644 /system/app/superuser.apk --> ERROR

"chmod: /system/app/superuser.apk: Not a directory"

what happned?

"neste comando dá erro dizendo que o aplicativo não é um diretório"
[Upgrading, Modifying and Unlocking] erickreisbr:
Turn on the phone and check if SuperUser is installed. If you are ok. If you do not install it by google play.
[Upgrading, Modifying and Unlocking] estape11:
Hey i have the same problem, i download Superuser app from play store and still not working :( i try many times and doestn work, help me please:confused:
[Upgrading, Modifying and Unlocking] erickreisbr:
Reboot into recovery mode and use the commands:

adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system

adb push su /system/bin

adb push busybox /system/bin

adb push superuser.apk /system/app
[Upgrading, Modifying and Unlocking] estape11:
How i reboot in recovety mode?
[Upgrading, Modifying and Unlocking] sanijsnj:
hii... I'm having same problem as estape11 in rooting my device..

tried everything.. still can't root..

for the command: adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system

it says invalid argument..

please help..
[Upgrading, Modifying and Unlocking] royboss:
blu dash 3.5

Hey man i was wondering if you wouldnt mind explaining exactly how you got to root your blu dash 3.5 . i tried everything with out any succes :(... i had givin up hope until i read this ...but i dont understand what it is you did. can you please brake it down step by step ?

plz reply thanks
[Upgrading, Modifying and Unlocking] silivrenion:
There seems to be something wrong with the automatic tool that was posted earlier on page 10... I followed the instructions and noticed that it tries to CHMOD superuser.apk, but it errors on the permissions. I can't seem to find superuser or su installed on the device.

One of the previous posts mentions to reboot into recovery mode, mount the partition in RW and push all the files up, but when I reboot into recovery ADB doesn't see the device listed under adb devices, so I can't issue commands to it.

I installed superuser via the market, but without su it's pretty useless. Root checker confirms that the root access isn't on it yet.

I don't know if the tool was actually able to change anything or not.. is it just a matter of remounting and copying the apk's over, or is there more to it to complete the root process?

Also, can the person who wrote that tool PLEASE update their post/software with more information once this bug is worked out? I don't seem to be the only one that tried the utility with no success...

EDIT:

I did try the manual steps as well as the auto tool. It fails to CHMOD superuser.apk, and root checkers/superuser don't see SU at all. Recovery mode (PWR + vol+) doesn't allow for adb access so I can't fix it. What have I done wrong here?
[Upgrading, Modifying and Unlocking] erickreisbr:
News on how to root the device.

News on how to root the device.

I got along with the staff of fanpage "micromax A54" on facebook a clockworkmod that works without displaying the video on the screen.

1 - USB debugging must be active.

2 - Unzip ADB.zip to c: \ ADB and copy the file "su-bin-3.1.1-arm-signed.zip" to the sd card.

3 - Install cwm-blu-d170.img with fastboot. (Fastboot flash recovery cwm-blu-d170.img)

To access the fastboot mode of our device need power the device holding the volume down button.

4 - After installing reboot the device holding power + volume up until the screen goes black and the buttons are illuminated.

5 - Connect the device in USB cable and run the file c:\ADB\ asm.jar. Select the device and click ok.

Hopefully the cwm recovery screen will appear on ASM. The image appears in four parts, but nothing that would prevent the use.

6 - Upon entering the cwm press vol+, vol-, vol+, vol- will appear written "back menu button enable". After that comes the phrase the power button can select options on the screen.

7 - Use the vol + or vol- to select the option "install zip from sdcard". And the power button to select.

8 - select "choose zip from sdcard".

9 - Select the file "su-bin-3.1.1-arm-signed.zip". in the following section and the option YES.

Wait for the process to terminate and restart the device.

Now install the SuperUser by Google Play and ready your device has root access.

Remember: It is so at your own and risk, not responsible for damage to equipment.
[Upgrading, Modifying and Unlocking] johk0563:
SOLUTION porfabor

First of all not English, I hope I understand, googlpe translation,

E seen its 13 pages, and I've made ​​the process of page 10 - # 98, this gave me super for a day, then returned to perform the process, not change,

Choose to test the recovery system, does work, retrieve the recovery, then try the last page 13 --- # 122, this recovery "<e3>", do not install the image given write error, and lost phone, after several attempts to connect adb to the device, manages to recognize it,

At this point I proceeded with the first named (page 10 - # 98), but surprise at the end, this worked, which check was that "recovery <e3>" this functional

Power gave approval to superuser, it exists and it works, I could install "titanium pro Bacum" super asks permission, I grant the permits,

With several more, all ok, walks superuser, or root is the blu dash 3.5,

Problem with internet: only problem is no internet, if configure APN, but not run, not the GPS.

ASK A SOLUTION porfabor

thanks from now: Bueno:
[Upgrading, Modifying and Unlocking] estape11:
Hey i speak spanish (Costa Rica) contact me in private message or Twitter [MENTION=4934175]estape11[/MENTION]_
[Upgrading, Modifying and Unlocking] johk0563:
bárbaro guri ¡¡¡

barbaro guri pero yo no tengo Twitter , solo g mail y hotmail tenia skype pero ace tanto que no entro que la verdad no se si eciste jajaja por las dudas es johk0563 mi id, yo no soy ducho en esto pero si te digo que me revuelvo como gato entre la leña, podes esplicarme ya que boy despasio y seguro, el aparato anda pero no el superuser, hoy mismo se elimino la libertad de acion, luego te esplico para que lo necesito jajaja desde ya mil gracias y un abraso desde URUGUAY: Laugh:: Good:
[Upgrading, Modifying and Unlocking] silivrenion:
This worked wonderfully. Thanks!

Can we get a CWM recovery that displays on the screen now? Or is it safe to fastboot back to the original recovery?
[Upgrading, Modifying and Unlocking] erickreisbr:
It is not necessary to go back to the original recovery. We do not have cwm recovery working with video.
[Upgrading, Modifying and Unlocking] juanqg:
Thanks for the guide and all the work.

I followed it and after some bumps I finally got it working, however, after the phone loads up it shows "Sim Disabled" and doesn't work.

it did recognize it once and worked for about 5 minutes, then after restart it is not able to connect to the network.

Can you shed some light on this?

Thanks!
[Upgrading, Modifying and Unlocking] GuiSouza:
Erick, segui os passos e parece que deu certo, mas como sei se o root tá mesmo funcionando :?

esquece, ja fiz o teste e funcionou PERFEITAMENTE! =D valeu cara!

Worked perfectly! man, thanks!!!
[Upgrading, Modifying and Unlocking] GuiSouza:
As you see, SuperUser run great! :)
[Upgrading, Modifying and Unlocking] baidawi:
Blu Dash D160a

I am in desperate need of the boot.img and system.img files for the Blu Dash D160a (i.e. the single sim version of the D170).

Can anyone help?

I've tried all of the major phone tech outlets in my country as well as contacting the manufacturers but to no avail. Any assistance with this would be greatly appreciated.
[Upgrading, Modifying and Unlocking] huangfeng.ruan:
Help me fix CWM four minitor photo

Help me fix CWM Q-Smart S12 Vietnam 4 photo

---------- Post added at 07:42 AM ---------- Previous post was at 07:37 AM ----------

this is photo Q-SMart S12

[IMG]https://lh5.googleusercontent.com/-2jm0mrcyAY0/UZ8KUPNppBI/AAAAAAAALEM/N_xbV-jWalc/s1024/choimobile.vn-604007_293395887462110_1059096548_n.jpg[/IMG][/QUOTE]
[Upgrading, Modifying and Unlocking] erickreisbr:
Share this recovery for i test.
[Upgrading, Modifying and Unlocking] juanga1624:
Backup of D160a

Send me a private message i cant post the url
[Upgrading, Modifying and Unlocking] erickreisbr:
New CWM recovery for Blu Dash 3.5.

http://xdaforums.com/showthread.php?t=2321264

New custom rom for Blu Dash 3.5.

http://xdaforums.com/showthread.php?t=2321449
[Upgrading, Modifying and Unlocking] baidawi:
Those are for the D170 which is the Dual SIm version of the BLU. I have the D160a i.e. the Single Sim version.
[Upgrading, Modifying and Unlocking] zachpainter77:
This worked on my BLU DASH 4.0

I dont know if this will work with 3.5 but this works on 4.0

Watch this video: youtube-->How to root Blu Dash 4 0

follow his link to get the rootme pack...

You will need the adb driver... since BLU doesn't provide this anywhere you can install it via installing pdanet...

search google for "topnotchtablets installADBDriver"

I first installed ADB, then I ran the root script and voila my BLU DASH 4.0 was rooted... took me a while to find this out.. searched everywhere for the correct adb driver...

enjoy!:good:

I cannot post links yet because I just registered to this forum today... I would have posted the links tho.. sorry:(
[Upgrading, Modifying and Unlocking] ricbermo:
What's fastbook

Hi, thanks for this wonderfull tut.

I'm new to android and I'd like to know what is this fastbook. I don't know what you mean. should the cell be connected to the pc?, thanks
[Upgrading, Modifying and Unlocking] ricbermo:
could somebody tell me how to install the img with fastbook

Hi, there,

I'm newbe and don't know how to install the img with fastbook.

Really stocked here.