So for the last month or so, I've been trying to get back to Jelly Bean on my Note 3. I'm on the Kit Kat leak, and yes I've read the threads for going back to MJ5, I've read the threads in this forum and pretty much every comment looking for answers. I've googled every combination of words I can think of, and nothing has worked. I've used the Heimdall method to restore a bricked Kit Kat Rom back to the Kit Kat leak, but now when I try to get it back to Jelly Bean, Heimdall says it fails to download package information, fails to end session packet, etc...It'll recognize my phone, get all the way to the download package, and fail.
My Note 3 isn't damaged or broken or anything so it's not like I'm in a rush, which is why I've taken my time going over all the options I've seen. However, I would like to have the official Kit Kat build when it gets released or at least re-root my phone and for the time being I haven't found a way to do either...
Any help or guidance would be greatly appreciated!
The restore method worked for me, coming from the KNOXRAID Kit Kat version--restored successfully to MJ5.
Are you able to flash that version (Knoxraid), then try the restore?
Edit: Heimdall took me a few tries, along with odin. Had to switch from usb3 to usb2 to even get it to be recognized.
Sent from my SAMSUNG-SM-N900A using Tapatalk
composi said:
So for the last month or so, I've been trying to get back to Jelly Bean on my Note 3. I'm on the Kit Kat leak, and yes I've read the threads for going back to MJ5, I've read the threads in this forum and pretty much every comment looking for answers. I've googled every combination of words I can think of, and nothing has worked. I've used the Heimdall method to restore a bricked Kit Kat Rom back to the Kit Kat leak, but now when I try to get it back to Jelly Bean, Heimdall says it fails to download package information, fails to end session packet, etc...It'll recognize my phone, get all the way to the download package, and fail.
My Note 3 isn't damaged or broken or anything so it's not like I'm in a rush, which is why I've taken my time going over all the options I've seen. However, I would like to have the official Kit Kat build when it gets released or at least re-root my phone and for the time being I haven't found a way to do either...
Any help or guidance would be greatly appreciated!
Click to expand...
Click to collapse
The op states that heimdal will not finish. You have to check no reboot and yank the battery and boot into recovery to flash your zips. Every time I do it l, heimdal quits at 95 percent. I've used this method at least a dozen times without fail.
i understand but it fails before even 1% is shown...ive used the method before so i am aware of the 95% that is mentioned in the op but this time nothing happens...i hit start and about 10 seconds later it fails
Sent from my iPad using Tapatalk
composi said:
i understand but it fails before even 1% is shown...ive used the method before so i am aware of the 95% that is mentioned in the op but this time nothing happens...i hit start and about 10 seconds later it fails
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
That's happened to me before. I just hit start again and it worked. Try it a few times.
Also, one time I couldn't get anything to work and I switched the USB cable I was using. Usb3 gave me that 1% error, but usb2 worked like a charm.
Sent from my SAMSUNG-SM-N900A using Tapatalk
I'll keep that in mind when I try again later tonight.!
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
I thought all we have to do is Odin into safe strap and wipe your device then flash your old jellybean rom
Sent from my SAMSUNG-SM-N900A using xda app-developers app
I think he is referring to the leak, not the ROM.
chispas117 said:
I thought all we have to do is Odin into safe strap and wipe your device then flash your old jellybean rom
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
ZOOPidy said:
I think he is referring to the leak, not the ROM.
Click to expand...
Click to collapse
Exactly
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
So you tried dvilpotatomans method to get back to stock?
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Any luck?
Sent from my SM-N900A using Tapatalk
Related
Ok soooo ive uninstalled safestrap and back on stock recovery and stock ics rooted. What else do i need to do to recieve ota when its pushed out?
Sent from my DROID4 using xda app-developers app
rruleford said:
Ok soooo ive uninstalled safestrap and back on stock recovery and stock ics rooted. What else do i need to do to recieve ota when its pushed out?
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
If it's like the last OTA to ICS, you're probably going to have to flash the ICS fastboot files before the new OTA will take. The problem before was safestrap changed something, somewhere (logwrapper maybe?), that did not get changed back after uninstalling the safestrap recovery and app. MAYBE this has been changed/fixed in the new versions of safestrap? Pretty sure we were on version 2.x at the time. You can always try without fastbooting and see what happens. Won't hurt anything. If you do need to fastboot, use jsnweitzel's utility. It has an option to fastboot without wiping data. That's what I'm planning on doing. It should still fix whatever safestrap changed.
Sent from my Droid 4 - LiquidSmooth
kwyrt said:
If it's like the last OTA to ICS, you're probably going to have to flash the ICS fastboot files before the new OTA will take. The problem before was safestrap changed something, somewhere (logwrapper maybe?), that did not get changed back after uninstalling the safestrap recovery and app. MAYBE this has been changed/fixed in the new versions of safestrap? Pretty sure we were on version 2.x at the time. You can always try without fastbooting and see what happens. Won't hurt anything. If you do need to fastboot, use jsnweitzel's utility. It has an option to fastboot without wiping data. That's what I'm planning on doing. It should still fix whatever safestrap changed.
Sent from my Droid 4 - LiquidSmooth
Click to expand...
Click to collapse
In doing that it froze on step 3 of 17 mbmloader. Over night. When disconnected and tried again the battery was to dead. Plugged into wall charger now. Should i try again when its fully charged??
Sent from my DROID4 using xda app-developers app
rruleford said:
In doing that it froze on step 3 of 17 mbmloader. Over night. When disconnected and tried again the battery was to dead. Plugged into wall charger now. Should i try again when its fully charged??
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
Yes. Never try to flash a fastboot or sbf file without making sure you have PLENTY of charge. Same goes for backing up and ROM flashing. You never want your phone to die in the middle of a flash.
Sent from my Droid 4 - LiquidSmooth
I think the most important thing to do is grab the update file and post it on Mediafire or similar so that the rest of us can have it
Hey guys. I ran into some trouble trying to root my note 3 and got this message. Now the phone won't turn on our connect to kies to try to repair it. I have the Samsung drivers installed and I believe I followed the directions closely. Can any of you tell me how to get back to factory settings or all the way through the root process. I'm stuck at this screen for now. Any help would be awesome.
Sent from my Nexus 7 using xda app-developers
Try using the one click oding to get back to the stock firmware. Put the phone in download mode and flash the first step of the root procedure and then stop and make sure your phone will work in stock form first before you try rooting it again.
Quickvic30 said:
Try using the one click oding to get back to the stock firmware. Put the phone in download mode and flash the first step of the root procedure and then stop and make sure your phone will work in stock form first before you try rooting it again.
Click to expand...
Click to collapse
Instead of Pass in a green box, I get Failed in a red box and the progress bar on the phone stops
That's not good, maybe try a new download. Which firmware are you flashing? MI1 or MI9?
That's actually what happened when I tried to root. It would sit forever and fail due to a timeout. What I did is after the failure..I left the phone in dl mode and connected and closed the odin..then relaunched odin and it worked the second time. That's my experience and your mileage may vary..
Same thing!
xavier6303 said:
That's actually what happened when I tried to root. It would sit forever and fail due to a timeout. What I did is after the failure..I left the phone in dl mode and connected and closed the odin..then relaunched odin and it worked the second time. That's my experience and your mileage may vary..
Click to expand...
Click to collapse
The exact same thing happened to me... I tried to install Kies 3 and add the drivers but to no avail. So from there on I just closed everything. Disconnected my note 3, reconnected it, and ran odin once more. It immeadiately passed and rooted my phone.
I have seen that in the past it is the sign of a brick you definitely have to Odin back to stock to fix that
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Yes it happened to me too. I just figured it was my crappy computer so I continued to try and after the 4th try I was able to achieve root status. Like a previous commenter suggested, it's a timed out issue.
Yea. I must have tried a dozen times a dozen different ways and I was stuck. I just said eff it and got a new phone. Debating if I want to try again, but I don't feel like potentially going thru the same heart ache. Really the only reason I care to root this phone is to get rid of those damn bloat ware apps; especially My Magazine.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
alpinesun said:
Instead of Pass in a green box, I get Failed in a red box and the progress bar on the phone stops
Click to expand...
Click to collapse
It was MI9
Sent from my SAMSUNG-SM-N900A using xda app-developers app
alpinesun said:
It was MI9
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
Just went thru this on my Note 3 - chances are youre using a vm on a mac arent you?
Make sure you use a dedicated *windows* machine and not a vm (or at lest not a fusion VM) That was my issue, I havent tried parallels. I grabbed a dedicated win 7 machine and it works perfectly.
I was going to return it of that failed, which luckily it didnt.
Cheers
So I tried rooting my Samsung Galaxy Note 3 SM-N900A with Odin but it went wrong somewhere along the way and now the phone won't start up. When I try to start up, the screen says "firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" But when I tried to recover in Kies, it always gets to the end and then says that the PC can't recognize my mobile device. I can still access download mode but that's about it. I have tried looking EVERYWHERE and there is no solution! someone please help! D:
Also, I found something online that says that I can recover through Odin and I went through the whole process but when I start flashing, it says FAIL so that didn't work for me either
Did you use RDLV on MJ5 to root? If so, that's probably what bricked you.
Sent from my SM-N9005 using Xparent Red Tapatalk 2
U will prolly need to flash from scratch using the pit file
Sent from my SAMSUNG-SM-N900A using Tapatalk 4
antiguangenius said:
U will prolly need to flash from scratch using the pit file
Sent from my SAMSUNG-SM-N900A using Tapatalk 4
Click to expand...
Click to collapse
What's the pit file?
becky0251 said:
What's the pit file?
Click to expand...
Click to collapse
That just showed off why your phone got bricked. Rooting a phone got some responsibility. Let this be a lesson for you and read before you root. You will need to download the stock firmware and flash this through Odin. I guess you still can enter Download mode?
Wi-Fi Issues
I also need some help here... I did successfully root my note 3, however whenever I install a custom rom such as knoxraid or azure, my wi-fi will not work at all.
The wi-fi will be on from a clean flash, but once I try to connect to any network (I've only tried those with passwords), the wi-fi grays out and I can no longer turn it on or off. I haven't encountered anyone else with the same problem, and I have tried deleting the rom partitions and recreating them.
Disclaimer: I don't have enough posts to post in the dev forums, so that's why I'm posting here. Sorry about that.
Dearest Becky, im so sorry girl..
butchya may be fuct for a lil while let me tell ya why..
This same thing happened to me!!
I looked everywhere for an easy solution BUT THERE IS NONE !! Yet.
The reason why is because there are no easy "Odin back to stock files" yet is because at&t is a fn a-hole and locked the bootloader !!
I brikt my shıt about 4 days after I brought it home from costco.
I combed through the interwebs for the 48 hrs straight like a mad tweaker!! because of course this is our 800 dollar babies we're talking about !!
I kept getting the same error message as you are mentioning about the kies update connect your pc blah and so I tool it back to costco and played dumb and said that I got a notification to update and clicked ok and it did some stuff and "now its stuck on this screen with some error??" .. the lady at the kiosk looked it up and down and said someone else had come in last week with the same error message . LoL !!
I walked out of there with a brand new baby !!
Maybe you can do the same thing? Just hoping you are within your return timeframe.
your last but definitely not last worst case scenerio option is to stick your sim card in another phone and wait till someone from our awesome family here finds away around/through that damn bootloader and drops the beautiful Odin+files to give new birth to your 5.7 beast of an angel !!
Hope this helped in any sort of way. Good luck dear Sister!!
Please let us know how it goes. I think there are many brothers and sisters desperate as F and in ypur same predicament.
This is your best bet.
If you can get into download mode or should work
http://forum.xda-developers.com/showthread.php?p=48243768
Sent from my SAMSUNG-SM-N900A using xda app-developers app
mrkhigh said:
This is your best bet.
If you can get into download mode or should work
http://forum.xda-developers.com/showthread.php?p=48243768
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
THANK YOU SO MUCH! this worked :good:
all i did is using kingo, it work perfect.
来自我的 SM-N9005 上的 Tapatalk
Glad it worked
For anyone Reading this thread for similar issues
What probably happened is she attempted to root de LA Vega method while she was on firmware mj5 rdlv method is based on mi9 and die to this it will soft brick your device.
Unfortunately att diff not release an Odin file for mj5 or even put it on kies.
One of or members figured out how to fiddle with the files we have access to to flash a hybrid of mi9 and mj5
Making it possible to more or less recover from an mj5 brick.
Follow his steps completely and you will wind up with a stock rooted os.
But since this is such an odd way to recover I chose to use kingo to root.
Xda doesn't support kingo dir to hour closed they are in their methods and the fact it is not apparent how they are funding themselves. so you'll have to Google it. It was one of the easiest root methods I've done on a device it installs chainfires su. It is completely removable and I personally believe it is the lest chance of a brick method.
Sent from my GT-P3110 using xda app-developers app
Ok, so here's the breakdown:
I was on KK (KNOXRAID 5.1), and wanted to try a different ROM. I always like starting fresh on things, and accidentally went a little too far. I wiped /data, /system/, /cache...everything. So then I lost everything and was always stuck on "No OS installed!". Then I used the guide here: http://forum.xda-developers.com/showthread.php?t=2559715 to kind of restart myself.
That works ok, and now I'm on a rooted stock MJ5. My next thing was to try to get to KK again, and so I used the other guide here: http://forum.xda-developers.com/showthread.php?t=2712039. I've tried this literally about eight times, and every time I end up stuck on the boot / splash screen after finishing every single time. I really have no idea why, as I've followed the instructions exactly.
I've also tried going from a custom ROM, using different USB ports, etc...no luck.
Would someone mind pointing me in the right direction? I want to be on FireNote.
Some details:
Running Windows 8.1 Pro 64-bit
Using OEM cable
I've attached a screenshot of my "About" screen on my current stock rooted MJ5 setup.
Thank you!!
Here you go follow the link. http://forum.xda-developers.com/showthread.php?t=2627234
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
lildoggs said:
Here you go follow the link. http://forum.xda-developers.com/showthread.php?t=2627234
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm afraid I don't follow? Are you saying that there is a post somewhere in the FireNote thread where the solution is mentioned?
Firenote is based on mj5 so no need to go to kk. Just make a slot in ss then flash it there or if you're a bit of an adventurer flash it on stock slot. Just make a backup first.
posersk8r said:
Firenote is based on mj5 so no need to go to kk. Just make a slot in ss then flash it there or if you're a bit of an adventurer flash it on stock slot. Just make a backup first.
Click to expand...
Click to collapse
Yeah...wish I would have realized that obvious fact early on. Only realized a few hours ago.
Apart from all this though, I just tried it on another computer and everything worked great. Don't know what's going on with my laptop, but the desktop worked great. Problem solved.
Thanks anyway everyone!
Long story short, I was trying to install Dynamic Kat but it wouldn't work. Each time I would try to install SS 3.72, it wouldn't boot into recovery. If I tried to flash the ROM with SS 3.70, the ROM wouldn't boot--it would just get stuck on a black screen with a blue LED. I was advised to flash Odin and start over. I've been trying to flash stock with several files, however nothing is working (N900AUCUBMI9_OneClickBin.exe). It fails everytime.
Anybody know what I can do to resolve this issue? Needless to say, my phone is soft-bricked at the moment.
Are you able to get into safe strap at all?
As in safe strap recovery.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Thank you for your response.
I actually got it resolved. I was on a ROM which I thought was 4.4.2, however it was 4.3 so it was causing a bunch of problems. All sorted out now
Glad you got it figured out.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app