Related
Hi guys. I am having a bit of an issue here.
I just got my DX a couple days ago. I have a buddy that has been into modding with his D1 for a while, and he recently got a Fascinate. He convinced me to try doing some stuff with my phone...
I rooted my phone successfully. I then wanted to install the DX Invertnito theme. It said I needed to Deadex my phone. I got the xultimate 2.2.2 deodex pack and successfully deodexed my phone. I then downloaded the zip file for the Invertnito theme. I put the zip file on my phones sd card as stated in the instructions. I then downloaded Koush's DX Bootstrapper from the market and Clockwork Rom manager. Installing the theme automatically through the rom manager didnt work, but the phone did boot normally nonetheless. I then decided to go directly through the Bootstrapper app [clicked the recovery mode right on the menu out of two options]. The phone instantly shut down, then booted into the clockworkmod recovery menu. I followed the instructions given to install the Invertnito from the .zip file on the zd card. I clicked install on that file. Everything seemed to work fine to this point. Installation successful.
Unfortunately, now the phone will not boot at all.... It loads the Motorola M logo and stays there. I've tried waiting for 30 min on the logo and it just doesn't move. If I remove/replace the battery, the phone will then load the clockworkmod recovery menu again just like it did after it shutdown from running the first time. I've tried clearing cache, restarting the phone, replacing the battery 20 times. Always stuck on boot M screen. Sometimes it will go the the Motorola bootloader screen, but when i click reboot system, it just gets stuck on the M logo.
Any help would be appreciated here. I'm hoping I haven't bricked my phone somehow. I didn't expect this as I can't find anyone else who installed this same theme have the same problem. Is there something I can do to get it back to normal? Is it possible to somehow get my OS back to clean stock and go from there?
Thanks
Did you do a nandroid backup before loading the theme?
Unfortunately, no. I just read of someone having a similar issue though. Said he used RSD Lite 4.8 and an SBF and he was able to get back into his phone. Not sure how to dgo about any of that though.
Retriraver said:
Unfortunately, no. I just read of someone having a similar issue though. Said he used RSD Lite 4.8 and an SBF and he was able to get back into his phone. Not sure how to dgo about any of that though.
Click to expand...
Click to collapse
go over to mydroidworld and look in the droid x mods section. It has rdslite and sbf for froyo
rcerulli said:
go over to mydroidworld and look in the droid x mods section. It has rdslite and sbf for froyo
Click to expand...
Click to collapse
Thanks, I will go check that out and see if I can get this fixed.
be carefull i am in the same situation like you and flash the sbf file from THB team i now i think my phone is reall ****ed up bricke nooooooo
trying the 2.1 sbf file i hope its works
well first time failed and then was stuck in bootloader saying code corrupt damn i was so mad... so i tried again the 2.1 sbf adn voila droid x alive again ufffff
i will keep the ota version **** the custom rom relly i dont need it hehehehehe
Also, how can i run the RSDlite and connect it to my phone while my phone is stuck on the M screen?
Retriraver said:
Also, how can i run the RSDlite and connect it to my phone while my phone is stuck on the M screen?
Click to expand...
Click to collapse
hold volume down and camera button while you press power button it will then say ready to program.
if you did the OTA 2.2 DO NOT USE THE 2.1 SBF!!!!
if your on the leaked 2.2 and you try the 2.2 sbf but get errors due the 2.1, if you get a boot loop after that you need to go into the stock recovery and factory reset, hold home button and
ive been there as well. pull out an adapter for ur memory card or get another phone and pop ur memorycard in it and dl the file inside this link.
http://forum.xda-developers.com/showthread.php?t=794007
scroll down to option "2"
2. Update.zip - File
1.Wipe and reboot.
the "File" will be clickable and will send u to a link to dl. place it on the root of memory card(doesnt really matter where as long as its on the memory card) and click
install update.zip(if its in root and named update.zip) or u can go click choose .zip file or whatever and go look for it. hope it works for u. let us know. ill be waiting to hear ur respnse.
djtoonjr said:
ive been there as well. pull out an adapter for ur memory card or get another phone and pop ur memorycard in it and dl the file inside this link.
http://forum.xda-developers.com/showthread.php?t=794007
scroll down to option "2"
2. Update.zip - File
1.Wipe and reboot.
the "File" will be clickable and will send u to a link to dl. place it on the root of memory card(doesnt really matter where as long as its on the memory card) and click
install update.zip(if its in root and named update.zip) or u can go click choose .zip file or whatever and go look for it. hope it works for u. let us know. ill be waiting to hear ur respnse.
Click to expand...
Click to collapse
This worked for me...thanks mate!!!!
First off, I am very familiar with Custom Roms and Never had this problem before.
I had to use the 2.3.13 SBF bc I was in a boot loop from a theme. I am rooted again using rageagainstthecage and can access the ClockworkMod recovery. I have tried multiple times to install 2.3.15 deodexed from the TBH app with no success. ClockworkMod says the install was successful but under system info it states it is 2.3.13. I know that it is 2.3.13 odexed bc Tranquility causes a boot loop. Backup and Restore work fine but not zip files. Does anyone know why it will not install?
I think I just experienced the same thing. Had to use the same sbf last night. This morning I tried to install zapx and seems like nothing happened and I was back at stock. Also I cant get back into clockwork recovery.
SysAdmNj said:
I think I just experienced the same thing. Had to use the same sbf last night. This morning I tried to install zapx and seems like nothing happened and I was back at stock. Also I cant get back into clockwork recovery.
Click to expand...
Click to collapse
You probably need to bootstrap the system again using the koush's app, to get back into recovery.
I installed ZapX but I had network issues with the market. So i reverted using a backup.
I was able to get clockwork back and install a different rom and the rom took this time. Rubix .5 to be exact.
good news- full 2.2 sbf is available now. there are links in x development.
thanks but i think they removed the thread ?
SysAdmNj said:
thanks but i think they removed the thread ?
Click to expand...
Click to collapse
Yeah- they did. there are other android forums with links still. Or search for...
VRZ_MB810_2.3.15_1FF_01.sbf
on megaupload or hot file or one of those sites.
I rooted my nexus one using one click root, installed Rom Manager, flashed the clockworks mod recovery. Then i went to the CM 7 nightlies and got the latest one on the list it was #9 i believe. Everything went fine, it said it got an update, so i click download it was #37, i click on make a backup and didn't check the option that wipes.
Now it wouldn't boot. It gets to the X while booting and then just shuts off. I tried going into fast boot and click on recovery and it show the X again and then shuts off.
Could i some how connect it to my pc and wipe the whole thing so i could start fresh?
Yes: http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
/facepalm
if only you unlocked the bootloader... so easy...
Still can unlock the bootloader...
Sent from my Nexus One using XDA App
ok so i restored using passimg method.
Rooted again, but this time rom manager wont do anything it just keeps saying an error occurred while attempting to run privileged commands! i went into Superuser, and rom manager is not listed under Apps. Is there a way i could manually add apps to Superuser?
key3thermal said:
ok so i restored using passimg method.
Rooted again, but this time rom manager wont do anything it just keeps saying an error occurred while attempting to run privileged commands! i went into Superuser, and rom manager is not listed under Apps. Is there a way i could manually add apps to Superuser?
Click to expand...
Click to collapse
got it to add permissions again, had to remove fix_permissions.log from my sd card, and then click on fix permissions in rom manager again.
Going back to CM 6.1.1 till 7 is stable again i guess.
Now everything seems to be working great. I flashed gapps 20101114 in hopes that it would update to the new market but no luck. Is there any other way to update to the new market? i also updated maps, that didn't help either.
I have the same issue as the OP. My N1 currently will not boot passed the "X" screen. I have a locked bootloader, so I tried using the PASSIMG.zip method from the link that was provided. I downloaded the FRG33 stock build from http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Roms. After the PASSIMG.zip was checked, I get an error stating "Main Version is older!" and the update failed. Any ideas how to get past this point?
key3thermal said:
Now everything seems to be working great. I flashed gapps 20101114 in hopes that it would update to the new market but no luck. Is there any other way to update to the new market? i also updated maps, that didn't help either.
Click to expand...
Click to collapse
With gapps 20101114 installed, try flashing Pendo blue market. It worked on my phone.
This post is only for discussing all issues regarding the use of the Bonsai roms. We can talk here about any version from 1.0.0 to x.x.x
Due to some political issues please do not post any links to the Bonsai website! This thread is just for us users and don't expect the developers of Bonsai to ever visit here.
One last thing >
nor
Yes this try to keep this thread open.
Sent From My Evo Killer!
So is there a way to get a 600mhz step in the kernal for bonsai 4.0 last i heard he was going t put it in back in 3.0.1 but still not there. Or is there an easy way to included it in the kernal page file or something that set cpu uses? Also is there a way to get the voodoo color fix or a tweak that works that will make the brightness lower at the lowest setting for 4.0 becase the brightness on this screen is way to brght at night time. I used to have a tweak like this in syndicate rom for 2.1 it was great. Any info would be great thanks guys.
Sent from my SPH-D700 using XDA App
I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force
forcelite said:
I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force
Click to expand...
Click to collapse
Were you using CWM 3.0.0.6 or 3.0.0.5 ?
Sent from my SPH-D700 using Tapatalk
Good question as i was just going to as a question about EXT4 and CW.
The rom manger is version 3.0.1.4
however the CW mod flashed is version 3.0.2.4
It only has 2 to choose from in rom manger, 3.0.2.4 or an older 3.0.1.4
Not sure were people are getting these other versions from.
Force
PS I booted into CW and saw it was v2.5.1.0
am I way off?
abrcrmdl23 said:
So is there a way to get a 600mhz step in the kernal for bonsai 4.0 last i heard he was going t put it in back in 3.0.1 but still not there. Or is there an easy way to included it in the kernal page file or something that set cpu uses? Also is there a way to get the voodoo color fix or a tweak that works that will make the brightness lower at the lowest setting for 4.0 becase the brightness on this screen is way to brght at night time. I used to have a tweak like this in syndicate rom for 2.1 it was great. Any info would be great thanks guys.
Click to expand...
Click to collapse
I can't remember what stepping is on the kernel as we have been beta testing 4.0.1 and have been mainly dealing with a new setCPU governor called interactive. Were also still working on the other governor called smartass as well. I think that the stepping goes directly from 400 to 800, but we are always looking to go faster and with better battery life. I'll bug Randy and Mammon about it.
The sound will be Voodoo version 7, but I don't think the Voodoo color fix is going to make it into 4.0.1. Sorry, but we can't do everything...at least not all at the same time.
forcelite said:
I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force
Click to expand...
Click to collapse
Did I see a similar post on the Bonsai website earlier today? I just want to verify that you were using CWM 3.0.0.6 as anything else will cause problems like that. Also when you get to these kinds of problems you should attempt a second flash of Bonsai before going to the trouble of a ODIN job. A second flash seems to fix a whole variety of odd kind of problems.
As you can imagine with all the beta testing I do I'm always finding ways to corrupt my phone. Some days I have managed to bork it 3-5 times.
I decided to test out today a 4.0.1 install directly from DI18 > CWM 3.0.0.6 > Bonsai 4.0.1 full rom. It went great with no problems at all and running just fine, so far
I think that is my problem, I am using a the CW that came with the one click unroot.
So I guess I need to do this, even if I am already rooted?
http://forum.xda-developers.com/showthread.php?t=897612&highlight=EXT4
PS
I booted into CW and saw it was v2.5.1.0
bluetooth
I could not get bonsai 3.0.1 or 4.0.0 to pair with my bluetooth headset. Tried pairing on an epic with acs 1.1 and paired fine. Anyone else have a pairing problem?
forcelite said:
Good question as i was just going to as a question about EXT4 and CW.
The rom manger is version 3.0.1.4
however the CW mod flashed is version 3.0.2.4
It only has 2 to choose from in rom manger, 3.0.2.4 or an older 3.0.1.4
Not sure were people are getting these other versions from.
Force
PS I booted into CW and saw it was v2.5.1.0
am I way off?
Click to expand...
Click to collapse
Do not use Rom Manager to be installing the beta CWM files. The correct way is with one of the 1 step CWM tools in the development forum. 3.0.2.4 is half-finished and is very difficult even to navigate through the various menu's. I know this because I tried out that CWM version for some grins one day. It will majorly screw your Epic if your not extremely careful. When DI18 was prevalent Rom Manager worked great to root your phone. When we started the move into the Froyo roms Rom Manager quit working and that is why the 1 click then became more prevalent.
Just follow the directions posted all over the place and Bonsai will install just fine and you will be a happy camper.
I am installing it now after updating to CW3 (from CW2.5) . I think it will come out fine now, I am an idiot and didn't realize the original one click root installed an older version of CW.
Thx All,
Force
forcelite said:
I think that is my problem, I am using a the CW that came with the one click unroot.
So I guess I need to do this, even if I am already rooted?
http://forum.xda-developers.com/showthread.php?t=897612&highlight=EXT4
PS
I booted into CW and saw it was v2.5.1.0
Click to expand...
Click to collapse
The linked one is the correct one for Bonsai version 4.x.x.
olddocwhite said:
I could not get bonsai 3.0.1 or 4.0.0 to pair with my bluetooth headset. Tried pairing on an epic with acs 1.1 and paired fine. Anyone else have a pairing problem?
Click to expand...
Click to collapse
Some people do and some don't I do know that Randy has instituted quite a few bluetooth linux upgrades into 4.0.1 rom. Some people are able to clear the data, but the problem usually reappears. Mattalica76 has the link to a more permanent fix to this problem, give him a PM.
Duplicate... Sorry
forcelite said:
I am installing it now after updating to CW3 (from CW2.5) . I think it will come out fine now, I am an idiot and didn't realize the original one click root installed an older version of CW.
Click to expand...
Click to collapse
Don't beat yourself up as we all have been there. It's a process of learning new skills and a new language. Give yourself a pat on the back for getting through this when 98% of the world would have said screw it or not even tried at all.
Actually it didnt boot this time either, it installed the firs ttime fine, then kept booting after samsung in a loop,
So I went into CW3 and tried to flash bonsai 4.0.01 again and it gave me this error. It is long, however I shortened it, I have the whole error photo copied)
Finding package
Opening package
Install update
Assert failed getprop (“ro.product.device)”)
Sph-700
E:error in /SDcard/bonsai……….
(status 7)
Installation aborted
Top Nurse said:
Don't beat yourself up as we all have been there. It's a process of learning new skills and a new language. Give yourself a pat on the back for getting through this when 98% of the world would have said screw it or not even tried at all.
Click to expand...
Click to collapse
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.
forcelite said:
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.
Click to expand...
Click to collapse
CWM3 will convert your filesystem to ext4 the first time you boot into it. It won't touch the sdcard so that won't be converted. After CWM is finished with the conversion, do not reboot the phone, you will then flash Bonsai.
forcelite said:
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.
Click to expand...
Click to collapse
After flashing the boot script of cwm 3.0.0.6 you then have to power off. Then hold down the camera button, vol down, and power keys at the same time and the EXT4 script will automatically start to format your system. Please keep in mind that it is not formatting the SD card, but only the read only memory of the phone.
After you finished a few beers it will be done and will drop you back to cwm. Do not reboot, but flash bonsai. After bonsai is finished then reboot.
Sent from Bonsai 7.0.3
Ok watched video and liked it. Next running the current (as of last nite) Cm7. Would like to get the camera working have read some of the threads. Best I can figure its not happening. Also having some problem viewing youtube videos. Is there a rom that solves these problems or should i go back to some form of mod gingerbread. Or what?
I believe you are using the official CyanogenMod nightlies, correct?
The official nightlies don't incorporate the fixes for video and other media out of the box.
You could install the fixes, but you will have to Google around and find them, then install the zip in
I recommend using the unofficial CyanogenMod nightlies over in the Rootzwiki Droid X Developer Forum.
It supports all the fixes plus 720p video playback, as well as other fixes.
If you're interested find the thread and follow the instructions given.
Sent from my Transformer TF101 using XDA App
http://rootzwiki.com/topic/10191-updated-info-on-revnumbers-cm4dx-gb/
There is the thread on RevNumbers.
And I agree that those are the better bet for CM7.
Since you appear to be on official...
You're not on the correct kernel to flash RevNumbers nightlies.
Make sure you are (I don't think you are) on .602/.605 system version.
Follow the usual procedure to back up your applications with Titanium Backup and all that good stuff...
Then SBF to .602
http://rootzwiki.com/topic/331-guide-flashing-droid-x-sbf/
My signature has a more thurough walkthrough of the actual backing up/re-rooting/flashing procedure if you need it.
Definitely suggest going to the gingerbread based cm7 on DX. There's two different releases of it just compiled on 01/07/2012 and instructions for applying any fixes are in the OP. The only one necessary for certain is the camera fix. If you need help, I can give you a hand, but not FAST, as I'm at work during regular business hours M-F EST
base BP_C_01.09.07P
kernel 2.6.32.9-g55626e1 [email protected]#1
mod cyanogenmod-7-11162011-nightly-droidx
build cyanogen_shadow-eng 2.3.7 gingerbread eng.buildbot.20111116.084404 test-keys
Ok so you folks are saying that i loaded the nightly and need to get the full os before the nightly ok. while i'm in the is there anything that can be done about under volting be low 300 to save battery. Do i need a updated radio or kernel?
speops38 said:
base BP_C_01.09.07P
kernel 2.6.32.9-g55626e1 [email protected]#1
mod cyanogenmod-7-11162011-nightly-droidx
build cyanogen_shadow-eng 2.3.7 gingerbread eng.buildbot.20111116.084404 test-keys
Ok so you folks are saying that i loaded the nightly and need to get the full os before the nightly ok. while i'm in the is there anything that can be done about under volting be low 300 to save battery. Do i need a updated radio or kernel?
Click to expand...
Click to collapse
Kernel is the problem...but we can't manually update our kernels.
Do a nandroid (just in case) and titanium backup.
Then sbf to .602. This will update your kernel for you (and is the best [only outside of certain update.zips that rom manager provides] method).
Root using the method detailed in my sig.
And flash the rom.
Ok sbf too .602 but having problems rooting tryed pete's tool but it just sits there. if i reboot my computer it says to connect my phone then just sits there. tryed z4mod 1.3.0 it keeps force close. Any ideals ? Also ever time i plug phone in to computer it trying to open window for verizon backup page.
speops38 said:
Ok sbf too .602 but having problems rooting tryed pete's tool but it just sits there. if i reboot my computer it says to connect my phone then just sits there. tryed z4mod 1.3.0 it keeps force close. Any ideals ? Also ever time i plug phone in to computer it trying to open window for verizon backup page.
Click to expand...
Click to collapse
You make sure USB Debugging was enabled?
Yes it was in and used same port for sbf. ? When using rs and it boots phone it shows 100% on 1 column but the next 1 says in progress. How long should I allow this to care on before unplugging it. Shave sbf 2 because the phone app wouldn't let me call out. It would show contact and green phone and click when you touched it but nothing happened.
Ok here where we are at.
1) went in and checked the debugging and allow unknow source (nobody said anything about this but tryed it at this point). Used moto 5.4.0
2) I have sbf .602 using rsdlite 5.4.4 (left the cable in the same port for the rest of this).
3) wiped data using the power & home button to get to the bios menu.
4) tryed to boot with pete's tool v1.07 ( it just sat there waiting for the phone to be hooked up)
5) tryed just for fun Z4mod 1.3.0
6) Read some more tryed the Droid 3 easy root v7 it ran half to night sitting there waiting for the phone to be hooked up.
So what am I missing??????
speops38 said:
Ok here where we are at.
1) went in and checked the debugging and allow unknow source (nobody said anything about this but tryed it at this point). Used moto 5.4.0
2) I have sbf .602 using rsdlite 5.4.4 (left the cable in the same port for the rest of this).
3) wiped data using the power & home button to get to the bios menu.
4) tryed to boot with pete's tool v1.07 ( it just sat there waiting for the phone to be hooked up)
5) tryed just for fun Z4mod 1.3.0
6) Read some more tryed the Droid 3 easy root v7 it ran half to night sitting there waiting for the phone to be hooked up.
So what am I missing??????
Click to expand...
Click to collapse
After you SBF you must recheck USB Debugging.
Sent from my Transformer TF101 using XDA App
I have checked a number times!!!! Also how well does factory wipe clean these because this phone was rooted before. What about the dalvik memory?
speops38 said:
I have checked a number times!!!! Also how well does factory wipe clean these because this phone was rooted before. What about the dalvik memory?
Click to expand...
Click to collapse
Try using a different USB port or a different computer. Also, try reinstalling or updating your moto drivers.
A data wipe won't remove root, but SBFing will. It's always safe and recommended to wipe the dalvik cache.
Sent from my Transformer TF101 using XDA App
Planing on trying a different computer on Saturday.
New problem!!!!
1) got a 64bit windows laptop loaded moto usb driver
2) booted computer and checked phone for usb debugging on
3) down loaded pete's one step root
4) unzipped and ran program it said it was looking for phone plugged it in
5) pete's tool took over and rooted .602
6) went into market and got droid2 paid ran it
7) wiped data and wipe dalvik
8) loaded cm7 154 and it said something about wrong kernel.
9) rebooted
Now it will not let me back into clockwork.
10) try droid X bootloader try going though rom manger
no luck it goes blank but the screen is still some what lite.
Help!!
speops38 said:
New problem!!!!
1) got a 64bit windows laptop loaded moto usb driver
2) booted computer and checked phone for usb debugging on
3) down loaded pete's one step root
4) unzipped and ran program it said it was looking for phone plugged it in
5) pete's tool took over and rooted .602
6) went into market and got droid2 paid ran it
7) wiped data and wipe dalvik
8) loaded cm7 154 and it said something about wrong kernel.
9) rebooted
Now it will not let me back into clockwork.
10) try droid X bootloader try going though rom manger
no luck it goes blank but the screen is still some what lite.
Help!!
Click to expand...
Click to collapse
You tried to flash a Froyo kernel rom over stock Gingerbread (using the Gingerbread kernel), which bricked your device.
SBF back to .602, root again, and flash RevNumber's unofficial CM7 nightlies (and Gapps) from RootzWiki.
Sent from my Transformer TF101 using XDA App
Found the problem. When using rslite you need to un zip the .602 file do not us rslite to uncompress it. It was making a bad os on phone once i did that it loaded and rooted like clockwork. Thx for all you folks hanging in the with me.
Android Ver 2.3.7
Base Ver bp_c_01.09.13p
kernel ver 2.6.32.9-g34b306d [email protected]#2
mod ver cyanogenMod-7.1.0-DROIDX-KANG
Build Num GRH78C
So what is next? Can i do nightly from here? Is there anything else to install
speops38 said:
Android Ver 2.3.7
Base Ver bp_c_01.09.13p
kernel ver 2.6.32.9-g34b306d [email protected]#2
mod ver cyanogenMod-7.1.0-DROIDX-KANG
Build Num GRH78C
So what is next? Can i do nightly from here? Is there anything else to install
Click to expand...
Click to collapse
You can flash RevNumber's unofficial nightlies. Attempting to flash an official nightly will brick your device.
Sent from my DROIDX using XDA App