(Q) (Help) Problems flashing Roms - can't mount system - Nexus 5 Q&A, Help & Troubleshooting

Let me start by saying that I am not new to flashing Roms on my devices, that being said I have never had an LG phone till now.
When I go in to Twrp and try to flash a new rom or even wipe it tells me it can't mount system. I've tried fixing permissions but nothing helped. I ended up having to use Nexus tool to restore phone to stock. (lost everything on phone)
I got the phone rooted and flashed carbon rom but decided that I wanted to flash a rom with 4.4.1 and same thing happened with phone not able to mount system. This time I was able to restore a Twrp backup I had and then flash the stock 4.4.1 rom available on this forum.
Is there something with this phone that is different then flashing on others? Can't seem to flash more then once without going back to stock? I have 2 nexus 7's 2012 & 2013 models and everything seems fine on these have flashed numerous Roms without a hitch.
I came from GS3 and have Asus prime, Motorola, HTC and just about every other manufacturers device in my house. Why is this one giving me so much issues.
Also battery won't charge past 77% now. Any ideas?
Sent from my Nexus 5 using XDA Premium 4 mobile app

nelomen said:
Let me start by saying that I am not new to flashing Roms on my devices, that being said I have never had an LG phone till now.
When I go in to Twrp and try to flash a new rom or even wipe it tells me it can't mount system. I've tried fixing permissions but nothing helped. I ended up having to use Nexus tool to restore phone to stock. (lost everything on phone)
I got the phone rooted and flashed carbon rom but decided that I wanted to flash a rom with 4.4.1 and same thing happened with phone not able to mount system. This time I was able to restore a Twrp backup I had and then flash the stock 4.4.1 rom available on this forum.
Is there something with this phone that is different then flashing on others? Can't seem to flash more then once without going back to stock? I have 2 nexus 7's 2012 & 2013 models and everything seems fine on these have flashed numerous Roms without a hitch.
I came from GS3 and have Asus prime, Motorola, HTC and just about every other manufacturers device in my house. Why is this one giving me so much issues.
Also battery won't charge past 77% now. Any ideas?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
the battery percentage should be an issure with your custom rom, for the mounting problem... are you using the latest version of twrp? - and maybe you could try cwm ( i recommend that always ) - also, no there isn't a difference in flashing things on an lg device, as log it's an nexus one

nelomen said:
Let me start by saying that I am not new to flashing Roms on my devices, that being said I have never had an LG phone till now.
When I go in to Twrp and try to flash a new rom or even wipe it tells me it can't mount system. I've tried fixing permissions but nothing helped. I ended up having to use Nexus tool to restore phone to stock. (lost everything on phone)
I got the phone rooted and flashed carbon rom but decided that I wanted to flash a rom with 4.4.1 and same thing happened with phone not able to mount system. This time I was able to restore a Twrp backup I had and then flash the stock 4.4.1 rom available on this forum.
Is there something with this phone that is different then flashing on others? Can't seem to flash more then once without going back to stock? I have 2 nexus 7's 2012 & 2013 models and everything seems fine on these have flashed numerous Roms without a hitch.
I came from GS3 and have Asus prime, Motorola, HTC and just about every other manufacturers device in my house. Why is this one giving me so much issues.
Also battery won't charge past 77% now. Any ideas?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I would try: fastboot flash cache cache.img. use cache.img from the 4.4 factory image.

golem95 said:
the battery percentage should be an issure with your custom rom, for the mounting problem... are you using the latest version of twrp? - and maybe you could try cwm ( i recommend that always ) - also, no there isn't a difference in flashing things on an lg device, as log it's an nexus one
Click to expand...
Click to collapse
Thanks for the response. The battery issue has resolved itself by running battery down to 0%and recharging.
I will give CWM a try. Maybe.
I've noticed that before I started flashing Roms I ran stock go 2 weeks and was consistently getting almost 5 hours of screen time. Coming for the GS3 I was amazed but since I've started using custom rooms I'm barely getting 3.
Going to test this out some before I do too much more flashing.
Sent from my Nexus 5 using XDA Premium 4 mobile app

I've used cataclysm rom with franko kernel and have gotten 24 hours with over 7 screen on

nelomen said:
Thanks for the response. The battery issue has resolved itself by running battery down to 0%and recharging.
I will give CWM a try. Maybe.
I've noticed that before I started flashing Roms I ran stock go 2 weeks and was consistently getting almost 5 hours of screen time. Coming for the GS3 I was amazed but since I've started using custom rooms I'm barely getting 3.
Going to test this out some before I do too much more flashing.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
wow, 5hrs i get barely 3h +/-

