Database Develop

[ROM] Verizon i815 STOCK ICS rooted IMM76D.LP11 - Verizon OTA as CWM flashable ROM

UPDATE: My hosting I had for XDA related work expired, so I re-uploaded everything here: http://www.mods4cars.com/pub/xda
Here's the new Verizon OTA packaged up as a full CWM flashable ROM. Wiping should not be necessary if you are coming from our last ICS ROM (LP10).
This is meant for those who have CWM installed and for those who modified their system to the point that the OTA does not work because it expects certain files.
If you are on full stock (rooted) ICS LP10 and are not getting the OTA update the regular way, you can look here for a way to manually install it:
http://forum.xda-developers.com/showthread.php?t=1932597&page=26
The rom is pre-rooted. After installing, run super-su and let it check for binary updates. Also a cached copy of su for restoring with Voodoo OTA rootkeeper is included (for extra safety).
Part1: The ROM
Install with CWM
http://electron73.org/XDA/i815/electron_ICS-LP11_i815.zip
Part2: The MODEM
Flash with ODIN in PHONE section
http://electron73.org/XDA/i815/electron_ICS-LP11_i815_modem.tar
Part3 (optional): Stock Recovery
If you want to be full stock afterwards, flash with ODIN in PDA section
http://electron73.org/XDA/i815/electron_ICS-LP11_i815_recovery.tar
Part4 (optional): Stock SBL
If you did all 3 parts above and want to be able to receive future Verizon OTA's flash this in ODIN in BOOTLOADER section
http://electron73.org/XDA/i815/electron_ICS-LP11_i815_sbl.tar
Enjoy

Many thanks!

Thanks Electron. You da man for us i815 owners.

Many thanks! I just decided to go back to stock for stability reasons. Your method works perfectly.
I don't know where many of us i815 users would be without your help. Thanks again man!
Sent from my Galaxy Nexus using xda premium

Gilbot said:
Many thanks! I just decided to go back to stock for stability reasons. Your method works perfectly.
I don't know where many of us i815 users would be without your help. Thanks again man!
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
So I was installing the ROM zip in CWM and it froze at "double-checking /data partition." Am I hosed?

esoh said:
So I was installing the ROM zip in CWM and it froze at "double-checking /data partition." Am I hosed?
Click to expand...
Click to collapse
How long did you wait?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

electron73 said:
How long did you wait?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
20 mins or so. I was getting no movement on the status bar. I rebooted and I can get into Odin mode and I was able to get into CWM once, but that's it. Otherwise it just hangs on the Samsung Galaxy Tab 7.7 screen.
---------- Post added at 09:17 PM ---------- Previous post was at 09:12 PM ----------
esoh said:
20 mins or so. I was getting no movement on the status bar. I rebooted and I can get into Odin mode and I was able to get into CWM once, but that's it. Otherwise it just hangs on the Samsung Galaxy Tab 7.7 screen.
Click to expand...
Click to collapse
So I wound up getting back into CWM and tried reflash and it's going now. Will let you know result

esoh said:
20 mins or so. I was getting no movement on the status bar. I rebooted and I can get into Odin mode and I was able to get into CWM once, but that's it. Otherwise it just hangs on the Samsung Galaxy Tab 7.7 screen.
---------- Post added at 09:17 PM ---------- Previous post was at 09:12 PM ----------
So I wound up getting back into CWM and tried reflash and it's going now. Will let you know result
Click to expand...
Click to collapse
Did you have lots of apps installed? I just realized it's doing a run_program("/tmp/fsck.ext4", "-Dfy", "/dev/block/mmcblk0p10");
on the data partition. If that partition is full with lots of files then the check might take a while. The status bar doesn't move while this command is executing. I never tried it on a "full" partition! A freshly wiped data partition is checked in 2 seconds

electron73 said:
Did you have lots of apps installed? I just realized it's doing a run_program("/tmp/fsck.ext4", "-Dfy", "/dev/block/mmcblk0p10");
on the data partition. If that partition is full with lots of files then the check might take a while. The status bar doesn't move while this command is executing. I never tried it on a "full" partition! A freshly wiped data partition is checked in 2 seconds
Click to expand...
Click to collapse
Yeah, I had about 100 apps installed. In any case, I tried it again through CWM. When it did the check this time, it took about 10 secs. So the first one must've been a hiccup or something. I was able to flash ROM and then radios through ODIN, so I think I'm good. I looked at the files on the internal storage and the SD card and they are still there, so I'm assuming that I'm good. Anything else to check or are there any log files that you want me to try to grab for you? Thanks again.

