Im sorry to post this, was hoping to keep finding/reading solutions but i have broke it now, and so Im posting this
I recently received a verizon note 3 and wanted to put cyanogenmod on it
so i followed this guide
however my problems started with:
Failed to confirm end of PIT file transfer!
Which the guide addresses and says to clone the repo and manually compile it. which i did but than ended up with:
"Failed to confirm end of file transfer sequence"
I was unable to fix this error and abandoned the guide
next i tried odin (as opposed to Heimdall used above). I installed the Samsung drivers and am able to see that odin is connected to my phone.
tried step 2a on here but received an error from odin
was trying some other tutorial as well but turned out that was for a developer version of the phone which i dont have
The latest thing I'm trying is this ([Official] Note 3 Verizon Bootloader Unlock)
however it needs root, so i attempted Root De La Vega but after trying to flash the ap file (Root_de_la_Vega.tar.md5) in odin i am now stuck at the Software Update Failed screen. I've read alot of post saying that the boot loader is locked and there isn't a known unlocker yet, but most of those post are well over a year old and the post linked above ([Official] Note 3 Verizon Bootloader Unlock) is recent.
Is it even possible to unlock the boot loader and root my phone? which guide should i follow?
How do i fix this Software Update Failed screen that im stuck at? Should i use the verizon software repair assistant to repair the image?
i cant get back into android to read any more specs
but i had verified earlier that my CID does starts with 15
its not a developer phone
its has android 5.0
its a sm-N900V
its a verizon note 3
You need the Verizon forum .
Have you tried flashing stock rom with Odin the latest is 0f1,try that then root then unlock bootloader mines unlocked can't flash older rom until bootloader unlocked.
Sent from my SM-N900V using Tapatalk
Related
I'm running the Phronesis ROM and it says that to make the video recording work, I need to flash the bootloader, and it also comes with a modified modem. My bootloader is the stock bootloader, and I just unlocked it a long time ago. So, I'm using Odin to flash the files with my Sprint Note 3 in download mode. Odin and my downloader both say that it failed to download. (Auth fail) It didn't change my phone at all; it just won't write the new data.
My bootloader is unlocked or I couldn't get into Phronesis. Any idea what's causing the issue?
What is the Odin error? The error probably occurred because Odin could not flash a particular file to the phone.
Urgent help needed as I'm leaving the country at the end of the week o any help is appreciated!
Just successfully rooted my device:
Black, Unlocked, PRA-LX1, UK, Dual SIM
After doing so successfully, I attempted to flash LineageOS from the following link:
https://forum.xda-developers.com/p8lite/p8-lite-2017-development/rom-lineageos-15-1-hi6250-devices-t3811583
Although when I completed Step 6 on the Installation guide and rebooted the phone, I started seeing the message:
------------------
ERROR MODE
Attention!
Please update system again
(Green Android picture)
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
------------------
Despite this, I didn't receive a box with my phone due to being second hand, and I didn't see the model number on the receipt as it was from a reselling store. I didn't remember to note down the specific model number
It'd be extremely helpful if someone could possibly help just from the device description above as I'm not sure if it's safe for me to just attempt to flash every stock rom for every other LX1 device out there.
---------------------------------------------------------------
Update:
To restore this, I connected via fastboot with a working USB & flashed an original stock recovery in the video found here
(Just in case their download link ever goes down, I have uploaded the same copy to my MEGA, found here)
The recovery installed fine when using the command
fastboot flash recovery oeminfo.img
Click to expand...
Click to collapse
Whenever trying to flash any other recovery such as twrp before this fastboot stuck on a loading icon.
The stock recovery seems to be downloading the original firmware, too.
PRA-LX1C432B202 is presumably the model.
Both the bootloader and FRA were unlocked when everything else was inaccessible.
Looks like the custom ROM's recovery that you've flashed is not compatible with PRA-LX1. Try to flash stock recovery. If not working, then flash stock firmware.
Thanks @Botar230!
I didn't see your comment until just now after deciding to edit this post since I've gotten a step closer to restoring my device.
Your solution was the method I used although I didn't know my phone model, so I found a random solution which just worked for my device, and the eRecovery seems to be downloading the stock firmware anyways. Thanks again
Before flashing this lineage os you should update to EMUI8 to get treble support, i suppose you was running EMUI5, hence the error mode.
I installed TWRP so i could use Magisk and pass safetynet so i could use GooglePay. However during the process i mustve messed up. Currently i can enter TWRP aswell as Download mode however Odin gives the the error "Complete(Write) operation failed." and my phone says "SW REV CHECK FAIL DEVICE 3, BINARY 1"
My device is Galaxy S8 G950F UK H3G, i have checked that i am flashing the right firmware. In addition to this, when i try to boot normally im stuck on the "Samsung Galaxy S8" Boot screen.
Anyhelp would be much appreciated, i just want to get my phone working again.
Any reassurance with drivers and links to specific drivers would be useful, i installed all the ones i could find
Seems like your firmware you are trying to flash is older than the bootloader... try to flash the latest firmware and reply.
shayeque said:
I installed TWRP so i could use Magisk and pass safetynet so i could use GooglePay. However during the process i mustve messed up. Currently i can enter TWRP aswell as Download mode however Odin gives the the error "Complete(Write) operation failed." and my phone says "SW REV CHECK FAIL DEVICE 3, BINARY 1"
My device is Galaxy S8 G950F UK H3G, i have checked that i am flashing the right firmware. In addition to this, when i try to boot normally im stuck on the "Samsung Galaxy S8" Boot screen.
Anyhelp would be much appreciated, i just want to get my phone working again.
Any reassurance with drivers and links to specific drivers would be useful, i installed all the ones i could find
Click to expand...
Click to collapse
Yes thats what this error means your bootloader is updated and you are flashing older firmware than the device currently has by the device 3 I would assume your device is updated to revision 3 of firmware
Hey guys, I recently bought a used hero2lte(SM-G935F) device from a coworker and started modding it right away. (Everything worked fine until then)
I flashed the Superman Rom all according to the noob friendly guide there (flash twrp, wipe, flash rom, installed bootloader, modem and csc from aroma installer, magisk after reboot).
Right away my data didn't work so I got the Oreo CSC (DBT) and flashed it. Still didn't work.
Currently I'm in a state where I don't have a working IMEI/baseband. I followed the instructions here and here.
First one doesn't work since I can't downgrade to older firmware and the second didn't work since there were no modemst1 or modemst2 directories. (/dev/block/platform/155a0000.ufs/by-name/ on my device).
Also I can't seem to access my device with heimdall which has worked before: "ERROR: libusb error -7 whilst receiving bulk transfer. Retrying..." and I suspect the "Secure Download: Enabled" I can see on the download screen. Which is weird since I enabled OEM Unlock.
I just want to get my IMEI back (I have the correct number here), what can I do guys?
Noob here: I need help with my Note 3 (SM-N900V).
I bought a used phone to replace a stolen one; it came with Android 4.0. A few years ago I successfully used Odin to flash TWRP 3.1.0.0 and the stock OF1 Android 5.0 rom, followed by a root with ArabicTool.
Phone works fine for everyday use, including root-requiring apps, but several apps are now requiring a more recent version of Android. Also, I can no longer boot into recovery mode; instead I get a message saying "System software not authorized by Verizon Wireless has been found on your phone".
I thus decided to try to flash the phone from scratch.
First I tried to use ADB and Fastboot to make sure the bootloader is unlocked. Unfortunately, while ADB worked fine, I was never able to get Fastboot to see the phone, despite following the advice of several web pages addressing this issue, and trying several different drivers.
Pressing on, I decided to try to install TWRP again. Booted phone with VolDown, Home, Power. First I tried using Heimdall 1.4, both with drivers from Samsung, and then with the MSM8960 drivers that came with Heimdall, using this command:
heimdall flash --RECOVERY twrp-3.3.1-0-hlte.img --no-reboot
In both cases, all I got was "ERROR: Failed to access device. libusb error: -12"
Therefore, decided to try it with Odin. Booted phone with VolDown, Home, Power. Run Odin 3.12.4_4, which immediately shows "Added". Load TWRP 3.3.1.0 with AP button, click Start...and get a red Fail flag within a few seconds. Log shows "FAIL! (Auth). Phone shows "SYS REV CHECK FAIL: No Version" and "SECURE MAGICCODE CHECK FAIL: recovery".
I didn't even bother trying to flash the LineageOS ROM.
Can someone please tell me what I'm doing wrong? Please don't assume I know anything about what I'm doing.
--
*not an expert*
Verify that you are using the correct build of twrp-3.3.1.
I am using the hlte build of 3.3.1 on my phone (SCL22)... but my gut tells me that you and I wouldn't share the same build.
Nope basic problem is that OP is in the wrong forum for a Verizon phone .
Assuming that download mode still works (if it is, lucky you); I'd suggest reflashing the stock firmware for your Verizon device.
Flashing a stock firmware would *hopefully* fix your recovery and download issues.
Perhaps the errors you described may have been caused by installing the wrong ROM/firmware.
So, NEVER INSTALL/FLASH a custom or stock ROM that is not tested to work on your device. The main reason is because different variants of the same device (N9000, N900A, N900V) use different chipsets, software and drivers. Also, flashing a wrong ROM/kernel/firmware may cause application errors, boot loops, broken recovery/download mode, or a hard brick.