golem95 said:
wow, 5hrs i get barely 3h +/-
Click to expand...
Click to collapse
Check it out. That was on stock in the first couple of days of getting the phone. But once I started flashing Roms it has only been about 3. Going to try stock for another while see if I can reproduce the amazing battery life I first had.
Sent from my Nexus 5 using XDA Premium 4 mobile app

Maybe u must change ur cwm
Sent from my GT-S5360 using xda app-developers app

nelomen said:
Check it out. That was on stock in the first couple of days of getting the phone. But once I started flashing Roms it has only been about 3. Going to try stock for another while see if I can reproduce the amazing battery life I first had.
(not sure if pics attached but they are of my 5hrs screen time)
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my Nexus 5 using XDA Premium 4 mobile app

nelomen said:
Let me start by saying that I am not new to flashing Roms on my devices, that being said I have never had an LG phone till now.
When I go in to Twrp and try to flash a new rom or even wipe it tells me it can't mount system. I've tried fixing permissions but nothing helped. I ended up having to use Nexus tool to restore phone to stock. (lost everything on phone)
I got the phone rooted and flashed carbon rom but decided that I wanted to flash a rom with 4.4.1 and same thing happened with phone not able to mount system. This time I was able to restore a Twrp backup I had and then flash the stock 4.4.1 rom available on this forum.
Is there something with this phone that is different then flashing on others? Can't seem to flash more then once without going back to stock? I have 2 nexus 7's 2012 & 2013 models and everything seems fine on these have flashed numerous Roms without a hitch.
I came from GS3 and have Asus prime, Motorola, HTC and just about every other manufacturers device in my house. Why is this one giving me so much issues.
Also battery won't charge past 77% now. Any ideas?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
When your in TWRP and your trying to flash a ROM try restarting recovery by pressing reboot then reboot recovery then flash the ROM
Sent from my Nexus 5 using Tapatalk

OptimusVDarwin said:
When your in TWRP and your trying to flash a ROM try restarting recovery by pressing reboot then reboot recovery then flash the ROM
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks, I've never tried that but am willing to give it a shot after I finish my testing of battery life on stock compared to custom roms.
For some reason I am getting about 2 hours more screen time with stock then with custom rom.
Sent from my Nexus 5 using XDA Premium 4 mobile app

Related

[Q] Nexus S keep's restarting itself.

Good day all, I recently got a Nexus S for free from my brother becuase it keep's restarting its self. The phone was rooted with Cyanogen rom, and from what he told me has been dropped a couple of times. With this all being said, he went ahead and flashed a fresh rom on there (unk which one) and wiped everything etc.. Anyone exp this type of problem before and if so what can be done to fix it?
King350z said:
Good day all, I recently got a Nexus S for free from my brother becuase it keep's restarting its self. The phone was rooted with Cyanogen rom, and from what he told me has been dropped a couple of times. With this all being said, he went ahead and flashed a fresh rom on there (unk which one) and wiped everything etc.. Anyone exp this type of problem before and if so what can be done to fix it?
Click to expand...
Click to collapse
Lol I think you over clocked it on the minimum ... try the minimum at 800m ... or if anything flash a new rom.. its probably the rom itself
Sent From In between Your Moms Boobies
Try another (stable) rom? (no development rom)
Wipe everything.
And yes, probably its underclocked/overclocked too high.
I would like to flash a rom but once I turn it on it keeps force closing everything and I am unable to do anything on the phone, It boots into recovery mode just fine though
Sent from my HTC Vision using XDA App
King350z said:
I would like to flash a rom but once I turn it on it keeps force closing everything and I am unable to do anything on the phone, It boots into recovery mode just fine though
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Good news, you flash your ROM from recovery. Download the package, boot into recovery. Mount the SD card and push or push using adb push. Flash the zip from CWM.
my friend purchased the phone yesterday and he is on the latest Official version (2.3.6) and the phone keeps rebooting!!!
is this normal?? there must a problem!
3mar84 said:
my friend purchased the phone yesterday and he is on the latest Official version (2.3.6) and the phone keeps rebooting!!!
is this normal?? there must a problem!
Click to expand...
Click to collapse
Wipe data/factory reset from recovery if it's a used phone.
If he just bought it return it... thats easy
If he rooted it and changed the rom -- put it back to stock or put a new rom on it
I personally found that most of my restarts were due to me trying to pull the stock launcher into an unfamiliar rom. Make sure (if you are using Titanium backup) to only load apps not system *unless you are trying to go back to the same rom*
good luck
First check if he overclocked too much or underclocked too much. Put it to normal.
Alternatively you can just flash another rom. Before flashing remember to wipe everything
Goodluck!

[Warning] Ice Cream Sandwich OS Bricks

This thread is now irrelevant as Jellybean is available for the device.​
The old post can be found below:
As of right now be sure that you all are extemely cautious when trying to flash any type of ICS package (be it firmware, a ROM, or any type of system running it). Our tablet may have an issue with ICS as many other galaxy devices have. A bug currently exists that corrupts the mounting of the data partition on the device which *MAY* lead to a permanent hard bricking of your device.
This is currently a very RARE issue, however, those who are not well educated in Android development and that do not know how to 100% reset their tablet should refrain from flashing any type of ICS ROM or ODIN package.
If you have already flashed an ICS ODIN package or are running CM9 safely and have been for a good amount of time, then my guess is that this issue will not effect you, BUT it may strike you at any given time!
For those of you who insist on upgrading to ICS, *PLEASE* backup your entire ROM and make sure that you have the stock HC ODIN package. Although it probably won't help having them if you are hard bricked.​
A quote from an effected user:
ringnutz said:
I also had the can't mount data problem, I tried for 3 days to get it to work. I ended up sending it back to Samsung after reverting everything to stock. I was on cm9 though and one night it just started bootlooping while i was asleep. I.e. it would fully boot then restart after 5 seconds or so. So I tried reverting to stock and trying again, which is when I got the can't mount data issue. I literally tried every combination of wiping, recovery, Odin/heimdall, and the only thing that would get past the Samsung logo was cm9, which would just stick at the boot animation forever. I got tired of messing with it and thought it could have been a hardware problem, so I sent it back under warranty
Sent from my myTouch 4g via Tapatalk
Click to expand...
Click to collapse
A quote from an effected user:
daviddavid123 said:
i installed cm9 and ics 4 then my tab hard bricked and internal memory damaged
Click to expand...
Click to collapse
A quote from an effected user:
krbabb said:
I dont have posting privleges in the developer forums but i thought i would let you know whats up with my tab.
Rooted it, got cwm on it and flashed cm9. Worked for about a week without issue then started the bootlooping issues. I couldnt even wipe the data in recovery.
Used odin to go back to stock HC according to your instructions. Then i thought it bricked cause it just got stuck on the default screen showing galaxy tab. Tried installing HC a few more times but it never booted.
Tried one more time but now with the stock ics. Still nothing so i gave up.
Only thing is i couldnt power off. I planned to let the battery die. So it just sat on the default gakaxy tab screen and about 30 minutes later it showed the samsung boot animation.
I let it sit for another half hour with samsung pulsing. Nothing. So i reboot into recovery (stock) which i couldnt even get to before now, wipe everything like 5 times then reboot the device.
Booted up and works like a charm. I thought this thing wad gone.
Not sure if the stock ics tar file did the trick but let everyone know that mine came back to life. It possible other devices could be bricked but maybe there is a chance for some people.
Sent from my GT-P6210 using xda app-developers app
Click to expand...
Click to collapse
If you have flashed ICS and you have bricked your device I am sorry. I know there are a few people out there who have....
To conclude, everybody please be careful about tinkering with your device. I know ICS has great speed enhancements and all, but as of right now your box of ice cream sandwiches may or may not be poisoned.​
For the daredevils:
CM9 [View thread]
Guide to flashing ICS [View thread]
EDIT: Our case is not the same as the other galaxies.... Ours effects the data partition while theirs effects their emmc... I'm assuming ours may be a bug with the firmware installation / recovery as it was with theirs however I'm not sure why it is effecting users on CM9....
EDIT 2: We should all be cautious and NOT wipe at all using Samsung's ICS Recovery. I was chatting with aorth and he suggested that that may be the cause of the issue. His recovery (or the one I posted in my guide) are safe to wipe on.
EDIT 3: I guess we also have reports of the emmc being corrupted as well...
Just don't wipe data/factory reset using recovery ICS (RECOVERY 3e). Use recovery 5.5.0.4 or 6.0.x.x......only you wipe for up new rom, everything will be OK.
Sent from my GT-P6200 using Tapatalk 2
Yeah, i experienced this type of total brick. I flashed p6200 ics firmware with mobile odin and than did factory reset in ics recovery mode. I think this was the reason of hard brick. After some time tablet did shut down and didn't turn on. Service fixed the problem, they said that main board died.
Ignore this post.
StrumerJohn said:
That's not the case I afraid...
Click to expand...
Click to collapse
I really don't think it was a problem with upgrading. I had been on cm9 for over a month, then I woke up one morning and it was bootlooping. I got all the can't mount data errors afterwards, so it's either a hardware problem or cm9 is somehow magically corrupting the /data partition. I hadn't even installed anything recently
EDIT: Samsung just sent me the email that the repair is finished, they replaced the main board, so it definitely was a hardware problem.
Sent from my myTouch 4g via Tapatalk
This issue was brought up a couple months ago by aorth, I think its in his CM9 thread or in one of the rooting or CWM threads. I don't think it is an issue that will be going away any time soon as Samsung isn't in any hurry to fix it, that is if they even can or want to.
Using stock ICS for almost 3 weeks now.
I was backing up and restoring all of the partitions via CWM 6.0.1.0 two times.
Nothing weird happening for the moment.
I use the ics wipe/factory reset and I don't have any problem, I have 6210 .
Well, aorth entioned sth like this before, here his post:
aorth said:
Maybe you guys have heard, but some early ICS ROMs for Galaxy Note and other similar Galaxy S II variants have triggered hard bricks due to faulty MMC firmware handling erase commands improperly. I never bothered to read up about the issue until now, but it looks like we should also be careful.
Chainfire just released a tool to print out whether your device has a known-bad firmware revision, Got BrickBug?. As you can see, my device has firmware revision 0x19. This revision has been known to cause hard bricks on other devices using Samsung ICS ROMs.
CM9 is safe (Entropy512 haxx0red the kernel), but we should be careful.
Click to expand...
Click to collapse
I got this bad firmware revision too, but iam still safe after 2 months
Sent from my GT-P6200 using xda app-developers app
Bad2hold said:
Well, aorth entioned sth like this before, here his post:
I got this bad firmware revision too, but iam still safe after 2 months
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
I'm not sure if I had the bad one, but mine worked fine for months too. Then out of the blue it bootlooped and when I tried to fix it by reverting to stock, I got the error. Hopefully when it comes back it will have a different firmware revision (if that's what the problem was)
Sent from my myTouch 4g via Tapatalk
I flashed my tab with 'P6200OXALQ1_P6200XXLQ1_P6200XXLQ1' on 19th July - so far nothing has happened.... and it is working much faster than the 3.2 Honeycomb it came with.:fingers-crossed: Using Stock kernel/recovery... only rooted using temporary touch recovery.
02xda2 said:
I flashed my tab with 'P6200OXALQ1_P6200XXLQ1_P6200XXLQ1' on 19th July - so far nothing has happened.... and it is working much faster than the 3.2 Honeycomb it came with.:fingers-crossed: Using Stock kernel/recovery... only rooted using temporary touch recovery.
Click to expand...
Click to collapse
If you flashed it using Mobile Odin that's normal because it uses its own recovery.
Ok, so what's the verdict? This bug sounds very scary.
Given that I'm running a stock ICS flashed via ODIN, should I be running:
-Stock recovery
-CWM
-Something else
to avoid bricking while factory reset?
I also use mobile Odin to flash ics and no problem. So, could you say that with Mobile Odin are safe from this problem?
Just read this http://www.reddit.com/r/Android/comments/xj2hd/i777_superbrick/, seems some of the things said could be relevant for us.
I have a galaxy note and Entropy who is dealing directly with samsung on this issue has a thread over on the galaxy note page. Lots of information over there.
I use the free emmc bug check app by vinagre https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check&hl=en to check my samsung devices on ics. Not entirely sure that the same case applies for the note and the tab plus though but it does give me peace of mind.
Just to err on the side of caution, I always odin flash back to gingerbread to wipe cache and other stuff before upgrading. This seems to have worked for me so far. *fingers crossed*
Check out that app above, its free and have a read of entropy's thread http://forum.xda-developers.com/showthread.php?t=1698977 but beware they don't take kindly to noob questions. I just mainly read entropy's updates and replies and ignore most of the rest of the stuff there.
Is there any chance to bring my tab to life has the repair center hasen't repaired mine
hi,
i have flashed the stock ICS, the Austrian version using ODIN3. i have been running it since july 18th.
so far i dont see any problem with my tab..
just to say, i have flashed the firmware atleast 3 times, just as an exercise. and have factory reset it after ICS flash atleast like 5 times now.
everything so far works fine. i use the stock recovery for factory reset.
after the 1st flash, i had root.. then thought of unrooting, so flashed the firmware 2 more times.
and in between the flashes, i have factory reset a lot of times.
so far, the bootloop problem which i used to have when on HC, is not there. hopefully, it wont occur in ICS.
hope, this helps developers.
Zarvox said:
Is there any chance to bring my tab to life has the repair center hasen't repaired mine
Click to expand...
Click to collapse
Use pit file (tab 7.7) in topic of hg42 - galaxy note this forum.
http://forum.xda-developers.com/showthread.php?t=1667886
Or use this method:
http://forum.xda-developers.com/showthread.php?t=1661590
Sent from my GT-P6200 using Tapatalk 2
giangp1 said:
Use pit file (tab 7.7) in topic of hg42 - galaxy note this forum.
http://forum.xda-developers.com/showthread.php?t=1667886
Click to expand...
Click to collapse
Thanks with manual method described in this thread I've confirmation that my data partition became corrupted.
Yes it is alive !!!
I've deleted mmcblk0p9 (DATAFS on my P6210) and recreate one with smaller size (3 GB) than normal (15.2 GB).
When the tablet boot I realise I've 1.68 GB of storage
Now I may increase the size of data but previous tries told me if data reach 5 GB in size the creation of partition fail.