esoh said:
Yeah, I had about 100 apps installed. In any case, I tried it again through CWM. When it did the check this time, it took about 10 secs. So the first one must've been a hiccup or something. I was able to flash ROM and then radios through ODIN, so I think I'm good. I looked at the files on the internal storage and the SD card and they are still there, so I'm assuming that I'm good. Anything else to check or are there any log files that you want me to try to grab for you? Thanks again.
Click to expand...
Click to collapse
Hmm ok, definitely good to hear that it ran through the 2nd time. Maybe I should kick the FS checks out. They are still left over from last time where we had all those partition problems...
If you want, go check in the /cache dir for any log files left by CWM, maybe there's something in there.
Btw. Thank you for the generous donation! It is very much appreciated
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

electron73 said:
Hmm ok, definitely good to hear that it ran through the 2nd time. Maybe I should kick the FS checks out. They are still left over from last time where we had all those partition problems...
If you want, go check in the /cache dir for any log files left by CWM, maybe there's something in there.
Btw. Thank you for the generous donation! It is very much appreciated
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
I think the logs from the successful install are there but I don't see anything from the unsuccessful one, as far as I can tell.
RE: the donation, I meant to give you something from the original LP10 update and I just plumb forgot (after telling you that I was going to send something), so I figured that there was some interest involved. Thanks to all of your hard work.
---------- Post added at 10:47 PM ---------- Previous post was at 10:45 PM ----------
esoh said:
I think the logs from the successful install are there but I don't see anything from the unsuccessful one, as far as I can tell.
RE: the donation, I meant to give you something from the original LP10 update and I just plumb forgot (after telling you that I was going to send something), so I figured that there was some interest involved. Thanks to all of your hard work.
Click to expand...
Click to collapse
Also, regarding the current ROM, I really curious about the supposed batt life increases. My tab at this point is barely getting 4-5 hours screen time with it set fairly dim. Is that normal or should I be getting more that that? I don't suppose that a ROM update will help with screen time much, but just curious to hear what others are getting.

Update was painless
Sent from my SCH-I815 using xda app-developers app

My battery life is just shy of 8 hours with 40% brightness, wifi and 4G on. GPS off. This is better than LP10.

The first step went flawlessly using TWRP. I'll flash the LP11 modem.bin tonight using Odin.
Thanks for this, Electron. I'm about to make another small donation to your beer (or whatever) fund!

jkrell said:
The first step went flawlessly using TWRP. I'll flash the LP11 modem.bin tonight using Odin.
Thanks for this, Electron. I'm about to make another small donation to your beer (or whatever) fund!
Click to expand...
Click to collapse
I have never tried TWRP on this tab. What's the current version for our i815? Does it work well? I assume just like CWM it doesn't accept stock OTAs though, does it?
I still keep going back to stock recovery in order to accept OTAs (which never come for me haha and I end up updating manually!)
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

electron73 said:
I have never tried TWRP on this tab. What's the current version for our i815? Does it work well? I assume just like CWM it doesn't accept stock OTAs though, does it?
I still keep going back to stock recovery in order to accept OTAs (which never come for me haha and I end up updating manually!)
Click to expand...
Click to collapse
It was hard to flash (the apk method didn't work, I had to use Odin -- which really is no big deal, just scary for some). In any event, I'm running 2.3.10 available here: http://forum.xda-developers.com/showthread.php?t=1809295
I love TWRP... so much easier than fumbling with the volume and power buttons.
Never tested with OTA because I rely on you! :good:

I like TWRP but wish it could mount my encrypted /data partition like it could for my Nexus 7.

Stuck on 4G LTE Boot Screen
I'm going back from CM10 but after flashing ROM I'm now stuck on the Verizon 4G LTE screen. Not sure what you recommend?

mindstream98 said:
I'm going back from CM10 but after flashing ROM I'm now stuck on the Verizon 4G LTE screen. Not sure what you recommend?
Click to expand...
Click to collapse
Did you wipe data/cache? Coming from CM10 you definitely need to do a clean install. You can simply flash the "wipe" version of the LP10 rom first, then upgrade to the LP11
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

I'm buying you dinner tomorrow (well, I hope the donation I send you will ) ROM and modem installed without a single hitch. Only thing that caught me off guard again was the modified hosts file, bit I fixed that. Wife is happy! Thanks for your work on this.

[Q] Reliable method(s) of rooting.

I'm really having one hell of a time figuring out the most correct steps to rooting the verizon model. What I've always done upon attempting to root a new device is read all available information and decide from there. Between XDA, Reddit, Rootz and YouTube, I have no freaking idea which one is the most tried and true. My previous devices (Nexus 4 and Galaxy Nexus) were a walk in the park - even the droid X2 was a little easier to sift through and I faced less risk of very much destroying something. And after reading roughly 50 pages of threads here, I'm chalking most of this up to the device's immaturity. Regardless, there are people who have tried, succeeded and failed.
New folks need to hear what does and doesnt work in the most clear way possible and thats what I'm asking - what works, what doesnt work, what should I not even bother reading?

SlapMyMoto

nhizzat said:
SlapMyMoto
Click to expand...
Click to collapse
This.
Don't ask any questions, just follow the steps to the letter and you will be fine. I'm on a VZW model that I had to downgrade, and kept asking question after question.
You lose stock custom recovery forever, that's the risk on a non-dev-edition.

jl33 said:
I'm really having one hell of a time figuring out the most correct steps to rooting the verizon model. What I've always done upon attempting to root a new device is read all available information and decide from there. Between XDA, Reddit, Rootz and YouTube, I have no freaking idea which one is the most tried and true. My previous devices (Nexus 4 and Galaxy Nexus) were a walk in the park - even the droid X2 was a little easier to sift through and I faced less risk of very much destroying something. And after reading roughly 50 pages of threads here, I'm chalking most of this up to the device's immaturity. Regardless, there are people who have tried, succeeded and failed.
New folks need to hear what does and doesnt work in the most clear way possible and thats what I'm asking - what works, what doesnt work, what should I not even bother reading?
Click to expand...
Click to collapse
I am in the same boat after recently getting a Moto X and coming from a Galaxy Nexus that seemed to have more consensus, or least clearly indicated. It was a bit daunting to trying to start to learn the process again after over 2 years.
User dray has got you covered though regardless of what Moto X you are using and what version of Android you are on. Go here http://forum.xda-developers.com/showthread.php?t=2603358 and thank dray for his efforts.
I recently finished rooting my xt1060 starting at 4.2.2 and could show you what I did if you are in the same boat.

You can't compare a nexus to a device with a boot loader that can't be unlocked. A little research before purchasing would have shown you that its not as easy to root.
If you had a Moto x with an unlockable boot loader...then it would be just as easy as a nexus to root. Same steps in fact. So its not device immaturity ....its the fault of the particular one you bought.
Just saying.
Sent from my Moto X cellular telephone...

kj2112 said:
You can't compare a nexus to a device with a boot loader that can't be unlocked. A little research before purchasing would have shown you that its not as easy to root.
If you had a Moto x with an unlockable boot loader...then it would be just as easy as a nexus to root. Same steps in fact. So its not device immaturity ....its the fault of the particular one you bought.
Just saying.
Sent from my Moto X cellular telephone...
Click to expand...
Click to collapse
slapmymoto
Just saying.

syntrix said:
slapmymoto
Just saying.
Click to expand...
Click to collapse
That's nothing like the unlocked boot loader method...which is the same as the nexus method. And I can see how it intimidates new people.
So maybe quit quoting me with smart ass comments all over this forum and read the opening posts a bit more carefully.
He knows about slap ....its just a chore was his point...compared to flash recovery in fastboot...say yes to fix root.....reboot and done. Lol
Do us both a favor and put me on your ignore list....before this escalates.
Sent from my Moto X cellular telephone...

jl33 said:
I'm really having one hell of a time figuring out the most correct steps to rooting the verizon model. What I've always done upon attempting to root a new device is read all available information and decide from there. Between XDA, Reddit, Rootz and YouTube, I have no freaking idea which one is the most tried and true. My previous devices (Nexus 4 and Galaxy Nexus) were a walk in the park - even the droid X2 was a little easier to sift through and I faced less risk of very much destroying something. And after reading roughly 50 pages of threads here, I'm chalking most of this up to the device's immaturity. Regardless, there are people who have tried, succeeded and failed.
New folks need to hear what does and doesnt work in the most clear way possible and thats what I'm asking - what works, what doesnt work, what should I not even bother reading?
Click to expand...
Click to collapse
here is a complete guide that i made up hope it helps
http://forum.xda-developers.com/showthread.php?t=2603358

syntrix said:
This.
Don't ask any questions, just follow the steps to the letter and you will be fine. I'm on a VZW model that I had to downgrade, and kept asking question after question.
You lose stock custom recovery forever, that's the risk on a non-dev-edition.
Click to expand...
Click to collapse
Slap was one of the first methods I read about but I was then told that if I ignored the WP fix (like some of the guides leave out), Id have to go into recovery, and then reboot just to make changes to /system, which seems ridiculous. Correct me if I'm wrong.
dray_jr said:
here is a complete guide that i made up hope it helps
http://forum.xda-developers.com/showthread.php?t=2603358
Click to expand...
Click to collapse
I appreciate that thank you.

jl33 said:
Slap was one of the first methods I read about but I was then told that if I ignored the WP fix (like some of the guides leave out), Id have to go into recovery, and then reboot just to make changes to /system, which seems ridiculous. Correct me if I'm wrong.
I appreciate that thank you.
Click to expand...
Click to collapse
np at all let me know if you have any issues

I did it with twrp-2.6.3.1-ghost-4.4.img, i flash it in fastboot, enter the recovery, go to reboot/system, select root, reboot and you are rooted, its simple, its work for me in 4.2.2, 4.4 and 4.4.2
---------- Post added at 02:36 AM ---------- Previous post was at 02:34 AM ----------
if you can read spanish (or translate the page)
http://www.htcmania.com/showthread.php?p=12297991#post12297991
here's everything to change modem, recovery, root and even change the bootloader ulnock logo at the start

rivas1981 said:
I did it with twrp-2.6.3.1-ghost-4.4.img, i flash it in fastboot, enter the recovery, go to reboot/system, select root, reboot and you are rooted, its simple, its work for me in 4.2.2, 4.4 and 4.4.2
---------- Post added at 02:36 AM ---------- Previous post was at 02:34 AM ----------
if you can read spanish (or translate the page)
http://www.htcmania.com/showthread.php?p=12297991#post12297991
here's everything to change modem, recovery, root and even change the bootloader ulnock logo at the start
Click to expand...
Click to collapse
Unfortunately, that method is for unlocked bootloaders

Try it anyways you dont loose anything trying
Enviado desde mi XT1058 mediante Tapatalk

rivas1981 said:
Try it anyways you dont loose anything trying
Enviado desde mi XT1058 mediante Tapatalk
Click to expand...
Click to collapse
Guaranteed it won't work . Otherwise no one would ever unlock their boot loaders.
Sent from my Moto X cellular telephone...

syntrix said:
This.You lose stock custom recovery forever, that's the risk on a non-dev-edition.
Click to expand...
Click to collapse
Not forever. And what's a stock custom recovery? The only thing you lose "forever" is write protection if you use MotoPwnNoMo.
jl33 said:
Slap was one of the first methods I read about but I was then told that if I ignored the WP fix (like some of the guides leave out), Id have to go into recovery, and then reboot just to make changes to /system, which seems ridiculous. Correct me if I'm wrong.
Click to expand...
Click to collapse
I don't find it to be ridiculous at all. Rebooting into "recovery" adds maybe a minute to the whole process.

I'd like the same question as OP answered for the 1053 version. It really grinds my gears that there aren't separate forums for the different versions like they did with the variants of every other god damn phone (Galaxy Nexus as an example).
Sent from my XT1053 using XDA Premium 4 mobile app

elpeterson said:
I'd like the same question as OP answered for the 1053 version. It really grinds my gears that there aren't separate forums for the different versions like they did with the variants of every other god damn phone (Galaxy Nexus as an example).
Sent from my XT1053 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Why do they need separate forums? They all use the same root exploit with firmware specific to their model. There isn't enough development to justify separate forums.
Unlocking the bootloader is the same across the board as is rooting a locked bootloader. The only thing that differs in the entire process is the firmware.

nhizzat said:
Why do they need separate forums? They all use the same root exploit with firmware specific to their model. There isn't enough development to justify separate forums.
Unlocking the bootloader is the same across the board as is rooting a locked bootloader. The only thing that differs in the entire process is the firmware.
Click to expand...
Click to collapse
this phone is very simple let me break it down for you
locked bootloader
unlocked bootloader
lock need to use slapmymoto
unlocked and just install TWRP then install SUPERSU via custom recovery.
my guide tells you what phones can unlock there bootloader and what ones can't.

Sph-l720t update (there are dozens of us...dozens!)

While I realize it is relatively few to SPH-L720, I wanted to make a thread specific for the update ending with NAF for the triband variant,
the SPH-L720T.
While you may argue there is already a thread for the update, most of the userss are L720 not L720T, so the questions from L720T users keep getting drown out by others.
First order of business, though it has been asked but it has gotten no reply that I am aware of, has anyone gotten the OTA for the triband variant?
If so, can it be uploaded and distributed? It will be interesting to see if all the problems such as the sd card and rooting are the same.

I have the "T" model, and no OTA for me thus far.
I have rooted and installed some xPosed apps, but no custom recovery or rom. I'm hoping for 4.4.2 this week or so
Sent from my SPH-L720T using XDA Premium 4 mobile app

rocmat1 said:
While I realize it is relatively few to SPH-L720, I wanted to make a thread specific for the update ending with NAF for the triband variant,
the SPH-L720T.
While you may argue there is already a thread for the update, most of the userss are L720 not L720T, so the questions from L720T users keep getting drown out by others.
First order of business, though it has been asked but it has gotten no reply that I am aware of, has anyone gotten the OTA for the triband variant?
If so, can it be uploaded and distributed? It will be interesting to see if all the problems such as the sd card and rooting are the same.
Click to expand...
Click to collapse
I also have a 720T and haven't received notification of the update. I actually kind of regret my purchase of the 720T. I waited about a month to buy the 720T instead of the 720 because I figured I might as well "future proof" my purchase, but it seems most of the 720 mods and such don't work on the 720T. And with the S5 coming out, I think we'll be left in the dust. (I hope I'm wrong. My last phone was the original Evo and I loved how many different mods/roms/etc that had.)
---------- Post added at 08:16 AM ---------- Previous post was at 08:13 AM ----------
wlc108 said:
I also have a 720T and haven't received notification of the update. I actually kind of regret my purchase of the 720T. I waited about a month to buy the 720T instead of the 720 because I figured I might as well "future proof" my purchase, but it seems most of the 720 mods and such don't work on the 720T. And with the S5 coming out, I think we'll be left in the dust. (I hope I'm wrong. My last phone was the original Evo and I loved how many different mods/roms/etc that had.)
Click to expand...
Click to collapse
(I left off my last paragraph, oops) I'm sure we'll have the same issues with SD Cards since it's part of the new Android standard (or, newly enforced, at least) and root exploits would normally be fixed independent of the radios.

