Database Develop

[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

VS98024A - OTA manual install + Patched Stock Kernels

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.

Stock Boot, Recovery, System and OTAs for Cherry Mobile One G1

Here're the 7zip-ed stock boot, recovery and system images for the Cherry Mobile One G1:
6.0 (MRA58Y):
Boot: here
*SHA1: 577943CC98CFA242BE149418A9551063CBCB7704
Recovery: here
*SHA1: FDED2C995FDFAB4B9CC1A3A76F5B78F962D730A5
System: here
*SHA1: 7C31848ABE4966AB7BB0867AEEC314DF6895E568
5.1.1 (LUZ59Q):
Boot: here
*SHA1: 260ABCE487CFA01655D5B9E292FDB0E6EA4484EE
Recovery: here
*SHA1: 3902D668BC53E68A919972310AF36A429842AA1C
System: here
*SHA1: B7D4C903BB3D5E7A2E462BDF83C966BEFB4E3B53
5.1.1 (LUZ59M):
Boot: here
*SHA1: 86DF519A78BDDB3A7010EB999CAE64C72AB5E8A0
Recovery: here
*SHA1: 16072C9FD1777FC4264094B367422A3BC47013FE
System: here
*SHA1: 900A86BD863E5998AC0BF989B1DDB1896B4DEC96
MMB29K from MRA58Y:
here
MRA58Y from LUZ59Q:
here
LUZ59Q from LUZ59M:
here
LUZ59M from LUZ59J:
here
Disclaimer: Flash at your own risk as usual.
*SHA1 hashes are for the UNCOMPRESSED files and not the 7z files...

Notes/FAQ:
1.) I compressed them using 7zip since I'll be uploading extremely large files if I didn't. SHA1 hashes for boot and recovery matches those in the install-recovery.sh system file.
2.) The commands for flashing are as follows:
Boot: fastboot flash boot boot.img
Recovery: fastboot flash recovery recovery.img
System: fastboot flash system system.img
*replace boot.img, recovery.img and system.img with their respective filenames
**how to obtain the fastboot executables and drivers are explained in a separate thread
3.) The system.img provided above are stock and NOT ROOTED. If you want to go completely stock, just flash ALL the images above.
4.) These are not meant for UPGRADING. Upgrades usually have bootloader updates in them which might be required.

General mobile
My stock version is LUZ59R, can I flash these filmwares on the General mobile android one 4G?
thanks

Saphire007 said:
My stock version is LUZ59R, can I flash these filmwares on the General mobile android one 4G?
thanks
Click to expand...
Click to collapse
I don't know. Might work but then the OTA's you'll receive might be the Cherry Mobile ones instead of General Mobile's.

intersectRaven said:
I don't know. Might work but then the OTA's you'll receive might be the Cherry Mobile ones instead of General Mobile's.
Click to expand...
Click to collapse
Thanks, I guess I won't take the risk

Today I decided flashing the full firmware from Wileyfox Cyanogen OS 12.1 and played with it a little and decided that the G1 stock rom is better for me personally. So, I tried going back to the stock rom by flashing OTA files given above, but to no avail. It only gave me black screen. I was lucky that I was still able to boot into bootloader and reflash the Wileyfox Rom. So I was wondering if somebody could please pull the full stock rom files from their G1. I really wanted to go back to stock.

The above-posted files ARE the stock images for the G1...
rho57 said:
Today I decided flashing the full firmware from Wileyfox Cyanogen OS 12.1 and played with it a little and decided that the G1 stock rom is better for me personally. So, I tried going back to the stock rom by flashing OTA files given above, but to no avail. It only gave me black screen. I was lucky that I was still able to boot into bootloader and reflash the Wileyfox Rom. So I was wondering if somebody could please pull the full stock rom files from their G1. I really wanted to go back to stock.
Click to expand...
Click to collapse

rho57 said:
Today I decided flashing the full firmware from Wileyfox Cyanogen OS 12.1 and played with it a little and decided that the G1 stock rom is better for me personally. So, I tried going back to the stock rom by flashing OTA files given above, but to no avail. It only gave me black screen. I was lucky that I was still able to boot into bootloader and reflash the Wileyfox Rom. So I was wondering if somebody could please pull the full stock rom files from their G1. I really wanted to go back to stock.
Click to expand...
Click to collapse
This for imobile IQ II(same as G1)
To return to stock rom from CM12.1(wiley Swift)
1.Download ReTurn_IQ_Rom.rar from here and extract to pc destop.
https://drive.google.com/open?id=0BznGujNFQUzsRUctWlNPelV6NDQ
2.Unlock bootloader of your device again(after flashed your device with CM12.1,bootloader may be turn to relock)
3.boot your device to bootloader and connect to pc
4. double click at "3_return_IQ_rom.bat"
5. After first boot , connect your device via wifi to get ota-update from google ,immediately

Beach_Head said:
The above-posted files ARE the stock images for the G1...
Click to expand...
Click to collapse
They are stock images, I know. But those don't include stock images from bootloader and other partitions that were changed during the flashing.
---------- Post added at 07:49 AM ---------- Previous post was at 07:46 AM ----------
mrd.macdonald said:
This for imobile IQ II(same as G1)
To return to stock rom from CM12.1(wiley Swift)
1.Download ReTurn_IQ_Rom.rar from here and extract to pc destop.
https://drive.google.com/open?id=0BznGujNFQUzsRUctWlNPelV6NDQ
2.Unlock bootloader of your device again(after flashed your device with CM12.1,bootloader may be turn to relock)
3.boot your device to bootloader and connect to pc
4. double click at "3_return_IQ_rom.bat"
5. After first boot , connect your device via wifi to get ota-update from google ,immediately
Click to expand...
Click to collapse
Thanks, but before I do another flash, was this tested to work for the G1 already? I mean hypothetically it should work considering that they're all Android One devices, but has anybody actually tried returning to stock A1 rom from Cyanogen OS using this on the G1?

rho57 said:
They are stock images, I know. But those don't include stock images from bootloader and other partitions that were changed during the flashing.
---------- Post added at 07:49 AM ---------- Previous post was at 07:46 AM ----------
Thanks, but before I do another flash, was this tested to work for the G1 already? I mean hypothetically it should work considering that they're all Android One devices, but has anybody actually tried returning to stock A1 rom from Cyanogen OS using this on the G1?
Click to expand...
Click to collapse
If you're just going to go back to the stock you had before going to a CyanogenMod ROM you don't need those firmware files since the CyanogenMod ROMs don't modify those. You just need to flash the correct version that matches your original one.

rho57 said:
Thanks, but before I do another flash, was this tested to work for the G1 already? I mean hypothetically it should work considering that they're all Android One devices, but has anybody actually tried returning to stock A1 rom from Cyanogen OS using this on the G1?
Click to expand...
Click to collapse
The Cyanogen OS .bat installer flashes the other partitions too. Best to wait for a full G1 dump.

arvinquilao said:
The Cyanogen OS .bat installer flashes the other partitions too. Best to wait for a full G1 dump.
Click to expand...
Click to collapse
Exactly. What I was looking for was the full G1 dump.
---------- Post added at 03:28 PM ---------- Previous post was at 03:24 PM ----------
intersectRaven said:
If you're just going to go back to the stock you had before going to a CyanogenMod ROM you don't need those firmware files since the CyanogenMod ROMs don't modify those. You just need to flash the correct version that matches your original one.
Click to expand...
Click to collapse
You might be confusing CyanogenMod, which is a custom rom, from Cyanogen OS which is the stock ROM of Wileyfox. If you've tried flashing the Cyanogen OS from needrom, you should've known that it doesn't just flash boot, system, and recovery, but other partitions such as radio and fastboot as well. Thanks for the insight anyway. I'll just wait for someone to release a full dump from the G1.

