Database Develop

[Odin] Official Stock Firmware

Here is a direct Download to the Official Stock Firmware . Directly and thanks to Samsung-Updates, but I just uploaded to my server so that you dont have to deal with Slow Hotfile​
Software Version L720VPUAMDC Build Date:4-10-13
Download Link
Download Link Updated

Next time, don't make a place holder.. Your link just got updated a minute ago..

Do you know the difference between the XAS, and SPR versions of the firmwares? And how to identify which to use? Thanks

Gam3r 4 Life said:
Do you know the difference between the XAS, and SPR versions of the firmwares? And how to identify which to use? Thanks
Click to expand...
Click to collapse
use teh spr one, xas is similar to an engineering builds

everytime i use odin it says fail and now will not comeout of download mode

Here's another mirror for stock official:
http://stockroms.net/file/GalaxyS4/SPH-L720/L720VPUAMDC_L720SPTAMDC_SPR.zip
And how to install it for noobs:

zedomax said:
Here's another mirror for stock official:
http://stockroms.net/file/GalaxyS4/SPH-L720/L720VPUAMDC_L720SPTAMDC_SPR.zip
And how to install it for noobs:
Click to expand...
Click to collapse
Zedomax to the rescue! lol

zedomax said:
Here's another mirror for stock official:
http://stockroms.net/file/GalaxyS4/SPH-L720/L720VPUAMDC_L720SPTAMDC_SPR.zip
And how to install it for noobs:
Click to expand...
Click to collapse
can you tell me what case that is? it seems real nice
thanks

itster2 said:
can you tell me what case that is? it seems real nice
thanks
Click to expand...
Click to collapse
Cruzerlite S4 circuit case
http://www.amazon.com/Cruzerlite-Bugdroid-Circuit-Samsung-Galaxy/dp/B00BLVUPGQ

Hot damn, you got a pretty fast server! You're awesome hyelton!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

How can I flash this with Heimdall?

Just to let you know.......downloaded twice from this server on my lappy and both files came up corrupted. Can't even open with 7-Zip.
Also, I keep getting a pop-up saying that the download has been interrupted.
---------- Post added at 11:25 AM ---------- Previous post was at 11:04 AM ----------
Tried a third time and got the same "download has been interrupted" pop-up. After resuming and finishing the download, I looked at the file size and it was 246mb.

12MaNy said:
Just to let you know.......downloaded twice from this server on my lappy and both files came up corrupted. Can't even open with 7-Zip.
Also, I keep getting a pop-up saying that the download has been interrupted.
---------- Post added at 11:25 AM ---------- Previous post was at 11:04 AM ----------
Tried a third time and got the same "download has been interrupted" pop-up. After resuming and finishing the download, I looked at the file size and it was 246mb.
Click to expand...
Click to collapse
What U Uesin To Download It? Wifi 4G. 3 G?.. sometimes when your Internet is laggy. It Aiffects the download. Happened to me a few times. U need a stable Internet with a good speed
Sent from my SPH-L720 using xda premium

Son Rise said:
What U Uesin To Download It? Wifi 4G. 3 G?.. sometimes when your Internet is laggy. It Aiffects the download. Happened to me a few times. U need a stable Internet with a good speed
Sent from my SPH-L720 using xda premium
Click to expand...
Click to collapse
Downloaded on on my laptop.......and I have FiOS.

Does this work with the MDL baseband as well? I'm seeing MDC in the filename so I want to make sure

Caffeinatrix said:
Does this work with the MDL baseband as well? I'm seeing MDC in the filename so I want to make sure
Click to expand...
Click to collapse
No.
But this will!
L720VPUAMDL_L720SPTAMDL_SPR.zip
(Courtesy of sammobile and reuploaded by me)

So if you're already on MDL modem, have stock rooted ROM, stock kernel, triangle away back to zero and official, using Mobile Odin with this "should" put everything back to factory including putting stock recovery back on? I haven't had the need or time to pull the trigger to test it yet. I'm glad there's finally a stock tar of this. I guess it's just a matter of time before one clicks are made with this and rooted tars. I know this phone is slightly different with flashing than the e4gt. My mind is still stuck on the way things were done with that phone.

oscarthegrouch said:
So if you're already on MDL modem, have stock rooted ROM, stock kernel, triangle away back to zero and official, using Mobile Odin with this "should" put everything back to factory including putting stock recovery back on? I haven't had the need or time to pull the trigger to test it yet. I'm glad there's finally a stock tar of this. I guess it's just a matter of time before one clicks are made with this and rooted tars. I know this phone is slightly different with flashing than the e4gt. My mind is still stuck on the way things were done with that phone.
Click to expand...
Click to collapse
I would say that it will. I think even if you have the MDC modem it should upgrade to the MDL version. I'm going to try in a few minutes...almost downloaded. I am wondering if triangle away is even necessary. I'm showing "custom" on my phone so we'll see what happens.
I've already posted on sxtp about getting a one-click. They make things so easy. But at least with this file I can skip the (1) one-click MDC..... (2) wait for OTA upgrade to MDL.
This definitely is different from my E4GT.
BTW , what is that SS_DL.dll file in the zip?
Sent from my SPH-L720 using Tapatalk 2
---------------------------------------
Edit: OK, I just ODIN'd the file. Custom binary now shows Samsung Official and system status is Official. I forgot to check the kernel, but I'm pretty sure it's stock. Also it did flash modem.bin. ODINing this file left all my apps intact. I was expecting it to wipe my internalSD, but apparently it didn't.
Since I wanted to start from a clean slate, I'm now flashing the one-click MDC stock restore and I'll take the OTA and go from there. I'll just have to wait for a one-click rooted restore.