It's crazy that I haven't heard a single person on the 720T getting the update yet... has anyone done the google services framework clearing thing yet? I know it jacks stuff up but I'm thinking of trying it soon.

i tried it. no luck.

GOOD NEWS!
Following the advice hhere: http://www.androidcoliseum.com/2013/01/how-to-get-your-ota-update-faster.html
I got the update after the 5th try. If someone will help me to know where to find it on my phone I will upload it. It's 401.2 MB.
Yay! My phone is rooted ... and I have a custom recovery .... so the update may not work....but here's hoping!
Bleck my phone is at 18% so I have to charge it to be able to even try.

Found the file will be uploading soon

how did you get the settings menu pop up from the dial pad? notyhing happened for me'

lawmangrant said:
how did you get the settings menu pop up from the dial pad? notyhing happened for me'
Click to expand...
Click to collapse
Click menu / settings / apps
swipe over to the "All" category
scroll down for Google Services Framework and click it
click "clear cache" and "clear data"
hit home
go into your dialer
type in: *#*#2432546#*#*
wait for the notification "checkin succeeded"
Now go and try checking for your update.
Just go to the application manager, clear the data for the google services framework, go to dialer to type in *#*#2432546#*#*, check for update, repeat.... I've got the file about 50% uploaded

Got it to work, but the update errored out. I'm rooted with xPosed running. I guess I'm gonna try a restore tonight
Sent from my SPH-L720T using XDA Premium 4 mobile app

