Develop Bugs

[Q]I can get into TWRP, can't reflash 4.3, hangs @ ATT logo.$5 Paypal if you can fix!

Hello all,
I flashed and rooted my SGIII about 6 months back using these threads
http://forum.xda-developers.com/showthread.php?t=2387423
http://forum.xda-developers.com/showpost.php?p=47747640&postcount=1
Everything was running fine until Saturday, I noticed my phone kept shutting off in my pocket. Once i got home and started doing diagnostics, i couldn't really tell what caused it, i uninstalled the realtor.com app i had downloaded Saturday during the day just in case and wiped the cache of a bunch of apps I had before the problem started. The problem still exists, the phone will randomly flicker 3 or 4 times, the shutdown menu shows up then goes away, then it turns off and i have to boot it back up manually.
Anyone else had this issue?

It seems as though these threads come pretty frequently here lately, I am going to suggest a power button, it is a fairly common failure. On a good working phone if you push and hold the power button for 10 seconds it will turn the phone off, but not before popping up the power/reset menu.
Good luck hope you get it fixed quickly and perhaps I'm wrong?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Starting to think this is hardware related, i did a complete factory reset and same issue occurred. Now I have to take it back to stock and see if I have a case for a replacement.
Since i updated and rooted as I did, am I screwed?

now it seems to be soft bricked.. this is fun

Did you ever install the 4.3 OTA update on your phone? If not, you should be able to flash back to rooted stock, install and run Triangle away, flash back to non-rooted stock, and you should be fine.

audit13 said:
Did you ever install the 4.3 OTA update on your phone? If not, you should be able to flash back to rooted stock, install and run Triangle away, flash back to non-rooted stock, and you should be fine.
Click to expand...
Click to collapse
Yea I did, I'm currently searching how to do this process post-4.3 update

update: so i can get into TWRP just fine, cannot reflash 4.3 update, getting an error no MD5 file found, and "assert failed: apply_patch_check ("system/app/Bo.. it cuts off from there.. then says E:Error executing updater binary in zip
if i reboot it just hangs at the ATT logo
what I have done so far was backed up before this brick started, then factory reset, data and all cache, since the factory reset I haven't gotten past the ATT logo.
Not going to sleep tonight until this is solved, I know someone can help me since I can still get into TWRP
Was thinking of trying to ODIN back to 4.1.1 then flash 4.2 then flash 4.3 but I am pretty sure that will hard brick it right?
$5 paypal to whoever fixes this for me!

wellppp think i bricked it

serstylz2 said:
wellppp think i bricked it
Click to expand...
Click to collapse
I had similar issue before.
Here is what I did to recover
1. Make sure you are using TWRP 2.6.3.1 (I used 2.6.3.0 tried the steps below, the device was stuck at AT&T logo, I thought you have the same version?)
(TWRP 2.6.3.1 is available here http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar, you can flash it with ODIN v3.07)
2. Download a "almost official stock rom" from http://forum.xda-developers.com/showpost.php?p=47816011&postcount=18
3. Put the rom in SD card.
4. Boot into TWRP recovery.
5. Wipe->Format Data->Yes
6. Wide->Swipe to Factory Reset
7. Wide->Advanced Wipe->Check Dalvik Cache and Cache->Swipe to Wipe
8. Install->external_sd->AT&T_I747UCEMJB.zip
9. Reboot and done.

JEdad26 said:
I had similar issue before.
Here is what I did to recover
1. Make sure you are using TWRP 2.6.3.1 (I used 2.6.3.0 tried the steps below, the device was stuck at AT&T logo, I thought you have the same version?)
(TWRP 2.6.3.1 is available here http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar, you can flash it with ODIN v3.07)
2. Download a "almost official stock rom" from http://forum.xda-developers.com/showpost.php?p=47816011&postcount=18
3. Put the rom in SD card.
4. Boot into TWRP recovery.
5. Wipe->Format Data->Yes
6. Wide->Swipe to Factory Reset
7. Wide->Advanced Wipe->Check Dalvik Cache and Cache->Swipe to Wipe
8. Install->external_sd->AT&T_I747UCEMJB.zip
9. Reboot and done.
Click to expand...
Click to collapse
Wish I saw this earlier, probably would have worked. It doesn't even turn on anymore. Thank you for the help though. Just going to put in a claim and say I ran it over with my car or something

