Develop Bugs

My phone is constantly rebooting

I'm having a very strange issue with my device right now. Basically whenever I flash any custom ROM I end up in a boot loop. It started last night after I flashed a couple of CM10 based ROMs and then tried to revert back to Skynote which is touchwiz based. I was able to fix it by using Odin and flashing the stock Rogers ROM .tar file. That fixed everything and stock was running fine all night with no reboots or issues. This morning I did a fresh download of the ROM rebooted to TWRP wiped cache *2, Formatted system *2 and factory reset *2, installed the ROM and rebooted. I should mention I am using TWRP version 2.4.1.0. The ROM usually loads for about 1-2 mins then reboots and repeats over and over. Does anyone have any ideas? I've even formatted the internal and external storage. I did notice there is one folder on my internal SD card that I cannot seem to remove called Z and has a LMT.apk and another folder with wallpapers in it. I cannot delete or remove this folder as it keeps saying the folder is write protected. Even after formatting the internal storage that folder remains which makes me wonder if my SD card is screwed up.
Sorry for the long post but I am running out of ideas and don't want to be stuck on Stock. What could be causing this? I've tried flashing a new kernel from TWRP and still the same results, I've even tried different ROMs just in case but still the same results. The only thing that seemed to work so far was the stock ROM via Odin.

veebomb said:
I'm having a very strange issue with my device right now. Basically whenever I flash any custom ROM I end up in a boot loop. It started last night after I flashed a couple of CM10 based ROMs and then tried to revert back to Skynote which is touchwiz based. I was able to fix it by using Odin and flashing the stock Rogers ROM .tar file. That fixed everything and stock was running fine all night with no reboots or issues. This morning I did a fresh download of the ROM rebooted to TWRP wiped cache *2, Formatted system *2 and factory reset *2, installed the ROM and rebooted. I should mention I am using TWRP version 2.4.1.0. The ROM usually loads for about 1-2 mins then reboots and repeats over and over. Does anyone have any ideas? I've even formatted the internal and external storage. I did notice there is one folder on my internal SD card that I cannot seem to remove called Z and has a LMT.apk and another folder with wallpapers in it. I cannot delete or remove this folder as it keeps saying the folder is write protected. Even after formatting the internal storage that folder remains which makes me wonder if my SD card is screwed up.
Sorry for the long post but I am running out of ideas and don't want to be stuck on Stock. What could be causing this? I've tried flashing a new kernel from TWRP and still the same results, I've even tried different ROMs just in case but still the same results. The only thing that seemed to work so far was the stock ROM via Odin.
Click to expand...
Click to collapse
I should probably add that I was coming from Android 4.2.2 and want to get back on 4.1.2

veebomb said:
I'm having a very strange issue with my device right now. Basically whenever I flash any custom ROM I end up in a boot loop. It started last night after I flashed a couple of CM10 based ROMs and then tried to revert back to Skynote which is touchwiz based. I was able to fix it by using Odin and flashing the stock Rogers ROM .tar file. That fixed everything and stock was running fine all night with no reboots or issues. This morning I did a fresh download of the ROM rebooted to TWRP wiped cache *2, Formatted system *2 and factory reset *2, installed the ROM and rebooted. I should mention I am using TWRP version 2.4.1.0. The ROM usually loads for about 1-2 mins then reboots and repeats over and over. Does anyone have any ideas? I've even formatted the internal and external storage. I did notice there is one folder on my internal SD card that I cannot seem to remove called Z and has a LMT.apk and another folder with wallpapers in it. I cannot delete or remove this folder as it keeps saying the folder is write protected. Even after formatting the internal storage that folder remains which makes me wonder if my SD card is screwed up.
Sorry for the long post but I am running out of ideas and don't want to be stuck on Stock. What could be causing this? I've tried flashing a new kernel from TWRP and still the same results, I've even tried different ROMs just in case but still the same results. The only thing that seemed to work so far was the stock ROM via Odin.
Click to expand...
Click to collapse
Do you have SD Card adapter for the computer? If so, try removing the card from the phone, then plug it into the computer and formatting it that way. For the ROM boot loop issue, try flashing a stock ROM using ODIN, then using whatever method you like the most to flash the ROM you want to use.

thunderx2000 said:
Do you have SD Card adapter for the computer? If so, try removing the card from the phone, then plug it into the computer and formatting it that way. For the ROM boot loop issue, try flashing a stock ROM using ODIN, then using whatever method you like the most to flash the ROM you want to use.
Click to expand...
Click to collapse
I'm now pretty certain its a bootloader issue as I'm downgrading from Android 4.2.2 to 4.2.1 but thanks.

take your external sd card out and see what happens

wase4711 said:
take your external sd card out and see what happens
Click to expand...
Click to collapse
I wiped everythign 2x and then I flashed the file you posted in the other thread and removed my SD card but still getting reboots. Should my SD card be called sdcard0 still in my files?

yes, your card will still be called sdcard0
take your external card out completely, and see if the phone still boot loops

wase4711 said:
yes, your card will still be called sdcard0
take your external card out completely, and see if the phone still boot loops
Click to expand...
Click to collapse
It still loops. This is crazy, when I used Odin to go back to stock it was working ok but everythin else has made it bootloop. I can try using Odin again when I get home and see if the restore SD card file works then. Does anything have to be done to the bootloader?

no, don't mess with the bootloader; you will probably brick it if you do
go back to stock via odin for a day or 2, and make sure its not the hardware itself..

