Related
So here is one for ya.
I can't access my SD Card at all with this http://forum.xda-developers.com/showthread.php?p=25816870#post25816870 rom installed. I click to mount SD card and nothing happens. In recovery I can access the SD card backups etc
I find it strange. Although I do have to ask, I have been having this weird problem. I have Clean Rom 4.3 Installed (ICS) and I have been getting some random reset's and slow this or that. So I saw 4.5 was out - It literally reset everyime your open something and I mean anything Bam reset. However I installed the above rooted bleh bleh stock os (I do not have s-off so I used the PH img) I made sure I had no other boot images on there. Installed setup got everything ready. I have gotten 3 resets in 11 mins so far so now I backed up to Clean rom 4.3 and I have no idea what to do.
I also did the following:
Flashed back to STOCK o.s.
Then Downloaded the above linked rom, cleared data (everything) installed software patch and rom reset back up and same problem. I have been flasing rom's on this phone for a while now and this is the first time no matter what that I get these crashes and resets. Did I miss something?
You really should s-off that puppy. It is pretty easy, and will get you out of messes.
Sent from my ADR6425LVW using Tapatalk 2
Jason L said:
So here is one for ya.
I can't access my SD Card at all with this http://forum.xda-developers.com/showthread.php?p=25816870#post25816870 rom installed. I click to mount SD card and nothing happens. In recovery I can access the SD card backups etc
I find it strange. Although I do have to ask, I have been having this weird problem. I have Clean Rom 4.3 Installed (ICS) and I have been getting some random reset's and slow this or that. So I saw 4.5 was out - It literally reset everyime your open something and I mean anything Bam reset. However I installed the above rooted bleh bleh stock os (I do not have s-off so I used the PH img) I made sure I had no other boot images on there. Installed setup got everything ready. I have gotten 3 resets in 11 mins so far so now I backed up to Clean rom 4.3 and I have no idea what to do.
I also did the following:
Flashed back to STOCK o.s.
Then Downloaded the above linked rom, cleared data (everything) installed software patch and rom reset back up and same problem. I have been flasing rom's on this phone for a while now and this is the first time no matter what that I get these crashes and resets. Did I miss something?
Click to expand...
Click to collapse
I assume you're always wiping data and cache.
Have to tried Fix Permissions? I don't know if this rom has it in it's settings, but using others I've corrected some weirdness by wiping the cache and then running fix permissions.
Were you seeing the same thing with the stock rom? Or just using clean rom? Might try a different rom for a bit to see if the issues follow you there.
S-OFF isn't going to help you with this. It's perfectly fine to flash your boot image outside of Aman-Ra. I do it all the time.
Are you wiping everything between flashes?
I recommend using this - http://forum.xda-developers.com/showthread.php?t=1562176&highlight=clean
Flash it first and it wipes the needed partitions clean.
If you're still on the GB firmware, you need to flash the old firmware patch after the rom install also to get SD card access.
If none of the above helps and you're still on the GB firmware, set the phone back to stock using the GB RUU, otherwise you will have to s-off it so you can do the same.
Yep full wipes between flashes. I didn't keep the stock Rom for more than about 20 mins.
I didn't see a way with the debloated stock New leak to fix permissions. But with the 4.5 clean Rom I did that and it made no difference.
Delete
Sent from my ADR6425LVW using Tapatalk 2
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Thanks for the reply!
I didn't check the MD5 last night but I did just now and it matches.
I did a cache wipe the first time but not a system wipe. Then I started getting more desperate and tried reinstalling w/ system wipes and factory resets, but it didn't change anything.
No, I didn't change the ROM. Doing the Bootloader unlock exploit was about the absolute maximum of my technical abilities! The only thing I know I did wrong was that I didn't downgrade to the old boot version the first time (mainly because the wifi thing sounded inconsequential and I didn't want to learn the procedure if I didn't have to).
Anyway, I just tried Ultimate KangBang and it seems to work--no error messages so far. I don't know what I did wrong, but hopefully this keeps working!
IceDragon59 said:
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
Click to expand...
Click to collapse
andybones said:
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Click to expand...
Click to collapse
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
franklin411 said:
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
Click to expand...
Click to collapse
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
in the future it is always good practice to backup(nandroid) your current ROM. I have been burned too many times, always do a nandroid before you do anything in recovery.
your photos are normally saved to the SD, flashing ROMs or wiping the system will not delete them
andybones said:
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
Click to expand...
Click to collapse
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
franklin411 said:
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
Click to expand...
Click to collapse
na the name has nothing to do with it. it can be named whatever.
im guessing the wipe worked.
franklin411 said:
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Click to expand...
Click to collapse
weird, i was having the same problem with the same processes stopped working. i wiped cache dalvik and system but not factory reset. once i factory reset, it worked fine. i figured a system wipe would have been enough....
hey there
i hope my phone is not bricked, but i've been looking now for two hours for a solution and haven't found anything.
I have a rooted GT-9100 with jelly bean 4.1.2 XWLS8 official Samsung Rom.
In the last few days i was having problems with many apps, especially the video player and the gallery app, which wouldn't start because there wasn't enough memory (even after having deleted all the trash files and dumpstate files).
as i had not made a data wipe after updating from xwssl to xwls8 (i rooted afterwards, i didn't want to reconfigure everything again), i wanted to make a backup before i would try the data wipe now.
So i made the backup with my Rom Toolbox pro on the sd card, rebooted the phone to recovery mode, wiped the data and rebooted the phone. as always the starter mode wanted me to select the language, which i did and then suddenly the screen went black.
It started to reboot and since then the phone is hanging in the Samsung Logo.
i've tried to wipe data, wipe cache partition, wipe kalvik, no success.
tried to restore from the backup i made this morning, says md5 mismatches.
what now? any suggestions?
kind regards skapo
Sent from my girlfriend's GT-S5830 using xda app-developers app
Back to ICS stock (not 4.0.4) via Odin (Get one from Samfirmware or AndroidFirmwares.net), that will give you a clean slate & you can go from there.
Edit - Or....Search on here for the md5 mismatch thing with your backup. There's been plenty of threads on here over the past 18 mths or so. Not sure if these methods work all the time (or even at all, I've never had the problem so never had to use them), but you might as well find the threads & see if any of the suggestions for fixes work for you. Could save you doing a clean install of stock & starting again (which will obviously be somewhat time consuming).
thx for the fast reply
why ics? isn't jb stable enough?
is there actually a pure rom like the nexus phone for the s2? i was wondering if the touchwiz from samsung might be responsible for so many problems...
Sent from my GT-S5830 using xda app-developers app
Worry about all that once you get the phone working normally again, this should be the only thing you're thinking about right now. First thing's first
yeah, you're right. i'll give it a shot i'll update this post tonight. thx
UPDATE:
Ok, i've reinstalled a ICS 4.0.3 I9100XXLPS, Buildnumber IML74K.XWLP7 (whatever this may be, where is the guide to the structure of Android and all the definitions, can't find any proper introduction).
It seems to work fine, but i had to wipe data and wipe cache partition, otherwise the phone still got stuck in the boot loop.
So what now? I've tested the root access, which of course isn't available anymore after flashing the ICS Stock ROM.
Do i need to install first a JB ROM with root access to (try to) restore from my backup or can i do it right from here rooting the ICS ROM?
Almost Solved
sKapo_daVinci said:
yeah, you're right. i'll give it a shot i'll update this post tonight. thx
UPDATE:
Ok, i've reinstalled a ICS 4.0.3 I9100XXLPS, Buildnumber IML74K.XWLP7 (whatever this may be, where is the guide to the structure of Android and all the definitions, can't find any proper introduction).
It seems to work fine, but i had to wipe data and wipe cache partition, otherwise the phone still got stuck in the boot loop.
So what now? I've tested the root access, which of course isn't available anymore after flashing the ICS Stock ROM.
Do i need to install a JB ROM first with root access to (try to) restore from my backup or can i do it right from here rooting the ICS ROM?
Click to expand...
Click to collapse
OK, i think i've got the problem solved:
The first thing i tried is to root the ICS and restore with the CWM. Interesting that this time it didn't give me any md5 mismatch, but it suddenly stopped during the process and the phone booted normally to ICS, in other words the restore didn't work.
So I downloaded the latest SGS2 JB I9100XWLSJ again (i had that one installed before the whole mess), i thought that the one i had installed before may have been corrupted. I flashed the ROM, wiped data, cache and dalvik cache and rooted the phone with Siyah. From there i tried to restore again, but again it stopped because of the md5 mismatch.
At least the new JB ROM booted successfully, which allowed me to access the backup file in the phone's internal sd with my PC.
I edited the nandroid.md5-file with notepad ++ and the md5 calculator. There's a good instruction from here. The folder distribution from the original instruction is a little bit confusing, that's why i've uploaded another one
I recalculated every md5 number for each file in the backup (except the nandroid.md5-file itseld of course and in some cases the .android_secure.img [i didn't have such a file]) and modified the md5 numbers inside the nandroid.md5-file.
That solved my problem :laugh: I was able to restore from my backup .
Even so, the video player app is still crashing. I restored my files and all the config, but with it the same problems i had before :crying:
Good work on finding a solution & posting it here, I'm sure it will help someone at some point in the future
Re: the FC's with the video player (which one ?), sounds like restoring it/it's settings is causing you problems. You might want to try clearing data on it first - go into settings/apps/all & select the app, then clear data; and if that doesn't work, uninstall it then do a clean install without restoring the app or settings. If the settings were backed up on ICS & you're currently using JB, that may be the cause of the FC's.
sKapo_daVinci said:
I edited the nandroid.md5-file with notepad ++ and the md5 calculator. There's a good instruction from here.
Click to expand...
Click to collapse
Thank you so much for bringing that thread to my notice! Could be useful in the future..:thumbup:
And good work solving it on ur own. XDA needs more guys like u!
If u do manage to solve all ur issues, please add [SOLVED] to the title of ur post, so that others too may benefit from ur solution.
"To err is human, to forgive is divine"
Sent from my SGS II
I normally don't post unless I've exhausted every other option.
But this issue I am having has completely baffled me, and I really have exhausted every thing I know.
I was going through a rash of flashing roms on my I9300.
After finding an issue downgrading from 4.2.2 back down to 4.1.2. I Odin back to stock... so I though ok lets have another go at it.
However... Every ROM I flash will not boot (ie stuck @ Samsung I9300 screen). The flash goes well, MD5's are all ok, and I made sure to wipe data and cache like I've don't 500 times b4 on a dozen different phones.
I've even tried keeping the stock rom, simply rooted and just flashing another kernel both speedmod and siyah for 4.1.2... no go... no boot. I'm not quite sure what the issue is as it boots just fine on stock.
Any opinions?
Did you do a full wipe?
(Factory reset, Format system, cache, data and preload)
Sent from my GT-I9305 using XDA Premium HD app
Yep, full wipe each time, I even went so far as to format internal SD from CWM, just in case there was anything lingering.
did you try a mega wipe (will erase anything besides ext. sd)?
did you try to run a custom rom with stock kernel (as I understand stock rom & kernel are working?)?
Yep everything has been wiped down to the core.
And yes stock rom runs fine, and boots fine right off of odin, and even after running CF-Root.
I only get this no booting issue when trying to flash any other rom, even ones that I've previously flashed today b4 my first odin back to stock.
It def has something to do with the soft brick I recovered from earlier today, but I'm just not sure how or why, since I wiped everything and re flashed with odin.
Must be missing something tho.
Edit: Will try Flashing UltimaRom again with default setting and stock kernal see if anything changes.
Ok well i'm not really sure what I did, but I wiped everything again, from data to cache, to preload.
Reflashed ultimarom, this time on stock kernel, and whalha! Boot!
Then went back and flashed Siyah 1.8.9, and that booted ok aswell.
Not quite sure what the problem was but it seems to have been fixed.
Maybe phone was just being moody after all the flashes today!
Thanks for your help!
Let me start off by saying Im far from new to the rooting and roming game. Been through several phones. Never run into this issue.
Note 2 - i605
Team Win Recovery - Up to date
Clockwork Recovery - Up to date
MJ9 Radio from Zif
I am able to install CleanROM and Sophisticated. But when I attempt to install CM11, MeanBean, or Gummy the install fails. It attempts to unzip but always ends with failed. This occurs on both recoveries. I have even tried an alternative recovery. Nothing seems to get it done. Please someone help. Like to note I checked my external SD card for errors. It passed.
Sent from my SCH-I605 using XDA Premium 4 mobile app
General consensus seems to be that philz recovery is currently the recovery of choice for 4.3, id say give that a try
Note2.5
This same thing happened to me. I couldn't even install backups I had. I finally gave up, ODIN'd back to stock and reran casual, everything has been fine since. Even re-installing the same exact recovery.
Jiggabitties said:
This same thing happened to me. I couldn't even install backups I had. I finally gave up, ODIN'd back to stock and reran casual, everything has been fine since. Even re-installing the same exact recovery.
Click to expand...
Click to collapse
Im going to give that a shot. I think it may actually be the thing that sorts this all out. Not hat Phillz is not a good option. But that's the other recovery I already tried. Thinking that maybe the Casual I did was not smooth. As it did hang a couple times and was not as smooth as I would have liked. I am going to reply back when I do it to let everyone know how it turned out. Just in case someone else has the same issues.
:good:
So I odin stocked the phone. Perform casual. Much smoother this time. But still no dice. Still able to install only some roms.
Installable:
Sophisticated
CleanROM
Unable to Install:
CM 11
MeanBean ICE
MeanBean Reborn
Gummy
:crying:
Crotty.Josh said:
So I odin stocked the phone. Perform casual. Much smoother this time. But still no dice. Still able to install only some roms.
Installable:
Sophisticated
CleanROM
Unable to Install:
CM 11
MeanBean ICE
MeanBean Reborn
Gummy
:crying:
Click to expand...
Click to collapse
Hmmmm. Somewhere there's a step that's failing you (obviously). Maybe break down your process, from download to flash, and try to pinpoint where it's going wrong. In my experience the things that have caused an install to fail have been either an incompatible or outdated recovery, bad download (check the MD5), or borked system partition (which is when I Odin'd and re-casualed).
Had issues with CM11 until I ODIN'd back to stock LJB, unlocked bootloader/rooted, updated to latest TWRP 2.6.3.1 via ODIN, wiped all partitions included cache, data, dalvik, system, internal sdcard, external sdcard then adb push CM11 plus gapps and installed. Just make sure you can adb push before wiping everything along with checking file CRC and temporarily disable antivirus.
So I the issue ended up being one of an interesting nature but not normal. When I download thw rom of choice to my phone I move it to my SD card. Making sure its out of the distruction path. As is normal practice. I am using Rom Toolbox root browser to make the move. Turns out that although it gave the impression it was moving the files, it did not always do so. So each time I copy a file from place to another I have to check that it was done in full and without flaws. Quite an interesting problem. As a move of that sort should not break files.
Crotty.Josh said:
So I the issue ended up being one of an interesting nature but not normal. When I download thw rom of choice to my phone I move it to my SD card. Making sure its out of the distruction path. As is normal practice. I am using Rom Toolbox root browser to make the move. Turns out that although it gave the impression it was moving the files, it did not always do so. So each time I copy a file from place to another I have to check that it was done in full and without flaws. Quite an interesting problem. As a move of that sort should not break files.
Click to expand...
Click to collapse
It's always something small it seems. Good practice is to download the ROM, get it to it's final destination then check the MD5. I always wait until I've moved it to the SD to check the MD5 just in case there was a bad transfer.