rho57 said:
Exactly. What I was looking for was the full G1 dump.
---------- Post added at 03:28 PM ---------- Previous post was at 03:24 PM ----------
You might be confusing CyanogenMod, which is a custom rom, from Cyanogen OS which is the stock ROM of Wileyfox. If you've tried flashing the Cyanogen OS from needrom, you should've known that it doesn't just flash boot, system, and recovery, but other partitions such as radio and fastboot as well. Thanks for the insight anyway. I'll just wait for someone to release a full dump from the G1.
Click to expand...
Click to collapse
I see...still, the full dump is already available. If you need the other partitions, the OTA has the bootloader, radio, etc.

intersectRaven said:
I see...still, the full dump is already available. If you need the other partitions, the OTA has the bootloader, radio, etc.
Click to expand...
Click to collapse
Nice, I didn't bother checking the OTA zip file until now. Indeed, the other partitions are present. I don't have a G1 yet, but thanks for the upload.

Exactly my point...
Perhaps he was on an older build...
intersectRaven said:
If you're just going to go back to the stock you had before going to a CyanogenMod ROM you don't need those firmware files since the CyanogenMod ROMs don't modify those. You just need to flash the correct version that matches your original one.
Click to expand...
Click to collapse
---------- Post added at 10:55 PM ---------- Previous post was at 10:51 PM ----------
Okay. Sorry for the confusion...
rho57 said:
Exactly. What I was looking for was the full G1 dump.
---------- Post added at 03:28 PM ---------- Previous post was at 03:24 PM ----------
You might be confusing CyanogenMod, which is a custom rom, from Cyanogen OS which is the stock ROM of Wileyfox. If you've tried flashing the Cyanogen OS from needrom, you should've known that it doesn't just flash boot, system, and recovery, but other partitions such as radio and fastboot as well. Thanks for the insight anyway. I'll just wait for someone to release a full dump from the G1.
Click to expand...
Click to collapse

intersectRaven said:
I see...still, the full dump is already available. If you need the other partitions, the OTA has the bootloader, radio, etc.
Click to expand...
Click to collapse
Please share G1's full dump .

Like intersectRaven already said, the full dump is already available.
The stock images are posted and the radios, etc. are in the the OTA files...
mrd.macdonald said:
Please share G1's full dump .
Click to expand...
Click to collapse

Beach_Head said:
Like intersectRaven already said, the full dump is already available.
The stock images are posted and the radios, etc. are in the the OTA files...
Click to expand...
Click to collapse
This partitions are not present in ota files,
splash , DDR , abootbak , hypbak , rpmbak , sbl1bak , splash , tzbak
Where to find it ?
{
"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"
}

mrd.macdonald said:
This partitions are not present in ota files,
splash , DDR , abootbak , hypbak , rpmbak , sbl1bak , splash , tzbak
Where to find it ?
Click to expand...
Click to collapse
I won't be providing those as they're unimportant to restoring to a functioning stock boot.
Splash -> Why in heaven's name did you overwrite this?! Anyways, this is just for the spash screen on startup so not important.
*bak partitions -> These contains original boot, modem, etc. images from the factory. They're usually only used when the original fails since it's catastrophic when you can't load RPM or the like.
DDR -> This just contains zero data. Usually reformatted upon OTA since it has something to do with memory retraining. (my guess is to track "bad" memory)

LOL!
intersectRaven said:
Splash -> Why in heaven's name did you overwrite this?! Anyways, this is just for the spash screen on startup so not important.
Click to expand...
Click to collapse
I don't know why you even answered this guy...

