DELETE
5 downlds and no comment???
C'mon guys
Kolteabhiman said:
5 downlds and no comment???
C'mon guys
Click to expand...
Click to collapse
I have flashed and format it successfully.How can i feel the difference?
What do you mean the Streakmod backup isn't working for CM7? The nandroid made from Streakmod works just fine and unfortunately I didn't notice any improvement in performance after flashing the script
Sent from my cm_tenderloin using Tapatalk 2
Yeah!
The general responsiveness of device increased.
Check that it has successfully formatted to ext4
Seems to work fine on MIUI 2.3.23...
Please be aware people, to do a backup before flashing this and understand that you will have to reinstall everything again!
Can't say i can see any difference in speed really, a bit maybe.
Nandroid will not finish a backup.
I'm using this and believe I am noticing a remarkable improvement in performance on CM7. Now to get nandroids working!
Sent from my Dell Streak using Tapatalk 2
I think problem is in recovery
since it mounts data as mount ext3 innersd0p6
if we change it to ext4 it might work
its my personal opinion because it says invalid argument
lordmorphous said:
I'm using this and believe I am noticing a remarkable improvement in performance on CM7. Now to get nandroids working!
Sent from my Dell Streak using Tapatalk 2
Click to expand...
Click to collapse
I think the vold.fstab(from recovery) control mounting of partitions
or what u think
Now i have been using this for a while, i can say there is a definate speed increase, you notice it in everything really, there is much less lag and my phone seems to be much more responsive, apps start faster too.
I hope we can fix the nandroid backup issue cos i cannot use its truly a life saver.
I've been using this with Longhorn 2.8 for a day now and definitely notice the Streak is more responsive, Hoping one of our dev can get nandroid working
I think it will be simpler if we change mount arguments in then streakmod source and recompile it it will be
How to back FAT
I already flash zip and it work fine with may DS, so some function in StreakMod not work on EXT4 format. Please help me way to back FAT
If you want to go back to the format before, which isn't FAT by the way, you need to reflash your original rom, or use the nandroid backup you made before using the formatter.
You did make a nandroid backup didn't you?
Sent from my Dell Streak using XDA
(InsertNameHere) said:
If you want to go back to the format before, which isn't FAT by the way, you need to reflash your original rom, or use the nandroid backup you made before using the formatter.
You did make a nandroid backup didn't you?
Sent from my Dell Streak using XDA
Click to expand...
Click to collapse
@(InsertNameHere)
Have you or anyone else tried restoring a nandroid after this?
I tried it but got an error message but can't remember what it was except for it relating to not being able to restore the data partition
Flashing the ROM in zip format didn't reformat the data partition either
I ended up having to flash stock 407 and then factory resetting from recovery....
I tried factory reset from recovery twice before flashing the stock ROM trying to format the data partition but it had no effect... it would boot up right back into my ROM jjust like it was before factory reset
Only after flashing stock Olleh, factory resetting and then flashing Streakmod was I able to successfully restore my nandroid
Sent from my cm_tenderloin using Tapatalk 2
OK. So currently we have to flash factory recovery and rom to go back.
I thought mistakenly it may have been easier, still nobody said it was easy being on the cutting edge!
Thanks for finding out!
Sent from my Dell Streak using XDA
cdzo72 said:
@(InsertNameHere)
Have you or anyone else tried restoring a nandroid after this?
I tried it but got an error message but can't remember what it was except for it relating to not being able to restore the data partition
Flashing the ROM in zip format didn't reformat the data partition either
I ended up having to flash stock 407 and then factory resetting from recovery....
I tried factory reset from recovery twice before flashing the stock ROM trying to format the data partition but it had no effect... it would boot up right back into my ROM jjust like it was before factory reset
Only after flashing stock Olleh, factory resetting and then flashing Streakmod was I able to successfully restore my nandroid
Sent from my cm_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
Oh dear my friend
I try roll back from nandroid many time, my DS go to deep sleep
I used CkockMod flash fastbook without battery and after that with battery, take my princess out of forest
My God
After reflash 407, my DS still back in MiUI
Sent from my Dell Streak
@Kolte
Would you please do a new script for reverting data partition to fat?
We can't install any Rom correctly because we can't do wipe data/factory reset completely and it causes FC's in different Rom's
Actually its not father its ext3
I will make a scripts
Related
So I just installed Nerov4.1 which I must say I'm loving. However, my curiosity is making me want to check out axura's rom as well. I've read and seem some videos that state you should restore the phone to stock mode before installing another ROM. Is this true or can I just install another ROM through ROM Manager without having to do so? If I should restore my vibrant back to stock what is the best and easiest method to do it? I just want to make sure I'm doing the steps correctly when switching from ROM to ROM. Thanks for helping a newbie out fellas!
http://forum.xda-developers.com/showthread.php?t=803492
Thanks for the response but do I have to go back to stock mode each time I want to try a new ROM??
Sent from my SGH-T959 using XDA App
I'm very much just a noob, but as far as I'm aware you MUST disable voodoo. Vodoo comes automatically switched on in 4.1. If you are going back to stock this must be done.
I think you can go into clockwork recovery and turn it off. Or there's an app in the market that will be able to confirm/ switch it on or off I think.
thebig88 said:
Thanks for the response but do I have to go back to stock mode each time I want to try a new ROM??
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Depends, but is recommend.
Depends on?
Sent from my SGH-T959 using XDA App
I wrote steps in the noob guide... but as I pointed out there also, you do not always need to go back to stock.
I would disable voodoo (just to be safe)
make a backup
reboot
go back to cwr
factory wipe/wipe data/wipe dalvik (advanced)
flash the rom
reboot and wait
let the phone sit for 10 minutes
reboot
restore your apps (titanium Backup, assuming you use this app)
reboot
enable voodoo if not already
reboot
If you notice any issues then you should ODIN back to stock the flash the rom.. there may be "ghosts" from the previous rom causing the issue... it's a best practice, but absolutely not needed.
s15274n said:
...
factory wipe/wipe data/wipe dalvik (advanced)
...
Click to expand...
Click to collapse
You mean that all data from internal disk will be erased, inculding the titanium backups?
Thank you in advance!
im wondering the smae thing.ive been flashing a lot of roms and havent had to go back to stock but i know its only a matter of time.if you find a method that works great for you please let me know
when we install new roms doesnt the process wipe the system data and dalvik cashe.why is it better to use your method.im just a curios noob
no.. all your pics, videos, etc will still be there unless you do a format yourself.
Im currently running the first flight Rom and wanted to go back to alpha 2...i tried a reflash but my phone is still on the other Rom, i did another reset and reflash of alpha but it still hasn't change. I than tried to use my nandroid backup which ice used before but when i try to use it it tells me nothing on file...what do i do
Sent from my SAMSUNG-SGH-I717 using xda premium
After about 4 attempts i was able to flash alpha 2 and my back ups seem to be there as well...not just empty folders like before, weird
Sent from my SAMSUNG-SGH-I717 using xda premium
That is odd. Make sure you always factory reset multiple times as well as wipe cache multiple times when switching roms.
So you would:
- factory reset x3
- wipe cache x3
- wipe dalvik x1
- flash new rom
This should help with experiencing less if these type issues as well as other bugs.
Sent from my SAMSUNG-SGH-I717 using xda premium
Coffinfeeder said:
That is odd. Make sure you always factory reset multiple times as well as wipe cache multiple times when switching roms.
So you would:
- factory reset x3
- wipe cache x3
- wipe dalvik x1
- flash new rom
This should help with experiencing less if these type issues as well as other bugs.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
I actually do those steps. I flashed one of the other ics roms and I didn't really like it so I tried to flash alpha back, after reboot I was still on the other rom...I tried again with same result, finally I used my backup. This time the same thing happened but I was on a different rom, the only difference was I wasn't able to use my back up, backup folder said "no file" when trying to flash, so I was pretty much forced to keep trying to flash alpha, finally it worked and I checked my cwm folder and my backups are there and are not empty. Odd
Sent from my SAMSUNG-SGH-I717 using xda premium
nash2000 said:
I actually do those steps. I flashed one of the other ics roms and I didn't really like it so I tried to flash alpha back, after reboot I was still on the other rom...I tried again with same result, finally I used my backup. This time the same thing happened but I was on a different rom, the only difference was I wasn't able to use my back up, backup folder said "no file" when trying to flash, so I was pretty much forced to keep trying to flash alpha, finally it worked and I checked my cwm folder and my backups are there and are not empty. Odd
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
weird considering when you do a restore it erases boot partition before starting to restore so unless you used the wrong backup file it should've worked the first time.
roloracer said:
weird considering when you do a restore it erases boot partition before starting to restore so unless you used the wrong backup file it should've worked the first time.
Click to expand...
Click to collapse
I only used the restore one time a week or so ago because everytime I tried to flash back to alpha I was still on the collective rom. Thats when I used my backup and it worked but this time the same time happened....flashed alpha like 3 times and nothing happened, I than tried to use my backup but my phone told me the backup file was empty, I have 2 backups and my phone told me the same thing on both. I continued to flash alpha over and over again with wiping date etc each time and it finally worked, and my backups have data in them unlike before.
Sent from my SAMSUNG-SGH-I717 using xda premium
So, i performed a nandroid backup so i wouldnt get screwed later down the road and all went well. Went to reboot now and no go, just sits on the big M. What is the problem. So many problems lately with this....
Just do a battery pull. If that doesn't work get into recovery and clear cache.
Sent from my MB870 using xda app-developers app
i did the battery pull, cleared cach and dalvick, let it sit for 10 minutes and nada from anything. Anything else i should try. If i format wipe data am i able to flash the nandroid i made
The only other things I can suggest are a data wipe or sbf. If you opt to do the sbf you may as well do the data wipe first and see if that fixes it. If so you can potentially restore the nandroid you just made without going through the hassle of sbf.
Sent from my MB870 using xda app-developers app
What rom are you running ? If cm9..make sure you are using the cm7 patched bootstrap recovery ...I made the mistake of not swapping to it after flashing to cm9, did a nandroid and had the exact problem....all you have to do is flash your nandroid you just made and then flash cm9 again......it will boot up again with nothing lost....but may act crazy like its running things on its own.....just shutdown and reboot and you'll be good to go.....then install the patched cm7 recovery and you'll never have the problem again.
sent from a pimpin DX2 CM9DX2 Beta1 V6supercharged !
I have the motor a4 bar. Is that the correct one. I had to sbf and do a whole new install but added blue sleep before rebooting all working well now. Oh running aokp 6.
So ive been having issues with dhacker29's roms making my phone reboot and hang on the bootloader. Well the latest one, the selinux build which he put more bugs into an already screwed up reboot cycle it worked good when I first installed it, than it did one of its forced reboots.
Phone hasnt booted since, restored to previous rom that worked fine. Stock, all kinds of things tried. It just hangs on the motorola logo now.
Anybody got any ideas for me?
When you go back to other ROMs are you restoring apps and data along with them via Titanium Backup or another backup app? If so, that might be the cause. It may be something in your apps, not the ROM. And as always wipe cache and dalvik cache after any flash.
Just restoring back to a TWRP backup. not using tibackup or anything like that,
Ive tried wiping dalvik, Tried a factory reset on these backups. Even tried fix permissions. Still nothing.
Probably a bad backup
If you wipe fully (yes I mean a full wipe) and then restore a back up from working phone and it just loops, chances are you had a bad backup
Just wipe clean and flash a new rom
Sent from my Nexus 4 using xda premium
demkantor said:
Probably a bad backup
If you wipe fully (yes I mean a full wipe) and then restore a back up from working phone and it just loops, chances are you had a bad backup
Just wipe clean and flash a new rom
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I did some posting in the thread for the rom. 2 others had the same issue where none of there backups worked after flashing that rom version and after it crashed and rebooted it never came back. So I doubt it was a bad backup just something weird with the rom
Sent from my XT926 using Tapatalk 2
Unless there is something very strange about this ROM (as in it corrupts other partitions but so highly doubtful), backups are 100% separate from another ROM, this means a full wipe will erase everything about you current ROM and then restoring a backup from a previous ROM will work, so long ad the backup is good and the wipe is clean.
Sent from my Nexus 4 using xda premium
I don't know. The rom does have a form or selinux in it so maybe that caused it. I don't know the specifics of what selinux does internally just what the goal is
Sent from my XT926 using Tapatalk 2
Doesn't sound like it should brake anything, if the ROM won't boot for you that's one thing, but completely wiping your phone then flashing a new ROM should fix your issue.
I am highly suspect that the ROM in question could have done anything at all to your recovery or your backups.
You said you are using twrp, have you tried wiping/formating all partitions and then flashing a known working ROM? Does your phone have fast boot mode? If so this may be an even cleaner wipe to do prior to the flash
Sent from my Nexus 7 using xda premium
I had to fastboot back to stock to get anything to work.. No rom I tried would boot
Sent from my XT926 using Tapatalk 2
Again, without knowing anything about your phone, the ROM would not affect your bootloader/radio/recovery no firmware should be changed just by flashing a rom,.
If it won't boot after a full wipe then there is some other issue, but if you were able to fix things by flashing back to stock then good.
Without knowing more specifics about your phone or the ROM you had issues with I guess I can't help you any further, so long as your are up and running now I would suggest just to stay away from any ROM you have had issues with, make new backups and test them (yes fully wipe before a restore and being your phone has fastboot wipe there) and best of luck to you
Happy flashing!
Sent from my Nexus 7 using xda premium
RAZR hd... Cm10.1 on the post started by epinter.. You can read how others had the same issue. I had 4 backups and non boot looped. It would hang at the bootloader and never even make it to the boot animation. Apparently it's something nobody's seen before but me and 2 others there have experienced it. So it's not a 1 time fluke.
Sent from my XT926 using Tapatalk 2
Not sure what went wrong, but I've just had to use flashtool. I decided to flash one of the stock roms available. I don't feel any of what resulted was fault of the Rom so I won't specify. I made another backup of my tweaked Rom, and wiped as instructed and installed. Everything flashed ok but the Rom was a little buggy so I decided to restore my tweaked backup. Rebooted to reovery, wiped then selected which backup to restore. In short, the backup was showing no partitions available to restore and wouldn't work. So, I chose my original backup of stock and that showed everything so I restored. From there, the backup said complete so I rebooted. I ended up with the flashing red and blue led and could only boot to twrp. I tried to reflash the Rom zip but it failed to open. So here I am after using flashtool, which was an adventure as well. I'm curious if anyone else at all has had a similar experience? Is it possible my twrp was corrupt in some way?
Sent from my LGLS990 using Tapatalk
Had you ever tried to restore you backups prior? Just to make sure you had a good backup.
Did you use compression in TWRP? It's been an issue in the past. At least with the OG it was.
I have no other ideas. Sorry you had to go through that. But at least you got it fixed.
I hadn't restored prior to this, no. I think I did use compression on the second backup. Good point. One good thing, I don't have the ugly yellow spark boot ani any more. [emoji6]
Sent from my LGLS990 using Tapatalk
Evolution_Freak said:
I hadn't restored prior to this, no. I think I did use compression on the second backup. Good point. One good thing, I don't have the ugly yellow spark boot ani any more. [emoji6]
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
Is this after Flashtool? The only way I know of to get it back is ##RTN#. And you'll need your MSL.
You shouldn't have Wi-Fi calling either then. That's the clincher.
Be safe and backup your EFS first though.
Evolution_Freak said:
I hadn't restored prior to this, no. I think I did use compression on the second backup. Good point. One good thing, I don't have the ugly yellow spark boot ani any more. [emoji6]
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
i also used compression for my backup did you figure out if that was what caused the problem?
kMogs17 said:
i also used compression for my backup did you figure out if that was what caused the problem?
Click to expand...
Click to collapse
To be safe, boot into recovery and try to restore your backup. If you don't see the partitions listed, then it's probably compression.
Edit:
Don't wipe anything though!
Sent from my LGLS990 using Tapatalk
Evolution_Freak said:
To be safe, boot into recovery and try to restore your backup. If you don't see the partitions listed, then it's probably compression.
Edit:
Don't wipe anything though!
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
Yep yep - Im glad this is my second LG, I never use compression thanks to all I've learned from the lgog. That sucks though dude, but lesson learned.
For the record, I've flashed several things and restored several backups already(I have two, odexed stock and deodexed stock) without any issues.
Evolution_Freak said:
Not sure what went wrong, but I've just had to use flashtool. I decided to flash one of the stock roms available. I don't feel any of what resulted was fault of the Rom so I won't specify. I made another backup of my tweaked Rom, and wiped as instructed and installed. Everything flashed ok but the Rom was a little buggy so I decided to restore my tweaked backup. Rebooted to reovery, wiped then selected which backup to restore. In short, the backup was showing no partitions available to restore and wouldn't work. So, I chose my original backup of stock and that showed everything so I restored. From there, the backup said complete so I rebooted. I ended up with the flashing red and blue led and could only boot to twrp. I tried to reflash the Rom zip but it failed to open. So here I am after using flashtool, which was an adventure as well. I'm curious if anyone else at all has had a similar experience? Is it possible my twrp was corrupt in some way?
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
Noticed that you said you wiped before restore. I did that once on my G2 and ended up having to use flashtool.
leroybrute said:
Noticed that you said you wiped before restore. I did that once on my G2 and ended up having to use flashtool.
Click to expand...
Click to collapse
You should always wipe first IMO. There's always ghosts in the machine. It's just an added measure to give you a clean restore/flash. Most people that have issues with roms don't wipe, and dirty flash/restore.
I've never had an issue wiping all 4. And compression just seems to never work right. At least with all the G series.
engine95 said:
You should always wipe first IMO. There's always ghosts in the machine. It's just an added measure to give you a clean restore/flash. Most people that have issues with roms don't wipe, and dirty flash/restore.
I've never had an issue wiping all 4. And compression just seems to never work right. At least with all the G series.
Click to expand...
Click to collapse
If you wipe all four and your twrp isn't on your external SD card you're screwed if you want to restore.
I always wipe when installing roms, just not restoring. Habit from using phones without ext.
I also thought I saw a wipe script built into the restore option.
I called Sprint today to get my MSL. I needed to use the ##RTN# code to get the WiFi calling app and the other stuff back after flashtool. They had me do a factory reset first to see if that would do it but then gave me my MSL without question.
Thanks again for all the info learned in this thread. I finally got around to re-rooting and re-bumping and all were smooth and easy.
Sent from my Stump'd & Bump'd Sprint LG G3
engine95 said:
You should always wipe first IMO. There's always ghosts in the machine. It's just an added measure to give you a clean restore/flash. Most people that have issues with roms don't wipe, and dirty flash/restore.
I've never had an issue wiping all 4. And compression just seems to never work right. At least with all the G series.
Click to expand...
Click to collapse
I only had a problem with compression once on my OG for the rest of the time it worked fine and was a necessity because it had no external storage but anyway i just checked the compressed backup i made and the partitions show up under restore, but i havent tried it yet because i have no reason to. maybe when aosp comes out