Develop Bugs

Soft brick? Recovery not working properly

Hey guys all my restores are failing half way through. It also fails if I try to factory reset or wipe dalvik but wipe cache works fine It fails if i try flash any ROM.. And if I try to boot to system it shows SG logo then black screen I'm really kind of lost here. I've already tried flashing 4 different versions of Twrp/clockworkmod and I get the same result every time. The roms I'm trying to flash were running fine on my device before this happened. Never seen this before please help thank you.
Sent from RootBox infected sensation or my PacMan e739

djwuh said:
Hey guys all my restores are failing half way through. It also fails if I try to factory reset or wipe dalvik but wipe cache works fine It fails if i try flash any ROM.. And if I try to boot to system it shows SG logo then black screen I'm really kind of lost here. I've already tried flashing 4 different versions of Twrp/clockworkmod and I get the same result every time. The roms I'm trying to flash were running fine on my device before this happened. Never seen this before please help thank you.
Sent from RootBox infected sensation or my PacMan e739
Click to expand...
Click to collapse
is this an i747 or i747m (carrier?)? what was the last thing you did to the device/had you just modified or flashed something? were you using recovery or odin to flash the 4 different recoveries?

xBeerdroiDx said:
is this an i747 or i747m (carrier?)? what was the last thing you did to the device/had you just modified or flashed something? were you using recovery or odin to flash the 4 different recoveries?
Click to expand...
Click to collapse
I have sgh i747 at&t us model. Unlocked Sim for Tmobile use. Before having problems. I flashed vanilla rootbox att nightly. it was running fine then I flashed acid audio mod. And it worked but not well with my player of choice. So i flashed a restore from fright before the sound mod. And all I got was 2 different Samsung logos then black screen. At this point Twrp started asking for a password. I tried an older backup. (rootbox stable) and it booted fine. Everything seemed to be working. But when I rebooted again I got the 1St SG logo then black screen. Now recovery doesn't read anything on the internal card as well as the other problems I stated. I used mskips toolkit to flash Twrp originally and now I've been flashing back and forth between recoveries using recovery flashable zips. Also every time I flash roms or restore I did factory wipe/cache/dalvik and after I started having these issues I tried wiping system and that didn't help either. Thanks for trying to help
Sent from RootBox infected sensation or my PacMan e739

what recovery are you currently sitting on?

Twrp 2.4.4.0 is what I started with and now I'm back on it but from a flashable zip this time instead of whatever mskips toolkit used
Sent from RootBox infected sensation or my PacMan e739

here is the link to an odin flashable twrp 2.5.0.0 tar: http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.5.0.0-d2att.tar
and here's a recovery flashable twrp 2.5.0.0 zip link: http://forum.xda-developers.com/attachment.php?attachmentid=1917517&d=1367104589
if you flash in recovery, be sure to reboot recovery in order to boot into the new version. i'm sure you know most of this but i'm just trying to cover all the bases.
is twrp still asking for the password or were you able to get passed that?
if you have a micro sd card, you could place a ROM/gapps on it, flash this latest twrp recovery from odin or recovery, perform a full wipe (cache, dalvik, data, system) and flash the ROM/gapps. see if that remedies your situation.
if you dont have a micro sd card, and it appears you've wiped the system so there's no OS, you may have to odin back to rooted stock and start over. keep me posted

Still no luck. i flashed twrp2.5 through recovery and after rebooting back to recovery it still asked for a password so I hit cancel at which point it lets me continue and after full wipe as you described above and a fresh flash of stable rootbox 3.9.1 (md5 matched) im still in the same situation. also factory wipe says failed still

I think at this point if it were me, I would Odin flash back to stock then start from scratch. Pain in the butt I know, and no guarantee, but usually flash back to stock is a safe bet.

Another option is to grab the Odin flashable cwm tar in the "root from recovery" method in the general section. Flash the tar, boot into recovery and flash the 6.0.3.1 zip in post #2 of my signature link. Reboot recovery and try wiping/flashing again.
Since you're not entering the password in TWRP, I think that's why you're not getting successful wipes and flashes.

now I used the power+home+vol down button combo to see if bootloader would start. it gave me a choice to download a custom rom or cancel so I canceled and the phone rebooted and i was blessed with the beautifull rootbox animation. my rootbox 3.9.1 nandroid booted and seems to be running fine. Now Im afraid to reboot in fear it will start the whole process over again. any suggestions? or should I just leave it powered on for the rest of its life lol
edit: well I got up the guff to reboot and everything came back fine again WTH. this is so weird, I wish I had a clue what happened. anyways I just wanted to thank you guys one more time for you help. hopefully we wont have to come back to this thread. Peace ;-]

Man that is strange. If that ever happens again it would be interesting to see the log if you can get it. I wonder if there were issues mounting a partition and/or your SD card. If TWRP and CWM were both having an error and the files were on your SD card that would probably be the only thing in common that could cause something like this. Some Transformers seemed to have the password issue, but doesn't seem related to your experience. Glad you got it sorted.

Strange issues with latest TWRP for device and restoring / installing?

Hello all,
I'm running the latest TWRP for this device (that fixes most of the restore/backup issues). I had wicked v2 installed and running successfully for awhile. now I'm having a strange issue.
I made a nandroid backup of my stock as well as of my wicked install and played with some other roms. (aosp ones). Went back to wicked as they are all "not there yet" and the initial restore works.
Unfortunately if I shut down or rebootI basically find myself unable to boot. It hangs on "Samsung Galaxy S4". screen and doesn't finish.
If I reboot into recovery from here and try to say, clear the dalvik or something it asks me for a password like it's encrypted, and wiping dalvik for example fails.
My nandroid did not have an encrypted FS. On top of that, I tried reflashing wicked completely from scratch and I have the same issue.
Essentially I cannot reboot my phone now once flashed.
I can get into recovery no issue but I'm stuck in a cycle here.
Thanks for any help.

bezerker said:
Hello all,
I'm running the latest TWRP for this device (that fixes most of the restore/backup issues). I had wicked v2 installed and running successfully for awhile. now I'm having a strange issue.
I made a nandroid backup of my stock as well as of my wicked install and played with some other roms. (aosp ones). Went back to wicked as they are all "not there yet" and the initial restore works.
Unfortunately if I shut down or rebootI basically find myself unable to boot. It hangs on "Samsung Galaxy S4". screen and doesn't finish.
If I reboot into recovery from here and try to say, clear the dalvik or something it asks me for a password like it's encrypted, and wiping dalvik for example fails.
My nandroid did not have an encrypted FS. On top of that, I tried reflashing wicked completely from scratch and I have the same issue.
Essentially I cannot reboot my phone now once flashed.
I can get into recovery no issue but I'm stuck in a cycle here.
Thanks for any help.
Click to expand...
Click to collapse
it wasn't just latest update, people were taking about this issue for weeks now... not sure what the fix will be I think Odin back to stock... supposedly is a TWRP problem and it doesn't happen in CWM but I heard CWM has its own share of problems...
Sent from my SGH-M919

aLdaRiS said:
it wasn't just latest update, people were taking about this issue for weeks now... not sure what the fix will be I think Odin back to stock... supposedly is a TWRP problem and it doesn't happen in CWM but I heard CWM has its own share of problems...
Sent from my SGH-M919
Click to expand...
Click to collapse
Interesting.
I was about to try odin'ing back to stock and reflashing twrp.
The only thing I wonder if may be related is when you restore a backup with TWRP it gives options of all sorts of partitions besides system/data/cache etc... preload etc. It's possible it doesn't like mucking with those.

Interesting to note: If I install a CM nightly, it will allow me to reboot. Wickedv2 or my backup of wickedv2 no go.
Testing further.

Maybe when you flashed CM it messed with a partition or something. I would suggest to ODIN back to stock and then re-root and try again.

saldebot said:
Maybe when you flashed CM it messed with a partition or something. I would suggest to ODIN back to stock and then re-root and try again.
Click to expand...
Click to collapse
Righto. Sounds like a valid idea.
Unfortunately, the download links in konane's thread are timing out for me mid download. Tragic.

Managed to snag it from another location. Flashed back to stock firmware/recovery via odin.
Letting it boot to see what it does.
EDIT:
That did it.
Restored my backup and most everything is working correctly (restoring my titanium backup of all apps now.)
Few things were messed up (swiftkey was missing a language pack etc?)
But looks like AOSP/AOKP roms do something to the partition table as you said that requires flashing back the original.
Good to know and thanks for the help!

Don't wipe system in twrp.

makomek said:
Don't wipe system in twrp.
Click to expand...
Click to collapse
Does this cause issues? Didn't know.
I found that only CM nightlies would reboot fine. restoring via odin stock official then going back and putting on wicked again seemed to work to fix it and I can now reboot in a touchwhiz based rom.

re: stuck
bezerker said:
Hello all,
I'm running the latest TWRP for this device (that fixes most of the restore/backup issues). I had wicked v2 installed and running successfully for awhile. now I'm having a strange issue.
I made a nandroid backup of my stock as well as of my wicked install and played with some other roms. (aosp ones). Went back to wicked as they are all "not there yet" and the initial restore works.
Unfortunately if I shut down or rebootI basically find myself unable to boot. It hangs on "Samsung Galaxy S4". screen and doesn't finish.
If I reboot into recovery from here and try to say, clear the dalvik or something it asks me for a password like it's encrypted, and wiping dalvik for example fails.
My nandroid did not have an encrypted FS. On top of that, I tried reflashing wicked completely from scratch and I have the same issue.
Essentially I cannot reboot my phone now once flashed.
I can get into recovery no issue but I'm stuck in a cycle here.
Thanks for any help.
Click to expand...
Click to collapse
If you want a 95% sure way of fixing it so it boots completly,
then try this, it usually always works.
Get the phone into recovery mode twrp/cwm does not matter.
Then simply do a "factory reset" and I am fairly certain that it
will boot completly, I have seen this issue so many times
already not just here in the S4 thread but also in the S3.
The factory reset will not delete any of your music, videos and pictures.
Good luck!

[Q] Android 4.3 hanging on boot

I have an I747 on T-Mobile.
I recently installed SlimBean 4.3 on it, and it started up and worked fine. But when I went to restart it, it hung on the "SlimBean" screen. Never got to the bootanimation.
I read online that there's issues when coming from another 4.3 rom, and I had previously been running CyanogenMod 10.2, although it was a nightly and it crashed, corrupting my data. I decided not to try that again.
So after that experience with SlimBean, I tried to flash BeanStalk from the T-Mobile GS3 forum. This is also a 4.3 rom, and it ran fine on my I747, except when I went to reboot. It too hung on the logo.
And yes, I have wiped internal storage, and I'm running the latest version of TWRP. I even tried to flash Samsung's stock firmware with Odin, and it worked, but it wouldn't boot (or maybe I'm overestimating how quickly TouchWiz can boot). It overrode my recovery, like I was expecting, so I flashed TWRP with Odin and then proceeded to flash SlimBean 4.3 again. Same problem.
Does anyone have a solution to this? It's been driving me crazy. I will try some other 4.3 roms and see if they're all doing this.

