[Q] Kind of new to the Rooting, but I need a bit of help. - General Questions and Answers

Okay, so recently this week I rooted my Tmobile Galaxy note 3 SM-N900T model. I installed the Xnote Custom Rom and everything was pretty much fine.
This is where the problem started. I have a mobile app Called Odin Mobile, which I used to actually Custom Rom Flash, because I didn't see the option during the Bootloader to where I'm able to Custom Rom flash it from my external card, so I bought the Odin app to help me do it mobile and use CW Recovery to handle it. Now I went to find a wifi patch, because my wifi would NOT work with this Rom at all, I found a patch to install, so I used Odin Mobile Pro to simply just Flash the install on it and hope it would go through after a bit of research. Now my phone I believe is Paperweight softbrick. It doesn't go past the Xnote KitKat Menu of 4.4.2. I can't do anything, even worse my computer isn't reading my phone to where I can just get the files from my phone or external Microsdcard.
What should I do ? I'm pretty helpless at the moment. I even went to try and find a Stock Rom for my Model number which is the Tmobile Model Number: SM-N900TZWETMB Variant, I haven't been able to locate any, my only hope from what I'm reading, is to find a Stock Rom of 4.4.2 with my model and use Odin and hopefully that works, but I'm not able to locate anything, and the internet here is pretty horrible. If there is anything anyone can do to help me I appreciate it.

Snake2594 said:
Okay, so recently this week I rooted my Tmobile Galaxy note 3 SM-N900T model. I installed the Xnote Custom Rom and everything was pretty much fine.
This is where the problem started. I have a mobile app Called Odin Mobile, which I used to actually Custom Rom Flash, because I didn't see the option during the Bootloader to where I'm able to Custom Rom flash it from my external card, so I bought the Odin app to help me do it mobile and use CW Recovery to handle it. Now I went to find a wifi patch, because my wifi would NOT work with this Rom at all, I found a patch to install, so I used Odin Mobile Pro to simply just Flash the install on it and hope it would go through after a bit of research. Now my phone I believe is Paperweight softbrick. It doesn't go past the Xnote KitKat Menu of 4.4.2. I can't do anything, even worse my computer isn't reading my phone to where I can just get the files from my phone or external Microsdcard.
What should I do ? I'm pretty helpless at the moment. I even went to try and find a Stock Rom for my Model number which is the Tmobile Model Number: SM-N900TZWETMB Variant, I haven't been able to locate any, my only hope from what I'm reading, is to find a Stock Rom of 4.4.2 with my model and use Odin and hopefully that works, but I'm not able to locate anything, and the internet here is pretty horrible. If there is anything anyone can do to help me I appreciate it.
Click to expand...
Click to collapse
wish i could help, but after searching i came up empty just like you.
you really need the stock file to even see if this is fixable.
in the future you really should make a backup after installing a custom recovery before flashing anything else, for cases just like this.

Snake2594 said:
Okay, so recently this week I rooted my Tmobile Galaxy note 3 SM-N900T model. I installed the Xnote Custom Rom and everything was pretty much fine.
This is where the problem started. I have a mobile app Called Odin Mobile, which I used to actually Custom Rom Flash, because I didn't see the option during the Bootloader to where I'm able to Custom Rom flash it from my external card, so I bought the Odin app to help me do it mobile and use CW Recovery to handle it. Now I went to find a wifi patch, because my wifi would NOT work with this Rom at all, I found a patch to install, so I used Odin Mobile Pro to simply just Flash the install on it and hope it would go through after a bit of research. Now my phone I believe is Paperweight softbrick. It doesn't go past the Xnote KitKat Menu of 4.4.2. I can't do anything, even worse my computer isn't reading my phone to where I can just get the files from my phone or external Microsdcard.
What should I do ? I'm pretty helpless at the moment. I even went to try and find a Stock Rom for my Model number which is the Tmobile Model Number: SM-N900TZWETMB Variant, I haven't been able to locate any, my only hope from what I'm reading, is to find a Stock Rom of 4.4.2 with my model and use Odin and hopefully that works, but I'm not able to locate anything, and the internet here is pretty horrible. If there is anything anyone can do to help me I appreciate it.
Click to expand...
Click to collapse
Your phone is bricked. You should find a file of the stock rom and flash it via odin. Remember you can flash any note 3 firmware onto any note 3, so I'd recommend you to find the rom file of the international version of your phone (which is the N9005). Remember, if you're able to boot your phone into flashmode, you'll always be able to unbrick/repair it.

