Database Develop

Flash 5.0 N7 2012 [Auto Flash 5.0 LRX21P][From Bootloop/Bootloader/Normal State]

(WINDOWS ONLY)
WARNING: WIFI VERSION ONLY
This Tool flashes Android 5.0 Lollipop to your Nexus 7 2012 Automatically in about 2 mins.
You dont need to know anything about flashing.
You can use that Tool if your Device is in Bootloop/ Bootloader Mode and Normal State.
(Tested it from Bootloop/ Bootloader and from Normal State with Bootloader locked and some times with Bootloader unlocked)
I will update it with new Lollipop Builds for example 5.0.1 or so.
Would be nice if you try this out and give me Feedback!
Download(androidfilehost):
https://www.androidfilehost.com/?w=files&flid=22422
Changelog:
12092014 Release

I was a bit doubtful of this method bud I gave it a whirl and now I'm setting up lollipop. I'll let you know if there is any issues.
Had to run NTR to get my root back and also did not have a recovery. On the initial flash it brought me to a encrypted enter password screen so I had to work around that then it booted to start up.
On the plus side their is a camera app which has been missing on the other custom LP's I have flashed. My Rom Toolbox Pro works, which did not on the others. It's a bit slower than the f2fs rom's so I'm going to try and convert to that next. Thumbs up

PapaMag said:
I was a bit doubtful of this method bud I gave it a whirl and now I'm setting up lollipop. I'll let you know if there is any issues.
Had to run NTR to get my root back and also did not have a recovery. On the initial flash it brought me to a encrypted enter password screen so I had to work around that then it booted to start up.
On the plus side their is a camera app which has been missing on the other custom LP's I have flashed. My Rom Toolbox Pro works, which did not on the others. It's a bit slower than the f2fs rom's so I'm going to try and convert to that next. Thumbs up
Click to expand...
Click to collapse
??? This flashes STOCK Lollipop!

Julian_os said:
??? This flashes STOCK Lollipop!
Click to expand...
Click to collapse
I realized this right after I ran it. It's all good, this tool actually flashes a better working Lollipop than the custom ones that I have been running. My favorite apps are more friendly with this stock version. Run's a bit slower but still clocking over 20000 benchmark.
Thanks again looking forward to the 5.0.1 update.

Worked like a charm!

[Q] SYSTEM UI issues; How come I cannot install any "ghost" rom?

