yashsingh1/xdaforums huggingface dataset:
[iPAQ rw6828, XDA Atom General] shdamaj:
i had a HP IPAQ HW6945 with built in internal GPS module, i had dowload the google map directly to it via GPRS, the question is that the site ask me about my device, i enter it correctly then i found in the menu tab "locate me", i tab it and i found a blue spot on the screen then i realies that it locate me exacly where i was standing:p ,

i had now an Atom EXEC that doesn't had a built in GPS:( , but i think you must download the proper google map of your device and be awear to properly configure your GPS settings.

a review on google site shows that there is some work to do to make location finder work not only via GPS but also through your neerest location of a Signal Antena of your network provider, WIFI hotspot. but this is under test till now:cool:
[iPAQ rw6828, XDA Atom General] trjons:
I am interested in this subject as well.

I am using an Atom Life in Los Angeles and have the latest version of Google Maps (2.0.1.18).

My location is not available according to the phone. There has to be a hack or a tweak to get this to work since it works on every other WM phone I've tried.
[iPAQ rw6828, XDA Atom General] Phrak:
I don't believe the issue has anything to do with Google Maps support for a particular device.

Case in point: I run the HP RW6828 with Windows Mobile 6.1 Pro (PDAViet ROM v 2.03.03, CE OS build 5.2.19400) with the latest radio stack (v R060822N_MN1ARC_RS00052) and Google Maps Location feature doesn't work on my device.

Happy to be proven wrong!
[iPAQ rw6828, XDA Atom General] Phrak:
Ok so I've made a bit of progress.

See here for a very minor success:

http://xdaforums.com/showthread.php?t=398839
[XDA Assist] Usama Amir Rana:
I have S5 Active G870a with custom rom 5.0.1. I need 6.0.1 Custom Rom or RR Rom or Any Nouget Rom stable one. Please help if you know.
[XDA Assist] sawdoctor:
Greetings and welcome to assist. Unfortunately there does not seem to be any mm custom roms for your variant on xda. There is a guide here if you would like to try yourself

https://xdaforums.com/chef-central/android/guide-android-rom-development-t2814763

Good Luck

Sawdoctor
[General Questions and Answers] sliderfan:
Hi all.

I've been searching the net for hours for a solution to this issue, to no avail. :(

I have an Asus Slider SL101 that I wanted to upgrade to KatKiss so here's what I've done...

- Root successfully (1-click transformer root 1.1 from here: https://xdaforums.com/showthread.php?t=1689193)

- Installed CWM Recovery (6.0.1.3) successfully (also using above)

- put all the relevant zips (katkiss, gapps, slider comp pack) on the sd card ready for flash

- booted into recovery...

Next I went to wipe data/factory reset... but it froze so I did a hard boot and tried again: same thing.

So I went to install the rom zip from sdcard and I get error message 'can't mount /sdcard/'

Also getting 'error mounting /data' and 'unknown volume for path [/sdcard/].

I can't get back to my original Android settings at all, I'm assuming it's all gone or something. Maybe the reset did work.

The big issue is I can't access the damn zip files on the sd card to install a rom.

I have these ADB tools (with adb and all these random executables and various files scattered about) but if I can't start Android then I can't use them can I?

It's a bit of a mess really. I'm thinking if I can just get the slider to mount the sd card then I can install the rom and I should be back in.

I'm not sure how to go back to stock recovery (whatever that means) so if you advise that I should 'flash' then I'm afraid I'm going to need some clear instruction.

Stupidly, I forgot to do a backup, which is probably half the reason I'm here, although that still doesn't account for the sdcard error...

Anyway, please help a moron out? :(
[General Questions and Answers] Jebedia:
))

Ive got the same problem. CWM cant mount the sd card. Ive been searching for days, but all the links in any solution i did find are outdated. I did read somewhere that it means that the CWM version isnt compitable with the Sl101. I can't find any other/older versions then the Manager i downloaded from Playstore. I want to flash the Twrp Recovery and then the kisskat ROM, compability pack.. Gapps

.etc but i cant seem to get any of that done if CWM can't mount the damn sdcard. (Sorry i got a bit frustrated over this). Ive never rooted anything before so im new to this. Did anyone find a solution for this? Or has an link to some other version of CWM that is compitable to mount the sdcard? Thank you very much in advance:))
[General Questions and Answers] sliderfan:
Probably not what you wanna hear, but I didn't find a solution and had to throw my beloved slider away! :(
[Android Apps and Games] armnomads:
Sky Spin is fancy minimalistic one tap game.

