Database Develop

New Rom: 514 All regions

Details:
Version: Android 3.2
Build Date: Dec 19, 2011
Baseband Versions:
EU 3g: 11.810.09.13.00 (same as 507)
US 4g: 11.810.09.06.00 (same as 506)
US 4g: LG7_514_21700_30.pkg & recovery.img
US Wifi: LG7-WiFi_514_21700_30.pkg & recovery.img
EU 3g: LG7-820W_514_21700_00.pkg & recovery.img
EU Wifi: LG7-Wifi_514_21700_00.pkg & recovery.img
Prelim changelog:
Next to nothing over 506/7
Tablet market removed
Standard market added
Minimal driver changes(?)
Not included:
Latest standard market
Stage 1.7 update on market

Waiting for US 4g thanks ThaManii

I dont know if/when i'll be able to fish up the us4g or eu wifi ones as the 506/507 ones were named very stupidly. I didnt find the original 514 us wifi one but i did find the eu 3g one.
Keep in mind that this version may be techincally a leak, it was built on dec 19th and shouldnt be released till next week or so under their normal schedule (this is also completely ignoring the fact that the past few weeks have been holiday weeks).
If 514 really hits OTA it may not be till the end of the month

Found all four of them

Thanks Again that was Fast!!!

update zip
i was wondering if anyone can make the pkg into zip files to flash in cwm

Hi, Problem with Recovery.img of 514 EU Wifi in Wiki Recovery Error 404.
Greettings

calico12 said:
Hi, Problem with Recovery.img of 514 EU Wifi in Wiki Recovery Error 404.
Greettings
Click to expand...
Click to collapse
Yeah I can confirm there is a download error for the US 4G recovery... if TheManii took it down then it was probably for a reason and he will get back to us. I'm gonna try and flash using the 506 recovery and see what happens.. report back in a little bit
UPDATE: I flashed the 506 recovery that I used to flash the US 4G update package and it worked just fine for installing this update

Here's a post with a link to the download from Dell: http://www.androidcentral.com/dell-streak-7-getting-bugfix-update

wptski said:
Here's a post with a link to the download from Dell: http://www.androidcentral.com/dell-streak-7-getting-bugfix-update
Click to expand...
Click to collapse
Thanks for the link but there's nothing wrong with the .pkg files links, only the recoveries as far as I can tell

cdzo72 said:
Thanks for the link but there's nothing wrong with the .pkg files links, only the recoveries as far as I can tell
Click to expand...
Click to collapse
It was mentioned above that it would be released by Dell soon and I ran across it. Funny, checking for updates, still shows no updates!
Just a confused newbie! Since I'm still stock, I can go this route.

The 514 recs havnt been prepared yet, I'm gonna do them soon.
If you already have 506/7 installed you can simply use the equivilent 506/7 rec
Edit: recs have been uploaded for 514 now

Who has had success rooting the new build with superoneclick? I tried twice and it hung on step 7 both times. I then proceeded to install superuser via cwm and now have root.
Because I am still somewhat of a noob regarding Android I am not sure if superoneclick did a partial root or what.
One the plus side for some reason the update seems faster. My titanium backups are installing noticeably quicker.

Wetzel402 said:
Who has had success rooting the new build with superoneclick? I tried twice and it hung on step 7 both times. I then proceeded to install superuser via cwm and now have root.
Because I am still somewhat of a noob regarding Android I am not sure if superoneclick did a partial root or what.
One the plus side for some reason the update seems faster. My titanium backups are installing noticeably quicker.
Click to expand...
Click to collapse
I tried updating to the 514 today and wasn't able to root unless I flashed HoneyStreak R8, which I don't want to really do because for some reason Netflix will not run on R8 here in Costa Rica, but when I was in the USA last month I had no problems. Well then I tried to go back by flashing the 506 ROm for my US 4G Streak 7 and couldn't root that either, once again the only way to root was by flashing HoneyStreak R8...
If anyone has any ideas I'm open. If not, about the only thing I know to do is NVFlash HoneyStreak R2 and start from there

