Ok, so I did unrevoked and have an unrooted phone. Started to get bored with the stock 2.2 and wanted better battery life.
My Dinc has an SLCD screen. So, when I go into the standard clockwork recovery, it goes to a black screen with white bars on the side. I had to do a custom flash recovery for my phone through unrevoked/flash. I then did a nand backup.
Tonight, I downloaded MIUI and attempted to install through the recovery flash. I ended up getting errors. So, I then thought that I needed to go through the ROM Manager app.... when I tried to flash the ROM, it automatically switched my recovery back to the Clockworks recovery..... then tried to go into the recovery portion of the ROM flash. Needless to say, I had to do a battery pull. Now when I try to do a normal boot, the phone freezes at the white screen that reads "HTC Incredible". If I boot into recovery... I can get to the hboot screen with the three droids at the bottom, but a script comes up on the screen and I think that it says something about no image... from there I can navigate around the recovery menue, but nothing works for me getting past this. If I go to recovery, it just keeps going to the black screen with the two white bars.
Is there anything that I can do. I am wondering if it is trying to flash the ROM everytime it comes on.... but this recovery method is not working on my phone.
Any help would be greatly appreaciated!
I believe you need a special clockwork recovery for SCLD screens. Not exactly sure where to find it on here, but it should be hanging around somewhere. I hope I helped ya out a bit, good luck.
Sent from my Droid Incredible running SkyRaider 3.3.2 with King Kernel BFS #5.
OK, so I was working a 24 hour shift yesterday when I posted this... unable to download any zip or exe file (damn firewalls)... This morning I was able to remove the miui zip from the root of the sd card via card reader. I then copied the PPB31IMG.zip to the root of my sd card. Then booted into recovery. I asked if I wanted to flash this file, I said yes and then it gave me the correct recovery menue. from there I was able to choose the recovery image that I had created yesterday. It seemed as though it was going to work, booted up to a stock rom that required manual setup (like on a new phone). Then I started to get FC's all over the place. I was able to find on my sd card two other nandroids that were saved in a different place than the only one that recovery allowed me to choose from. I moved the newly found recovery folders to the same location as the first and now I had those recovery options listed. I chose one from last week and thankfully my phone is restored and working.
I am not sure if this information will help anyone with an SLCD Dinc. There seems to be a huge difference in how these phones react to roms and tweaks. I am very hesitant to attempt any other ROMs at this time. On my eris, I flashed about 30 different ROMs and about 5 differnet radios. I am not new to this, but this SLCD Dinc has been a headache.
Any Aosp rom on an Slcd takes a different kernel. Get yourself the koush test#2 kernel and just keep it on your sd card. Flash it everytime you do a AOSP rom.
Sense based roms all seem to be ok as the kernel was built with Slcd in mind.
Well I'm glad you got it back up and running. I've heard about them not working well with some roms, I didn't know it was with all asop roms.
Sent from my Droid Incredible running SkyRaider 3.3.2 with King Kernel BFS #5.
doug piston said:
Any Aosp rom on an Slcd takes a different kernel. Get yourself the koush test#2 kernel and just keep it on your sd card. Flash it everytime you do a AOSP rom.
Sense based roms all seem to be ok as the kernel was built with Slcd in mind.
Click to expand...
Click to collapse
Thanks for the info on the AOSP roms. I did not know either. I wonder if there is a way to make the AOSP roms to support it by providing the new kernal in the flash or at least making a note on the AOSP ROM forum page that states the issues with SLCD Dinc's and what needs to be done to avoid problems. I would venture to say that anyone new to this stuff and was feeling brave would not be able to figure out how to restore there phone when it was acting the way mine was. Just my 2 cents.
Thanks again for the info.
I've been trying to change my Samsung Galaxy S Boot Animation but it seems to be quite the challenge!
I currently use Darky's custom rom (latest 9.1 version based on Android 2.2.1) with Voodoo kernel (the one suggested by Darky himself..thought i don't know why).
I've been googling A LOT and all i could find was bootanimation.zip files and various methods to install them (mainly manual copy with root explorer or cwm) but none of them work and i always get the standard boot animation.
Tried to copy bootanimation.zip both in system\media and in data\local but i still get the same result.
Even these don't work!
http://forum.xda-developers.com/showthread.php?t=869347
The only thing i can do that has some sort of effect is to rename bootsamsung.qmg and bootsamsungloop.qmg.
By doing this a get a black screen instead of the boot animation, so i can assume my phone/kernel/whateverthereasonis only looks for boot animation within these files.
Am i missing something?Has someone had the same issue?
Thanks!
i faced the same problem i used the darky rom configurator and flashed back to 8.1 for the cool animation but since 9.2 runs heaps better with the fixed root and stuff i had to stick with it despite the now old and lame nexus boot screen
most of the other posts deal with HTC and other phones
i look forrward to the day i can change my boot animation to the droid pissing on an apple
Droid pissing on an apple THATs fer me. Where can i get it???
Sent from my GT-I9000 using XDA App and DArkys 9.2
This is so sad!I can't move on from the stock galaxy s anim..which is not that bad if you ask me, but i want one of my own!
Even using Darky's and changing the boot animation in the Rom Configurator i still get the same stock SGS anim!
Well..al least i can get rid of that annoying startup sound with something else!
lol check out the droid peeing boot screen
http://forum.xda-developers.com/showthread.php?t=693064
also i hope there is an answer for this cuz i've been looking for a while
Try another kernel
Sent from that Green Robot Device with a 4"screen, chewing on some froyo(with an extra .1)
Didn't darky say that changing the boot animation will break the startup script?
I've been trying to change my Samsung Galaxy S Boot Animation but it seems to be quite the challenge!
I currently use Darky's custom rom (latest 9.1 version based on Android 2.2.1) with Voodoo kernel (the one suggested by Darky himself..thought i don't know why).
Dump that rom use Rom Kitchen .
Choose your boot animation .
http://romkitchen.org/sgs/?s=generator
http://forum.xda-developers.com/showthread.php?t=817703
jje
Thanks for the advice!
But why do you say "dump that rom" like Doc's rom is much much better than Darky's?
I'm a new Android user so when i decided to go for a custom rom i did some googling and i found Darky's to be one of the most appreciated.
HOW TO install custom boot animation
Use Root Explorer to place the bootanimation.zip in the /system/media folder. Change permissions to match the other files in the folder.
totano84 said:
Thanks for the advice!
But why do you say "dump that rom" like Doc's rom is much much better than Darky's?
I'm a new Android user so when i decided to go for a custom rom i did some googling and i found Darky's to be one of the most appreciated.
Click to expand...
Click to collapse
I have used both and am sticking with docs + speedmod. Have had less issues with docs rom especially when flashing themes, boot animations etc.
Sent from my GT-I9000 using XDA App
I know this is old, but is the closest thing to my problem...
I have CM10 in my device (one of the latest nightlys), my boot scree used to show i9000T, the T used disappear after some milliseconds, now it shows me pure gibberish instead of the bootscreen...
Is there a way to get the old Samsung bootscreen?
From Boot animation onwards, everything runs pretty well.
Just like this
http://www.youtube.com/embed/vJuPage8aEk
Do you have same screen if you try to go into recovery mode (volume up +home+power)?
It looks like if you upgraded your device to gingerbread without flashing ginger bootloaders although they should be in any ginger stock rom.. or maybe you flashed directly cm10 on top of a froyo rom?
Bejda said:
Do you have same screen if you try to go into recovery mode (volume up +home+power)?
It looks like if you upgraded your device to gingerbread without flashing ginger bootloaders although they should be in any ginger stock rom.. or maybe directly from froyo to cm10?
Click to expand...
Click to collapse
Same screen in recovery.
I think it was from ecclair ... so it is better if I downgrade to eclair/froyo, update to gingerbread, and flash cm10 backup again? or the backup would restore the old bootloader?
Or should a gingerbread odin flash would suffice? Now that I remember, I tried to flash a Gingerbread direclty, but didn't find a reliable source for the rom, flashed one european rom, no phone network at all, flashed CF-Root-XW_XEE_JS7-v1.3-BusyBox-1.17.1.
Tried this ROM but failed to finish every single time GT_I9000_XWJS7_XXJPY_XEEJS1
Flash a ginger firmware will do it but..your device is i9000T then?
You know if it's safe to flash i9000 firmware on i9000T (except for 3 maybe)?
You could flash bootloaders alone too,there's Odin package but I don't want to lead you to something bad..from what I read it seems ok but I would prefer YOU to be sure or someone else confirming
The rom you already tried (XWJS7) was froyo actually so won't help here anyway.
Bejda said:
Flash a ginger firmware will do it but..your device is i9000T then?
You know if it's safe to flash i9000 firmware on i9000T (except for 3 maybe)?
You could flash bootloaders alone too,there's Odin package but I don't want to lead you to something bad..from what I read it seems ok but I would prefer YOU to be sure or someone else confirming
The rom you already tried (XWJS7) was froyo actually so won't help here anyway.
Click to expand...
Click to collapse
Didn't noticed the rom was froyo...
The device showed a i9000T, but in a matter of milliseconds, used to change to i9000 alone.
Behind the back cover and battery, it says i9000T, from what I know, is the same, and never found another source of roms different for i9000T. but I don't really know where to find another rom, every single rom I've tried had it's link broken or some other problem...
http://forum.xda-developers.com/showthread.php?p=14289635 for the LATAM areas (from what I know, previous Samsung phones used chars to make a difference for the region they where intended to be sold). and I'm downloading it right now.
Is there a way to backup a modem from a Rom? found a promissing rom with a modem useful for my carriers frequency.
I'm really sorry for all the trouble...
And it gets stuck in the SBL.bin
Stuck while sbl.bin?
Ouch,it's the worse that could happen..boot.bin and sbl.bin are precisely the bootloaders and the only flashing step that can brick a device ..how does it went since then?
Bejda said:
Stuck while sbl.bin?
Ouch,it's the worse that could happen..boot.bin and sbl.bin are precisely the bootloaders and the only flashing step that can brick a device ..how does it went since then?
Click to expand...
Click to collapse
Still got Download mode...
Flashed the previuous froyo (which I though was a GB), flashed CFroot, flashed CWM, launched CM10 installer zip (so it would load CWM6), restored my image...
Actually, it happened before, that's why I installed CM10 directly last time...
So I gave up, restoring froyo gives me the Boot screen just fine, but that specific Rom gets stuck at modem.bin, and I receive no signal...
I was able to change it just by replacing the file it already had.
I have new S3 That I want to put Cyanogenmod on, I have been following the CWM thread, I can get the recovery onto my phone and even get it to flash the latest stable cm-10.1.2-d2spr.zip from the CaynogemMod site. But It doesn't boot. I left it for 30 min expecting the first time to take a while (it took 15 min when I did my evo the first time). I tried the odin flashable rom that @CNexus posted but it errors out and my phone shows device not comparable error. Any help would be appreciated.
There seems to be major changes that have taken place on new S3's. It appears you won't be blessed to flash most AOSP roms at this time. The recovery was just modded yesterday to make it work on these new devices. The modded recoveries work for the tie being until the actual developers of the individual recoveries figure everything out.
Right now it looks like flashing TW roms is a go but AOSP roms is a no go.
Sent from the future via Tapatalk 4
edfunkycold said:
There seems to be major changes that have taken place on new S3's. It appears you won't be blessed to flash most AOSP roms at this time. The recovery was just modded yesterday to make it work on these new devices. The modded recoveries work for the tie being until the actual developers of the individual recoveries figure everything out.
Right now it looks like flashing TW roms is a go but AOSP roms is a no go.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
Thanks. I Guess I will have to look and see if any TW roms strike my fancy.
I've put this off forever and would really like to be able to use the secure sim element in TW Roms occasionally.
How I think the process is supposed to go:
Make a Nandroid of each the TW & AOSP Rom.
Flash Devil
Reformat to F2FS, create secondary partition.
Restore Secondary, boot into it.
Reflash Devil.
Switch to primary, restore primary.
However, I can't seem to actually boot http://forum.xda-developers.com/gal.../rom-ds-ne5v1-i317-ucucne5-mj4-stock-t2803363
I flash it, and I just get a black screen ( I think it's the boot animation?).
I don't know much. So far I've gotten myself out of a few jams on different devices. But in general I need exact instructions. There just isn't one set of instructions for what I'm currently trying to do. Any advice is appreciated.
So instead of me venturing forth, and messing up, and coming back for help, could I get some advice?
Tapatalked from my PACMAN 4.4.4 Note II
Cmon XDA, don't fail me now. Is everyone just busy with holidays?
Got a phone on eBay cheap that being said I did some things that normally shouldn't be done but the devices are so similar that it worked overall I wouldn't try if its your only phone I like the d710 so I did some digging and trying I don't think there is a ROM I have not flashed on here that is available I've even ported some have four d710s all together first time I tried this I got it to work but USB fried I guess from i9100 old bootloader the second time u was even less careful from my d710 cm11 running ROM I installed a kernel flasher I backed up the kernel I got a i9100 lollipop rom ,aosp kernel from rwilco12 I believe just started using it actually but changing the updater script asserts to match the d710 even the whole script pasted in works (except for the write boot part ) changing the device names on the build prop to match and changing libril. Whatever to libril40 like the d710 path zipped and flashed lollipop on d710 if the screen sleeps it restarts system ui so i changed sleep display setting to thirty minutes update supersu zip got me rooted no WiFi Bluetooth works though SD works but ext SD does not so I had to Bluetooth a lot of apps to the phone storage the file manager works to install the package installer works and installs apks fully rooted kernel flashed rebooted restored my backup and back on d710 I have also flashed a i9100 kernel and recovery the d710 recovery will flash a i9100 Kitkat compatible recovery but the i9100 recovery will only flash i9100 ROMs so went from d710 recovery flashed i9100 recovery and installed any i9100 lollipop ROM I have found the problems with WiFi is present in all but to the point it force closes the system ui it does not do that in the earlier method (but the earlier method can only be done with aosp I have tried and its always an endless bootloop of installing apps starting updating contacts and reboot to do it all over) as long as the screen does not sleep and the WiFi isn't messed with the ROM is stable on the d710 installed supersu zip to root installed all my root apps messed around full root flashed d710 kernel reboot wipe restore and back to d710 both methods worked for me installing with the i9100 caused more problems than just changing stuff but it works both ways I have been successfully other ways as well thething is the WiFi does not work the buttons are not mapped I mean there is no hard home key on d710 so it dont work the search key is the settings key and the back key is the back key the home key does Nada and the menu key does Nada the Bluetooth works the mobile data and calling do not but everything else I have tested on it does what can I do to fix this being that it works very well on the d710 looks amazing setting the DPI lower makes it look even more elegant its an obsolete phone I know but it still got a whole lot of life in it thanks to everyone at xda not my first phone not my only phone I'm a self learned guy and that was only possible with xda I went from what the hell is rooting? To this I am not trying to offend anyone with my chopping up of their ROMs to make them work they are the bosses I just want to be able to use those ROMs on my device and they function great dev phone its almost indestructible jig Odin stock or jig Odin custom I have been successful in flashing either through Odin installing through the phone popping battery out when done jig Odin aosp kernel reboot recovery update super and booted if anyone else have an interest in seeing lollipop on this phone it can be done
TLDR; Punctuation, man!
Trying to build it. Have been since the last post. I'm not a professional but I am in fact making progress. Porting drove me crazy, so I am now trying to build from source.
Sorry about the punctuation. There was a whole lot going on at once in my head. Hopefully its a little understandable
Built the boot.img. compiling rom now. Have not tested either.
Why Lollipop instead of Marshmallow?
Boot.img works.flashed cm 11, update supersu.zip ,4.4 gapps, installed xda premium.apk. i signed in and updated status it also has SD card readability unlike the i9100 recovery and I could explain why not marshmellow yet but the base of the explanation would be I am not a programmer . I am teaching myself to do this and I thought I would start on something that has a couple of ROMs to port not many marshmellow but I don't think I will stop at lollli I have noticed that there are typos that need fixed in the source files that after edited made me that lollipop recovery
Any updates? CM13 works on the I9100, so I'm wondering if that could ever be ported to this phone.