Database Info

[Q] Proper way to upgrade to JB

Brief history of what I've done..I am very new at this, like starting today new.
I unlocked using the asus tool.
Then downgraded to ICS
Rooted using debugfs
Verified using rootchecker, successfully rooted
Installed ota rootkeeper and supersu (also tried once without supersu and just used superuser)
Backed up root using rootkeeper and temp. unrooted
...Now here is where I am not sure...
To upgrade to jelly bean, am i just supposed to download the newest firmware off the asus site, then use rootkeeper to restore root? Because that's what I did a few times, (with and without supersu as noted before)....and i cant restore root.
Or is there a special way to upgrade to jellybean or special firmware file i need to download...
I've heard someone mentioning dlpkgfile but i'm not sure what that is.
Thanks

There are generally two ways to upgrade to JB:
For locked devices, the only way (keeping root) is downgrade to ICS, root, use OTA rootkeeper, and then upgrade using dlpkgfile files. These files are incremental updates that are normally downloaded for OTA updates. Friendly community members have saved them from their /cache partition and uploaded them. Use the search function to find the thread. If you use the firmware download from the Asus site, it will rewrite your complete system partition, overwriting any su backup.
For an unlocked device, everything is much easier. You don't need to keep root, you can root any firmware version directly by first installing a custom recovery via fastboot from your PC, then you need a flashable superuser package (a zip file) and install it from this custom recovery.
Basic steps:
- Get a custom recovery in blob format. Most TF700 users use TWRP, it has a nice touch interface.
- Get the fastboot program for your PC from the Android SDK. For Windows, you also need some ("naked"?) drivers.
- Get a flashable superuser package in zip format and store it on your device.
- Start fastboot mode: turn tablet off, hold down volume-down while turning on, use volume-down to go to the USB icon, use volume-up to confirm. Then from your PC start: fastboot flash recovery yourcustomrecovery.blob
- To start the custom recovery: turn tablet off, hold down volume-down while turning on,use volume-up to start RCK.
- From TWRP, tap "Install", select your flashable superuser zip and confirm.
- Congratulations, you are rooted.

_that said:
There are generally two ways to upgrade to JB:
For locked devices, the only way (keeping root) is downgrade to ICS, root, use OTA rootkeeper, and then upgrade using dlpkgfile files. These files are incremental updates that are normally downloaded for OTA updates. Friendly community members have saved them from their /cache partition and uploaded them. Use the search function to find the thread. If you use the firmware download from the Asus site, it will rewrite your complete system partition, overwriting any su backup.
For an unlocked device, everything is much easier. You don't need to keep root, you can root any firmware version directly by first installing a custom recovery via fastboot from your PC, then you need a flashable superuser package (a zip file) and install it from this custom recovery.
Basic steps:
- Get a custom recovery in blob format. Most TF700 users use TWRP, it has a nice touch interface.
- Get the fastboot program for your PC from the Android SDK. For Windows, you also need some ("naked"?) drivers.
- Get a flashable superuser package in zip format and store it on your device.
- Start fastboot mode: turn tablet off, hold down volume-down while turning on, use volume-down to go to the USB icon, use volume-up to confirm. Then from your PC start: fastboot flash recovery yourcustomrecovery.blob
- To start the custom recovery: turn tablet off, hold down volume-down while turning on,use volume-up to start RCK.
- From TWRP, tap "Install", select your flashable superuser zip and confirm.
- Congratulations, you are rooted.
Click to expand...
Click to collapse
So if I am getting this correctly, I could have just stayed on the latest official JB update from asus, unlocked like I did, and then followed the above steps, instead of downgrading, etc. ?
Thanks for the reply also

mdelongpre said:
So if I am getting this correctly, I could have just stayed on the latest official JB update from asus, unlocked like I did, and then followed the above steps, instead of downgrading, etc. ?
Click to expand...
Click to collapse
Correct.

