Related
Okay I do apologize in advance about the noob-ness of this thread.
Alright i have my defy, it's rooted. That was easy. Now i'm on to more complicated things, Cyanogen Mod. I have read Quarx and Zephyrot's thread on the matter. However, to me it seems fairly easy you just need to know what to download. That's the thing i'm not quite sure on that part. If there was some way i could have somebody tell me what I need for that would be very much appriciated. If there is anything you need to know about the phone just ask.
I haven't done anything to the phone except update to 2.2.1 and root it.
Again I do apologize for the noob-ness and any information is greatly apprciated.
okay
Okay I was able to get cm7 up and running giving me 2.3.4 however i didnt include the gapps file so i couldn't get the market. looking over quarx's thread i thought i could just do it again just with the added gapps pack on the sd card. however i just realized that i didnt have cwm or 2nd init installed on my phone since the flash. i had already done the wipes for the flash when i finally realized it. i think im now stuck on a boot loop. if someone could help me get back to the stock froyo that would be so much help.
Installing Quarx's cm7 does NOT remove 2nd init, in fact it is included in the zip you flashed. Wiping data/cache will not remove 2nd init. Only flashing a sbf or uninstalling it will remove it! You are in a bootloop because (probably) you wiped in stock recovery? In which case you should still have 2nd init. If you wiped in custom recovery then this shows that you did have CWM because you were in it when you wiped. If you were in it then you should have wiped, flash cm7, then flash gapps all in one session. Only wipe in stock recovery if you plan on flashing a sbf otherwise always use custom recovery. To go back to stock rom wipe in stock recovery then boot into bootlader and flash stock sbf with RSD. I have always been under the impression that even wiping from stock recovery will not remove 2nd init! Someone please correct me if I'm wrong
right now i just want my phone to work. so since i had 2.3.4 (i think thats what it was) because of cm7 what sbf do i need. or could i just use 2.2.1.
Yes you can easily downgrade from cm7 using your stock 2.2 sbf or any 2.2 sbf for that matter (There may be an exception to this rule so read carefully the sbf you are going to flash) Only flashing a full 2.3.4 sbf will prevent a downgrade But in general you should be able to flash ANY 2.2 sbf coming from cm7
I tried a search but didn't find much of any relevance to my Arc's problem.
My Arc was getting quite laggy so I decided to wipe and put a custom ROM on. I rooted, then unlocked the bootloader and managed to put on CWM using DoomLord's kernel. Everything fine up until here.
Then, mistakenly, I tried to put stable CM7 on without updating the stock ROM. I was still on 3.0 (2.3.3) something. Well, after that it got stuck in a boot loop with the SE and CM7 logos just coming up and restarting.
I then tried the Flashtool with a stock uptodate 4.0 something firmware. It flashed successfully, but it still was stuck in the loop, albeit now without the CM7 logo. I then tried the FTA unbricking tool for repairing the trim area but it still stayed in the boot loop.
What else can I do? Maybe there is a driver problem and that is why even after using Flashtool it still doesn't boot?
I would be very grateful if someone could help me on this.
You have to flash FXP's kernel and not DooMKernel.
But I also tried to flash a stock rom and that didn't work also.
EDIT: I flashed stock ROM again, still didn't boot. Installed DoomLord kernel and then arconium and it still doesn't boot.
EDIT 2: In CWM Recovery if I try to wipe data, it says this:
"E:format_volume: no MTD partition "userdata"
Has anyone got a fix for this?
It would be much appreciated.
can you charge your phone now?
Yep, I can charge the phone.
it means your kernel is still working....
then have it fully charged, then try to flashing again.
some tips:
1. always have latest flashtools
2. always have your phone fully charged b4 flashing.
3. proceed flashing carefully. if u miss one thing, then trouble come.
4. have cache and dalvik cache cleaned after flashing a kernel or Rom.
good luck mate...
gogo415 said:
it means your kernel is still working....
then have it fully charged, then try to flashing again.
some tips:
1. always have latest flashtools
2. always have your phone fully charged b4 flashing.
3. proceed flashing carefully. if u miss one thing, then trouble come.
4. have cache and dalvik cache cleaned after flashing a kernel or Rom.
good luck mate...
Click to expand...
Click to collapse
No luck with previous firmwares so I'll try to flash the latest .62 stock ROM and then see.
I'll let you know how I get on. Thanks!
Well lads, I managed to get it working by flashing the LT18i firmware (4.0.2.A.0.42_CE). Now I just need to go back to the drawing board and try to get CM7 on there.
Thanks for all the help! I'll update this thread with any experiences.
I've managed to do it. Installed latest .62 firmware, flashed CM7 kernel, flashed 7.2 ROM and then GAPPS.
I don't know why it took me two days to bring the phone back from the dead.
ZAnwar said:
I've managed to do it. Installed latest .62 firmware, flashed CM7 kernel, flashed 7.2 ROM and then GAPPS.
I don't know why it took me two days to bring the phone back from the dead.
Click to expand...
Click to collapse
hi, i came up with the same question:
E:format_volume: no MTD partition "userdata"
and my device is moto xt502
could you be so kind to give some details how you fix it
thank you very much
I am having the same problem too..please help! i flashed cm7 kernel n followed the instructions very carefully
ilamaan said:
I am having the same problem too..please help! i flashed cm7 kernel n followed the instructions very carefully
Click to expand...
Click to collapse
I followed the instructions too, though they are not so much noob-friendly (and neither are the people on the forums, it seems...). FXP is not responding (actually, they rarely respond to anything, they usually just post when new release is out), other people either don't know how to fix it, because they haven't experienced such issues, or they are just hostile because you're "a an annoying noob". Anyway... first time after trying to flash 64 baseband on 107 or 106 release, I got stuck on logo, then flashed back to .42 and it worked. Now, while updating to 108, I tried to flash the 64 libraries and patch, but it didn't work. Got back to .42, but this time nothing happened. Still stuck on logo. And when I try to restore data, it says:
E:format_volume: no MTD partition "userdata"
Error while formatting /data!
I think I'll go back to stock... love CM, but hate the poor/no help of the developers...
try these
flash new firmware using flashtool.
after flash.turn on your device.
enable uknown source n usb debug
then turn off your fon
flash baseband 64
then turn on your fon
put fxp108 updated-kang,gaps,baseband 64 libs on your memory card,
then turn off your fon
flash fxp kernel fastboot flash boot boot.img
after flash turn on your fon..go to recovery
formated factory reset,wipe cache,clear dalvik cache,wipe betry stats..
flash update cm7.update.zip,gaps.zip,baseband64libs.zip
reboot your fon..wait 2 or 3 mint..done
My thanks goes to you. I was hoping to avoid full wipe, but I don't care anymore, since I brought my phone back to life. I skipped these steps, though:
beranchoi said:
flash baseband 64
flash baseband64libs.zip
Click to expand...
Click to collapse
...because I went to check which baseband my phone was after flashing Global .62, and it said I was on -64, so it was no more necessary. For all of you having trouble with booting, follow the instructions given.
And now back to restoring all those apps
hey guys, can you post the link to that stock firmware, baseband and libs? maybe I've downloaded something wrong :/
btw. is there still that bug with a dark screen after locking phone?
lemon66 said:
hey guys, can you post the link to that stock firmware, baseband and libs? maybe I've downloaded something wrong :/
btw. is there still that bug with a dark screen after locking phone?
Click to expand...
Click to collapse
This is the link to the stock 4.0.2.A.0.42.. flash it using flashtool.. http://www.multiupload.com/W3B7BOKUXQ
Everything you need for flashing FXP is on his signature, including bb .64 (to be flashed with flashtool - doesn't erase a thing).. then download FXP (latest is 108) and inside the zip file you'll see boot.img, which contains the special kernel (to be flashed using fastboot, not flashtool).
Also there's no dark screen bug in the latest releases, certainly not in FXP 107 and 108, which I'm using now.
Please help!
beranchoi said:
try these
flash new firmware using flashtool.
after flash.turn on your device.
enable uknown source n usb debug
then turn off your fon
flash baseband 64
then turn on your fon
put fxp108 updated-kang,gaps,baseband 64 libs on your memory card,
then turn off your fon
flash fxp kernel fastboot flash boot boot.img
after flash turn on your fon..go to recovery
formated factory reset,wipe cache,clear dalvik cache,wipe betry stats..
flash update cm7.update.zip,gaps.zip,baseband64libs.zip
reboot your fon..wait 2 or 3 mint..done
Click to expand...
Click to collapse
Hey, this is my first post on here. I am new to android and just got an arc a few days ago. Even before i got it i was trying to figure out how to mod it. I am reasonably good at computers but a lot of the stuff i read on these forums is beyond me.
I have done my best to root and install CM7 on my arc but i have failed yet again.
I finally got it rooted and was all happy until when i tried to install CM7, all i can get to is the boot screen, but although the little android on the skateboard is very cool, i wish i could get it going!
So because I dont really understand the list of instructions you posted in this quote, i was hoping you could kind of translate into noob-speak. I still dont feel like i completely understand 'flashing'. In your instructions you say to "flash baseband 64" and that is the main point where I am stuck i think. Do you use a certain program (flashtool?) for this? or do it through a terminal window on the PC.
Also links to all the files mentioned would be awesome, its hard to find proper links with multiupload down and that kind of thing. Also with the rate this kind of tech evolves, things get outdated to quickly.
Please help! At the moment i have (i think) successfully returned my arc to the stock firmware using flashtool. Although i did this twice because i re-tried flashing CM7 and failed again. And the second time i couldnt seem to select LTI5i as the device to flash too, but LTI8i is what i used and it appears to have worked. So any help with that little conundrum would also be appreciated!
Cheers for any help given, I am so desperate to get this mod going as i have spent a solid 10+ hours trying already.
your bootloader unlock?right?
which kernel u use right now?
@tehknowitallnoob, I can lead you through the whole flashing process, if you want to, but only on Friday after around 9 pm GMT +1, since I don't have the time to do it earlier.
Sent from my LT15i (Xperia arc) on CM7
Try this:
Reflash back to stock ROM with a flashtool.
Then again flash the cm7 or try cm9
-cheers
Hi all,
I have a little problem with my Gio that I couldn't solve with googling and searching.
I immediately rooted the phone (I downloaded the rooting kit from here) and everything went right.
Everything started when I installed the wrong CWM from phiexz (from here)
- After flashing CWM ext4-only, it got bricked (*).
- So I flashed the stock recovery (from the same thread) via ODIN, in upload mode: my phone seemed restored, could turn on normally but when I booted into recovery mode it jus stucked on the samsung logo (just like it did when it was "fully"-bricked).
- So, with the phone turned on normally, I typed the "factory reset code", but then it went back fully-bricked (that actually surprised me...)
- Then I flushed CWM ext+rfs and it went back half-bricked
- I again tried factory reset with the same result
- I flushed the stock recovery, making it again half-bricked
(*) I guess I read it mentioned as "soft bricked": when I turn the phone in recovery or nurmally, it just shaws "SAMSUNG www.samsung.com", but download mode worked
Now I'm using it this way, with my original rom (customized by my phoning operator):
Android version: 2.2.1
Base band varsion: S5660XXKB9
Kernel version: 2.6.32.9-perf [email protected] #1
Build number: FROYO.AIKD2
What I wanted (and still want) to do is install CWM, make a back up of the ROM now installed and finally install cyanogen from phiexz (flash cwm and getting it to work, run the backup, run ext4formatter, flash cyanogen).
I could of course go without the backup.
What do you think I should do? Any help would be appreciated
Thanks a lot
Davide
davide_k said:
Hi all,
I have a little problem with my Gio that I couldn't solve with googling and searching.
I immediately rooted the phone (I downloaded the rooting kit from here) and everything went right.
Everything started when I installed the wrong CWM from phiexz (from here)
- After flashing CWM ext4-only, it got bricked (*).
- So I flashed the stock recovery (from the same thread) via ODIN, in upload mode: my phone seemed restored, could turn on normally but when I booted into recovery mode it jus stucked on the samsung logo (just like it did when it was "fully"-bricked).
- So, with the phone turned on normally, I typed the "factory reset code", but then it went back fully-bricked (that actually surprised me...)
- Then I flushed CWM ext+rfs and it went back half-bricked
- I again tried factory reset with the same result
- I flushed the stock recovery, making it again half-bricked
(*) I guess I read it mentioned as "soft bricked": when I turn the phone in recovery or nurmally, it just shaws "SAMSUNG www.samsung.com", but download mode worked
Now I'm using it this way, with my original rom (customized by my phoning operator):
Android version: 2.2.1
Base band varsion: S5660XXKB9
Kernel version: 2.6.32.9-perf [email protected] #1
Build number: FROYO.AIKD2
What I wanted (and still want) to do is install CWM, make a back up of the ROM now installed and finally install cyanogen from phiexz (flash cwm and getting it to work, run the backup, run ext4formatter, flash cyanogen).
I could of course go without the backup.
What do you think I should do? Any help would be appreciated
Thanks a lot
Davide
Click to expand...
Click to collapse
Backup and flash cyanogen
Maybe use an old version of CWM so extformatter isnt needed
Sent from my GT-S5660 using xda premium
dont use cwm & cyanogenMod on froyo baseband
Phiexz: I'm intrigued by the fact a Froyo baseband would cause issues with CWM, which doesn't run the radio... Care to expand a little on that?
Darkshado said:
Phiexz: I'm intrigued by the fact a Froyo baseband would cause issues with CWM, which doesn't run the radio... Care to expand a little on that?
Click to expand...
Click to collapse
i dont know, never tried cwm on froyo
but, i think the problem is bootloader & kernel
someone said gingerbread & froyo using different kernel & method of bootloader
Different bootloader images could explain those issues, I guess.
phiexz said:
dont use cwm & cyanogenMod on froyo baseband
Click to expand...
Click to collapse
What a pity Any suggestions about where to find a recovery image and a rom (the more like cyanogen, the better) that suits my phone?
EDIT: By the way, isn't there a way to upgrade and then install cyanogen, or at least upgrade to stock Gingerbread?
davide_k said:
What a pity Any suggestions about where to find a recovery image and a rom (the more like cyanogen, the better) that suits my phone?
EDIT: By the way, isn't there a way to upgrade and then install cyanogen, or at least upgrade to stock Gingerbread?
Click to expand...
Click to collapse
Have you tried updating your phone with your PC via Kies. If that doesn't work you can update to one of the official firmwares using Odin. Here's a link to the official firmware, and here's a link to instructions on flashing via Odin.
koodiifin said:
Have you tried updating your phone with your PC via Kies. If that doesn't work you can update to one of the official firmwares using Odin. Here's a link to the official firmware, and here's a link to instructions on flashing via Odin.
Click to expand...
Click to collapse
Thanks a lot! Updgrade vie Kies worked well, now everything works, also recovery mode...
Android version: 2.3.6
Base band version: S5660XXKT4
Kernel version: 2.6.35.7-perf-CL843729 [email protected] #1
Build version: GINGERBREAD.AIKT2
Of course, it is still my phone operator's rom... By hte way, it isn't rooted any more, i'll have do to it again...
So, I suppose now I can flush CWM (ext4+rfs), backup the current ROM, run ext4formatter, flush CWM ext4 (is this needed?), and finally flush cyanogenmod , can't I?
Thanks a lot for supporting me
Davide
davide_k said:
Thanks a lot! Updgrade vie Kies worked well, now everything works, also recovery mode...
Android version: 2.3.6
Base band version: S5660XXKT4
Kernel version: 2.6.35.7-perf-CL843729 [email protected] #1
Build version: GINGERBREAD.AIKT2
Of course, it is still my phone operator's rom... By hte way, it isn't rooted any more, i'll have do to it again...
So, I suppose now I can flush CWM (ext4+rfs), backup the current ROM, run ext4formatter, flush CWM ext4 (is this needed?), and finally flush cyanogenmod , can't I?
Thanks a lot for supporting me
Davide
Click to expand...
Click to collapse
No problem. Yes what I would do is:
-Setup everything how you like it on the stock ROM
-Flash CWM(ext4+rfs) from stock recovery
-Make a nandroid backup on CWM(ext4+rfs)
-Then flash CWM(ext4)
-Run ext4formatter
-Flash latest CM7.2 zip
-Flash latest CM7.2 patch zip
-Wipe data/factory reset
-Flash Google apps
-Setup everything how you like on the CM7.2 ROM
-Make a nandroid backup on CWM(ext4)
And then if you need to switch back to stock you will either have to try updating via Kies (from CM7.2 (this should work)) or download an official firmware and flash it via Odin (which will format your phone to RFS), once you have the phone back to a stock gingerbread again you can flash CWM(ext4+rfs) again, then restore your nandroid backup from CWM(ext4+rfs)
Installed cyanogen without problems... Thanks a lot for the support!
Davide
I think i have read it somewhere in xda forum, it said that
latest cwm is only support edify scripting which is used in gingerbread, while froyo are still using amend scripting.
May be that's explain why the latest CWM doesn't work if you ROM are still using Froyo.
sangkelana said:
I think i have read it somewhere in xda forum, it said that
latest cwm is only support edify scripting which is used in gingerbread, while froyo are still using amend scripting.
May be that's explain why the latest CWM doesn't work if you ROM are still using Froyo.
Click to expand...
Click to collapse
I think I'm having the same problem as OP, I have an s5660 rooted, and followed instructions http://forum.xda-developers.com/showpost.php?p=16979859&postcount=549 to install CWM 5.2.7 (cwm-5.0.2.7-ext4+rfs-odin.tar.md5).
Previously I was able to access recovery menu by holding HOME + POWER ON, but now the thing freezes at 1st samsung logo screen. Only now I've come to learn Froyo is not supported. It wasn't mentioned in any article I had read.
I think I will try flash the stock recovery, but I'm scared if it fails I will brick the phone.
Can anyone say, is there an alternative to CWM that will allow me to perform a full system backup that can easily restore the phone in case it's bricked... (and will work on Froyo 2.2.1). I would prefer to backup before attempting any further mods.
The reason I did this in the first place was to overcome "internal memory is low" issue. So far I have been able to move some apps to SD card using Link2SD app but I would like to do nandroid backup before I have a chance to really screw things up. This is my first time doing anything like this and it's my wife's phone, so I have to be extra careful. I tried googling "s5660 froyo nandroid backup", which brought me here.
Any advice is appreciated.
Same problem
Hi!
I have the same problem, did you ever find a solution?
I've installed various ROMs in an attempt to get back to working condition but can't seem to get past the samsung screen.
The problem is, I can't find any stock firmware downloads that still work!! I've been thorough pages and pages of links and keep hitting dead ends. Does anyone have a stock firmware version I can flash with ODIN and at least have a working Gio again!
Many thanks,
orangejuice43 said:
Hi!
I have the same problem, did you ever find a solution?
I've installed various ROMs in an attempt to get back to working condition but can't seem to get past the samsung screen.
The problem is, I can't find any stock firmware downloads that still work!! I've been thorough pages and pages of links and keep hitting dead ends. Does anyone have a stock firmware version I can flash with ODIN and at least have a working Gio again!
Many thanks,
Click to expand...
Click to collapse
download from here:
http://www.sammobile.com/firmwares/database/GT-S5660/
Hello,
i have a Problem with my Defy, i have no working Clockworkmod (CWM) or other Custom Recovery Mod.
Now my Defy have the Bootloop and the only thing i can reach ist the Stock Recovery Mode.
In there i can only install a update.zip, but all versions i would instal from CWM give a signature error.
Is it possible to install a Custom Recovery Mod only with the Stock Recovery Mode?
After this i can start the Custom Recovery Mod and install my last used Custom Rom, without losing my data.
Greetings.
Stock recovery can not flash anything that does not come from motorola, and it can not be replaced due to the fact that the bootloader is locked. Your only solution is to reflash/flash an sbf through rsdlite
Sent from my 1Ghz CM7 + CM9 Defy
Ok, that means that the thread on xda, do sign a update.zip, doenst work realy?
If i reflash the same sbf and the same custom rom, are the data deleted?
In most installation guides it says wipe manual?!
Thanks.
instantgip said:
Ok, that means that the thread on xda, do sign a update.zip, doenst work realy?
If i reflash the same sbf and the same custom rom, are the data deleted?
In most installation guides it says wipe manual?!
Thanks.
Click to expand...
Click to collapse
The zips on XDA are to flash with the 2nd-init recovery. To install that you must be rooted and use an app on the market (2nd-init installer). But that custom recovery does not replace the stock one seen as we can't overwrite it.
In order to flash a new sbf:
In stock recovery wipe data/factory reset
Plug phone in PC in bootloader mode (power+vol up?)
Flash sbf with RSDLite
Pretty easy, find which sbf was for your contry/carrier .
Sent from my 1Ghz CM7 + CM9 Defy
Hello,
thanks, what a pity that after a bootloop the data are not accessible anymore.
Greetings.
Because i was in the Bootloop i risk to install the same SFB that i have all the time installed, without anything wiping.
It works! I have acces to all my Data! I make a backup of everything und then i wiped to make a clean install.
Now i am on a new sbf and a newer rom, without losing any data.
instantgip said:
Because i was in the Bootloop i risk to install the same SFB that i have all the time installed, without anything wiping.
It works! I have acces to all my Data! I make a backup of everything und then i wiped to make a clean install.
Now i am on a new sbf and a newer rom, without losing any data.
Click to expand...
Click to collapse
How did you manage that without 2nd-init recovery?
Sent from my 1Ghz CM7 + CM9 Defy
I think he used titanium backup, SMS backup & Restore...
In fact I saw that there is a problem in the links for the 2ndInit apk in Pedrodh thread :
http://forum.xda-developers.com/showthread.php?t=1032212
All the downloading files at the end of the first post are in zip format now.:-(
So without custom recovery its impossible to use them. But I can be wrong and there is a way to do that?
No i was in bootloop and have only acces to the stock rom manager.
I take the phone in the bootmodus and flashed my old used sbf with rds, without wiping.
Then I start the phone normaly and see that some things was from the stock sbf and some things was from the custom rom that i used before. In my case Pays Rom Defy 5.1 .
Then i look if the Data were accesible, and yes it was. it backup my sms and contacts with MyPhoneExplorer.
Reboot in stock manager again, wipe all data and installed a new sbf and new miui custom rom, like the install guide it said.
instantgip said:
No i was in bootloop and have only acces to the stock rom manager.
I take the phone in the bootmodus and flashed my old used sbf with rds, without wiping.
Then I start the phone normaly and see that some things was from the stock sbf and some things was from the custom rom that i used before. In my case Pays Rom Defy 5.1 .
Then i look if the Data were accesible, and yes it was. it backup my sms and contacts with MyPhoneExplorer.
Reboot in stock manager again, wipe all data and installed a new sbf and new miui custom rom, like the install guide it said.
Click to expand...
Click to collapse
Ah ok, thanks for your answer... ;-)
Hi. All was working well when I was running Quarx's version of CM10 on my Green Lens Defy. I could update to each new update CM10 ROM by clearing the data and cache then flashing the ROM and GApps. After that, I wiped the dalvik cache and reboot. Note my Defy is using a Froyo kernel.
Then I decided to try out Codename Android JB Beta and I did what I normally did with the ROM and then GApps. I ended up stuck in a bootloop. No problem I thought. I'd just reflash Quarx's own version of CM10 after wiping data and cache. I got stuck in a bootloop again. Odd. I tried it with older versions of Quarx's CM10 and they result in me getting stuck in a bootloop as well. So I flashed the US T-Mobile SPF for the Defy using RSD Lite then I logged in to BLur and such as that is needed to access the homescreen where I then turned on USB debugging. I then plugged in my phone into my computer to use SuperOneClick Root to root my device. It said my device was already rooted though I don't think that should happen since I flashed a stock 2.1 SPF. Well I rebooted and installed the 2ndinit apk then installed 2ndinit using the app. I think it said that 2ndinit was already installed. But if my memory is wrong in this case, I then installed 2ndinit and rebooted my Defy but I never got a blue LED.
Then I did the same steps as I did previously over and over again with variations to try to get it to work.
Can someone help?
I caution anyone who may attempt to install Codename Android JB Beta from CM10.
On another matter, downloading an OTA update then rebooting when pressing "install now" brings me to the triangle with exclamation screen and gets stuck there.
Have you done a fullwhipe in the Motorola Recovery before flashing the SBF??(usually you would get a bootloop without fullwhiping but maybe the solution is that easy )
And why did you flash a 2.1 SBF you should maybe try some other SBFs like the Froyo SBFs for your Country
Steveletack said:
Have you done a fullwhipe in the Motorola Recovery before flashing the SBF??(usually you would get a bootloop without fullwhiping but maybe the solution is that easy )
And why did you flash a 2.1 SBF you should maybe try some other SBFs like the Froyo SBFs for your Country
Click to expand...
Click to collapse
Oh a full wipe in stokc recovery is needed? I'll try it.
Can you suggest a good SBF for a US Green Lens Defy if you know any?
Is it fine if I use the 3.4.2-179 CEE Deblur SBF as recommended by Quarz for a base then root, install 2ndinit. and flash CM10 from Clockwork Mod Recovery?
j814wong said:
Is it fine if I use the 3.4.2-179 CEE Deblur SBF as recommended by Quarz for a base then root, install 2ndinit. and flash CM10 from Clockwork Mod Recovery?
Click to expand...
Click to collapse
Yep fine for using that one but you should definitely check out the begginers guide for sbf rooting ect as you've been having trouble with this for the last few days now and I'd really like to see get this sorted once and for all
Sent from my MB525 using xda app-developers app
after you instaled 2ndinit
are you opend it and appli the recovery?
if you dont applied the recovery you will not find the led blue and the CWM