PRIMARY QUESTION: I cannot seem to install any "ghost" KitKat or Lollipop ROM on my XT1058. Can anyone please help shed some light on this? I've spent around a combined 12+ hours searching, researching, and tinkering trying to figure this out, but no success. I typically receive a "com.android.systemui" error message or "Unfortunately, System UI has stopped" message. After I acknowledge the message, it pops up again in a second or two. I have to force a shutdown of the phone and recover via TWRP. I've detailed my history and attempts below.
On the CM website, it says something about how "ghost" is a unified OS for every Moto X, except AT&T, since it's not unlockable. With Sunshine, shouldn't I be able to install the "ghost" ROM? Or does it not matter? I hope this isn't a case of, "even though you have an unlocked bootloader, the 'ghost' ROM isn't intended for your version of the phone." If that's true, it looks like all development on the XT1058 has pretty much stopped.
Many thanks, XDA Community, for helping me understand all this!
Secondary Questions:
I recently tried using the feature, "fixing permission" in TWRP thinking it might help with the "ghost" installations. I started getting bootloops when trying to restore to previous ROMs. The only restore that worked was my true original stock backup; the other restore attempts on SlimKat and other stock instances failed. That worries me. While I have successfully restored my phone, does anyone know if I may have screwed up my phone for the long-term?
(Answered by KidJoe; thank you!) Since I unlocked my bootloader at 4.2.2, can I freely upgrade and downgrade stock OSs? i.e., Can I install AT&T's stock 4.4.4 and then downgrade to 4.4.2?
(Answered by KidJoe; thank you!) Why do so many people seem to care to downgrade their stock OS? While I'm sure some may not be happy with some changes that come with upgrades, what could possibly be so "upsetting" that people need to downgrade?
HISTORY
Phone: AT&T Moto X XT1058, non-developer edition
Android: 4.2.2 | No attempt has been made to upgrade the OS beyond 4.2.2
Used Sunshine to unlock the bootloader while still on 4.2.2
Recovery: Installed TWRP v2.8.1.0, and I use TWRP to backup and install old and new ROMs (I think it's version 2.8.3... I never downloaded a version 2.8.1, but that's what the screen says. I'm wondering if the authors just forgot to update the version number in the program.)
Successful ROM installs:
SlimKat build 7 Official, msm8960dt
Cyanogenmod 11 Snapshot M5 msm8960dt (2014-04-05)
Failed ROM installs:
Cyanogenmod 11 Snapshot M12 ghost (2014-11-15)
Cyanogenmod 11 Nightly ghost (2014-12-19)
LiquidSmooth KitKat v3.2 Nightly ghost (2014-10-31)
LiquidSmooth Lollipop v4.0 Nightly ghost (2014-12-20)
Other Notes:
GApps were always installed when available. I also tried not installing them.

cxwong1 said:
Many thanks, XDA Community, for helping me understand all this!
Secondary Questions:
Since I unlocked my bootloader at 4.2.2, can I freely upgrade and downgrade stock OSs? i.e., Can I install AT&T's stock 4.4.4 and then downgrade to 4.4.2?
Why do so many people seem to care to downgrade their stock OS? While I'm sure some may not be happy with some changes that come with upgrades, what could possibly be so "upsetting" that people need to downgrade?
Click to expand...
Click to collapse
I will answer these two....
1. NO you can not. Once you have 4.4.2, 4.4.3 or 4.4.4 on your phone, do NOT attempt to downgrade, even if you have an unlocked bootloader... For more details see what I typed here -> http://forum.xda-developers.com/moto-x/general/4-4-4-downgrade-possibility-t2971847/post57563419 along with the other discussions in that SHORT thread.
2. The older root and write protection disable processes for a Moto X with a locked bootloader (like ATT and Verizon) rely on taking advantage of vulnerabilities in the 4.2.2 w/Camera update rom version, or the 4.4 rom. These processes walk you through downgrading your ROM to 4.2.2 w/Camera update and following a set of steps to upgrade which will keep root and disable write protection. NOTE: It was safe to downgrade from 4.4. to 4.2.2 w/Camera update when following the SlapMyMoto/MotoWpNoMo processes. But that was the only time it was safe!!!!

KidJoe, thank you much!
Does anyone else have any idea about my "systemui" issue?

cxwong1 said:
KidJoe, thank you much!
Does anyone else have any idea about my "systemui" issue?
Click to expand...
Click to collapse
Just got a Moto X 1st gen replacement from Motorola and getting same problem after unlocking/rooting. Have you found a fix for this? Or does anyone know how to fix? Spent all day working on this and its driving me nuts.

syckman said:
Just got a Moto X 1st gen replacement from Motorola and getting same problem after unlocking/rooting. Have you found a fix for this? Or does anyone know how to fix? Spent all day working on this and its driving me nuts.
Click to expand...
Click to collapse
Hey! Nope, I haven't found the answer, unfortunately. I haven't really tried to upgrade my OS since.

cxwong1 said:
PRIMARY QUESTION: I cannot seem to install any "ghost" KitKat or Lollipop ROM on my XT1058. Can anyone please help shed some light on this?
Click to expand...
Click to collapse
I bit the bullet yesterday and paid for the Sunshine bootloader unlock. After replacing the stock bootloader with TWRP and making a backup, I started looking into putting CyanogenMod onto it, as I had just updated a Galaxy Tab 2 7.0 to KitKat (via CyanogenMod 11) last week and it wasn't right that my phone had an older Android build than my tablet. I ran into conflicting information here and elsewhere, but the bottom line:
I have CyanogenMod 11 running on my AT&T Moto X.
More specifically, it's this zipball (remove spaces in next line to bypass the forum's lame link blocking):
https :// download.cyanogenmod.org / get / jenkins / 90775 / cm-11-20141115-SNAPSHOT-M12-ghost.zip
I also tried the latest 12.1 nightly, but while it appears to boot up, it reboots almost as soon as you try to set it up.
One thing that seems to help: before loading any ROM (whether stock, CyanogenMod, or whatever), wipe the flash. I have the ROM and Google Apps files on a flashstick that gets connected through an OTG cable, so I just tell TWRP to wipe everything but OTG storage, restore the ROM, let it boot up, then go back to TWRP to install the Google apps.
(Good thing I had the stock ROM backed up...had to revert to it this morning to back up aCar and Stocard data so I could bring them into CM.)
Starting configuration for my phone: AT&T XT1058, stock 4.4 firmware, rooted with the usual means for doing so, bootloader locked until Sunshine worked its magic.

