Database Users

I made a newbie mistake.

So I was following xBeerdroiDx guide on backing up/rooting/flashing the AT&T Samsung Galaxy S4. I got right up to step 4B before I realized my PC wasn't detecting my S4 or external SD card, so I couldn't put a rom on there. I restarted and nothing will load...I'm trying to get into download mode, but it just restarts into the battery logo and shows no sign of charging. Please help.

IIMaxII said:
So I was following xBeerdroiDx guide on backing up/rooting/flashing the AT&T Samsung Galaxy S4. I got right up to step 4B before I realized my PC wasn't detecting my S4 or external SD card, so I couldn't put a rom on there. I restarted and nothing will load...I'm trying to get into download mode, but it just restarts into the battery logo and shows no sign of charging. Please help.
Click to expand...
Click to collapse
Turn the phone off, take the battery out (maybe 30 seconds), put the battery back in, but keep the phone off. Plug the charger into the phone and let it charge for a while without turning it on (you may need to let it charge to 100%). Then, try to get into download mode, Odin the factory firmware, factory reset, and start again. That is, if it works. Good luck.

IIMaxII said:
So I was following xBeerdroiDx guide on backing up/rooting/flashing the AT&T Samsung Galaxy S4. I got right up to step 4B before I realized my PC wasn't detecting my S4 or external SD card, so I couldn't put a rom on there. I restarted and nothing will load...I'm trying to get into download mode, but it just restarts into the battery logo and shows no sign of charging. Please help.
Click to expand...
Click to collapse
When I power it on it just shows Samsung with custom underneath it and my PC immediately attempts to install Samsung Mobile MTP Device.

IIMaxII said:
When I power it on it just shows Samsung with custom underneath it and my PC immediately attempts to install Samsung Mobile MTP Device.
Click to expand...
Click to collapse
Ok, You are giving conflicting information. Try to get into recovery. Use the various button combinations to get into recovery. If you don't know them, search for them. If you can get into recovery, try to install a nandroid (if custom) or try factory restore if 3e. Again, if you can get into download mode and let ODIN do a factory install would be better. Or you can try Kies emergency restore.

scott14719 said:
Turn the phone off, take the battery out (maybe 30 seconds), put the battery back in, but keep the phone off. Plug the charger into the phone and let it charge for a while without turning it on (you may need to let it charge to 100%). Then, try to get into download mode, Odin the factory firmware, factory reset, and start again. That is, if it works. Good luck.
Click to expand...
Click to collapse
Did what you said. Plug it in the battery logo shows up but it doesn't show if it's red or green it just stays there, I'm assuming it's still accepting the current and charging though.

scott14719 said:
Ok, You are giving conflicting information. Try to get into recovery. Use the various button combinations to get into recovery. If you don't know them, search for them. If you can get into recovery, try to install a nandroid (if custom) or try factory restore if 3e. Again, if you can get into download mode and let ODIN do a factory install would be better. Or you can try Kies emergency restore.
Click to expand...
Click to collapse
I love you! I got into TWRP Recovery...now how can get my phone working again? Is this recovery the same to where I can just use odin? or do I need to be in download?

IIMaxII said:
So I was following xBeerdroiDx guide on backing up/rooting/flashing the AT&T Samsung Galaxy S4. I got right up to step 4B before I realized my PC wasn't detecting my S4 or external SD card, so I couldn't put a rom on there. I restarted and nothing will load...I'm trying to get into download mode, but it just restarts into the battery logo and shows no sign of charging. Please help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1984717 try this

IIMaxII said:
I love you! I got into TWRP Recovery...now how can get my phone working again? Is this recovery the same to where I can just use odin? or do I need to be in download?
Click to expand...
Click to collapse
have you placed the ROM and any other potentially necessary files (gapps, loki-doki) on your device or it's micro sd card yet? if so, what rom?
i'm assuming you've already wiped everything and thats why your device wouldnt boot up.

IIMaxII said:
I love you! I got into TWRP Recovery...now how can get my phone working again? Is this recovery the same to where I can just use odin? or do I need to be in download?
Click to expand...
Click to collapse
If you are in TWRP, you need to either restore a nandroid backup (if you have one) or download a compatible ROM (and Kernel if necessary) and flash it. But make sure it is compatible to your device! If you don't have a ROM available on your SD Card, download one onto your PC and transfer it to your SD card (manually if needed). Once it is on your SD card, just flash through TWRP.
And always start making Nandroids before you do anything...just in case.

norbarb said:
http://forum.xda-developers.com/showthread.php?t=1984717 try this
Click to expand...
Click to collapse
The thing is...I wiped before I had a rom on my internal storage or SD card...and while I was in TWRP, my pc wouldn't detect internal storage or external for me to copy it over...so I just rebooted my phone hoping that it would work...stupid mistake.
Is this right and safe to continue? I'm in download mode.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

xBeerdroiDx said:
have you placed the ROM and any other potentially necessary files (gapps, loki-doki) on your device or it's micro sd card yet? if so, what rom?
i'm assuming you've already wiped everything and thats why your device wouldnt boot up.
Click to expand...
Click to collapse
I actually meant to respond to you in the post above. :/

IIMaxII said:
I actually meant to respond to you in the post above. :/
Click to expand...
Click to collapse
do you have a micro sd card?

xBeerdroiDx said:
do you have a micro sd card?
Click to expand...
Click to collapse
Yes. 64 GB Class10. Can you tell me if the post above is correct? I'm going to restore to stock firmware and then try the process again with the rom actually on the sd card. xD

