Hi My GNex is rooted.... and I've been running a Modoco ROM for 3 months with no problems. Recently I flashed his latest after a wipe and reset.... it worked fine for a day until this morning when I get continual reboots!
I wiped again completely tonight and installed AOKP ROM and it was fine for an hour or so, now its started rebooting again... what should I do?
Should I try and return it to Samsung... I'm guessing I'll have to flash stock and unroot (if thats possible?)
Thanks
What stage does it get to before it reboots again? (Google Logo or Animated splash or in the OS?)
mine on stock done it and now on google logo, re flashing stock images now, takes the piss abit.
These things happen. Frequent nandroid backups are highly recommended
It boots to the OS, then its fine for 30 minutes... reboots, then typically the reboots start to become more and more common!
I've just tried the superwipe script and reflashed again. I'll try going to stock otherwise.
I did a Nandroid by when trying to recover it said there was a check-sum error or something!
Did it say there was an error restoring data?
This happened to me, essentially the data partition had become corrupted, and no amount of custom ROM flashing would help. I had to flash stock images to fix, as I could not restore any back ups I had made.
Make sure you back up your SD card contents, as it's wiped during a factory image flash.
Sent from my Galaxy Nexus using XDA App
I think that's what I'm going to have to do
Though I don't get any messages saying there's an error restoring data!
It sounds like you have an issue with your recovery. Reflash CWM see if that fixes it and make sure its the right version GSM or CDMA!. I'm 90% sure that will fix it. (After that flash rom and wipe data.)
If its a corrupted data partition then MAYBE fastboot oem lock and then oem unlock may fix it.
Just back up your sdcard contents first.
If that doesn't do it then flash the stock images.
Related
I was running Starburst v1.9 and saw a thread on Themes & Apps with ICS transitions. I downloaded both just in case (ICS Transitions & Revert back to stock). I went into Root Explorer and checked my Clockwork/Backup and saw that I had a backup in there. I booted into Recovery and flashed the theme transitions for ICS zip and thus problem began.
I then went to restore to restore the backup and it seems like that file was corrupted because it wouldn't restore. I ended up flashing the revert zip file and wiping my rom. It doesn't boot but I can still get into recovery. I believe that the issue is that the theme was made for the v1.9.5 and I had v1.9 of Starburst.
I was messing around with it and I was able to boot back in and click on the Android to set it up. After a while the phone will go crazy and the screen will flicker on and off. The buttons at the bottom became useless. How can I recover from this.
** I used my friend's Sensation and downloaded v.1.9.5 and threw it on my SD. I booted into Recovery and flashed the ROM and it still won't boot up. Any suggestions? **
The phone booting up I think was a luck of the draw thing. Since then the phone has not been able to boot into the actual ROM. I've been without a phone since yesterday and I'm planning on going into the Sprint store and getting it swapped.
Did you wipe system, data, cache, and dalvik?
THEN reflash the rom?
Yes. I was a flashaholic on my Evo.
I notice another thread in q&a with people the same issue as mines. I'm lost and haven't had my phone working for two days now.
Here's what I did:
Delete system, wipe factory reset, cache and dalvik, flashed ROM.
Could it be kernel related? I'm confused. I have a wedding tomorrow and this couldn't have happened at a worse time. Coincidentally something happened on my At&t dumb phone so I'm phoneless.
stupid suggestion...is your battery low?
with the evo it would see corrupted if the battery was low. may not apply, but hey its a shot.
if you cant figure out, theres always Odin to cure your issues
ReDL the ROM and reflash. Try mounting USB storage while in recovery. Alternatively, Odin the stock .tar for a full refresh.
If you've already retired reflashing I'd go with odin back to stock
Sent from my SPH-D710 using xda premium
here is the link for a format all then you can try and flash a rom again if you like. If not I would do like previously suggested and flash return to stock in Odin- link here
playya said:
here is the link for a format all then you can try and flash a rom again if you like. If not I would do like previously suggested and flash return to stock in Odin- link here
Click to expand...
Click to collapse
Awesome. The wedding made me forget about my phone but now that it's over I'm missing it.
I will flash to stock and re-root.
Sent from my Nexus S 4G using XDA App
I'm running Arhd with the stock kernels. Have been using it with no issues since the day I got it.
Wake up this morning to find it getting to the google logo and then rebooting. I can get into the boot loader and cwm, however if I try a backup it says 'error while making a backup image of data"
I can't restore a backup either as I get the same error where I can't restore /data.
I managed to wipe all data and flash a new rom but that still loops
Any ideas?
EDIT: Flashed the stock Google image and it seems to work :/
Evostance said:
I'm running Arhd with the stock kernels. Have been using it with no issues since the day I got it.
Wake up this morning to find it getting to the google logo and then rebooting. I can get into the boot loader and cwm, however if I try a backup it says 'error while making a backup image of data"
I can't restore a backup either as I get the same error where I can't restore /data.
I managed to wipe all data and flash a new rom but that still loops
Any ideas?
EDIT: Flashed the stock Google image and it seems to work :/
Click to expand...
Click to collapse
now flash an updated version of cwm and on to another rom... hopefully.
I've had this same problem before. Twice. What in the 7th circle of hell causes this randomness? I didn't flash anything, just tried to read a text and same thing. Is there anyway to recover without typing in 50 million lines of coding to flash stock google image and lose everything again?
Rabidaries said:
I've had this same problem before. Twice. What in the 7th circle of hell causes this randomness? I didn't flash anything, just tried to read a text and same thing. Is there anyway to recover without typing in 50 million lines of coding to flash stock google image and lose everything again?
Click to expand...
Click to collapse
Use a toolkit
http://forum.xda-developers.com/showthread.php?t=1392310
Sent from my GNex {GSM} T-Mobile
Just got a brand new N7100 today. Do my usual thing as with all my phones, flash CWM, root, flash custom rom (Omega v8.0). Changed kernel to Note2Core (OC, NOT EXTREME VERSION WITHOUT FSYNC), was running for a bit then it rebooted itself.
After reboot, phone won't run, so I go to do a full system wipe. Except now I can't wipe /data. Tried 3 different CWMs including TWRP (TWRP doesn't even start, just shows load screen then reboots).
Flashed stock ROM with ODIN including .PIT but the /data isn't being cleared, I can't clear it in any way. Only way to get the phone working now is stock ROM through ODIN but it boots up with a bunch of messed up stuff and I can't factory reset.
I have tried scanning for EMMC Brickbug but there are no errors. This one has got me stumped, I know my way around recoveries and android etc. but can't for the life of me figure out what I can do to fix this.
Don't really want to send in for warranty as I probably have a flashcounter (I will try to flash a rooted ROM through ODIN and triangleaway..)
Hoping since there's no EMMC brickbug triggered from the scans, that there's some way to fix this. I thought flashing PIT would wipe the /data partition but obviously not.
Any ideas? Would be most appreciated.
Thanks
I'm having the exact same issue on my N7105. It was working fine for days after flashing, then all of a sudden it rebooted and all user apps were gone. When I tried to reinstall from TB, I got an error on each app that it had stopped working.
I tried to reflash the ROM with full wipe, but CWM restarts when it tries to wipe /data.
I'm using this ROM http://forum.xda-developers.com/showthread.php?t=1985200 with Note2Core v2.10.
there is probably an issue with the internal sd card(hardware part).
or maybe you have done something wrong.
try using adb to format it.
I was finally able to format the /data folder by doing a factory reset, now it works in CWM and flashing a ROM doesn't fail when choosing the full wipe installation.
I'm not sure what the problem was. A faulty internal SD card would still be having this problem and incorrect flash method would show problems straight away, not 5 days later, right?
Hi guys,
I have the same issue, anything related to the partition /data is causing me troubles since I first tried to wipe it when I wanted to install CM9.1. (and I had stock ICS 4.0.4 at the time...)
Do you think it is the mmc bug ?
I can enter DL mode but when I try to flash stock rom, it just remains at the animated boot logo for hours...
Tried also to flash rom (with CODE, MODEM, CSC) and Odin stays stuck when starting DATA...
Any luck on your side ?
Wtf this is n7100 thread and forum. How can you get 4.0.x on it
Sent From Samsung's Galaxy Note II Using Internet
i think u guys just hardbricked ur n7100..maybe try to go samsung centre..can try ask for warranty
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!
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!