serstylz2 said:
Wish I saw this earlier, probably would have worked. It doesn't even turn on anymore. Thank you for the help though. Just going to put in a claim and say I ran it over with my car or something
Click to expand...
Click to collapse
Did you brick it because you downgraded from 4.3 to 4.1.1? you might still have chance to unbrick it although I've never tried it.
Here is the thread. http://forum.xda-developers.com/showthread.php?t=2549068

JEdad26 said:
Did you brick it because you downgraded from 4.3 to 4.1.1? you might still have chance to unbrick it although I've never tried it.
Here is the thread. http://forum.xda-developers.com/showthread.php?t=2549068
Click to expand...
Click to collapse
Also would have probably worked if I had any life at all from this thing. I think this was destined to break, I believe hardware failed.
It broke when I tried flashing d2att_I747UCUEMJ2_bootloader_modem after flashing boot_CWM_I747UCUEMJB

UPDATE: Able to get back into Download mode, TWRP and it still hangs at the ATT logo. Was able to do that by sticking a debrick dump img on my sd card and doing that method. Now I am trying to fully follow thru with that thread (http://forum.xda-developers.com/showthread.php?t=2549068) but I still have never seen a stock 4.3 that i can flash via ODIN, i asked them where I can find that. I may try these directions in the meantime (Also, I tried to update to TWRP 2.6.3.1 and ODIN froze on the checking .md5 step so, maybe that's the issue to begin with?)
1. Make sure you are using TWRP 2.6.3.1 (I used 2.6.3.0 tried the steps below, the device was stuck at AT&T logo, I thought you have the same version?)
(TWRP 2.6.3.1 is available here http://techerrata.com/file/twrp2/d2a....3.1-d2att.tar, you can flash it with ODIN v3.07)
2. Download a "almost official stock rom" from http://forum.xda-developers.com/show...1&postcount=18
3. Put the rom in SD card.
4. Boot into TWRP recovery.
5. Wipe->Format Data->Yes
6. Wide->Swipe to Factory Reset
7. Wide->Advanced Wipe->Check Dalvik Cache and Cache->Swipe to Wipe
8. Install->external_sd->AT&T_I747UCEMJB.zip
9. Reboot and done.

Welp I'm finally back up.. here's what I had to do
First, had to get a debrick img from http://forum.xda-developers.com/showthread.php?t=2549068&page=3
Then carried out these steps
First:
I used "Win32DiskImage" Located here But you can also use dd to write the image to your sd card in Linux.
On Windows:
Open Win32DiskImage. Brows to the Debrick dump you have for your device. Select the drive letter if your micro sd in the drop-down, click write. Bam done.
On Linux:
For ease of example, and method. Open Gparted on your Linux install or live cd, check the dev your sd card is in the drop down menu. For example mine was /dev/sdb/ then use "dd if=/path/to/debrick/dump.img of=/dev/sdb/" This method also works. Be careful you are selecting the right dev or you will overwrite another disk on your system. YOU HAVE BEEN WARNED.
Second:
Put that SD card in your device insert the battery and if the SD card is written correctly with a proper debrick file. You can put a jig in the device and it will boot straight to download mode. If you dont have a jig hold Vol Down + Home + Power the device will boot to download. If it does not, either the image didn't write to the card properly ( I had to write it a few times with Win32DiskImager, DD worked fine the first try), the debrick dump is no good. Or your trying to debrink your 4.3 bootloader downgrade brick with a dump from 4.1.2 compatible bootloaders. this will not work the blown efuse will still prevent the bootloader from booting from the SD card as well as the EMMC. You will know pretty fast if it worked, as the device will vibe with the jig or it will vibe with the button combo almost immediately after being pressed and held.
booted to Recovery, then basically whipped through these steps
"You will need to copy all of the files you are going to flash (you can download them below) onto your 1GB or larger SD card. You then Need Put your Debrick SD card in the Phone, Remove and reinstall the battery,Put the Phone in Recovery Mode (Must Be Either TWRP or CWM Instructions and TWRP Download Below), Dismount the Debrick SD card, Insert your SD card with your Bootloaders, ROM, kernel, and Modem into the Phone, Mount the SD card, Flash your files one at a time, wipe the cache and dalvik between each file, Once you are done reboot the system, You Might have to put the debrick SD back in and do another battery pull, boot up the phone, after you get in the phone reboot it without the Debrick SD card in. If it will not Boot on its own see the link below."
My original problem came when i removed the debrick SD and inserted the file SD, i wasn't mounting so i was confused for a min. Then the ROM i was trying to flash was the "update43" from the OTA 4.3 update thread, that does not work, ended up using the "almost Stock" from here http://forum.xda-developers.com/showpost.php?p=47816011&postcount=18
And I was good after that. Basically I just went a long way to do what the tuts had already said to do, and the screen flickering is also gone along with the random reboots i was getting.
Very thankful for this forum and you all

[SOLVED] How do you enter recovery mode for TWRP ? (Bootloop)

Hello everyone. I was attempting to install the Liquid Smooth 3.0 Beta ROM but it said failed in red words. So i wiped again and installed my backup. Its been stuck in boot loop. I've looked and can't seem to find how to enter recovery mode. I tried holding power + volume up + home and it just restarts the phone before it gets to the boot loop screen. Also, once I get in recovery mode, what would be the next step to fix the boot loop? Right now im reinstalling the ROM I had on backup (intergalactic) . Or should I wipe and re-install the backup?
Thanks
EDIT: Found the combo ( Volume up + home ). Now restoring my backup. If this doesn't fix the bootloop what should I do? Also when I mount my USB in recovery it doesn't show up on my computer.

TrippyAzN said:
Hello everyone. I was attempting to install the Liquid Smooth 3.0 Beta ROM but it said failed in red words. So i wiped again and installed my backup. Its been stuck in boot loop. I've looked and can't seem to find how to enter recovery mode. I tried holding power + volume up + home and it just restarts the phone before it gets to the boot loop screen. Also, once I get in recovery mode, what would be the next step to fix the boot loop? Right now im reinstalling the ROM I had on backup (intergalactic) . Or should I wipe and re-install the backup?
Thanks
EDIT: Found the combo ( Volume up + home ). Now restoring my backup. If this doesn't fix the bootloop what should I do? Also when I mount my USB in recovery it doesn't show up on my computer.
Click to expand...
Click to collapse
If you get to recovery mode, try doing a hard wipe/reset to return your phone to its original settings. You will lose all saved data so please keep your backup. Your phone may not be recognized by the computer in recovery mode but in download mode. Are you using custom recovery or stock recovery? If custom, which one?

Larry2999 said:
If you get to recovery mode, try doing a hard wipe/reset to return your phone to its original settings. You will lose all saved data so please keep your backup. Your phone may not be recognized by the computer in recovery mode but in download mode. Are you using custom recovery or stock recovery? If custom, which one?
Click to expand...
Click to collapse
Hello. How do I Hard Reset? I am using TWRP recovery mode. I've tried download mode and still not recognized. I also downloaded the latest driver.

TrippyAzN said:
Hello. How do I Hard Reset? I am using TWRP recovery mode. I've tried download mode and still not recognized. I also downloaded the latest driver.
Click to expand...
Click to collapse
Good! With TWRP, you will see the wipe option on the home screen immediately you get into recovery mode. Just do the standard wipe and then reboot to system.

Larry2999 said:
Good! With TWRP, you will see the wipe option on the home screen immediately you get into recovery mode. Just do the standard wipe and then reboot to system.
Click to expand...
Click to collapse
Just did that, still at the boot screen

TrippyAzN said:
Just did that, still at the boot screen
Click to expand...
Click to collapse
Sometimes, it may take several minutes after the reset for your phone to finally boot up so you may have to wait a bit before deciding it didn't work. However, do you recall what (stock) Android version you had before you attempted to flash the custom ROM?

Larry2999 said:
Do you recall what (stock) Android version you had before you attempted to flash the custom ROM?
Click to expand...
Click to collapse
Before I rooted? I was Jelly Bean 4.1.2 I think. But I flashed many Custom ROMs, the last one was 4.3 . The one I was installing was 4.4.2. But I dont think thats the problem, It just said failed to flash. And the back up restore was successful, just a boot loop. If I could get my computer to recognize my phone I could put my original ROM download in and flash that.

TrippyAzN said:
Before I rooted? I was Jelly Bean 4.1.2 I think. But I flashed many Custom ROMs, the last one was 4.3 . The one I was installing was 4.4.2. But I dont think thats the problem, It just said failed to flash. And the back up restore was successful, just a boot loop. If I could get my computer to recognize my phone I could put my original ROM download in and flash that.
Click to expand...
Click to collapse
Normally, if it was just a case of your phone getting stuck in a boot loop, a hard wipe/reset will fix that. If it's still not coming on, then it could be a slightly more severe case of firmware failure which, thankfully, can be easily recovered from since you can get into download and recovery modes. Your best option now would be to flash an official (stock) ROM to get your phone back in working order. From what you've said about the firmware history, stock Android 4.3 would be your best bet as you probably have the 4.3 boot-loader already. You can download the zip file you will find in the discussion thread below and flash this via TWRP recovery. The process is fairly simple. Download the zip file to your PC - do not extract. Verify the MD5. Copy to a micro SDHC card. Place the card in your phone. Boot to recovery mode. Select install and navigate your way to the zip file you just copied. Swipe across the screen to confirm installation. Wait for installation to complete. Clear your cache/dalvik. Reboot your system. Good luck!
http://forum.xda-developers.com/showthread.php?t=2658486
Before flashing custom ROMs, it is always helpful to do a lot of research as there is no easier way to brick or backdoor your phone.
NB
You need a special app to verify MD5. It's just a check to ensure you have the correct file and it downloaded correctly. If you do not have the app, check that the zip you have is about 933MB after download.

Larry2999 said:
Normally, if it was just a case of your phone getting stuck in a boot loop, a hard wipe/reset will fix that. If it's still not coming on, then it could be a slightly more severe case of firmware failure which, thankfully, can be easily recovered from since you can get into download and recovery modes. Your best option now would be to flash an official (stock) ROM to get your phone back in working order. From what you've said about the firmware history, stock Android 4.3 would be your best bet as you probably have the 4.3 boot-loader already. You can download the zip file you will find in the discussion thread below and flash this via TWRP recovery. The process is fairly simple. Download the zip file to your PC - do not extract. Verify the MD5. Copy to a micro SDHC card. Place the card in your phone. Boot to recovery mode. Select install and navigate your way to the zip file you just copied. Swipe across the screen to confirm installation. Wait for installation to complete. Clear your cache/dalvik. Reboot your system. Good luck!
http://forum.xda-developers.com/showthread.php?t=2658486
Before flashing custom ROMs, it is always helpful to do a lot of research as there is no easier way to brick or backdoor your phone.
NB
You need a special app to verify MD5. It's just a check to ensure you have the correct file and it downloaded correctly. If you do not have the app, check that the zip you have is about 933MB after download.
Click to expand...
Click to collapse
Which do I download? First or second link? Also How should I get my computer to recognize my phone? And if I do that, flashing a fresh ROM wont fix the boot loop?

TrippyAzN said:
Which do I download? First or second link? Also How should I get my computer to recognize my phone? And if I do that, flashing a fresh ROM wont fix the boot loop?
Click to expand...
Click to collapse
You need the first one since you are on TWRP. You are not connecting your phone to the computer at all so there is no worry about that. You only need to download the image to your computer and then copy it to an external Micro SD card using another device like a camera, phone, SDHC card reader/writer or SDHC card adapter if your PC has the required slot. Once you have the recovery image saved on to the external SD card, insert the card into your phone and boot into recovery mode. You will then install the zip from the card. This ROM should not only fix the boot loop, it will restore your phone to as near factory settings as possible including resetting your flash counter, installing the complete stock system and stock recovery.
Once you have your phone back in working order, you can revert to flashing custom ROMs but please be very careful and do all the research you need. Specifically, you should avoid any ROMs that may attempt to mess with your boot-loader.

Larry2999 said:
You need the first one since you are on TWRP. You are not connecting your phone to the computer at all so there is no worry about that. You only need to download the image to your computer and then copy it to an external Micro SD card using another device like a camera, phone, SDHC card reader/writer or SDHC card adapter if your PC has the required slot. Once you have the recovery image saved on to the external SD card, insert the card into your phone and boot into recovery mode. You will then install the zip from the card. This ROM should not only fix the boot loop, it will restore your phone to as near factory settings as possible including resetting your flash counter, installing the complete stock system and stock recovery.
Once you have your phone back in working order, you can revert to flashing custom ROMs but please be very careful and do all the research you need. Specifically, you should avoid any ROMs that may attempt to mess with your boot-loader.
Click to expand...
Click to collapse
Thanks for your help! That was a great idea, moving my SD card to a different device then putting the .zip in there and flashing from my device. Worked Perfectly. Didn't even have to use the restore file you linked me, I just re-flashed the old ROM i was using ( brand new, not the back up ). And its starting up now, all of my apps, widgets, wallpapers, and messages are exactly how I left them. Which is weird because of how many times I wiped and the fact that I re-flashed a brand new ROM lol.
Man this makes me not want to change ROMs anymore. Small stuff like this makes me paranoid. I don't have a back up phone lol

TrippyAzN said:
Thanks for your help! That was a great idea, moving my SD card to a different device then putting the .zip in there and flashing from my device. Worked Perfectly. Didn't even have to use the restore file you linked me, I just re-flashed the old ROM i was using ( brand new, not the back up ). And its starting up now, all of my apps, widgets, wallpapers, and messages are exactly how I left them. Which is weird because of how many times I wiped and the fact that I re-flashed a brand new ROM lol.
Man this makes me not want to change ROMs anymore. Small stuff like this makes me paranoid. I don't have a back up phone lol
Click to expand...
Click to collapse
Glad to know your phone is now functioning normally. One of your earlier restore operations probably restored your data whilst the new ROM you flashed restored the system without deleting data. Thankfully, you didn't lose anything. Now the phone is back to normal, please be careful with flashing ROMs especially custom ones.

Rooting and flashing ROMS with T-Mobile Note 3 with KitKat

Ok. I have seen several people asking about rooting their T-Mobile Note 3. I am sure there have been posts on how to accomplish this feat. I am going to put out the steps that I took and mention a few other options and my thoughts on those. I hope to make this an all inclusive post for newbies. This method works whether you are on 4.3 or 4.4 BUT you will need to make sure the recovery and ROM you download is for the correct version of android you are using. To make this easier I am going to assume you are already on 4.4 Not everything will be clear but should be able to be easily understood. If there is something you don't understand ask and I am sure people will try to help. That or you can do a google search and probably find the answer a whole lot faster. If you did have a problem and found the solution please post it so others can use your information. I don't have the time at the moment to provide all the links but I will try to update this thread as much as I can.
I am NOT responsible for bricked devices, voided warranties or downloaded virus to your computer.
That being said rooting should be a relatively simple and easy process.
1. Download Odin 3.07 or 3.09 .zip file and install on your computer. (I have found no real difference in between the two when attempting root.) (No link provided just google it.)
2. Download the custom recovery of you choice. (I use and prefer twrp, but some people have had problems flashing ROMs and have had better luck with philz recovery) Below is the link for TWRP. If using 4.4 make sure to download the img.tar file for 2.7. There are other files but you want the one ending in img.tar! http://teamw.in/project/twrp2
3. Open Odin and connect your phone. You need to put your phone into download mode before connecting. Shut your phone off and then turn back on while holding volume down, power and home key. You will see a special screen pop up and a warning. Acknowledge the warning and the connect to the computer. If you don't get a blue bar on the left side of Odin after connecting your phone then you need to update your driver's (google search).
4. Place the .tar file that you downloaded into the PDA(3.07) or AP(3.09) section. Make sure the ONLY boxes on the left are Auto Reboot and F. Reset Time are checked (that should be the default settings)!!
5. Hit the start button. Be advised that Flashing a custom recovery WILL trip Knox.
6. You should the blue bar turn green and say "pass." You know have a custom recovery on your phone and you can disconnect your phone.
At this point you do not have root access, you just have a custom recovery. You now have a choice to make. Do you want your phone rooted or do you want to flash a custom ROM. If you want to flash a custom ROM jump to #8. If you just want root and plan on staying on stock go to #7.
7. Download the latest version of SuperSU file from http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip and flash from your custom recovery. when you restart your phone make sure you can open the SuperSU app. If you cannot go to the play store and reinstall it from there. Congrats!!
8. If you want a custom ROM you need to download the .zip file of that ROM. I would recommend placing it on your EXTERNAL sd card.
9. Go to your custom recovery. There are some things you are going to need to back up prior to Flashing the ROM.
a. Backup your stock ROM, This could save you from some major problems. Back up-system, data and boot-to your EXTERNAL sd card.
b. Backup you EFS files (this can be done via twrp, other wise you will need to do it another way-Google search)
10. Wipe the phone. You want to wipe Data, Cache and Dalvik
11. Flash you custom ROM. Almost every custom ROM comes rooted. You just need to read the info on that ROM
12. Your phone should reboot and you are done!!
Below is some Q&A and helpful tips.
If I upgrade to 4.4 from 4.3 to get a diffent ROM can I switch back? NO
What is "Bricked"? It is a phone that will not boot and only stays on a black screen. Soft Brick is where your phone constantly reboots without opening your ROM.
What is Knox? Google it
Will tripping Knox void my warranty? Probably
How do I get into the recovery? Shut your phone off and then restart while holding the volume up, power and home key. You have to let go as soon as you see the blue letters "Recovery Booting"
There are not that many ROMS for T-mobile can I use an international ROM? Yes! I currently run an international ROM but on most of them you do loose your wifi calling feature. You also need to download a custom T-Mobile Kernel and the Wifi/BT fix.
Should I use CF Auto root or Klingo? I personally don't like the idea of Klingo. Some of the things I have seen they appear to be a little fishy and with them rooting your phone they initially have access to EVERYTHING. CF auto root does not place a custom recovery. You CANNOT flash a custom ROM without a custom recovery. I did it my way because I wanted a custom ROM and just not root.
What about the De La Vega Method? I have no idea and it seemed more work that it was worth. I did not care about tripping Knox
Tips:
Some ROMS will delete your internal memory when flashing as will wiping your phone. That is why I strongly suggest placing the backups and ROMS on your external sd card.
Some ROMS come with an Auroma set up. You will automatically be directed into it when you flash from recovery.
If you are flashing an international ROM make sure that you flash the ROM, T-mobile Kernel and Wifi Fix before choosing the reboot option. If you don't have the t-mobile kernel prior to reboot you will go into a bootloop.
I hope this helps and I will add more and clarify this post in the next few days. I just hope this can help some of you new guys out a little bit and if you found it useful especially if you obtained root please hit the thanks meter.

OK, I deleted all the information here about all the errors I made so that this won't confuse anyone. To summarize my error, I thought I had purchased Android 4.4.2 and flashed the wrong versions. After flashing the correct version, 4.3, everything worked.
The SD-card is not visible in stock recovery and the ADB method won't work without first having root, so that leaves the Odin method.
The Odin method flashes TWRP recovery successfully and when I exited it asked me if I wanted to root the device. I chose 'yes' and it worked for a while then booted into the Android OS. In Android it booted normally, then after I did something which I did not think about and don't recall, a dialog advised me that the GUI portion of the root process still needed to be applied. I allowed it to proceed and now I am rooted with TWRP. I verified the root through ADB by creating a file in the root directory.
Frank

I will try to break this down for you.
1. You need to reflash twrp via Odin to make sure it works correctly since doing auto root.
2. That screen you saw is exactly what you wanted to see. As stated in the OP when you see that screen let go of the buttons and wait, twrp will open shortly. I get the same screen so don't worry. Once you get into twrp and if you need a tutorial on twrp I would suggest looking it up on YouTube.
3. If you reflash the stock ROM via Odin it should fix everything. I am not sure about the partition problem. I will get back if I get some more info.
I would not worry about trying to reflash stock. I would just reflash twrp, boot into recovery and then proceed as listed in the OP.

Frank Westlake said:
**************************************************************************
I found my problem. I think the box, or something, was mislabeled because "About" tells me I have Android 4.3, not 4.4.2. So I flashed the 4.3 version of TWRP and booted right into it. After another reboot to make sure it's stable I'll try rooting again.
Frank
Click to expand...
Click to collapse
Great. Yes, it did not work because 2.7 is written for the new bootloader in 4.4. Are you planning on staying stock jb or planning on flashing a ROM?
sm-n900t: Powered by X-Note V13

FFTony said:
Are you planning on staying stock jb or planning on flashing a ROM?
Click to expand...
Click to collapse
Stock. With root I'm able to customize everything right on the device about as much as the ROM builders. But there are things I cannot do on the device so I'll be keeping an eye on the ROMs to see if anything is attractive.
After I finished this update I refreshed this page and saw that you had been commenting. The screen you saw should be there was also there when I flashed the correct TWRP, and it did move on to TWRP as you said. I'm adding the following paragraph separately so that it's easier for people to find if they need it:
After I had flashed the wrong version of TWRP (4.4 instead of 4.3) it boot-looped to the "SEANDROID NOT ENFORCING" display. To get out of that boot-loop I held the Download Mode keys (HOME-POWER-VOLDOWN) until it rebooted into the first download mode screen, the warning which says you can press VOL-DOWN to boot normally. At that point press VOL-DOWN and it will boot normally. If you press VOL-UP and continue into Download Mode then you will still be in the boot-loop when you reset the device and you will need to reboot again into the Download Mode warning screen and press VOL-DOWN to boot normally.
Thank you very much for your help with this.
Frank

FFTony said:
What about the De La Vega Method? I have no idea and it seemed more work that it was worth.
Click to expand...
Click to collapse
Samsung explains about Root De La Vega here: Samsungknox.com/en/blog/about-root-de-la-vega

[Q] S3 Gets stuck on ATT screen no root

I apologize in advance if this is in the wrong thread or section, I'm new to this and am kind of stuck on what to do next. If it is in the wrong section can you let me know where to post?
I'm not sure what the previous version my phone was on but in the recovery menu I see KOT49H.I747UCUFNE4 so I assume it was 4.4.2
Over the weekend I tried to update my stock I747 (no root) through menus using check for update and when it completed my phone would no longer boot.
It gets stuck on the ATT logo and when I try to wipe it in recovery mode it still gets stuck on the same screen.
I have also tried to use Kies but the devise does not show up under the emergency recovery option even though my phone can connect to the computer.
However I have no problems connecting to Odin in download mode.
So what would be the best option for me if I dont want to root my device? Can I use Odin or should I be using a different program?
If I have to root should I follow enewman17 tutorial? If so what step should I start at?
Thanks!

Are you running a stock recovery? Did you wipe everything in recovery?

yep stock recovery, tried to wipe everything but i get the same problem.

If I were in your situation, I would install a custom recovery and custom rom such as cm10.2 to get the phone up and running to verify the bootloader and modem currently on the phone.

Should I be installing the recovery through odin or an sd card? Do you have a link for a tutorial, I've looked through t3chn0s1s's sticky but most instructions seem like they are for phones that can boot.
The method I see using an sd card needs a terminal but i don't think i can get one because I can't boot my phone, is that correct?

Download the latest tar.md5 file from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Copy the latest CM10.2 or CM11 to your SD card. Place the SD card in the phone.
Flash Philz in the PDA section of Odin 3.07 and don't check anything except F.Reset Time. When you see "Reset" in the status window, disconnet the USB cable, pull the battery, replace the battery, boot into recovery, wipe cache, data, Dalvik, system, flash CM from the SD card, and reboot.

Thanks got it working last night!

If you want to run the latest CM11 or AOSP ROMs, you may have to update to the latest bootoader and modem.

[Q] deleted the os?

samsung galaxy tab 3 10.1
somehow deleted the os, twrp recovery console not allowing me to install any new zips.
any help please

Benjamus_Prime said:
samsung galaxy tab 3 10.1
somehow deleted the os, twrp recovery console not allowing me to install any new zips.
any help please
Click to expand...
Click to collapse
You don't have a backup that you can restore?

Can you flash the Stock-ROM with Odin?

Might need to reflash stock and root. See this

bdiddled said:
You don't have a backup that you can restore?
Click to expand...
Click to collapse
stupidly no

It will flash with odin, then when I try to install root and all that the customer recovery rom keeps saying failed. All I can s

OKAstro said:
Might need to reflash stock and root. See this
Click to expand...
Click to collapse
I'm in the same boat as the OP.. However, my PC will not recognize the tablet so I am unable to add files to the internal SD card. What are the steps I need to take to flash to the stock rom? I followed the link provided and flashed the recovery via Odin and I feel like Im still at step 0. What do I need to do from there? I really appreciate any help because I'm at a complete loss.

jaredmac11 said:
I'm in the same boat as the OP.. However, my PC will not recognize the tablet so I am unable to add files to the internal SD card. What are the steps I need to take to flash to the stock rom? I followed the link provided and flashed the recovery via Odin and I feel like Im still at step 0. What do I need to do from there? I really appreciate any help because I'm at a complete loss.
Click to expand...
Click to collapse
OK so you have kit kat and the custom recovery, right?
1. Download the file from step 3 in the link I provided and copy it to your phone's sd card.
2. Power off your phone.
3. Press the up VOL, Power Button and Home key all at the same time. release them when the samsung logo flashes.
4. If the phone reboots, power off and try again. You should now be at the TWRP recovery screen. If not then you didn't flash the recovery correctly. If not at the TWRP screen, repeat the recovery flashing step. Remember when in Odin, make sure the Auto Reboot is not checked. After it completes, power off the phone and repeat from step 3 above.
5. Once you get to the TWRP screen, select 'Install". Locate the SU zip file you copied in step 1 above, select it and slide the "slider" to flash it.
6. Reboot and that should do it.