Database Users

[Q] Botched flashing from 4.3 to twrp to aryamod 6 to BOE4

After more than a year with my 4.3 Note 3. I decided to flash a custom ROM. Namely Aryamod 6. (first attachment was the stock 4.3 I started with). I knew that I needed to backup my data so I decided to flash a custom recovery so I went about it by getting Rom Manager to flash CWM which eventually would allow me to flash TWRP. I eventually used the dd install method to install TWRP but that didn't work so I used odin to flash it. This caused my Note to freeze up a few minutes after booting with a black screen and the status bar just showing.
I decided to go through with flashing Aryamod v6 to get a fresh start. I flshed the BL and CP files which then caused my Note to go into a boot loop where I can't even boot to recovery. I was told to update to a 5.0 rom and I used the base rom of Aryamod v6 which is the BOE4 rom. Now when I try to flash the BOE4 rom I get the volume size is too big and invalid ext4 image.
Also sometime during the first bootloop I accidentally ticked Nand EraseAll but as far as I could see it did nothing.
Anyway, right now it is very difficult to download another ROM because of horrible Philippine isps and my Note is also my daily driver so I need to get it back into working order ASAP. These are the files I have:
ODIN 3.09
N9005XXUGBOEA_N9005OJVGBOE4_KSA - The Base ROM of Aryamod v6 a 5.0 rom
N9005XXUGBOEA_AryaModV6.0_Public - Aryamod v6
CP_N9005XXUGBOD3.tar.md5 - part of the aryamod instructions and I believe the modem of 5.0
BL_N9005XXUGBOEA.tar.md5 - part of the aryamod instructions and I think the bootloader?
twrp-2.8.7.0-hlte-4.3.img. zip- The twrp version I flashed when I was on 4.3
hlte-recovery.img.zip - I flashed this to get out of the recovery loop when I dd installed Twrp.
PIT-File-DBT+VFG-UK-MSM8974 - A PIT file.
SM-N9005_32GB.pit - another pit file. Flashing this got me into stock recovery.
N9005ZHUBMI7_N9005ZZHBMI7_N9005XXUBMI5_HOME.tar.md5 - I don't remember where I got this. Haven't flashed this but it might be a backup of my 4.3 rom
A few questions.
Can I fix my phone with these files?
When Flashing the BOE4, I just put it on PDA/AP? but in this thread http://forum.xda-developers.com/galaxy-note-3/general/guide-t2983873, he seems to be putting it on everything.
I really need your help on these

I have no idea about that file you have, whether it will work or not, but the only thing I can say is, the Polish ROM is the Lollipop ROM which works on most devices, so you might wanna give it a try.
I don't live in a place with even decent ISPs, but I can download a ROM in less than two hours, so if your condition is not worse then you will have to download a ROM rather than depending on what you have.

[Q&A] Safestrap Without Odin+Safestrap Flashable Firmwares

Q&A for Safestrap Without Odin+Safestrap Flashable Firmwares
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Safestrap Without Odin+Safestrap Flashable Firmwares. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