Can't load recovery after flashing Stock image 5.1.1

Hi all-so I decided to flash back to stock since my 32GB Nexus was down to about 14GB from flashing ROMS and such.Everything seems to have gone smoothly however when I try the oem unlock command I am told that the device is already unlocked.I proceeded to root and then I tried to flash TWRP but I get permission denied.
Also,my Play Store just crashed when I try and type in an app to search for.
The question is-how do I know which factory image is right for my device?
There are a number of 5.1.1 images,I selected the one marked for all carriers except T-Mobile.Could I have selected the wrong image to be causing some of these problems?
Or should I just go ahead and jump up to 6.0.1-there is only 1 image for that release.
I would't think the image mattered that much but something is wrong here.
I got the phone last week from the Amazon sale and I activated it no problem on Verizon and flashed several ROMS no issue.
Advice is much appreciated.

I really don't understand why anyone would flash to an old version of a ROM. I appreciate that people have different tastes (e.g. don't like material design) or perceive different characteristics (e.g. better battery life) but in general each new ROM brings advantages, stability, security, improvements, so why stick with an old one when you can have new?
Me, I'd definitely go for a full clean install of MMB29K.
And if you insist on root, be aware of the issues with Marshmallow - you need a different kernel (Elementalx is popular) or alternatively flash TWRP and install Chainfire's SuperSU 2.62. I say 2.62 rather than 2.65 because there are numbers of people reporting that root doesn't work with 2.65, which isn't the case with 2.62, and from personal experience 2.62 works absolutely fine on my 6.0.1 N6.

dahawthorne said:
I really don't understand why anyone would flash to an old version of a ROM. I appreciate that people have different tastes (e.g. don't like material design) or perceive different characteristics (e.g. better battery life) but in general each new ROM brings advantages, stability, security, improvements, so why stick with an old one when you can have new?
Me, I'd definitely go for a full clean install of MMB29K.
And if you insist on root, be aware of the issues with Marshmallow - you need a different kernel (Elementalx is popular) or alternatively flash TWRP and install Chainfire's SuperSU 2.62. I say 2.62 rather than 2.65 because there are numbers of people reporting that root doesn't work with 2.65, which isn't the case with 2.62, and from personal experience 2.62 works absolutely fine on my 6.0.1 N6.
Click to expand...
Click to collapse
Thanks for the detailed response. I was running 5.1 initially because that is what the phone booted with and I like full-featured ROMS like BlissPop. I guess I'll give 6.0.1 a whirl.It just seemed like it was too new to be rock solid. I had as many features on my old S3 running 4.4.2 as I have seen since then if not more actually. I am curious about Google Now On Tap however.
Hopefully this gets me fixed up.Cheers.

chiadrum said:
Hi all-so I decided to flash back to stock since my 32GB Nexus was down to about .......
Click to expand...
Click to collapse
It is possible that the issue is caused because you downgraded the bootloader by flashing 5.1.1.
Flash the complete latest stock 6.0.1 images.

Flashing 6.0.1 now. Both times the CMD window has showed me archive does not contain boot.sig and recovery.sig. I am guessing that is normal?
The 5.1.1 started working fine after an update all but I still couldn't install TWRP fyi.
Let's see how Marshmallow tastes!

The "does not contain boot.sig and recovery.sig" is standard. I have no idea why it continues to appear version after version, but it has no effect on the installation.

chiadrum said:
Flashing 6.0.1 now. Both times the CMD window has showed me archive does not contain boot.sig and recovery.sig.
Click to expand...
Click to collapse
Same on my N6 when flashing 6.0.1. When 6.0.1 is running, you can flash TWRP recovery in fastboot mode.