Wanted to report a positive bug fixed with 514 vs 512 that came with my device. When docked in my video dock, the streak will ask to disable the speakers ok or cancel. with 512 no matter what was said it disabled. With 514 it works
Now I can dock at my desk and watch Netflix
Have not found any bugs yet....

I believe 514 was a specific hotfix related to the dock, at least that's what I hear

I'm damn happy they fixed it. After seeing Dell stopped selling the streaks and the Video Docks I honestly thought I was screwed. Surprised they even continued to bring out software updates.
Bad enough I couldn't even get a Streak 7 dock. Morons sent me a streak 5 dock. And then told me after I attempted to return that they do not have one for the streak 7 in stock nor are they replenishing.
A pair of Dikes and a bit of patience fixed that problem

Does anyone know if this update will work on T-Mobile branded Streak 7?

icepop said:
Does anyone know if this update will work on T-Mobile branded Streak 7?
Click to expand...
Click to collapse
I had no problems... I flashed the 506 recovery image and it read the update.pkg for this ROM just fine and flashed without a hiccup... but I'm having trouble rooting it

cdzo72 said:
I had no problems... I flashed the 506 recovery image and it read the update.pkg for this ROM just fine and flashed without a hiccup... but I'm having trouble rooting it
Click to expand...
Click to collapse
Awesome, thanks. I'll give mine a shot today.

[Q] Bell XT860 stock recovery

I would have posted this question in response to these instructions, however I'm still a noob on these forums, and haven't met my 10 post quota yet.
http://forum.xda-developers.com/showthread.php?t=1255198
My question is will this recovery method work for Bell Canada users, or will it only function for Verizon users?
I've installed AOKP a few months back, and while I enjoy it, I've lost support for some key features; namely HDMI, which is disappointing. When I tried recovering to the stock rom to hold me over until some new features and revisions show up on the mod scene, I found out my system backup was corrupt.
I have found a few downloads to system images, however every one I have found link to files that are now taken down. Can someone upload a current system dump?

I can set you up when I get home later
Sent from my XT860 using xda premium

try here http://sbf.droid-developers.org/umts_solana/list.php

What would happen if I flashed the Bell firmware to a Verizon Droid3?
Will it change the radio.img
Will I have to unlock it again?
Will everything still work?
I am using 5.7.906.xt852

jazz53 said:
What would happen if I flashed the Bell firmware to a Verizon Droid3?
Will it change the radio.img
Will I have to unlock it again?
Will everything still work?
I am using 5.7.906.xt852
Click to expand...
Click to collapse
Quite honestly no one knows. Wanna be the first?
Sent from my XT860 using xda premium

I'm really eager to find out. Worst case, you could always just flash the bell XT860 radio afterwards and see what happens!

I am way too new at this to try experimenting with untried solutions
I just barely figured out how to root my ph. Still working on how to flash.
Is it the same as installing a ROM?

jazz53 said:
I am way too new at this to try experimenting with untried solutions
I just barely figured out how to root my ph. Still working on how to flash.
Is it the same as installing a ROM?
Click to expand...
Click to collapse
No, you have to completely reflash your device and will have to re-root it. I think you should give it a go though
You'll need to download RSD Lite and download the XT860 Bell SBF files (they are about 500mb to download). Also make sure you FULLY CHARGE your phone, just in case you run into any issues. I think you can find an SBF how-to doc in the development forums. Please keep us posted.
Are you on Verizon? Because if you and this works, you probably won't be able to use it with them anymore.

Nope, I am on PCMobile without a data plan, use wifi.
I think maybe I'll try a Rom first.

NEXUS 7 3G-"nakasig" - Jelly Bean/KitKat Discussions, Problems and Solutions