wase4711 said:
no, don't mess with the bootloader; you will probably brick it if you do
go back to stock via odin for a day or 2, and make sure its not the hardware itself..
Click to expand...
Click to collapse
So its not like moving back to ICS from jellybean where you had to flash a new bootloader?

Op you're on Rogers right? Make sure that you have the Skynote without the new modem.
~PsyCl0ne
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

PsyCl0ne said:
Op you're on Rogers right? Make sure that you have the Skynote without the new modem.
~PsyCl0ne
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
yes I am on Rogers, sorry but how can I tell that?

I don't think I have flashed a new bootloader more than once in the last 6 or7 years, on an htc evo4g..
you should not ever have to do that on this phone

veebomb said:
yes I am on Rogers, sorry but how can I tell that?
Click to expand...
Click to collapse
oh wait I think I see what you're refering to. I wonder how many different mistakes I have actually made durring this fiasco of mine.... I'll give that a try when I get home and post back

veebomb said:
oh wait I think I see what you're refering to. I wonder how many different mistakes I have actually made durring this fiasco of mine.... I'll give that a try when I get home and psot back
Click to expand...
Click to collapse
Okay I'm out right now but I'll check in every once in a while.
~PsyCl0ne
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

Same here
I am having the same exact problem you are veeboom. It's not boot-looping because it actually lets me into the phone for about one minute; then it reboots. I have tried everything that you have tried, right along with you and result is nil. It won't stay on for more than a minute. The only difference is that I am just trying to get Roger's Clean Stock ROM working. It sounds like you have accomplished that and are trying to get a custom going. I have tried Odin flashing 3 times; once without the sd card. I am pretty sure SD card is not the issue. I have wiped this phone at least 5 times (everything except the the extSdCard (AKA sdcard1).
I am going to see if I can find some other posts on this problem and will let you know if I finally find a fix. Hope you will do the same.

Happy to report the end of the boot loop!
Although I'm kind of embarrassed to admit it was caused by an incompatible modem file I flashed over and over... :silly:
Thanks for everyone's help.

floykoe said:
I am having the same exact problem you are veeboom. It's not boot-looping because it actually lets me into the phone for about one minute; then it reboots. I have tried everything that you have tried, right along with you and result is nil. It won't stay on for more than a minute. The only difference is that I am just trying to get Roger's Clean Stock ROM working. It sounds like you have accomplished that and are trying to get a custom going. I have tried Odin flashing 3 times; once without the sd card. I am pretty sure SD card is not the issue. I have wiped this phone at least 5 times (everything except the the extSdCard (AKA sdcard1).
I am going to see if I can find some other posts on this problem and will let you know if I finally find a fix. Hope you will do the same.
Click to expand...
Click to collapse
You should have started your own thread but can you give us a run down of what you did prior to having the boot loop?
~PsyCl0ne
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

Things just got worse
I have have the phone for about two months. A week ago I rooted it with Samsung Note II tool box and everything was fine, until I found out that there were these "custom ROMs" available. So I flash one, but it was unstable. I flashed liquid smooth; same thing, then I tried a few ROMS that were a little more mature, but their were always things I could not live with (like no blue tooth or apps crashing). I also found out what a boot loop was all about. It sucked, but the forums help me get it fixed. Now I am tried of messing with all these custom ROMs and I just want my old reliable system back, with root. Currently I am trying to get Roger's CleanROM AT&T Special Edition 1.2 working again (with I believe I started with). I have been unable to remedy boot loops that happen about every minute. I have flashed, wiped (everything), unrooted, re-rooted, flashed with Odin, flashed core kernel via odin per instructions, called it bad names and threatened it; then said I was sorry. I have repeated all these things many times, including with and without the extSdCard. SD card does not seem to be the issue. I am still looking for more things to try. Just now it has started refusing to boot at all. I gets to the boot screen and gets stuck.
I am trying to find out more about how to use ADB to re-partition upon stock ROM flash. You know anything about that? I have been at this all day.

It sounds like you may have done the same thing I did which was flash an incompatible modem file. My suggestion would be for you to use Odin and flash back to the Rogers Stock ROM. It's easy and takes less than 10 minutes.
Basic instructions,
1. Download and unzip Odin
2. Put your phone in download mode (turn off your phone, and press the buttons together: vol down + home + power for a few seconds)
3. Run Odin then hit PDA button on the right side, then find and choose the firmware file you downloaded to be flashed.
4. Make sure your device is recognized in Odin3 (The ID: COM box near the top left part of the Odin program should go yellow once you connect your phone)
5. Make sure re-partition in NOT checked
6.Press Start to initiate flashing
7. Once finished your device should automatically reboot. You may need/want to do a factory reset which will wipe all your data and you would be back to the way your first got your phone. Enter into recovery mode by turning off your phone and next press the three buttons simultaneously: volume up + home + power. After getting into recovery, select Wipe/Factory reset.
8. Reboot
You are now stock 100%
Here is a link to download Odin,
http://www.mediafire.com/?x4356fnc1ge48hf
Here is a link to the Rogers stock ROM you flash with Odin,
http://www.hotfile.com/dl/180165074/47da708/I317MVLALJ2_I317MOYAALJ2_RWC.zip.html
Here is a link to a guide with some instructions and a few pictures,
http://www.andromods.com/unroot-locking/how-to-restore-samsung-galaxy-note-2-to-stock-rom-firmware-with-odin.html

