Develop Bugs

Cant Flash new ROMs anymore. Please help.

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

USB Debugging not accessible

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

[Q] Samsung Galaxy s3 i747 stuck in Cyanogenmod boot screen

Hello:
So I rooted my phone today and I downloaded the app, "ROM Manager," and downloaded a ROM from it, which I read that I'm not supposed to do, afterwards. Now, whenever I turn my phone on, it only shows the Cyanogenmod boot animation. I read in another thread that I should clear the cache, which I did, but it did not help. Should I try and flash it to the stock? Please help! I am inexperienced with this and I don't know what to do. Thanks in advance!

dallinrigby said:
Hello:
So I rooted my phone today and I downloaded the app, "ROM Manager," and downloaded a ROM from it, which I read that I'm not supposed to do, afterwards. Now, whenever I turn my phone on, it only shows the Cyanogenmod boot animation. I read in another thread that I should clear the cache, which I did, but it did not help. Should I try and flash it to the stock? Please help! I am inexperienced with this and I don't know what to do. Thanks in advance!
Click to expand...
Click to collapse
Alright. First off: what OS were you running before you went to cyanogenmod? was it 4.0.4? 4.1.x? 4.2.x? or 4.3.x?
Second, give us more information about the phone.
Third, you might have to go into recovery mode, wipe your phone (theres two options in the main menu, and one in the advanced called wipe dalvik). Then youll have to reinstall Cyanogenmod.

ChinDaChin said:
Alright. First off: what OS were you running before you went to cyanogenmod? was it 4.0.4? 4.1.x? 4.2.x? or 4.3.x?
Second, give us more information about the phone.
Third, you might have to go into recovery mode, wipe your phone (theres two options in the main menu, and one in the advanced called wipe dalvik). Then youll have to reinstall Cyanogenmod.
Click to expand...
Click to collapse
Your phone will get stuck if you did not clear the dalvik as well as the cache. I would recommend first clearing cache again and also dalvik before rebooting back into the operating system or doing something else which may not be necessary.

shortydoggg said:
Your phone will get stuck if you did not clear the dalvik as well as the cache. I would recommend first clearing cache again and also dalvik before rebooting back into the operating system or doing something else which may not be necessary.
Click to expand...
Click to collapse
I have already tried to clear the cache and the dalvik and then did a reboot but it didn't change anything.

shortydoggg said:
Your phone will get stuck if you did not clear the dalvik as well as the cache. I would recommend first clearing cache again and also dalvik before rebooting back into the operating system or doing something else which may not be necessary.
Click to expand...
Click to collapse
ChinDaChin said:
Alright. First off: what OS were you running before you went to cyanogenmod? was it 4.0.4? 4.1.x? 4.2.x? or 4.3.x?
Second, give us more information about the phone.
Third, you might have to go into recovery mode, wipe your phone (theres two options in the main menu, and one in the advanced called wipe dalvik). Then youll have to reinstall Cyanogenmod.
Click to expand...
Click to collapse
I was running the stock jellybean before I installed cryogenmod...my phone is a galaxy s3 it47 (AT&T) network unlocked phone. Also, at the bottom in recovery mode it says
ClockworkMod Recovery v6. 0. 4. 5
I'm not sure whether or not this is important but it is the only thing that I can think of to tell you about my phone.
I don't care whether we keep my data, I just want it to be able to turn on! Can I just restore it using Odin somehow? I tried the wipe user memory option in recovery mode and that didn't help...

Personally, I hate both ROM manager and clockworkmod.
It sounds like you just need to wipe data (or factory reset), cache and dalvik, and then reboot. If that doesn't work, then you might have flashed a version of cyanogenmod that may not be compatible with your bootloader, and may have to manually try another ROM.

shortydoggg said:
Personally, I hate both ROM manager and clockworkmod.
It sounds like you just need to wipe data (or factory reset), cache and dalvik, and then reboot. If that doesn't work, then you might have flashed a version of cyanogenmod that may not be compatible with your bootloader, and may have to manually try another ROM.
Click to expand...
Click to collapse
I tried to do a factory reset, it didn't help as far as I know. How do i manually try another rom?