NEXUS 7 3G-"nakasig" - Jelly Bean/KitKat Discussions, Problems and Solutions
Hi Nexus 7 "Nakasig" users,
I would like to consider this thread as your one place to chat or anything else related to Jelly Bean on the NEXUS 7 - 3G
I need everyone help to keep this thread somewhat sane, report any trolling or flaming and don't respond to it.
Keep all your posts in this thread polite and make sure you follow The Forum Rules.
I request you to stop posting:
- 'Thanks this helped'
- 'Yeah Me too'
-'+1'
These kind of posts are useless instead use the thanks button to show your appreciation
Click to expand...
Click to collapse
For all your JB needs, go to:
==>[Index] All for NEXUS 7 - "Nakasig" - (GSM/HSPA+)
==>[GUIDE] Unlock and Root a Nexus 7 3G “Nakasig- Tilapia”
==> [GUIDE][BOOTLOADER][4.3] TILAPIA JWR66V - 4.23 Flash Image Instructions - UPDATE
==>[GUIDE]If you need some help for install SDK and ADB drivers in Win 7, you can use this guide which is really good and comprehensive for all of us
It will be better for you to find one thread where we can concentrate all discussions, problems and solutions for the Nexus 7 3G ​

It 's a tool which is very good if you want to buy a Google Nexus Devices :good:
Google Nexus Devices World Availability Checker

Top man!
Any one got a working recovery and supersu/superuser that works with 4.2?
Since I've heard people losing 3G and stuff when they rooted, and I kinda don't want to have to set my stuff up again

WarningHPB said:
Top man!
Any one got a working recovery and supersu/superuser that works with 4.2?
Since I've heard people losing 3G and stuff when they rooted, and I kinda don't want to have to set my stuff up again
Click to expand...
Click to collapse
You've probably heard that from idiots who don't know what they are doing.
The latest version of TWRP works perfectly fine with 4.2 (3G and not). I'm using it on my 3G without any issues.
And the previous 'su' binaries and apk's should be fine. Neither of them should cause any problems with the 3G functionality as they have nothing to do with it. I installed custom recovery and rooted mine the day I got it. Everything is perfect.
Also, absolute worst case scenario, if you do screw something up, it's easy to revert without losing all of your data.

Hmm...I don't consider myself an idiot but did nothing more sinister than root and flash CWM and lost cellular data functionality completely at random two days later (unknown baseband). Had about 6 Android devices before this going back to HTC Hero, flashed all sorts, and never seen anything like it. Eventually had to flash factory image to get it back. Not especially helpful as inexplicable and not reproduced but worth saying nonetheless.

dave_uk said:
Hmm...I don't consider myself an idiot but did nothing more sinister than root and flash CWM and lost cellular data functionality completely at random two days later (unknown baseband). Had about 6 Android devices before this going back to HTC Hero, flashed all sorts, and never seen anything like it. Eventually had to flash factory image to get it back. Not especially helpful as inexplicable and not reproduced but worth saying nonetheless.
Click to expand...
Click to collapse
FYI, there seems to be a sporadic bug in JB on my GNex where on certain reboots it says Unknown Baseband and IMEI in the About menu, and then on the next reboot it's fine. I am wondering if that same bug is cropping up on the N7, and it's just coincidentally happening on some people's devices after rooting, but it goes away later. On my GNex this issue is particularly noticeable if I gave the phone a full reboot from inside software (e.g. using the app Easy Reboot). Whereas a power off / power on does not as frequently run into this issue.

I'm looking forward to getting mine Ordered today and it shipped today! I'm going to give my 16gb (bought in Aug for $249 so no price mod for me ) to either my GF or my daughter. lol
Sorry for the OT post.. I'm just excited. It will be nice to not have to tether my N7 to my phone. I just switched to the shared data plan on AT&T so it will only cost me $10 to add the N7 to my plan

Just fired up my 3g and will root it tomorrow, is there anything really different in rooting this thing vs the 16gb, anything I should watch out for?

kitsunisan said:
Just fired up my 3g and will root it tomorrow, is there anything really different in rooting this thing vs the 16gb, anything I should watch out for?
Click to expand...
Click to collapse
No, they are identical from a rooting perspective. However, they do run slightly different versions of the image, so if you wind up flashing stock, use the right one.

so first my success, i have managed to get root and a TWRP recovery.
now my question in menus im seeing horizontal lines that move with the landscape. so as the phone rotates the screen, the lines also rotate. maybe its just the background design but it seems really awkward to me that they would intend from these lighter brighter lines to be there