http://speedy.sh/w3mSm/0de568e284ba...86de.USER-L720T-SPT-MK5-to-NAF-Update-FWD.zip
Also if someone could upload the original build.prop I would appreciate it
Yeah Im in the same situation. Got back the stock recovery but errored out, I was rooted as well, just unrooted seeing if that will work. Unfourtantely didnt backup before I was rooted

Why not ask and/or look here?

leaderbuilder said:
Why not ask and/or look here?
Click to expand...
Click to collapse
Thanks but I'm good now. Hey if anyone has problems installing it that rooted it and used the xposed app, you have to flash the xposed disabler in the root directory with a custom recovery, that fixed it for me. Finally, got my kitkat!
Crap, stuck at Sprint Spark Screen... getting Set Perm: Some changes failed
So I dont think its compelting so I'm getting stuck at the sprint spark screen
Well Im just going to go ahead and do a total factory reset and flash all stock firmware...I mean it sucks, but I've only had my phone for two weeks so not a ton of data I'm going to lose...

I uninstalled the Xposed framework from within Xposed, and it seemed to work. I just can not get the OTA to re-download now.
---------- Post added at 09:37 PM ---------- Previous post was at 09:36 PM ----------
rocmat1 said:
Thanks but I'm good now. Hey if anyone has problems installing it that rooted it and used the xposed app, you have to flash the xposed disabler in the root directory with a custom recovery, that fixed it for me. Finally, got my kitkat!
Crap, stuck at Sprint Spark Screen... getting Set Perm: Some changes failed
So I dont think its compelting so I'm getting stuck at the sprint spark screen
Well Im just going to go ahead and do a total factory reset and flash all stock firmware...I mean it sucks, but I've only had my phone for two weeks so not a ton of data I'm going to lose...
Click to expand...
Click to collapse
How are you flashing stock firmware? ODIN? Factory reset through phone?