|>/\nte said:
Your phone is bricked. You should find a file of the stock rom and flash it via odin. Remember you can flash any note 3 firmware onto any note 3, so I'd recommend you to find the rom file of the international version of your phone (which is the N9005). Remember, if you're able to boot your phone into flashmode, you'll always be able to unbrick/repair it.
Click to expand...
Click to collapse
Okay thank you for the info, I actually fixed my phone not a couple of hours, shortly after this post. What I did was get the latest Clockworkmod, mine was an old version and didn't have the Install option, when I used Odin, I use the updated Version and was able to Wipe my data, then simply Reflash the Custom Rom and solved my problem. Soon as I got my phone on, I instantly went and Nandroid, so.....won't be doing that again.
I actually didn't know I can flash any note 3 firmware on my phone, least the Tmobile versions, good to know. I'll find em and keep on my computer just in case. I still have the wifi problem, so hopefully I can tackle that down and learn to patch my rom.

Snake2594 said:
Okay thank you for the info, I actually fixed my phone not a couple of hours, shortly after this post. What I did was get the latest Clockworkmod, mine was an old version and didn't have the Install option, when I used Odin, I use the updated Version and was able to Wipe my data, then simply Reflash the Custom Rom and solved my problem. Soon as I got my phone on, I instantly went and Nandroid, so.....won't be doing that again.
I actually didn't know I can flash any note 3 firmware on my phone, least the Tmobile versions, good to know. I'll find em and keep on my computer just in case. I still have the wifi problem, so hopefully I can tackle that down and learn to patch my rom.
Click to expand...
Click to collapse
Just to mention it, that doesn't work only for t-mobile samsung phones. As I said, you can flash any note 3 firmware onto any note 3. I recommend the international version because it's generic, and generic firmwares are always the best ones, with as little bloatware as possible.

Related

[Q] Note 10.1 4G N8020 messed up