[Q] soft bricked maybe hard bricked need some help

HI guys so i have been at this for a few hours now i was going to update my roms to 4.2.2
did a full backup and then did a wipe and the problem started the roms was not good so installation was aborted. when i connected the computer to phone after putting it in download mode so i could load stock roms and then load up back up the computer doe not recognize the phone.
THe CWM version 5.5.0.4 does not allow me to look at my sd card for some reason.... is my phone done?
so the backup was saved on teh phone thats why i moved it using file explorer to sd card ...
any way i can talk to my phone well make my computer talk to my phone.....i know it used to connect to me computer with no issues.

systemdude2 said:
HI guys so i have been at this for a few hours now i was going to update my roms to 4.2.2
did a full backup and then did a wipe and the problem started the roms was not good so installation was aborted. when i connected the computer to phone after putting it in download mode so i could load stock roms and then load up back up the computer doe not recognize the phone.
THe CWM version 5.5.0.4 does not allow me to look at my sd card for some reason.... is my phone done?
so the backup was saved on teh phone thats why i moved it using file explorer to sd card ...
any way i can talk to my phone well make my computer talk to my phone.....i know it used to connect to me computer with no issues.
Click to expand...
Click to collapse
Your recovery version is pretty old, considering cwm 6.0.3.6 is the newest...

So is there anyway to fix this ?

Download ROM Manager from the PlayStore and let it install the latest CWM, or download GooManager and have it install TWRP.
So far as the computer, you'll need to be more specific about 'talk to'.
Might need drivers, might need a new cable, can't tell from what you said.

I think if he wiped already he wont be able to download from the play store, if im reading the OP correctly, you already wiped the device, you flashed the 4.2.2 or 4.2 and it aborted..correct?
Step 1. Okay here's what you can do since the PC isnt reading your phone, reboot or restart your pc put phone in odin/download mode and see if it reads it now. If it does Odin a stock rooted rom, then get goomanger from the play store and install open script recovery which will give you the twrp recovery, then you can attempt the flash again of the 4.2 based rom.
Step 2. If it still isnt reading after a pc restart load your old rom on an sd card and try to flash the old tw rom with that older cwm recovery and see if you can get back at least to a tw rom. If that doesnt work then pull the battery out your phone let it sit for 2min, put the battery back in and get into odin/download mode, and see if pc recognizes the device and connection, if it doesnt, download kies and it might help with the connection issue.
Did that help bro. Let me know?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

Op stated the he made a full backup. Should be able to boot directly into recovery and restore the backup?

thanks for the info everyone . the operating system is gone so no luck on play store.
mrkevo3000 yes the roms got aborted half way its weird why it would do that.... my phone has always had issues.
just like that as i am typing this my phone is now recognized by odin so i will what you said load up stock and the reflash my backup and then update cwm.
I will try and update and againg to 4.2.2 and let you know what happens.
I have seen so many flavors any preference one somethiong that might work on i747m ?
ill update this after recovering my phone and attempting reflash.
Also for some reason my sd card is not recognized by cwm and it is only looking at internal again never did this to me before thats why i got stuck.
Last time i attempted a update for some reason my apn settings were locked and could not be changed.

I did the same stupid thing myself. Really can not believe I did it but i was rushing and didn't read what it was, thinking i was doing something else. Was not worried as I had my trusty nandriod backup -.- . I guess I can consider myself lucky as i took it to telus hoping they would buy my story and they sent it to the samsung repair center. Worried all week that if they checked it would be clear i had voided the warranty and i would be paying a high repair cost or buying a new phone. Well I got the phone back an hour ago and they fixed it.... no charge. I guess I can consider myself very lucky.

systemdude2 said:
thanks for the info everyone . the operating system is gone so no luck on play store.
mrkevo3000 yes the roms got aborted half way its weird why it would do that.... my phone has always had issues.
just like that as i am typing this my phone is now recognized by odin so i will what you said load up stock and the reflash my backup and then update cwm.
I will try and update and againg to 4.2.2 and let you know what happens.
I have seen so many flavors any preference one somethiong that might work on i747m ?
ill update this after recovering my phone and attempting reflash.
Also for some reason my sd card is not recognized by cwm and it is only looking at internal again never did this to me before thats why i got stuck.
Last time i attempted a update for some reason my apn settings were locked and could not be changed.
Click to expand...
Click to collapse
I would use odin 1.85 and odin a rooted stock 4.1.2 rom.. then go to the playstore and download goomanger and get the teamwin recovery, by hitting menu inside goomanger app, and installing the open script recovery which will install the teamwin recovery, you can flash any pure google rom with that recovery, before you do make a nandroid of your current setup and then flash away, get into a habit of doing at least one back and check the md5 hash of the roms before you flash away... download using your pc instead of phone browsers, sometimes mobile browsers corrupt the files.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

Please need help eMMc dump for i747 At&t s3
danvee said:
Download ROM Manager from the PlayStore and let it install the latest CWM, or download GooManager and have it install TWRP.
So far as the computer, you'll need to be more specific about 'talk to'.
Might need drivers, might need a new cable, can't tell from what you said.
Click to expand...
Click to collapse
Hello good morning i am in need of your help. I need a eMMC dump of a rooted AT&T sgh i747
Run this as root from a working SGH-i747:
Code:
busybox dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1M count=128
Please help me out really need the help. let me know if you can. Thank you for even reading my request.

