Hi everyone,
I've been having some serious issues and I am stumped on what to do so I'm turning to you smart guys here at XDA...
I'm using a Droid X2 flashed to Cricket, running CM7.2. I read through the CM10 Jelly Bean thread and really wanted to give it a try because of all the neat features it has in it. I did a Nandroid backup, installed the zip and gapps, wiped data/cache and booted into CM10. Everything went good, got CM10 configured, but had a non-relevant issue with CM10 and figured it was probably just a bad install. I tried to restore my Nandroid and it froze up halfway through and sat at "Restoring .android_secure" for OVER an hour. So I made the dumb mistake of pulling the battery which resulted in a bootlooping soft-brick. I then did an SBF back to 2.3.5 which naturally wiped my flash to Cricket. So I rooted and re-flashed to get my network working again which went perfectly fine. Then I restored my Nandroid and went back to CM7.2....and now my Wi-FI says "Error" and will not even attempt to connect. I figured the Nandroid probably got botched so I restored it again and had the same issue. I tried to reflash CM7.2 and also tried to reflash CM10 and get the "assert failed: run_program (tmp/kernel_check) ==0 (status 7)" error on both. I have tried repeatedly redownloading both zip files and attempted reflash with the same error. Obviously rebooting the phone and trying Wi-Fi fixer do absolutely nothing. I would either like to stay on CM7.2 OR give CM10 another try but cannot flash either zip with the CM7 patched BSR. If I can have the Wi-Fi fixed on CM7.2 then great, if I can be on CM10 with working Wi-Fi even better, but I would like to be able to get this fixed WITHOUT having to do another SBF...flashing it to Cricket is a PITA and I can only do the flash on 2.3.5 since that is the only version that gives the "PC Mode" option for USB connection. Factory Reset is not an issue with me, I just want things working properly. Any and all help is as usual GREATLY appreciated. Thanks in advance.
Err, you couldn't have been on 2.3.5 and CM7 before. That and CM10 are 2.3.4 ROMs. If you sbf'd to 2.3.5 then your only options are stock ROM or eclipse 2.3
Sounds like you need to sbf back to 2.3.4
Sent from my DROID X2 using xda app-developers app
three west said:
Err, you couldn't have been on 2.3.5 and CM7 before. That and CM10 are 2.3.4 ROMs. If you sbf'd to 2.3.5 then your only options are stock ROM or eclipse 2.3
Sounds like you need to sbf back to 2.3.4
Sent from my DROID X2 using xda app-developers app
Click to expand...
Click to collapse
You are correct, they are ROMS that need to be flashed from 2.3.4, but I didn't flash, I restored a Nandroid backup. I started on 2.3.4, flashed CM7, used that for a while, then flashed CM10 over CM7, then did SBF to 2.3.5 and then restored a Nandroid back to my CM7. As I stated above, I can only get my phone onto Cricket from 2.3.5 as that is the only version of android that has the "PC Mode" option when connecting to computer with USB, that is the ONLY connection mode that can be used to network flashing. If I SBF back to 2.3.4 I might be able to flash a new ROM but then I won't be able to do the network flash myself, I will have to take it to cricket which I would prefer not to have to do.
d34thbl00m said:
You are correct, they are ROMS that need to be flashed from 2.3.4, but I didn't flash, I restored a Nandroid backup. I started on 2.3.4, flashed CM7, used that for a while, then flashed CM10 over CM7, then did SBF to 2.3.5 and then restored a Nandroid back to my CM7. As I stated above, I can only get my phone onto Cricket from 2.3.5 as that is the only version of android that has the "PC Mode" option when connecting to computer with USB, that is the ONLY connection mode that can be used to network flashing. If I SBF back to 2.3.4 I might be able to flash a new ROM but then I won't be able to do the network flash myself, I will have to take it to cricket which I would prefer not to have to do.
Click to expand...
Click to collapse
You can not restore a nandroid from one kernel to another without having problems even with wiping. You can try to flash the Mx2 versions they don't ask for the kernel check but you might still have problems on 2.3.5.
appl3mac said:
You can not restore a nandroid from one kernel to another without having problems even with wiping. You can try to flash the Mx2 versions they don't ask for the kernel check but you might still have problems on 2.3.5.
Click to expand...
Click to collapse
Yeah I started to think that that could have been the issue, that it was still running the 2.3.5 kernel. Well I saw no other option so I decided to SBF back to 2.3.4, and it somehow now has the PC Mode option, so I can do the Cricket flash on that now. Weird that it didnt have that option the last time I did the SBF. Guess it should work now, will post a final update once I get the Cricket flash and CM10 reflashed.
Stick with 2.3.4 for Cm7, definitely if that is what your Nandroid is from. 2.3.5 is so limited as to what is developed for it.
tallyforeman said:
Stick with 2.3.4 for Cm7, definitely if that is what your Nandroid is from. 2.3.5 is so limited as to what is developed for it.
Click to expand...
Click to collapse
Yeah I got it all figured out, gonna run CM9. I've reflashed to Cricket so many times by now I can do it in 5 minutes or less lol. Thanks for the input guys.
CM9 is full of bugs.... you sure?
Sent from my DROID RAZR HD using Xparent Cyan Tapatalk 2
GoClifGo05 said:
CM9 is full of bugs.... you sure?
Sent from my DROID RAZR HD using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
Yeah, I've been using it for 2 solid days now and other than a little battery drain and the very occasional random reboot I would say it's running really good. I'm just sick of Gingerbread and after trying CM10 I decided I won't be going that route until a couple more alphas are released.
Related
Hello, my international 3G [850 Mhz UMTS with Claro Dominican Republic] stopped working a few days back. I´ve reflashed to stock, and back to different roms, on the hopes that it will update my baseband version, but not even the Home Base Rom, with an alternate Baseband (i believe) changed it on the phone.
My question is, how do i install a baseband version, or does someone have any baseband sbf or img files for the Photon, to see if it fixes the issue.
Any help would be greatly appreciated, thanks.
Motorola Photon 4G
Unlocked Bootloader, Rooted, Custom CWM
Home Base ROM with Update 4.2
No one?
There isnt a way to download or extract the baseband or modem software from the Photon? It is not on the SUN 198 .sbf.
I wonder the same. I saw people have 03, 05, and 07 basebands. I had all OTAs and then flashed 198_6, but I still got 05, not 07. I recall that I received an error message at BP passthrough (phone disconnected) during 198_6 flashing. Afterward, my system shows 05 baseband and 198_6 build.
Mine says _01.21.07R, which might be updated, but i believe it messed up my UMTS settings or something.
fix thing
I had similar situation. This happened once I flashed the homebase.
How did it start working?
using CMW I wiped all data and without booting to homebase, I activated RSD protocol and flashed stock firmware using RSD lite. After that all work without problems.
I actually tried that, with no luck. It might be that my actual hardware is messed up.
robinrisk said:
Mine says _01.21.07R, which might be updated, but i believe it messed up my UMTS settings or something.
Click to expand...
Click to collapse
That's the baseband that used to work for me!! Can u extract it somehow
I'm sure there's a way to, and flash it via sbf or cwm
Shabbypenguin, minerheart or yay4juggs would know
hope they read this or ill post in dev section
Mine is n01.28.05s.to
I wanna know wat caused the change. The ota, the SBf flash, the pudding plus custom rom (homebase)
Can ppl post there current baseband versions and what they've done to there phones up to date (ota, Roms etc)
Sent from my MB860 using xda premium
---------- Post added at 05:17 AM ---------- Previous post was at 04:23 AM ----------
i flashed the 198_6 sbf again
it is now
N_01.28.07R, and it wont connect to UMTS
still wanna try the one ur on
If you can post in the evs seciton about how to back up your baseband that weould be awesome.
Im a newbie so you might get more responses.
http://forum.xda-developers.com/showthread.php?t=1305008
Sent from my MB855 using xda premium
Dude, there is a guy who´s doing a ROM and is working right now with the baseband versions, he might know. I already asked him but just so you know.
http://forum.xda-developers.com/showthread.php?t=1304881
robinrisk said:
Dude, there is a guy who´s doing a ROM and is working right now with the baseband versions, he might know. I already asked him but just so you know.
http://forum.xda-developers.com/showthread.php?t=1304881
Click to expand...
Click to collapse
I don't know about the basebands, unfortunately. I even have some ISSUES with mine myself. When I call, it initiates and virtually "hangs up" but also continues the call, and forces the phone back into calling mode. /expletive/ing weird.
Yup
sigh
Sent from my Nexus S using xda premium
Tried
Officially tried everything. (BTW, i managed to change baseband versions and did nothing to my phone, i believe we dont want to see that our phones are physically messed up)
Lets see if there is anything left to do.
1. Flashed 198 Stock SBF
2. Flashed 154 Stock SBF
3. Tried Alien Rom
4. Tried Stockbase Rom
5. Tried CM7 Pre-Alpha Rom
6. Restored Nandroid from a completely stock rom but rooted, unlocked adn with CWM.
7. Factory reset (About 25 times but besides deleting data, system and cahche does not do anything.
8. Changed basebands.
Is there anything left to do or is my photon messed up physically?
BTW man, ima do a nandroid backup now that i have the other baseband, and ima upload it on thursday, on my day off, so you can try it on your own photon. Be sure to do a nandroid beforehand, in case anything goes wrong.
robinrisk said:
BTW man, ima do a nandroid backup now that i have the other baseband, and ima upload it on thursday, on my day off, so you can try it on your own photon. Be sure to do a nandroid beforehand, in case anything goes wrong.
Click to expand...
Click to collapse
so th enandroid DOES change the baseband?
i see u said 'changed basebands'
thanks
Nah, never mind. the baseband changed when i flashed the 154 build, but then it chanfed again to the oe that ends in 7. I dont have any idea how that updated.
When I am flashing eclipse for some reason I am getting a abort error for line 294?? I have downloaded the zip file twice and same problem. Any ideas??
Edit. Something is wrong Liberty X3 is showing same thing. failure at line 398 set_perm_recursive 0 0 0755 system
This sucks so bad. I can restore back to my stock 2.3.4 nano backup. Shouldn't that be as good as a fresh start like a sbf? Or will I need to try a sbf to fix what I have going on here? Ah man stock sucks!!
I was able to flash the sd flip flop and battery fix with no issues to the stock 2.3.4 But when I try to flash a rom I get errors.
I would just SBF (no biggie) unless someone with more experience with this issue replies.
X0dus said:
I would just SBF (no biggie) unless someone with more experience with this issue replies.
Click to expand...
Click to collapse
If I dont get a answer I will sbf tomorrow morning. I have a stock back up I always save. I was on Eclipse and also had back up of liberty and eclipse. However I was reading the post about custom roms do not need v6 supercharge. So I deleted my recovery of elipse and liberty and went back to stock. When I went to try and flash the roms I get errors. I can flash other things but not the rom.
I will probably sbf later tonight or first thing in the morning. Weird I swap between roms all the time never had this issue.
So did you try flashing Eclipse and/or Liberty after flashing your stock backup?
X0dus said:
So did you try flashing Eclipse and/or Liberty after flashing your stock backup?
Click to expand...
Click to collapse
Ya I tried both eclipse and liberty and they both get line errors. Hopefully the sbf does it I will have to do it tonight. I am missing eclipse with ics theme.
FIXED... I SBF to stock 2.3.4 and rooted again. Flashed the same Eclipse 1.3 zip and everything is good again. Thanks Xodus for your help!
Travisdroidx2 said:
FIXED... I SBF to stock 2.3.4 and rooted again. Flashed the same Eclipse 1.3 zip and everything is good again. Thanks Xodus for your help!
Click to expand...
Click to collapse
Good deal. np (really didn't do much)
Not the best solution, but fixed nonetheless. I tried to Google those errors and unfortunately this thread was the first to show up. Not much luck with following results given. Say, you wanna add [Solved] to the title? Helps with others with a similar issue..assuming they search and read first.
Sent from my DROID X2 using xda premium
X0dus said:
Good deal. np (really didn't do much)
Not the best solution, but fixed nonetheless. I tried to Google those errors and unfortunately this thread was the first to show up. Not much luck with following results given. Say, you wanna add [Solved] to the title? Helps with others with a similar issue..assuming they search and read first.
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Got it thanks. Sorry for freaking out. I hope this can help someone else.
Still having this issue!!
So after last time I did a sbf I was able to flash Eclipse 1.3 and also Liberty X3 both and was smart enough to get them nano back up saved. Today I wanted to try another rom and had the line error again. So I went ahead and did a sbf again. After that I rooted again and then had a clean start to flash Molten 2.1 It did the same thing again. I am not sure why this is happening but luckily my back up that I saved work still. So I am going back to stock then going back to eclipse. I am puzzled now I thought the fact that I sbf and also wiped data 3 times with cache I would be good to go but not the case. I am getting scared that I will not be able to flash future roms.. I removed solved from the title since I still have the problem even after I sbf this time.
I made it back to my saved eclipse 1.3 but I really wish I knew what was going on.
Quick question. Can I do a nandroid restore after wiping data, cache and dalvik?
If you chose to put it in your external SD card when you made it, yes. wiping the big 3 doesn't wipe the SD card
Sent from my MB870 using XDA App
IDMA.DROID.X2 said:
If you chose to put it in your external SD card when you made it, yes. wiping the big 3 doesn't wipe the SD card
Sent from my MB870 using XDA App
Click to expand...
Click to collapse
So i will be able to go back to my original ROM just as I left it even after wiping the big 3?
Yup! I've got a back ulbof every ROM except MIUI, haven't flashed it yet! Haha
Sent from my MB870 using XDA App
EDIT: Make sure its on the external SD card though. Not sure weather it will be there on the SD card if you put it there then wiped the big 3
IDMA.DROID.X2 said:
Yup! I've got a back ulbof every ROM except MIUI, haven't flashed it yet! Haha
Sent from my MB870 using XDA App
EDIT: Make sure its on the external SD card though. Not sure weather it will be there on the SD card if you put it there then wiped the big 3
Click to expand...
Click to collapse
I have a nandroid on my internal that has endured several data wipes and sbf's. It is a backup of my stock phone before flashing anything. I backed it up in both places just in case.
Sent from my cm7dx2 using XDA App
litetaker said:
So i will be able to go back to my original ROM just as I left it even after wiping the big 3?
Click to expand...
Click to collapse
Well, that depends. If you upgraded to say, Android 2.3.5, then you have a different kernel and the kernel is NOT backed up via Nandroid. So unless you are still on the same android version, then you should SBF back to the base OS version you were on. This was tested extensively about a month or so back and it was determined that a nandroid restore doesn't restore the kernel.
Otherwise, nandroiding back should get you where you were before.
iBolski said:
Well, that depends. If you upgraded to say, Android 2.3.5, then you have a different kernel and the kernel is NOT backed up via Nandroid. So unless you are still on the same android version, then you should SBF back to the base OS version you were on. This was tested extensively about a month or so back and it was determined that a nandroid restore doesn't restore the kernel.
Otherwise, nandroiding back should get you where you were before.
Click to expand...
Click to collapse
Good to know! I missed the tests done, I thought it backed up everything.
Sent from my MB870 using XDA App
iBolski said:
Well, that depends. If you upgraded to say, Android 2.3.5, then you have a different kernel and the kernel is NOT backed up via Nandroid. So unless you are still on the same android version, then you should SBF back to the base OS version you were on. This was tested extensively about a month or so back and it was determined that a nandroid restore doesn't restore the kernel.
Otherwise, nandroiding back should get you where you were before.
Click to expand...
Click to collapse
So if MIUI is saying that it is running Android 4.0.3, and CM7 is Android 2.3.7, then is it not ok to nandroid back to CM7 from MIUI?
jsgraphicart said:
So if MIUI is saying that it is running Android 4.0.3, and CM7 is Android 2.3.7, then is it not ok to nandroid back to CM7 from MIUI?
Click to expand...
Click to collapse
No, it should be fine. 4.0.3 is STILL using the same kernel. 4.0.3 is the OS version, not necessarily the kernel version.
Since the bootloader is still locked, flashing the DX2 MIUI still keeps the 2.3.4 kernel. All that gets replaced are the system files. So, nandroiding back to CM7 (which is what I did) is fine because you are still running the same kernel.
At least, that's how I read it when I researched a little on this and with some other people posting their explanations as well.
The reason you shouldn't flash 2.3.4-based ROMs over 2.3.5 is because the kernel version was changed. Remember, the kernel can ONLY be updated via a Verizon-approved OTA. The 2.3.5 update is not an official release, but it DID come from Motorola servers, so it has the signature in it that the X2 is looking for when the kernel is attempted to be upgraded. Hence, that is why flashing a 2.3.4-based ROM over a 2.3.5 image is not a good thing. Same goes with flashing a 2.3.5 ROM over a 2.3.4 image. It's just not a good idea and could pose problems down the road.
iBolski said:
No, it should be fine. 4.0.3 is STILL using the same kernel. 4.0.3 is the OS version, not necessarily the kernel version.
Since the bootloader is still locked, flashing the DX2 MIUI still keeps the 2.3.4 kernel. All that gets replaced are the system files. So, nandroiding back to CM7 (which is what I did) is fine because you are still running the same kernel.
At least, that's how I read it when I researched a little on this and with some other people posting their explanations as well.
The reason you shouldn't flash 2.3.4-based ROMs over 2.3.5 is because the kernel version was changed. Remember, the kernel can ONLY be updated via a Verizon-approved OTA. The 2.3.5 update is not an official release, but it DID come from Motorola servers, so it has the signature in it that the X2 is looking for when the kernel is attempted to be upgraded. Hence, that is why flashing a 2.3.4-based ROM over a 2.3.5 image is not a good thing. Same goes with flashing a 2.3.5 ROM over a 2.3.4 image. It's just not a good idea and could pose problems down the road.
Click to expand...
Click to collapse
Ok, that makes sense. I figured it would be fine but didnt know the technical details.
I've flashed my 2.3.4 backups over 2.3.5 quite a bit since my cheesecake backup is 2.3.5 and I've never had any issues. Do we really know if the kernel changed? I never really looked at the kernel version on 2.3.5.
Sent from my MB870 using XDA App
T3HBR1AN said:
I've flashed my 2.3.4 backups over 2.3.5 quite a bit since my cheesecake backup is 2.3.5 and I've never had any issues. Do we really know if the kernel changed? I never really looked at the kernel version on 2.3.5.
Sent from my MB870 using XDA App
Click to expand...
Click to collapse
Back in December, I asked the question about nandroiding and if it replaced the kernel. Motcher (and ashclepdia) helped out with this one. Motcher SBF'd to 2.3.4 and then nandroided back to Eclipse 2.0.3 (which is 2.3.5) based and the kernel version came up as 00005 which is the 2.3.4 kernel. So, Nandroiding does NOT replace the kernel.
Here's the posted that he posted about this:
http://forum.xda-developers.com/showpost.php?p=20808392&postcount=20
It may be that the differences are minor enough that it won't cause issues, but if the official 2.3.5 ever comes out, it might be best to always SBF back to 2.3.4 if you have to just to be on the safe side. I guess the moral of the story is, do this at your own risk.
Ok I tried to nandroid back to cm7 from Miui and I got a md5-sum mismatch message, and I wasn't able to go back. Do I need to wiped the big 3 every time I nandroid ?
Sent from my DROID X2 using XDA App
bandit1224 said:
Ok I tried to nandroid back to cm7 from Miui and I got a md5-sum mismatch message, and I wasn't able to go back. Do I need to wiped the big 3 every time I nandroid ?
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
No. That means the md5-sum hash key that was generated after the backup was created isn't matching with your nandroid backup. It means possibly your backup is corrupted.
Wiping the big three has nothing to do with nandroiding.
Uninstall bsr -either cm7 or orig. Then reinstall cm7 bsr. It worked for me On cm7. BTW Be sure not to use any spaces when renaming.
failed restore
So im trying to reload my backup from my sd card. I have made 2 thus far and neither work.
I am on the Rogers network on a i747 with the dlk4 baseband. CWM, rooted, stock rom. When i try to restore it loads a few things (ie. system), and starts loading the DATA portion. Which at this point i get an error message. I reboot it, and my phone gets hung up at the samsung loading screen.
I have tried wiping the big 3 and also under mount and unmount i formated system before restoring as well with no success.
Could it be that my version of CWM is 5.5.0.4.. And, from my understanding I dont think it would be the cause, but maybe because i made the backup after being rooted and flashing cwm
Sykotyk said:
So im trying to reload my backup from my sd card. I have made 2 thus far and neither work.
I am on the Rogers network on a i747 with the dlk4 baseband. CWM, rooted, stock rom. When i try to restore it loads a few things (ie. system), and starts loading the DATA portion. Which at this point i get an error message. I reboot it, and my phone gets hung up at the samsung loading screen.
I have tried wiping the big 3 and also under mount and unmount i formated system before restoring as well with no success.
Could it be that my version of CWM is 5.5.0.4.. And, from my understanding I dont think it would be the cause, but maybe because i made the backup after being rooted and flashing cwm
Click to expand...
Click to collapse
this is a thread for the motorola droid x2.
oops
Lorenzo VonMatterhorn said:
this is a thread for the motorola droid x2.
Click to expand...
Click to collapse
i've been searching threads with search tool....guess i wasn't paying attention.
Cheers
Okay, so I was going to install the new cm9 alpha rom that was released. But every time I try to BSR; superuser denied the permission. Even though I have it set to allow it.
But what I though was weird was that if I powered my phone off. Then plugged it into a charger, that the BSR screen appeared. So I made a nandroid recovery of my 2.3.5 OS and then tried to flash cm9. But then it started to give me errors. So I then was gonna just recover the nandroid backup since I factory reset and clear cache. but then it froze trying to recover.
Then I though that I should just power back on my phone then try it again. So I did that and now the BSR screen won't appear it just shows the motorola logo and stays there. HELP!!
I think we will need clarification of your abbreviations before we can help you. Do you mean, SBF or BSR. SBF means you use RSDLite to re-flash your phone to a stock state, and BSR is your Boot Strap Recovery. Unless I'm missing something.
Sent from my DROID X2 using XDA
BSR sorry...
Have you tried holding down the volume button when you power up, plugged into the wall? That should get you into Android Recovery. I believe you may see a lil Droid with a triangle. Then press both volume up and down at the same time. Your menu should appear.
The first problem I saw when reading the OP was that you need to be on 2.3.4 to flash CM9.
jsgraphicart said:
The first problem I saw when reading the OP was that you need to be on 2.3.4 to flash CM9.
Click to expand...
Click to collapse
Totally... right...
You will throw so many errors running 2.3.5 kernal ( which only goes back to 2.3.4 with an sbf)
Sent from my MB870 using Tapatalk 2
6Flip9 said:
Totally... right...
You will throw so many errors running 2.3.5 kernal ( which only goes back to 2.3.4 with an sbf)
Sent from my MB870 using Tapatalk 2
Click to expand...
Click to collapse
Yeah i sbf back to 2.3.4 and had to re-root my phone and start all over. So everything is working fine. I think the problem was that I updated to 2.3.5 and it unrooted me but still had the superuser.apk installed but not let me have su permission. eather way I fixed it.
Since the last time I flashed CM7, RSD (any version) with any SBF file doesn't wipe my phone the way it used to. It's gotten to the point I can no longer flash custom ROMs. If I don't wipe data/cache first, it will flash a new SBF yet leave the apps that were on it before hand. And when I try to flash a custom ROM, I get an error every time. Did I mess up something down in the locked areas that can never be fixed? Is there another way to wipe the phone to a more original or basic point? Right now I'm completely wiping the int and ext sd-cards, wiping data/cache/dalvik, SBFing to 2.2.2, and OTAing back up to see what happens, though I'm doubting it will help.
edit: Didn't work. Still can't flash a custom ROM. I can run rooted stock 2.3.5 though, guess that's what I'm stuck with. Better than nothing.
Performing an SBF does not wipe any user data from the phone. Wipe the phone using the stock recovery before performing the SBF. There are many threads on here on how to SBF, root, and install your favorite ROM.
RyanThaDude said:
Performing an SBF does not wipe any user data from the phone. Wipe the phone using the stock recovery before performing the SBF. There are many threads on here on how to SBF, root, and install your favorite ROM.
Click to expand...
Click to collapse
It doesn't matter if I wipe everything or not, I still can't flash a custom ROM. Get an error every time, and have to SBF to get it bootable again. I had weird issues the first time I ran CM7 and tried to SBF back to stock. Took multiple battery pulls and random button pushing while rebooting before I could get it back into RSD mode. This last time let me SBF back fine, but I get the PASS result instead of the REBOOT PHONE MANUALLY now and can't flash anything.
Scur827 said:
It doesn't matter if I wipe everything or not, I still can't flash a custom ROM. Get an error every time, and have to SBF to get it bootable again. I had weird issues the first time I ran CM7 and tried to SBF back to stock. Took multiple battery pulls and random button pushing while rebooting before I could get it back into RSD mode. This last time let me SBF back fine, but I get the PASS result instead of the REBOOT PHONE MANUALLY now and can't flash anything.
Click to expand...
Click to collapse
Try this a files sometimes corrupt.
Download all new. Perform the sbf, while the phone reboots do the volume down power button thing to get into Android Recovery. Once there wipe data and cache....
I have about 10 cables in my house...only two or three work for flashing and such...try a different cable....
DROID DOES, Apple did...like I forgot when
Pixelation said:
Try this a files sometimes corrupt.
Download all new. Perform the sbf, while the phone reboots do the volume down power button thing to get into Android Recovery. Once there wipe data and cache....
I have about 10 cables in my house...only two or three work for flashing and such...try a different cable....
DROID DOES, Apple did...like I forgot when
Click to expand...
Click to collapse
I have a couple good cables that always work, tried them both. Wiped data and cache on SBF reboot, too. Rooted with One click and Pete's both. So far, nothing works.
are you sure, sbf is flashing correct?
try different version like 2.2.3 or 2.3.5
and check system info after to verify
then update.zip or flash 2.3.4 sbf
or try ezsbf to flash and/or root
Sent from my MB870 using xda premium
i've seen usb cables work with one device and not another, can be hard to tell
Sent from my MB870 using xda premium
sd_shadow said:
are you sure, sbf is flashing correct?
try different version like 2.2.3 or 2.3.5
and check system info after to verify
then update.zip or flash 2.3.4 sbf
or try ezsbf to flash and/or root
Sent from my MB870 using xda premium
Click to expand...
Click to collapse
I've tried 2.2.2, 2.3.3, and 2.3.4 all, then updated. I've tried 3 different versions of RSD. Exact same result. Haven't heard of ezsbf though, I'll check it out.
http://www.droidxforums.com/forum/droid-x2-hacks/41697-tool-ezsbf-dx2.html
it's an iso file you burn to cd or thumb drive, reboots pc to a Linux os
with options to flash sbf and root with zergrush
works for some, when rsd lite or rooting failed
Sent from my MB870 using xda premium
... Have you thought that maybe the recovery your using is corrupted? Download that apk again (the plain one not the patched cm7/9 version) and give that
Sent from my MB870 using xda app-developers app
Scur827 said:
Since the last time I flashed CM7, RSD (any version) with any SBF file doesn't wipe my phone the way it used to. It's gotten to the point I can no longer flash custom ROMs. If I don't wipe data/cache first, it will flash a new SBF yet leave the apps that were on it before hand. And when I try to flash a custom ROM, I get an error every time. Did I mess up something down in the locked areas that can never be fixed? Is there another way to wipe the phone to a more original or basic point? Right now I'm completely wiping the int and ext sd-cards, wiping data/cache/dalvik, SBFing to 2.2.2, and OTAing back up to see what happens, though I'm doubting it will help.
edit: Didn't work. Still can't flash a custom ROM. I can run rooted stock 2.3.5 though, guess that's what I'm stuck with. Better than nothing.
Click to expand...
Click to collapse
The reason why you can't flash custom ROMs such as CM7 or CM9 is that you keep going to 2.3.5 or maybe even trying on 2.2.2 or 2.3.3. I have a check to prevent you from using any version besides 2.3.4. Restoring a nandroid won't cut it either. You must SBF back to 2.3.4, wipe data/cache, root (using zergRush or Pete's Root Tools), install the unpatched BSR, and flash CM7 or CM9.
As for why your apps show up still after an SBF, like you said, you didn't wipe data/cache and the apps are stored in the data directory on your phone. An SBF does not wipe data or cache.
LordRalh3 said:
... Have you thought that maybe the recovery your using is corrupted? Download that apk again (the plain one not the patched cm7/9 version) and give that
Sent from my MB870 using xda app-developers app
Click to expand...
Click to collapse
That's the only thing I haven't tried I think, I'll give it a try. Good idea.
Droid X2 > Eclipse 2.2.1 > Tapatalk
dragonzkiller said:
The reason why you can't flash custom ROMs such as CM7 or CM9 is that you keep going to 2.3.5 or maybe even trying on 2.2.2 or 2.3.3. I have a check to prevent you from using any version besides 2.3.4. Restoring a nandroid won't cut it either. You must SBF back to 2.3.4, wipe data/cache, root (using zergRush or Pete's Root Tools), install the unpatched BSR, and flash CM7 or CM9.
As for why your apps show up still after an SBF, like you said, you didn't wipe data/cache and the apps are stored in the data directory on your phone. An SBF does not wipe data or cache.
Click to expand...
Click to collapse
I haven't tried to flash CM7 or CM9 since the last time I came off of it. I really like having the camcorder around my daughter. That was my only problem with either. they worked great when they were on. I've mostly been trying to get Eclipse back on.
I think that CM7 had something to do with my problem, though. I've flashed it twice before. The first time was hell coming back to stock, I thought my phone was bricked for about an hour. It took multiple boot attempts, battery pulls, and button mashing before I finally could get back to RSD mode to flash a SBF.
Everything seemed fine for a couple months, until I tried CM7 once again. When I tried to come back off of it the second time, RSD gave it a PASS at the end instead of hanging on REBOOT PHONE MANUALLY like it always did before, and has every time since then (was hit and miss before). Now I can still flash a SBF and update an OTA (but only after doing a *228 to download and install it, can't flash an OTA file from recovery), but if I try to flash any ROM (and I've tried a half dozen of them) while using any root method, I get an error while flashing, and have to wipe everything possible to be able to SBF back to stock. I've tried flashing ROMs at least 20 times over the past few days. Either something got messed up, somewhere in an area that both RSD and recovery don't touch, or it's a hardware issue. That's the only thing I can come up with.
Now, I don't believe it's CM7's fault. At all. There are just too many people who enjoy. I simply believe there was something odd or wrong about my phone.
Its like you know the words but not which ones go with what things... Flashing and sbfing are two completly different things, and there is no button mashing involved pull your battery one time, hold power and volume up at the same time, that puts you in rsd mode to sbf, to get over a bootloop just go to android recovery (power button and volume down then cycle to recovery) you don't flash roms in this recovery just wipe data/cache. If you grabbed the right sbf file (check your android version in about phone should be 2.3.4 ) you can root with motorola one click and install the bootstrap recovery program NOT THE CM7 VERSION, Plug phone into the wall bsr WIPE DATA/CACHE and flash cm7, its a standard process and your phone is not special
Sent from my MB870 using xda app-developers app
LordRalh3 said:
Its like you know the words but not which ones go with what things... Flashing and sbfing are two completly different things, and there is no button mashing involved pull your battery one time, hold power and volume up at the same time, that puts you in rsd mode to sbf, to get over a bootloop just go to android recovery (power button and volume down then cycle to recovery) you don't flash roms in this recovery just wipe data/cache. If you grabbed the right sbf file (check your android version in about phone should be 2.3.4 ) you can root with motorola one click and install the bootstrap recovery program NOT THE CM7 VERSION, Plug phone into the wall bsr WIPE DATA/CACHE and flash cm7, its a standard process and your phone is not special
Sent from my MB870 using xda app-developers app
Click to expand...
Click to collapse
Fine, I don't FLASH an SBF file. But I've flashed ROMs on the X2 alone at least a hundred times, I know what's what. I know the difference between stock recovery and BSR. I know the difference between BSR and the CM7 version, and when to switch over. I know what wiping data does, what wiping cache does, what the Dalvek cache is and what wiping it does, what fixing permissions really does.
When I say I couldn't SBF out of CM7, I mean after flashing CM7 the first time, I ran RSD Lite and used SBF 2.3.4-380 to get back to stock. RSD gave me an error, and stopped. I couldn't reboot the phone, it just hung up on the red M. Holding vol down+power hung up on the red M. Holding vol up+power hung up on the red M. So I would pull the battery and try it again. And again. And again. No buttons, every button. Letting it sit on the red M for 30 mins. Eventually I got a weird RSD message at the top (and no, not the vol up+power RSD message), different from the others, and I could SBF again. I still got an error, but could vol down+power into the regular menus, so once I got into the standard RSD mode the next SBF went fine, except I got a pass at the end instead of having RSD hang up on the reboot phone manually message it always got before. And since then I don't get the boot loops after it reboots like it used to, though the pass message is hit and miss. I've SBFed dozens and dozens of times since then, used fresh downloads and different versions of everything, and I've never seen another boot loop afterwards. Something, somewhere, is definitively different. I have a few good cables that have always worked, and I've switched them out. I've wiped and formatted everything possible on the phone several times. It's just not the same as it was before CM7. And after coming off of CM7 the second time, I've gotten a pass at the end of the SBF every single time. Another new thing after a CM7 flash.
Like I said, I don't think it's a CM7 issue, I just think there is something wrong with my phone on a level I can't touch, and it really didn't like CM7. It isn't operator error. Give me any instructions you like for getting me on, say, Molten (since it's 2.3.4-380 and the simplest to flash). I'll follow them to the T, but it won't work. I can't *228 anymore, so I can't download a system update, and I get a file signature error if I try to flash an update from stock recovery. I'm stuck on stock 2.2.2, 2.3.3, 2.3.4, or 2.3.5. I can still root them using any method, except 2.3.5 since it requires carrying root over with OTA Rootkeeper from 2.3.4.
Sorry if i came off too negatively btw its just that this phone is SOOOOO close to indestructible programming wise... Your next step is to burn ezsbf and head to someone elses computer and try that
Sent from my MB870 using xda app-developers app
LordRalh3 said:
Sorry if i came off too negatively btw its just that this phone is SOOOOO close to indestructible programming wise... Your next step is to burn ezsbf and head to someone elses computer and try that
Sent from my MB870 using xda app-developers app
Click to expand...
Click to collapse
Me too, just woke up.
I tried ezsbf yesterday on a laptop, no change. Tried a fresh copy of BSR from a different source this morning, no luck there either. I'm completely out of ideas now, there's nothing I haven't tried alternatives to. But I have a fully functional phone rooted on 2.3.4, and sometime in the near future I'll be getting something new and shiny, so it could be worse. When I do get a new one, this one will be perfect to have GrooVe IP on it for my 8 yr. old daughter, and the big screen is nice for games.
Droid X2 > Eclipse 2.2.1 > Tapatalk
Scur, I uploaded a nandroid of eclipse 2.3
don't know if that will work any better
but who knows, it just might work for you
http://www.mediafire.com/?7b71gn1j3r2dwrj
edit: if you problem is kernel related, it's not going help
also have you been checking the kernel,
System version:
1.3.418
Android version:
2.3.5
Baseband version:
N_03.13.31P
Kernel version:
[email protected]#2
sd_shadow said:
Scur, I uploaded a nandroid of eclipse 2.3
don't know if that will work any better
but who knows, it just might work for you
http://www.mediafire.com/?7b71gn1j3r2dwrj
edit: if you problem is kernel related, it's not going help
also have you been checking the kernel,
System version:
1.3.418
Android version:
2.3.5
Baseband version:
N_03.13.31P
Kernel version:
[email protected]#2
Click to expand...
Click to collapse
Here's where I am now. With a method to root 2.3.5, I can SBF it and root. It will let me flash Eclipse 2.3, but will lose root when it flashes. So I can get Eclipse 2.3, but it's unrooted and I haven't found a way to root it after flashing yet. Odd there. I have a couple abd tips to try to get it going, but I'm going to try your nandroid first. Much thanks.
Droid X2 > Rooted 2.3.5 > Tapatalk
The nandroid worked like a charm, I thank you good sir.
Droid X2 > Eclipse 2.3 > Tapatalk