_that said:
Correct.
Click to expand...
Click to collapse
just wanted to update this real quick...
I installed the latest JB firmware and followed this guide... http://forum.xda-developers.com/showthread.php?t=1938129
now I have JB, root, and can flash custom roms with TWRP
So thank you and good luck to others trying this, PM me because I might have been in the same situation for some of you newbies like me attempting this

mdelongpre said:
I installed the latest JB firmware and followed this guide... http://forum.xda-developers.com/showthread.php?t=1938129
now I have JB, root, and can flash custom roms with TWRP
Click to expand...
Click to collapse
Great that you made it!
Please check that your TWRP version is 2.3 or later (the guide is old and recommends an older version) - otherwise you might run into problems (brick) when you choose "wipe data" in the bootloader menu.

[Q] Z3 dual D6633 problem with update OTA !!!!! (could not verify)

I have xperia Z3 dual D6633 with build number 23.0.F.1.82 and rooted it with giefroot_v3 then installed Z3-lockeddualrecovery2.8.2 without unlock bootloader my bootloader still locked.
I want to update the system via ota update center to version 23.0.1.F.0.96 after finish download it give me this message (could not verify). I tried a lot of times and tried factory rest same problem (could not verify) why??
I want update system without loosing root and recovery and without flash it via flashtool I want just update it via Ota to the newer system 23.0.1.F.0.96 with size(134.7 MB only)..... :crying:
thank you for all...

Google PRFCreator and create your own prerooted flashable zip for the latest firmware.
It will contain recovery as well.

gregbradley said:
Google PRFCreator and create your own prerooted flashable zip for the latest firmware.
It will contain recovery as well.
Click to expand...
Click to collapse
this means I can not update it via wifi only flash zip with the latest my own prerooted frimware?

borhan0089 said:
this means I can not update it via wifi only flash zip with the latest my own prerooted frimware?
Click to expand...
Click to collapse
Well if you definitely want to keep root I suggest doing it that way. It takes about 7 minutes to create the flashable zip (All automated, it is very easy) and about 30 seconds to flash it....

gregbradley said:
Well if you definitely want to keep root I suggest doing it that way. It takes about 7 minutes to create the flashable zip (All automated, it is very easy) and about 30 seconds to flash it....
Click to expand...
Click to collapse
I will try thank you friend..

ROOT [n910C] Samsung Galaxy Note 4 Andoid 5.1.1 with Same Bootloader (5.1.1)

