The XDA LG QPair Developer Challenge Voting Has Begun!

It seems like it was just yesterday that weannounced that we had paired up with LGto … more

Major Update for the Sony Smartwatch 2 Brings DND and More

With the wearables landscape now dominated by Android Wear and Pebble, its … more

How to Root Android Wear 5.0.1 Lollipop Devices – XDA TV

The Lollipop update for Android Wear devices has hit the market and people are … more

Android 5.0.2 and New Factory Images For Nexus 7 (Wi-Fi) Available

Android 5.0 is has been publicly available since early November, and the … more

Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

[DEV][THINK TANK] Two step booting process on the Z2?

OP DooMLoRD

3rd June 2014, 07:52 AM   |  #21  
DooMLoRD's Avatar
OP Recognized Developer
Flag Noida
Thanks Meter: 39,110
 
13,127 posts
Join Date:Joined: Jul 2010
Quote:
Originally Posted by adfad666

Z2 is definitely aligned to the power button, like the rear logo too!

Attachment 2777337

ya exactly! i was just going to say the same thing!

(sorry for OT)


coming back to the topic... can we actually use this in some way?
5th June 2014, 09:38 PM   |  #22  
Junior Member
Thanks Meter: 0
 
19 posts
Join Date:Joined: Jul 2012
So on this two step booting process, is that why I somehow have TWO recoveries installed at the same time? I installed DoomKernel as part of my original rooting process. I then installed Monx Rom, which installed TWRP. Using Rom Manager, I tried to put CWM back. Now, whenever I reboot to recovery, CWM will come up, but when I reboot system from CWM, it boots to TWRP. From there, when I reboot system, it then boots up to system. Some weird side effects to this too. I lose some installed apps when I finally get back to Android. RSA Secure ID and Go Launcger Ex seem to be the two that are constantly being "forgotten" when I go through this cycle. Also, I did a "Erase SD" from the settings menu. All was good, Ext SD was functioning fine, nice and clean. Then, Reboot recovery and go through the who double recovery cycle and WHAM! My ext sd has ALL the data I erased back on it.

So, is this double boot process you speak of responsible for this behavior?

Thanks,

-Hans
5th June 2014, 09:48 PM   |  #23  
DooMLoRD's Avatar
OP Recognized Developer
Flag Noida
Thanks Meter: 39,110
 
13,127 posts
Join Date:Joined: Jul 2010
Quote:
Originally Posted by Hans.physics

So on this two step booting process, is that why I somehow have TWO recoveries installed at the same time? I installed DoomKernel as part of my original rooting process. I then installed Monx Rom, which installed TWRP. Using Rom Manager, I tried to put CWM back. Now, whenever I reboot to recovery, CWM will come up, but when I reboot system from CWM, it boots to TWRP. From there, when I reboot system, it then boots up to system. Some weird side effects to this too. I lose some installed apps when I finally get back to Android. RSA Secure ID and Go Launcger Ex seem to be the two that are constantly being "forgotten" when I go through this cycle. Also, I did a "Erase SD" from the settings menu. All was good, Ext SD was functioning fine, nice and clean. Then, Reboot recovery and go through the who double recovery cycle and WHAM! My ext sd has ALL the data I erased back on it.

So, is this double boot process you speak of responsible for this behavior?

Thanks,

-Hans

No

Sent from my D6503 using XDA Free mobile app
5th June 2014, 10:14 PM   |  #24  
defsix's Avatar
Senior Member
Thanks Meter: 73
 
419 posts
Join Date:Joined: Aug 2011
Quote:
Originally Posted by Hans.physics

So on this two step booting process, is that why I somehow have TWO recoveries installed at the same time? I installed DoomKernel as part of my original rooting process. I then installed Monx Rom, which installed TWRP. Using Rom Manager, I tried to put CWM back. Now, whenever I reboot to recovery, CWM will come up, but when I reboot system from CWM, it boots to TWRP. From there, when I reboot system, it then boots up to system. Some weird side effects to this too. I lose some installed apps when I finally get back to Android. RSA Secure ID and Go Launcger Ex seem to be the two that are constantly being "forgotten" when I go through this cycle. Also, I did a "Erase SD" from the settings menu. All was good, Ext SD was functioning fine, nice and clean. Then, Reboot recovery and go through the who double recovery cycle and WHAM! My ext sd has ALL the data I erased back on it.

So, is this double boot process you speak of responsible for this behavior?

Thanks,

-Hans

Quote:
Originally Posted by DooMLoRD

No

Sent from my D6503 using XDA Free mobile app

LOL !

