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
Related
So two days ago I thought about installing Vision X rom on my Note 3 (T Mobile).
I downloaded the ROM and then backed up my current ROM (nandroid). I had Phillz touch recovery then.
Then I thought about going to TWRP and thus I downloaded the latest zip for my phone and flashed it via Phillz upon trying to reboot into recovery it got stuck in the screen "Rebooting Recovery...".
When I restarted it would still try to reboot into recovery and get stuck. I got out of that by going into download mode and then selecting "Restart Phone".
After that I looked for solutions and upon failing to find any I thought about going back to stock and starting from ground zero. I managed to flash the latest stock using Odin however I forgot to do a factory reset before hand.
When I tried to do a factory reset in my, now stock, phone it failed and then got stuck trying to get into recovery. It would flash "Rebooting Recovery..." then restart and flash that in a loop.
I have lost my root as well in the process and trying to root using Odin and CF-Root just get's me back in the recovery boot loop. I can use the phone OK however this is not a stable situation.
I'm sure I've made some serious errors in the tinkering and would like to get my recovery back. I really love Custom Roms. Any kind and knowledgeable souls out there to help me in my cause?
kaif15 said:
So two days ago I thought about installing Vision X rom on my Note 3 (T Mobile).
I downloaded the ROM and then backed up my current ROM (nandroid). I had Phillz touch recovery then.
Then I thought about going to TWRP and thus I downloaded the latest zip for my phone and flashed it via Phillz upon trying to reboot into recovery it got stuck in the screen "Rebooting Recovery...".
When I restarted it would still try to reboot into recovery and get stuck. I got out of that by going into download mode and then selecting "Restart Phone".
After that I looked for solutions and upon failing to find any I thought about going back to stock and starting from ground zero. I managed to flash the latest stock using Odin however I forgot to do a factory reset before hand.
When I tried to do a factory reset in my, now stock, phone it failed and then got stuck trying to get into recovery. It would flash "Rebooting Recovery..." then restart and flash that in a loop.
I have lost my root as well in the process and trying to root using Odin and CF-Root just get's me back in the recovery boot loop. I can use the phone OK however this is not a stable situation.
I'm sure I've made some serious errors in the tinkering and would like to get my recovery back. I really love Custom Roms. Any kind and knowledgeable souls out there to help me in my cause?
Click to expand...
Click to collapse
Go to the Playstore and download TWRP Coordinator and then
use it to install the latest TWRP recovery for your phone.
Once you can get back into TWRP recovery you need to flash
the cf-autoroot for your phone. Be sure you flash the CORRECT
version of cf-autoroot for your phone's model.
Good luck!
Misterjunky said:
Go to the Playstore and download TWRP Coordinator and then
use it to install the latest TWRP recovery for your phone.
Once you can get back into TWRP recovery you need to flash
the cf-autoroot for your phone. Be sure you flash the CORRECT
version of cf-autoroot for your phone's model.
Good luck!
Click to expand...
Click to collapse
The app is constantly crashing!
It would start for a second then close. I tried the TWRP manager as well with the same result.
I've lost root access when I Odined back to stock, won't I need root access to install new recoveries?
Sounds like you flashed the stock 4.4 firmware and now need recovery to root. Flash this TWRP file using Odin http://goo.im/devs/OpenRecovery/hltetmo/openrecovery-twrp-2.7.0.1-hltetmo-4.4.img.tar
Once you flash it, you need to boot into recovery to install supersu to root.
Switch off the Galaxy Note 3 (remove the battery and reinsert if needed)
Next, press and hold simultaneously Volume Up, Home and Power.Release the buttons when the screen flickers and wait for the TWRP menu.
Select Reboot, then System and install Supersu for root.
Once booted, open Supersu to update it and grant permission.
Hope this helps. Good luck.
My non-rooted GT-N7100 didn't want to boot after a longer period without battery charge. After fully charging, i got this screen: dropbox dot com/s/jy8sirmpgp6zm7h/20140823_214100.jpg
Later, i got the "firmware upgrade encountered an issue"-message. I tried to flash the latest stock ROM (via ODIN, from sammobile, checked MD5) but I get a fail when writing system.img.
So I decided to flash a custom recovery (twrp v2.8.0.1) (and trip knox..) to flash via an OTG-cable, but this also doesn't work.
TWRP tells me there is "no OS installed" when trying to reboot.
What am I doing wrong?
Wensjong said:
My non-rooted GT-N7100 didn't want to boot after a longer period without battery charge. After fully charging, i got this screen: dropbox dot com/s/jy8sirmpgp6zm7h/20140823_214100.jpg
Later, i got the "firmware upgrade encountered an issue"-message. I tried to flash the latest stock ROM (via ODIN, from sammobile, checked MD5) but I get a fail when writing system.img.
So I decided to flash a custom recovery (twrp v2.8.0.1) (and trip knox..) to flash via an OTG-cable, but this also doesn't work.
TWRP tells me there is "no OS installed" when trying to reboot.
What am I doing wrong?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1922461
try the steps under "3. Odin Instructions for the Samsung Galaxy S III "based" devices".
TWRP recovery should not be an issue if you rooted your phone before installing it. But, if you somehow have messed it up, try getting the firmware from Sammobile and flash it using odin. That should also replace your recovery to stock.
Hope this helps.
Cheers
I can flash a bootloader, recovery, pit-file, .. I'm using the right cable/drivers/.. It's just impossible to flash system.img to that partition. Twrp/philz/cwmrecovery give me an error when trying to wipe. Is it possible that that partition is corrupt?
I've tried a few stock roms and different custom/pre-rooted roms. None are flashable via odin (1.85, 3.07, 3.09), via adb sideload or USB-stick. I can't mount micro SD cards.
The phone was 4.3 when problems started; does anyone know where i can find the latest universal 4.3 stock rom? Sammobile only shows 4.4 and up..
Bricked?
Try twrp 2.7.2.1. and see if it works.
i317 no custom recovery or rom. On stock rom and rec. Phone one day got stuck in samsung screen. I can enter recovery and DL mode. Odin flashes all fail with nand write start. In recovery mode E: everything fails to load or directory not found. Knox is still on 0. Anyone have any solutions? Read threw 100's of threads and no one seems to have fixed.
Any Solutions
Neo2020Marz said:
i317 no custom recovery or rom. On stock rom and rec. Phone one day got stuck in samsung screen. I can enter recovery and DL mode. Odin flashes all fail with nand write start. In recovery mode E: everything fails to load or directory not found. Knox is still on 0. Anyone have any solutions? Read threw 100's of threads and no one seems to have fixed.
Click to expand...
Click to collapse
Which file are you trying to ODIN?
It needs to be one that DOES NOT have the sboot.bin in there. Review your flashes, it is probably bombing when trying to flash the bootloader, Which after MK6 is not allowed to be overwritten.
This may help
http://forum.xda-developers.com/showthread.php?t=2618447
Tried UCUBMK6, UCUCNE5, stock and recovery flashes. Even tried pit files with (nand erase all) (auto reboot) (Re-Partition) (F reset time) but returns with fail as photo. Tried the whole post you suggest with same results. I dont believe its completly dead as recovery some what works and DL mode still works.
To try and get your phone running, try flashing the latest TWRP from here via Odin: http://techerrata.com/browse/twrp2/t0lte
Copy a custom ROM to your external SD card. Boot into recovery, wipe cache, Dalvik, system, data, flash the ROM, and reboot.
No O/S - can only boot into download mode
I've got an interesting one. I was prepping my phone for selling, decided to clear out all the memory. Somehow I must have deleted more than I meant to b/c when I restarted the phone, it just hangs on the Samsung screen. I can get into download mode, but not into recovery and nothing ever loads. I tried at least one version of installing CWM but it doesnt look like I can boot into recovery even after the Odin install appears ok. Before the crash, I was running a modded 4.4.2 rom with the bootloader and other things that come with it. Is there anything I can do to get this thing up and running again?
Thanks!
I suggest you flash a custom recovery and CM10.2 to at least get the phone up and running so you can confirm the bootloader and modem on the phone before flashing anything. Flashing the wrong bootloader, modem, or bootloader/modem combintaion could hard brick the phone.
audit13 said:
I suggest you flash a custom recovery and CM10.2 to at least get the phone up and running so you can confirm the bootloader and modem on the phone before flashing anything. Flashing the wrong bootloader, modem, or bootloader/modem combintaion could hard brick the phone.
Click to expand...
Click to collapse
Thanks. I'm positive I was running 4.4.2 on the phone before I decided to turn it into a paperweight
Flashing a custom recovery would be the goal, problem is that I can't find a recovery that I can flash. I've tried the latest version of PhilZ Touch recovery and that doesnt seem to work. ODIN shows it as a good install but when I restart the phone, I can't get into recovery. So was hoping for some direction on a different way of going about it. Basically, had 4.4.2, now I can only get into Download mode...
Download the latest tar.md5 file from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Open Odin, connect phone, uncheck everything except f.reset time. Flash Philz. When you see reset in the status windows, remove USB cable, pull battery, replace battery, boot into recovery, flash ROM.
There are different versions of the 4..4.2 so it is best to determine the exact bootloader.
I once tried to "Unroot" my phone by factory restoring it then flashing a stock rom and original firmware through Odin. Flashing the stock rom worked however when I tried to flash the firmware through Odin I got an "ext4 image fail" error. I am now stuck with a phone that does not boot. It is just stuck on a "Connect to Kies for emergency recovery" screen - but my phone is never detected in Kies. I cannot boot into recovery mode: I tried and I get the Samsung logo with the blue "RECOVERY BOOTING" text at the top for a split second, but then the screen goes black and I get this message at the top of the screen:
"image size too large!! W:1000, H:1920
display image fail
SECURE FAIL: KERNEL"
Basically, I had 4.2.2 Jellybean installed but wanted Kitkat (this was much earlier this year) and so I found a method of installing KitKat which also gave root access. Can't remember what I did to install it.
I have now successfully flashed CWM recovery through Odin but I have absolutely no idea what to do next. All the guides I have read talk about installing something through an SD card via the recovery menu, which I obviously cannot do because I can't reach the recovery menu.
Anyone know the steps to take?
SoulWithin said:
I once tried to "Unroot" my phone by factory restoring it then flashing a stock rom and original firmware through Odin. Flashing the stock rom worked however when I tried to flash the firmware through Odin I got an "ext4 image fail" error. I am now stuck with a phone that does not boot. It is just stuck on a "Connect to Kies for emergency recovery" screen - but my phone is never detected in Kies. I cannot boot into recovery mode: I tried and I get the Samsung logo with the blue "RECOVERY BOOTING" text at the top for a split second, but then the screen goes black and I get this message at the top of the screen:
"image size too large!! W:1000, H:1920
display image fail
SECURE FAIL: KERNEL"
Basically, I had 4.2.2 Jellybean installed but wanted Kitkat (this was much earlier this year) and so I found a method of installing KitKat which also gave root access. Can't remember what I did to install it.
I have now successfully flashed CWM recovery through Odin but I have absolutely no idea what to do next. All the guides I have read talk about installing something through an SD card via the recovery menu, which I obviously cannot do because I can't reach the recovery menu.
Anyone know the steps to take?
Click to expand...
Click to collapse
Not quite sure what you mean by flashing rom & firmware as it's the same thing, I guess you mean you flashed multipart rom files as separate items. Or did you flash "extra" files, by which I mean flash a full stock rom plus some duplicates eg csc, bootloader etc at the same time? Not sure if this would just overwrite or cause issues. Is there a procedure you followed? Eactly what files did you flash?
Anyhow, I think your first problem is that your cwm recovery has not installed properly. CWM is not maintained anymore The first thing I would do is try to flash a stable TWRP for our phone (see ne0zone75's TWRP thread) as this is maintained. If after flashing TWRP you still can only access download mode then you should flash a full stock rom (1 file with 4 files inside) as others have done to solve "image size too large" problem (try different Odin version if fails). If you can boot into recovery thin you can flash a zip file (though I think it would be a good idea to flash a full stock rom so you at least starting with a known configuration , then flash a custom rom or root it)