Galaxy s3 keeps shutting off by itself during sleep

I have a really bad problem, my gf and I recently both got the Verizon galaxy s3 from Amazon wireless. I happen to like mine. In a day I rooted, flashed Synergy and won't go back.
Now..my gf's galaxy is a different story. From day one,.Hers likes to shut off by itself or become unresponsive (with the blue light blinking in sleep mode. The only fix is to pull the battery and restart.
Here is what I've tried..
Browse the hell out of forums (mainly yours)
Changing stock settings.
Flashed a custom ROM to see possibly it's the stock rom was broken. Same issue
Used my battery to see if it was a bad battery.still didn't fix it
Flashed a different kernel to see if the kernel is to blame. No dice.
Wiped to stock using Odin. Nuh uh.
I'm pretty much out of options.
I'm thinking about sending it back.
Hers has Synergy on it atm. If no one has any options left, can I just Odin back to stock, lock the bootloader, and use triangle away?
Thanks
Sent from another Galaxy far, far away using xda premium
stanleyopar2000 said:
I have a really bad problem, my gf and I recently both got the Verizon galaxy s3 from Amazon wireless. I happen to like mine. In a day I rooted, flashed Synergy and won't go back.
Now..my gf's galaxy is a different story. From day one,.Hers likes to shut off by itself or become unresponsive (with the blue light blinking in sleep mode. The only fix is to pull the battery and restart.
Here is what I've tried..
Browse the hell out of forums (mainly yours)
Changing stock settings.
Flashed a custom ROM to see possibly it's the stock rom was broken. Same issue
Used my battery to see if it was a bad battery.still didn't fix it
Flashed a different kernel to see if the kernel is to blame. No dice.
Wiped to stock using Odin. Nuh uh.
I'm pretty much out of options.
I'm thinking about sending it back.
Hers has Synergy on it atm. If no one has any options left, can I just Odin back to stock, lock the bootloader, and use triangle away?
Thanks
Sent from another Galaxy far, far away using xda premium
Click to expand...
Click to collapse
What build was your Synergy ROM? I've had difficulties with any ROM after about 3/23 due to some problems with the whole 3.4 thing. I'm not familiar with the Synergy ROM (obviously I've heard of it, but I don't like the stock "feel") and the problems that I've encountered have been on AOKP and CM based ROMS. But you may want to try flashing an earlier build. I went back to a build of the ROM I use from 3/13 and the problems I had that were similar to the ones you described stopped.
I've been running synergy for months now, and with almost all of their different releases. I have never had random reboots like that though. If you are using r420, or pretty much any of the newer releases, make sure you are doing a full wipe and not restoring any app data. That's the only way to make sure it isn't the ROM causing it. If it's still a problem, use that manufacturer warranty
Sent from my SCH-I535 using xda app-developers app
SynergyROM is awesome agreed. I had similar problems at one point due to my voltage settings. Not all phones are created equal. Increased voltage and changed governor to 'on demand' because 'interactive x' had problems at the moment.
Some have just flashed a different kernel but imo ziggy is a genius and I will rock his kernel as long as he makes one.
The issue is one one of the builds ziggy and I think phones with rev4 couldn't handle the low volt
The blue light blinks or stays on for a bit like when booting.?
Clearly..... It your phone does it on a stock kernel,
I highly doubt the software is causing it.
It sounds like somewhere across the line you have a hardware issue.
Oh damn...hardware..that's what I suspected. Should I do the three steps (odin, re-lock , triangle away) and send it back to Amazon?..or sammy?
And will they know if I messed with it?
Sent from my SCH-I535 using xda premium
I'm having the exact same problem with the latest AOKP and CM10.1. I reverted back to an older version to see if this fixes the problem.
stanleyopar2000 said:
Oh damn...hardware..that's what I suspected. Should I do the three steps (odin, re-lock , triangle away) and send it back to Amazon?..or sammy?
And will they know if I messed with it?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
triangle away first then odin, since you need root to use triangle away. re-lock not necessary if you flash a stock image.
reslor1 said:
triangle away first then odin, since you need root to use triangle away. re-lock not necessary if you flash a stock image.
Click to expand...
Click to collapse
+1. Also, Odin will not up your flash counter unless your flashing something that isn't stock......Odin as the last step will leave you at out of box stock.
Sent back the phone. Hope for the best
Sent from my SCH-I535 using xda premium
Amazon apologized and she got overnight a 32gb s3 for the same price as the 16. This new one has no sleep issues
Sent from my SCH-I535 using xda app-developers app

