When I got this about two months ago, I went on trying to root it, but I only was successful in flashing TWRP. Rooting it seemed to fail every time I tried. So It has TWRP but not rooted. Unfortunately, yesterday I accidentally wiped out everything (via TWRP) including the OS itself. So now, it can't be booted, but I've found the two firmware for J7 on SamMobile which are for China. I had both of them downloaded to my computer and flashed them using the latest Odin3_v3.10.7. I did the latest version first, which failed. So, I tried the older but it failed just like the first.
What should I do?
Sorry, I just figured that I was installing the wrong firmware. Mine is J700H not J7008, so please ignore and close this.
Mod Edit
Thread Closed - At op request
ronnie498
Senior Moderator
Related
Hi xda!
I've been reading lots of posts from the shadows and this is my first reach out for help. I am fully aware that I most likely bricked my phone due to carelessness. The short version of the story is that after 1.5 years of having a happily rooted note 2 with 4.1.? firmware, I decided to upgrade to 4.4. When I finished the upgrades (after one or two failed upgrades), I blindly tried to flash route66 to root (I know... I was exhausted from travelling). Well, this gave me the "verizon hates what you did and you need to bring it to the store.." message. I thought, f-u verizon, I can recover from this. To the internet!!!
galaxyNote2root.com was my primary source of information and I downloaded the stock firmware as instructed. I had been using Odin3 1.85 before transforming this great device into an $800 paperweight. When I tried to flash the stock firmware, it would hang or fail right at the beginning. I decided to download Odin 3.07 and try from there. When I flashed, it made it most of the way (99%ish) and would fail at the end.
Back to the forums. I found androidcentral and xda-developers. I dug through so many similar stories to mine and found many of the same instructions which weren't working for me. One new suggestion I tried, which was deemed a last-resort solution by some was to flash the stock partition. This was successful when I flashed it, but I still got continued failures on the stock rom.
I have taken the phone to a "tech" booth at the mall... waste of time. Before I give up and sell a bricked note 2 for scrap, does anyone have any suggestions or know any wizards I can bring this to?
The files I've tried to flash (downloaded multiple times from multiple sources to ensure a good download) are below:
Note2-CWM-6.0.4.3-SCH-i605.tar
Samsung-Driver.exe
sch-i605-16gb.pit
I605VRAMC3_I605VZWAMC3_VZW
Odin3v185
Odin307
root66_VZW_stock_system.tar
I605VRAMC3_I605VZWAMC3_VZW.zip
Thanks for reading!
Edit: found a thread to go through that I hadn't seen before. http://forum.xda-developers.com/showthread.php?t=2296441&page=2
Can't flash anything now. Tried to flash the bootloader in Odin. When I get home, I can post the bootloader file I tried to flash. I can still get to download mode, but flashing in Odin won't even kick off the progress bar (I left it running for hours).
Now seeking out a wizard.
So I rooted my s3 t999 so I could get cyaneginemod. I used the flashing rom way, and it didn't work,(i used twerp recovery) it kept saying failed, and then I went to the easier way of installing the rom with, the new cyaneinge mod app, (I'm still rooted). Then after waiting for it too finish my phone rebooted, but cyaneinge was not on it, instead it came with a page that said root missing I clicked on yes fix the missing root, n well nothing happens I was back on touchwiz, superuser was their but Samsung Knox kept it from doing anything but I used supersu to disable it. I thought that knox was keeping the cyaneinge mod app from working, so I decided to downgrade to 4.1 when knox didn't exist, bless that time, but I couldn't since odin kept failing at flashing a stock rom, I did this soo msoon times I went through every firm ware n back to 4.3, it kept failing, im pretty sure its boot locked, but the root is also limited, every time I reboot n go to recovery n leave it asked me if it should fix the missing root, but yes or no, it wont change, n every time I reboot it says optimizing apps 0 of 48, it takes at least 5 min to go through. N after going through every forum, YouTube video, asking friends, I still can't find a solution, n im stuck on a screwd up root version of 4.3 plz help
You cannot flash an older firmware once you are on 4.3. What was the error message you got when flashing the rom?
serio22 said:
You cannot flash an older firmware once you are on 4.3. What was the error message you got when flashing the rom?
Click to expand...
Click to collapse
i don't remember but I used twrp n as I Was flashing through rom it said failed, same thing when I flashed 4.3 stock firmware on odin later
If you have Kies that will give you problems with Odin. And make sure you have latest twrp
Reflash your current firmware with Odin. Then flash recovery, then the rom. No need to root first.
If the rom flash fails, you need to post the exact error it gives, and attach the recovery.log or theres little we can do to help.
We could start throwing out guesses, but there could be dozens of things potentiality causing your problem.
I decided to un-root and push the Lollipop update today, but it took all day thanks to alot of issues. I figured I would start this thread to help others along with upgrading from KitKat.
So alot of the tutorials you will come across for un-rooting and flashing back to stock using ODIN, so your phone will update, then rooting Lollipop so you can push custom ROMS are INCORRECT. After updating to Lollipop, alot of tutorials said to re-flash the stock Lollipop firmware, then immediately flash CF-Auto-Root and then TWRP Recovery. This is WRONG, for two reasons. Firstly, the .tar file used for flashing Lollipop STOCK is the INCORRECT file. I visited FIVE tutorials and every time I would get Force Closes or get stuck in bootloop, this is because if you watch carefully your phone will name itself NOTE 4 instead of 3 by default after flashing firmware from the links. I didnt catch on to what was going on for over 5 hours as I tried again and again with different methods and then following instructions Step-by-Step all unsuccessfully until it hit me. ALL OF THE LINKS ARE POINTING TO THE WRONG FIRMWARE, instead of flashing Note 3 Firmware, you flash Note 4 Stock Lollipop Firmware, which as you can imagine, causes SERIOUS issues with your phones system.
To fix this problem, find the KitKat NF9 4.4.2 Firmware and flash that, then allow your device to update ITSELF to Lollipop VIA official T-Mobile OTA. This is what worked for me. After updating, then I simply use CF-Auto-Root and then TWRP flashes in NORMAL FASHION, allowing restarts IN BETWEEN FLASHES, clearing cache/dalvik after each install, and allowing 10 mins of settle time after every boot. Then I installed a Custom ROM and Mods, and now it all works perfectly.
Let me know if this helps or if you have experienced similar issues.
What are the links to all these incorrect firmwares?
Posting the links would be more informative than suspicions.
Pp.
wallacengineering said:
I decided to un-root and push the Lollipop update today, but it took all day thanks to alot of issues. I figured I would start this thread to help others along with upgrading from KitKat.
So alot of the tutorials you will come across for un-rooting and flashing back to stock using ODIN, so your phone will update, then rooting Lollipop so you can push custom ROMS are INCORRECT. After updating to Lollipop, alot of tutorials said to re-flash the stock Lollipop firmware, then immediately flash CF-Auto-Root and then TWRP Recovery. This is WRONG, for two reasons. Firstly, the .tar file used for flashing Lollipop STOCK is the INCORRECT file. I visited FIVE tutorials and every time I would get Force Closes or get stuck in bootloop, this is because if you watch carefully your phone will name itself NOTE 4 instead of 3 by default after flashing firmware from the links. I didnt catch on to what was going on for over 5 hours as I tried again and again with different methods and then following instructions Step-by-Step all unsuccessfully until it hit me. ALL OF THE LINKS ARE POINTING TO THE WRONG FIRMWARE, instead of flashing Note 3 Firmware, you flash Note 4 Stock Lollipop Firmware, which as you can imagine, causes SERIOUS issues with your phones system.
To fix this problem, find the KitKat NF9 4.4.2 Firmware and flash that, then allow your device to update ITSELF to Lollipop VIA official T-Mobile OTA. This is what worked for me. After updating, then I simply use CF-Auto-Root and then TWRP flashes in NORMAL FASHION, allowing restarts IN BETWEEN FLASHES, clearing cache/dalvik after each install, and allowing 10 mins of settle time after every boot. Then I installed a Custom ROM and Mods, and now it all works perfectly.
Let me know if this helps or if you have experienced similar issues.
Click to expand...
Click to collapse
Yes, could you post the links that you say have the issues?
AxAtAx said:
Yes, could you post the links that you say have the issues?
Click to expand...
Click to collapse
Sure thing guys, A good example would be this guide here: http://forum.xda-developers.com/showthread.php?t=2672393
Really great guide, makes everything nice and easy, until you get past flashing the Lollipop Stock firmware VIA THIS LINK: http://www.sammobile.com/firmwares/database/SM-N900T/ in one of the very first seps.
If you download the N900TUVUFOB6 (Lollipop) Firmware and flash it, you will get alot of random force closes once the ROM boots and settles. If you pay attention after flashing, you will note the device name defaults to Note 4, and there's your clue.
I still cant believe Ive been working on this phone for the past 13 hours trying to get everything working properly. Happily I have found a ROM I like that is INSANELY FAST AND STABLE and I've installed all the Mods that I want. All I need to do at this point is re-download all my apps and set all the settings.
wallacengineering said:
Sure thing guys, A good example would be this guide here: http://forum.xda-developers.com/showthread.php?t=2672393
Really great guide, makes everything nice and easy, until you get past flashing the Lollipop Stock firmware VIA THIS LINK: http://www.sammobile.com/firmwares/database/SM-N900T/ in one of the very first seps.
If you download the N900TUVUFOB6 (Lollipop) Firmware and flash it, you will get alot of random force closes once the ROM boots and settles. If you pay attention after flashing, you will note the device name defaults to Note 4, and there's your clue.
I still cant believe Ive been working on this phone for the past 13 hours trying to get everything working properly. Happily I have found a ROM I like that is INSANELY FAST AND STABLE and I've installed all the Mods that I want. All I need to do at this point is re-download all my apps and set all the settings.
Click to expand...
Click to collapse
I just put that stock rom on my wifes phone a few days ago, and it defaulted to Note 3 on hers. well, never mind, as you have seem to have got it rolling now.:good::good:
I must be taken crazy pills.
Pp. :what:
Can i ever unbrick my note 3
Frustrated at the moment. I've been trying to unbrick my note 3 for 2 days without any luck. I switched it off after after a week of rooting it and bang it wouldn't go past the samsung logo, it restarts itself automatically without going past the samsung logo. I've downloaded countless version of kitkat stock firmware from different sources for my sm-N900T, flashed with odin more than 10 times, followed every instruction about unbricking.
Any help would be greatly appreciated.
boofydon said:
Frustrated at the moment. I've been trying to unbrick my note 3 for 2 days without any luck. I switched it off after after a week of rooting it and bang it wouldn't go past the samsung logo, it restarts itself automatically without going past the samsung logo. I've downloaded countless version of kitkat stock firmware from different sources for my sm-N900T, flashed with odin more than 10 times, followed every instruction about unbricking.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Do you have stock recovery installed and can you get to it? You might want to try wiping cache and doing a factory reset. If that doesn't fix it then maybe try downloading a stock firmware from Sammobile and flashing it with Odin. You might have have an incompatible app that was installed with a previous rom and a wipe of the Data partition might be needed. You will lose all of your data and apps though.
Next step I'd do if none of that worked would be flashing twrp and wiping data, cache and dalvik and hope...
Good luck.
Ravoz88 said:
Do you have stock recovery installed and can you get to it? You might want to try wiping cache and doing a factory reset. If that doesn't fix it then maybe try downloading a stock firmware from Sammobile and flashing it with Odin. You might have have an incompatible app that was installed with a previous rom and a wipe of the Data partition might be needed. You will lose all of your data and apps though.
Next step I'd do if none of that worked would be flashing twrp and wiping data, cache and dalvik and hope...
Good luck.
Click to expand...
Click to collapse
Thank you for your time. I flashed it with a new stock from sammobile but it's still in a boot loop state even though odin always show pass. And when I flashed it with twrp my note 3 was unable to enter recovery mode.
Hello this is my first post on this website, do tell me if I'm posting this in the wrong place.
I've decided to root my phone and install a custom ROM a couple of days of ago.. But I think I installed a ROM for the wrong version of my phone. After I wiped the phone using TWRP I tried installing Resurrect remix.
This is the message that showed when I tried installing Resurrect Remix v5.6:
'This package is for device: t0lte, t0ltexx, GTn7105, t0ltedv, GT-N8105T, t0lteatt, SGH-I317, t0ltetmo, SGH-T899, t0ltecan, t0ltevl, SGH-I317M; this device is *t0ltevzw*'
So when that failed, I rebooted and it was completely reset to a clean phone. I then tried recovering my backup that I made earlier using TWRP in my microSD card. After I done that is when the problem in the title occured...
I can't press anything else but 'OK', but as soon as I press it the pop-up comes right back up again saying S-Suggest has stopped.
I'm new to all this and I would appreciate if any you could give me some insight.
-BTW when I was reading the linked post for the ROM it said to download GAPPS, but there was no download link so I downloaded it separately for android version 6, and queued to install it alongside the ROM. I'm not sure if I was supposed to do this or if it might the cause of the problem. THANKS.
If you downloaded from opengapps for 6.0 then you did it well.
Go to apps manager and clear data for s suggest, it should help
So, I got an A50, and I'm really happy that I did. However, switching from a phone that had TWRP and Magisk is something I am not finding easy, even if the phone is much faster than my old one. So, of course, after thoroughly reading my warranty, which had no mention of not covering software device damage, I decided to to go ahead and try to flash TWRP and then install Magisk. I went ahead and easily figured out that my model is SM-A505FN (which would have been all that I needed for my old phone). Seeing that there were successful attempts at installing TWRP and Magisk on this model, I decided to try it out, but quickly found myself with a soft bricked phone, so off to finding a Stock ROM I went. After booting it up again I did more digging, but that yielded no result, however, I decided to try using Magisk manager to patch the AP file and then tried patching that. Sadly, no luck. I even went as far as trying a few of those programs that would root your phone from your PC, but that proved to be a waste of time as even that didn't work (which I suspected would happen, but whatever).
While fondling with the phone, I noticed something in the recovery. It wrote a50xx and then I realized that that must have been the reason for nothing working. And now we get to the title of this post. Has anybody been successful at rooting or flashing TWRP on an a50xx device, and, if so, would you be so kind as to elaborate on how you did it?
If not, I guess I should either wait, or look into trying to port TWRP to a50xx myself.
Edit: In case I do decide to port TWRP, any help or pointers are welcome.
Hello @BrainReader,
Same problem here! I tried rooting my device (sm-a505fn as well) by flashing the ap-file using magisk manager. I kept ending in a bootloop. I tried the latest version v20.x and even tried v19.3 which should work stable according to this thread: https://forum.xda-developers.com/galaxy-a50s/how-to/guide-root-galaxy-a50s-magisk-v19-3-t4001271.
I hope this thread gets more attention and someone finds a solution for rooting the a50!
Kind regards,
Shademaster639
I have a rooted a505fn twrp is not working but rooting with magisk works fine. Every magisk version above 19.3 is giving problems. The latest magisk give very much reboots. What I did I first installed the newest software with Odin. Then install magisk 19.3 after that I set in magisk the update channel to get no further then 19.3.
That patch the AP file and reflash everything with the patched version.
It works without problems.
You must flash complete firmware stock
Then reflash complete firmware with mm agisk ap