if someone would do me a HUGE favor and get me a stock JVP15S recovery? i flashed over mine with CWM before i could back it up and now i have a 34mg OTA update i cant take because of the custom recovery image

death 90 said:
if someone would do me a HUGE favor and get me a stock JVP15S recovery? i flashed over mine with CWM before i could back it up and now i have a 34mg OTA update i cant take because of the custom recovery image
Click to expand...
Click to collapse
I'm not sure that you will find someone who can give you this file, cause it contains all personal data and apps.

death 90 said:
if someone would do me a HUGE favor and get me a stock JVP15S recovery? i flashed over mine with CWM before i could back it up and now i have a 34mg OTA update i cant take because of the custom recovery image
Click to expand...
Click to collapse
I don't have my N7 yet, but on most Androids the stock recovery images do not vary much or at all between minor upgrades, so any stock recovery should be fine. Try the recovery.img inside the JOP40C image straight from Google. https://developers.google.com/android/nexus/images#nakasigjop40c
Worst case if the update still won't take, flash both system and boot from the stock image too (this will unroot you but so would the OTA, and you can fix that later), and then you'll be stock enough for OTAs to work the next time it prompts.
philos64 said:
I'm not sure that you will find someone who can give you this file, cause it contains all personal data and apps.
Click to expand...
Click to collapse
The recovery partition does not contain any personal data or apps. Everything personal is in /data.

philos64 said:
I'm not sure that you will find someone who can give you this file, cause it contains all personal data and apps.
Click to expand...
Click to collapse
im pretty sure the "recovery" partition doesn't contain any of those things. i don't want a stock rom, i need stock a recovery. twrp allows you to back up certain partitions such as boot, cache, and recovery
cmstlist said:
I don't have my N7 yet, but on most Androids the stock recovery images do not vary much or at all between minor upgrades, so any stock recovery should be fine. Try the recovery.img inside the JOP40C image straight from Google. https://developers.google.com/android/nexus/images#nakasigjop40c
Worst case if the update still won't take, flash both system and boot from the stock image too (this will unroot you but so would the OTA, and you can fix that later), and then you'll be stock enough for OTAs to work the next time it prompts.
The recovery partition does not contain any personal data or apps. Everything personal is in /data.
Click to expand...
Click to collapse
i just downloaded that ill try flashing it now i downloaded the "Google Nexus 7 Toolkit" and while it didn't work for me, it did provide a JRo03d stock recovery which i flashed with fastboot and that recovery did not work. when you nexus 7 arrives i believe it would be possible to recover the stock recovery using "fastboot boot twrp-recovery", ALTHOUGH im not sure when you would execute the "backup recovery" if it would read the phones actual partition or the image you uploaded and booted on

cmstlist said:
The recovery partition does not contain any personal data or apps. Everything personal is in /data.
Click to expand...
Click to collapse
Sorry for my quick answer, I haven't seen the "recovery.img". that's file system.zip or tar which contains apps and data for restore
And if you want the Factory image, go to the thread : [Index] All for NEXUS 7 - "nakasig" - (GSM/HSPA+) , it is on, ready for download

ya i grabbed it thanks. what i don't understand is what the 34mg update is for? any ideas? i uploaded two shots, one settings page showing the build mine shipped with and the other is just the update screen i got showing size. Im about to flash the stock ROM from google now. we'll see how goes

the 34mg update was "signed-nakasig-JOP40C-from-JVP15S". i was able to flash the recovery from the stock ROM JOP40C and use that to patch through android and avoid flashing usuing TWRP