I wonder if the root option in mobile Odin works with stock MDL.

Help me correct this --
Foulwx said:
I would say that it will. I think even if you have the MDC modem it should upgrade to the MDL version. I'm going to try in a few minutes...almost downloaded. I am wondering if triangle away is even necessary. I'm showing "custom" on my phone so we'll see what happens.
I've already posted on sxtp about getting a one-click. They make things so easy. But at least with this file I can skip the (1) one-click MDC..... (2) wait for OTA upgrade to MDL.
This definitely is different from my E4GT.
BTW , what is that SS_DL.dll file in the zip?
Sent from my SPH-L720 using Tapatalk 2
---------------------------------------
Edit: OK, I just ODIN'd the file. Custom binary now shows Samsung Official and system status is Official. I forgot to check the kernel, but I'm pretty sure it's stock. Also it did flash modem.bin. ODINing this file left all my apps intact. I was expecting it to wipe my internalSD, but apparently it didn't.
Since I wanted to start from a clean slate, I'm now flashing the one-click MDC stock restore and I'll take the OTA and go from there. I'll just have to wait for a one-click rooted restore.
Click to expand...
Click to collapse
I attempted to root my s4 via motochopper (before finding out that this method does not work) - then I Odin'd the CF-Auto-Root-jfltespr-jfltespr-sphl720.zip and rebooted. (per qbking77 instructions which were ALSO out of date) It installed the SU apk (red pirate android) and once rebooted, SU did not work and root checker told me I was not rooted. At this point I am wanting to remove SU (since it's not working, binaries will not update) and return to "normal". I should Odin the file in this thread for the VPUAMDL, correct?
I follow instructions well, have read a thousand threads about this today (before diving in) and have rooted a dozen phones before this (never an s4) - I have never had a problem, until this happened today. I'm a little irritated because I was relying on the information as CURRENT (because info on rooting and installing custom recovery for the s4 seems to be SPARSE) -
Any help is appreciated,
Thx, Chictek

[SCRIPT] DROID RAZR HD 926 (only) Utility 1.4 KK - Windows [Updated 06/16/2014]

*********PSA**********
a new update is rolling out NOW
use version 1.41 and the UNLOCK GUIDE now!!!, before you take the update!!!.
once updated by the 9/9/14 ota, you are screwed permanently from unlocking and rooting.
WARNING
unlocked users on the oficial KK need to use rsd to flash back to JB before you can use the JB version of this utility again.
locked users on KK can not flash back to JB by any means, including this script.
check out my guide for flashing to KK, unlocking the bootloader, and flashing back to JB if you wish here.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is ONLY for the DROID RAZR XT926 and DROID RAZR HD MAXX XT926. Do NOT use this on an XT925!
DROID RAZR HD Utility by MattLGroff, Updated [1.3+] to include the latest OTA, Recoveries, and Root by Me.
Thanks and Credit goes to Matt and the dev's who's tools are in this script.
- Mac & Linux Instructions See This Thread
( no longer supported in newer versions, sorry)
Extract .zip to its own folder on the Desktop.
Install the required drivers. The folder with the drivers is called "Drivers [WINDOWS ONLY]" and is included in the Utility folder.
Double click the ".bat" file. This will be called "WindowsUtility.bat" the image is just for reference.
SOME OPTIONS ARE NOT AVAILABLE IN EVERY VERSION, no point including things that dont work on the version being flashed.
Possible options, depending on version:
1 Flash 4.1.2 Stock System, Kernel, and Radio (Data Wipe) [from AP Fastboot]
2 Flash 4.1.2 Stock Recovery [from AP Fastboot]
3 Motochopper Root Exploit by djrbliss [from Normal Boot] old method, older builds, 9.16 and before
4 Same as #3 UPDATED for the latest ota by SamuriHL, merged into this script by Me New method, locked or unlocked bootloader 9.18.79 to 9.20.1
5 Unlock Bootloader (Install Motopocalypse App) [from Normal Boot] this will NOT unlock your bootloader if you are already on 9.18.79, 9.20.1, or newer JB, but will on rooted KK
6 Flash TWRP 2.6.3.0 Recovery -[Updated by Djuniah] UNLOCKED BL REQUIRED [from Normal Boot]
7 Flash OUDHS 1.0.3.4 Recovery - UNLOCKED BL REQUIRED [from Normal Boot]
8 Flash CWM 6.0.3.5 Recovery - UNLOCKED BL REQUIRED [from Normal Boot]
Number 1 Explained -- This option requires your phone be in AP Fastboot mode. It will flash the official 4.1.2 System, Kernel, and Radio as well we wipe your data.
Number 2 Explained -- This option requires your phone be in AP Fastboot mode. It will flash the official 4.1.2 Stock Recovery.
Number 3 Explained -- This is Dan Rosenberg's root exploit called 'Motochopper'. This option requires your phone to be booted normally, with USB Debugging enabled. old builds
Number 4 Explained-- Same as #3 UPDATED by SamuriHL for 9.18.79 and 9.20.1 (locked or unlocked bootloader)
Number 5 Explained -- Again, this will NOT unlock your bootloader if you are already on this update
This option requires your phone to be booted normally, with USB Debugging enabled. It will install an App version of Dan Rosenberg's Motopocalypse exploit for unlocking the bootloader.
Number 6 Explained -- This option requires your phone to be booted normally with USB Debugging enabled, and be already Rooted. This will flash TWRP 2.6.3.0 Recovery.
Number 7 Explained -- This option requires your phone to be booted normally with USB Debugging enabled, and be already Rooted. This will flash OUDHS 1.0.3.4 Recovery.
Number 8 Explained -- This option requires your phone to be booted normally with USB Debugging enabled, and be already Rooted. This will flash CWM 6.0.3.5 Recovery.
Remember, do not run this utility unless your phone is at 100% battery OR you have bought yourself one of Team Black Hat's Factory-Style Programming Adapters.
Thanks to Shabbypenguin and OUDHS for making the original OUDHS which Matt ported over. Thanks to Hashcode and dhacker29 for making the STS-Dev Team repo. Thanks to Djrbliss for Motochopper and Motopocalypse! Thanks to TomSgt for making the video (coming soon to be added to the OP).
Video:
http://youtu.be/ej7HBxvNPv0
Download version 1.33 (10/25/2013) (added root for the ota in this build, 9.18.79-9.20.1)
File size: 582 MB
MD5: 7DE0DCEC718445B76B34B1FE70EB1ED0
Download version 1.34 (11/09/2013) (updated to the latest ota 9.30.1/9.18.94, slimmed down version, new ota and current recoveries only)
(there was no working root method for this ota at the time of this build, so its not included)
File size: 569 MB
MD5: 374A052E99894676ACC7B959DA097AE6
GPT error fix -- Mirror 926 GPT error fix script this is for JB only, do not use this if you were on the official KK at any time, it will not work as the partition table can never be downdraded.
File size: 540MB
MD5: D60EBC01E1CC803E18A2C7B22D31ACA6
Download version 1.4 KitKat (05/22/2014) (this is a FULL version and can be used to flash from any version to KitKat. Data Wipe or NO Data Wipe files are included also.) (root can be achieved with this app)
File size: 703MB
MD5: E4BB44ECFC8CB70002BA17B0D8611448
Download version 1.41 KitKat (06/16/2014) THIS IS THE SAME VERSION AS 1.4 i merely added in sub folders, new root app, old bootloader app (yes this works again on KK), new cwm for KK, and new twrp for KK, for convenience.
File size: 710MB
MD5: 3586516747FD4B2F9EF78A34558A3364