NLBeev said:
Same on my N6 when flashing 6.0.1. When 6.0.1 is running, you can flash TWRP recovery in fastboot mode.
Click to expand...
Click to collapse
Thanks guys.

chiadrum said:
Thanks guys.
Click to expand...
Click to collapse
Ok more strangeness.pPhone is working fine,no issues.However I am unable to unlock bootloader using the fastboot OEM unlock command.
The message is "Not supported command in current status".
Yes,OEM unlock is allowed in Dev Options.I tried turning that off in case the indicator was faulty and then I couldn't even attempt to unlock,immediate failure.
Tried this several times after reboots as well.
Build MMB29K.
Any ideas?

Would it be too simple an answer to say that it's because the phone is already unlocked? You couldn't install a new ROM with a locked bootloader.
I myself have been a bit surprised by the peremptory & derogatory comments of some of the very senior members in these forums when people ask what seem to be questions with obvious answers, and I'm beginning to see their point...
Still, I also recognise that an "easy" question is one that you know the answer to, and I don't want to put people off asking questions. Being knocked back myself several times hasn't stopped me asking.

That's actually a very good point.Perhaps the image came boitloader unlocked.I'll see if I can flash TWRP and install something. I haven't loaded any roms since the initial flash,I was following protocol to unlock,root and then flash.Appreciate the help.Sometimes obvious seems too easy.

chiadrum said:
That's actually a very good point.Perhaps the image came boitloader unlocked.I'll see if I can flash TWRP and install something. I haven't loaded any roms since the initial flash,I was following protocol to unlock,root and then flash.Appreciate the help.Sometimes obvious seems too easy.
Click to expand...
Click to collapse
Confirmed I am an idiot.Device is unlocked already. Wasn't expecting that.The people way smarter than me who prepared that image took care of it for me.

Not an idiot at all. Like I said, an easy question is one that you know the answer to. Experience counts...
It's not the image that is unlocked - it's the device. Once unlocked, you have to specifically lock it again, but it's neither simple nor a good idea. An unlocked device gives you a far better chance to recover from errors.

GPS locks for Oreo Roms but will not follow when using navigation to go anywhere

Hi. I am at a loss on how to fix my GPS on my device. When using Lineage 7.1.2 I can use Google Maps without issue and use navigation to get me places. When I try and use ANY Oreo ROM I can get a GPS lock only on my current location however I can not use navigation; the device stays locked to the start point and will not follow me. When Oreo first came out I was able to upgrade to Oreo and use Maps without issue. I am somewhat a flashaholic and like trying different ROMS to see how they work day to day so I have flashed GZOP, Cardinal, Omni, Lineage 15. I have tried all different Firmware updates by Lord Boeffla trying 4.1.7 (Which I am currently using and Lineage 7.1.2 navigation works) 4.5.0 and 4.5.1 to try and rectify this but it does not matter. No matter what firmware I try and use the results are the same. Lock but will not follow At one point I even tried downgrading to Stock 3.5.4 firmware and software to which I was able to flash but the system would not boot only would bootloop. At this point I am not able to flash any stock OOS ROMS and I must use a custom built ROM such as Lineage to get the phone to boot. I have tried many GPS fix apps such as AGPS to try and force clear GPS cache and reset they system but the results are the same. Lock and no follow. Any ideas on what else can be tried to resolve this? I fear I may have damaged the device throuh flashing the firmware so many times and I will be stuck with Nougat forever with the current phone.

All Oreo ROM's are in Alpha/Beta build stages. I've experienced similar results on many Oreo ROMs. The best course of action you can take is providing logs to the developers of the consecutive ROM, and let them work.
Different firmware versions don't make any difference to the GPS. ROM's are built on top of the firmware, and such. Flashing different firmware's will not fix the issue. Go back to Nougat if you want a stable system.
The issue here is you're complaining about bugs on Alpha/Beta ROM's.

I have been facing the same problem in Nougat Roms too. I think it has been introduced in 4.1.7
The only course of action would be to get it fixed in Beta OOS by providing the logs to the devs.
Here's a related thread :
https://forum.xda-developers.com/oneplus-3t/help/poor-gps-oos-4-1-7-t3664864