lawmangrant said:
I uninstalled the Xposed framework from within Xposed, and it seemed to work. I just can not get the OTA to re-download now.
---------- Post added at 09:37 PM ---------- Previous post was at 09:36 PM ----------
How are you flashing stock firmware? ODIN? Factory reset through phone?
Click to expand...
Click to collapse
Im about to do it through odin should be like a brand new phone at that point. I didn't have a ton of data, I backed it up, we'll see if it actually works though... lol all I want is to use tap and pay. Once I install it, Ill root it again and get where I can make a wifi hotspot for free and that's all I care about Just realized that download place sucks. Im uploading to dropbox right now
FINALLY! lol Got it working
I uploaded the update file, and it should be in your cache. Stock recovery can install from the sd card as well. So if you lost it for some reason I uploaded it a few posts above

rocmat1 said:
Im about to do it through odin should be like a brand new phone at that point. I didn't have a ton of data, I backed it up, we'll see if it actually works though... lol all I want is to use tap and pay. Once I install it, Ill root it again and get where I can make a wifi hotspot for free and that's all I care about Just realized that download place sucks. Im uploading to dropbox right now
FINALLY! lol Got it working
I uploaded the update file, and it should be in your cache. Stock recovery can install from the sd card as well. So if you lost it for some reason I uploaded it a few posts above
Click to expand...
Click to collapse
I'm happy to report that I can still read the external sd card

what tar did you odin with?

lawmangrant said:
what tar did you odin with?
Click to expand...
Click to collapse
4.3 STOCK ROM
http://www.androidfilehost.com/?fid=23329332407569938
SPH-L720T 4.4.2 OTA
https://www.dropbox.com/s/v1zh46uku...86de.USER_L720T_SPT_MK5_to_NAF_Update_FWD.zip

rocmat1 said:
4.3 STOCK ROM
http://www.androidfilehost.com/?fid=23329332407569938
SPH-L720T 4.4.2 OTA
https://www.dropbox.com/s/v1zh46uku...86de.USER_L720T_SPT_MK5_to_NAF_Update_FWD.zip
Click to expand...
Click to collapse
OK...I got the 4.4.2 file and working on the 4.3 stock.
For ODIN, do I just connect and select the PDA opton? That's what I am reading.

lawmangrant said:
OK...I got the 4.4.2 file and working on the 4.3 stock.
For ODIN, do I just connect and select the PDA opton? That's what I am reading.
Click to expand...
Click to collapse
yes. thats all you need to do, and then select your tar file

[Help] Soft-bricked or hard-bricked?

So my N6 (64GB) has now stopped working. It is stuck in a boot loop, constantly flashing the charging icon (battery w/ lightning bolt) when plugged in. When not plugged in, it is unresponsive. I can boot into fastboot, but attempting to select any of the options from there brings me back to the boot loop. I can't boot into recovery mode, and attempting to wipe from fastboot give me the 'bootloader is locked' error. Is there anything I can do, or is RMA the only option? I am on 6.0.1, but I was experiencing similar problems on 6.0 and 5.1.1.

Locked bootloader+stock recovery (No TWRP)= RMA.

mikeprius said:
Locked bootloader+stock recovery (No TWRP)= RMA.
Click to expand...
Click to collapse
That's a shame. I RMA'd it though, and have another on the way. Thanks anyway!

Nexus are never bricked
Sent from my Nexus 6 using Tapatalk

Have you tried unlocking the bootloader and then flashing the factory image from Google via fastboot?

bryantjopplin said:
Nexus are never bricked
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Really? Or was this for the ten first posts?
---------- Post added at 08:21 AM ---------- Previous post was at 08:18 AM ----------
YungCharlemagne said:
So my N6 (64GB) has now stopped working. It is stuck in a boot loop, constantly flashing the charging icon (battery w/ lightning bolt) when plugged in. When not plugged in, it is unresponsive. I can boot into fastboot, but attempting to select any of the options from there brings me back to the boot loop. I can't boot into recovery mode, and attempting to wipe from fastboot give me the 'bootloader is locked' error. Is there anything I can do, or is RMA the only option? I am on 6.0.1, but I was experiencing similar problems on 6.0 and 5.1.1.
Click to expand...
Click to collapse
What similar problems were with 6.0 or 5.1? How stock are you? Was Enable OEM Unlocking ticked or not? Did you try fastboot oem unlock? Did you try turning it off and on again?

istperson said:
Really? Or was this for the ten first posts?
---------- Post added at 08:21 AM ---------- Previous post was at 08:18 AM ----------
What similar problems were with 6.0 or 5.1? How stock are you? Was Enable OEM Unlocking ticked or not? Did you try fastboot oem unlock? Did you try turning it off and on again?
Click to expand...
Click to collapse
Well not really but what most people do to it won't brick it. Unless he is changing stuff that most of don't even know how to. What he is describing sounds very fixable
Sent from my Nexus 6 using Tapatalk