Make sure if you use ODIN to restore that you get into recovery on the first boot and do a factory reset.

IIMaxII said:
Yes. 64 GB Class10. Can you tell me if the post above is correct? I'm going to restore to stock firmware and then try the process again with the rom actually on the sd card. xD
Click to expand...
Click to collapse
scott14719 said:
Make sure if you use ODIN to restore that you get into recovery on the first boot and do a factory reset.
Click to expand...
Click to collapse
OP, do you have a card reader for your pc that has a micro sd port or an sd adapter?

xBeerdroiDx said:
OP, do you have a card reader for your pc that has a micro sd port or an sd adapter?
Click to expand...
Click to collapse
Lets ignore the flashing for now...can you guys tell me if that appears correct in the screenshot I took? 0:[COM4] a youtube video I watched showed 0:[COM6] and I just want someone to confirm that what I'm doing is okay.

So twrp Dont find exsd?

IIMaxII said:
Lets ignore the flashing for now...can you guys tell me if that appears correct in the screenshot I took? 0:[COM4] a youtube video I watched showed 0:[COM6] and I just want someone to confirm that what I'm doing is okay.
Click to expand...
Click to collapse
The picture you posted looks fine. As long as your phone shows in the com port, ODIN recognized it. But there is never any guarantees. Everything should go OK, but there is always risk. I can tell you that it "appears" to be ready, but you will have to click the start button and see if it goes OK. As mentioned, make sure to boot into 3e recovery after ODIN reports successful and do a factory restore or it might not boot up right. Good luck. Let us know if it goes OK.

scott14719 said:
The picture you posted looks fine. As long as your phone shows in the com port, ODIN recognized it. But there is never any guarantees. Everything should go OK, but there is always risk. I can tell you that it "appears" to be ready, but you will have to click the start button and see if it goes OK. As mentioned, make sure to boot into 3e recovery after ODIN reports successful and do a factory restore or it might not boot up right. Good luck. Let us know if it goes OK.
Click to expand...
Click to collapse
I managed to restore to stock and everything is perfect! Now to get Cyanogenmod 10.1 on, unless you guys think there's something better?

IIMaxII said:
I managed to restore to stock and everything is perfect! Now to get Cyanogenmod 10.1 on, unless you guys think there's something better?
Click to expand...
Click to collapse
Make a nandroid...now. :good:

[Q] SGS4 sick recovery needed

I bricked my sgs4 when I used Rom Toolbox Pro to flash TWRP custom recovery. every time I unplug bat it goes into Odin mode. Every reboot with removal of battery. So I held down Volume- and home and power button the phone powered on to the screen asking if I wanted to go into Odin mode or Cancel. I. cancelled and was able to reboot successfully. Do I'm not completely bricked now. but when I try to get into stock recovery I get bricked to Odin mode. and have to remove the bat then volume- plus home plus power then Cancel going into Odin mode etc. I officially have no stock recovery
this is all due to the fact I went back after trying to flash cwm recovery...I flashed safestrap then removed it but still no recovery. and I really want the 4.3 that just came out.
btw safestrap is not working for me. I downloaded the kernel flash and a Rom specific for locked sgs4 ask I get after booting passed safestrap is a blank screen for ever.
Any help is great. thanks guys

Correct me if I'm wrong someone buy I'm pretty sure If you're boot loader is locked you are NOT to flash any custom recoveries or kernels. Safestrap is the only recovery you can use. I'm on mf3 myself, you may have to odin back to stock, root, and install safestrap again. Can't flash any kernels on mf3.. it will cause your phone not to boot.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

You are going to have to odin the stock tar files. I assume you are on mf3 firmware. Look for the mf3 tar files, there on one of the threads. Google "mf3 tar xda"

I looked for a link to firmware mf3 to flag in Odin but nothing
Already the bricking the phone deal is taken care of.

I don't know why its so hard for people to find stuff I googled it with results just fine.
http://forum.xda-developers.com/showthread.php?t=2502003
Sent from my SAMSUNG-SGH-I337 using xda premium

jd1639 said:
You are going to have to odin the stock tar files. I assume you are on mf3 firmware. Look for the mf3 tar files, there on one of the threads. Google "mf3 tar xda"
Click to expand...
Click to collapse
So do u have a link AT&T I337 MF3 firmware?

Lewis_Koseck said:
So do u have a link AT&T I337 MF3 firmware?
Click to expand...
Click to collapse
Google "mf3 tar xda"

WOW!

scott14719 said:
WOW!
Click to expand...
Click to collapse
That Google stuff is complicated, lol

Obviously I did and nothing. It's great when people ask for help all we get is snobbed nosed attitudes
And here I Google the brick problem Every one on xda saying only solution is Odin. And real no I was able to pull out of the brick without it so obviously not everyone is as smart as you guys but if it's even possible to keep your attitudes in check would be great!

jd1639 said:
That Google stuff is complicated, lol
Click to expand...
Click to collapse
Yeah must be.and neither me not anyone I know will be posting in xda sense it's just gonna illicit a bunch of re,tards talking sh.t.

Lewis_Koseck said:
Yeah must be.and neither me not anyone I know will be posting in xda sense it's just gonna illicit a bunch of re,tards talking sh.t.
Click to expand...
Click to collapse
Glad you got it fixed. But you probably have no clue how you got in the situation you were in nor how you got out of it. I'd suggest you do a lot of reading of the pinned threads in the general forum. Sorry, you'll have to get your own links.

