I have a Droid Incredible Rooted using Unrevoked forever with S-Off. I have been running CM 6.0.2 for a while now and had an issue the other day with my SD card. The card died and when I put a new card in the phone got stuck in a boot loop. I tried reflashing CM 6.0.2 and gapps but I continue to get the same boot loop. I understand that you need to wipe all data but when I atempt to wipe the Dalvik Cache I get the the following message "E:Can't mount /dev/block/ (File Found)" what do I need to do to fix this. I have no phone right now and have become extremely dependent on using it for everything from GPS to MP3 player in my daily life so any help would be greatly appreciated. I have read some posts suggesting running logcat to find what error I am getting during the bootloop that is happening, but I have no idea how to do that. I think the main issue is that I cannot do a full wipe before flashing the ROM.
Please help! I don't want to chalk this up to a bricked device, but I won't be able to hold out much longer since I have to travel this weekend.
First of all, do not double post. It just clutters up the forums.
Second, you need to post this in the Droid Incredible forum or at the VERY LEAST, the Android Q&A forum. I'm not sure why people took the time to create all of the different forums around here if you guys are not even going to use them.
I'm just taking a shot in the dark here based on my experience flashing older Android phones. So do not tell me I'm wrong, AGAIN this is just an option to try:
Just boot into recovery and do a factory reset on the phone. AGAIN, I'm just going on what I CAN REMEMBER here. Use the hboot menu try a restore. Load a factory ROM onto the SD card (using your PC) and the flash it.
I don't know man, maybe I'm wrong about all of this. FACT is that I've had NUMEROUS phones that were in the same shape you are in right now and after google searching, a little common sense and READING I was able to fix the issues. There is a way to go back to your FACTORY ROM but I'm not going to waste my time doing the research for you here, it's your phone and you have access to the same information all of us do.
EDIT:
I mentioned common sense. With that being said, take a look at your own post bro.
talltubatom said:
I understand that you need to wipe all data but when I atempt to wipe the Dalvik Cache I get the the following message "E:Can't mount /dev/block/ (File Found)"
Click to expand...
Click to collapse
I assume you meant "(File NOT Found)". You are trying wipe data off of a NEW SD Card here. How do you expect it to wipe files that are not even there to start with? Make sure your battery is fully charged before doing anything with the phone also. You might think that sounds like it has nothing to do with your problem BUT it can cause boot loops on SOME devices (android and others). Reset to factory from hboot menu. SKIP THE WIPE ALL PART BECAUSE YOU HAVE A NEW SD CARD. Just get back into your phone running Android and then you can redo everything from there.
Thank you for the response.
Sorry for posting in the wrong thread, perhaps a mod could move this to a more resonable place for this question. I'm not trying to clog anythining up. If that isn't an option I'll just create a new thread over there, but like you said that would just be clutter.
First: I did not mean (File NOT Found) the error says (File Found), seems like an odd error on a Formated SD Card that is why I mentioned it.
Second: I tried going to a stock ROM and it would not flash to the device I think it was looking for the previous official ROM that was relesed for the phone and would not install since that did not exist. The one that I downloaded was when Verizon pushed FroYo for the DInc, perhaps I can find one that supports a different upgrade path.
After trying all logical steps, google searches and reading many thread regarding people who have been stuck in this situation I was not able to find anything that was helping me restore my phone, that is why i started a new thread.
Roll Tide <<<< so you won't be so upset with me
The only reason I said posting in the device specific forum or android forums would be better is because there would be more people that know how to fix it viewing your question.
I'm shooting in the dark here but have you tried flashing Clockwork again? Just putting the .zip on the new SDCARD and flashing it? I'm sorry man, I've searched and tried to come up with a good answer but I've not found THAT much. Post in the Incredible forum would probably get your problem solved. I'm not sure that there is much of a difference between deviceds when it comes to recovery but I'm sure that you will get more accurate answer over there, even in the Android section.
Related
Ok, I've been reading around on the forums here, and did a ton of research in the best way to set up my gTab before I even got it. I like to think I am not a n00b, but someone correct me if I come across as one.
I was running vegan 5.1 with no issues up until yesterday. Yesterday, I got the dreaded boot loop. Looking around, it seems the most popular answer to this is to repartition. But here is my first question:
(1) in my pre-purchase research, I came across this issue a lot, and so I made sure to repartition right away. since I've partitioned the recommended way once already, does this eliminate repartitioning as a potential solution to my issue?
NVFlash seems like the next most popular solution. In researching how to do this, I came across several references to backing up your data, etc. It appears I can go into clockwork and mount my device via usb (haven't tried it yet, sorry, my bad) to do this. I didn't however find any reference to exactly what I would want to back up. I did a backup in cwm .. so my next question is:
(2) should I pull the cwm backup files? if so (and if not), which files exactly should I be looking for? just stuff in the \data folder? and would I just copy them back onto the gTab after flashing?
Again, sorry if I am coming across as a n00b, but I really have spent good amount of time searching the forums -- I am just a little confused and want to make sure I have everything right before taking either of these steps.
Thanks!
Kaz
TheKaz said:
Ok, I've been reading around on the forums here, and did a ton of research in the best way to set up my gTab before I even got it. I like to think I am not a n00b, but someone correct me if I come across as one.
I was running vegan 5.1 with no issues up until yesterday. Yesterday, I got the dreaded boot loop. Looking around, it seems the most popular answer to this is to repartition. But here is my first question:
(1) in my pre-purchase research, I came across this issue a lot, and so I made sure to repartition right away. since I've partitioned the recommended way once already, does this eliminate repartitioning as a potential solution to my issue?
NVFlash seems like the next most popular solution. In researching how to do this, I came across several references to backing up your data, etc. It appears I can go into clockwork and mount my device via usb (haven't tried it yet, sorry, my bad) to do this. I didn't however find any reference to exactly what I would want to back up. I did a backup in cwm .. so my next question is:
(2) should I pull the cwm backup files? if so (and if not), which files exactly should I be looking for? just stuff in the \data folder? and would I just copy them back onto the gTab after flashing?
Again, sorry if I am coming across as a n00b, but I really have spent good amount of time searching the forums -- I am just a little confused and want to make sure I have everything right before taking either of these steps.
Thanks!
Kaz
Click to expand...
Click to collapse
Clockwork and nvflash are 2 different thing,
for nvflash you need to power-up and hold the - of the volume, screen will show the bird then blank and it will try to load the APX usb driver on the computer. the UNIT IS MOUNTED INTO A SPECIAL TERMINAL recovery/command MODE
For clockwork you power-up and hold the + of the volume and recovery is executed, stock will simply load update.zip from the root of sdcard (internal memory), if clockwork is installed then the menu will appear and allow you to backup and restore the OS. but the UNIT IS NOT MOUNTED IN THE PC.
a full restore if the unit mean booting into recovery, restoring stock firmware following instruction from this post http://forum.xda-developers.com/showthread.php?t=861950 then installing clockwork and booting with the power-up + and restoring either your rom of choice (except for tnt lite 5.0) or your backup made previously with clockwork.
Bootloop are usually solved by wiping the partition/cache/data prior to flashing back a rom or backup.
hope this help, but there's plenty of how to already here...
...
I too had experienced "bootloop", but think I solved it through one of the threads in the dev forum. Something about formatting 2048/0 for the SD card...
Sorry I couldn't be of more help.
http://forum.xda-developers.com/showthread.php?t=865245
If your tablet bootloops…Also may be required to get market running correctly on some ROMs...
Press and hold the power button to shut the device down. Boot back into Clockwork. Select the advanced option at the bottom, then go to “partition SD card”, for the first option select 2048, and for the second option select 0. Then, redo steps 7-10. This erases all data on your tablet, including backups.
P00r said:
Bootloop are usually solved by wiping the partition/cache/data prior to flashing back a rom or backup.
hope this help, but there's plenty of how to already here...
Click to expand...
Click to collapse
Thanks. I am not as worried about the how-to, I can find those, I was just a little confused about what situation I am in, exactly, and which solution to use.
So, even though I've partitioned this way originally, it can still get corrupted to the point where the solution it to re-partition again..?
In the main clockwork mod thread there is no mention of repartioning prior to installing a rom.
Is this necessary and why?
I came across it in another guide.
Thanks
I think it's based on the rom, so that info would be found with your rom info
I asked the same question here:
http://forum.xda-developers.com/showthread.php?t=1006012
While there was no definitive answer I think I'll partition out of an abundance of caution. It seems that many problems are solved by repartitioning and as my Grandma used to say...
..."couldn't hoit."
I can answer, to a point. We've seen that, over time, the device can get into such a state that even a data wipe or reflash does not correct problems - that's where the SD repartitioning comes in. It's kind of a last ditch effort prior to nvflashing it.
I've had to repartition my device several times - the last time I did it, it fixed the "Status 7" errors when I tried to flash new firmware. My guess is that the /sdcard was so messed up that the recovery program could not accurately read the update.zip on it, anymore.
I was working fine, enjoying my new HTC One S with CM9 rom installed. Well the battery life wasnt the best on it, and i didnt install the custom kernel. So I looked for the custom kernel download(on my phone, not on my computer) and i found a .zip file. Well I thought that you could just download the kernel straight to my phone and open it up with "Rom Manager" which i did, it than said i needed to reboot the phone in recovery to continue the installation, so I did... it took me to recovery "to continue the installation" well than I looked away, looked backed down and it was black.... and i have tried powering up, booting into boot loader, booting into recover, and nothing... its just BLACK! nothing works, its literally useless ATM. I really messed up, is there anyway to fix this? Thanks in advanced!
----EDIT----
I think I accidentally flashed the kernel like i would normally flash a rom.... cause i downloaded the .zip file(directly to my phone, not using a computer), than i tapped the download and it asked me if i wanted to open it up with rom manager, so i did. and i think rom manager thought i was flashing a rom, when i wasnt, it was a kernel.... am i screwed? or is there anyway out of this?
Do you know the exact kernel you flashed--where did it come from
Some you need to extract and push
Assume you just tried to boot into bootloader thru phone buttons
Does your pc recognize your phone when plugged in, if so can you open a command window and try to access phone as in adb devices then adb reboot bootloader
assuming you are familiar with sdk adb/fastboot comands
otherwise i don't know what else to say--may be bad--sorry
Came from an XDA thread
Here is where it came from: http://forum.xda-developers.com/showthread.php?t=1708676 from "sun90" (half way down the page "CM9 KERNEL remix edition.zip - [Click for QR Code] (5.53 MB, 9 views) ")
i downloaded that straight to my phone and opened it up with Rom Manager, which i think the app took it as a rom, and installed it like a rom even though it was not a rom. I just tried to access it through adb, it comes up with no devices my PC does recognize it when i plug it in though...
Ive tried to get into bootloader tons of times, it just stays black... :'(
Thanks for your answer!
You flashed a galaxy s2 kernel on your one s? why would you ever think that was a smart thing to do?
Looking at the updater script in that zip it seems it wipes some partitions, the partitions on a SGS2 and the ONE S are different, so if that script accidentally wiped say the hboot partition, or some other critical-for-boot partition, you have a fully bricked phone.
For any devs that may know what partitions are what on the One S, the script wiped
mmcblk0p7, and wrote a zimage to mmcblk0p5
---EDIT---
Normally this is a cwm flashable zip on the Samsung Galaxy S II, which is why rom manager flashed it, as it met all the requirements, the only issue is, it was not made for the ONE S and probably overwrote some important things.
I tried for hours and hours to fix the same issue on a friend's One S (same symptoms, not same cause) to no avail. I tried QPST and telnet and a ridiculous amount of things. Had to bring it to the store and get a new one.
Good luck, but I don't believe there's anything you can do to fix it.
Just answered your question in the help thread, Didnt see this thread too !
Im afraid its not looking good, I think your best bet would be to call your provider and blame it on an OTA update.
And hope for the best
Alright, thanks for the help!
Well it looks like i bricked my phone than.... I thought that CM9 was only on the One S, so I just looked for the CM9 kernel, which obviously was for the sg2, i feel like such a dumb ass now! haha well thanks for all the help guys! ill be heading to the t-mobile store today to blame it on a OTA:]
yeah, others wont agree with what your about to do but........
just act like a complete noob, dont mention anything about software / firmware / ROMs / bootloader etc ect
just say your phone made a noise, you selected update and it died lol
good luck--I know it is heartbreaking
not sure of your situation with carrier, but you could go thru Retention if needed
Hi peeps.
i'm very new to all this but sort of know the basics
i'm running on Axiom now but tried to flash cm10 but after install i got a black screen so had to do a restore.
Today i just flashed venom and after the instal process is done, i hear the start up music but nothing on the screen.
I have had 3 other roms on my phone and never had a problem!
these are the steps i do
download rom - place on sd
put phone in recovery
reset factory
reset cache
install from sd
when it finish's reboot
blank screen.
Am i missing something?
Any help would be great and i can't post on the thread because i'm a noob with less than 10 and dont want to spam my way to the 10 :silly:
you are missing a lot, like reading the OP page and following install instructions
you missed separate flash of boot image and wiping system plus data and caches
i wipe system 3x to be safe
rugmankc said:
you are missing a lot, like reading the OP page and following install instructions
you missed separate flash of boot image and wiping system plus data and caches
i wipe system 3x to be safe
Click to expand...
Click to collapse
Thanks but i think that is now the least of my problems!
I used Goomanager and installed CM10, When I did it i installed teamwin recovery. It started to do a lot of strange things, when it finally rebooted i got a load of errors "phone is not working" nearly every 10 seconds?
it will not connect via usb, i discovered the the SD was not mounted.
I tried to mount the SD but it doesnt work, so i rebooted to recovery and tried to mount there but its coming up with - error unable to mount? ive tried everything but no joy
please please help
Thanks:crying:
see if this is your situation
http://forum.xda-developers.com/showthread.php?t=1630459
can you connect phone to pc and use fastboot commands
rugmankc said:
see if this is your situation
http://forum.xda-developers.com/showthread.php?t=1630459
can you connect phone to pc and use fastboot commands
Click to expand...
Click to collapse
I've got a mac
not sure what fastboot is.
I'll check out the link, and thank you very much for trying to help:good:
sorry i do know what fastboot is, yes can get in to it. but ive gone from CWM to teamwin recovery if i go in to the recovery section but that wont let me do anything because the mount. cant even load the phone up
I don't know Mac commands
My idea is to install htc drivers and set up fastboot/adb on pc--the info can be found in dev section on rooting
then open a command window and and boot into fastboot and flash a new recovery, maybe stock per the link, clear storage and try to get mounted
how did you unlock bootloader--
you will need to do alot of reading on adb/fastboot and flashing roms--first step is to have backups of rom and sdcard
since i don't the Mac commands to do fastboot, someone else will chime in at some point
you can alos go to the noob section in Q&A and resubmit your issue
someone will work you thru this, but in meantime study up on android sdk/fastboot/adb. a necessity to get out of these problems
you are not bricked, just need the info and right steps to get back on track
rugmankc said:
I don't know Mac commands
My idea is to install htc drivers and set up fastboot/adb on pc--the info can be found in dev section on rooting
then open a command window and and boot into fastboot and flash a new recovery, maybe stock per the link, clear storage and try to get mounted
how did you unlock bootloader--
you will need to do alot of reading on adb/fastboot and flashing roms--first step is to have backups of rom and sdcard
since i don't the Mac commands to do fastboot, someone else will chime in at some point
you can alos go to the noob section in Q&A and resubmit your issue
someone will work you thru this, but in meantime study up on android sdk/fastboot/adb. a necessity to get out of these problems
you are not bricked, just need the info and right steps to get back on track
Click to expand...
Click to collapse
im going to use someone elses alp top with windows. i'll ytry the all in one thing because thats how i rooted it in the first place. thanks for helping it means alot
good luck on it
First off love the N00b video at sign up that was hysterical, nice work to whoever made it.
Ok on to what I need to know:
I understand HOW TO root/flash a rom, my issue is kind of different than most peoples. I have scoured the web and this site for the files I need to accomplish this with my GT-P3113 build ending in LG5 however I am confused to hell.
1 place will say that CWM 6.0.1 is not usable on my device, another will say that it works fine and another will say to use TWRP (which might I add looks cool to use). Some will say that I need the expresso_wifi file to root my device, others will say use update.zip, and others will say a totally different file all together.
I know what ROM to get, I understand the steps:
Download drivers
Boot to download
use odin to install CWM
back up everything with CWM (which goes to the MicroSD I am guessing? since I wipe the device in a later step)
wipe the device
wipe the cache
wipe the Dalvik cache
flash the rom
flash the root
is all that correct? (just to make sure I got it right) so my biggest question is, which files do I really use? There is a thread from back in June before the 4.0.4 update OTA came through) saying to use instead of that if you have LG3 or etc.
Help would be greatly appreciated, I am a smart guy, just want to have my facts straight before I make this happen.
PS sorry if this is in the wrong place, figured this was the best place for it.
Please be sure and thank the person who decides to do your homework for you.
:laugh:
FlynnErik said:
First off love the N00b video at sign up that was hysterical, nice work to whoever made it.
Ok on to what I need to know:
I understand HOW TO root/flash a rom, my issue is kind of different than most peoples. I have scoured the web and this site for the files I need to accomplish this with my GT-P3113 build ending in LG5 however I am confused to hell.
1 place will say that CWM 6.0.1 is not usable on my device, another will say that it works fine and another will say to use TWRP (which might I add looks cool to use). Some will say that I need the expresso_wifi file to root my device, others will say use update.zip, and others will say a totally different file all together.
I know what ROM to get, I understand the steps:
Download drivers
Boot to download
use odin to install CWM
back up everything with CWM (which goes to the MicroSD I am guessing? since I wipe the device in a later step)
wipe the device
wipe the cache
wipe the Dalvik cache
flash the rom
flash the root
is all that correct? (just to make sure I got it right) so my biggest question is, which files do I really use? There is a thread from back in June before the 4.0.4 update OTA came through) saying to use instead of that if you have LG3 or etc.
Help would be greatly appreciated, I am a smart guy, just want to have my facts straight before I make this happen.
PS sorry if this is in the wrong place, figured this was the best place for it.
Click to expand...
Click to collapse
From someone relatively new to this as well, this is basically correct. Here are some tips from someone who has recently done it.
Make a backup.
Research the files you intend to flash, make sure they are right for your device
Verify the guide you are using has been tested and known to work.
This may seem elementary, but I didn't follow #3 and it cost me a lot of headache un-bricking my SGT 2.
ryphil said:
From someone relatively new to this as well, this is basically correct. Here are some tips from someone who has recently done it.
Make a backup.
Research the files you intend to flash, make sure they are right for your device
Verify the guide you are using has been tested and known to work.
This may seem elementary, but I didn't follow #3 and it cost me a lot of headache un-bricking my SGT 2.
Click to expand...
Click to collapse
Fully agreed! That's why I came to the experts. I have done my homework but the thing is my homework leads me to several different files from before the ICS update. There has only been 1 thread on 1 forum that has been post ICS update, and no real feedback on it. I think I even found one that uses ADB (I understand that concept, but would prefer not to use it since I don't know Linux well enough).
I would love to know what files to use, which ones to stay away from. As I said I have the concepts, I have the understanding, its the actual files that I want to verify, I can rattle off tons of files from tons of sites, but they may or may not be correct (and may have the same name as a correct one but still be incorrect, ie "update.zip" appears a few times on different threads from different time frames).
There is only post in the teamhacksung CM10 wiki that was last edited 8/12/2012, but that could have been anything that was updated, not the files/links to be used.
So I thank you in advance for your help, and you will certainly get a thank you in the forum for help you are providing, I always give credit where credit is due.
Well here goes nothing, going to reboot (to ensure the Kies drivers are installed and loaded into the system 100%), and try the instructions from this link http://forum.xda-developers.com/showthread.php?t=1788625
It seems to work for most, the only concern I have is that I have a different end to the build than most others do (and I am not sure why?)
Did I screw myself?
I rooted, and have CWM installed.
Is it to late to create a ROM backup of my device for when i go to install CM10 (I need a drink for now, so I might install it tomorrow night lol).
That link I posted in the last post is good to go if anyone else needs a safe bet set of directions.
Seriously though, I didn't do a backup, am I screwed now?
EDIT: I just did a back up and it said no sdcard/.android secure found, skipping of backup of apps
and
no sd-ext found skipping backup of that.
is that normal? Did it backup to my microSD?
Still hope I didn't screw myself by backing it up after rooting.
Hello, all. I hope someone can help me with my SGH-T959W. Right now I'm at the point where the phone has CWM installed, but will only boot into recovery no matter what I do. I've followed the N00b guide to Flashing/Fixing the SGS4G, but clearly I'm missing something.
I tried to follow the Windows-based procedure for the SGH-T959W, but was unable to get version 1.40 to execute, and was unable to locate version 1.31.
So, given that the SGH-T959W and SGH-T959V are the same phone except for the bootloader, I tried the Java-based Stock KJ-6 + Root. The first time I tried it, the upload failed after the PIT, and the phone was no longer able to boot into anything other than download mode. I eventually managed to get it to the point where it tried to flash the modem, but I was never able to get the modem to flash successfully. I tried both under Windows and Linux, using two different PCs and every USB cable I could find, since I know those tend to be dodgy. Still, I've never gotten past flashing the modem, though sometimes it's done worse.
But at this point, I had a phone that would dutifully boot into CWM, so I could change strategy anyway. So I grabbed the unofficial Cyanogenmod 10.1, copied it to the root of the SD card, and tried to load that via CWM. It failed the hardware check.
That's problem #1. Is it possible to modify Cyanogenmod to check for the 959W instead of only the 959V?
Now, problem #2. I decided to give Slim ICS a whirl, since it's light on requirements and a 512MB/1GHz device would probably appreciate a lighter load. The two packages claim to install, but the progress bar never reaches 100%, and when I try to boot the phone, it just boots into CWM. It's a newer version of CWM now, and the startup logo is different, so something worked, but clearly not everything.
When installing, I did mount UMMU, factory reset, wipe the cache and the Davlik cache, mount UMMU, install, then fix perms. But I still get that loop back to CWM.
So something critical didn’t take, however many times I tried (I've lost count, but I think I'm going on 10), and I don't know the architecture well enough to know where to start looking. I'm pretty comfortable with other operating systems, but this is only the second Android device I've tried to customize.
I suspect I can’t solve any other problem until I solve problem #2, regardless of which distro I end up wanting to run.
Sorry for the long-winded post, but I figured the more questions I answered up front, the better the chances of fixing this would be.
Thanks for any help you're willing to offer a n00b.
Dave F.
I think what you were doing with heimdall is the way to go except the t959w doesn't like modems and I think there's some way to leave out the modem part but eh.. I'm not that well versed. Anyway here's a link that may or may not be relevant
http://forum.xda-developers.com/showthread.php?t=1956025
Please read forum rules before posting.
Questions and request for assistance go in the Q&A section.
Thread has been moved.
Thank you for your future attention to this.
Have a great day!
dfarquhar said:
Hello, all. I hope someone can help me with my SGH-T959W. Right now I'm at the point where the phone has CWM installed, but will only boot into recovery no matter what I do. I've followed the N00b guide to Flashing/Fixing the SGS4G, but clearly I'm missing something.
I tried to follow the Windows-based procedure for the SGH-T959W, but was unable to get version 1.40 to execute, and was unable to locate version 1.31.
Click to expand...
Click to collapse
Look here for 1.3.1.
dfarquhar said:
So, given that the SGH-T959W and SGH-T959V are the same phone except for the bootloader, I tried the Java-based Stock KJ-6 + Root. The first time I tried it, the upload failed after the PIT, and the phone was no longer able to boot into anything other than download mode. I eventually managed to get it to the point where it tried to flash the modem, but I was never able to get the modem to flash successfully. I tried both under Windows and Linux, using two different PCs and every USB cable I could find, since I know those tend to be dodgy. Still, I've never gotten past flashing the modem, though sometimes it's done worse.
But at this point, I had a phone that would dutifully boot into CWM, so I could change strategy anyway. So I grabbed the unofficial Cyanogenmod 10.1, copied it to the root of the SD card, and tried to load that via CWM. It failed the hardware check.
That's problem #1. Is it possible to modify Cyanogenmod to check for the 959W instead of only the 959V?
Click to expand...
Click to collapse
Nope, not a CWM issue. Ever since TeamAcid and I started on CM9 (and I believe the last few CM7 builds) added support for T959W. Almost everyone (thankfully! ) has kanged those device trees and also support T959W. I'm sure other T959W users will chime in to tell you that 97% of all roms here work on T959W. (GB and forward)
dfarquhar said:
Now, problem #2. I decided to give Slim ICS a whirl, since it's light on requirements and a 512MB/1GHz device would probably appreciate a lighter load. The two packages claim to install, but the progress bar never reaches 100%, and when I try to boot the phone, it just boots into CWM. It's a newer version of CWM now, and the startup logo is different, so something worked, but clearly not everything.
When installing, I did mount UMMU, factory reset, wipe the cache and the Davlik cache, mount UMMU, install, then fix perms. But I still get that loop back to CWM.
Click to expand...
Click to collapse
Crazy mount setups shouldn't matter anymore. That was an oldschool Froyo/Early GB thing. Almost all new CWM install scripts do the right thing now.
dfarquhar said:
So something critical didn’t take, however many times I tried (I've lost count, but I think I'm going on 10), and I don't know the architecture well enough to know where to start looking. I'm pretty comfortable with other operating systems, but this is only the second Android device I've tried to customize.
I suspect I can’t solve any other problem until I solve problem #2, regardless of which distro I end up wanting to run.
Sorry for the long-winded post, but I figured the more questions I answered up front, the better the chances of fixing this would be.
Thanks for any help you're willing to offer a n00b.
Dave F.
Click to expand...
Click to collapse
I like the long posts! Especially when then they contain more detail for me to help you figure out your problem with. I'm also partial to the short posts that include logs!
TwitchyEye said:
I think what you were doing with heimdall is the way to go except the t959w doesn't like modems and I think there's some way to leave out the modem part but eh.. I'm not that well versed. Anyway here's a link that may or may not be relevant
http://forum.xda-developers.com/showthread.php?t=1956025
Click to expand...
Click to collapse
@TwitchyEye you're right That is the heimdall oneclick that should be used.
@dfarquhar I think using the heimdall oneclick that @getochkn made should be the right path for you. Make sure you use the right version of heimdall. Make sure you completely remove the old version (software and drivers), use zdiag to make absolutely sure!
If all else fails, post here again! (maybe with logs )
Thanks everyone. I grabbed v 1.3.1, so I'm getting ready to try it now.
If anything goes wrong, I'll look into where the logs are stored and how to retrieve them, and I'll be back. Assuming I can't use the logs to figure it out on my own of course.
dfarquhar said:
Thanks everyone. I grabbed v 1.3.1, so I'm getting ready to try it now.
If anything goes wrong, I'll look into where the logs are stored and how to retrieve them, and I'll be back. Assuming I can't use the logs to figure it out on my own of course.
Click to expand...
Click to collapse
Sometimes, it's just the output you see on your screen is a good enough log
bhundven said:
Sometimes, it's just the output you see on your screen is a good enough log
Click to expand...
Click to collapse
Got it working! Heimdall 1.3.1 was the key. I then turned around and flashed Slim ICS since I had it on the SD card already, and it worked. I'm debating whether to move on to Slim Bean, but maybe I need to leave well enough alone for a few days now that I have a working phone.
Thanks again,
Dave