Hi all. Tried my first root + custom rom installation and i messed up the device..
i had the newest KIES firmware update (phone XXBMA5) and (XXBMA6) and i rooted the device with odin (3.07). That went OK.
Then i installed the CWM recovery with odin and that was OK too.
Then i downloaded the latest Omega Rom (i missread that it supports N8020) and followed the installation instructions to the point where it started installing Omega V2.0 from SDCARD and then it asked me to select device from a list that included only (N8000,N8010,N8013)..
So the situation now is that i have working odin, working CWM and backup of the EFS (img+tar) but no working recovery. i live in Finland and the device is Sonera locked i think, so the stock roms (international) do not work i guess.
KIES has a backup of my Note but i can't even get to a point where KIES discovers the device.
So basically i think i need a working ROM for my model (Note 10.1 4G N8020), or can i recover the original samsung software somehow ?
Any advices ?
Removed
Just a thought, but can't you reflash CWM or the stock recovery?
If you didn't install the rom why do you need to re-install anything. Just powering down and powering up should have left you as was....
Alajarvi84 said:
working CWM .......... but no working recovery.
Click to expand...
Click to collapse
Maybe i'm missing something but isn't CWM your custom recovery?
It doesn't sound like you've actually installed any rom yet.The Omega installer doesn't actually install anything until a few steps after the one you mentioned about the model type.
I'm with ultramag69 on this one. You should still be on a stock rom unless you already wiped your original rom.
Hi again. Problem solved, just had to do emergency thing from KIES. Like i said this was the first time trying root + custom ro install and to be honest it went to ****. Somehow i managed to delete the stock firmware so that is why the recovery gave me (no files). I did make some backup but when tried to restore it said MD5 mismatch or something. At first the KIES emergency recovery could not find the device, but after i switched from CWMcto stock recovery it worked.
So what did i learn from all this ? Nothing, because i am getting too old (tired+lazy ) to do proper investigation. So one could say my strategy is to bang my head to the wall as long as it takes to go trough. Even if i could just go around it
So basically i am now at the point where i started, with stock 4.1.2 rooted. Used the triangle away to wipe the (6) custom installs or something away, but it still says custom in the settings> information. Does this mean that OTA won't work ? Any way around it ? Because i would like to check now and then that is my version of android the newest one..
Could someone recommend a custom ROM for my Note 10.1 4G (LTE) N8020 4.1.2 because the only one i was able to find was the CyanogenMod (or something) and it basically makes the S-Pen (almost) useless. What i would like is the Omega ROM, but like stated before the installation only supported N8000, N8010 & N8013...
Added screenshot from info.
Thanks anyway
What is truly amazing is that i did not brick the device tough..
switch from cwm to stock
Alajarvi84 said:
Hi again. Problem solved, just had to do emergency thing from KIES. Like i said this was the first time trying root + custom ro install and to be honest it went to ****. Somehow i managed to delete the stock firmware so that is why the recovery gave me (no files). I did make some backup but when tried to restore it said MD5 mismatch or something. At first the KIES emergency recovery could not find the device, but after i switched from CWMcto stock recovery it worked.
So what did i learn from all this ? Nothing, because i am getting too old (tired+lazy ) to do proper investigation. So one could say my strategy is to bang my head to the wall as long as it takes to go trough. Even if i could just go around it
So basically i am now at the point where i started, with stock 4.1.2 rooted. Used the triangle away to wipe the (6) custom installs or something away, but it still says custom in the settings> information. Does this mean that OTA won't work ? Any way around it ? Because i would like to check now and then that is my version of android the newest one..
Could someone recommend a custom ROM for my Note 10.1 4G (LTE) N8020 4.1.2 because the only one i was able to find was the CyanogenMod (or something) and it basically makes the S-Pen (almost) useless. What i would like is the Omega ROM, but like stated before the installation only supported N8000, N8010 & N8013...
Added screenshot from info.
Thanks anyway
Click to expand...
Click to collapse
How did you switch from CWM to stock? I have having a problem syncing with kies also using omega rom on n8013.
jjndimp said:
How did you switch from CWM to stock? I have having a problem syncing with kies also using omega rom on n8013.
Click to expand...
Click to collapse
I was not easy, i just tried the download mode over and over again with KIES open in windows and somehow it finally did find my device and offered a emergency restore. That is it, and the device was restored to default "original state".
OMG.... one would think after nearly having bricked your device you would either A) stop messing around with it or, B) read and learn more about what you're wanting to achieve and THEN maybe trying something with the ABSOLUTE certainty that a backup to restore is available to you in case of any mishap!
Moral of story :
Don't do anything until you are absolutely sure you have read EVERYTHING about what you are going to do.
For others wanting to mess with their devices, take heed! You may not be as lucky as OP (or troller) whichever is applicable.
There comes a certain point, that when crossed one does not care what happens to the device at hand. After fighting with my n8020 for several days in a row i couldn't care less, and like said before i dont have the level of enhusiasm like i had when i was younger. Of course i know now what went wrong.. But seriously, these are just overpriced toys, so it's not a matter of life and death.
Sent from my GT-N8020 using XDA Premium HD app

[ROM] Tab 3 7.0 SM-T210/R Stock 4.4.2 KitKat Update