[Q] Recovery bootloop after Odin/Kies/Heimdall STOCK flash, only boots to DL mode

Hi folks, long time reader, first time noob answer seeker.
I'm no stranger to rooting, flashing, hacking about and such - I even spend most of my day as a software engineer, and I've finally given up on this one - so here I am (rock me like a hurricane), please be kind.
SM-900T - It was rocking pretty darn well on Jedi Elite which I had flashed over rooted stock 4.3 MI7 - then (probably after one too many XPosed modules) it just kept rebooting randomly. Thinking it was no biggie, I thought I could just reflash to stock and call it a day. Thirteen or so flashes later, I gave up on 4.3 and figured I'd just take the thing up to 4.4.2 NB4 by upgrading everything to 4.4.2 via Kies.
That's when I first ran into the bootloop issue, read a lot about it, and managed to get it up(ish) on stock, rooted, with Philz 6.X... Couldn't flash a ROM to save myself and wound up with another soft brick.
Flash forward to Friday - decided to start from scratch again - attempted to flash stock 4.4.2 from Kies, from Odin, From Heimdall... Nothing seems to be able to get me out of the current state it's in:
Only boots to download mode. Flashes seem to work fine, but on that first reboot where it tries to go to stock recovery to finish up on the device itself, it never gets there - boot loops trying to load recovery no matter how it wants to get there. If I pull the battery and start up (either straight to system or by cancelling out of download mode), it boot loops trying to load system. Boots fine to download mode, where I attempt to flash again with the same results.
Yes, I've tried Odin 3.0.9, 3.0.7, 1.8.5, Heimdall on Mac, Heimdall on Windows, Kies on Mac, Kies on Windows - repartition via PIT and not. Installed, uninstalled, and reinstalled all software and drivers multiple times, tried multiple cables on multiple USB ports.... Most of the time it looks like it's going to be fine (sometimes the flash fails, usually through Kies), but never surivives that first reboot after the flash.
Every answer I've seen says to do the things I've already done or cannot do (flash stock via Odin, pull the battery and boot to stock recovery and do a factory reset - which I'd LOVE to do, but can't). No problem recognizing the sucker on the PC/Mac
Next step: try flashing a N9005 ROM...
Any other thoughts? I do have another N900T that's working but has a blacklisted IMEI, and I've been tempted to swap the IMEIs a last resort (although either I'm too dumb to make it stick, EFS pro says it succeeds in writing the IMEI after I do a EFS format, but it doesn't stick.... Either I'm missing something, or I need a UART cable) - is there a way of swapping just the radio hardware or just the internal storage? OR, is there a way of taking a full system image of my working phone and making an Odin-flashable tar from that?
Failing any of these options, perhaps I'll wait for an Odin-flashable 4.4.3 if such a thing exists - or, hope to get lucky and swap it out at a store praying they don't see I've tripped Knox.

Looks like you've tried almost everything. Take it in and have them swap it.
Sent from my SM-G900T using Tapatalk

Coming from you...
noobtoob said:
Looks like you've tried almost everything. Take it in and have them swap it.
Click to expand...
Click to collapse
Coming from you (I have read, and am quite thankful for, many of your posts), sounds like that might be the best option, however disconcerting.

bondidave said:
Coming from you (I have read, and am quite thankful for, many of your posts), sounds like that might be the best option, however disconcerting.
Click to expand...
Click to collapse
Well, I do have a few ideas... Got done questions though.
1. Do you have an external SD card?
2. It goes all the way through flash on 4.4 even with heimdall?
3. Is there anything you have left out? Even the smallest detail can help, and by the op you are detail oriented, so I just need to know.
Sent from my SM-G900T using Tapatalk

... is there a way of taking a full system image of my working phone and making an Odin-flashable tar from that?
Click to expand...
Click to collapse
Yes, but I don't have the details handy.
All your attempts suggest to me that you might have some damaged hardware which is causing data corruption during transfer. Open the back and take a good look at the USB port. Tighten the screws and try a transfer while firmly holding the cable in place -- don't move it while transferring.
If that doesn't work then let 'noobtoob' walk you through booting with the removable sdcard. Your second N900T will be needed to write the data to the sdcard. If this works then you can 'dd' write stock partitions to an sd card with #2 then 'dd' write them in #1.
If either of those works then unroot and take it in for warrenty exchange.
Frank

bondidave said:
... then (probably after one too many XPosed modules) it just kept rebooting randomly.
Click to expand...
Click to collapse
This also indicates data corruption, and this is what started it all. Since you have tried various cables and computers that leaves the device, probably the USB port.
Frank

probably the USB port.
Click to expand...
Click to collapse
Swapped the main board with the working phone to rule out the USB port - still no luck.
Definitely interested in trying the boot from external SD, I'll do my own search for it, unless you can quickly provide me with a link - but if it's as easy as it sounds (booting off of an SD in order to be able to send ADB commands to dd copy the partitions from the good phone to SD then from the booted SD back to internal) - I'm happy to give it a shot.
Tempted just to swing by TMO just to see if they'll swap it "under warranty" (despite picking it up from a private sale) - the only way they would notice it's been "tampered" with would be to check the knox counter by attempting to run download mode.
Oh, and yes, it does go all the way through with the flash (at least in Odin - I haven't tried a full flash through heimdall, just boot and recovery, Kies occasionally goes through to the end, but sometimes craps out at the same 57% point at which point the emergency restore screen shows up)
Thanks again guys

bondidave said:
Swapped the main board with the working phone to rule out the USB port - still no luck.
Click to expand...
Click to collapse
OK, but I still think the problem was initially caused by corruption. Maybe the files you have been flashing are corrupt.
Definitely interested in trying the boot from external SD, I'll do my own search for it, unless you can quickly provide me with a link - but if it's as easy as it sounds (booting off of an SD in order to be able to send ADB commands to dd copy the partitions from the good phone to SD then from the booted SD back to internal) - I'm happy to give it a shot.
Click to expand...
Click to collapse
This is the thread, it would be good to read the whole thing but if you need to save time begin at this message: http://forum.xda-developers.com/showpost.php?p=48685247&postcount=158
I have not tried this procedure yet but @noobtoob was actively involved in it.
Tempted just to swing by TMO just to see if they'll swap it "under warranty" (despite picking it up from a private sale) - the only way they would notice it's been "tampered" with would be to check the knox counter by attempting to run download mode.
Click to expand...
Click to collapse
Please try the SD-boot first so that we can add that experience to this newly developed procedure.
Oh, and yes, it does go all the way through with the flash (at least in Odin - I haven't tried a full flash through heimdall, just boot and recovery, Kies occasionally goes through to the end, but sometimes craps out at the same 57% point at which point the emergency restore screen shows up)
Click to expand...
Click to collapse
You have probably tried it, but if not, download fresh copies of everything and check the MD5 values.
Frank

Frank Westlake said:
OK, but I still think the problem was initially caused by corruption. Maybe the files you have been flashing are corrupt.
This is the thread, it would be good to read the whole thing but if you need to save time begin at this message: http://forum.xda-developers.com/showpost.php?p=48685247&postcount=158
I have not tried this procedure yet but @noobtoob was actively involved in it.
Please try the SD-boot first so that we can add that experience to this newly developed procedure.
You have probably tried it, but if not, download fresh copies of everything and check the MD5 values.
Frank
Click to expand...
Click to collapse
This was for hard brick method and no one has verified it works on 4.4 KK yet. There is an image in there though. My mediafire shows it was downloaded 11 times, but yet not a single "this works on KitKat" response. Located here you will find the kkunbrick.img. There is still a problem flashing anything through heimdall after updating to the 4.4 bootloader, so there is no way to tell if the phone actually took the recovery. I have had to switch to Odin for everything afterwards, and in personal experience 3.07 works best with my phone.
@bondidave I was thinking skipping the sd-card trick for now, and trying just a few other things first. Do you have a nandroid of any 4.4 ROMS saved anywhere? I was going to say try and flash the stock image. After it gets through flash and tries to boot into recovery, go back directly to download mode. Flash philz or twrp, whatever you need to. Try and perform a recovery boot, wipe everything, and nandroid restore of a 4.4 if you have one.
Also if you have an external find the efs fix zip and have handy on an sd-card, do the same steps above except the nandroid restore. Basically if we can get into a recovery we should be ok. I had a similar issue when it was just booting over and over into download mode and this was how I fixed it. I have never used the efs fix zip, but many others swear by it. I was able to recover fortunately enough.
Last resort try the sd-card boot. I don't necessarily think it will work with this particular case as you do not have the dreaded QHUSB_MODE and your phone is still recognized by the computer(s) you have been using.
As far as making a complete system backup of your current phone, I highly recommend against it, unless you just want to extract information from it and not re-write it. This could definitely cause some system corruption on a new device.
If none of these methods work, then try and have them swap it under warranty.

Frank Westlake said:
You have probably tried it, but if not, download fresh copies of everything and check the MD5 values
Click to expand...
Click to collapse
Yessirreeebobbyjimmy, tried several copies from several different places - that and Kies is a moron and redownloads it every time anyways.

noobtoob said:
My mediafire shows it was downloaded 11 times, but yet not a single "this works on KitKat" response.
Click to expand...
Click to collapse
I download these things just to have them handy if something fails.
Do you have a nandroid of any 4.4 ROMS saved anywhere? I was going to say try and flash the stock image. After it gets through flash and tries to boot into recovery, go back directly to download mode. Flash philz or twrp, whatever you need to. Try and perform a recovery boot, wipe everything, and nandroid restore of a 4.4 if you have one.
Click to expand...
Click to collapse
I don't think he got that far into installing 4.4, but I recommend not using anything that was saved after this problem began. If the problem was caused by corruption then the restore will reinstall the corruption.
Last resort try the sd-card boot. I don't necessarily think it will work with this particular case as you do not have the dreaded QHUSB_MODE and your phone is still recognized by the computer(s) you have been using.
Click to expand...
Click to collapse
If the problem is bad USB or other bad hardware causing corruption during transfer then the SD-card boot will get past that, then transferring the rest of the partitions by SD-card will continue to be corruption-free. He could then trade-in the phone.
But you are right -- he should try everything else before the SD-card boot. Because if something else succeeds then maybe the hardware is fine, and if he went immediately to SD-card boot he wouldn't know that.
Frank

Thanks for the advice guys - I'm going to try the backup from my other phone, then the efs fix, then the sd-card boot... I'll report back, wish me luck.

A nandroid previous failure, or a ROM install from external SD card was all I meant.
Sent from my SM-G900T using Tapatalk

I got some answers I was looking for here. Glad I read this thread.

Lorettaa said:
I got some answers I was looking for here. Glad I read this thread.
Click to expand...
Click to collapse
Glad something good came out of my frustration!
Here's a quick update: I've done everything but the boot from SD card with no luck (and actually thought I had hard(er?) bricked it for a while after trying to copy over a few images from the other phone - turns out it needed to stay with the battery out for at least 20 minutes).
Good news - walked into a TMO brick-and-mortar last night, showed the guy my endless bootloop, and a replacement is on its way to my house for an affordable $20 warranty service fee.
At this point, I'm thinking the internal flash memory is just bad - as a software engineer, I'm ok with chalking this one up to a hardware issue (as much as I was hoping that my first post on XDA would result in some new profound solution to a longstanding issue common to a few folks).
Oh well - new Note 3 on it's way, and a new S5 shortly behind it (didn't hold out much hope on TMO hooking me up, so I ordered an S5)... let the battle of the Samsungs begin!
Thanks again to you guys who helped out - and the whole XDA community in general, I am very grateful.

Finally you made it fix and enjoy the battle between your phones

Well, sucks it couldn't be fixed, but glad you got a replacement on the way. It pretty much sounded like the partitions were well over written before we attempted anything, but always worth a shot.
Sent from my SM-G900T using Tapatalk

Yes, but I don't have the details handy.
All your attempts suggest to me that you might have some damaged hardware which is causing data corruption during transfer. Open the back and take a good look at the USB port. Tighten the screws and try a transfer while firmly holding the cable in place -- don't move it while transferring. :good:

Continuous reboots, device is almost a brick... Can you help me?

Hi guys,
I had already suffered in the past for sudden reboots, but at least i was able to use the phone for a decent amount of time and fix it. After last night, though, the situation seems desperate. When i woke up i was able to turn off the alarm clock, check my email, but then hell started...
My phone is a gsm Nexus (maguro i9250), with CyanogenMod11 snapshot M5 and the appropriate google apps (at least they were appropriate about 1 month ago). I recently had some minor issue with the Google+ app, after it was updated: it kept crashing, until i uninstalled it and reinstalled after downloading from the Play Store. Should i instead search for a newer gapps packet?
Now the situation is pretty awful. The phone will reboot after at most 2 minutes. I don't really know what makes it crash so bad.
I also have two weird problems. Whatever change i manage to make before the phone reboots doesn't get persisted. For example, the alarm clock will always start activated, no matter if i managed to deactivate it before the reboot.
I'm also not able to reset it to factory defaults. I am using ClockworkMod 6.0.4.7. If i try the reset procedure, the /data and /cache partitions are formatted, but not the sdcard one. Indeed, i get the following output:
Code:
Formatting /data
Formatting /cache
Formatting /sd-ext
E: unknown volume for path [/sd-ext]
Formatting /sdcard/.android_secure
Data wipe complete
When i reboot the phone after this procedure, everything is still there, and the phone will keep doing its reboots after 1-2 minutes.
What can i do? Is there an hardware way to hard-reset the phone? Is there a program i could use?
Thanks in advance!

Fried EMMC (memory)
Sent from my Galaxy Nexus using XDA Free mobile app

mrgnex said:
Fried EMMC (memory)
Click to expand...
Click to collapse
Maybe, but if everything is still there after a reboot, sounds doubtful.
Have you tried installing a different rom? Can you connect via adb? Do you have a nandroid?

Format /system under Mounts and Storage in CWM and reflash ROM and GApps?

Hi guys, thanks for your replies! Sorry for the late answer, i was pretty busy.
I spent last night trying everything i could, but i think my phone is gone
I used Skipsoft's Android Toolkit and Odin, with no success.
The first one seemed to succeed: i tried twice, with two different stock roms, but i always ended up with the same CM11, same apps, same everything.
Odin always failed (i tried at least 3 times, i honestly lost the count).
I did find a post in the forums regarding a guy with my same problem, and he was told about the eMMC as well. I am pretty sure that is my problem as well.
Further proofs of that:
1) I downloaded the latest CM11 nightly build, was able to push its zip file on the device using Eclipse (i swear it was there), but when i tried to flash it using CWM, the file wasn't there.....
2) With Android Toolkit i was able to boot into a different recovery tool (TWM, i think). I wiped everything with it, and i was starting to hope.... but the same darn CM11 appeared!
I don't have a nandroid, i formatted everything i could in Mounts in CWM (i got to a point that i formatted everything that was formattable). I also tried to reflash the rom and gapps. No luck, always ended up with the same situation.
I didn't really try a different rom. I didn't try to connect using adb on the terminal, but i think that Eclipse is based on that, so i think adb is working.
Oh well... Right now i'm using an old phone, but i have started looking for a new one, i am tempted by the Nexus 5

