CyanogenMod is a free, community built, aftermarket firmware distribution of Android M (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
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.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed.
This rom is for both the Nook Tablet 512M/8GB and 1GB/16GB versions. The device code name is "acclaim".
Prerequisites:
A recovery. To install a recovery when coming from a stock device, you need to prepare a special SD card. Installation instructions can be found here on xda.
Installation:
Grab a new recovery (http://get.cm/?device=acclaim or TWRP) and flash it with fastboot.
If you have a CM installed, flash the new recovery and try the updater, otherwise download the zip from nightlies, boot to CM recovery or TWRP and flash it.
Once a version is installed (and all bugs fixed), you will be able to use CM Updater
Settings->About tablet->CyanogenMod updates->Refresh
THE NEW NIGHTLIES HAVE EMULATED STORAGE ENABLED. YOU LOOSE ALL YOUR DATA. MAKE SURE YOU BACKUP!!!! THE INTERNAL EMMC 1GB PARTITION IS ALSO NOT ACCESSIBLE ANYMORE. COPY THE CONTENT. THE EXTERNAL SDCARD IS NOT USED ANYMORE AS PRIMARY STORAGE. ALL APP DATA ON THE SDCARD WILL BE LOST. I ALSO RECOMMEND TO WIPE.
BACKUP!
RE-PARTITIONING IS NOT MANDATORY. IF YOU WANT TO RECLAIM THE 1GB PARTITION (called media) YOU CAN TRY TO FOLLOW THE RE-PARTITION GUIDE:
https://docs.google.com/document/d/1wSAaAZfQcnvkiHKlbZ7_H1h67m2kx0mq-p3Wjgue3qA/edit?usp=sharing
PLEASE COMMENT ON THE DOCUMENT IF SOMETHING IS NOT CLEAR.
Building:
The CM wiki explains that here: http://wiki.cyanogenmod.org/w/Build_for_acclaim
Returning to stock BN firmware:
If you have installed above rom and the CWM recovery and you really hate it and want to go back to stock, you may wish to try to flash the original acclaim_update.zip from BN. You have to unzip that file and edit META-INF/com/google/android/updater-script. Drop the first two lines here:
assert(getprop("ro.product.device") == "blaze" ||
getprop("ro.build.product") == "blaze");
Zip the package again. Then go to recovery, flash the zip, wipe, and reboot.
Support:
For any issues encountered, please post into this forum, but add steps to reproduce and dmesg, logcat and audit.log information. If you don't know what this is or how to get them, try to find that out first before posting here.
Thanks:
hashcode, ntemis, kuzma30, fattire, mik_os, and many others that contribute to cyanogenmod and especially this version.
kuzma30 - great kernel job
hashcode - we have reused lots of your work and effort for the various omap devices (esp kindle fire). It is thanks to you mainly that we are now official CM device. Also many thanks for the L bringup help.
mik_os - great touchscreen firmware flasher and other efforts
fattire - for helping us everywhere he can
ntemis - thanks for giving so much energy to this - esp for 4.4 and L I have copied lots of things from you
CM community (stargo, etc.) - thanks for replying to all my questions!
DISCLAIMER:
- update the CWM if you come from older versions - otherwise you'll see funny error messages when installing zip
- It is possible that you need to wipe your device. I did not do that, but...
- Also you must flash your own gapps. It can be found somewhere....
- The SELINUX policies are enforced now.
Known issues:
- system partition is too small for full gapps. use a mini gapp package.
- the touchscreen firmware flasher doesn't work on M. Use CM11 to flash it first.
- Currently the CM13 recovery does not flash the open gapps (due to move to toybox instead of busybox)
- CMUpdater (and adb reboot recovery) don't boot into recovery
- The system is altogether not really the fastest thing on earth
Recently fixed:
- M bringup
Get it from
http://download.cyanogenmod.org/?device=acclaim
Get ENG recovery from here. It allows to adb into recovery even when data is wiped.
File: https://dl.dropboxusercontent.com/u...cclaim-eng-recovery-UNOFFICIAL-20150606.0.img
md5sum: 6136fc49c5e9a32f115d40d762bb6f2d
- Reserved -
Need some help. I flashed the recovery from the CM site, and now it only boots to recovery, even after side-loading the CM13 zip for acclaim. Any ideas how to get out of recovery?!?!
Edit: I also tried to "adb sideload" a different recovery (CWM) but it fails to install, saying "E: footer is wrong, E: signature verification failed"
I can only get into adb sideload mode, as "adb devices" says my device is "UNAUTHORIZED", and can't boot to CM at all.
Edit #2: Anything (other than CM zip) I try to flash from ADB sideload within CM recovery fails due to signature verification. Seems like its checking for updates signed by CM. Ugh, not seeing a way out of this.
Thank you, it runs well in account to the specs and age of this old tablet. This experience is better than the CM12 experience, more stable.
Sent from my LGLS991 using Tapatalk
srgibbs99 said:
Need some help. I flashed the recovery from the CM site, and now it only boots to recovery, even after side-loading the CM13 zip for acclaim. Any ideas how to get out of recovery?!?!
Edit: I also tried to "adb sideload" a different recovery (CWM) but it fails to install, saying "E: footer is wrong, E: signature verification failed"
I can only get into adb sideload mode, as "adb devices" says my device is "UNAUTHORIZED", and can't boot to CM at all.
Edit #2: Anything (other than CM zip) I try to flash from ADB sideload within CM recovery fails due to signature verification. Seems like its checking for updates signed by CM. Ugh, not seeing a way out of this.
Click to expand...
Click to collapse
Most likely the bootcounter reached max number of boots. So when booting, the bootloader sends you to recovery.
I'll try to see if the bootcounter reset doesn't work anymore in cm13 recovery.
Anyway, to get you out of this, can't you hold the nook key during boot to go in cyanoboot menu, start fastboot and flash twrp or old recovery with fastboot?
Chris
I Confirm, experience is much better than CM12.1.
Chris you are a legend.
chrmhoffmann said:
Most likely the bootcounter reached max number of boots. So when booting, the bootloader sends you to recovery.
I'll try to see if the bootcounter reset doesn't work anymore in cm13 recovery.
Anyway, to get you out of this, can't you hold the nook key during boot to go in cyanoboot menu, start fastboot and flash twrp or old recovery with fastboot?
Chris
Click to expand...
Click to collapse
The bootcounter reset indeed doesn't work anymore.
To get out of here:
- Let the device go to recovery
- adb to the device
- run the following commands:
mount /system
/sbin/clearbootdata.sh
Reboot
I'll try to fix this ASAP.
Chris
chrmhoffmann said:
The bootcounter reset indeed doesn't work anymore.
To get out of here:
- Let the device go to recovery
- adb to the device
- run the following commands:
mount /system
/sbin/clearbootdata.sh
Reboot
I'll try to fix this ASAP.
Chris
Click to expand...
Click to collapse
Fixed:
http://review.cyanogenmod.org/#/c/128693/
Chris
chrmhoffmann said:
Fixed:
http://review.cyanogenmod.org/#/c/128693/
Chris
Click to expand...
Click to collapse
Thanks for the reply Chris!
The boot counter does increment (top left corner of cyanoboot, goes from 0-9 then starts over) however no matter what I press on that screen it immediately loads recovery.
Also, I can't get shell access with ADB. When I do "adb devices" it says this device is "UNAUTHORIZED". I can, however, choose "Apply update via ADB" in recovery and it changes to "sideload" but it still won't give me shell access.
Without shell access, what are my options? Seems like i can only flash official CM builds. Will the next nightly help me if your fix is in it? Does it affect the boot.img or or does that only affect the recovery?
First boot time? ... working now!
How long does the initial flash take to boot up for the first time?
I built this ROM (cm-13.0-20160116-UNOFFICIAL-acclaim.zip) and gave up after 45 minutes on the bootanimation.
Right now, I am flashing the cm-13.0-20150117-NIGHTLY-acclaim.zip and it is still booting after 30 minutes.
I flashed with TWRP 2.8.7. Is this OK?
BTW - great work on this ROM!
== // ==
Never mind. I built another (completely Linaro) ROM and it flashed and booted OK. The only thing that I did differently was that I did not flash SuperSu-v2.46 after I flashed the ROM.
Again, thanks for bringing Marshmallow to this device!
srgibbs99 said:
Thanks for the reply Chris!
The boot counter does increment (top left corner of cyanoboot, goes from 0-9 then starts over) however no matter what I press on that screen it immediately loads recovery.
Also, I can't get shell access with ADB. When I do "adb devices" it says this device is "UNAUTHORIZED". I can, however, choose "Apply update via ADB" in recovery and it changes to "sideload" but it still won't give me shell access.
Without shell access, what are my options? Seems like i can only flash official CM builds. Will the next nightly help me if your fix is in it? Does it affect the boot.img or or does that only affect the recovery?
Click to expand...
Click to collapse
I am afraid that you are now in trouble, but it is not fatal.
Options:
a) You can flash with "adb sideload" a zip that installs another recovery. I'll try to create that for CM13 now, as there's only some really old stuff available.
b) You can prepare a SDCARD that flashes recovery like if you would come from stock.
Hang on a bit until I provide a).
Chris
chrmhoffmann said:
I am afraid that you are now in trouble, but it is not fatal.
Options:
a) You can flash with "adb sideload" a zip that installs another recovery. I'll try to create that for CM13 now, as there's only some really old stuff available.
b) You can prepare a SDCARD that flashes recovery like if you would come from stock.
Hang on a bit until I provide a).
Chris
Click to expand...
Click to collapse
Sounds good and thanks.
I actually tried dropping the TWRP recovery.img inside the official CM13 zip and flashing that, but again, it failed due to signature verification. I wonder if you could have access to add a build that includes TWRP (or a fixed recovery image) to the "experimental" channel for CM? Or maybe a boot.img that gives me a second or two to press N and load something other than EMMC recovery.
Maybe that way it would be signed by CM and the current recovery would accept it.
chrmhoffmann said:
I am afraid that you are now in trouble, but it is not fatal.
Options:
a) You can flash with "adb sideload" a zip that installs another recovery. I'll try to create that for CM13 now, as there's only some really old stuff available.
b) You can prepare a SDCARD that flashes recovery like if you would come from stock.
Hang on a bit until I provide a).
Chris
Click to expand...
Click to collapse
I had some time today so I tried b) and it finally got some results. I was able to boot to another recovery and flash twrp. Installing CM13 now! I'll update once im done.
Demetris said:
I Confirm, experience is much better than CM12.1.
Chris you are a legend.
Click to expand...
Click to collapse
Yep, this tablet is usable on CM13.
Sent from my LGLS991 using Tapatalk
srgibbs99 said:
I had some time today so I tried b) and it finally got some results. I was able to boot to another recovery and flash twrp. Installing CM13 now! I'll update once im done.
Click to expand...
Click to collapse
Finally got it up and running on CM13. Runs great, and as others have said its much more stable than CM12.
Also, based on my experience, I would advise against installing the CM custom recovery. Much safer to stick with TWRP.
Thanks for all your help Chris.
The new nightlies should have the boot counter fixed, but it's true that cm recovery doesn't support open gapps flash right now as busy box support was dropped.
So it's maybe best to stick with twrp until further notice.
Chris
Sent from my wiko using Tapatalk
Updated to the latest nightly last night (20160119) and upon reboot got "Google Play Services has stopped", and a notification that Play services wont run until you update,.
am unable to go into apps setting to attempt to clear app storage . Crashes when trying the "manage space" option for Google Play Services
ignore , sorry I thought I was in the CM 12 thread duh...
I never posted on this site but a google now card mentioned cm13 on the ole nook tablet so I gave it a whirl.
Clean flashed the 1/18 nightly the other night. Flashed the smallest gapps I could find because the other kept giving me error that not enough space. Was up and running and though bit slow all seemed well.
Tried running cm updater to get the 1/19 nightly but I got a md5 error. So I ended up downloading the nightly. Then I had to move it to the external sd card. Then I dirty flashed it. Everything still worked and no errors except there were no quick tiles when I pulled down from the top. This was fixed by holding the gear icon for a few seconds until it was spinning. After that there were several options that popped up and then the quick tiles were back.
Lastly and the main reason I am here. Is the home screen supposed to be stuck in landscape mode? The lock screen rotates but the home screen does not. Also the clock is not correct and I am unable to change it.
I use ClockWorkMod 6.0.4.5 to flash the roms btw if that matters.
You must change the auto rotate settings for the home screen.
Chris
Auto rotate is on as is 0, 90, and 270 degrees. Also have rotate on lock screen on. Not sure if there is another rotate setting I am not seeing. I will clean flash the next update and see if this fixes it.
Edit: fixed. I did not know about the cm13 menu by holding the screen then swiping up. Rookie mistake.
Related
My brother has a Nabi 2 which was rooted, and we recently received an update from Jelly Bean to Kit Kat. We (more like I) tried to do this without unrooting, and it ended up boot looping for around 4 hours before I intervened. I downloaded the latest stock ROM I could find, and I went into TWRP to flash it. Every single time, it says "Unable to flash zip '/external_sdcard/246stock.zip', then tells me that there is no operating system installed. I tried upgrading TWRP, and got 2.8. Touch was very close to unresponsive. I also tried 2.7.1.0, and 2.7.0.0, and also every other version I could find. Every single version either couldn't flash it, couldn't mount anything, or touch was unresponsive. I downloaded all the recoveries from xda's Nabi 2 page. None of them work. Is there anything I can try to fix this?
wither719 said:
My brother has a Nabi 2 which was rooted, and we recently received an update from Jelly Bean to Kit Kat. We (more like I) tried to do this without unrooting, and it ended up boot looping for around 4 hours before I intervened. I downloaded the latest stock ROM I could find, and I went into TWRP to flash it. Every single time, it says "Unable to flash zip '/external_sdcard/246stock.zip', then tells me that there is no operating system installed. I tried upgrading TWRP, and got 2.8. Touch was very close to unresponsive. I also tried 2.7.1.0, and 2.7.0.0, and also every other version I could find. Every single version either couldn't flash it, couldn't mount anything, or touch was unresponsive. I downloaded all the recoveries from xda's Nabi 2 page. None of them work. Is there anything I can try to fix this?
Click to expand...
Click to collapse
You don't "install" that zip, you "restore" it.
Use TWRP 2.7.0
Download this 3.0.13 stock ZIP
Use an external SDcard and make a backup of just "boot"(this is a setup for next step)
Put SD card in computer. Navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
- Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
- Unzip the 3.0.13 stock you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. This should set you up for the 3.0.13 ROM.
- Download this 3.0.13 bootloader
- Copy the zip to the SDcard. This will be for the bootloader update.
- Put sdcard in Nabi
- Go to "restore tab", and find the backup under the "yourfolder" you made and unzipped the files to.
- You should be able to select boot, system, and addon and skip the others.
- If everything restores then go to TWRP "install tab", find the bootloader zip you downloaded and install it.
- Reboot
aicjofs said:
You don't "install" that zip, you "restore" it.
Use TWRP 2.7.0
Download this 3.0.13 stock ZIP
Use an external SDcard and make a backup of just "boot"(this is a setup for next step)
Put SD card in computer. Navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
- Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
- Unzip the 3.0.13 stock you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. This should set you up for the 3.0.13 ROM.
- Download this 3.0.13 bootloader
- Copy the zip to the SDcard. This will be for the bootloader update.
- Put sdcard in Nabi
- Go to "restore tab", and find the backup under the "yourfolder" you made and unzipped the files to.
- You should be able to select boot, system, and addon and skip the others.
- If everything restores then go to TWRP "install tab", find the bootloader zip you downloaded and install it.
- Reboot
Click to expand...
Click to collapse
ok, im in BIG trouble with my daughter... Yep, I managed to brick her Nabi 2 following this tutorial and I dont know really know where I went wrong. But now when the Nabi 2 is powered on, all I see is the nabi logo, but no OS...or TWRP!... eeek!
I had been trying for days to get a stable TWRP on and Gapps, I did get TWRP v2.3.3.0 up and running at one point, but no Gapps installed and no SuperSU to be found, it was as if it wasnt rooted at all. (even after reinstalling both within TWRP). Then of course i found a thread that said Gapps didnt work on nabi 2 version 2.1...!
I do have a TWRP backup folder saved but i dont seem to have any way to get it back onto the Nabi 2... as its no longer detected in windows like it was before..? (despite the ding sound windows makes when plugged in ?).
I can only get to the 1st bootmenu (holding Vol+ and Power ok. Selecting any options results in little (or nothing) happening... i.e. when selected;
Boot Normally - nothing happens, nabi logo only. And if i leave it too long, it freezes here and i have to reboot.
Fastboot Protocol - with usb connected to pc, i do get to the Bootloader menu with, Bootloader, Continue, Reboot-bootloader, Reboot and Poweroff , options. The Pc 'dings' to indicate detection, but is not detected by adb ?
Recovery Kernel - nothing happens, nabi logo only.
Forced Recovery - screen goes black, then nothing follows.
on Fastboot Protocol menu, if i select the options;
Bootloader - without touching anything, pc dings to indicate some connection...?
Continue - if selected, i hear windows drop whatever connection it had previous..?
Reboot-bootloader - nothing happens, nabi logo only.
Reboot - reboots, then nabi logo only.
Poweroff - nabi 2 shuts down.
As it stands , all i can access are these options above, but i dont seem to have a way of getting windows to communicate over the usb cable...? that said, with pdanet running, it does detect the nabi 2, but of course it cant talk to it as I cant get to pdanet on the nabi 2... just gives some weird error that im using wrong adb , or it just cant connect to the nabi.
Tried using Nabilab v2, but device is not detected...?
...so i would be most grateful if some nabi 2 guru could assist with any possible resurrection, otherwise I will remain "the worst daddy ever"...ugh!
cheers in advance
the_xlr8r said:
ok, im in BIG trouble with my daughter... Yep, I managed to brick her Nabi 2 following this tutorial and I dont know really know where I went wrong. But now when the Nabi 2 is powered on, all I see is the nabi logo, but no OS...or TWRP!... eeek!
I had been trying for days to get a stable TWRP on and Gapps, I did get TWRP v2.3.3.0 up and running at one point, but no Gapps installed and no SuperSU to be found, it was as if it wasnt rooted at all. (even after reinstalling both within TWRP). Then of course i found a thread that said Gapps didnt work on nabi 2 version 2.1...!
I do have a TWRP backup folder saved but i dont seem to have any way to get it back onto the Nabi 2... as its no longer detected in windows like it was before..? (despite the ding sound windows makes when plugged in ?).
I can only get to the 1st bootmenu (holding Vol+ and Power ok. Selecting any options results in little (or nothing) happening... i.e. when selected;
Boot Normally - nothing happens, nabi logo only. And if i leave it too long, it freezes here and i have to reboot.
Fastboot Protocol - with usb connected to pc, i do get to the Bootloader menu with, Bootloader, Continue, Reboot-bootloader, Reboot and Poweroff , options. The Pc 'dings' to indicate detection, but is not detected by adb ?
Recovery Kernel - nothing happens, nabi logo only.
Forced Recovery - screen goes black, then nothing follows.
on Fastboot Protocol menu, if i select the options;
Bootloader - without touching anything, pc dings to indicate some connection...?
Continue - if selected, i hear windows drop whatever connection it had previous..?
Reboot-bootloader - nothing happens, nabi logo only.
Reboot - reboots, then nabi logo only.
Poweroff - nabi 2 shuts down.
As it stands , all i can access are these options above, but i dont seem to have a way of getting windows to communicate over the usb cable...? that said, with pdanet running, it does detect the nabi 2, but of course it cant talk to it as I cant get to pdanet on the nabi 2... just gives some weird error that im using wrong adb , or it just cant connect to the nabi.
Tried using Nabilab v2, but device is not detected...?
...so i would be most grateful if some nabi 2 guru could assist with any possible resurrection, otherwise I will remain "the worst daddy ever"...ugh!
cheers in advance
Click to expand...
Click to collapse
Wow I havent been on here in ages, got an email about your quote though.
I have forgotten so much about these Nabis over the last decade?! So how did you get to the non-booting part? You were able to complete the steps above all successfully? or did it fail at some part?
If you successfully flashed 3.0.13 bootloader with install in TWRP then I don't think you will be able to boot the TWRP you had on the device. That would be my guess at this point why you can't get to recovery.
[NABI] General Information
Fuhu Nabi General information 1. Introduction It was only recently that the Nabi2 got it's own forum. This device has been out a couple of years so the information you may be looking for is spread all over XDA. The largest single chunk of...
forum.xda-developers.com
Read the above. You are pretty much stuck in having to use fastboot.(The driver must be installed if you keep hearing the ding). You will need a fastboot.exe if you don't have one. Search minimal ADB and fastboot. I'd download TWRP 2.8.7 and try to use section 7 to get it on device i.e "fastboot flash recovery recovery.img"
If you unsuccessfully flashed bootloader then you need to use TWRP 2.8.5 Files should be in that thread also or my AHF https://androidfilehost.com/?w=files&flid=41987.
Ill check back later
aicjofs said:
Wow I havent been on here in ages, got an email about your quote though.
I have forgotten so much about these Nabis over the last decade?! So how did you get to the non-booting part? You were able to complete the steps above all successfully? or did it fail at some part?
If you successfully flashed 3.0.13 bootloader with install in TWRP then I don't think you will be able to boot the TWRP you had on the device. That would be my guess at this point why you can't get to recovery.
[NABI] General Information
Fuhu Nabi General information 1. Introduction It was only recently that the Nabi2 got it's own forum. This device has been out a couple of years so the information you may be looking for is spread all over XDA. The largest single chunk of...
forum.xda-developers.com
Read the above. You are pretty much stuck in having to use fastboot.(The driver must be installed if you keep hearing the ding). You will need a fastboot.exe if you don't have one. Search minimal ADB and fastboot. I'd download TWRP 2.8.7 and try to use section 7 to get it on device i.e "fastboot flash recovery recovery.img"
If you unsuccessfully flashed bootloader then you need to use TWRP 2.8.5 Files should be in that thread also or my AHF https://androidfilehost.com/?w=files&flid=41987.
Ill check back later
Click to expand...
Click to collapse
Hi, thanks for getting back ...
Q. So how did you get to the non-booting part? You were able to complete the steps above all successfully? or did it fail at some part?
A. yes i followed the tut but once i rebooted that was the end and where my big problems began.
Q. If you successfully flashed 3.0.13 bootloader with install in TWRP then I don't think you will be able to boot the TWRP you had on the device. That would be my guess at this point why you can't get to recovery.
A. Yes, using TWRP i installed 3.013 bootloader.
Q. You are pretty much stuck in having to use fastboot. (The driver must be installed if you keep hearing the ding). You will need a fastboot.exe if you don't have one. Search minimal ADB and fastboot.
A. This may be the issue, i may be using older version of adb and fastboot. I already had minimal adb stored away, so i experimented by copying the adb files over to my NabiLabFull folder, this time it was green (detected) ... sort of...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ill have a read at the links you provided and will report back soon, thanks.
ok... getting somwehere but not where i expected....
i tried to install the 2 x TWRP versions you mentioned but it wouldnt load into either. So i reverted back to trying 2.3.3.0 and bingo , im in... but shouldnt 2.8.5 or 2.8.7 have worked since Im now showing Navi version as 3.0.13.. (was previously on 2.1.9) ?
im sitting at the TWRP 2.3.3.0 menu now , and still have Nabilab running but am afraid to do anything next lol.... where should i proceed to, from here ? Should I be installing any particular version of Root and Gapps now that im into TWRP 2.3.3.0 (or even try to update TWRP beforehand ?
PS. I am using a UK nabi 2 , in case that makes any difference to files im downloading to it ?
cheers
Im not at a location where I can look at the Nabilab script but as I recall the script is pulling it from build.prop on the system partition. This would indicate to me that the system partition flashed, and so likely the addon and boot. Also the fact that you can't boot another TWRP besides 2.3.3, and the normal boot hanging at the logo leads me to believe that the bootloader was not updated.
Again I'm trying to remember here....but as I recall the bootloader for the Nabi is passing a commandline to the kernel. You have a kernel in the 3.0.x ROM and an identical kernel in TWRP 2.8.7. The fact that neither boot would mean to me the bootloader is original and passing the old commandline to a newer kernel.
You have to get things in sync. The bootloader and the boot.img(kernel+ramdisk) have to match each other. The way that makes the most sense is to install the bootloader3013 zip through TWRP. You already tried that obviously and that's how you got here.
1) You could try the bootloader install inside TWRP again, seems like you can recover if it fails now. Of course if it works then 2.3.3 TWRP should no longer work(which is what I thought happened and why you couldn't boot TWRP initially) so you'd have to try the 2.8.7 at that point.
2) Since the bootloader is original(or Jellybean-ish) you could restore your backup and regroup.
When I get to a place I can look at the install script for the bootloader maybe I can jog my memory. I thought it just dd to mmcblock0
ok. thanks.
so i make no more mistakes, ill check I have all the correct files i need with you first...
I have saved to external sdcard, KK3013bootloader.zip containing;
META-INF
android-info.txt
blob
I have also saved to external sdcard, 3013stock.zip (unzipped)
I have also saved to external sdcard, some old Gapps.zip version (no idea if recent or not) ?
I have also saved to external sdcard, some old root.zip version, again, not sure if correct ?
I think I'm breaking it when i get to here...
1) You could try the bootloader install inside TWRP again, seems like you can recover if it fails now. Of course if it works then 2.3.3 TWRP should no longer work(which is what I thought happened and why you couldn't boot TWRP initially) so you'd have to try the 2.8.7 at that point.
....So, if im in TWRP 2330 now, and I install KK3013Bootloader.zip, it will then no longer boot to TRWP ... is that correct? If so, how then do i get TWRP 285 or 287 working ?
....think i'm getting a smidge lost at this bit lol
[update] - cannot install anything in TRWP 2330 as its not recognizing my 64gb sdcard (formatted to fat32) ... does it have to be a certain formatted type FAT/FAT32/EXT12/3/4 or other ?
Also, i couldnt find a working download link for anyone's scripts... many thanks
the_xlr8r said:
I think I'm breaking it when i get to here...
1) You could try the bootloader install inside TWRP again, seems like you can recover if it fails now. Of course if it works then 2.3.3 TWRP should no longer work(which is what I thought happened and why you couldn't boot TWRP initially) so you'd have to try the 2.8.7 at that point.
So, if im in TWRP 2330 now, and I install KK3013Bootloader.zip, it will then no longer boot to TRWP ? is that correct. If so, how then do i get TWRP 285 or 287 working ?
[update] - cannot install anything in TRWP 2330 as its not recognizing my 64gb sdcard (formatted to fat32) ... does it have to be a certain formatted type FAT/FAT32/EXT12/3/4 or other ?
Click to expand...
Click to collapse
For #1 You install the bootloader zip. Swipe install then reboot. It won't do anything at first because it installs the "blob" (which is the bootloader) to the staging partition. Reboots for 15 seconds and installs the blob. The only way at that point to get a newer TWRP is by booting bootloader to fastboot, and then fastboot flash the newer TWRP on to it.
No it should recognize fat32. There was something about storage being realigned between versions too. You could always use adb too I guess.
adb push bootloaderXXXX.zip /data/media ?
The end of this thread may be usefully too
[RECOVERY][NABI2] TWRP 2.3.3.0, 2.8.5.0 testing
This is an update to the TWRP recovery for the Nabi 2. At this point this recovery is still considered in testing. The normal disclaimers apply. Have a good backup moved to your computer from the previous recovery. Before starting this...
forum.xda-developers.com
The original TWRP posts
Nabi 2 Root and Gapps Install
#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...
forum.xda-developers.com
Nabi 2 Root and Gapps Install
#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...
forum.xda-developers.com
thanks, am i downloading the correct TWRP zip ?
TWRP 2.8.5.0 Released
TWRP 2.8.5.0 is out now for all currently supported devices.
twrp.me
Which version Gapps should i be using ?
The Open GApps Project
OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.
opengapps.org
the_xlr8r said:
thanks, am i downloading the correct TWRP zip ?
TWRP 2.8.5.0 Released
TWRP 2.8.5.0 is out now for all currently supported devices.
twrp.me
Which version Gapps should i be using ?
The Open GApps Project
OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.
opengapps.org
Click to expand...
Click to collapse
No download the TWRP in one of the last 2 links I sent. First is 2.8.5, and other is 2.8.7
I thought on KitKat Fuhu actually has Gapps? You will let Playstore update it to whatever version they stopped with for KitKat support.
There is always NabiLabGUI2015 https://drive.google.com/file/d/1x_4btZE2VzYWJ_aag9U20ubIGY9NXjcN/view?usp=sharing
I never really finished the project but it might be easier as it has all the recoveries already in it. Stay away from NVflash/APX stuff for now.
ok , sorry i already went ahead and installed bootloader3103
then ADB'd on twrp-recovery-KKNV7AUS-287.zip
I can now get TWRP 2.9.7.0 loaded up, but still no OS booting once i have rebooted the nabi2...
maybe the OS is missing ..? how do i reinstall it ? (i tried doing a restore by using the old TWRP backup i had from the start , by pasting in the 3013stock files) but that didnt work.
....still stuck, but getting closer
the_xlr8r said:
maybe the OS is missing ..? how do i reinstall it ? (i tried doing a restore by using the old TWRP backup i had from the start , by pasting in the 3013stock files) but that didnt work.
....still stuck, but getting closer
Click to expand...
Click to collapse
No I think we are good, the plan was for you to flash bootloader to proper, and that seems to be the case.
It might not be missing the OS, it might need data/media wiped(factory reset). Of course the tablet is completely wiped during that, don't know if the daughter had stuff on there.
Either way it doesn't hurt to try and restore it again. When you say pasting the 3013 restore files, you mean in the folder with your backup? Over top the files or just a folder in the same folder as the backup?
The fact that Nabilab says 3.0.13 makes me think the system files were restored and not missing. You did all this through NabiLab or TWRP?
hi , tried every way i could
yes, i copied and pasted the 3013stock files over the top of the old backup and tried to restore, still didnt boot to OS.
tried your NabiLab2015 , UK menu didnt open so i just used the US menu.
tried to follow step.2 "Flash Full" , seemed to start ok , but then..... this happened...
Note: using NabiLab2015, I skipped using step 1. to download stock 3013, as it wouldnt do it, so i copied the 3013.zip i had downloaded earlier into this folder. which seemed to allow step 2 to work...
whats best option to use now that it failed at 30% install ? thanks
the_xlr8r said:
hi , tried every way i could
yes, i copied and pasted the 3013stock files over the top of the old backup and tried to restore, still didnt boot to OS.
tried your NabiLab2015 , UK menu didnt open so i just used the US menu.
tried to follow step.2 "Flash Full" , seemed to start ok , but then..... this happened...
Note: using NabiLab2015, I skipped using step 1. to download stock 3013, as it wouldnt do it, so i copied the 3013.zip i had downloaded earlier into this folder. which seemed to allow step 2 to work...
whats best option to use now that it failed at 30% install ? thanks
View attachment 5718161
Click to expand...
Click to collapse
Looks like the ADB connection reset. This step is copying the files to the tablet to data/media. It failed at addon. Either cable to computer had a glitch or maybe data/media(internal storage) is full. You can retry again, it didn't flash anything to device at all.
Maybe in TWRP, go to advanced, terminal and type bdf? See if filesystem looks ok. Seems like a cable issue right now though
[UPDATE]
thankyou sir for all your help.
after another try on a Flash Full , everything was installed and it rebooted and updated.
i'm so glad your email still worked after 10 years of not looking at this nabi stuff , otherwise this nabi of mine would be in the bin before now.. lol.... @)
..couple of things, now that its on android 4.4 etc , is it safe to perform any further updates ?
Its running as a US version now, will that affect anything with me being in the UK ?
still not able to get external sdcard detected in TWRP... any ideas ?
many thanks
the_xlr8r said:
[UPDATE]
thankyou sir for all your help.
after another try on a Flash Full , everything was installed and it rebooted and updated.
i'm so glad your email still worked after 10 years of not looking at this nabi stuff , otherwise this nabi of mine would be in the bin before now.. lol.... @)
one last thing, now that its on android 4.4 etc , is it safe to perform any further updates ?
Click to expand...
Click to collapse
No problem, havent thought about Nabi's in probably 2 years. Some of my favorite memories were helping people on Christmas Day, or this Dad from Brazil on his son's birthday, Mom from Italy etc, etc and imagining the kids didn't even know all the panic haha.
You are pretty much done at 4.4. Really no OS level updates to do. Fuhu never did anything else, the source code they gave us was worthless for kernel building, and honestly this Tegra chipset was at it end anyway. Like I said earlier Google play services will update to the latest for the kitkat version, and that will be it. Apps that still support Android this old will have updates of course.
EDIT: Its funny about NabiLabGUI2015. I get emails about my google drive link because link is so old and I have to manually share it the zip for it. I forgot that it would have been really useful if I ever finished it.
most of the trouble I was facing was working links on the forum, hardly any worked and I spent days searching.
even searching for NabiLab2015 proved impossible. Only for you providing a new link, i would never have found it... maybe you could update some old posts with fresh links, and that will make some old-timers like myself, feel young again trying this stuff lol.
but andyways, thank you again so much for your help. theres not many out there in this day and age, that would have bothered... so i salute you sir!
kind regards
stay safe
ps. my daughter says Im the best dad in the world again ... I told her the wizard on the tinterweb fixed it using some of Gandalf's magic....
So I got my shiny new device today, and it feels really nice. I worked with the launcher it came with, tried another one, and realized that yep, I gotta root and install a new rom. The notification bar just annoys me too much as I'm used to having quick actions and other things in there.
So, I followed a few guides, and finally worked my way through to having my command line find my device and can successfully reboot it into fastboot mode.
At that point, I realized that I can boot into recoveries without flashing them first (essentially trying them out to see how it works). However, I tried the 4 official version on the twrp site, and one made by a user here (cuoco92). They all successfully boot into the recover using the command "fastboot boot nameOfFileHere.img". At this point, every single recovery failed to respond to touch and volume presses. I can press the power button to turn off the screen, and pressing power to turn the screen back on shows a locked recovery screen, but I can't slide the screen to unlock it.
This is quite concerning to me. I don't want to flash a recovery for good if it's not working properly. I hope this makes sense. Or, is it normal to just flash a recovery and hope for the best? Do recoveries work with just booting to them without being flashed?
I haven't rooted and/or flashed any devices in about 5+ years, the last being a phone from virgin mobile that supported sd cards. When installing new roms, do we store the zips in the root of the phone, or does this get cleared out/deleted when doing the wipe cache/dalvik/etc?
Personally, I just want to make sure I don't rush into this, as there seems to be fragmented results when searching around for twrp not working with touch. I know these things have been asked before plenty of times, and I hope I don't come across as another "ugh, this again" post. I really appreciate any responses!
you never did, then just leave it as it is...its a nice phone eui is not bad... take it easy
Try booting the official TWRP recovery. As far as I remember, some of the versions tweaked by Cuoco92 had issues with the touch panel.
Anyway, EUI is not that bad, as your were told. While I used it, I also used an app called "Notification Toggles", which lets you get Quick Settings like toggles on notification area. It's nice and easy to set up, and the results, although not the same as having the AOSP toggles, is quite nice and convenient.
BTW, which stock ROM did your phone come with?
I have tried 4 different official twrp files (all from the twrp site). My phone is an x820 6gb/64gb and came with EUI version: 5.8.019S (Stable). EUI is nice, very fast and sleek. Maybe I do just need to get used to it, or maybe it's just me itching to try out the different options available since I finally have a phone is not carrier/manufacturer locked down.
Heyyo, hmm that's very odd indeed! I wonder if maybe by temporary booting Cuoco92's TWRP it could have messed up your recovery hmm...
I'd recommend first to flash the stock recovery over your current one and then reboot to fastboot and then flash TWRP. Hopefully this will erase any problem that Cuoco92's recovery could have caused.
This was the guide I followed and it worked flawlessly for me
https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151
I never actually flashed any of them. I have only ever just tried booting into them using "fastboot boot recovery name.img". I have not used the fastboot flash command for any of the files.
The only thing I can do after booting the recoveries is hold the power button and eventually the phone will boot up normally.
Remember that I just wanted to boot them to make sure they worked before flashing them. I'll be checking out the guide you linked shortly.
Haven't flashed any of them eh? Hmm should work just fine then... Have you tried TWRP 3.0.2-0 ? I know that one was built with Marshmallow sources
As for which ROM to try? I'd recommend OmniROM if you want to try a custom Nougat ROM.
If you want to see why I think so? I made a massive post or two about it here heh
https://forum.xda-developers.com/le-max-2/help/party-rom-best-help-t3691165/
Thank you so much for the guide you linked. I'm making a little bit of progress here.
I found a twrp recover by cuocos92 that is labeled V3 (apparently from what I read in other threads, V3 seems to be good with the 6gb/64gb models). This recovery allows the use of the touchscreen . Remember that I am only using the "fastboot boot" command so no flashing yet.
Now that I am in a working recovery, I kept hitting "keep read only" so that the stock recovery would not be replaced. I set out to make a backup. Well that kept failing with attempts of trying to mount /system and such. Off to more reading, found out that using the Wipe->Swipe to Factory Reset inside twrp fixes this. I did that. I successfully created a backup.
Now to try to flash the SuperSU zip I have, which was previously copied to the root of the phone from my pc. Can't see any zip files on the internal storage. Reboot the phone (forgetting that it takes a long time after the wipe). Copy the backup to my pc. Copy the SuperSU back to root of phone. Restart the process of adb and fastboot -> back into the cuocos92 V3 recovery. Still no zip to be found. Couldn't mount system again...
Did some more reading. I just attempted the Wipe->Format data. I am currently rebooting back into the phone to set it up again. Apparently, a lot of people say this needs to be done if we did not reboot after unlocking the bootloader. Since twrp has been asking for a password each time I entered it, the format data is supposed to solve this.
I'll edit/post again with more steps or results.
I apologize for the second post here, but this seems more than should go into an appended edit:
After doing the Wipe->Format data, it's advised to reboot back into the recovery. Without flashing the twrp cuocos92 recovery, my thoughts are it would just be back into the stock recovery. At least the twrp version works, so I have no problems with flashing it. And then I'll have to Wipe->Format data again, reboot back into recovery, and then I can flash my SuperSU zip. But how can I get my SuperSU zip on the phone?
Doesn't Wipe->Format data remove it? Everytime I reboot my phone after that the SuperSU on the root of the phone is gone. I can't seem to mount to my pc from the recovery either, clicking the usb storage just unchecks itself right away, and clicking the enable MTP doesn't seem to do anything. So, even if I flash the recovery, Wipe-Format data again, reboot back into the recovery, I still don't see a way of getting the SuperSU zip onto the phone anyways.
I know it probably sounds like I'm whining by now about how things aren't as easy as it seems. I'm trying to be descriptive in what I am doing and what's happening.
Hmm by chance are you using Windows 10? At least I've noticed for me it fails to properly mount the correct drivers for ADB and MTP for TWRP. I'd recommend checking device manager.
If I remember correctly here's what mine looked like at first
https://photos.app.goo.gl/wXaqbi3OeH3bKEf62
Select MTP > update driver > browse my computer > let me pick > (standard MTP Device) > MTP USB Device
Sorry I'm not in front of my PC but I'm sure it's something like that to solve it
If that doesn't work? You can always use...
Code:
adb push ROM.zip /sdcard
Which will copy the zip file to the root of your data storage (on the Le Max 2 much like the One Plus 3 they use /Sdcard as a shortcut since we don't have external Sdcard hardware).
As for system read only? Swipe to allow modifications. Can't flash a ROM properly if the system is read only eh? Hence the failed to mount system.
It's really just there as a disclaimer to cover their ass in case people use TWRP improperly and brick their device. Following green man gaming's guide is safe as I've used it plus many other people as you'll see in his replies
I'd also recommend following the guide and flashing TWRP to your recovery. I only did boot recovery image for backup and then booted to EUI and copied that backup to my PC.
Format data is handy to get rid of encryption and also give you full access to your storage capacity because when I didn't before I didn't get 54.43GB of data storage only something like 40GB.
Tbh I haven't used any custom EUI ROMs but if you're fighting with TWRP? I know Cuoco92's eui has a fastboot installable version
Hope this helps
Well thank you so much for the information. I am running windows 10, but never saw mtp under portable devices, only the phone name Le Max 2. That's ok, as I booted (still not flashed) into recovery and this time I swiped to allow modifications. I still couldn't mount /system but I was able to use the adb push command and the SuperSU file appeared inside the /sdcard directory when looking under Install inside twrp. I swiped to flash the zip, then hit reboot system. Looking in the SuperSU app, I noticed that the setting "Install SuperSU into /system" is greyed out. Well, at least I think it worked.
At this point in time, since things appear to be working, I'll be flashing the recovery and installing OmniRom (it was either this or Resurrection Remix). I think if the play store just works on OmniRom like people mention, it'll be worth it.
So, my steps will be to:
adb -> fastboot -> fastboot flash recovery fileName.img
recovery -> wipe -> factory wipe (using factory to get rid of system encryption) -> reboot back into recovery
recovery -> wipe -> dalvik/cache (do i still need to do this after factory wipe?)
adb -> adb push romFileName.zip /sdcard
adb -> adb push gapps.zip /sdcard
recovery -> install -> /sdcard -> romFileName.zip
recover -> install -> /sdcard -> gapps.zip
At any point do I need to flash SuperSU again? I guess I should after flashing the rom/gapps because, afterall, SuperSU is an app.
Once again, thank you so much for all the information that you have already provided!
Heyyo, it's always recommended to do a full wipe when installing a different ROM so you should format data, wipe system, data, dalvik and cache and then install the ROM of choice with Gapps of choice
Wiping system is OK when flashing a ROM as it'll write into system.. plus there's always the risk of instability if system is not wiped if a Gremlin setting is left over from previous ROM
I'd recommend using Magisk v14.3 over SuperSU as SuperSU doesn't have the same functionality as Magisk for passing SafetyNet...
Plus Magisk is full open source software (FOSS) where as SuperSU is closed source so gotta love that open source (this part is more personal preference since Android is built upon open source and people working together).
Plus there's really cool Magisk modules you can do like ART Optimizer and so fourth if you check the XDA forum section for it
Also, you're welcome! We all had our start on XDA at different points and passing on the knowledge I find is just as important as the ROMs we love
Don't use SuperSU. Magisk is the way to go for rooting nowadays. Easy, systemless, updated frequently to pass safetynet. It's a no brainer.
Bootloop of Death (BLOD) Workaround AnyKernel3 zip for Nexus 6P
osm0sis said:
Guys.. bad news.. my Nexus 5X just got hit with the BLOD.
Good news for everyone is I spent a bit of time tonight to first patch TWRP 3.2.1-0-FBE (File-Based Encryption support) image to be 4core, then made an AnyKernel2 zip which will patch the existing boot and recovery partitions on-device to add all the 4core fixes from @XCnathan32.
Should work over any ROM, any custom kernel, recovery, etc., can be added in queue after ROM, root zip + custom kernel to patch it from TWRP or FlashFire (so good for OTAs), and simplifies the initial process greatly since you can now fastboot boot any 4core recovery.img and then adb sideload my AK3 zip to fix the likely newer recovery you already had on your device.
Click to expand...
Click to collapse
Original thread posts: Nexus 5X, Nexus 6P
Now updated to an AnyKernel3 zip to support the SAR (system-as-root) and 2SI (2 stage init) ROMs that have popped up for Pie and Android 10+!
General Information
If you've found this thread then I'm sure you probably already know what the Bootloop of Death is - separation of the performance (perf) CPU cores - and that the only way to recover from it is to unlock your bootloader and patch to disable the faulty cluster. If you have not enabled unlocking your bootloader yet, the known methods to get it to boot long enough so you can go to System, then Developer Options and toggle "OEM unlocking" are:
super cooling the device in a freezer in a ziplock bag to keep out moisture,
super heating around the camera, and
letting the battery run all the way down before trying to boot.
For further details on these methods check out the original threads by @XCnathan32, linked in the "Thanks" section.
Some important notes before going any further:
Freezing at the Google logo likely points to it being perf cluster separation, but this could also be caused by other components separating.
Freezing at the boot animation suggests ROM/ROM data problem or could also potentially be a BLOD with other components now beginning to separate and that's what people have reported when the 4core mods suddenly stop working with no configuration changes - if you've tried the default boot.img for your ROM, patched with the BLOD AK3 and it still doesn't work, sorry but your device is a brick.
If no 4core recovery boots for you then you definitely have more components than just the performance cores separated, sorry but your device is a brick.
I haven't seen anyone say their devices only worked using a "1core" modification who had tried a proper 4core patched setup; 4core makes sense because it's the separate perf cores cluster becoming unsoldered, but if the 4 low power cores cluster also starts to come unsoldered logically not even a single core would work.. I think that's where the "Green Screen Of Death" comes into it.
DemiGod = Green Screen Of Death; unfortunately this (more components separating given more time - maybe the flash memory chip?) is why many call the 4core workaround only temporary.. there's not much that can be done after that from what I've read.
EX Kernel does not support FBE on these devices because the EX zip patches the fstab forcefdeorfbe flag to encryptable.
Android 10 does not appear to support FBE on these devices but the 4core FBE TWRP build can be used to BLOD patch the latest TWRP (see instructions in next post).
On Oreo, I was personally on stock ROM still, FBE enabled, rooted with SuperSU v2.82 SR5 + suhide and the latest Franco Kernel on my 5X. Then I bumped up the min freq on the low perf cores and it's working great - totally fine for general use, just anything creating a bit of heat like games maxing the low power cores for awhile, or charging, will make it pretty painfully laggy and risk further solder deterioration.
Even though SuperSU development is ostensibly dead, I still strongly recommend it on BLOD-affected devices using stock ROM for reasons I'll explain below.
My development work on my many projects comes out of my free time, so if you enjoy this project or anything else I've done on xda, please consider sponsoring my ongoing work using my GitHub Sponsors profile. For a one-time donation you can hit the donate link from my profile. Thank you for your support!
Step-By-Step Installation Instructions
Any quoted commands should be entered without quotes
1) Download and unzip platform-tools for your PC from https://developer.android.com/studio/releases/platform-tools.html
2) Navigate to https://androidfilehost.com/?w=files&flid=312881 (also mirrored below) and download N5X-6P_BLOD_Workaround_Injector_Addon-AK3-signed.zip to your platform-tools folder as well as
2a) twrp-3.2.1-0-fbe-4core-bullhead.img (Nexus 5X), or2b) twrp-3.2.1-0-fbe-4core-angler.img (Nexus 6P)3) Hold Shift + right-click on your platform-tools folder and
3a) Open a command window here (Windows <10), or3b) Open a PowerShell window here, then enter "cmd" at the Windows PowerShell prompt (Windows 10+)4) Reboot your phone to bootloader and connect it to your PC with a USB cable
5) Enter "fastboot flash recovery twrp-3.2.1-0-fbe-4core-angler.img" into the cmd prompt
6) Reboot your phone to recovery and tap Advanced, then ADB Sideload
7) Enter "adb sideload N5X-6P_BLOD_Workaround_Injector_Addon-AK3-signed.zip" into the cmd prompt
8) Reboot and cross your fingers that it works
For information how to seamlessly update to stock and custom ROM OTAs, see the following post
Source Code: https://github.com/osm0sis/N5X-6P-BLOD-Workaround-Injector
Status: No Longer Updated
Thanks:
- @XCnathan32 for researching and developing the 4core workarounds for both the Nexus 5X and Nexus 6P
- chetgurevitch (GitHub) for the original FBE supporting TWRP builds
- @Aukaminator for the original step-by-step write-up
Update Flashing Instructions
Keep N5X-6P_BLOD_Workaround_Injector_Addon-AK3-signed.zip on your device sdcard, henceforth referred to as BLOD AK3 zip
The correct manual order for a clean flash is: ROM -> root -> custom kernel -> BLOD AK3
Always flash the BLOD AK3 zip last!
Reflashing the BLOD AK3 zip will likely be required after anything that could modify the boot.img or recovery.img, including (but not limited to): ROM updates, custom kernel updates, custom recovery updates.
ROMs:
On custom ROMs with built-in Flash After Update (i.e. OmniROM-based), place your root (if using SuperSU), custom kernel and BLOD AK3 zip in /sdcard/OpenDelta/FlashAfterUpdate/ ensuring the BLOD AK3 is last in the directory listing so that they will be flashed after each update.
On custom ROMs that do not have built-in Flash After Update (i.e. LineageOS-based), you may add my FlashAfterUpdate addon.d script to /system/addon.d/ and then place your root (if using SuperSU), custom kernel and BLOD AK3 zip in /sdcard/FlashAfterUpdate/ ensuring the BLOD AK3 is last for the same effect: flashed after every OTA.
On stock ROM rooted with SuperSU (SuperSU v2.82-SR5 recommended) instead of tapping "Reboot & Install" once the OTA is downloaded you should use @Chainfire's excellent FlashFire app to queue the OTA from /data/ota_package/update_s.zip then queue the SuperSU zip, custom kernel and BLOD AK3 zip, ensuring the BLOD AK3 is last. This is how I have mine set up, since this is by far the most seamless. Be sure to disable EverRoot since SuperSU v2.82-SR5 is newer than the SuperSU included in FlashFire.
On stock ROM rooted with Magisk you must uninstall Magisk from within Magisk Manager to restore your stock boot.img, reboot the ROM to restore your stock recovery partition, tap "Reboot & Install" once the OTA is downloaded, then go through the steps above to flash the 4core TWRP and BLOD AK3 zip again. I definitely recommend SuperSU on this device to avoid the hassle of unrooting and/or messing with factory images.
Kernels:
Custom kernels can be flashed from an app like Franco Kernel Manager & Updater, which can be set to flash without reboot for Franco Kernel updates, or "Flash only" can be chosen in the manual flasher. The FK app supports all types of AnyKernel3 zip so the BLOD AK3 zip may then be flashed after the custom kernel zip to repatch the new kernel's ramdisk.
For other kernel managers that don't support AK3 zips, simply reboot to recovery and flash the BLOD AK3 zip from there to repatch before attempting to boot the ROM again. Also see above under "stock ROM rooted with SuperSU", since FlashFire also works perfectly for this use-case, queuing the custom kernel zip and then the BLOD AK3 zip, with FlashFire's EverRoot option disabled since the device is already rooted.
Recoveries:
Download the updated custom recovery .img and, without flashing it, reboot to recovery, use TWRP's flash image feature to flash the new recovery.img, then without rebooting immediately flash the BLOD AK3 zip to patch it. You can then dump/backup the recovery partition if you want it as a recovery.img. Custom recovery updates can also be done from FlashFire, queuing the BLOD AK3 zip afterward, but the "Preserve recovery" feature must be disabled.
If you prefer to stay on stock recovery for some reason, you can still use TWRP to do the above without flashing TWRP to the device by using "fastboot boot twrp-3.2.1-0-fbe-4core-angler.img".
My development work on my many projects comes out of my free time, so if you enjoy this project or anything else I've done on xda, please consider sponsoring my ongoing work using my GitHub Sponsors profile. For a one-time donation you can hit the donate link from my profile. Thank you for your support!
Changelog
2018-01-15 - Original post in other BLOD threads.
2018-07-21 - Update AK2 Core+Backend files to latest, add searching of all init.*.rc files for problematic cpuset commands which were popularized by Franco Kernel and are now used by multiple custom kernels. (6758 downloads)
2019-10-30 - Update to AnyKernel3, add support for SAR and 2SI Treblized ROMs. (1720 downloads)
2020-01-16 - Update AK3 Core+Backend files to latest to fix AVBv1 signing in recovery on Android 10, update boot_signer-dexed.jar. (570 downloads)
2020-02-17 - Update AK3 Core+Backend files to latest to fix SAR mount support in fragmented TWRP and Lineage 16+17 Recovery. (1412 downloads)
2020-05-25 - Update AK3 Core+Backend files to latest to improve SAR mount support in Lineage 17 Recovery and AVBv1 signing. (1789 downloads)
2021-07-21 - Update AK3 Core+Backend files to latest to support Lineage 18.1 recovery and Android 11 ROMs.
Good luck and enjoy!
Glad to see this exclusive thread... just came here to report that I've been using your fix since Jan this year ( https://forum.xda-developers.com/ne...-6p-bootloop-death-blod-t3640279/post75220708 ) and yeah my phone's still alive and running fine. Kudos to your work... Great job you did there... saving hundreds of bucks... Really appreciated!
Thanks again.
Hi osmosis,
I have done everything you said and I got stuck in step 7, when I enter "adb sideload N5X-6P_BLOD_Workaround_Injector_Addon-AK2-signed.zip", the return message is:
adb: sideload connection failed: closed
adb: trying pre-Kitkat sideload method...
adb: pre-Kitkat sideload connection failed: closed
I tried swiping where it says "Swipe to Start Sideload" and then doing step 7, but when I swipe my computer stops recognizing my device.
Thank you
SH15 said:
Hi osmosis,
I have done everything you said and I got stuck in step 7, when I enter "adb sideload N5X-6P_BLOD_Workaround_Injector_Addon-AK2-signed.zip", the return message is:
adb: sideload connection failed: closed
adb: trying pre-Kitkat sideload method...
adb: pre-Kitkat sideload connection failed: closed
I tried swiping where it says "Swipe to Start Sideload" and then doing step 7, but when I swipe my computer stops recognizing my device.
Thank you
Click to expand...
Click to collapse
You need to let your computer install drivers for adb sideload. If your computer is having trouble with that for some reason and the recovery otherwise works then just adb push the zip to /sdcard and flash it from on the device instead of sideloading. :good:
osm0sis said:
You need to let your computer install drivers for adb sideload. If your computer is having trouble with that for some reason and the recovery otherwise works then just adb push the zip to /sdcard and flash it from on the device instead of sideloading. :good:
Click to expand...
Click to collapse
Thank you for answering. I had to adb push the file to /sdcard and then I flashed it using TWRP, however even after installing the file the phone is still stuck on the Google logo screen when booting up. I don't know what to do.
Thank you
SH15 said:
Thank you for answering. I had to adb push the file to /sdcard and then I flashed it using TWRP, however even after installing the file the phone is still stuck on the Google logo screen when booting up. I don't know what to do.
Thank you
Click to expand...
Click to collapse
That's weird. The fact that the recovery worked suggests the 4core fix works for you. Maybe flash the lastest factory image then the BLOD AK2 zip.
Can this be flashed on top of the Oreo img from the previous thread? Is this one for Oreo?
I've applied the previous Oreo one and my phone's past the Google logo loop and is now in the loading animation for Lineage OS.
FlameSting said:
Can this be flashed on top of the Oreo img from the previous thread? Is this one for Oreo?
I've applied the previous Oreo one and my phone's past the Google logo loop and is now in the loading animation for Lineage OS.
Click to expand...
Click to collapse
Please read the OP. It works over any ROM, any custom kernel, any recovery.
osm0sis said:
That's weird. The fact that the recovery worked suggests the 4core fix works for you. Maybe flash the lastest factory image then the BLOD AK2 zip.
Click to expand...
Click to collapse
Thank you very much! I flashed the newest factory image for Oreo and then re-flashed the BLOD AK2 zip and it worked. Thank you for your help! :good:
Idk if I'm in the right place.
I recently replaced my battery (2nd time this week, first one was bad) and everything was working fine. Then my phone started randomly rebooting. Googled it and apparently it's one of the first signs of BLOD. Followed this and the phone stopped shutting down randomly. Now the phone only works if plugged into a power source. Idk if I did something wrong or the battery is trash (even though it was working fine all day)
I'd appreciate an guidance [emoji24]
Sent from my [device_name] using XDA-Developers Legacy app
This saved my day! Thanks everyone! Got my 6P booted up again... and it's not even rooted
I want just only to thanks @osm0sis and it's genial solution!
Thanlks i recover my phone and saved a lot of money.
I understand it could be a temporary solution but thanks!!!
gabriele
After I flashed twrp and try to go to Recovery there is a message "Your device software cannot be checked for corruption. Please lock the bootloader." And after that it goes back to bootlloop. Any idea what to do next? Thanks
godd said:
After I flashed twrp and try to go to Recovery there is a message "Your device software cannot be checked for corruption. Please lock the bootloader." And after that it goes back to bootlloop. Any idea what to do next? Thanks
Click to expand...
Click to collapse
That just means you unlocked your device. If no 4core recovery works then unfortunately your device can't be saved.
I had my phone hang on the google logo a couple times, but rebooting it fixed it. Is this an early sign of this problem? Just replaced battery and so far it seems fine.
osm0sis said:
That just means you unlocked your device. If no 4core recovery works then unfortunately your device can't be saved.
Click to expand...
Click to collapse
I am in this same boat... RIP N6P, this is my 2nd N6P Google replaced the first one due to the BLOD and now the replacement is dead.
Thanks for all the efforts and help.
osm0sis said:
That just means you unlocked your device. If no 4core recovery works then unfortunately your device can't be saved.
Click to expand...
Click to collapse
It seems the basketbuild site is down. Any chance you could throw the modded twrp for oreo and the 4core fix up here?
osm0sis said:
That just means you unlocked your device. If no 4core recovery works then unfortunately your device can't be saved.
Click to expand...
Click to collapse
Same as the guy above. Sites down need mirrors or something?
jbjcurly said:
It seems the basketbuild site is down. Any chance you could throw the modded twrp for oreo and the 4core fix up here?
Click to expand...
Click to collapse
CavyS said:
Same as the guy above. Sites down need mirrors or something?
Click to expand...
Click to collapse
Mirrored in the OP. Thanks!
Edit: And BasketBuild is also back! :good:
Code:
/*
* Your warranty will be VOID after installing a custom ROM.
*
* Get notified yourself that 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.
*/
# Team Win Recovery Project
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom "ROM" like OmniROM
You can find the source code for TWRP at github.com/teamwin/android_bootable_recovery/
# Features
Flashing a ROM
Factory reset
Erasing the partitions including system, data, cache, internal storage
Backup and restore
Supports F2FS formatting
USB ADB/MTP/OTG
# Downloads
Galaxy Tab S3 LTE (gts3llte, SM-T825)
Galaxy Tab S3 WiFi (gts3lwifi, SM-T820)
# How to install
You have to unlock your bootloader in advance. Check "OEM Unlock" in the device settings.
## Via Odin/Heimdall
Download "twrp-*-gts3l*.img.tar"from the given link.
Check the file name to yours, gts3llte or gts3lwifi.
Enter the download mode by pressing the volume-down + home + power buttons at the same time.
Open Odin or Heimdall and set the AP slot as the downloaded recovery file.
Flash.
Reboot to the recovery by pressing the volume-up + home + power buttons at the same time.
Done.
## Via rooted ADB
This is for those who can get the rooted ADB shell, by the custom ROM or previous TWRP, etc.
Download "twrp-*-gts3l*.img"from the given link.
Check the file name to yours, gts3llte or gts3lwifi.
In this guide, assume that the file is named "twrp.img".
Copy the recovery file into somewhere the device can access.
Enter the ADB shell with rooted mode.
In the shell, go to the directory that the recovery file copied.
Enter the command, "dd if=twrp.img of=/dev/block/bootdevice/by-name/recovery"
Reboot to the recovery by pressing the volume-up + home + power buttons at the same time.
Done.
# Notes
It may slow until formatting data partition when you are from the stock ROM. It tries to mount data partition using ext4 filesystem but it fails repeatedly.
# Sources
Device Tree
gts3llte: https://github.com/awesometic/android_device_samsung_gts3llte-twrp
gts3lwifi: https://github.com/awesometic/android_device_samsung_gts3lwifi-twrp
Kernel: https://github.com/awesometic/android_kernel_samsung_msm8996
# Buy me a coffee
If you like my efforts or would like to support me, please don't hesitate to buy me a cup of coffee.
https://www.paypal.com/paypalme/awesometic
# Credits / Special thanks to
Android Open Source Project
TeamWin Team
LineageOS Team
OmniROM Team
TWRP Minimal Manifests
@Valera1978 for his amazing previous work including his MSM8996 kernel
@ashyx for his amazing previous work on his TWRP
@EonOfBlack for confirming its working on SM-T820
## Changelogs
2021. 11. 30
Updated TWRP version to 3.6.0
Started to use my custom kernel
Set the kernel to "awesometic-kernel-v0.3"
Merged CAF tag LA.UM.7.6.r1-07800-89xx.0
Now it supports F2FS file system
Improved performance
And some more but not related to the recovery
2021. 7. 9
Initial release
reserved
Nice to see TWRP for the sm820...
Cannot really test since my tabs3 is needed as a daily, but that might just change soon...
Flashed with an old TWRP. It works. Can't test with stock rom either... Strange bug with the shell:
Code:
libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xfffffffffffffff0 in tid 635 (ls), pid 635 (ls) Segmentation fault
It happens only when trying to access /external_sd/ (ls, find, etc.) no problem at / or /sdcard/ /external_sd/ is accessible with the internal file browser. Portrait orientation? Why not.
I have flashed with tweaked ROM https://forum.xda-developers.com/t/rom-sm-t820-tweaked-rom-sm-t820-tweaked.3659433/ via adb shell. It work right
Awesometic said:
Code:
/*
* Your warranty will be VOID after installing a custom ROM.
*
* Get notified yourself that 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.
*/
# Team Win Recovery Project
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom "ROM" like OmniROM
You can find the source code for TWRP at github.com/teamwin/android_bootable_recovery/
# Features
Flashing a ROM
Factory reset
Erasing the partitions including system, data, cache, internal storage
USB ADB/MTP/OTG
## Prepared but not tested
Backup and restore
Hardware decryption
# Downloads
Galaxy Tab S3 LTE (gts3llte, SM-T825)
Galaxy Tab S3 WiFi (gts3lwifi, SM-T820)
# How to install
You have to unlock your bootloader in advance. Check "OEM Unlock" in the device settings.
## Via Odin/Heimdall
Download "twrp-3.5.2_9-0-gts3l*.img.tar"from the given link.
Check the file name to yours, gts3llte or gts3lwifi.
Enter the download mode by pressing the volume-down + home + power buttons at the same time.
Open Odin or Heimdall and set the AP slot as the downloaded recovery file.
Flash.
Reboot to the recovery by pressing the volume-up + home + power buttons at the same time.
Done.
## Via rooted ADB
This is for those who can get the rooted ADB shell, by the custom ROM or previous TWRP, etc.
Download "twrp-3.5.2_9-0-gts3l*.img"from the given link.
Check the file name to yours, gts3llte or gts3lwifi.
In this guide, assume that the file is named "twrp.img".
Copy the recovery file into somewhere the device can access.
Enter the ADB shell with rooted mode.
In the shell, go to the directory that the recovery file copied.
Enter the command, "dd if=twrp.img of=/dev/block/bootdevice/by-name/recovery"
Reboot to the recovery by pressing the volume-up + home + power buttons at the same time.
Done.
# Notes [2021. 7. 9]
I started roughly, so the recovery has some files for dealing with hardware encrypted file system, but I couldn't test yet because I need the stock ROM to test but I should keep the workflow with my LineageOS. If anyone can test this then please let me know it works or not.
# Sources
Device Tree
gts3llte: https://github.com/awesometic/android_device_samsung_gts3llte-twrp
gts3lwifi: https://github.com/awesometic/android_device_samsung_gts3lwifi-twrp
Kernel: https://github.com/awesometic/android_kernel_samsung_msm8996
# Buy me a coffee
If you like my efforts or would like to support me, please don't hesitate to buy me a cup of coffee.
https://www.paypal.com/paypalme/awesometic
# Credits / Special thanks to
Android Open Source Project
TeamWin Team
LineageOS Team
OmniROM Team
TWRP Minimal Manifests
@Valera1978 for his amazing previous work including his MSM8996 kernel
@ashyx for his amazing previous work on his TWRP
@EonOfBlack for confirming its working on SM-T820
Click to expand...
Click to collapse
I would like to help to add dualboot for sm-t820, is there some project in this direction ?
Thanks, Good job!!
samsuffit said:
Flashed with an old TWRP. It works. Can't test with stock rom either... Strange bug with the shell:
Code:
libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xfffffffffffffff0 in tid 635 (ls), pid 635 (ls) Segmentation fault
It happens only when trying to access /external_sd/ (ls, find, etc.) no problem at / or /sdcard/ /external_sd/ is accessible with the internal file browser. Portrait orientation? Why not.
Click to expand...
Click to collapse
Actually, on my side, I have no issue when accessing the SD card, /external_sd. I'm usually putting a file into that directory through ADB. Sorry, don't know why that happens..
If there's no problem when you use another TWRP, can you tell me which one?
XolYnrac said:
I would like to help to add dualboot for sm-t820, is there some project in this direction ?
Thanks, Good job!!
Click to expand...
Click to collapse
There's no plan for something related to the dual-boot.
Awesometic said:
Actually, on my side, I have no issue when accessing the SD card, /external_sd. I'm usually putting a file into that directory through ADB. Sorry, don't know why that happens..
If there's no problem when you use another TWRP, can you tell me which one?
Click to expand...
Click to collapse
I tried again, before I messed it up https://forum.xda-developers.com/t/rom-sm-t820-tweaked-rom-sm-t820-tweaked.3659433/post-85316477 and had the same error. Before I was using TWRP 3.2.1-1 and I never had any error with adb shell. The error wasn't with adb push, but adb shell.
I'm a bit tired of this damned tablet, I don't know, it was a bit expensive for a Digital Photo Frame.
---
Interesting. So, I succesfully "unbrick" this doomed tablet with the method of the seven days, then I flashed your TWRP with Heimdall, with the option '--no-reboot' and pressed Home/Vol+/Power to reboot immediately in recovery. The splash screen appear and nothing. I flashed TWRP 3.2.1-1 wich can be find in this forum, reboot in recovery, I had this new red message "RECOVERY IS NOT SEANANDROID ENFORCED" and... it worked. Format Data, wipe everything, flash Lineage, Magisk, as usual, reboot in recovery. Inside TWRP 3.2.1-1 I flashed your TWRP 3.5.2_9-0 and... it worked!
From Stock Rom:
- Flash with Heimdall/Odin -> NOT OK
- Flash with TWRP -> OK
Still, I have the error.
Code:
[email protected] $ adb shell
gts3lwifi:/ # ls /external_sd/
libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xfffffffffffffff0 in tid 4616 (ls), pid 4616 (ls)
Segmentation fault
samsuffit said:
I tried again, before I messed it up https://forum.xda-developers.com/t/rom-sm-t820-tweaked-rom-sm-t820-tweaked.3659433/post-85316477 and had the same error. Before I was using TWRP 3.2.1-1 and I never had any error with adb shell. The error wasn't with adb push, but adb shell.
I'm a bit tired of this damned tablet, I don't know, it was a bit expensive for a Digital Photo Frame.
---
Interesting. So, I succesfully "unbrick" this doomed tablet with the method of the seven days, then I flashed your TWRP with Heimdall, with the option '--no-reboot' and pressed Home/Vol+/Power to reboot immediately in recovery. The splash screen appear and nothing. I flashed TWRP 3.2.1-1 wich can be find in this forum, reboot in recovery, I had this new red message "RECOVERY IS NOT SEANANDROID ENFORCED" and... it worked. Format Data, wipe everything, flash Lineage, Magisk, as usual, reboot in recovery. Inside TWRP 3.2.1-1 I flashed your TWRP 3.5.2_9-0 and... it worked!
From Stock Rom:
- Flash with Heimdall/Odin -> NOT OK
- Flash with TWRP -> OK
Still, I have the error.
Code:
[email protected] $ adb shell
gts3lwifi:/ # ls /external_sd/
libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xfffffffffffffff0 in tid 4616 (ls), pid 4616 (ls)
Segmentation fault
Click to expand...
Click to collapse
I haven't faced that issue so far. Actually I use only one kind of SD card so probably I couldn't find that issue.
Could you attach the logcat when the error occurs?
Awesometic said:
I haven't faced that issue so far. Actually I use only one kind of SD card so probably I couldn't find that issue.
Could you attach the logcat when the error occurs?
Click to expand...
Click to collapse
Unfortunately there isn't logcat in recovery and the recovery.log dump doesn't show anything. /external_sd is mounted correctly, that's why I can access it with the internal file browser or choose it to pick up a file to flash. kernel.log (dmesg) doesn't show anything either. The problem is with the shell, busybox. I can't help you more, I'll think to an other way to find where's the error come from.
Reading the logs, I've found where the date and time are, for my other problem in the other thread.
Code:
I:Created '/persist' folder.
I:TWFunc::Fixup_Time: Pre-fix date and time: 2017-01-01--09-56-37
I:TWFunc::Fixup_Time: Setting time offset from file /sys/class/rtc/rtc0/since_epoch
I:TWFunc::Fixup_Time: will attempt to use the ats files now.
I:TWFunc::Fixup_Time: Setting time offset from file /persist/time/ats_2, offset 1592833667239
I:TWFunc::Fixup_Time: Date and time corrected: 2020-06-22--23-44-25
samsuffit said:
Unfortunately there isn't logcat in recovery and the recovery.log dump doesn't show anything. /external_sd is mounted correctly, that's why I can access it with the internal file browser or choose it to pick up a file to flash. kernel.log (dmesg) doesn't show anything either. The problem is with the shell, busybox. I can't help you more, I'll think to an other way to find where's the error come from.
Reading the logs, I've found where the date and time are, for my other problem in the other thread.
Code:
I:Created '/persist' folder.
I:TWFunc::Fixup_Time: Pre-fix date and time: 2017-01-01--09-56-37
I:TWFunc::Fixup_Time: Setting time offset from file /sys/class/rtc/rtc0/since_epoch
I:TWFunc::Fixup_Time: will attempt to use the ats files now.
I:TWFunc::Fixup_Time: Setting time offset from file /persist/time/ats_2, offset 1592833667239
I:TWFunc::Fixup_Time: Date and time corrected: 2020-06-22--23-44-25
Click to expand...
Click to collapse
Oh okay, thank you for the report anyway.
And the date/time issue, I didn't know that the time data is stored into the /persist directory.
twrp seems very stable, however incredibly slow to start. it takes 30 to 40 seconds ro get the twrp boot screen for me (t820) other thsn that it works well, I also tested this out by not flashing the kg/rmm state patch, as well the the encryption disabler and was able to boot back to this recovery without my data getting absolutely wiped. before with asyx twrp, twrp would delete all system files and data if those two zip files werent flashed, especially when updating the rom or dirty flashing. so far so good keep it up.
LedgendaryEpics said:
twrp seems very stable, however incredibly slow to start. it takes 30 to 40 seconds ro get the twrp boot screen for me (t820) other thsn that it works well, I also tested this out by not flashing the kg/rmm state patch, as well the the encryption disabler and was able to boot back to this recovery without my data getting absolutely wiped. before with asyx twrp, twrp would delete all system files and data if those two zip files werent flashed, especially when updating the rom or dirty flashing. so far so good keep it up.
Click to expand...
Click to collapse
Yeah I'm using my TWRP and I agree that there's a performance issue. Will look into this problem.
Awesometic said:
Yeah I'm using my TWRP and I agree that there's a performance issue. Will look into this problem.
Click to expand...
Click to collapse
I'd love to see camera first, cause that's what I need much more, than a fast booting TWRP.
That I'm using only once a month or less and if it needs 40"' or 5' to start doesn't bother me.
I have 2 questions. Do I need to install the patch, Tab3 oreo forced encryption disabler??
Second, do i need to uncheck auto reboot after install this twrp version?
hinghing1113 said:
I have 2 questions. Do I need to install the patch, Tab3 oreo forced encryption disabler??
Second, do i need to uncheck auto reboot after install this twrp version?
Click to expand...
Click to collapse
1. Well I never installed so it seems not necessary
2. If you mean Odin flashing the TWRP, surely.
Otherwise the old stock recovery gets revived when auto rebooting and not into TWRP directly.
Does this require root?
I can successfully get into TWRP and format Data but rebooting makes my T820 act as it were factory reset (boots up to setup wizard) and replaces TWRP with stock recovery. I'm not selecting read only mode when first opening TWRP. I'm not latest stock firmware
fulleden said:
Does this require root?
I can successfully get into TWRP and format Data but rebooting makes my T820 act as it were factory reset (boots up to setup wizard) and replaces TWRP with stock recovery. I'm not selecting read only mode when first opening TWRP. I'm not latest stock firmware
Click to expand...
Click to collapse
Hello.
Strange. Once you have installed TWRP recovery on your tablet then it should not be turned into the stock recovery again automatically. I believe.
Have you checked OEM unlock option in the Developer options menu? I don' know it is possible to enter the custom recovery without checking that option..
Awesometic said:
Hello.
Strange. Once you have installed TWRP recovery on your tablet then it should not be turned into the stock recovery again automatically. I believe.
Have you checked OEM unlock option in the Developer options menu? I don' know it is possible to enter the custom recovery without checking that option..
Click to expand...
Click to collapse
I agree. I didn't realize the stock recover could overwrite TWRP once you were able to boot into it. Yes, I did have the bootloader unlocked (by OEM unlock in Dev Options, not sure there's another way). I was using Odin to flash and even tried a few different versions. The tablet originally had the latest Oreo Rom. I tried downgrading it to an older Oreo and also tried a Nougant rom. I had to do a "Format Data", otherwise I would get a boot loop and it seems to me that this then forced a "factory reset" on the next restart where it would sit on the Samsung logo for a very long time. I tried several different angles. I could reboot from TWRP back into TWRP. I even tried flashing TWRP on top of TWRP. Every time I went to boot into Android, it would take forever while it was apparently performing a rebuild of something. I was trying to avoid root to avoid tripping Knox. My ultimate goal was to systemize an app using TWRP which I've done on several older Samsung tablets.
In the end, I flashed Magisk then everything worked on the first try. Booting into Android went quick and I still had TWRP. I tripped Knox but in the end I was able to get what I needed onto the tablet. All is fine now.
Thanks for your work on this TWRP recovery and for sticking around to help support it.
Hi everyone!
I'm using a Samsung gt-n8010. It could be done for due to the age, but maybe there is still hope.
My problem is that the tablet boots always to TWRP recovery and I can switch to download mode as well. Everything seems all right, internal storage and sd card shows exactly how they should, BUT... I can't do anything in TWRP. If I have the Keep system partition read only unticked, it still says the storage is read only and /data/media is not accessable. I can see it and access it with TWRP File manager. I tried flashing ROM and Recovery, also stockROM with Odin, but Failed. Clearing Cache, Data, Dalvik... also ends up with error. Format Data works, and also changing the partition types, but when I reboot device, it all comes back the same as before, no changes take effect. In Download mode I tried to use Adb from computer terminal, but it was stuck saying 'Waiting for device'. If Tab is in Recovery my PC shows both internal storage and sd card, but the internal storage is empty when I open it.
For details: I use Lineage OS 18.1 with TWRP 3.6.1_9-0. On my computer I use Linux Mint 20.3, but I tried with a laptop using Win10 as well, no success.
I've read many solutions on 'Unmodified system partition' or some had 0MB internal storage problem, but in my case that is different, as I have them all, but it seems all is read only and not accessable. I even tried to have the last Backup (2 month old) set using Restore of TWRP, but during the process, the tablet reboots and TWRP comes up again. I can't even turn it off, as TWRP comes up after some minutes.
Please help me somehow to be able to use the Tablet. If you need any further details, just tell me.
TWRP is not out yet on android 12, if you have it as of writing it wont be able to unencrypt your device. So all you can do is use it to install roms (YOU MUST FIRST FACTORY RESET THE DEVICE).
I also have never used odin as I have prefered adb
Code:
adb shell
/sbin/recovery --wipe_data
/sbin/recovery --update_package=SDCARD:romname.zip
adb should work in twrp?
I see your point. I intended to change/downgrade LineageOS version, but I was not successful. Now I am not able to do a factory reset either with success from TWRP, but I give a try to your adb codes. Give me some time
leathan said:
TWRP is not out yet on android 12, if you have it as of writing it wont be able to unencrypt your device. So all you can do is use it to install roms (YOU MUST FIRST FACTORY RESET THE DEVICE).
I also have never used odin as I have prefered adb
Code:
adb shell
/sbin/recovery --wipe_data
/sbin/recovery --update_package=SDCARD:romname.zip
adb should work in twrp?
Click to expand...
Click to collapse
Hi, I gave a try to that code both on TWRP and Linux terminal (from PC). But no effect First I did a FactoryWipe (successful) and went back to the Terminal each time. I tried with ROM zip and TWRP img as well, but after rebooting, TWRP 3.6.1 comes back again. I downloaded Lineage OS 17.1 (with GAPPS pico) and TWRP 3.5.0-9. It seems somehow I got stuck with that TWRP 3.6 and all I get on every attempt of flashing or wiping is it can't see '/data/media (No such file or directory)' or 'Unable to make /cache/recovery: Read-only file system'. I hope there would be a solution to get my system out of Read-only state
Nektarin87 said:
Hi, I gave a try to that code both on TWRP and Linux terminal (from PC).
Click to expand...
Click to collapse
Do you have adb installed and do you see your phone when you type "
Code:
adb devices
"
Usually its as simple as just booting into TWRP -> Factory reset then install the rom and done.
Maybe you do need odin but im pretty sure you can use adb instead like I outlined above, I hated using odin but if you find the right file it should also fix your issue.
What is the codename for your tablet? I cant find it on lineageos's site, what guide did you use its an official lineageos im assuming?
leathan said:
Do you have adb installed and do you see your phone when you type "
Code:
adb devices
"
Usually its as simple as just booting into TWRP -> Factory reset then install the rom and done.
Maybe you do need odin but im pretty sure you can use adb instead like I outlined above, I hated using odin but if you find the right file it should also fix your issue.
What is the codename for your tablet? I cant find it on lineageos's site, what guide did you use its an official lineageos im assuming?
Click to expand...
Click to collapse
Well, I have adb installed, but as my Tablet can only load in recovery it says like these:
adb devices
List of devices attached
4107cd04a2b611b5 recovery
When I load Odin or fastload mode (Download mode as tablet says) I can not list it with 'Fastboot device" command. It says 'waiting for device'.
My tablet is Samsung gt-n8010 (10.1) and I follow this thread to make changes:
LineageOS 16.0 Android 9 for GT-N8000 GT-N8010 GT-N8013 GT-N8020 FINAL VERSION EOL
/* * 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...
forum.xda-developers.com
I had Lineage OS 18.1 installed and maybe what caused the issue is that I did not update the TWRP, or we do not have a TWRP ready for it yet, but currently I have TWRP 3.6.1_9-0 installed and stuck with. As I mentioned, on rebooting tablet always starts with TWRP, asking if I want system read only or not with an Unmodified system partition heading. I can not boot OS at all, I can go to Download mode, but Odin always failed indicating my system is read-only.
Ok yes your device is listed as recovery because it has not booted anything. I'm not sure if the commands I gave work without the system actually booting however.
After you entered adb commands there was no error text?
Also if you cant get odin to recognize your phone (RUN IT AS ADMINISTRATOR) you should figure out that first as thats a last resort fix when you really mess things up which I dont think you have yet. I think you must have something off in your configuration if its not reading anything make sure u can access another phone to rule out your pc, but get this working asap.
Usually if your device boot loops you can wipe the cache, and now days remove magisk modules.
If your device still boots straight to recovery It should be as easy as I outlined above, try not isntalling the apps/plugins after the initial rom, and again make sure you wipe cache/data before hand.
If your device boots straight to the bootloader then your left with Odin.
Man I hate video guides. But it looks good (unless he forgot to wipe) should have been as simple as that. He does not however provide you with the firmware (not rom) file that I believe you are going to need if you improperly downgraded the android a full version number. Post on his youtube and find that firmware file and fix your odin connection and flash it. If odin is also dead I have no idea but I have never in nearly 20 years had a phone fully brick even when I try to brick them. But I know it can be possible but your most likely going to recover from this.
If he doesn't respond just read more and learn, you may need some specific large file though to flash over what I believe may now be missing partitions entirely.
Maybe someone else here can help too. Good luck!
leathan said:
Man I hate video guides. But it looks good (unless he forgot to wipe) should have been as simple as that. He does not however provide you with the firmware (not rom) file that I believe you are going to need if you improperly downgraded the android a full version number. Post on his youtube and find that firmware file and fix your odin connection and flash it. If odin is also dead I have no idea but I have never in nearly 20 years had a phone fully brick even when I try to brick them. But I know it can be possible but your most likely going to recover from this.
If he doesn't respond just read more and learn, you may need some specific large file though to flash over what I believe may now be missing partitions entirely.
Maybe someone else here can help too. Good luck!
Click to expand...
Click to collapse
Hi there, I actually find some videos or instructions useful and some helped me out a lot. But as always, things can only be proper if anyone is qualified to do it or when you have the exact same issue on the device. Now back to my case...
I tried many ways, many aspects, but none helped me out. There was this good and working Samsung 10.1 gt-n8010 and one afternoon I found it turned off. When I charged it for a while I turned it on and all it could load is TWRP and I could not do anything. It seems to be working, but I could not see internal storage, while it showed all the 12 GB amount I had, so the issue is not that it shows 0 GB like in many videos. I tried to wipe cache, data, system, even change partition types, all ended with a fail saying my 'system is read only'. I also tried to use Odin and Heimdall to flash new recovery and ROM, also gave a chance to stockRom with android 4.1 or 4.4, but in all cases it said FAILED. To conclude all: I think it could be a hardware issue and as the machine is more the 10 yrs of age, it would not be a surprise, but it's a same it can't be flashed.
If anyone had a similar issue or may have suggestions I'm all ears and the thread remaines, but I am out of ideas at the moment and put my Samsung tab on the shelves.