i am temporarily removing the download because although this works, there appears to be a mix up with the files that i overlooked.
i will get it fixed and re-up the file shortly.
sorry for the inconvenience!

ok its fixed and the file will be updated in 30 minutes.
sorry again for the confusion.
when i get time i will try to mesh the new root method into the script, until then use the utility here.
update: upload failed to match md5, ill have to try again tomorrow, sorry

ok it fixed, tested and uploaded.
sorry for the delay

bweN diorD said:
ok it fixed, tested and uploaded.
sorry for the delay
Click to expand...
Click to collapse
Nice thx for the update

op updated to 1.33
merged root for 9.18.79 and 9.20.1 into the script.
credit to SamuriHL for updating the root script for us, to the new builds.

Has anyone tried the Telesa version to unlock the boatloader.
Sent from my SGH-T889 using Tapatalk

TheGman125 said:
Has anyone tried the Telesa version to unlock the boatloader.
Sent from my SGH-T889 using Tapatalk
Click to expand...
Click to collapse
never heard of it, got a link plz.
never mind, i see it

as it said if you are on 9.18.79 it won't unlock your bootloder then how would I unlock it?
i was on this http://forum.xda-developers.com/showthread.php?t=2307439
and they told me to check out this

albatnawy91 said:
as it said if you are on 9.18.79 it won't unlock your bootloder then how would I unlock it?
i was on this http://forum.xda-developers.com/showthread.php?t=2307439
and they told me to check out this
Click to expand...
Click to collapse
If you're on the update, you can't unlock the bootloader with any utility.

I rooted and unlocked the bootloader and have never gone back to stock since. Would it be beneficial for me to install the 4.1.2 firmware just for the radios and then return back to CM or does it even matter?

stefilini said:
I rooted and unlocked the bootloader and have never gone back to stock since. Would it be beneficial for me to install the 4.1.2 firmware just for the radios and then return back to CM or does it even matter?
Click to expand...
Click to collapse
4.3 is known to have some issues with stock radios from what i have read.
if your not having any radio issues, i wouldnt mess with it personally.

How would you flash the 4.1 radio onto 4.3 CM?
Sent from my XT926 using XDA Premium HD app

sgtslaughter64 said:
How would you flash the 4.1 radio onto 4.3 CM?
Sent from my XT926 using XDA Premium HD app
Click to expand...
Click to collapse
Find a flashable baseband .zip and flash it in recovery.

RikRong said:
Find a flashable baseband .zip and flash it in recovery.
Click to expand...
Click to collapse
sgtslaughter64 said:
How would you flash the 4.1 radio onto 4.3 CM?
Sent from my XT926 using XDA Premium HD app
Click to expand...
Click to collapse
i didnt make this, nor can confirm it works, it was posted by someone right after the update on another forum. http://www.mediafire.com/download/g5jyi3m45skpo3g/RAZR_HD-radio_updater.zip

Tried flashing, but no joy. Couldn't get the zip to install. Thanks for the help though.
Sent from my XT926 using XDA Premium HD app

