After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Did you wipe data and cache when you flashed the new rom?
nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM
cobraboy85 said:
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM
Click to expand...
Click to collapse
thanks for the info, will try this all out soon. I've been flashing roms for years now and have never run into anything like this, and as previously stated, this didn't occur solely with your rom which has me thinking something has happened to the phone itself. will get back to you soon and once again thank you
chucktdriscoll said:
Did you wipe data and cache when you flashed the new rom?
Click to expand...
Click to collapse
of course, wiped data, cache, & delvik
nyyankees1237 said:
of course, wiped data, cache, & delvik
Click to expand...
Click to collapse
my point is...
coming from a cm based ROM, or aokp, whatever you said... you would want to format system as well.
nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
I was having some of the same issues. I downloaded XquiziT's Superwipe and ran it by installing from external sd card. I ran it three times to clear everything out, then I wiped data, cache and the rest three times.
No probs for me after that.
Will definitely give that a try as well! Thank you! Will post my results when the holiday is over.
Happy thanksgiving
Sent from my SGH-T999 using xda app-developers app
Related
So, been a couple weeks been trying to flash CM10 ROMs, Paranoid, AOKP and CYANO, Everytime i flash I wipe everything as instructed and when it reboots it just hangs on the cyanogem boot image with the wheel spinning and does nothing. Not even a boot loop?! I let it sit for up to a half hour before and still nothing. But I can go and restore my old rom (not CM!) and works great..and if I flash a a new TW rom it flashes correctly.
Any ideas. I am on CWM when I flash. I also tried to flash TWRP and that would not take as well and had to go back to CWM.
Things I would check:
Verify MD5 tags of the roms your flashing when you download
Try wiping cache/dalvik/system and doing a factory reset after you have a successful flash
Question I have for you...
Have you tried unrooting and rooting again?
TWRP and CWM should both work, but have you ran the darkside scripts if using CWM? > http://forum.xda-developers.com/showthread.php?t=1477955
Lastly - I have heard people needing to reflash several times before it "takes" which it sounds like maybe you've tried & I realize these may be very basic things for you but you never know hopefully someone can help the more info you provide.
ldd_recoil said:
Things I would check:
Verify MD5 tags of the roms your flashing when you download
Try wiping cache/dalvik/system and doing a factory reset after you have a successful flash
Question I have for you...
Have you ever successfully loaded a custom rom on this particular phone?.... because you may have improperly rooted
TWRP and CWM should both work, but have you ran the darkside scripts if using CWM? > http://forum.xda-developers.com/showthread.php?t=1477955
Click to expand...
Click to collapse
I am on a custom rom now and everything is fine..but when I try to flash anything other than a Touchwhiz rom it seems to fail. I had paranoid running for a little while but I could not access my external sd so went back to my Jedi Mind Trick rom and everything was fine...so I decided to try a different paranoid thinking the issue was with this specific rom and it would not boot..went back to JMT and then tried aosp cm10 rom thinking and it wouldn't boot.
i have tried everything you have suggested except for the Factory Reset after the flash. Never really check the MD5 though. Might give it a try later on when I get bored with this rom again.
Thanks,
T
Sorry, reread your post now that I have the right context... Try unrooting and rerooting if you continue to have new rom flash issues.
toreone said:
So, been a couple weeks been trying to flash CM10 ROMs, Paranoid, AOKP and CYANO, Everytime i flash I wipe everything as instructed and when it reboots it just hangs on the cyanogem boot image with the wheel spinning and does nothing. Not even a boot loop?! I let it sit for up to a half hour before and still nothing. But I can go and restore my old rom (not CM!) and works great..and if I flash a a new TW rom it flashes correctly.
Any ideas. I am on CWM when I flash. I also tried to flash TWRP and that would not take as well and had to go back to CWM.
Click to expand...
Click to collapse
Solution is Simple.... When it hang in the cyanogenmod boot image with the wheel spinning just switch off -> Go to recovery -> install the DarkSide Cache Wipe.Zip then see the magic.... :good:
srikanth.t989 said:
Solution is Simple.... When it hang in the cyanogenmod boot image with the wheel spinning just switch off -> Go to recovery -> install the DarkSide Cache Wipe.Zip then see the magic.... :good:
Click to expand...
Click to collapse
Thanks, i will give this a try next time i flash...and i'll report back. This happened with a few different roms...this should fix those too!? also, I am pretty sure I ran the Darkside before I did first boot...should I have waited?
EDIT::: THIS WORKED...IT WAS HUNG UP ON BOOT IMAGE..FOLLOWED INSTRUCTIONS ON TOP AND BINGO!!!! I SAW THE MAGIC
toreone said:
Thanks, i will give this a try next time i flash...and i'll report back. This happened with a few different roms...this should fix those too!? also, I am pretty sure I ran the Darkside before I did first boot...should I have waited?
Click to expand...
Click to collapse
I was running into this same issue until I switched from CWM to the most recent TWRP, it's super easy just install Goomanager app and hit menu button >install OpenRecoverScript. After switching I haven't needed the Darkside script and I've yet to get a single hang at boot. Hopefully it helps!
cluckkillerb said:
I was running into this same issue until I switched from CWM to the most recent TWRP, it's super easy just install Goomanager app and hit menu button >install OpenRecoverScript. After switching I haven't needed the Darkside script and I've yet to get a single hang at boot. Hopefully it helps!
Click to expand...
Click to collapse
I actually tried this yesterday and it went through the motions and when I restarted into recovery it was just like a blue background with the Team Win on it but never made it past that...so I had to flash back to CWM through Odin to get it to be able to flash again..
cluckkillerb said:
I was running into this same issue until I switched from CWM to the most recent TWRP, it's super easy just install Goomanager app and hit menu button >install OpenRecoverScript. After switching I haven't needed the Darkside script and I've yet to get a single hang at boot. Hopefully it helps!
Click to expand...
Click to collapse
After doing this try downloading quickboot to boot into twrp recovery, if that doesn't help you might need to flash back to stock/re-root and start from square one =/
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.
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!
Hello,
I can not flash any ROM to my GT-P5210 Tab anymore.
I was on BinDroid ONE P5210 LITE V3.0.0, but since it is discontinued
and 2 other ROMs rolled out over the past days I wanted to give it a try.
- went back to stock with official firmware from "sammobile" for my device,
- flashed TWRP with Odin 3.07
- flashed ROOT with Odin
- went to recovery did factory reset + dalvik/cache (
- flashed new ROM (neither ROM Pimpdroid or Grievous is working)
after flashing Tab goes into a bootloop to recovery. First boot after flash takes some time in the Galaxy Tab3 Logo but in the end it reboots into TWRP. I have tried CWM too with the same results.
I am not totaly new to flashing, did it with my I9000 and now with my I9300 int. but with this Tab3 now I am lost.
Any ideas are much appreciated.
regards and sorry for my english its not my native tongue
zerodv8 said:
Hello,
I can not flash any ROM to my GT-P5210 Tab anymore.
I was on BinDroid ONE P5210 LITE V3.0.0, but since it is discontinued
and 2 other ROMs rolled out over the past days I wanted to give it a try.
- went back to stock with official firmware from "sammobile" for my device,
- flashed TWRP with Odin 3.07
- flashed ROOT with Odin
- went to recovery did factory reset + dalvik/cache (
- flashed new ROM (neither ROM Pimpdroid or Grievous is working)
after flashing Tab goes into a bootloop to recovery. First boot after flash takes some time in the Galaxy Tab3 Logo but in the end it reboots into TWRP. I have tried CWM too with the same results.
I am not totaly new to flashing, did it with my I9000 and now with my I9300 int. but with this Tab3 now I am lost.
Any ideas are much appreciated.
regards and sorry for my english its not my native tongue
Click to expand...
Click to collapse
did u try root check app to c if u r truly rooted? is ur su updated? if so try reflashing the recovery...n the root file. do u have the stock kernel?
THink I Got a fix
This worked for me. The TWRP does NOT actually wipe anything. go to settings in whatever rom you are running, and do a factory data reset from there. Let it wipe all app data and EVERYTHING. Then go through the steps to install whichever ROM you want. It worked for me!! Post back and let me know if it worked for you too. I tried for 3 days to install anything, and this is the only thing that worked.:victory:
Tquarter said:
This worked for me. The TWRP does NOT actually wipe anything. go to settings in whatever rom you are running, and do a factory data reset from there. Let it wipe all app data and EVERYTHING. Then go through the steps to install whichever ROM you want. It worked for me!! Post back and let me know if it worked for you too. I tried for 3 days to install anything, and this is the only thing that worked.:victory:
Click to expand...
Click to collapse
ok did read your post before trying to flash. i lost my back up and as well as my emmc. so i need a stock firmware only problem I now have is downloading one. Three quarter of links r dead and the three i have tried have had errors. Can you help me anyone with a google drive or box download of an unknown region stock firmware so I can breathe light in t o my brick please
https://db.tt/63atdfRZ Here ya go!
I'm uploading a stock firmware that can be flashed using ODEN. I have not tried this file, I just downloaded it, before I flashed anything, in case something went wrong. I'll post the link when it finishes uploading. Good luck! Post back and let us know how it went.
solved
Tquarter said:
This worked for me. The TWRP does NOT actually wipe anything. go to settings in whatever rom you are running, and do a factory data reset from there. Let it wipe all app data and EVERYTHING. Then go through the steps to install whichever ROM you want. It worked for me!! Post back and let me know if it worked for you too. I tried for 3 days to install anything, and this is the only thing that worked.:victory:
Click to expand...
Click to collapse
I tried your method and it worked. Another thing that works is first thing when you enter TWRP check if system is mounted, if not tick mount and then wipe the way installation of the rom suggests. This worked for me too. Thanks for ur time and the fish
Oh cool, I'm glad to help. I also tried to manually mount system, but untill I got that first ROM installed, it just un-mounted itself again. I hope these problems will be sorted out. Both recoveries act choked down somehow. (TERP, CWM) Looks like "source manifest CM 10.2 "thread is making exciting progress. I can't stop watching it. Most of it is over my head, but google helps me, in trying to grasp what they are saying.
Tquarter said:
Oh cool, I'm glad to help. I also tried to manually mount system, but untill I got that first ROM installed, it just un-mounted itself again. I hope these problems will be sorted out. Both recoveries act choked down somehow. (TERP, CWM) Looks like "source manifest CM 10.2 "thread is making exciting progress. I can't stop watching it. Most of it is over my head, but google helps me, in trying to grasp what they are saying.
Click to expand...
Click to collapse
can someone recommend a clean rom for gt-p5210
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!