TWRP 2.8.5.0 YotaPhone 2 recovery imageAfter the bare bones modded stock recovery for YotaPhone 2 it's time for something more advanced. The TeamWin Recovery Project 2, or TWRP2 is just that: a fully fledged, graphical, touch enabled, custom recovery.
This recovery image for YotaPhone 2 is still an alpha version, so expect some rough edges. Which leads me to:
Disclaimer
I am not responsible for damaged or bricked devices. If you follow instructions in this post, then YOU are making the choice to tinker with your device. You are likely to void your warranty by doing so, and on a bad day you might even damage or brick your device.
What is it?
It's a recovery image for YotaPhone 2 based on TWRP2 custom recovery, and the stock kernel from Yota Devices. You can boot it ad-hoc, or flash it permanently to the recovery partition. Use it to root, install software, make backups, update ROMs etc.
What can you do with it?
- adb root & shell access
- All TWRP 2.8.5.0 functionality (except MTP)
- install update zips (signed with testkeys (e.g. SuperSU), Yota Devices software, and also unsigned zips like Xposed framework.
- You can sideload packages, but also install them from internal storage (e.g. Download folder)
- make partition backups
- root your device
What can it NOT do?
- In this recovery image the MTP functionality of TWRP is disabled, it doesn't play nice with YD's kernel.
What do you need?
- YotaPhone 2 (YD201) with Lollipop 5.0
- Some technical confidence to cope with quirks that come with an alpha version
- USB cable with a PC or laptop on one end
Steps overview:
NOTE: I used less detail in this post than the previous recovery thread, please look there for more detail.
1) backup (sync stuff, copy photos off, use a backup app etc, use search if unsure how to)
2) Install adb and fastboot if not yet installed. (For Windows look e.g. here, for linux the fastest is probably to install Android SDK with platform tools, see here If this is not enough info to get you started, please use xda search!)
3) Unlock the bootloader if you haven't done so before (read warning below!)
4) Download recovery image: recovery_twrp_yd201_alpha2.img
5) boot or flash the recovery image
Unlocking bootloader:
Warning: It is currently not known how to re-lock the bootloader. This means you cannot completely undo the next step as of yet. This might have consequences for sending the device in for repairs, if they check for this, and deem it a (warranty) problem.
See stock recovery thread for unlock steps
BOOT the recovery image:
a) First: put the device in fastboot/download mode:
Power off with USB cable disconnected, then hold volume down key while inserting USB cable (which should already be in your PC on the other end).
You should see a black screen with a tiny white: downloading...
b) Boot the recovery image:
Code:
fastboot boot path/to/recovery_twrp_yd201_alpha2.img
Alternatively, flash the recovery image (overwriting the stock recovery):
Code:
fastboot flash recovery recovery_twrp_yd201_alpha2.img
Problems & FAQ
Q: It doesn't work!!1!
A: Please provide plenty of detail about error messages, which step, what versions etc. Without providing any detail you'll look silly. TWRP has it's own logfile that you can copy to (virtual) SD card, and access from there.
Kernel sourcecode:
In this recovery image is Yota Device's version of the Linux kernel v3.4.0 for YotaPhone 2. Yota Devices are required by the GPLv2 license to release the source code for this kernel, but so far they haven't taken that step or even shown intention to do so as far as I know. The YotaPhone firmwares and also this recovery image are in effect violating the GPLv2 license if the situation does not change. Attempts to contact Yota Devices on the subject through support, press departement, and an attempt to contact Yota Device's management, have gone pretty much unanswered as of writing. I'm hoping they're just busy making great devices instead of being unwilling.
If you would like to help future custom ROM development for YotaPhone 2 please do the following:
Encourage Yota Devices through their twitter or facebook accounts to publish the Kernel sourcecode for YotaPhone 2, and ask them to support the open source Android community. You can also submit a request through their support page (hint: choose 'sales' as category, otherwise you'll have to enter lots of details. Be polite!).
Info & credits::
TWRP2 is created and maintained by TeamWin. Please donate through their site if you enjoy their work!
Recovery image for YP2: SteadyQuad
Version: alpha2 based on TWRP 2.8.5.0 with Yota Devices kernel (1.39 EU1)
Thanks to: TeamWin for TWRP, @Dees_Troy for hints for getting it up and running, @Jeopardy for testing, @Chainfire for SuperSU and lastly Yota Devices for a great device.
Linking to this recovery image:
Please don't link directly to the download image, link to this post instead. That way users can get the most recent version and any updated info. (It's an alpha version after all)
Created: 2015-06-23
Last Updated: 2015-06-24
SteadyQuad said:
If you would like to help future custom ROM development for YotaPhone 2 please do the following:
Encourage Yota Devices through their twitter or facebook accounts to publish the Kernel sourcecode for YotaPhone 2, and ask them to support the open source Android community. You can also submit a request through their support page (hint: choose 'sales' as category, otherwise you'll have to enter lots of details. Be polite!).
Click to expand...
Click to collapse
I just approached Yota for the Yotaphone 2 kernel's source code, and they gave me a link to Yotaphone's developer page (https://yotaphone.com/developer/). It's not there (yet). Maybe they'll release the source code once they finalize the SDK...? That, or the recipient of my query didn't understand the question.
Regarding the recovery: works flawlessly. :good:
Jeopardy said:
I just approached Yota for the Yotaphone 2 kernel's source code, and they gave me a link to Yotaphone's developer page (https://yotaphone.com/developer/). It's not there (yet). Maybe they'll release the source code once they finalize the SDK...? That, or the recipient of my query didn't understand the question.
Regarding the recovery: works flawlessly. :good:
Click to expand...
Click to collapse
Yeah, I got the same boxed response and replied that it was not relevant, and explained why. Their SDK (for app development) has nothing to do with the kernel sourcecode, and at the moment their developer pages do not mention anything about kernel sources. I think that their support page tickets are handled by an external company (quicksupportlink.com), that is dependent on Yota for definitive answers, and they're probably instructed to send this reply. At least Yota will get reports from them, with hopefully lots of requests for kernel source. On the press page there's email addresses of 2 press ladies, you could try those too (as I did).
So nice to see this! Looking forward to trying, once mine comes.
Jeopardy said:
I just approached Yota for the Yotaphone 2 kernel's source code, and they gave me a link to Yotaphone's developer page (https://yotaphone.com/developer/). It's not there (yet). Maybe they'll release the source code once they finalize the SDK...? That, or the recipient of my query didn't understand the question.
Regarding the recovery: works flawlessly. :good:
Click to expand...
Click to collapse
Hi Jeopardy,
Next great mod by you! Congrats! :good:
BTW: Does it mean that your version of TWRP recovery doesn't work with 1.44 EU firmware?
Or if I flash this recovery it will work, but the kernel is one step back to 1.39 version?
Thanks in advance for the info.
Regards!
zencooler said:
Hi Jeopardy,
Next great mod by you! Congrats! :good:
BTW: Does it mean that your version of TWRP recovery doesn't work with 1.44 EU firmware?
Or if I flash this recovery it will work, but the kernel is one step back to 1.39 version?
Thanks in advance for the info.
Regards!
Click to expand...
Click to collapse
This recovery is done by SteadyQuad, only tested by me.
But I can answer your question: this recovery works just fine with 1.44 EU firmware. I have flashed it myself successfully. I'm quite sure it is not tied to the firmware version in any way.
Jeopardy said:
This recovery is done by SteadyQuad, only tested by me.
But I can answer your question: this recovery works just fine with 1.44 EU firmware. I have flashed it myself successfully. I'm quite sure it is not tied to the firmware version in any way.
Click to expand...
Click to collapse
Hi again,
Soory for the mistake (I just replied not for the first post). Once again sorry SteadyQuad and congrats for you again!
Jaopardy, thanks for the quick info and confirmation it works on 1.44 EU firmware! It's a good news
Regards!
Jeopardy said:
...Yotaphone 2 kernel's source code...
Click to expand...
Click to collapse
https://srv-fs1.yotadevices.com/public/file/5OyPZKU7Vk6HvML_YZpuRQ/yotaphone2_kernel.tar.gz
elatllat said:
https://srv-fs1.yotadevices.com/public/file/5OyPZKU7Vk6HvML_YZpuRQ/yotaphone2_kernel.tar.gz
Click to expand...
Click to collapse
Thanks, this archive was already known, it contains a kernel snapshot of end of june 2015. I put it on github with some small adjustments to make it build initially. (and it actually boots
I've also put up an initial device and vendor tree there, although both are pretty far from complete/correct at this point.
BTW @elatllat where did you get the link from?
SteadyQuad said:
...where did you get the link from?
Click to expand...
Click to collapse
I did a xda forum search and found that link, this thread, and thought I should link them up.
(as it's not widely known)
so anyone tried xposed??
varun.gid said:
so anyone tried xposed??
Click to expand...
Click to collapse
Yeah. It works as expected. No problems for me.
Has any flashed this recovery permanently over 1.60
Sent from my YD201 using Tapatalk
adamo86 said:
Has any flashed this recovery permanently over 1.60
Sent from my YD201 using Tapatalk
Click to expand...
Click to collapse
You can use this TWRP recovery image with 1.60 just fine (the recovery image is pretty much independent of firmware version).
SteadyQuad said:
You can use this TWRP recovery image with 1.60 just fine (the recovery image is pretty much independent of firmware version).
Click to expand...
Click to collapse
I am having this issue with my yotaphone the epd freezen for a long time I'm not sure if it's twrp. At the moment I flashed the stock modified recovery and it stopped freezing for the last 24hrs i will report back in a few days
Sent from my YD201 using Tapatalk
adamo86 said:
I am having this issue with my yotaphone the epd freezen for a long time I'm not sure if it's twrp. At the moment I flashed the stock modified recovery and it stopped freezing for the last 24hrs i will report back in a few days
Sent from my YD201 using Tapatalk
Click to expand...
Click to collapse
TWRP is only doing anything when you boot into recovery. When you're just using your phone normally, Android doesn't even know about TWRP. So your EPD freezing must be something else.
May be my phone is dieing?
Sent from my YD201 using Tapatalk
SteadyQuad said:
TWRP is only doing anything when you boot into recovery. When you're just using your phone normally, Android doesn't even know about TWRP. So your EPD freezing must be something else.
Click to expand...
Click to collapse
Your right my phone is bust does anyone have yota contact details
Sent from my YD201 using Tapatalk
adamo86 said:
Your right my phone is bust does anyone have yota contact details
Have you done a factory reset?
My EPD was freezing and system clock screwing up. Factory reset, wiped caches etc, then cleared out a few apps didn't need and some system crap, seems to be ok now. Battery drain still occurs but I'm resigned to that unfortunately, just hoping 5.1 fixes the issue (and that we get it soon.).
If nothing works you could try emailing [email protected], hopefully you get somewhere. Their customer service was very good initially for me but seems to take a very long time to get anything done nowadays.
Either way good luck and I hope your phone gets some decent function back eventually .
Click to expand...
Click to collapse
zute333 said:
adamo86 said:
Your right my phone is bust does anyone have yota contact details
Have you done a factory reset?
My EPD was freezing and system clock screwing up. Factory reset, wiped caches etc, then cleared out a few apps didn't need and some system crap, seems to be ok now. Battery drain still occurs but I'm resigned to that unfortunately, just hoping 5.1 fixes the issue (and that we get it soon.).
If nothing works you could try emailing [email protected], hopefully you get somewhere. Their customer service was very good initially for me but seems to take a very long time to get anything done nowadays.
Either way good luck and I hope your phone gets some decent function back eventually .
Click to expand...
Click to collapse
I got rid of it I tried everything downgraded wiped data etc clean install then did ota still freezes after a while. I did clean install of Rom twice. I think the screen is dying or something inside it is loose because the epd started off as freezes then moved to very light grey instead of black and would refresh but old pics and widget would be visible and it started to flicker from one side then it would start to work after a while then fade again etc. When these freezes happened I would get a blue screen when phone was rebooted and it would slow device down then reboot it self until the screen got unfrozen. I noticed even after installing rom new the screen would some time be frozen. It's only sometimes the screen would be reseted if I did a new installation.
I will miss my yotaphone. I will be getting a nexus 6p or v10.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
Related
Alright, so following some prodding, searching, and questioning, I flashed MIUI V6 to my BLU Vivo Air alongside TWRP.
I will update this post with a detailed, step-by-step guide including my own personal mirrors for your convenience and those of you without 4PDA accounts, which is the Russian equivalent of XDA.
Upon booting, I noticed apps force closing without being launched. Namely Hangouts and Newsstand. I'm sure reinstalling them will resolve the issue rather quickly.
Stay tuned for updates.
Update 1:
TWRP had difficulty mounting data and cache for me, and was unable to format them. This led to applications force closing, window mishaps, and accounts glitching out. I just flashed Carliv recovery, and flashed MIUI with it. Flashing gapps at the moment, and will update you on my progress.
Update 2:
Currently attempting to format data (success), cache (success), and dalvik (success).
Update 3:
Rebooting into MIUI V6, checking if I've entered a bootloop.
5 seconds - Boot animation reached, "MIUI Pro."
165 seconds - Still booting.
180 seconds - Setup screen reached, MIUI V6 flashed successfully.
Update 4:
Google apps flashed successfully, no redraws or force closes this time. Had an issue with the keyboard not registering as being selected, Google voice typing appeared as the default. Pull down notification shader and "choose input method" to select MIUI Smart Keyboard. Signed into Google successfully. Will run preliminary tests on video playback, camera, and multitasking.
Guide:
If you mess up your phone, it is on you, and I am not to be held liable for your actions. This is your responsibility. A lack of planning on your part does not constitute an emergency on mine. With that out of the way, if you encounter troubles, I am more than happy to help you.
Step 1:
Root your phone using one of the links provided. Click HERE for method 1, or HERE for method 2. I personally used method 1 because it was the first I saw. They both get the job done.
Step 2:
Install THIS application (Settings -> Security -> Unknown Sources), and install a recovery. I installed Carliv recovery, and had no problems with it. You can also install TWRP, however, it had issues mounting data and cache. This left it unable to factory reset when I flashed MIUI, which subsequently led to problems. I do not recommend flashing TWRP - You have been warned. Carliv recovery says it can't "mount" cache, although when formatting it does so without a problem. I believe Carliv is supposed to be touch-based, although the touches weren't responding for me. The controls are as follows: Volume +/- for navigating, Power for selecting, and the Back key for, you guessed it, going back.
Step 3:
Install MIUI V6, located HERE, and then install Google Apps, located HERE. After installing, factory reset the device from recovery and reboot into the system. I posted my timestamps at the top of the post, so you can get an idea of how long your flash/boot process should take.
Step 4:
Basic setup. Be ready to fix your keyboard if you had the same issue I did, which isn't even necessarily a problem. Choose WLAN network and sign into your accounts, then you're good to go.
To root the ROM, I recommend finding "iRoot" for your computer. Then boot to recovery and install the SuperSU zip, as it's better than the root app which comes with the iRoot method.
Enjoy your ROM, and be sure to thank our Ruski comrades over at 4PDA!
Special thanks to @DvDwx. (research), @itsJohnuno (answers), and @Milly7 (testing).
All download links are being hosted by me, and I recommend creating mirrors of your own as safety precautions in the event that the files are removed or become unavailable.
Have a phenomenal day or night, possibly even both. If you have any questions, I'll do my best to answer them.
Nice Guide ;D
DvDwx. said:
Nice Guide ;D
Click to expand...
Click to collapse
Push that Guide to Android Development thread, that is a ROM ;D
We need talk with our Forum Administrator to Manage some Topics and Fuse KAZAM Tornado 348 with BLU Vivo Air menu... and try explain to this administrator about the re-branding process to he can add the other phones like AllView, Fly and Gionee to this Phone Menu Threads topics ;D
:highfive:
DvDwx. said:
Push that Guide to Android Development thread, that is a ROM ;D
We need talk with our Forum Administrator to Manage some Topics and Fuse KAZAM Tornado 348 with BLU Vivo Air menu... and try explain to this administrator about the re-branding process to he can add the other phones like AllView, Fly and Gionee to this Phone Menu Threads topics ;D
:highfive:
Click to expand...
Click to collapse
I didn't create the resources in the ROM, I just made a guide to flashing ROMs using a specific ROM as an example. I would feel bad posting it in the developer section because I don't wish to be given credit for the ROM. I didn't make it.
Ilxaot said:
I didn't create the resources in the ROM, I just made a guide to flashing ROMs using a specific ROM as an example. I would feel bad posting it in the developer section because I don't wish to be given credit for the ROM. I didn't make it.
Click to expand...
Click to collapse
i understand that ;D
on my WonderMedia WM8880 Tablet project i share the projects from other developers... but i asked they to have permission to share that, and leave on post the credits with their names... maybe if you talk with developer on 4PDA for permission to do it or ask him if it is possible he share he ROM Project here is will be perfect... anyway Good Guide to Flash this ROM :highfive:
Could you please describe how to flash the carliv recovery. I downloaded the app in step 2 but I can't even seem to install the twrp recovery because phone reboots into stock recovery and I don't even see an option for the carliv one.
dimasp6 said:
Could you please describe how to flash the carliv recovery. I downloaded the app in step 2 but I can't even seem to install the twrp recovery because phone reboots into stock recovery and I don't even see an option for the carliv one.
Click to expand...
Click to collapse
You need have root to do this... And sometimes the root dont work correctly and dont stay giving the rights to aplicantion can work...
DvDwx. said:
You need have root to do this... And sometimes the root dont work correctly and dont stay giving the rights to aplicantion can work...
Click to expand...
Click to collapse
I do have root with Kingroot. So I just need to keep trying until it successfully flashes?
Edit: The app mlp RIO recovery installer constantly freezes on me not allowing me to flash any of the recoveries.
dimasp6 said:
I do have root with Kingroot. So I just need to keep trying until it successfully flashes?
Edit: The app mlp RIO recovery installer constantly freezes on me not allowing me to flash any of the recoveries.
Click to expand...
Click to collapse
You can also try iRoot. Install SuperSU and try using it as the root granter for the recoveries.
Does the magnetometer (compass) work for you guys on the miui rom? It doesn't work for me.
ron580 said:
Does the magnetometer (compass) work for you guys on the miui rom? It doesn't work for me.
Click to expand...
Click to collapse
The app itself hadn't worked for me, I tried it earlier. Have you tested another app? It may be the stock app. I haven't messed with it much, not a huge navigator myself. [emoji14]
Ilxaot said:
The app itself hadn't worked for me, I tried it earlier. Have you tested another app? It may be the stock app. I haven't messed with it much, not a huge navigator myself. [emoji14]
Click to expand...
Click to collapse
The senor doesn't work at all using this rom & google maps wont work properly without it. Also the time on the lock screen and the home screen show different times about an hour apart Other than that everything else works fine.
ron580 said:
The senor doesn't work at all using this rom & google maps wont work properly without it. Also the time on the lock screen and the home screen show different times about an hour apart Other than that everything else works fine.
Click to expand...
Click to collapse
Yeah. I've also noticed that downloading updates is botched, because it downloads an update for a different phone model. If you try to install it the installation will fail, but it won't hurt your phone.
All in all it's a pretty solid ROM for me.
Ilxaot said:
Yeah. I've also noticed that downloading updates is botched, because it downloads an update for a different phone model. If you try to install it the installation will fail, but it won't hurt your phone.
All in all it's a pretty solid ROM for me.
Click to expand...
Click to collapse
Yes its a great rom maybe we can ask the developer if he can fix the issues for us on 4pda. I would do it but i couldn't register on 4pda i kept on receiving an error.
request
Ilxaot said:
All in all it's a pretty solid ROM for me.
Click to expand...
Click to collapse
Known bugs? any screenshot running this ROM please? I'd like to see some, I'm not updated on what's going on with MIUI and btw, great work! thanks in advance!
JesusEMC said:
Known bugs? any screenshot running this ROM please? I'd like to see some, I'm not updated on what's going on with MIUI and btw, great work! thanks in advance!
Click to expand...
Click to collapse
I'll post some tomorrow. Re-read the past 5-6 posts and you'll see the bugs. I think you'll like it. MIUI is certainly different (settings default apps) and such, but it's a formidable ROM and performs relatively well.
ron580 said:
Yes its a great rom maybe we can ask the developer if he can fix the issues for us on 4pda. I would do it but i couldn't register on 4pda i kept on receiving an error.
Click to expand...
Click to collapse
on Captcha you need count the numbers and ignore the russian Letters Like for exemple -> ##22###16## -> 22+16= 38
to can finish the registration... and no, you don't need use VPN or Proxy to create the account :highfive:
ron580 said:
Yes its a great rom maybe we can ask the developer if he can fix the issues for us on 4pda. I would do it but i couldn't register on 4pda i kept on receiving an error.
Click to expand...
Click to collapse
I'm sure he knows about it...and the guy is activity working on the ROM...except the latest update seems to just boot loop from what I've read, rather just wait and see.
itsJohnuno said:
I'm sure he knows about it...and the guy is activity working on the ROM...except the latest update seems to just boot loop from what I've read, rather just wait and see.
Click to expand...
Click to collapse
Our Buddy @SSJGohon found the kernel source code and already shared on some topic(i Already re-shared that on Cyanogen Mod to Mediatek SoC's Development thread... but anyone there say nothing about it... and already shared on 4PDA to maybe the MiUi developer can Bring something to All...). i already downloaded and already start my research about what can be maked with that and for sure have a possibility to we have a custom Kernel and maybe Custom ROM like PURE AOSP, AOSPA... but Cyanogen Mod is more difficult because we don't have a updated Repo Source from MediaTek to work like Driver Blobs to GPU, Bluetooth, Wifi Drivers... etc
My real problem is i don't have all skills to make a custom kernel to Mediatek SoC because a lot of things change from Qualcomm to Mediatek.. but if anyone here want to try development that just search the topics with @SSJGohon comments replays :highfive:
Ilxaot said:
I'll post some tomorrow. Re-read the past 5-6 posts and you'll see the bugs. I think you'll like it. MIUI is certainly different (settings default apps) and such, but it's a formidable ROM and performs relatively well.
Click to expand...
Click to collapse
I've already installed the ROM, it runs smoothly! You were right, I really like it! I had an issue trying to format /data, it took like 15 minutes, and did a hard reset (pressed power button for a few seconds) and tried to format again and it worked. Im a little bit worry cause I've had 2 radom reboots so far.. Any idea of what has happened to me?
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
I'm missing something or I'm just watching text? Lol @satana.nik.1996 I saw already this posted on 4PDA, it has idol3 detected on TWRP to install things instead of Ido?
EDIT: well indeed it works, and it is fast as ****, the problem it is only has russian language and i can't test if the twrp is ido or idol3
Enviado desde mi 6045B mediante Tapatalk
Any chance of getting for idol 347?
Thanks for the update! now has all the languages, anyways it had a less bug with other device name, just edited the initrd/default.prop and now all good, it is really really fast, it install roms and backups as twice the old speed lol
Guys, do you mind kicking me in the right direction to find this? Would like to try it out, but can't seem to find it on 4PDA... Thanks!
@kt-Froggy i don't know if i'm allowed to do this, but satanik if you want the link removed from here tell me lol
https://4pda.ru/forum/index.php?showtopic=753533&view=findpost&p=59165103 here is the first post, only russian lang
https://4pda.ru/forum/index.php?showtopic=753533&view=findpost&p=59176110 here is the translated one, but has the device as p839v55 instead of idol3
https://4pda.ru/forum/index.php?showtopic=753533&view=findpost&p=59196559 here is the one i edited from satanik to change the device to idol3
you need an 4PDA account (except for the translated p839v55 one), if @satana.nik.1996 wants to post it here i will do it too
panchovix said:
you need an 4PDA account
Click to expand...
Click to collapse
Thank you! No idea how I missed that in the ROM thread ("Прошивки")... Duh!
My Russian is a bit better than my English, and I do have an account on 4PDA.
Of course, thanks to @satana.nik.1996, too!
@kt-Froggy yeah you are lucky tho, i just use translate
4PDA has some goods Roms too, @andrejchern for example did AOSP_6045Y and Xperia_6045Y, they are really good for battery life (i'm using Xperia_6045Y now)
Can this one deal with encrypted partitions?
Twrp 3.0.2.0 for idol 3 [4.7] 6039 version
Hi!
This is TWRP 3.0.2.0 @santana.nik1996 version modded by me for Idol 3 [4.7] 6039 version!
[*]Micro SD_Card is the main partition.
[*] You can mount System, data, cache,Modem,Persist,USB-OTG,Internal SDCard (internal storage)
[*] It starts in MTP-ADB mode
twrp-3.0.2.0-satana.nik.1996_modded.img
https://mega.nz/#!lpBHkILJ
key: !2Jso7ocAqlb8YWtPI-30BY9DKXv-QK4sueDbEd2XzKE
If you want a easy way just download and execute this exe file!
twrp-3.0.2.0-satana.nik.1996_modded.exe
https://mega.nz/#!k1x3VJqa
key: !dic2Q_hrcIaDmqRjJ6sQ_-9i5lSUj0Q5mNItmAoxTKU
[TESTED AND WORKING!]
NOTE: There is a issue ( from default image), if TWRP enter in sleep mode ( lock screen ) it get issues, at start up go to settings -> screen -> unselect "Enable screen timeout" and everything will be fine.
@santana.nik1996 do you know how to fix this? Thanks! ( Great Job by the way! )
This is default version only change the mounting options, use the exe to install it!
twrp-3.0.2.0-satana.nik.1996.exe
https://mega.nz/#!M4A1QJAZ
key: !ZbmyJQ2guHkMT-bE6JQ9MGJvPpBG8astcePetZrqo-Q
Enjoy it!
.
Well since he posted the 4.7 already, i will post the one i modded for the 5.5 version, obs all the credits for satana.nik1996
This is TWRP 3.0.2.0 Santana.nik1996 edited for Idol 3 [5.5] 6045 Version, he posted one working already on 4PDA here https://4pda.ru/forum/index.php?showtopic=753533&view=findpost&p=59176110, but i just changed the p839v55 to idol3 (on default.prop in initrd)
as i said, very fast (the time to install roms is like 50% less more or something like that), tested to install multiple roms and no problems so far
the .img is here https://mega.nz/#!t54mgBbT!WcJiSByzyuTZFcRXOxXPSePKmioMOmiTU9TPfVbwW1k
Install from TWRP 3.0.0.0 or 3.0.1.0 with install image option, or if you are lucky via fastboot
PS: i suggest if this possible, to an admin, to move thsi thread from general to Android Development, if possible
Installed OK, but didn't have a chance to really test it yet... One little issue found so far - "Reboot Recovery" (from TWRP itself) doesn't seem to work... It boots straight to the OS. But I can reboot to recovery from the OS, and also by Pwr+VolUp from the "off" state, so not a big deal...
kt-Froggy said:
Installed OK, but didn't have a chance to really test it yet... One little issue found so far - "Reboot Recovery" (from TWRP itself) doesn't seem to work... It boots straight to the OS. But I can reboot to recovery from the OS, and also by Pwr+VolUp from the "off" state, so not a big deal...
Click to expand...
Click to collapse
Twrp 3.0.0-0 do the same, it doesn´t boot on recovery again, it starts O.S.
@kt-Froggy EDIT: my bad, yes you are right lol, anyways when you put reboot, just press vol + (without power) and no problem, on 3.0.1.0 this worked well
panchovix said:
Well since he posted the 4.7 already, i will post the one i modded for the 5.5 version, obs all the credits for satana.nik1996
This is TWRP 3.0.2.0 Santana.nik1996 edited for Idol 3 [5.5] 6045 Version, he posted one working already on 4PDA here https://4pda.ru/forum/index.php?showtopic=753533&view=findpost&p=59176110, but i just changed the p839v55 to idol3 (on default.prop in initrd)
as i said, very fast (the time to install roms is like 50% less more or something like that), tested to install multiple roms and no problems so far
the .img is here https://mega.nz/#!t54mgBbT!WcJiSByzyuTZFcRXOxXPSePKmioMOmiTU9TPfVbwW1k
Install from TWRP 3.0.0.0 or 3.0.1.0 with install image option, or if you are lucky via fastboot
PS: i suggest if this possible, to an admin, to move thsi thread from general to Android Development, if possible
Click to expand...
Click to collapse
Hi!
When it enter in lock screen by it selfe, can you unlock screen right or get issue?
.
persona78 said:
Hi!
When it enter in lock screen by it selfe, can you unlock screen right or get issue?
.
Click to expand...
Click to collapse
do you mean, when the phone locks itself (without using it for 1 for example), if i can unlock it without problems? if is that, i have no problems unlocking the screen
now if is other thing, i didn't understand it D:
After I just got done flashing 3.0.1.0 haha, I'll give this a go.
I have one question, what is the difference between flashing rom with 2.74 version and 3.0.0? Is it possible to flash any rom on 2.74 version? Can nougat be flashed with 2.74?
Sent from my 6045I using Tapatalk
panchovix said:
do you mean, when the phone locks itself (without using it for 1 for example), if i can unlock it without problems? if is that, i have no problems unlocking the screen
now if is other thing, i didn't understand it D:
Click to expand...
Click to collapse
Yes, if you wait 1 minute, it lock by himselfe then if i want to unlock it get all crazy and i must to reboot it.
.
persona78 said:
Yes, if you wait 1 minute, it lock by himselfe then if i want to unlock it get all crazy and i must to reboot it.
.
Click to expand...
Click to collapse
No problem here, i'm using now Xperia_6045Y (from 4PDA, it is based on 6045Y stock) and tested too on LineageOS13, and no problems, are you sure it is related to TWRP?¿
Maybe something is different between 6039 and 6045 in these aspect
---------- Post added at 07:03 PM ---------- Previous post was at 07:00 PM ----------
belkoo said:
I have one question, what is the difference between flashing rom with 2.74 version and 3.0.0? Is it possible to flash any rom on 2.74 version? Can nougat be flashed with 2.74?
Sent from my 6045I using Tapatalk
Click to expand...
Click to collapse
sometimes some roms can be flashed on old TWRP versions, and i would say (i can't say this is true) N, if it is released, it will need atleast TWRP 3.0.0.0
for example in my old Moto G 4G (XT 1040), i couldn't flash AOKP 7.1.1 on TWRP 3.0.2.0, i needed to upgrade to TWRP 3.0.3.0
CAUTION TO NOT LOOSE TWRP
I read two posts that say v21, now again on V8.5, put the stock recovery back instead of twrp. This is probably a side effect of a fresh stock /system and wipe of /data.
As a preventive step, when done flashing and wiping reboot to recovery FIRST, before booting the system It will allow recovery to handle removing the recovery-from-boot.p that flashes stock recovery.
I just patched the modified V7.4.2 up to the newly released 8.3 now 8.4. 8.5, 8.7,9.0 -V9.2 Patch
New update has been made from V17 to V21 of the non prime version of R1-HD, Non prime is behind on security patch (2017-05-05)
Copied ROM from phone and made twrp install ROM from it.
* No preloader change (official updates change the preloader to block your ability to use sp flash tools for rom flashing)
* No lk.bin change __ this part is what allows you to choose boot options(boot menu when power and volume pressed together)
* No "FOTA" app Fota has now been left in to make it easier to get next update, if that ever happens.
* No opera browser
* No adds (removed in the modified 7.4.2)
* Custom boot logo (only done on v8.3, there was no interest in this so abandoned)
--Newer versions of rom left stock, Leaving mods up to user.
** while it is not necessary to do a wipe with this ROM, I still recommend it.
**Thanks:
** @vampirefo needed his patched v7.4.2 in order to apply this new 8.3 patch and again for 8.4
** @ColtonDRG OR @jasonmerc I do not remember which one made it: For the image used in the custom logo
and the modified zip is here .
Roms are rootable with SuperSU, flashed in twrp after install. Must be done in systemless mode. In order to patch system veridy in boot.img
Logo update did not work on original rom changing link to updated version
BLU rolled v8.3 back to v7.4.2 because of app compatability issues. V8.4 is there fixed release. Both 8.3 and 8.4 are modified prime roms with ads stripped
V21 is the non prime update.
Unmodified V6.1
==>NON-ROOTED-logo-not-replaced-modified-V8.3
==>Fixed Logo modified NON_ROOTED V8.3
==>>modified V8.4
==>>modified V8.5
==>>Full with Ads V8.7
==>>Full with Ads V9.0
==>>Patch For V9.2 must be flashed on top of fresh V9.0
****Run debloat ==>script to remove ads if you need/ want to, or remove from zip before flashing ****
alt. manual example: before reboot, while still in twrp. Select mount and put checkmark next to system. Then run these two commands in adb terminal
Code:
adb shell rm /system/priv-app/com.amazon.*/com.amazon.*.apk
adb shell rm /system/app/Adups*/*.apk
==>>Modified V21
** stand alone logo installs
I flashed this but I didn't get the custom boot logo.
mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
I had that happen to my second phone too.
I don't have an explanation yet.
I even made a separate update.zip , that one didn't make the logo change either. I did eventually change it with sp flash tool.
I tried with both recoveries.
and multiple /dev location formats. and for whatever reason my one phone did not accept the logo change from recovery.
And the other test phone it worked.
mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
Neither did I but it all seems to be working fine
Been using this for about a day now, likewise no custom boot logo, but that's fine. Otherwise, it's been running super well. A lot better than the previous mostly stock version did for me with the bloatware APKs removed after the install. A lot of the general idiosyncrasies of the previous version of the stock rom seem to have gone away for me. It seemed to have weird storage management issues, errors moving to SD, broken symlinks that prevent apps from moving or being reinstalled, and a lot of other little non-storage issues, but so far, none off that here.
Long story short, good work! I hope we eventually see proper 7.x roms through some of the efforts going on, but in the meanwhile, your work here has made life a little bit better on 6.
It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
**logo-update is same as composite but with alt updater-binary
**composite-logo screenshot is in op
**stock logo will return to original BLU logo
mrmazak said:
It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
Click to expand...
Click to collapse
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?
Serenitybs said:
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?
Click to expand...
Click to collapse
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
linuxsociety said:
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
Click to expand...
Click to collapse
Somebody already tried this out
linuxsociety said:
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
Click to expand...
Click to collapse
It was just wishful thinking. I have no idea how all of this is done. All I know is @mrmazak has helped me to fall in love with my phone again with this V8.3. The 7.4.2 did seem a bit buggy for my phone but this update works beautifully and I didn't even root it. If this remains true I will be happy with this phone for awhile even on 6.0
Really confused right now.
I was browsing through the settings menus. And found in the Settings-security- menu a toggle labeled "quick boot" ( not to be confused with "fastboot") . I enabled it then rebooted to see if it booted quicker. Didn't seem to make much if any difference. So I went back to turn it back off. And it wasn't there. I checked in my other phone , it wasn't there on that one either.
Did any body see this menu item, and if so where is is it?
Edit 1:
Few more power off , power on cycles to compare times. With other phone and defiantly seems to have turned on some faster boot option.
This phone goes from off to on in 5-6 seconds other phone takes about 20.
Edit 2:
OK , I panicked for a minute.
Couldn't find the setting and thought that it was another way to block sp flash tool by preventing you from ever being fully powered off.
But the setting was in accessibility not security.
Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?
detroitredwings said:
Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?
Click to expand...
Click to collapse
The mode changer app is technically a security issue. I did have that warning a few times when using mode changer app from the XDA thread of the developer, then when I used the app downloaded from f-droid it worked with systemless root and didn't give the security warning.
The app downloaded from f-droid worked for me as well, many thanks!
Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.
Letitride said:
Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.
Click to expand...
Click to collapse
I also had an app that previously work, say is not compatible now.
Maybe has to do with apps that have links to pay accounts. And that has something to do with trustzone. (Tee1 & tee2)
Those sections I left out of the update. I will add it back in and test. Update when I do. It is also possible this problem is why Blu rolled back there update.
**EDIT**
well that didn't go well at all.
I flashed the new trustzone.bin files from the official update. Now phone no longer turns on and no longer connects to flash tool
**EDIT 2**
After much persistence and many failed attempts to get phone recognized in pc again. Finnaly got to a point that phone was cycling between "preloader" driver and "usb serial device", and with careful timing was able to start sp flash tool at just right time and the flashing back to original trustzone files seems to have recovered phone.
for the record i am not sure what steps made it work. But I was shifting back and forth between leaving phone sit on charge, then on charge with rubber band wrapped around power button, then not plugged in , and not plugged in with rubber band on power button.
Okay... persistence is key in customization, i guess! I am getting somewhere here!
mrmazak said:
The first link is needed to get phone unlocked so you can install twrp.
Click to expand...
Click to collapse
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!
OldSkewler said:
Okay... persistence is key in customization, i guess! I am getting somewhere here!
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!
Click to expand...
Click to collapse
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Many ways to do that.
Easiest is to copy to phone while phone is connected to PC.
Cam also download file from internet with your phone.
Bottom line is get zip file to the phone boot to recovery and install
Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3
mrmazak said:
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Easiest is to copy to phone while phone is connected to PC.
Bottom line is get zip file to the phone boot to recovery and install
Click to expand...
Click to collapse
Right on man! I am officially running 8.3 ROM with April 5th 2017 Security Patch Level! Geez.. it was not easy but I got this working!
MrMazak, I followed all your instructions on both links, so could you tell me what exactly I have on my phone? Is it rooted? Bootloader Unlocked? The phone seems to be working fine but I don't know what level of access I have. Honestly I don't even know exactly what the differences between all these terms are.
Also, do I have or not SU? One of the steps under the .bat I believe install it. How do I access it?
Thanks again!
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
Weasel0 said:
Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3
Click to expand...
Click to collapse
My install is pretty fresh, couple of hours, but as far as I can tell all is working fine with Wifi, As a matter of fact this is a new device only connected with Wifi and no SIM Card.... internet works fine.
INTRODUCTION
We all know the famous bootloop-of-death on the Nexus 5X and there's finally something we can do about it, thanks to XCnathan32 who devised a fix that works on all security patch updates by Google. What Unblod does is quite simple. It's a tool that automates the entire process of generating a boot.img that runs on 4 of the A53 cores. It's all about just a few taps and right now supports only Windows!
PREREQUISITES
A Windows PC
A boot.imgfrom any ROM of your choice (even stock)
if ( you're unsure which ROM's on your phone ) - [Difficulty = Easy] [Recommended]
Get the stock factory image of the Android version of your choice
Extract the ZIP
Follow the instructions described above to flash the image onto your device
Move into the extracted folder and open the image-bullhead-<build_no>.zip
Copy the boot.img from within to your desired folder (e.g. Desktop)
if ( you know which ROM's on your phone ) - [Difficulty - Intermediate]
Download the boot.img of the build that corresponds to that of the ROM on your phone from here or here (for Android O)
Copy the boot.img from within to your desired folder (e.g. Desktop)
A BLOD-bricked Nexus 5X
With bootloader unlocked
In fastboot / bootloader mode
About 15 minutes
STEPS
Download the attached ZIP
Extract Unblod.zip
Launch Unblod.exe
Tap Load and browse to the location of the boot image that you'd copied sometime back in step 2-1-5 (e.g. Desktop)
[Recommended] Check the auto-flash box if you'd like to flash the modified boot.img automatically onto your phone
Connect your Nexus 5X in bootloader / fastboot mode to your PC
Tap Run and wait for the tasks to complete (i.e. till the status field says idle)
After about a minute or so your device should boot
NOTES
Wait for a while as the first boot would take quite some time on the smaller 4 cores
If you'd like to flash a recovery, a modified TWRP recovery image is required as the unmodified ones fail on 4 cores - get one from here
You'd have lost root by now so consider rooting your device again (by flashing Magisk / SuperSu)
Feel free to lock your bootloader
BUGS
None at the moment. The tool is in BETA right now though it has been tested for complete success on my Nexus 5X as you can see in the attached screenshots. Kindly let me know if there are any bugs! Also if your device is suffering from a motherboard failure or any other kind of hardware fault, Unblod ain't gonna do no magic. It does what it says and I take no ownership of your bricked device!
CREDITS
XCnathan32 - for his awesome work on inventing the 4-core fix
osm0sis - for his amazing AIK Linux Kitchen
T1mb3 - for his thread that houses all the fixed boot images and associated recoveries
DOWNLOADS
Check out the attached file. Thanks!
theGeekyLad said:
INTRODUCTION
We all know the famous bootloop-of-death on the Nexus 5X and there's finally something we can do about it, thanks to XCnathan32 who devised a fix that works on all security patch updates by Google. What Unblod does is quite simple. It's a tool that automates the entire process of generating a boot.img that runs on 4 of the A53 cores. It's all about just a few taps and right now supports only Windows!
STEPS
As simple as just extracting the attached ZIP and launching Unblod.exe! The rest just follows and requires just your presence of mind (and a bricked Nexus 5X in fastboot mode, of course). All you need to do is make sure the build of the ROM that's on your device matches that of the boot.img supplied - that's more of a precautionary step. The rest is self-explanatory! Make sure you leave your Nexus 5X in fastboot mode connected to your PC if you choose to use the auto-flash feature that's bundled in.
BUGS
None at the moment. The tool is in BETA right now though it has been tested for complete success on my Nexus 5X as you can see in the attached screenshots. Kindly let me know if there are any bugs! Also if your device is suffering from a motherboard failure or any other kind of hardware fault, Unblod ain't gonna do no magic. It does what it says and I take no ownership of your bricked device!
CREDITS
XCnathan32 - for his awesome work on inventing the 4-core fix
osm0sis - for his amazing AIK Linux Kitchen
T1mb3 - for his thread that houses all the fixed boot images and associated recoveries
DOWNLOADS
Check out the attached file. Thanks!
Click to expand...
Click to collapse
What is the use of this? cover the two cores?
Enviado desde mi Nexus 5X mediante Tapatalk
stifmaster81 said:
What is the use of this? cover the two cores?
Enviado desde mi Nexus 5X mediante Tapatalk
Click to expand...
Click to collapse
The BLOD as indicated in a popular XDA post is due to the A57 cores breaking (I guess due to thermal throttling). I also heard in a certain Reddit post that it's due to contact pins breaking underneath the A57s. So this fix just disables the A57s and the phone works fine on the A53s.
Thanks stifmaster81!
Please provide some step by step instruction,and pre-installation requirements to run this tool, thanks.
Okay, fixed the problem, great tool and it works!
5 engines detected this file
SHA-256 fe7bbba705746a11c3137dacb53627e3016ba01d0bcd61fdbbd20b3e4125a331
File name Unblod.zip
File size 5.37 MB
Last analysis 2017-12-15 02:15:02 UTC
https://www.virustotal.com/#/file/fe7bbba705746a11c3137dacb53627e3016ba01d0bcd61fdbbd20b3e4125a331/
curiousbeing said:
Please provide some step by step instruction,and pre-installation requirements to run this tool, thanks.
Okay, fixed the problem, great tool and it works!
Click to expand...
Click to collapse
Hey curiousbeing! Coming up soon. Will be posting a step by step guide.
Does the phone need to be rooted/unlocked for this tool to work and fix the bootloop?
theGeekyLad said:
Hey curiousbeing! Coming up soon. Will be posting a step by step guide.
Click to expand...
Click to collapse
I will waiting for yout step by step!
Enviado de meu Nexus 5X usando Tapatalk
AVNascimento said:
I will waiting for yout step by step!
Click to expand...
Click to collapse
Me too...
Me too...
monzer said:
Me too...
Click to expand...
Click to collapse
mireste said:
Me too...
Click to expand...
Click to collapse
AVNascimento said:
I will waiting for yout step by step!
Enviado de meu Nexus 5X usando Tapatalk
Click to expand...
Click to collapse
curiousbeing said:
Please provide some step by step instruction,and pre-installation requirements to run this tool, thanks.
Okay, fixed the problem, great tool and it works!
Click to expand...
Click to collapse
paradoxiumwind said:
Does the phone need to be rooted/unlocked for this tool to work and fix the bootloop?
Click to expand...
Click to collapse
Hey guys! I'm really sorry to leave all of you hanging without detailed instructions. I've finally updated the OP with a step-by-step guide that goes right from scratch till the end. Kindly try it out and let me know of your views!
Thanks!
theGeekyLad said:
Hey guys! I'm really sorry to leave all of you hanging without detailed instructions. I've finally updated the OP with a step-by-step guide that goes right from scratch till the end. Kindly try it out and let me know of your views!
Thanks!
Click to expand...
Click to collapse
Thanks,
soon as possible I'll try and post the result/opinion.
Ciao
can you get STEPS for vedio
monzer said:
can you get STEPS for vedio
Click to expand...
Click to collapse
Hey monzer, I can try shooting a video. Will keep you posted! Thanks!
Thanks for your
Hi
I'm stuck at fastboot.exe error
AdbWinApi.dll is missing
My Nexus 5X have this version of android: OPP6.171019.012, Nov 2017 (8.1 DP2) and yesterday I got bootloop, my warranty is gone (bough phone over 2 years ago ) and I never modified soft, no root etc.
Thanks for any help.
nvm.
I forgot to check bootloader is it unlocked and it's not.
Probably now there is nothing to fix it
I've tested, tool works but I faced wrong behaviour and don't know what was the reason - my custom ROM or some kernel error.
I use ABCrom for Nexus 5X and have to combine it with modified EX kernel since my 5X in BLOD. Goal was to use native ABCrom kernel which comes with rom.
I did wipes except data/storage, flashed ROM zip and modified ABC 4-core-boot from unblod tool. As result phone boots up successfully, but all MAC addresses are gone, attemps to switch wifi causes systemui crash so it's unusable and I did all wipes to revert back.
Maybe it works fine with stock kernel or requires some other way of integration modified custom kernel back to ROM zip, not just by flashing it over or by replacing boot.img file in ROM zip.
Interceptor1910 said:
Hi
I'm stuck at fastboot.exe error
AdbWinApi.dll is missing
My Nexus 5X have this version of android: OPP6.171019.012, Nov 2017 (8.1 DP2) and yesterday I got bootloop, my warranty is gone (bough phone over 2 years ago ) and I never modified soft, no root etc.
Thanks for any help.
nvm.
I forgot to check bootloader is it unlocked and it's not.
Probably now there is nothing to fix it
Click to expand...
Click to collapse
I'm really sorry for such a late reply which is because of not receiving any notifications! Interceptor1910, the issue is because ADB and Fastboot hasn't been configured on your system. The ZIP natively supports systems without Fastboot configured, but looks like there's a small issue. I'll update the ZIP in another 15 minutes and update the OP. Thanks for bringing the issue to light!
enqless said:
I've tested, tool works but I faced wrong behaviour and don't know what was the reason - my custom ROM or some kernel error.
I use ABCrom for Nexus 5X and have to combine it with modified EX kernel since my 5X in BLOD. Goal was to use native ABCrom kernel which comes with rom.
I did wipes except data/storage, flashed ROM zip and modified ABC 4-core-boot from unblod tool. As result phone boots up successfully, but all MAC addresses are gone, attemps to switch wifi causes systemui crash so it's unusable and I did all wipes to revert back.
Maybe it works fine with stock kernel or requires some other way of integration modified custom kernel back to ROM zip, not just by flashing it over or by replacing boot.img file in ROM zip.
Click to expand...
Click to collapse
Hey enqless, glad to know that you've used the tool. As you stated, the issue seems more of custom kernel specific. Maybe it works well with a few custom kernels (haven't tested it personally). I'll be heading back to college next week when I can test it on my buddy's Nexus 5X that's got a BLOD with the ABCrom kernel that you've mentioned and let you know of experience. Thanks enqless!
theGeekyLad said:
Hey enqless, glad to know that you've used the tool. As you stated, the issue seems more of custom kernel specific. Maybe it works well with a few custom kernels (haven't tested it personally). I'll be heading back to college next week when I can test it on my buddy's Nexus 5X that's got a BLOD with the ABCrom kernel that you've mentioned and let you know of experience. Thanks enqless!
Click to expand...
Click to collapse
That's ok) Thanks for your work, first of all, for maintaining all us to stay alive. Otherwise, our 5X would be laid on shelf as brick long time ago.
With unblod tool we can definitely prepare 4-core stock kernels by ourselves, Just to go ahead with further firmware updates as our device is still supported, without waiting and exploring forums until somebody posts modified kernel.
Disclaimer
**** All flashing is done at your own risk! ****
**** While this recovery should not break your device, don't come back here blaming anyone if it does! ****
This is a TWRP 3.2.3 build based on Android 7.1.2 source kernel for the Galaxy Tab Active 2 (codename: gtactive2lte) - Exynos. The "tar" file should be installed using Odin (tested on Odin 3.12.3).
Special Notes:
1. DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options, if its not there, you may have to wait for a few days to access that option, some users claim that its within 10 days before this option appears).
2. KNOX will be tripped once you flashed custom binaries to your phone.
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
4. It is HIGHLY UNRECOMMENDED to purchase any access to any kind of private forums, ROMs or Kernels.(DO NOT GET FOOLED.)
Installation process:
1. Flash Stock ROM.
2. Flash recovery using Odin (AP = recovery.tar).
3. Load recovery immediately after flashing.
4. Format data (Will erase /data partition).
5. Reboot to recovery.
6. ADB push SuperSU to internal storage / insert SD-Card with SuperSU.zip.
7. Flash SuperSU using TWRP install option.
8. Reboot to system (May bootloop several times. Wait untill system loads).
Bugs:
1. ADB sometimes doesn't work in MTP mode. Need to manually change to PTP in order to get adb usage.
2. Bad label in ADB shell + bad characters appearing while writing through AD. Works well out of recovery and on recovery's terminal.
Sources:
Device tree - Device tree
Kernel - Kernel
TWRP sources - platform_manifest_twrp_omni
SuperSU - SuperSU-2.82-SR5
Recovery download:
Recovery
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 08/19/2018 (DD/MM/YYYY)
Contributors:
Many thanks to TWRP's developers for the support on building this recovery.
Special thanks to CaptainThrowback, Bigbiff and Dees_Troy on TWRP-freenode and Ashyx on xda-developers.
Please post any bugs you encounter. I will try to fix any issues that come up.
Thanks for the work and sharing. I'm excited to try. Having root would be great, but I'd also like to be able to make voice calls ( using bluetooth as the built-in speaker & microphone aren't adequate ). Do you think this is possible. What changes, if any, are required to have work with T397 Tab Active 2 ( US variant ) ? I'm sure that it's mobile frequencies are different than what the euro-spec'd T395, but otherwise I think identical.
Slomo
slomo2 said:
Thanks for the work and sharing. I'm excited to try. Having root would be great, but I'd also like to be able to make voice calls ( using bluetooth as the built-in speaker & microphone aren't adequate ). Do you think this is possible. What changes, if any, are required to have work with T397 Tab Active 2 ( US variant ) ? I'm sure that it's mobile frequencies are different than what the euro-spec'd T395, but otherwise I think identical.
Slomo
Click to expand...
Click to collapse
Well, Samsung has a nice repo of their source kernels for every phone Samsung sources
I guess we just have to validate some data taken from boot.img from the stock rom and then build the same with the appropriate source kernel.
Shedaim said:
Well, Samsung has a nice repo of their source kernels for every phone Samsung sources
I guess we just have to validate some data taken from boot.img from the stock rom and then build the same with the appropriate source kernel.
Click to expand...
Click to collapse
Had no idea the source was available for these devices, thanks for sharing. T397 source is in the repository. Let me know if there is something that I can do to assist. I've not compiled these sources although I've compiled other things. Possible to use this tablet as a phone with this ROM as stock T397 ( even after installing several different dialers does not dial ) ?
slomo2 said:
Had no idea the source was available for these devices, thanks for sharing. T397 source is in the repository. Let me know if there is something that I can do to assist. I've not compiled these sources although I've compiled other things. Possible to use this tablet as a phone with this ROM as stock T397 ( even after installing several different dialers does not dial ) ?
Click to expand...
Click to collapse
I can't check the dialer thing, as I don't even have cellular network on my Tablet.
I'll try to build the recovery for the T397 later today, but you will have to check it I guess, as I have no access to that one.
Shedaim said:
I can't check the dialer thing, as I don't even have cellular network on my Tablet.
I'll try to build the recovery for the T397 later today, but you will have to check it I guess, as I have no access to that one.
Click to expand...
Click to collapse
This will be great, let me know if I can help, perhaps document.
slomo2 said:
This will be great, let me know if I can help, perhaps document.
Click to expand...
Click to collapse
Ok, so this is a first try, so I believe it's not going to work, but who knows? we may get lucky.
Recovery for SM-T397 - Android 7.1.2
If it doesn't get installed or leads to a bootloop, I'm gonna need you to pull the boot.img from your device, or send me a link of the stock ROM if it's available.
Please follow the intsallation process described on the README file on the github repository
Shedaim said:
Ok, so this is a first try, so I believe it's not going to work, but who knows? we may get lucky.
Recovery for SM-T397 - Android 7.1.2
If it doesn't get installed or leads to a bootloop, I'm gonna need you to pull the boot.img from your device, or send me a link of the stock ROM if it's available.
Please follow the intsallation process described on the README file on the github repository
Click to expand...
Click to collapse
Thank you! Successfully installed. I found this video helpful for this generation of Samsung device and learning how to navigate recovery and download modes. I disabled auto-reboot in ODIN per your instructions, but it wasn't clear to me how to power-off after download so as to be able to go into recovery without booting so after adequate time I just pulled the battery. I'll spend the evening playing with things and report back, but so far everything seems to be working
---------- Post added at 11:27 PM ---------- Previous post was at 11:15 PM ----------
slomo2 said:
Thank you! Successfully installed. I found this video helpful for this generation of Samsung device and learning how to navigate recovery and download modes. I disabled auto-reboot in ODIN per your instructions, but it wasn't clear to me how to power-off after download so as to be able to go into recovery without booting so after adequate time I just pulled the battery. I'll spend the evening playing with things and report back, but so far everything seems to be working
Click to expand...
Click to collapse
One thing I notice, 7.1.1 is what was/is installed on my tablet now. Not sure what version of Android available on Samsung Opensource or how to check it, but I suspect it is the same since nothing has been pushed OTA.
7.1.1 is what The T397U should have already been on before you started. Mine is and I have not installed this recovery as of yet. Just wanted to let you know it's where it should be.
slomo2 said:
Thank you! Successfully installed. I found this video helpful for this generation of Samsung device and learning how to navigate recovery and download modes. I disabled auto-reboot in ODIN per your instructions, but it wasn't clear to me how to power-off after download so as to be able to go into recovery without booting so after adequate time I just pulled the battery. I'll spend the evening playing with things and report back, but so far everything seems to be working
---------- Post added at 11:27 PM ---------- Previous post was at 11:15 PM ----------
One thing I notice, 7.1.1 is what was/is installed on my tablet now. Not sure what version of Android available on Samsung Opensource or how to check it, but I suspect it is the same since nothing has been pushed OTA.
Click to expand...
Click to collapse
Awesome. I really had my doubts being it the first build and all. I guess, there aren't really any major differences.
If it's possible, can you go through the TWRP checklist here
Some of the tests aren't really necessary, but it's a good checklist to go by anyway.
That way, I can officially add it to the OP.
Shedaim said:
Awesome. I really had my doubts being it the first build and all. I guess, there aren't really any major differences.
If it's possible, can you go through the TWRP checklist here
Some of the tests aren't really necessary, but it's a good checklist to go by anyway.
That way, I can officially add it to the OP.
Click to expand...
Click to collapse
Sorry for delay. I've done the following tests all with the expected results. The only thing I noticed compared to previous installations of TWRP that I've performed ( some years ago ) is that the load time of recovery seems long at 1:15. Also a message about "RECOVERY NOT SEANDROID ENFORCING" which I suspect is normal. Tablet has been working without incident. Thanks again.
Blocking checks
- Correct screen/recovery size
- Working Touch, screen
- Backup to internal/microSD
- Restore from internal/microSD
- reboot to system
-ADB ( yes, if this means being able to access from ADB while in recovery )
Medium checks
- Screen goes off (and on )
- F2FS/EXT4 Support, exFAT/NTFS where supported
- all important partitions listed in mount/backup lists
===> define important ? - depends on the device, i guess
= Assume we can still boot a recovery (aboot/lk is still there for fastboot), can restore everything left ?
- backup/restore to/from external (USB-OTG) storage
- Correct date
Minor checks
- MTP export
- reboot to bootloader
- reboot to recovery
- poweroff
- battery level
- USB mass storage export
- set brightness
- vibrate
Security Policy Updates should not be applied to this system ?
Since this is stock Samsung OS that is rooted I'm guessing this system is still SELinux "enforcing" so does this mean that I can/should say yes to Security Enhancements automatic updates from Samsung ? Any explanation or link on this matter appreciated.
Hey @Shedaim, thanks a lot for this recovery, would it be possible to release an update for oreo?
maddada said:
Hey @Shedaim, thanks a lot for this recovery, would it be possible to release an update for oreo?
Click to expand...
Click to collapse
Hey, sorry for the very late answer.
I'm currently not working on Android and I've never tried on OREO, so my politically correct answer would be: "Right now there is no plan to work the same magic on OREO, but whoever wants, can try to use the device tree I created with a new official OREO kernel (didn't know they have one already)".
Anyway, keep checking the forum from time to time, I may have found the time to work on it
Links to the device tree and other tools used are in the main page of this thread.
Thank you,
Shedaim
I Pay 100$ for making my Galaxy Tab Active 2 booting when its charging
Hey guys,
i hope somebody can help me.
Im trying since 2 Weeks to make my Galaxy Tab Active 2 booting when its charging.
I try all the ways i found (fastboot, LPM change and Autoboot App) and nothing was successful.
So i hope to find with this way somebody who would help me to get the feature.
I need it because i installed the Active 2 on my Harley Davidson as my navigation.
And the problem is that i make a Novalauncher thats looking like the original Harley Davidson one and starts without a code.
So when i put the Tablet in the Mask i dont get a method to press to power button and when i make a method (hole trough the mask or something) then everybody can start up my tablet and use it.
So if somebody can help me with that i will pay them 100$ for helping!
you can contact me at [email protected].
thanks alot
Excuse me for a moment, but i have a Galaxy Tab Active 2 WIFI (sm-t390) and im looking for a custom recovery for it. All i can find for this model is the SM-T395 variant of TWRP,root, etc. Absolutelly nothing for the SM-T390? Does any one have any ideas???? Thank you in advance either way.
sCOTTN916 said:
Excuse me for a moment, but i have a Galaxy Tab Active 2 WIFI (sm-t390) and im looking for a custom recovery for it. All i can find for this model is the SM-T395 variant of TWRP,root, etc. Absolutelly nothing for the SM-T390? Does any one have any ideas???? Thank you in advance either way.
Click to expand...
Click to collapse
I used the methods and recovery here for my tablet which is a T397U...works flawlessly. The same should work for the wifi T390 you have aswell.
Flash process
I am new to the rooting process. This will be my first time. What is the actual flash process? How do I flash the rom on my tablet?
All the links are dead can anyone please post this recovery
i can Flash this twrp-3.2.3-0-gtactive2lte-7.1.2.tar, Odin says pass, but there is no TWRP. it boots into System. when i stop and boot to recovery, there is stll custom recovery from T395XXU5CSH2.
Any hints?