It's time to bring warranty back Just flash attached file using CWM and here you are!
If you prefer a manual way then type the following line in terminal (or using adb shell):
Code:
dd if=/dev/zero of=/dev/block/mmcblk0 bs=1 count=1 seek=3145732
Be EXTREMELY careful if you're typing this manually. One mistake can brick your phone!
Confirmed to work with Gingerbread and JellyBean.
Would this trick work in Gingerbread? Did you get Custom binary: NO?
I still have virgin counter, but I assume that many users may ask about his.
Antsm, once again you are the first one, who finds new areas in i8160 cracking (root, CWM and now Flash Counter). Good job! :good:
Works - Thank's
Before i had the counter in 34 , after 0 (NO) , is a good change.(CWM)
Flash failed ( TWRP )
Maybe u can beat me in English , but im not sure that u can beat me in mandarin
Same here, Error flashing zip with TWRP. But the command works great. Thanks mate.
arroyo said:
Would this trick work in Gingerbread? Did you get Custom binary: NO?
Click to expand...
Click to collapse
Absolutely
BTW, i had something like 145 before
Rikxzdjz
Sigint89,
Something in updater-script needs to be correct in order to use it with TWRP.
I'll check it ASAP (need to install TWRP kernel) or maybe someone will be more rapid :laugh:
However, it would be nice to look at recovery log.
Thanks a lot, we really need this!
Wow thanks antsm. Works great!!
PS: Try the attached zip if you have TWRP. I am not sure if it works. I just changed the update-binary. (Works fine in CWM btw)
Edit: Attachment removed
But we still have "Current binary: Custom", isn't it ?
I think we have to patch checksum too, not 300004 only
avkiev said:
But we still have "Current binary: Custom", isn't it ?
I think we have to patch checksum too, not 300004 only
Click to expand...
Click to collapse
No. I have:
Custom Binary Download: No
Current Binary: Samsung Official
with ofc, custom kernel installed in my phone.
I don't know why TWRP won't save recovery log but i wrote it from screen:
http://pastebin.com/Ti5bGqQi
And i have "Current binary: Custom" after using terminal command, I'll try Kyrillos' zip in a moment and post results.
Results: Now it gives "Can't copy META-INF/com/google/android/..." error.
Need to flash a stock sammy kernel to get:
Current Binary: Samsung Official
Click to expand...
Click to collapse
Not a big deal. Anyway, i'll check what can be done.
antsm said:
Need to flash a stock sammy kernel to get:
"Current Binary: Samsung Official "
Click to expand...
Click to collapse
Yes, excellent
As I do not have CWM or TWRP, I tried the console command with the "Shell Terminal Emulator" and it says "cannot open for writeermission denied".
It did not ask for admin rights or something ... what did I forget?
did you type "su", to get superuser permission?
Thanks, that seemed to help. For the records, I had to type
su dd if=/dev/zero of=/dev/block/mmcblk0 bs=1 count=1 seek=3145732
Click to expand...
Click to collapse
cbolumar said:
Before i had the counter in 34 , after 0 (NO) , is a good change.(CWM)
Click to expand...
Click to collapse
How and where can I check if the counter is zero ..... where do you see this?
Okay, setting byte at offset 0x300008 to 0x01 goes to:
"Current Binary: Custom"
Click to expand...
Click to collapse
setting to 0x02 goes to:
"Current Binary: Samsung Official"
Click to expand...
Click to collapse
I'll update zip file in the first post as soon as i fix TWRP issue.
Excellent!
Kudos for your work antsm!!!
kyrillos13 said:
I am not sure if it works. I just changed the update-binary. (Works fine in CWM btw)
Click to expand...
Click to collapse
You've put me on the right way! Just downloaded latest update-binary from TWRP home and it works like a charm
I also added reset of "Current Binary" status. First post updated.
Related
NOTICE
As i no longer own this tab, i will no longer be providing support for it.
As devhost is slowly and surely deleting my files, i have moved them
to androidfilehost https://www.androidfilehost.com/?w=files&flid=23547
As androidfilehost does not delete files, these recoveries will remain hosted indefinitely.
m
Update 1 Uploaded - Choose v2
i am doing a new build as i may have missed setting support for extended attributes.
will update shortly.
v2 is up - link updated
changed default security module to selinux and modified source /bootable/recovery-cm/updater/install.c
as follows:
<cm11 source dir>/bootable/recovery-cm/updater/install.c
in line 586 (under the function ParsePermArgs(int argc, char** args):
654:- parsed.has_capabilities = true;
654:+ parsed.has_capabilities = false;
mainly for testing. still functional as before.
on v2
okay,
i have been using v2 quite a lot since i posted it and it works pretty solidly.
A major note- to flash supersu update zip you must use most recent version from chainfire's site.
The adb experience is good provided you remember to mount data and system.
I will be getting to Philz Advanced after a little more practice with building.
Right now my attempt in th recovery arena will be to get aromafm built and working.
Both versions of my cwm build will remain posted.
m
edit- uploaded v2 Alien - i know, it's goofy but it looks pretty cool. =)
Philz Adv CWM 6.55.0 - CWM 6.0.5.0
sorted.
screen shots
Philz Adv CWM - Update August 2, 2014
Before all other things, @Hazou , Dude you rock !!
Unending thanks to @Phil3759 for making your source available.
okay so this is Philz Advanced Touch for GT-P5210 [fixed, no lag].
If anyone needs CWM rebuilt let me know.
This time i have released it in a flashable zip [CWM]. I wil be pulling the clunky one [Philz]
And with that, I think I am done with recovery building for now. Enjoy
the name of the file is PhilzAdvCWM-6_55_0-gtp-5210.zip. See OP for link.
m
AROMAFM
yup, aromafm :victory:
okay so,
issues are lag, resolution and possibly a ram related crash, in which event, force reboot [will return you to recovery] and then reboot normally.
i'm working on it. NOTE- enabling automount seems to reduce occurence of crash/hang.
in terminal ~#whoami
returns ~#uid0 :good:
busybox :good:
see OP for link. this is an initial offering and requires work.
thanks a million times to @amarullz for making his source available
thanks to @Hazou as ever :good:
please pm me to report bugs and issues. enjoy !
m
TWRP v2.7.1.0 for GT-P5210
Reserved for TWRP
Will be attemtping to improve/fix/sort terminal.
Didn't want to be unfair to TWRP users.
Will update.
m
Thanks @Siberian Tiger :good:
Okay so, TWRP is up. See OP for link.
I am still looking for what i need to know to make the terminal in twrp a less-suck experience.
No lag and, I am actually starting to like TWRP alot. I have tested on my tab, backup/recovery are good. aromafm installs and runs well. adb seems to be in order. I did trim the fstab leaving system, data/internal storage, cache, recovery, boot and external storage.
If other variants need different setup please let me know.
As always please do not post thank-you's. Bugs and issues only.
thank you for reading
m
Notes
I did not generate any new or additional code.
All sources are already available - CWM, PHILZ, TWRP, AROMAFM
However the patches applied to cm11 build environment are
@Hazou , infinitely thankable :good:
https://github.com/HazouPH/android_system_core/commit/54cf228097d58713d71a13a6c79794bfa373eab0
https://github.com/HazouPH/android_device_motorola_smi/blob/jellybean/patch/cwm_0001.patch
m
if i try to flash philz it keep saying my device is santos103g and not santos10wifi
i have 100% sure gt-p5210 it is on the back of the tablet
damian312 said:
if i try to flash philz it keep saying my device is santos103g and not santos10wifi
i have 100% sure gt-p5210 it is on the back of the tablet
Click to expand...
Click to collapse
hi,
you need to follow this thread from first post, hear me out,
you must first download, extract to /sdcard and dd write cwm 6.0.5.0 [recovery.img] with the following terminal command
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p11
from that point you can flash philz normally. the assert in the updater script is correct. it calls to your
/system/build.prop
and verifies whether or not you have the correct device. The issue is with your process and your build prop.
if you are unable to resolve the issue, you may extract the recovery.img from the zip and write it in the same
fashion as cwm 6.0.5.0 to your recovery block.
m
Thanks @stamatis
moonbutt74 said:
hi,
you need to follow this thread from first post, hear me out,
you must first download, extract to /sdcard and dd write cwm 6.0.5.0 [recovery.img] with the following terminal command
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p11
from that point you can flash philz normally. the assert in the updater script is correct. it calls to your
/system/build.prop
and verifies whether or not you have the correct device. The issue is with your process and your build prop.
if you are unable to resolve the issue, you may extract the recovery.img from the zip and write it in the same
fashion as cwm 6.0.5.0 to your recovery block.
m
Thanks @stamatis
Click to expand...
Click to collapse
Awsome. With the instruction spelled out to me, even I might be able to have a go att it.
BIG thanx for your patients with us end-users (that have no talent for coding )
/H
hmm...
Hey friend I have a question . How can we install twrp on the new 4.4.2 stock rom? I can't install it.it says some errors and reboots
FurFur_ said:
Hey friend I have a question . How can we install twrp on the new 4.4.2 stock rom? I can't install it.it says some errors and reboots
Click to expand...
Click to collapse
Read the OP completely.
moonbutt74 said:
Read the OP completely.
Click to expand...
Click to collapse
Of Course! thaaanks~~
moonbutt74 said:
dev-host link - http://d-h.st/users/moonbutt74/?fld_id=38524#files TO RECOVERIES
dev-host link - http://d-h.st/users/moonbutt74/?fld_id=38598#files TO AROMAFM - W.I.P.
NOTE- This is not a flashable/odin-able file. You must dd write to /dev/block/mmcblk0p11 [or appropriate recovery block]
Click to expand...
Click to collapse
"PhilzAdvCWM-6_55_0-gtP-5210.zip
Description: good 2 go kitkat kapable cwm flashable thanks Hazou @xda"
Is it flashable or not?
Edit it was not flashable, don't know why download states that.
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p11
"/dev/block/mmcblk0p11 Cannot open for write: Permission denied"
kgyirhj said:
"PhilzAdvCWM-6_55_0-gtP-5210.zip
Description: good 2 go kitkat kapable cwm flashable thanks Hazou @xda"
Is it flashable or not?
Edit it was not flashable, don't know why download states that.
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p11
"/dev/block/mmcblk0p11 Cannot open for write: Permission denied"
Click to expand...
Click to collapse
You need to execute the command as the root user, or what we call the superuser. Execute: su root. And then you are good to go.
Thanks @Divine_Madcat
m
moonbutt74 said:
hi,
you need to follow this thread from first post, hear me out,
you must first download, extract to /sdcard and dd write cwm 6.0.5.0 [recovery.img] with the following terminal command
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p11
from that point you can flash philz normally. the assert in the updater script is correct. it calls to your
/system/build.prop
and verifies whether or not you have the correct device. The issue is with your process and your build prop.
if you are unable to resolve the issue, you may extract the recovery.img from the zip and write it in the same
fashion as cwm 6.0.5.0 to your recovery block.
m
Thanks @stamatis
Click to expand...
Click to collapse
Okay i would like to flash this but because i currently have twrp installed and am not a fan cause it won't let me install 4.4. However i have know idea what this means. Can i flash this cwm using twrp?
Made TWRP Friendly
@jyerly
Okay so, this is Philz Recovery with the assert removed to be Old TWRP Friendly
TESTED, WORKING. I don't do it any other way.
devhost link - http://d-h.st/SSY
m :good:
HI Moonbutt74,
sorry for my maby silly question, but always just flashed via ODIN, CW; TWRP on my SGSII.....the Tab3 is differnet here and seems I have no clue .
I have rooted my Tab via the Root.zip and use the CWM from DutchDanny, still on stock firmware (see my sig).
I'd like to update to one of your new recoveries and go with Restl3ss Pimpdroid....but have no clue from terminal command.
Is there any hint how I execute the command you posted in OP?
Thanks for your kind help,
GeScha
This thread was originally for Pixel-specific rooting instructions, but by now the SuperSU ZIP and TWRP are fully supported:
- Fastboot boot TWRP
- Install latest SuperSU ZIP (v2.79-SR3 at the time of writing)
Note that at this time I recommend against fastboot flashing TWRP. With the Pixel's new partition layout, the recovery files are inside the boot partition, and so is SuperSU. If you flash both, SuperSU's internal boot image backup will not be of the original boot image, but of TWRP. This means that neither the 'full unroot' option in SuperSU, nor incremental OTA update through FlashFire, will work as expected.
OR
- Use CF-Auto-Root for Pixel (not released at the time of writing, but should be released soon)
Nice work!
Hell Yeah!!! Thanks @Chainfire, your time as well as others that have made this and the bootloader unlock happen is appreciated very much.
Sent from my Pixel XL using Tapatalk
can we flash another kernel such as elementalX on top of this?
diabl0w said:
can we flash another kernel such as elementalX on top of this?
Click to expand...
Click to collapse
How does this relate?
Ker~Man said:
How does this relate?
Click to expand...
Click to collapse
because I attempted to not really thinking about that its systemless and wasnt sure if root would persist. after attempting to flash boot elementalX's kernel my device just powered off so i immediately reflashed root and all is okay now
diabl0w said:
can we flash another kernel such as elementalX on top of this?
Click to expand...
Click to collapse
Lol if you read chainfires instructions you would have e your answer,but it short no, not until they add it
I did read the readme.. so not sure what your getting at
cwalker0906 said:
Lol if you read chainfires instructions you would have e your answer,but it short no, not until they add it
Click to expand...
Click to collapse
chainfire said:
- If you want to use a custom kernel, simply 'fastboot boot' the root image again after flashing the custom kernel. This has been tested with a few custom kernels and found to work well so far.
Click to expand...
Click to collapse
It was a valid question since this flashing method is different than what we are used to due to the difference in partitions and the file system.
lexcyn said:
It was a valid question since this flashing method is different than what we are used to due to the difference in partitions and the file system.
Click to expand...
Click to collapse
okay thanks, so i guess the answer is actually yes
Thanks @Chainfire - booted and working well!
thanks..emoji..root explorer.. viper.. naptime.. titanium.. yes..
if new kernel must boot boot to root again..
Seems I cannot remount /system_root as rw (to copy Emoji font over).
marlin://system_root/system/fonts # mount -o remount,rw /system_root
mount: '/dev/block/bootdevice/by-name/system_a'->'/system_root': Device or resource busy
Edit: Nevermind, used Solid Explorer and granted it SuperUser and seemed to work. Strange.
Does anyone have the stock boot.img for the pixel xl? I don't have the data to download the full factory image.
Life is good!
Thanks to all involved, especially Chainfire.
You Rock!
Worked like a charm. Thanks @Chainfire!
Can't thank you enough. Works perfectly.
can someonone please post the exact steps they are using?
I just unlocked my bootloader. then tried flashing the root-boot img file, it did the reboots, but when i complete android setup, theres no SuperSU and if i install the .apk, it still does not detect root...
just reflashed stock boot.img, locked and unlocked bootloader. waiting for instrustion.
thanks!
spunks3 said:
can someonone please post the exact steps they are using?
I just unlocked my bootloader. then tried flashing the root-boot img file, it did the reboots, but when i complete android setup, theres no SuperSU and if i install the .apk, it still does not detect root...
just reflashed stock boot.img, locked and unlocked bootloader. waiting for instrustion.
thanks!
Click to expand...
Click to collapse
fastboot boot boot-to-root.img
lexcyn said:
fastboot boot boot-to-root.img
Click to expand...
Click to collapse
what about superSU?
I have LG g2 mini d620r and i instaled custom rom and when i run my phone after instalation i get notification UPTADE so i download and click instal and i go to recovery and run update and my phone dont want to run system. I run my phone i see logo of lg and im in recovery.
pls help
sorry for my english :c
What recovery do you have?
Which ROM?
Vagelis1608 said:
What recovery do you have?
Which ROM?
Click to expand...
Click to collapse
i have TWRP 3.0.2.0
and want to install LineageOS 14.1
https://forum.xda-developers.com/g2-mini/development/unofficial-lineageos-14-1-t3529585
discoamazing said:
i have TWRP 3.0.2.0
and want to install LineageOS 14.1
https://forum.xda-developers.com/g2-mini/development/unofficial-lineageos-14-1-t3529585
Click to expand...
Click to collapse
If you had read the last couple of pages on the link you posted you would have know that is a known problem.
Read them. I think someone figured a workaround.
discoamazing said:
I have LG g2 mini d620r and i instaled custom rom and when i run my phone after instalation i get notification UPTADE so i download and click instal and i go to recovery and run update and my phone dont want to run system. I run my phone i see logo of lg and im in recovery.
pls help
sorry for my english :c
Click to expand...
Click to collapse
Classic problem if you update over OTA, go in the twrp and open the terminal :
first that : ' dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota '
second : ' dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc '
now just reboot system
likeadracula said:
Classic problem if you update over OTA, go in the twrp and open the terminal :
first that : ' dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota '
second : ' dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc '
now just reboot system
Click to expand...
Click to collapse
That is for stock.
The problem OP is having is a known issue of LaOS
Vagelis1608 said:
That is for stock.
The problem OP is having is a known issue of LaOS
Click to expand...
Click to collapse
It happened to me yesterday the same and i did this and worked with the lineageOS.
likeadracula said:
It happened to me yesterday the same and i did this and worked with the lineageOS.
Click to expand...
Click to collapse
Well, in that case, you are right :good:
i will test it
Doesnt work but i have a idea can someone who have working lg d620 send to me backup for twrp.
discoamazing said:
Doesnt work but i have a idea can someone who have working lg d620 send to me backup for twrp.
Click to expand...
Click to collapse
Download a ROM to your SD (using a PC or another phone) and flash it with TWRP
I repair it i replace motherboard
likeadracula said:
Classic problem if you update over OTA, go in the twrp and open the terminal :
first that : ' dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota '
second : ' dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc '
now just reboot system
Click to expand...
Click to collapse
My phone is up again by using terminal. Thanks
discoamazing said:
I repair it i replace motherboard
Click to expand...
Click to collapse
Your board certainly isn't dead. But if you don't need it, send your board then to @Quarx to have one, because his board burned with white smoke .
Thread Closed
Thread Closed
@TheHitMan Thank you so much, this port is perfect! But I think I made a mistake... When, in TWRP, need to flash "no-verity-opt-encrypt.zip" I tryed to flash the lastest (6.0) but it says "FAIL" or something like that...
Long story short, When I turn on the device says "your device has been unlocked and can't be trusted" , "Your device will boot in 5 seconds" (After the 5 seconds the device boot normally)
What can I do to fix that little detail???
WaLt-B.F. said:
@TheHitMan Thank you so much, this port is perfect! But I think I made a mistake... When, in TWRP, need to flash "no-verity-opt-encrypt.zip" I tryed to flash the lastest (6.0) but it says "FAIL" or something like that...
Long story short, When I turn on the device says "your device has been unlocked and can't be trusted" , "Your device will boot in 5 seconds" (After the 5 seconds the device boot normally)
What can I do to fix that little detail???
Click to expand...
Click to collapse
Nothing bad with this warning. Its a bootloader unlock warning.
Officia TWRP is available
shagul said:
Officia TWRP is available
Click to expand...
Click to collapse
No difference, until this build works fine.
Hey bro, can you belive I just do the OTA update with twrp and my phone boot to twrp but not to system???
What can I do??? =\
WaLt-B.F. said:
Hey bro, can you belive I just do the OTA update with twrp and my phone boot to twrp but not to system???
What can I do??? =\
Click to expand...
Click to collapse
Reflash system partition again. First wipe then install.
TheHitMan said:
Reflash system partition again. First wipe then install.
Click to expand...
Click to collapse
I´ve tryed but that doesn´t worked... Long story short, I restarted the phone in flashboot mode, at least in my case i had to install adb bootloader drivers manually, and then use the "flashall.bat" of the stock rom... I was worried...
Thank you!
WaLt-B.F. said:
I´ve tryed but that doesn´t worked... Long story short, I restarted the phone in flashboot mode, at least in my case i had to install adb bootloader drivers manually, and then use the "flashall.bat" of the stock rom... I was worried...
Thank you!
Click to expand...
Click to collapse
You can't install OTA updates with a custom recovery. You need stock recovery to perform OTA update operation.
TheHitMan said:
You can't install OTA updates with a custom recovery. You need stock recovery to perform OTA update operation.
Click to expand...
Click to collapse
Tell me about it xD
I didn´t know that until yesterday, what a noob, lol. Thanks for you help and for answer so soon! :good:
Hi, do u have a version for MT6735 variant?
My device details:
Model: Moto e4 plus
SKU: xt1772
variant: MT6735
i can successfully flash and boot this twrp version, but twrp recognizes my device as codename "woods" (thats moto e4).
Anyway, i tried to install roms for moto e4 "woods" but they all loop the bootloader.
DanielBrownM said:
Hi, do u have a version for MT6735 variant?
My device details:
Model: Moto e4 plus
SKU: xt1772
variant: MT6735
i can successfully flash and boot this twrp version, but twrp recognizes my device as codename "woods" (thats moto e4).
Anyway, i tried to install roms for moto e4 "woods" but they all loop the bootloader.
Click to expand...
Click to collapse
Its "MT6735" the SOC (system-on-chip) not the variant. Do not install moto e4 roms into moto e4 plus you will always ended up with bootloop. Can you please elaborate futher, How it recognize your device as wood ?
Because when i tried to intall the roms, they all returned an error saying: this rom is for nicklaus and this device is woods (not the exact words).
And in twrp home screen, top left of the corner (where usually shows the cpu temperature) says: 3.2.1-opr1-woods
DanielBrownM said:
Because when i tried to intall the roms, they all returned an error saying: this rom is for nicklaus and this device is woods (not the exact words).
And in twrp home screen, top left of the corner (where usually shows the cpu temperature) says: 3.2.1-opr1-woods
Click to expand...
Click to collapse
Thanks for reporting.
I will fix this soon and for now use 3.1.1 build floating around here.
TheHitMan said:
Thanks for reporting.
I will fix this soon and for now use 3.1.1 build floating around here.
Click to expand...
Click to collapse
Thanks but already tried with 3.1.1.
In that version the problem is similar, but instead of woods recognizes the device just as "e4".
DanielBrownM said:
Thanks but already tried with 3.1.1.
In that version the problem is similar, but instead of woods recognizes the device just as "e4".
Click to expand...
Click to collapse
I double check out the 3.1.1 XT1772 thread and no one report about the error you mentioned here.
I have installed v3.1.1 right now, after reading your post, just to be sure.
The output is the next when triting to install roms (dot and aosp) for nicklaus:
Code:
E004: This package is for: nicklaus, e4plus; this device is e4.
DanielBrownM said:
I have installed v3.1.1 right now, after reading your post, just to be sure.
The output is the next when triting to install roms (dot and aosp) for nicklaus:
Code:
E004: This package is for: nicklaus, e4plus; this device is e4.
Click to expand...
Click to collapse
What i have seen from error is not the recovery problem at all. Probably you need to upload META-INF from dotos or aosp rom. It looks like assert command problem.
TheHitMan said:
What i have seen from error is not the recovery problem at all. Probably you need to upload META-INF from dotos or aosp rom. It looks like assert command problem.
Click to expand...
Click to collapse
I just checked updater-script in META-INF file of the rom and probably is assert problem.
When i run ro.product.device in adb the command return this:
Code:
C:\Users\admin>adb shell getprop ro.product.model
Moto E (4) Plus
C:\Users\admin>adb shell getprop ro.product.device
nicklaus_f
C:\Users\admin>adb shell getprop ro.build.product
nicklaus
But, when trying to install the rom in twrp, the return of that command is "wood" for twrp v3.2.1 and "e4" in twrp 3.1.1.
Maybe i should try to delete assert line in updater-script of the rom and install.
----edited---
Actually when i write getprop ro.build.product in twrp terminal returns "woods"
ONLY FOR A605FN,
ATTENTION,
this method is no longer the best option,
for root A6 + I recommend following the ashyx tutorial in the following post:
https://forum.xda-developers.com/galaxy-a6/development/recovery-twrp-3-2-3-1-galaxy-a6-a605-t3868598
1 - Backup your files.
2 - Flash this patchet boot.img with ODIN -
Download for A605FN (A605FNXXU1ARE2 PHE)
Download for A605FN (A605FNXXU2ARG2 PHE)
3 - When reboot your device automatic restore (dont worry,remember step 1).
4 - Install Magisk.apk and SuperUser working.
THANKS TO MAGISK FOR THE NEW ROOT METHOD WITHOUT RECOVERY
If I have helped you, invite me to a beer by clicking HERE.
Do it work with a605G. Thạnk
Safetynet
Does safetynet check work?
Anyone already try A605G
Andrianovaldi said:
Anyone already try A605G
Click to expand...
Click to collapse
I've tried and I get error Only offical binary is allowed to boot.
josemaesra said:
Click to expand...
Click to collapse
Can you make a file for A605G. This is the stock boot.img of A605G. Thank you very much
https://drive.google.com/file/d/1rKBan8G8ht73kSXPuciE4O_Qp6uqqXz_/view?usp=sharing
So I couldn't get safetynet check to work, is it just me or?
Codelyoko2409 said:
I've tried and I get error Only offical binary is allowed to boot.
Click to expand...
Click to collapse
U already activated oem unlock?
Andrianovaldi said:
U already activated oem unlock?
Click to expand...
Click to collapse
Yes. I flashed successfully but when I boot my phone. It show error
Codelyoko2409 said:
Can you make a file for A605G. This is the stock boot.img of A605G. Thank you very much
https://drive.google.com/file/d/1rKBan8G8ht73kSXPuciE4O_Qp6uqqXz_/view?usp=sharing
Click to expand...
Click to collapse
For A605G - Download
josemaesra said:
For A605G - Download
Click to expand...
Click to collapse
Thanks. But I can not test right now. I has to wait for a week
josemaesra said:
1 - Backup your files.
2 - Flash this patchet boot.img with ODIN - Download for A605FN.
Download for A605G
3 - When reboot your device automatic restore (dont worry,remember step 1).
4 - Install Magisk.apk and SuperUser working.
tried on A605FNXXU1ARE2
Click to expand...
Click to collapse
so, i just simply flash the boot.img, restart normally then instal supersu? need more detail steps and explanations
3 - When reboot your device automatic restore (dont worry,remember step 1). >> what;s mean remember step 1??
Codelyoko2409 said:
Yes. I flashed successfully but when I boot my phone. It show error
Click to expand...
Click to collapse
Pls try the new one sir
Andrianovaldi said:
Pls try the new one sir
Click to expand...
Click to collapse
Sorry. I hace to wait for 4 day to have oem unlock
an-_-dro said:
so, i just simply flash the boot.img, restart normally then instal supersu? need more detail steps and explanations
3 - When reboot your device automatic restore (dont worry,remember step 1). >> what;s mean remember step 1??
Click to expand...
Click to collapse
After flashing the boot image the device is restored and all personal files are deleted,
that's why it's important to remember step 1.:good:
[
josemaesra said:
After flashing the boot image the device is restored and all personal files are deleted,
that's why it's important to remember step 1.:good:
Click to expand...
Click to collapse
I already try boot.img for SM-A605G and get error not_dev bla bla, and i try boot.img for A605FN and sucessfully flashed and after reboot it say verification failed and must factory reset then i factory reset and succses untill homescreen, then i try acces twrp with volume up + down + power and show error u only official binary allowed to boot bla bla??
Andrianovaldi said:
[
I already try boot.img for SM-A605G and get error not_dev bla bla, and i try boot.img for A605FN and sucessfully flashed and after reboot it say verification failed and must factory reset then i factory reset and succses untill homescreen, then i try acces twrp with volume up + down + power and show error u only official binary allowed to boot bla bla
Click to expand...
Click to collapse
Currently there is no TWRP for A6 +,
this method is only to have superuser permissions.
After the factory reset only install Magisk.apk and you will have Superuser.:good:
josemaesra said:
Currently there is no TWRP for A6 +,
this method is only to have superuser permissions.
After the factory reset only install Magisk.apk and you will have Superuser.:good:
Click to expand...
Click to collapse
Ah i see, so after i factory reset and succesfully show homescreen i just install magisk.apk and done? Pfff now i must wait 7days or 14 days again too do it again?
josemaesra said:
Currently there is no TWRP for A6 +,
this method is only to have superuser permissions.
After the factory reset only install Magisk.apk and you will have Superuser.:good:
Click to expand...
Click to collapse
only magisk or superSU will work also? im not really like magisk for those complicated, superSU lot simple.
Andrianovaldi said:
Ah i see, so after i factory reset and succesfully show homescreen i just install magisk.apk and done? Pfff now i must wait 7days or 14 days again too do it again
Click to expand...
Click to collapse
bro, u're from indonesia right? your handset 6+ A605G/DS? the one which is working is img for A605FN?
which version f/w your currently on? i'm on ARG1.