Database Develop

[STOCK][C6603][4.3] Update to 10.4.B.0.569 [Root & XZDualRecovery][DE-/ODEX]

{
"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

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.

[Q] need help broken usb prot

hi guys im having problems with my usb port on my s3 mini l1890T its been rooted and is currently running a custom ROM but i need to put it back to stock so i can use the warrenty to get it fixed however i cant find any backups of this phone prior to the custom rom as i think it was on my old pc when it kicked the bucket. so im after a stock rom that could be flashed via cwm if this is possible.
please help and leave a comment even if its to say sorry but your screwed. i really need to get this sorted tonight as i need to return it in the morning.

jezcullen09 said:
hi guys im having problems with my usb port on my s3 mini l1890T its been rooted and is currently running a custom ROM but i need to put it back to stock so i can use the warrenty to get it fixed however i cant find any backups of this phone prior to the custom rom as i think it was on my old pc when it kicked the bucket. so im after a stock rom that could be flashed via cwm if this is possible.
please help and leave a comment even if its to say sorry but your screwed. i really need to get this sorted tonight as i need to return it in the morning.
Click to expand...
Click to collapse
Stock ROM via cwm is possible but I don't know if anyone have made a zip for it.
What country/service provider?
Sent through time and space from my s3mini/CM11

im in new zealand and im on telecom.
my wife has the same phone i was wondering if i could root her phone then take a backup of that and install the backup on mine
would that work?

tys0n said:
Stock ROM via cwm is possible but I don't know if anyone have made a zip for it.
What country/service provider?
Sent through time and space from my s3mini/CM11
Click to expand...
Click to collapse
im in new zealand and im on telecom.
my wife has the same phone i was wondering if i could root her phone then take a backup of that and install the backup on mine
would that work?

jezcullen09 said:
im in new zealand and im on telecom.
my wife has the same phone i was wondering if i could root her phone then take a backup of that and install the backup on mine
would that work?
Click to expand...
Click to collapse
Could work, depending on how backups are stored. I can just tell that tarp looks for backups in a folder with your device-id.
{
"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 you need is system and boot, and a flashable zip with original recovery.
Sent through time and space from my s3mini/CM11

tys0n said:
Stock ROM via cwm is possible but I don't know if anyone have made a zip for it.
What country/service provider?
Sent through time and space from my s3mini/CM11
Click to expand...
Click to collapse
tys0n said:
Could work, depending on how backups are stored. I can just tell that tarp looks for backups in a folder with your device-id.
View attachment 2783531
What you need is system and boot, and a flashable zip with original recovery.
Sent through time and space from my s3mini/CM11
Click to expand...
Click to collapse
i dont suppose you know where i could find them do you?
what about the idea that i had with my wifes phone?

jezcullen09 said:
i dont suppose you know where i could find them do you?
what about the idea that i had with my wifes phone?
Click to expand...
Click to collapse
No i dont. Not as cwm flashable zip.
Backup from another phone probably works as long as the backup folder is named right so that recovery finds it.
Make a backup and folders will be created, use external storage.
Whole restore process would be:
Make sure binary count is zero with triangle away.
Boot download mode to make sure as well.
Copy backups of system and boot to backup folder.
Boot to recovery, factory reset, restore backups from other phone, factory reset again.
Boot system to see that all is OK.
Unroot from SuperSU settings if needed.
Back to recovery to flash flashable zip of stock recovery.
I guess you'll have to make one more factory reset from stock recovery to get everything official status.
I hope I didn't miss anything
(I can make that zip for you if you'll need it. Downloading firmware right now, just in case)
Sent through time and space from my s3mini/CM11

tys0n said:
No i dont. Not as cwm flashable zip.
Backup from another phone probably works as long as the backup folder is named right so that recovery finds it.
Make a backup and folders will be created, use external storage.
Whole restore process would be:
Make sure binary count is zero with triangle away.
Boot download mode to make sure as well.
Copy backups of system and boot to backup folder.
Boot to recovery, factory reset, restore backups from other phone, factory reset again.
Boot system to see that all is OK.
Unroot from SuperSU settings if needed.
Back to recovery to flash flashable zip of stock recovery.
I guess you'll have to make one more factory reset from stock recovery to get everything official status.
I hope I didn't miss anything
(I can make that zip for you if you'll need it. Downloading firmware right now, just in case)
Sent through time and space from my s3mini/CM11
Click to expand...
Click to collapse
that would be awsome if you could make that zip for me i would really appreciate it but if its to much of a hasel for you ill start the process of rooting my wifes phone.

jezcullen09 said:
that would be awsome if you could make that zip for me i would really appreciate it but if its to much of a hasel for you ill start the process of rooting my wifes phone.
Click to expand...
Click to collapse
No problem at all. I could have made whole firmware for you if it wasn't for my damn internet upload when I'm at home. (data plan from my phone at the moment)
Downloaded firmware while I was at a friend.
Sent through time and space from my s3mini/CM11

tys0n said:
I could have made whole firmware for you if it wasn't for my damn internet upload when I'm at home. (data plan from my phone at the moment)
Click to expand...
Click to collapse
i know that feeling we live out on a farm and the speeds are so slow

Damn. I just extracted firmware and recovery.img is not included there.
Sent through time and space from my s3mini/CM11
---------- Post added at 02:59 PM ---------- Previous post was at 02:14 PM ----------
Im pretty sure i8190 stock recovery will do anyway. We got the same partitions. Otherwise you would not been able to flash a custom recovery neither.
Sent through time and space from my s3mini/CM11

Any progress?

tys0n said:
Any progress?
Click to expand...
Click to collapse
No not yet I went root my wife's phone but she had next to no battery plus it was about 2 in the morning

jezcullen09 said:
No not yet I went root my wife's phone but she had next to no battery plus it was about 2 in the morning
Click to expand...
Click to collapse
Ah I see.
Is this the firmware you two have?
PDA: I8190TDCAMA3
CSC: I8190TTNZAMA2
MODEM: I8190TDCAMA3
If it is, then I got a flashable zip for you. Took me only ten minutes to make, and uploaded at another friend
No root no, busybox, no deodexed. Just stock.
I8190T-DCAMA3_I8190T-TNZAMA2_TNZ.zip

tys0n said:
Ah I see.
Is this the firmware you two have?
PDA: I8190TDCAMA3
CSC: I8190TTNZAMA2
MODEM: I8190Towe you oneDCAMA3
If it is, then I got a flashable zip for you. Took me only ten minutes to make, and uploaded at another friend
No root no, busybox, no deodexed. Just stock.
I8190T-DCAMA3_I8190T-TNZAMA2_TNZ.zip
Click to expand...
Click to collapse
Thanks mate she worked all that is left is the cwm but I'm going to risk sending it in for repair.
I owe you one if you ever find your self in nz come have a feed

jezcullen09 said:
Thanks mate she worked all that is left is the cwm but I'm going to risk sending it in for repair.
I owe you one if you ever find your self in nz come have a feed
Click to expand...
Click to collapse
Good to hear that it worked out fine. I even flashed it myself to make sure it would work.
Nothing owned.. A simple push on thanks button is enough
Hope you'll get it back fully functional again.
Sent through time and space from my s3mini/CM11

HTC One M7(Intl) soft bricked? What ROM?

Hi so I've spent a good deal of the morning attempting to finally fix this phone, a couple years ago I removed all OS from it and no backup but I still have TWRP.
The phone is tampered/unlocked.
Hboot is 1.54.0000
I tried loading one of the latest ROMS from here via side loading - http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
I used this guide - http://htc-one.wonderhowto.com/how-to/fix-soft-bricked-htc-one-by-flashing-new-rom-via-adb-0154361/
Unfortunately once the sideload is complete I get an error E: Zio file is corrupt, I was wondering if anyone knows what I'm doing wrong? Can attempt to provide more information if required.

Purdy8TV said:
Hi so I've spent a good deal of the morning attempting to finally fix this phone, a couple years ago I removed all OS from it and no backup but I still have TWRP.
The phone is tampered/unlocked.
Hboot is 1.54.0000
I tried loading one of the latest ROMS from here via side loading - http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
I used this guide - http://htc-one.wonderhowto.com/how-to/fix-soft-bricked-htc-one-by-flashing-new-rom-via-adb-0154361/
Unfortunately once the sideload is complete I get an error E: Zio file is corrupt, I was wondering if anyone knows what I'm doing wrong? Can attempt to provide more information if required.
Click to expand...
Click to collapse
What recovery version do you have? Try flashing newest TWRP and give it a go

donkeykong1 said:
What recovery version do you have? Try flashing newest TWRP and give it a go
Click to expand...
Click to collapse
Hey thanks for the reply
This is the ROM I downloaded https://www.androidfilehost.com/?fid=95916177934554130
My recovery version is v2.6.0.1 for TWRP, should I upgrade?

You can't flash that via recovery. That's a RUU, and your phone must be in RUU mode and you flash it via recovery. Also, you're on very old firmware, so you need to flash all firmwares before that one. My suggestikn is to flash the latest recovery, and then flash a custom ROM. You can find custom ROMs on M7 android development thread

donkeykong1 said:
You can't flash that via recovery. That's a RUU, and your phone must be in RUU mode and you flash it via recovery. Also, you're on very old firmware, so you need to flash all firmwares before that one. My suggestikn is to flash the latest recovery, and then flash a custom ROM. You can find custom ROMs on M7 android development thread
Click to expand...
Click to collapse
Ah that would explain it lol, sadly very inexperienced with this.
Would there be a stock rom or just choose the one close to stock? (As in HTC sense one)

Purdy8TV said:
Ah that would explain it lol, sadly very inexperienced with this.
Would there be a stock rom or just choose the one close to stock? (As in HTC sense one)
Click to expand...
Click to collapse
I think there should be a stock rooted ROM, but you can flash pretty much any ROM from there. Most of them are stockish looking

donkeykong1 said:
I think there should be a stock rooted ROM, but you can flash pretty much any ROM from there. Most of them are stockish looking
Click to expand...
Click to collapse
Hey thanks very much for your speedy replies
Would this be okay then - http://forum.xda-developers.com/htc-one/development/rom-google-play-edition-lollipop-v1-00-t2963927 ?
Also do I just sideload it as I attempted previously once TWRP is updated?

Purdy8TV said:
Hey thanks very much for your speedy replies
Would this be okay then - http://forum.xda-developers.com/htc-one/development/rom-google-play-edition-lollipop-v1-00-t2963927 ?
Also do I just sideload it as I attempted previously once TWRP is updated?
Click to expand...
Click to collapse
Of all sense TOMs out there, you picked a GPE [emoji4] that's not Sense, but it will work.
New recoveries have MTP option, so you don't need sideload. Just mount MTP, and move your zip to your phone

donkeykong1 said:
Of all sense TOMs out there, you picked a GPE [emoji4] that's not Sense, but it will work.
New recoveries have MTP option, so you don't need sideload. Just mount MTP, and move your zip to your phone
Click to expand...
Click to collapse
Haha yeah, I did decide I actually preferred closer to stock android after using my Z3
I don't really know how to do that, will side loading still be okay? (I assumed this was my only option as I literally have no OS on my phone and just get stuck at the HTC loading screen when I turn phone on normally)

Purdy8TV said:
Haha yeah, I did decide I actually preferred closer to stock android after using my Z3
I don't really know how to do that, will side loading still be okay? (I assumed this was my only option as I literally have no OS on my phone and just get stuck at the HTC loading screen when I turn phone on normally)
Click to expand...
Click to collapse
MTP is much easier than sideload, and newer TWRP have it. You go into recovery (updated) and you will see "mount MTP" option. Click that, and your phone will show up on your PC. After that it's just drag and drop, but sideload will work too I think

donkeykong1 said:
MTP is much easier than sideload, and newer TWRP have it. You go into recovery (updated) and you will see "mount MTP" option. Click that, and your phone will show up on your PC. After that it's just drag and drop, but sideload will work too I think
Click to expand...
Click to collapse
Hmm
I can just see 'Mount' on the main TWRP page, then I go into that and see Cache/Data/devlog/System/USB OTG as check boxes and then just disable MTP button at the bottom.
Nothing showing on my macbook (not sure if that makes a difference as my w10 pc could not recognise the phone at all)

Purdy8TV said:
Hmm
I can just see 'Mount' on the main TWRP page, then I go into that and see Cache/Data/devlog/System/USB OTG as check boxes and then just disable MTP button at the bottom.
Nothing showing on my macbook (not sure if that makes a difference as my w10 pc could not recognise the phone at all)
Click to expand...
Click to collapse
Disable MTP is the one. Click it twice, and you're good to go

donkeykong1 said:
Disable MTP is the one. Click it twice, and you're good to go
Click to expand...
Click to collapse
Not showing up as a removable storage

Purdy8TV said:
Not showing up as a removable storage
Click to expand...
Click to collapse
Weird... Then go with sideload

donkeykong1 said:
Weird... Then go with sideload
Click to expand...
Click to collapse
Okay so I tried side loading, downloaded the google plus ROM from the link I posted, zipped it up and ended up getting this error.

Purdy8TV said:
Okay so I tried side loading, downloaded the google plus ROM from the link I posted, zipped it up and ended up getting this error.
Click to expand...
Click to collapse
That error means your adb tool is not working properly. At least that was the case on my PC. Can you try it on your windows machine?

donkeykong1 said:
That error means your adb tool is not working properly. At least that was the case on my PC. Can you try it on your windows machine?
Click to expand...
Click to collapse
Yeah I'll go give it another go on it.
It wouldn't be anything to do with the fact my device is tampered? (S Off I think?) Do I need something extra other than just the one link in the ROM I said i chose?

Purdy8TV said:
Yeah I'll go give it another go on it.
It wouldn't be anything to do with the fact my device is tampered? (S Off I think?) Do I need something extra other than just the one link in the ROM I said i chose?
Click to expand...
Click to collapse
You're s-off??? Go to your bootlader and confirm that please

donkeykong1 said:
You're s-off??? Go to your bootlader and confirm that please
Click to expand...
Click to collapse
Talking out my arse I'm S-ON lol, thought tampered meant S OFF lol, apologies

donkeykong1 said:
You're s-off??? Go to your bootlader and confirm that please
Click to expand...
Click to collapse
Okay so windows can detect the device it seems!
I see this, do I just delete the sideload.zip and then drag and drop the ROM I downloaded ?
{
"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"
}

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