frabena said:
Hi guys, thanks for your replies! Sorry for the late answer, i was pretty busy.
I spent last night trying everything i could, but i think my phone is gone
I used Skipsoft's Android Toolkit and Odin, with no success.
The first one seemed to succeed: i tried twice, with two different stock roms, but i always ended up with the same CM11, same apps, same everything.
Odin always failed (i tried at least 3 times, i honestly lost the count).
I did find a post in the forums regarding a guy with my same problem, and he was told about the eMMC as well. I am pretty sure that is my problem as well.
Further proofs of that:
1) I downloaded the latest CM11 nightly build, was able to push its zip file on the device using Eclipse (i swear it was there), but when i tried to flash it using CWM, the file wasn't there.....
2) With Android Toolkit i was able to boot into a different recovery tool (TWM, i think). I wiped everything with it, and i was starting to hope.... but the same darn CM11 appeared!
I don't have a nandroid, i formatted everything i could in Mounts in CWM (i got to a point that i formatted everything that was formattable). I also tried to reflash the rom and gapps. No luck, always ended up with the same situation.
I didn't really try a different rom. I didn't try to connect using adb on the terminal, but i think that Eclipse is based on that, so i think adb is working.
Oh well... Right now i'm using an old phone, but i have started looking for a new one, i am tempted by the Nexus 5
Click to expand...
Click to collapse
You can try by downloading a clean google factory image and then flash it using bootloader and see it helps, it could be a bad script inside. If this doesn't help then you should totally get the Nexus 5. I got GNex only recently and its still a good device I reassure you. A little tweak and a little overclock makes it as good as a stock N4 minus the bad graphics.

