Related
No matter how many times I wipe my phone I still can't flash any pic the newer roms. I have root explorer an have been able to see that nothing changes. The weird thing is I'm not getting any errors after installing a Rom. Usually if there is a media folder on my SD card but never get passed the three skateboards. I can flash tazz14 an it boots just like I never took it off my phone. An no it wasn't flashed from a nand. Need help.
Sent from my Eris using XDA App
cpole17 said:
Usually if there is a media folder on my SD card but never get passed the three skateboards.
Click to expand...
Click to collapse
I intend no disrespect, and perhaps I am alone in this, but I'm having difficulty understanding, other than in a general sense, what this sentence means.
I agree. Don't really understand what you are saying. What are you trying to flash?
I've checked some of your previous post discussing the problem. It is unlikely but possible that your recovery image has been corrupted. I would suggest that you recover from a nandroid then run jcase's one click root app, don't worry about flashing rootme.zip, but do ensure that you reboot twice after running the app. And when you flash the ROM do both Dalvik wipe and factory/data wipe. Hope this works.
http://dl.dropbox.com/u/8699733/erisone010.apk
ok sorry for the broken sentences. I let my frustration get the best of me.
I use to be able to flash any rom. One day I decided to try some of Tazz and shed's roms. I had no problem flashing up to Tazz v14 and shed's v2. I tried to flash Tazz V15 and this is when I first noticed my problems.
When I would flash v15 or higher i would get the e: error in line 238 e:wasn't able to write boot image and installation aborted.
Shed's roms don't give me the error it just says installed from sdcard. On a re-boot I just get the skateboards and it never boots. just sits there. At first I thought I didn't wait log enough so I waited 20 minutes. Never booted.
I always do a factory/data and dalvik at least 3 times before trying to load a new rom
I don't believe it has anything to do with their roms. I went all the way back to 2.1 stock and started over. then one click eris root. It seems as if i flash a new rom the new stuff doesn't overwrite over the old system files.
sounds like it could be a couple of issues.
not sure what recovery you are using... but i'd read this thread here:
http://forum.xda-developers.com/showthread.php?t=827718
could be some very useful tips for clearing space on your phone.
reason i say that... if you are getting all the way to the boot image, then it's failing... then i'd say you either have a bad DL (check the md5's), a bad recovery image (already mentioned), or you are running out of space in /system/ block (maybe the reason some ROMs are successful in flashing, and not others... as the "heavier" ROMs maybe too big to fit on whatever amount of space you have left in /system/).
if you could, load/flash a ROM that works... then, from a command line, do the following and post it:
adb remount
adb shell
busybox df -h
copy/paste the results so we can have a look
Filesystem Size Used Available Use% Mounted on
tmpfs 95.4M 12.0K 95.4M 0% /dev
tmpfs 95.4M 0 95.4M 0% /mnt/asec
/dev/block/mtdblock3 170.0M 105.8M 64.2M 62% /system
/dev/block/mtdblock5 159.5M 37.0M 122.5M 23% /data
/dev/block/mtdblock4 130.0M 47.8M 82.2M 37% /cache
not sure if this is what you mean. never ran adb before.
I'm having a similar issue where I can't get past the skating androids when flashing new ROMs. KaosFroyo v37 is the only stable ROM I can flash. I've tried numerous things to fix with no luck. I hope we can find a fix.
P.S. - My mem usage breakdown looks very similar to yours. Within a few %.
There has to be away to clear alot of that data. Just don't know enough yet to do that.
Sent from my VANILLA TAZZ using XDA App
cpole17 said:
There has to be away to clear alot of that data. Just don't know enough yet to do that.
Sent from my VANILLA TAZZ using XDA App
Click to expand...
Click to collapse
hmmm... if I correctly recall there is a delete partition command associated with fastboot. I have no idea what would come of this. Perhaps as a last resort.
I haven't given up just have had no time to work on this.
Sent from my VANILLA TAZZ using XDA App
I'm still stuck with the same prob too. Here are a few things I have tried in the past week.
1. Repartition SD Card to 1 partition.
2. Format SD Card FAT32.
3. After flashing, booting w/o SD Card.
4. Completely unrooted back to 2.1, rerooted.
All of these were followed by a fully wipe, dav wipe, flashing new ROM and reboot and all resulted in endless skating androids.
I'm just stumped.
I have a feeling that the OP has one of those Erises that cannot be overclocked to 710 MHz; all of the latest ones seem to default to that. I'd say that it would be proved if you can flash Plain Jane and it works, as that defaults to stock 528 MHz.
I did find a way to alter the xtrROMs to allow a flash and then, before restarting the phone, using ADB commands to change the default maximum clock speed to something other than 710000. See http://androidforums.com/eris-all-things-root/212791-kernel-overclock-custom-rom-s.html#post1841188
It's worth a try, anyway. I'm not sure that I'd try it with anything other than xtrROM or xtrSENSE for now; I haven't checked any other ROMs to see if that would be the proper procedure.
I have been working with Conap who writes the kernel for many of the new roms out there for the past week and we finally resolved the issue. Apparently with CFSv6+ he added CIFS support to the kernel which was causing the boot problem for me. Try flashing his rom CELB v3.8 and see if it works for you.
THIS UTILITY IS FOR FASCINATE TOUCHWIZ FROYO/GINGERBREAD ONLY
UPDATED FOR EC09 GINGERBREAD
I have created a format utility that can be used from within CWM3 recovery. Just select the ZIP in CWM3 recovery, and the package will do ALL of the work for you.
These utilities come in two independent packages which will completely format your device with EXT4. As a bonus, it will create all directories and setup all ownership and permissions in accordance to the Fascinate.
Voodoo recovery does not currently allow you an option to select a format style, and furthermore does not truly format any partition unless it runs through the Voodoo "lagfix" transition upon booting the device.
There is one caveat in order to use EXT4: you need a kernel that supports it, and this would be using a "Voodoo" style kernel that has built in support. Luckily, most of the "good" kernels available have this ready to go.
Understand that this package will completely wipe your system, data, datadata (dbdata), and cache. This is a "full" wipe of the device. If you already have a ROM installed on your device and want to keep your device the way it is, and also want EXT4, then use the Voodoo method to switch to EXT4. The reason for this is because it backs up your data before it formats.
After you use this package, you can install any ROM of your choosing, as the package will already self-manage Voodoo's methods for "enabling" or "disabling" the "lagfix".
--------
Please report if the package is not working.
A good indicator of this is if you try to install the package and it only takes 1 second to work, then says it is finished. This means it is probably not working, however, if you are formatting the same type of file system over itself with no pre-existing data on the device, it will take the aforementioned 1 second to work.
To see if it worked: mount each partition in CWM3 recovery, then adb shell into your device and type the mount command, in the listing you should see what file system your partitions are using. If the big four all say EXT4, then the package install has been successful.
In order to assure that it will work correctly, use the latest version of a CWM3 recovery that you can find. I can personally vouch for nemesis2all's OTB CWM3 Recovery v3.0.2.8x.OTBv2. Unfortunately not all CWM3 recoveries are the same, and yours may not work with these utilities. If you find a recovery that works fine, post it here and I will update this.
--------
Packages updated: 6/28/2011 - 12:57PM EST
EXT4 Format ALL (formats everything): http://www.mediafire.com/?6hx7f8g7c8vv6xz
EXT4 Format CACHE: http://www.mediafire.com/?2621a888ydv41mg
EXT4 Format DATA: http://www.mediafire.com/?ck2bb340yybpe4z
EXT4 Format DBDATA: http://www.mediafire.com/?ahxzs8xsyyvemed
EXT4 Format FOTA: http://www.mediafire.com/?42ijpi67grdb6mm
EXT4 Format PREINSTALL: http://www.mediafire.com/?d42as1l3pdbhr2t
EXT4 Format SYSTEM: http://www.mediafire.com/?rgs46hhq8qd951t
--------------------
If you like my work, consider donating, or thanking me by clicking the thanks button
thanks for this
navenedrob said:
I have created two format utilities that can be used from within CWM3 recovery. Just select the type of file system you want to use, select it in CWM3 recovery, and the package will do ALL of the work for you.
These utilities come in two independent packages which will completely format your device with either RFS or EXT4. As a bonus, it will create all directories and setup all ownership and permissions in accordance to the Fascinate.
Voodoo recovery does not currently allow you an option to select a format style, and furthermore does not truly format any partition unless it runs through the Voodoo "lagfix" transition upon booting the device.
There is one caveat in order to use EXT4: you need a kernel that supports it, and this would be using a "Voodoo" style kernel that has built in support. Luckily, most of the "good" kernels available have this ready to go.
Understand that this package will completely wipe your system, data, datadata (dbdata), and cache. This is a "full" wipe of the device. If you already have a ROM installed on your device and want to keep your device the way it is, and also want EXT4, then use the Voodoo method to switch to EXT4. The reason for this is because it backs up your data before it formats.
After you use this package, you can install any ROM of your choosing, as the package will already self-manage Voodoo's methods for "enabling" or "disabling" the "lagfix".
Please report if the package is not working.
A good indicator of this is if you try to install the package and it only takes 1 second to work, then says it is finished. This means it is probably not working, however, if you are formatting the same type of file system over itself with no pre-existing data on the device, it will take the aforementioned 1 second to work.
To see if it worked: mount each partition in CWM3 recovery, then adb shell into your device and type the mount command, in the listing you should see what file system your partitions are using. If the big four all say EXT4 or RFS (depending on script used), then the package install has been successful.
In order to assure that it will work correctly, use the latest version of a CWM3 recovery that you can find. I can personally vouch for nemesis2all's OTB CWM3 Recovery v3.0.2.8x.OTBv2. Unfortunately not all CWM3 recoveries are the same, and yours may not work with these utilities. If you find a recovery that works fine, post it here and I will update this.
Click to expand...
Click to collapse
Ok, I think I'm having a complete idiot moment here so please be patient with me. What would be the benefits of me running this on my device that is currently running jt's CM7 with OTB 1.5 kernel and EXT4 (voodoo for those who don't know) already converted? Thanks in advance.
It would be of no use. Unless you need to format your entire device.
So this would be a good thing to flash in place of wiping between rom flashes? Does it have any benefits compared to a regular data and cache wipe when you are already converted to ext4?
It would be a good idea to flash it in that scenario, yes. Currently no ROM will do the job that this package will for you, which is why a lot of ROM's say not to wipe your device, because you'll run into major issues if you do. When you do your "wipes" through recovery it doesn't really do anything besides a recursive delete of files, so it doesn't really format anything (even though it says "format" in the menu system). The only time it actually does any formatting is during the Voodoo transition. When you do wipe those areas, it does not leave the file structure intact and also does not leave the ownership and permissions intact. These packages completely solve that problem. Also, these packages are focused on performance so everything is done that is possible to make sure that your file system is as fast as possible.
navenedrob said:
It would be a good idea to flash it in that scenario, yes. Currently no ROM will do the job that this package will for you, which is why a lot of ROM's say not to wipe your device, because you'll run into major issues if you do. When you do your "wipes" through recovery it doesn't really do anything besides a recursive delete of files, so it doesn't really format anything (even though it says "format" in the menu system). The only time it actually does any formatting is during the Voodoo transition. When you do wipe those areas, it does not leave the file structure intact and also does not leave the ownership and permissions intact. These packages completely solve that problem. Also, these packages are focused on performance so everything is done that is possible to make sure that your file system is as fast as possible.
Click to expand...
Click to collapse
Ok, so basically what you are saying is this would be ideal to use instead of data/cache/dalvik wipe for rfs to rfs and ext4 to ext4, correct? Thanks in advance.
That's correct.
I've teamed up with nemesis2all and we are thinking about adding all of these abilities to the OTB kernel, so you'll be able to choose different kinds of file systems and format options through CWM3 recovery instead of having to use these packages here. That will come when it comes, but for now this is the ideal solution.
EXT2/EXT3/EXT4/XFS/RFS etc...
Also, I've updated the attachments in the post.
navenedrob said:
That's correct.
I've teamed up with nemesis2all and we are thinking about adding all of these abilities to the OTB kernel, so you'll be able to choose different kinds of file systems and format options through CWM3 recovery instead of having to use these packages here. That will come when it comes, but for now this is the ideal solution.
EXT2/EXT3/EXT4/XFS/RFS etc...
Also, I've updated the attachments in the post.
Click to expand...
Click to collapse
Just to let you know, I ran the ext4 package and I got some serious lag issues after I installed my rom and it actually starting going into a soft boot loop. It began to act very weird and unstable. I booted back into recovery and I wiped everything the way I usually do and formatted the system/data/dbdata/cache manually in mounts and storage and reinstalled. It's better than it was but it still seems like it is kinda slower and more laggier than it was before I ran the package. Any ideas? Thanks man.
You'll need to give me more information than that to determine your problem.
What kernel are you using? What recovery are you using? What ROM are you running? What are the results of running the mount command with all partitions mounted?
navenedrob said:
You'll need to give me more information than that to determine your problem.
What kernel are you using? What recovery are you using? What ROM are you running? What are the results of running the mount command with all partitions mounted?
Click to expand...
Click to collapse
OTB 1.5, CM7. It's kinda weird. When I ran your package and then flashed cm7 and booted it, it was laggier than I have ever seen my phone and when I would try to do certain operations it would soft boot. At one point I couldn't even turn wifi on. So, I booted back into recovery and wiped and manually formatted everything and reinstalled everything. After that it was still kind of laggy but much better. I restored all of my apps and got my phone back to all my custom settings. Then I began to notice that it wasn't really lagging anymore, in fact it seemed pretty snappy. I ran quadrant to see if the numbers were the same as before to determine if I was in fact ext4 converted. Surprisingly the numbers were higher than normal. And I even noticed in titanium backup that some of my internal memory had been freed up. I can't explain it but everything seems to be running really good right now. It's almost like after running your package the phone had to be conditioned, and once it was conditioned it ran real good. But, that doesn't explain why it was soft booting and wifi wouldn't work. Who knows.
Not really sure exactly, it actually could have been a few different things causing the "issues". I'm going to try your exact scenario and see what happens.
kidserious said:
OTB 1.5, CM7. It's kinda weird. When I ran your package and then flashed cm7 and booted it, it was laggier than I have ever seen my phone and when I would try to do certain operations it would soft boot. At one point I couldn't even turn wifi on. So, I booted back into recovery and wiped and manually formatted everything and reinstalled everything. After that it was still kind of laggy but much better. I restored all of my apps and got my phone back to all my custom settings. Then I began to notice that it wasn't really lagging anymore, in fact it seemed pretty snappy. I ran quadrant to see if the numbers were the same as before to determine if I was in fact ext4 converted. Surprisingly the numbers were higher than normal. And I even noticed in titanium backup that some of my internal memory had been freed up. I can't explain it but everything seems to be running really good right now. It's almost like after running your package the phone had to be conditioned, and once it was conditioned it ran real good. But, that doesn't explain why it was soft booting and wifi wouldn't work. Who knows.
Click to expand...
Click to collapse
It's possible that since you wiped your market was trying to restore all your apps in the back ground which was taking all your memory up and making your phone lag. But after you restored all your apps it was all set
Coreyc1123 said:
It's possible that since you wiped your market was trying to restore all your apps in the back ground which was taking all your memory up and making your phone lag. But after you restored all your apps it was all set
Click to expand...
Click to collapse
What I meant was as soon as it booted (during setup wizard) it was super laggy. I download TB from the market by itself and it took forever to register. I was doing the GPS fix and it soft booted. I couldn't turn wifi on and it soft booted. All before I did a batch restore in TB. And I know that the market begins to sync automatically as it always does but this was much much different.
Sent from my SCH-I500 using Tapatalk
kidserious said:
What I meant was as soon as it booted (during setup wizard) it was super laggy. I download TB from the market by itself and it took forever to register. I was doing the GPS fix and it soft booted. I couldn't turn wifi on and it soft booted. All before I did a batch restore in TB. And I know that the market begins to sync automatically as it always does but this was much much different.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
I had these same symptoms one time that I installed kasonate v7, but after reflashing, the next time it didnt.
I know you're not talking about the same cm version, but they might be related and not related to the format utility.
Ok, I ran this package again to make sure that I didn't do something wrong and to see if I would get the same results. I ran the package, flashed cm7 then gapps then OTB GB 1.5. all from the recommended recovery in your post. Again I ended up in a soft boot loop and wifi was acting up again and was causing a boot loop. So once again I booted into recovery and wiped data/cache/dalvik normally and formatted manually via mounts and storage and reinstalled again and she's running like a dream. Very weird but I must say I am very happy with the results I ended up with, regardless of how I got them. So obviously, this was not your intention for it to be done this way but I do see an improvement in responsiveness, speed and memory being freed up. Before, my free internal memory was 1.49 and now it is 1.52. Thank you sir, I appreciate this.
Thanks for this utility! Works great. Went from Jt's cm7 to the miui/touchwiz rom and ran the utility in between. My phone is running faster than ever and no issues. Thanks again!
Sent from my SCH-I500 using XDA App
Yeah running this on mesmerize with heinz 57 best my phone has ever run quadrant of 2250s @ 1.5 ghz
Sent from my SCH-I500 using XDA App
stephenj37826 said:
Yeah running this on mesmerize with heinz 57 best my phone has ever run quadrant of 2250s @ 1.5 ghz
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
You're welcome, the utility enables a few nice options as far as file system performance is concerned, that Voodoo doesn't at this time.
Do tell oh and thanks a million
Sent from my SCH-I500 using XDA App
Hi,
My EVO 4G LTE is S-OFF. I've been running FreshROM 5.3.1 since it was released without issue. Last Thursday I started getting a lot of backround app crashes. Not a big deal, I wiped, reloaded the ROM, then restored everything via Titanium Backup pro. All was well for a couple of days.
Yesterday, my battery died within about 3 hours. Normally, I go over 16 hours. After some investigation and I found a process 'flush-179:0' eating CPU (and battery). I've wiped, flashed again, even flashed different ROMs. It's still there; every time.
I found one post on XDA where someone said it was caused by a performance tweak app (http://forum.xda-developers.com/showthread.php?t=2016993). Their fix was to flash stock, radios, etc. then root again. I haven't used any apps to tweak anything. So, if it's a similar cause...data/config corruption?
Has anyone else seen this? Does anyone know of a fix?
Thanks!
I'm not familiar with this specific issue but you mentioned that you restored everything using titanium backup. If you are experiencing problems I would strongly recommend NOT restoring all data as you may be restoring that very same issue. If you don't want to have to start all over then at least only restore just apps and data. Never system data.
Sent from my EVO using Tapatalk 2
eddy0090 said:
I'm not familiar with this specific issue but you mentioned that you restored everything using titanium backup. If you are experiencing problems I would strongly recommend NOT restoring all data as you may be restoring that very same issue. If you don't want to have to start all over then at least only restore just apps and data. Never system data.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Of course, the problem is that it's there when I wipe and flash a new ROM (Fresh, Rejuvenated, etc.). Even before I load my data via TB.
zisix said:
Hi,
My EVO 4G LTE is S-OFF. I've been running FreshROM 5.3.1 since it was released without issue. Last Thursday I started getting a lot of backround app crashes. Not a big deal, I wiped, reloaded the ROM, then restored everything via Titanium Backup pro. All was well for a couple of days.
Yesterday, my battery died within about 3 hours. Normally, I go over 16 hours. After some investigation and I found a process 'flush-179:0' eating CPU (and battery). I've wiped, flashed again, even flashed different ROMs. It's still there; every time.
I found one post on XDA where someone said it was caused by a performance tweak app (http://forum.xda-developers.com/showthread.php?t=2016993). Their fix was to flash stock, radios, etc. then root again. I haven't used any apps to tweak anything. So, if it's a similar cause...data/config corruption?
Has anyone else seen this? Does anyone know of a fix?
Thanks!
Click to expand...
Click to collapse
u should try mean rom 6.5 ICS.. if your still on the old base.. or flash new firmwear and radio in bootloader then flash a new jelly bean rom if u want to try the new base out
evo401 said:
u should try mean rom 6.5 ICS.. if your still on the old base.. or flash new firmwear and radio in bootloader then flash a new jelly bean rom if u want to try the new base out
Click to expand...
Click to collapse
I think I will; this seems to fit with the latest info I just figured out.
I flashed Fresh again, and suddenly started getting the warning about the SD card being damaged and to format it (as we know, that's not the external SD card). No matter how many times I format it, the error comes back. From some other searching, the 'flush-179:0' process seems to have something to do with storage, maybe because it can't read that partition it's causing issues.
I updated the firmware and radio, still no luck.
So I tried loading another ROM (I went with Mean Bean). That fixed the issue with the SD Card partition being unreadable/unformatable. Maybe that was caused by multiple flashes
But, the flush-179:0 process is still eating CPU and battery.
zisix said:
I updated the firmware and radio, still no luck.
So I tried loading another ROM (I went with Mean Bean). That fixed the issue with the SD Card partition being unreadable/unformatable. Maybe that was caused by multiple flashes
But, the flush-179:0 process is still eating CPU and battery.
Click to expand...
Click to collapse
?? i never heard of that flush-197:0?? could it be an app u downloaded maybe.. if u flash meanbean over abd dont install any app does is that flush-179 still there or it it there after u install yoir apps?
evo401 said:
?? i never heard of that flush-197:0?? could it be an app u downloaded maybe.. if u flash meanbean over abd dont install any app does is that flush-179 still there or it it there after u install yoir apps?
Click to expand...
Click to collapse
As far as I can tell, it's part of Fresh 5.3.1 and other ROMs I had on my SDCard that are based on the old OTA. The latest Mean Bean doesn't have the same issue after wipe & flash.
I emailed flipz (the Fresh dev), though who knows if/when he'll get back to me. For now, I'm thinking about running MeanBean for a while.
You really can't go wrong with mikeyxda and his mean series of ROM's. That man consistently puts out quality work. No doubt about it.
zisix said:
I flashed Fresh again, and suddenly started getting the warning about the SD card being damaged and to format it (as we know, that's not the external SD card). No matter how many times I format it, the error comes back. From some other searching, the 'flush-179:0' process seems to have something to do with storage, maybe because it can't read that partition it's causing issues.
Click to expand...
Click to collapse
You nailed it. I was having issues with the flush-179 system process taking up 100% of my CM10's (JB) CPU time. It got so bad that I couldn't even reboot or shutdown without pulling the battery, which of course caused other problems. Initially I thought the "System" process was just out in the weeds, but by using OS Monitor and unchecking "Hide System Process", I was able to find the flush-179 culprit.
My first clue that it might be SD card-related was obtained after opening a terminal window and typing 'mount'. The line for /mnt/sdcard showed (paraphrased):
# mount
...
/dev/block/vold/179:65 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,...
...
Realizing that a "flush" process probably had something to do with filesystem caching and seeing the "179" in the mount output, I focused on my SD card. After pulling the card, backing it up, formatting, and restoring it in Windows, I am happy to report that my little Android has been fast, snappy, and problem-free for several days now.
- Dave
I've tried several times to install the custom ICS ( [ROM] CM9 / LiquidSmooth / AOKP / Random ICS ), but WiFi is not coming on.
Any ideas how to resolve this?
Better yet, I am trying to flash the latest ICS ROM to my thunderbolt that is stable.
Seems most have some sort of reboot problem
So far I have tried all the Liquid Smooth - very nice ROMs but get random reboot
PS
From about phone, I see the following
Mode version: liquid mecha.mr3.100212
Build number: Liquid ICS v1.5MR3-JMOD
Radio: 2.00.00.0308, 0.02.00.0312r
brochild said:
Better yet, I am trying to flash the latest ICS ROM to my thunderbolt that is stable.
Seems most have some sort of reboot problem
So far I have tried all the Liquid Smooth - very nice ROMs but get random reboot
PS
From about phone, I see the following
Mode version: liquid mecha.mr3.100212
Build number: Liquid ICS v1.5MR3-JMOD
Radio: 2.00.00.0308, 0.02.00.0312r
Click to expand...
Click to collapse
Maybe THIS helps?
I just stumbled unto that site by accident (I love it)
I have registered and downloaded the nusense ROM (Beta v10.8) and will report my findings.
Thanks for the great work(on your ROM) and for the quick reply.
brochild said:
I just stumbled unto that site by accident (I love it)
I have registered and downloaded the nusense ROM and will report my findings.
Thanks for the great work(on your ROM) and for the quick reply.
Click to expand...
Click to collapse
No problem, hope you enjoy.
There's also a DeSensed version, called UnSense, which you likely saw as well.
See ya around that way.
Yes, I saw it and am trying to learn the differences between these 2 ROMs - so far better battery life stands out
Looks like I will be spending a lot more time there.
By the way, I was looking at your ext4 instructions (re-printed below for clarity - hope you don't mind)
Select Wipe/Format Menu Option
Wipe cache and dalvik
In the same Wipe/Format Menu: Wipe all partitions except SD
Now back in 4ext main menu: Select Tools
Select Format ext3 option I chose ext4 instead of ext3
Format Cache
Format Data
Format System
Now go back to the main menu and select the rom .zip to install
I chose ext4 instead of ext3 - could this be the cause of my random reboots using Liquid Smooth ICS ROM?
When I flash your ROM, I will choose to format ext3 - just to be sure (heh heh heh):laugh:
brochild said:
By the way, I was looking at your ext4 instructions (re-printed below for clarity - hope you don't mind)
Select Wipe/Format Menu Option
Wipe cache and dalvik
In the same Wipe/Format Menu: Wipe all partitions except SD
Now back in 4ext main menu: Select Tools
Select Format ext3 option I chose ext4 instead of ext3
Format Cache
Format Data
Format System
Now go back to the main menu and select the rom .zip to install
I chose ext4 instead of ext3 - could this be the cause of my random reboots using Liquid Smooth ICS ROM?
When I flash your ROM, I will choose to format ext3 - just to be sure (heh heh heh):laugh:
Click to expand...
Click to collapse
You can't use ext4 file system with nusense or unsense yet because the kernel doesn't support it. The random reboots with twisted ics could be related but I can't be sure since I haven't used it in a while.
Sent from my ADR6400L using Tapatalk 2
I tried the nusense ROM and formatted using ext3
Am still getting WiFi to drop randomly
At times it turns itself off - when it does that I see "out of range'.
Google Market changed to "Google Play", and most of the times that process stops working and prevent me from installing my apps
WiFi turns off and prevent update from Google Play as well - since I have it setup to update over WiFi
Also, am getting lots of process is not responding messages like "process.com.android.phone is not responding"
I get these messages very frequently.
I may go back to using LiquidSmooth ICS8 mr3v1
Are you sure you formatted all the partitions in ext3? The only way I get those messages are when I don't format properly. Also, maybe try clearing cache and data in the phone app and as for the market trying clearing data and cache. It may not hurt to run a fix permissions in the recovery. Does you wifi problem only happen with ics roms?
Sent from my ADR6400L using Tapatalk 2
If you do not format all partitions in ext3 format, you will have issues.
If you are not waiting until after the initial setup to sign into the market, that is likely an issue.
You need to wait until the home screen has set up and the device settles.
Then reboot, wait a minute and then sign into the market.
In my FAQ, you will see, the Market is the Play Store, no difference, just themed.
It has updated since the rom's last update and will do so when you sign in.
It's just an incremental update, but the theme goes away that I included for it an so does the custom icon and "Market" name.
If you do the above and still have issues, clearing the market (Play Store) app data and cache should sort you out.
If you are restoring data from another rom, then that is why you are also having force closes or wifi issues.
You cannot restore wifi data from an AOSP based rom that uses a GB kernel and expect that the same config will work well with the ICS rom and kernel.
disconnecktie said:
Are you sure you formatted all the partitions in ext3? The only way I get those messages are when I don't format properly. Also, maybe try clearing cache and data in the phone app and as for the market trying clearing data and cache. It may not hurt to run a fix permissions in the recovery. Does you wifi problem only happen with ics roms?
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Yes, I am sure I formatted the partition in ext3
I cleared data, davlik factory reset etc
The only thing I did not do was "fix permission"
After installing all my apps, I booted to recovery and did the swipe thing again
Yes, my WiFi issue is only with ICS ROM, specifically this one (during and after setup)
So far the LiquidSmooth ICS 1.5 MR3 is working the best for me.
No WiFi issues at all, but I still do get occasional reboots.
Did you wipe boot and system partitions before flashing the rom?
Sent from my ADR6400L using Tapatalk 2
santod040 said:
If you do not format all partitions in ext3 format, you will have issues.
Click to expand...
Click to collapse
Yep, I did that
santod040 said:
If you are not waiting until after the initial setup to sign into the market, that is likely an issue.
You need to wait until the home screen has set up and the device settles.
Then reboot, wait a minute and then sign into the market.
Click to expand...
Click to collapse
I waited as instructed
santod040 said:
In my FAQ, you will see, the Market is the Play Store, no difference, just themed.
It has updated since the rom's last update and will do so when you sign in.
It's just an incremental update, but the theme goes away that I included for it an so does the custom icon and "Market" name.
If you do the above and still have issues, clearing the market (Play Store) app data and cache should sort you out.
Click to expand...
Click to collapse
I followed your instructions to the letter
santod040 said:
If you are restoring data from another rom, then that is why you are also having force closes or wifi issues.
You cannot restore wifi data from an AOSP based rom that uses a GB kernel and expect that the same config will work well with the ICS rom and kernel.
Click to expand...
Click to collapse
I am starting WiFi from scratch by turning it on, wait for it to scan and locate available networks.
Then I select my SSID and enter my keys to activate it.
At times I am downloading from Google Play, and will loose WiFi intermittently.
At times, I am viewing email messages, and will loose WiFi intermittently.
I was tempted to downgrade my RADIOS -but decided to go back to LiquidSmooth ICS 1.5 MR3
disconnecktie said:
Did you wipe boot and system partitions before flashing the rom?
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Yes Sir, I did all that
I really appreciate all your efforts and your replies both to you and to Santod, I really, really do!
At this time, I resign myself to the fact that some of these ICS ROMs are not yet in their final stages and will wait patiently.
A huge Thanks for the great work to all developers, busting their humps to get this done.
I'm back baby
A funny thing happened to me yesterday, and I'm still laughing
Previously, I mentioned that I was tempted to downgrade my radio, but decided to go back to Liquid ICS v1.5MR3V1
So far I was still getting random reboots - way too many for my taste.
After reading numerous posting, I decided to roll back my radio from 2.00.00.0308, 0.02.00.0312r to 1.49.00.0406w_1,0.01.79.0331w_1.
But, in doing so, I accidentally installed the leaked ICS ROM instead (2.11.605.19).
So I thought I was downgrading my radio, but ended up installing the leaked ROM :laugh:
Incidentally, I also un-rooted my T-bolt - Thanks to the new tool I was able to quickly root it back.
Luckily, I also backed up the previous ROM, and was able to restore it.
All in the sudden, my T-bolt is back - everything is working fine and no more reboots :victory:
To Recap, after downgrading my radio to the leaked radio 1.49, all is well again .
My T-bolt is running so good that I am hesitant to load the latest ROMs.
My choices are the nuSense beta 17.2 or AOSP 4.0.4 ICS [Multi-Source]
Is it a wise decision to upgrade or should I stay put
That updated nusense is amazing but I wouldn't run it with the full leaked radios. I use the combo of the. 19/leaked radios and they work great.
Sent from my ADR6400L using Tapatalk 2
Why should I try NuSense ROM by Santod
disconnecktie said:
That updated nusense is amazing but I wouldn't run it with the full leaked radios. I use the combo of the. 19/leaked radios and they work great.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Thank you sir, for your prompt reply!
Sounds like I need to give the NuSenseROM a try, but ....
1) what's so amazing about it, and how does it differ from what I'm currently using (where can I get screenshots)
a) I know its been reworked - but that's over my head (for now)
2) I am not entirely sure what the combo 19/leaked radio is, is it this ".19 cdma and the ICS LTE radio" posted by Santod?
Thanking you in advance.
1) Basically everything works the way it was intended to. Camcorder included. Only drawback is battery is slightly worse than Twisted's build.
A) He rebased the rom using the official Droid Incredible 2 ota which is a better base since the original base was from the leak that sucked balls big time.
2) Yes
Sent from my ADR6400L using Tapatalk 2
I now have the NuSenseROM installed - so far so good.
No reboots yet and I am still using the 1.49.00.0406w_1,0.01.79.0331w_1 radio
The ROM is nearly flawless, but I wish it had the phone dialer interface, and the people interface of the Liquid Smooth ROM
I love the fact the camcorder works, but I wish it also had the ICS camera (But I can download it).
I am using Go SMS Pro, and this ROM is not linking my accounts pictures there (bummer)
The Liquid Smooth ROM showed my accounts picture on that app.
I am using and synchronizing my Google, Verizon, Facebook, and Voxer accounts
Hello,
I posted this same question over at androidforums.com.
I rooted my phone and installed the rooted stock 4.3 from Beanstown " [Rom][I605VRUEMJ9][4.3] Stock Root Odex/Deodex [12/08/13]★ - xda-developers "
I installed the deodexed version.
I then followed the rest of the directions to fix the wifi, and also loaded the framework to gain wifi tether.
The phone was working fine for a few days.
Then I got the system UID error after the battery drained all the way over night.
I could no longer run / install certain apps and I would get random reboots. I tried deleting those apps from data/data. this did help with most of the apps but not all. Regardless the UID error would not go away.
SO I wiped the data . Factory reset. I wiped 3 or more times. Loaded the rom back. This time I didn't load the framework or the wifi fix. I believe those were still in effect because the wifi still worked and the wireless thether still worked.
Now a whole bunch of apps still would not install. Very frustrating. A few days later I got the system UID error again,
SO this morning I wiped the phone like 8 times. loaded the rom again. I still cant install certain apps.
I am so fed up with this phone right now. I used to love this phone before 4.3 . Now this phone is wasting my time. Im way too busy to be working on my phone every few days. This phone is supposed to assist me with work, not cause more work for me.
Can someone please please advise me what to do?
I think I need to re format. But I have no idea how to do that.
by the way I have CWM recovery.
I went into clock work and formatted my internal sd card. in CWM its called the external for some reason. there were a few options that I wasnt sure about. I chose ext to be 4096, swap to be 256 and the last was the file structure. I choose 3 .
Im still having the same issues.
I just want my phone working again
Im going to use Odin to to the PIT and flash the stock vram3. Then Re root... Maybe I should just stick with 4.1.2 .
OK so that worked!
I returned to stock.
THen re rooted with Casual. Im going to stay here and avoid 4.3. 4.3 is a terrible terrible experience. Ill miss some of the added features like "blocking mode" but Ill live without.
The mistake was that joke 4.3 beanstown rom. Can I reccomend http://forum.xda-developers.com/showthread.php?t=2603295
Mean bean is by far the best i605 rom in my eyes. I loved mikeys 4.1 build and the new 4.3 mean bean is incredible.
Sent from my SCH-I605 using Tapatalk
I had similar issues with CM11 latest nightly until I wiped all partitions with latest TWRP recovery then copied CM11 (Android 4.4.2) and gapps over via adb push. So, I think the key is wiping all partitions including data, cache, dalvik, system, internal sdcard and external sdcard.