Downgraded, rooted, now want to install.... quick question.

T

thefunkygibbon

Senior Member

Sep 17, 2004

856

66

Samsung Galaxy Tab S2

Samsung Galaxy S20

• Jun 11, 2014

• #1

Hi, thanks for reading,

Ok so my 6903 z1, i've downgraded it to .534, rooted it, installed dualrecovery and am sitting here wondering where to go next.
I wouldn't mind unlocking the bootloader so that I could install other kernels such as pimped kernel. But reading the dualrecovery thread it seems that it is only if you are using the original kernel. So my main question is, what should i do next?

use recovery to flash a zip of a new rom then unlock bootloader then flash a supported recovery?
or should i unlock bootloader now and then new rom etc? (was concerned about the camera issue unlocking the bootloader on <4.3 roms.... will it be "fixed" if i was running on a newer "flashed via recovery" ROM?)

any help is appreciated as I don't want to bugger up the phone like i somehow managed to last time i tried all this (had the IMEI disappearing issue)

 

gregbradley

Retired Forum Moderator

Mar 23, 2011

12,038

6,495

Probably marking work or drinking beer...Maybe bot

• Jun 11, 2014

• #2

If you want to unlock the boot, there is was no need to downgrade to root

Just backup your TA, unlock the boot, flash a custom kernel of your choice then flash away

 

T

thefunkygibbon

Senior Member

Sep 17, 2004

856

66

Samsung Galaxy Tab S2

Samsung Galaxy S20

• Jun 11, 2014

• #3

oh ok. well i've done it now. although I've just checked my service menu

First, you should confirm that it is possible to unlock the boot loader of your phone by checking the service menu. In your phone, open the dialler and enter *#*#7378423#*#* to access the service menu.

In your phone, tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.

Click to expand...

Click to collapse

and it says bootloader unlock allowed: No

So i'm guessing I randomly cannot unlock it anyway? (any reason why if that is the case?)

 

eclyptos

Senior Member

Jun 14, 2008

3,040

640

Planet Earth

• Jun 11, 2014

• #4

thefunkygibbon said:

oh ok. well i've done it now. although I've just checked my service menu


and it says bootloader unlock allowed: No

So i'm guessing I randomly cannot unlock it anyway? (any reason why if that is the case?)

Click to expand...

Click to collapse

If that it saying then no way around to unlock your bootloader. BTW, stock kernel isn't that bad and with root you will be able to customize your room and get some tweeks.

 

T

thefunkygibbon

Senior Member

Sep 17, 2004

856

66

Samsung Galaxy Tab S2

Samsung Galaxy S20

• Jun 11, 2014

• #5

eclyptos said:

If that it saying then no way around to unlock your bootloader. BTW, stock kernel isn't that bad and with root you will be able to customize your room and get some tweeks.

Click to expand...

Click to collapse

so if i cannot unlock bootloader, does that mean i wont be able to use custom roms like Paranoid android etc which run off of CM and presumably a CM kernel?

 

T

thefunkygibbon

Senior Member

Sep 17, 2004

856

66

Samsung Galaxy Tab S2

Samsung Galaxy S20

• Jun 11, 2014

• #6

and is it worth trying to unlock the bootloader in flashtool anyway just to see?

What options/next steps do i have then if i cant flash a custom rom due to not being able to use a different kernel?

Guess i can flash a modified stock rom and thats about it?

 

eclyptos

Senior Member

Jun 14, 2008

3,040

640

Planet Earth

• Jun 11, 2014

• #7

thefunkygibbon said:

so if i cannot unlock bootloader, does that mean i wont be able to use custom roms like Paranoid android etc which run off of CM and presumably a CM kernel?

Click to expand...

Click to collapse

Unfortunately No, anything based on Custom Kernels you cannot install. Everything based on Stock Kernel you can Install, even Custom Roms.

 

T

thefunkygibbon

Senior Member

Sep 17, 2004

856

66

Samsung Galaxy Tab S2

Samsung Galaxy S20

• Jun 11, 2014

• #8

oh bloody hell. ok so i'm now stuck in a sony logo boot loop after installing romaur v8 and installing the kernel (561) which it told me to.

any ideas what to do? guessing i'm going to have to flash the old 4.2.2 rom from scratch again

 

T

thefunkygibbon

Senior Member

Sep 17, 2004

856

66

Samsung Galaxy Tab S2

Samsung Galaxy S20

• Jun 11, 2014

• #9

ok so now i'm back to .534 [nut] and rooted. any tips on where to go next so that i dont get stuck in another bootloop???

 

eclyptos

Senior Member

Jun 14, 2008

3,040

640

Planet Earth

• Jun 12, 2014

• #10

thefunkygibbon said:

ok so now i'm back to .534 [nut] and rooted. any tips on where to go next so that i dont get stuck in another bootloop???

Click to expand...

Click to collapse

Just any Rom based on Stock Kernel.

 

T

thefunkygibbon

Senior Member

Sep 17, 2004

856

66

Samsung Galaxy Tab S2

Samsung Galaxy S20

• Jun 15, 2014

• #11

eclyptos said:

Just any Rom based on Stock Kernel.

Click to expand...

Click to collapse

I thought the romaur rom Was based on stock. Ho hum. Installed the pure stock one and it was OK thanks.

 

punkt

Senior Member

Jul 2, 2008

515

172

• Jun 15, 2014

• #12

In Android developement thread all roms are based on stock - in original Android developement they are based on pure android.
Bootlooping is mostly caused when flashing wrong bootbundle/kernel.

Sent from my C6903 using XDA Premium 4 mobile app

 

eclyptos

Senior Member

Jun 14, 2008

3,040

640

Planet Earth

• Jun 16, 2014

• #13

@punkt, nice your avatar, that is what I call HD..lol..