Lewis_Koseck said:
Yeah must be.and neither me not anyone I know will be posting in xda sense it's just gonna illicit a bunch of re,tards talking sh.t.
Click to expand...
Click to collapse
Post #5 in THIS thread GAVE you a link to the MF3 firmware 2 HOURS before you posting again asking for it. How much more help would have liked to receive? I suggest you evaluate your own mental state of being before you respond to others with childish name calling. At the very least, read the thread you are in before making yourself look ignorant. You will definitely not be a loss to the community with an attitude like yours.

scott14719 said:
Post #5 in THIS thread GAVE you a link to the MF3 firmware 2 HOURS before you posting again asking for it. How much more help would have liked to receive? I suggest you evaluate your own mental state of being before you respond to others with childish name calling. At the very least, read the thread you are in before making yourself look ignorant. You will definitely not be a loss to the community with an attitude like yours.
Click to expand...
Click to collapse
I swear I even gave him the link to what he needed all he had to do was read it. Does he need arrows pointing to it or pilot navigation or something? Smh... Calling people names when all we're trying to tell him is look first than read.
Sent from my SAMSUNG-SGH-I337 using xda premium

Lewis_Koseck said:
I bricked my sgs4 when I used Rom Toolbox Pro to flash TWRP custom recovery. every time I unplug bat it goes into Odin mode. Every reboot with removal of battery. So I held down Volume- and home and power button the phone powered on to the screen asking if I wanted to go into Odin mode or Cancel. I. cancelled and was able to reboot successfully. Do I'm not completely bricked now. but when I try to get into stock recovery I get bricked to Odin mode. and have to remove the bat then volume- plus home plus power then Cancel going into Odin mode etc. I officially have no stock recovery
this is all due to the fact I went back after trying to flash cwm recovery...I flashed safestrap then removed it but still no recovery. and I really want the 4.3 that just came out.
btw safestrap is not working for me. I downloaded the kernel flash and a Rom specific for locked sgs4 ask I get after booting passed safestrap is a blank screen for ever.
Any help is great. thanks guys
Click to expand...
Click to collapse
Lewis_Koseck said:
I bricked my sgs4 when I used Rom Toolbox Pro to flash TWRP custom recovery. every time I unplug bat it goes into Odin mode. Every reboot with removal of battery. So I held down Volume- and home and power button the phone powered on to the screen asking if I wanted to go into Odin mode or Cancel. I. cancelled and was able to reboot successfully. Do I'm not completely bricked now. but when I try to get into stock recovery I get bricked to Odin mode. and have to remove the bat then volume- plus home plus power then Cancel going into Odin mode etc. I officially have no stock recovery
this is all due to the fact I went back after trying to flash cwm recovery...I flashed safestrap then removed it but still no recovery. and I really want the 4.3 that just came out.
btw safestrap is not working for me. I downloaded the kernel flash and a Rom specific for locked sgs4 ask I get after booting passed safestrap is a blank screen for ever.
Any help is great. thanks guys
Click to expand...
Click to collapse
You should realy read.... All of us on MF3 know that !!... That was one of the fist ways to boot back up. Safe strap is going to be a savior for you.... Basically this has been discussed a million times..... If you are on MF3 you cannot downgrade you can only upgrade or stay on MF3, If you want 4.3 sooooo bad I will link it for you. But I suggest staying patient. There is nothing really that improved over 4.2.2. So I would advise you not to upgrade but I will post the links and tell you how to do it. One if you were smart you would have made a nandroid backup thru SS and then when you boot into that you stay on the stock rom slot. Hit then go in and write your backup just the system folder.... So you won't lose all of your data. Now if you didn't make a nandroid backup. Then you can try flashing the stock recovery and fixing the permissions thru safe strap..... IF that doesn't work well you are just up the creek.....
HAHAHAHA. JK Get odin and get the MF3 Tar.MD5 files But your phone manually into odin mode and Go back to stock MF3. Seriously read, read, read. I will make it real easy for you this time. By posting links but you are just asking for it. So first grab these files: https://mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE These are the stock MF3 files that were contributed to the community by Shockndrop: http://forum.xda-developers.com/showthread.php?t=2502003
Now grab Odin, I prefer this one: ODIN 1.85 http://forum.xda-developers.com/showthread.php?t=1262272
Now put the MD5 files in their proper places in odin and and hook your phone up with a Good **** Solid Universal Serial Bus Cable: Like pitured here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Put her down into a coma AKA, ODIN Recovery mode manualy by holding power, home, and volume down. Then when prompt after the warning volume up to continue. Flash with Odin to restore to stock MF3. Brand Spaking new!!!!
Use your favorite root Method, New root method is the only one we support here on XDA, Which involves an SD Card,and the Terminal from the Play store. Or if you want the fast and dirty way because you are lazy do the Kingo root, I don't indorse it, but I have yet to hear anything negative about it, other than speculation. Links: http://www.kingoapp.com/android-root/download.htm - one click method Easy.
Old proper way: Quoting Jortex "HOWTO:
Use a card reader to format the micro SD card to exFAT (FAT32 or other formats does not work) in Windows. I haven't tried Linux or MacOS X, so they may not work.
Download the attached file (Root_for_ATTSG4_FM3.rar) http://forum.xda-developers.com/attachment.php?attachmentid=2165629&d=1375669716 and extract it into the root of your EXTERNAL microSD card using the card reader in Windows. (You can do the extraction using WinRAR, http://www.rarlab.com/download.htm or 7-zip, http://www.7-zip.org/download.html ).
Put the SD card back to the phone and download the Android Terminal Emulator app.
Open the Terminal Emulator app and run below 3 commands:
Code:
cd /mnt/extSdCard
./pwn
./script.sh
Then, open SuperSU and check everything looks good.
Then open a root app and it should be working properly.
Reboot your device once to confirm root is still working after reboot.
Come back to the post and press the THANKS button
Notes:
I uploaded a screenshot from the Terminal screen where the instructions are entered. Yours should be the same except you don't need to enter the "ls -l" command. It's just to show what files I have on the SD card. Ignore LOST.DIR directory.
Remove any SuperSU apps from your phone before following the above steps. script.sh installs it automatically.
You can use adb shell instead of a terminal app which is more convenient but requires Android SDK. Follow these steps only if you are about to use adb:
Download and install all Samsung Galaxy S 4 drivers from here: http://www.samsung.com/us/support/owners/product/SGH-I337ZWAATT#
Activate Developer options -> USB Debugging mode. To have the phone show the Developer options, go to Settings -> More -> About device. Tap on "Build number" 6 times.
You have to use an external SD card. No other alternative have been found yet. Using the device storage, i.e. /mnt/sdcard, or /data/local/tmp, DOES NOT work.
Warning (suggested by rushi.1986): "We have root for MF3 but we neither have a working recovery, nor an ODIN back to stock package. Be very careful what you do with your root. At this point, there is no way to recover even from a soft brick. (unless you know exactly what caused the soft brick and can correct it using adb)"
For those who do not know how to format an SD card on Windows (thanks to jee'sgalaxy):
Insert the micro SD into the computer (may have to use a reader or a micro SD adapter).
Go to "My Computer".
Right click on your SD card that showed up.
Click Format.
Choose exFAT as the format.
Click "OK".
Don't forget to press the THANKS button.
Credits:
***Exploit adapted for AT&T by Jortex***
***Original Guide by Open1Your1Eyes0 for Verizon Galaxy S 4***
***Original Exploit by DooMLoRD***
Next install your only way as of now to run custom roms period in your current situation and you should be incredibly grateful instead of saying that you want 4.3 soooooo bad....... really not tooo many benefits at all. Now 4.4 KittyKit lol is a different story..... So grab the latest and greatest version of safestrap from here: http://forum.xda-developers.com/devdb/project/dl/?id=1814&task=get
After Flashing Any Compatable Rom flash these every time Link: http://forum.xda-developers.com/devdb/project/dl/?id=508
They are the MF3 modules you will need them for wifi to work.
Transfer to sd card install just as you would a regular unknown source APK File..... Tick that in settings Security tab. Also hit your build number 20 times to unlock developer options and always have usb debugging on.
Now boot into safe-strap and dump a nandroid backup and you will be good to go. All thanks to the HashMan aka HashCode, And his sexifing SS. Okay now that you have a backup do anything of your hearts content. Just don't be fooling around with the bootloaders code.... this can really turn your cell phone into a paper weight.
Now here is a list of known compatable roms with SS:
Confirmed working ROMs Thanks to graydiggy http://forum.xda-developers.com/showthread.php?t=2428254
Google Play Edition 4.2.2
http://forum.xda-developers.com/showthread.php?t=2356276
http://forum.xda-developers.com/showthread.php?t=2341376
Deadly Venom
SHOStock
Darth Stalker
Graviton (Installs fine for some, will not install for others)
Goldeneye (May have issues)
Wicked ROM (T-Mobile) Input correct APN and change network mode to Auto LTE/GSM Will most likely lose root.
All Infamous TW Roms should work
Input correct APN settings for non AT&T ROMs (ie i9505 ROMs) to get LTE
Omega ROM i9505
Echo ROM i9505
Vision X i9505
BoBCaTROM i9505 (May not need to change APN)
Hyperdrive ROM. (May not be able to send SMS while on LTE)
Grab one create a rom slot and flash to your hearts content.
As for the 4.3 Odin files...... I think you can find them yourself it would be ignorant for me to post them for you.

@JohnMonsour I doubt he will read this he didn't even try to read the link I posted to try to help him. But great guide
Sent from my SAMSUNG-SGH-I337 using xda premium

Yeah. Unfortunately. I should re-post this guide for MF'd people though. What do you think? I think the the OP died..... LOL.
---------- Post added at 12:52 AM ---------- Previous post was at 12:51 AM ----------
[email protected] said:
Does he need arrows pointing to it or pilot navigation or something?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
This I lol'd at....... HAHAHAHAHA.

[HELP] Cannot boot to recovery

Hi.
Some time I have rooted my d802 using ioroot10 everything was fine, except I was not able to boot to recovery (I don't remember what was exactly an issue, I wasn't bothered as all I needed was root). Now I need recovery to flash custom ROM, and when I tried to reboot in to recovery (by pressing physical buttons, or through reboot options), phone reboots and then it is stuck in fastboot mode, with two lines of text:
[xxxx] Fastboot mode started
[xxxx] udc_start()
Click to expand...
Click to collapse
Same when tried to flash different recoveries.
So I have started the process from scratch. I have done factory reset of the phone. Then proceeded with ioroot17 which gave me this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
but ioroot10 has done the job. Confirmed with root checker.
Then proceeded to flashing recovery again.
I have tried 1_Click_recovery install which have stuck on this screen:
But it supposed to reboot phone to recovery (phone doesn't reboot at all)
then i have followed this guide as I have some experience with adb: http://www.android.gs/install-twrp-recovery-lg-g2/
I have went through all the process just fine, up to last steps were after adb reboot recovery phone reboots, and it is stuck in fastboot with two lines :
[xxxx] Fastboot mode started
[xxxx] udc_start()
Click to expand...
Click to collapse
Now, WTF? It roots fine (if not to count problems in ioroot17), and flashes recovery fine (i think) it just cant boot in to it.
Aditional info:
Carrier: Three (H3G) (UK carrier)
Build number: JDQ39B
Software Version: D80210b-234-20
Can anybody please help?
I know it is long post, but I wanted to give as much info as I can.
Thanks

Any one? Please...

Well, I have found answer my self, so I will post it here in case someone has the same issues.
For some reason which I very little understand all those scripts for flashing recovery those were referring to location /sdcard/....
While trying to flash recover by terminal method from this post, directly from terminal emulator on the phone, after typing commands using this location I had error message 'no such file or directory'. When to file explorer and found out that my files reside on different path: /storage/sdcard0/
so what I did was to change path in all the commands, and it worked. I have flashed and booted to recovery.
I have still some strange issues because of that, i.e. CWM saves backup under /sdcard/ which is not find-able under normal explorer. Or in new ROM I can find some files from previous, stock ROM i.e. ringtones which are doubled or even tripled. So that gives me some suspicion that not all file from previous ROM were removed even if I have wiped out all data, sdcard, dalvik cache etc.....
This could be a reason why new ROM (CM 11 M2) has such huge battery drain with the screen on. Phone gets really hot.
Maybe with this info someone can understand what the issue is, and help me flash clean ROM on cleared memory. I am not expert but I have rooted and flashed before on phones like HTC DHD, Galaxy s2, Galaxy Nexus, and Nexus 7

hedeon said:
Well, I have found answer my self, so I will post it here in case someone has the same issues.
For some reason which I very little understand all those scripts for flashing recovery those were referring to location /sdcard/....
While trying to flash recover by terminal method from this post, directly from terminal emulator on the phone, after typing commands using this location I had error message 'no such file or directory'. When to file explorer and found out that my files reside on different path: /storage/sdcard0/
so what I did was to change path in all the commands, and it worked. I have flashed and booted to recovery.
I have still some strange issues because of that, i.e. CWM saves backup under /sdcard/ which is not find-able under normal explorer. Or in new ROM I can find some files from previous, stock ROM i.e. ringtones which are doubled or even tripled. So that gives me some suspicion that not all file from previous ROM were removed even if I have wiped out all data, sdcard, dalvik cache etc.....
This could be a reason why new ROM (CM 11 M2) has such huge battery drain with the screen on. Phone gets really hot.
Maybe with this info someone can understand what the issue is, and help me flash clean ROM on cleared memory. I am not expert but I have rooted and flashed before on phones like HTC DHD, Galaxy s2, Galaxy Nexus, and Nexus 7
Click to expand...
Click to collapse
I believe CWM saves the backups in the /data/media folder in the root directory, not on the SD card. CWM will not wipe that folder when doing a fatcory reset. You may want to check there to see if there is a ringtones or notifications folder also.

Ronbo19 said:
I believe CWM saves the backups in the /data/media folder in the root directory, not on the SD card. CWM will not wipe that folder when doing a fatcory reset. You may want to check there to see if there is a ringtones or notifications folder also.
Click to expand...
Click to collapse
Thanks. Nope, /DATA folder is completely empty

Try the Data/media/0 folder
Sent from my LG-D800 using Tapatalk

tdevaughn said:
Try the Data/media/0 folder
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
/DATA is empty. No folders nor files there

Do you have a rom installed? There are a lot of things that get installed in the data folder. Its not possible for it to be empty.
How are you searching for it? Recovery. Or from a file explorer?
Sent from my LG-D800 using Tapatalk

Lets go tried and true
hedeon said:
Well, I have found answer my self, so I will post it here in case someone has the same issues.
For some reason which I very little understand all those scripts for flashing recovery those were referring to location /sdcard/....
While trying to flash recover by terminal method from this post, directly from terminal emulator on the phone, after typing commands using this location I had error message 'no such file or directory'. When to file explorer and found out that my files reside on different path: /storage/sdcard0/
so what I did was to change path in all the commands, and it worked. I have flashed and booted to recovery.
I have still some strange issues because of that, i.e. CWM saves backup under /sdcard/ which is not find-able under normal explorer. Or in new ROM I can find some files from previous, stock ROM i.e. ringtones which are doubled or even tripled. So that gives me some suspicion that not all file from previous ROM were removed even if I have wiped out all data, sdcard, dalvik cache etc.....
This could be a reason why new ROM (CM 11 M2) has such huge battery drain with the screen on. Phone gets really hot.
Maybe with this info someone can understand what the issue is, and help me flash clean ROM on cleared memory. I am not expert but I have rooted and flashed before on phones like HTC DHD, Galaxy s2, Galaxy Nexus, and Nexus 7
Click to expand...
Click to collapse
How about we go back to stock or use the LGsupport tool to load LG recovery and get it booting. Then after a bunch of FC's and and error messages the phone will settle and we can backup what ever data is on there. Then we get freegee app load TWRP and reflash the rom of yer liking. Sound good or do you already have resolution?

geosnipe said:
How about we go back to stock or use the LGsupport tool to load LG recovery and get it booting. Then after a bunch of FC's and and error messages the phone will settle and we can backup what ever data is on there. Then we get freegee app load TWRP and reflash the rom of yer liking. Sound good or do you already have resolution?
Click to expand...
Click to collapse
Well, I have never said phone was not booting. It is booting just fine.
Yesterday I have boot to recovery and I have pressed almost every possible wipe/format option possible in there. Then I have sideloaded
CM11 Gapps and Radio. Seams to be fine now. I don't know why but it almost looks like my phone was somehow different from other g2's Folder structure was different. For example no /sdcard/android , it was in /storage/sdcard0/android
Although there are still few things bothering me. Memory. Total storage reported is 10.62GB. Phone is 16GB version, from which I would expect about 15GB of usable memory. So where is missing 4GB? Do you people with custom ROMs have the same? anyway to get it back?

hedeon said:
Well, I have never said phone was not booting. It is booting just fine.
Yesterday I have boot to recovery and I have pressed almost every possible wipe/format option possible in there. Then I have sideloaded
CM11 Gapps and Radio. Seams to be fine now. I don't know why but it almost looks like my phone was somehow different from other g2's Folder structure was different. For example no /sdcard/android , it was in /storage/sdcard0/android
Although there are still few things bothering me. Memory. Total storage reported is 10.62GB. Phone is 16GB version, from which I would expect about 15GB of usable memory. So where is missing 4GB? Do you people with custom ROMs have the same? anyway to get it back?
Click to expand...
Click to collapse
LG has occupied some of the storage (its hidden). Some of it could be caused by your issue. I think LG could have given us the whole 32GB. No way to reclaim with out carrier unlocking keys for the partitions- it sucks! Flashing custom roms definitely gives us advantages, but not without risks. I say flash to stock for proper file structure and then customize again from there. Less likely to encounter more issues in the future

Root/TWRP/SD Fix/Init d/FlashPlayer/ADBlocking/debloating the SM-T900 / T900UEUAND4

Update 10/30/2014
There's no need to go back to the "B3" version any longer. The T900UEUANI1 is available on SamMobile, to be flashed w. Odin.
The cf-auto-root listed as "B3" on chainfire's site will work.
Note, I have not created any of this, please thank the original developers in their posts. This is simply a compilation of available info needed to have the most complete and working SM-T900, Samsung Galaxy Tab Pro 12.2.
The sole purpose is to make you save time. However, I'm not saying this will work, and it might even brick your device, but that risk is yours to take. However, it worked for me, so why shouldn't it... Trust the steps, there's a reason for this madness. Believe me when I say it; I've learned the hard way, and it has not been a pleasant journey.
If your SD cards looses necessary rw privileges it seems like not even a backup will correct them, even after wiping the SD cards and formatting data.
If you haven't yet upgraded from B3 to D4, I recommend you to do this first! There are major improvements between the two versions.
1. Rooting:
First flash the P900XXUANB3-RecoveryImg (forgetting this will create a softbrick, and you will have to start over, also use the Odin 3.07, supplied, I have not tested with the later 3.09)
then flash CF-Auto-Root-v2wifi-v2wifixx-smt900
for detailed method and files see: http://androidcentral.us/2014/05/root-galaxy-tab-pro-12-2-sm-t900/
I forgot, it's important to use original cables directly connected to the PC, a docking station connection, or an EOM cable might be a reason for flash failure.
2. install TWRP:
Flash openrecovery-twrp-2.7.1.0-v1awifi
link: http://forum.xda-developers.com/showthread.php?t=2679825
3. disable Knox:
Open SuperSU and answer yes to disabling KNOX
4. fix SD-card issue in KitKat 4.4:
Download and run JRummy's "SD KitKat Fixer" from market. I had no luck with any other comfortable fixing apps.
5. important!:
reboot into recovery and wipe both External and Internal SD, as well as Formatting Data. Don't forget to backup all files you want to keep onto your PC! for later re-installation. I know this must feel hard, but I sincerely advice you you follow this step. Most apps are not KitKat ready, as of now, and won't allow you to download or access the data if you haven't prepared your SD's in advance.
6. init d support:
Download and install Stericson's BusyBox from market
Download and install Uni-init v1.0
link: http://forum.xda-developers.com/showthread.php?t=1933849
7. Flash Player support:
Download and install fixed AdobeFlashPlayer 11.1
link: http://forum.xda-developers.com/google-nexus-5/help/guide-how-to-play-flash-video-android-4-t2548001
If you're using Dolphin Browser, also install the Dolphin JetPack, and modify Settings/Web Content/Flash Player/ to Always On.
8. ADBlocking:
Dowload and flash LATEST_MoaAB_ADBlocking_Super
link: http://forum.xda-developers.com/showthread.php?t=1916098
9. De-bloating:
for de-bloating at a maximum you can disable numerous of the Samsung apps, by pushing the three dots, upper right corner, while in the apps-screen mode.
Also, don't forget to un-check the de-bloated apps from auto-update in Play Store, as well as in the Samsung update if you signed up for this service.
10. (Re)-nstall your apps
You're done, and it's time to restore or download all the apps you need and it will work in KitKat 4.4
None of the modified stock ROM's currently available seem to mount correctly. If something goes wrong, you will most likely loose your SD card privileges. The original T900UEUAND4 stock ROM can be found here: http://www.sammobile.com/firmwares/3/?download=29102. Just unzip and flash with Odin, then start again with step 1.
Also, due to lack of time, I will not be able to monitor this post. I hope you will help one another out with clarifications, or anything I might have missed.
Best of luck,

Delete

Very nicely laid out. I've already done all this, but it's great to see a guide for new comers that may not know what to do. Thank you.

Thank you for the guide and gathering everything together. I just wanted to throw this out there, I followed the directions exactly....and I could not get mine to root. It would continually soft brick and a screen full of odd colors would come up every time. I read on the CF Auto Root thread that others had the same issue. One determined individual said he did it 10 times and it finally worked. Soooo....I continued to do it. And it finally worked, trying nothing different each time.
I tried 2 different computers, a win7 and win8, installed Kies to make sure drivers were there. Used official and another cable. I tried everything I could think of. In the end I would say as long as you're following the directions just keep trying.
http://forum.xda-developers.com/attachment.php?attachmentid=2591013&d=1392923580
That's a link to the P900XXUANB3-RecoveryImg that my friend and I both used before getting root. Thanks again for the guide arcadia2uk!

So I was able to root and install TWRP but after an app caused some issues I went to wipe cache and brick. Flashed stock and had to do factory reset. However, I learned that attempting to restore a backup or wipe cache or do factory reset via twrp causes brick. Have to use Odin to flash back to factory. I also had to use the German region and lost my symbols on keyboard.
................edit..............
I updated kies and reinstalled all the drivers and flashed the cellular south firmware...All is well and current. Rooted, twrp, having fun.

Hi,
I followed all instructions but Flashing was successfully only after USB driver update. This is my story:
My Tab Pro 12 has ND4 stock.
Downgrade P900XXUANB3-RecoveryImg with Odin.
Then flash CF-Auto-Root-v2wifi-v2wifixx-smt900.
All Odin task stucked at Cache and after a few minutes screen got attached frightening picture
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
.
Then tab not booted.
Tried this http://forum.xda-developers.com/showpost.php?p=54576936&postcount=63
and tried different usb ports, cables.
But no success.
Then I installed latest Kies3 (started only the usb driver in tools menu) then restart Win7 and after then all right.
Odin flashed CF root.
Best wishes I hope this helps!

deleted

robert1968 said:
Hi,
I followed all instructions but Flashing was successfully only after USB driver update. This is my story:
My Tab Pro 12 has ND4 stock.
Downgrade P900XXUANB3-RecoveryImg with Odin.
Then flash CF-Auto-Root-v2wifi-v2wifixx-smt900.
All Odin task stucked at Cache and after a few minutes screen got attached frightening picture
.
Then tab not booted.
Tried this http://forum.xda-developers.com/showpost.php?p=54576936&postcount=63
and tried different usb ports, cables.
But no success.
Then I installed latest Kies3 (started only the usb driver in tools menu) then restart Win7 and after then all right.
Odin flashed CF root.
Best wishes I hope this helps!
Click to expand...
Click to collapse
The fix is actually put the m
Sent from my HTC One_M8 using Tapatalk

I don't know if it will help anyone else, but I just flashed TWRP 2.8 on my Galaxy Tab Pro 12.2 wifi with "D4" firmware using odin and it worked and I was able to make successfully a backup. Below is a link to the recovery I flashed. Of course your mileage may vary so do it at your own risk.
http://teamw.in/project/twrp2/244

The easiest way to debloat it is probably via titanium backup's batch mode actually.

Oh boy I just mess up my Tab.... It's stock in the firmware error screen. Will try to flash stock firmware as soon as I get WiFi, reflashing stock via Odin should fix it as I read right?
Fingers crossed: say yes please!
Edit: it boots with stock fw now is back to normal except that can't access or boot into recovery mode. Any help or a working recovery file? Thanks in advance
Sent from my HTC One using Xparent BlueTapatalk 2

saruba said:
Oh boy I just mess up my Tab.... It's stock in the firmware error screen. Will try to flash stock firmware as soon as I get WiFi, reflashing stock via Odin should fix it as I read right?
Fingers crossed: say yes please!
Edit: it boots with stock fw now is back to normal except that can't access or boot into recovery mode. Any help or a working recovery file? Thanks in advance
Sent from my HTC One using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
try flashing the latest TWRP 2.8.1.1 with Odin. You can also download Quick Boot (Reboot) from Play Store, that will facilitate the booting process.

arcadia2uk said:
try flashing the latest TWRP 2.8.1.1 with Odin. You can also download Quick Boot (Reboot) from Play Store, that will facilitate the booting process.
Click to expand...
Click to collapse
Yey! U R the man! Thanks so much it works flawlessly!
I think I have 2 different recovery files and they both doesn't work I don't know why I got them from twrp site... Anyways just to let you know I've done every thing with Odin 3.09 so yeah I'm confirming that it works fine.
Sent from my HTC One using Xparent BlueTapatalk 2

[Discussion] Dumb attempt to upgrade to Marshmallow with TWRM in osprey

Hi everyone, posting this as a information about something you should NOT try: upgrade your OTA rom with custom recovery installed, in my case TWRP.
I did this with ignorance of not think that (or search about) the custom rom could interfere at the normal process of OTA upgrade from Lollipop to MarshMallow. Actually I remembered that I was unlocked and rooted the phone but I did not remember I was using custom recovery. AFAIK at this device is impossible to root without unlocking and custom recovery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are on TWRP don't do this!
For those don't know about TWRP and OTA updates, read this:
https://twrp.me/faq/officialota.html
In short terms: don't try OTA updates (official updates) if you installed custom rom such as TWRP. "Installing official updates from your manufacturer or carrier is not supported by TWRP." "[This] may result in unexpected behavior" "Most of the time the best way to get a new update onto your device is to simply wait a couple of days for ROM makers for your device to come up with ROMs that are based on the new update that you can safely and easily install."
But I did it. And now I'm reporting it for those who are curious. So, what's happened?
Fortunately the device is not bricked as I thought when it reboot to TWRP for flashing the OTA update instead of the stock recovery process! I thought that I messed everything when I see the frozen TWRP for something about 10 minutes or less. After the long 10 minutes of frozen TWRP image I got the recovery working and checked the log:
Of course, errors on the log.
Rebooted and got a frozen background image, after a while a permanent black. When the screen turn off the notification system shows the battery as dead (and it as not). But I could turn it off and gain access to the recovery holding power and volume down buttons.
After two failed reboots to the system with the same result I tried to make a screenshot using the hard buttons and it works (screenshoted the black screen) and suddenly the lock screen shows up. I got into, everything working slow meaning that there was a lot things working in the background. Got some error messages from google service and MMS/SMS communication and minutes later it automatically reboots and booted the TWRP again.
This turned to a loop. I stopped this by going to the system setup - about the device - check for updates. And got a message "the update has failed". Good. After a while the message offering the update shows again... No, thanks...
I rebooted to TWRP and fixed the permissions, maybe this solve some problems.
Right now the phone is working but the rebooting process has unexpected behaviors, some tries result in a normal fast process and other tries result in a long black image and the system/launcher just don't arm up for some minutes, but after a while it works. I'm not confident. Already backed up apps with Titanium backup.
I'm planning to restore everything from the stock using this guide:
http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3054303
And them, maybe, update the OTA to marshmallow. Before doing that, I will search and get to know if it is possible to re-root the phone with marshmallow in osprey (that means re-unlock and install TWRP again). Rooted device it's a need for me.
This is what happened to my device when tried to OTA update with TWRP. I had luck not bricking this.

+1 on the dumb attempt. Early morning, excited for the release, upgrade please! Yeah, no good. Is restoring our only option? Seems the upgrade has not even started so what about deleting the downloaded image file or trying to kill the process attempt?

did you really had to make a new thread with that huge wall of text? haha come on man, common knowledge that to take the OTA you need stock recovery ?
Sent from my Nexus 6 using Tapatalk

Seems the upgrade has not even started so what about deleting the downloaded image file or trying to kill the process attempt?
Click to expand...
Click to collapse
Yeah, DON'T proceed with the update! Deleting the downloaded files just break the process... My advise is to make a backup before deleting this.

sgloki77 said:
did you really had to make a new thread with that huge wall of text? haha come on man, common knowledge that to take the OTA you need stock recovery
Click to expand...
Click to collapse
Ok, sorry about the huge wall of text.

No need to adb stock image. A simple factory reset worked for me. Next time will have more caffiene before attempting anything major with my phone.

golgiapp said:
No need to adb stock image. A simple factory reset worked for me. Next time will have more caffiene before attempting anything major with my phone.
Click to expand...
Click to collapse
:good:
Good to know that a factory reset could fix the problems caused by the OTA update with TWRP. But after this it should remain with custom recovery and not possible to OTA update. for stock MM

i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??

gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
Not sure, but take a look at /cache

gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
/data/data/com.motorola.ccc.ota/app_download

hp420 said:
/data/data/com.motorola.ccc.ota/app_download
Click to expand...
Click to collapse
found it!!
thanks extracted ok !!
its a zip flashable,can it be converted to install like the oem recovery images using the adb method?

gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
Thank you for the warning
---------- Post added at 12:58 AM ---------- Previous post was at 12:54 AM ----------
Thank you for the warning

I experience this today, I flashed a stock rom again so I can have the OTA update, but what I can't do is root my device, I flash the custom recovery and then I flash the beta version of SuperSU, and when I reboot my device it bricks in the Motorola Logo, anybody knows how to fix this, or should I wait a little bit longer to root my phone? as the OP I need root too

Use the latest 2.62 superSU zip. And never root with the TWRP option before reboot.
Sent from my MotoG3 using Tapatalk

nelsonw said:
Use the latest 2.62 superSU zip. And never root with the TWRP option before reboot.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Never done that, I tried flashing the superSU 2.52 from a bunch of tutorials I found on Google, but all it does is bricking my phone on the Motorola Logo, then I have to do all the downgrade and update process again

VicSanRED said:
Never done that, I tried flashing the superSU 2.52 from a bunch of tutorials I found on Google, but all it does is bricking my phone on the Motorola Logo, then I have to do all the downgrade and update process again
Click to expand...
Click to collapse
this is a known issue with the mm update. Use 2.61 or newer, only. These are the new systemless root zips.

hp420 said:
this is a known issue with the mm update. Use 2.61 or newer, only. These are the new systemless root zips.
Click to expand...
Click to collapse
I tried with the latest version 2.66 and still the same issue. Don't know what to do now.

So its posible to root MM ?? Safe ,stable?
Supersu v 2.62??

Yeah, 2.62 is the only one working. This worked for me BETA-SuperSU-v2.62-20151210170034
Sent from my MotoG3 using Tapatalk

nelsonw said:
Yeah, 2.62 is the only one working. This worked for me BETA-SuperSU-v2.62-20151210170034
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Can you post a little tutorial?, I wanna be sure I'm doing everything OK.