yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 2 Themes and Apps] AlbertoSONIC:
It doesn't work for me... In Miniapps i see popup browser with little android and if i open it, it fc....
[Galaxy Tab 2 Themes and Apps] maclx8:
try to replace popupbrowser.apk with pidio1's apk on system/app
[Galaxy Tab 2 Themes and Apps] andrefly:
Can you make a version for CM?
[Galaxy Tab 2 Themes and Apps] tuxafgmur:
No. I can't do.

This app its only for Samsung Stock.
[Galaxy Tab 2 Themes and Apps] marnold425:
Doesnt work on my p113 either just force closes and i tried installing both ways... i see the mini tray icon but it looks horrible and when i tap it nothing happens and a few seconds later it says pop up browser fc
[Galaxy Tab 2 Themes and Apps] bencak:
5110

This is work on tab 2 gt-p5110?
[Galaxy Tab 2 Themes and Apps] fireman9iner:
Yea doesnt work on mine either same as everybody else, anyway way to fix android is upgrading from happening every boot?
[Galaxy Tab 2 Themes and Apps] samsgun357:
Yeah as long as you're running a stock base ROM.

Eat Play Google
[Samsung Galaxy Nexus] mannyvinny:
I've CWM 6.0.2.3 installed.But i think it needs some kind of improvement.To select an option, we need to double touch that option.One for selecting and second for confirmation.This is because there would be less chance u select any other option rather that u want.Example is PhilZ recovery is the best recovery i used on my GNote..

Also, i want to know that which recovery (CWM or TWRP) is the best recovery for Gnex ?I heard TWRP is best alternative for CWM.

Thirdly, I used to restore my call logs and sms through Titanium Backup from CWM backup earlier.But the CWM backup format has now been changed.Instead of creating "backup" folder, contents are now saved in several folders called "blobs".So m left with no option to restore sms from newer CWM backup.

Any solutions or ideas??
[Samsung Galaxy Nexus] EddyOS:
CWM 6.0.2.3 reverted back to the old TAR format so doesn't use blobs any more unless you tell it to
[Samsung Galaxy Nexus] mannyvinny:
what about TWRP recovery?and have u used PhilZ recovery?did u noticed any change?
[Samsung Galaxy Nexus] MIKEYSAKZ:
I am rather new at all things android development but keeping that in mind I have easily backed up, wiped, flashed, installed, and restored no problem using twrp. Tremendously simple to download, install, and use with no hiccups along the way

I would check some videos out on twrp you might find it useful in your decision making on which recovery to use
[Samsung Galaxy Nexus] mannyvinny:
ya..ur rite..i haven't used twrp till now but i heard its better than cwm..so m surely gonna give it a try
[Samsung Galaxy Nexus] EddyOS:
TWRP - I don't like it personally, I always use CWM. PhilZ? Never heard of it...
[Samsung Galaxy Nexus] mannyvinny:
philZ made modified CWM recovery for devices like S2 and GNote..
[Samsung Galaxy Nexus] reysonance:
As far that I know of PhilZ only makes recovery for Exynos-based device, like the original Note, there's no PhilZ for the Gnex. TWRP has all the thing that you've said earlier (And IMHO, more user friendly), but backups aren't interchangeable between the two. So you'll have to get rid of those blobs.
[Xperia Play Themes and Apps] RottenFoxBreath:
I've got a sneaking suspicion that the devs of this, have also played Super Stardust, either on PS3, PSP, or Vita..
[Xperia Play Themes and Apps] joshsarena:
cool

This game is amazing. And its free!!!! must have for All XPERIA PLAY owners.:D great find.

P.S Yes it does show up in the launcher :p
[Xperia Play Themes and Apps] narflynn619:
I'm actually loving it. Forgot to play Wild Blood and MC4 for hours. :D
[Samsung Captivate Glide] risis78:
This is the procedure to use SD Card (FAT32) as internal SD in the Stock ROM (with script made by Mattiadj) for people (like me) that can't install custom Roms:

Requirement: Stock ROM and root

Steps:

- Flash attached zip with recovery

- Download SManager from Google Play

- Open SManager and navigate to /etc/init.d folder

- Click to 11extsd2internalsd

- Ckeck SU and Boot options and then Save

- Reboot

To return to the previous situation and disable the mod as long as you delete the file 11extsd2internalsd from init.d or unckeck Boot option for this file from SManager
[Upgrading, Modifying and Unlocking] erickreisbr:
Update: New guide is in post # 122

http://xdaforums.com/showthread.php?p=40433602#post40433602

The guide is in post # 98

http://xdaforums.com/showthread.php?p=39362805#post39362805

Hello,

I have a Blu Dash 3.5 and would like to install clockworkmod recovery and enable root access, but so far have not found anything. Could you help me?

thank you
[Upgrading, Modifying and Unlocking] erickreisbr:
I tried using SuperOneClick, Gingerbreak, zroot but all without success.

Anyone have any other option?
[Upgrading, Modifying and Unlocking] fenrixarena:
_ _
[Upgrading, Modifying and Unlocking] erickreisbr:
I managed to set up the android SDK on ubuntu but I get permission denied message when trying to copy the files to the /system

I suppose I have to remount the partition in RW to be able to put the files but no idea how to do this.
[Upgrading, Modifying and Unlocking] az0ik:
fenrixarena, hope you get to find any progress on rooting this phone. I also agree with you that it is no worth the time or effort with this kind of phone but I think that the challenge is interesting ;) . In my case I have no idea on how you may root it but I am sure it is possible i guess it all in find another compatible boot.img that can be rooted, right?

Regards,
[Upgrading, Modifying and Unlocking] erickreisbr:
What is the address of the site that charges $ 30? We can verify that other users would like to do and split the cost ...
[Upgrading, Modifying and Unlocking] erickreisbr:
I managed to make root ...

I found the CWM recovery and stock recovery for Qsmart.

I was very curious if it would work in BLU and ended up installing the CWM with fastboot. It did not work, the screen just stays with the BLU and not access the recovery.

Then I installed stock recovery and did not work ...

But I realized that Windows recognized the device connected and I recognized two units with unsupported format.

then returned to the prompt and saw that the ADB was working. I used the command 'adb shell' and to my surprise was how the cursor #

So without wasting time already put su and busybox in /system/ bin and superuser.apk in /system/app, I changed the permissions and restarted the phone. And the root was working perfectly. :victory:

Only one problem, I do not have the recovery installed.

I wonder how I can help you to make root without losing recovery
[Upgrading, Modifying and Unlocking] erickreisbr:
I use Windowns 7 Pro x64 bits.

I installed the drivers in the SuperOneClick version 2.3.3.

With the drivers installed could use fastboot and adb command.

Turning on the phone + vol - access mode fastboot / bootloader

It would be good to get root without losing the recovery. Because we need him to compile a clockworkmod recovery.

I used the romdump and got the following files:

https://docs.google.com/file/d/0B5rQL4bfhfPRZXhhZkg1Mkx5SHc/edit?usp=sharing

I used the mkfs.yaffs2 to convert the file system.tar for system.img

https://docs.google.com/file/d/0B5rQL4bfhfPRMGdaNnQ4b1RwclU/edit?usp=sharing

This system.img would function on another device?
[Upgrading, Modifying and Unlocking] fenrixarena:
okay, I am having one problem, what did you type for the permissions?

I've got superuser.apk pushed and the su in the /system/bin but when i try to chmod 777 it returns to -r- after I reboot!

Here's howto manually back up now that I have recovery adb root:

cat /proc/mtd