bryantjopplin said:
Well not really but what most people do to it won't brick it. Unless he is changing stuff that most of don't even know how to. What he is describing sounds very fixable
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Then you must be new to the Nexus 6. Which is alright, but then please don't promise what you can't keep.
So, the Nexus 6 was the first Nexus that had an 'Enable OEM Unlocking' switch in the settings. And if it's unticked, and your bootloader is locked, and you can't boot your system, and you have stock recovery, then you're boned. And this is a fact.
People started bricking their Nexuses just following the instructions on Google's development site, because Google put there that the last step when going stock is locking the bootloader. Now flashing everything reverts the 'Enable OEM Unlocking' switch, but flashing everything does not guarantee that it will actually boot up. And if you lock the bootloader before checking if it boots, you've got a brick only by following Google's own basic instructions.
And no secret stuff was changed at all.

istperson said:
Then you must be new to the Nexus 6. Which is alright, but then please don't promise what you can't keep.
So, the Nexus 6 was the first Nexus that had an 'Enable OEM Unlocking' switch in the settings. And if it's unticked, and your bootloader is locked, and you can't boot your system, and you have stock recovery, then you're boned. And this is a fact.
People started bricking their Nexuses just following the instructions on Google's development site, because Google put there that the last step when going stock is locking the bootloader. Now flashing everything reverts the 'Enable OEM Unlocking' switch, but flashing everything does not guarantee that it will actually boot up. And if you lock the bootloader before checking if it boots, you've got a brick only by following Google's own basic instructions.
And no secret stuff was changed at all.
Click to expand...
Click to collapse
Does the qhsub_bulk fix not work for this? And I'm sure an sbf doesn't work either. And no I've had the n6 since last December.
Sent from my Nexus 6 using Tapatalk
---------- Post added at 08:48 AM ---------- Previous post was at 08:47 AM ----------
bryantjopplin said:
Does the qhsub_bulk fix not work for this? And I'm sure an sbf doesn't work either. And no I've had the n6 since last December.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Also he didn't say he tried flashing stock images
Sent from my Nexus 6 using Tapatalk

bryantjopplin said:
Does the qhsub_bulk fix not work for this? And I'm sure an sbf doesn't work either. And no I've had the n6 since last December.
Sent from my Nexus 6 using Tapatalk
---------- Post added at 08:48 AM ---------- Previous post was at 08:47 AM ----------
Also he didn't say he tried flashing stock images
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=59561963&postcount=2
ccfries said:
First, fastboot flash partition gpt.bin
Then, fastboot reboot-bootloader
Then flash the other images.
If you just bricked by downgrading bootloader, the persist and modem calibration should still be happily where it was when you started.
This won't help you if you're stuck with Allow OEM Unlock. Be careful locking on 5.1. There's accurate information elsewhere in the forum on that.
-Chris
Click to expand...
Click to collapse

Stock rom without root or unlock only can enter bootloader

My nexus 6 using stock rom and update to the latest version thru OTA, without root or unlock bootloader. Yesterday it suddenly reboot and only allow to boot into bootloader. Cannot select recovery or factory mode, check the bootloader log show failed to validate the boot image or recovery image.
I've read many threads and try many methods to unloock the bootloader and flash the factory image but failed.
Anyone can help to get the nexus 6 back, thanks so much.

Probably going to have to do an RMA, you can't use any of the recovery options (fastboot, custom recoveries) with a locked bootloader, that is the whole point of it being locked.

Since we're now suggesting RMA, I have to ask...
Have you tried in the bootloader screen "fastboot oem unlock"?
Maybe you have, but your problem description is really pretty vague.
scryan, not trying to tread on your toes, and I may be completely wrong (about to fall asleep) but isn't the whole point of "fastboot oem unlock" that it runs in bootloader specifically to unlock it?

dahawthorne said:
Since we're now suggesting RMA, I have to ask...
Have you tried in the bootloader screen "fastboot oem unlock"?
justMaybe you have, but your problem description is really pretty vague.
scryan, not trying to tread on your toes, and I may be completely wrong (about to fall asleep) but isn't the whole point of "fastboot oem unlock" that it runs in bootloader specifically to unlock it?
Click to expand...
Click to collapse
I am sorry as this is my 1st post here. My Nexus 6 was not rooted and even not enable "usb debug" or "oem unlock" setting.
I've already tried "fastboot oem unlock" and failed. I've also tried "fastboot flashing unloock", it said ok but restart the bootloader and it still show locked.
I've also tried the Nexus Root Tools too to unlock or flash the factory image, recovery image or boot to twrp but all failed too.

Then you have no choice but to request a RMA. To be able to unlock the bootloader so you can then flash a stock ROM, you have to enable Developer Options, then in Developer Options enable both USB Debugging and OEM Unlock.

Have you tried the hardbrick tread? Not sure if this will work with locked bootloaders. http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
Sent from my Nexus 6 using Tapatalk
---------- Post added at 09:06 PM ---------- Previous post was at 08:50 PM ----------
Have you tried fastboot reboot-recovery to enter recovery? With or without the "-", I forget the proper form. With locked bootloaders I don't think u can flash anything from recovery. Plus it may be a hardware issue not necessarily software related.
Sent from my Nexus 6 using Tapatalk
---------- Post added at 09:07 PM ---------- Previous post was at 09:06 PM ----------
But if you can enter recovery maybe you can factory reset and at least get it to boot!
Sent from my Nexus 6 using Tapatalk
---------- Post added at 10:03 PM ---------- Previous post was at 09:07 PM ----------
What version of fastboot are you using, old fastboot may not work properly.
Sent from my Nexus 6 using Tapatalk

Jnewell05 said:
Have you tried the hardbrick tread? Not sure if this will work with locked bootloaders. http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
Sent from my Nexus 6 using Tapatalk
---------- Post added at 09:06 PM ---------- Previous post was at 08:50 PM ----------
Have you tried fastboot reboot-recovery to enter recovery? With or without the "-", I forget the proper form. With locked bootloaders I don't think u can flash anything from recovery. Plus it may be a hardware issue not necessarily software related.
Sent from my Nexus 6 using Tapatalk
---------- Post added at 09:07 PM ---------- Previous post was at 09:06 PM ----------
But if you can enter recovery maybe you can factory reset and at least get it to boot!
Sent from my Nexus 6 using Tapatalk
---------- Post added at 10:03 PM ---------- Previous post was at 09:07 PM ----------
What version of fastboot are you using, old fastboot may not work properly.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Thx so much for your reply, I've tried the hard-brick thread but can't install the qualcomm driver.
I plan to contact the Google see whether it can help me since I am in HK and my Nexus 6 is not directly bought from HK Google.
It really quite depress me since I do nothing with the phone, I do not flash any custom rom, do not root or unlock bootloader, just normal use it then suddenly crashed .... >_<

this exact same thing happened to my wife's phone just a month ago... and the sad thing is the phone was just bought new for only 2 months or so. never installed any custom roms, never rooted, etc. and now i wish that i did so that i could have at least turned ON that option in Developers Option to "allow OEM Unlock" and if i did, it should've been an easy fix.
i never had this kind of issue before thats why i thought there is nothing important to turn on in the Developers Option. they should've made that information more available and even point it out on the Update but they didn't which sucks.
i also tried to contact Motorola US but since im not in the US, even though the phone is bought in the US via Ebay, they weren't able to help and sent me to another Motorola site for my region. i'm trying it now and i still cant go through the site...
it's really depressing when this kind of things happen... i hope in the future there would be some kind of fix for this. i heard if we can get a signed System that we could flash into the phone then there's a chance it could work but as of now, i keep checking for information about this and hoping someone came up with something...
hope this thing won't happen to anyone else and if you got a Nexus 6, make sure to turn On "Allow OEM Unlock" on your phone.

quinceyr said:
this exact same thing happened to my wife's phone just a month ago... and the sad thing is the phone was just bought new for only 2 months or so. never installed any custom roms, never rooted, etc. and now i wish that i did so that i could have at least turned ON that option in Developers Option to "allow OEM Unlock" and if i did, it should've been an easy fix.
i never had this kind of issue before thats why i thought there is nothing important to turn on in the Developers Option. they should've made that information more available and even point it out on the Update but they didn't which sucks.
i also tried to contact Motorola US but since im not in the US, even though the phone is bought in the US via Ebay, they weren't able to help and sent me to another Motorola site for my region. i'm trying it now and i still cant go through the site...
it's really depressing when this kind of things happen... i hope in the future there would be some kind of fix for this. i heard if we can get a signed System that we could flash into the phone then there's a chance it could work but as of now, i keep checking for information about this and hoping someone came up with something...
hope this thing won't happen to anyone else and if you got a Nexus 6, make sure to turn On "Allow OEM Unlock" on your phone.
Click to expand...
Click to collapse
Hi, quinceyr, I've just tried the below thread and restore my Nexus 6 back and only draw back is updated to Android N preview version. I've tested for a while seems work fine and will keep monitor for a period.
http://forum.xda-developers.com/nexus-6/help/command-device-corrupt-update-t3362317/page2
Hope your Nexus 6 will recover back.