[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.

Question Is there a step by step guide for flashing stock payload.bin files.

Hi everyone. Apparently I know just enough to get me in trouble. I received my new OnePlus 10 Pro 5G yesterday which I ordered thinking OnePlus phone were easy to root and mod. I was able to get the boot loader unlocked eventually, but then when I tried to root the phone I ended up in a boot loop. I can still get into to fastboot, lock and unlock my boot loader, but I can't get it to boot.
I found a rollback file for North America and was hoping to hopefully save my new phone by reflashing it.
Sorry for inexperience, I'm hoping there is a guide to doing this. I've been looking for hours
Thanks,
KB

For rooting our device we can use This guide, i don't know which model is you device but probably you can use the files provided there.
Now to solve your problem you need a stock boot.img file that match your current system version and flash it via fastboot

you are kind of sol. keep watching this thread and hopefully someone will post new login creds https://forum.xda-developers.com/t/edl-flash-tool-leak.4494211/

g96818 said:
you are kind of sol. keep watching this thread and hopefully someone will post new login creds https://forum.xda-developers.com/t/edl-flash-tool-leak.4494211/
Click to expand...
Click to collapse
That is what I was afraid of. I saw this thread before asking for help. There is just so much to sort through and hard to know
RokCruz said:
For rooting our device we can use This guide, i don't know which model is you device but probably you can use the files provided there.
Now to solve your problem you need a stock boot.img file that match your current system version and flash it via fastboot
Click to expand...
Click to collapse
My model is the NE2215. I found this rooting guide after following a bad rooting guide. I think the main difference is that the other one had me flash the patched boot.ini file and not boot from that file.
As far as stock boot image, I thought I found one in this thread https://community.oneplus.com/thread/1114712420498538501 for the Android 13 beta. It has a rollback package to revert to 12.

KB- said:
That is what I was afraid of. I saw this thread before asking for help. There is just so much to sort through and hard to know
My model is the NE2215. I found this rooting guide after following a bad rooting guide. I think the main difference is that the other one had me flash the patched boot.ini file and not boot from that file.
As far as stock boot image, I thought I found one in this thread https://community.oneplus.com/thread/1114712420498538501 for the Android 13 beta. It has a rollback package to revert to 12.
Click to expand...
Click to collapse
So you are on global ROM, do you remember which version? If it's the lastest version(NE2215_11_C.21) I can provide you with the stock boot.img

RokCruz said:
So you are on global ROM, do you remember which version? If it's the lastest version(NE2215_11_C.21) I can provide you with the stock boot
Click to expand...
Click to collapse
I had the August update I believe. It was the latest update.

KB- said:
That is what I was afraid of. I saw this thread before asking for help. There is just so much to sort through and hard to know
My model is the NE2215. I found this rooting guide after following a bad rooting guide. I think the main difference is that the other one had me flash the patched boot.ini file and not boot from that file.
As far as stock boot image, I thought I found one in this thread https://community.oneplus.com/thread/1114712420498538501 for the Android 13 beta. It has a rollback package to revert to 12.
Click to expand...
Click to collapse
Don’t know which version you’re on, but it’s best to follow the right guide for your model https://forum.xda-developers.com/t/oneplus-10-pro-ne2215-rooted.4431585/
All the stock boot files are there. Recommend you try booting each one until you find one that works, then validate your phone os version and flash the correct boot image.
May or may not work depending on your luck

KB- said:
I had the August update I believe. It was the latest update.
Click to expand...
Click to collapse
g96818 said:
Don’t know which version you’re on, but it’s best to follow the right guide for your model https://forum.xda-developers.com/t/oneplus-10-pro-ne2215-rooted.4431585/
All the stock boot files are there. Recommend you try booting each one until you find one that works, then validate your phone os version and flash the correct boot image.
May or may not work depending on your luck
Click to expand...
Click to collapse
As said here, download the stock boot from there and only boot it, it your device boots then flash that boot.img on fastboot or fastbootenhace

KB- said:
I had the August update I believe. It was the latest update.
Click to expand...
Click to collapse
I'm sorry, when you say version, I was assuming you meant which software update I had. Which version am I looking for?

RokCruz said:
As said here, download the stock boot from there and only boot it, it your device boots then flash that boot.img on fastboot or fastbootenhace
Click to expand...
Click to collapse
Sorry if these are dumb questions but I just want to make sure I'm doing it right.
I have downloaded both the global (6812ccee9a8a891032af1e053e3217731ac7ad92) and North American versions (2370_sign_NE2215_11_A_OTA_0130_all_bb1e47_10100001)
I have extracted them so I have the boot.img files as well. So you're saying I should run 'fastboot boot boot.img' and if it works, then I should do 'fastboot flash boot.img'?

KB- said:
Sorry if these are dumb questions but I just want to make sure I'm doing it right.
I have downloaded both the global (6812ccee9a8a891032af1e053e3217731ac7ad92) and North American versions (2370_sign_NE2215_11_A_OTA_0130_all_bb1e47_10100001)
I have extracted them so I have the boot.img files as well. So you're saying I should run 'fastboot boot boot.img' and if it works, then I should do 'fastboot flash boot.img'?
Click to expand...
Click to collapse
Yep that should be the procedure, the important thing is if that version match the current installed in your device, do you remember which android version you had? A13? A12?

RokCruz said:
Yep that should be the procedure, the important thing is if that version match the current installed in your device, do you remember which android version you had? A13? A12?
Click to expand...
Click to collapse
I don't know what version I had. I just tried to boot off both boot.img and both failed.

KB- said:
I don't know what version I had. I just tried to boot off both boot.img and both failed.
Click to expand...
Click to collapse
Quick settings look like this? How many updates did you installed?
{
"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"
}

RokCruz said:
Quick settings look like this? How many updates did you installed?
View attachment 5767207
Click to expand...
Click to collapse
I can't get into my phone at all other than the fastboot screen.

KB- said:
I can't get into my phone at all other than the fastboot screen.
Click to expand...
Click to collapse
Yeah I know that but you almost see Q's once, anyway the only way that comes to my mind is flashing the full ROM via fastboot enhance for you device that should be NE2215_11_C21(Android 13)
For now i didn't used that tool, i upgraded my device via local update so I can't help with that

KB- said:
I can't get into my phone at all other than the fastboot screen.
Click to expand...
Click to collapse
RokCruz said:
Yeah I know that but you almost see Q's once, anyway the only way that comes to my mind is flashing the full ROM via fastboot enhance for you device that should be NE2215_11_C21(Android 13)
For now i didn't used that tool, i upgraded my device via local update so I can't help with that
Click to expand...
Click to collapse
Thank you for all your help. I think I've done about all I know how to do. I guess I'll just take it as an expensive lesson learned and hope that there is a way to do it in the future.

RokCruz said:
Yeah I know that but you almost see Q's once, anyway the only way that comes to my mind is flashing the full ROM via fastboot enhance for you device that should be NE2215_11_C21(Android 13)
For now i didn't used that tool, i upgraded my device via local update so I can't help with that
Click to expand...
Click to collapse
I've flashed a full firmware via Fastboot enhance after I installed a GSI..
I connected when in fastboot..
Deleted cow files, need to search then delete each one, then grabbed my most current full firmware payload.bin and flashed it.
Device booted fine, one part of it I need to be in Fastboot d, I think that was the cow files part. I could be remembering that part wrong though.

dladz said:
I've flashed a full firmware via Fastboot enhance after I installed a GSI..
I connected when in fastboot..
Deleted cow files, need to search then delete each one, then grabbed my most current full firmware payload.bin and flashed it.
Device booted fine, one part of it I need to be in Fastboot d, I think that was the cow files part. I could be remembering that part wrong though.
Click to expand...
Click to collapse
@KB- that should fix your issue.
@dladz I guess the patched boot.img needs to be flashed in fastbootd instead bootloader? to avoid bootloops anyway better to just boot it.

RokCruz said:
@KB- that should fix your issue.
@dladz I guess the patched boot.img needs to be flashed in fastbootd instead bootloader? to avoid bootloops anyway better to just boot it.
Click to expand...
Click to collapse
If it's within a payload then no it's integrity is intact.
If it's been extracted to be patched then yes booting is preferred, but there's no option in Fastboot enhance for that.

RokCruz said:
@KB- that should fix your issue.
@dladz I guess the patched boot.img needs to be flashed in fastbootd instead bootloader? to avoid bootloops anyway better to just boot it.
Click to expand...
Click to collapse
Thank you for the advice. Is there a tutorial on how to do all this? I feel like I'm just making it worse since I don't know enough