yashsingh1/xdaforums huggingface dataset:
[Droid Ultra General] rds217:
If you need to hear it explicitly, I started with 4.4 with version 19.6.3, but I had encrypted my storage, requiring me to start from scratch. I FXZ'ed to 19.5.3, performed the PIE+wpbegone exploits in conjunction to get 4.4 version 19.5.3 with root AND write protection off. I then took the OTA via system update for 19.6.3. Once on 19.6.3, I installed Safestrap and copied the 4.4.4 rom to the internal memory. I reboot into safestrap recovery, and installed the 4.4.4 rom. Finally, I reboot into the bootloader, and flashed the boot image using the fastboot command.

The end result is 4.4.4 version 21.11.21 with root and w/p off.

Also, the quicksettings button is borked for me. I can still swipe the bottom of the notification panel to get to it, but the button itself isn't working. Anyone else have the same issue?
[Droid Ultra General] Topsnake:
This is a clever way to get 4.4.4 rooted, but I feel that most have already taken the update by the time this was posted.
[Droid Ultra General] MrTweakers:
I can confirm that this worked exactly as described as long as you follow the directions exactly. I was rooted w/WP off on version 19.6.3, I followed the steps, and I am now on android 4.4.4 build version 21.11.21

I still have all my apps, data, pictures, everything, and it's working flawlessly. I have zero issues with it so far. If anyone has any questions as to what the end results of this entails please feel free to ask!

P.S. This could easily be a placebo effect but my phone feels a lot smoother and snappier than it was before. And a very CPU heavy game I play on my phone for hours each day (not exaggerating) called Parallel Kingdom is definitely smoother. I can see the little feet on my character take steps as I move him now. Lol

Sent from my rooted, WP off, DROID ULTRA!
[Droid Ultra General] MArtyChubbs:
Sorry for the delay, yes I lost wp-off once I installed the 4.4.4 update in safe strap. Since the update is installed in safe strap, the bootloader is still at 4.4 and fastbooting back to 4.4 is ok.

My daily driver is a 32gb unlocked Maxx. I tried the method in the op on a new locked 16 gb maxx luckily still on 4.4. Once I fast booted to 4.4, I just flashed the 4.4.4 radios and left it.
[Droid Ultra General] mrwinkle:
tried it kept on getting "C:\Users\Office>fastboot flash boot boot.img

(bootloader) Variable not supported!

error: cannot open 'boot.img'" when i got to step 5 of part 2. boot.img is located in C:\adt-bundle-windows-x86_64-20140321\sdk\platform-tools. Any leads?
[Droid Ultra General] samwathegreat:
Ummm yeah. Isn't it obvious??

You are running the command from C:\Users\Office

But......the boot.img file is in C:\adt-bundle-windows-x86_64-20140321\sdk\platform-tools

You obviously have changed a path variable to allow you to run fastboot from any folder, but how is it supposed to know where to find boot.img??

Either put boot.img in C:\Users\Office OR change directories to where you put boot.img
[Droid Ultra General] mrwinkle:
DUHHHHH!!!!! I feel so dumb right now thanks a lot
[Droid Ultra General] mrwinkle:
working like a charm! the reason why i bit the bullet and went with this "upgraded" was to allow my droid ultra to have the "cast screen" option available on my chromecast app. Now my chromecast is mirroring my phone's screen LIKE A BOSS!!!
[Droid Ultra General] Archangel:
I am wondering if there is any downside to doing this?
[Droid Ultra General] rdenova:
Installing zip file via Safestrap now.

Why flash the boot.img? Just finished, booting up now.

...ok, now I see why to flash the boot.img...lol Now it's optimizing the apps.

Guess I'll have to do that next. Build number says 4.21 but Android version still says 4.4 - I get it....

