Downgrade advice after latest Lollipop Upgrade - AT&T Galaxy Note 3 Q&A, Help & Troubleshooting

I've been reading a few threads but since I have an AT&T Note 3 there seems to be a ton of jargon I'm having a hard time picking up on, I've done a few previous Android phones but those seemed to have a guide where everything was exactly what I had and it just worked step by step. I have a fully stock Note 3
Baseband version:
N900AUCUEOC2
Kernel version
3.4.0-4335446
[email protected] #1
Fri July 31 21:47:49 KST 2015
Build Number:
LRX21V.N900AUCUEOC2
Every OTA update something seems to happen on this Note 3, GPS issues on one, battery on another and now it's Wifi issues along with missing text messages. (both of which suck the most). I've never rooted or flashed this phone, either I would like to go back to 4.4.2 or maybe try another rom but I'm having a real hard time figuring out all the steps since it seems any time there's an update they all change, towelroot, safestrap, kingo root, heimdall, MJ5, etc hell are the notes in the main post for AT&T Samsung Galaxy Note 3 All-In-One Resource Thread still good?
Basically I figure I would take it back to 4.4.2 and run that for a month and see if texting, gps and battery are stable, that's my big three. Getting rid of the Samsung bloat and flashing a new rom are secondary at this point. I've done the whole wipe and factory reset the phone a few times but I still can't shake this texting bug where sometimes it silently stops working, tried the built in Messaging app, switched to Google Messenger and even tried Handcent and Go SMS Pro with the same results, texts stop coming in randomly, I can send out but replies never show up and rebooting the phone doesn't cause them to show up, they are just gone but a reboot will restore the ability to receive texts.

Hello. It seems you have a few different options, since your on N900AUCUEOC2, which is the same thing as N900AUCUEOC1, but with an update that patches Stagefright, you can downgrade and upgrade to pretty much anything you want.
What you need to know:
SuperSU is the super user you will use.
Safestrap is the ONLY bootloader that you can use.
Towelroot will root 4.4.2 and below.
You make sure Busybox gets installed before installing Safestrap.
Click to expand...
Click to collapse
Download and Install to your computer:
Code:
[URL="http://odindownload.com/"]http://odindownload.com/[/URL] <--- Odin
[URL="http://odindownload.com/SamsungUSBDriver/USB_Drivers_1.5.27.0.rar"]http://odindownload.com/SamsungUSBDriver/USB_Drivers_1.5.27.0.rar[/URL] <--- Samsung USB Drivers
Download and place on your Desktop.
Code:
[URL="https://www.androidfilehost.com/?fid=95784891001615211"]https://www.androidfilehost.com/?fid=95784891001615211[/URL] <--- 4.4.2 (N900AUCUCNC2)
Download Towelroot and Safestrap on your SD card.
Code:
[URL="https://www.androidfilehost.com/?fid=23681161096070831"]https://www.androidfilehost.com/?fid=23681161096070831[/URL] <--- Towelroot
[URL="https://www.androidfilehost.com/?fid=95832962473398959"]https://www.androidfilehost.com/?fid=95832962473398959[/URL] <--- Safestrap
Download busybox and SuperSU off the playstore.
Code:
[URL="https://play.google.com/store/apps/details?id=stericson.busybox&hl=en"]https://play.google.com/store/apps/details?id=stericson.busybox&hl=en[/URL] <--- Busybox
[URL="https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en"]https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en[/URL] <--- SuperSU
1. Back everything up that you don't want to lose, then perform a factory reset before proceeding to step 2.
2. Start odin and connect your phone to your computer.
* Odin should display 0:[COM4] and
Code:
<ID:0/004> Added!!
in the log box.
3. Load N900AUCUCNC2 into the AP slot of Odin.
* The below output should display in the log.
Code:
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
4. Click start and wait awhile, your phone will eventually boot into 4.4.2.
5. Navigate through the startup menus.
6. Install Towelroot off your SD card.
7. "Make it rain." and you'll have root.
8. Download and install SuperSU off the playstore.
9. Download and install Busybox off the playstore.
10. Install Safestrap off your SD card.
11. Enjoy stock 4.4.2 with root.

