Hey I have a problem here.I have a dev edition Note 4. I have been running EMSpoilt's first ROM ([Rom][N910VOYU1ANI1][4.4.4] Stock Root Deodex/Knox-Free Updated 11/24/2014) for about 2 weeks now. It was running great smooth as butter until now. I tried flashing his new [Rom][N910VVRU1ANJ5][4.4.4] Stock Root Odex/Knox-Free) but my phone wouldn't boot up, it wouldn't get past the first Samsung screen just keeps restarting. I made sure to follow step by step instructions. Wiped everything but my SD card. Tried it 2 more times and nothing. Tried to wipe cache and all that. Nothing helped. So I decided to restore back to my backed up ROM. Once restored it started to act weird. My finger print scanner doesn't work and I can't download anything another than apps from app store...the phone is very glitchy and almost unusable.. almost like it has a virus. It did get pretty hot when I was flashing the ROM I hope I didn't fry anything. I tried and tried to reset things but no luck. I don't have a backup of stock Dev ROM unfortunately...is there a way to reset back to stock(out of the box state)? I still have root and TWRP recovery works fine.
Anyone help please?
Sent from my SM-N910V using XDA Free mobile app
Sent from my SM-N910V using XDA Free mobile app
shpotik said:
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
If you want to get the NJ5 ROM up and running without issues I would suggest flashing the NJ5 stock restore tar file in Odin, then flash TWRP recovery in Odin. Once that is done boot into TWRP and flash SU, then flash the ROM. I was having the same issue yesterday and this fixed things for me.
+1 on what airmaxx23 has recommended. Caution: Make damn sure you ODIN the stock restore file intended for the DE, not the retail. If you just want to get back to a fully functional DE without the ROM then ODIN the stock restore file, ODIN TWRP and flash SUPERSU in recovery. You don't have to flash the ROM.
jpcalhoun said:
+1 on what airmaxx23 has recommended. Caution: Make damn sure you ODIN the stock restore file intended for the DE, not the retail. If you just want to get back to a fully functional DE without the ROM then ODIN the stock restore file, ODIN TWRP and flash SUPERSU in recovery. You don't have to flash the ROM.
Click to expand...
Click to collapse
Can you point me into direction of stock restore file? Thanks
Sent from my SM-N910V using XDA Free mobile app
shpotik said:
Can you point me into direction of stock restore file? Thanks
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
I linked all the files you need for the DE in my original response.
shpotik said:
Can you point me into direction of stock restore file? Thanks
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
Here you go: http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937. Make sure you go to post #2 and select the stock restore file for the DE.
I am having problems with mine, too
After getting into trouble yesterday with a phone that stuck in Verizon logo screen, I was able to restore from backup.
Then I started noticing weird things that I believe were working a day ago.
I cannot download any email attachments, cannot create folders on sdcard, cannot install xposed or even install Fora offline dictionary files I downloaded from PlayStore. I never flashed custom ROMs on my DE, just flashed TWRP and then rooted it. I am still running original SW N910VOYU1ANI1. Screenshots and photos are saved just fine (burst shots on sdcard and regular photos on extsdcard).
Any Ideas? I've tried to restore from pre-root backup, then restored my image that has root and some applications but cannot move from there.
inseek said:
After getting into trouble yesterday with a phone that stuck in Verizon logo screen, I was able to restore from backup.
Then I started noticing weird things that I believe were working a day ago.
I cannot download any email attachments, cannot create folders on sdcard, cannot install xposed or even install Fora offline dictionary files I downloaded from PlayStore. I never flashed custom ROMs on my DE, just flashed TWRP and then rooted it. I am still running original SW N910VOYU1ANI1. Screenshots and photos are saved just fine (burst shots on sdcard and regular photos on extsdcard).
Any Ideas? I've tried to restore from pre-root backup, then restored my image that has root and some applications but cannot move from there.
Click to expand...
Click to collapse
Here is what I would do if I were you:
1. Go into TWRP Recovery and do a complete wipe (system, data, cache, delvik). Do not select recovery.
2. While in TWRP do a factory reset
3. In TWRP, RESTORE the backup you mentioned.
4. While in TWRP clear cache and delvik again
5. Power off the phone and remove the battery
6. Replace the battery and boot
7. If the phone boots normally then power off the phone, boot into recovery and flash SuperSU (Do not try to restore any "image", just flash SuperSU.zip)
8. Reboot the phone
jpcalhoun said:
Here is what I would do if I were you:
1. Go into TWRP Recovery and do a complete wipe (system, data, cache, delvik). Do not select recovery.
2. While in TWRP do a factory reset
3. In TWRP, RESTORE the backup you mentioned.
4. While in TWRP clear cache and delvik again
5. Power off the phone and remove the battery
6. Replace the battery and boot
7. If the phone boots normally then power off the phone, boot into recovery and flash SuperSU (Do not try to restore any "image", just flash SuperSU.zip)
8. Reboot the phone
Click to expand...
Click to collapse
Although I did it already almost the same way multiple times since yesterday, I'll try it again.
How do I do #2 in your list from TWRP?
Thanks.
inseek said:
Although I did it already almost the same way multiple times since yesterday, I'll try it again.
How do I do #2 in your list from TWRP?
Thanks.
Click to expand...
Click to collapse
Go to "Wipe" then "Format Data" then type "yes" and hit "go". This will completely remove all data. Under "Advanced Wipe" check "dalvik", "system", "data", and "cache" and wipe those as well.
If that doesn't work you're going to have to start fresh.
inseek said:
Although I did it already almost the same way multiple times since yesterday, I'll try it again.
How do I do #2 in your list from TWRP?
Thanks.
Click to expand...
Click to collapse
When you're in TWRP and select Wipe, there will appear a "swipe bar" that when swiped will perform a Factory Reset. It is the first screen you see when you select Wipe on the home screen. Do the Factory Reset and then clear cache, delvik, system and data. You can do the Factory Reset before clearing cache etc or after clearing cache etc. It really doesn't make a difference in what order you do the Factory Reset, just do it.
If this process doesn't get you back to normal then another option is to flash the stock restore file for NJ5 availble in the Android Development Section. But, lets do the process I've outlined first.
jpcalhoun said:
Here is what I would do if I were you:
1. Go into TWRP Recovery and do a complete wipe (system, data, cache, delvik). Do not select recovery.
2. While in TWRP do a factory reset
3. In TWRP, RESTORE the backup you mentioned.
4. While in TWRP clear cache and delvik again
5. Power off the phone and remove the battery
6. Replace the battery and boot
7. If the phone boots normally then power off the phone, boot into recovery and flash SuperSU (Do not try to restore any "image", just flash SuperSU.zip)
8. Reboot the phone
Click to expand...
Click to collapse
I did everything up to the #7, then powered the phone. I am getting all bunch of errors like "com.sec.phone has stopped" and other I don't remember. It shouldn't be this way, right?
Then I powered the phone off and on again, this time I got the setup wizard without error messages and flashed SU and then installed Xposed. So far, so good. Will install couple apps to see how it goes.
Thanks, jpcalhoun!
airmaxx23 said:
If you want to get the NJ5 ROM up and running without issues I would suggest flashing the NJ5 stock restore tar file in Odin, then flash TWRP recovery in Odin. Once that is done boot into TWRP and flash SU, then flash the ROM. I was having the same issue yesterday and this fixed things for me.
Click to expand...
Click to collapse
do i have to extract the file with 7zip ?
inseek said:
I did everything up to the #7, then powered the phone. I am getting all bunch of errors like "com.sec.phone has stopped" and other I don't remember. It shouldn't be this way, right?
Then I powered the phone off and on again, this time I got the setup wizard without error messages and flashed SU and then installed Xposed. So far, so good. Will install couple apps to see how it goes.
Thanks, jpcalhoun!
Click to expand...
Click to collapse
Glad you got it working. I'd have to see the error messages to try, I emphasize try, to determine what might be causing them. Often after flashing or using ODIN to install software you'll get an error message until the system has been rebooted. You should probably power off you phone, again, pull the battery, replace the battery and reboot to see if you continue to get error messages. You shouldn't be getting error messages during boot unless you have installed something that has turned a service off or has altered a service that the system is asking for (that's not technically well stated, but I think you get the point). Exposed Framework is great and enables users to customize many things in Android. But, not all the modules work the same on every device, and in fact some modules will not work at all on the Note 4. If you're trying to run a module that does not work as advertised then you should uninstall that module or not select that particular customization. A misbehaving module can cause problems that manifest themselves in funny ways.
shpotik said:
do i have to extract the file with 7zip ?
Click to expand...
Click to collapse
Yes, extract it with 7zip.
Related
So I got my S3 a few days ago and decided to root so I could run a stock Android experience (not that TouchWiz is bad) Anyway I followed the instructions in the no flash counter root sticky and it seemed to work when it was going through the steps and such. Anyway the phone rebooted after I used Odin and now it comes up with a prompt telling me that android.process.acore has crashed and I press OK and it comes back every five seconds or so. I'm not sure what the deal is, but I attempted to factory reset using Odin and a file I found on XDA also and the same thing is happening.
I need some direction as to where I went wrong and what I can do to fix this, because to be honest right now my phone is unusable with this prompt showing up every five seconds when I try to do something. Any help or suggestions are appreciated!
EDIT: So I was able to fix the issue by using the built in factory restore setting, but I'm not sure where the root went wrong still...
Make a nandroid, factory reset, wipe cache, format system and flash a new to. To see if the problem is still there
Sent from my SGH-I747 using xda app-developers app
liltitiz said:
Make a nandroid, factory reset, wipe cache, format system and flash a new to. To see if the problem is still there
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Well I guess I should say I never achieved root as well. I followed the instructions, but for whatever reason I couldn't flash CWM onto the phone to flash a ROM or anything.
Had the same issue. Just rebooting into recovery and clearing cache and factory resetting did the trick for me. To get CWM easiest way is to download ROM Manager and let it install for you
Can also use Goo Manager. Download goo manager from play store. Once downloaded open. Hit your menu button and select Install OpenRecoveryScript
Just to be clear
kenney001 said:
Had the same issue. Just rebooting into recovery and clearing cache and factory resetting did the trick for me. To get CWM easiest way is to download ROM Manager and let it install for you
Click to expand...
Click to collapse
ROM Manager = clockworkmod recovery
jasvncnt1 said:
Can also use Goo Manager. Download goo manager from play store. Once downloaded open. Hit your menu button and select Install OpenRecoveryScript
Click to expand...
Click to collapse
Goo manager = twrp recovery
You need to boot into recovery and do a factory reset. Most likely the phone go have has a new modem version. When you flash the old g1 modem root over it it gets funky until you factory reset then you'll be golden.
Sent from my SAMSUNG-SGH-I747 using xda premium
Okay, I searched before posting. Here is my steps.
I was on SKYNOTE 8.2 and wanted to go back to stock and see what At&t's update was about.
Once back to stock, I rooted my phone and have been on this setup for about 2 weeks.
I was in the original thread and saw the new 4.2.2 Collective AoCP / CM10.1 ROM.
I wanted to try it out.
Using TWRP's latest, followed all instructions and when rebooting it still has stock root ROM.
What am I doing wrong?
I thought it was TWRP so I went to an earlier ver, still no change.
I've tried 4 times now to flash this 4.2.2 Rom and nothing.
Factory Reset
Wiped Dalvik
Install Zip
Install gapps
It says to wipe cache and data again
then boot up
It boots up alright, right into my old phone.
Any input I can get is appreciated guys !!!! Thanks.
Copy the ROM to your device (some storage folder)
Boot directly to TWRP
Manually install the ROM and the appropriate GAPPS
(watch the script window and see what it says.. look for errors)
Clear caches and dalvik
reboot
LuckyColdJohnson said:
Okay, I searched before posting. Here is my steps.
I was on SKYNOTE 8.2 and wanted to go back to stock and see what At&t's update was about.
Once back to stock, I rooted my phone and have been on this setup for about 2 weeks.
I was in the original thread and saw the new 4.2.2 Collective AoCP / CM10.1 ROM.
I wanted to try it out.
Using TWRP's latest, followed all instructions and when rebooting it still has stock root ROM.
What am I doing wrong?
I thought it was TWRP so I went to an earlier ver, still no change.
I've tried 4 times now to flash this 4.2.2 Rom and nothing.
Factory Reset
Wiped Dalvik
Install Zip
Install gapps
It says to wipe cache and data again
then boot up
It boots up alright, right into my old phone.
Any input I can get is appreciated guys !!!! Thanks.
Click to expand...
Click to collapse
Try wiping cache/delvik cache, then factory reset twice, then system wipe twice, Install .zip, Install GApps, then wipe cache/delvik again(don't wipe data after .zip is installed. That's how I always do it and it works great.
I think its my recovery Twrp. I changed something.
adam_wingert said:
Try wiping cache/delvik cache, then factory reset twice, then system wipe twice, Install .zip, Install GApps, then wipe cache/delvik again(don't wipe data after .zip is installed. That's how I always do it and it works great.
Click to expand...
Click to collapse
I have tried everything. Its got to be the recovery. No matter what I do in twrp, nothing changes. It says updating partitions and stimulating actions
. It also says successful. After updating to the newest twrp it started this. I changed something. ##[email protected] went into settings and reset....nothing. What if I flashed CWM and then went back to TWRP.
LuckyColdJohnson said:
I have tried everything. Its got to be the recovery. No matter what I do in twrp, nothing changes. It says updating partitions and stimulating actions
. It also says successful. After updating to the newest twrp it started this. I changed something. ##[email protected] went into settings and reset....nothing. What if I flashed CWM and then went back to TWRP.
Click to expand...
Click to collapse
Try cf auto root to reinstall stock then reinstall twrp through odin
Sent from my GT-N7105 using xda premium
What have I done ?
Android The Greek said:
Try cf auto root to reinstall stock then reinstall twrp through odin
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
Okay guys....This has made me sick to my stomach.....I have tried all the different methods. I even soft bricked my phone today using CWM.
Kies wouldnt even fix my phone.
I had to download stock firmware and flash via Odin to get back.
Installed TWRP
Rooted
Went into recovery and wiped everything again
Installed the custom ROM
Rebooted
TWRP didnt do anything even though it says it did.
My phone boots up like normal with Att logo and works but no Custom Rom and no wipes.
What is this? Im going to try other things but wow, this is crazy.
On my SD card I have alot of stuff. I also have a folder named TWRP, it has a back up in there. I wonder if I should remove that?
IDK,,,,,Stuck with Stock root for now. Help If you can. Never had this issue before. What a day
LuckyColdJohnson said:
Okay guys....This has made me sick to my stomach.....I have tried all the different methods. I even soft bricked my phone today using CWM.
Kies wouldnt even fix my phone.
I had to download stock firmware and flash via Odin to get back.
Installed TWRP
Rooted
Went into recovery and wiped everything again
Installed the custom ROM
Rebooted
TWRP didnt do anything even though it says it did.
My phone boots up like normal with Att logo and works but no Custom Rom and no wipes.
What is this? Im going to try other things but wow, this is crazy.
On my SD card I have alot of stuff. I also have a folder named TWRP, it has a back up in there. I wonder if I should remove that?
IDK,,,,,Stuck with Stock root for now. Help If you can. Never had this issue before. What a day
Click to expand...
Click to collapse
Might as well try everything. wipe your sd card in twrp,if that doesn't work reformat through android when booted. Then copy the custom rom over and try again. Only other thing I can think to try is to check that all partitions that are needed are mounted, or try CWM instead.
Also, how did you install TWRP? Through the app? that is the best way to do it, I have had problems flashing twrp through CWM or through the computer. If you aren't already, use goomanager to install it. TWRP has instructions on their website
I figured it out!!!!!!!
Doggydude said:
Might as well try everything. wipe your sd card in twrp,if that doesn't work reformat through android when booted. Then copy the custom rom over and try again. Only other thing I can think to try is to check that all partitions that are needed are mounted, or try CWM instead.
Also, how did you install TWRP? Through the app? that is the best way to do it, I have had problems flashing twrp through CWM or through the computer. If you aren't already, use goomanager to install it. TWRP has instructions on their website
Click to expand...
Click to collapse
It was the settings in TWRP. One of the boxes was checked. Sim actions for theming. I unchecked that and was on my way. Rocking The Collective AoCP now !!!!! Yes.....Thanks to all of you for your input. I'm going back to each and will hit thanks right now! Thanks again XDA members.
Lucky
I'm glad things worked out... isn't it amazing how attached we get to our toys
Sent from my GT-N7105 using Tapatalk 2
Hi
I was flashing back to Stock from task650 to fix my gps. Well something blew up and when the phone reboots the screen goes black but I hear the AT&T start-up tune. Essentially I can't get to enable USB debugging to reflash. I can get to download or recovery, but there are no files to recover<?> and busybox never got installed.
What do I do now?
Do you have the stock recovery now? If so, try going in there and resetting to defaults. That helps sometimes.
Otherwise, you may need to Odin back to stock if you still want to go stock.
CZ Eddie said:
Do you have the stock recovery now? If so, try going in there and resetting to defaults. That helps sometimes.
Otherwise, you may need to Odin back to stock if you still want to go stock.
Click to expand...
Click to collapse
Yes I have stock recovery. Odin is of no use because it hangs waiting for the USB debug to respond. And i can't turn it on because the screen is black and I can't navigate
Do you have a micro sd card? If so, throw a rom on there. If you want to go back to stock, there' a flashable stock zip at the bottom of post #2 in the link in my signature. Under the emergency toolkit section. Flash that, turn on use debugging, do your gps fix and continue on with the task release
xBeerdroiDx said:
Do you have a micro sd card? If so, throw a rom on there. If you want to go back to stock, there' a flashable stock zip at the bottom of post #2 in the link in my signature. Under the emergency toolkit section. Flash that, turn on use debugging, do your gps fix and continue on with the task release
Click to expand...
Click to collapse
Thanks. I created an emergency tool kit on an SD, I wiped data, wiped cache and Davlik and formated system. Flashed the stock rom. When I rebooted it now hung at the Samsung Galaxy S III screen.
How do I get out of this mess?
Try wiping data and cache again in recovery
xBeerdroiDx said:
Try wiping data and cache again in recovery
Click to expand...
Click to collapse
I've wiped data and cache several times, and format/system. I've even tried to flash CWM 6.0.3.1 and I get a status 7 error. Nothing is taking.I get signature failures.
I re downloaded all the files figuring they were corrupted. Nothing doing. I need some real help, because this is beyond my abilities to figure out.,
Now I've got a red triangle showing up in recovery.
BertMor said:
I've wiped data and cache several times, and format/system. I've even tried to flash CWM 6.0.3.1 and I get a status 7 error. Nothing is taking.I get signature failures.
I re downloaded all the files figuring they were corrupted. Nothing doing. I need some real help, because this is beyond my abilities to figure out.,
Now I've got a red triangle showing up in recovery.
Click to expand...
Click to collapse
i dont know why some of these things are not working correctly for you. you're seeing the red triangle because you have stock recovery now from the stock firmware zip. you cannot flash anything in stock recovery nor can you format /system. what happens when you boot up after a factory reset and cache wipe?
a couple of your options include either using odin to flash the stock firmware back onto your device or to use odin to flash a custom recovery back and make a move from there.
xBeerdroiDx said:
i dont know why some of these things are not working correctly for you. you're seeing the red triangle because you have stock recovery now from the stock firmware zip. you cannot flash anything in stock recovery nor can you format /system. what happens when you boot up after a factory reset and cache wipe?
a couple of your options include either using odin to flash the stock firmware back onto your device or to use odin to flash a custom recovery back and make a move from there.
Click to expand...
Click to collapse
When it rains it pours. Now I can't get into recovery. I get the empty battery graphic cycling on and off, and its very warm to the touch. I think the battery is not charging.
I tried using Odin and flashed a stock rom but I kept getting verification errors and status 7 errors. Things just are not taking. I fear I've got a hard brick and I don't know what to do to fix it.
I appreciate your help
aaaaand let the questions roll:
you got verification errors in odin? and after flashing the firmware, i'm assuming you then flashed cwm and that's where you were getting the status 7 errors?
at what point did it all go off? i need to know what order you did all of these things.
can you still get into download mode?
xBeerdroiDx said:
aaaaand let the questions roll:
you got verification errors in odin? and after flashing the firmware, i'm assuming you then flashed cwm and that's where you were getting the status 7 errors?
at what point did it all go off? i need to know what order you did all of these things.
can you still get into download mode?
Click to expand...
Click to collapse
No, it won't go into download. I initially flashed stock rom, but I don't think I wiped anything. That was probably the big mistake. I used something called Samsung S3 QCom tool kit to do an initial flash. It never failed me before. And I also flashed a CWM.
I followed your advice and made a emergency SD kit and flashed from there. I did a clean flash several times. Things just never worked and I kept getting those error messages. Then it just got more difficult to get into download. Now it just flashes a drained battery
it might indeed be drained. leave it plugged in for a while and report back.
you were getting the error/status 7 messages after you flashed cwm back on it likely because the cwm wasnt up-to-date.
what was the last thing you tried before it stopped working altogether?
It gets really hot if I leave it plugged in. But it seems like I can get into recovery again. The last thing I flashed was CMW 6.0.3.1. But what is on it now is CMW 5.5.0.4
actually, what you're saying is the last thing you flashed was cwm 5.5.0.4, just via odin not cwm.
if the phone was in my hands, i would:
flash the cwm 6.0.3.1 zip, select advanced and reboot recovery. now you will be in the updated cwm recovery.
perform a full wipe: wipe data, cache, dalvik, format /system, format /data
flash rom and gapps. if you're going to stick with tasks, use the 4/23 release. i'm on that with no feature or stability issues.
wipe data, wipe cache, reboot.
give it a few minutes to boot up.
BertMor said:
No, it won't go into download. I initially flashed stock rom, but I don't think I wiped anything. That was probably the big mistake. I used something called Samsung S3 QCom tool kit to do an initial flash. It never failed me before. And I also flashed a CWM.
I followed your advice and made a emergency SD kit and flashed from there. I did a clean flash several times. Things just never worked and I kept getting those error messages. Then it just got more difficult to get into download. Now it just flashes a drained battery
Click to expand...
Click to collapse
xBeerdroiDx said:
actually, what you're saying is the last thing you flashed was cwm 5.5.0.4, just via odin not cwm.
if the phone was in my hands, i would:
flash the cwm 6.0.3.1 zip, select advanced and reboot recovery. now you will be in the updated cwm recovery.
perform a full wipe: wipe data, cache, dalvik, format /system, format /data
flash rom and gapps. if you're going to stick with tasks, use the 4/23 release. i'm on that with no feature or stability issues.
wipe data, wipe cache, reboot.
give it a few minutes to boot up.
Click to expand...
Click to collapse
Nope. When I try to flash CWM 6.0.3.1 I get an assert failed error. I came across this fix, I wonder if it is safe to try http://mobotechie.com/tips-tricks/how-to-fix-android-custom-rom-status-7-installation-abort-assert-failed-error-in-recovery-easily-ultimate-guide
BertMor said:
Nope. When I try to flash CWM 6.0.3.1 I get an assert failed error. I came across this fix, I wonder if it is safe to try http://mobotechie.com/tips-tricks/how-to-fix-android-custom-rom-status-7-installation-abort-assert-failed-error-in-recovery-easily-ultimate-guide
Click to expand...
Click to collapse
Well I think I managed it!. First I tried to install an update d/l'ed from Dropbox and that did nothing. Then I flashed an old .tar that was a rooted stock and it rebooted!
I tried editing the updater-script but I couldn't getit to save the changes properly.
Well I will now re flash the RM and CWM and hope for the best
Thanks for all your help, greatly appreciated
Hi everyone. Just guy my note tablet. Rooted with towlie.
Build number kot49h.p607tuvuane2
Finding a bit of confusion on which TWRP I should install. I did one with Odin, and it didn't take.
Can someone point me to right file and/or directions if i need to downgrade first?
I want to start playing and customizing, but cannot back up or reflash.
redheadplantguy said:
Hi everyone. Just guy my note tablet. Rooted with towlie.
Build number kot49h.p607tuvuane2
Finding a bit of confusion on which TWRP I should install. I did one with Odin, and it didn't take.
Can someone point me to right file and/or directions if i need to downgrade first?
I want to start playing and customizing, but cannot back up or reflash.
Click to expand...
Click to collapse
most stable version would be 2.6.3.3
buhohitr said:
most stable version would be 2.6.3.3
Click to expand...
Click to collapse
Have heard a few things about needing an Odin firmware downgrade. Is that necessary with my firmware? And should I use Odin, or ADB?
Really appreciate the info. I want to tinker, but without working recovery, I'm a bit Leary.
redheadplantguy said:
Have heard a few things about needing an Odin firmware downgrade. Is that necessary with my firmware? And should I use Odin, or ADB?
Really appreciate the info. I want to tinker, but without working recovery, I'm a bit Leary.
Click to expand...
Click to collapse
the version I stated is most stable, other twrp version may cause cache corruption and other issues.
buhohitr said:
the version I stated is most stable, other twrp version may cause cache corruption and other issues.
Click to expand...
Click to collapse
the closest release i could find was twrp 2331.
i flashed with odin. but when i tried to reboot to recovery, i got a scrambled, pixelated screen which after a few seconds rebooted system.
redheadplantguy said:
the closest release i could find was twrp 2331.
i flashed with odin. but when i tried to reboot to recovery, i got a scrambled, pixelated screen which after a few seconds rebooted system.
Click to expand...
Click to collapse
Get it here http://www.techerrata.com/browse/twrp2/lt03wifiue
You need to wipe cache, davik cache and data, then flash the rom.
buhohitr said:
Get it here http://www.techerrata.com/browse/twrp2/lt03wifiue
You need to wipe cache, davik cache and data, then flash the rom.
Click to expand...
Click to collapse
I found that version on the link, but i thought that was for the Exynos chipset.
I have the Qualcomm LTE version. Will it still work?
redheadplantguy said:
I found that version on the link, but i thought that was for the Exynos chipset.
I have the Qualcomm LTE version. Will it still work?
Click to expand...
Click to collapse
For Qualcomm LTE the version is 2.6.3.1
https://goo.im/devs/OpenRecovery/lt03ltexx/openrecovery-twrp-2.6.3.1-lt03ltexx.zip/
Hi,
This post saved me, I installed TWRP 2.8 and my system froze, I couldn't get past the Samsung 10.1 screen.
But found this post and flashed 2.6.3.3 via Odin and it all went smoothly.
PS Goo.img.com dosen't have the files anymore
buhohitr said:
For Qualcomm LTE the version is 2.6.3.1
https://goo.im/devs/OpenRecovery/lt03ltexx/openrecovery-twrp-2.6.3.1-lt03ltexx.zip/
Click to expand...
Click to collapse
I currently have no recovery. I tried flashing 2.8 originally.
How would i clear cache, data, and all before trying to flash 2631?
redheadplantguy said:
I currently have no recovery. I tried flashing 2.8 originally.
How would i clear cache, data, and all before trying to flash 2631?
Click to expand...
Click to collapse
No, you flash TWRP 2631, then boot into the twrp then select advance then put a check for cache, davik cache and data, then swipe. Once done just flash your rom. I would copy the rom to the download folder on the internal storage (/sdcard/download/) before flash your new twrp.
Is 2.6.3.3 more reliable / stable in terms of making / restoring nandroids? I just got my new Note last week (p607t) and flashed xKat with TWRP at one point, restoring apps from (some with data to avoid re-entering account info or redoing complex settings...) I have had one problem however, when I was almost done restoring, I noticed that I was getting fc's, particularly with games that required an internet connection. I wiped dalvik and cache in TWRP, then hit fix permissions, which I think screwed everything up (maybe due to the bootloader / firmware base mismatch). Anyway, my most recent nandroid was with the fresh xKat install, but fixing permissions caused this weird "hot"-bootloop where it skipped the boot animation but start loading immediately after rebooting, but then freezing before all boot tasks had completed (ex. some optimizations on boot with Android Tuner Pro, FolderMount mounting folders, loading xposed modules...)
Not wanting to re-restore, I first just tried dirty-flashing the ROM again (only wiped dalvik and cache, but did something I hadn't tried before: in the wipe menu I hit "repair partition" for system and data, pre-flash). Luckily it worked and set everything straight... but just want to make sure, 2.6.3.3 is still recommended as the most stable version (in my experience, fixing permissions in recovery can be very hit or miss on any version)?
2 questions before I roll back my recovery, I think these "killer features" (totally serious, #2 has been huge since I got a couple of the newish flash drives with micro usb on one side and regular usb on the other) of TWRP were implemented in 2.6.3.3, but just want to make sure: can you 1) compress nandroids and 2) mount a USB OTG drive and flash from or backup to it? Thanks all, really loving my new Note (massive upgrade from my Note 8!)
buhohitr said:
No, you flash TWRP 2631, then boot into the twrp then select advance then put a check for cache, davik cache and data, then swipe. Once done just flash your rom. I would copy the rom to the download folder on the internal storage (/sdcard/download/) before flash your new twrp.
Click to expand...
Click to collapse
I HAVE flashed 2631 for the qualcomm lte.
I've done or several times since you told me that's the best version.
IT WILL NOT BOOT INTO TWRP. it's a scrambled screen. That's all. No touch options. No check boxes. After a minute, tablet reboots itself. I am on stock firmware still. Rooted.
Maybe I should just try CWM. never had this much problems with twrp on any other device.
redheadplantguy said:
I HAVE flashed 2631 for the qualcomm lte.
I've done or several times since you told me that's the best version.
IT WILL NOT BOOT INTO TWRP. it's a scrambled screen. That's all. No touch options. No check boxes. After a minute, tablet reboots itself. I am on stock firmware still. Rooted.
Maybe I should just try CWM. never had this much problems with twrp on any other device.
Click to expand...
Click to collapse
How about wipe cache/davikcache/data with your stock recovery (just reflash your stock recovery). After that let it boot up, then power down and flash twrp. Once done, don't boot up, boot back to twrp . Let me know how it goes.
Cool. I can try that when I get home. Do you have a link handy for the stock recovery?
redheadplantguy said:
Cool. I can try that when I get home. Do you have a link handy for the stock recovery?
Click to expand...
Click to collapse
Please try this twrp. Many ppl reported it's working for p607t.
http://forum.xda-developers.com/showpost.php?p=53138918&postcount=776
If not working then we will go for stock recovery.
buhohitr said:
Please try this twrp. Many ppl reported it's working for p607t.
http://forum.xda-developers.com/showpost.php?p=53138918&postcount=776
If not working then we will go for stock recovery.
Click to expand...
Click to collapse
THANK YOU SO MUCH! TWRP booted right up, and nandroid in progress. now I'll be able to try some custom ROM's and play in system.
:laugh:
I need to get Data from my Samsung Galaxy S3 SGH-1747 and it won't boot past the Samsung Logo.
Someone told me to...
"Get TWRP image for your S3 model, flash image using Odin, boot into TWRP recovery, mount storage to PC and recover data."
I'm very new and sorry lol. Could someone help me with the steps necessary? I have no idea what TWRP is. My phone is not rooted. Is there a guide with photos or a video? What do I need to download for Odin? How do I flash?
My phone is in the most recent Android for it.
TWRP thread is here: https://forum.xda-developers.com/showthread.php?t=1793224
audit13 said:
TWRP thread is here: https://forum.xda-developers.com/showthread.php?t=1793224
Click to expand...
Click to collapse
I went to the post and it said I need to download to my phone from play store.
How?
My phone is not rooted and is stuck in Bootloop.
Please and thank you if you could help.
Before you do anything, try to figure out if you can boot your phone into these 2 mode:
Download mode - With the device powered off, hold Home + Volume Down + Power
Recovery mode - With the device powered off, hold Home + Volume Up + Power. (Take a picture of your recovery mode because it will tell your bootloader version)
If you can't get into those mode, your phone is likely to have a bigger problem.
CanadaChino666 said:
Someone told me to...
"Get TWRP image for your S3 model, flash image using Odin, boot into TWRP recovery, mount storage to PC and recover data."
Click to expand...
Click to collapse
The instruction is for Samsung i9305 but it will work on d2att. To flash TWRP into your phone, you need to follow this instruction. (https://wiki.lineageos.org/devices/i9305/install). Also you need those files:
Heimdall suite - http://glassechidna.com.au/heimdall/#downloads
TWRP image - https://twrp.me/Devices/Samsung
CanadaChino666 said:
What do I need to download for Odin? How do I flash?
Click to expand...
Click to collapse
The only way to flash stock firmware into the phone, is with the software Odin. It's basically starting your phone with a fresh firmware through 'Download Mode' with your phone (With the device powered off, hold Home + Volume Down + Power). It will erase everything.
CanadaChino666 said:
I went to the post and it said I need to download to my phone from play store.
How?
My phone is not rooted and is stuck in Bootloop.
Please and thank you if you could help.
Click to expand...
Click to collapse
There was a link in the thread to the official TWRP website with instructions for using Odin to install TWRP for the d2att which is the SGH-i747: : https://twrp.me/samsung/samsunggalaxys3att.html
Download the tar version of TWRP from here: https://twrp.me/Devices/ I recommend starting with version 2.8.7.0 as a starting point.
Download Odin 3.07 from here: https://www.google.com/url?sa=t&rct...ntid=1168421&usg=AOvVaw0aq_x8M8nbsqDFAFe9tFoy
Download and install the Windows Samsung USB drivers: https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows. I assume you are using a Windows computer.
Make sure the battery is fully charged. Open Odin, do not check anything except f reset time, click on the PDA box and select the TWRP tar file, connect the phone in download mode to the computer with the original Samsung USB cable, flash the TWRP. When you see the word reset, remove the USB cable from the phone, remove the battery, replace the battery, use the button combination to get into recovery. Once in recovery, mount the data partition and copy of the data.
WARNING: flashing a phone always involves risk and you could wind up with a bricked phone and/or loss of data. Proceed cautiously and at your own peril.
Thank You
Thank You So Much!
One love, Much Love ??????
So it worked...
Any ideas how you get the text messages and S3 Notepads out?
I've mounted it on my computer.
If I use TWRP to backup my phone, will it really bootloop if I reinstall the backup?
CanadaChino666 said:
If I use TWRP to backup my phone, will it really bootloop if I reinstall the backup?
Click to expand...
Click to collapse
Yes it will, you need to figure out what's making your system bootloop and resolve it or wipe data and cache.
Omarkoopa said:
Yes it will, you need to figure out what's making your system bootloop and resolve it or wipe data and cache.
Click to expand...
Click to collapse
Any idea how to investigate?
How do I wipe data and cache on TWRP?
Would backing up Data but not system, help restore files like the memos, text messages etc?
Because I could backup the Data and then wipe factory reset and then reinstall the data backup.
How do you factory reset from TWRP?
BlackBeast888 said:
Any idea how to investigate?
How do I wipe data and cache on TWRP?
Would backing up Data but not system, help restore files like the memos, text messages etc?
Because I could backup the Data and then wipe factory reset and then reinstall the data backup.
How do you factory reset from TWRP?
Click to expand...
Click to collapse
The data is what makes the system bootloop in most of the cases and since you're not rooted it is certainly the data what's causing the problem so restoring it would solve nothing.
The option is there on twrp to wipe data and cache.
---------- Post added at 05:41 AM ---------- Previous post was at 05:39 AM ----------
To inevstigate hmmm
You need to remember what you did before the bootloop happened
For example if you installed and app try to remove it and it's data using the twrp file browser.
Omarkoopa said:
The data is what makes the system bootloop in most of the cases and since you're not rooted it is certainly the data what's causing the problem so restoring it would solve nothing.
The option is there on twrp to wipe data and cache.
---------- Post added at 05:41 AM ---------- Previous post was at 05:39 AM ----------
To inevstigate hmmm
You need to remember what you did before the bootloop happened
For example if you installed and app try to remove it and it's data using the twrp file browser.
Click to expand...
Click to collapse
Wiping Data and Cache will erase my files, yes?
I was uploading a file to Google Photos before the crash and loop
BlackBeast888 said:
Wiping Data and Cache will erase my files, yes?
Click to expand...
Click to collapse
Yes. It's like a factory reset.
BlackBeast888 said:
I was uploading a file to Google Photos before the crash and loop
Click to expand...
Click to collapse
I think you can try to remove Google Photos apps via adb and see if it does fix your bootloop issue. Since you have a backup, you can undo your steps. https://forum.xda-developers.com/showthread.php?t=559925.
You can get adb here: https://forum.xda-developers.com/showthread.php?t=2317790
CanadaChino666 said:
If I use TWRP to backup my phone, will it really bootloop if I reinstall the backup?
Click to expand...
Click to collapse
Before proceeding, I recommend copying what you can to a computer by mounting the data partition. Then, I would create a complete backup (system and data). Once completed, copy the back to at least one safe place, preferably 2.
Now, try wiping the cache only and reboot. It may be a cache problem that is preventing the phone from fully booting.
Unfortunately, I'm not able to provide instructions to back up text and notes.
audit13 said:
Before proceeding, I recommend copying what you can to a computer by mounting the data partition. Then, I would create a complete backup (system and data). Once completed, copy the back to at least one safe place, preferably 2.
Now, try wiping the cache only and reboot. It may be a cache problem that is preventing the phone from fully booting.
Unfortunately, I'm not able to provide instructions to back up text and notes.
Click to expand...
Click to collapse
I wiped cache and still nothing.
Is there any other options besides factory reset?
Can the backup bring it back to the way it was or will it make it bootloop again?
I haven't used twrp for a long time but you could try restoring the backup and wipe the cache before booting.
Note that restoring your backup will overwrite what's currently in the phone storage.
audit13 said:
I haven't used twrp for a long time but you could try restoring the backup and wipe the cache before booting.
Note that restoring your backup will overwrite what's currently in the phone storage.
Click to expand...
Click to collapse
Unfortunately I can only backup the current bootloop state lol.
I think there's no other option except factory reset.
nehc_rm said:
Yes. It's like a factory reset.
I think you can try to remove Google Photos apps via adb and see if it does fix your bootloop issue. Since you have a backup, you can undo your steps. https://forum.xda-developers.com/showthread.php?t=559925.
You can get adb here: https://forum.xda-developers.com/showthread.php?t=2317790
Click to expand...
Click to collapse
is there any other option besides factory reset from here lol?
BlackBeast888 said:
is there any other option besides factory reset from here lol?
Click to expand...
Click to collapse
The only option maybe you have is using adb to uninstall apps one by one and hope it fixes the bootloop. You can try maybe to clear the dalvik cache + cache but I think you have done that.
I have been in this situation before. It's not fun at all. The only way to backup/recover data in a modular way, is with apps like Titanium Backup [root] and Helium. Backup your app + data when the phone is working. When you have a bootloop, do a factory reset and restore the app data incrementally. They are really great apps.
nehc_rm said:
The only option maybe you have is using adb to uninstall apps one by one and hope it fixes the bootloop. You can try maybe to clear the dalvik cache + cache but I think you have done that.
I have been in this situation before. It's not fun at all. The only way to backup/recover data in a modular way, is with apps like Titanium Backup [root] and Helium. Backup your app + data when the phone is working. When you have a bootloop, do a factory reset and restore the app data incrementally. They are really great apps.
Click to expand...
Click to collapse
Can these apps be used while it is in bootloop? Lol