Hi Everyone, This is my first post. I am not a developer. Hope this will help you to Root your Note 4 N910C on 5.1.1, if you have any suggestions for me, you're most welcome
Note: I am not responsible for any damage of your phone, kindly read the steps carefully and follow one by one. I have done this with my Galaxy Note 4 N910C on Andoid 5.1.1. Its 100% working.​I have read many thread and websites, I only find Root Note 4 N910C with 5.0.1 bootloader, there was no any option without 5.0.1 bootloader one.
So, with this method you can stay with 5.1.1 Bootloader and can Root your phone. So, here is method I am going to explain you.
First Make sure that your phone's battery is charged above 60%
STEP-1
You need these Files to Root Your Note 4 N910C with Bootloader 5.1.1
Odin3_v3.10.7
SpaceX Kernel
TWRP Recovery
SuperSU
STEP-2
Connect your phone with your computer, You must have installed Samsung USB Drivers in your computer (if you don't have drivers, you can download Samsung USB Drivers Click here)
STEP-3
Copy SpaceX Kernel and SuperSU files in SD Card - Note: I have done this with SpaceX Kernel, if you want to use GoogyMax Kernel or any other Cutom Kernel you can try it. However, I highly recommend SpaceX Kernel.
STEP-4
Disconnect your phone and Switch off then put it into Download Mode (Press HOME+POWER+VOLUME DOWN) Buttons at same time until logo (GALAXY NOTE 4 Powered by Android LOGO) appears.
STEP-5
Open Odin3_v3.10.7 file in your computer (I will recommend open the file as an Administrator - right click on the file.)
STEP-6
Connect your phone with Computer - After Connecting, you will see in the first box [Blue Color] COM:6 or 8 or any other number.
---> if you will not see this please reinstall the Samsung USB Drivers and restart your computer and reconnect your phone.
STEP-6
Click on AP and select TWRP Recovery File from your computer, you have downloaded
Before Click on the Start, please make sure that your phone should not restart. Because it may orverwrite the stock recovery
You Can Do this:
When you see PASS on the window REMOVE The Battery or Press VOLUME UP+POWER+HOME buttons, it will show you the TWRP Recovery page
STEP-7
If you want your can Backup your Stock Kernel, if you want to update your Stock RoM, or install updates in future.
here are the steps:
1. select backup in TWRP Recovery
2. check Boot and uncheck all other options
3. swipe the backup option - and it will save in your internal storage - or you can also choose external storage option, its there
STEP-8
1. Now Install SpaceX Kernel - Click on the install and find SpaceX Kernel and install
2. Go Back and again Install SuperSU
STEP-9
Restart your phone
Your are Done Now!
If you want to check if you phone has been rooted or not,
1. Open SuperSU app in your phone go to setting -> Access (default) -> make it Grant.
2. Download Root Checker from Play Store and check if your ROM is Rooted.
Thank you!
I am new, please let me know if you have any suggests/advise for me.

Thanks, followed instructions to the letter and it's working for me

kazim said:
Thanks, followed instructions to the letter and it's working for me
Click to expand...
Click to collapse
You are welcome!

Titanium backup failed to find root access

Works!
Thanks man! followed the instructions to the letter, works great![

whats the difference between this version or flashing 5.0.1, rooting and flashing 5.1.1 bootloader afterwards?
like this
You can download the bootloader ► here or ► here and flash it via Odin adding the file in the "BL" box.
from here?
http://electron-team.com/dn5_note4_n910c.html

Thanks mate...It really made wonders for me!!!
Saved my time from going to Service station! By mitake I used CF-root method to root phone on my stock 5.1.1. rom and got infinite bootloop.
By using your method, my phone got rebirth.
Thanks again.

niceashwin79 said:
Thanks mate...It really made wonders for me!!!
Saved my time from going to Service station! By mitake I used CF-root method to root phone on my stock 5.1.1. rom and got infinite bootloop.
By using your method, my phone got rebirth.
Thanks again.
Click to expand...
Click to collapse
you can rebirth it also by flashing 5.1.1 fro scratch from sammobile...

annus9214 said:
Titanium backup failed to find root access
Click to expand...
Click to collapse
you may need busybox, install it from playstore

I want to install a ROM on my Z3

My Sony Xperia Z3 d6633 is fully stock and is updated to the latest android i never rooted it or did anything to the phone but now i want to install existenz marshmallow rom what should i do to install it?

If you don't want aosp roms, just root it and install recovery so you can flash stock based roms.
There is thread in General section for just rooting and install recovery.

OmarElAdawy007 said:
My Sony Xperia Z3 d6633 is fully stock and is updated to the latest android i never rooted it or did anything to the phone but now i want to install existenz marshmallow rom what should i do to install it?
Click to expand...
Click to collapse
hi,
assuming that you're using windows,
follow this guide ( use this fw)
TRY A FEW TIMES IF IT FAILS.
Now you have gained root access without losing your drm keys and your bootloader it's still locked.
Now you have to install the recovery
just download the zip archive and extract it to a folder and run install.bat.
now download the eXistenZ Marshmallow... or whatever you want.
do a factory reset (wipe and factory reset) and install your zip (install and browse to yours zip location).
reboot and ENJOY :good:

Alex261099 said:
hi,
assuming that you're using windows,
follow this guide ( use this fw)
TRY A FEW TIMES IF IT FAILS.
Now you have gained root access without losing your drm keys and your bootloader it's still locked.
Now you have to install the recovery
just download the zip archive and extract it to a folder and run install.bat.
now download the eXistenZ Marshmallow... or whatever you want.
do a factory reset (wipe and factory reset) and install your zip (install and browse to yours zip location).
reboot and ENJOY :good:
Click to expand...
Click to collapse
Thank you so much you helped me a lot ?

OmarElAdawy007 said:
Thank you so much you helped me a lot
Click to expand...
Click to collapse
no problem

[GUIDE] Root, Bootloader Unlocks, and More!

Greetings from the AT&T S5 Forum!
We've recently discovered the usability of engineering firmwares in our journey to get root, as outlined here: https://forum.xda-developers.com/att-galaxy-s5/general/guide-merry-christmas-heres-t3516196
Now, I'm here to try to bring this same method to you guys! With the help of @jrkruse, here are the root instructions:
How it works:
These engineering firmwares are usually based on KitKat, and have their SELinux set to PERMISSIVE. This not only leaves the firmware very vulnerable to towelroot, but it also keeps SELinux from raining on our parade.
Thanks again to @jrkruse for the updated root instructions, and @mohammad.afaneh for the Safestrap!
Revised October 6, 2018.
Directions:
Before you get going, use this APK to check your eMMC chip's CID:
eMMC_CID_Checker_.apk[/SIZE][/B][/CENTER]
Your CID Number will be the first two numbers in the eMMC Box under "CID"
If the first two digits are "15," your bootloader is unlockable and you can install TWRP/AOSP ROMs.
If the first two digits are "11," your bootloader is not unlockable, but you can use rooted Lollipop ROMs that are based on TouchWiz (with the help of SafeStrap). You can also use non-rooted Marshmallow ROMs (based on TouchWiz) and flash mods with SafeStrap.
BACK UP YOUR STUFF NOW, YOUR STORAGE WILL BE WIPED!​
If your eMMC CID starts with "15," start here:
1. Download and unzip this file: EMMC_15_Root_Bootloader_Unlock S5_QB2_PB1.zip
2. Reboot the phone to Download Mode (Pwr +Vol Dwn+Home)
3. Use Odin 3.12 and load the "COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5" firmware in the AP Slot
4. Flash and let the phone process the file. It will reboot twice and you should be dropped into Android within a minute and a half.
5. Copy the following files to your phone:
"RootS5" Folder and "EMMC_15_SafeStrap_QA1_6_0_1_MM_Bootloader_Unlock_AIO.zip",
and EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip
6. Use the File Manager (you can find it in the app drawer) to install Superuser.apk, Busybox.apk, tr_v2.apk, and SafeStrapKK.apk . Do not open anything yet.
7. Open towelroot and click "MAKE IT RAIN". It should tell you you have succeeded. Otherwise, reboot and try again.
8. Now open SuperSU and click "New User" to install it.
Once done, open SuperSU and update the SU binaries using the "NORMAL" method. It will tell you you need to reboot, but you can skip that. (If the Superuser install hangs for more than 5 minutes reboot phone and try to install it again.)
9. Now open the BusyBox app, grant SuperSU access and install BusyBox.
10. Now open SafeStrap, grant SuperSu access and click "install recovery". If the SafeStrap recovery fails to install, make sure BusyBox is installed by rerunning the BusyBox app (it will tell you if BusyBox is installed). If its not installed, click "install" again, reboot the phone, re-open SafeStrap and try to install recovery again
11. Once SafeStrap Recovery is installed click "reboot to SafeStrap Recovery".
12. Once in SafeStrap Recovery choose install and select EMMC_15_SafeStrap_QB2_6_0_1_MM_Bootloader_Unlock_AIO.zip
13. Install the zip. The phone will power off. Reboot the phone to TWRP Recovery with Pwr+VolUp+Home
14. You will now have an Unlocked Bootloader and TWRP recovery Installed. Now whoose Wipe > Advanced Wipe. Select Dalvik Cache; Data; System; Cache, and swipe the swipe to wipe bar. When done, click the back button, click Install, and choose:
EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip
You're done! You will have stock rooted Marshmallow QB2 Build installed with an unlocked bootloader and custom recovery.
If your eMMC CID starts with "11," start here:
1. Download and unzip this file: EMMC_11_ Root S5_QB2_PB1.zip
2. Reboot Phone to Download Mode (Pwr +Vol Dwn+Home)
3. Use Odin 3.12 and load the COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5 in the AP Slot.
4. Flash and let the phone reboot. It will reboot to recovery and finish install then it will reboot and take about 20 seconds to boot.
5. Copy the following to the phone:
Root S5 Folder, EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip, EMMC_11_QA1_6_0_1_MM_Firmware_Bootloaders.zip, and the TouchWiz ROM you want to install.
6. Use the File Manager (you can find it in the app drawer) to install Superuser.apk, Busybox.apk, tr_v2.apk, and SafeStrapKK.apk . Do not open anything yet.
7. Open towelroot and click "MAKE IT RAIN". It should tell you you have succeeded. Otherwise, reboot and try again.
8. Now open SuperSU and click "New User" to install it.
Once done, open SuperSU and update the SU binaries using the "NORMAL" method. It will tell you you need to reboot, but you can skip that. (If the Superuser install hangs for more than 5 minutes reboot phone and try to install it again.)
9. Now open the BusyBox app, grant SuperSU access and install BusyBox.
10. Now open SafeStrap, grant SuperSu access and click "install recovery". If the SafeStrap recovery fails to install, make sure BusyBox is installed by rerunning the BusyBox app (it will tell you if BusyBox is installed). If its not installed, click "install" again, reboot the phone, re-open SafeStrap and try to install recovery again
11. Once SafeStrap Recovery is installed click "reboot to SafeStrap Recovery".
12. Once in SafeStrap Recovery, choose what firmware you want to be on:
Lollipop 5.0 Firmware=EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip
Marsmhallow 6.0 Firmware=EMMC_11_QA1_6_0_1_MM_Firmware_Bootloaders.zip
13. Install the firmware zip, and then flash a TouchWiz Lollipop ROM. (Here is the latest stock rooted Lollipop Rom: VZW_BPB1_ODEX_DEODEX_V9.zip). You may want to download a copy of the latest SuperSu zip, and flash if installing a Lollipop ROM that is not rooted. Remember that you cannot root Marshmallow ROMs, so do not try and flash the SuperSu zip on a Marshmallow Rom (you will softbrick if you do).
14. After you install any Lollipop ROM, you may need to reinstall SafeStrap Recovery. Most of the time you don't have to and SafeStrap can be reached by flashing the KitKat Kernel in Download Mode with ODIN. But, in some cases, when flashing a ROM that flashes a system.img instead of a system folder, you may lose SafeStrap during install. This will be the case if you install the above ROM. You can reinstall it after the ROM is booted up. A Safestrap-G900V-4.04_LL_MM.apk is included that will flash a version of SafeStrap that will allow you to reboot to SafeStrap Recovery without flashing a KitKat kernel in Odin. Install BusyBox again from the BusyBox App in the RootS5 Folder. Install Safestrap-G900V-4.04_LL_MM.apk and make sure to grant SuperSU access. It may take a few seconds to prompt. If SafeStrap is not installed, click "Install Recovery". If Safestrap is still installed click on "Uninstall Recovery", close the app, and reopen it. It should say recovery is not installed. Now click on "Install Recovery". If this doesn't work, reboot the phone and try again. Once installed, you can just click reboot to SafeStrap from the SafeStrap app and you will reboot straight to SafeStrap. Remember to flash the appropriate Kernel when leaving SafeStrap!
Download and place these on your device:
LL_KERNEL_SS-FF_Flashable.zip, and
MM_KERNEL_SS-FF_Flashable.zip
If something goes wrong you can usually get back to SafeStrap by simply rebooting the phone to Download Mode and flashing NI2_stock_kernel.tar.md5. When the phone reboots, watch for the SafeStrap splash screen and enter SafeStrap.
WARNING: Do NOT change ANY boot options in SafeStrap. ROM slots cannot be used, so you must flash to the Stock ROM slot EVERY TIME OR YOU WILL SOFTBRICK. Some functions don't work in SafeStrap, like choosing an image file to flash directly. All image files must be flashed via zip file.
For CID11 users that have followed the above instructions and want to use Marshmallow:
QA1_MM_Firmware_With_QA1_Bootloader_CAUTION.zip=Marshmallow Firmware (use if flashing a MM TW ROM other than the one posted below). Just remember there is no root for Marshmallow ROMs, but having SafeStrap installed gives you the ability to do things like flash debloat Scripts, Mods, etc and the ability to go back to a rooted Lollipop ROM without going through the root process all over again. Simply flash the Lollipop ROM and EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip.
Here is a special ROM that includes SafeStrap, so you can flash a Marshmallow ROM and still be able to use SafeStrap to flash things. You will not have root but you can still access SafeStrap. VZW_QB2_STOCK_SAFESTRAP_ONLY_V1.zip More Instructions about this can be found HERE
When using a MM ROM, it is necessary to flash the KitKat Kernel with Odin to enter SafeStrap. When leaving SafeStrap, make sure to flash MM_KERNEL_SS-FF_Flashable.zip which is necessary to leave SafeStrap (This zip will be placed on storage automatically with the above ROM and you also download it in instructions above.) Just navigate to the .MM_KERNEL_SS-FF folder located on both Internal and External storage.

i'll odin my spare s5 to stock later if i get the chance and let you know if this works on my g900v.

The methods in post 1 are seriously outdated the easiest method to obtain unlocks or update or downgrade unlocked bootloaders can be found below they were updated December of 2021​
EMMC 15 Unlocking Bootloader
2022_VZW_EMMC_15_ AIO_Tool To Unlock_Bootloader+Install_TWRP And MM_QL1_Rooted_Rom Works On Any Version Bootloaders_MM_LL_KK-Reactivation Lock Remover
This Process Will Root Phone Unlock Your VZW EMMC 15 Chipset Bootloader Install TWRP Recobery And Imstall Latest QL1 Stock Rom . Downloads S5_Root_Tools_2023.7z EMMC_15_Rom.zip -- Stock QL1 6.0 Directions For Unlocking Stock Phone I would...
forum.xda-developers.com
EMMC 15 Updating Unlocked Bootloaders Or Downgrading
2022_VZW_EMMC_15_Chipset For Unlocked Dev BL To Downgrade To LL_KK Or Upgrade To MM_And Keep Unlock Bootloader
This Process Will Update Or Downgrade Your VZW EMMC Chipset DEV Aboot Bootloader Unlocked S5 To Marshmallow 6.0 Lollipop 5.0 Or Kitkat 4.2 or 4.4 Root And Unlock Instructions Can Be Found Here EMMC 15 Rooting And Bootloader Unlocking EMMC 11...
forum.xda-developers.com
For Rooting EMMC 11 Phones
2021_VZW_Locked_Bootloader_EMMC_11_Rooted/NonRooted_Roms_With_Safestrap_MM_LL_KK
This Process Will Install On The EMMC_11 Locked Bootloader Verizon S5 Marshmallow QL1 Stock Rom NonRooted With Safestrap. Lollipop PB1 Stock Rom Rooted With Safestrap. KK Rom Rooted With Safestrap What This Does This gives you the ability to...
forum.xda-developers.com

I cant seem to get the link for locked bootloaders to work... But does this mean that CID 11 people will finally have unlocked bootloaders and can install Lineage OS? may seem like a dumb question...

its uploading sorry it failed at 99 percent

jrkruse said:
its uploading sorry it failed at 99 percent
Click to expand...
Click to collapse
Thank you! very much appreciated

jacob0298 said:
I cant seem to get the link for locked bootloaders to work... But does this mean that CID 11 people will finally have unlocked bootloaders and can install Lineage OS? may seem like a dumb question...
Click to expand...
Click to collapse
Its uploaded

jrkruse said:
Its uploaded
Click to expand...
Click to collapse
Downloading as we speak. I will let you know how everything goes!

tested on one of the spares I had kicking around
does what it says on the tin
!kickass

The apps are kind of hard to see in the App Drawer I installed View attachment Apex_Lancher.apk and it gets rid of that Info screen covering the Apps

The OP has been updated to reflect @jrkruse 's new instructions

AptLogic said:
The OP has been updated to reflect @jrkruse 's new instructions
Click to expand...
Click to collapse
I just cleaned them up a little I'll Pm you the changes
---------- Post added at 08:22 PM ---------- Previous post was at 07:32 PM ----------
jacob0298 said:
I cant seem to get the link for locked bootloaders to work... But does this mean that CID 11 people will finally have unlocked bootloaders and can install Lineage OS? may seem like a dumb question...
Click to expand...
Click to collapse
This does not unlock bootloaders for CID11 people. There will probably never be a bootloader unlock for those people unless the Verizon S5 gets one from Samsung as it grows old and irrelevant.

jrkruse said:
This does not unlock bootloaders for CID11 people. There will probably never be a bootloader unlock for those people unless the Verizon S5 gets one from Samsung as it grows old and irrelevant.
Click to expand...
Click to collapse
Which, I should add, has about a 1 in 10,000,000 chance of occurring.

I was able to successfully flash COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5 in the AP Slot
After it rebooted to system , I am unable to get the phone to be recognized by windows. When I plug it in I hear the beep that it's plugged in charging, but I cannot find an option for file transfer on the phone itself. I tried a couple different Samsung drivers on Windows but to no avail. Does anyone know why this is happening or how I can get it to connect to the pc?
This was one of the drivers I used: (one linked in original thread)
http://org.downloadcenter.samsung.c...NG_USB_Driver_for_Mobile_Phones_v1.5.45.0.exe

guitar1238751 said:
I was able to successfully flash COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5 in the AP Slot
After it rebooted to system , I am unable to get the phone to be recognized by windows. When I plug it in I hear the beep that it's plugged in charging, but I cannot find an option for file transfer on the phone itself. I tried a couple different Samsung drivers on Windows but to no avail. Does anyone know why this is happening or how I can get it to connect to the pc?
This was one of the drivers I used:
Click to expand...
Click to collapse
Try rebooting the phone and the PC. I've had that happen before and usually that fixes the problem.

AptLogic said:
Try rebooting the phone and the PC. I've had that happen before and usually that fixes the problem.
Click to expand...
Click to collapse
Yup I've tried that a few times. I even went back to download mode, redid the process and booted back to system, still couldn't get it to connect.

guitar1238751 said:
Yup I've tried that a few times. I even went back to download mode, redid the process and booted back to system, still couldn't get it to connect.
Click to expand...
Click to collapse
That's peculiar... Have you tried another cord? Otherwise you'll have no choice but to take out the SD card and plug it into the PC manually.

AptLogic said:
That's peculiar... Have you tried another cord? Otherwise you'll have no choice but to take out the SD card and plug it into the PC manually.
Click to expand...
Click to collapse
I'll try it again with another cable and laptop. If it still doesn't work I'll copy it directly to the SD card. This is my friend's phone. I'm in class now so when I see him later I'll continue the steps and let you know what happens. Thanks

guitar1238751 said:
I'll try it again with another cable and laptop. If it still doesn't work I'll copy it directly to the SD card. This is my friend's phone. I'm in class now so when I see him later I'll continue the steps and let you know what happens. Thanks
Click to expand...
Click to collapse
Happy to help

["QUOTE=AptLogic;71212479]Happy to help [/QUOTE]