jrkruse said:
Rooting Tools For Lollipop​Edit: I reuploaded the Rooting_Tools_For_S5_Lollipop.zip as the md5 was not right if your md5 is not b3dc378a34c0551efe4925912bfa1a9c please redownload and delete the .1Stock_Firmware_Zip from your internal and external sd card and reflash zip
Here is every thing you need to use safestrap without odin. This zip will install the files need if you have to return to KitKat NCG to obtain root. It will also install the firmwares that can be flashed in safestrap so you will not need to use odin. This zip will also install Lollipop SafeStrap Recovery which will allow you to use safestrap without having to use odin to flash kernels and firmwares. I recommend using safestrap to flash for the simple fact if something goes wrong you can still have a chance of booting back to safestrap to reflash something as where using Flashfire if something fails there is a good chance you will have to odin back and start all over. For you who prefer Flashfire I still recommend installing safestrap just as a backup just incase flashfire fails. This zip will also install the Flashfire app
Rooting_Tools_For_S5_Lollipop.zip
Instructions for rooting Verizon S5 on Kitkat Or Lollipop Roms Or If your Already Rooted On A KitKat Rom (If you took the OE1 OTA Update there is currently no root method available)
If already running a rooted kitkat rom with safestrap proceed to step 4
1. Download Odin_3.10.6.zip and install on computer
2. Download NCG_Rescue_Tar_And_NCG_For_Root.tar.zip and extract the zip into the odin folder
3. Download lates USB drivers for computer Found HERE and install to computer
4. Download these 3 zips and extract them and copy the folders containing the zips to your sdcard. They are not flashable because you but the zips inside the folders are flashable and are needed in safestrap later on. If your already rooted skip to step 19 after you extract these zips to your sdcard
Stock_Firmware_Zip.zip
Stock_Kernel_Zip.zip
RootS5.zip
5. Copy anything you don't want to get deleted to your external sd card as this process is going to wipe internal storage
6. Reboot Phone to Download mode by holding the power button+volume down button+home button all at the same time.
7. Open Odin on your computer
8. Plug Phone into computer.
9 Press Volume up button on Phone (if you havent already done so) and let odin find your phone. The ID:COM box will turn blue when its ready
View attachment 3411569
10. Click the AP Box in odin and locate the NCG_Rescue_Tar_And_NCG_For_Root.tar.md5 file (which you should have extracted in the odin folder) click on the file and let odin load it. It may take several minutes to load
View attachment 3411570
11. Once it has passed MD5 check the AP box will populate the file
View attachment 3411571
12. Click Start and wait for it to finish will take around 5 to 10 minutes to flash
13. When phone is finally booted up just skip through the setup wizard there is no need to add any accounts as the files you will need you already added to your phone sd card
14. Use the file manager and open the RootS5 folder on your Sd card and install
tr_v3.apk
Superuser.apk
BusyBox.apk
Safestrap-G900V-3.75-KitKat.apk
15. Once all are installed open Towel Root and click Make it rain box then open SuperUser and when it ask to update binary click update normally, then it will ask to disable knox click yes. This may hang if so reboot then open SuperUser again it will again ask to disable knox click yes and then it successfully disable knox.
16. Open BusyBox and grant SuperUser root request. Then click install
17. Open safestrap grant super user root request then install safestrap. Once installed click reboot to recovery inside the safestrap app. If it fails to reboot to recovery install safestrap again and then click the reboot to recovery button it should work this time
18. Now make sure you have the Stock_Firmware_Zip folder and the Stock_Kernel_Zip folder on your sd card both folders should contain 3 flashable zips files
19. Copy Rom to sd card
20. Reboot to safestrap flash rom once rom is flashed navigated to the Stock_Firmware_Zip folder and flash the firmware that matches your rom that you flashed and click reboot
Instruction to Use SafeStrap Without odin If Already on rooted lollipop rom
1. Flash Rooting_Tools_For_S5_Lollipop.zip
2. Open Lollipop SafeStrap Recovery
3. Click Install SafeStrap. It will open Safestrap App wait for the SuperUser Request and grant permission(This may take a few seconds be patient) once you grant permission you may have to go back and reopen the app. Then install SafeStrap. wait for safestrap to install then click install safestrap again(Sometimes on BOD5 firmware it takes 2 times to stick this is why I say do it twice)
4. Open Lollipop SafeStrap Recovery
5. Click on Recovery Reboot
6. Click The Flash Button Grant SuperSu Root Access
7. Click the Reboot To SafeStrap Box
8. Phone will Reboot to SafeStrap. (If for some chance it doesnt boot to safestrap you will need to use odin and manually flash one of the lollipop kernels below. Then once rom is rebooted install safestrap again and problem should be fixed)
9. To return to rom from Safestrap you will need to flash the the stock kernel matching your rom or if your flashing Firmware then just flash that zip there is no need to flash kernel if you flashed a firmware zip. The Firmwares only need to be flashed if the rom you flashed is a different firmware otherwise just flash the kernel. The Firmwares will be located on internal and external SD cards in a file called 1Stock_Firmware_Zip folder and the Kernels will be in 1Stock_Kernel_Zip folder They should be at the top of the list of folders
10. If a problem happens when flashing a rom and you bootloop you will then need to use odin to flash the NI2 Kernel then you can get back to Safestrap
Odin Flashable Tars if you need them
NCG_Rescue_Tar_And_NCG_For_Root.tar.zip
NI2_stock_kernel.tar.md5
VZW_BOC4_RETAIL_FIRMWARE_ONLY.tar.md5
VZW_BOC4_RETAIL_KERNEL_ONLY.tar.md5
VZW_BOD5_RETAIL_FIRMWARE_ONLY.tar.md5
VZW_BOD5_RETAIL_KERNEL_ONLY.tar.md5
VZW_BOE1_RETAIL_KERNEL_ONLY.tar.md5
Thanks
@Hashcode for safestrap
@benwaffle for the Kernel flashing tool
@klabit87 for making this for verizon
@chetqwerty for the OE1 update.zip which I got the kernel and modem from
Click to expand...
Click to collapse
Hello Im trying to unbrick my phone using NCG rescue zip. It wont pass cahce and will FAIL AUTH. Im using Odin I have a verizon GS5. Any ideas? Anyway I can disable secure download?
It says on my phone: (ODIN MODE)
UDC START
SYS REV CHECK FAIL (s): REFER 2 > BINARY 1
SECURE CHECK FAIL: CAHCE
THanks

j0mz said:
Hello Im trying to unbrick my phone using NCG rescue zip. It wont pass cahce and will FAIL AUTH. Im using Odin I have a verizon GS5. Any ideas? Anyway I can disable secure download?
It says on my phone: (ODIN MODE)
UDC START
SYS REV CHECK FAIL (s): REFER 2 > BINARY 1
SECURE CHECK FAIL: CAHCE
THanks
Click to expand...
Click to collapse
Did you unzip and load the md5 tar in odin? Are you on BOE1 firmware if so you can not flash older firmwares.

Yes, I just did this two or three days ago from stock oc4 in order to install AllianceROM. Follow the instruction in the first spoiler and it works like a breeze. All you need is an internet connection for towelroot.
Edit: I was trying to reply to a post in discussion but it won't quote the post, and I have too few posts to reply there

long time lurker, first time poster. All boils down, nothing works, especially with locked bootloader.
I stupidly took OG5 OTA update, now I lost my root and that also locked my unlocked bootloader! I had tried everything that I could find on this form and google, NOTHING. I even ran Linux on VM and created custom ROM to work with OG5, nada. It didn't work.
I ODIN'd my phone back to the OG5 OTA update.
Until someone finds the way, I am stuck with extremely bloated stock which I hate so much.

@jrkruse, I'm a little unclear on something here. Maybe I'm just dense, just ask my wife.?
I'm currently on rooted stock NK2, with SafeStrap, and if I understand correctly I need to flash the OG5 room, and the OG5 kernel. Since I'm already rooted, I don't need to run the RootTools zip, correct? Also, what about the bootloader? Did I miss something somewhere?

Cappricorn said:
@jrkruse, I'm a little unclear on something here. Maybe I'm just dense, just ask my wife.
I'm currently on rooted stock NK2, with SafeStrap, and if I understand correctly I need to flash the OG5 room, and the OG5 kernel. Since I'm already rooted, I don't need to run the RootTools zip, correct? Also, what about the bootloader? Did I miss something somewhere?
Click to expand...
Click to collapse
Flash OG5 rom then OG5 firmware zip no need to flash kernel if flashing firmware zip

Got it. Thank you! ?

trying to root Note 4 5.1.1 on 910W8

Hey guys i followed this youtube guide for rooting 5.1.1 using TWRP Method https://www.youtube.com/watch?v=qpsGX_Xoxcg
i downloaded all the files but the firmware (not listen i have n910W8 = telus)
I have odin, supersu, TWRP (which n910w8 is listed) and samsung drivers.
I moved superSU and the TWRP file to root directory of note 4 5.1.1. rebooted into download mode, saw the blue indicator on odin and loaded the file. Rebooted holding volume up this time and tried to load the kernal but it doesnt exist.
I think im confused the TWRP file is NOT the kernal? Where can I get a kernal for n910W8 (telus)
thanks in advance!!

So I found this
http://www.sammobile.com/firmwares/download/56498/N910W8VLU1COI4_N910W8OYA1COI4_TLS/
which is telus 5.1.1 Rom. ill move this to my root directory and load the 910W8 TWRP file in odin and flash? Ill give it a try now wish me luck lol