Glad I have a backup, nothing noticeably different other than some colors... Going back to 4.4 - 19.6.3 rooted/WP off
[Droid Ultra General] mrwinkle:
One big difference I noticed is HDR on Google camera app.
[Droid Ultra General] rdenova:
Some color changes I noticed but I use Camera MX on this Maxx and it does very well for video and pics. I wasn't really expecting much but it was fun to try...

Restoring the backup via Safestrap worked as expected. I may tinker with it more having successfully updated and restored. Choices are good.
[Droid Ultra General] mrwinkle:
Hey could you supply us with your debloat list?
[Droid Ultra General] gotsaved289:
So if I'm on 19.5.3 already with root, w/p off and safestrap installed do I have to re-RSDflash 19.5.3 and start over? Or is there a way to manually update to 19.6.3 and continue this method from there?
[Droid Ultra General] samwathegreat:
Personally....I don't see any reason that you couldn't just do this procedure straight from 19.5.3. With the Moto X, it doesn't matter what version we have safestrap installed on - as long as it is installed (and WP disabled). Some are still running safestrap on 4.2.2 while others are running it on 4.4 -- both can successfully use the 4.4.4 stock-based safestrap ROM.

Perhaps the OP could tell us why the instructions specify 19.6.3 (as opposed to EITHER 19.6.3 OR 19.5.3) ? It is possible something is different between the droid variant an the X regarding safestrap....not sure since I don't own one.
[Droid Ultra General] gotsaved289:
Just to confirm that I followed the instructions on the op and am now on 4.4.4. From the 19.5.3 update of 4.4. Thanks for the help Sam!
[Droid Ultra General] gotsaved289:
Screen shot
[Droid Ultra General] samwathegreat:
Thanks for the reply and confirmation :good: - I figured it would work. I'm sure it saved you some hassle and will for others as well.
[Droid Ultra General] distortedloop:
I've been considering trying this, but I'm leery of running a modified ROM from a fairly new member with little history on the site. Any way to know for sure the ROM is secure (no trojans, backdoor, etc.).

I mean no disrespect to the OP, I'm just extra cautious these days.
[Droid Ultra General] gotsaved289:
Oh yeah no problem, the one thing that I did notice right away is that I did lose the hotspot capability which I got back by installing the zip from this thread http://xdaforums.com/droid-ultra/orig-development/mod-native-tether-exploit-build-21-11-21-t2811810 .
[Droid Ultra General] Topsnake:
19.6.3 has the 4.4.4 radio from the moto x. Maybe that's why.
[Droid Ultra General] gotsaved289:
On that note, I noticed that the data was really slow especially when opening Ingress so when I had time this evening I flashed an updated radio from the below thread and my data is actually seems to be running faster than before.

http://www.bloglovin.com/viewer?pos...me_type=b&blog=5233323&frame=1&click=0&user=0
[Droid Ultra General] mrwinkle:
How do I get my live wallpapers back? I took livewallpapers.apk and odex and livewallpaperspicker.apk and odex copied to system/app, change permissions to 644, hit install, and I get app not installed. The apks are from a 19.6.3 ultra system dump, any thoughts?
[Droid Ultra General] aviwdoowks:
Hit install??

Reboot to install.
[Droid Ultra General] mrwinkle:
...and rebooted, still nothing.
[Droid Ultra General] aviwdoowks:
Be sure to uninstall any data app & delete any other conflicting versions. Set permissions to rw-r--r--.

There is a ATT 444 dump in the dev section

---------- Post added at 11:09 AM ---------- Previous post was at 10:50 AM ----------

I meant to quote you!
[Droid Ultra General] mrwinkle:
The ATT 444 dump apks did install but the livewallpaperspicker apk is FCing. Any suggestions?
[Droid Ultra General] aviwdoowks:
Here.
[Droid Ultra General] mrwinkle:
That did the trick!
[Droid Ultra General] summer.cat:
you can d.i.y. opening zip-file and navigate to \META-INF\com\google\android\updater-script