Then just cat (mtd#) > /sdcard/(image.img)

You can restore via fastboot flash
[Upgrading, Modifying and Unlocking] erickreisbr:
you get root access in adb shell?

send su to /system/bin with permission 6755.

busybox to /system/bin with permission 755.

and superuser.apk to /system/app with 644.

reboot your phone

then download terminal emulator on your phone and enter the command su

if the cursor change to # worked
[Upgrading, Modifying and Unlocking] az0ik:
These are actually good news... Right on!!! Cheers if you manage to root Blu Dash 3.5 :victory:

Can someone guide me on how I can Root my phone? What adb tools do i need?

Regards
[Upgrading, Modifying and Unlocking] fenrixarena:
I can upload the cwm.img & adb I used + fastboot. Not all adb.exe will recognize the phone. Also drivers from qsmart for adb bridge.

1 boot holding vol down + power (about 15 sec.)

Fastboot flash recovery cwm.img

Then turn phone off.

Boot holding vol UP + Power (about 15 sec)

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

reboot your phone

terminal emulator - su

permission granted

IT WORKED!

:)

---------- Post added at 02:21 AM ---------- Previous post was at 02:00 AM ----------

sorry, tomorrow I will upload a zip with the img i used and so forth all in one zip so you can root with that, unless it's here by someone else by then I gotta work!
[Upgrading, Modifying and Unlocking] az0ik:
Thank you so much Fenrixarena!! You are awesome :good::good::good:. I still can believe it, i thought it was a lost hope... I really appreciate for uploading the files I am patient enough to wait another day ;)
[Upgrading, Modifying and Unlocking] erickreisbr:
Follow the ADB and the recovery I've used.

The drivers installed by SuperOneClick, but have these here:

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

64 bits - http://www.mediafire.com/?1hrwo325cb1ej2w
[Upgrading, Modifying and Unlocking] fenrixarena:
Fx
[Upgrading, Modifying and Unlocking] erickreisbr:
the root worked on your phone?

Now we need a recovery. I'm trying to learn how to compile cwm, but it is very complicated.
[Upgrading, Modifying and Unlocking] az0ik:
Why does the Blu Dash doesn't come with a CWM Recovery? Most of androids devices have it pre installed, right?

I am trying to understand this, erickreisbr, you are trying to inject cwm to q12 rom? have you checked in the Vietnamese forum if they have a Rom

that has cwm pre installed?
[Upgrading, Modifying and Unlocking] erickreisbr:
az0ik,

Normally the android comes with a basic recovery where only allowed to install packages provided by the manufacturer.

The clockworkmod recovery is more advanced with it we can apply various packages that insert applications, such as root, and even custom roms.

The Q-S12 smart hardware is almost identical to the 'Blu 3.5' and thus I ventured cwm recovery install it on my device. The recovery did not work but he got access to the files /system may then include su, busybox and superuser.apk in /system device enabling root access.

If the recovery of s12 ran on blu we could install a package that would enable the root.

It would be good to get root access without losing the original recovery because then we could extract the recovery and try to build a cwm for our model.
[Upgrading, Modifying and Unlocking] fenrixarena:
Yeah, I forgot. But, couldn't one of us had sent az0ik a rooted system.img & had him do:

Fastboot flash system /sdcard/system.img

Then from the terminal on the phone use "cat" to >(send)mtd6(recovery) to the sdcard, then we would have the original recovery?

Although using the cat command from the nonworking rooted cwm recovery like I said we can still backup manually by cat > each mtd partition for a backup

But there are no roms unless someone is going to build one

So i dont see the point in having a recovery at all
[Upgrading, Modifying and Unlocking] az0ik:
So, without a cwm recovery we don't have a complete rooted phone? Or its really not a "must have" and i am good to go with rooting the phone with the uploaded files by erickreisbr?
[Upgrading, Modifying and Unlocking] fenrixarena:
Technically, yes it will be rooted, you can run root apps & modify the system. I stripped 'bloatware' and deleted the dalvik cache, and used a cache cleaner app to identify & remove the old data files from the removed bloatware, I freed 30+mb of space, I will put the apps I dl'd into the system/app folder because my phones always run faster that way for as many apps will work that way.