danielhep said:
I have an I747 on T-Mobile.
I recently installed SlimBean 4.3 on it, and it started up and worked fine. But when I went to restart it, it hung on the "SlimBean" screen. Never got to the bootanimation.
I read online that there's issues when coming from another 4.3 rom, and I had previously been running CyanogenMod 10.2, although it was a nightly and it crashed, corrupting my data. I decided not to try that again.
So after that experience with SlimBean, I tried to flash BeanStalk from the T-Mobile GS3 forum. This is also a 4.3 rom, and it ran fine on my I747, except when I went to reboot. It too hung on the logo.
And yes, I have wiped internal storage, and I'm running the latest version of TWRP. I even tried to flash Samsung's stock firmware with Odin, and it worked, but it wouldn't boot (or maybe I'm overestimating how quickly TouchWiz can boot). It overrode my recovery, like I was expecting, so I flashed TWRP with Odin and then proceeded to flash SlimBean 4.3 again. Same problem.
Does anyone have a solution to this? It's been driving me crazy. I will try some other 4.3 roms and see if they're all doing this.
Click to expand...
Click to collapse
p
I had something that sounds similar when I was trying to update from task's 4.2.2 to 4.3. Kept stopping at the kernel screen ( after the usual wiping of caches and system). Finally, someone recommended that, in addition to wiping data, that I format data as well. This basically wipes everything (i was using twrp 2.3.3.1). After doing this, I reinstalled the ROM and gapps and it works now.
Not sure this is what you experienced but it sounded similar. Before doing anything else, be sure that you have a back up and that you have removed any external sd card, should you have to go back. Good luck.

captican said:
p
I had something that sounds similar when I was trying to update from task's 4.2.2 to 4.3. Kept stopping at the kernel screen ( after the usual wiping of caches and system). Finally, someone recommended that, in addition to wiping data, that I format data as well. This basically wipes everything (i was using twrp 2.3.3.1). After doing this, I reinstalled the ROM and gapps and it works now.
Not sure this is what you experienced but it sounded similar. Before doing anything else, be sure that you have a back up and that you have removed any external sd card, should you have to go back. Good luck.
Click to expand...
Click to collapse
Yeah, I did that. I wiped everything I could and formatted data. Maybe I should try installing a different kernel?
With your issue, was it stopping on the first boot or did you get it running once then it stopped?

danielhep said:
I have an I747 on T-Mobile.
I recently installed SlimBean 4.3 on it, and it started up and worked fine. But when I went to restart it, it hung on the "SlimBean" screen. Never got to the bootanimation.
I read online that there's issues when coming from another 4.3 rom, and I had previously been running CyanogenMod 10.2, although it was a nightly and it crashed, corrupting my data. I decided not to try that again.
So after that experience with SlimBean, I tried to flash BeanStalk from the T-Mobile GS3 forum. This is also a 4.3 rom, and it ran fine on my I747, except when I went to reboot. It too hung on the logo.
And yes, I have wiped internal storage, and I'm running the latest version of TWRP. I even tried to flash Samsung's stock firmware with Odin, and it worked, but it wouldn't boot (or maybe I'm overestimating how quickly TouchWiz can boot). It overrode my recovery, like I was expecting, so I flashed TWRP with Odin and then proceeded to flash SlimBean 4.3 again. Same problem.
Does anyone have a solution to this? It's been driving me crazy. I will try some other 4.3 roms and see if they're all doing this.
Click to expand...
Click to collapse
I had the same problem since 4.3 came out. It has to do with partition tables... What i've done to correct the problem:
- Odin back to stock
- Format entire phone. (Complete wipe) + Dalvik and cache
- Odin stock with root
- Replaced TWRP recovery for CWM
- Flashed 4.3 ROM and VOILA
- I have tried every 4.3 rom ever since with no problems
Don't (Complete wipe) with Twrp recovery, it seems to mess up the partitions.
Hope this works for you
Cheers

danielhep said:
Yeah, I did that. I wiped everything I could and formatted data. Maybe I should try installing a different kernel?
With your issue, was it stopping on the first boot or did you get it running once then it stopped?
Click to expand...
Click to collapse
It loaded the first time and then rebooted, freezing on the kernel screen. I could get into recovery, and restore a previous ROM but it would hang up on 4.3. I described the steps I had taken when someone suggested reformatting data. I tried again and it is working now.
The method described in the other post may also solve your problem. I say that because I cannot update twrp to 2.6.1, at least via goo manager. I have not tried using Odin to update (yet).