in this file you can see all apps, i decided to refer to the bloatware list.
[Droid Ultra General] kazpur:
Used this to go from 19.5.3 with root and wp off to 21.11.21. Kept root and wp off. Only problem I have now is that Touchless controls does not work. Start the training process, but unable to record. It doesn't pick up any sounds while waiting for launch phrase. Tried to clear data and reset phone. Neither one worked. Anyone else run in to this issue? Other than that, everything (that I use) seems to work.

EDIT:

Oh, and Assist crashes when a text or call come in while in driving mode and "Talk to me" is checked.
[Droid Ultra General] Archangel:
Same thing happen to me on a older build when I themed the framework and systemui. Apparently when something is out of whack touch-less control is the first thing to go.
[Droid Ultra General] samwathegreat:
Likely, you had modified something in /system before you flashed the new safestrap-compatible ROM.

You should be able to restore back to 19.5.3, re-root, obtain wp-off, install safestrap, and repeat the procedure -- flashing the ROM to stock slot and flashing boot.img with fastboot.

I bet it solves all of your problems...
[Droid Ultra General] blu422:
Well looks like the info you originally had was right. I realize you already flashed but I have been reading a ton into djrbliss's method and it looks like he pulled the trick off originally in early July... And (sort of) released it only after carriers and OEMS were aware of the bug seeing as the bug also presents a danger to phones as well as help. So in other words his method may or may not be already patched by 4.4.4 just so everyone knows. Also don't keep your fingers crossed because the info he did give on how to do it is more like a location of the bug. But not how to exploit it and experimenting is dangerous at that level so there aren't many who will want to put their phone at risk to try to develop that method. Our only hope is if some wizard like djrbliss is able to discern the method. Really the lesson to be learned from all this is to be grateful for what you're given the reason djrbliss didn't post the method publicly is because last time he did he got a ton of crap.

---------- Post added at 10:13 PM ---------- Previous post was at 09:59 PM ----------

Will this method with with this ( http://xdaforums.com/showthread.php?p=54404733) instead if I still flash the boot.IMG?
[Droid Ultra General] samwathegreat:
I do not believe that it can be made into a safestrap-compatible ROM, since it isn't stock based (it's ported). Care to comment on this, [MENTION=3582521]Topsnake[/MENTION] ?
[Droid Ultra General] Topsnake:
Not 100% sure what we are talking about here. There's like 3 different convos in here.

My port is built for unlocked bootloaders and only supported as such.
[Droid Ultra General] blu422:
Yeah but it is it maybe possible to try to flash your ROM using this method? With the boot.img also found in this tread? Would it do any harm if I tried? I'm just getting sick of the texting and global mode and all (I use the maxx on T-Mobile) and your ROM fixes that. Because if this works without an unlocked bl don't you think you're ROM in place of this one would also?
[Droid Ultra General] Topsnake:
Its not packaged for that. Not only that, but the boot.img from this thread might not run the port. Lastly my port isn't rooted as packaged.

Best bet would probably be to run a Moto X custom rom built for SS like [MENTION=4850320]iKrYpToNiTe[/MENTION] Krypton. Which by the way ill be porting to the Maxx and maintaining for unlocked BL soon.

Anytime you want to run a rom on a locked BL its a pain.
[Droid Ultra General] samwathegreat:
From what I understand, this is the problem:

Safestrap works by "dual-booting" a *different* system image -- by flashing it to the "stock ROM slot" of safestrap recovery.

Unfortunately, the problem seems to lie in that you can't flash ***ANY*** un-signed images with a locked BL. This means that you *CAN'T* flash a Moto X boot.img (boot.img is the KERNEL) to one of the droid variants (UNLESS you are Un-Locked). Obviously, the device will most likely fail horribly *IF* it will even boot with a mismatched ROM/KERNEL (for instance, using the boot.img from this thread with a port or custom rom).

This is my understanding as to why stock-based ROMs can run on SS, but Ports, and custom roms can not.