Change direction to avoid obstacles and keep from falling off the platform! Collect gems to unlock all of the characters.

FEATURES

◉ One Tap Controls

◉ 25+ Different Characters to Unlock

◉ Minimal Art

◉ Ambient Soundtrack

◉ Leaderboards

Google Play Market: https://play.google.com/store/apps/details?id=com.armnomads.skyspin

Follow Us:

Facebook - http://www.facebook.com/armnomads

Twitter - http://www.twitter.com/armnomads
[Android Apps and Games] armnomads:
Our other Games in Google Play: Noble Run and Cubway
[BLU R1 HD Guides, News, & Discussion] mrmazak:
BLU R1-HD bootloader unlock script tool, and TWRP install tool.

Download is a zip file, unpack it to somewhere you will remember. Run the dirty-cow-tool.bat // mtk-su-tool.bat

The included files and folders are set to hidden, in effort to keep them safe from accidental delete.

Must have adb+fastboot + drivers installed and setup prior to using tool

Easiest method to install adb + fastboot on windows is with "15 second adb + fastboot install TOOL"

LINK==>ADB+FASTBOOT

It is for windows

In linux :

"sudo apt-get install android-tools-adb"

"sudo apt-get install android-tools-fastboot" Some fastboot commands were missing when i used this one ie "fastboot flashing get_unlock_ability"

"sudo apt-get install fastboot" worked better when I tried. ( i used that command as a check before doing the unlock, so it was needed only for that check)

Using Tool

On Windows?

Unzip the downloaded file to a new folder, open new

folder and click on "dirty-cow-tool.bat". // "mtk-su-tool.bat"

Do the steps in order (1-2-3-4) to be unlocked, then

Step (5) to get to second page where step (1) is root

The rest is optional

On Linux?

Unzip downloaded file to new folder folder .

Open folder. Then open R1-Linux-tool-v2 folder

Open terminal from that folder and type

" . R1-HD-TOOL.sh "

Same order of steps (1,2,3,4) step (5) for extra

Steps (1 on second menu) for superSU root.

Second menu steps (2,3,4,5,6,7,8) are optional.

**Linux Note**

The tool uses "fastboot flashing get_unlock_ability" as one of the methods to check before doing the unlock.

The version of fastboot that installed with "apt-get install android-tools-fastboot" did not recognize

this command. But "apt-get install fastboot" updated some version and then the command was recognized.

******OTHER NOTES****

--- this has been mentioned in the general thread and the modified v17 thread, but It has come up again so I wanted to make note of it.----

--- The newest blu versions (V7.4.2 and V17) Have made changes to "toolbox" and this effects things like "adaway" and "titanium backup"

--- The suggested fix is to install busy-box. I have had success with the version from play store, some prefer to use f-droid version. Either one will do. Install it and open the app. From in the app you need to do an install.

CHANGE LOG

Credits to @Diplomatic for his work on the Mtk_su that I used used to make this tool work again after Dirty-Cow was patched.

DOWNLOAD LINK

Preferred to use the Downloads tab of this thread.

Archived downloads on android file host also == link

XDA:DevDB Information

R1-HD Dirty-cow Unlock Tool, Tool/Utility for the BLU R1 HD

Contributors

mrmazak, vampirefo for his recovery, lopestom for his recovery, emc2cube for his debloat zips, christianrodher for his dirtycow method,

Source Code: https://github.com/mrmazakblu/DirtyCow-R1_HD

Version Information

Status: Testing

Current Stable Version: V11

Stable Release Date: 2017-04-11

Current Beta Version: MTK-SU

Beta Release Date: 2019-04-14

Created 2017-02-22

Last Updated 2019-04-18
[BLU R1 HD Guides, News, & Discussion] mrmazak:
Reserved

Items planed to be addressed in next release:

--Add few more file integrity checks to the extra's page

--Add copy log to clipboard option so it is easier to post log entry if needed-------*********----already-_added to github copy of batch file

--Add a verification step that checks what recovery is installed( to prevent trying to do steps on extra's page with stock recovery)

--Possibly move to a "fastboot boot recovery" instead of "adb reboot recovery" for the same reason as above

--Add wget or similar to the extra's items so initial "TOOL" size is smaller (not that 40-50MB is big, but to some it may be )

--Add additional "selinux mode changer apk" for fm radio install rather than just the note that says it needs to be found.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
Reserved
[BLU R1 HD Guides, News, & Discussion] nickstewartroc:
Works great on OEM 6.6, thanks for the tool!
[BLU R1 HD Guides, News, & Discussion] theredbaron1834:
So I got the one-click-root.sh done, maybe. Can some linux users go over it, make sure I didn't do anything stupid? I don't exactly have a device to check it with atm, and I am not pro with scripting, barely novice, so it is a pretty basic conversion of the batch file. Still, it might work :). Just would like a few eyes on first.