Want to downgrade from EOC2 Lollipop to NC2 Kitkat
Phlashb4k said:
Hello. It seems you have a few different options, since your on N900AUCUEOC2, which is the same thing as N900AUCUEOC1, but with an update that patches Stagefright, you can downgrade and upgrade to pretty much anything you want.
What you need to know:
Download and Install to your computer:
Code:
[URL="http://odindownload.com/"]http://odindownload.com/[/URL] <--- Odin
[URL="http://odindownload.com/SamsungUSBDriver/USB_Drivers_1.5.27.0.rar"]http://odindownload.com/SamsungUSBDriver/USB_Drivers_1.5.27.0.rar[/URL] <--- Samsung USB Drivers
Download and place on your Desktop.
Code:
[URL="https://www.androidfilehost.com/?fid=95784891001615211"]https://www.androidfilehost.com/?fid=95784891001615211[/URL] <--- 4.4.2 (N900AUCUCNC2)
Download Towelroot and Safestrap on your SD card.
Code:
[URL="https://www.androidfilehost.com/?fid=23681161096070831"]https://www.androidfilehost.com/?fid=23681161096070831[/URL] <--- Towelroot
[URL="https://www.androidfilehost.com/?fid=95832962473398959"]https://www.androidfilehost.com/?fid=95832962473398959[/URL] <--- Safestrap
Download busybox and SuperSU off the playstore.
Code:
[URL="https://play.google.com/store/apps/details?id=stericson.busybox&hl=en"]https://play.google.com/store/apps/details?id=stericson.busybox&hl=en[/URL] <--- Busybox
[URL="https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en"]https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en[/URL] <--- SuperSU
1. Back everything up that you don't want to lose, then perform a factory reset before proceeding to step 2.
2. Start odin and connect your phone to your computer.
* Odin should display 0:[COM4] and
Code:
<ID:0/004> Added!!
in the log box.
3. Load N900AUCUCNC2 into the AP slot of Odin.
* The below output should display in the log.
Code:
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
4. Click start and wait awhile, your phone will eventually boot into 4.4.2.
5. Navigate through the startup menus.
6. Install Towelroot off your SD card.
7. "Make it rain." and you'll have root.
8. Download and install SuperSU off the playstore.
9. Download and install Busybox off the playstore.
10. Install Safestrap off your SD card.
11. Enjoy stock 4.4.2 with root.
Click to expand...
Click to collapse
@phlashb4k: Hay there, i have something like the same question but my scenario is quit different,
i have an AT&T Note 3 running EOC2 now but i have installed it with the help of "FlashFire", (as far as i live in a country other than USA/non AT&T country so i could not get OTA updates, hence i had to find manual ways to update to OC2. And as you know FlashFire needs root so, my device is rooted now and shows a padlock on startup but i don't have any custom recovery installed.
NOW i want to remove root and go stock everything (bcz now i know that i can install that OTA.zip with the help of adb),
As far as i want to remove root access i think going to superSU settings and clicking on full unroot would do the job, am i right?
and than because i have (N900AUCUEOC1_N900AATTEOC1_N900AUCUEOC1_HOME.tar.md5) file so i think i will have to simply odin start and AP file the above tar and connect my phone, after added shows i press start button and everything goes will, is it right?

I was wondering if its possible to go back to jellybean? im on 4.4.2?

Sorry I've been busy!
talvigi said:
@Phlashb4k: Hay there, i have something like the same question but my scenario is quit different,
i have an AT&T Note 3 running EOC2 now but i have installed it with the help of "FlashFire", (as far as i live in a country other than USA/non AT&T country so i could not get OTA updates, hence i had to find manual ways to update to OC2. And as you know FlashFire needs root so, my device is rooted now and shows a padlock on startup but i don't have any custom recovery installed.
NOW i want to remove root and go stock everything (bcz now i know that i can install that OTA.zip with the help of adb),
As far as i want to remove root access i think going to superSU settings and clicking on full unroot would do the job, am i right?
and than because i have (N900AUCUEOC1_N900AATTEOC1_N900AUCUEOC1_HOME.tar.md5) file so i think i will have to simply odin start and AP file the above tar and connect my phone, after added shows i press start button and everything goes will, is it right?
Click to expand...
Click to collapse
Hey man. Just saw your post, sorry about the late reply, I've been really busy with college. Are you still needing help or did you get everything taken care of? Let me know

Some help here please.
If i do this, if i downgrade 5.0 to 4.4.2 then can i upgrade to a custom rom, like Cyanogenmod? i buy a note 3 SM n900a ATT and i use in my contry Honduras, i want to root and instal custom ROM. does IT HELP?

satiacums said:
I was wondering if its possible to go back to jellybean? im on 4.4.2?
Click to expand...
Click to collapse
Once your on kitkat or lp there's no going back to jelly bean

Does anyone know if there is a video tutorial on how to do this? I'm a squid it won't be my first time rooting a device and I really don't want to break my phone. Also once I get back to KitKat lop able to run custom roms?

great thread zombie

jacky37 said:
Once your if you're on on kitkat or lp there's no going back to jelly bean
Click to expand...
Click to collapse
If ur on eoc2, how can u downgrade to lp or KitKat?
---------- Post added at 09:21 AM ---------- Previous post was at 08:57 AM ----------
phlashb4k said:
Hello. It seems you have a few different options, since your on N900AUCUEOC2, which is the same thing as N900AUCUEOC1, but with an update that patches Stagefright, you can downgrade and upgrade to pretty much anything you want.
What you need to know:
Download and Install to your computer:
Code:
[URL="http://odindownload.com/"]http://odindownload.com/[/URL] <--- Odin
[URL="http://odindownload.com/SamsungUSBDriver/USB_Drivers_1.5.27.0.rar"]http://odindownload.com/SamsungUSBDriver/USB_Drivers_1.5.27.0.rar[/URL] <--- Samsung USB Drivers
Download and place on your Desktop.
Code:
[URL="https://www.androidfilehost.com/?fid=95784891001615211"]https://www.androidfilehost.com/?fid=95784891001615211[/URL] <--- 4.4.2 (N900AUCUCNC2)
Download Towelroot and Safestrap on your SD card.
Code:
[URL="https://www.androidfilehost.com/?fid=23681161096070831"]https://www.androidfilehost.com/?fid=23681161096070831[/URL] <--- Towelroot
[URL="https://www.androidfilehost.com/?fid=95832962473398959"]https://www.androidfilehost.com/?fid=95832962473398959[/URL] <--- Safestrap
Download busybox and SuperSU off the playstore.
Code:
[URL="https://play.google.com/store/apps/details?id=stericson.busybox&hl=en"]https://play.google.com/store/apps/details?id=stericson.busybox&hl=en[/URL] <--- Busybox
[URL="https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en"]https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en[/URL] <--- SuperSU
1. Back everything up that you don't want to lose, then perform a factory reset before proceeding to step 2.
2. Start odin and connect your phone to your computer.
* Odin should display 0:[COM4] and
Code:
<ID:0/004> Added!!
in the log box.
3. Load N900AUCUCNC2 into the AP slot of Odin.
* The below output should display in the log.
Code:
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
4. Click start and wait awhile, your phone will eventually boot into 4.4.2.
5. Navigate through the startup menus.
6. Install Towelroot off your SD card.
7. "Make it rain." and you'll have root.
8. Download and install SuperSU off the playstore.
9. Download and install Busybox off the playstore.
10. Install Safestrap off your SD card.
11. Enjoy stock 4.4.2 with root.
Click to expand...
Click to collapse
.rar wont work in odin's ap slot dude.

Related

[Q] Currently unable to install any rom

Hi guys,
Current situation
I haven't been able to use my phone for a good day now and I been busy reading guides, trying out stuff for a bunch of hours now. I thought it was time to ask you guys. Currently this is the only thing I'm able to do:
When I boot normally its stuck on the black screen with Samsung Galaxy Note on it.
When I boot with volume down, a screen popups up if I'm sure than press volume up. After that I'm in ODIN mode (says so with red letters in the left top). Below that it says: PRODUCT NAME: GT-N7000 , CUSTOM BINARY DOWNLOAD: NO , CURRENT BINARY: SAMSUNG OFFICIAL.
In the middle of the screen below the Android guy it says: Downloading... Do not turn of target !! (I'm not really sure if its suposed to say downloading there, while its not downloading anything?)
What I did so far
I came from a gingerbread Rocket ROM and decided to try out the ICS Stunner rom. I downloaded the ROM and read the install discription. I pretty much went into CWM right away to install the zip (rom) from SD card. It did work and ofcourse everything was still there cause I didnt wipe anything. But I noticed that a bunch of things didn't work and a lot of programs where crashing. I assumed I must have missed a step so I decided to go with the 'Squeaky Clean' install, which was posted on the team-passion website.
This was the last time I was able to get into CWM and connect my phone true USB with my laptop. Because I did the following steps:
Reboot in to ClockworkMod Recovery.
Format the following:
- Wipe Data/Factory Reset
- Wipe Cache Partition
**Enter 'Mounts and Storage'**
- Format everything it will allow you to
**Go Back, enter 'Advanced'**
-Wipe Dalvik Cache
-Wipe Battery Stats
**Go Back to main menu, reboot system**
The next step on that list is: Remove your battery and boot up into 'Download Mode'. But the only mode I am getting into is the ODIN MODE where it already says 'Downloading...'. When I try to flash using ODIN, it isn't able to setup the connection. It does identify that the phone is connected because the ID:COM is yellow on 0:[COM3]. It didn't before, but after reading somewere that it might help to install Kies for the drivers it did.
Also tried "InitialCFRootFlasher" and "DooMLoRD_v4_ROOT-zergRush-busybox-su" but both arent able to establish the connection. Just like ODIN.
What I'd like to do
I'd prefer going with the ICS Stunner ROM, seeing thats how this all started. But currently I'd settle for anything working, because being phoneless for a day is pretty anoying hehe.
What do you guys suggest?
I really don't know how u understood the process. But just don't screw this. Go download any of the pre rooted odex rom -link in my signature - and flash it via odin.
Or any rootable rom from dr ketan's thread - link in my signature - and follow the steps mentioned there to the Dot slowly and calmly. Just get to GB and rooted. Then report here. Will tell u how to go to ics stunner after that.
BOOMED from my BOMBASTIC NOTE
Thanks for the quick reply. I'm currently downloading one of the prerooted roms from your signature. However it would suprise me if ODIN allows me to install these seeing it can't really connect to the phone. Am I suposed to be in the 'Downloading... Do not turn of target !!' screen on my phone, while connected to laptop true USB?
Will update once I'v got it.
h4y0 said:
Thanks for the quick reply. I'm currently downloading one of the prerooted roms from your signature. However it would suprise me if ODIN allows me to install these seeing it can't really connect to the phone. Am I suposed to be in the 'Downloading... Do not turn of target !!' screen on my phone, while connected to laptop true USB?
Will update once I'v got it.
Click to expand...
Click to collapse
Yup u need to be in that mode. The odin on your PC should show the Com port as yellow. If it doesnt then there is some drivers problem.
It is connected yeah, the com port is shown as yellow. After loading any rom in PDA, Phone or Bootloader and only checking auto reboot and f. reset time this is what happens:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
And thats where its hanging, nothing on the phone screen is changing.
I don't remember the screen saying 'Downloading..' last time I flashed something. It's already saying that when I enter the screen, when its not downloading anything.
Apparently I'm not able to make edits yet here so heres another post after figuring out how to load these files:
It is connected yeah, the com port is shown as yellow. After loading the three files in ODIN under PDA, PHONE and CSC just like on the screenshot in your signature. And only checking 'Auto reboot' and 'F. Reset Time' the following happens:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Rooted_Stock_Odex_N7000XXLA6.tar.md5 is valid.
<OSM> MODEM.tar.md5 is valid.
<OSM> CSC_N7000XEULA1_XEU.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
abhisahara said:
Just get to GB and rooted. Then report here.
Click to expand...
Click to collapse
Done! I'm still not sure what went wrong, I think placing the files in the wrong place in ODIN. Got a tip from someone how to place them and they worked in one go. Pretty weird cause I was using the same setup as the XDA guide post.
Main problem is solved now, I'll have to look into the ICS thing now. Thanks for your help.
h4y0 said:
Done! I'm still not sure what went wrong, I think placing the files in the wrong place in ODIN. Got a tip from someone how to place them and they worked in one go. Pretty weird cause I was using the same setup as the XDA guide post.
Main problem is solved now, I'll have to look into the ICS thing now. Thanks for your help.
Click to expand...
Click to collapse
Sorry was away so couldnt reply. The setup shown i xda should work perfectly. Anyways its good to know that you got all things settled. You can install the ICS Stunner (no touchwiz and no samsung apps) if you so want. Remember to backup your data as you will have to wipe data for going to ICS. From rooted GB install mobile odin then download the lp1 repack from my signature and after all that is done reboot to recovery clear caches and data and flash stunner (download the latest build by clicking Stunner in my signature) clear caches and data and reboot.
* Triangle away is required only when you flash lp1 through PC Odin.*
Ended up using the mobile odin application, works like a charm.
Thanks for your help!
h4y0 said:
Ended up using the mobile odin application, works like a charm.
Thanks for your help!
Click to expand...
Click to collapse
You are welcome. Glad it all worked for you. Hitting some thanks button will be good too LOL

[How To] Root - Galaxy Tab 2 7"

here it is
since we have no forum yet (um come on mods get to it!) I can't post a shiny new thready for my very first real dev, ROOT FOR YOUR GALAXY TAB 2 7.0!!
so I'll put it in this post, and I'll mention I posted this on rootzwiki first, we have our very own forum there... (XDA I love ya, and I know you will get there hehe)
** Edit ***
I just attached the files as well as mediafire, rename the txt file to pit (xda won't accept the file as is..
_________________
Method
I have gained root through using a modified boot.img from the gt-p3110 leak posted a few weeks ago, took me all day but here it is.
Note I haven't only tested this on my device, its 2am est and all my testers are asleep (that being termitech lol)..
Standard YMMV
So big fat warning, I MAKE NO GUARANTEES THIS WILL NOT BRICK YOUR TAB, USE AT YOUR OWN RISK!!
Now with that unpleasantness out of the way.. with out further ado. I present the very first root for the Samsung Galaxy Tab 2 7.0!! Yay mom I'm a dev now!
The method will have you using hemidall/heimdall-frontend there is a way to put this all into an odin package but I'm too exhausted to do so (for now).. Also I will not re-hash how to install or use heimdall.. you can look that up on your own
Get it here:
http://www.glassechidna.com.au/products/heimdall/
Process
Once that is installed do the following:
reboot tablet into download mode
adb reboot download
launch heimdall-frontend
go to flash tab
load attached pit file (gt-p3110.pit)
Then from partion details choose "KERNEL", click "Add"
then choose "Browse" and select the attached boot-bjr.img
choose "Start"
after the tablet reboots:
Code:
adb shell
./su
./gtab2-root.sh
Congratulations you are now rooted!
I'm going to try and stay up a bit longer and monitor this (and the xda thread) please let me know immediately of success or failure, I will pull the files if failure.. Issues with heimdall aside, I want reports back on if things work.. They work for me.. and I tested a fresh factory img just a few minutes ago.. pretty sure we are good!
gt-p3110.pit
boot-bjr.img
Big fat warning, I MAKE NO GUARANTEES THIS WILL NOT BRICK YOUR TAB, USE AT YOUR OWN RISK!!
Now with that unpleasantness out of the way.. with out further ado. I present the very first root for the Samsung Galaxy Tab 2 7.0!! Yay mom I'm a dev now!
Flash xoomdev's CWM recovery First, then flash the package in this post.
Xoomdev's thread
Paste of his instructions:
Download the recovery.tar.md5
Make sure Kies is closed
Reboot into Download mode (adb reboot download)
Open Odin, confirm connection
Click PDA
Load recovery.tar.md5 file
Click Start
Device will reboot when the flash is complete
To reboot into recovery, just like any other device; adb reboot recovery
Link to the CWM Package
Link to root package
Congratulations you are now rooted!
nycbjr said:
Big fat warning, I MAKE NO GUARANTEES THIS WILL NOT BRICK YOUR TAB, USE AT YOUR OWN RISK!!
Now with that unpleasantness out of the way.. with out further ado. I present the very first root for the Samsung Galaxy Tab 2 7.0!! Yay mom I'm a dev now!
Flash xoomdev's CWM recovery First, then flash the package in this post.
Xoomdev's thread
Paste of his instructions:
Download the recovery.tar.md5
Make sure Kies is closed
Reboot into Download mode (adb reboot download)
Open Odin, confirm connection
Click PDA
Load recovery.tar.md5 file
Click Start
Device will reboot when the flash is complete
To reboot into recovery, just like any other device; adb reboot recovery
Link to the CWM Package
Link to root package
Congratulations you are now rooted!
Click to expand...
Click to collapse
Thank for making this possible!
I followed these directions exact. But, I am getting the following error - E:signature verification failed - when updating 'cmw-root-gtab2.zip'
I did run that Samsung update on the device last week when it was first powered on @ BB - could this have any issues with the root process?
are you sure you have clockwork mod for recovery?
you would only see this error with stock recovery
I have tried doing it this way 5x now, and when I try to use Odin, it loads the recovery.tar.md5 file, I click start, then I get what i linked below
I dont know what I am doing wrong. I am in the download mode
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
That is what I get since you cant see the picture very well.
derek1387 said:
I have tried doing it this way 5x now, and when I try to use Odin, it loads the recovery.tar.md5 file, I click start, then I get what i linked below
I dont know what I am doing wrong. I am in the download mode
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
That is what I get since you cant see the picture very well.
Click to expand...
Click to collapse
Try to redownload the file, also try hiemdall instead.. and check out the thread on rootzwiki until more gets posted here, the issue is with flashing cwm, not the root.
Also did you reboot after flashing and try to access recovery mode?
My tab doesnt reboot after the flash, its like it never even happened.
I tried the heimdall way, but the img file cant be found anywhere at the moment.
I am new to the android world, so bear with me. I followed the exact steps for this one that you posted, and my tablet acts like nothing even happened.
ejpyle said:
Thank for making this possible!
I followed these directions exact. But, I am getting the following error - E:signature verification failed - when updating 'cmw-root-gtab2.zip'
I did run that Samsung update on the device last week when it was first powered on @ BB - could this have any issues with the root process?
Click to expand...
Click to collapse
derek1387 said:
My tab doesnt reboot after the flash, its like it never even happened.
I tried the heimdall way, but the img file cant be found anywhere at the moment.
I am new to the android world, so bear with me. I followed the exact steps for this one that you posted, and my tablet acts like nothing even happened.
Click to expand...
Click to collapse
Pretty sure you need to follow the thread over on rootzwiki called "Stopping recovery overwrite" in the Galaxy Tab 2 (7") Development forum. After that use ODIN to flash CWM. You need to do this if the upgrade was applied to your stock tab (UEALD3 / SEP-66 #1).
If you follow the instructions it will work. If you get a signature error, you are NOT on CWM. Look at the top of the screen, if do you not see Clockwork Mod you are not using CWM you are using 3e recovery which is the stock. Start over and flash CWM.
Once you have CWM flash the root package. You should then be all set. I've done it a dozen times now and it worked every time.
is this method for p3113 or p3100?
bark777 said:
Pretty sure you need to follow the thread over on rootzwiki called "Stopping recovery overwrite" in the Galaxy Tab 2 (7") Development forum. After that use ODIN to flash CWM. You need to do this if the upgrade was applied to your stock tab (UEALD3 / SEP-66 #1).
Click to expand...
Click to collapse
Yeah, when i opened it it updated. So that may be the issue then?
Sent from my GT-P3113 using Tapatalk 2
I think I royally F***ED my tab up...
I'm stuck at the boot splash screen with "ABORT IN SBL" in the upper left corner.
I can't get it to boot to recovery. I can only get it to boot into the download mode now.
Is there any way to flash this back to stock using heimdall on ubuntu?
Please dear god tell me there is a way to fix this.
bark777 said:
Pretty sure you need to follow the thread over on rootzwiki called "Stopping recovery overwrite" in the Galaxy Tab 2 (7") Development forum. After that use ODIN to flash CWM. You need to do this if the upgrade was applied to your stock tab (UEALD3 / SEP-66 #1).[/QUOTE
Thank you! This actually corrected the issue.
Click to expand...
Click to collapse
I think I am just going to give up on trying to root this thing till an easier solution comes out.... I cant get this thing to recover back to the stock shipped software.
I am a newb... i know. Lol
derek1387 said:
I think I am just going to give up on trying to root this thing till an easier solution comes out.... I cant get this thing to recover back to the stock shipped software.
I am a newb... i know. Lol
Click to expand...
Click to collapse
There will likely never be any other solution. You will always have to flash recovery in Heim or Odin. After that you can flash a rooted ROM. But there will always be that initial work.
I will see if I can find a stock firmware package, but it will be the same type of flashing.
D
.
I will post some links tonight when I get home to stock..
and try an re-write my instructions..
Check back in a bit!
nycbjr said:
I will post some links tonight when I get home to stock..
and try an re-write my instructions..
Check back in a bit!
Click to expand...
Click to collapse
You have a factory made one? Not a pulled one?
You cannot flash a pulled one, something people new to Samsung may not know.
D
.
Error flashing Root files through CWM...
I odined the recovery and now I have CWM. But when I try to flash the Root file (through install zip from sdcard) it says:
E:Can't mount /sdcard/
Do I have to have an external SD card or something?
What should I do?
Edit: I mounted an external Micro SD card and it worked flawlessly. Please add this mote in the OP, thanks a lot...
ahmadshawki said:
I odined the recovery and now I have CWM. But when I try to flash the Root file (through install zip from sdcard) it says:
E:Can't mount /sdcard/
Do I have to have an external SD card or something?
What should I do?
Edit: I mounted an external Micro SD card and it worked flawlessly. Please add this mote in the OP, thanks a lot...
Click to expand...
Click to collapse
Yes, clockwork uses an ext card.
D
.
How can I unroot my tab?

[Q] Triangle away with original rom

Hi, at first I want to say, that I wanted to post into the original thread, but I can't since I don't have permission to write into a developer thread. I just used Triangle away on my mobile phone and it resseted the counter to exact 0. Everything works fine and I'm good, but now, I want to also flash the original rom again, what would increase the counter to 1. Can I use triangle away also on an original rom? or only at custom rom?
and what is about the root? do i have to unroot my mobile phone if i want to send it back to samsung? or would it be enough if i flash an original rom and reset the flash counter to 0?
fluttershy said:
Hi, at first I want to say, that I wanted to post into the original thread, but I can't since I don't have permission to write into a developer thread. I just used Triangle away on my mobile phone and it resseted the counter to exact 0. Everything works fine and I'm good, but now, I want to also flash the original rom again, what would increase the counter to 1. Can I use triangle away also on an original rom? or only at custom rom?
and what is about the root? do i have to unroot my mobile phone if i want to send it back to samsung? or would it be enough if i flash an original rom and reset the flash counter to 0?
Click to expand...
Click to collapse
If your counter is already 0, then you can just flash stock rom using pc odin and doing so will not raise the counter.. Also when you flash the stock rom it removes any kind of modification like custom kernel, root etc. Head over to this thread if you want to download and flash stock rom of your country with tutorial for flashing stock rom too:
http://forum.xda-developers.com/showthread.php?t=1424997
treacherous_hawk said:
If your counter is already 0, then you can just flash stock rom using pc odin and doing so will not raise the counter.. Also when you flash the stock rom it removes any kind of modification like custom kernel, root etc. Head over to this thread if you want to download and flash stock rom of your country with tutorial for flashing stock rom too:
http://forum.xda-developers.com/showthread.php?t=1424997
Click to expand...
Click to collapse
Hi, thanks for the answer, but I'm following every step and Odin tells me the following:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_N7000XXLT4_N7000OXALT4_1103517_REV02_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
try to put the phone into download mode again (power+volume down+home button) and connect to computer, make sure kies service is not running in the background (end it with task manager along with antivirus) and if it is desktop connect the usb cable to the back usb port on the computer or in laptop you can connect it to back usb port if there is such usb port. Follow the instructions again from Dr. Ketan's thread coz the log you mentioned does not seem complete. also make sure you have the correct firmware downloaded and that too complete only extract the main zip file to get tar.md5 file.
treacherous_hawk said:
try to put the phone into download mode again (power+volume down+home button) and connect to computer, make sure kies service is not running in the background (end it with task manager along with antivirus) and if it is desktop connect the usb cable to the back usb port on the computer or in laptop you can connect it to back usb port if there is such usb port. Follow the instructions again from Dr. Ketan's thread coz the log you mentioned does not seem complete. also make sure you have the correct firmware downloaded and that too complete only extract the main zip file to get tar.md5 file.
Click to expand...
Click to collapse
Hi, thanks again, but this didn't work also, so I just tried to download the latest Odin Version (3.04) and with this version it worked without any other problems. But there must a reason that the xda-developers recommend Odin v1.85 instead of version 3. So if you found this thread with Google don't rely on me here.
fluttershy said:
Hi, thanks again, but this didn't work also, so I just tried to download the latest Odin Version (3.04) and with this version it worked without any other problems. But there must a reason that the xda-developers recommend Odin v1.85 instead of version 3. So if you found this thread with Google don't rely on me here.
Click to expand...
Click to collapse
i am still using Odin3 V1.85 and it works always. Haven't used any other version but sure should be the same with others too.
Check if a kies process is running in the background. Like device manager or connection manager.
Sent from my GT-N7000 using xda premium

[Q] rooted Gt7000 that I pressed update firmware,now not working . . please help

Hello All
I have a GT 7000 with stock 4.1.2 on it and it is only rooted.
It told me it had downloaded firmware update which i pressed install ( not knowing I shouldn't have because of my note being rooted) , and in doing so it is now just showing the little android dude with the blue thing in his tummy going round
Pressing volume up, home, power button won't do anything.
I can only get it into odin mode ( volume down, home, power button )
I am a complete noob and not sure what to do to get my note to work.
A friend said I need to flash a new rom via odin and I cant find a clear guide on how to do that.
For I can't afford to brick my note.
Please help
Kindest regards
pipsqueak 22 ooox
You have to have the samsung drivers installed for odin to work.
To get a stock rom google for sammobile. There are all official formwares (You will have to register).
After that extract that file, run odin and select the pda file (extracted md5 file).
Flash it. After reboot go to stock cwm and wipe data.
You should be fixed now.
Sent from note, a phone like never before
Odin is the way to go and the only way. Use this link http://forum.xda-developers.com/showthread.php?t=1901191 it will show how to flash Philz kernel on your phone and then you will have cwm. After that you will have to get a cwm flashable Rom out of the android dev section and put on your sd card, usb mass storage my work in philz kernel if so just put Rom on card and flash through cwm. Then phone will work or find a guide on pc Odin for flashing stock n7000 roms they are out there
Sent from my GT-N7000 using XDA Premium 4 mobile app
This just happened to me!!
Thanks jakuburban for your advice.
Though i didn't need to "After reboot go to stock cwm and wipe data." or maybe i do.
I just let it finish booting etc and everything was working fine,everything intact and okey dokey.
Can anyone say why this happened and what to do about updates in the future please?
Thanks again guys.:laugh:
Yeah, you sometimes don't need to wipe data. I told You to do this to be 100% sure it will work.
For the future, You can't use official update if You have root (normally it should give You information that You can't update the os because "Your device has been modified"), as You don't have original cwm and it won't boot into cwm to update Your os.
Sent from note, a phone like never before
Okey dokey.
Thanks again for the info.
Still having Trouble
Hi Guys,
Thanks heaps for your advice
I did what you said jakuburban but odin would get through seemmed like it was almost there then hung/froze
this is what was in the Odin txt box
"
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N5120XXCMI1_N5120VNZCMH5_N5120XXCMG7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection.."
and just hung/froze at that point well over an hour.
and unpluged it - can still only get into odin mode
Not sure what to do?
Is this where I have to flash a hole new Rom?
Im not sure how to do this as I was looking at putting cyanogenMod rom on but I was reading some where not all rom's come in .tar forms
and I downloaded the latest stable rom from cyanogenMod but it is a . zip
so im not sure what to do there?
Thanks heaps
pipsqueak 22
Hanging at that place means there is some problem with the connection between note and pc. Make sure you have all the drivers installed and use original USB cable and main USB ports.
zip file roms need to be installed using clockwork mod recovery.
nokiamodeln91 said:
Hanging at that place means there is some problem with the connection between note and pc. Make sure you have all the drivers installed and use original USB cable and main USB ports.
zip file roms need to be installed using clockwork mod recovery.
Click to expand...
Click to collapse
yes I Used the origianl USB cable and have the latest Usb driver
turned off my firewall and antivirus softwared ( on work desktop)
then tryed on my laptop using kies USB driver - still no luck
ooo
Pipsqueak22 i've PM'd ya.
Yes you WILL be flashing a new ROM in Odin.
Make sure it's the right ROM you need.:good:
Raggerty64 said:
Pipsqueak22 i've PM'd ya.
Yes you WILL be flashing a new ROM in Odin.
Make sure it's the right ROM you need.:good:
Click to expand...
Click to collapse
Thanks ooo

Invalid argument in twrp recovery fix/ unable to mount error fix.

DISCLAIMER:TRY ON YOUR OWN RISK IF YOUR DEVICE IS ALLREADY MESSED UP THEN NO NEED TO WORRY TO TRY THIS OUT.
Hello everyone i created this odin flashable file for following errors and devices this file will hopefully will fix any of this errors. THERS IS NO ANY BOX REQUIRED LIKE Z3X OR OCTOPUS FOR THIS METHOD.
This will work for allmost all samsung devices running 4.2.2 ,4.4.4,5.0,5.1.1 ( 6.0 not tested yet let me know if someone have tested it)
Invalid argument in twrp recovery
Unable to mount cache
Unable to mount efs
Unable to mount system
Unable to mount data
Unable to mount cache,efs,system in stock recovery
HOW TO FLASH
1 OPEN ODIN TOOL 3.10 OR HIGHER
2 CHOOSE IN ODIN ( BL ) TAB AND SELECT FILE IN DOWNLOAD LINK.( DONT CHOOSE AP TAB IT WON'T WORK )
3, GO TO DOWNLOAD MODE AND CONNECT DEVICE WITH PC
4, PRESS START IN ODIN UNTIL IT SAYS (PASS)
TESTED WITH FOLLOWING DEVICES
GALAXY S3 ( Tested with 4.2.2)
GALAXY GRAND NEO( Tested with 4.2.2)
GALAXY S4 ( tested with 4.2.2,5.0)
GALAXY NOTE 3 (TESTED WITH N9005 4.4 & 5.0)
GALAXY NOTE 4 (TESTED WITH 4.4.4 & 5.0,5.1.1 NOT TESTED WITH 6.0.1)
GALAXY GRAND 2 ( tested with 4.2)
GALAXY GRAND NEO PLUS ( tested with 4.4.4)
GALAXY GRAND DOUS ( tested with 4.2)
GALAXY NOTE 2 ( tested with 4.4.2)
GALAXY S5 ( TESTED WITH 4.4.4 & 5.0 )
I'LL UPDATE MORE MODELS AS SOON I TEST THEM
PLEASE REPORT BACK HERE IN THIS THREAD IF IT WORKS FOR YOUR DEVICE.
DONT FORGET TO HIT THANKS
Download link
https://mega.nz/#!3YtWAQyb!4w5TjsBP2Br6YkRmra6GauNBgcTp_mRLxLrRkuCMghI
Guys anyone successful with this method please report back here
Hey!
I would try it but Odin says:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> TREX888_EFS_FIX.tar.md5 is invalid.
<OSM> End...
Can you help?
Thanx
aaxaaxaax said:
Hey!
I would try it but Odin says:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> TREX888_EFS_FIX.tar.md5 is invalid.
<OSM> End...
Can you help?
Thanx
Click to expand...
Click to collapse
Sorry this file was broken i uploaded again here you go.
https://mega.nz/#!3YtWAQyb!4w5TjsBP2Br6YkRmra6GauNBgcTp_mRLxLrRkuCMghI
Everytime I try to update my N910F Galaxy Note4 KK4.4.4, Odin stops working and the window closes
AfXv237 said:
Everytime I try to update my N910F Galaxy Note4 KK4.4.4, Odin stops working and the window closes
Click to expand...
Click to collapse
Which system you are running right now ? If you are on lollipop or marshmallow then you cannot go back to kitkat because bootloader is locked.
You can flash 5.1.1 lollipop or 6.0.1 marshmallow.
Trex888 said:
Which system you are running right now ? If you are on lollipop or marshmallow then you cannot go back to kitkat because bootloader is locked.
You can flash 5.1.1 lollipop or 6.0.1 marshmallow.
Click to expand...
Click to collapse
My phone is kind of messed up for 2 weeks now. I had Marshmallow 6.0.1 and I wanted to update to a newer 6.0.1 version via Odin, but it failed and ever since I can't get it working. I believe the main reason is because I was running CNX version I tried upgrading to DBT version without a PIT file. I tried all versions (with PIT files, CS, BL). I have over 100gb of downloaded versions and can't get it working. I get all those failed to mount cache, data, efs etc errors and can't do anything. I can't format and repair data or cache or system via TWRP recovery. However, a few times the phone started up. I don't know how, but it started 3 or 4 times and worked flawless (even for 2 hours with Kit Kat 4.4.4. It started with 6.0.1 as well), but after I restarted it to introduce the SIM card, it got stuck on boot and has shown me the same failed to mount errors in recovery.
Do you have any solutions?
AfXv237 said:
My phone is kind of messed up for 2 weeks now. I had Marshmallow 6.0.1 and I wanted to update to a newer 6.0.1 version via Odin, but it failed and ever since I can't get it working. I believe the main reason is because I was running CNX version I tried upgrading to DBT version without a PIT file. I tried all versions (with PIT files, CS, BL). I have over 100gb of downloaded versions and can't get it working. I get all those failed to mount cache, data, efs etc errors and can't do anything. I can't format and repair data or cache or system via TWRP recovery. However, a few times the phone started up. I don't know how, but it started 3 or 4 times and worked flawless (even for 2 hours with Kit Kat 4.4.4. It started with 6.0.1 as well), but after I restarted it to introduce the SIM card, it got stuck on boot and has shown me the same failed to mount errors in recovery.
Do you have any solutions?
Click to expand...
Click to collapse
Are you sure you are flashing correct firmware for your model ? Take a screenshot of about device and a picture of download mode and I'll see what i can do
Without knowing enough information i cant help
Trex888 said:
Are you sure you are flashing correct firmware for your model ? Take a screenshot of about device and a picture of download mode and I'll see what i can do
Without knowing enough information i cant help
Click to expand...
Click to collapse
http://forum.xda-developers.com/not...icked-ecant-mount-cache-t3488486#post69328395
Do you have it as zip file so I can load it with adb sideload filename.zip method?
only snapdragon, correct? exynos here
efs fix
thanks it worked on a Samsung GT-N8013, but now shows PDA info ..Any help on this
matsr04 said:
thanks it worked on a Samsung GT-N8013, but now shows PDA info ..Any help on this
Click to expand...
Click to collapse
Flash stock firmware for your model via Odin.
After flash boot into stock recovery and wipe cache+data factory reset then reboot.
Hope this helps.
caarlosl said:
only snapdragon, correct? exynos here
Click to expand...
Click to collapse
Exynos will work too but which samsung model you have ?
I did not tested on note 4 exynos but it should work because note3 exynos it worked for me.
It wont brick your device unless you miss some steps and if your device is already in weird condition then give it a try and report back so others may know too.
Trex888 said:
Sorry this file was broken i uploaded again here you go.
https://mega.nz/#!3YtWAQyb!4w5TjsBP2Br6YkRmra6GauNBgcTp_mRLxLrRkuCMghI
Click to expand...
Click to collapse
Hi I hope you can help......I have this ERROR & I tried several ways to fix it Running the EFS Professional.exe as Administrator.....& it keeps telling me I don't have enough storage & I deleted a bunch of apps & data from phone /sd but I keep getting this error unable to back up certain partitions
dd:writing'/sdcarrd efsprobackup/temp/userdata no space left on device
887462+0records in
887461+0records out
363504025 btes (3.4gb) copied,94,239635 seconds,36.8 MB/s
exitcode=1
now I tried your method & it says invalid binary,......plz assist
thanks it works on GT i9060.. much appreciate it

Categories

Resources