dallinrigby said:
I tried to do a factory reset, it didn't help as far as I know. How do i manually try another rom?
Click to expand...
Click to collapse
Can you tell us what version of touchwiz you were running before you tried rooting it? It's important if it's past 4.3.x, or before 4.3.x. Do the following if you were running 4.3.x before you rooted.
Go to http://download.cyanogenmod.org/?device=d2att&type=
Choose the one named: cm-10.2.0-d2att.zip
Download it and save it to your SD Card.
Go here and download 10.2: http://wiki.cyanogenmod.org/w/Google_Apps and put it on your SD card with the above .zip.
Once thats done, power off your phone. Go into recovery mode (volume up + home + power).
Wipe Data/Factory Reset
Wipe Cache partition
Advanced -> wipe Dalvik Cache
Go back, and choose Install Zip
Choose zip from /storage/sdcard (find your cm10.2 zip, run it. then run the gapps)
After you "installed" both zips, go back to the main menu and reboot system now
This will be a clean install of 10.2.
FYI: Clockworkmod Recovery is v6.0.4.5, so you have the most up to date.

ChinDaChin said:
Can you tell us what version of touchwiz you were running before you tried rooting it? It's important if it's past 4.3.x, or before 4.3.x. Do the following if you were running 4.3.x before you rooted.
Choose the one named: cm-10.2.0-d2att.zip
Download it and save it to your SD Card.
Once thats done, power off your phone. Go into recovery mode (volume up + home + power).
Wipe Data/Factory Reset
Wipe Cache partition
Advanced -> wipe Dalvik Cache
Go back, and choose Install Zip
Choose zip from /storage/sdcard (find your cm10.2 zip, run it. then run the gapps)
After you "installed" both zips, go back to the main menu and reboot system now
This will be a clean install of 10.2.
FYI: Clockworkmod Recovery is v6.0.4.5, so you have the most up to date.
Click to expand...
Click to collapse
I don't know what version I had. Is there a way for me to tell? I just had whatever I bought it with, I never downloaded anything else.
It says on that second link to download Torrent or via It Vends, is this the right place, and if so what do I pick?
Thanks by the way, also is there a way I could do this with Odin?

