Related
My SkyRocket is rooted and I have CWM installed. If I do a factory Data Reset from the "Privacy" menu within the phone will it set the phone back to its (out of the box) condition and will it take CWM off of the phone? The reason I am asking is because I have read several posts that claim you can not take an OTA update with CWM installed. I would like to have the option to remove CWM from the phone if it will not take the ICS OTA if / when it is finally released. If the factory data reset doesn't remove CWM from the phone, what is the best method of doing so (if it is needed for the OTA). Thank you.
Edit:
OK, I found a post in the "DEV" section with the original I727 factory ROM, which can be flashed via ODIN that should return the phone to its original "out of the box", unrooted, and CWM removed condition incase it is needed for the upcoming ICS update.
My question is: Is it possible to "just" reflash the "original factory recovery" part of the original ROM that came with the phone instead of reflashing the entire ROM, in effect, replacing CWM with the original recovery without disturbing the rest of the phone? This would basically be the reverse of how I installed CWM in the first place. Is this possible? Do the files (just the recovery part) for the 2.3.6 version of the original I727 (Skyrocket) exist in a flashable form file (TAR)? I don't care about the flash counter increasing because this isn't about returning the phone, it is about what might be needed to be done in preperation for an ICS OTA update. I figure these types of questions will only become more frequent the further into the first Quater of 2012 we get, so it will be an advantage to everyone to try and figure a few things out ahead of time. Thanks for any help in this matter.
scott14719 said:
My SkyRocket is rooted and I have CWM installed. If I do a factory Data Reset from the "Privacy" menu within the phone will it set the phone back to its (out of the box) condition and will it take CWM off of the phone? The reason I am asking is because I have read several posts that claim you can not take an OTA update with CWM installed. I would like to have the option to remove CWM from the phone if it will not take the ICS OTA if / when it is finally released. If the factory data reset doesn't remove CWM from the phone, what is the best method of doing so (if it is needed for the OTA). Thank you.
Click to expand...
Click to collapse
no.
factory reset will not touch your recovery, your kernel or your /system
it wipes /data which stores your settings/configuration/user-installed apps
it also wipes /cache
it does NOT touch the actual system ROM, so your root will remain intact, and your CWM will still be there.
Bump...because I added new question(s) to the OP. Thanks.
scott14719 said:
Bump...because I added new question(s) to the OP. Thanks.
Click to expand...
Click to collapse
While I'm not 100% sure, odin will flash back to a stock rom. However the tar that is around is a rogers rom. Ota updates should work.
mimart7 said:
While I'm not 100% sure, odin will flash back to a stock rom. However the tar that is around is a rogers rom. Ota updates should work.
Click to expand...
Click to collapse
This is the thread that has the I727 and the Rogers TARs.
http://forum.xda-developers.com/showthread.php?t=1342348
These are supposed to bring the phones back to the "Out of the Box" condition if flashed through ODIN (if I read it correctly).
What I am looking for is a way (method) to just flash the recovery part of this back to the phone, basically replacing CWM with the phones original Recovery. A reversal of flashing CWM to replace the stock revovery in the first place.
I like CWM and plan to install it back to the phone after the ICS update, but from what I understand (and I know it isn't final until the ICS update is released and someone with CWM tries it), phones with CWM will not take OTA updates.
I am looking for a way to just reflash the "recovery" part so the rest of the phone will remain the same (keep root, data, and applications). A full stock TAR would erase all of that. I know programs like Titanium backup will back these things up and then replace them, but just replacing the "stock revovery" by itself would eliminate the need to do so and should be quicker and easier.
I am on 2.3.6 so it would need to be a working TAR that has the 2.3.6 stock recovery (only) for the AT&T SkyRocket. If it doesn't already exist, I would certainly be willing to "Donate" to a DEV that could create such a working TAR. I bet a 2.3.5 and Rogers version would be popular as well.
If this has been done or can be done please let me know. Thank you.
Read this thread... it has a link to the stock UCKJ2 recovery tar. Not sure if there is any difference between 2.3.5 recovery and 2.3.6 recovery, however. Hope this helps: http://forum.xda-developers.com/showthread.php?t=1360943
just download the ics rom and load it up when it comes out. it'll be the same rom but you'll still be rooted.
The stock recovery.tar here works on 2.3.5 and 2.3.6 in order to take an ota update you need to flash the stock recovery.tar with odin, and have all bloatware intact. http://forum.xda-developers.com/showthread.php?t=1360943
DoctorQMM said:
Read this thread... it has a link to the stock UCKJ2 recovery tar. Not sure if there is any difference between 2.3.5 recovery and 2.3.6 recovery, however. Hope this helps: http://forum.xda-developers.com/showthread.php?t=1360943
Click to expand...
Click to collapse
silver03wrx said:
The stock recovery.tar here works on 2.3.5 and 2.3.6 in order to take an ota update you need to flash the stock recovery.tar with odin, and have all bloatware intact. http://forum.xda-developers.com/showthread.php?t=1360943
Click to expand...
Click to collapse
Thanks to both of you. This is exactly what I was looking for. I may just wait for the ICS ROM to surface and flash it, but if I want to take the OTA ICS update, this will be very helpful. As promised, I will go and "Donate" to the person that provided this TAR. Again. thanks.
I'm confused now. So I bought this phone used it, rooted it, used da_g's kernel, flashed the UCLA modem and used stockmod rom. now i need to get it back to stock.
i removed the sd card, then did the ODIN instructions and went into download mode and flashed it 'back to stock.' after reboot all my stuff is still on there; so i went into privacy and formatted erased everything. rebooted now i'm at my screen and i went to about, android version 2.3.5, baseband version i727ucla3, kernel 2.6.35.11, build number GINGERBREAD.UCKJ2.
why is my baseband version still at ucla3? i thought flashing the ODIN stock it would set everything back to stock. basically i want to give this to a family member but i want it in the condition that it truly is stock and they can run updates just fine. i ran the 'software update' to try to get the OTA for 2.3.6 but it said 'Current software is up to date' -- isn't the newest 2.3.6.. is my baseband preventing the update. is my kernel back to stock? can i ODIN 2.3.6 stock straight to the device?
also why cant i get back into the 'download mode' i saw previously, all i get when i hold vol up and down is an 'android recovery 3e' what is that.. if i can't get download mode how can i ODIN? im thinking i need to CWM this guy to flash the old baseband then do the process over again to get stock rom and stock kernel... help!
thanks in advance.
Download 'root check free' and see what it says. Also make sure the superuser app is uninstalled
haroonie said:
I'm confused now. So I bought this phone used it, rooted it, used da_g's kernel, flashed the UCLA modem and used stockmod rom. now i need to get it back to stock.
i removed the sd card, then did the ODIN instructions and went into download mode and flashed it 'back to stock.' after reboot all my stuff is still on there; so i went into privacy and formatted erased everything. rebooted now i'm at my screen and i went to about, android version 2.3.5, baseband version i727ucla3, kernel 2.6.35.11, build number GINGERBREAD.UCKJ2.
why is my baseband version still at ucla3? i thought flashing the ODIN stock it would set everything back to stock. basically i want to give this to a family member but i want it in the condition that it truly is stock and they can run updates just fine. i ran the 'software update' to try to get the OTA for 2.3.6 but it said 'Current software is up to date' -- isn't the newest 2.3.6.. is my baseband preventing the update. is my kernel back to stock? can i ODIN 2.3.6 stock straight to the device?
also why cant i get back into the 'download mode' i saw previously, all i get when i hold vol up and down is an 'android recovery 3e' what is that.. if i can't get download mode how can i ODIN? im thinking i need to CWM this guy to flash the old baseband then do the process over again to get stock rom and stock kernel... help!
thanks in advance.
Click to expand...
Click to collapse
My best advice for you is to do more reading before you really mess something up. If you don't know the difference between 3e recovery -vs- CWM you haven't read nearly enough to do what you want to do. I am not telling you this to be a smart-a*s, but because I don't want to see you brick your phone. And, almost everyhting you have asked has been discussed in detail.
The modem / radio (baseband) lives on its own little partician so you will probably need to flash the radio you want by itself (while you still have CWM). You can find the different radio zips in the "Radio" thread in the "Dev" section.
But you will first need CWM back. You will need to be rooted to have CWM and you can get CWM (after root) by using ROM manager to download it or you can ODIN CWM if you use Copperhed's root method.
Once you are rooted and have CWM installed, you can flash whichever modem / radio you want. Then, go to K0nane's "Return to stock" thread and follow the directions completely! Read the entire thread first...JUST DO IT!
Once you are back to stock and have the modem you want, use ODIN to install the 3e recovery (original Samsung revovery) back to your phone. There is a thread that has the 3e recovery .TAR but you will have to do a search to find it.
THEN...you will be back to stock. Of course the AT&T 2.3.6 updates have been pulled (again, discussed in many threads) so you probably won't get the OTA update anyway. But it won't hurt to check. Again, read everything before you do anything and if you still have questions after reading everything...ask before you jump.
Good luck.
android recovery 3e is recovery mode. Holding the volume keys + power button is how you get into recovery, not download mode. To get into download mode:
1 - power off the phone.
2 - plug in your USB cable into your computer/laptop (but not the phone yet)
3 - now hold down the volume keys and plug in the usb cable to the phone while still holding down the volume keys. The phone will vibrate and you can release the volume keys once you see that you're in download mode. I can't remember, but it might actually just be the volume down key and not both.
If that still doesnt work, try taking out the battery and then reinserting it after you power off the phone. Then try again.
scott14719 said:
My best advice for you is to do more reading before you really mess something up.
Click to expand...
Click to collapse
m4570d0n said:
android recovery 3e is recovery mode. Holding the volume keys + power button is how you get into recovery, not download mode. To get into download mode:
Click to expand...
Click to collapse
Thanks for the help, very informative and you basically confirmed what i was thinking. i come from the iOS world where the firmware files when restored it was back to stock, contained the os/modem fw and kernel; plus wiped everything so that just added to the confusion!
so here's how i think it works - your post says the modem, kernel, OS & recovery all live on separate partitions and since some aren't contained in K0nane's stock ODIN; i need to be sure to flash each to be considered "fully stock." if you do K0nane's stock ODIN (does not contain modem, but has orig 3e recovery, kernel, OS) and it is incompatible with the existing modem; you could be in deep sh*t or a brick. also if you flash stock ODIN, you loose the ability to flash kernel or modem because you're now unrooted and without cwm to do that...
two questions - where in android can i see if i'm truly on stock kernel because can't the build string be spoofed? if i restore my cwm backup from post-root-stock state, does that restore / contain modem or kernel?
TIA again.
haroonie said:
Thanks for the help, very informative and you basically confirmed what i was thinking. i come from the iOS world where the firmware files when restored it was back to stock, contained the os/modem fw and kernel; plus wiped everything so that just added to the confusion!
so here's how i think it works - your post says the modem, kernel, OS & recovery all live on separate partitions and since some aren't contained in K0nane's stock ODIN; i need to be sure to flash each to be considered "fully stock." if you do K0nane's stock ODIN (does not contain modem, but has orig 3e recovery, kernel, OS) and it is incompatible with the existing modem; you could be in deep sh*t or a brick. also if you flash stock ODIN, you loose the ability to flash kernel or modem because you're now unrooted and without cwm to do that...
two questions - where in android can i see if i'm truly on stock kernel because can't the build string be spoofed? if i restore my cwm backup from post-root-stock state, does that restore / contain modem or kernel?
TIA again.
Click to expand...
Click to collapse
OK, I see K0nane's thread has the .TAR stock (Odin flash) and apparently already has the 3e recovery included so if you use K0nane's .TAR, you should not have to re-root or install CWM after the flash. So the only reason you would need to re-root and install CWM is if the modem still remains unchanged.
If the modem (radio) is still wrong after the "return to stock .TAR Odin flash, you will need to do what I wrote above (ie. re-root and install CWM) then flash the correct radio through CWM, then re-odin the return to stock .TAR. Others have reported that they were able to get the OTA update (when it was available) using this method. Maybe a .TAR (ODIN flashable modem) exists, but I'm not sure if I've read anything about anyone trying it if it does. If it does, and it works, you can use ODIN to flash the radio as well.
Yes, the modem itself does live on a different partician. Some custom ROMS include the modem and a script for installing it, but usually mention this up front. If the modem doesn't change after a ROM flash, it must be flashed seperately. I've never seen a phone bricked because of a modem mismatch with a ROM (as long as it is an AT&T (I727) skyrocket ROM and modem). But there may be issues with lost data connectivity or APNs.
But you are on the right path, just make sure you read everything and you will be fine.
As far as spoofing the build, I guess the only way to be sure if it is 100% stock is if you restore a nandroid (if you made one) and then ODIN 3e recovery. Or if you use Kies to reurn to stock.
scott14719 said:
But you are on the right path, just make sure you read everything and you will be fine.
As far as spoofing the build, I guess the only way to be sure if it is 100% stock is if you restore a nandroid (if you made one) and then ODIN 3e recovery. Or if you use Kies to reurn to stock.
Click to expand...
Click to collapse
Thanks for the details man, really appreciate it. I read through the threads you suggested and they helped, but no mention of modem. After my initial k0nane stock flash, modem was incorrect so i did the below steps and everything looks good. Still no OTA, but thats fine because it may be because of other reasons (2.3.6 pulled).
You mentioned 100% stock if i have my nandroid, but i would still have to 'un-root' my device afterwards. (i could then just goto settings > privacy > factory data reset would delete everything including the root then?) i am under the impression you needed to be rooted to create a nandroid so you would be restoring to the rooted state. is it true if you restore a nandroid you restore all partitions including the modem and kernel then?
Here's how i finally went back to stock when my device was not rooted but had a different modem.
0. DO NOT ODIN WITH RE-PARTITION OPTION ON, UN-CHECK THIS!
1. re-rooted with superoneclick SuperOneClickv2.3.3-ShortFuse.zip
2. odin to enable cwm SkyrocketCWMrecovery.tar
3. use cwm to flash modem to stock ATTKJ2 Radio_RIL__I727ATTKJ2.zip
4. use cwm to wipe data/factory reset
5. odin k0nane's stock SGH-I727-UCKJ2-k0nane.tar
6. verify in about section modem, kernel and software versions.
7. Voila!
So i did something stupid right after rooting my Relay. I deleted basic stock files that are necessary for the phone to function properly. I was able to copy them from my current phone (rooted T-Mobile G2/Desire Z) onto an SD card and in turn push them back onto my Relay. My problem is that I still get error messages constantly after boot up and the simplest tasks can take hours (not to mention I can't use phone, contacts, messaging). I have seen all over the web (and XDA) about unrooting the phone and retuning it to stock. I was thinking that I could unroot, then reroot my Relay and that will solve my problem.
I was all set to unroot when I encountered yet another issue. Samsung-updates.com and sammobile both direct you to download the firmware files from hotfile. Hotfile has been shut down due to copyright infringement. Where I can find the stock firmware files now that hotfile has been shut down?
Please help me as I anxiously await using my new phone without the extra bloatware!
Thank you,
RockinRita
RockinRita said:
I was all set to unroot when I encountered yet another issue. Samsung-updates.com and sammobile both direct you to download the firmware files from hotfile. Hotfile has been shut down due to copyright infringement. Where I can find the stock firmware files now that hotfile has been shut down?
Click to expand...
Click to collapse
Would Samsung's Kies software be able to restore it to stock, or is it too far gone for Kies to work?
Bobby Tables said:
Would Samsung's Kies software be able to restore it to stock, or is it too far gone for Kies to work?
Click to expand...
Click to collapse
Without the stock files wouldn't Kies be pointless?
The easiest way I've found to completely revert to stock, is to get a CWM flashable version of the unmodified stock rom (From the straight system image, not an update.zip reformated image) and a CWM flashable version of the stock recovery. Flash those in. If you want to reset your flash counter, make certain to also flash a su binary of some form (I personally prefer SuperSU, since it's so easy to clear out, run triangle away, then uninstall your su app properly.
http://forum.xda-developers.com/showpost.php?p=48581775&postcount=6
I've just put up recovery and system flashables of Stock JB.
Pushing on a Relay
RockinRita said:
So i did something stupid right after rooting my Relay. I deleted basic stock files that are necessary for the phone to function properly. I was able to copy them from my current phone (rooted T-Mobile G2/Desire Z) onto an SD card and in turn push them back onto my Relay.
Click to expand...
Click to collapse
I did a very similar thing to my Relay and I can only get it boot off of the SD card. I am curious how you performed the push. I assumed that you
used adb push, but how?
Thanks,
Lou
scopedial said:
I did a very similar thing to my Relay and I can only get it boot off of the SD card. I am curious how you performed the push. I assumed that you used adb push, but how?
Thanks,
Lou
Click to expand...
Click to collapse
I copied the files from my rooted HTC Desire Z/ T-Mobile G2 to a spare SD card I have and then I inserted that card into my Relay and started it up. It took me a few hours to get passed all the error messages that constantly pop up. And then I went into my files, external SD and moved the files over to the system folder on the Relay. After several reboots, the error messages still are coming up which I why I need to unroot it and reroot it.
Magamo said:
The easiest way I've found to completely revert to stock, is to get a CWM flashable version of the unmodified stock rom (From the straight system image, not an update.zip reformated image) and a CWM flashable version of the stock recovery. Flash those in. If you want to reset your flash counter, make certain to also flash a su binary of some form (I personally prefer SuperSU, since it's so easy to clear out, run triangle away, then uninstall your su app properly.
http://forum.xda-developers.com/showpost.php?p=48581775&postcount=6
I've just put up recovery and system flashables of Stock JB.
Click to expand...
Click to collapse
You may have just saved me, Magamo! Thank you for saving them to Drive! Once I get on my old slow Dell laptop (i'm on my Chromebook now- which unfortunately doesn't support most things) I'll try to flash your files and update you here since I cannot comment on your post as I have not posted enough myself.
Stock ROM Restore Method I Used
Magamo said:
The easiest way I've found to completely revert to stock, is to get a CWM flashable version of the unmodified stock rom (From the straight system image, not an update.zip reformated image) and a CWM flashable version of the stock recovery. Flash those in. If you want to reset your flash counter, make certain to also flash a su binary of some form (I personally prefer SuperSU, since it's so easy to clear out, run triangle away, then uninstall your su app properly.
http://forum.xda-developers.com/showpost.php?p=48581775&postcount=6
I've just put up recovery and system flashables of Stock JB.
Click to expand...
Click to collapse
You could also use Odin to flash a md5 sum of T699UVBMC5_HOME using the download mode of the Relay. Place in PDA, and tick off the Auto Reboot and F. Reset Time and hit start. Make sure you have the drivers required to do this. I think they're included with Kies. In my case, I used CWM to format /system, then I used download mode. However, I had to reset my device. AND CWM (plus root access) was erased after the stock restore. I didn't miss an important detail, did I?
furboom1240 said:
You could also use Odin to flash a md5 sum of T699UVBMC5_HOME using the download mode of the Relay. Place in PDA, and tick off the Auto Reboot and F. Reset Time and hit start. Make sure you have the drivers required to do this. I think they're included with Kies. In my case, I used CWM to format /system, then I used download mode. However, I had to reset my device. AND CWM (plus root access) was erased after the stock restore. I didn't miss an important detail, did I?
Click to expand...
Click to collapse
I'll be honest, you've got me on this one. I've never used ODIN, and am not well versed in its use. But yes, this is sounds like a more technical way of doing it without the CWM flashables I've mentioned. -- Impossible in some situations. For example, my fiancee's phone's USB port has died for all purposes other than charging, So if I'm to send it in for a warranty repair, I'll have to use the method I posted.
Confused here
Magamo said:
The easiest way I've found to completely revert to stock, is to get a CWM flashable version of the unmodified stock rom (From the straight system image, not an update.zip reformated image) and a CWM flashable version of the stock recovery. Flash those in. If you want to reset your flash counter, make certain to also flash a su binary of some form (I personally prefer SuperSU, since it's so easy to clear out, run triangle away, then uninstall your su app properly.
http://forum.xda-developers.com/showpost.php?p=48581775&postcount=6
I've just put up recovery and system flashables of Stock JB.
Click to expand...
Click to collapse
Magamo,
I'm sorry, but I'm still totally confused here. Not sure how to flash the files in. I downloaded Kies and both of the zip files from your post. Successfully updated the firmware and my error messages are gone, but I don't have CWM on it. I extracted your files, but now what? I'm not very technologically inclined so this is all Greek to me.
furboom1240 said:
You could also use Odin to flash a md5 sum of T699UVBMC5_HOME using the download mode of the Relay. Place in PDA, and tick off the Auto Reboot and F. Reset Time and hit start. Make sure you have the drivers required to do this. I think they're included with Kies. In my case, I used CWM to format /system, then I used download mode. However, I had to reset my device. AND CWM (plus root access) was erased after the stock restore. I didn't miss an important detail, did I?
Click to expand...
Click to collapse
furboom,
What is T699UVBMC5_HOME? How do I get the md5 sum of it? How do I use CWM to format /system? How do I get to stock restore? Again, I'm sorry for asking so many questions, i just have no clue what I'm doing here.
Thanks,
Rockin Rita
RockinRita said:
Magamo,
I'm sorry, but I'm still totally confused here. Not sure how to flash the files in. I downloaded Kies and both of the zip files from your post. Successfully updated the firmware and my error messages are gone, but I don't have CWM on it. I extracted your files, but now what? I'm not very technologically inclined so this is all Greek to me.
furboom,
What is T699UVBMC5_HOME? How do I get the md5 sum of it? How do I use CWM to format /system? How do I get to stock restore? Again, I'm sorry for asking so many questions, i just have no clue what I'm doing here.
Thanks,
Rockin Rita
Click to expand...
Click to collapse
If you don't have CWM, or some other custom recovery running on this, how did you get root in the first place? The easiest way to get root is to use heimdall or ODIN to flash CWM or another custom recovery, then flash Superuser or SuperSU using your new custom recovery.
The .zip files I linked are only meant to be flashed through recovery. Not Kies, not ODIN, not any other method.
Got it!!
With the help of this site (http://www.celldekho.com/how-to-unroot-samsung-galaxy-s-relay-4g/) and the file it linked to on rapidshare, along with your tip Magamo, I was able to unroot my Relay successfully. I'll reroot it later when I have the time and make sure not to delete important files LOL Thanks so much for the help!
What are my alternatives now?
Previously I was running CleanRom7 – but somehow must taken enough of update to somehow have locked the bootloader:
I’m currently running a “official Samsung” version that is 4.1.2.
I can do the following:
• Flash Root
• Flash a new recovery – used the latest CWM version 2.6.3.1
• Any attempt to either flash the latest ML1 or old CleanRom7 don’t successfully boot.
• At that point I can ODIN back to the 4.1.2 official Samsung version
The download screen looks like this:
Product Name: ICH-I535
Custom Binary Download: Yes (2 count)
Current Binary: Samsung Official
System Status: Official
Qualcom Secureboot: Enable
I’m constantly getting asked by some app if I want to do the OTA upgrade, I have been postponing for 1 hour
Question is given these 2 alternatives, what are the opinions to these two questions:
At this point should I just either ODIN or flash the latest ML1 upgrade and then root?
Or
Stay on 4.1.2?
bgbird said:
What are my alternatives now?
Previously I was running CleanRom7 – but somehow must taken enough of update to somehow have locked the bootloader:
I’m currently running a “official Samsung” version that is 4.1.2.
I can do the following:
• Flash Root
• Flash a new recovery – used the latest CWM version 2.6.3.1
• Any attempt to either flash the latest ML1 or old CleanRom7 don’t successfully boot.
• At that point I can ODIN back to the 4.1.2 official Samsung version
The download screen looks like this:
Product Name: ICH-I535
Custom Binary Download: Yes (2 count)
Current Binary: Samsung Official
System Status: Official
Qualcom Secureboot: Enable
I’m constantly getting asked by some app if I want to do the OTA upgrade, I have been postponing for 1 hour
Question is given these 2 alternatives, what are the opinions to these two questions:
At this point should I just either ODIN or flash the latest ML1 upgrade and then root?
Or
Stay on 4.1.2?
Click to expand...
Click to collapse
Ok, The question is, do you still want to flash custom rom/kernel?? If you do and since you're still on 4.1.2 you still can unlock the bootloader and flash custom 4.3 rom (with unlocked bootloader) for the 4.3 experience/look & feel.
More info
buhohitr said:
Ok, The question is, do you still want to flash custom rom/kernel?? If you do and since you're still on 4.1.2 you still can unlock the bootloader and flash custom 4.3 rom (with unlocked bootloader) for the 4.3 experience/look & feel.
Click to expand...
Click to collapse
I'd like a custom rom - but when I tried to flash the ML4.3 offered on this site - or even tried to reflash my old Cleanrom7 that i still had on my external flash memory that previously worked I couldn't boot.
I flashed VRUCML1_Stock_Root_Deodex (12.31.13 downloaded from the link. MD5 checked OK) this would try to boot - then just go back into recovery (I used the latest version of TWRP and used EZ-Unlock). Of course I wiped the device before I started. I flashed the rom and observed all of the successful messages during the flash. I never caught the really little blue message that flashed at the beginning of the boot cycle before it went black and rebooted to recovery. At that point I wiped again and flashed Cleanrom 7. It flashed, then started the installer that let me pick all sorts of apps. When I tried to boot - it just hung on the Samsung SIII banner that appears shortly after boot. I let it sit there for about an hour before pulling the battery. Then I ODINed back the the 4.1.2 version that I'm running now.
I tried this several times - even going as far as installing CRP recovery - same result.
So I'm about our of ideas...
bgbird said:
I'd like a custom rom - but when I tried to flash the ML4.3 offered on this site - or even tried to reflash my old Cleanrom7 that i still had on my external flash memory that previously worked I couldn't boot.
I flashed VRUCML1_Stock_Root_Deodex (12.31.13 downloaded from the link. MD5 checked OK) this would try to boot - then just go back into recovery (I used the latest version of TWRP and used EZ-Unlock). Of course I wiped the device before I started. I flashed the rom and observed all of the successful messages during the flash. I never caught the really little blue message that flashed at the beginning of the boot cycle before it went black and rebooted to recovery. At that point I wiped again and flashed Cleanrom 7. It flashed, then started the installer that let me pick all sorts of apps. When I tried to boot - it just hung on the Samsung SIII banner that appears shortly after boot. I let it sit there for about an hour before pulling the battery. Then I ODINed back the the 4.1.2 version that I'm running now.
I tried this several times - even going as far as installing CRP recovery - same result.
So I'm about our of ideas...
Click to expand...
Click to collapse
When you flashed back to 4.1.2 and it's working fine, at this point check to see if your bootloader is unlocked (even unlock tool said unlocked, you need to verify that it's unlocked). If it's not what ever you flash will not work.
buhohitr said:
When you flashed back to 4.1.2 and it's working fine, at this point check to see if your bootloader is unlocked (even unlock tool said unlocked, you need to verify that it's unlocked). If it's not what ever you flash will not work.
Click to expand...
Click to collapse
I never "flash" back. I have an ODIN image (KIES_HOME_I535VRBMF1_1152558_REV09_user_low_ship.tar.md5 ) that I use. At that point everything is replaced and I'm back to a stock bootloader (at least that's how it looks to me). When I root - then use EZ-Unlock at this point, the bootloader is locked. I suppose that it would be interesting to try to "flash" a 4.1.2 original and see what would happen.
bgbird said:
I never "flash" back. I have an ODIN image (KIES_HOME_I535VRBMF1_1152558_REV09_user_low_ship.tar.md5 ) that I use. At that point everything is replaced and I'm back to a stock bootloader (at least that's how it looks to me). When I root - then use EZ-Unlock at this point, the bootloader is locked. I suppose that it would be interesting to try to "flash" a 4.1.2 original and see what would happen.
Click to expand...
Click to collapse
I believe your image is fine. The key I want to point out is make sure your bootloader is unlocked. After you unlock with EZ-Unlock, boot into download mode and verify that the bootloader is actually unlock, before you proceed to flash anything else.
buhohitr said:
I believe your image is fine. The key I want to point out is make sure your bootloader is unlocked. After you unlock with EZ-Unlock, boot into download mode and verify that the bootloader is actually unlock, before you proceed to flash anything else.
Click to expand...
Click to collapse
OK - I'll try that. What do I look for in download mode that would indicate (or what should I try to do) that would prove that I'm "unlocked"?
boot into Odin mode (download mode) and you shoud see.
buhohitr said:
boot into Odin mode (download mode) and you shoud see.
Click to expand...
Click to collapse
I don't see anything about "unlocked"
when i press the down volume, home and power button I start into ODIN mode.
if i press the down arrow the phone will just re-boot
then i press the up arrow to continue into ODIN (download mode) I get:
:
Product Name: ICH-I535
Custom Binary Download: Yes (3 count)
Current Binary: Customl
System Status: Customl
Qualcom Secureboot: Enable
I still don't see anything about the unlocked bootloader
bgbird said:
I don't see anything about "unlocked"
when i press the down volume, home and power button I start into ODIN mode.
if i press the down arrow the phone will just re-boot
then i press the up arrow to continue into ODIN (download mode) I get:
:
Product Name: ICH-I535
Custom Binary Download: Yes (3 count)
Current Binary: Customl
System Status: Customl
Qualcom Secureboot: Enable
I still don't see anything about the unlocked bootloader
Click to expand...
Click to collapse
This Qualcom Secureboot: Enable - meaning bootloader is locked
buhohitr said:
This Qualcom Secureboot: Enable - meaning bootloader is locked
Click to expand...
Click to collapse
Just as a matter of curiosity, EZ-Unlock reports the bootloader to be “unlocked”. Wonder what’s wrong with that?
So pretty much at this point it appears that the only thing that I can do is to ODIN the official 4.3 tar file or stay on the 4.1.2 file that I ODINed previously.
bgbird said:
Just as a matter of curiosity, EZ-Unlock reports the bootloader to be “unlocked”. Wonder what’s wrong with that?
So pretty much at this point it appears that the only thing that I can do is to ODIN the official 4.3 tar file or stay on the 4.1.2 file that I ODINed previously.
Click to expand...
Click to collapse
Are you rooted? if not it's not going to work.
buhohitr said:
This Qualcom Secureboot: Enable - meaning bootloader is locked
Click to expand...
Click to collapse
I am rooted - I'm sure of that...
I'm also running the latest TWRP recovery.
EZ-Unlock still lets me lock and unlock the bootloader.
I'm also thinking of flashing VRLE6.bootloader.zip, rebooting, doing an EZ-Unlock and seeing what happens.
If that doesn't work - I'll have to decide
1. do I f staying where I'm at - running 4.1.2 ?
or
2. Do I give up and take the softbrick tar file and lock everything up ?
I'm not sure of what are the pros and cons of either alternative
bgbird said:
EZ-Unlock still lets me lock and unlock the bootloader. I'm also thinking of flashing VRLE6.bootloader.zip, rebooting, doing an EZ-Unlock and seeing what happens.
If that doesn't work - I'll have to decide
1. do I f staying where I'm at - running 4.1.2 ?
or
2. Do I give up and take the softbrick tar file and lock everything up ?
I'm not sure of what are the pros and cons of either alternative
Click to expand...
Click to collapse
If you're not rooted, EZ unlock just report false results.
If you like to play with custom rom/kernel, meaning not bug free and become a flashcoholic then stay with 4.1.2
If you want a stable, no headache trouble free then upgrade to 4.3
I upgraded my wife to 4.3 and very happy with the results. Everything just work, performance is very good and smooth, gps locked in seconds...enough said.
buhohitr said:
If you're not rooted, EZ unlock just report false results.
If you like to play with custom rom/kernel, meaning not bug free and become a flashcoholic then stay with 4.1.2
If you want a stable, no headache trouble free then upgrade to 4.3
I upgraded my wife to 4.3 and very happy with the results. Everything just work, performance is very good and smooth, gps locked in seconds...enough said.
Click to expand...
Click to collapse
Even if I had to stay on 4.1.2 I'd want CleanRom7 at least. I used that since July when it came out. I liked the features and customizations. I'd like to continue to flash - however every time that I try ( and you can see the results earlier in the thread) the phone wouldn't boot. I think that some part of the OTA got on the phone. For a period of time, I was constantly nagged to take the upgrade. I think that my son answered "yes" and some part updated - until stopped Cleanrom.
Anyway I tried to reflash CleanRom as well as the non-locked ML1 item. Each time, Samsung flashes, then the ornamental Samsung SIII graphic just sits there. In a normal boot, that only lasts a second. Maybe I'll try it again and let sit there for an hour or two and see if something changes.
bgbird said:
Even if I had to stay on 4.1.2 I'd want CleanRom7 at least. I used that since July when it came out. I liked the features and customizations. I'd like to continue to flash - however every time that I try ( and you can see the results earlier in the thread) the phone wouldn't boot. I think that some part of the OTA got on the phone. For a period of time, I was constantly nagged to take the upgrade. I think that my son answered "yes" and some part updated - until stopped Cleanrom.
Anyway I tried to reflash CleanRom as well as the non-locked ML1 item. Each time, Samsung flashes, then the ornamental Samsung SIII graphic just sits there. In a normal boot, that only lasts a second. Maybe I'll try it again and let sit there for an hour or two and see if something changes.
Click to expand...
Click to collapse
If you are switch from rom to rom, you may have trash residuals. I would wipe cache/dalvik cache/data/system before I flash another rom (clean install), saved me a lot of little issues here and there...
buhohitr said:
If you are switch from rom to rom, you may have trash residuals. I would wipe cache/dalvik cache/data/system before I flash another rom (clean install), saved me a lot of little issues here and there...
Click to expand...
Click to collapse
Formatting your internal SD may also be needed, because 4.3 creates a 0/ folder that 4.1 doesn't have.
Alternatively, philz touch recovery has a 0/folder migration that will clear out that folder when switching.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Formatting your internal SD may also be needed, because 4.3 creates a 0/ folder that 4.1 doesn't have.
Alternatively, philz touch recovery has a 0/folder migration that will clear out that folder when switching.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
two questions?
1. Do you have a link for philz touch recovery?
2. If I format the internal SD - will an nandroid backup still work? I thought that that had to back into an identical file structure...
Also I do a factory reset each time that I flash.
I know that I'm root because EZ-Unlock requires it. If root isn't enabled - it terminates. When Root is enabled, SuperSU asks permission to do the unlock
bgbird said:
two questions?
1. Do you have a link for philz touch recovery?
2. If I format the internal SD - will an nandroid backup still work? I thought that that had to back into an identical file structure...
Click to expand...
Click to collapse
1.
http://forum.xda-developers.com/showthread.php?t=2588639
2. No, The file structure gets completely replaced because a nandroid copies your internal sd card. It'll remake the folder structure.
Sent from my SCH-I535 using Tapatalk 2
Just a quick question to cover all the bases. Which version of EZ Unlock are you using? Version 1.2 is the only one that actually works to unlock your bootloader.
Hey everyone, so I have from what I researched here is a "soft" bricked phone as my recovery mode (TWRP) and download mode works fine but no boot.
First let me say this is the Canadian version of the Note 5 SM-N920W8. I posted here because there is no forum for that version everything seems to be the same and posted under 920T version.
HISTORY OF THE PHONE:
It was a while ago that I rooted but let me describe to the best of my memory how my note 5 ended up in the state that it is in. So stock was lollipop 5.1.1. I flashed the skyhigh kernel which gave root access but had random reeboot issues which led me to flashing TWRP recovery so I could flash boot.img as an image file which did take away the random reeboot problem and removed that red error on startup "kernel is not SEANDROID enforcing". Life was good at this point! Everything worked great woth no issues. I greenified everything and underclocked the cpu with system tuner and used system app removed to manually all the bloatware as I didnt want to start using custom roms I stuck with the stock firmware. Part of the reason that I didnt want to use custom roms is because I started reading up on xposed framework, so I decided to flash it and give it a try. I read the xposed framework thread followed the download link to my version downloaded it and flashed with TWRP. Immediately after this was a bootloop.
TROUBLESHOOTING:
Unfortunately I had no backup in TWRP.. In a panic before researching I started flashing other kernels like arters kernel and I think space x whcih can be used on some note 5s.. which brought back that SEANDROID error message in the bootloop. I flashed the skyhigh kernel but flashing the boot.img didn't get rid of that error message again.
A friend of mine at work recommended that I just wipe everything and flash the stock firmware from sammobile.com with odin since I still have recovery mode then just re root. So I went into TWRP and wiped EVERYTHING. I think there was 4 or 5 boxes in twrp data wipe but I selected all the boxes. Now the phone doesn't even get the Samsung logo on boot or anything but download mode works so I flashed twrp again which loads up. I downloaded my version of the Samsung firmware which was about 1.6gb from sammobile.com. I open odin load the file that I extracted. A tar.md5 file which took longer than normal to load into the AP but I didn't change any settings or anything. Should I have? Because after I hit start it failed. I retried at least 3 times. Does this firmware contain all the AP CP and all the other boxes or do I need to find those separately? Should I just try a custom rom?
Im not sure what to do here I have a completely blank phone but twrp and download mode works so it recoverable right?
I read up on adb sideloader but didn't get too far.. is that worth trying for recovery in this case?
I also read a few threads on here for other samsung versions where they say to flash a PIT file with odin but they all say that it only works specifically for that phone and I couldn't find one for this version of the note 5.
I know the #1 rule here is to research before posting and Ive really made my best attempt to research on here and Google over the last few days but I really need my phone back. Any help is greatly appreciated.
re: phone won't boot
bloewen4 said:
Hey everyone, so I have from what I researched here is a "soft" bricked phone as my recovery mode (TWRP) and download mode works fine but no boot.
First let me say this is the Canadian version of the Note 5 SM-N920W8. I posted here because there is no forum for that version everything seems to be the same and posted under 920T version.
HISTORY OF THE PHONE:
It was a while ago that I rooted but let me describe to the best of my memory how my note 5 ended up in the state that it is in. So stock was lollipop 5.1.1. I flashed the skyhigh kernel which gave root access but had random reeboot issues which led me to flashing TWRP recovery so I could flash boot.img as an image file which did take away the random reeboot problem and removed that red error on startup "kernel is not SEANDROID enforcing". Life was good at this point! Everything worked great woth no issues. I greenified everything and underclocked the cpu with system tuner and used system app removed to manually all the bloatware as I didnt want to start using custom roms I stuck with the stock firmware. Part of the reason that I didnt want to use custom roms is because I started reading up on xposed framework, so I decided to flash it and give it a try. I read the xposed framework thread followed the download link to my version downloaded it and flashed with TWRP. Immediately after this was a bootloop.
TROUBLESHOOTING:
Unfortunately I had no backup in TWRP.. In a panic before researching I started flashing other kernels like arters kernel and I think space x whcih can be used on some note 5s.. which brought back that SEANDROID error message in the bootloop. I flashed the skyhigh kernel but flashing the boot.img didn't get rid of that error message again.
A friend of mine at work recommended that I just wipe everything and flash the stock firmware from sammobile.com with odin since I still have recovery mode then just re root. So I went into TWRP and wiped EVERYTHING. I think there was 4 or 5 boxes in twrp data wipe but I selected all the boxes. Now the phone doesn't even get the Samsung logo on boot or anything but download mode works so I flashed twrp again which loads up. I downloaded my version of the Samsung firmware which was about 1.6gb from sammobile.com. I open odin load the file that I extracted. A tar.md5 file which took longer than normal to load into the AP but I didn't change any settings or anything. Should I have? Because after I hit start it failed. I retried at least 3 times. Does this firmware contain all the AP CP and all the other boxes or do I need to find those separately? Should I just try a custom rom?
Im not sure what to do here I have a completely blank phone but twrp and download mode works so it recoverable right?
I read up on adb sideloader but didn't get too far.. is that worth trying for recovery in this case?
I also read a few threads on here for other samsung versions where they say to flash a PIT file with odin but they all say that it only works specifically for that phone and I couldn't find one for this version of the note 5.
I know the #1 rule here is to research before posting and Ive really made my best attempt to research on here and Google over the last few days but I really need my phone back. Any help is greatly appreciated.
Click to expand...
Click to collapse
If you have either a custom or stock rom installed or the official Samsung firmware installed
then it should be an easy fix, you must have flashed a incompatible kernel or perhaps you
deleted the kerned. (the phone will not boot without a kernel)
You need to find a compatible kernel and flash it using twrp recovery.
Here is a link you may want to try, it's for kernels for the Note 5 only:
http://forum.xda-developers.com/tmobile-galaxy-note5/orig-development
It might even be better if you were to Odin flash a fresh copy of your Note 5 specific
firmware using download mode, that's the surest way to get your phone working again.
Give it a try...
Good luck,
Have a great day!
Good luck!
Hi thanks for the reply! I did try that already unless flashing a stock firmware is different than putting it in AP as I flashed the kernel. Do I need to select some different optioms in odin since I data wiped everything and need all the necessary files to boot the phone? Oh and I did put the skyhigh kernel back on.
A friend of mine at work recommended that I just wipe everything and flash the stock firmware from sammobile.com with odin since I still have recovery mode then just re root. So I went into TWRP and wiped EVERYTHING. I think there was 4 or 5 boxes in twrp data wipe but I selected all the boxes. Now the phone doesn't even get the Samsung logo on boot or anything but download mode works so I flashed twrp again which loads up. I downloaded my version of the Samsung firmware which was about 1.6gb from sammobile.com. I open odin load the file that I extracted. A tar.md5 file which took longer than normal to load into the AP but I didn't change any settings or anything. Should I have? Because after I hit start it failed. I retried at least 3 times. Does this firmware contain all the AP CP and all the other boxes or do I need to find those separately? Should I just try a custom rom?
Click to expand...
Click to collapse
Unfortunately I had no backup in TWRP.. In a panic before researching I started flashing other kernels like arters kernel and I think space x whcih can be used on some note 5s.. which brought back that SEANDROID error message in the bootloop. I flashed the skyhigh kernel but flashing the boot.img didn't get rid of that error message again
Click to expand...
Click to collapse
re: not sure what you mean
bloewen4 said:
Hi thanks for the reply! I did try that already unless flashing a stock firmware is different than putting it in AP as I flashed the kernel. Do I need to select some different optioms in odin since I data wiped everything and need all the necessary files to boot the phone? Oh and I did put the skyhigh kernel back on.
Click to expand...
Click to collapse
Your best bet is to download the official Note 5 N920T odin flash firmware,
unzip it so you will end up with a TAR.MD5 file.
Then do a full wipe including system, data, cache, dalvik and last but not least
a factory reset in twrp recovery.
Once you do that your phone will be working properly again, flashing a kernel
or flashing firmware is the same process in odin. Use the AP slot.
And now I know what messed up your phone... it was as I posted before either
flashing the wrong kernel or the kernel got deleted who knows how.
That's all I can tell you except if you want the link to the official Samsung
N920T firmware here it is:
http://forum.xda-developers.com/tmo...t/rom-android-6-0-marshmallow-note-5-t3250812
The link also guides you thru the odin flashing process and other important things.
Good luck!
re: not sure what you mean
Quote:
Originally Posted by bloewen4
Hi thanks for the reply! I did try that already unless flashing a stock firmware is different than putting it in AP as I flashed the kernel. Do I need to select some different optioms in odin since I data wiped everything and need all the necessary files to boot the phone? Oh and I did put the skyhigh kernel back on.
Click to expand...
Click to collapse
I was researching some methods of flashing firmware to a completely wiped phone and read somewhere that there is a method to download all the files individually and put them into all the other sections in odin but I guess these tar.md5 files are a package of everything and one file is enough for a completely wiped phone? If all I need to k ow is to download that firmware unzip and flash in AP then awesome So longlong as they both have the same effect.
Your best bet is to download the official Note 5 N920T odin flash firmware,
unzip it so you will end up with a TAR.MD5 file.
Then do a full wipe including system, data, cache, dalvik and last but not least
a factory reset in twrp recovery.
Once you do that your phone will be working properly again, flashing a kernel
Click to expand...
Click to collapse
Just to clarify the order of this; first download that firmware via that link. 2nd wipe everything in twrp except for recovery so I can go back into twrp and factory reset in twrp? This alone will boot my phone before flashing the firmware? Or do I need to factory reset in twrp then flash that firmware in odin to get a boot? And is this custom firmware do I need to root again after I get boot?
Thanks for the link to that firmware going to be trying this right after work
bloewen4 said:
re: not sure what you mean
Quote:
Originally Posted by bloewen4
Hi thanks for the reply! I did try that already unless flashing a stock firmware is different than putting it in AP as I flashed the kernel. Do I need to select some different optioms in odin since I data wiped everything and need all the necessary files to boot the phone? Oh and I did put the skyhigh kernel back on.
I was researching some methods of flashing firmware to a completely wiped phone and read somewhere that there is a method to download all the files individually and put them into all the other sections in odin but I guess these tar.md5 files are a package of everything and one file is enough for a completely wiped phone? If all I need to k ow is to download that firmware unzip and flash in AP then awesome So longlong as they both have the same effect.
Your best bet is to download the official Note 5 N920T odin flash firmware,
unzip it so you will end up with a TAR.MD5 file.
Then do a full wipe including system, data, cache, dalvik and last but not least
a factory reset in twrp recovery.
Once you do that your phone will be working properly again, flashing a kernel
Just to clarify the order of this; first download that firmware via that link. 2nd wipe everything in twrp except for recovery so I can go back into twrp and factory reset in twrp? This alone will boot my phone before flashing the firmware? Or do I need to factory reset in twrp then flash that firmware in odin to get a boot? And is this custom firmware do I need to root again after I get boot?
Thanks for the link to that firmware going to be trying this right after work
Click to expand...
Click to collapse
Wait. You have a W8 variant. Odin won't flash a T variant on your W8 device, I don't believe. You need to download your carrier specific, hopefully 6.0.1 version, of the firmware for your specific carrier version, and flash that in the latest 3.10.7 version of odin.
---------- Post added at 09:21 PM ---------- Previous post was at 09:08 PM ----------
bloewen4 said:
re: not sure what you mean
Quote:
Originally Posted by bloewen4
Hi thanks for the reply! I did try that already unless flashing a stock firmware is different than putting it in AP as I flashed the kernel. Do I need to select some different optioms in odin since I data wiped everything and need all the necessary files to boot the phone? Oh and I did put the skyhigh kernel back on.
I was researching some methods of flashing firmware to a completely wiped phone and read somewhere that there is a method to download all the files individually and put them into all the other sections in odin but I guess these tar.md5 files are a package of everything and one file is enough for a completely wiped phone? If all I need to k ow is to download that firmware unzip and flash in AP then awesome So longlong as they both have the same effect.
Your best bet is to download the official Note 5 N920T odin flash firmware,
unzip it so you will end up with a TAR.MD5 file.
Then do a full wipe including system, data, cache, dalvik and last but not least
a factory reset in twrp recovery.
Once you do that your phone will be working properly again, flashing a kernel
Just to clarify the order of this; first download that firmware via that link. 2nd wipe everything in twrp except for recovery so I can go back into twrp and factory reset in twrp? This alone will boot my phone before flashing the firmware? Or do I need to factory reset in twrp then flash that firmware in odin to get a boot? And is this custom firmware do I need to root again after I get boot?
Thanks for the link to that firmware going to be trying this right after work
Click to expand...
Click to collapse
What carrier are you on? Go to sammobile and find out exactly what firmware is the latest for your variant on your carrier, for us T variants it's dpd1, but yours will be different, and sammobile is slow so if you can find a mirror somewhere for the stock firmware do that, download it...should be a tar.md5....if you get an error loading it you can often remove the .md5 from the extension...now first reboot recovery and you only need to wipe art/dalvik cache, system, data, cache, and if you want to internal storage but I normally don't...if you wipe efs and everything else you'll be sorry because only thing that will restore it is a full factory odin firmware flash...which is exactly what we're doing...so wipe those partitions then reboot download mode....launch odin and load your downloaded image into the AP slot. Make sure it's at least 3.10.7 version of Odin...when you connect the usb after rebooting to download mode you should see a green/blue box with COM:x (where x is a com port number on your pc) and it should say added...now flash it and wait until it finishes, it'll reboot maybe even a couple times, but it'll eventually make it to the setup screen- from here you can continue stock or flash twrp in odin then recovery flash a rooted kernel for stock rooted or continue with a custom rom, there's a fix in the note 5 gen section for making t/w8 devices work with call audio on intl roms and there's some stock Deodexed stuff at this point and certainly tekhd's mm rom...so from there the choices are yours...but your device is fine you just NEED to flash the correct stock firmware for your variant and use the latest version of odin with a factory usb cable and latest usb drivers from Samsung on your pc when you do it...you'll find links to all this stuff in most of the guides that are abundantly available...
Wait. You have a W8 variant. Odin won't flash a T variant on your W8 device, I don't believe. You need to download your carrier specific, hopefully 6.0.1 version, of the firmware for your specific carrier version, and flash that in the latest 3.10.7 version of odin.
Click to expand...
Click to collapse
I realize I have a W8 and hes providing the firmware for a T. I rooted with a kernel that was for a T version and everything worked fine. I researched rooting note 5 SM-N920W8 and they said do everything the same for the T version because theyre basically identical and isnt much info on the w8 version. So far Ive had no issues flashing everything designed for the T version on my W8. Actually Ive only tried flashing stock w8 firmware from.sammobile.com and got a fail in odin so now Ill try the version MisterJunkie provided me with for the T version unless considering all this you think I should still try a different firmware all together for the W8?
Misterjunky said:
Your best bet is to download the official Note 5 N920T odin flash firmware,
unzip it so you will end up with a TAR.MD5 file.
Then do a full wipe including system, data, cache, dalvik and last but not least
a factory reset in twrp recovery.
Once you do that your phone will be working properly again, flashing a kernel
or flashing firmware is the same process in odin. Use the AP slot.
And now I know what messed up your phone... it was as I posted before either
flashing the wrong kernel or the kernel got deleted who knows how.
That's all I can tell you except if you want the link to the official Samsung
N920T firmware here it is:
http://forum.xda-developers.com/tmo...t/rom-android-6-0-marshmallow-note-5-t3250812
The link also guides you thru the odin flashing process and other important things.
Good luck!
Click to expand...
Click to collapse
Bud, that's not the official tmo pd1 firmware, and I'm not sure if the leaked (alright it would likely run) would be the best here...plus he scares me when he says he cleared EVERYTHING cuz I'm thinking back to exactly how much twrp will wipe, but it's a lot so I fear he's going to need some partitions restored that are only going to come from a full pit file mapping...I don't believe official pd1 would flash in odin, nor would I recommend doing so- I would locate the most recently official firmware to ensure all partitions are restored, then if he doesn't have official mm support he can look into the leak, but if he had official for his variant and carrier that's his best bet to ensure 100% fix and give him a solid foundation to start from if he wants to root, rom, mod, etc
Not to discount your advice, I'd just hate to see him in a worse place than he is...which he's not even bricked YET...but he's starts screwing with wiping efs or messaging with csc stuff from different variants and he could back himself into a corner...
What carrier are you on? Go to sammobile and find out exactly what firmware is the latest for your variant on your carrier, for us T variants it's dpd1, but yours will be different, and sammobile is slow so if you can find a mirror somewhere for the stock firmware do that, download it...should be a tar.md5....if you get an error loading it you can often remove the .md5 from the extension...now first reboot recovery and you only need to wipe art/dalvik cache, system, data, cache, and if you want to internal storage but I normally don't...if you wipe efs and everything else you'll be sorry because only thing that will restore it is a full factory odin firmware flash...which is exactly what we're doing...so wipe those partitions then reboot download mode....launch odin and load your downloaded image into the AP slot. Make sure it's at least 3.10.7 version of Odin...when you connect the usb after rebooting to download mode you should see a green/blue box with COM:x (where x is a com port number on your pc) and it should say added...now flash it and wait until it finishes, it'll reboot maybe even a couple times, but it'll eventually make it to the setup screen- from here you can continue stock or flash twrp in odin then recovery flash a rooted kernel for stock rooted or continue with a custom rom, there's a fix in the note 5 gen section for making t/w8 devices work with call audio on intl roms and there's some stock Deodexed stuff at this point and certainly tekhd's mm rom...so from there the choices are yours...but your device is fine you just NEED to flash the correct stock firmware for your variant and use the latest version of odin with a factory usb cable and latest usb drivers from Samsung on your pc when you do it...you'll find links to all this stuff in most of the guides that are abundantly available...
Click to expand...
Click to collapse
My carrier is Rogers. I did goto sammobile.com already and downloaded and flashed what I thought was the current stock firmware for my 920w8, but I flashed without wiping all data as previously stated. Maybe doing this will allow my firmware to flash? Will try when Im home from work. Will also post the link from sammobile.com for the exact firmware I download just to verify ots the right one.
Yeah I literally wiped everything I checked all the boxes and I remember having to manually type y e s to proceed so yeah pretty serious wipe lol.
I have the latest version of odin 3.10.7 and tried installing drivers on my pc said theyre already installed.
When I connect my phone to usb in download mode it says com:4
I thought also that just flashing the stock firmware would be the solution since I get download mode and twrp I just have a blank phone but as I said I did get the stock firmware from sammobile.com and try but it failed. Maybe I grabbed the wrong one but it looked pretty straightforward. Maybe with MM coming out Wednesday for rogers note 5 Im downloading the wrong version.
Im worried like you wrote earlier that I deleted too much with twrp if I needing mapping partitions and PIT files I will need some serious help that stuff is beyond me.
Go to sammobile and find out exactly what firmware is the latest for your variant on your carrier, for us T variants it's dpd1, but yours will be different, and sammobile is slow so if you can find a mirror somewhere for the stock firmware do that, download it...should be a tar.md5....if you get an error loading it you can often remove the .md5 from the extension...now first reboot recovery and you only need to wipe art/dalvik cache, system, data, cache, and if you want to internal storage but I normally don't...if you wipe efs and everything else you'll be sorry because only thing that will restore it is a full factory odin firmware flash...which is exactly what we're doing...so wipe those partitions then reboot download mode....launch odin and load your downloaded image into the AP slot. Make sure it's at least 3.10.7 version of Odin...when you connect the usb after rebooting to download mode you should see a green/blue box with COM:x (where x is a com port number on your pc) and it should say added...now flash it and wait until it finishes, it'll reboot maybe even a couple times, but it'll eventually make it to the setup screen- from here you can continue stock or flash twrp in odin then recovery flash a rooted kernel for stock rooted or continue with a custom rom
Click to expand...
Click to collapse
Goodmorning, as I mentioned I would try this right after work. Heres what I did.. I verified that I had the 3.10.7 version of odin which I do, checked drivers on pc which I have. I re downloaded the firmware from here http://www.sammobile.com/firmwares/database/SM-N920W8/ Its was the Canadian Rogers version 5.1.1 near the bottom as mm isnt out for rogers yet.. Oh and I checked my cable ot connected another device to my PC.. so after all this I went into twrp wiped everything you mentioned. After that I was looking for the factory reset option in twrp but couldn't find anywhere only restore which I have no rom backups made. Do I need this step?
Went into download mode pressed vol up.. opened odin 3.10.7. I did notice a change after wiping. Its now says com:6 instead of com:4 if that means anything.. I loaded the firmware into AP it took a while to load but it did without errors. Flashed and failed If you need I can copy the error message from odin in here tonight.
Do you think I need to remap partitions as you said earlier? Getting PIT files? Im lost here... appreciate any help
Still with a blank phone, any ideas?
Or if anyone could direct me to another thread that might be useful for re mapping partitions?
Have you tried flashing twrp again in Odin?
I hit too many buttons before when wiping. It even erased my recovery.
Once I had recovery again I could Odin flash the official firmware.
Could try Philz recovery as well.
Sent from my SM-N920T using XDA-Developers mobile app
Yeah I did try that heres the link where I got the firmware and yeah twrp is on there.
Goodmorning, as I mentioned I would try this right after work. Heres what I did.. I verified that I had the 3.10.7 version of odin which I do, checked drivers on pc which I have. I re downloaded the firmware from here http://www.sammobile.com/firmwares/database/SM-N920W8/ Its was the Canadian Rogers version 5.1.1 near the bottom as mm isnt out for rogers yet.. Oh and I checked my cable ot connected another device to my PC.. so after all this I went into twrp wiped everything you mentioned. After that I was looking for the factory reset option in twrp but couldn't find anywhere only restore which I have no rom backups made. Do I need this step?
Went into download mode pressed vol up.. opened odin 3.10.7. I did notice a change after wiping. Its now says com:6 instead of com:4 if that means anything.. I loaded the firmware into AP it took a while to load but it did without errors. Flashed and failed If you need I can copy the error message from odin in here tonight.
Click to expand...
Click to collapse
bloewen4 said:
Yeah I did try that heres the link where I got the firmware and yeah twrp is on there.
Click to expand...
Click to collapse
Since you have twrp on the phone.. Tap to create a backup even if there's no system on it so that you can at least make it create the folder.. Try using adb to push a ROM and kernel to the phone so you can use twrp to flash it. If you can get into the phones storage using Windows then just drop a ROM and kernel for your device in the folder and then use twrp to flash.
By the way.. Use the SkyHigh kernel.
Follow the directions to a T!!
http://forum.xda-developers.com/note5/orig-development/kernel-skyhigh-tw-6-0-1-kernel-t3321646
If you can get into the phones storage using Windows then just drop a ROM and kernel for your device in the folder and then use twrp to flash.
Click to expand...
Click to collapse
I did try immediately to connect with Windows to my phone so I could try flashing stock firmware with twrp but its currently not allowing me access to view storage on Windows though it does connect with odin saying com:6.
Since you have twrp on the phone.. Tap to create a backup even if there's no system on it so that you can at least make it create the folder..
Click to expand...
Click to collapse
I will do this as soon as I am home from work. Will this perhaps allow access with Windows and/or adb sideloader?
Try using adb to push a ROM and kernel to the phone so you can use twrp to flash it.
Click to expand...
Click to collapse
I will be researching how to do this. Have you any threads to learn adb? So basically this will allow me to put ROMS or other files into the internal memory?
By the way.. Use the SkyHigh kernel.
Follow the directions to a T!!
http://forum.xda-developers.com/note...ernel-t3321646
Click to expand...
Click to collapse
Is this the right kernel for SM-N920W8?
* SAME kernel for ALL supported variant !!
** If other party cannot hear voice when on speaker phone ** Then read Post #636
SM-N920 C / CD / G / i [ v3.2 ]
SM-N9200_HK [ v3.2 ]
Click to expand...
Click to collapse
Also Marshmellow isnt out officially for SM-N920W8 so Ill need a kernel for lollipop 5.1.1 unless you suggest to wait for marshmellow then try a mm kernel?
Thanks for helping!
How about this adb sideloader does anyone think that will work to load the firmware? If so any good threads to guode me?
What did you end up doing? I have a similar problem except no recovery mode, just download mode for Odin.
bloewen4 said:
Goodmorning, as I mentioned I would try this right after work. Heres what I did.. I verified that I had the 3.10.7 version of odin which I do, checked drivers on pc which I have. I re downloaded the firmware from here http://www.sammobile.com/firmwares/database/SM-N920W8/ Its was the Canadian Rogers version 5.1.1 near the bottom as mm isnt out for rogers yet.. Oh and I checked my cable ot connected another device to my PC.. so after all this I went into twrp wiped everything you mentioned. After that I was looking for the factory reset option in twrp but couldn't find anywhere only restore which I have no rom backups made. Do I need this step?
Went into download mode pressed vol up.. opened odin 3.10.7. I did notice a change after wiping. Its now says com:6 instead of com:4 if that means anything.. I loaded the firmware into AP it took a while to load but it did without errors. Flashed and failed If you need I can copy the error message from odin in here tonight.
Do you think I need to remap partitions as you said earlier? Getting PIT files? Im lost here... appreciate any help
Click to expand...
Click to collapse
Where did you get your firmware from?
Why oh why did I bother reading through this entire thread, with intentions to help OP. Lol I didnt realize the date till the last post.