Database Info

[Bootloader] JZO54K Bootloader

Here is the bootloader in a zip that can be flashed over anything.
I recommend flashing this because it fixes the issue where you couldn't boot into recovery from the bootloader.
Download (Mediafire)
Download (Goo.im)
MD5: a8715642fcb0400579dde21b5e4cc673

yeah,finally!!!!
it's my fisrt need in absolute in all my device the fix of the reboot-to-recovery from bootloader's bug...many times away from pc i bootlooped the n7 by my tests,and i had to wait hours to came back home to connect to pc...very good by google!:laugh:
On another side,i think is abolsutely right flash this BL and continue using a 4.1.1 rom instead of new base...right?
EDIT Wow,is very light a bootloader for nexus 7...compared tol for example a gnex one..

Odd...doesn't fix the boot into recovery bug for me. At least with TWRP.

In the german android-hilfe forum someone soft bricked his N7 by flashing this (He got a bootloop and cannot Boot into the CWM anymore).
Can someone confirm that the zips are functional or not?

I downloaded from the meadifure link in his forum on rw, installed it through clockworkmod touch and haven't had any problems. Booting to recovery from the bootloader works fine for me.
Sent from my Nexus 7 using xda premium

Thanks for this, for some reason when I updated to 4.1.2 OTA using CWM everything went fine no errors but it didn't actually update my bootloader which is odd. So I was able to update it using the CWM zip provided. Thanks!

Thanks for this! Flashed without issues.
Skickat från min Nexus 7 via Tapatalk 2

How would this affect my ability to hide breaching my warranty? Would replacing the bootloader that was shipped with the device give me away, or does an OTA update flash the new one anyway?

z1gackly said:
How would this affect my ability to hide breaching my warranty? Would replacing the bootloader that was shipped with the device give me away, or does an OTA update flash the new one anyway?
Click to expand...
Click to collapse
Update is supposed to flash new one anyway
---------- Post added at 11:13 PM ---------- Previous post was at 11:00 PM ----------
Worked fine here, thanks a lot
TWRP and PA 2.1799

how do we flash this? i have cm10 running. Thanks in advance

this,in recovery cwm...or via fastboot if you found the .img,but this case is from cwm

sert00 said:
in recovery cwm of course.(or twrp)
Click to expand...
Click to collapse
Thanks i tried that and i ended up with boot loops. I managedto flash the grouper bootloader and booted up. What am i missing or doing wrong?

Worked great for me, thanks OP.

Thanks, worked for me on JRO03S ROM.
Sent from my Nexus 7

Thanks OP worked like a charm!!!
Sent from my Nexus 7 using XDA Premium HD app

Crazy4G1 said:
Thanks i tried that and i ended up with boot loops. I managedto flash the grouper bootloader and booted up. What am i missing or doing wrong?
Click to expand...
Click to collapse
Did you double-check the MD5 hash of the download to ensure it wasn't corrupted in the downloading process?

Ahh dang i got a bootloop, I can get into fastboot mode but recovery is a no go, any suggestions?

Same im stuck at google logo, cant get into recovery. Any ideas?

Pithism said:
Same im stuck at google logo, cant get into recovery. Any ideas?
Click to expand...
Click to collapse
I'm bout to factory reset with the nexus 7 toolkit, just for reference which link did you download from?
---------- Post added at 02:18 AM ---------- Previous post was at 01:51 AM ----------
Okay i was able to factory reset and got out of the bootloop. But I lost all my data(which is my fault for not making a backup to my pc). OP should really post the md5 so we can check it.

Dl'd via goo link, but used browser to access. Flashed via teamwin, wiped, profit. PA 2.14
sent secretly from my paranoid 7

[DEVS][OTA] Original M7UL 4.4.3 OTA update zip

The original update OTA can be obtained here: WWE_4.07.1700.4-3.62.1700.1_KTU84L.H4_release_377648
This cannot be flashed unless your device meets all requirements. Wait for a ROM otherwise.

Can someone with the latest version of the stock 4.4.2 GPE help me out! Need one file to update to 4.4.3!
http://forum.xda-developers.com/showthread.php?t=2772266
Thanks!