Someone please correct me if wrong, but based on my knowledge of safestraps inner-workings, the above is the underlying issue.

Now - it shouldn't brick you to try...I'm just extremely doubtful that it will work. If you want to try, be my guest. ***NOT RESPONSIBLE*** if anything goes wrong. Although it shouldn't brick you to try and you should be able to flash back to stock, you have been warned.
[Droid Ultra General] iKrYpToNiTe:
I wouldn't say it's a pain, it just requires more steps a lot of the time, and theoretically he should be able to run my rom as long as he is running the Maxx's 4.4.4 kernel.

For the most part your explanation is correct, I didn't feel like reading the whole thread but he should be able to run a Moto X rom on the Maxx's 4.4.4 kernel. The key word is should lol, but he will have to try and find out.
[Droid Ultra General] blu422:
Thanks guys I'll do some experimenting and report back!!!
[Droid Ultra General] blu422:
Oh but if I am unsuccessful the only firmware I could recover it to would be 4.4.4 WP on if I've already flashed the boot.img... Not sure if it's worth the risk...
[Droid Ultra General] samwathegreat:
That's not true at all! boot.img can be 'downgraded' no problem.

Only gpt.bin and motoboot.img can not be downgraded. You aren't flashing EITHER of those...
[Droid Ultra General] blu422:
So it's hanging on rebuilding cache... Starting apps.. Any ideas?
[Droid Ultra General] summer.cat:
Reboot the device manually, by holding Vol- and Power buttons. After this, phone should start normally.
[Droid Ultra General] KeepingItCuttingEdge:
I had the same issue of it hanging on the spinning Droid thing as well. I had done this with another phone a week ago using the "4.4.4_rooted.zip" file and manually flashing the "boot.img" and it worked FINE, so I used the old method on 2 of these today and it still worked. I didn't try the "bloated" file, but the "multilocale-4.4.4-SU4.21-Rooted.zip" hung on me.
[Droid Ultra General] ReverendYo:
Hello!

Can't believe I'm the dummy that can't figure this out, but I always encourage people to ask questions...guess its my day to eat my pride. The 2 downloads in the original post are not available for download for me. Just a 'request access' link to his drive account. Did I miss these being mirrored somewhere else in the thread? I've looked and just don't see it.
[Droid Ultra General] hendrahida:
same here, cant access both download link :confused:
[Droid Ultra General] summer.cat:
Guys!!!

SU5-24 (Blur 23.3.23) rooted coming soon!​
[Droid Ultra General] Koneesha:
I am using this rom but find that Facebook, and other google apps load data very slowly now. Is there a way to fix this?
[Droid Ultra General] AVishvas:
I took all the OTAs on my Droid Maxx XT 1080 and now I am on SU5-24 Blur 23.3.24.

Shall I ever be able to root my droid maxx? :confused:
[Droid Ultra General] summer.cat:
sorry, but you are not able to get root
[Droid Ultra General] tiguy99:
I'm in the same boat...wish we knew if/when the fix will come out for this phone
[Droid Ultra General] smartazz69:
I read the forum and I'm confused if this forum shows how to root the 4.4.4. I think I got lost somewhere in the reading.
[Droid Ultra General] mistermatrix24:
Link issues

Is the debloated version gonna be re hosted anytime soon? also is anyone else having trouble downloading the stock kernel in step 5? I keep getting an error "this file doesn't exist"
[Droid Ultra General] zefyx:
Still waiting on the debloated rom.
[Droid Ultra General] JCroffut:
root and boot

I have the droid Maxx XT1080 4.4.4 and I could use any help I can get on rooting and unlocking boot loader. I'm completely stock and I just factory reset. HHHHHHEEEEEEEELLLLLLLLLPPPPPPPP
[Droid Ultra General] jball:
Only dev edition devices can be rooted right now.I've been searching all over for the same.

Root if anything would be nice
[Droid Ultra General] Samg381:
Not going to happen, unfortunately.