death 90 said:
im pretty sure the "recovery" partition doesn't contain any of those things. i don't want a stock rom, i need stock a recovery. twrp allows you to back up certain partitions such as boot, cache, and recovery
i just downloaded that ill try flashing it now i downloaded the "Google Nexus 7 Toolkit" and while it didn't work for me, it did provide a JRo03d stock recovery which i flashed with fastboot and that recovery did not work. when you nexus 7 arrives i believe it would be possible to recover the stock recovery using "fastboot boot twrp-recovery", ALTHOUGH im not sure when you would execute the "backup recovery" if it would read the phones actual partition or the image you uploaded and booted on
Click to expand...
Click to collapse
Honestly don't try toolkits. Just don't, because you don't know what commands or files they are really flashing, and especially because they were written for the wi-fi version. The stock recovery from the wi-fi version is not guaranteed to be compatible with the 3G version.
philos64 said:
Sorry for my quick answer, I haven't seen the "recovery.img". that's file system.zip or tar which contains apps and data for restore
And if you want the Factory image, go to the thread : [Index] All for NEXUS 7 - "nakasig" - (GSM/HSPA+) , it is on, ready for download
Click to expand...
Click to collapse
System.img is also devoid of personal information because to the standard end user it is write-protected. All the personal stuff is in the data partition.
death 90 said:
the 34mg update was "signed-nakasig-JOP40C-from-JVP15S". i was able to flash the recovery from the stock ROM JOP40C and use that to patch through android and avoid flashing usuing TWRP
Click to expand...
Click to collapse
Glad it worked out for you. I had a feeling it was just going to give you JOP40C anyway.

So, I have been trying to root my 3G tablet (JOP40C), but have no luck. I installed TWRP and unlocked just fine using the Google Nexus 7 ToolKit 3.2. When I use the toolkit to root it seems like it is doing everything fine, reboots, and I do not see any errors during the process. However, when I access Titanium backup, or Root Checker it cannot gain root access. I have tried all the options in the toolkit and nothing is working. Can anyone give me some pointers? Thanks!

spongers said:
So, I have been trying to root my 3G tablet (JOP40C), but have no luck. I installed TWRP and unlocked just fine using the Google Nexus 7 ToolKit 3.2. When I use the toolkit to root it seems like it is doing everything fine, reboots, and I do not see any errors during the process. However, when I access Titanium backup, or Root Checker it cannot gain root access. I have tried all the options in the toolkit and nothing is working. Can anyone give me some pointers? Thanks!
Click to expand...
Click to collapse
Yes - Don't use a toolkit!
Since you already have a custom recovery, put the attached file on your sdcard and install it using TWRP. Then you should be good to go.

How to flash from 1.32 to 1.40 without losing your freaking mind (requires S-Off)

So yeah the people in the Int'l forums got that 1.40 OTA and the ROM devs have updated their ROMs to the 1.40 base.
Of course, this means we T-Mobile users are absolutely screwed unless we too update to the 1.40 base since trying to flash anything with the 1.40 base will make us bootloop and cry and swear. Mostly cry...and swear.
So here's a quick guide on getting your device to the 1.40 base so you can actually flash those ROMs again. Here we go. Note: I'm not responsible if anything bad happens. I sympathize, but it's not my bad.
Prerequistes:
1. You need S-Off. That means you'll need to fork out $25 to Sunshine and get it done.
2. You need Minimal ADB and Fastboot. The link for that is here.
3. An external SD card large enough to hold one nandroid backup and one ROM.
4. You'll need to make a Nandroid backup for your protection.
Guide:
1. First thing's first. You'll need to download ANY 1.40-based ROM. It doesn't matter which one, whatever one you want. Put that on your EXTERNAL SD CARD. You can find those in the Android Development section of the HTC One M9 international forums. The link for that is here. I highly recommend one that boasts that it's compatible with T-Mo devices. I flashed one of the Int'l-only ones and lost mobile data. Had to download and install another ROM. Learn from my mistakes.
2. Next you'll need to pick up the 1.40 firmware. The one I used is linked here. You'll want to download the latest one.
3. Now we get to have some fun. Open up minimal adb and fastboot and put your One M9 into DOWNLOAD MODE. Type "fastboot devices" without the quotes to make sure your device is recognized. If not, you need to go download the HTC One M9 drivers (just download and install HTC Sync). Once fastboot recognizes your device, type this command:
Code:
fastboot oem writecid 11111111
That is eight 1's, by the way. This will make your phone capable of flashing just about any firmware. Be careful and don't flash everything you find on the Internet. Once done, reboot back into download mode if it's not already there.
4. Rename the 1.40 firmware you downloaded to "update.zip" (no quotes) and put it in the minimal adb and fastboot folder (usually under C drive in the program files x86 folder).
5. Okay kids, this is the hard part so pay attention. You're going to flash the update TWICE. Why? I'll explain in the moment. Type these commands in order:
Code:
fastboot oem rebootRUU
followed by:
Code:
fastboot flash zip update.zip
Now at this point you'll probably get something like "90 Fail" or "Fail 90". What's just occurred is that part of the update was flashed, but not all of it. Sometimes it'll un-**** itself and continue on its own but usually not. To fix it, simply type the command a second time:
Code:
fastboot flash zip update.zip
This should complete the flash.
6. Reboot back into your recovery. Mount any partitions that may not be mounted.
7. Flash the ROM you downloaded back in step 1. Make sure you wipe everything (system, data, cache, dalvik) before doing so.
8. Reboot and enjoy.
Now that should be it. If you have problems, you'll want to visit this thread and the thread you downloaded the 1.40 firmware from (linked above) because those guys seem to know what they're doing and I really don't.
From this point forward, you SHOULD be able to flash any 1.40 based ROM without issues or cheap fixes (like in the ViperROM...by the way, it was really awesome of them to include that fix, even if it was a cheap fix. Thanks guys!).
Also, a big thanks to NO ONE for writing this guide anywhere else. Good job, jackass. As per the norm, you don't have to thank me and I don't care if you copy/paste the guide somewhere else without giving me credit. Information is free.