sgtslaughter64 said:
Tried flashing, but no joy. Couldn't get the zip to install. Thanks for the help though.
Sent from my XT926 using XDA Premium HD app
Click to expand...
Click to collapse
theoretically speaking, if you took this utility and deleted all the img files except the modems and removed the data wipe command, it should fail everything because of the missing files and just flash the modems.

Please Advice!
Hello Guys
I have Australian Telstra Razr HD XT925 and i rooted it using Motochoper and started playing with it till i bricked it after trying to change system font using font installer, i was lost guys ! but after long reading i came up with custom ROMs
Now i have Beanstalk ROM android 4.3.1 but i have radio issues sometimes data loss for a min. and come back and sometimes complete drop and i have to reboot device! its annoying ....
Please advice me can i use this utility on my Telstra XT925 with my custom ROM android 4.3.1 and my custom recovery OUDHS
Note : I have no backup from my stock ROM
Device : XT925
ROM : Beanstalk
Android : 4.3.1
Recovery : OUDHS
Bootloader : Unlocked
Previous ROMs : Xenon HD, Liquid Smooth, Slimbean, Carbon, Paranoid Android, CM10.2, AOKP

the very first line of my OP post reads as follows:
This is ONLY for the DROID RAZR XT926 and DROID RAZR HD MAXX XT926. Do NOT use this on an XT925!

bweN diorD said:
the very first line of my OP post reads as follows:
This is ONLY for the DROID RAZR XT926 and DROID RAZR HD MAXX XT926. Do NOT use this on an XT925!
Click to expand...
Click to collapse
Yes You Are Right ... Sorry for annoying you i went through without reading this line, my fault
Now do you recommend any utility such as this utility that we can use with XT925 and particularly can be used with custom ROMs and android 4.3.1 ? sorry for disturbing u brother

[Q] How can I update to Lollipop 5.1 if my device is already rooted?

Hello
Excuse me but I'm a newbie to all of this. I have found tons of posts here to help me with whatever I need but now I can't seem to find a way to update to 5.1
I tried the OTA but it didn't work since my device is already rooted although I am still running 5.0.1.
I tried sideloading it but it didn't work and I read a few posts that it won't work anymore since I rooted already.
So what's left to do? Flash image? If so, can someone point me in the right direction? Didn't any new posts regarding 5.1 image flashing and I really don't wanna risk doing anything stupid. Also, I read that there's a way through which I can bypass losing all my data?
Thanks in advance!

mounirkh said:
Hello
Excuse me but I'm a newbie to all of this. I have found tons of posts here to help me with whatever I need but now I can't seem to find a way to update to 5.1
I tried the OTA but it didn't work since my device is already rooted although I am still running 5.0.1.
I tried sideloading it but it didn't work and I read a few posts that it won't work anymore since I rooted already.
So what's left to do? Flash image? If so, can someone point me in the right direction? Didn't any new posts regarding 5.1 image flashing and I really don't wanna risk doing anything stupid. Also, I read that there's a way through which I can bypass losing all my data?
Thanks in advance!
Click to expand...
Click to collapse
you can just flash a 5.1 rooted rom, just like before 5.1. thats the easiest way around. you can flash the factory img as well, then reroot.

Download the Google factory image here: https://developers.google.com/android/nexus/images
Extract the system.img and boot.img then fastboot flash them. Read general > all in one guide > question 28 for fastboot.
Once flashed, boot straight into twrp recovery and flash SuperSU. Zip to root.
Edit.. Or if you want, you can download a pre-rooted ROM.zip and just flash that from twrp recovery

rootSU said:
Download the Google factory image here: https://developers.google.com/android/nexus/images
Extract the system.img and boot.img then fastboot flash them. Read general > all in one guide > question 28 for fastboot.
Once flashed, boot straight into twrp recovery and flash SuperSU. Zip to root.
Edit.. Or if you want, you can download a pre-rooted ROM.zip and just flash that from twrp recovery
Click to expand...
Click to collapse
simms22 said:
you can just flash a 5.1 rooted rom, just like before 5.1. thats the easiest way around. you can flash the factory img as well, then reroot.
Click to expand...
Click to collapse
Do you guys advise me to do this? http://forum.xda-developers.com/nexus-6/development/rom-3-13-stock-rooted-5-1-lmy47d-root-t3054253
Also all I need is to flash this ROM? Nothing else? If so, I intend to do it using ROM Manager.

mounirkh said:
Do you guys advise me to do this? http://forum.xda-developers.com/nexus-6/development/rom-3-13-stock-rooted-5-1-lmy47d-root-t3054253
Also all I need is to flash this ROM? Nothing else? If so, I intend to do it using ROM Manager.
Click to expand...
Click to collapse
no advice, flash whatever you like. but ill warn you ROM Manager is an ancient app that WILL cause you issues. what you should do iz boot into twrp recovery, flash whatever, then reboot. thats how you flash. remember my words, rom manager WILL cause you iasues.

Just flashing a rooted rom will not install the newest bootloader and modem/radio. So I wouldn't recommend that....
But either way works if all you want to do is get on 5.1 without updating the bootloader and modem/radio

idtheftvictim said:
Just flashing a rooted rom will not install the newest bootloader and modem/radio. So I wouldn't recommend that....
But either way works if all you want to do is get on 5.1 without updating the bootloader and modem/radio
Click to expand...
Click to collapse
I'm never updating my bootloader. At least not until I have to. The 5.1 bootloader is not a friend of anyone racking up their frequent flasher miles.

