Related
Mates, the problem is there, we should admit that, had it on Galactus rom twice ( reflashed the rom again after full wipes to make sure ), and had it also on the stock LSZ with its stock kernel, and also on Cassie's rom.
Nothing solves the problem apart from wiping data.
Is it the preload ? the kernel ? defective JB from Samsung ? I really don't know.
The only thing I would really like to mention is that on Cassie's rom, had the issue surprisingly occuring on odd restarts not the even ones ! the first restart gets stuck, the other goes on !
Tried all the tricks in the book (restart to recovery, reinstalling bootloader, overinstalling the same rom, wiping everything keeping data, nothing worked.
Unless data gets wiped, the problem persists.
BTW, I had the same problem on all the previous leaked versions before the official ones.
Back to ICS while discussing here.....
i have no bootloop on the LSZ. been on it for couple of days and many reboots later....no issue.
i flashed the .md5 file from samfirmware link via odin ...let it boot and settle....then flashed philz LM5 4.35 kernel for root...
then i changed my build.prop for lcd density and installed the xposed installer and xposed app settings etc...
no lag and no bootloop.
also uninstalled a couple of the german apps that came with the firmware.
looks good!!
I (luckily) resolved it by
pressing POWER BUTTON for about 5 seconds while on samsung splash screen bootloop...
or
reboot to recovery>>advance>>reboot to recovery(again)>>>reboot system now..
or
making nandroid backup and restoring it
Recognized Distributor™
I have not flashed the latest stock ROM yet, but my understanding after reading various threads is that it seems like the issue is appearing only if you restore data using TITANIUM backup(or any other type of of data restoration).
Is this common for all which faced the issue?
I mean is there any one that wiped everything just installed the ROM and then did not restored anything from a backup and faced the issue?
thanks,
Panagiotis
I think bootlops are caused by the use of /preload partition for some .apk since JB rom like xxls7 that didn't use preload like RRv3 aren't affected by them.
Before reporting that you never have bootloop bug you should do this..
1. Force reboot, press power button about 7 sec...lets see if you phone past the N7000 logo or not..
Or
2. Force shutdown, pull out your battery while phone is ON..
Please make Nandroid backup 1st..
Sent from my GT-N7000 using Tapatalk 2
zai89 said:
Before reporting that you never have bootloop bug you should do this..
1. Force reboot, press power button about 7 sec...lets see if you phone past the N7000 logo or not..
Or
2. Force shutdown, pull out your battery while phone is ON..
Please make Nandroid backup 1st..
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Exactly, especially the 7 sec power button restart, almost 100% bootloop state.
Sent from my GT-N7000 using Tapatalk 2
pbirdas said:
I have not flashed the latest stock ROM yet, but my understanding after reading various threads is that it seems like the issue is appearing only if you restore data using TITANIUM backup(or any other type of of data restoration).
Is this common for all which faced the issue?
I mean is there any one that wiped everything just installed the ROM and then did not restored anything from a backup and faced the issue?
thanks,
Panagiotis
Click to expand...
Click to collapse
Had the issue on clean roms without any 3rd party app whatsoever, just the rom itself on the device before even restoring contacts through gmail.
Sent from my GT-N7000 using Tapatalk 2
jaguaralani said:
Had the issue on clean roms without any 3rd party app whatsoever, just the rom itself on the device before even restoring contacts through gmail.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Ohh...I see.. This is what is keeping me away of flashing the official ROM.. i will just wait for the issue to be found before i flash it.. Thanks for the info!!
Official JB is quite stable.. on XLSC (ultimate rom) my phone face sudden bootloop while it on my pocket, longest use on XLSC is 2 or 3 days before it bootloop by it self...only can be solve by restoring nandroid backup, something happen when I make force reboot or force shutdown...
But on XLSZ I only got bootloop on 1st reboot (after force reboot & force shutdown)....on 2nd reboot my phone will reboot normally..and never face suddent bootloop.. But yes bootloop bug is still there..
My XLSZ now is on:
+stock kernel
+rooted
+odexed/stock official
+some system apps is on preload partition
+no system/data restored by TB..
Sent from my GT-N7000 using Tapatalk 2
Here it explains why does bootloop happen and how to solve it
https://github.com/jeboo/initramfs_XWLSD/commit/95a98729983e71a3310c04e147994143651fe62c
We need to have the JB kernel sources in order to get rid of the bootloops
Sent from my GT-N7000 using xda premium
zai89 said:
Before reporting that you never have bootloop bug you should do this..
1. Force reboot, press power button about 7 sec...lets see if you phone past the N7000 logo or not..
Or
2. Force shutdown, pull out your battery while phone is ON..
Please make Nandroid backup 1st..
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Ok....so I tried both your methods of getting a boot loop.
1. After holding down power button till it came to the Sammy screen, it stuck there. I held power button down until screen went blank and let go....within a second phone came back on and rebooted normal.
2. Same as what happened in 1.
But this happened before where it would sometime get stuck at Sammy logo..in other versions of android and even inn my i9000 before....but it boot up fine after so no problems here.
Sent from my GT-N7000 using Tapatalk 2
ssss69 said:
Here it explains why does bootloop happen and how to solve it
https://github.com/jeboo/initramfs_XWLSD/commit/95a98729983e71a3310c04e147994143651fe62c
We need to have the JB kernel sources in order to get rid of the bootloops
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Thanks for the info mate, this clearly shows that it is a Samsung problem.
Sent from my GT-N7000 using Tapatalk 2
Now we need someone who is already stuck on the logo to flash Philz LSZ kernel and tell us if it fixes it or not.
Sent from my GT-N7000 using Tapatalk 2
jaguaralani said:
Now we need someone who is already stuck on the logo to flash Philz LSZ kernel and tell us if it fixes it or not.
Click to expand...
Click to collapse
Not fixed mate, already at PhilZ LSZ. Need someone to translate the github commit above to laymen terms. Seems that we need to format /data and then edit the fstab.smdk4210??
Anyway, based on that here is what I do, in CWM rather than wipe data/factory format, I just format /data and then using advance nandroid restore to restore just /data partition. It's not a solution but at least my setup is still there and data is intact. Of course you must do a nandroid backup in the first place! I take this trouble because to me XXLSZ is way snappier and smoother than the previous ROMs.
Edit: After successful reboot to system I went back to recovery and tried to reboot from there. Still stuck at boot logo, however pressing the power button for 7 seconds will clear it. Only tried few times though.
I've never had bootlop with LS7 and LSA and LSZ only few bootlops with lsc but i do wipeing cash and dalvik and works again
Verstuurd van mijn GT-N7000 met Tapatalk
kopitalk said:
Not fixed mate, already at PhilZ LSZ. Need someone to translate the github commit above to laymen terms. Seems that we need to format /data and then edit the fstab.smdk4210??
Anyway, based on that here is what I do, in CWM rather than wipe data/factory format, I just format /data and then using advance nandroid restore to restore just /data partition. It's not a solution but at least my setup is still there and data is intact. Of course you must do a nandroid backup in the first place! I take this trouble because to me XXLSZ is way snappier and smoother than the previous ROMs.
Edit: After successful reboot to system I went back to recovery and tried to reboot from there. Still stuck at boot logo, however pressing the power button for 7 seconds will clear it. Only tried few times though.
Click to expand...
Click to collapse
Thanks for the info mate...
today I'm updating my friend phone from stock ICS DXLR5 to XLSZ (free of chrge) using PC ODIN..while on stock XLSZ kernel I make a force reboot on my friend phone and its stuck on N7000 logo and boot find after second reboot (without any wipe or restore) , same things happen to my phone to...after that flash new Philz XLSZ kernel on my phone & my phone too from stock recovery...and what is surprise me is my friend phone survive when I make a force reboot but my phone not...maybe its time to reflash, will report again..
I have faced this problem many times before and the only cure sometimes was to make a nandroid backup and restore it
but if the backup failed at the data partition that means the data is corrupted and you must wipe your data ...
but one solution for sure worked for me with all roms I've tried ... do not use the preload partition ....
I do not use it at all ... even if i downloaded a rom which uses preload partition I modify the rom to use
only system partition ... with this I've never faced any boot loop with JB again.
Super Prince said:
... even if i downloaded a rom which uses preload partition I modify the rom to use
only system partition ... with this I've never faced any boot loop with JB again.
Click to expand...
Click to collapse
Care to share how to do this?
I am going crazy with this damn phone as I constantly restore back to my previous states but every reboot it is asking for password and I have non. It has never done this before. I formatted the internal data and all that and it keeps doing this over and over again.
Any ideas? I cant restore anymore because I keep formatting the internal drive and then I restore then it goes back to asking me de DECRYPT DATA.
:crying:
Brava27 said:
I am going crazy with this damn phone as I constantly restore back to my previous states but every reboot it is asking for password and I have non. It has never done this before. I formatted the internal data and all that and it keeps doing this over and over again.
Any ideas? I cant restore anymore because I keep formatting the internal drive and then I restore then it goes back to asking me de DECRYPT DATA.
:crying:
Click to expand...
Click to collapse
I'm having a similar problem. As soon as I install a TWIZ rom and reboot it seems to encrypt it and it will not boot. I find TWRP allows me to bypass the password and restore to a backup but I have been unable to use any TWIZ roms.
Fixed it Odin stock rom and starting from the very beginning. Twrp was damaged somehow. Everything works now. Try that
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4 Beta
Brava27 said:
Fixed it Odin stock rom and starting from the very beginning. Twrp was damaged somehow. Everything works now. Try that
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Are you running a custom rom no problem? What ROM/Kernel are you using?
I took your advice and redid my phone from scratch. Now it works great! thanks for the recommendation
Awesome! I was surprised I didn't find any solution anywhere. I was reluctant to stay with TWRP and go with CMW but I'm still with TWRP and everything is smooth. I believe my problem was formatting my internal drive or Twrp was damaged somehow. Anyways, good to know we can always Odin stock, root and bring everything back to normal again.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4 Beta
can anyone help me i have a g2 801 t-mobile version and flashed the cloudyflex rom and noticed i didnt have data working so i went to twrp and wiped everything and restored my old stock rom but notice nothing was working no wifi no notification bar and it keeps randomly rebooting and it cant be turned off i have flashed several backups i had stored and none of them work
1stloc said:
can anyone help me i have a g2 801 t-mobile version and flashed the cloudyflex rom and noticed i didnt have data working so i went to twrp and wiped everything and restored my old stock rom but notice nothing was working no wifi no notification bar and it keeps randomly rebooting and it cant be turned off i have flashed several backups i had stored and none of them work
Click to expand...
Click to collapse
I would suggest you to make a clean install of the stock rom!
That should fix the issue!
zacharias99 said:
I would suggest you to make a clean install of the stock rom!
That should fix the issue!
Click to expand...
Click to collapse
I tried and nothing works i even went back to stock using this thread http://forum.xda-developers.com/showthread.php?t=2432476
What recovery were you using and do you have any backups from then or is everything gone?
sp33dsk8 said:
What recovery were you using and do you have any backups from then or is everything gone?
Click to expand...
Click to collapse
the latest twrp....i have backups on my computer but cant transfer them because it keeps rebooting and since i went back to stock i cant root as it does not let cuz of the constant reboot
1stloc said:
the latest twrp....i have backups on my computer but cant transfer them because it keeps rebooting and since i went back to stock i cant root as it does not let cuz of the constant reboot
Click to expand...
Click to collapse
I'd try and get with this guy
"As usual, I'm on #lg-g2 in Freenode as IOMonster, if I'm around I'll be happy to help wherever I can."
http://forum.xda-developers.com/showthread.php?t=2432476
I had the exact same problem! Phone would boot into the rom, or stock and freeze after about a minute and reboot itself constantly. I had the updated version of TWRP and was flashing the new 1/30 Mahdi build and it happened after I did that! I tried flashing stock roms, aosp roms, and eventually did a Flash back to stock method, which non of them worked. I took the phone into T-Mobile and did a warranty replacement, got a new one overnight. Not sure if it is related to Mahdi or not, but it happened after a supposed successful flash.
I tried my TWRP Backups too, and those still restarted on me. Nothing helped me..Tried wiping the sd card, format the whole card, wipe cache, fix perm..
Hopefully you have a warranty or figure it out!
Good luck.
ZetterbergDatsyuk said:
I had the exact same problem! Phone would boot into the rom, or stock and freeze after about a minute and reboot itself constantly. I had the updated version of TWRP and was flashing the new 1/30 Mahdi build and it happened after I did that! I tried flashing stock roms, aosp roms, and eventually did a Flash back to stock method, which non of them worked. I took the phone into T-Mobile and did a warranty replacement, got a new one overnight. Not sure if it is related to Mahdi or not, but it happened after a supposed successful flash.
I tried my TWRP Backups too, and those still restarted on me. Nothing helped me..Tried wiping the sd card, format the whole card, wipe cache, fix perm..
Hopefully you have a warranty or figure it out!
Good luck.
Click to expand...
Click to collapse
Dam no I do not have warranty and I'm on a prepaid plan and bought the phone from swappa sucks the phone is a waste now
Sent from my Nexus 5 using Tapatalk
ZetterbergDatsyuk said:
I had the exact same problem! Phone would boot into the rom, or stock and freeze after about a minute and reboot itself constantly. I had the updated version of TWRP and was flashing the new 1/30 Mahdi build and it happened after I did that! I tried flashing stock roms, aosp roms, and eventually did a Flash back to stock method, which non of them worked. I took the phone into T-Mobile and did a warranty replacement, got a new one overnight. Not sure if it is related to Mahdi or not, but it happened after a supposed successful flash.
I tried my TWRP Backups too, and those still restarted on me. Nothing helped me..Tried wiping the sd card, format the whole card, wipe cache, fix perm..
Hopefully you have a warranty or figure it out!
Good luck.
Click to expand...
Click to collapse
Hey can you tell me how t-mobile insurance works i use to be with sprint and if they couldnt fix it they would send me a new at no cost...my friend has t-mobile insurance can he put his sim card in and they have a look at it and if they do will he be charged anything?
OK learn about adb sideload so you can sibeload a ROM or have you us LG G2 to go back to stock and start all over?
Sent from my LG-LS980 using XDA Premium 4 mobile app
Nicamarcel1 said:
OK learn about adb sideload so you can sibeload a ROM or have you us LG G2 to go back to stock and start all over?
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ok read my other post as i have gone back to stock and it has not worked
I had the same problem. If you looked for other threads, you would find fix.
Problem is in CPU voltage.
http://forum.xda-developers.com/showthread.php?t=2612243
Wysłane za pomocą LG G2 przez TWRP
1stloc said:
Dam no I do not have warranty and I'm on a prepaid plan and bought the phone from swappa sucks the phone is a waste now
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Should still be under warranty with LG. I'd call their support and give them the serial number to see if it still covered.
As far as the LG Warranty goes, all I did is walk into the store and show them the issue at hand, and he put in a order for a new one sent overnight to me. They send you a prepaid label and a box to ship your old one back(phone only). The new phone I have appears to be brand new, with all the crazy plastic protection on it... not sure if it is a refurbish or not. Didn't cost me a penny, as I have the JUMP w/ protection plan.
Hi, I'm desperate today. I've been without my phone since a few days.
In the first place, I wanted to flash another custom ROM. I hadn't change anything to my N4, I was using AOSPAL. You know that F2FS has come, so I wanted to test it. After some fails, some resets, I succeeded to make my phone clean & fast (F2FS & custom kernel). Now I can tell you about my problem.
I noted that, after many tests/flashs, my phone can't boot after turning it off. I stuck at "Google" logo, the ROM apparently disappeared from my phone, or something else went wront. I don't know what.
Then I did a new factory reset, I flashed a ROM/Kernel without any changes to FS, but I got the same problem. If I reboot (reboot from adb, ROM...) my phone, it works. But if I turn it off, I'll stuck at "Google" logo the next boot.
I've actually no ideas, and Google gave me no results...
I'll try to make a new reset, or try another kernel... I don't know where I'm going.
Thanks for help and I wish you to have a nice day.
PS : I'm not a newbie, I already did more than hundreds flashes, some bricks, but I've never seen a similar problem.
Why don't you try flashing the factory image and start over. That should clean everything up
Sent from my Nexus 5
hi
try use nexus tool kit for restore fone bootloop flash rom stock
jd1639 said:
Why don't you try flashing the factory image and start over. That should clean everything up
Sent from my Nexus 5
Click to expand...
Click to collapse
I've already done that each time before flashing any custom mod, since I got that problem.
eltonpestana said:
try use nexus tool kit for restore fone bootloop flash rom stock
Click to expand...
Click to collapse
This isn't the problem... I flashed the factory image many times. It works, but when I turn my N4 off and I want to boot it, I stuck at "Google".. When I reboot from the ROM or adb, there's no problems...
Diaruga said:
I've already done that each time before flashing any custom mod, since I got that problem.
This isn't the problem... I flashed the factory image many times. It works, but when I turn my N4 off and I want to boot it, I stuck at "Google".. When I reboot from the ROM or adb, there's no problems...
Click to expand...
Click to collapse
I assume you've done a factory reset in the stock recovery too? If so I think something is wrong with your phone. Is it still under warranty.
Sent from my Nexus 5
jd1639 said:
I assume you've done a factory reset in the stock recovery too? If so I think something is wrong with your phone. Is it still under warranty.
Sent from my Nexus 5
Click to expand...
Click to collapse
Mhhh when I tried F2F2 and wanted to try something else, I've not done a factory reset in the recovery (did you mean the format partitions in ext4fs or the wipe data/cache/dalvik ?). I used fastboot in order to erase all my partitions, then I flash the factory image archive through fastboot command "-w update".
I don't know whether something is wrong with my phone or not, but I've never seen that problem. It appeared when I did some tests with F2FS. That's all, that's so weird...
Diaruga said:
Mhhh when I tried F2F2 and wanted to try something else, I've not done a factory reset in the recovery (did you mean the format partitions in ext4fs or the wipe data/cache/dalvik ?). I used fastboot in order to erase all my partitions, then I flash the factory image archive through fastboot command "-w update".
I don't know whether something is wrong with my phone or not, but I've never seen that problem. It appeared when I did some tests with F2FS. That's all, that's so weird...
Click to expand...
Click to collapse
I would definitely try to flash the factory image again, then boot into the stock recovery and do a factory reset. F2FS may have borked something. I've never tried it since it does mess with the positions
Sent from my Nexus 5
hi'
I'm not sure if this can work. But it never hurts to try. After flashing stock ROM with CWM. Enter recovery and make full format of all partitions. System and Data partitions and cache and all. After that reinstall the stock rom using nexus tool kit for flashing mode in bootloop. after that flashing custom recovery again and do cleanup, but not the only formates cleanings. I believe you are having trouble reading recognition, partition boot. Uncompensated You must have notice a conflict of partitions on the system format.
eltonpestana said:
Uncompensated You must have notice a conflict of partitions on the system format.
Click to expand...
Click to collapse
I was wondering the same thing...
Thanks guys for your help, I'll flash stock again, and then I'll format correctly the partitions. I hope that's the good way...
Next time its stuck on the Google logo just try plugging in you're charger.
I had the same problem but not down to using F2FS but it did hang on the logo during boot.
After plugging in the charger it booted and hasn't stuck since.
Don't ask my why as I haven't a clue but it worked.
Sent from my Nexus 4 using XDA Premium 4 mobile app
bladebuddy said:
Next time its stuck on the Google logo just try plugging in you're charger.
I had the same problem but not down to using F2FS but it did hang on the logo during boot.
After plugging in the charger it booted and hasn't stuck since.
Don't ask my why as I haven't a clue but it worked.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
FYI this could indicate a problem with your battery
@Diaruga did you ever find a solution?
Sent from my Nexus 5
I plugged my N4, then I tried to flash the factory image again. That was fine. After flashing a custom ROM + custom kernel, still no probems after turning my phone off.
I can't explain why...
Thanks to all, my problem has been solved.
Diaruga said:
I plugged my N4, then I tried to flash the factory image again. That was fine. After flashing a custom ROM + custom kernel, still no probems after turning my phone off.
I can't explain why...
Thanks to all, my problem has been solved.
Click to expand...
Click to collapse
Thanks, glad you got it working again
Sent from my Nexus 5
Okay, so I feel like I've looked everywhere and tried everything for this problem with my Nexus 7. The closest thing I found was this:
(Google: Nexus 7 2012 rebooting reverts back to previous state)(I can't post outside links as I am a new member)
and there was no followup reply, and the thread was closed.
Here's my problem (I want to be very detailed in case I missed something):
I've had Cyanogenmod 11 on my Nexus 7 for a long time (I think I started with M1 release). I recently installed the M7 release after previous nightly and it was working so smooth that I had finally decided there was no need to install nighties anymore. Everything was going fine until the night after when I noticed it kept rebooting, so I reverted it back to the nightly I had before (June 11th?) because I assumed it was probably something bad with the update. Except it did the same thing, rebooting after a couple minutes, which is weird because it never did that with this nightly. There was never enough time to download the nightlies before it reboots so I tried downloading them on my laptop and then just transferring them to my nexus via usb. I put it in the cmupdate folder so that I could quickly go to settings and press install (as it can see the update from there). It rebooted to install, but it went into cwm with what appears that nothing happened, and I usually never see cwm when updating this way. So I figured, while I'm here, I could just "install zip" and find that zip I just transferred and install, right? Nope. The zip mysteriously vanished, yet the other two updates were still there (M7 and the previous nightly). So I just rebooted just to try the process again, maybe the file transfer didn't work. Same thing happened. So I went to cwm and tried wiping cache, nothing. Wiped dalvik cache, nothing. So I went and did it, wiped data/factory reset, that did NOTHING, as in I rebooted and everything was still there.
So I got to the point where I just wanted to see if I could just revert back to stock so I have a place to start from, maybe contemplate on just staying there for a while where there shouldn't be problems. So I got that all set up with fastboot, got the latest 4.4.3 image, unarchived until I could get to the flashall.bat I ran that and it was successful. Okay now I can just boot into that, right? Suddenly I see the cyanogenmod boot graphic. What happened? Even all of my apps are still there. Still freezing and rebooting.
I tried reverting to stock manually by erasing then formating everything that I can, flashed bootloader (grouper 4.23), flashed zip, locked bootloader, unlocked bootloader (trying to erase as much as I can). This did nothing, still cyanogenmod. I tried a third time while rebooting to bootloader with each step. Nothing. I tried doing a factory reset within cyanogenmod, but when I press the "erase everything" button it doesn't lead anywhere, so I could never get that to start the process. I also tried doing the erasing and formatting from cwm (which isn't being overwritten, as it seems, by all the attempts at flashing stock?), nothing.
I was curious. I uninstalled Netflix because it was right there in my dock. Then I rebooted myself. When it came back up, Netflix was still there. I tried various things, also going back to locking the bootloader and rebooting the bootloader, it still said it was unlocked. So I came to the conclusion that literally nothing was being written or committed to the sdcard no matter what I do.
I did some more research and found that article up top. So I tried uninstalling some apps because it said it may have something to do with a third-party app misbehaving (seems a bit extreme, I'll do it anyways), but there's never enough time to erase everything before it reboots. It also said to try to get it into safemode. I think I might have gotten there once but it still rebooted (which makes me think that it didn't get to safemode), the rest of the times it wouldn't even get to the lockscreen.
What I'm currently attempting is to see if I can get it into safemode, or I'm trying to uninstall or stop/clear data for every single app with an intentional reboot each time.
Anyone got any idea what's going on? Is it maybe a bad sector, or worse, bad sdcard?
Gonna bump this. Still no luck on my part.
Anyone have any idea?
Perhaps somehow something got triggered to prevent anything being written to the sdcard? (Kinda like the lock switch on actual sdcards?) Is everything I've been doing going straight to memory since everything reverts back after a reboot? That's the only explanation I can think of.
Perhaps there's more I could try. I'm only moderately knowledgeable with things like fastboot and roms, so maybe someone with more experience might have more insight. Please, chime in.
Thanks in advance,
JM
Same problem here....
Flash factory image
USBhost said:
Flash factory image
Click to expand...
Click to collapse
Although you flash the factory image, the previously ROM boots again, that is precisely the problem.
Amd64bits said:
Although you flash the factory image, the previously ROM boots again, that is precisely the problem.
Click to expand...
Click to collapse
O ok
Amd64bits said:
Same problem here....
Click to expand...
Click to collapse
Curious, how did you get to the point where it boots the previous rom? Same as me or something else? Are you using cyanogenmod? I want to try and rule out some possibilities.
I'm at the same point since last time. Trying to nuke the hell out of cyanogenmod but it won't go away!
This just outright baffles me!
Try this out format /system /cache /data with twrp to f2fs
If it doesn't boot then cheers you got out if the loop
Then adb sideload an f2fs ROM and kernel them flash
USBhost said:
Try this out format /system /cache /data with twrp to f2fs
If it doesn't boot then cheers you got out if the loop
Then adb sideload an f2fs ROM and kernel them flash
Click to expand...
Click to collapse
I have clockworkmod recovery v6.0.4.3 probably from installing cyanogenmod, however formating any of those partitions does literally nothing. I'm not sure what file system it formats it to, but the process seemed too quick for a full format.
I cannot flash a different recovery because... well... it doesn't remember me flashing a recovery (even when nothing "fails" when flashing). So I'm stuck with whatever is already on my internal storage. Nothing is writing to the sdcard, and nothing is being deleted.
violoncellemuse said:
I have clockworkmod recovery v6.0.4.3 probably from installing cyanogenmod, however formating any of those partitions does literally nothing. I'm not sure what file system it formats it to, but the process seemed too quick for a full format.
I cannot flash a different recovery because... well... it doesn't remember me flashing a recovery (even when nothing "fails" when flashing). So I'm stuck with whatever is already on my internal storage. Nothing is writing to the sdcard, and nothing is being deleted.
Click to expand...
Click to collapse
Boot twrp temporary from the bootloader
USBhost said:
Boot twrp temporary from the bootloader
Click to expand...
Click to collapse
I'm unfamiliar with this, how do I boot temporarily?
violoncellemuse said:
I'm unfamiliar with this, how do I boot temporarily?
Click to expand...
Click to collapse
1 set getting on computer
Okay, so I was able to boot twrp and change the partitions to f2fs. No dice. Still cyanogenmod.
violoncellemuse said:
Okay, so I was able to boot twrp and change the partitions to f2fs. No dice. Still cyanogenmod.
Click to expand...
Click to collapse
then you did boot twrp temporary
USBhost said:
then you did boot twrp temporary
Click to expand...
Click to collapse
I did. I didn't know that was possible until now.
But still, changing the file system or formating anything doesn't do anything after I reboot. I even checked after I changed the file system to f2fs in twrp to see the "current file system" when changing the partitions again, but it says it's ext4 still.
I tried repairing system, which processed quickly. However, trying to repair cache and data led to an error. Perhaps this might mean something? or is this normal?
violoncellemuse said:
I did. I didn't know that was possible until now.
But still, changing the file system or formating anything doesn't do anything after I reboot. I even checked after I changed the file system to f2fs in twrp to see the "current file system" when changing the partitions again, but it says it's ext4 still.
I tried repairing system, which processed quickly. However, trying to repair cache and data led to an error. Perhaps this might mean something? or is this normal?
Click to expand...
Click to collapse
thats not normal
ok i know why its a new cyanogenmod feature
no matter what you do cyanogenmod is now unkillable lol
this is such a strage problem
USBhost said:
thats not normal
ok i know why its a new cyanogenmod feature
no matter what you do cyanogenmod is now unkillable lol
this is such a strage problem
Click to expand...
Click to collapse
Do you have any more info? Perhaps my sdcard is "softlocked" or something.
violoncellemuse said:
Do you have any more info? Perhaps my sdcard is "softlocked" or something.
Click to expand...
Click to collapse
i have been noticing CWMR is the root of all the problems
i dont sorry but your not the only one i think there are 3+ people that have this same problem
formating should have fixed it
USBhost said:
i have been noticing CWMR is the root of all the problems
i dont sorry but your not the only one i think there are 3+ people that have this same problem
formating should have fixed it
Click to expand...
Click to collapse
I do thank you for trying to help me out.
I found a thread with someone with the same problem I'd like to direct people towards: http://forum.xda-developers.com/showthread.php?t=2800064
violoncellemuse said:
Curious, how did you get to the point where it boots the previous rom? Same as me or something else? Are you using cyanogenmod? I want to try and rule out some possibilities.
I'm at the same point since last time. Trying to nuke the hell out of cyanogenmod but it won't go away!
This just outright baffles me!
Click to expand...
Click to collapse
Well, I have Paranaoid Android 4.4.4, not Cyanogen, and everything seemed ok until I installed Cloudmagic (and maybe Busybox?) that poped up a Play Store error (I don't remember which one), and suddenly all the problems began. It started to reboots, rebooted so many times that I decided to flash another ROM... but this wasn't possible.
My recovery is TWRP, so we can discard Cyanogen, ParanoidAndroid, CMW and TWRP as guilty, I think.
USBhost said:
Try this out format /system /cache /data with twrp to f2fs
If it doesn't boot then cheers you got out if the loop
Then adb sideload an f2fs ROM and kernel them flash
Click to expand...
Click to collapse
Tried that, nothing happened, still with Paranoid Android.
violoncellemuse said:
I did. I didn't know that was possible until now.
But still, changing the file system or formating anything doesn't do anything after I reboot. I even checked after I changed the file system to f2fs in twrp to see the "current file system" when changing the partitions again, but it says it's ext4 still.
I tried repairing system, which processed quickly. However, trying to repair cache and data led to an error. Perhaps this might mean something? or is this normal?
Click to expand...
Click to collapse
Same here.