Just wondering if anyone who bought a north american version, e1005, had twrp flashed and working.
joho5 said:
Just wondering if anyone who bought a north american version, e1005, had twrp flashed and working.
Click to expand...
Click to collapse
Yes, flashed @eng.stk version of TWRP and his kernel as well. Smooth and stable.
Search the General section for guides and how to's :thumbup:
Mojar7070 said:
Yes, flashed @eng.stk version of TWRP and his kernel as well. Smooth and stable.
Search the General section for guides and how to's :thumbup:
Click to expand...
Click to collapse
I know how to...I have unlocked bootloader and flashed recovery in nexus 4, 5, 5x, 6p, opo, op2, and now opx...but twrp won't flash on this device for me.
joho5 said:
I know how to...I have unlocked bootloader and flashed recovery in nexus 4, 5, 5x, 6p, opo, op2, and now opx...but twrp won't flash on this device for me.
Click to expand...
Click to collapse
It should be the same routine for the OPX as all of those devices then.
Just to be sure, you're doing it this way (step 5)?
Make sure that your bootloader is unlocked first, or it won't flash (step 2).
Also, make sure that when you use the command "fastboot flash recovery xxx.img" that "xxx.img" is identical to the name of the img file you have placed in your sdk tools folder.
Mojar7070 said:
It should be the same routine for the OPX as all of those devices then.
Click to expand...
Click to collapse
Should be...key word. Guys I've tried it over and over again. All different ways to boot recovery after...different places downloading the file...different way installing (fastboot and flashify).
Only weird thing is that "fastboot oem device-info"
Says tampered is false
Unlocked is true
Does just unlocking bootloader usually trip the tampered flag?
So you're sure that you've enabled OEM unlocking in the developer options??
Mojar7070 said:
So you're sure that you've enabled OEM unlocking in the developer options??
Click to expand...
Click to collapse
yes of course...Ive been through the process with the op2.
all drivers installed correctly, got rsa key, unlocked bootloader...one thing is that the confirmation bootloader unlocking screen was in chinese, but I chose the top option to confirm.
Same Issue
I'm having the exact same problem and would love to know a fix as well. My device is also unlocked by the tamper flag was not set off. I'm having the same problem of not being able to load TWRP onto the phone as well.
im guessing maybe because there isnt an official twrp for this phone.
There is only a custom and I know the internals are the same, but I think there are some kind of differences from phone to phone from region to region.
joho5 said:
im guessing maybe because there isnt an official twrp for this phone.
There is only a custom and I know the internals are the same, but I think there are some kind of differences from phone to phone from region to region.
Click to expand...
Click to collapse
Hello,
I believe there is an official twrp. I did a search and found that you were already involved in that thread by @CafeKampuchia using the TWRP (onyx version) by @h2064
That was the initial recovery I had before I flash to the f2fs version by @eng.stk.
Mojar7070 said:
Hello,
I believe there is an official twrp. I did a search and found that you were already involved in that thread by @CafeKampuchia using the TWRP (onyx version) by @h2064
That was the initial recovery I had before I flash to the f2fs version by @eng.stk.
Click to expand...
Click to collapse
If you look here, there is no official TWRP for OPX yet, just for OPO & OP2.
https://twrp.me/Devices/
I did kingroot, flasify, twrp, replace kingroot with SuperSU. Getting lazy and didn't connect it to a pc...
neilownz said:
I did kingroot, flasify, twrp, replace kingroot with SuperSU. Getting lazy and didn't connect it to a pc...
Click to expand...
Click to collapse
Flashify wouldn't allow me to flash twrp either.
joho5 said:
Flashify wouldn't allow me to flash twrp either.
Click to expand...
Click to collapse
Sure did for me after I was rooted.
neilownz said:
Sure did for me after I was rooted.
Click to expand...
Click to collapse
Yours is US version?
CafeKampuchia said:
If you look here, there is no official TWRP for OPX yet, just for OPO & OP2.
https://twrp.me/Devices/
Click to expand...
Click to collapse
I see, I apologize for the misunderstanding.
joho5 said:
Yours is US version?
Click to expand...
Click to collapse
Sure is.
joho5 said:
Flashify wouldn't allow me to flash twrp either.
Click to expand...
Click to collapse
neilownz said:
Sure did for me after I was rooted.
Click to expand...
Click to collapse
Without an unlocked bootloader?
CafeKampuchia said:
Without an unlocked bootloader?
Click to expand...
Click to collapse
I have no idea if it is unlocked... like I said I didn't use a computer.
Related
Root is now available for our lovely 6P!
Flash TWRP from here
Flash the boot image from here (angler-mdb08k-boot.zip)
Flash the latest SuperSU beta from here
then you'll be good to go!
Does it require a custom kernel? I couldn't find mention of it in the link. Also, what the heck is a "boot image?" I know bootloader, recovery, and kernel. Do we now have another thing to consider?
Cool... Can any1 confirm though that rooting wont effect fingerprint sensor working..... I don't really care for Android pay
Sent not from Nexus 6P
Poke_N_PDA said:
Does it require a custom kernel? I couldn't find mention of it in the link. Also, what the heck is a "boot image?" I know bootloader, recovery, and kernel. Do we now have another thing to consider?
Click to expand...
Click to collapse
The boot image is the kernel, it's the one in the zip mentioned at the link.
rohit25 said:
Cool... Can any1 confirm though that rooting wont effect fingerprint sensor working..... I don't really care for Android pay
Sent not from Nexus 6P
Click to expand...
Click to collapse
Confirmed everything is working fine.
Tung_meister said:
The boot image is the kernel, it's the one in the zip mentioned at the link.
Confirmed everything is working fine.
Click to expand...
Click to collapse
Can you confirm or deny that rooting breaks Android Pay? I've seen nothing but rumors from people
Akasa Fox said:
Can you confirm or deny that rooting breaks Android Pay? I've seen nothing but rumors from people
Click to expand...
Click to collapse
I'm in the UK so don't have access to Android Pay I'm afraid.
Is there already a way to unroot? Also I hope we don't lose any data while rooting and then unrooting.
This will be my first Nexus.
nageshv24 said:
Is there already a way to unroot? Also I hope we don't lose any data while rooting and then unrooting.
This will be my first Nexus.
Click to expand...
Click to collapse
If you just reflash the stock system image that would erase any trace of root. You wouldn't lose any data. You'll only be able to flash the root zip/kernel if you've already unlocked your bootloader. If you've not done that you'll have to do it first and the process of unlocking will wipe the device.
Tung_meister said:
If you just reflash the stock system image that would erase any trace of root. You wouldn't lose any data. You'll only be able to flash the root zip/kernel if you've already unlocked your bootloader. If you've not done that you'll have to do it first and the process of unlocking will wipe the device.
Click to expand...
Click to collapse
The first thing I do with my 6P will be unlocking the bootloader [emoji4]. Thanks
Sent from my GT-I9500 using Tapatalk
nageshv24 said:
The first thing I do with my 6P will be unlocking the bootloader [emoji4]. Thanks
Sent from my GT-I9500 using Tapatalk
Click to expand...
Click to collapse
Had to check lol.
Tung_meister said:
Root is now available for our lovely 6P!
Flash TWRP from here
Flash the boot image from here (angler-mdb08k-boot.zip)
Flash the latest SuperSU beta from here
then you'll be good to go!
Click to expand...
Click to collapse
.
Um? Don't think we're quite there yet?
.
Quote from Chainfire.
Acquiring root without modifying the boot images is still under investigation. Please note that the current method will not be officially supported. Future roots may require a clean system: we are at a very early stage of root for 6.0, methods used are subject to change.
Born<ICs said:
.
Um? Don't think we're quite there yet?
.
Quote from Chainfire.
Acquiring root without modifying the boot images is still under investigation. Please note that the current method will not be officially supported. Future roots may require a clean system: we are at a very early stage of root for 6.0, methods used are subject to change.
Click to expand...
Click to collapse
We are, the second is a link to the modified boot image required. It's working perfectly on my device as we speak.
MDA89D my 6p is still on that that build number what boot image do i use?
pro4ever said:
MDA89D my 6p is still on that that build number what boot image do i use?
Click to expand...
Click to collapse
I'd download the factory image and update to the latest build. you can edit the "flash-all.bat" so that it doesn't wipe your phone. Change the command
"fastboot -w update" to
"fastboot update"
to preserve your data.
I have re-opened this thread, because the linked thread isn't the same - this isn't a duplicate.
"4. How To Root Your Stock Rom
This section will be revisited when more information is available."
This thread presents something new.
Akasa Fox said:
Can you confirm or deny that rooting breaks Android Pay? I've seen nothing but rumors from people
Click to expand...
Click to collapse
Yes, it breaks Android Pay (justchecked). Google already disclosed this to us, so it's not a rumor.
Tung_meister said:
We are, the second is a link to the modified boot image required. It's working perfectly on my device as we speak.
Click to expand...
Click to collapse
.
You may want to modify OP to mention Flashing Modified Boot Image before flashing TWRP may be a good idea.
Tung_meister said:
We are, the second is a link to the modified boot image required. It's working perfectly on my device as we speak.
Click to expand...
Click to collapse
Just boot loops for me , even with Chainfire's boot.img. Is it necessary to do the steps one right after another?
Neat! Glad it is all happening quickly. I think I want to keep encryption, so I will probably wait to root and install TWRP until wiping data to remove encryption is no longer necessary.
Can someone please confirm if the damn fingerprint sensor still works after rooting?
my stock ver is 13.3.2 using safestrap 3.75. is it possible that i download the new safestrap 4.0 and install new rom CM11 or nexus like the way i did before?
If you're on 3.2.3.2, you can install TWRP (a true recovery) and unlock your bootloader (which will also allow you to install ROMs like CM12).
EncryptedCurse said:
If you're on 3.2.3.2, you can install TWRP (a true recovery) and unlock your bootloader (which will also allow you to install ROMs like CM12).
Click to expand...
Click to collapse
thank you for your reply, but i dont know how to unlock BL
fuxkamazon said:
thank you for your reply, but i dont know how to unlock BL
Click to expand...
Click to collapse
Thanks to draxie's tool, it should be really simple: http://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014
I had downloaded that tool and virtual box, but everytime it say my device is not connected. i pretty sure i have adb on. btw, i use windownX64
EncryptedCurse said:
Thanks to draxie's tool, it should be really simple: http://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014
Click to expand...
Click to collapse
Is it still possible to fix this phone if it stuck at this screen on every boot?
bchiu said:
Is it still possible to fix this phone if it stuck at this screen on every boot?
Click to expand...
Click to collapse
I tried choose every option using volume rocker and use power button to enter but the phone just reboot no matter which option I choose.
bchiu said:
I tried choose every option using volume rocker and use power button to enter but the phone just reboot no matter which option I choose.
Click to expand...
Click to collapse
Unlock the bootloader and flash either stock or custom ROM.
Ujwal Agrawal said:
Unlock the bootloader and flash either stock or custom ROM.
Click to expand...
Click to collapse
I can't unlock the bootloader. I already tried on Motorola website.
bchiu said:
I can't unlock the bootloader. I already tried on Motorola website.
Click to expand...
Click to collapse
There are key combos by which you can clear cache and dalvik cache, this might help. Google it
Seems like none of the options works
bchiu said:
Seems like none of the options works
Click to expand...
Click to collapse
Flash this
https://www.androidfilehost.com/?fid=24052804347833874
Rajendran Rasa said:
Flash this
https://www.androidfilehost.com/?fid=24052804347833874
Click to expand...
Click to collapse
Thanks. But how do I flash since I can't get into any of the options?
bchiu said:
Thanks. But how do I flash since I can't get into any of the options?
Click to expand...
Click to collapse
Flash in fastboot
For more info search YouTube or xda
Rajendran Rasa said:
Flash in fastboot
For more info search YouTube or xda
Click to expand...
Click to collapse
But my bootloader is locked
bchiu said:
But my bootloader is locked
Click to expand...
Click to collapse
You can flash stock rom in locked/unlocked bootloader using fastboot command
Rajendran Rasa said:
You can flash stock rom in locked/unlocked bootloader using fastboot command
Click to expand...
Click to collapse
Okay thanks. Will try that.
N I could not install twrp recovery
bchiu said:
Okay thanks. Will try that.
Click to expand...
Click to collapse
Did it work man???? Wondering if I can get twrp to boot one time on this piece of junk so I can flash superSU over the locked loader to the system partition -.-
Rajendran Rasa said:
You can flash stock rom in locked/unlocked bootloader using fastboot command
Click to expand...
Click to collapse
Thank you so much buddy. I thought it was a write off. Now it's back to live!
bchiu said:
Thank you so much buddy. I thought it was a write off. Now it's back to live!
Click to expand...
Click to collapse
I wonder if that'd fix my issues as well, I got the stock images a while back might as well give it a go xD.
If any of you face a hard brick or soft brick, have a look at my XDA DevDB post. It might be of help to you... Unbrick hard bricked Motorola Moto E - Aravind V. Nair (XDA)
aravindvnair99 said:
If any of you face a hard brick or soft brick, have a look at my XDA DevDB post. It might be of help to you... Unbrick hard bricked Motorola Moto E - Aravind V. Nair (XDA)
Click to expand...
Click to collapse
Thanks bro! Curious as to if the xt1022 and this CDMA model could be interchangeable as far as software/ROMs go
LilAnt530 said:
Thanks bro! Curious as to if the xt1022 and this CDMA model could be interchangeable as far as software/ROMs go
Click to expand...
Click to collapse
Unbrick method is common to a device series. But the files you use aren't. Only the modem files are different as far as I have seen. Correct me if I'm wrong. I don't think any other difference is there. After unbricking, you will get partition errors. Then, simply go to fastboot and use the correct files from your firmware. Instruction are given in my GitHub repository for this project. Read through my post and GitHub README.MD
Between, I'm still making things proper... You can have a look though..
aravindvnair99 said:
Unbrick method is common to a device series. But the files you use aren't. Only the modem files are different as far as I have seen. Correct me if I'm wrong. I don't think any other difference is there. After unbricking, you will get partition errors. Then, simply go to fastboot and use the correct files from your firmware. Instruction are given in my GitHub repository for this project. Read through my post and GitHub README.MD
Between, I'm still making things proper... You can have a look though..
Click to expand...
Click to collapse
Well I have the xt830c model and all i really want is the xt1022 5.1 update lol. I cant acquire root or unlock the bootloader because of worthless straight talk and its my only device
Will someone please Loki the latest release for jftlevzw I want to install Oreo and the official release makes me have to Odin to stock. Yes I am on mdk.
Plitskin5 said:
Will someone please Loki the latest release for jftlevzw I want to install Oreo and the official release makes me have to Odin to stock. Yes I am on mdk.
Click to expand...
Click to collapse
Hmm I can. What rom???
Sent from my Pixel 2 XL using Tapatalk
Well i did but there is something wrong with twrp. I decompiled the img and swapped out every part from from the 3.2.3.0 into a 3.1.0.0 ramdisk and little by little i narrowed it down to the libaosprecovery.so and recovery within the sbin thats keeping it from booting. everything else replaced is working fine
bryantjopplin said:
Hmm I can. What rom???
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
bryantjopplin said:
Well i did but there is something wrong with twrp. I decompiled the img and swapped out every part from from the 3.2.3.0 into a 3.1.0.0 ramdisk and little by little i narrowed it down to the libaosprecovery.so and recovery within the sbin thats keeping it from booting. everything else replaced is working fine
Click to expand...
Click to collapse
https://forum.xda-developers.com/ga.../jdcteam-android-source-project-oreo-t3685231 is the rom. And I see
Plitskin5 said:
Will someone please Loki the latest release for jftlevzw I want to install Oreo and the official release makes me have to Odin to stock. Yes I am on mdk.
Click to expand...
Click to collapse
What?!!!!!!!WHAT THE!!!!!WHAT IS YOUR ANDROID? ???
ford1234 said:
What?!!!!!!!WHAT THE!!!!!WHAT IS YOUR ANDROID? ???
Click to expand...
Click to collapse
He's on Android 4.2.2 jelly bean with the MDK bootloader. It is an exploitable bootloader that allows loki doki to be installed thus bypassing the bootloader lock that allows TWRP to be installed and custom ROMs to boot. Now you're probably wondering how you can get this bootloader. Well you can't because once you have updated to a newer bootloader, you can't go back.
StoneyJSG said:
He's on Android 4.2.2 jelly bean with the MDK bootloader. It is an exploitable bootloader that allows loki doki to be installed thus bypassing the bootloader lock that allows TWRP to be installed and custom ROMs to boot. Now you're probably wondering how you can get this bootloader. Well you can't because once you have updated to a newer bootloader, you can't go back.
Click to expand...
Click to collapse
I hate this!!!I wanna try to downgrade if is possible,trust me,i will brick brake hit do everything until the phone blows off by itself ?
If you attempt to downgrade you will brick your phone the moment ODIN finishes flashing the MDK firmware. If you're on lollipop, my advice is to root then use flash fire version 0.53 to flash the OC1 or OF1 bootloader then install stang5litre ROM from there.
StoneyJSG said:
If you attempt to downgrade you will brick your phone the moment ODIN finishes flashing the MDK firmware. If you're on lollipop, my advice is to root then use flash fire version 0.53 to flash the OC1 or OF1 bootloader then install stang5litre ROM from there.
Click to expand...
Click to collapse
Good news
I hard bricked my phone:laugh:
ford1234 said:
Good news
I hard bricked my phone:laugh:
Click to expand...
Click to collapse
I told you that would happen if you attempt to downgrade farther than OC1 or OC3 (can't remember which). This may help you if you wanna try and fix it, I don't know: https://forum.xda-developers.com/galaxy-s4-verizon/general/guide-sch-i545-vrugof1-look-t3395833
Once you've got it back to working order, you can follow my guide here to get stang litre ROM running. https://forum.xda-developers.com/ga...al/guide-rooting-roming-sch-i545-pl1-t3846576
StoneyJSG said:
I told you that would happen if you attempt to downgrade farther than OC1 or OC3 (can't remember which). This may help you if you wanna try and fix it, I don't know: https://forum.xda-developers.com/galaxy-s4-verizon/general/guide-sch-i545-vrugof1-look-t3395833
Once you've got it back to working order, you can follow my guide here to get stang litre ROM running. https://forum.xda-developers.com/ga...al/guide-rooting-roming-sch-i545-pl1-t3846576
Click to expand...
Click to collapse
Thank you for helping me but I dropped in my garbages
Take care
bryantjopplin said:
Well i did but there is something wrong with twrp. I decompiled the img and swapped out every part from from the 3.2.3.0 into a 3.1.0.0 ramdisk and little by little i narrowed it down to the libaosprecovery.so and recovery within the sbin thats keeping it from booting. everything else replaced is working fine
Click to expand...
Click to collapse
I loki patched the JFLTEXX (GT-I9505) TWRP 3.2.3.0 and flashed it and it seems to work. Something must be wrong with the JFLTEVZW builds of TWRP.
Looking to try the JDCTeam Optimized LineageOS 16: https://forum.xda-developers.com/ga...team-optimized-lineageos-16-0-builds-t3858607
I have done my research on xda and Google about my phone version not having access to root yet; and I would like to know the opinion of users of my same phone model: SM-A526U; What benefits can i find if i install magisk?
can i use the magisk modules without being rooted?
thank you for reading my post and thank you in advance if you respond
EdAmsterdam said:
I have done my research on xda and Google about my phone version not having access to root yet; and I would like to know the opinion of users of my same phone model: SM-A526U; What benefits can i find if i install magisk?
can i use the magisk modules without being rooted?
thank you for reading my post and thank you in advance if you respond
Click to expand...
Click to collapse
you will needmagisk to root,if and when its available unless a twrp is available, but without root its useless
gav83collins said:
you will needmagisk to root,if and when its available unless a twrp is available, but without root its useless
Click to expand...
Click to collapse
thank you gav83collins for you fast response.... I'll keep waiting until there's root for my SM-A526u
is it the same for the aio-adb-tool?
do i need to have root to use that?
i would love to take out some of the bloatware and that tool seems very nice
EdAmsterdam said:
is it the same for the aio-adb-tool?
do i need to have root to use that?
i would love to take out some of the bloatware and that tool seems very nice
Click to expand...
Click to collapse
you dont need root for that no, for most of the current features except pulling a logact
gav83collins said:
you dont need root for that no, for most of the current features except pulling a logact
Click to expand...
Click to collapse
great.... thank you again
i will try and play with that tool until there is SU access
EdAmsterdam said:
I have done my research on xda and Google about my phone version not having access to root yet; and I would like to know the opinion of users of my same phone model: SM-A526U; What benefits can i find if i install magisk?
can i use the magisk modules without being rooted?
thank you for reading my post and thank you in advance if you respond
Click to expand...
Click to collapse
Have you tried Odin to do the flashing? While not the same device, I have rooted my SM-A526B without TWRP by patching the boot image with Magisk and then copying over the patched boot.img file to a computer, then finally flashed it over using Odin.
I have played with TWRP and Odin in the past with other phones; But I don't feel comfortable experimenting with this phone since it's my only source of work right know. After the process is proved ok by other people with the exact same model as mine, I can't risk experimenting like I have done other times.
daft plonker said:
Have you tried Odin to do the flashing? While not the same device, I have rooted my SM-A526B without TWRP by patching the boot image with Magisk and then copying over the patched boot.img file to a computer, then finally flashed it over using Odin.
Click to expand...
Click to collapse
This won't work on Samsung "U" variant phones because of their locked bootloader. Once you modify boot.img with Magisk, the phone will automatically detect it as custom firmware and it won't allow it to be flashed because of locked BL.
ShaDisNX255 said:
This won't work on Samsung "U" variant phones because of their locked bootloader. Once you modify boot.img with Magisk, the phone will automatically detect it as custom firmware and it won't allow it to be flashed because of locked BL.
Click to expand...
Click to collapse
That makes sense. Sorry didn't know their bootloader was permanently locked
ShaDisNX255 said:
This won't work on Samsung "U" variant phones because of their locked bootloader. Once you modify boot.img with Magisk, the phone will automatically detect it as custom firmware and it won't allow it to be flashed because of locked BL.
Click to expand...
Click to collapse
daft plonker said:
That makes sense. Sorry didn't know their bootloader was permanently locked
Click to expand...
Click to collapse
I also didn't knew that was the reason.... thank you