[Q] Nexus S Custom rom issue

Today i decided to go custom with my nexus s. I installed helly bean rom from nexus hacks. The ROM seemed to work fine until i used titanium backup to restore my data+settings. After restoring, I rebooted and since then was unable to make a call, send a message etc. I flashed back to 4.1.2 official via nandroid. Since then, every time I connect my phone to my computer and touch to enable usb, the phone reboots . Any ideas? I tried taking out the battery for 5 mins and then replacing it which helped to connect. After 1/2 an hour the phone rebooted again..... what should I do??
ibadimran said:
Today i decided to go custom with my nexus s. I installed helly bean rom from nexus hacks. The ROM seemed to work fine until i used titanium backup to restore my data+settings. After restoring, I rebooted and since then was unable to make a call, send a message etc. I flashed back to 4.1.2 official via nandroid. Since then, every time I connect my phone to my computer and touch to enable usb, the phone reboots . Any ideas? I tried taking out the battery for 5 mins and then replacing it which helped to connect. After 1/2 an hour the phone rebooted again..... what should I do??
Click to expand...
Click to collapse
It's due to titanium backup... Update you ROM as well... The version from that website is old... The latest is 27/10/2013
Sent from my Nexus S using XDA Premium 4 mobile app
Setting.Out said:
It's due to titanium backup... Update you ROM as well... The version from that website is old... The latest is 27/10/2013
Sent from my Nexus S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Maybe I was not able to convey my message properly. I've switched back to official 4.1.2 jb using nandroid. the reboot issue has started since then...
ibadimran said:
Maybe I was not able to convey my message properly. I've switched back to official 4.1.2 jb using nandroid. the reboot issue has started since then...
Click to expand...
Click to collapse
Use Nexus Root Toolkit, flash back to stock (via bricked option) and start over..

Phone restarts if it gets stuck on some apps

I just recently had this problem. I tried flashing PSX ROM and managed to mess it up. So I had to restore back to my original backup. Before trying to flash a ROM, my phone never had problems. Today my phone restarted on its own 5 times within 10 minutes. I have Franco kernel right now. Anyone else have any restarting problems by any chance? If not, I'm about to unroot
Sent from my Nexus 5 using xda app-developers app
choboii said:
I just recently had this problem. I tried flashing PSX ROM and managed to mess it up. So I had to restore back to my original backup. Before trying to flash a ROM, my phone never had problems. Today my phone restarted on its own 5 times within 10 minutes. I have Franco kernel right now. Anyone else have any restarting problems by any chance? If not, I'm about to unroot
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
You don't need to unroot. Just wipe system, data, and the caches and then restore your backup.

Categories

Resources