Disclaimer:
Code:
/*
*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about the tools/files!
* YOU are choosing to make these modifications, and if you point the
* finger at me for messing up your device, I will laugh at you.
*
*/
You NEED a MicroSD, and it WILL be formatted during this process.
THIS WILL NOT WORK ON GALAXY S3/GALAXY S4/GALAXY S6|e/Galaxy S7|e. It will NOT work on AT&T.
We can't help you root or teach you how to use ADB. It's important you have the ability to do these things or research them a bit before blindly using this.
Click to expand...
Click to collapse
This is a summarized guide with the required files to upgrade and unlock the new bootlloader required for Android 6.0.1 Marshmallow (N910VVRU2CPD1) on Verizon Samsung Galaxy Note 4 (SM-N910V). Extended details about each step (e.g., rooting) can be found in the General Section of this forum.
If you're already on unlocked Android 6.0.1 Marshmallow bootloader, you can extract and flash the DevEd partial firmware via Odin to upgrade:
N910VVRU2CQL1_PartialFirmware_DevEd.tar.md5.7z
This will upgrade the base firmware (NON-HLOS, modem, rpm, sbl1, sdi, and tz) to N910VVRU2CQL1.
Click to expand...
Click to collapse
Requirements:
Verizon Samung Galaxy Note 4 (SM-N910V)
All files in the Download Section
Odin installed on Windows
ADB installed on Windows, Mac, or Linux
Click to expand...
Click to collapse
Notes:
If you own a Developer Edition, you can still use this method unless you want to keep your original CID and signature. If so, make backup of your aboot and CID! You may contact @ryanbg to create a special unlock binary for your own device.
Everyone should unlock his bootloader on Lollipop to save extra steps and prevent complications. The official thread (or any guides based on it) will change your device CID to 150100523231384d4100657e54fc1200 which will match and allow for direct unlocking of the Marshmallow bootloader. Otherwise, the unlock binary will change your decvice CID and reboot, which may end up with a bootloop that requires extra step(s) to fix.
It's recommended to wipe data (factory reset) in stock recovery after Odin flash of full firmware.
Make appropriate backups of everything before trying this.
Click to expand...
Click to collapse
Instructions:
Unlock your Lollipop bootloader to match CID (start here)
You can ignore this step if you did it already. If not and for Developer Edition owners, I'd recommend to flash N910VVRU2BPA1 Full Firmware via Odin before unlocking.
Boot into Download Mode
Extract and flash N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5 via Odin
This will make you on Lollipop with Marshmallow bootchain/firmware/modem, which is rootable.
Root your device (Check General Section for detailed instructions)
Note that WiFi will not work due to the updated bootloader, but you can use Mobile data if needed for rooting.
Unlock the bootloader using the same method:
Code:
[email protected]:/ # cd /data/local/tmp/
[email protected]:/ # chmod 777 samsung_unlock_n4-fix <
[email protected]:/ # ./samsung_unlock_n4-fix
============================== samdunk unlock 0.0.1 ==============================
NOTE 3 BETA UNLOCK!!!!!!!!!!!!!
this application comes with NO WARRANTY (express or implied)
this binary may not be rehosted, repackaged, one-clicked, etc.
there is no support provided for this application
this application has been tested on the Verizon Galaxy S5 only
it may work on the AT&T Galaxy S5, and possibly other similar Galaxy devices
there are no compatibility checks, do your research first
if run on an incompatible phone, it will likely permanently ruin the device
we STRONGLY advise against running any binary not obtained from the official source
official source is available at http://github.com/beaups/SamsungCID
SD card is required, all data on the SD card will be destroyed
changing to this developer CID may have other implications
the psn derived from the CID may be used for critical services
changing this psn may cause unexpected behavior or loss of services
continue at your own risk, you've been warned
aboot dev signature research credit to ryanbg
http://forum.xda-developers.com/member.php?u=766721
eMMC vulnerability, exploit, and the code you are running by beaups (sean beaupre)
http://forum.xda-developers.com/member.php?u=711482
Do you understand the implications of these warnings?
(Yes/No)
[+] CID at boot time is/was: 150100523231384d4100657e54fc1200
[+] dev CID matching, proceding to unlock
[+] backing up loaders, this will take a few minutes
[+] loaders successfully backed up
[+] success! powering off device, hopefully its not bricked!
Boot into Download Mode
Extract and flash twrp-3.0.2-0-trltevzw.tar.md5 via Odin
Boot into TWRP recovery
Flash MM Safe Upgrade, JasmineROM, or any MM TW (or MM+ AOSP-based) ROM
Extract and flash N910VVRU2CQL1_PartialFirmware_DevEd.tar.md5.7z via Odin
This will upgrade the base firmware (NON-HLOS, modem, rpm, sbl1, sdi, and tz) to N910VVRU2CQL1.
Reboot to system
ENJOY!
Click to expand...
Click to collapse
.
XDA:DevDB Information
Bootloaader Unlock, Tool/Utility for the Verizon Samsung Galaxy Note 4
Contributors
hsbadr, ryanbg, beaups
Source Code: https://github.com/beaups/SamsungCID
Version Information
Status: Stable
Created 2016-06-14
Last Updated 2018-01-21
Reserved
Reserved
Thank you Hsbadr.
Sent from my SM-N910V using Tapatalk
@hsbadr @ryanbg @beaups thanks for all the hard work in unlocking new bootloader
Can we run this already?
Edit: Doesn't seem like all the files are available yet.
Sent from my Unlocked/Rooted SM-N910V using XDA-Developers mobile app
Where does one find the N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5 file?
Bicknasty said:
Where does one find the N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5 file?
Click to expand...
Click to collapse
Looks like its still in testing. I dont see the file either.
tolymatev said:
Looks like its still in testing. I dont see the file yet either.
Click to expand...
Click to collapse
blah, that's what I get for resetting before downloading the necessary files
Extra Virgin said:
thanks for all the hard work in unlocking new bootloader
Click to expand...
Click to collapse
You're welcome.
tolymatev said:
Can we run this already?
Click to expand...
Click to collapse
Sure. Why is it posted then?!
Bicknasty said:
Where does one find the N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5 file?
Click to expand...
Click to collapse
tolymatev said:
Looks like its still in testing. I dont see the file either.
Click to expand...
Click to collapse
Bicknasty said:
blah, that's what I get for resetting before downloading the necessary files
Click to expand...
Click to collapse
Click to expand...
Click to collapse
No, it's already tested a few days ago. I just recreated the tar to include MM modem and NON-HLOS so that you don't have to flash extra tars. I'll upload it very soon, but in the meanwhile, you can familiarize yourself with the process and do any preliminary steps (backups, LP unlock, ... etc)
Thank you @hsbadr ....I.m glad your here with us
If I took the OTA, would I have to rollback to 5.1.1 and do this?
datstudandre said:
If I took the OTA, would I have to rollback to 5.1.1 and do this?
Click to expand...
Click to collapse
Yes, unless another method exists.
hsbadr said:
You're welcome.
Sure. Why is it posted then?!
No, it's already tested a few days ago. I just recreated the tar to include MM modem and NON-HLOS so that you don't have to flash extra tars. I'll upload it very soon, but in the meanwhile, you can familiarize yourself with the process and do any preliminary steps (backups, LP unlock, ... etc)
Click to expand...
Click to collapse
You are the greatest man, thanks!
For anybody who looked before but didn't notice, the missing firmware file has been uploaded and linked in the OP
I'm a little confused where does adb come into play at when do we flash the note 4 fix sorry the instructions seem a little vague....sorry....
ct_tec313 said:
I'm a little confused where does adb come into play at when do we flash the note 4 fix sorry the instructions seem a little vague....sorry....
Click to expand...
Click to collapse
If it's like the original root process you have to push a file via ADB.
ct_tec313 said:
I'm a little confused where does adb come into play at when do we flash the note 4 fix sorry the instructions seem a little vague....sorry....
Click to expand...
Click to collapse
Follow the link in the 1st step! It's probably b/c you own a developer edition and never tried to unlock/upgrade the bootloader before. Simply, you need ADB to push the unlock binary to /data/local/tmp and execute it after rooting. Theoretically, this can be done in Terminal Emulator on device, but we prefer to use ADB since users should increase their knowledge before trying something dangerous like this one.
Thank you I do own a developer edition...lol I know how to use adb I'm just a little rusty
..
Sent from my SM-N910V using Tapatalk
hsbadr said:
Disclaimer:
Code:
/*
*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
You NEED a MicroSD, and it WILL be formatted during this process.
This is a summarized guide with the required files to upgrade and unlock the new bootlloader required for Android 6.0.1 Marshmallow (N910VVRU2CPD1) on Verizon Samsung Galaxy Note 4 (SM-N910V). Extended details about each step (e.g., rooting) can be found in the General Section of this forum.
Requirements:
Notes:
Instructions:
.
XDA:DevDB Information
Bootloaader Unlock, Tool/Utility for the Verizon Samsung Galaxy Note 4
Contributors
hsbadr, ryanbg, beaups
Source Code: https://github.com/beaups/SamsungCID
Version Information
Status: Beta
Created 2016-06-14
Last Updated 2016-06-13
Click to expand...
Click to collapse
Is there anyway us Verizon Edge guys can get our unlock binary updated for MM? :fingers-crossed:
Related
[IMG]4.4.4 & 5.0 Pure Edition Мodified stock recovery.img - no signature ckeck
Code:
#include <std_disclaimer.h>
/*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Here are modified stock recovery images from XT1095 Pure Edition build KXE21.187-42 (Android 4.4.4), build LXE22.39.6 (Android 5.0, system version 22.11.6) and build LXE22.46-11 (Android 5.0, system version 22.21.11).
Stock recovery was patched to disable signature check of any update.zip during installation. No other modifications were made.
It may be useful to install modified OTA update which can not be installed using custom recovery.
To use these images your Moto X's bootloader have to be UNLOCKED.
How to use.
I would not recommend to flash it. Please use the following command instead:
Code:
fastboot boot stock_recovery_PATCHED.img
Attached files:
stock_recovery_PATCHED.zip - for Android 4.4.4
22.11.6_stock_recovery_PATCHED.rar - for Android 5.0, system version 22.11.6
Recovery-5-0_LXE22.46-11.zip - for Android 5.0, system version 22.21.11
Thank you for this work.... Does it allow to install (flashable zips) other than OTA's?
theone_s_me said:
Does it allow to install (flashable zips) other than OTA's?
Click to expand...
Click to collapse
Yes. In fact it is the stock recovery, but it does not check signature for flashable zips during installation.
Awesome... Its really helpful... One thing u mentioned is not recommending to flash it, any reason behind that?
theone_s_me said:
One thing u mentioned is not recommending to flash it, any reason behind that?
Click to expand...
Click to collapse
Nothing special - just to be on safe side. You can flash it. However if you have OTA installed, it will be overwritten with fully stock recovery after phone's reboot.
I know this is stupid but you should mention, before someone asks or tries it, that you have to be unlocked to use it. I know... Believe me, I know. But trust me, it's worth mentioning. Nice job on this. Very sweet concept.
Sent from my SM-P600 using Tapatalk
SmuriHL, thank you for the advise - OP updated.
Al936 said:
SmuriHL, thank you for the advise - OP updated.
Click to expand...
Click to collapse
@Al936 does this involve a lot of development?
I would like to do something similar for my Moto maxx (XT1225) so I can flash supersu
are there any guides or somewhere I can start?
Al936 said:
Code:
#include <std_disclaimer.h>
/*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Here are modified stock recovery images from XT1095 Pure Edition build KXE21.187-42 (Android 4.4.4) and build LXE22.39.6 (Android 5.0, system version 22.11.6).
Stock recovery was patched to disable signature check of any update.zip during installation. No other modifications were made.
It may be useful to install modified OTA update which can not be installed using custom recovery.
To use these images your Moto X's bootloader have to be UNLOCKED.
How to use.
I would not recommend to flash it. Please use the following command instead:
Code:
fastboot boot stock_recovery_PATCHED.img
Attached files:
stock_recovery_PATCHED.zip - for Android 4.4.4
22.11.6_stock_recovery_PATCHED.rar - for Android 5.0, system version 22.11.6
Click to expand...
Click to collapse
will this be updated to work with system version 22.21.11
Can I flash this recovery on XT1097?? Work to flash SuperSU.zip on my device without lost OTA updates?
hdtechk said:
will this be updated to work with system version 22.21.11
Click to expand...
Click to collapse
Yes - OP updated
Please forgive the noob question but could I use this to install the new 5.1 ota even though I modified my /system by deleting some system apps? I know the unmodified stock recovery won't flash it for this reason. Thanks!
This also does not install the ota because your /system is modified.
BOOTSTACK (KK and L) for L90
Supported variants: D400hn, D405, D405n, D410, D410hn, D415
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What is BOOTSTACK ?
Bootstack is a bunch of files placed deep inside your phone. They are responsible for turning your phone ON and OFF, they are providing download mode which allows you to flash official KitKat and Lollipop .kdz files. Bootstack is ensuring SIM support so you could make calls, send texts and access mobile internet. Those files also allows you to fix your bricked phone after flashing bad ROM. Bootstack is basically making you phone work. If those files get corrupted you may have to send your phone to repair.
YOU SHOULD NOT MESS AROUND WITH DOES FILES !!!
Bootstacks available in download section are meant for advanced users who know what they are doing.
Which BOOTSTACK do I need ?
Usually you do NOT need and should NOT touch those files.
They are being updated when you flash .kdz file.
When you're updating your L90 to Lollipop using .kdz you are also updating bootstack to a newer version. After that update you can only use stock LG Lollipop. So if you want to go back to stock KitKat or install any customROM you have to downgrade your bootstack.
You can do this in two ways:
1. Use .kdz file with KitKat in LG Mobile Support Tool. After that update you may lose all your data, your bootloader will be locked (does not apply to D415), your recovery will be restored to original and you will lose ROOT privileges. Your entire phone will be restored to factory state. (Safer and recommended for inexperience users)
2. Use bootstack zips provided here. After flashing one of the zip available below you will downgrade or upgrade your bootstack (depending on which zip will you use). You will get unlocked bootloader and your recovery will change to TWRP. ROOT privileges will NOT be affected.
If you decide to use second option check out this description:
- If you want to use official LG stock Lollipop choose Lollipop zip
- If you want to use official LG stock KitKat or customROM choose KitKat zip.
I still don't understand what is BOOTSTACK for
If you updated your stock software from KitKat to Lollipop using .kdz file (or official OTA) you also (unwillingly) updated your BOOTSTACK to Lollipop version which is good. It's how it supposed to be. But if you decide to restore your KitKat backup from recovery or install customROM while being on stock Lollipop you will NOT be able to make calls, send texts or access mobile internet. To have SIM support you need KitKat BOOTSTACK and you can find it in this thread. Read again "Which BOOTSTACK do I need ?" to make sure you know what you are doing. If you have never updated your phone to official stock Lollipop from LG you don't need to change anything.
If you still have questions about BOOTSTACK ask them in Q&A section here:
http://forum.xda-developers.com/lg-l90/help/qa-bootstack-kk-l-l90-t3118867
You will need ROOT, unlocked bootloader and custom recovery (TWRP recommended) to flash this.
If you decide to use my bootstacks, please let me know if it worked correctly for you (please include variant number and name of zip you used) !!!
Download:
If you want to use official LG stock Lollipop choose Lollipop zip
If you want to use official LG stock KitKat or customROM choose KitKat zip.
Click to expand...
Click to collapse
It's STRONGLY advised to less advanced users to read sections: "What is BOOTSTACK ?" and "Which BOOTSTACK do I need ?" before doing anything.
They should also choose ONLY files labeled as STABLE. They are confirmed as working properly for most of the people.
You should NOT forget that even stable files can work incorrectly for some users.
Click to expand...
Click to collapse
D400hn (Single SIM, equipped with NFC)
Disclaimer:
Information and files published here may be incorrect. Using files provided in this thread may lead to complete, irreversible device damage. STABLE status is ONLY a suggestion NOT a fact. Every file available here, even files marked as STABLE might be faulty and may cause serious damage to software and/or hardware. I'm not responsible for bricked devices.
YOU ARE USING THOSE FILES AT YOUR OWN RISK !
Click to expand...
Click to collapse
KitKat: Faulty zip. If you already downloaded the file, please delete it !
Version: 1.0
Status: untested, use at your own risk !]
Lollipop: Not available.
D405 (Single SIM, no NFC)
Disclaimer:
Information and files published here may be incorrect. Using files provided in this thread may lead to complete, irreversible device damage. STABLE status is ONLY a suggestion NOT a fact. Every file available here, even files marked as STABLE might be faulty and may cause serious damage to software and/or hardware. I'm not responsible for bricked devices.
YOU ARE USING THOSE FILES AT YOUR OWN RISK !
Click to expand...
Click to collapse
KitKat: https://www.androidfilehost.com/?fid=24052804347759481
Version: 1.0
Status: STABLE. Confirmed as working by user: H84
Lollipop: https://www.androidfilehost.com/?fid=24052804347759482
Version: 2.0
Status: STABLE. Confirmed as working by user: H84
D405n (Single SIM, equipped with NFC)
Disclaimer:
Information and files published here may be incorrect. Using files provided in this thread may lead to complete, irreversible device damage. STABLE status is ONLY a suggestion NOT a fact. Every file available here, even files marked as STABLE might be faulty and may cause serious damage to software and/or hardware. I'm not responsible for bricked devices.
YOU ARE USING THOSE FILES AT YOUR OWN RISK !
Click to expand...
Click to collapse
KitKat: https://www.androidfilehost.com/?fid=24052804347759483
Version: 1.4
Status: STABLE. Confirmed as working by users: Xemidra, grey heron, velosa.
Lollipop: https://www.androidfilehost.com/?fid=24052804347759484
Version: 2.4
Status: STABLE. Confirmed as working by users: Xemidra, grey heron.
Lollipop: https://www.androidfilehost.com/?fid=24052804347772737
Version: 2.5
Status: untested, use at your own risk !
D410 (Dual SIM, no NFC)
Disclaimer:
Disclaimer:
Information and files published here may be incorrect. Using files provided in this thread may lead to complete, irreversible device damage. STABLE status is ONLY a suggestion NOT a fact. Every file available here, even files marked as STABLE might be faulty and may cause serious damage to software and/or hardware. I'm not responsible for bricked devices.
YOU ARE USING THOSE FILES AT YOUR OWN RISK !
Click to expand...
Click to collapse
KitKat: https://www.androidfilehost.com/?fid=24052804347759487
Version: 1.3
Status: STABLE. Confirmed as working by user: 4peace1
Lollipop: https://www.androidfilehost.com/?fid=24052804347759485
Version: 2.4
Status: STABLE. Confirmed as working by user: 4peace1
Lollipop: https://www.androidfilehost.com/?fid=24052804347759486
Version: 2.5
Status: STABLE. Confirmed as working by user: 4peace1
D410hn (Dual SIM, equipped with NFC)
Disclaimer:
Information and files published here may be incorrect. Using files provided in this thread may lead to complete, irreversible device damage. STABLE status is ONLY a suggestion NOT a fact. Every file available here, even files marked as STABLE might be faulty and may cause serious damage to software and/or hardware. I'm not responsible for bricked devices.
YOU ARE USING THOSE FILES AT YOUR OWN RISK !
Click to expand...
Click to collapse
KitKat: https://www.androidfilehost.com/?fid=24052804347798525
Version: 1.0
Status: STABLE. Confirmed as working by user: F. Gacrux
Note: This bootstack was created by user F. Gacrux. Unlocked bootloader included. TWRP is NOT present in this zip. Please make sure you have installed the latest version of TWRP.
Lollipop: https://www.androidfilehost.com/?fid=24052804347798524
Version: 1.0
Status: STABLE. Confirmed as working by user: F. Gacrux
Note: This bootstack was created by user F. Gacrux. Unlocked bootloader included. TWRP is NOT present in this zip. Please make sure you have installed the latest version of TWRP.
D415 (Single SIM, no NFC, US-only )
Disclaimer:
Information and files published here may be incorrect. Using files provided in this thread may lead to complete, irreversible device damage. STABLE status is ONLY a suggestion NOT a fact. Every file available here, even files marked as STABLE might be faulty and may cause serious damage to software and/or hardware. I'm not responsible for bricked devices.
YOU ARE USING THOSE FILES AT YOUR OWN RISK !
Click to expand...
Click to collapse
KitKat: https://www.androidfilehost.com/?fid=24052804347761027
Version: 1.1
Status: untested, use at your own risk !
KitKat: https://www.androidfilehost.com/?fid=24052804347759490
Version: 1.2
Status: untested, use at your own risk !
Lollipop: https://www.androidfilehost.com/?fid=24052804347759489
Version: 2.3
Status: STABLE. Confirmed as working by user: jran0880
Installation instructions:
0. Make sure you have ROOT privileges, unlocked bootloader and custom recovery (TWRP recommended) installed on your device.
1. Download correct zip and place it on you SDcard.
2. Go to you custom recovery, chose INSTALL and select zip file with the bootstack
3. Confirm your choice and wait. That's it !
If the installation fail do NOT leave recovery. Connect your charger, write in this thread and wait for help.
Information about content:
- Both KitKat and Lollipop versions
- Unlocked bootloader and TWRP 2.8.5.0 included
Status:
Partly tested*
Using files provided in this thread may lead to complete, irreversible device damage. I'm not responsible for bricked devices. You are using this files at your own risk.
* - STABLE status is given after confirmation that everything is OK from users who used the ZIP files on their variants of L90. I do NOT test those files. Be aware that in some cases some ZIPs may be marked as STABLE by mistake so even STABLE ZIPs may be faulty. USE AT YOUR OWN RISK !
Credicts / Thanks:
LG - for releasing .kdz files
shoxxy - for TWRP for L90
Зевс - for unlocked bootloaders
ITS NOT ALLOWED TO MIRROR MY FILES , IF YOU WANT TO SHARE , ASK ME , AND ONLY LINK TO THIS ORIGINAL THREAD !!!
---------------------------------------------------------------------------------------------------------------------------
If you like what I'm doing. Please use Thanks! button below.
Finally, I was waiting for this thread. Can I ask you if V20A bootstack for D405n is good in V20B?
SlimShady's said:
Finally, I was waiting for this thread. Can I ask you if V20A bootstack for D405n is good in V20B?
Click to expand...
Click to collapse
It should.
There is no information about changes between 20A and 20B and even if they are, they are probably regarding system partition. The only bootstack that I used was slightly modified D405n for KitKat.
Hi
What it is? I'm a noob so that's why I'm asking. Am I need it for something, or what?
freeman94 said:
Hi
What it is? I'm a noob so that's why I'm asking. Am I need it for something, or what?
Click to expand...
Click to collapse
You are not the first person who ask about this so I included an information in first post.
Flashed BOOTSTACK_v1.2_D415-20B w/TWRP. Flash was said to be successful. Reboot system and black screen. Seems to be stuck in download mode. Cannot get back into recovery, or boot into system
bobl61 said:
Flashed BOOTSTACK_v1.2_D415-20B w/TWRP. Flash was said to be successful. Reboot system and black screen. Seems to be stuck in download mode. Cannot get back into recovery, or boot into system
Click to expand...
Click to collapse
What ROM were you on when you flashed the bootstack?
Sent from my LG-D415 using XDA Free mobile app
Hi
It should be NO Bootstack from KK needed. :
1.Flash Lollipop from KDZ
2.Root the Device
3.Unlock Bootloader using this from my Thread ( Thx @Зевс)
4.Flash my TWRP or any recovery you want, via an app like: rashr, or flashify or .......
Thats it
The Bootstack thing is only needed on devices with locked Bootloader... but i bricked my G-Pad v400 (msm8226) many many times , when i try that out :silly: so the unlocked Bootloader (if its available) is the best way for me :good:
Best Regards
bobl61 said:
Flashed BOOTSTACK_v1.2_D415-20B w/TWRP. Flash was said to be successful. Reboot system and black screen. Seems to be stuck in download mode. Cannot get back into recovery, or boot into system
Click to expand...
Click to collapse
Before messing around I suggest you to flash kdz. Also, maybe in OP there should be a disclaimer regarding this shouldn't be used when nothing is wrong about your device ATM.
bobl61 said:
Flashed BOOTSTACK_v1.2_D415-20B w/TWRP. Flash was said to be successful. Reboot system and black screen. Seems to be stuck in download mode. Cannot get back into recovery, or boot into system
Click to expand...
Click to collapse
Thats what i am talking about. if you could not go into Recovery or Download Mode you are bricked at QHSUSB Mode 9006 or 9008.
This Bootstack Thing should only be used if you defintly know what you do, also make sure you could unbrick your device
What about bootstack C KitKat for D-415 ZNF..... Don't see it listed for people who need it
@Xemidra
I used the version kk on my d405n and everything ok.as soon as I can I will test the LP version
velosa said:
@xemidra
i used the version kk on my d405n and everything ok.as soon as i can i will test the lp version
Click to expand...
Click to collapse
you dont need the bootstack !!!
shoxxy said:
you dont need the bootstack !!!
Click to expand...
Click to collapse
thanks for the advice but I know.only use to test.
shoxxy said:
Hi
It should be NO Bootstack from KK needed. :
1.Flash Lollipop from KDZ
2.Root the Device
3.Unlock Bootloader using this from my Thread ( Thx @Зевс)
4.Flash my TWRP or any recovery you want, via an app like: rashr, or flashify or .......
Thats it
The Bootstack thing is only needed on devices with locked Bootloader...
Click to expand...
Click to collapse
Bootstack are needed when you want to flash custom ROMs and your phone is upgraded to official lollipop.
Installing ROMs that way (without using kk bootstack or flashing back kk via kdz) ends with unknown baseband, no network signal.
Are you suggesting that people can use custom ROMs directly from lollipop stock?
judas1977 said:
Bootstack are needed when you want to flash custom ROMs and your phone is upgraded to official lollipop.
Installing ROMs that way (without using kk bootstack or flashing back kk via kdz) ends with unknown baseband, no network signal.
Are you suggesting that people can use custom ROMs directly from lollipop stock?
Click to expand...
Click to collapse
ok i dont know that will try it out.
is it not enough to flash the modem then ?
also its much safer i think to flash the kk Kdz ?
edit: the bootstack is also neede on devices like my gpad (wheres no unlocked BL)... to use twrp on stock LP
thats the reason why i have to use bootstack from kk there
regards
edit2: yes youre right,(just tryed out) i i was not so much on my L90 the last days , so i dont saw that . THx @judas1977
So guys..I don't understand what Bootstack is..What I wanna ask is..
1- ATM I'm in stock Lollipop
2-If I unlock bootloader and install CM, there'll be unknown baseband..And I know this..
3-If I flash KK bootstack on Official LG Lollipop Stock, and then flash a custom ROM, will baseband work?
P.s. My phone is fully working right now, and I don't need bootstack for unbricking my phone.
You need bootstack to get network working on custom ROMs
SlimShady's said:
So guys..I don't understand what Bootstack is..What I wanna ask is..
1- ATM I'm in stock Lollipop
2-If I unlock bootloader and install CM, there'll be unknown baseband..And I know this..
3-If I flash KK bootstack on Official LG Lollipop Stock, and then flash a custom ROM, will baseband work?
P.s. My phone is fully working right now, and I don't need bootstack for unbricking my phone.
Click to expand...
Click to collapse
Yes, That's correct. After flashing KK bootstack you will get a working baseband on customsROMs.
Razer206 said:
What about bootstack C KitKat for D-415 ZNF..... Don't see it listed for people who need it
Click to expand...
Click to collapse
Bootstock C, you mean 10C ?
D415 ZNF ? What's ZNF ?
Code:
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* in the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/
Prerequisites for Installation
- Must have an unlocked bootloader
Installation
- Use Flashify OR:
- Go into fastboot mode
- Install using the following command where <recovery-image> is the relevant file for your device
Code:
fastboot flash recovery <recovery-image>
*** Please do NOT create any mirrors ***
Downloads
All TWRP Builds for Apollo and Thor
Source Code
- Kernel Source
XDA:DevDB Information
TWRP, Tool/Utility for the Amazon Kindle Fire HDX 7" & 8.9"
Contributors
ggow
Version Information
Status: Stable
Stable Release Date: 2016-02-25
Many thank to your great work.
Can Flash it via Flashtify ?
Sent from my LG-D855 using XDA Free mobile app
NeverSmile said:
Many thank to your great work.
Can Flash it via Flashtify ?
Sent from my LG-D855 using XDA Free mobile app
Click to expand...
Click to collapse
Yes you can, as long as your bootloader is unlocked
I assume it's ok to flash this via TWRP 2.8.7.0 (to the recovery Partition of course)?
Cl4ncy said:
I assume it's ok to flash this via TWRP 2.8.7.0 (to the recovery Partition of course)?
Click to expand...
Click to collapse
Should be fine
Sent from my Nexus 6 using Tapatalk
ggow said:
Should be fine
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Thanks, it worked fine.
The screenshot function still creates a 0 bytes file in Pictures\Screenshots though, which can be deleted via TWRP only.
Question:
First run after installation there was a page regarding the option to mount System as read-only with a checkbox whether that page should not re-appear. I did NOT enable (i.e. left it disabled) that checkbox, but I've not seen that page again (regardless if I re-booted into recovery via the extended shutdown menu, or by pressing Vol+&Power at start). Is that option somewhere in the settings? And is it to be considered a bug that the page did not re-appear?
Cl4ncy said:
Question:
First run after installation there was a page regarding the option to mount System as read-only with a checkbox whether that page should not re-appear. I did NOT enable (i.e. left it disabled) that checkbox, but I've not seen that page again (regardless if I re-booted into recovery via the extended shutdown menu, or by pressing Vol+&Power at start). Is that option somewhere in the settings? And is it to be considered a bug that the page did not re-appear?
Click to expand...
Click to collapse
It's not a bug, usually appears on first run only and should not impact TWRP's ongoing use.
NeverSmile said:
Many thank to your great work.
Can Flash it via Flashtify ?
Click to expand...
Click to collapse
ggow said:
Yes you can, as long as your bootloader is unlocked
Click to expand...
Click to collapse
Worked like a charm. Nice visual upgrade over 2.8.7.0. Summary of other changes here.
New Build is Up
- Dated 29 March 2016
- Fix slow performance especially when flashing open-gapps-6.x packages
- I would urge everyone to update their recovery partition before upgrading to future builds of CM-13.0
ggow said:
- Dated 29 March 2016
- Fix slow performance especially when flashing open-gapps-6.x packages
- I would urge everyone to update their recovery partition before upgrading to future builds of CM-13.0
Click to expand...
Click to collapse
Updated via Flashify on a pair of Thors; no issues.
Please help me. my hdx7 has locked bootloader. I made a mistake, flashed your TWRP3.0 .........Now, HDX7 cant work,cant connect computer ,cant in recovery.
only display "kindle fire". how can i repair it? plz.....
chaefei said:
Please help me. my hdx7 has locked bootloader. I made a mistake, flashed your TWRP3.0 .........Now, HDX7 cant work,cant connect computer ,cant in recovery.
only display "kindle fire". how can i repair it? plz.....
Click to expand...
Click to collapse
How did you attempt to flash TWRP (Safestrap, Flashify, FireFlash)? In the end it really doesn't matter. If your HDX won't progress past the gray Kindle Fire screen it is probably toast. Do you know what version of FireOS was last on the device (3.x, 4.x)?
Davey126 said:
How did you attempt to flash TWRP (Safestrap, Flashify, FireFlash)? In the end it really doesn't matter. If your HDX won't progress past the gray Kindle Fire screen it is probably toast. Do you know what version of FireOS was last on the device (3.x, 4.x)?
Click to expand...
Click to collapse
my hdx7 had been flashed twrp2.8, and flashed cm11. Today, I flashed cm12,but i found hdx7 cant work. So i think it maybe because twrp2.8 is old version.
i used twrp2.8 to flash new twrp3.0........
chaefei said:
my hdx7 had been flashed twrp2.8, and flashed cm11. Today, I flashed cm12,but i found hdx7 cant work. So i think it maybe because twrp2.8 is old version.
i used twrp2.8 to flash new twrp3.0........
Click to expand...
Click to collapse
You failed to read the documentation. CM12 also requires an unlocked bootloader as clearly stated in the OP. That's why it didn't flash with TWRP 2.8. There is no "maybe". Played with fire and got burned.
Since you had TWRP 2.8 installed the last version of FireOS was likely 3.1.x. There is an outside chance your device can be recovered following instructions in the following thread. Good luck.
http://forum.xda-developers.com/kin...-to-unbrick-kindle-fire-hdx-firmware-t3277197
Davey126 said:
You failed to read the documentation. CM12 also requires an unlocked bootloader as clearly stated in the OP. That's why it didn't flash with TWRP 2.8. There is no "maybe". Played with fire and got burned.
Since you had TWRP 2.8 installed the last version of FireOS was likely 3.1.x. There is an outside chance your device can be recovered following instructions in the following thread. Good luck.
http://forum.xda-developers.com/kin...-to-unbrick-kindle-fire-hdx-firmware-t3277197
Click to expand...
Click to collapse
thank you very much
chaefei said:
thank you very much
Click to expand...
Click to collapse
Before you try @Davey126's suggestion - assuming you're on Fire OS 3.1.x - you should just give the bootloader unlock a try. Zero risk, it either unlocks or fails.
Cl4ncy said:
Before you try @Davey126's suggestion - assuming you're on Fire OS 3.1.x - you should just give the bootloader unlock a try. Zero risk, it either unlocks or fails.
Click to expand...
Click to collapse
because my hdx7 is second-hand device，i don't know whether it is lock or not.
Before flashed twrp3.0 , it had been flashed twrp 2.8、 cm11. is it means unlock？
chaefei said:
because my hdx7 is second-hand device，i don't know whether it is lock or not.
Before flashed twrp3.0 , it had been flashed twrp 2.8、 cm11. is it means unlock？
Click to expand...
Click to collapse
Well, to be as clear as possible about this. You had the real TWRP installed, i.e. TWRP 2.8.7.0, NOT Safestrap based on TWRP?
If you had the real TWRP installed you were on Fire OS v3.1.x - v3.2.3.2, which are unlockable versions. Even with Safestrap v3.7x it could be worth a try to unlock.
Again: You can't mess up anything by trying. It either unlocks or fails. And you can try the one-click-solution. Be sure to grab the PDA drivers if you suffer from the good ol' device not found problem.
Cl4ncy said:
Well, to be as clear as possible about this. You had the real TWRP installed, i.e. TWRP 2.8.7.0, NOT Safestrap based on TWRP?
If you had the real TWRP installed you were on Fire OS v3.1.x - v3.2.3.2, which are unlockable versions. Even with Safestrap v3.7x it could be worth a try to unlock.
Again: You can't mess up anything by trying. It either unlocks or fails. And you can try the one-click-solution. Be sure to grab the PDA drivers if you suffer from the good ol' device not found problem.
Click to expand...
Click to collapse
thanks. i will try .
i want use fastboot method. But when i connect hdx to computer, the computer have nothing response.....
DISCLAIMER
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Warning:
this rom is for J500F but you can still test and report if it works on the J500FN also i need to mention that i dont own this device.
Information:
On 16.0.6.16 Samsung released officaly Android 6.0.1 for SM-J500F for the Indian J5 model, i decided to take this thing in my hand and tryed to make it 7 days after its release available for all Countries and ofc easy to install. TECHNICALLY it should boot fine for the J500F and J500FN model, however I CANT guarantee that it will boot so you need to try your luck and test. PLEASE: As soon as you test out, head over to XDA and post or pm me if it woked.
Edit: Seems like marshmallow wont boot with the lollipop bootloader so in clear text that does mean that you cant get around using Odin. If you are an J500F user please contact me. For J500FN users i am sorry to say that its unpossible currently to get marshmallow on your device because j500fn will refuse to load the j500f bootloader
Installation:
1. download the rom and put the downloaded file on your internal storage
2. install twrp recovery
3. boot into recovery
4. factory reset, wipe data and cache and format system and data
5. install rom
6. reboot and be patient as firstboot might take a long time
7. enjoy :good::laugh:
Download:
ALPHA_GALAXYJ5_601_ROM
If you could add the features too that would be great, but yeah im downloading and testing now
cheers
Simow.b said:
If you could add the features too that would be great, but yeah im downloading and testing now
cheers
Click to expand...
Click to collapse
Its stock Marshmallow 6.0.1 samsung so u could just google that quick ☺
oranaise2412 said:
Its stock Marshmallow 6.0.1 samsung so u could just google that quick
Click to expand...
Click to collapse
Tested on J500F it's not booting! it just gets you like a big yellow screen and then it reboots to the recovery
Good luck
Simow.b said:
Tested on J500F it's not booting! it just gets you like a big yellow screen and then it reboots to the recovery
Good luck
Click to expand...
Click to collapse
Hmmmm... TECHNICALLY it should work cuz the only dev thingy i did was making it a flashable zip
Maybe its a bootloader problem ! Do u have telegram or hangouts or so ?? Maybe we get this to work
Simow.b said:
Tested on J500F it's not booting! it just gets you like a big yellow screen and then it reboots to the recovery
Good luck
Click to expand...
Click to collapse
Also can u describe that yellow screen ? Does it show j5 splash screen ?
oranaise2412 said:
Also can u describe that yellow screen ? Does it show j5 splash screen ?
Click to expand...
Click to collapse
It shows that when i hit the reboot system after flashing the rom! it shows the samsung galaxy j5 screen then it starts with a blue line in the middle of the screen then it washes out the entire screen with yellow! i don't have hangouts nor telegram, pm me your skype
Simow.b said:
It shows that when i hit the reboot system after flashing the rom! it shows the samsung galaxy j5 screen then it starts with a blue line in the middle of the screen then it washes out the entire screen with yellow! i don't have hangouts nor telegram, pm me your skype
Click to expand...
Click to collapse
Alright lets chat on skype
oranaise2412 said:
DISCLAIMER
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Warning:
this rom is for J500F but you can still test and report if it works on the J500FN also i need to mention that i dont own this device.
Information:
On 16.0.6.16 Samsung released officaly Android 6.0.1 for SM-J500F for the Indian J5 model, i decided to take this thing in my hand and tryed to make it 7 days after its release available for all Countries and ofc easy to install. TECHNICALLY it should boot fine for the J500F and J500FN model, however I CANT guarantee that it will boot so you need to try your luck and test. PLEASE: As soon as you test out, head over to XDA and post or pm me if it woked.
Installation:
1. download the rom and put the downloaded file on your internal storage
2. install twrp recovery
3. boot into recovery
4. factory reset, wipe data and cache and format system and data
5. install rom
6. reboot and be patient as firstboot might take a long time
7. enjoy :good::laugh:
Download:
ALPHA_GALAXYJ5_601_ROM
Click to expand...
Click to collapse
EDIT:
Alright after a little bit of effort me and Simo'w got it working. Stay tuned will provide you with more info soon
I'll try next release on a j500fn. Hope it works!
Let's see, will test it on FN when you tell us how you've made it to work.
Does not work on my j500fn. Screen turns green after install and then turns back to twrp. Maybe there are ways to fix this Problem. Waiting to long for this version.
chello83 said:
Does not work on my j500fn. Screen turns green after install and then turns back to twrp. Maybe there are ways to fix this Problem. Waiting to long for this version.
Click to expand...
Click to collapse
Yea same thing here. Did you wipe system, data etc? Maybe we shouldn't do that in order to make it work.. hmm maybe worth a try I guess?
I wiped everything (cache/davlik/system/secure/storage) with twrp 3.0.2. Installation goes trough withouth any issues.
chello83 said:
I wiped everything (cache/davlik/system/secure/storage) with twrp 3.0.2. Installation goes trough withouth any issues.
Click to expand...
Click to collapse
I know. will test now a few variations: Deleting only system, deleting only Data... Will tell if I get it working or not this way.
EDIT: Not working, waiting for OP.
erik96joe said:
I know. will test now a few variations: Deleting only system, deleting only Data... Will tell if I get it working or not this way.
EDIT: Not working, waiting for OP.
Click to expand...
Click to collapse
This evening i will continue working on it i need more testers p.s. formating system and data is a must
oranaise2412 said:
This evening i will continue working on it i need more testers p.s. formating system and data is a must
Click to expand...
Click to collapse
I will love to test your rom on my j500fn. Maybe this way goes faster than the official samsung ota update for me in germany.
chello83 said:
I will love to test your rom on my j500fn. Maybe this way goes faster than the official samsung ota update for me in germany.
Click to expand...
Click to collapse
I speak german too hit me up on skype : opium165
For all who want to test add me on skype : opium165
Info: The reason why v0.1 did not work is the bootloader so means that we cant boot 6.0.1 with the lollipop bootloader
This evening i tryy to provide the marshmallow bootloader as a odin flashable , if all works fine i l be working on optimzing marshmalllow ( adding root , busybox bla bla )
oranaise2412 said:
I speak german too hit me up on skype : opium165
For all who want to test add me on skype : opium165
Click to expand...
Click to collapse
Added you I am free today all day long, so I can test anytime!
Code:
[COLOR="gray"]
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* in the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/
[/COLOR]
IMPORTANT
- Only works with devices that originally had and retain the bootloaders fromFireOS 5.0.1
- This recovery cannot be flashed whilst the bootloader is locked. In order to boot recovery use the following command from fastboot.
Code:
fastboot boot twrp_fire7_302-0.img
*** Please do NOT create any mirrors ***
Downloads
- Amazon Fire (ford) TWRP Image
Source Code
- Kernel Source
Thanks
csolanol
diegocr
Dees_Troy
XDA:DevDB Information
TWRP, Tool/Utility for the Amazon Fire
Contributors
ggow
Version Information
Status: Stable
Created 2016-11-25
Last Updated 2016-11-26
New Build is Up
- Dated 25 November 2016
- Build Number 3.0.2-0
- Initial Release
Does this work with any FireOS version?
I remember you could only run it with 5.0.X.
Can you run it with other versions now?
tonibm19 said:
I remember you could only run it with 5.0.X.
Can you run it with other versions now?
Click to expand...
Click to collapse
Only works with 5.0.x, will add a note to the OP.
this is awesome! Thanks!
Any chance you could make a 3.1.0 build?
https://www.xda-developers.com/twrp...-support-for-adb-backup-ab-ota-zips-and-more/
FBis251 said:
Any chance you could make a 3.1.0 build?
https://www.xda-developers.com/twrp...-support-for-adb-backup-ab-ota-zips-and-more/
Click to expand...
Click to collapse
Yes, I'm on holiday next week so will do so after that.
ggow said:
Yes, I'm on holiday next week so will do so after that.
Click to expand...
Click to collapse
Current version doesn't let me unencrypt /data. Do you think an updated one will? Have you tested this with an encrypted tablet?
nirogu325 said:
Current version doesn't let me unencrypt /data. Do you think an updated one will? Have you tested this with an encrypted tablet?
Click to expand...
Click to collapse
This appears to be an unresolved issue on some/many devices starting with v3.0.2 and continuing through the 3.1.x series. Head over to TewmWin's site for details - although a well crafted Google search may be more productive.
Davey126 said:
This appears to be an unresolved issue on some/many devices starting with v3.0.2 and continuing through the 3.1.x series. Head over to TewmWin's site for details - although a well crafted Google search may be more productive.
Click to expand...
Click to collapse
No need. It works on my Nexus device with 3.1.x, but it would be better to try an updated TWRP on this tablet to see if it lets me decrypt /data. Also my post is an indirect suggestion to put a warning on the original post that states it doesn't work with encryption. Hopefully it'll work with 3.1.x whenever ggow updates this. Right now, all TWRP shows me is an option to modify system, but doesn't recognize there's an encrypted partition and that's why it doesn't show me the screen where I input the password.
nirogu325 said:
No need. It works on my Nexus device with 3.1.x, but it would be better to try an updated TWRP on this tablet to see if it lets me decrypt /data. Also my post is an indirect suggestion to put a warning on the original post that states it doesn't work with encryption. Hopefully it'll work with 3.1.x whenever ggow updates this. Right now, all TWRP shows me is an option to modify system, but doesn't recognize there's an encrypted partition and that's why it doesn't show me the screen where I input the password.
Click to expand...
Click to collapse
Field reports suggest a password prompt is raised on 3.1.x for some devices but decryption ultimately fails. Didn't dig deep enough to identify device types or commality across posts. Appears hardware dependent.
Davey126 said:
Field reports suggest a password prompt is raised on 3.1.x for some devices but decryption ultimately fails. Didn't dig deep enough to identify device types or commality across posts. Appears hardware dependent.
Click to expand...
Click to collapse
Yeah, that's why I said it's more productive to try a newer version on this tablet. I learned a lesson some months ago and no longer run any device unencrypted. That's why it's important to me.
@ggow
can we use 2ndinit source code from https://forum.xda-developers.com/fire-tv/development/firetv-1-bueller-twrp-recovery-t3383286 (thanks to @rbox for source code https://github.com/androidrbox/firetv-2ndinit ) for boot TWRP on rooted Fire up to 5.3.2.1?
my knowledges is not enough for this
Kramar111 said:
@ggow
can we use 2ndinit source code from https://forum.xda-developers.com/fire-tv/development/firetv-1-bueller-twrp-recovery-t3383286 (thanks to @rbox for source code https://github.com/androidrbox/firetv-2ndinit ) for boot TWRP on rooted Fire up to 5.3.2.1?
my knowledges is not enough for this
Click to expand...
Click to collapse
No. Recoveries and ROMs built for other devices do not work. Also, 5.3.2.1 is not able to be rooted, except in one, as of now, unrepeatable instance. Lastly, only 5.0.x can boot TWRP, as Amazon removed the command in later versions.
@PorygonZRocks
I know it all
I'm talking about principle. Not about using "FireTV 1 (bueller) TWRP Recovery" as-is
As i understand, 2ndinit can be adapted for Amazon Fire with some nuances
Kramar111 said:
@PorygonZRocks
I know it all
I'm talking about principle. Not about using "FireTV 1 (bueller) TWRP Recovery" as-is
As i understand, 2ndinit can be adapted for Amazon Fire with some nuances
Click to expand...
Click to collapse
Sorry, I probably should have read the link before talking ?
It looks cool, but I don't have the technical knowledge to know if it's portable.
ggow said:
Yes, I'm on holiday next week so will do so after that.
Click to expand...
Click to collapse
Any progress on a new TWRP for this device? Your post is months old, that's why I'm wondering. A new version might finally let me decrypt /data.
nirogu325 said:
Any progress on a new TWRP for this device? Your post is months old, that's why I'm wondering. A new version might finally let me decrypt /data.
Click to expand...
Click to collapse
What would being able to decrypt the /data do for the end user? And will we every get to a point where we dont need the super tool to boot into twrp for this device?
Dakotalee24 said:
What would being able to decrypt the /data do for the end user? And will we every get to a point where we dont need the super tool to boot into twrp for this device?
Click to expand...
Click to collapse
I assume at least one of your 5th gen Fire devices is rocking a 5.0.x bootloader. While you need a tether to load/boot TWRP the SuperTool is not required. Simply place your device in fastboot mode and issue the following command from the host command prompt;
fastboot boot <recovery.img>
....where 'recovery.img' is the name of the TWRP image. You'll need to prefix as needed depending where the image file is located.
Dakotalee24 said:
What would being able to decrypt the /data do for the end user? And will we every get to a point where we dont need the super tool to boot into twrp for this device?
Click to expand...
Click to collapse
Addressing the first question since Davey126 already addressed the second one. By the time of that post, I had my tablet encrypted and the current TWRP version in this thread never prompt me for decryption. I stopped using encryption because I read this device's SoC doesn't have AES (hardware encryption acceleration) plus Lollipop doesn't behave well when encrypted (unlike Marshmallow or later Android versions).