Had same issue, refresh latest beta firmware.

I've no issue using gmaps on ob 17 I use it daily.

CPU 100% frequency.

Hello,
I apologize in advance for my English.
I'm using nexus 6, stock 7.1.1 no root, no unlock bootloader ....
The problem is that my cpu2,3 is still running at 100% frequency.
I tried flash, factory reset ... nothing helps.
Before that, I had a root and I played with thermal config so that the kernels did not turn off at 40% of the battery.
I'm running now stock and the kernels behave like this ...
Please help, I'm quite desperate, my battery is gone, my phone is hot.
I discovered that this usually happens when the battery falls to about 35%, the two cores turn off, and when I charge the kernels are connected but the frequency is still 2649mhz.

Do you have an old battery?
You might try resetting the bootloader logs and see if that gives you any relief.
1) Power off your phone
2) Press and simultaneously hold the Power and Volume Down buttons putting the phone in fastboot mode
3) Use the Volume buttons and scroll through the menu until you see "Bootloader logs"
4) Press and hold the power key for 7+ seconds until the phone reboots normally
5) On boot, fully charge the battery
If you see some improvement as a result of those steps, consider replacing the battery.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

Hello,
the battery is one month old.
This bug started after I tried different rom and kernels .... I tried also to change the BCL and wrote in a set of thermal engine.
Now, even after the flash stock rom these things happen, with a load of 0% and a frequency of 2649mhz.
I noticed that we just made stock 7.1.1 when I'm 5.1.1 so I'm going without a mistake.
I apologize for writing English through the translator

It's possible it's still the battery. But I'm not certain what the following means;
zip545 said:
I noticed that we just made stock 7.1.1 when I'm 5.1.1 so I'm going without a mistake.
Click to expand...
Click to collapse
Are you still on 5.1.1?
If that is right, then the thing to do is update to the last stock release. The easiest way to do that is probably using ADB sideload with a factory full OTA.
You can also fastboot flash the full factory image (confusing I know, but full factory and full OTA are different).
The instructions on each of those google sites are good. On the second one, where you would be fastboot flashing, the N6 is an older device so when 2 possible commands are suggested, use the one indicated as for older devices.
Also, instead of installing the full Android SDK, you could use Minimal ADB and Fastboot.
This thread should help.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

I tried this procedure about 5x ...
I do not know anymore so I'm writing to you where you have more experience ...
I was on 5.1.1 and flash ota update helped adb on 7.1.1 and so far everything goes well. I will check if the processor does not go all the way to 2649mhz.
As I say it all started by trying out rom, different kernels and editing a set of thermal engine .....
Is it possible that full factory image does not return all files ???
I have a screenshot but I can not send it here because I'm new.

If you did a full return to stock after trying the kernels you mention, all of those changes are gone.
When you flash a kernel, it's the same as the boot image. So when you sideload or fastboot flash the stock ROM, the boot image is returned to stock and your previous changes are gone.
I'm wondering if you had matched the kernels to the ROM version you were running. If you flashed a 7.x kernel on a 5.1.1 ROM, that might cause the trouble you had.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

I did some searching to refresh my memory. It's been a long while since 5.x [emoji6]
If all of your maxed cpu problems occurred while you were running 5.1.1, then I think it's likely a DNS bug that was around back then may have been the root cause of your problems.
If you still experience the cpu problems on 7.1, then it's not likely due to that bug.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

I probably wrote it wrong ....
I used android 7.1.1, no 5.1.1
I installed the lineage os14.1, I changed the thermal engine file so that two cores did not shut down at 40% of the battery.
I also installed the script to turn off the BLC which is here on the forum.
Then I installed the stock 7.1.1 and did the same, it did not work so I installed the Elementalx kernel.
Then I installed the factory image 7.1.1 and you noticed that the 2.3 core is ON 2649mhz! This was done even when the battery was 100%, 80% .....
Nothing helped, factroy reset, installing factory image ... just nothing
Then I installed stock 5.1.1 and everything worked out!
On stock 5.1.1 the processor was driving normally, then I factorydled again factory 7.1.1 and again the CPU kernels went nonstop to 2649mhz.
Now it seems that the processor is running normally, I am in the testing phase 7.1.1.