Is there any way to keep WiFi calling? Do I need to flash a modern or radio?

Is the T-Mo version of this updated ROM expected to release soon ?

I tried this, but I got very little lte reception. I even tried flashing the T-Mobile radio image, and I still had bad LTE. I flashed the T-Mobile firmware and all is good with LTE. Has anyone else have this problem?

jbfountain said:
I tried this, but I got very little lte reception. I even tried flashing the T-Mobile radio image, and I still had bad LTE. I flashed the T-Mobile firmware and all is good with LTE. Has anyone else have this problem?
Click to expand...
Click to collapse
Flash the firmware and then the T-Mobile radio

ahrion said:
Flash the firmware and then the T-Mobile radio
Click to expand...
Click to collapse
Anyone try the 2.7 firmware with a TMO radio?

123421342 said:
Anyone try the 2.7 firmware with a TMO radio?
Click to expand...
Click to collapse
I've tried flashing a Tmo radio after flashing the new 2.7 firmware however I get a fail message (can't remember all the details). I was using a radio image from a thread in the General section of the International M9 forum... I was able to flash that same radio with the 1.40 firmware so who knows if there's something different now...

ahrion said:
Flash the firmware and then the T-Mobile radio
Click to expand...
Click to collapse
That's the way I did it, but still had bad reception until I flashed the T-Mobile firmware again.
---------- Post added at 02:11 PM ---------- Previous post was at 02:03 PM ----------
xHVGx said:
I've tried flashing a Tmo radio after flashing the new 2.7 firmware however I get a fail message (can't remember all the details). I was using a radio image from a thread in the General section of the International M9 forum... I was able to flash that same radio with the 1.40 firmware so who knows if there's something different now...
Click to expand...
Click to collapse
Go here http://forum.xda-developers.com/one-m9/general/recovery-flashable-radio-zip-t3122983. You can flash it using TWRP according to this thread. Let us know how you do.
Cheers

Prasad said:
Is the T-Mo version of this updated ROM expected to release soon ?
Click to expand...
Click to collapse
Expect something newer than 1.40 coming very soon. ? I'd share some screenshots but that's saying too much.
Sent From My HTC One (M9)

Rydah805 said:
Expect something newer than 1.40 coming very soon. I'd share some screenshots but that's saying too much.
Sent From My HTC One (M9)
Click to expand...
Click to collapse
so pretty much 2.7 TMO confirmed within a week?

Rydah805 said:
Expect something newer than 1.40 coming very soon. I'd share some screenshots but that's saying too much.
Sent From My HTC One (M9)
Click to expand...
Click to collapse
Really hoping for that newer version soon. From what I've heard, the improvements seen in 1.4 and 2.7 both make the phone much better to use. 1.32 is fine, but the thing really does heat up way too quickly, and others have said this problem is much less noticeable on newer firmwares.

