So, as the title says, I am having problems installing MS2Ginger on my BRAVO. I downloaded the GreenbreadBravo.zip and the other backup file (I don't remember which one) and followed the instructions listed by Walter79. The install worked fine.
However after following the instructions I tried to boot up the phone and ended up with a bootloop after the Green LED light.
I think I may have downloaded the from Nandroid backup file, but i'm not sure.
Any help would be appreciated, Thanks in advance.
It sounds like you downloaded MS2Ginger3.0. It currently doesn't boot on the Bravo, I've tried. Try 2.1, it works, except for the camera.
BTW, you were supposed to download the Nandroid, just not that one.
yeah, I figured out that I had downloaded the 3.0., but after that I couldn't figure out with file to download because it was listed for the DEFY. Could you please list the two files I need?
MS2Ginger2.1
Yes, it's supposed to be listed as Defy. The Defy and Bravo are very similar phones, so we can run a lot of Defy roms, with slight modifications. Honestly, I'm not sure if there is a 2nd 2.1 file. There's more information in the thread on pages 2 and 3. I only installed 2.1 once, and after a few hours of camera lib bootlooping, went back to CM72.
Thanks, I usually don't have problems with stuff like this. I have been switching back and forth between all the ROMs for the BRAVO since I got the phone, and I can't decide whether I want to stick with stock or do what I can to make the camera work in GingerBlur.
Yes, I am one of those strange people that actually like Motoblur.lol
Try fixing the Ginger camera, if you can.
Have you tried Blur 3d Launcher at the Defy forums. It's pretty nice, but I had this issue once where widgets decided that they wanted to disappear. They came back after I found an invisible widget and moved it around. I was using CM72 at the time. It made me start to wonder how hard it would be to merge Blur with CM7.....
Sorry I can't help anymore with this, but I haven't used 2.1 very much.
Wow, I wish I would have know about this sooner, that would have saved me a lot of trouble. thanks lol
Maybe I will go back to CM7, I just figured out that I can get the keyboard too.
First though I'm gunna do what I can to get the camera working in this ROM.
Related
I bought a DX earlier this week. It was updated to system 2.3.340 before i left the store. I also have a D2 and experience flashing ROMs and SBFing. What is puzzling me here is that no matter what ROM I install i get random reboots. This happens no matter what apps, activities, etc... i am doing, even when just idle, i will look down and phone is rebooting. I haven't tried SBFing the DX yet because i can't find a clear answer on how i need to do it. I know that a full .340 SBF does not exist yet. I have a full .32 SBF file and a system only .340 file. I am assuming that i would flash the .32 full, then the .340, or could i just flash the .32 and then let the phone update the factory way to .340? I am getting this reboot problem with Rubix 1.9.5, Fission 2.4.3, and GummyJar 2.5. Any advice, input, or help would be greatly appreciated. THanks in asvance.
willjohnson said:
I bought a DX earlier this week. It was updated to system 2.3.340 before i left the store. I also have a D2 and experience flashing ROMs and SBFing. What is puzzling me here is that no matter what ROM I install i get random reboots. This happens no matter what apps, activities, etc... i am doing, even when just idle, i will look down and phone is rebooting. I haven't tried SBFing the DX yet because i can't find a clear answer on how i need to do it. I know that a full .340 SBF does not exist yet. I have a full .32 SBF file and a system only .340 file. I am assuming that i would flash the .32 full, then the .340, or could i just flash the .32 and then let the phone update the factory way to .340? I am getting this reboot problem with Rubix 1.9.5, Fission 2.4.3, and GummyJar 2.5. Any advice, input, or help would be greatly appreciated. THanks in asvance.
Click to expand...
Click to collapse
try here http://rootzwiki.com/index.php/Smartphones/Motorola/Droid-X/Droid-X.html#comment220 scroll down towards the end (idk if you use windows or linux but the linux method of sbf'ing is alot easier ive used both) except in their directions it says an older sbf file just insert the one you have, then go here http://www.mydroidworld.com/forums/...ystem-baseband-2-3-340-kernel-bootloader.html to download these zip files for kernel updater, 340 system update your baseband and bootloader should already be the correct ones, (i recently bought my X too) then once you finally root your newly sbf'd X and installed droid x bootstrap etc and get into clockwork mod recovery you can flash those 2 zips (recommend flashing only one at a time, reboot, and do the next) and then you should be updated to full .340
gl
http://forum.xda-developers.com/showthread.php?t=869007
heres a thread with discussion about those update zips
Thanks for the quick replies. Gonna try your suggestion tonight or tomorrow. Now i get random lock ups followed by a boot after about five minutes. The only upside right now is that its 4 days old so if i can get some resemblance of factory back on it then i can just exchange it Thanks again will report back with results.
And also by "insert the file you have", i assume you mean the file i have that is VRZ_MB810_2.3.32_01.sbf is the file i need to use in RSD Lite, then update the other files with clockwork recovery?
Thanks again.
willjohnson said:
And also by "insert the file you have", i assume you mean the file i have that is VRZ_MB810_2.3.32_01.sbf is the file i need to use in RSD Lite, then update the other files with clockwork recovery?
Thanks again.
Click to expand...
Click to collapse
correct tho the one i used had was labeled VRZ_MB810_2.3.32_1FF_01.sbf
I guess the one i got is ok? it came from the TBH app from the market? I would like to get ahold of the one you got too if thats possible, since you know that file works.
LOL i am a dumbass, left the FF part out for somereason, thats the exact file name i have. Thanks again.\
Edit- Just tried this, i don't know whats wrong but it has the start button in RSD Lite greyed out when i select the file, its the exact one listed above. Gonna try same file from different locations
Ok, so now i am starting to worry. Tried 3 different .320 full sbf's. All the same result. Failed process close to the begging. Then on the phone it says
Critical Error
FEBE
0047
Please Helppppp. I don't need a really expensive paperweight, all i need to do is get it so that GummyJar doesn't show on boot and i can take it back, its brand new.
Try removing the battery. Then boot into recovery (volume down + power) then do a factory reset/restore.
Sent from my ADR6300 using XDA App
Tried that, i finally got it to flash, i had the phone in the desk dock, didn't think about it. Once i plugged it into the usb cable direct everything went fine(so far). Also i noticed that with this phone and my wifes D2, i have to put a (1) at the end of the sbf file name to get RSD Lite to use it, otherwise the start button stays greyed out. THanks for the replies and help, will post again if there are any more problems.
willjohnson said:
Tried that, i finally got it to flash, i had the phone in the desk dock, didn't think about it. Once i plugged it into the usb cable direct everything went fine(so far). Also i noticed that with this phone and my wifes D2, i have to put a (1) at the end of the sbf file name to get RSD Lite to use it, otherwise the start button stays greyed out. THanks for the replies and help, will post again if there are any more problems.
Click to expand...
Click to collapse
ive heard there are several problems with rsd lol thats why ive stuck with my ubuntu/Linux its 10x easier
willjohnson said:
I guess the one i got is ok? it came from the TBH app from the market? I would like to get ahold of the one you got too if thats possible, since you know that file works.
LOL i am a dumbass, left the FF part out for somereason, thats the exact file name i have. Thanks again.\
Edit- Just tried this, i don't know whats wrong but it has the start button in RSD Lite greyed out when i select the file, its the exact one listed above. Gonna try same file from different locations
Click to expand...
Click to collapse
i also believe you DO have to have it all in specific locations but idk i use linux to do it, if you continue to play with the X after u get new one i would read up on how to dual boot ubuntu its a whole lot easier once you find ur way around i have it booting off of a 1TB external hard drive no need to install the correct moto drives etc..just plain easy lol
Finally total success!!!! Flashed .320 Full SBF, then used the Kernel and System updates you referenced and bam, back to stock. Now i feel better about ROM flashing, cause i can recover from most anything with this process. THanks again for your help and info.
willjohnson said:
Finally total success!!!! Flashed .320 Full SBF, then used the Kernel and System updates you referenced and bam, back to stock. Now i feel better about ROM flashing, cause i can recover from most anything with this process. THanks again for your help and info.
Click to expand...
Click to collapse
it only takes once correctly doing it to feel comfortable lol also make sure using droid x bootstrap recovery make sure to tap the first choice and let it do its thing, otherwise it will constantly reboot to recovery EVERY time you turn it back on
Well... the SBF and updating where successful. But even after the SBF, SD Card Formating(Long format in windows, then 3 times on phone to be sure), clean install and download of all Fission stuff i normally use, still get random reboots. Gonna SBF again and try Rubix and see how that goes. If it still has problems too, i may SBF again and go to the store and return phone for a new one.
willjohnson said:
Well... the SBF and updating where successful. But even after the SBF, SD Card Formating(Long format in windows, then 3 times on phone to be sure), clean install and download of all Fission stuff i normally use, still get random reboots. Gonna SBF again and try Rubix and see how that goes. If it still has problems too, i may SBF again and go to the store and return phone for a new one.
Click to expand...
Click to collapse
try something blurless like darkslide, which im currently running, no random reboots
Funnyface19 said:
try something blurless like darkslide, which im currently running, no random reboots
Click to expand...
Click to collapse
LOL funny you should mention, thats what i actually decided to go with instead. It really looks great, seems to be seemless too. Since you use it maybe you could tell me... Can you overclock? I downloaded the blurless version from their link and it has the blur alarm clock and a few others? is this right or is something wrong with the link? Thanks again.
willjohnson said:
LOL funny you should mention, thats what i actually decided to go with instead. It really looks great, seems to be seemless too. Since you use it maybe you could tell me... Can you overclock? I downloaded the blurless version from their link and it has the blur alarm clock and a few others? is this right or is something wrong with the link? Thanks again.
Click to expand...
Click to collapse
Well I haven't overclocked yet anyway the phone gets hot enuf lol plus coming from an Eris 1k is fast lol
Um yeah it should be wright depends on what the blur clock looks like lol
Sent from my DROIDX using XDA App
I looked back at there post in another forum and it actually says that they added a few Blur parts in the blurless rom. I guess some blur things just work better.
willjohnson said:
I looked back at there post in another forum and it actually says that they added a few Blur parts in the blurless rom. I guess some blur things just work better.
Click to expand...
Click to collapse
yeah but the obsidian rom is completely blurless just not everything working
Running DarkSlide4.1 can't tell u last I had a reboot
Sent from my DROIDX using XDA App
Hey guys, I just wanted to share my experience so far. I can't post on the MIUI page because I don't have enough posts, so I'll share here for anyone interested.
For anyone wanting to try MIUI for the DX, here's my experience, some tips, and suggestions.
-Beware, installing or trying to install ANY ROM may brick your phone. although it's very rare and unlikely to be unable to find a solution to problems, it can and has happened. so take caution and read instructions and so-forth carefully.
Some history of my DX. I soft-bricked my phone back in the early months of the DX trying to deodex it to install themes. It was stuck on M logo for 2 days before i learned enough from scratch to find out what an SBF was, where to find it, and how to flash my phone back to stock. Ever since then these nice folk on XDA-developers forums and other droid forums have helped me successfully mod my phone many times, through Q&A, detailed instructions, and a little luck.
I've rooted my phone using the command method, Z4Root, and several other processes. Some were hard to figure out, some soft-bricked my phone, most were easy as pie. I'm on a Z4Root atm.
The first successful ROM I installed was GUMMY-JAR. I liked it, it was good to me. nothing like the comprehensive ROMs out now though.
Then I jumped to Liberty 1.5, Liberty x.x etc... Liberty was awesome, but was still basically Froyo with advanced options. I loved it.
Now, just today, I've installed MIUI. And let me tell you, its amazing!
For anyone running Froyo Liberty ROMs, I believe that you can install MIUI right over the top. I didn't think it was going to work, as I hadn't seen anyone mention if it did or not over the top of Liberty 1.5.
If you want to install MIUI, go here. http://forum.xda-developers.com/showthread.php?t=1181486
You MUST be rooted, and be running FROYO, NOT GB! You must also have the Droid X bootstrapper.
I won't give instructions, as I'm not qualified to do so. But I can tell you what I did from Liberty 1.5. MAKE SURE TO MAKE A BACKUP FIRST! 1) I downloaded the MIUI ROM from the above XDA post to my SD card on my phone. 2) I clicked 'bootstrap recovery' on the DX bootstrapper app, then 'reboot recovery.' My phone booted into clockwork recovery mode. 3) wiped data/factory reset. 4) cleared cache. 5) install from SD Card. 6) install MIUI.zip i downloaded from the link i posted above. let it run it's course. rebooted. DONE.
It's really that easy if you are running the DX stock Froyo kernal.
Keep in mind with MIUI, it does NOT auto-sync your Google account. you need to go into the options>>accounts/sync and add your Google account. You can then re-install apps from your backup or just re-download them. Make sure you've synced your contacts with your Google account so they will be there when you add your Google account.
Some thoughts on MIUI...
There is NO STOCK APP DRAWER. I recommend ADW launcher or Launcher PRO. The MIUI launcher inst bad, but it's like iOS in that there's no app drawer. It's just a bunch of screens with all your app icons like an iPhone.
You can download theme's and customize themes through settings>>personal>>theme manager. MIUI allows you to change fonts, boot animation, boot audio, lock-screen style, status bar, icons, launcher, wallpapers, text style, dialer style etc. There's tons of pre-made packages, but you can also change them all individually and create one you like best. You can do all of this directly from the settings menu including looking up new themes, downloading them, and applying them.
MIUI is running on 2.3.4 GB. So it wont say 2.2 anymore after you install. (I believe the kernal is still Froyo though? Please correct me if I am wrong)
I really hope this helps some of you newbies. I am thankful for all of you that have made posts like this that I have found useful in the past.
Note- some people are having issues installing MIUI. They are getting bootlooped on the M logo for some reason. I have no idea why this is, it worked perfectly for me first try. Just remember to follow the instructions on the ROM page, and that you are running the correct version of Android. You shouldn't get a boot-loop if you do so.
Hope this helps!
i have a question.... and this question is what will decide if i keep this or go back to liberty gingerbread....
how the hell do i flash anything.. i can't even install clockwork mod without getting bootloops.... and i'd love to flash certain apps onto this.... but if this can not be done i will have to go back.... the only thing going into recovery does is use the retarded original recovery... and that is a big deal.. if i ruin my phone on the go and need to pullup a backup i can not do this with this rom and i will end up phoneless until i can get to a computer to sbf
nosboost300 said:
i have a question.... and this question is what will decide if i keep this or go back to liberty gingerbread....
how the hell do i flash anything.. i can't even install clockwork mod without getting bootloops.... and i'd love to flash certain apps onto this.... but if this can not be done i will have to go back.... the only thing going into recovery does is use the retarded original recovery... and that is a big deal.. if i ruin my phone on the go and need to pullup a backup i can not do this with this rom and i will end up phoneless until i can get to a computer to sbf
Click to expand...
Click to collapse
What exactly are you asking? "Flashing" is the process of basically overwriting your current Android OS with an Android OS SBF. If you are trying to install MIUI, you cannot do it with Gingerbread installed on your phone. "You MUST be on CyanogenMod 7 or .340 Froyo to flash this rom!" (MIUI)
If you want to install MIUI, i think the best bet would be SBF flashing to stock DX 2.2 .340 FROYO, re-rooting, then using the DX boot-strapper to boot into recovery. Then installing the MIUI .zip from SDcard in the recovery menu. Everything should work fine after that. Rmember you CANNOT go into recovery using DX boot-strapper once this ROM is installed. you CAN go into recovery with this ROM using ROM-manager. This is what I have experienced so far, and what others have said also.
no.. i already have the rom installed... i just want to be able to go into recovery without needing to be booted up.
i'm trying to install some zips through clockwork such as the old blur camera and a few other things... i will install rom manager and see how it goes from there... i love the UI of this rom but as far as being comfortable and stable.. liberty gingerbread has my vote as of now
i've cleared my cache and data several times and i get force closes alot. and this is a clean install coming straight after an SBF.
with liberty gingerbread i had the ability to set it so every phone reboot, even if a battery pull, would boot directly into clockwork mod.. making it easy for me in case i installed a zip that would get me into bootloop
Hmm, sorry mate, I dunno what to tell ya. Try looking aroudn forums or startign a new thread. someone more knowledgable than you or me will help you out.
thanks for everything though!! this really is a beautiful rom and i'd love to stick with it... i'll bite the bullet for the meantime and post around to get some help... i'd love to post in the developer section but i don't have enough posts yet.. haha
nosboost300 said:
no.. i already have the rom installed... i just want to be able to go into recovery without needing to be booted up.
i'm trying to install some zips through clockwork such as the old blur camera and a few other things... i will install rom manager and see how it goes from there... i love the UI of this rom but as far as being comfortable and stable.. liberty gingerbread has my vote as of now
i've cleared my cache and data several times and i get force closes alot. and this is a clean install coming straight after an SBF.
with liberty gingerbread i had the ability to set it so every phone reboot, even if a battery pull, would boot directly into clockwork mod.. making it easy for me in case i installed a zip that would get me into bootloop
Click to expand...
Click to collapse
You need to install Rom Manager, and select flash Clockwork Recovery. Make sure you select Droid X (2nd Init). Then you can reboot into recovery with Rom Manager :-D
laxattack said:
You need to install Rom Manager, and select flash Clockwork Recovery. Make sure you select Droid X (2nd Init). Then you can reboot into recovery with Rom Manager :-D
Click to expand...
Click to collapse
but the problem is that i would like to be able to go into recovery without having to do it through an app... i'd like to make it so every reboot (including battery pull) makes it boot into recovery. thats how i had liberty gingerbread doing it... if not.. i can live with it.. i'll just be a little more careful on what i'm installing
Just wanted to chime in about MIUI rom, I just flashed it yesterday and am ABSOLUTELY loving it thus far. I had no trouble at all installing the rom what-so-ever. I used ROM Manager to do the whole thing: downloaded newest ver. of MIUI, backup current ROM, wipe data and dalvik. Let it run its course and it rebooted and was up and running in no time flat!
This is my first post in XDA.I hope this is the right spot for this questions.
I have searched everywhere for the answers to this question before posting. I flashed to CM7 with the tiamat kernel awhile back. I love CM7 but was curious to see what other rom developers are doing.
I ALWAYS do a back up before doing any flashes. I backed up my CM7 and my base rooted HTC downgraded 2.2 through RM. I was able to flash to synergy with no problems and restore to CM7. I decided to check out MIUI over the weekend. I flashed it with no problem. Last night I wanted to try mikshifted-g and Supreme Sense . I could not install either of them . The both stalled once CWM started to install. It was stuck on updating. There were no errors. I took the battery out and tried to restore CM7 backup through CWM. The restore went as expect but when I went to reboot it was only the HTC logo. I took the battery out and went back to MIUI through CWM and the phone booted. I then did a restore of my original rooted 2.2 the phone booted. I tried to install the above again on a fresh HTC stock rooted phone through RM and still had the same thing happen.
My question, is why I am not able to flash any other roms successfully other than restoring to MIUI and stock rooted htc 2.2 ? Installing Synergy works !
I do a full flash of system,data, cache and dalvik cache. I am not sure what I am missing.
If I understand correctly MIUI is a GB kernel as well as the others so there should not be a problem of compatibility ? I am assuming I still have root ? My HBOOT does say S off and PG 06001. I will try downloading CM7 through MIUI again to see if it works through RM. Sorry for the long post. I wanted to give as much detail as possible. Thanks in advance for any help
Richard
My suggestion would be don't use ROM Manager to flash, wipe or make nands. Do everything manually through recovery. I've seen too many people have the same type problems when using ROM manager.
what I have noticed is the progress bar in cwm doesn't work with sense roms, at least it never did in the mikshifted roms i tried and they take a LOT longer to install than cm7. How long did you let them sit at the install screen with that blank progress bar? Try clearing all your data/caches then install a sense based rom but leave your phone alone for like 10 minutes while it sits at that screen with the blank progress bar that says mikroms or whatever it says (been awhile since i used one). It shouldn't take 10 minutes but if your phone sits at that screen for that long then you know for sure it isn't working. I pulled my battery a couple times before i realized that's what was happening. I read about it somewhere online.
I have tried both RM and CWM. Both have the same results. 99% of the time I prefer the manual CWM method. Sorry I did not make it more clear.
I did re-flash CM7 with no problem. I do let the rom flash sit for a while but I will try longer since you say it takes longer with the roms in question. I let it sit for a few minutes. That seems like it should be more than enough. CM7 is pretty quick to install as well MIUI like you said. I love the layout and features of MIUI but since I am in a 4G area seems to defeat the purpose of having 4G if you can't use it. To be realistic though 4G is spotty in Atlanta and I mostly end up for 3G or using my wireless at home. I will probably end up with CM7 again since I like it equally as much as MIUI. If I wait longer for it to install and it does not work is there anything I should be looking at as the culprit other than myself
you were right, it just took a LONG time to install. I thought I was losing it. It took over 5 minutes. I am used to the install times of the MIUI and CM7 . Thanks for telling me to wait a little long. It's always the simple overlooked things like patients
My advice is just make sure you do a FULL Wipe before flashing a Rom. Like on THIS GUIDE, saves headaches later. Aslo, as you've learned Sense Roms usually take quite a bit longer than MIUI ,ASOP, or most others. But yes patience is important .
I definitely do a full wipe . I used all the guides here to make sure I did everything correct. I did not realize that the sense roms took longer than the CM or MIUI. I love the layout of MIUI. I wished it at some point 4G was going to be a part of it but I understand why it will not be .
4G in Atlanta, GA is not reliable, at least on my shift with sprint. I hate to pay for a feature that I am not able to use on regular basis. It's so spotty here I have gotten used to it.
I was never a big sense fan but it seems like if you want to have the 4G feature you use either use CM or another Sense rom right ? I got the shift because of how solid it's built and many reviews favor the EVOs or Galaxy S on Sprint
Thanks for all the feedback
Richard
Well you might want to give [AOSP ROM] S.O.A.P. ROM (sense-ish on android phones) a try. Sounds more like what your looking for. It's by one of the Shift members here.
Here's my issue. I was using the latest racks prepared boot for CM9. The one dated 5/1 or so. I decided I wanted to try my hand at converting a nightly and flashing it on my own. I've been having nothing but trouble with the conversion process and I have no idea what I'm doing wrong.
And I've tried a few different ones of Eyeballers nightlies, but I'm always getting the same error. I just tried it using the Android script and the windows script and I'm getting different issues in each.. When I try to convert in dos, i'm getting really tiny files and most of the time it gives me a bunch of lines with items not found.
I'm really new at this but I've looked and was unable to find any answer to why this wouldnt be working or even what i could be doing wrong. I can get into the recovery, I install the converted nightly and when I try to boot into it I just get a black screen, I waited a few minutes to make sure it wasnt just something with the the device or just a first time thing but nothing happened.
on the android version I get the error attached. Im not sure how else to say whats going wrong but if someone has some suggestions I'd really appreciate it.
You might get a better response if you post this question in Racks conversion thread. Here:
http://forum.xda-developers.com/showthread.php?p=25648626
Sent from my Nook Color running ICS and Tapatalk
unfortunately I am not able to until I reach the 10 post threshold. but rather than spam to hit that. I figured I'd try this first. Thanks though. Hopefully he'll still see this.
kontam said:
unfortunately I am not able to until I reach the 10 post threshold. but rather than spam to hit that. I figured I'd try this first. Thanks though. Hopefully he'll still see this.
Click to expand...
Click to collapse
I will put a post there for you.
kontam said:
Here's my issue. I was using the latest racks prepared boot for CM9. The one dated 5/1 or so. I decided I wanted to try my hand at converting a nightly and flashing it on my own. I've been having nothing but trouble with the conversion process and I have no idea what I'm doing wrong.
And I've tried a few different ones of Eyeballers nightlies, but I'm always getting the same error. I just tried it using the Android script and the windows script and I'm getting different issues in each.. When I try to convert in dos, i'm getting really tiny files and most of the time it gives me a bunch of lines with items not found.
I'm really new at this but I've looked and was unable to find any answer to why this wouldn't be working or even what i could be doing wrong. I can get into the recovery, I install the converted nightly and when I try to boot into it I just get a black screen, I waited a few minutes to make sure it wasnt just something with the the device or just a first time thing but nothing happened.
on the android version I get the error attached. Im not sure how else to say whats going wrong but if someone has some suggestions I'd really appreciate it.
Click to expand...
Click to collapse
1.Are you using latest version of script 1.3?
2.Did you try the terminal emulator for running script?
3.Did you try to delete and extract again the folders of the c2dsd in case something went wrong during first extraction?
thanks for posting there for me.
RASTAVIPER said:
1.Are you using latest version of script 1.3?
2.Did you try the terminal emulator for running script?
3.Did you try to delete and extract again the folders of the c2dsd in case something went wrong during first extraction?
Click to expand...
Click to collapse
1. I updated both scripts and was still getting issues.
2. if you mean the one on android then yes, thats what I was using. I also tried it using the cmd on windows.
3. I've tried that at least two times with each including redownloading all aspects of it to make sure that wasn't the case.
kontam said:
thanks for posting there for me.
1. I updated both scripts and was still getting issues.
2. if you mean the one on android then yes, thats what I was using. I also tried it using the cmd on windows.
3. I've tried that at least two times with each including redownloading all aspects of it to make sure that wasn't the case.
Click to expand...
Click to collapse
Not sure about the windows issue. I'll have DizzyDen take a look at that. But with the Android version, i'll take a look at that in a little while. Looks like it's another mistake on my end. Mkimage is dependent on 'libmusl.so' which I did not include in the tools folder. I overlooked this tidbit because I had "BOTBREW" installed on my system so it never complained about linking to it.
Sorry for all the problems. I'll try and have a fix ASAP. Your feedback is much appreciated. Can't fix things if I don't know if their broken or not.
Thanks,
Racks
EDIT: Fixed I believe. Please try the v1.3a for the Android script.
I'm looking into the DOS version as we speak....
You guys are all really amazing for helping me out.
And as probably mentioned before by rasta Im not sure what the issue is but theres still something not quite gelling for the version. I took another screen to hopefully help you identify where its going weird. It is a little different but its still that crc cd issue. Im not going to try to flash it to see if it works, only because Im pretty certain that won't do it. But I really appreciate you looking into it.
and for clarity I also get a very similar if not exactly the same message when It trys to do the gapps as well. (using the 4/29 signed gapps)
And I decided now to try flashing the rom. it worked. Fantastically! though the boot animation is freezing. I dont even care about that since its actually working again. Awesome. But.. now im having those same issues as Rasta with the gapps. I flashed them and when I went to reboot it brought me to stock. When I converted them, i converted them with the rom. That rom worked. the gapps did not. if theres anything else I can help just ask and Ill try to do. Im just so happy to have a bootable CM9 again. Thank you so much
kontam said:
You guys are all really amazing for helping me out.
And as probably mentioned before by rasta Im not sure what the issue is but theres still something not quite gelling for the version. I took another screen to hopefully help you identify where its going weird. It is a little different but its still that crc cd issue. Im not going to try to flash it to see if it works, only because Im pretty certain that won't do it. But I really appreciate you looking into it.
and for clarity I also get a very similar if not exactly the same message when It trys to do the gapps as well. (using the 4/29 signed gapps)
And I decided now to try flashing the rom. it worked. Fantastically! though the boot animation is freezing. I dont even care about that since its actually working again. Awesome. But.. now im having those same issues as Rasta with the gapps. I flashed them and when I went to reboot it brought me to stock. When I converted them, i converted them with the rom. That rom worked. the gapps did not. if theres anything else I can help just ask and Ill try to do. Im just so happy to have a bootable CM9 again. Thank you so much
Click to expand...
Click to collapse
Thanks for the feedback... looking into gapps issue now... is this for primary or alternate?
Everything I'm referring to is for the alternate. Also not sure if this has anything to do with it but the calendar is broken with the gapps back from the novemeber or whenever dual boot apps. But flashing the fix doesnt fix it anymore, and then a reboot after that brings me to stock.
Also, im having issues doing a factory reset on stock when i take the SD card out.. is there something that clockwork did when it was trying to flash an incorrect rom?
If you want to return to stock situation, you probably should wipe everything and find stock image to flash.
Unleashed from my Revolutionized Desire HD
Hello there! I really hope you can help me with this, because I don`t have any other ideas or even the courage to try new ones. I recently bought a defy plus and after tens of pages read on the Internet about kernels, SBFs, ROMs and other android stuff I decided to start modding it. It came with a stock 2.3.6 Android, which I swapped for a ParanoidAndroid 2.14 (with Android 4.1.1), which I liked a lot, but I was quite laggy.
Then I decided to look for other ROMs and I wanted to install CM7. But here is my problem: I can`t. I tried to flash this file (cm-7.2.0-jordan), but it didn`t work. Then I had to flash a SBF to get my phone back. I think it was the wrong SBF (filename: JRDNEM_U3_3.4.2_179-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTTR_P013_A013_HWp3_Service1FF.sbf) because it bricked ( hard brick, I couldn`t even start it), but luckly I had it fixed cause I still have my guarantee (which is a mistery for me, how did they do it? didnt they see it was rooted and this broke the terms of the guarantee?).
Anyway, they re-softed it and now I have a working phone. I rooted it, installed 2nd init and tried again. Now with a nightly version of CM7: cm-7-20130301-NIGHTLY-jordan. It still goes into a bootloop. I went through all the steps, root phone, install 2nd init, Wipe data/factory and Wipe cache and install from sd card.
My first and most important question is: do I have to be on stock android (meaning I have to flash the stock 2.3.6) every time I want to flash a custom ROM? Or can I be on, let`s say ParanoidAndroid, and change directly to CM10?
And my second question: How can I install CM7 for defy plus?
Thank you for your future responses.
Ok, I figured out the CM7 part, I think I was trying to flash a wrong nightly file. I got another one and I finally have CM7 on my phone. But, please, can someone give me an answer to my first question: For every custom ROM I install, I have to go back to stock 2.3.6 every time? Or can I flash, for example a MIUI, right now, on my CM7, without going back to stock rom?
No need to flash stock every time. Data should be wiped along with cache
Sent from my MB526 using Tapatalk 2