https://github.com/theredbaron1834/Scripts/blob/master/one-click-root.sh

Also, I looked at dirty-cow-tool.bat. However, wow, more an advanced batch file, and I am not sure what the first half does, so not sure how to convert :(. However, it seems if anyone does get it, the eqiv of goto for linux is funtions. simple cheatsheet:

function stuff {
echo "this stuff is run via the function"
{
stuff #goes to stuff and runs function
[BLU R1 HD Guides, News, & Discussion] mrmazak:
thank you for your input.

As far as the begining of the batch, It is adding a few folders to the "path" variable so help ensure the "adb push" commands find the files it is trying to push. Then it sets some folder "flags" to hidden so that the files the batch needs don't get accidentally moved or changed. Then the large section with mostly "echo" that is to set up the "simulated" G.U.I.

The lines of just "::::::::::" are simply used to help with reading the batch file. i use them to seperate functions. They are not needed.

The lines with only 2 "::" are standard windows comment / remark line entries

The lines with 1 ":" are the beginning line of the loop/ function == the line that "goto *" searches for
[BLU R1 HD Guides, News, & Discussion] khyr:
Does Works to unlock 7.4.2?
[BLU R1 HD Guides, News, & Discussion] mrmazak:
It is supposed to. It is the same base codes used from original script, and that one was confirmed to work. I Do not have first hand use of V7.4.2 so it is only confirmed through other users.

The dirty-cow being used has been patched by google in Dec but blu has not rolled out the patch. So there is no reason for it not to work.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
edit:

I have the linux version ready.

-the first step, (ADB Push) is ready. including md5 file checks

-step 2 is ready= running dirty-cow with md5 check before final writing to mmcblk device

-step 3 is ready unlocking bootloader = including check if unlock is done, but need to fix the "unlock_adility" check

I can make to file to compare and grep the line needed, but cannot "sed" the extra information or do a > < comparison

-step 4 is ready .--flash twrp

Finished 90% of tool.

still need to tweek the log feature.

I ran tests on the lop back to menu and test ran

1. push files for dirty-cow and md5 check . then made push fail to verify the check method was valid ==pass

2. run dirty cow commands and md5 verification on resulting file. ==pass

3.unlock bootloader --- I ran it (needed to fake the already unlocked check) it works == pass

4 . flash twrp --installed both version i have, both install fine ===pass

5 extra menus -- ran . install su-----debloat---rebloat--- add fm radio--- preloader roll back =====all pass

(bootloader roll back needs manual intervention to re-enter fastboot during the boot loop that is unavoidable)

6. instruction ====not written yet

7. exit yes it closes == pass

8. logs --- needs completeing
[BLU R1 HD Guides, News, & Discussion] torchredfrc:
I just loaded this on my OTA updated 7.4.2 device. I would note that the batch file does not actually create the /sdcard/Download folder so you might need to go into the terminal and actually create this on your sdcard... also worth noting that this batch file **requires** an sd card in the device to do any of the loads in the "5" menu.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
no it does not.

the /sdcard is the internal memory and the Download folder is already there.

you might be having issues but the folder is already part of normal system
[BLU R1 HD Guides, News, & Discussion] torchredfrc:
Fair enough, my restore didn't have /sdcard/Download and I made an assumption that /sdcard was my mounted card. Thanks for the insight.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
OOPS

found typo on V4 of tool. batch files sets variables for "return", from loop functions. And two returns were set to same label9, so if you had tried to do extra's menu option #8. "ROLL Back Preloader" , instead it was running option # 5. " MTK_BLU Debloat v2"

fixed and still reading and re-reading to search for errors.

This looks bad.

The reason I put together this tool was I felt it was important to make a way to minimize the problems usually associated with android modifications. By making "typo's" a thing of the past, and I found them in my own script.

re-posted V5 combined with linux V2--
[BLU R1 HD Guides, News, & Discussion] gabriel986:
I'm a total noob, and I'd like to know how to proceed with the supersu and all the other parts of step 5. Thank you
[BLU R1 HD Guides, News, & Discussion] mrmazak:
Ok. After you have completed upto twrp install. You can do the options on #5. It is all programed and automatic. What is does is put zip files onto the phone and reboots phone into recovery, then recovery installs them.
[BLU R1 HD Guides, News, & Discussion] gabriel986:
I get up to the recovery installation, but then I can not access such recovery on the phone, If I turn it on with power+vol up, it takes me to the default factory recovery by blu.

And If I try to the super su step with the phone on, it resets it, and get it to the screen with the dead android, while the script just shows the ADB DETECTED message.

In case it's needed, my R1 HD is running on

BLU_R0010UU_V7.4.2_GENERIC 09-11-2016 13:38
[BLU R1 HD Guides, News, & Discussion] mrmazak:
You missed a step in the process.

As tool finishes the recovery install it comes to a "pause" in the script, you need to hold the volume up button on phone "before" pressing button on pc keyboard to continue.

If phone does a normal reboot at this point then the system will replace the newly installed recovery with the stock one.

Giving you the situation you have now.

This step I cannot control, you must press volume button on phone to get the boot menu, and directly boot into recovery to ensure that the install sticks.
[BLU R1 HD Guides, News, & Discussion] gabriel986:
trying again....

for how long should I press the volume up key?
[BLU R1 HD Guides, News, & Discussion] mrmazak:
When tool says Hold button , keep it held. Then continue the script. Phone should reboot to the boot menu. Then let go of volume

Some phones do not accept the fastboot reboot command, on those phones need to hold power to shut off. Then volume and power together to come on, release power when screen come on
[BLU R1 HD Guides, News, & Discussion] gabriel986:
ok.. trying again

---------- Post added at 02:00 PM ---------- Previous post was at 01:46 PM ----------

it beat me!

I get stuck in that part of the process, If anyone uploads a video to check what i'm doing wrong, I'll be grateful.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
This should be easy if you copy the contents of the tool v11 folder into the minimal adb folder.

From your screenshot it is

C:\Program Files(x86)\Minimal ADB and Fastboot

Once the files are in that folder I think it will work.

Of course if you add that folder location to system "path" than it should work from anywhere.

But that's a class for another time.
[BLU R1 HD Guides, News, & Discussion] Krixux:
Problem solved

Thank so much for your time and help mrmazak.

As you said I copied all the content of the tool folder and pasted into the minimal adb-fastboot folder and everything went right.

Then I followed 1-2-3-4 steps and unlocked the bootloader with no problem at all, later I installed TWRP manually as you mentioned in your post and now I'm downloading Modified_rom_R1HD_7.4.2.zip.

Thank you so much for your post. I did not have any issue while running the tool
[BLU R1 HD Guides, News, & Discussion] aacm88:
So I reinstalled the VM and started again the whole process, still no clue, lets see if I can upload a picture this time.

https://postimg.org/image/kw4kd8ekz/

[IMG="Screenshoot command pront"]https://s21.postimg.org/wl8k175jr/Screen_Shot_2017-04-25_at_5.12.10_PM.png[/IMG]

imagen jpgcertificity.com

(Windows 8.1 on Virtual Machine and Blu R1 HD 16g Version 6.6)

---------- Post added at 09:40 PM ---------- Previous post was at 09:39 PM ----------

So I reinstalled the VM and started again the whole process, still no clue, lets see if I can upload a picture this time.

https://s21.postimg.org/wl8k175jr/Screen_Shot_2017-04-25_at_5.12.10_PM.png

https://postimg.org/image/kw4kd8ekz/

[IMG="Screenshoot command pront"]https://s21.postimg.org/wl8k175jr/Screen_Shot_2017-04-25_at_5.12.10_PM.png[/IMG]

imagen jpgcertificity.com

(Windows 8.1 on Virtual Machine and Blu R1 HD 16g Version 6.6)
[BLU R1 HD Guides, News, & Discussion] aacm88:
UPDATE OVER HERE:

I was able to follow the advice you gave to Krixux, about copying the tool in the adb folder, I wasn't using minimal adb, I was using the 15 sec adb, so I located the folder and copied the tool there.

I was able to see the menu of your tool, but when I started it says that there is not connected devices even thought that I run the command "fastboot devices" on cmd it says there is a device.

[IMG="Screenshot 1"]https://s11.postimg.org/pphc4wrsz/Screen_Shot_2017-04-25_at_6.40.04_PM.png[/IMG]

[IMG="Screenshot 2"]https://s24.postimg.org/mb3ksgqx1/Screen_Shot_2017-04-25_at_6.46.18_PM.png[/IMG]
[BLU R1 HD Guides, News, & Discussion] mrmazak:
I think it is result of same problem I mentioned before.

The way the script looks for device is to write to a file, and then search that file. But your last post showed it could not make the file. And with no text file the script thinks no device.

I am working on a modified script for you.

take this .txt file and change it to a .bat file, put it in the folder where the other dirty-cow-tool file is and try to open and run it.

When you try to run tool , and it fails. Look in the folder that you run it from for a new folder called "working" and look at files inside. If the folder is not there or it is empty, this will give you the problem of "no connected device"

Please get newest version of tool downloaded from in you windows VM and unzip the download right in the download folder. And try to use it from there.
[BLU R1 HD Guides, News, & Discussion] libyandroid:
I had the same problem and solved it

I faced the same problem and tried every thing and no luck. then I solved it by two things. I moved the minimal adb folder to drive D or E in my pc and copied the content of V10 to the same folder and also edited the .bat file and I replaced every Blu_R1_HD in the file to R1_HD and everything worked fine after that.

do as I did and it will work. if you have any problem tell me and I will upload to you the folder worked for me with all its contents so you just put it in your D drive or E drive and will work for you.

sorry for my bad english
[BLU R1 HD Guides, News, & Discussion] White_Lion:
Great work! I used the tool and have no poblem in any of the steps, everything worked perfect and now i'm rooted, debloated and even with fm radio with just one .bat, thanks for this amazing tool.

I just had problem conecting my device to adb-fastboot (i just received, haven't made modifications to it before) but this is not tools fault, is a driver thing and i solved thanks to this driver https://xdaforums.com/showpost.php?p=67927242&postcount=23, my device was showing as "unknown device" and just manually installed that driver, then in fastboot mode asked for another driver, just go to device manager in windows again, rigth click on MTP and click update driver, select update manually from a list, then select Android Device and will show 3 selections, the correct is Android Fastboot Interface...and you're ready.

Thanks again.
[BLU R1 HD Guides, News, & Discussion] atari2600a:
V9 does not work with arch's usually-up-to-date adb/fastboot/d, usually located in /usr/bin, same as the ubuntu packages.

V11 includes the linux binaries but no script

Can someone fix please?

V9 gives me 'no such file or directory' on something or other along the lines of working/adb_devices.txt

Also, not sure if related, fastboot gives me this:

atari2600a@TARDIS:~/Downloads/Tool9$fastboot continue
resuming boot...
FAILED (remote: not support on security)
$

---------- Post added at 12:08 AM ---------- Previous post was at 12:06 AM ----------

I'd take a whack at it myself but the security stuff in android gives me a big headache & I make a general rule not to program in brickable environments.
[BLU R1 HD Guides, News, & Discussion] mrmazak:
I have made no changes to linux side. I do not run linux normally,. Only a vm once in a while.

Just try to put the v-9 script in the v-11 folder.

Not sure what that fastboot continue message is about. But on windows, the continue and reboot commands fail on v6.6 and above. That is one of the lesser talked about changes that the OTA made.

It is a change in the lk.bin (boot loader)
[BLU R1 HD Guides, News, & Discussion] atari2600a:
Same result

Please enter your choice number: 1
./R1-HD-TOOL.sh: line 10: working/adb_devices.txt: No such file or directory
grep: working/adb_devices.txt: No such file or directory
no detected devices
trying to return from fastboot
./R1-HD-TOOL.sh: line 28: working/adb_devices.txt: No such file or directory
grep: working/adb_devices.txt: No such file or directory
./R1-HD-TOOL.sh: line 36: working/fast_devices.txt: No such file or directory
grep: working/fast_devices.txt: No such file or directory
No Fastboot devices found
press enter to exit

Out of curiosity where is this 'working' folder supposed to point to?

---------- Post added at 12:41 AM ---------- Previous post was at 12:40 AM ----------

Maybe I can make a symlink or something
[BLU R1 HD Guides, News, & Discussion] mrmazak:
"working" folder is supposed to be made by the script in same folder the script is in.

Edit

just looked through the shell and it does not have the mkdir command. (oops)

just need to add a folder in the same directory as the main shell.'
[BLU R1 HD Guides, News, & Discussion] waylonh:
I would really like to uninstall some system apps such as Blu Help and Email...

However, after following these instructions, I was able to complete all of the steps - only to find that the phone now has system-less root - not full root. (I am using the nonprime variant).

How can I uninstall these system applications while operating only in system-less root?

Thanks!
[BLU R1 HD Guides, News, & Discussion] mrmazak:
From recovery, do adb remount, then remove all you want. Be careful
[BLU R1 HD Guides, News, & Discussion] waylonh:
Thank you for the response.

Along the lines of being careful - is it sufficient to just backup the original kernel image? Is there anything else I have to consider? Thanks!