frabena said:
Hi guys, thanks for your replies! Sorry for the late answer, i was pretty busy.
I spent last night trying everything i could, but i think my phone is gone
I used Skipsoft's Android Toolkit and Odin, with no success.
The first one seemed to succeed: i tried twice, with two different stock roms, but i always ended up with the same CM11, same apps, same everything.
Odin always failed (i tried at least 3 times, i honestly lost the count).
I did find a post in the forums regarding a guy with my same problem, and he was told about the eMMC as well. I am pretty sure that is my problem as well.
Further proofs of that:
1) I downloaded the latest CM11 nightly build, was able to push its zip file on the device using Eclipse (i swear it was there), but when i tried to flash it using CWM, the file wasn't there.....
2) With Android Toolkit i was able to boot into a different recovery tool (TWM, i think). I wiped everything with it, and i was starting to hope.... but the same darn CM11 appeared!
I don't have a nandroid, i formatted everything i could in Mounts in CWM (i got to a point that i formatted everything that was formattable). I also tried to reflash the rom and gapps. No luck, always ended up with the same situation.
I didn't really try a different rom. I didn't try to connect using adb on the terminal, but i think that Eclipse is based on that, so i think adb is working.
Oh well... Right now i'm using an old phone, but i have started looking for a new one, i am tempted by the Nexus 5
Click to expand...
Click to collapse
Well I got bad news well not really bad but kinda. If you wiped efs data while you were wiping your phone will never properly connect to the network anymore. That obviously won't matter unless you somehow get out of this bootloop.