I have this same as problem. It's annoying. I reflashed the rom 15 times yesterday. I'm gonna try and see if Deathstrings idea works.
Sent from my SGH-I747 using XDA Premium 4 mobile app

I managed to load a stock rom back to the phone but again, it hung on the SAMSUNG screen. Took it to "a guy" and he did a
key sequence and got it to boot. Woulnd't tell me what it was........
ANy one know???

Apocalypse487 said:
I have this same as problem. It's annoying. I reflashed the rom 15 times yesterday. I'm gonna try and see if Deathstrings idea works.
Sent from my SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This happened to me after I flashed back but formatting data got it to work (but I have had more problems with apps not installing properly but I learned how to deal with that...still cannot update TWRP via goo manager; waiting on trying it with Odin).

[Q][SOFT BRICK] Weird...

So this is the weirdest "brick" I have ever experienced. My phone was working flawlessly with a TWRP recovery and a slightly modded mostly stock ROM. I was playing around modding the stock MMS app, SecMms.apk, and flashing it through recovery. One of these flashes did not complete successfully. I got to the lockscreen, but it would not respond. And there was no network connection. So I figured something got screwed up. I rebooted into recovery and flashed a stock ROM. Boot loop. I got back into recovery and performed a factory data reset, erased everything, flashed a stock ROM. Boot loop. I downloaded a completely stock ROM with stock recovery, stock everything. Got into download mode and flashed it through ODIN. Boot loop. Well, actually, the initial boot got a screen where I could see the taskbar with time and no-service indicator; the rest of the screen was black for a minute; then I got a popup window stating that "Process system is unable to continue" and asking if I wanted to wait of close it. Then it boot looped. I tried booting without a SIM card and an external SD card - same result.
So, to recap - I can get to Download Mode, and ODIN, but anything I flash, including completely stock ROM boot loops.
I am at a loss as to what to try next. If anyone has ideas, I'm willing to try just about anything. I'm gonna take it to T-Mo store tomorrow to see if they can do anything with it...

re: phone issues
6uPMAH said:
So this is the weirdest "brick" I have ever experienced. My phone was working flawlessly with a TWRP recovery and a slightly modded mostly stock ROM. I was playing around modding the stock MMS app, SecMms.apk, and flashing it through recovery. One of these flashes did not complete successfully. I got to the lockscreen, but it would not respond. And there was no network connection. So I figured something got screwed up. I rebooted into recovery and flashed a stock ROM. Boot loop. I got back into recovery and performed a factory data reset, erased everything, flashed a stock ROM. Boot loop. I downloaded a completely stock ROM with stock recovery, stock everything. Got into download mode and flashed it through ODIN. Boot loop. Well, actually, the initial boot got a screen where I could see the taskbar with time and no-service indicator; the rest of the screen was black for a minute; then I got a popup window stating that "Process system is unable to continue" and asking if I wanted to wait of close it. Then it boot looped. I tried booting without a SIM card and an external SD card - same result.
So, to recap - I can get to Download Mode, and ODIN, but anything I flash, including completely stock ROM boot loops.
I am at a loss as to what to try next. If anyone has ideas, I'm willing to try just about anything. I'm gonna take it to T-Mo store tomorrow to see if they can do anything with it...
Click to expand...
Click to collapse
Go into recovery mode and do a complete wipe including "Factory Reset", wipe data, wipe system,
wipe cache, wipe dalvik cache and then if you have a working nandroiod backup restore it.
If you don't have a nandroid backup then go into download mode and flash the official stock
firmware for the N900T phone from http://SamMobile.com
Either one of these two options will get your phone back up and running.
Good luck!

I have already done all of the above, and...no go. Even stock firmware from SamMobile boot loops. Unfortunately, I do not have a nandroid backup, so that's the one thing I cannot do.

