Does it no longer work? I've the correct drivers installed. I pulled the firmware straight from Sammobile. I flash through download mode, but after the restart, it just sits at "Samsung". That is with Kit Kat. With Lollipop firmware, I just get application and UI crashes on welcome screen.
You need to wipe data in recovery first.
This will solve both issues, the crash in lollipop and the downgrade to kitkat.
ashyx said:
You need to wipe data in recovery first.
This will solve both issues, the crash in lollipop and the downgrade to kitkat.
Click to expand...
Click to collapse
Well, all I've got available to me is download mode. So, I should try and get TWRP back onto it, wipe, then flash firmware via download mode? I'm coming from BlissPop, trying to bring it back to stock Kit Kat, so I can sell it. xD I tried flashing autoroot, but I don't think it works, as it only boots into download, not TWRP.
UPDATE: I totally forgot the device had it's only recovery with options. Lmao. Sorry. Thanks.
Related
I don't how to fix it,i try to flash stock 4.3 but it look same still stuck at odin failed_please help
matt.adid78 said:
I don't how to fix it,i try to flash stock 4.3 but it look same still stuck at odin failed_please help
Click to expand...
Click to collapse
You can try two things but I think that 2 won't work for you.
First: Try to do a emergency recovery with KIES. Keep in mind that it will wipe all your data but your device should be as new
Two: This screen is also a connection screen. If you couldn't enter download mode, just plug-in your phone on this screen. It should works as well with odin. If you can't flash to 4.3 immediately, try to flash an older ROM (I recommend 4.1.2) and do an OTA update.
I only can say you this as well:
I'm totally NOT happy with 4.3. It is a really battery killer and it use unnecessary a bunch of RAM!
It will also gives you a new bootloader with KNOX integrated that makes it very hard to root without tripping it.
my work requires encryption. i was on slimkatv22 at the time and had to encrypt. as encryption kept failing, i went back to stock. way back to stock.
so i'm running
JZO54K.I317UCAMH3 ROM
TEAMWIN Recovery
I317UCUCNE5 Bootloader
with Root and Busybox installed.
everytime i try to update via device update, it downloads, reboots and runs TWRP, I decrypt using password, reboots and the update fails with "Update Interrupted" message.
Is there a way to update ROM and keep encryption?
You can't OTA stock ROMs without stock recovery.
xBkKx said:
You can't OTA stock ROMs without stock recovery.
Click to expand...
Click to collapse
Thanks for your response. I tried updating ROM via ODIN and was not successful. Always got stuck in boot logo after i flashed new ROM.
Is there a stock recovery I should flash over TWRP to try?
Thanks for your help.
I have never used encryption so I can't really help if there are specifics around that. What exactly are you trying to install through Odin? If it's the firmware such as THIS it should overwrite the custom recovery with the stock one. If the stock ROM isn't booting you might have to boot into recovery and factory reset/wipe dalvik cache. This is my first Samsung phone so if nothing helps someone else who'd like to offer their assistance would probably be more knowledgeable.
I was going back to stock, which I guess, was mostly successful. however, I've not been able to install new ROM, namely 4.4.2 I317UCUCNE5. so if I install from your link, that should overwrite custom recovery and allow me to upgrade to 4.4.2 ROM either OTA or via Odin?
Maybe? Using the OTA always tells me there isn't an update (cause I'm on T-Mobile I guess?) and I haven't seen any files to update to Kitkat firmware through Odin
http://forum.xda-developers.com/showthread.php?t=2618447
i'm going to try this.
thanks,
miserly said:
http://forum.xda-developers.com/showthread.php?t=2618447
i'm going to try this.
thanks,
Click to expand...
Click to collapse
haven't had time to try. tbutbut i noticed that foxfi doesn't work even though i'm rooted. i searched for tether and doesn't seem to be a working solution for a free app.
SOLVED
finally got around to following the directions from dicksteele and voila! i'm on 4.4.2!
thanks all!
m
i've samsung note 4 sm-n910p
was working fine ,tried to install firmware but got bricked
i've tried downloading many firmwares all fail
need someone to send the right firmware for my device
attached the error i get
thanks
And here we go again...... What version software was installed before trying to update? Were you rooted?
zjor2000 said:
i've samsung note 4 sm-n910p
was working fine ,tried to install firmware but got bricked
i've tried downloading many firmwares all fail
thanks
Click to expand...
Click to collapse
Try Flashing CF Auto Root through Odin and reboot your phone and report back please.
w7excursion said:
And here we go again...... What version software was installed before trying to update? Were you rooted?
Click to expand...
Click to collapse
Lol, ikr....
done so ,,but nothing keeps restarting ,,,,loop
it needs a new firmware .. OS
zjor2000 said:
done so ,,but nothing keeps restarting ,,,,loop
it needs a new firmware .. OS
Click to expand...
Click to collapse
Were you on the OG5 OTA and tried to root your phone?
rooted thru odin
now i can't get to OS ,just show samsung sign and loops
Flash whatever firmware u was on in odin
zjor2000 said:
rooted thru odin
now i can't get to OS ,just show samsung sign and loops
Click to expand...
Click to collapse
In Odin, Flash the TWRP recovery
Download notarized,cm12 or sacs and put it on your SD card, and reboot to recovery and install your choice of Rom downloaded.
Reboot and relax.
tried to do thru sd card ,but i get :
dm-verity verification failed
can i just go back to 5.1 lollipop with an official stock rom via odin ?
zjor2000 said:
can i just go back to 5.1 lollipop with an official stock rom via odin ?
Click to expand...
Click to collapse
There is no official rom
any firmware can get me back to lollipop with odin !!!
zjor2000 said:
any firmware can get me back to lollipop with odin !!!
Click to expand...
Click to collapse
Here's what I understand as far as recovering with Odin by build:
All these builds NIE, NK2 (KitKat) and first Lollipop (OB7) were downgradeable; you were free to flash in Odin within these builds. Or KIES but not downgrade.
OE1 didn't have a tar, it also locked out the older ones but was compatible with OF5 to flash Odin or KIES to upgrade. Can only go back to OE1 with nandroid backup from OF5. OE1 introduced reactivation lock to prevent flashing over user locked phone as well as preventing the downgrade to escape the feature. Seems dine could recover from a bit loop by flashing CF Auto Root in Odin.
OF5 was released with a supporting tar eventually but it's the same story as OE1. But I'm not sure if CF Auto Root worked to recover boot when looped.
OG5 locks it further. If you don't have a nandroid, recovering from boot loop options may include flashing CWM recovery or a compatible flash that takes you away from OG5 almost entirely. Sacs, Notarized, and CM12 are reportedly working. Reportedly, can't go back to OF5 with Odin and not sure about nandroid, maybe not.
Depending on certain exceptions unclear, Odin and KIES have been reported to work together, flashing stock OB7 ROM, parts of stock tar with Odin with a flash result that won't boot but connecting KIES in recovery and using the emergency recovery method. If KIES doesn't see your phone on recovery, you may try this fix on your Windows PC:
http://forum.xda-developers.com/showpost.php?p=34864154&postcount=14
I'll add this too: flashing L Speed Mod may fix adb with ADB Insecure in booted mode; ADB Insecure wouldn't be needed in recovery anyway so it works without it. I can report this does work for me with the above MTP fix on OB7.
Sent from my SM-N910P using Tapatalk
samep said:
Here's what I understand as far as recovering with Odin by build:
All these builds NIE, NK2 (KitKat) and first Lollipop (OB7) were downgradeable; you were free to flash in Odin within these builds. Or KIES but not downgrade.
OE1 didn't have a tar, it also locked out the older ones but was compatible with OF5 to flash Odin or KIES to upgrade. Can only go back to OE1 with nandroid backup from OF5. OE1 introduced reactivation lock to prevent flashing over user locked phone as well as preventing the downgrade to escape the feature. Seems dine could recover from a bit loop by flashing CF Auto Root in Odin.
OF5 was released with a supporting tar eventually but it's the same story as OE1. But I'm not sure if CF Auto Root worked to recover boot when looped.
OF5 locks it further. If you don't have a nandroid, recovering from boot loop options may include flashing CWM recovery or a compatible flash that takes you away from OG5 almost entirely. Sacs, Notarized, and CM12 are reportedly working. Reportedly, can't go back to OF5 with Odin and not sure about nandroid, maybe not.
Depending on certain exceptions unclear, Odin and KIES have been reported to work together, flashing parts of stock tar with Odin and connecting KIES using the emergency recovery method. If KIES doesn't see your phone on recovery, you may try this fix on your Windows PC:
http://forum.xda-developers.com/showpost.php?p=34864154&postcount=14
I'll add this too: flashing L Speed Mod may fix adb with ADB Insecure in booted mode; ADB Insecure wouldn't be needed in recovery anyway so it works without it. I can report this does work for me with the above MTP fix on OB7.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Was i incorrect in my method of getting him back on his feet? I should suggest CWM instead of TWRP? Now im confused.
The last thing i want to do is tell someone the wrong procedure, only causing more frustration. I thought i read 'Twrp, Install and Viola!' from many users in the other thread.
xxSTARBUCKSxx said:
Was i incorrect in my method of getting him back on his feet? I should suggest CWM instead of TWRP? Now im confused.
The last thing i want to do is tell someone the wrong procedure, only causing more frustration. I thought i read 'Twrp, Install and Viola!' from many users in the other thread.
Click to expand...
Click to collapse
I think your suggestion is consistent with what we're learning as you gave it. It seems to be evolving with trial and error. The CWM suggestion came from a single experience shared.
http://forum.xda-developers.com/showthread.php?p=62196189
The OP was asking for another solution and it wasn't clear where he started from to correctly recovery so tried to answer including all the options for each build. I added some things that may help depending on his situation.
Sent from my SM-N910P using Tapatalk
i managed to find the right fW ,,,if anyone has same problem u can do it your self
https://1fichier.com/dir/IOjXgJUa
and download this file : N910PVPU3BOF5_SPT3BOF5_SPR_Sprint_USA_5.0.1.zip
In short, I have a SM-T800 on 4.4.2 stock. I have TWRP installed. The problem is the USB is out of order, it's just busted on hardware level, so I can't use ODIN or ADB or anything requiring USB.
Does there exist a way to flash the device upwards (maybe to 6.0.1) with only these tools available? I can't get OTA updates due to the custom recovery.
I've tried flashing with FlashFire a stock 5.0.2 firmware from samsung-updates, but FlashFire can't flash the bootloader, and the SM-T800 needs a bootloader upgrade to go over 4.4.2. The flash resulted in softbricking, but I've managed to return back to working 4.4.2.
Basically what I need (I would imagine) is a TWRP flashable package, which includes the bootloader.
Dorden said:
In short, I have a SM-T800 on 4.4.2 stock. I have TWRP installed. The problem is the USB is out of order, it's just busted on hardware level, so I can't use ODIN or ADB or anything requiring USB.
Does there exist a way to flash the device upwards (maybe to 6.0.1) with only these tools available? I can't get OTA updates due to the custom recovery.
I've tried flashing with FlashFire a stock 5.0.2 firmware from samsung-updates, but FlashFire can't flash the bootloader, and the SM-T800 needs a bootloader upgrade to go over 4.4.2. The flash resulted in softbricking, but I've managed to return back to working 4.4.2.
Basically what I need (I would imagine) is a TWRP flashable package, which includes the bootloader.
Click to expand...
Click to collapse
There is literally no way to flash the bootloader except by official means.
Kingroot is able to root most LL roms.
So if you go back to complete stock you can take the OTA and get the LL bootloader.
The thing I'm not sure about is if you will be offered the LL update or just the MM update.
Once you have the LL bootloader you will be able to root and install MM via FF.
ashyx said:
There is literally no way to flash the bootloader except by official means.
Kingroot is able to root most LL roms.
So if you go back to complete stock you can take the OTA and get the LL bootloader.
The thing I'm not sure about is if you will be offered the LL update or just the MM update.
Once you have the LL bootloader you will be able to root and install MM via FF.
Click to expand...
Click to collapse
Thanks, I'll have to go back to stock recovery then and see after if I can get rooted without USB after that, will see.
But how do you get back to stock if your on a custom room. I can't seem to get the right file to work. Everytime I try and extract and do it through Odin it fails
So something I did went wrong and I'm at a lost to what to do. I tried searching google and here but if someone could point me in the right direction, I would be most greatful.
So I install 6.0.1 using smartswitch which went just fine, but I decided to root it using odin and cf-autoroot, but that seemed to fail and I was stuck in download mode. I manage to exit download mode but it just remains stuck on the samsung logo. I am able to boot into twrp recovery (had installed already from 5.01. root) and I did a factory reset but I'm still stuck.
Any ideas? Any hope?
Update: Got it working buy downloading henklbr stock rom located here: http://forum.xda-developers.com/gal...firmware-selection-sm-t700-sm-t2960225/page18 I think I screwed up odin the first time by not having auto-reboot checked. And can I say samsung-updates needs a better download provider, I did not want to wait 8 hours for their download to complete.
If you are reading this because you ran into the same issue, rooting with cf-autoroot still didn't work for me, I ended flashing twrp via odin and and then going into twrp and flashing superuser. Now I have root again.
Just saw you fixed the problem.. may my time wasted rest in peace :angel:
Yeah uh last I and others I know checked cf-autoroot does not work with android 6.0.1
Feel free to try this though:
Okay so here is how you can MAYBE fix your T700.
1. Download a firmware or ROM from here or other source: http://www.sammobile.com/firmwares/database/SM-T700/
2. Download Odin v3.10.6 on your PC.
3. Use Odin to flash the firmware or ROM on your T700. (Don't know how? Try to find a general guide on flashing firmware)
Once you do that feel free to use this root method that works on the T700 running 6.0.1:
http://android-rooters.blogspot.com/2016/10/how-to-root-samsung-galaxy-tab-s-84_27.html
yep, just download a TWRP with a TAR extension for ODIN and happy flashing... You can root after installing your Rom. The same can be done if you install the stock ROM before installing TWRP and rooting for debloating.
Thanks anyways ZimriTech, Google lead me to be leave CT auto root would work, lesson learned.