FORUMS
Remove All Ads from XDA

[GUIDE][ROOT] Blu Dash 3.5 d170 - Help with recovery and root

94 posts
Thanks Meter: 32
 
By erickreisbr, Member on 11th February 2013, 11:45 AM
Post Reply Email Thread
19th March 2013, 04:02 AM |#91  
GuiSouza's Avatar
Member
Flag Ribeirão Preto
Thanks Meter: 2
 
More
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 ?
 
 
19th March 2013, 02:46 PM |#92  
Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by erickreisbr

Perfect ... thank you ... now I'm trying to compile cwm

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.
19th March 2013, 11:57 PM |#93  
OP Member
Flag Campinas
Thanks Meter: 32
 
More
Quote:
Originally Posted by 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.

my root still works normally. you installed or removed anything?
20th March 2013, 12:35 AM |#94  
Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by erickreisbr

my root still works normally. you installed or removed anything?

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...
Quote:

Adb push su /system/bin
Adb push busybox /system/bin
Adb push superuser.apk /system/app
adb shell
~# chmod 6755 /system/bin/su
~# chmod 755 /system/bin/busybox
~# chmod 644 /system/app/superuser.apk

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??
20th March 2013, 04:15 AM |#95  
Junior Member
Thanks Meter: 0
 
More
Unhappy 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!
20th March 2013, 11:11 AM |#96  
fenrixarena's Avatar
Member
Thanks Meter: 3
 
More
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.
20th March 2013, 01:19 PM |#97  
GuiSouza's Avatar
Member
Flag Ribeirão Preto
Thanks Meter: 2
 
More
Quote:
Originally Posted by eriickiller

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!

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/msabpgsjvs...covery_bak.zip
The Following User Says Thank You to GuiSouza For This Useful Post: [ View ] Gift GuiSouza Ad-Free
20th March 2013, 03:45 PM |#98  
OP Member
Flag Campinas
Thanks Meter: 32
 
More
[GUIDE] - Root Blu Dash 3.5 d170
English is not my native language so forgive me for spelling errors.

Quote:

DISCLAIMER: I'm Not Responsible for any damage to your device
echo Caused by these instructions (though it may not happen!).

The tutorial consists of:
  1. Install a recovery.img that enables the temporary root access on the device.
  2. Upload the files su, busybox and superuser.apk system for the device
  3. Install the recovery of the original Blu Dash 3.5

Required Files:
  1. ADB drivers installed
  2. File root_blu_dash_d170.exe - https://docs.google.com/file/d/0B5rQ...it?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.


For those who used the boot Qsmart S12 to gain root access, boot follows the original Blu D170.
https://docs.google.com/file/d/0B5rQ...it?usp=sharing
Attached Thumbnails
Click image for larger version

Name:	screenshot_2013-03-12_12-56-38.png
Views:	368
Size:	34.5 KB
ID:	1819746   Click image for larger version

Name:	screenshot_2013-03-12_12-57-03.png
Views:	375
Size:	20.6 KB
ID:	1819747  
The Following 4 Users Say Thank You to erickreisbr For This Useful Post: [ View ] Gift erickreisbr Ad-Free
20th March 2013, 06:24 PM |#99  
Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by erickreisbr

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



The tutorial consists of:

  1. Install a recovery.img that enables the temporary root access on the device.
  2. Upload the files su, busybox and superuser.apk system for the device
  3. Install the recovery of the original Blu Dash 3.5

Required Files:
  1. ADB drivers installed
  2. File root_blu_dash_d170.exe - https://docs.google.com/file/d/0B5rQ...it?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.


For those who used the boot Qsmart S12 to gain root access, boot follows the original Blu D170.
https://docs.google.com/file/d/0B5rQ...it?usp=sharing

Excellent Guide Erick We thank you for your time and dedication on making this possible.
20th March 2013, 06:40 PM |#100  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by GuiSouza

Hey man, i used this boot, try this...



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

if don't work, the originals are here:

thank you gui, i will try today.

Quote:
Originally Posted by erickreisbr

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



The tutorial consists of:

  1. Install a recovery.img that enables the temporary root access on the device.
  2. Upload the files su, busybox and superuser.apk system for the device
  3. Install the recovery of the original Blu Dash 3.5

Required Files:
  1. ADB drivers installed
    • The driver can also be installed by SuperOneClick v2.3.3
  2. File root_blu_dash_d170.exe

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.


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

great tutorial Erick, chará
20th March 2013, 06:50 PM |#101  
Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by 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.

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 Anyhow, thanks again!!!
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes