Disabling secure boot

Search This thread
By:
Advanced…
V

vrushabh sutar

Senior Member
Mar 5, 2014
56
35
Ahmedabad
firstly i request all moderators of xda in grand 2 forum,
as i am unable to post on developement section,
i am posting the thread here..
plz move it to developement section.

ok now back to topic,

try at your own risk!
i will not be responsible if anything happens to your phone

To all the users who have succesfully rooted grand 2,

there can be a way to install (flash) recovery on your phone!

i was exploring the system and i found a file in "/system" folder
called "recovery-from-boot.p"

i THINK this is the file that causes problem!


you may delete it or rename it...(renaming is safer)
once you delete it, you may flash custom recovery via ODIN
and even if the recovery gets currupted or if you cant boot into recovery, you can simply boot normally and restore the renamed or deleted file!!! ;)

and then once again you may try to flash custom recovery from ODIN (as stock gets deleted as soon as you modify recovery-from-boot.p file)


press thanks if this post helped!
 
Last edited:
  • Like
Reactions: vandroid699
V

vrushabh sutar

Senior Member
Mar 5, 2014
56
35
Ahmedabad
how would u know that it won't help..
i only post threads as i know what i am doing.
the file which i uploaded up there is taken from MY PHONE ITSELF i.e galaxy GRAND 2..
and That FILE (recovery-from-boot.p) IS present on my phone and i m using Stock rom and not any other rom..
 
V

vrushabh sutar

Senior Member
Mar 5, 2014
56
35
Ahmedabad
it only appears on a Stock UN-ROOTED firmware..
In order to inject custom CWM there isnt a necessity to root device.
so firstly we need to remove file that I mentioned in my previous post and inject recovery.
and via that recovery,
we can flash a custom kernel that automatically roots device!
 
Last edited:
0

00hacktheworld00

Senior Member
Mar 7, 2013
53
34
Bangalore
vrushabh sutar said:
it only appears on a Stock UN-ROOTED firmware..
In order to inject custom CWM there isnt a necessity to root device.
so firstly we need to remove file that I mentioned in my previous post and inject recovery.
and via that recovery,
we can flash a custom kernel that automatically roots device!
Click to expand...
Click to collapse

Dude, if the FILE just appears in STOCK UNROOTED FIRMWARE , so how can we delete that.
Coz, to delete a /system file, we need ROOT access.

NOT POSSIBLE.
And in rooted version, the FILE is not available :victory:
 
V

vrushabh sutar

Senior Member
Mar 5, 2014
56
35
Ahmedabad
00hacktheworld00 said:
Dude, if the FILE just appears in STOCK UNROOTED FIRMWARE , so how can we delete that.
Coz, to delete a /system file, we need ROOT access.

NOT POSSIBLE.
And in rooted version, the FILE is not available :victory:
Click to expand...
Click to collapse
Thank you for replying.
I know that it can't be deleted,
but one may understand the importance of that ".p" file and understand its working, as it plays a vital role in booting up recovery...

the only thing I wanna let users understand is that,
stock recovery includes that file and
it got deleted when rooted because the rooting package (eg. CF root) didnt contain the .p file

when I studied that strange file,
it consisted of mapping and accurate memory address as well as accurate size of stock recovery image in bytes,
so that whn new recovery gets flashed, it verifies with the .p file!

and talking abt modifying the .p file,
we must create a custom linux binary with zerglings and packed into .tar file which gets flashed to phone via Odin!
 
  • Like
Reactions: vandroid699 and manan001
manan001

manan001

Senior Member
Sep 16, 2011
2,363
494
Ahmedabad
mananbhatt86.blogspot.in
OnePlus 7T
OnePlus 11
  • Like
Reactions: Sagar_Patel and vandroid699
mobihack

mobihack

Senior Member
Mar 16, 2014
178
58
Ottapalam, Palakkad
So I found the reason behind this ;)
It is a file used by Software Update Application to flash updates.
If you want proof go-to the data folder of the SOFTWARE UPDATER and there will be a 3mb file. Copy it to pc and open using winrar. You can see many files including boot.img.
So the author of this thread was about to update his/her phone when he found the file :thumbdown:

SO MYSTERY SOLVED :cool:
SCOOBY DOOBY DOOO :D

Sent from my SM-G7102
 
  • Like
Reactions: Sagar_Patel
V

vrushabh sutar

Senior Member
Mar 5, 2014
56
35
Ahmedabad
i didnt't get what you are on to...

i noticed that the Update Package (i.e the OTA) easily jumps over all the restrictions imposed by Bootloader(locked one) and gets easily flashed to the phone...
therefore the whole matter is now pointing out to the 'ro.build.fingerprint' as well as Verification of MD5 hashes linked directly to Flashing InstructionSet
 
  • Like
Reactions: vandroid699
You must log in or register to reply here.

Similar threads

Y
[ROM] AOKP - 7.1 2. [FULLY STABLE] August Security Pacth
Replies
81
Views
58K
D
darwasha1
D
Sm-g7102 service manual(dead boot repair guide)
Replies
3
Views
29K
J
jaiswalnilesh
V
Qualcomm MSM boot process
Replies
9
Views
13K
V
vrushabh sutar
N
how to disable Grand 2 screen lock and unlock with flip cover?
Replies
9
Views
14K
citBabY
citBabY
G
  • Poll
Lag Fix& Boost Performance (Game&app) for any rom (compatible with all device)
Replies
66
Views
21K
A
anjel05

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 2
    V
    vrushabh sutar
    00hacktheworld00 said:
    Dude, if the FILE just appears in STOCK UNROOTED FIRMWARE , so how can we delete that.
    Coz, to delete a /system file, we need ROOT access.

    NOT POSSIBLE.
    And in rooted version, the FILE is not available :victory:
    Click to expand...
    Click to collapse
    Thank you for replying.
    I know that it can't be deleted,
    but one may understand the importance of that ".p" file and understand its working, as it plays a vital role in booting up recovery...

    the only thing I wanna let users understand is that,
    stock recovery includes that file and
    it got deleted when rooted because the rooting package (eg. CF root) didnt contain the .p file

    when I studied that strange file,
    it consisted of mapping and accurate memory address as well as accurate size of stock recovery image in bytes,
    so that whn new recovery gets flashed, it verifies with the .p file!

    and talking abt modifying the .p file,
    we must create a custom linux binary with zerglings and packed into .tar file which gets flashed to phone via Odin!
    View
    2
    manan001
    manan001
    for build creation you can use this tool..

    http://www.xda-developers.com/android/comprehensive-guide-to-the-android-build-process/?__utma=60652090.747738090.1398670920.1400078979.1400132113.21&__utmb=60652090.0.10.1400132113&__utmc=60652090&__utmx=-&__utmz=60652090.1400132113.21.12.utmcsr=google|utmccn=%28organic%29|utmcmd=organic|utmctr=%28not%20provided%29&__utmv=-&__utmk=163283131
    View
    1
    V
    vrushabh sutar
    firstly i request all moderators of xda in grand 2 forum,
    as i am unable to post on developement section,
    i am posting the thread here..
    plz move it to developement section.

    ok now back to topic,

    try at your own risk!
    i will not be responsible if anything happens to your phone

    To all the users who have succesfully rooted grand 2,

    there can be a way to install (flash) recovery on your phone!

    i was exploring the system and i found a file in "/system" folder
    called "recovery-from-boot.p"

    i THINK this is the file that causes problem!


    you may delete it or rename it...(renaming is safer)
    once you delete it, you may flash custom recovery via ODIN
    and even if the recovery gets currupted or if you cant boot into recovery, you can simply boot normally and restore the renamed or deleted file!!! ;)

    and then once again you may try to flash custom recovery from ODIN (as stock gets deleted as soon as you modify recovery-from-boot.p file)


    press thanks if this post helped!
    View
    1
    mobihack
    mobihack
    So I found the reason behind this ;)
    It is a file used by Software Update Application to flash updates.
    If you want proof go-to the data folder of the SOFTWARE UPDATER and there will be a 3mb file. Copy it to pc and open using winrar. You can see many files including boot.img.
    So the author of this thread was about to update his/her phone when he found the file :thumbdown:

    SO MYSTERY SOLVED :cool:
    SCOOBY DOOBY DOOO :D

    Sent from my SM-G7102
    View
    1
    V
    vrushabh sutar
    i didnt't get what you are on to...

    i noticed that the Update Package (i.e the OTA) easily jumps over all the restrictions imposed by Bootloader(locked one) and gets easily flashed to the phone...
    therefore the whole matter is now pointing out to the 'ro.build.fingerprint' as well as Verification of MD5 hashes linked directly to Flashing InstructionSet
    View

New posts