rootSU said:
I'm never updating my bootloader. At least not until I have to. The 5.1 bootloader is not a friend of anyone racking up their frequent flasher miles.
Click to expand...
Click to collapse
the last time i flashed a bootloader was on the nexus 7, and that was in 2012. i dont flash bootloaders ever, but that n7 original bootloader was broken. im not planning on flashing the n6 bootloader either.

simms22 said:
the last time i flashed a bootloader was on the nexus 7, and that was in 2012. i dont flash bootloaders ever, but that n7 original bootloader was broken. im not planning on flashing the n6 bootloader either.
Click to expand...
Click to collapse
I flashed one if the modified loaders on the n5. Just aesthetics really.

This ROM manager? Ah... Memories
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Google N6 on VZ

DebianDog said:
This ROM manager? Ah... Memories
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
Always hated that app tbh Caused problems instead of offering solutions. Just my opinion though..

gee2012 said:
Always hated that app tbh Caused problems instead of offering solutions. Just my opinion though..
Click to expand...
Click to collapse
Yep. I saw a lot of HTC desire users get into trouble with it.

rootSU said:
Yep. I saw a lot of HTC desire users get into trouble with it.
Click to expand...
Click to collapse
Helium is seemingly going the same way lately, fc`s while backing up apps and loaded cloud backups not restoring

gee2012 said:
Always hated that app tbh Caused problems instead of offering solutions. Just my opinion though..
Click to expand...
Click to collapse
No it was one of those things I bought to support the developer but I never used it. Because like you said[emoji6]
Sent from my Google N6 on VZ

DebianDog said:
No it was one of those things I bought to support the developer but I never used it. Because like you said[emoji6]
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
Bought the app too, in that time we needed it as CM could only be downloaded through Rom Manager. Flashed it with CWM afterwards because RM didn`t work and messed up CWM recovery so i had to reflash it ugh.....