dallinrigby said:
I don't know what version I had. Is there a way for me to tell? I just had whatever I bought it with, I never downloaded anything else.
Click to expand...
Click to collapse
I used Goo.im. It's a funky looking website, but it's legitimate. I didn't do this with Odin, I used Cyanogenmod Installer :silly:
If you follow what I posted before, it will update everything, and you will run cyanogenmod 10.2. (What I'm running on my s3). HOWEVER, it will update your phone to 4.3. This means you cannot downgrade it, or it will be bricked. By downgrade, I mean you will not be able to run anything before 4.3. (So you can ONLY install roms that are 4.3, or jellybean).
I'm pretty sure you already updated everything since its stuck in the boot loop.
Any chance you did a nandroid backup(before you did the root)? If not, you've got nothing to lose and might as well go through with CM 10.2 (in my honest opinion).

ChinDaChin said:
I used Goo.im. It's a funky looking website, but it's legitimate. I didn't do this with Odin, I used Cyanogenmod Installer :silly:
If you follow what I posted before, it will update everything, and you will run cyanogenmod 10.2. (What I'm running on my s3). HOWEVER, it will update your phone to 4.3. This means you cannot downgrade it, or it will be bricked. By downgrade, I mean you will not be able to run anything before 4.3. (So you can ONLY install roms that are 4.3, or jellybean).
I'm pretty sure you already updated everything since its stuck in the boot loop.
Any chance you did a nandroid backup(before you did the root)? If not, you've got nothing to lose and might as well go through with CM 10.2 (in my honest opinion).
Click to expand...
Click to collapse
Okay, so now it says Android system recovery <3e> at the top and at the bottom is this:
#MANUAL MODE#
--Applied Multi-CSC...
Applied the CSC-code : ATT
Successfully applied multi-CSC
Then when I pushed install from sdcard it said E:failed to verify whole file signature
Do i need to unzip it?

dallinrigby said:
Okay, so now it says Android system recovery <3e> at the top and at the bottom is this:
#MANUAL MODE#
--Applied Multi-CSC...
Applied the CSC-code : ATT
Successfully applied multi-CSC
Then when I pushed install from sdcard it said E:failed to verify whole file signature
Click to expand...
Click to collapse
Don't lose hope, but every site/page I check, it says the error is with you flashing through Rom Manager. It's okay though, there has to be a solution.
I'm going to continue looking for the solution. If you could try and remember what version of the OS you were running before you tried to root, it would help out SO MUCH!
LOL., I forgot to hit post on this.
And no, don't unzip it. The phone can read it fine.
Anyway, after some quick reading, a few people are saying its either your rom that is corrupted, or you don't have the proper recovery. It can't be the rom, because the rom was downloaded from the source. So chances are its your recovery. I'm not sure if you can download the CWM recovery, and flash it from recovery. (if that makes sense?)

ChinDaChin said:
Don't lose hope, but every site/page I check, it says the error is with you flashing through Rom Manager. It's okay though, there has to be a solution.
I'm going to continue looking for the solution. If you could try and remember what version of the OS you were running before you tried to root, it would help out SO MUCH!
LOL., I forgot to hit post on this.
And no, don't unzip it. The phone can read it fine.
Anyway, after some quick reading, a few people are saying its either your rom that is corrupted, or you don't have the proper recovery. It can't be the rom, because the rom was downloaded from the source. So chances are its your recovery. I'm not sure if you can download the CWM recovery, and flash it from recovery. (if that makes sense?)
Click to expand...
Click to collapse
I don't really understand this stuff very much, and also I am pretty sure my android version before was 4.1.2, that's jelly bean right? is that what you meant?

If it's CWM that is the problem, you can download TWRP and flash it via Odin if you can get into download mode. Then, you can use TWRP to flash a custom ROM.

audit13 said:
If it's CWM that is the problem, you can download TWRP and flash it via Odin if you can get into download mode. Then, you can use TWRP to flash a custom ROM.
Click to expand...
Click to collapse
Where do i get TWRP? It doesn't say that I have Clockwork anymore, since I factory reset it

dallinrigby said:
I don't really understand this stuff very much, and also I am pretty sure my android version before was 4.1.2, that's jelly bean right? is that what you meant?
Click to expand...
Click to collapse
Sorry.
I'm kind of conflicted on what's going on with your phone. It is partially a problem with going through Rom Manager to flash cyanogenmod.
audit13 said:
If it's CWM that is the problem, you can download TWRP and flash it via Odin if you can get into download mode. Then, you can use TWRP to flash a custom ROM.
Click to expand...
Click to collapse
I guess you can try TWRP. I haven't used TWRP so I can't comment on it. I'll try finding an explanatory video that is simple to follow. (Don't throw out Cm10.2, or the gapps. You will need those to get Cyanogenmod on your phone!)

Help restoring my DEV note 4 please!!

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.

After Factory Reset, Phone is Slow as Hell - HELP!!

I'm rooted on my Galaxy S3. Last month I made a backup through TWRP recovery. Yesterday when I restored to the backup, the restore wasnt complete. I tried to restore again and I encountered the same incomplete restore. My customized settings in the apps were gone and some of the apps I had backed up weren't included in the restore. Looks like something got messed up.
I then wiped cache, Dalvik, data and system. I even formatted the phone. I also did a factory reset. This messed up my phone so I installed a new rooted stock rom. So now, the phone is slow as hell and apps arent very responsive. Everything is laggy and slow. And the play store and youtube have slow connection speeds.
What should I do to fix this stupidity??

Did you try restoring a stock ROM via Odin?

I had the same thing happen before. Odin with a stock rom is all that fixed it for me.

audit13 said:
Did you try restoring a stock ROM via Odin?
Click to expand...
Click to collapse
Yes I did. But Playstore downloading speed and wifi speed are slow as hell. What do you suggest?

Are you downloading over WiFi or cellular data network? The phone is running the latest rom without root? After flashing, you you immediately go to b recovery and do a full wipe?

audit13 said:
Are you downloading over WiFi or cellular data network? The phone is running the latest rom without root? After flashing, you you immediately go to b recovery and do a full wipe?
Click to expand...
Click to collapse
Yes I'm downloading over wifi and its slow. The phone is laggy too. Its running JB with root. I tried a full wipe of dalvik, cache and data or system. It doesnt help.

This is really strange because a factory reset usually does the trick.
This may be a redundant question but was the phone flashed with the correct ROM? I see different variations of the T999 on sammobile.com's website.

audit13 said:
This is really strange because a factory reset usually does the trick.
This may be a redundant question but was the phone flashed with the correct ROM? I see different variations of the T999 on sammobile.com's website.
Click to expand...
Click to collapse
Hi audit.. Its not a dumb question at all. The rom was the correct one for my phone. Everything was working fine up until a week ago. Its possible that my phone fell and maybe that caused damage maybe.
Not only that but restoring bsckups through TWRP doesnt yield perfect restores. All my restores have not been complete. Customized settings all returned to default and apps were rearramged differently.
Anyeay, just to make sure, how can I do a proper wipe without wiping out my custom settings and apps? Do I just wipe dalvik, cache and system?

You would wipe dalvik and cache only.
Wiping data wipes apps.
Wiping system wipes the rom.

audit13 said:
You would wipe dalvik and cache only.
Wiping data wipes apps.
Wiping system wipes the rom.
Click to expand...
Click to collapse
Thanks for a speedy reply. Can you explain why my backuo restores through TWRP dont yield perfect restores? Custom settings return to default and apps are arranged differently.

I am not sure why that happens but I have used twrp on several phones, including the lg g2, nexus 4, note 3, htc one x, and Samsung tab without issue. Maybe you need to do a full wipe before restoring? Does the phone have the latest twrp?

audit13 said:
I am not sure why that happens but I have used twrp on several phones, including the lg g2, nexus 4, note 3, htc one x, and Samsung tab without issue. Maybe you need to do a full wipe before restoring? Does the phone have the latest twrp?
Click to expand...
Click to collapse
Hi audit. Yes the phone has the latest TWRP. I downloaded it from the play store yesterday.
I got an important question. I backed up my rom a few days through TWRP as I said. Is it possible to open up the backup on my laptop and search for specific pics? I dont want to restore the rom, since as I stated, I have problems doing so. I just need to get those pics. Is this possible?

I am not sure but it is worth a try.
Humour me but is the twrp 2.8.7?

audit13 said:
I am not sure but it is worth a try.
Humour me but is the twrp 2.8.7?
Click to expand...
Click to collapse
Thats right, current version is 2.8.7.0.

I don't know why it doesn't restore properly. Maybe try re-flashing twrp from Odin? Can't really think of anything else.

audit13 said:
I don't know why it doesn't restore properly. Maybe try re-flashing twrp from Odin? Can't really think of anything else.
Click to expand...
Click to collapse
How do I reflask TWRP through odin? In doing so, would I risk losing my data, apps, etc? Is it safe?

You download the tar file for d2att, open Odin, put phone into download mode, put the tar file in the pda box, and flash.

audit13 said:
You download the tar file for d2att, open Odin, put phone into download mode, put the tar file in the pda box, and flash.
Click to expand...
Click to collapse
Wait, when you say the tar file for d2att you mean the TWRP file, right? Hope thats what you mean because the way you describe it, it sounds like instructions on flashing the whole rom.
Where do I get the tar file for the TWRP app?

TWRP link: https://dl.twrp.me/d2att/

audit13 said:
TWRP link: https://dl.twrp.me/d2att/
Click to expand...
Click to collapse
Thanks audit. Now, I'd like to know what app do you recommend to find out which apps are causing the phone to get so hot. Thanks.