okay, so I flashed the CM7 (prefinal) ics rom and all was well for awhile till i decided i was sick and tired of it because it seemed really laggy and imcomplete, so I figured I'd go back to stock 4.5.91 and to do so, you have to (atleast to my knowledge) RSD flash it to your phone. So i did, and my phone is now in the infamous infinite bootloop. Now I know there are already a million threads on this, but this is the first one (ive seen) that has THIS problem and got to it THIS way. I dont know if CM7 prefinal updated to 2.3.6 and you cant go back or if you cant flash back to stock period. Any advice? Thanks in advance.
Did you do an OTA update to gingerbread?
Sent from my MB860 using XDA App
You should have flashed a fruitcake via recovery instead of rsd. It is safer. However I believe I also got a bootloop when going back to stock via a fruitcake. Can you get into recovery?
Sent from my MB860 using XDA App
Yes, I did the OTA update to 4.5.91. If it matters (which I don't think it does), I was rooted and unlocked, I had the CM7 kernal + prefinal ROM installed, and tried to revert to stock 4.5.91 via RSD. Maybe its because I installed the kernal? And I can get to stock (worthless) android recovery.. actually scratch that, I can get to the triangle with the ! in the middle, but the menu wont pop up...
psshh is this a joke? I finally figured out to access the dumb stock recovery (yeah i know, its common knowledge) and formatted cache/system and it worked! What im trying to figure out is why it worked..... o well.
lol great i was going to suggest flashing.a fruitcake they are closest to stock without the pitfalls of rsd light
Sent from my MB860 using Tapatalk
Related
i have Motorola droid 2 on 2.2 rooted with bootstrap recovery, everything was workin fine till i decided to install custom rom, which was unleashed epic 2.5 (by mat) and now everytime i turn on my phone it goes into a loop reboots and never turns on all the way.
i have tried using sbf RSDlite to restore it, tried using linux ubuntu(newk8600 method ty btw) method as well to restore it, none seems to work i keep getting errors whenever i try to do it.
however before i installed the custom rom i did full backup using bootstrap recovery but the only way (that i know) to get in recovery is using bootstrap app, so is there a way i can manually get into bootstrap recovery so i can restore from backup?
please let me know, or if you have different method i'll appreciate your help. thanks in advance.
Which version of the software did you have before you installed epic unleashed, and which SBF did you use?
From what I have heard, Epic Unleashed will "brick" your phone if you try to install it on the 2.3.20 build. Since your phone did get bricked, it's likely that you are running 2.3.20 and not 2.2. You might want to make sure you are using the 2.3.20 SBF to flash your phone, and not the 2.2 SBF (which won't work because the kernel changed between the two)...
What type of errors do you get?
i always have luck getting into clockwork recovery by having my phone plugged in and within the first few seconds taking out my battery forcing it to take along time booting after the M logo and hence putting it into clockwork. I hope this helps
after you get passed the M pull the battery then boot back up it should come up in to recovery
thank you all for your help, however i tried all of these steps already, but i found another way to get it workin, here is the solution to whom got the same problem as mine.
its not letting me post the link for some reason, anyway just search for (Droid 2 Global SBF File (2.4.29) Full and RSDLite ).
just got relased today , big thanks to team Black Hat and MyDroidWorld
hope that helps.
Glad you got it fixed. Let me ask you something though. Before you installed the custom rom, did you wipe data and cache? Not doing so could result in a bootloop.
Sent from my DROID2 using XDA App
orkillakilla said:
Glad you got it fixed. Let me ask you something though. Before you installed the custom rom, did you wipe data and cache? Not doing so could result in a bootloop.
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Sounds like the OP was trying to install a ROM for the original Droid 2 on the Droid 2 Global. It wouldn't have worked, no matter what install steps were used.
Phoible said:
Sounds like the OP was trying to install a ROM for the original Droid 2 on the Droid 2 Global. It wouldn't have worked, no matter what install steps were used.
Click to expand...
Click to collapse
Ah op didn't mention it was a global. Should have realized when he said he used the global sbf though... brain fart
Sent from my DROID2 using XDA App
orkillakilla said:
Ah op didn't mention it was a global. Should have realized when he said he used the global sbf though... brain fart
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
It's all good people need to read where they are posting this is in the D2 General section not the D2 Global general section. That's half his problem, he's been looking at ROMs for the original D2 not the device that he currently uses.
So I couldnt find a thread that quite answered my question. I have many ideas, but no sure answer, and I dont want a brick.
I have a rooted and Deodexed X on 2.2 that couldnt update to 340 for whatever reason. I want to update to OTA 340 and run the ApeX 141 ROM on that. Should I undo the root and reodex the phone before updating? Can I update it somehow as is and not have a brick? I saw something about doing an SBF, but Im not entirely sure if thats what I do...
Ive been away too long... ha
You could do an sbf, it is not too hard but if you don't know much about it you might as well try to stay away from it. What system version are you on exactly?
If you end up doing an sbf back to stock there are a few videos on youtube that walk you though the process. I watched xdroidroms and it worked perfect for me.
Sent from my DROIDX using XDA App
http://www.youtube.com/watch?v=N0jrXqqiepI&feature=youtube_gdata_player
Video walkthrough
Sent from my DROIDX using XDA App
If you decide to sbf it will automatically put you on 2.3.340. Just download the full version not the system only file. After that z4 to root. Install bootstrap make a backup and flash away. Good luck. Don't worry doing an sbf is not hard. Just read and read some more.
Sent from my DROIDX using XDA App
SoundZombie said:
So I couldnt find a thread that quite answered my question. I have many ideas, but no sure answer, and I dont want a brick.
I have a rooted and Deodexed X on 2.2 that couldnt update to 340 for whatever reason. I want to update to OTA 340 and run the ApeX 141 ROM on that. Should I undo the root and reodex the phone before updating? Can I update it somehow as is and not have a brick? I saw something about doing an SBF, but Im not entirely sure if thats what I do...
Ive been away too long... ha
Click to expand...
Click to collapse
I'm running that now, it's awesome.
2.2.1 rooted apex 1.4.1 honeybread v2
What I ended up doing was the Materstcok method. Seemed to be a lot easier then trying to learn sbf. Unfortunately I ended up having to do an sbf anyway because I tried deodexing for some reason. Haha. It all worked out in the end anyway. Loving the ApeX ROM as well!
Sent from my DROIDX running ApeX using XDA App.
Sbf wasn't as difficult as I thought, I used it to get back to stock in order to be able to flash gingerbread.
Droid X 2.3.3 Rooted
Morning all,
Is anyone running the Gbread 595 leak yet? I am thinking about trying it out this morning, as everything I read indicates it will be the launching point for what could be the official 596 release on the 13th.
Let me know if you have any observations on this.
Thanks,
Steve
I downloaded it yesterday, and am running liberty v.5 on top of it and I love it. It is really fast, and other than a few bugs with my contacts syncing up with facebook, I am having no problems.
Im gonna wait it out, till we get the official release... Apex2.0.0 is pretty sweet for now
Sent from my DROIDX using XDA App
owenbeals said:
Im gonna wait it out, till we get the official release... Apex2.0.0 is pretty sweet for now
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I agree. Apex is amazing. I will wait for it to update
Weird issue I am running into....
I upgraded to 588 with no problems from 340 Froyo. I used DroidX recovery to accomplish this. When I rebooted 588 I tried to go to 595. I tried using DroidX recovery but this did not allow me to boot into recovery...it only gave me a blank screen. When I got back to 588 I uninstalled DroidX recovery and then installed Droid2 recovery. I was then able to reboot into recovery and try to install 595. The install aborted saying it was looking for 3 arguments and got 4.
Any ideas? Which recovery should I be using thoughtout this?
Thanks,
Steve
Both recoveries (AFAIK) are the same clockwork recovery, it's just a different method of "bootstrapping" so that you can get into the recovery. Droid2 bootstrap works on gbread unless USB debugging is disabled, then droidx bootstrap works.
Sounds like you got a bad file.
Just redownload the file and it should work
Yes the one I downloaded yesterday was bad, and a new one was uploaded. I just downloaded the new one and am going to try again to move back up to 595. Once that happens I am hanging on til the 13th.
I would assume once this official update comes out then VZW will no longer support the DX with official updates. We really need to get Moto to unlock the bootloader for us, so we can continue to develop for the DX.
Steve
I have made it successfully to 595. I am having a problem with Gingerbreak 1.2, so I am betting there is something in 595 that doesnt allow it to root.
stevefxp said:
I have made it successfully to 595. I am having a problem with Gingerbreak 1.2, so I am betting there is something in 595 that doesnt allow it to root.
Click to expand...
Click to collapse
P3Droid released three different versions of .595: full stock, rooted and odexed, and rooted and deodexed.
You can try flashing one of the rooted .595 releases.
Sent from my DROIDX using XDA App
Yes it looks like the rooted ones will accept Gingerbreak. I may go back to .591 and hold there until the official OTA version comes out.
You shouldn't need Gingerbreak on the rooted ones, as they are already rooted.
stevefxp said:
Yes it looks like the rooted ones will accept Gingerbreak. I may go back to .591 and hold there until the official OTA version comes out.
Click to expand...
Click to collapse
If you are going to flash a rooted version what do you need gingerbreak for?
smiteme said:
I downloaded it yesterday, and am running liberty v.5 on top of it and I love it. It is really fast, and other than a few bugs with my contacts syncing up with facebook, I am having no problems.
Click to expand...
Click to collapse
So you're not running it at all then... lol. You downgraded it back to .591 when you installed Liberty.
Sent from my DROIDX using Tapatalk
Curious, I'm running .573 now, if I flashed the latest rooted & deoxed, do I really have to sbf back to Froyo before hand like I've read in other places? OR can I just flash over it and roll on?
You only need to flash back if you don't have root, I believe.
Sent from my DROIDX using XDA App
Not having luck.
I tried to install, initially from my rooted deoxed stock .340 to rooted deoxed .595, first got a corrupted file report....would not upgrade.
Next got boot loop (repeating M), so SBF back to stock 340...Rooted and tried again with the same file and got a very unstable phone, reboots etc.
The only thing I can think of is that the phone was stock rooted but not deoxed, so when I tried loading the deoxed version it didn't like it? no idea.
I did a wipe before each load but can't seem to get it to work on my phone. My phone is very new.
SBF'd back to stock unrooted and I'll leave it like that to see if I can get the update from VZW.
I believe you have to start at .588 (or .573) then flash .591 over it, then flash .595 over it.
Sent from my DROIDX using XDA App
I'm on 2.2 and waiting. Just not convinced about 595 and getting the update. How do we know its going to be 596.
Sent from my DROIDX using XDA App
infazzdar said:
I believe you have to start at .588 (or .573) then flash .591 over it, then flash .595 over it.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Not completely accurate.. I went from .588, to .595 without any adverse effects. Phone is a bit snappier than before too, app drawer scrolls more fluidly, etc.
Going on 2 1/2 hours now.. Nothing but problems... I got all the way to installing Liberty, restarted, and got stuck at the Liberty boot logo.. Now I'm having to SBF back to 2.3.340, root, back to GB leak, then try again... I wanna pull my hair out and throw my phone against the wall...
Did you clear data the first time?
Sent from my Xoom using XDA Premium App
Yea, I've done it all. Nothing seems to be working. Sbfing back to 2.3.340 AGAIN!
Are you trying to flash a deodexed or odexed version of GB? if so you need to flash a rooted version of the official ota updated before flashing the custom GB.
If you are SBF'ing back to 2.3.340, then you might as well give CM4DX (CM7 for DX) a try. The beta was released yesterday, but of course, there are bugs that still need to be worked out.
I'm really loving it though...
Isn't 3g broken on it?
Sent from my DROIDX using XDA App
Lofi Goosh said:
If you are SBF'ing back to 2.3.340, then you might as well give CM4DX (CM7 for DX) a try. The beta was released yesterday, but of course, there are bugs that still need to be worked out.
I'm really loving it though...
Click to expand...
Click to collapse
I'm gonna wait until they fix all of the bugs. I just got Liberty last night, but didn't realize there was a new version for GB. I just posted a thread about an error I'm getting trying to sbf to gb. Anyone know what this could be?
http://forum.xda-developers.com/showthread.php?p=14765687#post14765687
Thanks!
Hi everyone, I been reading on this forum for a quiet some time now but never felt the need to create an account to post any questions. because i always find informative threads that help me solved my problems but not this time.
i been helping my friend to tried to install a custom rom on his D2, i wouldnt say im very experienced, but i have done it to couple other phones including a droid x so im kind of familiar with what to do.
so i rooted it, bootstrapped, using rom manager to install cwm, then bootstrapped to cwm recovery, from there wipe data / cache, then install zip from sd.
i tried with cyanogen mod first, but it didnt work, it would get stuck on the m logo after rom is installed, so i sbfed it and repeat the whole process and installed the liberty this time but same thing happened again, so i repeated the whole process again and i tried liquid smooth just now, and it still didnt work.
is there something im missing?
You need to make sure the phone is on gb. Also wipe data/cache/dalvik once before you flash and twice after.
Sent from my DROID2 using xda premium
so it has to be 2.3 and above? the system say its 2.2 right now, but the sbf file i used its "vbz a955 2.3.20_1ff" so i assumed it was on gb. is there specific version of gb i need to upgrade to?
thanks for the suggestion
To flash cm7 or any gingerbread rom you have to first be on the ota 2.3.3
Sent from my DROID2 using xda premium
ooohh thanks! whats the best way to update to 2.3.3? do you have a link? all the links i see is for 2.3.0
thanks alot hope if works
The best was to update is to sbf to stock 2.2 then accept the ota update. Then once you update you can root, bootstrap then install cm7.
Sent from my DROID2 using xda premium
hmm im using doroot , and i can root it after the update, is it normal?
Just follow this tutorial. http://www.droid-life.com/2011/09/0...roidx2-droidx-and-droid3-running-gingerbread/
Sent from my DROID2 using xda premium
thanks, everythings fixed!