Orginator said:
Can someone with the latest version of the stock 4.4.2 GPE help me out! Need one file to update to 4.4.3!
http://forum.xda-developers.com/showthread.php?t=2772266
Thanks!
Click to expand...
Click to collapse
Googling for this MD5 first gives me your postings (scattered across XDA ) as well as this link: http://rghost.net/53665485
EDIT: file has been deleted.

sanderg said:
Googling for this MD5 first gives me your postings (scattered across XDA ) as well as this link: http://rghost.net/53665485
EDIT: file has been deleted.
Click to expand...
Click to collapse
Trust me, the first thing I do is google.. been there, done that! Yeah sadly deleted and I'm still stuck at 4.4.2, so many must have made a CWM backup before updating to 4.4.3, yet so hard to get that file :/

Orginator said:
Trust me, the first thing I do is google.. been there, done that! Yeah sadly deleted and I'm still stuck at 4.4.2, so many must have made a CWM backup before updating to 4.4.3, yet so hard to get that file :/
Click to expand...
Click to collapse
What if you manually edit updater-script to not patch Youtube?

I could do that, but then I'll have the same issue on next OTA! I'd rather have a 100% clean update, if you know what I mean!

Could you make a ROM GPE with Sense camera ?

Orginator said:
I could do that, but then I'll have the same issue on next OTA! I'd rather have a 100% clean update, if you know what I mean!
Click to expand...
Click to collapse
Mine fails as well - on basicDreams.apk. It doesn't look like it can be applied to every device, e.g. when integrating apps into the ROM using Titanium Backup it will most likely fail. Will be taken care of by the ROM devs though.

sanderg said:
Mine fails as well - on basicDreams.apk. It doesn't look like it can be applied to every device, e.g. when integrating apps into the ROM using Titanium Backup it will most likely fail. Will be taken care of by the ROM devs though.
Click to expand...
Click to collapse
I don't use Titanium Backup or anything alike.

Can we flash this OTA.zip from stock recovery after we returned back to Google Edition ?

HAAANG ON!! hang on......
this....is a 4.xx.xxxx.x update
previous was 3.62.xxxx.x
....I may assume that is like a....major release or something...?
I expect a good improvement, even in performance (that on sense roms is always 2 times better, dunno why)

Can we flash this?
Sent from my HTC One using Tapatalk

gaja22 said:
Could you make a ROM GPE with Sense camera ?
Click to expand...
Click to collapse
No
---------- Post added at 06:13 AM ---------- Previous post was at 06:12 AM ----------
throcker said:
HAAANG ON!! hang on......
this....is a 4.xx.xxxx.x update
previous was 3.62.xxxx.x
....I may assume that is like a....major release or something...?
I expect a good improvement, even in performance (that on sense roms is always 2 times better, dunno why)
Click to expand...
Click to collapse
Stick to your sense ROM then because performance hasn't changed much between 4.4.2 and 4.4.3
---------- Post added at 06:13 AM ---------- Previous post was at 06:13 AM ----------
mrgwap said:
Can we flash this?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Don't think so, it's an OTA file that needs to be installed by the stock recovery, not a custom recovery.

Nic2112 said:
No
---------- Post added at 06:13 AM ---------- Previous post was at 06:12 AM ----------
Stick to your sense ROM then because performance hasn't changed much between 4.4.2 and 4.4.3
---------- Post added at 06:13 AM ---------- Previous post was at 06:13 AM ----------
Don't think so, it's an OTA file that needs to be installed by the stock recovery, not a custom recovery.
Click to expand...
Click to collapse
About to RUU back to 4.4.2 with stock recovery.
What do I do afterwards. I have the file in the OP downloaded. Do I just place it in root storage and look for a update than root afterwards.

charlieb620 said:
About to RUU back to 4.4.2 with stock recovery.
What do I do afterwards. I have the file in the OP downloaded. Do I just place it in root storage and look for a update than root afterwards.
Click to expand...
Click to collapse
All I had to do was RUU to 4.4.0 because that's the one I had handy, let the phone OTA to 4.4.2, and when it booted all I had to do was hit the "check for update" button 2-3 times and then it prompted me to download the OTA and voila, 4.4.3

