Hi,
Upgraded to 2.3.3 and lost root.
Bored of mucking about with oneclick etc, I unlocked the bootloader. Easy(ish), cool!
Trying to flash amon ra with fastboot, everything goes well (appears as though it's flashed). But when I re-boot, it isn't there!
Padlock showing - so bootloader unlocked.
Nexus drivers installed, device showing with "fastboot devices".
Trying to flash amon ra 2.2.1.
Any suggestions?
Ta!
Andy
When you boot a stock rom it wipes custom recoverys and puts the stock one back.
Use the search feature on the forum.
Sent from my Nexus One using XDA App
Read my signature, look there for recovery installation guide w/ unlocked bootloader.
albundy2010 said:
When you boot a stock rom it wipes custom recoverys and puts the stock one back.
Use the search feature on the forum.
Click to expand...
Click to collapse
Thanks for your reply.
I've spent (literally) all day searching the forum (I'm in the uk - so hours and hours). There's so much, and some of it contradictory.
Ok, so I can't put a rom on without a custom recovery, but I can't put a custom recovery on because the stock rom wipes it?
I don't actually want a custom rom, simply a rooted stock phone. Which I have had previously.
Cheers! (driven to booze!)
Andy
Jack_R1 said:
Read my signature, look there for recovery installation guide w/ unlocked bootloader.
Click to expand...
Click to collapse
Thanks.
Yes, that's what I've been doing. There's a mistake in that part of the faq:
Faq states at the end "reboot recovery"
Should be "reboot-bootloader"
That works, but as soon as I then reboot into 2.3.3 - it wipes the custom recovery (which is why I'm in the q + a).
The other problem I'm having is that my phone doesn't appear rooted from within the o/s (apps that require root don't work), but the padlock is there ans the bootloader is unlocked. I can install su and busybox installer from the market, but neither work.
Back to the beer!
Andy
I can't explain all in detail while on my phone.
Do this. Grab a preroooted stock rom from the dev section and put it on SD card.
Boot into fastboot and flash the custom recovery.
Then load up that recovery without booting up the os.
Flash the rom you downloaded.
There are other ways to fix your issue but this is probably the simplest for you.
Sent from my Nexus One using XDA App
albundy2010 said:
There are other ways to fix your issue but this is probably the simplest for you.
Click to expand...
Click to collapse
Thanks, that makes sense - and I agree with your statement above (simplest for me)!
I had (mistakenly) thought that unlocking the bootloader, then installing busybox and su from the market gave me a rooted phone.
I'll give it a go, when my wife regains her patience ;-)
Andy
andynx1 said:
Thanks.
Yes, that's what I've been doing. There's a mistake in that part of the faq:
Faq states at the end "reboot recovery"
Should be "reboot-bootloader"
That works, but as soon as I then reboot into 2.3.3 - it wipes the custom recovery (which is why I'm in the q + a).
Click to expand...
Click to collapse
Damn, you're right. The guide is missing the part of removing 2 files that the other guides have. I'll try adding that.
Jack_R1 said:
Damn, you're right. The guide is missing the part of removing 2 files that the other guides have. I'll try adding that.
Click to expand...
Click to collapse
Guide fixed. I've uploaded and linked the file that removes the stock recovery restoring files from the stock ROM.
You can repeat the guide and include the new part - it should prevent stock recovery from being restored on reboot.
Please try and write your feedback.
cheers! i've done what was suggested tho', and its worked a treat.
thanks again.
Andy
Related
First off I would like to thank everyone on this amazing site for all the advice, guides and tutorials.
I unlocked my nexus bootloader and flashed a couple different roms. I really like the rom manager so I've used that to download roms and then flash them using that app.
When I downloaded the stock version of 91and flashed it, the phone no longer seemed to have root or clockwork recovery but my bootloader was still unlocked. When I downloaded rom manager, it could not get super user permissions, this being useless in flashing a backup or new rom. So I used universal one click root to gain root access and then rom manager was able to flash a backup.
I know this may be a dumb question but hope someone could explain to me why I needed to re-root and why I lost clockwork recovery...?
Thanks for the help in advance.
cwazynit said:
When I downloaded the stock version of 91and flashed it
Click to expand...
Click to collapse
Right theres your problem. stock roms dont have root built in you have to root them again. unless you download a prerooted stock rom. hope this helps.
cwazynit said:
I know this may be a dumb question but hope someone could explain to me why I needed to re-root and why I lost clockwork recovery...?
Click to expand...
Click to collapse
also it isnt a stupid question its that you didnt know and you wanted to know. when i started i didnt know either. lol.
krypticos said:
Right theres your problem. stock roms dont have root built in you have to root them again. unless you download a prerooted stock rom. hope this helps.
Click to expand...
Click to collapse
Yep this seems to be your problem. If you're wanting stock with the basic add-ons then the first link in this thread is your answer: Link.
Thanks very much. That does make sense. I thought unlocked bootloader meant I was rooted regardless of rom! I'm in way over my head lol. Looking forward to learning more...thanks for the new rom link as well
Sent from my Nexus One using XDA App
cwazynit said:
Thanks very much. That does make sense. I thought unlocked bootloader meant I was rooted regardless of rom! I'm in way over my head lol. Looking forward to learning more...thanks for the new rom link as well
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
The advantage of unlocking your bootloader means you can flash a custom recovery from Fastboot mode, without having to "root" the ROM. Next time this happens you can just boot into fastboot and flash clockwork from there like this:
fastboot flash recovery PATHTO\RECOVERYFILENAME.img
so say you download clockwork and save it to c:\sdk\fastboot named recovery.img from a command prompt you enter the following
cd \sdk\fastboot
fastboot flash recovery recovery.img
once it is done flashing you can do this
fastboot reboot recovery
and that should take you into clockwork where you can flash your favorite ROM (or restore a backup).
Thanks for the help. I will be sure to try that method out next time. Very helpful.
Step by step what I did:
I rooted my tab via this tutorial: http://forum.xda-developers.com/showthread.php?t=812367
I then installed bootstrap (http://forum.xda-developers.com/showthread.php?t=981307), and after going through the steps and restarting I can't get into recovery or anything. It just sits at the logo.
How do I just reset it to factory?
If I completly broke this I think I'm going to puke... Can somebody give me a little bit of hope or help?
obihann said:
Step by step what I did:
I rooted my tab via this tutorial: http://forum.xda-developers.com/showthread.php?t=812367
I then installed bootstrap (http://forum.xda-developers.com/showthread.php?t=981307), and after going through the steps and restarting I can't get into recovery or anything. It just sits at the logo.
How do I just reset it to factory?
Click to expand...
Click to collapse
1st question .. is your tab unlock ?
2nd if not , means you gonna reflash your stock rom again via odin
3th . maybe you can use P1_add_hidden.pit via odin and press start and maybe its work , but 80% its work if didn't work u have to go for step 2
k0sh said:
1st question .. is your tab unlock ?
2nd if not , means you gonna reflash your stock rom again via odin
3th . maybe you can use P1_add_hidden.pit via odin and press start and maybe its work , but 80% its work if didn't work u have to go for step 2
Click to expand...
Click to collapse
My tab is unlocked. So I'm going to have to reflash my stock rom using odin? Where is the best place to track down the froyo rom for my tab?
obihann said:
My tab is unlocked. So I'm going to have to reflash my stock rom using odin? Where is the best place to track down the froyo rom for my tab?
Click to expand...
Click to collapse
I just found these links which may help:
http://forum.xda-developers.com/showthread.php?t=889165
http://forum.xda-developers.com/showthread.php?t=888071
Am I correct these should help?
Obihannm, I did the same yesterday.
You need the original stock firmware for your galaxy and Odin for flash it again.
Look for sam firmware in the google to grab your stock kernel, tools and guides for recovery.
With luck and patience, it is possible ressurrect your tab, but It will back unrooted and maybe you get a locked bootloader.
Just go here and follow attached guide guide.
Thanks guys, I will be up late trying this for sure. I noticed that this probably should live within the QA area not Genreal, so if a Mod or Admin wants to move it, please do.
TheATHEiST said:
Just go here and follow attached guide guide.
Click to expand...
Click to collapse
That would end up with me having gingerbread correct? Should I try to first restore it to factory since right now I can't even enter recovery? Or is it a moot point and I may as well go forward get gingerbread on it?
k0sh said:
1st question .. is your tab unlock ?
2nd if not , means you gonna reflash your stock rom again via odin
3th . maybe you can use P1_add_hidden.pit via odin and press start and maybe its work , but 80% its work if didn't work u have to go for step 2
Click to expand...
Click to collapse
wait by unlocked do you mean rooted? it is rooted but that is it...
obihann said:
That would end up with me having gingerbread correct? Should I try to first restore it to factory since right now I can't even enter recovery? Or is it a moot point and I may as well go forward get honeycomb on it?
Click to expand...
Click to collapse
You dont need to enter any recovery at all. Just "download" mode.
Go and read the guide.
TheATHEiST said:
You dont need to enter any recovery at all. Just "download" mode.
Go and read the guide.
Click to expand...
Click to collapse
OK, a few deep breaths and some "reading" (a new concept for me it seems) later I think I have a bit of a better understanding.
So reading through the overcome guide and a few other threads I think my issue is I must have had a protected bootloader, and that bootstrap program would have frigid that up (there probably was a warning if I slowed down). So that means my issue is my bootloader... Am I correct thus far?
If this is true, does this mean my current rom is actually fine, and fixing my bootloader is my #1 goal?
From there I can insteall the overcome rom, the normal gingerbread rom, or go back to stock? As I see it overcome/gingerbread is the best option.
Just install the stock rom, once back to normal if you have a locked bootloader patch it
All that you need in one handy page
http://forum.xda-developers.com/wiki/index.php?title=File:SamsungGalaxyTab.png
TheATHEiST said:
You dont need to enter any recovery at all. Just "download" mode.
Go and read the guide.
Click to expand...
Click to collapse
I read through the guide you linked to as well as this one (http://forum.xda-developers.com/showthread.php?t=1078622). You suggest I only need to access "download" mode, which I discovered how to do last night. Should Heimdall or other applications be able to see my device via download mode? Or is there a step I am missing.
As well I noticed in the guide you linked me it references patching the bootloader if it is locked, do I need to patch my bootloader or replace it completely as it seems to be broken?
I want to learn this stuff, this I read, and now I am asking. Again all help is appreciated.
Heimdall doesn't seem to do anything at all. I followed the guides as I best understood, and when it came time to hit the start button it instantly said completed with no actual results...
Any ideas?
a coworker was nice enough to help me out, using the stock rom with an unlocked bootloader he was able to bring it back for me. I'm now running froyo, rooted, and a unlocked boot loader so I should have no issues putting overcome on it.
I'm having issues getting the Superuser app to grant root to root apps.
The superuser apk is installed but isn't functioning.
Here's what I did. I was coming from pirateghost's CWM root ROM which was built off the stock developer's ICS OTA update (see my signature). I decided to start over since the sync icon would not go away from the notification tab. I know this is a minor issue but it was very annoying staring at it every time I used the phone.
I did the following:
1) Installed Wildchild's recovery using fastboot
2) Wiped all the data from the phone using wildchild's recovery
3) Locked the bootloader
4) Installed the ATT Stock RUU
5) Unlocked the bootloader
6) Reinstalled wildchild's recovery using fastboot
7) Installed the Superuser apk using wildchild's recovery
Everything is working fine and I don't have the sync icon stuck in the notification tab, but now I can't get any root application to be granted root access. The system just times out when the app is requesting root.
I'm guessing that Wildchild's recovery root is not compatible with the stock ICS release, but is this true? I haven't used the vivid all in one kit because it appears to be using the same method to install root. Everytime you install root it blows away all the data on the phone and makes you start from fresh, so I'm reluctant to try anything unless I'm certain it will work.
Any suggestions from the experts?
Did you look at the last post in the superguide? WC made a post to make rooting easier. Also a video in there as well.
Sent from my HTC PH39100 using XDA
megatronisabeast said:
Did you look at the last post in the superguide? WC made a post to make rooting easier. Also a video in there as well.
Sent from my HTC PH39100 using XDA
Click to expand...
Click to collapse
Yes, this is exactly what I did to the "T", just as in his video. SU is installed on my device but it doesn't grant any privileges to any root apps. I've been digging around searching for answers for about 3 hours and have found many people posting about the same issue but no fix.
3.07 is the latest version of su...redo it with unguarded version see if that works...the rom i used was unrooted and all stock
Wild Child said:
3.07 is the latest version of su...redo it with unguarded version see if that works...the rom i used was unrooted and all stock
Click to expand...
Click to collapse
I saw that and was wondering what "engineering Unguarded superuser" was but didn't know. I guess it's worth a try at this point.
FYI, I used the "Install eng (unguarded) su" and all it did was uninstall the Superuser apk.
Now the root apps respond with a different message when they request root. They don't see the SU app and reply with this statement, before they would hang while they requested SU access.
I'll wait until WC figures out what is going on or just download his ROM.
Are there any known bugs with his ROM?
[email protected] rooting....if going through trouble of unlocking bootloader and flashing a recovery....why not just flash a stock custom rom?....This make no [email protected] do this....Im the first to like completely stock builds,as thats what i use personally...but i cannot stand the at&t bloatware....Main problem with trying to root a stock build is the root access to kernel config....ill upload a stock rooted kernel, if having issues with root after using the recovery you need to install busybox from provided link below.
or flash the boot.img provided.
From original [email protected] guide
- ONCE BOOTED, if you have titanium backup installed but it says there isn't root or busybox isn't installed, download a free app from the market called BUSYBOX INSTALLER. Run this program and proceed in installing busybox. After that, try titanium backup again and it should work.
https://play.google.com/store/apps/...DMsImNvbS5qcnVtbXkuYnVzeWJveC5pbnN0YWxsZXIiXQ..
I had pirateghost's rooted ICS ROM installed but had the sync notification issue. That's why I decided to go back to the stock RUU. I've always been a stock kind of person. I don't know why, but I've always gone back to stock with my phones then rooted it and debloated it myself.
I'm downloading your ROM right now! Since I already have your recovery installed I'm sure this will be a breeze. Thanks!
megatronisabeast said:
Did you look at the last post in the superguide? WC made a post to make rooting easier. Also a video in there as well.
Sent from my HTC PH39100 using XDA
Click to expand...
Click to collapse
I tried using the WCX recovery to install su and I now have super user as one of the apps but Titanium backup could not acquire root privileges.
What am I doing wrong?
samsat said:
I tried using the WCX recovery to install su and I now have super user as one of the apps but Titanium backup could not acquire root privileges.
What am I doing wrong?
Click to expand...
Click to collapse
Look at wild Childs post a couple above this.
Sent from my HTC PH39100 using XDA
Thanks for helping Mega.
I tied installing busybox installer but it says no root access.
Is the stock rooted kernel being referred to boot.zip?
What's the safest way to flash this?
The fastboot flash boot boot.img command is the safest.
samsat said:
Thanks for helping Mega.
I tied installing busybox installer but it says no root access.
Is the stock rooted kernel being referred to boot.zip?
What's the safest way to flash this?
Click to expand...
Click to collapse
Wild Child said:
The fastboot flash boot boot.img command is the safest.
Click to expand...
Click to collapse
I successfully flashed the boot.img file above.
Titanium backup and busybox installer both say no root access.
No apps in superuser.
I really want to get your ROM installed, just this root issue which is stopping me!
Something else is going on then, my rom has nothing to do with this....the roms i release are already rooted and debloated stock builds
samsat said:
I successfully flashed the boot.img file above.
Titanium backup and busybox installer both say no root access.
No apps in superuser.
I really want to get your ROM installed, just this root issue which is stopping me!
Click to expand...
Click to collapse
Samsat, so let's see what you have done so far:
flashed boot.img
flashed recovery
what about the rom? What did you do with that? Was it a zip file from WC's site?
megatronisabeast said:
Samsat, so let's see what you have done so far:
flashed boot.img
flashed recovery
what about the rom? What did you do with that? Was it a zip file from WC's site?
Click to expand...
Click to collapse
Yes done the above but still running RUU ICS stock rom.
samsat said:
Yes done the above but still running RUU ICS stock rom.
Click to expand...
Click to collapse
I would say if you want root, the best thing to do is install one of Wild Child's roms. Once you install it, you will have root. He has an att build just like the att ruu but without the bloat.
http://www.wcxxperia-nce.com/index.php
This is his site. You have to register to see the vivid forum. Also, make sure to read the rules before installing his rom.
Exact process i did and it is rooted with titanium back up working...so flashing from wcxrecovery does work.
Testing procedure:
1 Flashed fastboot oem relock...success
2 Flashed PH39IMG.zip
3 Said Update was complete
4 Phone rebooted
5 My custom ROM was still present
6 Flashed PH39IMG.zip again
7 My custom ROM was still present
8 Attempted running RUU,Failed
9 Entered fastboot via Hboot menu
10 Re ran ruu,ROM updated completely.
11 Ran bootloader unlock command
12 Flashed wcx recovery (provided)
13 Flashed rooted kernel (provided)
14 Booted ROM,fully loaded
15 Rebooted into recovery
16 Installed superuser and su
17 Signed into Market
18 installed stericson Busybox
19 Installed titanium Backup
20 Succesfully rooted with stock att rom
21 Reboot phone after doing said process above Perm root achieved
Thanks WC. I must have been doing the same while you were posting this!
All went according to plan. I now have a rooted phone with unbloated ICS kernel, WCX recovery etc. etc.
Thanks WC, This is great
Well... I was using this http://forum.xda-developers.com/showthread.php?t=1818502 and it works.
Then used http://forum.xda-developers.com/showthread.php?t=1826378
to install the latest CM10.1 nightly file, then failed(some problem with the zip file?), the usb mounting wont work. Then when I reboot recovery I gone back into normal recovery. And I cant install anything nor mount my USB to the default recovery.
Now I'm stuck. Some help please?
KiD3991 said:
Well... I was using this http://forum.xda-developers.com/showthread.php?t=1818502 and it works.
Then used http://forum.xda-developers.com/showthread.php?t=1826378
to install the latest CM10.1 nightly file, then failed(some problem with the zip file?), the usb mounting wont work. Then when I reboot recovery I gone back into normal recovery. And I cant install anything nor mount my USB to the default recovery.
Now I'm stuck. Some help please?
Click to expand...
Click to collapse
You really haven't given much informaton to go on. Basics with any help request;-
What are you trying to achieve?
What version are you running?
What ROM were you on before?
Rooted?
Bootloader locked or unlocked?
What recovery have you installed?
EXACT error message - this is the single most important detail!!
There are plenty of guides around if you are trying to get from 'Stock' to CM10.1;-
Upgrade to 'Stock' JB first
Root
Unlock bootloader
Install CWM (v6.0.3.1)
Install CM from zip
Install gApps from zip
.....
Profit
SimonTS said:
You really haven't given much informaton to go on. Basics with any help request;-
What are you trying to achieve?
What version are you running?
What ROM were you on before?
Rooted?
Bootloader locked or unlocked?
What recovery have you installed?
EXACT error message - this is the single most important detail!!
There are plenty of guides around if you are trying to get from 'Stock' to CM10.1;-
Upgrade to 'Stock' JB first
Root
Unlock bootloader
Install CWM (v6.0.3.1)
Install CM from zip
Install gApps from zip
.....
Profit
Click to expand...
Click to collapse
My bad.
I want to install Cm10.1
running on stock rooted v10e
Rooted yes.
My device is SEA, not sure if I unlocked bootloader...(might be the problem)
The recovery i stated on my question.
I now can only hope lg support tool can help me out.
Because I might forgot bootloader and my device is already wiped out clean(so i cant even return to stock because the whole device is empty).
edit:
Figured out how to enter download mode... haha
Will keep Continue my effort!
I've gone through hell Unlocking Sensation XE, 4X wont beat me!
SimonTS said:
There are plenty of guides around if you are trying to get from 'Stock' to CM10.1;-
Upgrade to 'Stock' JB first
Root
Unlock bootloader
Install CWM (v6.0.3.1)
Install CM from zip
Install gApps from zip
.....
Profit
Click to expand...
Click to collapse
KiD3991 said:
My bad.
I want to install Cm10.1
running on stock rooted v10e
Rooted yes.
My device is SEA, not sure if I unlocked bootloader...(might be the problem)
The recovery i stated on my question.
I now can only hope lg support tool can help me out.
Because I might forgot bootloader and my device is already wiped out clean(so i cant even return to stock because the whole device is empty).
Click to expand...
Click to collapse
Highlighted in red for a very good reason. You'll need to reflash your stock v10e first, yet again there are guides on how to do this. Once you have the phone back up and running on v10e then read carefully and make sure you understand all the steps before trying again
SimonTS said:
Highlighted in red for a very good reason. You'll need to reflash your stock v10e first, yet again there are guides on how to do this. Once you have the phone back up and running on v10e then read carefully and make sure you understand all the steps before trying again
Click to expand...
Click to collapse
Via LG mobile supporter I'm installing 20a or something. Then I will redo it. Thanks for your effort in helping. Hahaha. :good:
Hi, I followed the guide to install CWM and it seemed to go fine, but when I power on the phone and tap the vol-down key nothing happens, I do get the vibrations as I'm doing it though. Is CWM really necessary to install a custom rom? Cos I might just skip it.
You can't flash a custom rom without cwm recovery.
Sent from my C2104 using XDA Free mobile app
karthikys1 said:
You can't flash a custom rom without cwm recovery.
Sent from my C2104 using XDA Free mobile app
Click to expand...
Click to collapse
O lol, I guess I need to solve this then. I thought I just used FlashTool to flash the rom and viola, rom is on.
Does anyone have any ideas what I might be able to try to figure out why CWM isn't working? Any way to see if CWM is actually on my phone? (Maybe it's just not there, rather then not working).
Edit: Rom Manager seems to think I have CWM installed, also I did a Nandroid Backup which seemed to be configured to use CWM so I don't know if it's there or not, or working or not
Which guide did you follow? And how did you make a Nandroid Backup?
I followed this guide.
I downloaded Nandroid Backup Root, it created the backup without rebooting the phone, so it never needed to boot into CWM.
Astralogic said:
I followed this guide.
I downloaded Nandroid Backup Root, it created the backup without rebooting the phone, so it never needed to boot into CWM.
Click to expand...
Click to collapse
That's what I thought. The fact that it can create a backup doesn't mean it has a recovery installed, it doesn't use a recovery to create it. If the LED is lighting up at boot, and it is vibrating, and it doesn't get back in, I don't know what the problem would be. I'd try reinstalling CWM, and FYI, you should use V8; V9 has issues.
At the very least, if it really is installed, you should have a "recovery.tar" and "chargemon" file in /system/bin/.
Antiga Prime said:
That's what I thought. The fact that it can create a backup doesn't mean it has a recovery installed, it doesn't use a recovery to create it. If the LED is lighting up at boot, and it is vibrating, and it doesn't get back in, I don't know what the problem would be. I'd try reinstalling CWM, and FYI, you should use V8; V9 has issues.
At the very least, if it really is installed, you should have a "recovery.tar" and "chargemon" file in /system/bin/.
Click to expand...
Click to collapse
I don't have those files so CWM is not installed. I can't find v8 of CWM for Xperia T but I found this file "CWM4XperiaT_v8i_JB.zip", is that it?
Astralogic said:
I don't have those files so CWM is not installed. I can't find v8 of CWM for Xperia T but I found this file "CWM4XperiaT_v8i_JB.zip", is that it?
Click to expand...
Click to collapse
It clearly says "Xperia T" in the name of that file... yes, that's it. Now I'm wondering what you installed, if you didn't install that one, or V9.
Antiga Prime said:
It clearly says "Xperia T" in the name of that file... yes, that's it. Now I'm wondering what you installed, if you didn't install that one, or V9.
Click to expand...
Click to collapse
V8 works perfectly, it's installed fine.
I am going to follow this guide to install cyanogenmod, do I need to obtain a bootloader unlock code? Or should I just skip right to installing the ROM?
Edit: Oops forgot the link: http://wiki.cyanogenmod.org/w/Install_CM_for_mint
Astralogic said:
V8 works perfectly, it's installed fine.
I am going to follow this guide to install cyanogenmod, do I need to obtain a bootloader unlock code? Or should I just skip right to installing the ROM?
Edit: Oops forgot the link: http://wiki.cyanogenmod.org/w/Install_CM_for_mint
Click to expand...
Click to collapse
First of all, yes, you need an unlocked bootloader. You can't flash custom kernels on a locked bootloader. Secondly, I've never tried that tutorial (I have a TX), but I'm assuming it should work fine, but, personally I'd either go with FXP, or one of the OMNI builds here in XDA, since, as far as I know, developers here have more fixes than what I've seen on FXP and/or CM.
Also, there are a easier ways to flash your ROM, since you already have a custom ROM. I don't think it's necessary to have to fastboot the kernel first.
Edit: The Carbon ROM I'm on also has a T version. The reason I'm on this ROM (and previously OMNI) was because FXP/CM roms have/had a battery drain that was never fixed, something that was fixed here on XDA.
Antiga Prime said:
First of all, yes, you need an unlocked bootloader. You can't flash custom kernels on a locked bootloader. Secondly, I've never tried that tutorial (I have a TX), but I'm assuming it should work fine, but, personally I'd either go with FXP, or one of the OMNI builds here in XDA, since, as far as I know, developers here have more fixes than what I've seen on FXP and/or CM.
Also, there are a easier ways to flash your ROM, since you already have a custom ROM. I don't think it's necessary to have to fastboot the kernel first.
Edit: The Carbon ROM I'm on also has a T version. The reason I'm on this ROM (and previously OMNI) was because FXP/CM roms have/had a battery drain that was never fixed, something that was fixed here on XDA.
Click to expand...
Click to collapse
There's a problem My bootloader is not unlockable... does this mean I've been wasting my time?
Edit: There is this guide, it makes no mention of unlocking the bootloader so it might work?
Astralogic said:
There's a problem My bootloader is not unlockable... does this mean I've been wasting my time?
Edit: There is this guide, it makes no mention of unlocking the bootloader so it might work?
Click to expand...
Click to collapse
No, that tutorial won't work. Never follow a guide for flashing ROMs that wasn't meant for your phone. Your phone didn't even exist yet when that guide was written.
If you can't unlock your bootloader then there is no way you'll ever be able to flash a custom ROM, because, like I mentioned earlier, custom ROMs have custom kernels, and custom kernels need an unlocked bootloader.
I wouldn't consider it a waste, it's always useful to have a recovery installed; with it you can at the very least backup and restore, flash deodexed/zipaligned stock ROMs, such as this one, flash files, and even have access to ADB if your phone doesn't boot up, which can save you from having to wipe everything, etc., so not a complete waste of time.
Antiga Prime said:
No, that tutorial won't work. Never follow a guide for flashing ROMs that wasn't meant for your phone. Your phone didn't even exist yet when that guide was written.
If you can't unlock your bootloader then there is no way you'll ever be able to flash a custom ROM, because, like I mentioned earlier, custom ROMs have custom kernels, and custom kernels need an unlocked bootloader.
I wouldn't consider it a waste, it's always useful to have a recovery installed; with it you can at the very least backup and restore, flash deodexed/zipaligned stock ROMs, such as this one, flash files, and even have access to ADB if your phone doesn't boot up, which can save you from having to wipe everything, etc., so not a complete waste of time.
Click to expand...
Click to collapse
Ok, well, I learned a bit in the process, and I still have an Xperia SP bootloader to unlock, then flash cyanogenmod, so I'm in a better position to handle that now, thanks for all the help guys.