gee2012 said:
Bought the app too, in that time we needed it as CM could only be downloaded through Rom Manager. Flashed it with CWM afterwards because RM didn`t work and messed up CWM recovery so i had to reflash it ugh.....
Click to expand...
Click to collapse
Yes and the good news is those guys are sitting on like 500 million dollars right now so mission accomplished[emoji23]
Sent from my Google N6 on VZ

rootSU said:
I'm never updating my bootloader. At least not until I have to. The 5.1 bootloader is not a friend of anyone racking up their frequent flasher miles.
Click to expand...
Click to collapse
I could have used you guys over in the Wugfresh thread this evening...just endless crazy...
---------- Post added at 09:40 PM ---------- Previous post was at 09:39 PM ----------
simms22 said:
the last time i flashed a bootloader was on the nexus 7, and that was in 2012. i dont flash bootloaders ever, but that n7 original bootloader was broken. im not planning on flashing the n6 bootloader either.
Click to expand...
Click to collapse
Such sage advice...again, the Wugfresh thread needs you...

Getting back stock recovery

Hi, I hope I post this in the right place. Anyway, as the title suggests, I want to get back stock recovery on my Nexus 6 without getting back the entire system image. I currently have TWRP as a recovery and I want to be able to receive OTA updates but I would need to uninstall BusyBox, which TWRP uses. The only thing that is 'custom' right now is the recovery and that's all I want to replace because I've heard that if I flash the entire system image, I lose data. I haven't been successful in finding the exact guide or support I need so I am posting my own thread. Sorry if it's in the wrong place.

You would download the stock image, extract recovery.img from that, boot phone into the bootloader and using a computer with the Android SDK installed, use the command fastboot to flash the recovery, so: fastboot flash recovery recovery.img
There's guides here on how to do this.

RMarkwald said:
You would download the stock image, extract recovery.img from that, boot phone into the bootloader and using a computer with the Android SDK installed, use the command fastboot to flash the recovery, so: fastboot flash recovery recovery.img
There's guides here on how to do this.
Click to expand...
Click to collapse
I have Android SDK but I have no idea how to do it. I don't suppose you have a link? If not, it's alright. Thank you for the quick response.
I have found guides on how to do it, but I can't get them to work. Haven't seen one using Android SDK.

Are you rooted?
Sent from my Nexus 6 using Tapatalk
---------- Post added at 07:51 AM ---------- Previous post was at 07:47 AM ----------
Gotta be with busy box, twrp. Flashifly should do the job. Strangely I've go a update alert on stock rooted ROM with twrp.
Official Team Bliss Flo/Deb/v410 Maintainer
Sent from my Nexus 6 using Tapatalk

713brianp27 said:
Are you rooted?
Sent from my Nexus 6 using Tapatalk
---------- Post added at 07:51 AM ---------- Previous post was at 07:47 AM ----------
Gotta be with busy box, twrp. Flashifly should do the job. Strangely I've go a update alert on stock rooted ROM with twrp.
Official Team Bliss Flo/Deb/v410 Maintainer
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yes I am.
So, I flashed the stock recovery of Android 5.0.1 and when I try to boot into recovery, I get an Android laying down, chest open with a red caution sign. I think I may have downloaded the wrong version. I probably have Android 5.1 not 5.0.1

Flashifly app does fine job on boot&recovery. Don't see the need for fastboot. Hate wiring up to a computer just for an image. It'll flash it then boot you to it. Bam done
Sent from my Nexus 6 using Tapatalk

You'll not be able to flash teh update because youa re rooted. You will need to flash recovery.img and system.img and boot.img to get back to 100% stock. You will recieve OTA then, though you may aswell download latest version now so no need to update.
---------- Post added at 03:59 PM ---------- Previous post was at 03:58 PM ----------
713brianp27 said:
Flashifly app does fine job on boot&recovery. Don't see the need for fastboot. Hate wiring up to a computer just for an image. It'll flash it then boot you to it. Bam done
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Flashify doesn't flash system.images. You need to do that to flash back to stock.

Flashifly most certainly does. Exactly where is your info coming from.
Sent from my Nexus 6 using Tapatalk
---------- Post added at 09:07 AM ---------- Previous post was at 09:07 AM ----------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 6 using Tapatalk

713brianp27 said:
Flashifly most certainly does. Exactly where is your info coming from.
Sent from my Nexus 6 using Tapatalk
---------- Post added at 09:07 AM ---------- Previous post was at 09:07 AM ----------
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
My info is coming from the fact I have flashify installed for many yars and now it is also coming from your screenshot, which also confirms it cannot flash system images.

Screen shows two images?! Your boot and recovery ARE images. What is the point of the app otherwise?
http://highonandroid.com/android-ap...n-rooted-android-with-flashify-app-root-apps/
Sent from my Nexus 6 using Tapatalk

713brianp27 said:
Screen shows two images?! Your boot and recovery ARE images. What is the point of the app otherwise?
http://highonandroid.com/android-ap...n-rooted-android-with-flashify-app-root-apps/
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
#
I think you're misreading my post. I didn't say it cannot flash images. I said it cannot flash System Images.

danarama said:
#
I think you're misreading my post. I didn't say it cannot flash images. I said it cannot flash System Images.
Click to expand...
Click to collapse
I never said it could flash the system.img
The thread is about recovery. Cut and dry. You bring in a fact I'm aware of. But no one is talking about the system.img . it would be system image, not system images which could confuse , using it plural implies reference to images in the system (partition). Anyway. You can flash your stock recovery.img with app. Thread question solved. And folks he's right, can't flash system image.
Sent from my Nexus 6 using Tapatalk

713brianp27 said:
I never said it could flash the system.img
The thread is about recovery. Cut and dry.
Click to expand...
Click to collapse
No it is not. Read between the lines. The thread is about being able to accept OTA updates. Flashing stock recovery is what the OP has guessed is required to do this (he is wrong)
713brianp27 said:
You bring in a fact I'm aware of.
Click to expand...
Click to collapse
Really? I said it cannot flash system images twice and you still said it could. Maybe you are aware of it, but your reading misses things. I'll give you the benefit of the doubt.
713brianp27 said:
But no one is talking about the system.img
Click to expand...
Click to collapse
I AM!!! Because that is the resolution to this thread.
713brianp27 said:
it would be system image, not system images which could confuse , using it plural implies reference to images in the system (partition).
Click to expand...
Click to collapse
What, you flash one image and then it explodes, so you can't flash any more? You can flash multiple recovery images. I use plural because the English language allows for it. And Yes, System images are the System partition. Not sure I'm grasping your point.
713brianp27 said:
Anyway. You can flash your stock recovery.img with app
Click to expand...
Click to collapse
Great! Though no help here.
713brianp27 said:
Thread question solved.
Click to expand...
Click to collapse
Yes, by using fastboot, which was why I posted about flashify not being able to flash system images. "Don't see a need for fastboot" - Well, there is a need.

Thread title"Getting back stock recovery". Easy. Answered. She want the ota. Not a system.img. Yhey get recovery. Should they get an alert. OTA.
Here is my point. 1) what's the title, answered.
2)you bring up "can't ..." When NOBODY EVER said flash system.img with any app, fastboot, or any other means. Intent is get it via carrier download---
3) How in the world of reality do you flash something that is coming through the carrier update push , as far as I know they don't leave a copy behind
4) Stick to topic. Title... Simple. I can flash stock recovery now, and reflash twrp. So why the "need". Why bring up system image(s). Which can be packaged and flashed in custom recovery. I've got an ota notice running stock root so the only thing I would of lacked was ... Yes correct recovery
I apologize for entertaining and debating. I am going to make an exit. Good day
Sent from my Nexus 6 using Tapatalk

713brianp27 said:
Thread title"Getting back stock recovery". Easy. Answered. She want the ota. Not a system.img. Yhey get recovery. Should they get an alert. OTA.
Here is my point. 1) what's the title, answered.
2)you bring up "can't ..." When NOBODY EVER said flash system.img with any app, fastboot, or any other means. Intent is get it via carrier download---
3) How in the world of reality do you flash something that is coming through the carrier update push , as far as I know they don't leave a copy behind
4) Stick to topic. Title... Simple. I can flash stock recovery now, and reflash twrp. So why the "need". Why bring up system image(s). Which can be packaged and flashed in custom recovery. I've got an ota notice running stock root so the only thing I would of lacked was ... Yes correct recovery
I apologize for entertaining and debating. I am going to make an exit. Good day
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Look, all I wanted to do was help the OP get what they want and identify the need for using fastboot.
The fact that you either didn't read the thread properly or don't have the technical understanding of OTA to answer the question effectively is of no concern. You can argue what you want, but flashify won't help here. Reading the title of a thread is not enough, you should read the full opening post first. You can be forgiven for not having the technical understanding needed to resolve the issue. But you shouldn't keep going on when someone points out that your answer won't help.
In regards to your very last point. Getting notification is not the same as getting the ota. Yes you need stock recovery, but also you must have 100% stock android. No root. Must be never rooted.. I can tell you're a noob by not knowing this and again, that is fine. What is not fine though, is your attitude and refusing to believe you are wrong. It's not the first time you've been like this either. I've seen it before.. I don't really care what you think you know though to be honest.
@Prowler1000, the *ONLY* way you will successfully get an OTA officially in the future is by flashing the system.img first.
You cannot simply have a stock recovery or use any other unroot methods. You must have a clean, untouched rom and kernel, never rooted.. Any change, even if just one letter in a text file of the rom will be enough to make the official OTA flash fail, this i promise you. This is why you must flash a system.image.

Actually on a ROM I built in buildbox. And know my way around. But think what you want. Said bye once. Troll on. Your blocked so I hear no more
Sent from my Nexus 6 using Tapatalk

713brianp27 said:
Actually on a ROM I built in buildbox. And know my way around. But think what you want. Said bye once. Troll on. Your blocked so I hear no more
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Haha. You're priceless. Luckily, anyone reading this thread will see your true qualities.

danarama said:
No it is not. Read between the lines. The thread is about being able to accept OTA updates. Flashing stock recovery is what the OP has guessed is required to do this (he is wrong)
Click to expand...
Click to collapse
No, I just needed to get rid of TWRP so I could get rid of BusyBox. That is all.
Edit: I was hoping by getting rid of BusyBox, I could update without having to flash a system.img so that I don't have to wipe my phone. But I guess that is out of the picture. I will just flash M, rather then waiting for the OTA.

Prowler1000 said:
No, I just needed to get rid of TWRP so I could get rid of BusyBox. That is all.
Edit: I was hoping by getting rid of BusyBox, I could update without having to flash a system.img so that I don't have to wipe my phone. But I guess that is out of the picture. I will just flash M, rather then waiting for the OTA.
Click to expand...
Click to collapse
What you are saying is you want to get rid of TWRP so you can get rid of busybox (TWRP does not need busybox by the way) and that getting rid of busy box will enable you to get an Update.
What I am saying is that is not enough. Root is preventing you getting the update. You *must* flash the system.img to clean your ROM to be able to accept future updates.
However, for info, flashing a system.img does NOT wipe your phone. system.img goes in the /system partition only. It is the ROM. all your data is in the data partition. If you just flash the system.img, recovery.img and boot.img, you will be stock enough to take updates in the future. If you flash the full factory image (which includes all the indivudual images I mentioned, plus cache.img, userdata.img, radio.img, bootloader.img) then that WILL wipe your phone, but you do not need to do that.
If your plan is to stay rooted in the future, the best thing is to keep TWRP and just flash the system.img and boot.img when you ware ready to update. OTA's are more hassle than benefit anyway, and you cant take them if you want to stay rooted. But once rooted on a stock rom, you can never unroot without flashign that system.img (at least not to the point where an OTA will flash successfully

danarama said:
What you are saying is you want to get rid of TWRP so you can get rid of busybox (TWRP does not need busybox by the way) and that getting rid of busy box will enable you to get an Update.
What I am saying is that is not enough. Root is preventing you getting the update. You *must* flash the system.img to clean your ROM to be able to accept future updates.
However, for info, flashing a system.img does NOT wipe your phone. system.img goes in the /system partition only. It is the ROM. all your data is in the data partition. If you just flash the system.img, recovery.img and boot.img, you will be stock enough to take updates in the future. If you flash the full factory image (which includes all the indivudual images I mentioned, plus cache.img, userdata.img, radio.img, bootloader.img) then that WILL wipe your phone, but you do not need to do that.
If your plan is to stay rooted in the future, the best thing is to keep TWRP and just flash the system.img and boot.img when you ware ready to update. OTA's are more hassle than benefit anyway, and you cant take them if you want to stay rooted. But once rooted on a stock rom, you can never unroot without flashign that system.img (at least not to the point where an OTA will flash successfully
Click to expand...
Click to collapse
But I can manually flash the new update, right?

[ROM][STOCK]SM-J700T/T1/Deodexed APK6 Update

I present you a fully deodexed MOSTLY stock working APK6 update with busybox installed, init.d support built in and deknoxed status. Download and flash at your own risk. THIS WILL VOID YOUR WARRANTY! If you point the finger at me for a nuclear cyclone, I will enjoy laughing at you. This will wipe your data upon installation, so make a backup!
INSTRUCTIONS
Download the ROM, boot into recovery and flash.
For root download Supersu v2.79 (https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip)
To mount data in TWRP download @ashyx encryption and dm-verity breaker (https://www.androidfilehost.com/?fid=24591000424951049) flash this after Supersu if you wish to obtain a root exploit.
Reboot.
LINK
https://www.androidfilehost.com/?fid=529152257862723618
THANKS TO
@killshotbravo86 and @walkerblue2023 for helping me tweak the rom
@ashyx for the encryption break
@messi2050 for the awesome kernel
@Chainfire for his awesome supersu work
@ASSAYYED for the awesome Kitchen
DON'T FORGET THE THANKS BUTTON!​

Metabolic12 said:
I present you a fully deodexed MOSTLY stock working APK6 update with busybox installed, init.d support built in and deknoxed status. Download and flash at your own risk. THIS WILL VOID YOUR WARRANTY! If you point the finger at me for a nuclear cyclone, I will enjoy laughing at you. This will wipe your data upon installation, so make a backup!
INSTRUCTIONS
Download the ROM, boot into recovery and flash.
For root download Supersu v2.79 (https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip)
To mount data in TWRP download @ashyx encryption and dm-verity breaker (https://www.androidfilehost.com/?fid=24591000424951049) flash this after Supersu if you wish to obtain a root exploit.
Reboot.
LINK
https://drive.google.com/file/d/0B-PmYxrJj-4Hd0lMT0RZZWpsZ2s/view?usp=sharing
THANKS TO
@ashyx for the encryption break
@messi2050 for the awesome kernel
@Chainfire for his awesome supersu work
@ASSAYYED for the awesome Kitchen
DON'T FORGET THE THANKS BUTTON!
Click to expand...
Click to collapse
Good Job man!

walkerblue2023 said:
Good Job man!
Click to expand...
Click to collapse
Right on brother!

Exactly what I've been waiting for! Thanks brother

ctindell1981 said:
Exactly what I've been waiting for! Thanks brother
Click to expand...
Click to collapse
No problem bro. Glad to help.

I can confirm Magisk v12 works flawlessly

I am currently running this rom and am planning on leaving metropcs since it seemed someone may have ruined their network. I paid for the 60 dollar a month plan and I cant even get close to a single megabit download speed. Is there any way someone could post or attatch a twrp backup of the modem? I tried to flash the stock modem from the stock firmware but I dont have a computer right now and accidentally erased my modem.

micaiahmorris said:
I am currently running this rom and am planning on leaving metropcs since it seemed someone may have ruined their network. I paid for the 60 dollar a month plan and I cant even get close to a single megabit download speed. Is there any way someone could post or attatch a twrp backup of the modem? I tried to flash the stock modem from the stock firmware but I dont have a computer right now and accidentally erased my modem.
Click to expand...
Click to collapse
Install flashfire, you can do all that with the stock firmware package. No PC required. It's a godsend

ctindell1981 said:
Install flashfire, you can do all that with the stock firmware package. No PC required. It's a godsend
Click to expand...
Click to collapse
I tried that but it failed miserably. I also tried to dd if=modem.bin of=/dev/block/mmcblk0p14 (modem.bin from the csc file) in android and the twrp terminal. No luck! I remember a twrp backup of a working modem took care of the problem but I accidentally deleted it and dont have the proper technology to run testdisk or foremost on the internal memory to try and restore the radio.emmc.win.

micaiahmorris said:
I tried that but it failed miserably. I also tried to dd if=modem.bin of=/dev/block/mmcblk0p14 (modem.bin from the csc file) in android and the twrp terminal. No luck! I remember a twrp backup of a working modem took care of the problem but I accidentally deleted it and dont have the proper technology to run testdisk or foremost on the internal memory to try and restore the radio.emmc.win.
Click to expand...
Click to collapse
Did you download the latest stock firmware, load it in flashfire in the ota section, then select the modem, leaving everything else unchecked?
I just uploaded a nandroid of my modem in the next Post. This ought to sorry things out for you

Here's a TWRP backup of my modem. Unzip to the root of your sd card.

ctindell1981 said:
Here's a TWRP backup of my modem. Unzip to the root of your sd card.
Click to expand...
Click to collapse
Thank you bro your a lifesaver!

micaiahmorris said:
Thank you bro your a lifesaver!
Click to expand...
Click to collapse
Did that work for you?

ctindell1981 said:
Did that work for you?
Click to expand...
Click to collapse
nope. I also tried reflashing the stock firmware. Fails at boot loader. m2kefs /dev/block/mmcblk0p14. Now all I got is a tablet. Won't function at all with the modem in place.

micaiahmorris said:
nope. I also tried reflashing the stock firmware. Fails at boot loader. m2kefs /dev/block/mmcblk0p14. Now all I got is a tablet. Won't function at all with the modem in place.
Click to expand...
Click to collapse
Let me create a nand for you and upload it to mega. You still have access to TWRP?
Send me a pm on here, we don't need to spam this thread

ctindell1981 said:
Let me create a nand for you and upload it to mega. You still have access to TWRP?
Send me a pm on here, we don't need to spam this thread
Click to expand...
Click to collapse
I was finally able to resolve my situation. Thinking back.. I thought maybe I just accidentally turned my radio off but I actually hard bricked my phone because I had to format the modem partition for the phone to even function properly over WiFi. Perhaps if anyone else has that problem the new firmware posted on mega.nz will have the proper modem driver for hw rev 05. If not then this phone could have a factory limitation to stop people from developing their own open source Android Rom for the device. A defect I would call it in this case. Although I haven't been able to verify it because I have no reason to corrupt my modem and then try flashing the new firmware.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-J700T1 using Tapatalk

Fantastic bro. Such a rewarding feeling when you figure stuff out. So my firmware helped, or was it another package you found?

I have a J700T1 MetroPCS device. I have been pulling my hair out and studying day and night to run XModGames on my phone. (XMG "XModGames is a modding app for rooted phones to alter games) I have done this before on other phones. I have tried flashing a permissive kernel, and once it was permissive XMG would still give an error. I have installed BusyBox, deleted app data, changed XMG to system app through LuckyPatcher... Restarted and flash my phone several times! Just trying to figure this out... Can anyone give some ideas? I'm testing this ROM Deodex & Deknox but it stayed in T-Mobile boot screen for 30 minutes. I'm about to flash stock again.