Rooting this phone is extremely difficult and currently there are no developers working on it.
[Droid Ultra General] jball:
It's wild though how the development just stopped.

4.4.4 and BAM!! screw it

It's not a big deal considering this device is just a toy that was given to me compared to my other devices.
[Droid Ultra General] brackett5:
I'm on su6-7 will this work for that??
[ONE Q&A, Help & Troubleshooting] MrC11:
Hello guys,

Monday i received mine Oneplus One and it is a true flagship killer. But i am not happy with the default icon pack, Don't get me wrong. I love it but, just a few apps get changed.

Now i am a designer and i would love to change the icons. But how can i change the .png of the app in the app drawer?

I have googl'd enough but i don't understand that, it is like abracadabra to me. Does someone have a really useful tut for me?

I don't want to create a new icon pack, i just want to expand the default one.

Greetz,

MrC
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] jasjamming:
I just spoke live with Imate Support via clubimate asking the rep about an upgraded ROM with AKU3.2. Here is a copy/paste of the screen shot:

Bob> Welcome to Club i-mate. My name is Bob and I am a Club Advisor. What can I help you with?

rv> Hi Bob, thanks for your assistance

rv> I have a short query in regards to ROM upgrades

Bob> hi

Bob> yes?

rv> will IMATE be offering a ROM update with AKU3.2 for the JASJAM

rv> ?

Bob> We are definitely going to launch some new updates for JASJAM soon. They are still in the design and testing stage and hence I cannot give you a specific time frame for the launch or the device specifications. However, as and when we receive the information, it will be posted on the site www.clubimate.com. Please keep a regular check on our website for further news and updates on our devices and services.

rv> the problem is A2DP in bluetooth, the sound is terrible with many stereo BT headsets, and ive heard that an upgraded BT stack will resolve these issues

Bob> yes

Bob> A2DP works only with certain headsets, that why it is not announced, that JASJAM supports A2dp

rv> i have tried both blueant x5 and itech blueband/clip, all 3 work but sound is rather low quality on the JASJAM as compared to a PC

rv> I beleive it is the BT stack, MS needs to tweak it

rv> thanks for your efforts today Bob, greately appreciated

Bob> welcome:)
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] joedoe:
Well, from this transcript it doesn't look like it's going to happen soon, just a usual canned replay.
[LG Optimus L9 P760, P765, P768, P769] bulgi:
Hello everyone

I have a LG P769 L9

And I ask you to help me find a ROM that has a multi-language Hebrew (Full)

Lots and lots of thanks

:crying:
[LG Optimus L9 P760, P765, P768, P769] adosin:
I know your looking for a ROM with built in Hebrew language pack but just thought this link may get you started.

http://androidforums.com/i7500-all-things-root/112698-howto-hebrew-support-any-rom.html
[LG Optimus L9 P760, P765, P768, P769] bulgi:
Thank you very much :))
[Sony Xperia M] Droidlover123:
Hey all....

I am having hard time using GPS on my xperia m.:banghead:

Am on stock rom and whenever i use google maps it is always stucked on locking gps location ...

So is gps working for you guys?and any fix for this?

Thanks

:beer:
[Sony Xperia M] RedLedLight:
It probably is a firmware bug... It didn't work for me either .

Wait for an OTA update.
[Sony Xperia M] FindYanot:
Fix
[Sony Xperia M] Droidlover123:
Ty will try that...

And its highly unacceptable that brand like Sony is providing such poor services. They must provide us officially with permanent fix :mad::mad:
[Shield Q&A] Keithn:
That's odd. I was able to grab the preinstalled source just fine, but OTA0 wouldn't sync. What are you trying to grab? It looks like an error with the init rather than grabing the files like mine was though

