Hi everyone!
This is my first time here so bear with me. I recently tried flashing cm12 on my kindle fire hdx 7" and apparently flashed it in the wrong place. Right now its stuck in fastboot mode and everytime I try and flash something it gives me this error:
Code:
FAILED (remote: flashing not allowed for locked hw)
I don't know what i'm doing wrong and it won't leave fastboot mode. Can any of you all help me?
tekmeister98 said:
Hi everyone!
This is my first time here so bear with me. I recently tried flashing cm12 on my kindle fire hdx 7" and apparently flashed it in the wrong place. Right now its stuck in fastboot mode and everytime I try and flash something it gives me this error:
Code:
FAILED (remote: flashing not allowed for locked hw)
I don't know what i'm doing wrong and it won't leave fastboot mode. Can any of you all help me?
Click to expand...
Click to collapse
Oh I forgot to mention I was on fire os 4.5.2 before this happened.
You can't flash CM12 on 4.5.2 — or any other ROM, for that matter.
EncryptedCurse said:
You can't flash CM12 on 4.5.2 — or any other ROM, for that matter.
Click to expand...
Click to collapse
well this happened before i acutally did that. It was trying to flash either twrp or safestrap.. one of the two. i think i flashed one of them in the boot partition and its locked up now
tekmeister98 said:
well this happened before i acutally did that. It was trying to flash either twrp or safestrap.. one of the two. i think i flashed one of them in the boot partition and its locked up now
Click to expand...
Click to collapse
I guess what i'm asking is how to fix it. No matter what I do its just telling me I can't flash to locked hw.
tekmeister98 said:
I guess what i'm asking is how to fix it. No matter what I do its just telling me I can't flash to locked hw.
Click to expand...
Click to collapse
And I can't get to adb shell... so I need help.
Adb commands do not work in fastboot. What you need to do is reboot it with the fastboot version of the adb command that got you there.
Something like fastboot reboot recovery (I do not remember if there was a reboot system command). You can find the commands in the unlock boot loader thread in the original dev section.
lekofraggle said:
Adb commands do not work in fastboot. What you need to do is reboot it with the fastboot version of the adb command that got you there.
Something like fastboot reboot recovery (I do not remember if there was a reboot system command). You can find the commands in the unlock boot loader thread in the original dev section.
Click to expand...
Click to collapse
I've tried that but I'm stuck in a bootloop.
In the bootloop, if you have a grey and orange logo, and you have enabled adb, you can use adb commands. With root, even shell. However, if it only boots to fastboot, your system is corrupted. Try holding down the plus volume button on boot to see if you can get to recovery.
lekofraggle said:
In the bootloop, if you have a grey and orange logo, and you have enabled adb, you can use adb commands. With root, even shell. However, if it only boots to fastboot, your system is corrupted. Try holding down the plus volume button on boot to see if you can get to recovery.
Click to expand...
Click to collapse
Yeah that doesn't work. Is there any fix for a corrupted system?
The only fix if your bootloader is locked (which it almost definitely is), is to get fastboot to install an oem system or recovery image. I do not think it will work though. Read up on fastboot. Use the number code for our device before each operation.
lekofraggle said:
The only fix if your bootloader is locked (which it almost definitely is), is to get fastboot to install an oem system or recovery image. I do not think it will work though. Read up on fastboot. Use the number code for our device before each operation.
Click to expand...
Click to collapse
hmmm.. okay. Are you able to give me a cat /sys/block/mmcblk0/device/manfid and a cat /sys/block/mmcblk0/device/serial on a device of yours so I can try and unlock it?
No, those numbers are custom to devices and non-transferable. Also, my bootloader is old and unlocked. Sorry.
lekofraggle said:
No, those numbers are custom to devices and non-transferable. Also, my bootloader is old and unlocked. Sorry.
Click to expand...
Click to collapse
dang. Okay. Thanks for the help though. I'll just have to keep at it.
did you ever get your bootloader unlocked?
bowman1966 said:
did you ever get your bootloader unlocked?
Click to expand...
Click to collapse
Nope. I tried a bunch of stuff but it didn't work.
Well, the bootloader of versions 3.2.3.2 and lower can be unlocked only, so unsurprisingly your (tekmeister98) 4.5.2 bootloader couldn't be unlocked. But why you, bowman1966, can't do it if you had TWRP installed remains a mystery to me.
Cl4ncy said:
Well, the bootloader of versions 3.2.3.2 and lower can be unlocked only, so unsurprisingly your (tekmeister98) 4.5.2 bootloader couldn't be unlocked. But why you, bowman1966, can't do it if you had TWRP installed remains a mystery to me.
Click to expand...
Click to collapse
Thats just par for my coarce lol.
Ill let it sit awhile and play another day....
Resurrecting this thread... Any new fixes out yet? I've seen workarounds for starting with stock os but other than that I don't know.
Related
I've looked around and I can't seem to find a way to unlock the bootloader on my 2.3.6 Atrix. Most tuts are for 2.3.4. What's the best way to do it?
http://dl.dropbox.com/u/34025287/4547-fix-try2.sbf
Flash this with RSD lite - run the fastboot oem unlock commands if needed. Its as simple as that
G-Man. said:
http://dl.dropbox.com/u/34025287/4547-fix-try2.sbf
Flash this with RSD lite - run the fastboot oem unlock commands if needed. Its as simple as that
Click to expand...
Click to collapse
You just run those in ADB, right?
mugabuga said:
You just run those in ADB, right?
Click to expand...
Click to collapse
Yes that's correct. You shouldn't need to if you unlocked your bootloader before the .141 update. To re-root use this method, it will give a couple errors at a certain point, just disregard the errors and continue with the commands and reboot your Atrix when you've finished - http://www.atrixforums.com/forum/mo...ing-stock-locked-2-3-4-2-3-6-a.html#post47155
G-Man. said:
Yes that's correct. You shouldn't need to if you unlocked your bootloader before the .141 update. To re-root use this method, it will give a couple errors at a certain point, just disregard the errors and continue with the commands - http://www.atrixforums.com/forum/mo...ing-stock-locked-2-3-4-2-3-6-a.html#post47155
Click to expand...
Click to collapse
But even if I've never unlocked it, it should still work?
mugabuga said:
But even if I've never unlocked it, it should still work?
Click to expand...
Click to collapse
If you've never unlocked it, it will act like a soft brick and hang on the first reboot - this is normal. You should have a screen pop up with a list of a dozen or more options, you'll need to select 'fastboot' and then run the command in ADB - fastboot oem unlock - this will give you a unique ID # - repeat the fastboot oem unlock command with the # at the end like this - fastboot oem unlock <unique ID # here> and press enter, it will give a warning about voiding your warranty, select yes and continue. From there, it should proceed with the unlock. After wards you'll need to let it fully reboot. Then boot your Atrix BACK into fastboot again, and flash RomRacers latest recovery with ADB. You can find the thread in the Development section. Then you load your ROM of choice onto your internal SD card and boot into CWM Recovery (RomRacers) and flash the ROM - give your Atrix 10-15 mins to fully boot after you install your ROM.
G-Man. said:
If you've never unlocked it, it will act like a soft brick and hang on the first reboot - this is normal. You should have a screen pop up with a list of a dozen or more options, you'll need to select 'fastboot' and then run the command in ADB - fastboot oem unlock - this will give you a unique ID # - repeat the fastboot oem unlock command with the # at the end like this - fastboot oem unlock <unique ID # here> and press enter, it will give a warning about voiding your warranty, select yes and continue. From there, it should proceed with the unlock. After wards you'll need to let it fully reboot. Then boot your Atrix BACK into fastboot again, and flash RomRacers latest recovery with ADB. You can find the thread in the Development section. Then you load your ROM of choice onto your internal SD card and boot into CWM Recovery (RomRacers) and flash the ROM - give your Atrix 10-15 mins to fully boot after you install your ROM.
Click to expand...
Click to collapse
EDIT: Fixed the problem by pulling the batt and unpluging from the computer.
mugabuga said:
Alright. It says it worked on the phone, but my RSD Lite claims it failed with an error switching phone to BP Pass through mode (0x70BE). Its just hanging at the success screen on my phone.
Click to expand...
Click to collapse
Can you upload a pic of the screen you are seeing?
[edit] I gotta get to bed, I'll check back here tomorrow if someone else is unable to assist you tonight. Its after midnight here and I'm getting over a bad cold still. I will check back here tomorrow.
mugabuga said:
EDIT: Fixed the problem by pulling the batt and unpluging from the computer.
Click to expand...
Click to collapse
Glad to hear that Ya had me a bit concerned for a minute there...
Hi, I literally opened the nexus 9 out of the box, powered it on & after choosing a wifi network it began updating, the device crashed during this update and now it won't boot! I've tried & searched for everything, anyone have any ideas?
Booting to recovery with HW buttons, wiping cache/userdata/factory reset - Nada!
Can boot into fastboot, no permission to flash as oem unlock is disabled!
I cant get into the tablet to unlock fastboot oem unlock within devOpitons or usb debugging etc, (com.android.phone has stopped on boot) black screen indefinitely.
I can't flash any images while it is locked
surely there must be a simple method?
desperate here
Return it
I'd just return it. I'm no expert, but I'd seek a way to avoid the update during setup and try to postpone it until you unlock developer options and OEM unlock. I'm not sure how you'd bypass the update during setup, but you're in the right place if it's possible.
VermontKindBud said:
I'd just return it. I'm no expert, but I'd seek a way to avoid the update during setup and try to postpone it until you unlock developer options and OEM unlock. I'm not sure how you'd bypass the update during setup, but you're in the right place if it's possible.
Click to expand...
Click to collapse
Hmm, its one of works, just bought bulk amount of them. surely it can't be stuck in an unescapable cycle?
syko9 said:
Hmm, its one of works, just bought bulk amount of them. surely it can't be stuck in an unescapable cycle?
Click to expand...
Click to collapse
Certainly it can. If it started to install the 5.0.2 OTA, there have been a lot of bricks.
cam30era said:
Certainly it can. If it started to install the 5.0.2 OTA, there have been a lot of bricks.
Click to expand...
Click to collapse
Alright thanks for the info, guess it shall be replaced thanks.
syko9 said:
Alright thanks for the info, guess it shall be replaced thanks.
Click to expand...
Click to collapse
Welcome. And FWIW: there's a button for that.
If I remember correctly you can still flash the stock images even with the boot loader locked. Its only custom images that google will not accept unless you unlock boot loader.
Ripx88 said:
If I remember correctly you can still flash the stock images even with the boot loader locked. Its only custom images that google will not accept unless you unlock boot loader.
Click to expand...
Click to collapse
Bootloader has to be unlocked to "fastboot flash" anything.
You can sideload an OTA with a locked bootloader, but you have to be able to access recovery.
cam30era said:
Bootloader has to be unlocked to "fastboot flash" anything.
You can sideload an OTA with a locked bootloader, but you have to be able to access recovery.
Click to expand...
Click to collapse
Ah ok gotcha. My apologizes, I thought I heard somewhere you could. Thank you for the correction.
Ripx88 said:
Ah ok gotcha. My apologizes, I thought I heard somewhere you could. Thank you for the correction.
Click to expand...
Click to collapse
No problem. That's how we learn.
cam30era said:
No problem. That's how we learn.
Click to expand...
Click to collapse
Indeed I'm still new to nexus devices. I've been flashing on Samsung devices for years so I'm still stuck in my Odin ways. Just got the N9 less then a week ago. The whole fastboot thing was foreign at first but I'm getting there lol. Thank you again.
Hello,
situation ist this:
Cyanogen Recovery is installed and there is no rom on the phone. But it won't install a new one through apply update. So I tried installing twrp through fast boot. But it failed with:
FAILED (remote: Device not unlocked cannot flash or erase)
So i tried to unlock it which gave me:
FAILED (remote: oem unlock is disabled)
oem devices gave me tampered = false and unlocked = false
What can I do.
Would appreciate help
Morishno
Flash stock recovery and try unlock again.
Dumb Question but how exactly do I do that?
Just flash it via fast boot? And where do i get it?
Morishno said:
Dumb Question but how exactly do I do that?
Just flash it via fast boot? And where do i get it?
Click to expand...
Click to collapse
You can get it from oneplus downloads section, if you cant find it ask me... Yes you have to flash official stock recovery through fastboot
Exodusche said:
Flash stock recovery and try unlock again.
Click to expand...
Click to collapse
cva_kabil said:
You can get it from oneplus downloads section, if you cant find it ask me... Yes you have to flash official stock recovery through fastboot
Click to expand...
Click to collapse
Not really, OP reports that the unlock command gave him FAILED (remote: oem unlock is disabled)
Hey OP, did you enable OEM Unlocking from Developer options ?
Joshwin Aranha said:
Not really, OP reports that the unlock command gave him FAILED (remote: oem unlock is disabled)
Hey OP, did you enable OEM Unlocking from Developer options ?
Click to expand...
Click to collapse
If not is there any other way?
cva_kabil said:
If not is there any other way?
Click to expand...
Click to collapse
I'm sorry but i do not know any other method that works without flipping that switch in Developer Options.
Joshwin Aranha said:
I'm sorry but i do not know any other method that works without flipping that switch in Developer Options.
Click to expand...
Click to collapse
You dont need to be sorry, thats okay i jus asked... Maybe OP didnt enable oem unlocking.
I didnt enable oem unlocking because it wasnt necessary. The device was unlocked and twrp and cyanogenmod were installed. But somehow cyanogen recovery was installed. Super user was away and I tried to reinstall it. Not knowing the recovery had changed I chose twrp/cwm to install it what resulted in a boot loop. No problem I thought just flash a ROM which didn't worked. No problem just flash a proper recovery it didn't worked. And somehow the device is locked again..
Sorry I was little brief when I said flash stock recovery. I believe if you revert back completely stock you can start the process from the beginning again. That would mean fastboot flash stock recovery then any firmware of OnePlus X. I'm not sure how a bootloader can relock itself.
Exodusche said:
Sorry I was little brief when I said flash stock recovery. I believe if you revert back completely stock you can start the process from the beginning again. That would mean fastboot flash stock recovery then any firmware of OnePlus X. I'm not sure how a bootloader can relock itself.
Click to expand...
Click to collapse
But I couldn't flash twrp.. Is it possible to flash the stock recovery with a locked boot loader? I don't have access to the phone at the moment and i want to gather as much information possible thats why i'm asking
Morishno said:
But I couldn't flash twrp.. Is it possible to flash the stock recovery with a locked boot loader? I don't have access to the phone at the moment and i want to gather as much information possible thats why i'm asking
Click to expand...
Click to collapse
I'm not sure but this has been addressed many times. Comb the threads you will find the information you need.
Exodusche said:
I'm not sure but this has been addressed many times. Comb the threads you will find the information you need.
Click to expand...
Click to collapse
Found a hard brick guide. You mean that?
So I just remembered something was able to help someone else with a similar issue. If you can boot Into something and your rooted download the app Rashr. With it you can flash stock recovery and be back in business.
The problem is i dont have anything to Boot
//UPDATE: So I tried booting with fastboot boot but it said cannot boot device isn't unlocked.
Edited
So i managed to save the Phone using the Hard Brick Guide. Thanks everyone!
Thank goodness for the hard brick guide. ?
Exodusche said:
I think your gonna have to go through the hard bricked guide.
Click to expand...
Click to collapse
Yeah i did that and it worked thank you
Hello,
I have tried and searched a lot, but can't find solution.
ADB,Kindle drivers are installed.
Tablet is rooted with kingroot.
Adb is working quite well, but can't enter fastboot mode.
adb reboot bootloader only restarts tablet.
How can I initate fastboot mode?
P.S OS: Windows 10 x64
arshileus said:
Hello,
I have tried and searched a lot, but can't find solution.
ADB,Kindle drivers are installed.
Tablet is rooted with kingroot.
Adb is working quite well, but can't enter fastboot mode.
adb reboot bootloader only restarts tablet.
How can I initate fastboot mode?
P.S OS: Windows 10 x64
Click to expand...
Click to collapse
Seems device has some history. If the guidance in the first link fails to work (and it probably won't) you should probably go for the full automated unlock via 1-click.
https://forum.xda-developers.com/kindle-fire-hdx/general/how-to-root-unlock-hdx-noobies-t3916167
https://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014
arshileus said:
Hello,
I have tried and searched a lot, but can't find solution.
ADB,Kindle drivers are installed.
Tablet is rooted with kingroot.
Adb is working quite well, but can't enter fastboot mode.
adb reboot bootloader only restarts tablet.
How can I initate fastboot mode?
P.S OS: Windows 10 x64
Click to expand...
Click to collapse
Guessing, without more info:
With HDX off press and hold power and volume down buttons.
Or
Depending on which twrp recovery (if any) is installed, you can reboot to the bootloader from there
gwardsc65 said:
Guessing, without more info:
With HDX off press and hold power and volume down buttons.
Or
Depending on which twrp recovery (if any) is installed, you can reboot to the bootloader from there
Click to expand...
Click to collapse
Nope; button technique only works with unlocked bootloader.
Davey126 said:
Nope; button technique only works with unlocked bootloader.
Click to expand...
Click to collapse
So, what's the solution?
arshileus said:
So, what's the solution?
Click to expand...
Click to collapse
https://forum.xda-developers.com/ki...-mode-kindle-fire-hdx-7-t3923367/post79381593
Davey126 said:
https://forum.xda-developers.com/ki...-mode-kindle-fire-hdx-7-t3923367/post79381593
Click to expand...
Click to collapse
Sorry, but maybe you even didn't read my post )
I have rooted device, not it needed to be unlocked.
But while trying adb reboot bootloader, it doesn't go to fastboot but restarts.
arshileus said:
Sorry, but maybe you even didn't read my post )
I have rooted device, not it needed to be unlocked.
But while trying adb reboot bootloader, it doesn't go to fastboot but restarts.
Click to expand...
Click to collapse
I did and am well aware of the behavior. Use 1-click to fully unlock the bootloader which will restore your ability to boot to bootloader.
Davey126 said:
I did and am well aware of the behavior. Use 1-click to fully unlock the bootloader which will restore your ability to boot to bootloader.
Click to expand...
Click to collapse
I can't find download link of 1-Click unlocker, I have sent letter for post author, but no answer.
Can you send it to me?
arshileus said:
I can't find download link of 1-Click unlocker, I have sent letter for post author, but no answer.
Can you send it to me?
Click to expand...
Click to collapse
The developer (@draxie) has requested that he be the sole source for distribution which I respect. He typically responds to PMs within a few days.
UPDATE (03/09/2019):
This thread is now dedicated to the development of the Vertu Aster P replica, which has MTK's MT6755 Helios P10 chipset.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Hi All,
I've just recently bought a Vertu Aster P replica, which came pre-loaded with a Vertu-themed (skinned) version of Android 6.0 Marshmallow. In the 'About Device' menu, however, the developers have (not so cleverly) disguised it to say Android 8.1.0 (Oreo). Why they would do this, rather than just taking Oreo and skinning it with the Vertu theme, I don't know. Anyway, I've gone and hard bricked the phone while trying to install a custom recovery, and it will not turn on or charge. It is still recognised when plugged into the laptop, so if I had the original ROM that it came with, I would be able to reflash it and have a working phone again. Sadly, I cannot find the ROM for it anywhere online. I can find the ROM's for the Vertu Signature Touch replica and Vertu Ti, and others, but not for the new Aster P replica, which uses the MT6755 chipset. Here are a few photos of the phone's OS. So, I'm wondering if anyone might be able to point me in the right direction of where I might be able to find this ROM. I have already been in contact with the company I bought it from. Still waiting to hear back from them. Hopefully they can just send me a download link.
Chris
Still living in hope that someone has access to the ROM for this phone.
Someone kind enough eventually came along and sent me the ROM. Flashed it and my phone now works again. Lesson learnt. ALWAYS DO A BACKUP BEFOREHAND.
I will upload it myself and make it available on here for other Aster P (replica) owners shortly.
Chris
Here it is.
https://www.needrom.com/download/vertu-aster-p-mt6755-chinese-clone-firmware/
I have also successfully managed to root the device using Magisk. If anyone else has the same device and wishes to root it, I'll guide you through the method if need be.
Chris
chris8189 said:
I have also successfully managed to root the device using Magisk. If anyone else has the same device and wishes to root it, I'll guide you through the method if need be.
Chris
Click to expand...
Click to collapse
Chris are you fastbooting to Recovery or actually flashing to the recovery partition?
I found a TWRP on XDA forums which @lopestom made for the BLU Pure XR P0030UU smartphone -
https://forum.xda-developers.com/pure-xr/development/twrp-twrp-3-1-x-x-blu-pure-xr-p0030-t3623865
The above phone also has the MT6755 P10 Helios chip, same as the Vertu Aster P clone, so I thought I would try and port the ROM over for the Vertu Aster P replica.
I got an error while doing the repack, however @ashyx managed to perform a successful repack on the image file and the phone does indeed boot up the TWRP. Problem is, there is no touch functionality. Plugging in an OTG mouse however might work, or likewise flashing the recovery image file to the boot partition, doing what you need to do in TWRP, and then flashing the stock (or modified) boot image back. I have put the feelers out for the kernel source, so (hopefully) we can then do the necessary tweaks to make TWRP function correctly, or even better, build a TWRP from source (if we can get it). Below is the link to the TWRP file.
https://mega.nz/#!J45FWIzJ!aFyFooO5aOtxjFany_osL4BpRRQSMljQjtfnYSFKDis
Chris
ashyx said:
Chris are you fastbooting to Recovery or actually flashing to the recovery partition?
Click to expand...
Click to collapse
I am flashing the recovery using SP Flash Tool (for MTK devices) to the recovery partition.
Chris
chris8189 said:
I am flashing the recovery using SP Flash Tool (for MTK devices) to the recovery partition.
Chris
Click to expand...
Click to collapse
Does this device not support fastboot?
Also does touch work if flashed to the boot partition?
ashyx said:
Does this device not support fastboot?
Also does touch work if flashed to the boot partition?
Click to expand...
Click to collapse
Yes, the device does support fastboot mode.
When flashing this TWRP to the boot partition, touch functionality, and all aspects of TWRP work perfectly.
Chris
chris8189 said:
Yes, the device does support fastboot mode.
When flashing this TWRP to the boot partition, touch functionality, and all aspects of TWRP work perfectly.
Chris
Click to expand...
Click to collapse
What happens if you just Fastboot boot 'recovery.img' rather than flashing it?
ashyx said:
What happens if you just Fastboot boot 'recovery.img' rather than flashing it?
Click to expand...
Click to collapse
When I do that, it says that oem unlock is false, however in the developer options on my phone, I have the OEM Unlock turned on, so I don't understand why it's saying that. When type in 'fastboot oem unlock', my phone gives me the option to unlok the bootloader, or not, with the volume up and down keys. Volume up being unlock the bootloader and volume down being don't unlock the bootloader. When I press volume up, nothing happens. If I press volume down, however, it allows me to not unlock the bootloader, lol. Has an extra layer of security been added to this device? Is the OEM unlock option in my dev options just a fake toggle switch?
Chris
chris8189 said:
When I do that, it says that oem unlock is false, however in the developer options on my phone, I have the OEM Unlock turned on, so I don't understand why it's saying that. When type in 'fastboot oem unlock', my phone gives me the option to unlok the bootloader, or not, with the volume up and down keys. Volume up being unlock the bootloader and volume down being don't unlock the bootloader. When I press volume up, nothing happens. If I press volume down, however, it allows me to not unlock the bootloader, lol. Has an extra layer of security been added to this device? Is the OEM unlock option in my dev options just a fake toggle switch?
Chris
Click to expand...
Click to collapse
What result do you get for:
fastboot oem device-info
I tried it and the command doesn't work.
chris8189 said:
I tried it and the command doesn't work.
Click to expand...
Click to collapse
Try:
fastboot getvar unlocked
Typing 'fastboot getvar unlocked' confirms that the bootloader is locked. It says 'unlocked :no'
Chris
chris8189 said:
Typing 'fastboot getvar unlocked' confirms that the bootloader is locked. It says 'unlocked :no'
Chris
Click to expand...
Click to collapse
It definitely says OEM_UNLOCK enabled in developer settings and you're issuing the oem unlock command while in FASTBOOT mode?
ashyx said:
It definitely says OEM_UNLOCK enabled in developer settings and you're issuing the oem unlock command while in FASTBOOT mode?
Click to expand...
Click to collapse
Correct.
I read up online about it and some MTK devices don't support bootloader unlocking. Or, you have to obtain an 'unlock code' from the manufacturer.
Chris
chris8189 said:
Correct.
I read up online about it and some MTK devices don't support bootloader unlocking. Or, you have to obtain an 'unlock code' from the manufacturer.
Chris
Click to expand...
Click to collapse
Probably a daft question, but have you actually tried booting the unpacked twrp recovery image?
If these devices are so similar maybe the kernel is too.
ashyx said:
Probably a daft question, but have you actually tried booting the unpacked twrp recovery image?
If these devices are so similar maybe the kernel is too.
Click to expand...
Click to collapse
It doesn't load. It bootloops. So they have different kernels.
Chris