Okay not sure how many people still frequent this forum, but hopefully someone can help. So yesterday my phone was charging up and I decided to reboot it because it was time for a weekly reboot. So I held the power button and selected reboot to reboot it. It shut down then started to boot, the samsung logo appeared then disappeared followed by the galaxy s3 logo.
After that it just shut off. When I tried to turn it on again, all it did was vibrate vibrant and vibrant in a loop every time I pushed the power button. Finally I decided to try recovery mode (stock recovery) and wipe cache...no dice. So I tried download mode and that came up fine. I rebooted out of download mode and plugged the phone in. The charge animation came up as well as the LED red charge light. I let it charge for a few hours then unplugged it, removed the battery for a minute and put it back in and tried to turn it on. I even tried a different/another battery and got the same result.
All it did was the vibrate loop sequence again i mentioned above. I don't want to loose all my stuff I have on it. I heard dirty flashing in ODIN will wipe your data. I'm not sure if the debrick image is for Android 4.4.2 because that's what I'm on. Does anyone know how to fix this or have had similar issues and got it working again?
StoneyJSG said:
Okay not sure how many people still frequent this forum, but hopefully someone can help. So yesterday my phone was charging up and I decided to reboot it because it was time for a weekly reboot. So I held the power button and selected reboot to reboot it. It shut down then started to boot, the samsung logo appeared then disappeared followed by the galaxy s3 logo.
After that it just shut off. When I tried to turn it on again, all it did was vibrate vibrant and vibrant in a loop every time I pushed the power button. Finally I decided to try recovery mode (stock recovery) and wipe cache...no dice. So I tried download mode and that came up fine. I rebooted out of download mode and plugged the phone in. The charge animation came up as well as the LED red charge light. I let it charge for a few hours then unplugged it, removed the battery for a minute and put it back in and tried to turn it on. I even tried a different/another battery and got the same result.
All it did was the vibrate loop sequence again i mentioned above. I don't want to loose all my stuff I have on it. I heard dirty flashing in ODIN will wipe your data. I'm not sure if the debrick image is for Android 4.4.2 because that's what I'm on. Does anyone know how to fix this or have had similar issues and got it working again?
Click to expand...
Click to collapse
You could try reflashing system and boot partition.
iloveoreos said:
You could try reflashing system and boot partition.
Click to expand...
Click to collapse
Is this done in ODIN? Will it wipe all my data? I'm trying to avoid anything like a data factory reset as I want to recover my stuff that wasn't saved to my SD card.
StoneyJSG said:
Is this done in ODIN? Will it wipe all my data? I'm trying to avoid anything like a data factory reset as I want to recover my stuff that wasn't saved to my SD card.
Click to expand...
Click to collapse
I don't know why it would, but I have never tried it on a Samsung. Flashing something like TWRP doesn't erase data when you flash it.
Which ROM is currently on the phone?
AT&T never released a stock ROM for the sgh-i747 after 4.1.1 or 4.1.2. All system updates were pushed to the phone via OTA; therefore, you can't re-flash the ROM using Odin unless you use a file that was specfically create for Odin.
audit13 said:
Which ROM is currently on the phone?
AT&T never released a stock ROM for the sgh-i747 after 4.1.1 or 4.1.2. All system updates were pushed to the phone via OTA; therefore, you can't re-flash the ROM using Odin unless you use a file that was specfically create for Odin.
Click to expand...
Click to collapse
Would the one for sgh i747m work if you just flashed system and boot? You can get that in 4.4.2.
Before flashing anything, I recommend booting into download mode and confirm the the model is SGH-i747 and whether there is a line that makes reference to Knox or warranty bit.
If it is the sgh-i747 and there is reference to warranty bit, you should look at the possibility of flashing a ROM from here: https://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654
If it is an sgh-i747 with no reference to warranty bit, this means the phone is not running a 4.3 or newer bootloader.
audit13 said:
Before flashing anything, I recommend booting into download mode and confirm the the model is SGH-i747 and whether there is a line that makes reference to Knox or warranty bit.
If it is the sgh-i747 and there is reference to warranty bit, you should look at the possibility of flashing a ROM from here: https://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654
If it is an sgh-i747 with no reference to warranty bit, this means the phone is not running a 4.3 or newer bootloader.
Click to expand...
Click to collapse
It is on Android 4.4.2 with bootloader NE4. It's the sgh-i747 AT&T variant. My warranty bit is 0. I can boot into download mode and stock recovery fine, just it won't boot into Android. I read somewhere that it might be an IC chip or emmc issue?
Someone took the NE4 OTA and made some ODIN files out of it so I downloaded them. I just want to be able to recover my files from the internal storage so I haven't flashed anything yet.
Glad you are on top of things.
Flashing the same ROM should be fine and it does not normally wipe your data. That being said, there is always a chance that flashing will result in data loss.
If it is an errant app that is causing the issue, you may have no choice but to wipe the data.
Ah ok, that's a bummer. Well I guess I will try flashing the same ROM over it and see what happens. Hopefully my data and apps stay in tact. I thought it might be a chip on the logic board so I took it to a repair shop over the weekend. Now to get it back from them and try flashing the ROM over the ROM.
audit13 said:
Glad you are on top of things.
Flashing the same ROM should be fine and it does not normally wipe your data. That being said, there is always a chance that flashing will result in data loss.
If it is an errant app that is causing the issue, you may have no choice but to wipe the data.
Click to expand...
Click to collapse
Just an update. I managed to fix my phone with Odin. I flashed the NE4 kit kat BL, AP, CSC, and CP files. It did wipe everything and put it back to factory stock like a factor data reset would do, so I lost all my files and apps.
Sorry to hear that the data was wiped.
Thanks for the update.
CrDroid O/S works good on my old Samsung Galaxy S3 i747
audit13 said:
Before flashing anything, I recommend booting into download mode and confirm the the model is SGH-i747 and whether there is a line that makes reference to Knox or warranty bit.
If it is the sgh-i747 and there is reference to warranty bit, you should look at the possibility of flashing a ROM from here: https://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654
If it is an sgh-i747 with no reference to warranty bit, this means the phone is not running a 4.3 or newer bootloader.
Click to expand...
Click to collapse
Firstly, I am a newbie. I don't understand about this "warranty bit" . The Samsung S3 i747 is a very old phone ( hence no warranty after 8+ years ). Please explain !
---------- Post added at 04:46 PM ---------- Previous post was at 04:37 PM ----------
StoneyJSG said:
Okay not sure how many people still frequent this forum, but hopefully someone can help. So yesterday my phone was charging up and I decided to reboot it because it was time for a weekly reboot. So I held the power button and selected reboot to reboot it. It shut down then started to boot, the samsung logo appeared then disappeared followed by the galaxy s3 logo.
After that it just shut off. When I tried to turn it on again, all it did was vibrate vibrant and vibrant in a loop every time I pushed the power button. Finally I decided to try recovery mode (stock recovery) and wipe cache...no dice. So I tried download mode and that came up fine. I rebooted out of download mode and plugged the phone in. The charge animation came up as well as the LED red charge light. I let it charge for a few hours then unplugged it, removed the battery for a minute and put it back in and tried to turn it on. I even tried a different/another battery and got the same result.
All it did was the vibrate loop sequence again i mentioned above. I don't want to loose all my stuff I have on it. I heard dirty flashing in ODIN will wipe your data. I'm not sure if the debrick image is for Android 4.4.2 because that's what I'm on. Does anyone know how to fix this or have had similar issues and got it working again?
Click to expand...
Click to collapse
I'm not sure how many of us are out there, tinkering around with the 8+ year old Samsung Galaxy S3 i747 . While I am a newbie, I have enjoyed flashing Custom ROM's , from CyanogenMod, thru various versions of Lineage, and now CRdroid.
You spoke of: " . . . dirty flashing in ODIN . . . "
I have always used ODIN to INSTALL a 'recovery' system such as TWRP ( which is a .Tar file )
After TWRP is installed ( using ODIN ) I unplug phone from my computer. Then boot into TWRP recovery ( holding down the three buttons ). I do a clean install (flash) of the newest O/S that I can find ( Android 4.4 is really old ). It is that .Zip file that I flash, then reboot the phone. Always works for me.
Eventually I learned how to back up all my contacts, SMS, logs, photos, etc.
BTW I am totally free of Google; no Google Play Store, no Google Pay, no Google Framework, no Gapps, no Google spyware, no Google bloatware, no Google tracking etc.
I download all my apps as APK's which are readily available on the Net ( Google them . . . just kidding! ).
My older Samsung S3 i747 was a 'd2att' originally locked to Rogers, in Ottawa, Ontario, Canada. Then switched over to MTS (Manitoba Telephone System). Now running on Bell Canada. My replacement is also a Samsung S3 i747, originally running T-Mobile in Arizona, now running on Bell Canada.
These are damn fine phones.
DavidWCS said:
Firstly, I am a newbie. I don't understand about this "warranty bit" . The Samsung S3 i747 is a very old phone ( hence no warranty after 8+ years ). Please explain !.
Click to expand...
Click to collapse
Do you see anything in the download mode screen that has the term "warranty bit"?
Is the phone model in download mode screen shown as an sgh-i747 or sgh-747m?
audit13 said:
Do you see anything in the download mode screen that has the term "warranty bit"?
Is the phone model in download mode screen shown as an sgh-i747 or sgh-747m?
Click to expand...
Click to collapse
Curious, I rebooted my phone into download mode ( holding volume down in the 3 finger format ).
There is nothing in the download mode screen that has the term "warranty bit". Just the WARNING !! A custom OS can cause critical problems . . .
There is no phone model in download mode screen shown as an sgh-i747 or sgh-747m
Sorry, but I still don't understand the importance of warranty in an 8+ year old phone. Am I still missing something?
DavidWCS said:
Curious, I rebooted my phone into download mode ( holding volume down in the 3 finger format ).
There is nothing in the download mode screen that has the term "warranty bit". Just the WARNING !! A custom OS can cause critical problems . . .
There is no phone model in download mode screen shown as an sgh-i747 or sgh-747m
Sorry, but I still don't understand the importance of warranty in an 8+ year old phone. Am I still missing something?
Click to expand...
Click to collapse
You are not in download mode.
The warranty bit term is not about warranty, it is about whether the phone has a locked bootloader.
audit13 said:
You are not in download mode.
The warranty bit term is not about warranty, it is about whether the phone has a locked bootloader.
Click to expand...
Click to collapse
OK, I tried it again. This time I went one step further. Aha! Tiny print on upper left of screen. Have attached a sample photo showing what I see. And yes, I can see what you mean: " Warranty Bit: 1 " . Thank you, it makes sense now.
.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DavidWCS said:
OK, I tried it again. This time I went one step further. Aha! Tiny print on upper left of screen. Have attached a sample photo showing what I see. And yes, I can see what you mean: " Warranty Bit: 1 " . Thank you, it makes sense now.
.View attachment 4991379
Click to expand...
Click to collapse
The phone is not an AT&T S3, it is a T-Mobile s3 sgh-t999?
audit13 said:
The phone is not an AT&T S3, it is a T-Mobile s3 sgh-t999?
Click to expand...
Click to collapse
There are 2 i747 phones; d2Can & T999. In the past, the O/S's that I flashed, were designed for d2att. No difference in how they functioned, as far that I could notice.
DavidWCS said:
There are 2 i747 phones; d2Can & T999. In the past, the O/S's that I flashed, were designed for d2att. No difference in how they functioned, as far that I could notice.
Click to expand...
Click to collapse
Yes, there are two models of the i747: sgh-i747 (AT&T, d2att) and sgh-i747m (non-AT&T, d2can)
The T-Mobile s3 is sgh-t999 (d2tmo).
Related
Hello. I was using my phone and suddenly in the afternoon it started to restart automatically.. its never ending and it only stops when I take out the battery... When I put the battery again SAMSUNG Logo comes up followed by Samsung Galaxy W (CyanogenMod 9) screen then it restarts again and back to SAMSUNG logo... this process is never ending...
I also plugged in the charger and all i see is battery meter trying to calibrate but phone restarts and again i get to see the un-calibrated battery meter... this process also never ending...
I'm using ''CyanogenMod 9 Final Release (EOL)'' for past 3 weeks and there wasn't any problem... all this happened all of a sudden... I don't know what to do... So experts kindly help me out... Thanks a lot!!
hiitsme123 said:
Hello. I was using my phone and suddenly in the afternoon it started to restart automatically.. its never ending and it only stops when I take out the battery... When I put the battery again SAMSUNG Logo comes up followed by Samsung Galaxy W (CyanogenMod 9) screen then it restarts again and back to SAMSUNG logo... this process is never ending...
I also plugged in the charger and all i see is battery meter trying to calibrate but phone restarts and again i get to see the un-calibrated battery meter... this process also never ending...
I'm using ''CyanogenMod 9 Final Release (EOL)'' for past 3 weeks and there wasn't any problem... all this happened all of a sudden... I don't know what to do... So experts kindly help me out... Thanks a lot!!
Click to expand...
Click to collapse
I'm not an expert, but i would like to help Try to enter cwm recovery, reflash the rom and gapps. Hope it works
reply
thank you so much for your quick response... the problem is i cannot enter into CWM... i just googled and found the problem to be a SOft Brick/ Boot Loop issue... I hope someone has a solution for it...
geniusboy93 said:
I'm not an expert, but i would like to help Try to enter cwm recovery, reflash the rom and gapps. Hope it works
Click to expand...
Click to collapse
U have to flash stock rom via odin and start everything again
Sent from my GT-I8150 using xda premium
1) a bootloop won't stop you from getting into cwm.
2) cwm will usually stop a bootloop.
Something else is going on here. The symptoms you describe *could* indicate a damaged power button.
With a normally working W, if you press and hold the power button for long enough, the phone will switch off. If you continue to hold the power button, the phone will come back on....and then switch off again.....in a continual loop.....
It *could* be that the power button has failed by *maybe* being pressed into the phone (it can happen)...this would replicate the above scenario....
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
regarding odin
yeah im trying to flash everything again through odin... but the problem is when i go into the download mode the phone restarts... i dont know how to flash the file if it keeps on restarting like this... can u help me on that?
gameboy20131 said:
U have to flash stock rom via odin and start everything again
Sent from my GT-I8150 using xda premium
Click to expand...
Click to collapse
regarding power button
i dont think so it is because of the power button...
you see the exact problem which i face on this video... http://www.youtube.com/watch?v=iWg0LifdXlQ
the sad thing is even the uploader hasnt found a solution yet...
let me know if you know anything... as i dont want to buy a new phone
keithross39 said:
1) a bootloop won't stop you from getting into cwm.
2) cwm will usually stop a bootloop.
Something else is going on here. The symptoms you describe *could* indicate a damaged power button.
With a normally working W, if you press and hold the power button for long enough, the phone will switch off. If you continue to hold the power button, the phone will come back on....and then switch off again.....in a continual loop.....
It *could* be that the power button has failed by *maybe* being pressed into the phone (it can happen)...this would replicate the above scenario....
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Click to expand...
Click to collapse
i had this problem recently , i did a cmw sd phone partition and kinda bricked my phone , samsung logo restarts rapidly
so at the time u can do 2 things
flash the galaxy via odin , if that didn't work then there is no other ways to fix it
or go to samsung and play dum cuz i went to samsung and replaced the motherboard under warranty , like a fresh phone!
Cheers..
Ok.....so watched that video....in his case, it ain't software related.....if it was, the phone would restart at the same point every time. You notice that the phone would restart after the galaxy w logo screen but when he started hitting the phone it fully booted. That's defo hardware related. I'm not suggesting you mistreat your phone the way he did, but if you did, I bet you'd notice a certain lack of regularity as to where the boot process fails.
My money's still on hardware as the cause of your phones problem.....
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
regarding odin
can you tell me how you fixed it using odin? because when i put my phone into download mode, the phone restart keeps continuing... all the youtube tutorials and posts say that you got to start off with download mode and then proceed... i can go to download mode for just like 5 seconds and my mobile restarts again....
help me!!
redshift9 said:
i had this problem recently , i did a cmw sd phone partition and kinda bricked my phone , samsung logo restarts rapidly
so at the time u can do 2 things
flash the galaxy via odin , if that didn't work then there is no other ways to fix it
or go to samsung and play dum cuz i went to samsung and replaced the motherboard under warranty , like a fresh phone!
Cheers..
Click to expand...
Click to collapse
regarding rebooting
it is definitely restarting at the same time for me... i just pasted the link just get an idea of it... when i see SAMSUNG logo and SAMSUNG Samsung Galaxy W screen it restarts at that point... as shown in the video i tried doing that and the phone proceeded to load till i stopped hitting it... but once it restarted it went back to the same rebooting sequence...
keithross39 said:
Ok.....so watched that video....in his case, it ain't software related.....if it was, the phone would restart at the same point every time. You notice that the phone would restart after the galaxy w logo screen but when he started hitting the phone it fully booted. That's defo hardware related. I'm not suggesting you mistreat your phone the way he did, but if you did, I bet you'd notice a certain lack of regularity as to where the boot process fails.
My money's still on hardware as the cause of your phones problem.....
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Click to expand...
Click to collapse
Ok...going back to OS basics to try to explain this.....
As I'm sure you know, an operating system will load up files in a specific and pre defined order. The ONLY thing that will stop this process is an interruption of the power or a corrupted file that the OS is trying to load. The phone in the video is NOT suffering from a bootloop due to a corrupted file......hitting the phone will not suddenly make that file ok and allow the phone to fully boot. If there was a corrupted file, the boot process would fail at EXACTLY the SAME point EVERY time.....regardless of what was done to the phone.
You say you've managed to reproduce the results in the video and get your phone to boot past the startup screen?.......that being the case, it's NOT software related....simply because the boot process doesn't fail at the same point and gets further in.
You say you can't access recovery or download mode because the phone restarts......this is another indication that the OS has nothing to do with it as during these tasks, the OS isn't even being used.
EVERYTHING I've seen and read here is telling me that it's a hardware issue....specifically the power button......wouldn't hurt to get it checked
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
regarding rebooting
thank you for your reply... now it makes sense...
and what do you mean by get it checked? my phone is rooted and its using Cyanogen Mod 9 custom rom and its more than a year old (Out of Warranty period) So if I contact Samsung service center will they help me out? I mean with all the rooted stuff?
keithross39 said:
Ok...going back to OS basics to try to explain this.....
As I'm sure you know, an operating system will load up files in a specific and pre defined order. The ONLY thing that will stop this process is an interruption of the power or a corrupted file that the OS is trying to load. The phone in the video is NOT suffering from a bootloop due to a corrupted file......hitting the phone will not suddenly make that file ok and allow the phone to fully boot. If there was a corrupted file, the boot process would fail at EXACTLY the SAME point EVERY time.....regardless of what was done to the phone.
You say you've managed to reproduce the results in the video and get your phone to boot past the startup screen?.......that being the case, it's NOT software related....simply because the boot process doesn't fail at the same point and gets further in.
You say you can't access recovery or download mode because the phone restarts......this is another indication that the OS has nothing to do with it as during these tasks, the OS isn't even being used.
EVERYTHING I've seen and read here is telling me that it's a hardware issue....specifically the power button......wouldn't hurt to get it checked
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Click to expand...
Click to collapse
If the phone is out of warranty, it shouldn't matter that you've rooted and gone custom as they'll charge you anyway....just got to tell them that you want to stay custom or they're likely to return you to stock and unroot the phone (and charge you for that too).......
You could always try an unauthorized repair shop and see what they say.....
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Just done a little research.....
It turns out that the power button is soldered directly to the mainboard.
See image below....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So unless the repairer is good at soldering, then replacing the mainboard (and the custom OS) is a very real (expensive) possibility......
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Power Button
Thank you for that quick search... i dont know what to do... i badly wish the mobile is stable in download mode so that i can flash the rom into it
keithross39 said:
Just done a little research.....
It turns out that the power button is soldered directly to the mainboard.
See image below....
View attachment 2132195
So unless the repairer is good at soldering, then replacing the mainboard (and the custom OS) is a very real (expensive) possibility......
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Click to expand...
Click to collapse
regarding odin
Just one more thing...
1.Can you tell me how to approach this problem if it is totally related to software? I mean like there is a mobile phone which is stuck with boot-loop and I want the mobile to snap out of it?
2. Kind of a general question... if the phone restarts even in download mode how to use ODIN? Because then the process might fail... any other way to flash?
keithross39 said:
Just done a little research.....
It turns out that the power button is soldered directly to the mainboard.
See image below....
View attachment 2132195
So unless the repairer is good at soldering, then replacing the mainboard (and the custom OS) is a very real (expensive) possibility......
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Click to expand...
Click to collapse
To answer both of your questions together....if it is software related and odin can't be used because download mode can't be relied on.....jtagging is the only option.....
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
jtagging
is there any forum which gives info about the jtag? because i couldnt find much info about it...
P.S. I just want to make sure to try out all options before taking it to service center... thanks
keithross39 said:
To answer both of your questions together....if it is software related and odin can't be used because download mode can't be relied on.....jtagging is the only option.....
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Click to expand...
Click to collapse
In my opinion, I don't think jtagging will help in this case. I'm 99.999% certain that it's hardware related. Even if you did jtag, I still reckon you will have a phone that continually restarts. All you'd be doing is replacing one functioning OS with another. Jtag is primarily used for a phone that will not boot at all......
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Issue
1. Phone won’t boot beyond the Samsung Logo.
2. It won’t boot into recovery (download mode works).
3. Can flash rom using Odin but phone still won't boot.
Type of Phone
Type: AT&T Samsung Galaxy Note 2
Model: i317
Ownership: Bought in Nov 2012 brand new. Warranty is up but it is insured through AT&T.
History: Rooted and then un-rooted and returned to stock in January 2014.
Actions leading up to Issue
Updated to Samsung’s newest firmware Android 4.3 but didn’t like it. I rooted my phone and tried a custom rom but wasn’t happy. Un-rooted by flashing original stock rom via Odin 3.07. Worked great and I was back in business. But then the phone went through an update and never booted back up.
Detail
I’ve rooted all my other phones but never felt the need to root this one until I updated to Samsung’s new Android 4.3. I wasn’t happy with the decreased battery life and poor performance. So I used the method at http://forum.xda-developers.com/showthread.php?t=2004650 to root my phone using “root66_ATT_I317UCALJ2.tar.md5” with Odin 3.07 and it worked. I then tried a custom Cyanogen Mod rom but it still left something to be desired.
After more research I flashed the original stock rom “KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user_low_ship.tar.md5” via Odin 3.07 and my phone worked beautifully, at least for a day. Then I started getting the AT&T update window for Android 4.3 and the only way to get rid of it was to pull my battery. It was happening so much that I couldn’t even make a phone call. Out of pure frustration I decided to accept the update.
After the update installed it rebooted and never made it past the Samsung logo. So I figured I would just go into recovery and perform a factory reset as well as wipe the cache. The problem here is that it won’t boot into recovery. Only download mode works. I’m also seeing a red LED which I’ve read is a sign of SDS.
I’ve tried re-flashing the original stock rom again. Every time I do I get the green “Pass” display but my phone still won’t boot. The binary count is now at 21 since I’ve tried flashing so many times. I’ve been working on this and researching for 3 weeks. I’ve never had an issue that I couldn’t resolve when it comes to any of my past phones but this is beyond my skill or understanding. I also tried Samsung keys but it says my device is not supported.
Short of digging a hole in my back yard and burying it, is there anything I can do to fix this?
(Note) My wife has the same phone and also didn’t like the update so I flashed the same original stock rom to her phone via Odin and it has been working just fine. Only difference is I never rooted hers. I should have gone that route with mine.
Have you tried flashing, via Odin, just a custom recovery?
If that works, you may be able to follow this guide, starting at post #2.
http://forum.xda-developers.com/showthread.php?t=2618447
If that doesn't work, it is possible you have an emmc issue.... Your symptoms are similar to what others have reported here recently. You might be able to get a repair covered if you can get them to look past the custom counter ... You are running stock firmware... Maybe kies tripped the counter... Stranger things have happened...
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Zen Arcade said:
Have you tried flashing, via Odin, just a custom recovery?
If that works, you may be able to follow this guide, starting at post #2.
http://forum.xda-developers.com/showthread.php?t=2618447
If that doesn't work, it is possible you have an emmc issue.... Your symptoms are similar to what others have reported here recently. You might be able to get a repair covered if you can get them to look past the custom counter ... You are running stock firmware... Maybe kies tripped the counter... Stranger things have happened...
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks I'll give it a try. I had thought about it but was afraid to mess things up even more. Is there one that you would recommend?
josh3josh3 said:
Thanks I'll give it a try. I had thought about it but was afraid to mess things up even more. Is there one that you would recommend?
Click to expand...
Click to collapse
Here's the link to TWRP (you want the Odin link toward the bottom):
http://teamw.in/project/twrp2/124
Here's the direct link to the latest philz cwm (you want the md5 file):
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/t0lteatt
I prefer philz, but you will likely need TWRP to follow the dicksteele guide. You should also track down a CWM flashable recovery package for MH3 recovery to flash back should you need to return the phone for repairs. You can get this by following the i317 link in my sig.
If flashing this in Odin doesn't work that would tend to support the emmc fail scenario. (i.e. you flash it, Odin behaves as if it flashed ok, you power off, attempt to boot recovery with home-VolUp-power and it still doesn't boot). If it does boot recovery, you can try the guide as I mentioned before. Good luck!
Zen Arcade said:
Have you tried flashing, via Odin, just a custom recovery?
If that works, you may be able to follow this guide, starting at post #2.
http://forum.xda-developers.com/showthread.php?t=2618447
If that doesn't work, it is possible you have an emmc issue.... Your symptoms are similar to what others have reported here recently. You might be able to get a repair covered if you can get them to look past the custom counter ... You are running stock firmware... Maybe kies tripped the counter... Stranger things have happened...
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried each of those just now and they both flashed fine however there is no change. I guess before I break out the shovel I'll try to see if AT&T will fix it since I do pay for the insurance. Thanks for the help that was good stuff. I wish it could have worked.
josh3josh3 said:
I tried each of those just now and they both flashed fine however there is no change. I guess before I break out the shovel I'll try to see if AT&T will fix it since I do pay for the insurance. Thanks for the help that was good stuff. I wish it could have worked.
Click to expand...
Click to collapse
if you have nothing else to lose, can you try flashing the boot loader on this link
http://d-h.st/Krs from this thread
http://forum.xda-developers.com/showthread.php?t=2589891
then try one of the official odin package or this:http://d-h.st/DGZ
So, there appear to be many people who see this update as a bad joke. Like me.
I had a thread a couple days ago about how to kill the notification from att
Without root. Nothing can be done as far as ive heard/seen. Im a bit confused
About needing a battery pull to remove pp note, I have been just reboot and it
Goes away until next data use/net access. When my 8 hrs is up I turn data on
(Data off as 8hrs expires) and immediately get note and then I hit home- get
another 8 hrs. Im sorry to hear they wore you down with the note- im going to
fight and resist for the duration. And keep stock. Its a game now!
R, john
qkster said:
if you have nothing else to lose, can you try flashing the boot loader on this link
http://d-h.st/Krs from this thread
http://forum.xda-developers.com/showthread.php?t=2589891
then try one of the official odin package or this:http://d-h.st/DGZ
Click to expand...
Click to collapse
Tried it and it failed to flash. Now I have the yellow triangle. At least its something different. Still no good though. Reflashed stock rom and I'm back to the Samsung logo. Was worth a shot. Thanks.
Try param and tz package mentioned in post #3 here.... Might be something
http://forum.xda-developers.com/showthread.php?t=2596256
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
josh3josh3 said:
Tried it and it failed to flash. Now I have the yellow triangle. At least its something different. Still no good though. Reflashed stock rom and I'm back to the Samsung logo. Was worth a shot. Thanks.
Click to expand...
Click to collapse
You flashed LJ2 Stock ROM from ODIN?
And you are back to the Samsung Logo that flashing/pulsing blue???
If so .....
Pull the battery and let the phone sit for a few seconds, pop the battery in and boot into stock recovery (HOLD VOL UP+HOME+POWER) and do a FACTORY RESET then reboot.
I had to do the same thing an hour ago....
dicksteele said:
You flashed LJ2 Stock ROM from ODIN?
And you are back to the Samsung Logo that flashing/pulsing blue???
If so .....
Pull the battery and let the phone sit for a few seconds, pop the battery in and boot into stock recovery (HOLD VOL UP+HOME+POWER) and do a FACTORY RESET then reboot.
I had to do the same thing an hour ago....
Click to expand...
Click to collapse
Have tried that many times with no luck. Wish it were that simple.
josh3josh3 said:
Have tried that many times with no luck. Wish it were that simple.
Click to expand...
Click to collapse
Have you tried this yet ?
http://forum.xda-developers.com/showpost.php?p=49826416&postcount=9
Zen Arcade said:
Try param and tz package mentioned in post #3 here.... Might be something
http://forum.xda-developers.com/showthread.php?t=2596256
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I can't believed it worked. Flashed this and suddenly I have recovery. Then I re-flashed the original stock rom, did a reset and wiped the cache and I'm back up and running. Brilliant I say. Genius! Thank you for the great post and thanks everyone for your help. Seems like there should be a like button or something so that you get credit but I don't see one. This was my first time ever posting on any forum so I'm a little ignorant.
josh3josh3 said:
I can't believed it worked. Flashed this and suddenly I have recovery. Then I re-flashed the original stock rom, did a reset and wiped the cache and I'm back up and running. Brilliant I say. Genius! Thank you for the great post and thanks everyone for your help. Seems like there should be a like button or something so that you get credit but I don't see one. This was my first time ever posting on any forum so I'm a little ignorant.
Click to expand...
Click to collapse
That would be the Thanks button by the Quote...
OUTSTANDING !!!
Glad you're back among the living.
This will get you back to 4.1.2
http://forum.xda-developers.com/showpost.php?p=49616718&postcount=2
EDIT:
I just did this and it worked perfectly .....
I'm actually doing that step right now also. I flashed back to stock testing the ATT update server.
EDIT #2:
At this step when the phone reboots the script will run. When it completes you want to boot to system. The next prompt will be do you want to install ROOT. If you do the swipe it will install ROOT, there is a DO NOT INSTALL button on the middle of the screen. Just a heads up, don't know if you are turning your phone back in or not now.
- Second step is:
You will need to download TWRP 2.6.3.1 and flash it in ODIN.
http://goo.im/devs/OpenRecovery/t0lt...lteatt.img.tar
This is necessary for an openrecovery script to run that is stored in the /cache directory from the update.
- Put your Note 2 in Download Mode.
- Open ODIN, put openrecovery-twrp-2.6.3.1-t0lteatt.img.tar in PDA slot. Click Start and let the phone reset.
- Your phone will reboot in TWRP. If not, pull battery and enter recovery mode boot into TWRP recovery (HOLD VOL UP+HOME+POWER). The script will run by itself.
sgh-i317 EFS seems like its gone
could anybody help me out with my note 2. ive tried just about everything i can think of. im getting pretty desperate. i can get everything to work fine (recovery,download mode,) but something is keeping it from booting up to the main screen, it will just hand at the boot animation, or the att logo. in twrp it tells me failed to mount efs. ive looked around in the file folders and its like it got wiped out? im not sure how though. could that be why its not booting up?
any ideas??
I searched but seems like everyone else has a slightly different situation than I do and I don't want to screw my phone up any more.
I picked up a Galaxy S5 and wanted to give my Galaxy S3 to my mom.
(This next process happened almost a month ago, so I forgot many of the useful details, I'm really sorry about that)
I don't remember which ROM I was running, I'm fairly certain it was CM10 that hasn't been updated in almost a year. I ended up rebooting and flashing a stock rom that I had backed up on my computer. I flashed it and I got a weird message. The phone wouldn't boot to the ROM and kept going to the home screen. I tried a different stock ROM that I got online, got the same issue, so I tried another source's stock ROM. I got a weird error, phone shut down, and wouldn't power back up.
It would vibrate once when I held the power button, but it didn't do ANYTHING else. I tried doing the power+volume down trick, vibrated twice, did nothing more than that. I got fed up, took the battery out and the memory card, and let it sit in a drawer.
At this moment the only thing the phone does is a short vibration when I do either the power button or power button + volume down.
Today I decided to try to recover it and saw something about a USB Jig I can buy on eBay that may help.
Is this something that may work or is my phone permanently bricked? If the Jig does work, where should I get the stock ROM for this phone, and if it matters, how do I know which stock ROM to install?
It's an AT&T Galaxy S3 16gb model.
here is a thread for stock ROMs.
do you know your bootloader and baseband version?
http://forum.xda-developers.com/showthread.php?t=2939781
"all i can really do , is stay out of my own way and let the will of heaven be done"
mrrocketdog said:
here is a thread for stock ROMs.
do you know your bootloader and baseband version?
http://forum.xda-developers.com/showthread.php?t=2939781
"all i can really do , is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse
I don't know any of that.
Also what's the difference between MJ2, LK3, LG1, and LEM?
Sounds like you flashed an incorrect ROM and/or bootloader onto your phone.
The bootloader is important because if you have the mjb and newer bootloader, flashing an older bootloader will brick the phone.
audit13 said:
Sounds like you flashed an incorrect ROM and/or bootloader onto your phone.
The bootloader is important because if you have the mjb and newer bootloader, flashing an older bootloader will brick the phone.
Click to expand...
Click to collapse
I can see me flashing the wrong rom, but is the bootloader attached to the rom package?
If the bootloader is ****ed, will the jig work for me or am I out of luck?
Where did you get the last ROM you flashed? Provide a link if you can.
Have a look at the debrick thread as it may be helpful if your phone can't get into download mode. The jig may or may not help but it's good to have one for Samsung phones.
audit13 said:
Where did you get the last ROM you flashed? Provide a link if you can.
Have a look at the debrick thread as it may be helpful if your phone can't get into download mode. The jig may or may not help but it's good to have one for Samsung phones.
Click to expand...
Click to collapse
I honestly have no clue, the only rom I could find in my downloads folder on my computer that I can't identify as a custom rom is "pac_d2lte", and I remember the d2lte part throwing me off even though thats what a few sites said to download.
The Jig worked, btw, I'm at the download screen with the phone plugged into my pc, should my PC be showing it as an external device? Cause it doesn't show it in "My Computer".
Can I just take an SGH-I747 rom off this page and flash it with ODIN?
http://forum.xda-developers.com/showthread.php?p=33570269#post33570269
I would not flash any stock rom until you know the bootloader version on your phone.
Since you can get into download mode, flash philz touch recovery for the d2lte and flash a custom rom such as cm11 onto your phone to at least get it booted so you can confirm the bootloader and baseband.
netchemica said:
Can I just take an SGH-I747 rom off this page and flash it with ODIN?
http://forum.xda-developers.com/showthread.php?p=33570269#post33570269
Click to expand...
Click to collapse
I actually just did just that. It seemed to restore my phone to working condition. It seemed a little buggy during set up, but I don't know if it's because I was running it without a sim card or not. So far it looks like it's running just fine.
In other words, this is what I did (in case someone has the same problem and stumbles across this thread):
Purchased a Samsung Galaxy Jig from Amazon
Downloaded one of the LK3 ROMs from this thread
Downloaded Odin 307
Connected the Jig to my phone to allow it to boot to download mode
Once in download mode I unplugged the Jig and plugged the phone into my PC
I launched Odin and it found my phone right off the bat.
With the settings "Auto Reboot", "F. Reset Time", and "PDA" checked, I clicked on PDA and selected the ROM I just downloaded.
I clicked start, Odin did its magic, and my phone rebooted to the setup screen
audit13 said:
I would not flash any stock rom until you know the bootloader version on your phone.
Since you can get into download mode, flash philz touch recovery for the d2lte and flash a custom rom such as cm11 onto your phone to at least get it booted so you can confirm the bootloader and baseband.
Click to expand...
Click to collapse
I didn't see your post before I flashed. I took a gamble and it seems to have worked.
Warm greetings to you all friends,
So far one week ago i bought a Samsung galaxy S3 i9300 SGH-1747 (AT&T Vietnam) from my big friend. As you know on smartphones you need to reset if you are a new user. I made a factory data reset by pressing all the buttons procedure. I wiped the phone and it rebooted. But since i reseted the phone, It started switching off its self after like every 4 minutes it sets off. It showed me this message “The device has detected an application attempting to perform actions that are not permitted, Reboot now or reboot later" even if press restart nothing changes it brings it back again. So my friend requested me that he can fix that by changing the rom.
After he has erased the phone, and connects it to odin if failed to upgrade, immediately after pressing start it fails. He has downloaded almost the roms of it type but again they fail in odin software. It cannot connect to kies software. Now it just blinks "Samsung" logo on the screen after a second and it goes off. Please kindly advise me, what can we do? I love that phone because there very expensive here. Help me please what can we do?
XDA Visitor said:
Warm greetings to you all friends,
So far one week ago i bought a Samsung galaxy S3 i9300 SGH-1747 (AT&T Vietnam) from my big friend. As you know on smartphones you need to reset if you are a new user. I made a factory data reset by pressing all the buttons procedure. I wiped the phone and it rebooted. But since i reseted the phone, It started switching off its self after like every 4 minutes it sets off. It showed me this message “The device has detected an application attempting to perform actions that are not permitted, Reboot now or reboot later" even if press restart nothing changes it brings it back again. So my friend requested me that he can fix that by changing the rom.
After he has erased the phone, and connects it to odin if failed to upgrade, immediately after pressing start it fails. He has downloaded almost the roms of it type but again they fail in odin software. It cannot connect to kies software. Now it just blinks "Samsung" logo on the screen after a second and it goes off. Please kindly advise me, what can we do? I love that phone because there very expensive here. Help me please what can we do?
Click to expand...
Click to collapse
Hello, and thank you for using XDA Assist!
You may need a download mode jig at this point.
At any rate, I am connecting this thread to the forum your device experts can be found:
> AT&T, Rogers, Bell, Telus Samsung Galaxy S III > AT&T Galaxy S III Q&A, Help & Troubleshooting
Please note, in order to respond to replies, you will need to register for an XDA account.
Hope this helps, and good luck!
You state
Samsung galaxy S3 i9300 SGH-1747 (AT&T Vietnam)
Click to expand...
Click to collapse
The i9300 and the i747 are different phones and any ROM or custom recovery suitable for one could hardbrick the other.
Could you power off the device, remove the back cover, and then check under the battery to verify the model?
I checked it and the model is that one.
Tonnie_Travie said:
I checked it and the model is that one.
Click to expand...
Click to collapse
Which one? The i9300 or the i747?
dawgdoc said:
Which one? The i9300 or the i747?
Click to expand...
Click to collapse
Yaeeeeh its i747
Tonnie_Travie said:
Yaeeeeh its i747
Click to expand...
Click to collapse
The i747 makes things a bit more limited in things we could do to correct this. The last full official ROM released by AT&T was the 4.1.1 release. If your phone had a newer bootloader and modem on it than that for 4.1.1 or the 4.1.2 partial release, then the 4.1.1 release is not safe for you to use.
Do you know, or can you get, information about what it was your friend tried to flash?
Can he tell you what bootloader and modem were on your phone before he flashed anything?
Boot into download mode (Odin mode) and report back with all of the small text at the top of the screen. If there is a line about "warranty bit" that would indicate you to be on at least the 4.3 bootloader.
I expect the solution will using a debrick image on an external sdcard, booting from it,, swapping cards, determining the correct bootloader and modem, flashing them, flashing a custom recovery, and finally flashing a rom. Here is a thread about using a debrick image, it has links to where he obtained his info.
Would someone mind helping me out, I cant use my phone any more. The last thing I did was install Emotion OS and then I installed the Emotion Kernel, upon reboot the phone was stuck on the emotion boot screen after restarting the phone Im not sure how it happened however the phone went from TWRP to some recovery that looks like the lineageos logo, I cant install any updates from this recovery and my phone via USB in download mode or ADB is not detected by any computer I have tried 3 computers in my house. I have never seen this recovery screen and I do not know what to do. I downloaded a stock MM firmware and converted it to a zip file from a tutorial on here however I keep getting an error message from this recovery. I really need my phone back up and running Im not sure what the heck happened.
Continued from other posts
Quote:
Originally Posted by shadeau
Do you have any options in recovery? Even if you could perform a "factory reset" with lineage OS you'd at least be able to enable ADB and reinstall TWRP. Also, when you say that the phone isn't recognized by the computer does that mean ADB, ODIN, and your OS don't recognize the phone?
So I do have options in this Lineage Recover but I cant get anything to work, Here are my options Reboot System Now, Apply Update, Factory Reset, Advanced. I have already tried factory reset however I may have deleted the OS all together with the Wipe Data Option. When I reboot the phone it stays on the the Samsung Galaxy Note 4 Screen with the little padlock that shows my bootloader is unlocked. I was messing around with flashing betwen several roms, I went from CM 14.1 to Lineage to Emotion OS, I then flashed the emotion kernel. If I select Apply update it gives me these several options, Apply from ADB choose from emulated (no typo) choose from sdcard1. I have tried to sideload via adb shell and my pc ( have tried multiple computers) does not detect the device. I even went to the extent of reinstalling windows and all Samsung USB and ADB drivers. Selecting choose from sdcard1 I can see the various zip files on my sd card however when it goes to install any roms it fails and just says error. There is a error log however it will not let me view these. My phone before this stopped connecting to any pc's I could plug the phone in via usb and it would charge but I would not get any notifications from windows! I will seriously send money to who ever can hlep me out I do not want to shell out for a new phone. Placing the phone in download mode still works however odin will not detect the phone either lol what the heck is going on here. I do have a micro sd card reader for the mc so i can place files on the phones card but I dont know what kind of file this recovery is looking for. I do not know how this recovery even got on here as I have been using TWRP from the very beginning. Please help me
I have never seen this recovery it has the lineage os logo and just says RECOVERY. I wish I could take a picture of the screen.
I have also tried renaming files on my sd card as update.zip and this does not help. It comes back with an error every time.
ziggsta2 said:
I have also tried renaming files on my sd card as update.zip and this does not help. It comes back with an error every time.
Click to expand...
Click to collapse
Are you using the Samsung OEM USB cord?
quinciebee said:
Are you using the Samsung OEM USB cord?
Click to expand...
Click to collapse
good questions will try another usb cable all I have is 1 for right now
quinciebee said:
Are you using the Samsung OEM USB cord?
Click to expand...
Click to collapse
Do you know what recovery this is? It has the lineage symbol! I cant find a picture of it any where if someone knew what recovery it was maybe then I could research info from the name
ziggsta2 said:
Do you know what recovery this is? It has the lineage symbol! I cant find a picture of it any where if someone knew what recovery it was maybe then I could research info from the name
Click to expand...
Click to collapse
It sounds likes it's the default factory recovery, you probably lost TWRP when you flashed the rom. When Odin recognizes your phone again, just Odin TWRP in there through download mode and you should be good to go.
quinciebee said:
It sounds likes it's the default factory recovery, you probably lost TWRP when you flashed the rom. When Odin recognizes your phone again, just Odin TWRP in there through download mode and you should be good to go.
Click to expand...
Click to collapse
When I plug my phone into a USB port I get a grey battery icon however it doesn't appear that its doing anything, is it possible I have a bad usb port on my phone? Odin wont recognize it, I have yet to find a single computer to see my phone, and I have now tried multiple USB cables.
ziggsta2 said:
When I plug my phone into a USB port I get a grey battery icon however it doesn't appear that its doing anything, is it possible I have a bad usb port on my phone? Odin wont recognize it, I have yet to find a single computer to see my phone, and I have now tried multiple USB cables.
Click to expand...
Click to collapse
Try unplugging your phone completely, pull the battery, boot into download mode, then plug it into your computer using the Samsung USB cord.
quinciebee said:
Try unplugging your phone completely, pull the battery, boot into download mode, then plug it into your computer using the Samsung USB cord.
Click to expand...
Click to collapse
I wish that was the fix, I have tried everything at this point, for the life of me i cannot get any pc to recognize this phone. If I could get odin to detect the phone I would be all set
ziggsta2 said:
I wish that was the fix, I have tried everything at this point, for the life of me i cannot get any pc to recognize this phone. If I could get odin to detect the phone I would be all set
Click to expand...
Click to collapse
CHECK THIS OUT People are having the same issues
https://forum.xda-developers.com/android/help/phone-stuck-bootloop-t3510266
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ziggsta2 said:
Click to expand...
Click to collapse
In the advanced menu is there an option to "mount system" or something? Also see if there's a setting in there for chmod
I actually ordered a new note 4 I believe my device is dead I will have to charge it as when I try to boot into recovery the words no command flash very quickly on the bottom of the screen, I do know I saw mount system I remember trying it and it didn't do anything but I will charge it tonight and try it. I have read about the nexus 6p and how 7.1.1 has bricked alot of devices, do you think upgrading to Emotion Os 7.1 was the culprit?
ziggsta2 said:
I actually ordered a new note 4 I believe my device is dead I will have to charge it as when I try to boot into recovery the words no command flash very quickly on the bottom of the screen, I do know I saw mount system I remember trying it and it didn't do anything but I will charge it tonight and try it. I have read about the nexus 6p and how 7.1.1 has bricked alot of devices, do you think upgrading to Emotion Os 7.1 was the culprit?
Click to expand...
Click to collapse
I just tried EmotionOS over the weekend and had no issues so I'm not sure that's the culprit. I think you accidentally flashed something into the recovery partition that broke it. Another possibility is that the latest EmotionOS build is specifically designed for the custom TWRP that @hsbadr made. I used that to flash EmotionOS then returned to stock TWRP to flash a different ROM.
shadeau said:
I just tried EmotionOS over the weekend and had no issues so I'm not sure that's the culprit. I think you accidentally flashed something into the recovery partition that broke it. Another possibility is that the latest EmotionOS build is specifically designed for the custom TWRP that @hsbadr made. I used that to flash EmotionOS then returned to stock TWRP to flash a different ROM.
Click to expand...
Click to collapse
You know what you might be right I don't remember ever changing TWRP, what is weird is that I lost all usb connectivity too a point that could be due to a damaged usb port, too many unknowns at this point. It was a little embarrassing in the household when I had to admit that I bricked my phone. I was asked if I was going to mess with my new phone......I will have it rooted and unlocked TONIGHT lol
ziggsta2 said:
You know what you might be right I don't remember ever changing TWRP, what is weird is that I lost all usb connectivity too a point that could be due to a damaged usb port, too many unknowns at this point. It was a little embarrassing in the household when I had to admit that I bricked my phone. I was asked if I was going to mess with my new phone......I will have it rooted and unlocked TONIGHT lol
Click to expand...
Click to collapse
Well, good luck! Send me a PM if you have trouble finding the links to unlocking and rooting.
Ha I got there too man . pretty cool recovery wish I wouldn't have fixed it so fast might try duplicate your accident. OK its an easy fix just flash twrp in Odin for our device then boot back into twrp and do a complete wipe (might not be possible if u can't see sdcard if that is case wipe data system cache art/cache then install then wipe the internal after ROM flash . at this point I would factory reset and backup but hey that's me . anyway should be fine from here. BTW did you select the DL recovery option in dev options? I was wondering if that's how I got there the (lineage recovery) the first time. Lol your post made me want to check it out. Omg bud i almost forgot and this is crucial. Aosp ROMs like emotion take a long long time to boot the first time(damn near 15 mins) ! The last thing you want to do is mistake this for a bootloop
mojoswagger1980 said:
Ha I got there too man . pretty cool recovery wish I wouldn't have fixed it so fast might try duplicate your accident. OK its an easy fix just flash twrp in Odin for our device then boot back into twrp and do a complete wipe (might not be possible if u can't see sdcard if that is case wipe data system cache art/cache then install then wipe the internal after ROM flash . at this point I would factory reset and backup but hey that's me . anyway should be fine from here. BTW did you select the DL recovery option in dev options? I was wondering if that's how I got there the (lineage recovery) the first time. Lol your post made me want to check it out. Omg bud i almost forgot and this is crucial. Aosp ROMs like emotion take a long long time to boot the first time(damn near 15 mins) ! The last thing you want to do is mistake this for a bootloop
Click to expand...
Click to collapse
Ouch ! I kinda failed to take into account the very real possibility the ROM you wished to flash might not be on your device and you may have no means to get it there.....in which case flash twrp then you need (if you don't want relock bootloader) to flash a system only image . vague I know I'm thinking .....bottom line is whatever you flash cannot contain aboot image or you will relock boot loader. If on 6.0.1 boot loader there is a safeupgrade to the most recent firmware that won't relock if on 5.1.1 (bpa1 ) idk if there is one . I think there is . in fact I'm sure there is hsbrad made Odin flashable IMG for all Verizon note 4 firmware broth dev and retail . look under his profile on XDA should link you to it
ziggsta2 said:
Do you know what recovery this is? It has the lineage symbol! I cant find a picture of it any where if someone knew what recovery it was maybe then I could research info from the name
Click to expand...
Click to collapse
That is the lineage os recovery it comes in every build, you must have hit update recovery in the developer options of the settings menu. You just need to reflash twrp like you did when you unlocked your bootloader.
weard1212 said:
That is the lineage os recovery it comes in every build, you must have hit update recovery in the developer options of the settings menu. You just need to reflash twrp like you did when you unlocked your bootloader.
Click to expand...
Click to collapse
Yeah ty I went ahead and tried last night cause I was bored ....meh lack luster . oh and I did it intentionally and just restored recovery with flashify and I just realized this probably wasn't directed at me but yep lineage