I have the SM-910C Exynos trelte version of Note 4. I had the unofficial CM 13 ROM from the official development forum, it was all running fine, until the phone shut off with the flashlight on.
Now i can't recover no matter what I try.
Cleared All caches, restored to factory = Bootloop
Pushed a new rom through ADB and flashed it through CWM = Bootloop
Deleted all Internal memory contents, pushed another ROM and flashed = Won't even get past Samsung logo
Installed Odin and tried installing 2 stock factory 5.1.1 firmwares =
Odin:
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
Device (DL MODE):
SW REV. CHECK FAIL. DEVICE 2, BINARY 1
What am i supposed to do now?
Restore EFS partition whit your recovery backup
Try to install C0J5 rom.
Using search on those threads ( official and unofficial cm13 ) will help you out ... Your EFS partition is corrupted and you have to restore it.
Search over the threads and you will find everything You need.
if you didn't do EFS backup like me, you have 3 options
1- Reinstall cyanogenmod
2- wipe EFS partition, but lose IMEI => no phone calls
3-Send your phone to samsung's service and hope for the best
I sent my phone to samsung and they asked me to wait for 5 days.
I had to send my phone to samsung, they fix it for free
here where I live was really fast the repair, only takes one day. (I had a lot of lucky)
If you are on COJ5, doest have so much to do.
you can try flash another rom, oficial, try to backup your EFS and restore
your phone will boot if you use the .pit file, but you'll lose your IMEI (format EFS)
Alright.. I know this is a little off beat from the original question however I am experiencing something similar.
Prior to installing cm 13, all was running well, i went from lollipop to rooted lollipop, to mm stock, to ditto note and then last but not least cm13...
Upon completing the factory wipe before installing stock mm (for online banking purposes, plus the software was glitchy as shi*..)
I am now stuck on download mode, have no USB access to my phone, No TWRP/Clockworkmod. however i do have a nandroid back up on my PC and SD card...
My problem is that I have no way of accessing the phone.. to Samsung it goes?
I have had several issues in the past with my S3 and note 3.. and I found the fix everytime.. this one.. is driving me through the roof..
Please help..
I have tried installing CDC drivers on my PC.. (No Change)
Odin ver 3.10.7/ 3.10.6 and 3.09 which was the one i did my previous installs on..
Related
I have the s5 900f. I'm not new to custom ROMs and thought I'd give one a go for the s5.
Done system backup with twrp and flashed bliss. The ROMs is but I preferred the stock. Anyway I done a full wipe and then selected the restore. All seems to go well and the restore completes. But when restart the phone it starts to boot then fails. No error message or anything. OK I know I can flash another stock rom but I had the back just how I wanted it with all my settings and customisation.
I read a lot about the partitions being changed with a custom rom which can cause a restore to fail. I will flash a stock ROM then once I get it working I will try a restore again. Do I need to flash the pit file?
OK so previously have had htcs. On those I had to flash the bootloader via fastboot and then flash the ROM from recovery. Is it right that with the s5 the bootloader is bundled and flashed with the custom ROM? So when I reflashed the backup the phone still had the bootloader from the customer ROM? Can someone confirm if that is correct or not? I know how to fix my phone but I also like to learn and under stand what happenened.
Just flash the G900F PIT file along with a stock ROM in ODIN
PIT files should be avoided there are many risks while flashing them, albeit the procedure is as easy as it gets.
I would recommend getting Titanium Backup (i have the pro version so i don't know whether what i'm about to suggest is available in the free version or not) and then using titanium to "Extract from Nandroid backup" in the Main Menu and scrolling down to Special Backup/Restore
Hi Guys, I downloaded the stock rom from sammymobile and flashed it via odin. It also reset my recovery to stock as well but was is easy enough to fix
I then made sure the reactivation lock was turned off and reflashed my recovery back and I then reflashed my original backup recovery and success!
Tp recap if anyone else has this problem....
Download and flash the original stock rom,
Boot the phone and turn off the reactivation lock (you dont need to bother with account setup)
Flash the recovery (must be the same one you used for your backup)
Flash your saved backup
Done
Hopefully this gelps someone who finds themselves in my pickle.
To be honest after coming from HTCs I never appreciated the differences when it comes to rooting, customs roms etc. I now do!
A few weeks ago I rooted my Samsung Galaxy S5 (G900H) and flashed a custom ROM on it. But after a few weeks I reflashed the original 5.0 ROM. I then installed cwm and rerooted my phone but something didn't go well because it failed to open cwm 2 out of 3 times, some apps failed to recognize it as a rooted phone (because of improper root maybe) and even some Samsung features were having a trouble in running and my phone was lagging and hung, a lot. So I backed up all my data and decided to do a factory reset.
I went into recovery and pressed on wipe all data/cache but it hung up while formatting. After half an hour or so I pulled out the battery only to see that my phone was stuck on the Samsung logo on boot.
I can't reformat it again as it keeps on saying error mounting data. So I decided to flash it with pit and the android 4.4.4 but since I had my reactivation lock on and usb debugging off, I couldn't flash it with anything.
Please help me in getting out of this situation.
Hi guys,
some weeks ago I upgraded my recovery from 3.0.1 to last version (3.0.2-0).
I made the upgrade by the official App (downloaded from Play store). No problem at the first look. But some day ago I tried to made an upgrade to my custom rom AryaMod 8.1 to 8.3) and during the flash the device has been rebooted and the upgrade of the rom has failed. The device is ok and all functional. I have thought at an error. Not important in this case.
But to day I have made a good backup of all my data and (after a full wipe of Dalvik, Cache, Data and System) I re tried an change of custom rom with a new one Rom (DarkWolf_FW Galaxy S7 Edge Port][V2]) on my device.
The some result as the previous upgrade. The device has been rebooted after some second during the flash of the rom. At the device restart no OS or Data (locked on "Note 3" startup logo) but this is normal after a full wipe.
Furtunaly I restored my backup (made by recovery) and everything is back to normal situation before the wipe.
My question is... Some guy have found a similar problem with the new release of the recovery TWRP 3.0.2-0?
My device is a Samsung Galaxy Note 3 (Qualcom international)
I have had the same issue with some roms.
Touchwiz roms often fail to update and the recovery boots into recovery again.
No errors, just random reboot at initiating the installation.
CM13 and latest AOSP roms seem to flash without any issue.
Try going back to 2.8.7.X it will work.
Too bad you will loose the theme and glossiness of TWRP3
***
Also please backup your data on your computer if your partitions are f2fs while downgrading.
You cannot use twrp 3 for aroma zip.
Sent from my SM-N920C
Hello everyone,
A couple of days ago I've tried to switch a N910C from CM 13.1 to SimplRom. To my surprise, that resulted on bootloops on any possible scenario.
This was not different when flashing the latest stock for it, N910CXXU2DPG8_N910CZVV2DPI1_N910CXXU1DPE4_HOME.tar.md5, and even fully formatting/repartitioning the phone, using TRELTE_EUR_OPEN_SEA.pit, the right PIT file for it.
All flashing processes done by TWRP and Odin were successful.
I was able to use the phone again only after a restore of the nandroid backup of the CM 13.1 on TWRP.
So, I have a few questions, please:
1. Is there a possibility that, even doing all of this, some corrupted/incompatible settings were still present on the phone, avoiding any rom to boot?
2. Is possible that the EFS partition could be causing the bootloops? When I try to access some subfolder of /efs using Total Commander I get reboots on CM 13.1. The same happens when trying to access the Hardware tab of Samsung Phone Info app.
If this partition is corrupted, how repair it?
Solved using https://forum.xda-developers.com/note-4/help/n910c-to-stock-rom-cm13-t3321132.
I hope that this info could help someone else.
my n910c currently stuck on samsung galaxy note 4 screen, is it a bootloop ? i tried to flash rom via ordin but it stop at cache. then i tried with kies it load very slow and stop at around 65%, i can't connect adb with twrp even got driver installed. i even flash stock with pit file.. i guess i tried everything but still no way to restore my phone ! can anyone help ?
It took me a lot of time but finally I've been able to install Android Nougat (lineage-14.1-20170719-UNOFFICIAL-j5ltexx) on my daughter's J500FN I've made a Backup before but the problem is that I forget to save SMS and some phone numbers that was not in is google account . I'm trying to restore backup (and go well except for a message "Failed to mount ? /preload? (invalid argument)") and the phone wont boot it still in a curious classical boot screen who's turning progressively to green and logo's disappearing. What could I do to have it boot again ? I've tried so many things that I'd remember all, like restore whit different TWRP, flash official recovery etc...
Did you wipe data,cache and dalvik?Incase you want to unbrick the phone,and save 100$ for repair(i was unlucky tho),download Samsung Kies 3,install it,then open it and go to Firmware Upgrade & Recovery,type your model number,and then in the serial number field,remove your battery and you will see the code,type it in,continue everything,accept,and then wait,your phone should go back to its original settings,and does the ROM working?Incase it didn't you might have installed it over MM which is not eligible to install ROM's over,cause of security patches,if you want to reflash lineage(or Resurrection Remix(i strongly recocmmend it,its official)),flash the 5.1.1 firmware,install TWRP and root,AND then you flash Lineage.