ok i followed a guide online and now my phone just keeps restarting. I think im in big trouble. Im able to load openrecovery-twrp-2.8.1.0-trltecan.img into odin and boot to TWRP but now i cant load kernels? looked so easy to do now im down a phone? any help is much appreciated thanks!!!

You need to odin (bell, rogers, telus) 5.1.1 then odin TWRP then twrp a custom kernel. Our 5.1.1 needs a custom kernel in order to work rooted. Or.....you can load a custom 5.1.1 rooted rom that is W8 compatible or any Tmobile rom such as Tekxodus which i am running.

ok so i loaded openrecovery-twrp-2.8.1.0-trltecan.img in AP (for my device) copied the custom rom
" cm-12.1-20150423-NIGHTLY-trltetmo" which was suppose to work with my 910w8 (910T) used recovery to flash it and also supersu it flashed OK... I restart and i see a little blue guy and its stuck optimizing apps. Suck in restart loop.
what did i do wrong? try a different kernel ?
thanks in advance
EDIT 1
im trying the " Tekxodus" rom. this file is way larger whats going on with that. Is it the same procedure to flash it?
EDIT 2
Flashed to tekxodus rom optimizing apps... now its stuck System UI has stopped. and I cant do nothing. Any suggestions? ?? ?
EDIT 3
Do I need to flash a certain BootLoader along with the recovery for my device (BL and AP) ? , reboot in recovery and flash the custom rom ie "Tekxodus" ?
found this guide for 910C
http://www.ibtimes.co.uk/how-root-galaxy-note-4-n910c-android-5-1-1-lollipop-1518168 with these steps
"Step-1: Download the flashable root package and transfer it to the storage of the phone
Step-2: Download Android 5.0.1 bootloader package. Extract it using any extracting tool and you should find a folder containing Odin flashable tar package and Odin binaries"
so confused lol

All you have to do is Odin stock 5.1.1 rom (COI4 i believe) then Odin TWRP then flash Tekxodus V3.2. Let everything optimize and let it sit there for a good 10 mins after optimization. Ignore what its doing. It will just work. No need to flash anything else unless you want Xposed, then you flash that right after flashing Tek (do not boot in between)

any idea where to get a custom kernel for 910w8 5.1.1 to root stock rom?

Im running this rom (flashed using odin)
http://www.sammobile.com/firmwares/download/56498/N910W8VLU1COI4_N910W8OYA1COI4_TLS/
stock telus rom. I loaded this rom by clicking BL in odin and selecting it (along with my recovery for telus 910w8). This was the only was to get my phone back into working order.
______-
I loaded my recovery for telus into odin and went to download mode.
booted into TWRP
Flashed Tekxodus V3.2.
Optimized apps for about 10 minutes and it just restarted and optimized again and again.
One time it said System UI has stopped and I was hooped.
not sure where I went wrong?
thanks for the response btw I really want to get this going cheers

equlizer said:
You need to odin (bell, rogers, telus) 5.1.1 then odin TWRP then twrp a custom kernel. Our 5.1.1 needs a custom kernel in order to work rooted. Or.....you can load a custom 5.1.1 rooted rom that is W8 compatible or any Tmobile rom such as Tekxodus which i am running.
Click to expand...
Click to collapse
can i use any carrier software for the COI4? That's my only question. Thanks for helping!!

[FIX] Note 4 Exynos N910C/H/U Bootloop issue + Restoring EFS partition