As for the dual recovery problem, i'd a similar problem on a Sony Tablet S , one boot cycle i had root and X number of apps, on the second boot i had no root and Y number of apps.
Factory reset , full re-flash, factory reset and finally root was the only way I got it back to normal.
6th June 2014, 11:28 AM   |  #25  
vishal_android freak's Avatar
Recognized Developer / Recognized Contributor
Flag Mumbai
Thanks Meter: 5,285
 
1,784 posts
Join Date:Joined: Dec 2012
More
Quote:
Originally Posted by Hans.physics

So on this two step booting process, is that why I somehow have TWO recoveries installed at the same time? I installed DoomKernel as part of my original rooting process. I then installed Monx Rom, which installed TWRP. Using Rom Manager, I tried to put CWM back. Now, whenever I reboot to recovery, CWM will come up, but when I reboot system from CWM, it boots to TWRP. From there, when I reboot system, it then boots up to system. Some weird side effects to this too. I lose some installed apps when I finally get back to Android. RSA Secure ID and Go Launcger Ex seem to be the two that are constantly being "forgotten" when I go through this cycle. Also, I did a "Erase SD" from the settings menu. All was good, Ext SD was functioning fine, nice and clean. Then, Reboot recovery and go through the who double recovery cycle and WHAM! My ext sd has ALL the data I erased back on it.

So, is this double boot process you speak of responsible for this behavior?

Thanks,

-Hans

Afaik, rom manager will install a recovery. tar format of recovery which works on chargemon hacking. Bcz we don't have a separate partition for recovery here. So that's why cwm exist in your system and twrp in your kernel :P

Sent from my Nexus 5 using Tapatalk
6th June 2014, 10:50 PM   |  #26  
waynekirby's Avatar
Senior Member
Flag Barnsley
Thanks Meter: 479
 
930 posts
Join Date:Joined: Nov 2010
Donate to Me
More
Quote:
Originally Posted by vishal_android freak

Afaik, rom manager will install a recovery. tar format of recovery which works on chargemon hacking. Bcz we don't have a separate partition for recovery here. So that's why cwm exist in your system and twrp in your kernel :P

Sent from my Nexus 5 using Tapatalk

But we have FOTA kernel partition do we not? Wouldn't we be able to utilise that for dualbooting?

Sent from my D6503 using Tapatalk
8th June 2014, 12:26 PM   |  #27  
Member
Thanks Meter: 4
 
34 posts
Join Date:Joined: Sep 2011
Quote:
Originally Posted by waynekirby

But we have FOTA kernel partition do we not? Wouldn't we be able to utilise that for dualbooting?

Sent from my D6503 using Tapatalk

I was just thinking about this while looking at the ROMs on offer at the moment. The googymax kernel I had on my S3 was great as it allowed me to use a stock ROM I could quickly boot in to and record in amazing quality instead of the custom ROM as that used the CM camera which couldn't use the same drivers as the official camera. The kernel also messed with my partitions and uninstalling it led me to have two recoveries, a CWM and a TWRP.

I'd love to see multiboot so I still have the bonus of a custom ROM but still have the option to boot to stock if I want better camera stuff.
1st October 2014, 12:25 PM   |  #28  
Member
Thanks Meter: 4
 
58 posts
Join Date:Joined: Jul 2014
Quote:
Originally Posted by DooMLoRD

Hey guys I dont know how many of you have noticed this but the Xperia Z2 has a "two step" booting process... first an initial kernel is booted, the one which shows the "Sony" logo.. and after that the custom kernel get booting... it might be using some sort of Kexec may be?

i noticed this when i saw that it was taking longer in boot process and it was not showing my custom bootlogo... so i investigated and this is waht i found in the dmesg:

Code:
root@D6503:/ # dmesg | grep logo
dmesg | grep logo
<6>[    3.378925] Skip drawing logo. Already drawn in boot.
<3>[    9.679902] init: cannot open '/initlogo.rle'
if i compare it against the Z1:
Code:
root@C6902:/ # dmesg | grep logo
dmesg | grep logo
<6>[    4.366685] Drawing logo.
<3>[   10.875083] init: cannot open '/initlogo.rle'
root@C6902:/ #
i have hacked the code to show my custom bootlogo so i am happy but it might be interesting to see what we can do if we can access that "base kernel"... may be we can explore proper multi-boot solutions?


what do you guys think?




P.S.: this is ment ONLY for DEVELOPERS to discuss... noobs/thank-you posts ARE NOT WELCOME!

only post if you have something useful to contribute...



regards,

DooMLoRD

Do you know how can I disable that sony boot logo?

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes