Related
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
AT&T Galaxy S3
Mac OSX 10.8
I know I can get my device back, I'm just not sure how. I successfully rooted using CASUAL, no problems there. Got the normal root applications installed, did the Clockwork backup, everything was great.
I then decided to try a custom ROM - the Cyanogen 10.1. It downloaded fine, and I selected to also install Google Apps, then it rebooted and the Cyanogen boot screen with the spinning circle came up. However, this lasted way longer than I thought it should, so I looked it up, and what I got from the research is that I had the wrong gapps on there.
So, I followed the instructions in this thread (same problem as me), and wiped the system. However, I believe I used the wrong list item, and now everything I had is gone. I can't boot from recovery because it doesn't exist, and when booting into CM I just get the same error message that setup has stopped working. I thought maybe I could put a new ROM on the sd card or phone harddrive and boot from that, but both are inaccessible through USB on my Mac.
I can get it into ODIN mode (where it says "Downloading... Do not turn off target!"), which I'm thinking is what I want, and I have Heimdall installed and it runs and recognizes my device, but I cannot for the life of me find a tar.gz file to use.
If anyone can offer any sort of help, I would super appreciate it.
chazbot7 said:
AT&T Galaxy S3
Mac OSX 10.8
I know I can get my device back, I'm just not sure how. I successfully rooted using CASUAL, no problems there. Got the normal root applications installed, did the Clockwork backup, everything was great.
I then decided to try a custom ROM - the Cyanogen 10.1. It downloaded fine, and I selected to also install Google Apps, then it rebooted and the Cyanogen boot screen with the spinning circle came up. However, this lasted way longer than I thought it should, so I looked it up, and what I got from the research is that I had the wrong gapps on there.
So, I followed the instructions in this thread (same problem as me), and wiped the system. However, I believe I used the wrong list item, and now everything I had is gone. I can't boot from recovery because it doesn't exist, and when booting into CM I just get the same error message that setup has stopped working. I thought maybe I could put a new ROM on the sd card or phone harddrive and boot from that, but both are inaccessible through USB on my Mac.
I can get it into ODIN mode (where it says "Downloading... Do not turn off target!"), which I'm thinking is what I want, and I have Heimdall installed and it runs and recognizes my device, but I cannot for the life of me find a tar.gz file to use.
If anyone can offer any sort of help, I would super appreciate it.
Click to expand...
Click to collapse
Your recovery shouldn't be affected by a wipe (unless you flashed something over it) as ROMs don't flash recovery, therefor vol up + home + power should get you in it. If you success to, You should be able to mount through recovery.
As for Heimdall, it just got S3 support (last week I believe), therefor it might not be easy to find a stock file for it. That being said, if you have access to any Windows pc, that'd be the easiest solution here (using Odin).
Yes, I can still get into the recovery menu, but when I use "backup and restore>restore" it says No files found. Is there anything I can do to just get a working OS running? Or am I just doing it totally wrong, I'm new to the rooting stuff. The Windows computer will be my last resort haha.
BWolf56 said:
Your recovery shouldn't be affected by a wipe (unless you flashed something over it) as ROMs don't flash recovery, therefor vol up + home + power should get you in it. If you success to, You should be able to mount through recovery.
As for Heimdall, it just got S3 support (last week I believe), therefor it might not be easy to find a stock file for it. That being said, if you have access to any Windows pc, that'd be the easiest solution here (using Odin).
Click to expand...
Click to collapse
Yes, I can still get into the recovery menu, but when I use "backup and restore>restore" it says No files found. Is there anything I can do to just get a working OS running? Or am I just doing it totally wrong, I'm new to the rooting stuff. The Windows computer will be my last resort haha.
chazbot7 said:
Yes, I can still get into the recovery menu, but when I use "backup and restore>restore" it says No files found. Is there anything I can do to just get a working OS running? Or am I just doing it totally wrong, I'm new to the rooting stuff. The Windows computer will be my last resort haha.
Click to expand...
Click to collapse
Windows pc is definitely the easiest option here but you try mounting your SD from recovery, redownload the ROM and Gapps you wanna use, put them on your device and flash them after a factory reset.
If you wiped your SD card, it's normal that you don't have a backup anymore.
BWolf56 said:
Windows pc is definitely the easiest option here but you try mounting your SD from recovery, redownload the ROM and Gapps you wanna use, put them on your device and flash them after a factory reset.
If you wiped your SD card, it's normal that you don't have a backup anymore.
Click to expand...
Click to collapse
It's aaaliiiiiiive! Grabbed an extra micro SD I had, threw Cyanogen 10.1.0 RC4 on it, and installed it just fine. Now updating to RC5. My only question now is how to get Google Apps on there. Does this need to be done beforehand, or can it be done after?
chazbot7 said:
It's aaaliiiiiiive! Grabbed an extra micro SD I had, threw Cyanogen 10.1.0 RC4 on it, and installed it just fine. Now updating to RC5. My only question now is how to get Google Apps on there. Does this need to be done beforehand, or can it be done after?
Click to expand...
Click to collapse
You usually flash the Gapps right after flashing the ROM, before rebooting.
P.S.: fully reading the instructions helps before flashing
Sent from my SGH-I747 using xda app-developers app
BWolf56 said:
You usually flash the Gapps right after flashing the ROM, before rebooting.
P.S.: fully reading the instructions helps before flashing
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Gotcha, sorry about that. Thanks for all the help good sir. This is actually way faster than my stock ROM, I'm pretty stoked on it, Google Apps or not.
chazbot7 said:
Gotcha, sorry about that. Thanks for all the help good sir. This is actually way faster than my stock ROM, I'm pretty stoked on it, Google Apps or not.
Click to expand...
Click to collapse
No need to apologize. Glad you got it back up! And it was mostly to keep you from making similar mistakes in the future
Sent from my SGH-I747 using xda app-developers app
also one thing you need to know
First boot after you flash will always take longer than normal. After that, it's fine
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.
I apologize in advance if any of this makes you roll your eyes at my stupidity.
Good Afternoon
I have an ATT samsung galaxy s3, Because of the glitches with 4.3 I was experiencing I decided to install custom software on my phone. So I looked up guides and got everything I needed. I did manage to get root access, and verified with super user. I also installed TWRP and CWM because each kept giving me errors when I tried to install CM 11 onto my phone. I tried CWM first, and when that didn't work I tried TWRP. It says there was no MD5 information found when I try to install any mod. how ever I have used the md5 file checker program and the MD5 matches up to what was listed in this one for example.
http://forum.xda-developers.com/show....php?t=2518998
Download:
CM 11.0 Unofficial Beta 7 for d2tmo and d2att
MD5: ef93957db1e6704f23f9015231a82826
So the MD5 matches, yet when I try to install it keeps giving me errors. I also tried other versions of CM that I found on here via links. Right now my phone has no OS as another guide I read some where also said to wipe system data (sorry if that was stupid, I was just following a guideline) And even more stupid, no I don't have a backup because in my naivety and stupidity I didn't think I'd need one as it seemed so simple from all the guides and videos I'd seen.
Yesterday a friend of mine knowledgeable with tech stuff took one of the original stock Image ROMs I'd downloaded and using linux and some program he managed to do some crazy stuff I can't even describe on here. All I saw was a lot of typing of command lines and it got my phone working again, how ever it wasn't exactly the stock image I guess because the phone would not make or receive calls/texts.
Since my phone was powering on again and the android OS was loading I figured I could connect it to my computer and use KIES to download the official latest update so my phone would be back on the legit software. But trying to do that...well broke my phone again. So I'm at a loss now of what to do. Right now I can still get to download mode on my phone, but when I try to get into recovery mode I get an error that "firmware upgrade encountered an issue. Please select recovery mode in KIES & try again." Which I've tried, and every time I try it gives me an error message.So I'm at a loss of what to do next.
So I'd like to get a working OS on my phone asap so I can get calls and texts.
Any help would be greatly appreciated. And being new I'm sorry if I broke any taboos or did not give some information that is typically given when describing a problem.
gvazquez82 said:
I apologize in advance if any of this makes you roll your eyes at my stupidity.
Good Afternoon
I have an ATT samsung galaxy s3, Because of the glitches with 4.3 I was experiencing I decided to install custom software on my phone. So I looked up guides and got everything I needed. I did manage to get root access, and verified with super user. I also installed TWRP and CWM because each kept giving me errors when I tried to install CM 11 onto my phone. I tried CWM first, and when that didn't work I tried TWRP. It says there was no MD5 information found when I try to install any mod. how ever I have used the md5 file checker program and the MD5 matches up to what was listed in this one for example.
http://forum.xda-developers.com/show....php?t=2518998
Download:
CM 11.0 Unofficial Beta 7 for d2tmo and d2att
MD5: ef93957db1e6704f23f9015231a82826
So the MD5 matches, yet when I try to install it keeps giving me errors. I also tried other versions of CM that I found on here via links. Right now my phone has no OS as another guide I read some where also said to wipe system data (sorry if that was stupid, I was just following a guideline) And even more stupid, no I don't have a backup because in my naivety and stupidity I didn't think I'd need one as it seemed so simple from all the guides and videos I'd seen.
Yesterday a friend of mine knowledgeable with tech stuff took one of the original stock Image ROMs I'd downloaded and using linux and some program he managed to do some crazy stuff I can't even describe on here. All I saw was a lot of typing of command lines and it got my phone working again, how ever it wasn't exactly the stock image I guess because the phone would not make or receive calls/texts.
Since my phone was powering on again and the android OS was loading I figured I could connect it to my computer and use KIES to download the official latest update so my phone would be back on the legit software. But trying to do that...well broke my phone again. So I'm at a loss now of what to do. Right now I can still get to download mode on my phone, but when I try to get into recovery mode I get an error that "firmware upgrade encountered an issue. Please select recovery mode in KIES & try again." Which I've tried, and every time I try it gives me an error message.So I'm at a loss of what to do next.
So I'd like to get a working OS on my phone asap so I can get calls and texts.
Any help would be greatly appreciated. And being new I'm sorry if I broke any taboos or did not give some information that is typically given when describing a problem.
Click to expand...
Click to collapse
same error happened to me yesterday and spent the whole day figuring it out. get into download mode. boot up ODIN and reflash your preferred custom recovery. after that, i couldn't find anything else to restore my phone with so i installed 4.3 leaked from here. doesn't matter which one you select. http://forum.xda-developers.com/showthread.php?t=2498233. place it on your sd card and head into recovery mode, wipe data/factory reset and cache. head to install zip from sd card and select the 4.3 zip you downloaded. reboot system and it should work. the at&t boot screen takes a while so be patient
MrHaPpY66 said:
same error happened to me yesterday and spent the whole day figuring it out. get into download mode. boot up ODIN and reflash your preferred custom recovery. after that, i couldn't find anything else to restore my phone with so i installed 4.3 leaked from here. doesn't matter which one you select. http://forum.xda-developers.com/showthread.php?t=2498233. place it on your sd card and head into recovery mode, wipe data/factory reset and cache. head to install zip from sd card and select the 4.3 zip you downloaded. reboot system and it should work. the at&t boot screen takes a while so be patient
Click to expand...
Click to collapse
First of all thank you for trying to help me, I hope you are having a good Thanks Giving.
I used the thread you linked to, and downloaded the version with out knox. I followed the instructions
transferred ROM and flashed kernel file to SD card
used odin to flash TWRP,
used twrp to flash rom and kernel file.
and it takes the file thankfully, there's only one issue. My phone can't make or receive calls/texts. Is yours able to?
I messed up and was playing with things That I had no business playing with and decided that I should do a restore of a backup (TWRP) I made as soon as I rooted the 4.3 OTA. well it has soft bricked my phone. it was a TWRP 4.3 Nandroid and has me messed up a little.
so far I tried My nandroid (no dice now a soft brick) cleared cache and dalvik, It was booting as far as the white at&t spinning thing,
Factory reset same on booting,
Tried a format of the internal sd this is where it gets sketchy it now goes as far as the second samsung screen(the one that says Samsung GALAXY S III)
4.3 OTA .zip (no dice TWRP wont flash it) same on the booting 2nd samsung boot screen
Tried the files in the link above and got a Hard brick
Used the debricking .IMG file and got TWRP and download mode back
Any suggestions?
Looks like I might need a JTAG/RIFF BOX for this one. If nothing else I spent many Hours of darkness discovering the darkness of android 4.3
If I get recovered from this and with a different rom like 4.1.2 I will be happy. the 4.3 OTA was very stable but I did miss wifi tether and the whole hardbrick thing was kind of a bummer. it would be real nice to have an ODIN file to fix this (AHEM samsung) or atleast perhaps stopped the progression of it to a hard brick.
New update
I got my phone booting up again however there is a catch. That unbrick.img file on my 16GB sd card is still required to boot the phone and I have no cell service what so ever. Tried to check apn settings because at home I sometimes get poor service and I run net10 so I was going to fix my apn and it says insert sim??? the sim is properly inserted???
Next Update
the bootloader I flashed apparently flashed to the external sd card? I flashed another one and it is booting from the internal sd. I had to flash a different modem the one in the bootloader/modem file I flashed from the link above didnt take? I got most everything sorted out, but im getting tired, it has been an all night adventure. its 08:23 est now
sorry for the delay in updating this I had to get some rest.
theramsey3 said:
I messed up and was playing with things That I had no business playing with and decided that I should do a restore of a backup (TWRP) I made as soon as I rooted the 4.3 OTA. well it has soft bricked my phone. it was a TWRP 4.3 Nandroid and has me messed up a little.
so far I tried My nandroid (no dice now a soft brick) cleared cache and dalvik, It was booting as far as the white at&t spinning thing,
Factory reset same on booting,
Tried a format of the internal sd this is where it gets sketchy it now goes as far as the second samsung screen(the one that says Samsung GALAXY S III)
4.3 OTA .zip (no dice TWRP wont flash it) same on the booting 2nd samsung boot screen
Tried the files in the link above and got a Hard brick
Used the debricking .IMG file and got TWRP and download mode back
Any suggestions?
Looks like I might need a JTAG/RIFF BOX for this one. If nothing else I spent many Hours of darkness discovering the darkness of android 4.3
If I get recovered from this and with a different rom like 4.1.2 I will be happy. the 4.3 OTA was very stable but I did miss wifi tether and the whole hardbrick thing was kind of a bummer. it would be real nice to have an ODIN file to fix this (AHEM samsung) or atleast perhaps stopped the progression of it to a hard brick.
New update
I got my phone booting up again however there is a catch. That unbrick.img file on my 16GB sd card is still required to boot the phone and I have no cell service what so ever. Tried to check apn settings because at home I sometimes get poor service and I run net10 so I was going to fix my apn and it says insert sim??? the sim is properly inserted???
Click to expand...
Click to collapse
Go into Settings, About Phone, Status and check to see if your IMEI and Serial Number are present. If you only lost your IMEI there's a guide on how to inject it back (I'm not sure where the guide is). However if you've lost your serial number and don't have a Nandroid that can restore it I don't know what to do.
spongdangly said:
Go into Settings, About Phone, Status and check to see if your IMEI and Serial Number are present. If you only lost your IMEI there's a guide on how to inject it back (I'm not sure where the guide is). However if you've lost your serial number and don't have a Nandroid that can restore it I don't know what to do.
Click to expand...
Click to collapse
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
gvazquez82 said:
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
Click to expand...
Click to collapse
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
theramsey3 said:
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
Click to expand...
Click to collapse
I will give that a shot, but what's an APN, sorry. And how do I create one, and is it needed for me to do so?
gvazquez82 said:
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
Click to expand...
Click to collapse
It should be, I'm working right now so I don't have time to fine the guide on how to inject your IMEI. If I remember correctly it involves using QPST. If you have an old (or any) working Nandroid backup that should fix the problem.
FYI, make sure you don't use the guide for the international S3 as it has different hardware and folder structure/contents.
As for the APN, it should automatically fill itself in since it reads it off the SIM Card (I might be wrong).
theramsey3 said:
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
Click to expand...
Click to collapse
I tried it and it work!!!!!!!!!!!!!!!!!
67 texts just came in. Sir, I thank you oh so kindly. You have made this gloomy rainy day oh so joyous.
No problem. Glad I could help you.
The real credit should go to -Mr.X-, loserskater and anyone else(no disrespect there were alot of files) whose stuff I tried to flash lastnight thank you all in the dev community who contribute.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
So I guess the next question, do I try again to install kit kat on my phone.
I've already made bucks of my existing working phone haha....but I'd still like to have kitkat in place. I believe the issue of my phone not reading MD5 confirmations would still be in place, does anyone know how to remedy that situation?
At the same time I'm more than happy to leave my phone as is.
gvazquez82 said:
So I guess the next question, do I try again to install kit kat on my phone.
I've already made bucks of my existing working phone haha....but I'd still like to have kitkat in place. I believe the issue of my phone not reading MD5 confirmations would still be in place, does anyone know how to remedy that situation?
At the same time I'm more than happy to leave my phone as is.
Click to expand...
Click to collapse
Pretty sure you can turn off MD5 checks in TWRP. Probably in CWM too. Sorry if this has been mentioned. Didn't have time to read the whole thread. Just skimmed through.
2nd, there is a major difference between an IMEI that reads 0 and an IMEI that shows unknown. If it shows an unknown simply reflash your ROM and modem and you will be good to go. Sometimes a reboot is all you need. If your IMEI is showing a 0 on the other hand its gone and will require that it be injected back in which is a messy situation that usually results in tour phone being stuck on EDGE.
3rd, as someone mentioned on the previous page, restoring a working nandroid will NOT reinject your IMEI if it shows up as 0. No amount of flashing anything will get it to come back. Not even stock. It needs to be reinjected manually.
flexfulton said:
Pretty sure you can turn off MD5 checks in TWRP. Probably in CWM too. Sorry if this has been mentioned. Didn't have time to read the whole thread. Just skimmed through.
2nd, there is a major difference between an IMEI that reads 0 and an IMEI that shows unknown. If it shows an unknown simply reflash your ROM and modem and you will be good to go. Sometimes a reboot is all you need. If your IMEI is showing a 0 on the other hand its gone and will require that it be injected back in which is a messy situation that usually results in tour phone being stuck on EDGE.
3rd, as someone mentioned on the previous page, restoring a working nandroid will NOT reinject your IMEI if it shows up as 0. No amount of flashing anything will get it to come back. Not even stock. It needs to be reinjected manually.
Click to expand...
Click to collapse
do you know of a good stable kit kat like ROM I could use for the s3? And any speculation as to why the ROMs werent taking for me?
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: