*********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
Related
Introduction:
This is an update zip containing stock JDQ39E, it is as close to stock as possible.
It also includes the M9615A-CEFWMAZM-2.0.1700.54 radio associated with JDQ39E
It should be close enough to be able to get OTAs when something beyond JDQ39E is released for the N4.
It is NOT rooted or modified in any way, this is as close to what you would expect from an actual google release as possible
It does not include /system/etc/install-recovery.sh as that is never included in preinstalled roms.
Click to expand...
Click to collapse
Requirements:
Fastboot unlocked
A custom recovery, it CANNOT be flashed with the stock recovery
Strongly recommended: Bootloader MAKOZ10o installed beforehand, this update zip does not include a bootloader
Click to expand...
Click to collapse
ROM Details
Build: JDQ39E
Build number: 610897
Build Date: Mar. 20, 2012
Tag: android-4.2.2_r1.2
Kernel:
Code:
[email protected] #1 Tue Mar 12 15:50:26 PDT 2013
Bootloader: MAKOZ10o
Radio: M9615A-CEFWMAZM-2.0.1700.54
Click to expand...
Click to collapse
Instructions:
Unlock device bootloader
STRONGLY RECOMMENDED: Flash MAKOZ10o
Download: update-N4-Stock-JDQ39E-1.zip
Flash or boot preferred custom recovery
Flash update zip with preferred method of flashing update zips
OPTIONAL: Root rom
OPTIONAL: Relock bootloader
Click to expand...
Click to collapse
Warnings:
It is NOT rooted
The stock JDQ39E recovery is included and automatically flashed alongside the rom
As with JDQ39, LTE is not expected to work without modifications
While it MAY be possible to OTA beyond JDQ39E, it is still STRONGLY RECOMMENDED to use an official google factory image when an update comes out
Click to expand...
Click to collapse
Changelog:
May 29, 2013: Initial Release
Click to expand...
Click to collapse
Credits:
Base rom: Google
Radio.img dump: eRajesh
System.img / bootloader.img dump: _Behemoth
Recovery.img dump: [xubz]
Click to expand...
Click to collapse
2char
Hasn't the JDQ39E code been pushed by Google.. awhile back?
http://www.androidpolice.com/2013/0...e-4-2-2_r1-2-here-is-the-developer-changelog/
Also, theres not really much new in JDQ39E, with 4.3 around the corner I don't really see the point for dumping 4.2.2_r1.2?
Unless I'm missing something...
Code yes, rom no.
We didnt get a good JOP40G dump until long after JDQ39 came out, and that was mainly due to the fact a tot exists.
Someone needs to dump it before an update comes out and it's lost to time, there's no guarantee that a tot will ever exist for JDQ39E
A dump of a newer OS version is always welcomed :thumbup:
Since I've already installed a custom kernel (faux123) and rooted. I can only contribute the stock recovery.
(Why oh why didn't I think of a Nandroid backup first. *bangs head on wall*)
Download link for recovery.img (from Stock Indian JDQ39E ROM): http://d-h.st/VHq (MD5Sum of recovery.img: 6300763a32d037cb5a3bdd307bcba4aa)
If you rooted, but know that you didnt do anything else to modify /system: it's likely still good.
I would still appreciate an additional dump of the recovery regardless, it would help to be sure we have a good dump.
Same with the radio, it couldnt hurt.
To dump radio/recovery:
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/<image> of=/system/<image>.img
where <image> is any one of:
recovery
modem
The rest should be done with nandroid
--------------------------------------------------------------------------------------
Edit: I am fairly certian that the recovery provided is a good dump, but I still would welcome a repeat of both the rec and modem to be confirmed
I have made a nandroid of JDQ39E after rooting and installing TWRP. Will it work for your cause? As you know from another thread I do have a 7 day old black nexus 4 with JDQ39E.
I have attached a screenshot of my nandroid backup. What all files do you need? I'm guessing the 1st two and last two?
How did you root, did you just flash supersu/superuser/something.zip?
As long as you didnt end up modifying boot.img, it should be ok that it's rooted.
what i need is boot / system / recovery.
Could I ask if you could redump them with CWM and in tar mode (i think this is the default)
I'm guessing that wins will work, but I'm a lot more comfortable with tars.
Also I plan on making a "stock" update zip with these once i have them, we're almost there
TheManii said:
How did you root, did you just flash supersu/superuser/something.zip?
As long as you didnt end up modifying boot.img, it should be ok that it's rooted.
what i need is boot / system / recovery.
Could I ask if you could redump them with CWM and in tar mode (i think this is the default)
I'm guessing that wins will work, but I'm a lot more comfortable with tars.
Also I plan on making a "stock" update zip with these once i have them, we're almost there
Click to expand...
Click to collapse
I rooted and installed TWRP using WugFresh's NRT 1.6.3.
Yea the root method seems to be fine,
I'd prefer tars but wins are ok if you dont wish to re-backup them as tars.
Here is the boot image -
boot.emmc.win - http://d-h.st/qdR
boot.emmc.win.md5 - http://d-h.st/tAV
Uploading the system image now.
Here is the system image -
system.ext4.win - http://d-h.st/klw
system.ext4.win.md5 - http://d-h.st/vsQ
If anyone can get the stock dump with CWM (I prefer it to TWRP) I'd appreciate it - NOT rooted
@Behemoth.
Any info on how to flash this to the device. Even i had the JDQ39E image when i bought this phone last week in India. But flashed it with a different image so now on JDQ39.
this is getting intereting
rajesheber said:
@Behemoth.
Any info on how to flash this to the device. Even i had the JDQ39E image when i bought this phone last week in India. But flashed it with a different image so now on JDQ39.
Click to expand...
Click to collapse
Absolutely no idea man! The pro's could help better.
If we had the .img files instead of .win you can use the flash-all.bat tool to flash via fastboot
immunityx said:
If we had the .img files instead of .win you can use the flash-all.bat tool to flash via fastboot
Click to expand...
Click to collapse
Exactly this. Surely someone just needs to unlock the bootloader and pulls the files manually?
Sent from my Nexus 4 using xda premium
EddyOS said:
Exactly this. Surely someone just needs to unlock the bootloader and pulls the files manually?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Yup for example for the system img the following command would work
Code:
adb pull /system system.img
---------- Post added at 06:37 PM ---------- Previous post was at 06:35 PM ----------
Im currently at work can someone trying renaming the .win to .tar and exact the .tar file in winrar or some tool similar.. i believe the .img files are in there
{
"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"
}
I'm almost done building an update zip, still testing it
You can just nandroid it with TWRP, but i'd much prefer an update zip over that
{
"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"
}
Requirements:
Flashtool by @Androxyde
XZDualRecovery 2.6 RELEASE or newer.
Current FW version: 10.3.1.A.2.67, maybe others too, let me know!
Special features:
SuperSU integrated in system, FULL root, no reboots when remounting /system RW!
XZDualRecovery 2.7.42 BETA (CWM & PhilZ Touch & TWRP) pre-installed;
Tailored FTF to minimize the chance of accidental system wiping!
No need to clear caches!
For both locked and unlocked bootloaders!
The C6603 ROM is based on the FTF provided by @Androxyde in this thread. Thanks dude
In the following guide I suggest you use an external SDCard but that's just good practice, you can use your internal storage or even an USB OTG storage device in TWRP if you like to install, that's no problem!... If you are modding and the likes, best is to have an external sdcard, just for safeties sake.
C6603: How to update to 10.4.B.0.569:
For C6603: Download C6603.flashable.10.4.B.0.569.zip (Bittorrent: 754MB), SuperSU_fix.zip (1.1Mb) and C6603_10.4.B.0.569_Stripped.ftf (18MB), save it somewhere you remember;
Put 'C6603.flashable.10.4.B.0.569.zip' on (the external) SDcard1;
Put 'C6603_10.4.B.0.569_Stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash 'C6603.flashable.10.4.B.0.569.zip' in TWRP, after flashing the ROM also flash 'SuperSU_fix.zip',
do not reboot but go back to the main menu, then go to reboot->power off;
Flash everything in 'C6603_10.4.B.0.569_Stripped.ftf';
Reboot to system without clearing (dalvik-/)cache.
The first boot will be considerably slower and after a long wait at the boot animation you will see Android optimizing the apps on your phone.
I have done this myself, using this method and I have not found any problem yet, again! :fingers-crossed:
Enjoy! :laugh:
DE-ODEX your ROM! (Read the NOTE below this guide before flashing!)
Make sure you have the flashable ROM installed before you do this.
Download deodex.10.4.B.0.569.zip (Bittorrent: 370MB), save it somewhere you remember;
Put 'deodex.10.4.B.0.569.zip' on (the external) SDcard1;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash 'deodex.10.4.B.0.569.zip' in recovery, do not reboot but go back to the main menu;
Clear dalvik-cache ONLY;
Reboot to system.
The first boot after flashing this you will see Android optimizing the apps on your phone, this might take a while... but should be just fine
NOTE: There are some issues with the deodexed ROM, it sometimes causes a FC, specifically if you go to keyboard & language settings through the settings app. I'm not able to find why it does this but my guess is that it's a bug in the Sony ROM that surfaces with deodexing it... There is a work around for this one though: Open any keyboard driven app (text editing/entering box), tap '12!?' and then tap the tools button on the right of the space bar. This will take you to the app to modify your keyboard settings.
Known XZDualRecovery Issues:
Busybox Updater/Installer: If you have XZDualRecovery installed, un-install any Busybox updating app/tool as most if not all of them will install a version of busybox which does not support the lzma compression applets XZDualRecovery depends on. The version installed together with XZDualRecovery is very stable and I have yet to hear anyone complain about it's stability.
How to report errors:
Please, before shouting out "It doesn't work!!1!" or "I lost root!" or even "My phone reboots when remounting /system RW!!" try the following:
Restore a /system ONLY using any means you are familiar with so you can try again.
Root it using [Z][ROOT] DooMLoRD Easy Rooting Toolkit.
Install XZDualRecovery and then try to update again using TWRP. This time you can skip the FTF as it has already done it's job.
If it still fails something from there on: LOGS!!.
NOTE: The important ones can be found in /cache/recovery and in /tmp/XZDualRecovery, pack them up and send them to me.
Thank you
Good shot man thank you
Tested and no bug at the moment
Sent from my C6603 using Tapatalk
if im getting this well, i am on a stock ROM of 4.2.2 (.67)running dual recovery as well.
I wont need to wipe or anything, i should just install this over it??
i'm to fast , downloading (85%) the original ftf packaged from androxyde , gonna try this later thanks man
A big Thanks for this Sir @Nut...
still waiting for the downloaded fw of 4.3 for my Z to test this..thanks again Sir :good:
slimldj said:
if im getting this well, i am on a stock ROM of 4.2.2 (.67)running dual recovery as well.
I wont need to wipe or anything, i should just install this over it??
Click to expand...
Click to collapse
Correct
Thanks you very much.
Added the deodex package to the OP.
Have fun modding JB 4.3 folks
[NUT] said:
Correct
Click to expand...
Click to collapse
I did it. After flashing the ftf file with flashmode, I rebooted and it came out with a triangle and a progress bar at the bottom. At first I tot something had gone wrong but that was just the phone actually updating to the new FW.
Thanks for this NUT. Hopefully we'll see more of your work like this for future released FW's.
Sent from my C6603 using Tapatalk
HELP!!!! Flash Tool not recognizing my Z :crying: green bulb flash ones :/
will this wipe the contents of internal storage??
doomhammer07 said:
will this wipe the contents of internal storage??
Click to expand...
Click to collapse
i think , nope sir...but to be sure, make a back-up before flashing
is this a pre release firmware or the final version?
spazzy1912 said:
is this a pre release firmware or the final version?
Click to expand...
Click to collapse
i think not yet sir, sony has not announced yet its final version or the official of it
totzkitotz said:
i think not yet sir, sony has not announced yet its final version or the official of it
Click to expand...
Click to collapse
oh i see, at least that means the official is just around the corner :3
spazzy1912 said:
oh i see, at least that means the official is just around the corner :3
Click to expand...
Click to collapse
yeah :highfive: i can smell it
How about the 6602? All your previous roms also worked on the 6602, but this is a complete new Android version, so i'm kinda scared.
denniskrol said:
How about the 6602? All your previous roms also worked on the 6602, but this is a complete new Android version, so i'm kinda scared.
Click to expand...
Click to collapse
i flashed it on my c6602 and it works fine
slimldj said:
I did it. After flashing the ftf file with flashmode, I rebooted and it came out with a triangle and a progress bar at the bottom. At first I tot something had gone wrong but that was just the phone actually updating to the new FW.
Thanks for this NUT. Hopefully we'll see more of your work like this for future released FW's.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
How long until the triangle screen went away?
travisd4est said:
How long until the triangle screen went away?
Click to expand...
Click to collapse
About 3 to 5 mins.
Sent from my C6603 using Tapatalk
After interrupting the 11A to 12B OTA to see what was happening and decompiling certain framework bits along with the LGFOTA.apk I was able to figure out how to force the 24A OTA KitKat build to install. Thanks to @JackpotClavin for finding the bin file.
It looks like an official release is near, so if you aren't VERY comfortable with adb, etc. then this isn't for you, and please don't attempt it. As with any procedures of this sort you risk getting your phone in an unusable state and potentially worse. If you are comfortable with this and don't want to wait for the OTA, here's what I did to make it work. Hopefully this will also help others force future OTAs as the procedure should be transferable.
Manual OTA Install:
Restore to 100% stock VS98012B via one of the available tot/kdz methods, then get root using the latest ioroot from autoprime (or do it manually). Don't install a recovery. Don't modify anything.
Download the bin file from here and verify that the md5 is ebb9750e33574c7738a8256fb01a9e00
Rename the file to dlpkgfile and push it to /cache/fota/
From an adb shell run the following command:
Code:
echo "--update_package=/cache/fota/dlpkgfile" > /cache/recovery/command
** Note: If the recovery directory does not exist on your phone...create it
From adb shell run the following command:
Code:
am start -n com.lge.lgfota.permission/com.lge.lgfota.permission.DmcEzUpdateStart
The phone will restart on its own and go through the software update procedure.
Optional:
If you want a custom recovery, then you have a few more steps. JackpotClavin has already written up an excellent guide on how to do so HERE. Follow his steps 5-8 (as you've theoretically already followed this guide to get to 24A), and substitute one of the .lok files included in this archive for the file named "boot.emmc.win" in step 7. If you have already gone through that procedure and have a custom recovery, you can simply flash either of the following two zips:
xdabbeb_vs98024a_kernel_google_gcc
xdabbeb_vs98024a_kernel_linaro_gcc
Q: What's the difference between the two?
A: One is built with the standard 4.6 gcc toolchain (same as stock LG) and the other is built with a linaro 4.7.4 optimized gcc toolchain.
Note: In order to have a custom recovery you need to be use an older (12b, 4.2.2) aboot/bootloader. At the same time, your laf partition (which is the one responsible for download mode) is now based on the new 24A OTA and won't work with the older aboot. All you need to do to get a working download mode again is dd the laf partition from 12b. You can find it right here. Since the only way you got to this point is by using dd to install an older aboot, I'll assume you can do the same thing for laf.
Devs: Feel free to use the kernels in your roms. Just give credit in your OP.
FAQ
Can I flash this with a custom recovery?
No, 100% stock. Follow the instructions in the OP or find an alternate version on pg. 37 here. There's also a video here, thanks Chet.
Is this Android 4.4.2 Kit Kat?
Yeah.
Is ART included/working?
It's broken/unusable for now.
Can I root on 24A?
Yeah. Use ioroot25!
Can I do this from my phone?
If you're rooted, go ahead and download a terminal emulator app. Then, proceed to do the process from your phone.
Enter The Nexus said:
No way to keep your data? Other than that, thanks, you're amazing.
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Well, if you want to manually undo every last thing on your phone that could possibly bork an OTA patch you certainly could, but I've made dozens of modifications to the stock ROM that I know would cause problems so for me it was easier to just use the TOT method to restore.
Only mod I have is Xposed. If I uninstall and reboot, should be good?
VZW LG G2 VS980
Only thing I've done is installed twrp.
Anyway to just undo that change?
Sent from my VS980 4G using xda app-developers app
This kept root you said?
Did you use any root backup method or you just kept the original /system/xbin/su and it didn't do anything?
Sent from my LG-VS980 using xda app-developers app
JackpotClavin said:
This kept root you said?
Sent from my LG-VS980 using xda app-developers app
Click to expand...
Click to collapse
Yes. It's just like the D80x update, they kept root, so did we.
Sent from my VS980 4G using Tapatalk
I'm not sure you can flash a stock recovery back. Perhaps using flashify to flash recovery image back?
UPDATE
3/31/2014
I've posted more details of the procedure on page 37
http://forum.xda-developers.com/showthread.php?p=51514625
Hope it helps some of you with the little details. Kit Kat runs great.
Sent from my VS980 4G using XDA Premium 4 mobile app
Yeah find the stock img in the old VZW thread. I'm going to try this on a rooted stock debloated ROM.
Sent from my VS980 4G using Tapatalk
@JackpotClavin Correct, I kept root and I've never used any of those "rootkeeper" methods. I just manually pushed/created everything necessary for root (you can look at the update-binary for SuperSU if you want) and it works fine.
If you have a stock vs98012b recovery you can just dd it back. At one point in my testing I did so. Here it is if you don't have it.
Is the FOTA apk needed?
Sent from my VS980 4G using Tapatalk
xdabbeb said:
@JackpotClavin Correct, I kept root and I've never used any of those "rootkeeper" methods. I just manually pushed/created everything necessary for root (you can look at the update-binary for SuperSU if you want) and it works fine.
If you have a stock vs98012b recovery you can just dd it back. At one point in my testing I did so. Here it is if you don't have it.
Click to expand...
Click to collapse
In the future we would probably have to downgrade back to 12b to reinstall custom recovery as Roms come out with this base correct?
Epic FAIL.
flyinj54 said:
In the future we would probably have to downgrade back to 12b to reinstall custom recovery as Roms come out with this base correct?
Click to expand...
Click to collapse
At this point, yes. Doing this will get you on stock KK. Waiting to flash this as a rooted custom rom will allow you to keep recovery.
Sent from my VS980 4G using XDA Premium 4 mobile app
That worked perfectly to get it started. Good find! Step two is taking forever, but I feel good about the outcome!
You changed the name of the file without .bin on the end, correct? Not sure why my attempt failed.
I already have files in my /cache/fota folder, should those be deleted?
{
"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"
}
player911 said:
At this point, yes. Doing this will get you on stock KK. Waiting to flash this as a rooted custom rom will allow you to keep recovery.
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What do you think about fastboot flashing modem.img for aosp based roms? Should work right?
Edit: kk modem breaks boot on cm11 ;p
RandomGuy982 said:
That worked perfectly to get it started. Good find! Step two is taking forever, but I feel good about the outcome!
Click to expand...
Click to collapse
Yeah, step two takes forever. Did that both times for me.
jesssiii said:
You changed the name of the file without .bin on the end, correct? Not sure why my attempt failed.
I already have files in my /cache/fota folder, should those be deleted?
Click to expand...
Click to collapse
Correcto. You could really name it whatever you want, but you'd need to adjust elsewhere accordingly. If you do everything exactly as in the OP you'll be fine. As I mentioned, if you had anything that wasn't 100% stock it could cause the update to fail. You will have a dummy file and a muc file in the fota/ dir from what I remember. Those are fine. If you had been attempting this on your own and left other files around I suppose it could cause problems though. Best to wipe it all out and return to 100% stock if you're not sure!
I'm getting no such file or directory regarding the first command- /cache/recovery/command.
This is a Safe Upgrade to the latest Lollipop firmware (N910VVRU2BOF1) for VZW Samsung Galaxy Note 4 (SM-N910V), both Retail & Developer Editions.
{
"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"
}
★ What do you mean by "Safe Upgrade"?
The latest N910VVRU2BOF1 bootloader is incremented; i.e., if you take the OTA or flash the official firmware via Odin, you won't be able to downgrade.
For Retail Edition: This is very important if you want to gain ROOT access when available & keep it over OTAs then.
For Developer Edition: If the bootloader is incremented with any coming OTA, it'll block your unlocked bootloader for good & you'll end up with a Retail Edition.
Click to expand...
Click to collapse
Check this thread for more details!
Safe upgrade allows you to downgrade (roll back) to any previous firmware (KK or LP)...
Click to expand...
Click to collapse
★ Disclaimer:THIS SERVICE IS FREE OF CHARGE, USE IT AT YOUR OWN RISK, TAKE IT OR LEAVE IT !
★ Instructions:
Extract the N910VVRU2BOF1_StockRestore.tar.md5 file using 7-Zip
Extract Odin v3.09 & open it
Reboot to Download Mode (press and hold Home + Power + Volume Down)
Connect phone and wait until you get a blue sign in Odin
Add the N910VVRU2BOF1_StockRestore.tar.md5 file to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back & wait a few minutes
Reboot into recovery (press and hold Home + Power + Volume Up)
Wipe data (Factory Reset)
Reboot to system
Special Instructions:
For Retail Edition coming from KK, flash N910VVRU1BOAF_Bootloaders.tar.md5 via Odin
<<<>>>
For Developer Edition, flash TWRP recovery, SuperSU & MultiSystem/Patched Kernel
DO NOT FLASH RETAIL BOORLOADER, IT WILL LOCK YOUR DEVICE !
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Downloads:
N910VVZW2BOF1 Stock Restore: N910VVRU2BOF1_StockRestore.tar.md5.7z
md5: 1c4df35b699e00bad4522cd24dde839a
N910VVRU1BOAF Bootloaders (RetEd ONLY): N910VVRU1BOAF_Bootloaders.tar.md5.7z
md5: deeef3cde3941572b036c0f6ea6e92b3
Click to expand...
Click to collapse
can i install this on my dev ed . will my bootloader still be unlocked ?
Sent from my iPhone using Tapatalk
salmanslick said:
can i install this on my dev ed . will my bootloader still be unlocked ?
Click to expand...
Click to collapse
YES. The title says "RetEd/DevEd" & the description states that it's a safe upgrade for both retail & developer editions!!! VERIZON VARIANT ONLY.
What does this upgrade actually do or improve?
krishaun27 said:
What does this upgrade actually do or improve?
Click to expand...
Click to collapse
No changelog available yet!
I can see many users are eager to upgrade & some have already taken it. So, a safe upgrade is important for both retail (to be able to downgrade for root whenever possible) & developer (to keep the bootloader unlocked) editions.
hsbadr said:
No changelog available yet!
I can see many users are eager to upgrade & some have already taken it. So, a safe upgrade is important for both retail (to be able to downgrade for root whenever possible) & developer (to keep the bootloader unlocked) editions.
Click to expand...
Click to collapse
So there's no going back to KK (NJ5) if I Odin this on my Note 4 DE?
Sent from my SM-N910V using Tapatalk
krishaun27 said:
So there's no going back to KK (NJ5) if I Odin this on my Note 4 DE?
Click to expand...
Click to collapse
Read the OP! Safe Upgrade = Ability to downgrade...
hsbadr said:
Read the OP! Safe Upgrade = Ability to downgrade...
Click to expand...
Click to collapse
OK, I see you JUST edited the OP. It was not entirely clear at first.
krishaun27 said:
OK, I see you JUST edited the OP. It was not entirely clear at first.
Click to expand...
Click to collapse
No problem! It's the difference between official OTA/upgrade & safe upgrade.
Thanks Hasbdr! I was looking for this! Hopefully the install goes well..
Note 4 on Tap
Sorry to have to ask but very much a newb at attempting this.
For updating retail edition from KK do you flash N910VVRU1BOAF_Bootloaders.tar.md5 via Odin and also flash N910VVRU2BOF1_StockRestore.tar.md5 to AP or is it one or the other? If you need to be doing both to upgrade Retail edition from KitKat, what order do you do it in with those 2 files?
Thanks for any help you can offer.
MatroxD said:
Thanks Hasbdr! I was looking for this! Hopefully the install goes well..
Click to expand...
Click to collapse
You're welcome! Glad I could help.
mray99 said:
Sorry to have to ask but very much a newb at attempting this.
For updating retail edition from KK do you flash N910VVRU1BOAF_Bootloaders.tar.md5 via Odin and also flash N910VVRU2BOF1_StockRestore.tar.md5 to AP or is it one or the other? If you need to be doing both to upgrade Retail edition from KitKat, what order do you do it in with those 2 files?
Thanks for any help you can offer.
Click to expand...
Click to collapse
It doesn't matter! Flash both tars via Odin & wipe data in recovery before the 1st boot!
mray99 said:
Sorry to have to ask but very much a newb at attempting this.
For updating retail edition from KK do you flash N910VVRU1BOAF_Bootloaders.tar.md5 via Odin and also flash N910VVRU2BOF1_StockRestore.tar.md5 to AP or is it one or the other? If you need to be doing both to upgrade Retail edition from KitKat, what order do you do it in with those 2 files?
Thanks for any help you can offer.
Click to expand...
Click to collapse
Flash both...using Odin, flash new updated OF1 .tar in AP/PDA slot and OAF bootloader .tar in BL slot.
Wait till is finished then boot into recovery wipe/factory reset, boot to system.
From what little I read about the update, reports of no change in phone performance other than new app milk music and the new bootloader not allowing to roll back to KK.
VZW and Sammy likely noticed how close devs are to disabling WP lol
Sent from my SM-G920V using Tapatalk
stealyourface1 said:
Flash both...using Odin, flash new updated OF1 .tar in AP/PDA slot and OAF bootloader .tar in BL slot.
Wait till is finished then boot into recovery wipe/factory reset, boot to system.
From what little I read about the update, reports of no change in phone performance other than new app milk music and the new bootloader not allowing to roll back to KK.
VZW and Sammy likely noticed how close devs are to disabling WP lol
Click to expand...
Click to collapse
This safe upgrade allows you to downgrade, if needed. VZW didn't release any changes yet, but I can see that it includes IMS updates, MSDC API, EMBMS, GMS & security updates... + some new bloatware.
hsbadr said:
This safe upgrade allows you to downgrade, if needed. VZW didn't release any changes yet, but I can see that it includes IMS updates, MSDC API, EMBMS, GMS & security updates... + some new bloatware.
Click to expand...
Click to collapse
I'm staying on KK until all hope is lost for perm root...been hoping for perm root to run your multi system on my N4...
Sent from my SM-N910V using Tapatalk
---------- Post added at 11:00 PM ---------- Previous post was at 10:57 PM ----------
@hasbadr thank you for all your hard work
Sent from my SM-N910V using Tapatalk
hsbadr said:
It doesn't matter! Flash both tars via Odin & wipe data in recovery before the 1st boot!
Click to expand...
Click to collapse
stealyourface1 said:
Flash both...using Odin, flash new updated OF1 .tar in AP/PDA slot and OAF bootloader .tar in BL slot.
Wait till is finished then boot into recovery wipe/factory reset, boot to system.
From what little I read about the update, reports of no change in phone performance other than new app milk music and the new bootloader not allowing to roll back to KK.
VZW and Sammy likely noticed how close devs are to disabling WP lol
Click to expand...
Click to collapse
Thanks very much to both of you for answering my question. Much appreciated!
I can attest to a blown locked bootloader. DON'T Just flash the retail edition, as that's EXACTLY what you'll get -
Follow HSBADR's instructions exactly.
I will keep HASBADR informed as to how my repair goes with samsung, as they will re-flash the phone back to developer for me, of course to the same version of KitKat that came with the developer. I am anticipating making the call tomorrow morning - speaking with Samsung's tech support, I already have a service ticket, just need to follow through with this.
as an FYI - I will tell you, yup, no noticeable difference in features in the update, maybe, just maybe a small small increase in battery life, for a retail edition - but, dang, miss that developer bootloader. I was stupid folks...
hsbadr you rock! I've been wanting to jump from NJ5 KitKat to Lollipop but have been waiting for a newer release for Gear VR driver support fixes (performance has been awful in Lollipop). Apparently Samsung was to deliver a fix by end of June so hopefully this build 6/16 (BOF1) may include those fixes .
Do I have to factory reset the device if updating from OAF?
Went through the motions and got up and going no issues from the start going NJ5 to OF1 via the safe upgrade in ODIN. Did initial boots no issues and went through the motions, went back and flashed TWRP then one of the patched kernels noted and now stuck in a boot loop. Tried flashing back the stock OF1 kernel via ODIN and still boot loops.
Flashed back the OF1 safe upgrade ODIN and now I'm back going again. Am I missing something?
EDIT: Tried again after flashing a second time to OF1 fresh from ODIN, flash the latest TWRP 2.8.7.0 no issues, multiple reboots quick and snappy. Tried patched kernel v3 and boot loops again, flash stock kernel for OF1 and still bootloops (cleared dalvik / cache both kernels), not sure about that.
Hi,
to seperate the discussion happened in the cm12 thread I open this new thread.
I am not the developer of this rom and you have to try i ON YOUR OWN RISK!
First you need an unlocked JBBL Bootloader.
If you have not unlocked it yet look for tutorials here or use the sunshine app.
If you are on KKBL you have first to downgrade your Bootloader. I have used this howto:
http://forum.xda-developers.com/showthread.php?t=2789743
worked fine for me! BUT AGAIN: I AM NOT RESPONSIBLE IF YOU ARE DAMAGE YOUR DEVICE.
You have first to flash a TWRP Version for the XT907:
http://4pda.ru/forum/index.php?showtopic=403669&st=18740#entry45788372
And now the rom:
http://forum.xda-developers.com/droid-razr-m/general/rom-t3343987
And you need some gApps.
I use opengapps! works great!
YOU HAVE TO FLASH BOTH ON ONE TIME! FIRST IN QUE IS THE ROM AND THEN THE GAPPS!
On the first boot the optimization of the apps is in russian language. In the first configuration window you can choose your language!
The rom works really fine for me with one exception: I am in Germany and have to use hdspa+ with this device. I did not get hdspa+ working yet. maybe I need another modem file?
Other users have problems with bluetooth... for me bluetooth works fine!
NFC should not working... I have not tried!
Regards
Ibaxx
edit:
link for new build from 23th april 2016:
https://yadi.sk/d/bhD94py_rEVHc
first official build for razr hd:
https://yadi.sk/d/F_-QsaQGrHcDg
I have some huge problems with this build with an clean install! upgrade from xt907 build works fine...
xt907 build from the 1st may 2016
https://yadi.sk/d/vTsjh4DBrRbeC
Does it work on the xt925 as well?
I don't know, maybe I find some time at the weekend to try out! But I can't try the radio on my xt925, because the Sim Slot is damaged
Sadly this doesn't works on an MB886 (Atrix HD). I know, totally different device, but just wanted to tell.
ibaxx said:
I don't know, maybe I find some time at the weekend to try out! But I can't try the radio on my xt925, because the Sim Slot is damaged
Click to expand...
Click to collapse
Thanks, my father has this phone so I can't test it myself,I would appreciate if you could test it.
cm-13.0-20160423-port-ilichva-xt907_jbbl
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
It.s msm8960 unified firmware, it will work on xt925
I have still Radio Problems... No HSDPA+ and WLAN connects only manually... Any ideas?
niton said:
cm-13.0-20160423-port-ilichva-xt907_jbbl
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
It.s msm8960 unified firmware, it will work on xt925
Click to expand...
Click to collapse
Tried it again on a MB886 (Atrix HD) without luck. I think it's not unified or there is something wrong. I'm already using TWRP 3 but it always stays on "Patching system image unconditionally". Any ideas?
I think that twrp 3 is only for xt907, i have xt926 and using twrp 2800 jb to install this rom is working well and i try to instal with twrp 3 i have error 7 so i still using twrp 2800 jb for this rom.
Nprevette has allready build blissmm for jb bootloader (alpha) and I try to install it on xt926 and it won't boot to home screen using twrp 2800 and i try it too with twrp 3 and i have error 7 maybe the recovery is not compatible for blissmm..
Is anyone here try blissmm jb rom?
I don't know the error I got when I tried First to install through a xt926 Recovery... Habe you installed the xt907 twrp Version?
Also die someone come from Verizon Rom?
You have First Format internal data through Recovery
Else you got an error
Error7 mean you try to install wrong firmware, so, to install wrong firmware, you should install wrong recavery flash twrp 3.0.2 for xt907, run it, wipe all, except external card, twice and then try to install firmware, and keep patiance, its stuck on patching system for along time. Also, old safestrap recovery works well, you can try it
With the Recovery from 4pda it is not possible to install blissmm...
The download Server from Bliss was down yesterday evening... I couldn't Download the Recovery from there.
I allready try to install bliss6 with twrp 3 full wipe and format internal storage but still have "error 7 this rom is for msm8960 not for scorpion mini"
Got the same error! Also with the twrp from Bliss
The twrp Version from Bliss shows up the Micro SD two times... Attention on wiping!
cm-13.0-20160425-port-ilichva-xt925_jbbl by ilichva
as you can see, it's not xt 907 port, it's for xt925, use the same twrp 3.0.2 recovery
NFC is working now, HSPA+ should work too
Can i install it to xt926?
dedik46 said:
Can i install it to xt926?
Click to expand...
Click to collapse
have installed it on xt926 looks like it runs fine!
i will try it a few days
Sliding down the notifications bar to quicksettings did not work! any ideas?
Buggy AS hell !
No notifications in The bar .... Lockscreen didnt work... Hspa+ did not work! Laggy system!