6uPMAH said:
I have already done all of the above, and...no go. Even stock firmware from SamMobile boot loops. Unfortunately, I do not have a nandroid backup, so that's the one thing I cannot do.
Click to expand...
Click to collapse
Google zedomax you will find his website for unrooting note 3. Will walk you thru with ever step.

It is no longer rooted after I have flashed stock firmware/ROM from SamMobile. Believe me , I have tried all the known methods of returning this phone to stock/unroot. I have flashed through recovery when I had custom recovery. I have flashed through ODIN. So far I have been unable to fix the issue. I am thinking my internal storage is corrupt, or the partition is corrupt. Anyone knows of a way to rebuild/repartition internal storage?

6uPMAH said:
It is no longer rooted after I have flashed stock firmware/ROM from SamMobile. Believe me , I have tried all the known methods of returning this phone to stock/unroot. I have flashed through recovery when I had custom recovery. I have flashed through ODIN. So far I have been unable to fix the issue. I am thinking my internal storage is corrupt, or the partition is corrupt. Anyone knows of a way to rebuild/repartition internal storage?
Click to expand...
Click to collapse
Did you try the "boot loop fix" flashable? It's essentially a script that sort of recreates the efs partition in recovery. It's been linked a few times in the twrp thread, and there may be a thread dedicated to the topic (search for "brick loop") - I don't have the links handy though, apologies.

The mans right^ that helped me out through my "soft brick". Totally out of the blue. Wasnt even messing around with anything I didnt knew I was doing
Sent from my SM-N900T using Tapatalk

Anybody has a link? I've searched, but there's nothing specific to Note 3 TMO...

6uPMAH said:
Anybody has a link? I've searched, but there's nothing specific to Note 3 TMO...
Click to expand...
Click to collapse
The method is outlined in the OP of this thread but the flashable version of what is outlined there can be found in this thread - hope that helps!

Thanks. I'll give it a go after work.
UPDATE: All is well in the world again. Thanks everyone for all your help. Thanks dwitherell ! The thread you pointed me to was the solution!

Stuck on "Samsung note 2"

Hey guys,
I was running liquid smooth ROM along with Agni kernel. Some of the apps were FC so I wanted to refresh the ROM by wiping and flashing it back. I mistenly hit softreboot instead of recovery. The phone got stuck on the loading liquidrom screen forever.
Went into recovery, made a backup, wiped everything out. Restored the backup.. still stucked on loading screen.
Went back into recovery, wipe everything, I mean everything, even external SD.
When a came to boot the phone, recovery told me there was no ROM installed.. duh!
So I grabbed the stock firmware from sammobiles and went with Odin to flash it. But I'm getting stock on NAND write start. I tried a second computer, with lastest Kies installed. Same stuff.
Is there a reason why the stock firmware just won't flash?
I'm gonna need help on this one cause I'm out of ideas.
Thank you

DanKicker said:
Hey guys,
I was running liquid smooth ROM along with Agni kernel. Some of the apps were FC so I wanted to refresh the ROM by wiping and flashing it back. I mistenly hit softreboot instead of recovery. The phone got stuck on the loading liquidrom screen forever.
Went into recovery, made a backup, wiped everything out. Restored the backup.. still stucked on loading screen.
Went back into recovery, wipe everything, I mean everything, even external SD.
When a came to boot the phone, recovery told me there was no ROM installed.. duh!
So I grabbed the stock firmware from sammobiles and went with Odin to flash it. But I'm getting stock on NAND write start. I tried a second computer, with lastest Kies installed. Same stuff.
Is there a reason why the stock firmware just won't flash?
I'm gonna need help on this one cause I'm out of ideas.
Thank you
Click to expand...
Click to collapse
Please see this thread I started yesterday: http://forum.xda-developers.com/gal...days-update-soft-bricked-phone-t2939649/page1. Many of us are having the same issue, and I was able to fix my Android last night.
Please spread the word.