guyverzero said:
Really hoping for that newer version soon. From what I've heard, the improvements seen in 1.4 and 2.7 both make the phone much better to use. 1.32 is fine, but the thing really does heat up way too quickly, and others have said this problem is much less noticeable on newer firmwares.
Click to expand...
Click to collapse
I've forgotten that this thing heats up. ? expect something very soon.
Sent From My HTC One (M9)

[Q&A] Droid Turbo XT1254 5.1 Rooted Images (+Xposed, other extras) / Upgrade from 4.

[Q&A] Droid Turbo XT1254 5.1 Rooted Images (+Xposed, other extras) / Upgrade from 4.
Q&A for Droid Turbo XT1254 5.1 Rooted Images (+Xposed, other extras) / Upgrade from 4.4
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Droid Turbo XT1254 5.1 Rooted Images (+Xposed, other extras) / Upgrade from 4.4. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

I followed instructions on the OP and keep getting a "No command" error when I try to boot into recovery (I've already let it boot to the set up screen already since some people have said that fixed it). Is there a way to fix this or did I somehow mess it up?

Biffins said:
I followed instructions on the OP and keep getting a "No command" error when I try to boot into recovery (I've already let it boot to the set up screen already since some people have said that fixed it). Is there a way to fix this or did I somehow mess it up?
Click to expand...
Click to collapse
Same thing for me...
Sent from my Droid Turbo

Biffins said:
I followed instructions on the OP and keep getting a "No command" error when I try to boot into recovery (I've already let it boot to the set up screen already since some people have said that fixed it). Is there a way to fix this or did I somehow mess it up?
Click to expand...
Click to collapse
getupandbeit said:
Same thing for me...
Sent from my Droid Turbo
Click to expand...
Click to collapse
At the recovery which reads "no command" hold power and press volume up.

Works on

What's going to happen if I push 5.1 and Android M comes out officially?
Am I better off holding until that time or is there a way to get there once I do all of this

Hello, Ive been reading on here about mofo for the last month, and Ive been waiting to see how lollipop goes over. After reading all the success stories, I bought mofo.
My phone has never been rooted, is there a specific guide for going to computerfreek274's loliipop image from a stock kitkat ? All the guides seem to assume Im already rooted on kitkat. Or should I root on kitkat first?
thanks

In the fastboot commands for this update, I notice that the command to flash radio.img is missing. Is this an oversight or is a flash of the radio partition not needed?
Thanks for all that you and Computerfreek274 contribute to this forum!!!

turpindm said:
In the fastboot commands for this update, I notice that the command to flash radio.img is missing. Is this an oversight or is a flash of the radio partition not needed?
Thanks for all that you and Computerfreek274 contribute to this forum!!!
Click to expand...
Click to collapse
The instructions in the main thread have were changed to reflect the latest files (you'll be flashing modem and a few others instead of radio). If you're using the guide that was linked, it hasn't been updated with the latest instructions yet.

firstEncounter said:
The instructions in the main thread have were changed to reflect the latest files (you'll be flashing modem and a few others instead of radio). If you're using the guide that was linked, it hasn't been updated with the latest instructions yet.
Click to expand...
Click to collapse
I am up an running I started experiencing data and voice signal issues - RIght now I have advanced calling I can talk and surf but the option is not in my Advanced Calling settings menu - but testing to see if the device holds signal for 1x communication. It keeps dropping the signal and never gets it backs a signal so I have been using my back up device for days now.

turk2333 said:
I am up an running I started experiencing data and voice signal issues - RIght now I have advanced calling I can talk and surf but the option is not in my Advanced Calling settings menu - but testing to see if the device holds signal for 1x communication. It keeps dropping the signal and never gets it backs a signal so I have been using my back up device for days now.
Click to expand...
Click to collapse
Make sure you haven't disabled the My Verizon app in order for the Advanced Calling menu to work correctly.
For radio issues, make sure you've downloaded the latest 5.1_images_v3.zip and used the fastboot commands in the main thread. You can run all those commands without reflashing your system.img just to make sure everything's up to date. If you're still having issues, I'm not sure what else you can try other than backing up everything and trying a data wipe.

firstEncounter said:
Make sure you haven't disabled the My Verizon app in order for the Advanced Calling menu to work correctly.
For radio issues, make sure you've downloaded the latest 5.1_images_v3.zip and used the fastboot commands in the main thread. You can run all those commands without reflashing your system.img just to make sure everything's up to date. If you're still having issues, I'm not sure what else you can try other than backing up everything and trying a data wipe.
Click to expand...
Click to collapse
seems stable now - I did two data wipes - was so many issues with the radio and I was like no way this cannot be fixed. I have nto left my office yet which will be the real test but right now all seems good.

turk2333 said:
seems stable now - I did two data wipes - was so many issues with the radio and I was like no way this cannot be fixed. I have nto left my office yet which will be the real test but right now all seems good.
Click to expand...
Click to collapse
I've had my phone get stuck on 1x a few times when using 4.4, so it's possible it's just a bug in the actual firmware.

firstEncounter said:
I've had my phone get stuck on 1x a few times when using 4.4, so it's possible it's just a bug in the actual firmware.
Click to expand...
Click to collapse
This is not being stuck this was no service at all would to G then I could not make calls or anything - totally screwed up - I have a new phone on the way from Assurion if this keeps happening. As I posted - I flashed all commands per instructions and that seem to do the trick I hope.

Thanks to everyone who keeps the updates updated... 23.11.39 Root went well... Thanks again!!!

Fastboot Command
Could someone please show me an example on how to flash files on the command prompt with adb. How do I direct it to the file location that I want to flash. Screen shot would be very helpful. Thank you for your time in advance.

Hi,
Can someone please explain something to me?
If the BL is locked on xt1254 but mofo somehow gets around it to enable flashing of rooted images.. What is stopping us from flashing a modified cyanogenmod or equivalent over?
Why do we need an unlocked bootloader if we can already flash modified images? Is there some check in place that prevents this? Or is this wip?
I'm obviously missing something!
Thanks guys
Sent from my Nexus 5 using XDA Free mobile app

Quick question
I am on stock 4.4.4 do i need "5.1 upgrade images (v3)" or "Rooted 5.1 system image (v2)" to get myself to 5.1 with root? And wifihotspot is enabled on all these images correct?

SkiiinZ said:
Hi,
Can someone please explain something to me?
If the BL is locked on xt1254 but mofo somehow gets around it to enable flashing of rooted images.. What is stopping us from flashing a modified cyanogenmod or equivalent over?
Why do we need an unlocked bootloader if we can already flash modified images? Is there some check in place that prevents this? Or is this wip?
I'm obviously missing something!
Thanks guys
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
because mofo can't write the kernel/boot partition
Sent from my XT1254 using Tapatalk

Tap053 said:
I am on stock 4.4.4 do i need "5.1 upgrade images (v3)" or "Rooted 5.1 system image (v2)" to get myself to 5.1 with root? And wifihotspot is enabled on all these images correct?
Click to expand...
Click to collapse
Either one should work if you follow the instructions but only the "extra" versions have tethering enabled. At this point, I'd use the image labeled "Extras 5.1 system image (rooted v2 + extras v4)". You can always start with the stock rooted, then dirty flash the extras version with mofo.
Sent from my XT1254 using Tapatalk
---------- Post added at 01:34 AM ---------- Previous post was at 01:29 AM ----------
Rag Man said:
Could someone please show me an example on how to flash files on the command prompt with adb. How do I direct it to the file location that I want to flash. Screen shot would be very helpful. Thank you for your time in advance.
Click to expand...
Click to collapse
Nowhere in the OP for this ROM does it mention flashing files with ADB. You can only flash the system image with the mofo tool. We do not have a custom recovery on the Turbo so you cannot flash ZIP files. We do not have a writable system partition so you cannot push files to it via ADB.
Fastboot is used to upgrade some of the other partitions to the 5.1 versions and is described in the OP.
Sent from my XT1254 using Tapatalk