What we do not have is S-OFF basically, as we cannot get an adb shell from usb debugging. Although as I stated since su works in the terminal it is possible to do anything from there such as cat>mtd /sdcard/img

If you want to salvage the recovery for us I can remove all personal data & send you a rooted system.img so u can flash that from fastboot instead of recovery, all it will do is add su and superuser.apk & busybox is installed

Then you can do cat > mtd6 /sdcard/blustockrecovery.img so the original recovery can be salvaged for hopeful modification.

---------- Post added 14th March 2013 at 12:07 AM ---------- Previous post was 13th March 2013 at 11:54 PM ----------

Okay,here's the correct commands

Cat /proc/mtd

Shows the mtd table

If you do like I said you can get the recovery via

cat /dev/mtd/mtd6 > /sdcard/recovery.img

From a terminal emulator on the phone.

It's up to you how important salvaging the recovery is.
[Upgrading, Modifying and Unlocking] erickreisbr:
Indeed cwm is not necessary for root access ... But it is necessary to facilitate backup, restoration and installation of roms.

The system.img I posted is the original android system image with root access enabled.

To install the phone you must:

1 - Unzip the ADB.zip I posted to the c:\ADB

1 - Enable debug mode on the device;

2 - Connect your phone to your PC and install the ADB drivers;

3 - With the drivers installed open the command prompt and access the folder c:\ADB.

Use the command 'adb devices' and verify that the device is recognized

4 - If you must reincia was recognized it in fastboot mode. Use the command 'adb reboot bootloader' or turning off the device and turn it on by holding vol - by 10s. the unit will stay with the BLU logo on the screen.

5 - Use the command 'fastboot devices' and verify that the device is recognized.

6 - Download the system.img and put it in the folder c:\ADB.

and install it using the command: 'fastboot flash system system.img'

7 - After restart with 'fastboot reboot'

DISCLAIMER: I'm Not Responsible for any damage to your device Caused by these instructions (though it may not happen!).
[Upgrading, Modifying and Unlocking] fenrixarena:
Lol, yep, then he has posted the system.img YAY! Yeah, so do that then download the terminal emulator and do the commands

su

cat /dev/mtd/mtd6 > /sdcard/recovery.img

Then post that recovery so we can put our stock recoveries back on! :)
[Upgrading, Modifying and Unlocking] az0ik:
Got it... You could not explained it better :good: Thank you so much. As for the Disclaimer LOL. I would worry if i was to do this on a Galaxy S3 :p

---------- Post added at 08:52 PM ---------- Previous post was at 07:56 PM ----------

fenrixarena, just let me get this straight, after I proceed with the steps posted by erickreisbr to load the system.img (the 180MB file, right?) I should run the command to backup the recovery.img? :confused: Sorry for being such a noob, but what is the difference between the system.img and the recovery.img.

I am doing this tomorrow and I will upload the recovery.img from work, because internet access is much faster there (10MB clear channel) so that you can download the recovery.img ASAP. :victory:

Regards
[Upgrading, Modifying and Unlocking] fenrixarena:
The system.img is simply a packaged file with everything that is under the /system folder on the root of the phone.

The recovery is what it boots to when buttons are being pressed.
[Upgrading, Modifying and Unlocking] fenrixarena:
http://builder.clockworkmod.com/
[Upgrading, Modifying and Unlocking] erickreisbr:
I saw this site and why I want the stock recovery.
[Upgrading, Modifying and Unlocking] az0ik:
Did not work :( phone reboots when trying to load android OS and stays in an infinite loop. Any advices on what to do??? I've fallowed all the steps from step 4 until 7, because adb did not recognized the device. I had to go in fasboot mode so that i could load the system.img.
[Upgrading, Modifying and Unlocking] GuiSouza:
Problem

My device also enters into an infinite loop ... what should I do to restore? :(
[Upgrading, Modifying and Unlocking] erickreisbr:
I'm uploading a new dump system.img. Once finished I'll post the link.
[Upgrading, Modifying and Unlocking] GuiSouza:
with that Dump System I can restore?

I will be forever grateful :)

---------- Post added at 10:27 PM ---------- Previous post was at 09:51 PM ----------

Sorry about poor english, i'm from Brazil.

...

I tried to restore other image files, but it still fails.

When u finish upload i will try again :)