This is the stock US KitKat ROM for The Galaxy Tab 3 7" Tablet. Finally found it after a bunch of hassle online, and figured I'd post it here to make things easier for everyone.
When I Odin'd this ROM, it actually upgraded my tablet, and left all my items installed (not guaranteeing this will work the same for everyone else).
Afterwards, I just Odin'd TWRP to reroot using Chainfire's SuperSU (no other Superuser would work) and called it good.
Caution: if you are using a custom ROM, this may not work without reflashing stock 4.1.2 since the 4.4.2 ROM appears to be an update, rather than a full ROM.
Rooted devices and custom kernels that are otherwise stock should be fine.
The cache, and if possible dalvik-cache should be cleared before flashing. Some of those files can sometimes interfere with upgrades.
It might be necessary to pinpoint apps that are force closing, uninstall and reinstall them. Some apps, particularly paid apps, store their data differently on KitKat, and will automatically fail as a result.
If that fails, it might be necessary to factory reset the device.
The Stock 4.1.2 ROM for the T210R is available here: http://forum.xda-developers.com/gal...-stock-sm-t210r-4-1-2-jellybean-odin-t2958676
The T210R...XAR file is for the 210R:
https://drive.google.com/open?id=0B2iEgzRTFjrQTmI0ZjRBbWtOajQ&authuser=0
The ITV file is for the T210 (no R)
To download these ROMs, a torrent client is required (such as utorrent).
Anyone who wishes to contribute, please seed if you can after downloading ("Force Starting" the torrent will seed it indefinitely.)
Can I flash this on the SM-T210?
john410 said:
Can I flash this on the SM-T210?
Click to expand...
Click to collapse
I've seen both devices referenced together quite regularly, implying that they use the same ROM.
http://www.boeboer.com/samsung-galaxy-tab-3-7-sm-t210r-manual-guide-wifi/
And even use the same kernel from what I've read:
http://forum.xda-developers.com/showthread.php?t=2439564
I would take standard precautions, such as having a odin image of your original software available and performing a backup of your current system (if able).
Perhaps someone else has some insight to this question?
edit: Looks like I had my information wrong. Found where I obtained the ROM from, it is for the T210R model, and was not intended for the T210.
There are custom ROMs that have been patched for use on both devices, which is where my confusion came from, but this is an official ROM.
I have gotten my hands on the T210(no R) ROM file, and have update the Links above.
I am not responsible for any failed attempts at flashing to either device.
Greaper88 said:
I've seen both devices referenced together quite regularly, implying that they use the same ROM.
http://www.boeboer.com/samsung-galaxy-tab-3-7-sm-t210r-manual-guide-wifi/
And even use the same kernel from what I've read:
http://forum.xda-developers.com/showthread.php?t=2439564
I would take standard precautions, such as having a odin image of your original software available and performing a backup of your current system (if able).
Perhaps someone else has some insight to this question?
edit: Looks like I had my information wrong. Found where I obtained the ROM from, it is for the T210R model, and was not intended for the T210.
There are custom ROMs that have been patched for use on both devices, which is where my confusion came from, but this is an official ROM.
I have gotten my hands on the T210(no R) ROM file, and have update the Links above.
I am not responsible for any failed attempts at flashing to either device.
Click to expand...
Click to collapse
First, thanks for this. I have the T210R. I tried using this and had the same result, it updated the tablet instead of loading a completely new version. I did however run into a problem...the tablet had many for closes and reboots to a point it was unusable and so I reverted back to my backup. Did you see this? Maybe I had a bad download?
[email protected] said:
First, thanks for this. I have the T210R. I tried using this and had the same result, it updated the tablet instead of loading a completely new version. I did however run into a problem...the tablet had many for closes and reboots to a point it was unusable and so I reverted back to my backup. Did you see this? Maybe I had a bad download?
Click to expand...
Click to collapse
I did not have this problem, but I didn't have much on my Tab either. (Some apps don't play well with KitKat upgrades.)
Torrents have multiple segmented hashchecks to make sure you get an uncorrupted download, but it might still be possible. I'm reasonably sure my file is OK since I've used it (can't speak for the non R file though).
Did you clear your cache, and if possible your dalvik cache? I've read that some of those files interfere with upgrades.
If you can pinpoint the apps that are force closing, uninstall and reinstall them. Some apps, particularly paid apps, store their data differently on KitKat, and will automatically fail as a result.
Other option would be to try a factory reset and see if that fixes it. (I understand not wanting to do that though.)
One more thing, if your ROM isn't stock, or stock rooted (custom kernel should be ok too), you may have to flash 4.2 before the 4.4 ROM will work on the device.
Right guys, here i go, just joined and first question!!!
i have not ever rooted a sm-t210 but it was rooted when i bought it second hand!
i have linux installed on my p.c. and was wondering if there is a way to upgrade to and official KITKAT!
as stated i am having problems because my SM-T210 wifi only! and want to update to kitkat official release!
but was hoping also that there is a way/method to root via LINX and not via windows!!
if that is not possible how do i go about it on windows!! as i can use a friends WINDOWS-P.C. if i must!
ah also my SM-T210 does not have the options to change the function of the USB-function,,,
i.e.
it used to have an option to,, use as a mass storege, media transfer or use with samsung keis,,, or some thing of the sort
but this option has dissapeared! may have been my fault!!!! as i uninstalled some system apps,
now it crashes and reboots whenever i try to turn of USB-DEBUGGING options in DEVELOPER-OPTIONS !!!!
many thanks in advance,
Void.Naught
void.naught said:
Right guys, here i go, just joined and first question!!!
i have not ever rooted a sm-t210 but it was rooted when i bought it second hand!
i have linux installed on my p.c. and was wondering if there is a way to upgrade to and official KITKAT!
as stated i am having problems because my SM-T210 wifi only! and want to update to kitkat official release!
but was hoping also that there is a way/method to root via LINX and not via windows!!
if that is not possible how do i go about it on windows!! as i can use a friends WINDOWS-P.C. if i must!
ah also my SM-T210 does not have the options to change the function of the USB-function,,,
i.e.
it used to have an option to,, use as a mass storege, media transfer or use with samsung keis,,, or some thing of the sort
but this option has dissapeared! may have been my fault!!!! as i uninstalled some system apps,
now it crashes and reboots whenever i try to turn of USB-DEBUGGING options in DEVELOPER-OPTIONS !!!!
many thanks in advance,
Void.Naught
Click to expand...
Click to collapse
I do know that Heimdall is a multiplatform flashing tool substitute for Odin. Check out
http://forum.xda-developers.com/galaxy-tab-3/general/root-sm-t210-r-using-heimdall-t2936061
for more info. Hope it helps.
thank you for finding and posting the correct files for this tab
hi i have a galaxy tab kid t2105 rooted, is it possible to install any other rom after 4.1.2?
Greaper88 said:
Rooted devices and custom kernels that are otherwise stock should be fine.
Click to expand...
Click to collapse
Just to triple check, by the above quote you mean that if my tablet is currently rooted, I should still be fine to flash this update correct? [obviously it would become non-rooted once flashed and I'd have to re-root it as you mentioned you rooted after installing]
Also, how much space does this take up?
thanks
~J
ubuntujason said:
Just to triple check, by the above quote you mean that if my tablet is currently rooted, I should still be fine to flash this update correct? [obviously it would become non-rooted once flashed and I'd have to re-root it as you mentioned you rooted after installing]
Also, how much space does this take up?
thanks
~J
Click to expand...
Click to collapse
That is correct. I was rooted running the Werewolf custom OC kernel. I still had my tablet upgrade without wiping, and one other user has reported back saying the same. But I can not promise upgrade as opposed to overwrite.
The flash file once extracted, is about 1.4 GB, I don't know sizes beyond that. It does not repartition the tablet however.
Greaper88 said:
That is correct. I was rooted running the Werewolf custom OC kernel. I still had my tablet upgrade without wiping, and one other user has reported back saying the same. But I can not promise upgrade as opposed to overwrite.
The flash file once extracted, is about 1.4 GB, I don't know sizes beyond that. It does not repartition the tablet however.
Click to expand...
Click to collapse
Awesome, thanks!
~J
Could you upload the T210 ITV file? This torrent is going to take 10 hours
No system file
Well this is awesome, system won't mount and I don't have a backup. Samsung website does NOT have the stock firmware, and attempting to get it for another country just to get this to load so I can flash a ROM leaves me with having to download at 15kbs. I am in the process of selling this to someone for their kid... And there are ZERO seeders for these files. Lovely.
Sorry, m'y post an error
ragnaroksangel said:
Well this is awesome, system won't mount and I don't have a backup. Samsung website does NOT have the stock firmware, and attempting to get it for another country just to get this to load so I can flash a ROM leaves me with having to download at 15kbs. I am in the process of selling this to someone for their kid... And there are ZERO seeders for these files. Lovely.
Click to expand...
Click to collapse
Are you looking for the Stock Rom?
Darthlord064 said:
Are you looking for the Stock Rom?
Click to expand...
Click to collapse
I am, can you help?
Greaper88 said:
I do know that Heimdall is a multiplatform flashing tool substitute for Odin. Check out
http://forum.xda-developers.com/galaxy-tab-3/general/root-sm-t210-r-using-heimdall-t2936061
for more info. Hope it helps.
Click to expand...
Click to collapse
For some (unknown) reason, Odin3 nor JOdin3 doesn't seem to work for flashing my Samsung Galaxy Tab3 device. For that reason I tried Heimdall-Frontend, but to make that work you need to extract the content of a stock ROM first.
Anyways, it still didn't lead to get my device into factory reset yet.
But that's another story on which I still have not yet found the answers needed to get the device successfully back into factory reset.
My guess is that the 'system.img' file, of Android 4.4.2, successfully has been loaded from Heimdall-Frontend, yet by going into reboot right away after Heimdall-Frontend releases the connected device, the download may be deleted.
I read that the cause of that may lie in the fact that Android 4.4.2 is only an update and no full ROM.

[Q] New Note Pro?

Hey guys, I just got my Note Pro a week ago and just started looking into rooting. I keep getting a notification about a 128mb stability update. I would assume it's gonna update to the latest build but I'm not sure what the latest build is or if it'll be rootable afterwords. my current build is KOT49H.P900UEU1ANAE. What is the latest build #? Is there a list of updates somewhere detailing what the improvements are? I just want to root, debloat, turn off OTA and remove KNOX.
Edit: sorry forgot to mention it's just the wife model SM-P900
So 48 views and not one person can tell me the latest build# ? I'll figure out the rest.
Sent from my SM-N900V using Tapatalk
Have you checked SamMobile?
http://www.sammobile.com/firmwares/database/SM-P900/XAR/
How i got there:
http://www.sammobile.com
1. Click Firmware on the top.
2. Click the greyed out firmware database link under the blue banner.
3. Under "Select your firmware" I picked Tablet-->Android-->SM-P900....-->Cellular South (which matches the US variants)
muzzy996 said:
Have you checked SamMobile?
http://www.sammobile.com/firmwares/database/SM-P900/XAR/
How i got there:
http://www.sammobile.com
1. Click Firmware on the top.
2. Click the greyed out firmware database link under the blue banner.
3. Under "Select your firmware" I picked Tablet-->Android-->SM-P900....-->Cellular South (which matches the US variants)
Click to expand...
Click to collapse
Thanks muzzy! I had already been to SamMobile but all it had was foreign countries listed. I didn't know about Cellular South being the US version. I'll look again.
Edit: oh look a list of the updates and release dates! My Wi - fi reception seems slow, do any of the update fix that?
I honestly can't say. I'm on NC5 which is dated back in April and have no major issues.
I'm rooted and debloated though, not that this would impact the wifi performance . .
48 views doesn't mean 48 users. About 44 of those are Google Content Crawler, which is Google search engine's bots crawling the net for content to display in google.com. It is an automated process.
Samsung doesn't release changelists, so we don't know what each update does beyond what we can see.
Thanks for the help guys! I just accepted the first update and it took me to ANC5. I guess I'll have to accept all updates until current and then try CF-Auto-Root. I'll report back then.
Actually I just got my tablet like a week ago as well. I m on the same build no as well....haven't updated yet. I also haven't installed Knox either. There is a download arrow on the Knox icon and if I click the icon it starts downloading so I just cancel it. I am thinking of rooting as well. Well what I m trying to say is...keep the thread updated and I will just follow your lead.....hehe.
It always helps to know your country as well as different countries are on slightly different versions. You can always go to sanmobile.com, click on firmware and search for p-900. That will give you the list of all the latest ROMs for different countries / carriers. US based ROMs are listed as "Cellular South".
Successful Root!
Okay guys sorry it's taken so long to respond, I had hernia surgery on Monday so I've been behind on getting this rooted.
My plan was to use CF-Auto-Root and then load TWRP recovery and then load "Debloat Stock Variant" by Gatsrom. I decided to do it in that order because I wasn't sure I could load a custom recovery without being rooted first.
I accepted all updates up to the current = P900UEU1BNK1. Using Win 7 and loaded Samsung drivers. Downloaded ODIN 3.09, Odin 3.07 came with CF-Auto-Root and downloaded TWRP. Booted into download mode and made sure ODIN recognized my P900. And this is when to fun began! Everything seem to be going okay but I did run into a snag. I used ODIN 3.07 because that's what came with Auto- Root and I'd read somewhere of people having trouble with 3.09??? Anyways I got a red "FAIL" message and my screen displayed multicolored lines. I tried running it in ODIN 3.09 and got the same result. (i didn't disconnect anything between the 3.07 or 3.09 attempts, maybe i should have?). I disconnected my P900 and it rebooted giving me a Firmware Error screen telling me to use Kies "Recovery Mode". I tried Kies Recovery but Kies3 wouldn't even recognize the P900. (I started freaking a little at this point!) Anyways, I decided to try and load TWRP because I thought I've got nothing to lose! I loaded TWRP into ODIN and it took, so I thought, because my P900 rebooted into an up and running normal state. (Big Sigh!) I tried booting into recovery but TWRP didn't take, it came up to stock recovery, trying to load TWRP just kicked the P900 out of the Firmware Error state it was in?? I decided to give Auto-Root another go after rebooting Win 7. Used ODIN 3.09 this time and everything went fine and I was rooted! Then I loaded TWRP and it loaded fine! I performed a TWRP backup at this point and things seem to be running smoothly. I still need to load the Debloat Variant, that's what's on my plate for today.
http://forum.xda-developers.com/showthread.php?t=2656551
http://forum.xda-developers.com/showthread.php?t=2706982
http://forum.xda-developers.com/gal...t/rom-original-stock-debloated-stock-t2860069
You are a much braver sole than I. Hope all goes smoothly.
I could be wrong but I would think that if one is going to a different ROM then rooting isn't necessary. Simply use Odin to flash TWRP but ensure that auto reboot is not enabled in Odin when you do it. If you allow the device to begin booting into stock system it's going to overwrite recovery again (with stock recovery) so what you want to do is flash TWRP, and once it's flashed FORCE a reboot directly into recovery again using the hardware keys on the device. At that point you can do an nandroid backup and then flash your ROM.
Sent from my SM-P900 using Tapatalk
treetopsranch said:
You are a much braver sole than I. Hope all goes smoothly.
Click to expand...
Click to collapse
I'm not that brave treetop! I just know my way around a computer and I've rooted a few of these things. Plus I know the guys here on XDA are good at helping out if you hit a snag. Luckily I figured this one out on my own! You've just gotta do your research before jumping in and search read, search read, search read! I provided some links to get you started....get to it!
muzzy99 said:
I could be wrong but I would think that if one is going to a different ROM then rooting isn't necessary. Simply use Odin to flash TWRP but ensure that auto reboot is not enabled in Odin when you do it. If you allow the device to begin booting into stock system it's going to overwrite recovery again (with stock recovery) so what you want to do is flash TWRP, and once it's flashed FORCE a reboot directly into recovery again using the hardware keys on the device. At that point you can do an nandroid backup and then flash your ROM.
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Thanks for the info muzzy, I'll remember that for next time! :good:
I did get the Debloat Variant up and running and loaded Xposed framework with sdcard full access. Everything seems to be running smoothly!
Ok So I finally got to it and successfully rooted (in first try, if I may add ). Thanks to xblue's guide/heroic efforts I avoided certain things and everything went smoothly. So Basically I installed samsung drivers using Kies, rebooted pc (Win 8.1). Downloaded cf autoroot and downloaded odin 3.09 as autoroot comes with 3.07. Replaced ONLY 3.07 odin exe with 3.09. Started Odin in Admin mode, put the tablet in download mode. Attched to pc and Odin recognized it. Then Gave it a final thought......lol. Pressed Start, device booted couple times. Then PASS appeared on the Odin window after like 30 secs. Installed root checker...successfully rooted. Installed TWRP via odin and flashed that successfully. Made a full back up and installed a ROM of my choice. I am a happy camper.
Sweet Deal singhsta! I'm glad my efforts were a help!
i would update to the latest version.. i tried using the original one that you have however i got the screen flicker issue so had to update.. the first update isnt very good wifi keeps dropping but the most recent version doesn't tho you may have a bug where every time you unlock the screen the tablet is still asleep even though the icons are visible so you have to lock the screen again and unlock. however if you factory reset this bug goes away.
i find the latest version is the most stable and battery life is better if you disable all the unnecessary apps that you can i usually get rid of most of the samsung back up apps and all the google ones bar the ones it needs to run play store etc and maintaining the ones that sync for back up.
wifi was really slow when i first got it and would drop very annoying but now it seems better but have experienced slow wifi i think it's a hardware issue all note pro's have in built that should have been sorted by the latest build. i hope they finally give it an update in the coming months even to 4.4.4. or something.

Samsung Galaxy Tab 2 7.0 P3113

As in the title states I have the galaxy tab 2 7.0 and recently I installed CWM and a ROM and everything looked like it went right however after I reloaded my tablet nothing seems different it jus seems to return to stock setting and now I cant do the OTA software update which means now certain apps and games I can no longer uses as it says my device isnt compatible. My goal was to simple update from Jellybean to at Least Kitkat.
Can someone help me. where did I go wrong?
Fleacore210 said:
As in the title states I have the galaxy tab 2 7.0 and recently I installed CWM and a ROM and everything looked like it went right however after I reloaded my tablet nothing seems different it jus seems to return to stock setting and now I cant do the OTA software update which means now certain apps and games I can no longer uses as it says my device isnt compatible. My goal was to simple update from Jellybean to at Least Kitkat.
Can someone help me. where did I go wrong?
Click to expand...
Click to collapse
Go to sammobile and flash the latest stock firmware for your device .
Newyork! said:
Go to sammobile and flash the latest stock firmware for your device .
Click to expand...
Click to collapse
Well after a short research I found a ROM called Resurrection Remix, loaded with 5.0.2 (or Lollipop) however now everything is force closing and I barely got my laptop to see it as MTP again after installing a new Binary (glad that did that trick for that) but I cant get it to boot into CWM Recovery bc I cant access the app the only thing it will let me do right now is change the Binary.
How can I fix this issue?
Edit: Okay so I got that solved with doing a factory reset twice, booted in CWM, loaded up the GApps. Now just wondering if there is away to make it not seen with phone options like the dialer or msgs as its jus a plan old tablet, doesnt take a sim card and has no carrier. I do have the source code but I am not tweaking that til I get a better understanding of it.
After a lot of research and tries (amazingly without bricking) I am now running an even newer version of a CM 13 Marshmellow

WiFi is not working...

Hi,
The first is to apologize for the language used, and the length of the text. I am from Spain and my level of English is low, so as it was a fairly long post I used Google Translator and I know that makes it very literal translation ...
I write this post to see if anyone can help me or give some idea ... I explain the problem.
I own for some time ago the Tablet, Samsung Galaxy Note 10.1 (2012) . He has always liked to try new ROMs, so far without much trouble, but .... I tempted fate a lot.
At some point, after changing the Recovery and ROM, to test Marshmallow, the WiFi stopped working, which is a problem in a device of this type, you lose a lot of functionality.
I have tried many ROMS, about 10, and none of them work properly. It is true that some seems, makes the attempt, working. But it does not work.
I have also tried different Recoveries (CWRM, TWRP, Stock, HigOnAndroid, ....), and I have not gotten the Tablet WiFi work.
With all these tests, entering DOWNLOAD mode, it indicates that the device model is the Note 10.1 GT-N8000, the model without WiFi. And when you install a ROM, and go to Settings/Info, the system said that the Tablet is the GT-N8000 model.
This has led me to perform multiple tests:
A- Flash several ROMS by Recovey, usually used the TWRP.
B- Change Recovey installed by Odin 3.10
C- The last thing I have tried, is back to the original ROM and Recovery by Odin 3.10
All these attempts, multiple, have thrown me the same result. The WiFi does not work, and continues to indicate that is the model GT-N8000
The questions are:
1 - Is it normal, even the GT-N8013 model DOWNLOAD mode appears as the GT-8000?
2- Is there any way to get back to its original state, GT-N8013, with WiFi?
3- What Recovery would be most appropriate? (I once used the TWRP)
4- What ROM for this Tablet is the most appropriate? (This question is very personal, I've always liked Omega Rom)
What model do you have .
Samsung Galaxy Note (2012) Gt-N8013
peirof said:
Samsung Galaxy Note (2012) Gt-N8013
Click to expand...
Click to collapse
Hi, WiFi isn't working because you probabily stay with a older bootloader but with 6.0. When you flashed the MM rom, your tablet at which version of android was? Maybe i think 4.4.x if WiFi doesn't start. You need to update the bootloader into marshmallow or try look on the thread where you found the rom if there are some modem updates. By the way, if you want to get the stock firmware and install it on your tab, first go in sammobile site and download the firmware ( pay attention to version 4g / without 4g ) and then put your device in download mode->connect to odin-> on "PDA" load the firmware you downloaded -> start -> wait 10/12 mimutes and you will have the tablet as you bought for the first time.
And check if the rom is right for your device( because when kernel is different if the device start it can have some issues like WiFi )
Hope i help you
If i helped you, remember to click the thanks button!
gosha98_ said:
Hi, WiFi isn't working because you probabily stay with a older bootloader but with 6.0. When you flashed the MM rom, your tablet at which version of android was? Maybe i think 4.4.x if WiFi doesn't start. You need to update the bootloader into marshmallow or try look on the thread where you found the rom if there are some modem updates. By the way, if you want to get the stock firmware and install it on your tab, first go in sammobile site and download the firmware ( pay attention to version 4g / without 4g ) and then put your device in download mode->connect to odin-> on "PDA" load the firmware you downloaded -> start -> wait 10/12 mimutes and you will have the tablet as you bought for the first time.
And check if the rom is right for your device( because when kernel is different if the device start it can have some issues like WiFi )
Hope i help you
If i helped you, remember to click the thanks button!
Click to expand...
Click to collapse
Hi,
Thanks, sorry for delay, I can solve the isue with another Rom

Categories

Resources