Related
This thread is discussion about porting Motoblur 2.1 (Cliq Leak) to our devices. I've supplied my work below. Finish it if you wish, or use it as reference.
THIS DOES NOT GET PASSED THE SPLASH SCREEN. IT IS NOT RECOMMENDED TO FLASH THIS UNLESS YOU ARE GOING TO DEBUG IT.
Done:
- edited boot.img (init.rc) (added init.trout, init.sapphire)
- a2sd (/sd-ext)
- oc'd kernel 2.26.34
- swap
- root
- Patched MTD Partitions. (THANKS FIRERAT & jcarrz1!)
To Do:
- Get it to boot. Almost done. Just audio issue.
Changelog | Issues:
Error Messages:
#demesg - "htc-acoustic: ioctl: invalid command"
#logcat - "Volmgr not ready to handle device"
Thanks/Credits:
Cyanogen, Kingklick92, Daneshm90, ChiefzReloaded, Firerat, shafty23, JesusFreke, jcarrz1, Drizzy, lbcoder, kmobs, barak,art010606.
If I missed anyone let me know.
I'm not responsible to what happens to your device.
Instructions FOR DEBUGGING:
- Nandroid backup before anything.
- Flash patch. (MTDBLUR-Patch.zip)
- Reboot to recovery mode.
- Flash ROM. (failblur-last-signed.zip)
Note: When flashing the rom, it will hang a bit near the end of the installation. Give it time.
Revert MTD Partitions (system: 90mb. cache:2mb. data: remaining.)
- Mount sdcard. Delete file /sdcard/mtdpartmap.txt.
- Flash FR-MTD-PartHack-recovery-v1-1_S.zip
- Reboot on recovery.
- Restore nandroid back up.
Have fun !
awesome. cant wait to see how it goes. i really hope people take this up. i cant stand stock and hero has seemed to die down. i personally didnt have a problem with blur. im big on social networking apps and blur is big for that. i really didnt mind it much at all and would LOVE to have a great blur rom. only problem with the cliq itself is that its a brick and moto keeps it locked up tighter than the house that is surrounded by cops in a "to catch a predator episode"
for those of you who dont know alot about it btw here are some of the new features,
http://www.youtube.com/watch?v=dpRUdHGirKQ
Only thing that looks cool about 2.1 is the adjustable widgets, from what I've seen on the Droid, the launcher runs slow and looks a lil choppy. I can't wait to see this done though
protomanez said:
Only thing that looks cool about 2.1 is the adjustable widgets, from what I've seen on the Droid, the launcher runs slow and looks a lil choppy. I can't wait to see this done though
Click to expand...
Click to collapse
adjustable widgets? we have some sense 2.1 roms but i do not recall that? is it a blur only feature?
asb123 said:
adjustable widgets? we have some sense 2.1 roms but i do not recall that? is it a blur only feature?
Click to expand...
Click to collapse
Yeah it was only in blur, it's in ADW but it doesn't work that well since the widgets weren't even made to be adjustable.
Skip to 1:50 http://www.youtube.com/watch?v=Lt2NMYXtWTU
your issues would be trying to actually succeed with a2sd at such an early stage. allow me to suggest shifted mtd partitions, see firerat's thread on the 1st page of this forum (usually)
it'll allow you to cram everything on. you'll have to edit the boot.img to negate the effects of a2sd support.
jcarrz1 said:
your issues would be trying to actually succeed with a2sd at such an early stage. allow me to suggest shifted mtd partitions, see firerat's thread on the 1st page of this forum (usually)
it'll allow you to cram everything on. you'll have to edit the boot.img to negate the effects of a2sd support.
Click to expand...
Click to collapse
Thanks, I'll try it out.
Updated post. I'm done for today. I'm off to sleep. I'll continue tomorrow. Hope someone can find out the audio issue out.
dont give up on this bro. keep it up
Glad to see progress. Can't wait till u get it to boot.
what kernel? try a different one to fix characters.
jcarrz1 said:
what kernel? try a different one to fix characters.
Click to expand...
Click to collapse
Thanks.
Yup, that was my error. I still had default kernel from the dump. lol.
OP updated.
Won't be able to work on this until Monday. My sdcard fried (Original one from launch). I'm basically phone less because I fastboot erased system, Rebooted into recovery, and sdcard wasn't detected. So no nandroid restore or rom flashing.
Still not booting though. Anyone care to help? I don't want this ROM to go the way the pulse 2.1 rom did....
rk0 said:
Thanks.
Yup, that was my error. I still had default kernel from the dump. lol.
OP updated.
Won't be able to work on this until Monday. My sdcard fried (Original one from launch). I'm basically phone less because I fastboot erased system, Rebooted into recovery, and sdcard wasn't detected. So no nandroid restore or rom flashing.
Still not booting though. Anyone care to help? I don't want this ROM to go the way the pulse 2.1 rom did....
Click to expand...
Click to collapse
it likely will... they're a pain in the ass to port, and they're slow even when they work, so i don't want to waste my time. The only worthwhile things atm are 2.1 sense and 2.2. But good luck, if it shows promise when you get it working, i'll jump all over it.
rk0 said:
Still not booting though. Anyone care to help? I don't want this ROM to go the way the pulse 2.1 rom did....
Click to expand...
Click to collapse
2.1 pulse? i didnt realize there was one lol
jcarrz1 said:
it likely will... they're a pain in the ass to port, and they're slow even when they work, so i don't want to waste my time. The only worthwhile things atm are 2.1 sense and 2.2. But good luck, if it shows promise when you get it working, i'll jump all over it.
Click to expand...
Click to collapse
the origional blur ports werent slow for first releases. i mean, im no expert when it comes to porting, but blur and pulse always seem to get little effort put into them. idk if its just the fact that the rom is so tied to the moto phones themselves or what the deal is that it makes it so its too hard for devs to continue progress on them. i just dont see how you can say its going to run slow and not be worthwhile without even seeing a preliminary release that actually boots...
idk, i just really hope someone will pick it up. if i knew how to do any of this stuff i would have tried my hand at it but i have no clue as to porting and i dont have the time with my work/family schedule.
sucks to the OP though. hope you can get a new sd card and a useful phone again.
I was never able to login or create an account with previous motoblur ports. :/
Sent from my PC36100 using XDA App
darkwingduck20 said:
I was never able to login or create an account with previous motoblur ports. :/
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Well it isn't necessarily moto blur, just an OS with little moto blur add-ons.
are you sure your sdcard is fried? I have a method to bypass sd temporarily, to flash a rom, etc.
Motoblur widgets included?
Sent from my evo using XDA App
jcarrz1 said:
are you sure your sdcard is fried? I have a method to bypass sd temporarily, to flash a rom, etc.
Click to expand...
Click to collapse
I got it back working. I figured out what happened. Something in my SPL was messing with my sdcard. I dont know how, but it was. It was making large qxdm_[time stamp].qm files each time i booted to recovery.
Solution: Get another sdcard, copy DREAIMG.nbh to sdcard and go back to 1.0. Btw, UI is ugly back then. lol. Then I rerooted. Reformatted my original sdcard. And now everything's working. I'll keep working on this tomorrow or Monday.
So what happened was last night my phone died. I let it charge, went to turn it on and it wouldent boot past the htc screen. When i went into recovery it gave me this error E:Can't open /cache/recovery/log and E:Can't open /cache/recovery/last_log. Im pretty much confused on what to do? I tried using that recovery file PD15IMG and keep getting FAIL-PU on bootloader boot recovery system userdata splash1 and then it gets stuck on radi_v2. Im running hboot-0.86.0000 radio-26.03.02.26_M i used ****ing rom manager -_- so im using clockworkmod v3.0.0.5. Im pretty much desperate at this point as ive tried everything and nothing seems to be working. Ive searched a ton and havent been able to find anything. Thank you SO much.
Wow, this is happening quite a bit lately. I think it happened to 2 other people within the past week. They were unable to fix it due to having the 86.0000 bootloader just like you.
http://forum.xda-developers.com/showthread.php?t=1008883
http://forum.xda-developers.com/showthread.php?t=997527
Those are the threads.
Wonderful. Hurray for 500$ paperweights.
No insurance?
Bought on craigslist brand new.
bmartin1207 said:
So what happened was last night my phone died. I let it charge, went to turn it on and it wouldent boot past the htc screen. When i went into recovery it gave me this error E:Can't open /cache/recovery/log and E:Can't open /cache/recovery/last_log. Im pretty much confused on what to do? I tried using that recovery file PD15IMG and keep getting FAIL-PU on bootloader boot recovery system userdata splash1 and then it gets stuck on radi_v2. Im running hboot-0.86.0000 radio-26.03.02.26_M i used ****ing rom manager -_- so im using clockworkmod v3.0.0.5. Im pretty much desperate at this point as ive tried everything and nothing seems to be working. Ive searched a ton and havent been able to find anything. Thank you SO much.
Click to expand...
Click to collapse
Before you go all bonker. If you go into the recovery image, is it still Clockwork ROM manager or is it the factory recovery image.
lowandbehold said:
Wow, this is happening quite a bit lately. I think it happened to 2 other people within the past week. They were unable to fix it due to having the 86.0000 bootloader just like you.
http://forum.xda-developers.com/showthread.php?t=1008883
http://forum.xda-developers.com/showthread.php?t=997527
Those are the threads.
Click to expand...
Click to collapse
not being able to mount the system is 100% different than mounting the logs....
two different things. This one might not be a huge problem.
Well that is good to hear, hope you guys get it figured out.
neidlinger said:
Before you go all bonker. If you go into the recovery image, is it still Clockwork ROM manager or is it the factory recovery image.
Click to expand...
Click to collapse
What do you mean exactly? When i boot into recovery it does take me into clockwork and i am able to do most things it just throws me that error on startup.
lowandbehold said:
Well that is good to hear, hope you guys get it figured out.
Click to expand...
Click to collapse
I have a feeling they tried flashing a 2.2 ROM using 3.0.0.5 which will create problem. and since the ROMs are different styles ext3/ext4 the log is stored differently.
neidlinger said:
not being able to mount the system is 100% different than mounting the logs....
two different things. This one might not be a huge problem.
Click to expand...
Click to collapse
how do i fix then?
If you can get into recovery you might be ok. Try this.
Go online with your computer. Download a CM nightly or the rc3 release.
Plug your phone into your computer while you are in clockwork recovery.
In clockwork go to mounts and storage. On the bottom click mount USB storage. You should now see your memory card on your computer.
Copy the CM zip you downloaded to somewhere you will remember on your memory card.
After it copies.... in your phone hit unmount storage.
Now... do a full wipe. Format data system cache dalvik cache.
Now using clockwork install the CM Tom you added to your SD card.
This should redo your partitions correctly and you should be good to go.
Sent from my HTC Glacier using XDA App
bmartin1207 said:
What do you mean exactly? When i boot into recovery it does take me into clockwork and i am able to do most things it just throws me that error on startup.
Click to expand...
Click to collapse
Okay, the MyTouchHD can run Gingerbread (2.3) ROMs and they can also run FroYo (2.2) ROMs. 2.3 are ext4 designed ROMs and 2.2 are Ext3 ROMs. The reason it cannot find your you log is they are looking for them in different places. The 3.0.0.5 is looking in spot A and they are stored in Spot B and it doesn't know where to look for them.
Try reading through This thread and see if that helps you out.
I have a feeling you tried flashing a 2.2 ROM using 3.0.0.5 recovery image.
neidlinger said:
Okay, the MyTouchHD can run Gingerbread (2.3) ROMs and they can also run FroYo (2.2) ROMs. 2.3 are ext4 designed ROMs and 2.2 are Ext3 ROMs. The reason it cannot find your you log is they are looking for them in different places. The 3.0.0.5 is looking in spot A and they are stored in Spot B and it doesn't know where to look for them.
Try reading through This thread and see if that helps you out.
I have a feeling you tried flashing a 2.2 ROM using 3.0.0.5 recovery image.
Click to expand...
Click to collapse
Nah i flashed a gingerbread rom im using CM7 RC2.
bmartin1207 said:
Nah i flashed a gingerbread rom im using CM7 RC2.
Click to expand...
Click to collapse
and you are getting caught in a bootloop?
something is odd.
Did you check the MD5SUM?
Yes I was one of those people it happened to, I did have the ENG bootloader .85.2007 but still couldn't get anything to work, i just gave up and got a replacement, sorry if this is any bad news
lowandbehold said:
Wow, this is happening quite a bit lately. I think it happened to 2 other people within the past week. They were unable to fix it due to having the 86.0000 bootloader just like you.
http://forum.xda-developers.com/showthread.php?t=1008883
http://forum.xda-developers.com/showthread.php?t=997527
Those are the threads.
Click to expand...
Click to collapse
This is horrible! I just bought this phone like 2 weeks ago =[
Are you on tmobile? Like Neidlinger said, it is a different issue so it might be fixable. If not take it to a store maybe you can get an exchange. If you look at the one of the thread about non warranty exchange I think someone said they bought a phone off of craigslist and they were able to exchange it at T-mobile. Good luck, hope you figure something out.
I went thru the same issue with RC2.... Couldnt mount anything,everything I tried to flash just showed errors,so I just threw my hands up & waved that white flag lol..... I called tmobile told them phne wnt get past splash screen,they replaced it & that was bout a month ago & havent gotten calls or emails bout voiding warranty so cross my fingers they never charge lol...i have cwr 3.0.0.6 now so hoping this dnt EVER happen again....
lowandbehold said:
Are you on tmobile? Like Neidlinger said, it is a different issue so it might be fixable. If not take it to a store maybe you can get an exchange. If you look at the one of the thread about non warranty exchange I think someone said they bought a phone off of craigslist and they were able to exchange it at T-mobile. Good luck, hope you figure something out.
Click to expand...
Click to collapse
I bought it off of craigslist too and getting a warranty replacement from tmobile by next week.
I don't normally like to post in development but I thought this needs some attention. I thought that I read that clockwork recovery was not backing up the 4G keys when doing a nand. If this is true flashing custom roms can be a bit risky because if you have a problem and loosed your keys you are screwed = no more 4g.
This was a problem for a long time on the evo with clockwork recovery many people flashed roms, would have some issue and would loose their 4g keys. Than they would flash back to a nand backup only to find out that clockwork had not backed up the keys in the nandroid. I also check my nand backup I was not able to find my wimax keys and this can be a big problem if you like using 4G.
This is what I have seen I could be incorrect but I don't think I am. Is there a way to have clockwork create a recovery specifically for the NS4G that would address this?
First of all, you are probably not running the right recovery. Secondly, the right recovery does not work at this time lol (broken keymaps). I spoke to Koush tonight and he is fixing the Nexus S 4G recovery, it should be done by tomorrow. If you are running the crespo recovery that is for the regular Nexus S, he will release one that has crespo4g in the filename, that is the one you need. After he releases that it may backup what you speak of. As of now there is no official Nexus S 4G recovery.
well actually there is. just the keymaps are broken
shabbypenguin said:
well actually there is. just the keymaps are broken
Click to expand...
Click to collapse
Exactly. Check here for the latest one: http://mirror.sea.tdrevolution.net/cm/recoveries/
* The one dated May 12th is the broken one.
yea i made the mistake of flashing it and quickly found out that it wasnt a good idea
shabbypenguin said:
yea i made the mistake of flashing it and quickly found out that it wasnt a good idea
Click to expand...
Click to collapse
Did the same lol. He doesnt have one to test it on so we were the guinea pigs.
just to give you guys some more confidence i ran trusselo's super easy batch scritp on my dad's windows 7 box to hack 3e recovery.
you can look at my 3e thread in captivate general but do not attempt the kernel swap methods!
use trusselo's script on windows
if it fails or you are on a mac/linux machine then use the manual 3e fix after you root the device.
after i got 3e modded for self signed update.zip zip flashing like the old 2e recovery on 2.1 sgs phones i installed rom manager and chose the captivate cwm recovery. rebooted into recovery, reinstaled packages. phone rebooted, reistaled packages again and i was sucessfully in cwm. from there i was able to backup the stock rom and installed a .zip file that just changed my build.prop (taking baby steps) i could have spoofed the build.prop in many ways but it was for the sake of testing. the flash was successful. i booted up checked for the change and confirmed it was written to /system properly.
then i rebooted and restored the backup. there were some graphical errors including a broken progress bar and a splash screen that covers the menu when the restore is done so it is difficult to navigate, but it is something. success! the restored rom booted and the old build.prop was in place proving it was a successful restore.
tomorrow i will try a replaced vending.apk (market) and the build.prop as a market fix and post it in a thread if it works. if gtg465x doesnt mind i will try to build a rom off his deodexed rom if someone doesnt beat me to it.
i think we need a bounty to buy a dev phone for someone more knowledgable than me. i dont want to go all cowboy and brick this thing, the captivate had much more as far as backup plans so im being more cautious with this one. and even if i had a dev phone i wouldnt be of as much help as others around xda.
Chika Da China Da Chinese Chicken?
Dani897 said:
just to give you guys some more confidence i ran trusselo's super easy batch scritp on my dad's windows 7 box to hack 3e recovery.
you can look at my 3e thread in captivate general but do not attempt the kernel swap methods!
use trusselo's script on windows
if it fails or you are on a mac/linux machine then use the manual 3e fix after you root the device.
after i got 3e modded for self signed update.zip zip flashing like the old 2e recovery on 2.1 sgs phones i installed rom manager and chose the captivate cwm recovery. rebooted into recovery, reinstaled packages. phone rebooted, reistaled packages again and i was sucessfully in cwm. from there i was able to backup the stock rom and installed a .zip file that just changed my build.prop (taking baby steps) i could have spoofed the build.prop in many ways but it was for the sake of testing. the flash was successful. i booted up checked for the change and confirmed it was written to /system properly.
then i rebooted and restored the backup. there were some graphical errors including a broken progress bar and a splash screen that covers the menu when the restore is done so it is difficult to navigate, but it is something. success! the restored rom booted and the old build.prop was in place proving it was a successful restore.
tomorrow i will try a replaced vending.apk (market) and the build.prop as a market fix and post it in a thread if it works. if gtg465x doesnt mind i will try to build a rom off his deodexed rom if someone doesnt beat me to it.
i think we need a bounty to buy a dev phone for someone more knowledgable than me. i dont want to go all cowboy and brick this thing, the captivate had much more as far as backup plans so im being more cautious with this one. and even if i had a dev phone i wouldnt be of as much help as others around xda.
Click to expand...
Click to collapse
Very nice. I am gonna try as well. As long as CM is working I am comfortable pushing my luck a little.
Awesome! Can you post the files or the link to the thread with the files?
slider2828 said:
Awesome! Can you post the files or the link to the thread with the files?
Click to expand...
Click to collapse
just look in the captivate general stickies. i would post a link but there is stuff in there that doesnt apply because we dont have any kernels to flash, i dont want to confuse anybody and cause bricks because someone flashes a sgs kernel. i might make new write up.
Chika Da China Da Chinese Chicken?
I was going to run the PC batch script but the download link actually downloaded a CWM zip.
That's no PC script....no batch file to be found.
EDIT: I am an idiot. Disregard.
slappyjoker said:
I was going to run the PC batch script but the download link actually downloaded a CWM zip.
That's no PC script....no batch file to be found.
EDIT: I am an idiot. Disregard.
Click to expand...
Click to collapse
you think you're an idiot now wait till you read the directions!
Chika Da China Da Chinese Chicken?
Dani897 said:
you think you're an idiot now wait till you read the directions!
Click to expand...
Click to collapse
That was pretty classic. But hey, it sure did work.
1st. Test with CM. Adhoc WiFi Supplicant Zip. (Success)
2nd. Dunno yet.
yep working great
i am backing up in cwm as we speak
samsungcaptivates said:
i am backing up in cwm as we speak
Click to expand...
Click to collapse
So CWM doesn't work in the traditional sense yet?
bella92108 said:
So CWM doesn't work in the traditional sense yet?
Click to expand...
Click to collapse
it does but there seems to be a problem. not sure why, i had no issues flashing small mods for testing but people are having trouble flashing roms. besides that the restore process seems to give me some graphical bugs but works. as far as i can tell it works like it should but i wont discredit others claiming issues mounting the sd card.
Dani897 said:
it does but there seems to be a problem. not sure why, i had no issues flashing small mods for testing but people are having trouble flashing roms. besides that the restore process seems to give me some graphical bugs but works. as far as i can tell it works like it should but i wont discredit others claiming issues mounting the sd card.
Click to expand...
Click to collapse
Hmm, how long is the timeframe between when CWM is updated? I'd love to get rid of all this AT&T [email protected]# they litter my phone with, but I don't want to brick it... and lots of people seem to brick phones without CWM, haha
bella92108 said:
Hmm, how long is the timeframe between when CWM is updated? I'd love to get rid of all this AT&T [email protected]# they litter my phone with, but I don't want to brick it... and lots of people seem to brick phones without CWM, haha
Click to expand...
Click to collapse
you can use titanium backup to remove stuff. also there is odin/heimdall to flash "refuse" from h8rift. they work and are also the safety net unique to samsung phones.
Dani897 said:
you can use titanium backup to remove stuff. also there is odin/heimdall to flash "refuse" from h8rift. they work and are also the safety net unique to samsung phones.
Click to expand...
Click to collapse
Yeah I suppose, I am just hoping that CWM for Infuse will release quick along with new ROMs (Gingerbread? hehe)
bella92108 said:
Yeah I suppose, I am just hoping that CWM for Infuse will release quick along with new ROMs (Gingerbread? hehe)
Click to expand...
Click to collapse
"Release quick?" We've been waiting for weeks already
beatblaster said:
"Release quick?" We've been waiting for weeks already
Click to expand...
Click to collapse
Weeks? Didn't this phone hit stores 5/21? That was 8 days ago.
bella92108 said:
Weeks? Didn't this phone hit stores 5/21? That was 8 days ago.
Click to expand...
Click to collapse
Nah, 5/15. It's been 2 weeks today. Anyway.....
Hey anyone find a way to install cwm install packages using this update.zip?
It says it can't mount the sdcard when I try to install the .zip.
Anyone?
I promise i searched "nandroid" but only result that came out was someone who flashed gingerbread kernal on froyo nandroid (something i would do...lol)
I've flashed my Vibrant and EVO a million diff ways from Sunday (i don't know too much, just enuf to get me in BIG TRUBBLE but luckily i have never ONCE seen that dreaded yellow triangle...lol
Anyway, here's where i am confused:
I rooted my Infuse, i installed unzipped modded 3e recovery, i flashed Recovery i9000 thru ROM MGR, then flashed into recovery thinking there would be a "nandroid backup" option and there isn't....
I don't want to flash Infused or any other ROM, i just want a nandroid backup option... Is that possible?(and if so, s-p-e-a-k v-e-r-r-r-r-y s-l-o-w-l-y...lol
ty!
Ms. D
You can back up your current rom by either booting into red CWM recovery, select Backup and Restore or open up Rom Manager and select Backup Current Rom option, and there you go.
Sent from my B.A. Infuse 4G
Ms.Dummbunny said:
I promise i searched "nandroid" but only result that came out was someone who flashed gingerbread kernal on froyo nandroid (something i would do...lol)
I've flashed my Vibrant and EVO a million diff ways from Sunday (i don't know too much, just enuf to get me in BIG TRUBBLE but luckily i have never ONCE seen that dreaded yellow triangle...lol
Anyway, here's where i am confused:
I rooted my Infuse, i installed unzipped modded 3e recovery, i flashed Recovery i9000 thru ROM MGR, then flashed into recovery thinking there would be a "nandroid backup" option and there isn't....
I don't want to flash Infused or any other ROM, i just want a nandroid backup option... Is that possible?(and if so, s-p-e-a-k v-e-r-r-r-r-y s-l-o-w-l-y...lol
ty!
Ms. D
Click to expand...
Click to collapse
Did you re-install packages "twice" in recovery to get cwm
Holy MIUI Batman!
LG_iiNsTiiNcT said:
Did you re-install packages "twice" in recovery to get cwm
Holy MIUI Batman!
Click to expand...
Click to collapse
nope, i didn't reinstall pkgs even ONCE...lol...was i supposed to? i should do it and then do it again and then "nandroid" will appear as an option?
ty!
Ms D
Ms.Dummbunny said:
nope, i didn't reinstall pkgs even ONCE...lol...was i supposed to? i should do it and then do it again and then "nandroid" will appear as an option?
ty!
Ms D
Click to expand...
Click to collapse
I'm guessing the recovery you are booting into is blue (which isnt really recovery) reinstall packs and you should be in green CWM recovery,
It won't say "nandroid", but you will have the option for "backup and restore" which is basically the same thing.
xIC-MACIx said:
I'm guessing the recovery you are booting into is blue (which isnt really recovery) reinstall packs and you should be in green CWM recovery,
It won't say "nandroid", but you will have the option for "backup and restore" which is basically the same thing.
Click to expand...
Click to collapse
yayyyyy it worked... Did it twice, 1st time it doesn't do it like u said (wonder why- wait! don't tell me...lol)
Don't know why i never saw anything before about that reinstalling pkgs to get it to the green screen, i guess cuz i always flashed a ROM that had it cooked in it maybe? But this time around i don't wanna flash any ROMS, i got it running perfectly just rooted and with a few tweaks : )
http://www.youtube.com/watch?v=E7jbgAzhDVg
thanx sooo much : )
Ms D
Ms.Dummbunny said:
yayyyyy it worked... Did it twice, 1st time it doesn't do it like u said (wonder why- wait! don't tell me...lol)
Don't know why i never saw anything before about that reinstalling pkgs to get it to the green screen, i guess cuz i always flashed a ROM that had it cooked in it maybe? But this time around i don't wanna flash any ROMS, i got it running perfectly just rooted and with a few tweaks : )
http://www.youtube.com/watch?v=E7jbgAzhDVg
thanx sooo much : )
Ms D
Click to expand...
Click to collapse
No problem that's what were here for. Re-installing the packages is what changes the recovery ie 3e and cwm
Holy MIUI Batman!
Wow you messed up on the West part of the process but got through the hard stuff, a little ditsy but nothing to be too ashamed of.
You did better than most guys who ask questions. Actually the girls usually do. Next time just get heimdall (more reliable than Odin and its easier to extract.tar dukes for Odin to use in heimdall than to create .tar files for use in Odin for custom stuff). And flash a voodoo kernel. Trust me its easier than what you did(fewer steps) and once gingerbread is out you will have to do this to root. Soc will no longer work with 2.3.3 or newer.