Nic2112 said:
All I had to do was RUU to 4.4.0 because that's the one I had handy, let the phone OTA to 4.4.2, and when it booted all I had to do was hit the "check for update" button 2-3 times and then it prompted me to download the OTA and voila, 4.4.3
Click to expand...
Click to collapse
Alright I will do the RUU and just check for Update.

charlieb620 said:
Alright I will do the RUU and just check for Update.
Click to expand...
Click to collapse
You would have to put the OTA at the right location and name it exactly what the recovery expects and I don't know how to do that.
Thing is with stock recovery, there are no options, it either updates or resets to factory default.

can someone make a flashable zip of the rom? Wouldn't really want to go thru all the trouble of converting back to stock recovery and rom to update since im on a custom rom now? A flashable zip would mean a lot!

ace-user said:
can someone make a flashable zip of the rom? Wouldn't really want to go thru all the trouble of converting back to stock recovery and rom to update since im on a custom rom now? A flashable zip would mean a lot!
Click to expand...
Click to collapse
Just wait a day or two.

I haven't really noticed a performance increase or decrease tbh after flashing the new firmware. It says "5.11.401.10" because I edited the android-info.txt file. But the date is 5/16/2014, to confirm that it is the newer v1.54 hboot. How would I go about making a deodex system dump into a flashable rom.zip? I have the system dump if someone can help me with the procedure.

Nexus 5 with "TeamWin" failed update - and won't start again

Hello everyone.
Two hours ago I received the notification about the Android 5.0 update. I downloaded it and hit "Install". Then, "TeamWin" started, but not the update. I rebooted into System and tried to update again - but it tells me that 4.4.4 is the latest version I can get now. I'm on Build KTU84P now.
1) Do I need to remove TeamWin? If yes, with what?
2) How can I start the update again? I'm on a super slow connection and it would hurt to download the 500 MB again…
Thank you!

Fablus said:
Hello everyone.
Two hours ago I received the notification about the Android 5.0 update. I downloaded it and hit "Install". Then, "TeamWin" started, but not the update. I rebooted into System and tried to update again - but it tells me that 4.4.4 is the latest version I can get now. I'm on Build KTU84P now.
1) Do I need to remove TeamWin? If yes, with what?
2) How can I start the update again? I'm on a super slow connection and it would hurt to download the 500 MB again…
Thank you!
Click to expand...
Click to collapse
You need to remove TeamWin, and load up your stock recovery. I don't have the exact instructions for this unfortunately.
The OTA update will come back to your phone soon, usually. Did for me within the hour.
The issue I am having now, back with stock recovery, is during the install I am getting a dead Android error icon, and can't continue. Looking for any help I can, and hopefully it will help you too.

Mysticodex said:
You need to remove TeamWin, and load up your stock recovery. I don't have the exact instructions for this unfortunately.
The OTA update will come back to your phone soon, usually. Did for me within the hour.
The issue I am having now, back with stock recovery, is during the install I am getting a dead Android error icon, and can't continue. Looking for any help I can, and hopefully it will help you too.
Click to expand...
Click to collapse
Maybe we need http://forum.xda-developers.com/google-nexus-5/general/stock-checker-zip-prepare-ota-t2927865?
Gosh, this used to be so easy all the time.

if you are using twrp, why the heck are you trying to install the ota? why not download(from xda) and flash a recovery flashable stock or aosp build, and make life much easier for yourself? heck, i dirty flashed from 444 to 5.0 via an aosp flashable zip without any issues, and kept all my data.

simms22 said:
if you are using twrp, why the heck are you trying to install the ota? why not download(from xda) and flash a recovery flashable stock or aosp build, and make life much easier for yourself? heck, i dirty flashed from 444 to 5.0 via an aosp flashable zip without any issues, and kept all my data.
Click to expand...
Click to collapse
I've read http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523 and it clearly states
-Do a factory reset (maybe you can keep data coming from STOCK 4.4.4 - maybe)
Click to expand...
Click to collapse
And I didn't want to count on a maybe.

I'm using stock recovery, rooted as per normal, and a custom kernal. OTA is giving an Android dead error, with no text. Trying to figure out how to diagnose this.

Fablus said:
I've read http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523 and it clearly states
Click to expand...
Click to collapse
it clearly states what? to use recovery version 2.8+? i used an older version, twrp version 2.6.2.4. what else?
---------- Post added at 05:51 PM ---------- Previous post was at 05:48 PM ----------
Mysticodex said:
I'm using stock recovery, rooted as per normal, and a custom kernal. OTA is giving an Android dead error, with no text. Trying to figure out how to diagnose this.
Click to expand...
Click to collapse
it wont flash over a rooted rom anymore as of lollipop. you can flash the factory img via fastboot though, in your bootloader.

simms22 said:
it clearly states what? to use recovery version 2.8+? i used an older version, twrp version 2.6.2.4. what else?
---------- Post added at 05:51 PM ---------- Previous post was at 05:48 PM ----------
it wont flash over a rooted rom anymore as of lollipop. you can flash the factory img via fastboot though, in your bootloader.
Click to expand...
Click to collapse
Trying to remove the root right now via SuperSU. I am hopeful it will work better afterwards.
Edit: SuperSU unrooted it, rebooted, did OTA again, error again. Is there no way to find out what this error is?

[ROM] MCG24.251-5 100% Stock

Flash using TWRP. This will flash all files in the MCG24.251-5 update except for recovery.
New features in this update that I've noticed:
-Marshmallow, aged to perfection in Verizon's own servers. Only one major release version obsolete, and with outdated security patches!
-WiFi calling (woooooo! Those custom roms just got another carrier-specific, unportable feature to compete with)
-The command center widget has been replaced with the Droid Turbo 2 version
Get it here: https://mega.nz/#!G1xg1aYa!fm2hUL7hDDVaxTAj_iPbtY61P-8VrQEvoOJiVsDtdho
Here's the stock recovery image if you want it: https://mega.nz/#!r1wDQRCJ!KHbo_Q6L-WE_VyB1x8W4FbT6PrerPEyn9H1C6VUAyf8
Flashing this rom updates the bootloader to a version that can communicate with the kernel to tell SafetyNet that it is unlocked, causing it to fail. Fret not, however, as there are two options to fix this:
OPTION 1: Flash the SU4TL-49 bootloader using the following TWRP package: https://mega.nz/#!6logEaIQ!q8qPJw65Upt38Hxiu1JyxErmwbgL7CBzuGzzPC0C9pQ
OPTION 2: Flash this patch made by @bhb27: https://www.androidfilehost.com/?fid=745425885120696423
Wipe cache and dalvik/art cache after either of these options.
NOTE that these options only fix failures due to SafetyNet checking the bootloader status. It will still fail due to root, xposed and the like. There are no known consequences or side effects to either of these options, so just pick whichever one you feel like.
If you notice weird things after you flash this rom (long boots other than the first one which is supposed to be long, random reboots, etc.) try flashing the stock recovery image and factory resetting.
If you want root, flash this version of SuperSU first, then flash whatever newer version you want: https://download.chainfire.eu/751/SuperSU/
If you have trouble flashing this, try TWRP Mod 3 instead of Mod 4.

Ouch, you have almost full flash inside archive, with bootloader too... Who is the most brave, introduce yourself ))
+ mirror

I can confirm that it works on old bootloader.
I had SULT-49 5.1 installed before and I just flashed this via TWRP. I haven't taken the OTA. It works perfectly. Thank you.
PS: My bootloader now is moto-apq8084-70.95 (2016-06-29). Do you have same version after taking OTA?

Did you have to wipe the system, data and cache first like you would with a new ROM or just dirty flash it?
Sent from my XT1254 using Tapatalk

Thanks OP

rickyblaze13 said:
Did you have to wipe the system, data and cache first like you would with a new ROM or just dirty flash it?
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
When in doubt, always wipe.

Hey everyone, what is your safetynet status with this rom? It's failing for me, and I can't figure out why.

rickyblaze13 said:
have to wipe the system, data and cache first
Click to expand...
Click to collapse
It works w/o, but, IMO, better wipe, than not. You don't need extra bugs, right )

It's completing setup now, I did a wipe after I backed up my phone. It's unlocked and rooted before I flashed the zip
Sent from my QMV7A using Tapatalk

Can we get this ULed to Dropbox or Google Drive? The Mega link and the mirror are taking forever...

Crowick said:
Can we get this ULed to Dropbox or Google Drive? The Mega link and the mirror are taking forever...
Click to expand...
Click to collapse
My google drive is full and I don't have Dropbox. But if you wanted to mirror it, I will gladly add the link to the OP.

Sure, I'll throw it up on Google Drive. Do you have just the MM stock recovery kicking around?
---------- Post added at 04:08 AM ---------- Previous post was at 03:50 AM ----------
Google Drive link to the TWRP Flashable version in your OP hosted on Mega.
https://drive.google.com/open?id=0BzQJqGBWW9ViQzFjTWJVUVZNazg

Crowick said:
Sure, I'll throw it up on Google Drive. Do you have just the MM stock recovery kicking around?
---------- Post added at 04:08 AM ---------- Previous post was at 03:50 AM ----------
Google Drive link to the TWRP Flashable version in your OP hosted on Mega.
https://drive.google.com/open?id=0BzQJqGBWW9ViQzFjTWJVUVZNazg
Click to expand...
Click to collapse
thanks for gdrive mirror

Crowick said:
Sure, I'll throw it up on Google Drive. Do you have just the MM stock recovery kicking around?
---------- Post added at 04:08 AM ---------- Previous post was at 03:50 AM ----------
Google Drive link to the TWRP Flashable version in your OP hosted on Mega.
https://drive.google.com/open?id=0BzQJqGBWW9ViQzFjTWJVUVZNazg
Click to expand...
Click to collapse
I don't. I don't know how I would get it since I need root access to get it, and I can't get root access without TWRP, and I have to overwrite the stock recovery to get TWRP.

TheSt33v said:
I have to overwrite the stock recovery to get TWRP.
Click to expand...
Click to collapse
fastboot boot TWRP.img

s5610 said:
fastboot boot TWRP.img
Click to expand...
Click to collapse
Nice! Good call.
https://mega.nz/#!r1wDQRCJ!KHbo_Q6L-WE_VyB1x8W4FbT6PrerPEyn9H1C6VUAyf8

Is anyone else having exceptionally long reboot/start times for their phone after flashing this rom?

Just the first boot after flashing
Sent from my XT1254 using Tapatalk

Thanks for that! Did anybody try to install it right over SU4TL-44? Just in case, I'm rooted, using xposed and twrp.

TheSt33v said:
Hey everyone, what is your safetynet status with this rom? It's failing for me, and I can't figure out why.
Click to expand...
Click to collapse
Perhaps this:
https://www.xda-developers.com/android-safetynet-now-reportedly-tripped-by-unlocked-bootloaders/
I just tried using AP a few hours ago and it failed with the screen in the article. OTA with unlocked bootloader.

We might be able to install updates without restoring the official system

We might be able to install OTA without restoring the /system /boot and so on.
In /system/usr/bin there are a few programs for installing and checking the OTA package,
One of them is "update_engine", which is called just before my update fails, it returns:
Code:
update_engine: [1124/214750:ERROR:utils.cc(193)] fd >= 0 failed: No such file off directory
Later it tries to read from fstab and return a hash of a partition which fails, because it is modified.
Do you think it is possible to trick it in to returning positive hash or am I wrong.
More info in the screenshot.
EDIT: added OTA log

Bump.
I'd love an easy solution for this as well! I'm unlocked/rooted/stock and would love an easier way to apply OTA updates than waiting for someone to post the full patched firmware.

hugehead83 said:
Bump.
I'd love an easy solution for this as well! I'm unlocked/rooted/stock and would love an easier way to apply OTA updates than waiting for someone to post the full patched firmware.
Click to expand...
Click to collapse
1) Just flash the lastest stock firmware over your current install but don't wipe 'userdata'.
2) Take the latest OTA
3) Re-root.
Takes 10-15 min tops.