for anyone looking for twrp for t520 10.1 wifi only

It is auto loaded when you load flashify. Then u can select wether u want twrp or cw recovery.
Hope this helps someone as twrp. Wifi t520 is not available on twrp site.

+1 confirmed it worked on mine (t520).

Can also be retrieved here if you want to flash via Odin.
http://goo.im/devs/OpenRecovery/picassowifi
I fond myself in a situation where my tablet wouldn't boot and I needed to install a custom recovery, so I had to flash via Odin.

I was just going to post a thread about this. Flashify app is the easiest way I have ever used to install custom recovery!

More details?
All,
I rooted my 10.1 yesterday, since ROMS are starting to come out. I used TWRP and CWM on a Toshiba Thrive prior to own the tab pro.
Anyways...I rooted last night with Odin, but still only have the stock recovery.
Please tell me how to get TWRP installed, without messing up the tablet (it is an expensive device, just want to make sure I don't brick it!)
Just flash the zip from the stock recovery?
Unroot and re-root using flashify or Odin?
I can't wait to get rid of all the Samsung crap!!! (but want to backup first)
Thanks a lot,
Damien

Re twrp for t520 and roms
Wish there was some way to help young 14 year old ik4ver [written first custom rom for our device]...some deadbeat loser keeps sabotaging his account now hijacked to extort a rom for the 12.2!!! I have never seen anything like this...hopefully karma works her magic on this scumbag!

I know right...I fortunately got his v3 rom yesterday before his posts got hacked again.
Tried to flash his rom today and almost bricked the tab, twrp couldn't mount ./system. Got stuck on the Samsung logo after this. Fortunately after 3 tries my twrp backup finally restored properly.
Does anyone know the exact steps to follow in twrp before flashing his rom?
Before not being able to mount system, it was saying can't mount cache, which seems to have resolved itself. Weird...
Sent from my SM-T520 using Tapatalk

rom thread back up
Can't help yet ..I haven't had balls to flash rom yet lol. Looks like his rom thread is back up and running for now.
MrBungle67 said:
I know right...I fortunately got his v3 rom yesterday before his posts got hacked again.
Tried to flash his rom today and almost bricked the tab, twrp couldn't mount ./system. Got stuck on the Samsung logo after this. Fortunately after 3 tries my twrp backup finally restored properly.
Does anyone know the exact steps to follow in twrp before flashing his rom?
Before not being able to mount system, it was saying can't mount cache, which seems to have resolved itself. Weird...
Sent from my SM-T520 using Tapatalk
Click to expand...
Click to collapse

when u figure out can you post solution? would be helpfull
perhaps young ik4evr will surface with a suggestion.
MrBungle67 said:
I know right...I fortunately got his v3 rom yesterday before his posts got hacked again.
Tried to flash his rom today and almost bricked the tab, twrp couldn't mount ./system. Got stuck on the Samsung logo after this. Fortunately after 3 tries my twrp backup finally restored properly.
Does anyone know the exact steps to follow in twrp before flashing his rom?
Before not being able to mount system, it was saying can't mount cache, which seems to have resolved itself. Weird...
Sent from my SM-T520 using Tapatalk
Click to expand...
Click to collapse

I did...have balls
spton said:
Can't help yet ..I haven't had balls to flash rom yet lol. Looks like his rom thread is back up and running for now.
Click to expand...
Click to collapse
Yep...I tried again...
So, in order, I...
- Rooted using Odin
- Install TWRP using Flashify (thanks to K8108 for the earlier post)
- Went to recovery
- Went to "Mount" and made sure all was checked
- Went to "Wipe", "Advanced"
- Checked everything except internal and external storage
- Install ik4evr's ROM
- Rebooted...
Tablet booted no problem (it stays on "SAMSUNG" for a little bit, which worried me...)
All Samsung apps are gone!!!

that's awesome thanks for the procedure details!
Actually it was young ik4evr that let me know bout twrp being auto loaded in flashify .. that's why I started thread as it's kinda confusing as twrp site doesn't list t520 wifi only.
Good work!

spton said:
Actually it was young ik4evr that let me know bout twrp being auto loaded in flashify .. that's why I started thread as it's kinda confusing as twrp site doesn't list t520 wifi only.
Good work!
Click to expand...
Click to collapse
This all forum is freaking confsuing, as it is about 6 (8?) different devices, where some are kinda similar, and others completely different (thinking especially of Exynos vs Qualcomm).
Plus there is no real guide, and takes hours trying to figure out if this thread/recovery/rom applies to our device or not.
Plus 8.4 became modrian, and 10.1 picasso.
Yay, confusing is the right word!!!

well I've loaded Treo with flashify and done full stock rooted rom
Backup. Now have to grow a pair and flash ver3 of ik4evrs rom! So you have zero issues and everything working?
I was going to wait at least till his thread gets sorted out...hmmm...i voided warranty anyway at this point lol
MrBungle67 said:
This all forum is freaking confsuing, as it is about 6 (8?) different devices, where some are kinda similar, and others completely different (thinking especially of Exynos vs Qualcomm).
Plus there is no real guide, and takes hours trying to figure out if this thread/recovery/rom applies to our device or not.
Plus 8.4 became modrian, and 10.1 picasso.
Yay, confusing is the right word!!!
Click to expand...
Click to collapse

Treo = twrp
Dang spell correction!

spton said:
Backup. Now have to grow a pair and flash ver3 of ik4evrs rom! So you have zero issues and everything working?
I was going to wait at least till his thread gets sorted out...hmmm...i voided warranty anyway at this point lol
Click to expand...
Click to collapse
Zero issue wouldn't the word lol! I did have a bit of a cold sweat yeterday...
I'd say as long as you have the stock rom backup go for it!
I actually started a thread separated from here. I wonder if "wipe internal storage" ok or not...what I can see is that bunch of folders remained from apps installed before flashing the rom.
As far as the steps listed above, I just did it this morning and all went well. As far as deep testing to see if everything is still working, I can't answer yet (at work, no time to play with it).
Let me know if you have any issue...

Ball grown yet?
Alright...so:
- Went to recovery
- Went to "Mount" and made sure all was checked
- Went to "Wipe", "Advanced"
- Checked everything except external storage
- Install ik4evr's ROM
- Rebooted...
Just reflashed the rom, this time wiping the internal storage as well.
After apps update, 472mb used, 11Gb free (was 6gb used before wiping the internal storage).
So far, the only issue is something I read on a post somewhere, but contacts aren't syncing.
I am sure a V4 will be here soon!!
Everything else seems to be working.

MrBungle67 said:
Yep...I tried again...
So, in order, I...
- Rooted using Odin
- Install TWRP using Flashify (thanks to K8108 for the earlier post)
- Went to recovery
- Went to "Mount" and made sure all was checked
- Went to "Wipe", "Advanced"
- Checked everything except internal and external storage
- Install ik4evr's ROM
- Rebooted...
Tablet booted no problem (it stays on "SAMSUNG" for a little bit, which worried me...)
All Samsung apps are gone!!!
Click to expand...
Click to collapse
I did the same. All worked.
Unfortunately I cannot restore apps succesfully from Titanium backup. The restore seems to be ok, but I only get FC's. The apps will not start. I cannot find the cause of the errors.
Something in directions of maps destination changed? Knox?
I do not understand it.

I had a hard time with TB also. Had to get most of my apps back from the play store. Lost some data. Oh well. My contacts are syncing from Google, tho.

k8108 said:
I had a hard time with TB also. Had to get most of my apps back from the play store. Lost some data. Oh well. My contacts are syncing from Google, tho.
Click to expand...
Click to collapse
I always reinstall from the play store... I like it clean and fresh, and I don't have that many apps to restore.
Now...How did you get your contacts? I just installed google+, and my circles finally synced in the contact app. As far as all other contacts (gmail), can't sync them...
Sent from my SM-T520 using Tapatalk

I don't know why my contacts are syncing. The only difference I can see is that in our flashing the rom, I didn't do the advanced wiping. I just did factory reset and cache wipe. I left my system unwiped. I'm not real savvy on this stuff - I have just been a good instruction follower for the past few years and have spent lots of hours reading here on XDA. I am heavily addicted to my tablets and use them for several hours a day so I have over 100 apps. It's a real pain for me to have to go thru the play store for a restore
Sent from my SM-T520 using XDA Premium 4 mobile app