Odin success on each version NB4,NE6 and OB6
Everything goes through smoothly, but it gets stuck on "rebooting to recovery" and never actually gets to recovery
I've flashed twrp,stock recovery img,chainfire, phils, none will actually boot
got this device from a person who said they tried to flash a custom rom and got it into this boot
all I can think of is to repartition the device, but cannot find a pit file that works
odin mode says write protection: enabled
if that is of importance
also tried the unbrick images on sd card, no luck
is there a way to make a bootable recovery.img sdcard? like how nooks can
made a pit from a working note 3 tmo, repartitioned, no go
What you are saying is that you odin successful, and it will not go into recovery, even if you force it to? After the rom image flash, are you in download mode and trying to flash a working recovery?
AxAtAx said:
What you are saying is that you odin successful, and it will not go into recovery, even if you force it to? After the rom image flash, are you in download mode and trying to flash a working recovery?
Click to expand...
Click to collapse
yes odin completely finishes, I tried forcing into recovery mode
loaded twrp,philz recovery, cwm, older versions of recovery, the current version etc.
no longer have the phone but still wonder why it was a no go
Hello, my friend has a Ace 2 (GT-I8160) and he wanted me to try and install CM 11 on his phone. I managed to root it and install temporary CWM on it, however his version of CWM could not flash CM 11 ROM's because it was outdated. I Googled around and found a TWRP .img file that I decided to flash via ODIN (CWM couldn't flash any TWRP .zip files for some reason). Everything went perfectly fine with ODIN, however my friends phone could not go pass the Samsung logo, it would appear for a few seconds and then the screen would go black. He also couldn't go into recovery but he could go into Download mode. Thinking that it was a recovery problem, I managed to get a .img file of TWRP 2.8.6.0 by Chronomonochrome and flash that via ODIN. Still the same problem - phone won't go pass the logo, however it can go into recovery.
So, now the phone boots perfectly to Download mode and recovery - and it can do everything from the recovery, like making backups, wiping, etc, but it cannot boot to the OS itself. I still haven't flashed a custom ROM on his phone because he didn't have the ROM file on his phone at the time nor could be transfer it to his phone via his PC because of some driver issue.
I'm currently downloading I8160XXBN1 firmware from Samsung Updates to flash via ODIN and try to get his phone back into working state. However, I also planned on placing my SD Card (which has the CM rom and Gapps on it) into his phone and flashing a new, custom ROM instead of flashing the firmware.
Does anyone have any advice on what I should do? Should I flash official firmware via ODIN or just flash the ROM using the recovery?
Thanks in advance.
I am am trying to take my Samsung i317 AT&T Note 2 back to stock.
Installed 4.4.2 NJ1 stock rom using ODIN. Reset/ cleared and started phone and went to OTA upgrade the latest patch from AT&T to make it to NJ2. However, when the phone reboots, the Samsung Note II logo shows up and the screen does dark. When I try to enter recovery, it starts to reinstall the OTA patch all over again and says updated. Tried turning the phone back on and the same thing happens again.
I was able to get the phone to work by reflashing the NJ1 stock rom and installed the ZIP stock recovery file using CWM. However, I am trying to get back to the original stock configuration as possible without having CWM installed on the phone and was hoping I can install the stock recovery so that when I go to download mode, everything shows Samsung Official. Knox Warranty Void is at 1, so I guess there is nothing I can do to fix that at this point.
Would installing this be the simple fix by downloading 4.3 Param.bin and Tz.img
Another would be to install the stock recovery ZIP file using CWM as I have already successfully done and maybe someone can point me to find a way to uninstall the CWM afterwards. I've searched online to remove CWM but couldn't find the md5.tar file that would do that from ODIN.
Tmobile Galaxy S4 (SGH-M919) Non-rooted
Problem:
The phone was working and then suddenly went into boot loop. The Samsung screen displays and right before it would goto the animation screen, it loops. I can get to download mode and the recovery OS.
What I've tried:
- First thought it was power button, sent it away to replace button but tech says it's not power button. The phone doesn't turn itself on when the battery is inserted. I can use the power button to turn on/off the phone fine.
- Cache wipe
- Factory reset
- Kies update/recovery
- Burn different firmware version (NB4, NH7, NK2, OH3)
- Tried just to burn NB4 twice consecutively without reboot (first time OK. when burn second time w/o reboot, the phone would display error saying the percentage completed is incorrect since it just finished 100%. Odin continues to burn to finish fine.)
Nothing seems to work. It still loops.
I am desperate. Please help! Thanks in advance.
Beocop
An update:
I tried CF Root and was able to get past he first Samsung screen, past the white TMobile screen, but it went back to boot loop again. Don't know what else to do. Any suggestions?
By burn do you mean you odin'd official stock rom? You cannot downgrade after 4.2.2 MDL so if you flashed OH3 then NB4 will not work anymore...just flash oh3 and root it. For root you can either flash recovery through odin then fash supersuBETA via recovery. Or (if you dont have a computer near you) use kingroot then push recovery through terminal emulator, then run remove kingroot app (google it) then flash supersu through recovery. Link to supersubeta: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
lordodin912 said:
By burn do you mean you odin'd official stock rom? You cannot downgrade after 4.2.2 MDL so if you flashed OH3 then NB4 will not work anymore...just flash oh3 and root it. For root you can either flash recovery through odin then fash supersuBETA via recovery. Or (if you dont have a computer near you) use kingroot then push recovery through terminal emulator, then run remove kingroot app (google it) then flash supersu through recovery. Link to supersubeta: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
I've tried flashing OH3 (twice) also. It still boot loops. Then I tried CF Root to see if it does anything. It flashes fine with no problem. It still boot loops.
I can get into download mode and recovery without problem. It just won't let me past the boot loop.
Try different versions of odin/usb cables and reflash. Or and this voids WARRANTY. Put TRWP on your phone and try a different kernel or OS.
lordodin912 said:
Try different versions of odin/usb cables and reflash. Or and this voids WARRANTY. Put TRWP on your phone and try a different kernel or OS.
Click to expand...
Click to collapse
update:
- I've tried different odin versions (3.07,3.09,3.10). I've tried different USB cables. There was no indication on any error during the flashing process.
- I can flash any stock ROM after NB4 (anything before NB4 => Odin fail). After flashing stock ROMS, it can never get past the Galaxy S4 screen. It just boot loop.
**** I tried to download the OH3 stock rom from Sammobile but I always get a corrupt file error in Winrar. Can someone verify if the OH3 ROM on Sammobile is error free?
- I've tried TWRP (2.6.0.0, 2.6.3.1, 2.8.4.0). I've used it to flash CM-12.1 and Darthstalker_S4_V3 ROMs.
- After flashing all the custom CM ROM, it got stuck with the pink screen.
- I get nothing from Darthstalker ROM, just blank.
I am so frustrated with this process. It seems that I am doing something wrong in my process to flash the ROMs. I am missing something.
Can you please list ALL the steps necessary to properly flash a ROM? Please list every single step that you would personally take, no matter how insignificant (remove battery, clear cache, settings, etc.). Just treat me like a 1st grader.
Thanks so much.
Another update...
- So far, I've tried to flash stock ROMS (NB4-OH3) with odin. None of the stock ROMs will boot fully. All stuck at Samsung logo and bootloops from there.
- The best, but not fully functional, solution I've found so far is from:
1- Flash stock rom NH7 (tried NB4,NH7 so far) with odin
2- Flash CF auto root (CF-Auto-Root-jfltetmo-jfltetmo-sghm919.tar.md5) with odin
3- Flash CWM for recovery
4- boot into recovery, from CWM, install cm-11-20140110-SNAPSHOT-InstallerXNPQ02R-jfltetmo-signed.zip from sdcard1
5- From CWM, install gapps kk for 4.4.3 from sdcard1
6- Clear dalvik, format data + cache
It'll boot up fine. However, I get no sound (not from speaker or headphone). Google keyboard keeping turn on and off. The camera doesn't work. Video's cannot be played.
info "about phone":
Model: SGH-M919
Android version: 4.4.2
Baseband version: M9191UVUFNH7 (prob from CF auto root ?)
Kernel version: 3.4.0 cyanogenmod
Cyanogenmod version: 11.0-installer-XNPQ02R
Build date: 1/9/14
Build number: cm_jftetmo-userdebug4.4.2 KOT49H-installerXNPQ02R release-keys
Don't know what to do now. I've no idea why it won't take stock ROMs. I don't know why I am having problems in cyanogenmod. I freakin hate working on these phones.
Any ideas? suggestions? PLEASE!
Flash philz cwm touch recovery with your current recovery. Then use philz recovery to flash this rom: http://forum.xda-developers.com/galaxy-s4-tmobile/development/moving-please-post-t3009561.
Vicious89 said:
Flash philz cwm touch recovery with your current recovery. Then use philz recovery to flash this rom: http://forum.xda-developers.com/galaxy-s4-tmobile/development/moving-please-post-t3009561.
Click to expand...
Click to collapse
Update:
-OK. I tried using philz cwm and burned this ROM but went through the installation process and picking choices. However, it wouldn't even boot.
-I decided to open up the phone to verify I had a SGH-M919. The sticker underneath the battery indicated SGH-M919. The phone has been using and updating OTA with T-Mobile firmware, the latest being OH3 with stagefright fix.
-After I removed the motherboard, what I saw underneath was disturbing. There was one big stamping showing "I337", which is AT&T. Many other stampings on the chips also show I337.
-In download mode, the product name indicated "SGH-M919".
So the question is, do I have a I337 or M919 phone? Currently, I cannot flash or install any firmware that is not for M919. I tried flashing ATT stock rom (I337ATTFNB1) with odin but it failed, indicating many errors such as PIT. I tried installing CM 11 for ATT but it also failed indicating that I need jfltetmo (M919) version. Ever since the bootloop problem, I cannot get the phone to boot with stock M919 roms.
before /how i got here
i wanted to install a rom on my n5110
first I flashed twrp through odin and i could never access the recovery
so i tried to follow these instructions
https://wiki.lineageos.org/devices/n5110/install
which use heimball (i have used adb before, and i did have some trouble installing himball on el capitan, but managed to install version 1.4.1 since then i found that maybe it doesnt work anymore)
this is where the trouble started after flashing i was unable to access stock rom or recovery and was stuck at boot image.
after that I tried to flash this rom via odin (return to stock)
https://forum.xda-developers.com/showthread.php?t=2773712
now...
somehow this failled and i ended up with a screen that reads (firmware upgrade encountered an issue. please select recovery via kies....)
since then I have tried flashing again via the above method which failled
and another stock (N5110UEEMF1 from https://forum.xda-developers.com/showthread.php?t=2289441) which may have further confused things as realise that this is the out of the box stock and I was on kitkat
which gave the error " invalid magic string"
I have searched for a similar enough problem but not found please help
bump
Download the stock ROM from updato.com or sammobile.com and flash it with Odin. If it gets stuck in a bootloop after flashing the stock ROM, boot into recovery and perform a factory reset.
I recommend flashing with the original Samsung USB cable, a USB 2.0 port, and Odin 3.07.