If you have checked out, downloaded and flashed RaymanFX's latest CM13 Unofficial Nightly ROM for Note 4 N910C/H/U users here: http://forum.xda-developers.com/not...-cyanogenmod-13-semi-official-builds-t3259878 chances are you failed miserably at getting back to Samsung's Stock Firmware as you have encountered a series of unending bootloops. The bootloops exist because your downgrading from Android 6.0.1 Marshmallow (CM13 ROM) back to Android 5.1.1 Lollipop (Your previous Original Samsung Stock Firmware), however if you've received the Android Marshmallow Update for your Note 4 model number and region as an OTA Update from your device or Manually by downloading it from sammobile.com or any other external link and have flashed it before flashing CM13 no need to worry you won't need a backup of your Samsung firmware (Unless you want one) as you can perform a clean install of your Samsung Marshmallow Firmware via Odin v3.10.7 Here is where the fix lies; i have compiled a series of posts from 2 very helpful XDA Members from the community because from my experience i have managed to rescue my device using their methods which i will mention below.
Firstly if you have made an Efs partition backup from your previous Original Samsung Stock Firmware in the form of a .tar or .img file e.g "efs_backup_2015-06-01_02-37-16.tar" or "efs.img" respectively then you are good to go if not leave this thread.
Also you will need to download a Note 4 N910C/H/U Pit file corresponding to the region of your Samsung Firmware so here is a link to a selection of pit files. You will need to create an account at sammobile or simply sign if you have a current account to see the download links here: http://www.sammobile.com/forum/showthread.php?t=30022
Follow FR34K-B1B0's helpful post on getting back to stock here: http://forum.xda-developers.com/showpost.php?p=65414257&postcount=39 Skip the 1st Step since we are restoring our IMEI using our backed up Efs file and we will be using a different method to restore this backup.AND AFTER ODIN IS DONE FLASHING THE SAMSUNG FIRMWARE there is a chance that your phone will boot to the Stock Recovery and you will notice a message down there saying: "dm verification failed" so simply wipe data/factory reset and wipe cache and then reboot. Afterwards your phone should boot properly. Now close he's post and carry on down here.
After your phone boots up and you have set it you will notice that your mobile is not connected to your specific mobile carrier and you will see the Emergency calls only text on your lockscreen hence the Not registered on network error. Go to Settings--->About device--->Status and scroll down and you will search and find that your IMEI is literally not the one your phone has and that your Serial number is of an Android Serial number given to you from flashing CM13( Since it's a pure stock android software). If you want you can download the Phone INFO App from the Playstore to verify your device's information and if you do so you will notice that your Samsung Serial number is a bunch of 0's like this: 0000000000 or it's not even present hence wiped.
HERE IS THE MOST IMPORTANT PART FOR RECLAIMING YOUR MOBILE NETWORK CONNECTION, your IMEI is wiped and so you must restore it using your Efs backup file which i mentioned previously above. To do so you will need to root your device and the guaranteed way of rooting your device is using Chainfire's CF-Auto-Root Method.
Here are the links to the Odin flashable MD5 files based on your Note 4's Model Number that you must download ---> For SM-N910C: https://download.chainfire.eu/559/CF-Root/CF-Auto-Root/CF-Auto-Root-trelte-treltexx-smn910c.zip For SM-N910H: https://download.chainfire.eu/577/CF-Root/CF-Auto-Root/CF-Auto-Root-tre3g-tre3gxx-smn910h.zip For SM-N910U: https://download.chainfire.eu/557/CF-Root/CF-Auto-Root/CF-Auto-Root-trhplte-trhpltexx-smn910u.zip After downloading the file on to your computer simply load the file through Odin, power off your phone and boot it to download mode then connect your device to your computer and flash the md5 file. After it's done flashing your device will boot to a custom screen with a red android logo then it will boot.
Right now your device is rooted and you will see the Supersu app in your app drawer. Next if your Efs backup is stored on your computer and is of the format .tar simply open it with 7zip or Winrar you will find the .img present then extract it your desktop. In order to restore your IMEI with this .img file we will need an update package that we can flash from a custom recovery(CWM or TWRP). Here is the link to civato's awesome flashable update package: http://forum.xda-developers.com/showthread.php?t=2331853 and you'll find the package down in the attachment. After downloading the attached file, rename your Efs backup file from "efs.img" to "EFS.img" then extract the contents of the downloaded update package to a folder with the same name of the package, copy your EFS.img file to it and use 7zip or Winrar to add the files to an archive(.zip).
Last but not least copy the new repackaged flashable zip to your external or internal sd card. Run Odin and flash your desired Custom Recovery(CWM or TWRP). Boot to the custom recovery and flash the update package and finally reboot system. After booting your phone will have it's Efs partition restored; your IMEI and Samsung Serial number will be back and your mobile network will be back on again. :fingers-crossed:
Special thanks to FR34K-B1B0 for he's helpful post on getting back to stock firmware
And Many Many Thanks to civato for he's really useful Efs restoring update package! :victory:
And last but not least thank you Chainfire for your great CF-Auto-Root Method that helped root our device(s).

[noob] bootloader and CM13

I'd like to test out CM13 on my rooted i337m, currently running CM 12 with bootloader I337MVLUFNE1. Before I start I'd like to get an idea of the steps involved; any help you can offer is appreciated!
My understanding is that to use CM 13 I will need to do the following:
1. Install the UCUAMDB or UCUAMDL bootloader from the i337
2. Flash the version of recovery that corresponds to the cm13 version I wish to use
3. Backup, wipe, flash CM13 ROM and GApps
I have no idea how to do steps 1 and 2. I've never messed with the bootloader and I'm not even sure if it's safe to use the i337 one on i337m. I also can't seem to get twrp manager to flash a .img file.
CM13 thread:
http://forum.xda-developers.com/gal...rom-cyanogenmod13-releases-nightlies-t3459578

Do you have an i337 or i337m? You can confirm the model number in download mode.
If it is the i337m, just flash twrp, cm13, and gaps.

Yes I've got the i337m, running I337MVLUFNE1 bootloader. So you're saying that I don't need to change bootloaders - all I need to do is flash the cm13 recovery that goes with my cm13 rom. That makes things easier!
I already have TWRP 3.0.2-0 installed. I am trying to use TWRP manager to flash the cm13 recovery from the 2016/8/20 snapshot ( cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J3-jflteatt-recovery.img), but it doesn't show up in the directory. I think this might be because it's a .img file instead of a .zip. Should I just zip it up?

If you have twrp installed as a custom recovery, just copy the rom, which should be in a .zip format, to the phone's internal memory or as card, boot into twrp, perform a full wipe, and flash the rom and your choice of gapps if the rom doesn't include google apps.

audit13 said:
If you have twrp installed as a custom recovery, just copy the rom, which should be in a .zip format, to the phone's internal memory or as card, boot into twrp, perform a full wipe, and flash the rom and your choice of gapps if the rom doesn't include google apps.
Click to expand...
Click to collapse
The problem with that is I get "error 7" from TWRP when flashing the rom as described above. The instructions linked in my original post say that the workaround for this is to first flash the specific recovery snapshot that corresponds to the rom snapshot. I put that recovery on my SD card but TWRP manager couldn't see it (its a .img file), so I zipped it and then tried to flash, but this failed.
So it seems the next step for me is to figure out how to flash that recovery snapshot before I go on worrying about the rom.
I appreciate your help and patience!

The status 7 error is usually caused by one of two items: the TWRP version is outdated or the ROM is not for the phone you are trying to flash.
Since you have an i337m, use Odin and flash TWRP for the gt-i9505, then flash CM.

audit13 said:
The status 7 error is usually caused by one of two items: the TWRP version is outdated or the ROM is not for the phone you are trying to flash.
Since you have an i337m, use Odin and flash TWRP for the gt-i9505, then flash CM.
Click to expand...
Click to collapse
Before I try to flash it with Odin, is it okay to instead use TWRP manager to install the latest jflteatt version of TWRP (since it's a jflteatt version of CM I want)? I bricked a device with Odin once so if you think this would work instead that's what I'll do!

Which version of TWRP did you install? Was it for the jfltecan? If it was, it may probably error out when flashing the att version of CM.

Yes I have JFLTECAN TWRP at the moment. On my old phone it was drilled into me to only use stuff for my version of that phone, which I guess isn't the case with the S4. So it's safe to put the jflteatt twrp on my phone?

Did you try to flash the jflteatt version to your phone using the can version of TWRP? If it won't flash, try the 9505 version of TWRP on the i337m.
I understand what you mean about bricking but the recoveries are very similar as are the phones themselves.

I got it to work. There were 2 issues: 1 was that I needed the jfltexx recovery like you suggested, and 2 was that TWRP manager wasn't properly installing new recoveries so I was actually always testing with the jfltecan recovery. Switching to Rashr allowed me to install the jfltexx recovery, which allowed me to get the fltexx cm13.
Thanks again for your help!

To install TWRP, I thought you flashed the tar version of TWRP using Odin 3.07 in the PDA box. That is the simplest way I know to flash it.