ptn107 said:
1) Just flash the lastest stock firmware over your current install but don't wipe 'userdata'.
2) Take the latest OTA
3) Re-root.
Takes 10-15 min tops.
Click to expand...
Click to collapse
Why wouldn't you just flash the latest update instead of going through all that?

ptn107 said:
1) Just flash the lastest stock firmware over your current install but don't wipe 'userdata'.
2) Take the latest OTA
3) Re-root.
Takes 10-15 min tops.
Click to expand...
Click to collapse
I keep getting E: failed to mount / in recovery

Ok, I did some more digging and as it turn out, even when I restored my phone to stock and tried to install from OTA, it somehow set the ROOTED flag to true, I don't understand why since my deice wasn't rooted at that moment.

TeamRainless said:
Why wouldn't you just flash the latest update instead of going through all that?
Click to expand...
Click to collapse
That only works if you are not rooted unfortunately : (
---------- Post added at 02:45 PM ---------- Previous post was at 02:27 PM ----------
ptn107 said:
1) Just flash the lastest stock firmware over your current install but don't wipe 'userdata'.
2) Take the latest OTA
3) Re-root.
Takes 10-15 min tops.
Click to expand...
Click to collapse
Thanks,
I've been looking for the latest stock firmware but can't find it anywhere. Also: wouldn't the latest stock firmware also include the latest OTA?

hugehead83 said:
That only works if you are not rooted unfortunately : (
---------- Post added at 02:45 PM ---------- Previous post was at 02:27 PM ----------
Thanks,
I've been looking for the latest stock firmware but can't find it anywhere. Also: wouldn't the latest stock firmware also include the latest OTA?
Click to expand...
Click to collapse
There is a collection of them on afh

hugehead83 said:
That only works if you are not rooted unfortunately : (
---------- Post added at 02:45 PM ---------- Previous post was at 02:27 PM ----------
Thanks,
I've been looking for the latest stock firmware but can't find it anywhere. Also: wouldn't the latest stock firmware also include the latest OTA?
Click to expand...
Click to collapse
Not necessarily. The latest firmware usually lags behind the latest OTA by a month or more. The latest flashable firmware is OPWS28.46-21-14 (Oct patch) and the latest OTA is OPWS28.46-21-16 (Nov patch).

ptn107 said:
The latest flashable firmware is OPWS28.46-21-14 (Oct patch) and the latest OTA is OPWS28.46-21-16 (Nov patch).
Click to expand...
Click to collapse
True. This is what I ended up doing, and it worked out ok:
- Took a nandroid backup in TWRP as a precaution (takes ~10-20 mins)
- Flashed full firmware from October w/o data wipe (took 2-3 mins)
- Booted normally. It took a few minutes for the "check for updates" to work, but eventually the November patch came in. It actually took ~20-30 minutes to apply.
- Rebooted to bootloader, then booted to TWRP img and pushed zips for TWRP and Magisk. (~5 mins)
- Booted normally, applied ad-blocker stuff
- Rebooted back to bootloader to flash the better boot logo
- Rebooted normally, all done.

hugehead83 said:
True. This is what I ended up doing, and it worked out ok:
- Took a nandroid backup in TWRP as a precaution (takes ~10-20 mins)
- Flashed full firmware from October w/o data wipe (took 2-3 mins)
- Booted normally. It took a few minutes for the "check for updates" to work, but eventually the November patch came in. It actually took ~20-30 minutes to apply.
- Rebooted to bootloader, then booted to TWRP img and pushed zips for TWRP and Magisk. (~5 mins)
- Booted normally, applied ad-blocker stuff
- Rebooted back to bootloader to flash the better boot logo
- Rebooted normally, all done.
Click to expand...
Click to collapse
Did this reset the modified flag in booloader?

vidra said:
Did this reset the modified flag in booloader?
Click to expand...
Click to collapse
I cannot recall or say for sure, but if you can tell me where specifically to look for that I'll check for you.