Sent from my One M8
[Shield Q&A] DragonHunt3r:
At this line it went wrong: repo init -u git://nv-tegra.nvidia.com/manifest/android/binary.git -b rel-roth-partner -m secureos/kk_roth.xml
[Shield Q&A] Keithn:
Try adding r5 into the init. All of the other branches have r* in the branch name and this has it in the link but not the branch.

So try " repo init -u git://nv-tegra.nvidia.com/manifest/android/binary.git -b rel-roth-r5-partner -m secureos/kk_roth.xml "

I was originally thinking tablet since that's what I have, but I took a quick look at the portable links.

Sent from my One M8
[Shield Q&A] DragonHunt3r:
Oh yeah also when looking at the URL it contained r5 but not in the repo init link... lol

Thanks It's syncing now :victory:
[Galaxy S 4 Q&A, Help & Troubleshooting] jdhot1:
My i9505 originally had I9505XXUFNB8 BTU firmware on it and was rooted using Chainfire's Auto Root.

The phone kept asking me to update the firmware so I decided to flash the stock firmware back on it using ODIN so that I could do so (I have read that you should never update via OTA if rooted).

When I flashed it using ODIN, upon boot up, the phone said that "Unfortunately, Touchwiz Home has stopped." I press OK but then I get another error message this time for Google Play Music (infinite loop).

I keep toggling between these two error messages, however they don't go away.

If I press the lock screen button, I can see the welcome message, the status bar etc. But soon as I swipe, the above error messages appear.

If I receive a phone call, the phone rings and goes to the answer / reject screen but I can't accept the call as the error message is in the way.

I have already tried factory reset via the recovery options boot menu, but to no avail.

I have flashed a new version of the ROM, I9505XXUFNB9 but still the same error. I then even tried rooting it again, but still the same issue.

Please help me.
[Galaxy S 4 Q&A, Help & Troubleshooting] VoLTaqe:
Flash stock rom via odin go to recovery wipe data, cache can solve your problem. Or try before put your phone airplane mode it may help your stopped after that delete play music and clear systemui data.
[Galaxy S 4 Q&A, Help & Troubleshooting] jdhot1:
No Luck

I have already tried the above, but I tried it again as per your instructions.

I flashed the stock rom via Odin (normal options selected just reset time and auto reboot). The device restarts and upgrades the system as per normal.

Before I even get to set the language a dialogue box appears saying that Google+ has stopped.

The Google+ dialogue box is now in an infinite loop.

Also, every time when I now turn it off and back on again, it goes through the upgrade screen but only for a few seconds.

I think my phone needs some sort of master reset.
[Galaxy S 4 Q&A, Help & Troubleshooting] VoLTaqe:
You are saying wrong steps.

1- Flash stock firmware

2- Wait until phone boot

3- After boot volume up + home + power button and go in stock recovery mode ( not cwm or twrp )

4- Wipe data / cache

5- Done.
[Galaxy S 4 Q&A, Help & Troubleshooting] jdhot1:
Will Try Now

I will do this now.

I have got stock recovery mode.

So I have to clear the data / cache before it boots up with the stock firmware?
[Galaxy S 4 Q&A, Help & Troubleshooting] jdhot1:
Still not working

Ok, so firmware was successfully uploading using ODIN.

Phone rebooted, I did the data and cache wipe (factory reset does them both at the same time).

I have now entered the setup screen, I waited for around 15 seconds, then the message appeared again "unfortunately, Google+ has stopped."

I press OK on this dialogue box, then I get another error "unfortunately, Google Play Music has stopped."

Then after pressing OK on this one, I get the Google+ one in a loop.
[Galaxy S 4 Q&A, Help & Troubleshooting] jdhot1:
Should I try Philz Touch Recovery?

I found this thread http://xdaforums.com/showthread.php?t=2480473 but I am unsure if I should try it.
[Galaxy S 4 Q&A, Help & Troubleshooting] VoLTaqe:
Wipe data factory and try again. If not success flash twrp and wipe cache, data, preload, system, internal sdcard after that flash any custom rom