thanks!
[Upgrading, Modifying and Unlocking] az0ik:
Thank you erickreisbr, you sure are a lifesaver :highfive::highfive:
[Upgrading, Modifying and Unlocking] GuiSouza:
YEP \o/
[Upgrading, Modifying and Unlocking] erickreisbr:
As I promised follows the new system.img

https://docs.google.com/file/d/0B5rQL4bfhfPRR0JnZXFQQWFvNlU/edit?usp=sharing
[Upgrading, Modifying and Unlocking] GuiSouza:
look this error >>> Image File

:(

---------- Post added at 08:38 AM ---------- Previous post was at 08:34 AM ----------

migre , me / dGBBR

"replace the comma by dot, remove spaces"

---------- Post added at 08:52 AM ---------- Previous post was at 08:38 AM ----------

Error say:

FAILED (data transfer failure (Too many links))

finished. total time: 56.121s

:rolleyes:

---------- Post added at 09:26 AM ---------- Previous post was at 08:52 AM ----------

I went back to the first file. IMG posted in this topic, and I've read articles related to Boot LOOP,

but still have no root, ie'm disoriented

I do not know what to do :(
[Upgrading, Modifying and Unlocking] erickreisbr:
I checked other posts and this error was solved by changing the usb cable.

Try swapping the usb cable and plug it into the computer's rear doors.
[Upgrading, Modifying and Unlocking] GuiSouza:
C:\Users\Guilherme>C:\Users\Guilherme>cd C:\Android\sdk\platform-tools

C:\Android\sdk\platform-tools>cd C:\Android\sdk\platform-tools

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 flash system system.img
sending 'system' (225280 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 59.246s

C:\Android\sdk\platform-tools>

I tried both of my USB, but return the same error :(

---------- Post added at 11:04 AM ---------- Previous post was at 10:27 AM ----------

format or wipe data would be a solution? I don't understand nothing :/
[Upgrading, Modifying and Unlocking] erickreisbr:
if you plug in recovery mode adb recognizes the device?
[Upgrading, Modifying and Unlocking] az0ik:
That is correct. Try using the fastboot mode and it should flash the system.img. I am currently downloading the .img file...Thank you erickreisbr for uploading it :good:. I'll post later on how it goes with this img.

---------- Post added at 08:47 AM ---------- Previous post was at 08:19 AM ----------

erickreisbr

Did not work :crying: got the "data transfer failure (Too many links)" message. I've try 3 different usb cables and I wiped data and erase previous system.img uploaded before flashing and still same problem...

From the Vietnamese site i downloaded a Chinese system rom and it boot it my phone, the only problem was that it was in Chinese and both sim slots did not work (did not recognize my carriers)

Any other suggestions or solutions???
[Upgrading, Modifying and Unlocking] fenrixarena:
Pud
[Upgrading, Modifying and Unlocking] az0ik:
Many thanks Fenrixarena for the suggestion. Erickreisbr, can you please help us with this so that we can flash with the correct system.img?

Regards,
[Upgrading, Modifying and Unlocking] erickreisbr:
Your recovery mode work?

If so I created a update.zip to install via recovery.

https://docs.google.com/file/d/0B5rQL4bfhfPRbnpVQ29FSng0ZFE/edit?usp=sharing
[Upgrading, Modifying and Unlocking] az0ik:
I tried to install via the Android system recovery <3e> through the "apply update form sdcard' and I get an error that says signature verification failed.... installation aborted
[Upgrading, Modifying and Unlocking] erickreisbr:
The device is recognized by adb when in recovery?
[Upgrading, Modifying and Unlocking] az0ik:
No, my devices is not recognized by adb only in fastboot mode.
[Upgrading, Modifying and Unlocking] GuiSouza:
My device too, adb recognize only in fastboot mode :/

---------- Post added at 04:00 PM ---------- Previous post was at 03:44 PM ----------

I tried use the Recovery img on my Blu Dash, but when i start with power + Vol+, the screen becomes white
[Upgrading, Modifying and Unlocking] az0ik:
erickreisbr, can you please upload an .img file instead of the .zip?
[Upgrading, Modifying and Unlocking] erickreisbr:
https://docs.google.com/file/d/0B5rQL4bfhfPRcHRnQUVQbThyQnc/edit?usp=sharing
[Upgrading, Modifying and Unlocking] GuiSouza:
same error

is it not because of the file size?

compared with the first system.img posted, there is a pretty big difference> before 184mb, and now 225mb.

Will the phone supports system.img with that size?
[Upgrading, Modifying and Unlocking] az0ik:
Erickresibr, I get the seme error:

:(
[Upgrading, Modifying and Unlocking] GuiSouza:
that curious ... when I type "fastboot devices", nothing shows up, but when I type "adb devices", it appears the serial, is there a difference?

Editing:

I see the diference :) sorry, im noob LOL

you are in "bootloader mode" from fastboot
[Upgrading, Modifying and Unlocking] erickreisbr:
The 184mb file I extracted the script romdump.

and the 220MB file with the command cat /dev/mtd/mtd1> /sdcard/system.img

220MB is the full size of the partition / system and 184mb is the space used.
[Upgrading, Modifying and Unlocking] GuiSouza:
i understand :)

so, i will go home because im at work... then will dedicated my time to recovery the phone, see ya!
[Upgrading, Modifying and Unlocking] az0ik:
Ok. But, what are we doing wrong that it does not load the img file to the partition, if so is the case? Because, you followed this instructions by fenrixarena:

???

So I am really stuck here :( I don know what to do....
[Upgrading, Modifying and Unlocking] fenrixarena:
I've switched to a new phone, I would gladly sell my root blu dash 3.5 :) I'm sorry, you prolly should have just rooted your phone.

oh, ya know what else might be a good idea would be to erase that partition before writing to it so it's clean.
[Upgrading, Modifying and Unlocking] az0ik:
How do i do that? Erase the partition...
[Upgrading, Modifying and Unlocking] erickreisbr:
Here is a new file.

https://docs.google.com/file/d/0B5rQL4bfhfPRX21nQ25nM3VISEE/edit?usp=sharing

Unpack and install with fastboot. Use fastboot erase system before the flash.
[Upgrading, Modifying and Unlocking] GuiSouza:
Progress result:

^C
D:\Users\Guilherme\Desktop\Android\ADB>fastboot devices
MSM7625ASKU3 fastboot

D:\Users\Guilherme\Desktop\Android\ADB>fastboot erase system
erasing 'system'... OKAY

D:\Users\Guilherme\Desktop\Android\ADB>fastboot flash system new.img
sending 'system' (188297 KB)... OKAY
writing 'system'... FAILED (remote: flash write failure)

D:\Users\Guilherme\Desktop\Android\ADB>

Editing:

I tried both of my USB ports... all show me the same erro of writing :/
[Upgrading, Modifying and Unlocking] az0ik:
Same here.... :crying:
[Upgrading, Modifying and Unlocking] GuiSouza:
hey, which version of your recovery mode?

---------- Post added at 11:28 PM ---------- Previous post was at 11:13 PM ----------

My "Recovery Mode" stopped working, so I tried to flash the recovery.img that posted here ... When I try to go into Recovery Mode, the screen goes completely white.

What should I do?

sorry for the low quality, I'm using a webcam...
[Upgrading, Modifying and Unlocking] az0ik:
Try this one:

This is the QSmart S12 Recovery which should work with the Blu Dash
[Upgrading, Modifying and Unlocking] GuiSouza:
thanksssssssssssssssssss!!!!

It worked :d