Related
I've modified froyo framework to add soft buttons (back and menu) on the status bar. But there are some screen artifacts on the lock screen with my mod. I'm thinking it could be due to a difference in the froyo source code i used. Does nookie froyo has a git repo anywhere? Turns out I forgot to copy over 1 of the jar files. Remount your froyo /system partition rw, and unzip the attached framework.zip, copy the files into /system/framework, reboot and enjoy
{
"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"
}
link to the source code patch for those interested.
There is a NookieDev's project on GitHub: http://github.com/NookieDevs/
But there are also several people working on their on forks of the repositories:
https://github.com/cicada/
https://github.com/fat-tire/
Nice work on the interface buttons I was hoping someone would start working on something like this. I've seen similar buttons on the GTab (TnT) releases and I was wondering what it would take to put those into Froyo (or some other build )
Edit: A picture of what I'm talking about:
Do the buttons work just like shown or do you have to drag the notification bar down to use them? Are you going to post instructions how to accomplish this?
Can you share your code? I've tried to put all 4 buttons in the bottom ala archos 101 with no success. Cant wait for the honeycomb open source code
Nook Color via Xda App
This is great! Is there any way to move it to the bottom, too?
Mat Sumpter said:
There is a NookieDev's project on GitHub: http://github.com/NookieDevs/
But there are also several people working on their on forks of the repositories:
https://github.com/cicada/
https://github.com/fat-tire/
Click to expand...
Click to collapse
I can't see froyo source code on any of the git repo above. Admittedly my git-fu is weak If I've mistaken about github and indeed froyo source is available in one of the repos above, let me know!
Novarider said:
Do the buttons work just like shown or do you have to drag the notification bar down to use them? Are you going to post instructions how to accomplish this?
Click to expand...
Click to collapse
The buttons work just like normal buttons. No need to pull down the notification.
cainhunpi said:
Can you share your code? I've tried to put all 4 buttons in the bottom ala archos 101 with no success. Cant wait for the honeycomb open source code
Nook Color via Xda App
Click to expand...
Click to collapse
Currently there are some screen artifacts (an extra plus button, and when you drag to unlock, the target dot is replaced by another image) on the lock screen. I'd like to sort this out before posting the compiled jar/apk and source.
jasoraso said:
This is great! Is there any way to move it to the bottom, too?
Click to expand...
Click to collapse
That's my idea too. i think B&N got this right. With a tablet form factor, it's definitely more convenient to have the buttons at the bottom rather than top. Google is going with this direction in honeycomb as well. I'm still trying to figure out how to do this in froyo though.
The nook color is my first android device so I'm not sure if this repo is for froyo (I read it was, but it was in a bit of an older post) or gingerbread but here it is.
https://github.com/android/following
Based on the dates of items added I believe it is froyo though.
Also, looking very much towards your release of this. It may re-enable the use of my volume buttons as volume buttons
Yes - this looks great. I spent some time trying to work on gesture based system-wide back menu functionality (like how in several popular ereaders you drag your finger down the left side of the screen to change brightness - or swiping left on the Bn eclaire status performs the back function) But your solution is quite elegant and I can't wait for you to release it. I think I migh wear out my remapped hard volume keys...
shameless self bump I've attached my framework mod in the 1st post. Everything should be working now.
I installed in fine, and it ran beautifully.
However, ever since I installed it, I started getting FCs in the Browser and some other apps like TweetDeck. I cleared cache, dalvik as well, still no go.
FWIW The same issue occurs when I apply the no network bars mod as well.
Good job however!
Could you explain a little bit more about how you did this, or post source code?
This is huge. Thanks for doing this.
This is great work, but I've gotten too addicted to having vol up and down be my menu and back buttons Also, you might wanna consider moving those buttons in towards the middle as we know how badly the NC's touchscreen works at the corners.
God, you GOTTA love Android and how infinitely modifiable/enhanceable it is.
Can you fix the width of the notification drawer or give me some instruction on how to do it?
rookie1 said:
I've modified froyo framework to add soft buttons (back and menu) on the status bar. Remount your froyo /system partition rw, and unzip the attached framework.zip, copy the files into /system/framework, reboot and enjoy
Click to expand...
Click to collapse
Followed your instructions and now stuck in a boot loop!!!!
rookie1 said:
shameless self bump I've attached my framework mod in the 1st post. Everything should be working now.
Click to expand...
Click to collapse
Damn I used root explorer to coy over your files and that worked fine then rebooted and now in a boot loop stuck at the Large Android on screen boot up.
I am on a mac had nookie froyo .58 on sdcard. ANy idea how I can fix?
Canadoc said:
Damn I used root explorer to coy over your files and that worked fine then rebooted and now in a boot loop stuck at the Large Android on screen boot up.
I am on a mac had nookie froyo .58 on sdcard. ANy idea how I can fix?
Click to expand...
Click to collapse
Correct me if im wrong, but since it is on an sdcard can't you just load the system partition (im 99% sure you can in ubuntu) and just swap it out with your old frameworks on your mac? (you did back up the older version right? if not Im sure someone can post it for you)
Canadoc said:
Damn I used root explorer to coy over your files and that worked fine then rebooted and now in a boot loop stuck at the Large Android on screen boot up.
Click to expand...
Click to collapse
I have the exact same issue. Stuck on the android screen. Copied files to /system/framework using root explorer on a dual-boot emmc setup. Stock boot still works, but froyo boot is borked.
MattJ951 said:
Correct me if im wrong, but since it is on an sdcard can't you just load the system partition (im 99% sure you can in ubuntu) and just swap it out with your old frameworks on your mac? (you did back up the older version right? if not Im sure someone can post it for you)
Click to expand...
Click to collapse
Can't mount system partition on the mac. That is the problem.
Canadoc said:
Can't mount system partition on the mac. That is the problem.
Click to expand...
Click to collapse
Fount a way to get them mounted on my mac.DOes anybody have the original files?
Say hi to "CyanoBoot" -- a 2nd bootloader/w menu aka "ub2" - (WIP)
“CyanoBoot”
(aka a "second bootloader")
Quick Guide
by fattire
(@fat__tire on Twitter)
Alpha 0: "I don't have a NT" Edition
{
"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"
}
(Thanks to indirect for the image.)
What is CyanoBoot?
CyanoBoot (working title) is a “second bootloader” in early development, which is based on the open-source “u-boot” project, as further customized by BN & Bauwks. It is similar to the bootloader provided by Bauwks but has additional enhancements to make booting unsigned partitions easier and to generally enhance the booting experience on the Nook Tablet (aka “acclaim”) device.
CyanoBoot is intended for use with the forthcoming CyanogenMod 9, but it can also be used to boot CM7 or Ubuntu Linux or even the stock firmware (provided of course you are not legally or contractually bound from doing so. I haven’t read or agreed to any BN user agreements, so can’t speak to this.)
CyanoBoot includes an on-screen menu system, the ability to boot into three basic modes (normal, recovery, and “altboot”), configuration options, fastboot, and more.
The same version of CyanoBoot should start from both SD card and emmc (although it must be packaged and installed differently for each.) It should work on both the 1gb and 512mb RAM models. NOTE: It has been reported that some devices may require a USB cable to be plugged in to boot from SD Card. If true, this issue is not understood and is not addressed, nor is it likely to be.
NOTICE: CYANOBOOT (WORKING TITLE) IS HIGHLY EXPERIMENTAL AND IS NOT INTENDED TO BE USED BY NON-DEVELOPERS AND/OR THOSE UNWILLING TO ACCEPT FULL RESPONSIBILITY FOR ANY UNTOWARD CONSEQUENCES OF USING (OR ATTEMPTING TO USE) THE SOFTWARE. ALL SUCH ACTIVITY MUST OCCUR *ENTIRELY AT YOUR OWN RISK* AND YOU ACCEPT ALL CONSEQUENCES FOR DOING SO. THE USE OR ATTEMPTED USE MAY HAVE UNINTENDED RESULTS, INCLUDING BUT NOT LIMITED TO LOSS OF DATA, DAMAGE TO HARDWARE, AND/OR EXPLOSIVE DIARRHEA. CYANOBOOT IS NOT ENDORSED, AFFILIATED, SPONSORED, NOR ASSOCIATED WITH THE "DAS U-BOOT" PROJECT, GOOGLE, BARNES AND NOBLE LLC, TEXAS INSTRUMENTS, DENX., NOR ANY OF THEIR PARTNERS, OWNERS, EMPLOYERS, AFFILIATES, CLIENTS, SUBCONTRACTORS, OFFICERS, DIRECTORS, ADMINSTRATORS, INFORMATION PROVIDERS, ETC. EXCEPT INSOFAR AS THEY HAVE PROVIDED AND LICENSED SOURCE CODE TO BE FURTHER MODIFIED AND DISTRIBUTED. SEE THE RELEVANT GNU PUBLIC LICENSE FOR LICENSING DETAILS AND OTHER DISCLAIMERS. THIS SOFTWARE IS OBVIOUSLY INTENDED FOR USE ONLY BY THOSE WHO ARE AUTHORIZED TO DO SO.
Whew!
LIST OF THINGS
Started with “UB1” (aka u-boot, “first boot”) source code
Includes changes to support new 512MB model
Includes Bauwks’ repairs to fix “locked bootloader” malware
Many duplicate UB1 functions removed
One-build-boots-all (emmc or SD card, custom OS or stock)
Boot device indicator (top-left corner)
Bootcount indicator (top-left corner)
On-screen feedback to let you know what it’s loading.
Console-based boot menu
Support for key-combo shortcuts for menu/recovery
Alternate “Altboot” multiboot support allows 2nd OS.
Emmc setting for default boot profile (normal/altboot)
Emmc setting for default boot device (emmc or sd)
Emmc setting for automatic bootcount clearing
Boot fallback for stock firmware (0 bytes + sec. header)
Boot fallback for bauwks’ uboot (256 bytes)
Numerous visual enhancements
Unused bulky images removed (smaller file)
FASTBOOT support (w/menu selection)
On-screen build timestamp so you know version
Perhaps much more, or maybe not
There are likely bugs all over the place, but this is how it's supposed to work:
Key Shortcuts
Hold down home (“n”) key for the menu.
Hold down home (“n”) + “power” to have UB1 start recovery. If UB2 is also installed, it should respect this key combo and continue to load recovery.
The default behavior if no keys are pressed is to boot “normally”-- if booting from emmc, the boot partition (p4) from emmc will be booted. If booting from SD the boot.img on SD file will be booted.
The Boot Menu
Use the Home (“n”) key to navigate through the menu options. You can select an option with the power key.
The option you choose will override any other configuration you have made.
NOTE: Just so you don’t ask-- the reason the home and power keys are used to navigate through the menu rather than the volume up and down keys is due to a required driver not being included with u-boot 1. While the home and power keys use a very simple “gpio” method to detect if they are pressed, the volume keys are more like keyboard keys and thus are more difficult to detect. (The Nook Color bootloader, in contrast, did have the appropriate driver, so volume key detection was possible.)
Boot Indicators
Since you can boot from either SD or EMMC, it may be difficult to ascertain which version you are starting from.
Never again. You can now see whether you have loaded CyanoBoot from EMMC or SD by lookin at the top left corner:
“E” -> CyanoBoot is starting from emmc
“S” -> CyanoBoot is starting from SDCard
The # that follows this indicator is the current “bootcount”. After 8 unsuccessful boots or so, stock behavior is to run recovery with a reflash instruction. See below for instructions on clearing the bootcount at every boot automatically.
Fastboot (used for development)
For those familiar with “fastboot”, you can select the fastboot option from the CyanoBoot menu to go into fastboot mode. You can then (hopefully) flash to the boot or recovery partitions via USB cable using a command such as:
$ fastboot flash boot boot.img
Installation (SD Card boot)
(If you are preparing your own SD card for booting, you should be aware that for OMAP devices such as the acclaim, the SDcard must be formatted using a very specific configuration, which is detailed elsewhere.)
For SD Card, CyanoBoot is packaged inside a “flashing_boot.img” file to be placed in the first vfat partition of the SD-card along with the signed “mlo” and “u-boot.bin” files from the 1.4.2 update.zip.
(I'm told the mlo file may be called called MLO_es2.3_BN in the BN update.zip and should be renamed to “mlo”.)
Next, the boot (“boot.img”), recovery (“recovery.img”) and/or alternate boot (“altboot.img”) image files may optionally be placed in this partition.
Installation (EMMC boot)
To boot from emmc, the “flashing_boot_emmc.img” file, which contains a packaged version of CyanoBoot, should be put at byte 0 of the third partition (recovery) and ALSO at byte 0 of the fourth partition (boot). Then, the boot/recovery partitions must be shifted “to the right” (to make room for Cyanoboot) so that it starts 512Kb in from the start of the file. Use a padding of zeros so that the boot image contents begin exactly at 512Kb.
The boot and recovery partitions are expected to use this offset. For the alternate boot from emmc, the “altboot.img” may be the identical file used in an SD-boot, placed into the /bootdata vfat partition without any offset.
NOTE: Again, use the flashing_boot_emmc.img file for emmc boot partitions, *not* flashing_boot.img, which is for SD card boot.
Offset Info
Again, when used on the emmc, CyanoBoot must be placed at byte 0, at both the boot and recovery partitions. The “actual” boot.img and recovery.img that would normally be at byte 0 of those partitions should be moved so that it starts 512Kb in.
Always use this offset in recovery (p3) and boot (p4) partitions. In other words, put CyanoBoot at offset 0 and then pad with zeros, then put the normal boot.img or recovery.img at offset 512.)
On SD Card, the “boot.img” and “recovery.img” files should have no padding or offset or anything. Use as normal. This is similar to how “uImage” and “uRamdisk” files are used on the NookColor, only use a single file for both with a header in front.
Installation Summary
One more time. Here are the locations for the boot images:
SDCARD
(p1-vfat)/boot.img file (no offset/padding)
(p1-vfat)/recovery.img file (no offset/padding)
(p1-vfat)/altboot.img file (no offset/padding)
EMMC
(p4-/boot partition)<- CyanoBoot at byte 0, boot.img contents at 512.
(p3-/recovery partition)<- CyanoBoot at byte 0, recovery.img contents at 512.
(p6-vfat)/bootdata/altboot.img (no offset/padding, same as SDCard)
Configuration
You can control the "default boot" behavior (ie, what happens when you don’t hold down any keys). If you are a developer that does not want to constantly clear the bootcnt, you can also cause CyanoBoot to clear the bootcount automatically at every boot. To do this, three configuration files may be added to /bootdata (partition 6) on the emmc.
CONFIG #1: BOOT DEVICE
This will cause CyanoBoot to always boot from the emmc boot partition rather than SD. In this way, you can boot “through” a bootable SD card to whatever is on the emmc.
To Make Default Always Boot To EMMC
$ echo -n “1” > /bootdata/u-boot.device
CONFIG #2: ALTBOOT
Aside from the normal boot and recovery boot, a third boot option is available, called “altboot” (alternate boot). This is a kernel/ramdisk pair that can be used for a third firmware, an overclocked kernel, or whatever you like. If you choose the “altboot” as a default and it does not exist, your boot will fail.
As discussed above, the altboot.img file goes in the following location:
SDCard: file on p1 called “altboot.img” (no special padding or offset)
EMMC: file at /bootdata/altboot.img (no special padding or offset)
To Make Default Always Boot to “altboot”
echo -n “1” > /bootdata/u-boot.altboot
CONFIG #3: CLEAR BOOTCOUNT -- You can automatically zero out the bootcount with every boot. To set this:
To Make Default Automatically Clear BootCount
echo -n “1” > /bootdata/u-boot.clearbc
NOTE: A version of “Nook Tablet Tweaks” is planned to automate the above options much as Nook Color Tweaks does for the encore device in CM7.
Thanks/Credits
Thanks to chrmhoffman, nemith, xindirect, Celtic, and loglud for testing, as I don’t have a device and have never actually run this. Thanks to j4mm3r for the first encore menu code. It was pretty much rewritten for acclaim, but the first menu was invaluable in showing me how to add the code for the console. Thx to pokey9000 for stuff that helped get fastboot working.
Also thanks to BN as well as all the talented u-boot developers at Denx and elsewhere for the GPL’d code upon which this was based.
http://www.denx.de/wiki/U-Boot is where you can find the main u-boot project.
Also, a huge thanks to Bauwks for his code contribution as well as for making this possible in the first place!
Remember, this is all experimental. I'll try to update this post if there's something that needs to be updated.
(source)
If you have an issue, be sure to mention the timestamp at the bottom so everyone knows which version you're using. There will be bugs.
reserved for future expansion
Awesome
Hi,
Congratulations fattire. This is amazing work.
It boots the CM9 nicely.
Rgds,
Chris
I just gotta say, I laughed pretty hard when I read: Alpha 0: "I don't have a NT" Edition
Thanks
Wow
wow wow and we can use fastboot on the nook Tablet too? awesome
~ Veronica
Yep.
Works fine. Sometimes I have to re plug device though. But it speeds up things incredibly.
Chris
lavero.burgos said:
wow wow and we can use fastboot on the nook Tablet too? awesome
~ Veronica
Click to expand...
Click to collapse
Sent from my GT-I9000 using XDA App
Great work! Especially thanks for mentioning GPL software and folks behind it - that's thanks to them Android, Nook, Kindle, and even this bootloader were at all possible. So, where's source for the changes you made to this GPL software? Thanks again.
It's in the same directory. I'm going to make it a little clearer in the OP and I think maybe better organize the link to be in a subdirectory. So heads up that the links will change... ...changed.
fattire,
This looks great! Is it extensible to other devices like CWM recovery? I'd love to see this on the Transformer/Prime. Ubuntu on those devices replaces recovery, so it would be great to have a 2nd bootloader to get past these limitations. Also, it would be cool to see CyanoBoot on other devices like the NC and Touchpad. The TP has moboot but I think there's something to be said for consistency in this area.
Awesome work!
-mm
Yes, it'll work with CWM, TWRP2, or any other recovery. That's the point
Looks like the prime is a tegra3-based system. I don't know much about the bootloaders for Nvidia machines-- the nice thing about OMAP3/4 from Texas Instruments is that the u-boot bootloader works great, and is open source so you can extend it and stuff. While the bootloader for transformer is now unlockable I don't know that they give you the source, do they?
That said, from CM on the Qualcomm-based touchpad I know that a similar 2nd-level boot menu can be added AFTER the bootloader. Take a look at
the excellent moboot (lead developer is jcsullins) for an idea of how to add a very flexible menu that slips between the bootloader and the kernel. You can see it in action on youtube-- just look for any TouchPad cm7 or cm9 video where it boots up and you can select between CyanogenMod, WebOS, or one of the recovery images.
Hope that helps!
Mistar Muffin said:
fattire,
This looks great! Is it extensible to other devices like CWM recovery? I'd love to see this on the Transformer/Prime. Ubuntu on those devices replaces recovery, so it would be great to have a 2nd bootloader to get past these limitations. Also, it would be cool to see CyanoBoot on other devices like the NC and Touchpad. The TP has moboot but I think there's something to be said for consistency in this area.
Awesome work!
-mm
Click to expand...
Click to collapse
fattire said:
Yes, it'll work with CWM, TWRP2, or any other recovery. That's the point
Click to expand...
Click to collapse
Sorry, I was trying to ask if CyanoBoot would be available on multiple devices the same way CWM is. I understand it allows the booting of recovery images. What I did not realize was that uboot was tied to the TI OMAP platform, so you're answer was very helpful. Thank you!
Gonna be honest, I'm pretty sure this is for flashing roms such as how cwm allowed me to install cm7-teamb but I'm not sure. Also I saw someone say it flashes cm9? Sorry I'm just trying to get a feel at what this would really be used for, no offense intended.
fattire said:
It's in the same directory. I'm going to make it a little clearer in the OP and I think maybe better organize the link to be in a subdirectory. So heads up that the links will change... ...changed.
Click to expand...
Click to collapse
Thanks! Why not push it to github? (At least I had a look thru your repos on github yesterday and didn't see anything related, sorry if I missed something.)
Thanks for the awesome work fattire.
Here are the problems I found:
I manage to include cynoboot in recovery & boot but then there's device no found error using adb. Am I missing some drivers? (I am using WinXP)
because of that fastboot is not working too.
and then once enter fastboot mode. I can't get out unless I power off (n button can't navigate)
Hi,
you can use "fastboot reboot" to reboot the device. I didn't have an adb problem. Are you saying you try to adb into the device when in the menu? This doesn't work as there is no android running. I guess on windows you have to install android SDK first to get the drivers.
Rgds,
Chris
chrmhoffmann said:
Hi,
you can use "fastboot reboot" to reboot the device. I didn't have an adb problem. Are you saying you try to adb into the device when in the menu? This doesn't work as there is no android running. I guess on windows you have to install android SDK first to get the drivers.
Rgds,
Chris
Click to expand...
Click to collapse
I mean if I boot up the rom (I'm running MIUI) with the boot.img that includes cynoboot, then adb does not work (device not found). If I boot with the original boot.img, then no problem with adb
And fastboot command does not work for me either (I have android sdk installed)
I'll try the sdcard version later.
sungod88 said:
Gonna be honest, I'm pretty sure this is for flashing roms such as how cwm allowed me to install cm7-teamb but I'm not sure. Also I saw someone say it flashes cm9? Sorry I'm just trying to get a feel at what this would really be used for, no offense intended.
Click to expand...
Click to collapse
It's a bootloader
cobrato said:
I mean if I boot up the rom (I'm running MIUI) with the boot.img that includes cynoboot, then adb does not work (device not found). If I boot with the original boot.img, then no problem with adb
And fastboot command does not work for me either (I have android sdk installed)
I'll try the sdcard version later.
Click to expand...
Click to collapse
Are you using the 1.4.2 mlo and a 1.4.2 kernel?
fattire said:
Are you using the 1.4.2 mlo and a 1.4.2 kernel?
Click to expand...
Click to collapse
I'm using 1.40
Sent from my LT18i using Tapatalk
cobrato said:
I'm using 1.40
Sent from my LT18i using Tapatalk
Click to expand...
Click to collapse
cyanoboot is effectively a 1.4.2 u-boot.bin as far as handling the 512 model and all that goes. I don't konw that there were significant changes that would affect usb/adb, but jic you might want everything to match up...
Oh also, as far as fastboot goes... the device vendor_id was changed from 0x0451 to the google usb vendor id that most fastboots use which is 0x18d1. The device product_id is 0x0100.
Worked for chrmhoffman and others...
Hi,
New NSS beta is available for download. It will implement installing and restoring
of the bootloader as single click solution. Although the Qcom loader could be
installed via normal flashing, it is much easier this way. Also recovery is intended
to save manual hex editing or cmd line commands.
1. Download the new version
2. Extract to a folder, start the program
3. Insert the 2 loaders in \loaders\special\wp7\ - the qualcom file: RM803_12w07_prod_generic_nokia_osbl.esco,
posted by xorizont here , second file: RM803_11w48_prod_raw_nokia_osbl.bin attached (unzip first)
4. Go to Flashing->WP7 Tools
You are ready to play. Quick description:
- Read PMM button - reads the PMM partition with Nokia specific values(product
code, MAC addresses, et), you can edit in the boxes
- Write PMM button - writes back to the partition a selected value (via Update
checkbox)
Install button - use this to quickly install Qcom loader on 710(no way to load on
800 as the cert is checked)
Parse FS button - you can use this to test NSS partition parser and compare
against 3rd party tool, to make sure something catastrophically wrong will not
happen during recovery
Restore button - This will attempt to recover the Nokia production loader (so called DLOAD)
via raw NAND write into partition 2 of the connected phone. Make
sure you start in Normal mode as NSS will need to check phone type and battery
value (to make sure wrong file is not written to 800, or if the battery is critically
low)
Please keep in mind, this is a Beta version, it has been tested only on one phone
and is possible to be a major phone killer, so thread lightly. It is offered as it is,
with the hope of being useful, and I can't be held responsible for fatal results.
My best recommendation is to check the partitions after write/recovery with
3rd party tool and make sure all is ok before restarting the phone power. All this
until some recovery method is found (if somebody has found flashing routines in
SECBOOT or other loader, pls PM me).
BR, Chris
Thanks for this nice tool!
I just wanted to stress that:
- Read PMM button - reads the PMM partition with Nokia specific values(product
code, MAC addresses, et), you can edit in the boxes
- Write PMM button - writes back to the partition a selected value (via Update
checkbox)
Click to expand...
Click to collapse
Are only possible when the phone has the qualcomm loader right? Because only then it's possible to overwrite the values using the NAND access mode (Qualcomm MSD).
Hi,
Yes, only in NAND mode, on phones that have it. If you have Nokia DLOAD loader
and not hacked phone, you can only read those value via JSON call to NCSD appl.
There isn't any method coded to change them in Normal mode(at least i did not
find one yet).
BR
Bph&co said:
Hi,
Yes, only in NAND mode, on phones that have it. If you have Nokia DLOAD loader
and not hacked phone, you can only read those value via JSON call to NCSD appl.
There isn't any method coded to change them in Normal mode(at least i did not
find one yet).
BR
Click to expand...
Click to collapse
It's good to see there is now a userfriendly way of doing stuff like this. Thanks again
now all we need is a tool to write an .nb file with one click. can one do it?
mariosraptor said:
now all we need is a tool to write an .nb file with one click. can one do it?
Click to expand...
Click to collapse
To be honest i have no idea how that exactly works - is there a need for a file
system parser and proper replacing of a file, or just writting to a const location
in the last partition.
The mount never worked on my Ubuntu install(and i am complete Linux newbie).
Bph&co said:
To be honest i have no idea how that exactly works - is there a need for a file
system parser and proper replacing of a file, or just writting to a const location
in the last partition.
The mount never worked on my Ubuntu install(and i am complete Linux newbie).
Click to expand...
Click to collapse
Thanks God. there is someone else like me in linux.( humor, no offense ofcourse ;-) )
mate i have no idea how it works. nobody wants to write a very accurate tutorial.
not being able to flash the custom rom was the reason that i reverted my bootloader.
To unlock bootloader I used to NCS and firmware posted by xorizont. So how make connection under Windows7 before flash xorizont's firmware if Nokia is in DLOAD mode?
this is very helpfull for many people to get to qulcomm on 710!
+1
So You are able to load Qualcomm B. via NSS even if on the moment I have got DLOAD?
Hi,
New Beta - 0.47.1 - with ability to write moded OS files(.nb).
OS File button - select .nb file
Write OS button - loads the file onto the last partition (change to OSBL mode first)
As with the previous beta - make sure you check the partion parser for errors.
Write will be verified, but not the exact write address, so maybe good to have a
look with WinHex before restarting the phone.
BR
Already a new version, you're working hard man! ;-)
So if i understand correctly, you have automated the process of 'block writing' (which without this tool requires using dd) the created custom roms to the correct partition on the Lumia?
Of course this requires Qualcomm bootloader; for the 710 your tool can load this even if the phone currently has the newer Nokia DLOAD.
Hi,
Yes, i work even in my sleep Right now killing myself with the baseband diss, but
decided to have a break and make this.
It seems the OsBuilder creates raw partition image, to fit exactly into the OS part
of the NAND chip. So all i do is open the usb device as physical disk, parse the
partition structure and do a low level read/write to absolute addresses.
Yes, it is mostly for 710, but write OS function should be working for 800 with
Qcom loader too, just can't test it as i don't have such phone.
Also the Install/Recovery should work forever on a 710, unless Nokia/MS release
some updated bootloader that somehow prevents loading of the signed Qcom
loader and the user does a full flash (or via sneak Zune update) and overwrite
the current DLOAD loader.
BR
Bph&co said:
Hi,
New Beta - 0.47.1 - with ability to write moded OS files(.nb).
OS File button - select .nb file
Write OS button - loads the file onto the last partition (change to OSBL mode first)
oh man you are a superstar. you did what i said it was missing. no more (hopefully) screwd phones.
@Mods please make this sticky.
Click to expand...
Click to collapse
Amazing tool!
I just used it to load Full Unlock Image for Lumia 710 by lucifer3006!
No more linux stuff needed, this is great and almost one-click windows solution!
Thank you!
When we talking about copy moded nb file into partition You mean sdx9 is default partition?
Hi,
The sdb thingi is something from Linux. On low level there are 4 primary partitions
in MBR, all the rest are logical, so the last entry in MBR points to the first logical one,
that for itself contains primary part and next one is logical as well. The last entry
in this linked list is the OS partition.
BR
1. OK I went through this. Tell me please how is possible to unlock bootloader if Lumia is in DLOAD mode? NSS can't reconized WP in this mode.
2. In case of relocking bootloader did I need copy Your specific RM803_11w48_prod_raw_nokia_osbl.bin or download an from navifirm?
I hope it's add backup and restore the "DPP.BIN" function!
like this!
{
"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"
}
Thank you very much!
djtonka said:
1. OK I went through this. Tell me please how is possible to unlock bootloader if Lumia is in DLOAD mode? NSS can't reconized WP in this mode.
2. In case of relocking bootloader did I need copy Your specific RM803_11w48_prod_raw_nokia_osbl.bin or download an from navifirm?
Click to expand...
Click to collapse
Hi,
1 - Maybe you have Zune running and NSS can't open the port ? Use the kill Zune
services option in NSS please
2 - Yes this specific loader is needed (its extract from an original file) and is hash
checked before writting to the second partition to prevent dead phones
BR
I haven't had enough to get a One now, but I'm pretty interested in the phone. Yesterday I saw a thread on Chinese forum, saying that LOGO.bin contains the image shown in fastboot mode, and thus everyone can choose his preferred image (like CM's) even if he uses ColorOS. So I tried to extract the bitmap from LOGO.bin and replace it with my own picture.
Now I've succeed PARTIALLY in identifying the BIN file format and extracting the images. There's no enough time to dig into replacing the pictures though, but I think it won't be hard.
Here is what I find, for those "aggressive" themers and ROM devs who want custom boot splash screen:
The BIN file starts with the following structure:
C:
struct SPLASHHEADERINDEX {
char magic_code[8]; // = { 'S', 'P', 'L', 'A', 'S', 'H', '!', '!' };
int img_width;
int img_height;
int reserved; // What's this? I haven't figured that out.
int img_offset[6];
char padding[468]; // The header is 512 bytes. Thanks [user=5757424]@chillstep1998[/user] !
};
Right after this structure, the raw data of boot splash image begins. Every pixel is described by 3 bytes in B-G-R order. The pixels begin at the upper left corner and then stored in the order of left to right & up to down. You can read (img_width * img_height * 3) bytes and write them into a BMP file. NOTE that BMP files require 4-pixel alignment for every horizontal row (Google that for details, otherwise you will get a "Broken image" info in image viewers) In order to avoid this problem, I wrote a simple program in VB.NET and used Bitmap.SetPixel and Bitmap.Save to solve it.
This is the VB code for this procedure. (I can't do GUI programs in C++...)
Code:
Dim bmp As New Bitmap(img_width, img_height)
Dim color As Color
For y = 0 To img_height - 1
For x = 0 To img_width - 1
b = fs.ReadByte 'fs is the FileStream of BIN file. Already sought to correct offset.
g = fs.ReadByte
r = fs.ReadByte
If b = -1 Then b = 0
If g = -1 Then g = 0
If r = -1 Then r = 0
color = color.FromArgb(r, g, b)
bmp.SetPixel(x, y, color)
Next
Next
There are some zeros after (img_width * img_height * 3) bytes. I don't know what's for...
Then let's look at the other images. Their offsets are in the img_offset array of SPLASHHEADERINDEX. They have headers like this:
C:
struct SPLASHHEADERNONINDEX {
char magic_code[8]; // "SPLASH!!" without \0
int img_width;
int img_height;
int reserved; //Still don't know
char padding[492];
};
Right after the structure is the raw data. Process that as mentioned above.
The image at img_offset[0] is the one shown in fastboot mode
[1] is AT current test (original Chinese: AT电流测试. What's AT?)
[2] is RF test
[3] is WLAN test
[4] is charging
[5] is low battery warning
Previews for new images are coming soon...
However: there is one bug: the images extracted are "mis-placed". You need to move 0x0 to 164xHEIGHT (163xHEIGHT maybe) area to the right side of the image to get the correct pic. The images extracted from ColorOS' LOGO.bin are listed as follows:
SPOILER:
[0]
{
"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"
}
[1]
[2]
[3]
[4]
[5]
Boot splash
Does anyone know the cause of this mis-place problem? Although that can be solved easily in the code, but it's not very reliable. Maybe it's related to the "reserved" member?
Since the format is rather simple, modding and repacking will be easy. When I get some free time I'll make a tool for this...
still dangerous. We don't know whether there's logo signiture check, even if we know how to make a logo.bin.
But good job!
dlhxr said:
still dangerous. We don't know whether there's logo signiture check, even if we know how to make a logo.bin.
But good job!
Click to expand...
Click to collapse
Can't come up with any reason why there should be signature check for logo, especially when we can use home-made modem fimwares and kernels without any problem... But it's worth considering since there's "reserved" member. ColorOS gets 0x00 0x00 0x00 0x00 and CM 0x00 0x00 0x00 0x01 in boot splash's "reserved" int. Haven't checked other 6 images though.
We already know how to make our own logo.bin...there's a thread in the "Themes and Apps" section.
treChoy said:
We already know how to make our own logo.bin...there's a thread in the "Themes and Apps" section.
Click to expand...
Click to collapse
Wow I didn't notice it before... This thread is revealing secrets of the magic and pushing it further
But he says the header is 512 bytes, which is different from what I've found. I will take a look. However, since there are pics as small as ~300*30, skipping 512bytes may cause visible loss of the content. Maybe that's for splash screen only.
updateing said:
Wow I didn't notice it before... This thread is revealing secrets of the magic.
But he says the header is 512 bytes, which is different from what I've found. I will take a look. However, since there are pics as small as ~300*30, skipping 512bytes may cause visible loss of the content. Maybe that's for splash screen only.
Click to expand...
Click to collapse
As far as they've discovered on the thread, they've only really uncovered the workings of the splash screen. We know that fastboot is also affected by the LOGO partition, but we don't know how that ties in with the bootloader. The ColorOS LOGO.bin displays, "已進人fastboot..." when in fastboot mode, and the International LOGO.bin displays "Fastboot Mode" with the Cyanogen mascot.
One thing is for certain though: this is DANGEROUS. There's a very good possibility of bricking because of the LOGO partition's relationship with the bootloader. I was talking to another developer here about his work with the LOGO partition, and he said he bricked his phone, but recovered it by holding the power button, and then manually writing the correct LOGO partition using the 'dd' command.
I've contacted OnePlus support about this, so we should hear word back around Easter.
treChoy said:
As far as they've discovered on the thread, they've only really uncovered the workings of the splash screen. We know that fastboot is also affected by the LOGO partition, but we don't know how that ties in with the bootloader. The ColorOS LOGO.bin displays, "已進人fastboot..." when in fastboot mode, and the International LOGO.bin displays "Fastboot Mode" with the Cyanogen mascot.
One thing is for certain though: this is DANGEROUS. There's a very good possibility of bricking because of the LOGO partition's relationship with the bootloader. I was talking to another developer here about his work with the LOGO partition, and he said he bricked his phone, but recovered it by holding the power button, and then manually writing the correct LOGO partition using the 'dd' command.
I've contacted OnePlus support about this, so we should hear word back around Easter.
Click to expand...
Click to collapse
Hope OnePlus support team is open to this kind of mod...
As for the developer you mentioned, could you please ask him if he entered Qualcomm DLOAD mode and used some .hex file to boot the phone into mass-storage mode? I know when this (QHSUSB DLOAD device) shows up, the bootloader has already failed and this is the last recovering method of the phone. Seen it on my Xperia TX...
And the method mentioned in this thread will also work on CM's LOGO.bin, except for the 164xH issue.
updateing said:
Hope OnePlus support team is open to this kind of mod...
As for the developer you mentioned, could you please ask him if he entered Qualcomm DLOAD mode and used some .hex file to boot the phone into mass-storage mode? I know when this (QHSUSB DLOAD device) shows up, the bootloader has already failed and this is the last recovering method of the phone. Seen it on my Xperia TX...
And the method mentioned in this thread will also work on CM's LOGO.bin, except for the 164xH issue.
Click to expand...
Click to collapse
The developer is @demkantor . And I was wrong about how he unbricked his device. He said that after messing around with the LOGO partition, he got the dreaded "QHUSB_BULK" error, but after a few seconds, his OPO rebooted on his own. He had to 'dd' the regular LOGO partition to get his bootloader up and running. Original thread here: http://forum.xda-developers.com/oneplus-one/help/qhsusbbulk-help-t2848238
treChoy said:
The developer is @demkantor . And I was wrong about how he unbricked his device. He said that after messing around with the LOGO partition, he got the dreaded "QHUSB_BULK" error, but after a few seconds, his OPO rebooted on his own. He had to 'dd' the regular LOGO partition to get his bootloader up and running. Original thread here: http://forum.xda-developers.com/oneplus-one/help/qhsusbbulk-help-t2848238
Click to expand...
Click to collapse
I have once seen somewhere that you can find specific .hex file (e.g. MPRG8960.hex for MSM8960) to download into the phone by QPST Service Programming. Then the phone will boot into mass storage mode, where computer will recognize the phone as a removable disk drive. Now the whole internal storage is "mounted" on the computer and you can use dd to restore then.
(Google'd and it says only QHSUSB_DLOAD need the hex file. QHSUSB_BULK should be mounting the internal storage to computer automatically and dd will be available. Not sure about that. Example: http://forum.xda-developers.com/showthread.php?t=2582142&page=1)
yeah the header is 512 bytes. Now the images are all correct :victory:
Flashing a bad LOGO.bin did send me to the QHSUB_DLOAD mode and I tired rebooting holding down all three buttons. It did seem to work but after a bit it seemed to just boot on its own. Then I just used an adb shell to run dd commands to flash the proper .bin and all has been well since then
Still have been to busy with our newborn to look into anything deeper but between this thread and the one by @chillstep1998 and treChoy and other it looks to be all good!
Glad all is coming together on this end, keep up the great work all
dear thread creater.. i tell u what is that zeros after anything.
actualy android reads anything in block size.. like this
4,4,4,4,4.....
or 8,8,8,8,8.....
or 16,16,16,16...
or....
or...
or...
or 512,512,512,512...
or......
so.. if block size is 512 then it would read 512 bytes first..
now think what if there is only 50 or 51 bytes.. if will be a error.. if it has code to handle errors.. it is slow.
this is called alignment.. we say header is aligned to 512 bytes.
to make alignment it would add padding of NULLs(chr(0) in vb)
same nulls for the end of file to make it aligned to some size.
thank you.
m9j_cfALt said:
dear thread creater.. i tell u what is that zeros after anything.
actualy android reads anything in block size.. like this
4,4,4,4,4.....
or 8,8,8,8,8.....
or 16,16,16,16...
or....
or...
or...
or 512,512,512,512...
or......
so.. if block size is 512 then it would read 512 bytes first..
now think what if there is only 50 or 51 bytes.. if will be a error.. if it has code to handle errors.. it is slow.
this is called alignment.. we say header is aligned to 512 bytes.
to make alignment it would add padding of NULLs(chr(0) in vb)
same nulls for the end of file to make it aligned to some size.
thank you.
Click to expand...
Click to collapse
Thanks! I know there are some alignment rules, but didn't expect them to be here. I've seen aligning the whole file to 4 bytes or so, but little do I know that a section header needs alignment as well. I guess that's because this LOGO.bin is used in such a low-level "environment" that we don't have enough time & space to handle the non-aligned data. Am I right?
updateing said:
Thanks! I know there are some alignment rules, but didn't expect them to be here. I've seen aligning the whole file to 4 bytes or so, but little do I know that a section header needs alignment as well. I guess that's because this LOGO.bin is used in such a low-level "environment" that we don't have enough time & space to handle the non-aligned data. Am I right?
Click to expand...
Click to collapse
Hi man!
Do you know how change the battery animation when the phone is charging(when is off)?
I've tried to change the imgs in /res/images/charger, but you know, it doesn't work eheheh...
Can you help me?
Reive said:
Hi man!
Do you know how change the battery animation when the phone is charging(when is off)?
I've tried to change the imgs in /res/images/charger, but you know, it doesn't work eheheh...
Can you help me?
Click to expand...
Click to collapse
I don't have a OPO to test, all these analysis are theoretical. So I may not be able to help. Sorry...
Support is discontinued. Between the 6 different variants that I made this recovery for, it has been downloaded less than 500 times total over a 2 month period. That tells me that this device is simply not popular enough for continued support.
Here is TWRP 2.8.3.0 (unofficial) for the Galaxy Tab 4, 8in (T330 & T331 & T335 & T337T & T360 & T365).
This has been briefly tested by @Rusell, but please be aware that there may be a few bugs still. I do not own this device, so please be very specific when reporting any bugs you may find.
This is not a "direct from source build" (I will eventually switch to that method), but instead, it is a port from my Tab 31x version using stock Tab 4 zImage and DT image.
NOTES:
The new MTP feature of TWRP may cause issues with ADB access while in recovery. You may need to toggle "Disable MTP" a from the "mounts" menu to get ADB access.
64gb sdcards are reported to not work in this TWRP
All versions of TWRP occasionally give the "can't mount /system" error. If you get this error, simply reboot recovery and try again.
Click HERE for the latest version.
Please report any bugs here in this thread and attach the recovery.log. Advanced --> Copy log to SDcard --> Then attach the log to your post.
Credits go to:
@Rusell for initial testing
and of course the Team Win group
Supplied in 3 formats:
Odin flashable tar.md5 (for first time installation)
Recovery flashable zip (requires a custom recovery to currently be installed)
.img file (for those who use Flashify or other direct methods).
Instructions for ODIN: (use the one with "tar" in the name)
Download ODIN on your computer.
Power off the device.
Restart in "Download Mode" by holding the "HOME" button, "Volume Down" and "Power" all at the same time (for about 5 seconds).
Hit the "Volume Up" to enter download mode.
Start the ODIN exe program. Un-check Auto Reboot. See notes about ODIN below.
Connect the device via USB to your computer. Verify the device shows as "Added" in the Message box. If it doesn't show then you need the Samsung USB drivers (just install KIES to get them).
Select "PDA" then choose the recovery file you want to flash.
Hit "START". Wait for Odin to finish (~10-15 seconds). The message area will display "RES OK" when finished.
Restart directly to recovery mode before rebooting into OS.(Hold POWER, Volume UP, and the HOME button all at the same time. When you see the Samsung Logo, let go of the POWER button, but keep holding the Volume UP and HOME until you see the recovery screen).
After you get the custom recovery working, you can flash the latest SuperSu zip to get root.
Notes about ODIN
--Make sure that "Re-Partition" is NOT checked.
--Auto Reboot can be un-checked if TWRP doesn't flash correctly on your device. Some have reported that un-checking Auto Reboot fixes this issue. If you un-check Auto Reboot, you will need to reboot the device yourself (refer back to step 9).
Flash at own risk!!!!
I take no responsibility for anything you do to your device. Flashing any custom recovery will trip KNOX.
+++++++++++++++++++++++++++++++
DOWNLOADS
Click HERE for the latest version.
-
{
"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"
}
XDA:DevDB Information
[RECOVERY] TWRP 2.8.3.0 for Galaxy Tab 4 8 inch, Tool/Utility for the Samsung Galaxy Tab 4
Contributors
gr8nole, moonbutt74
Version Information
Status: Beta
Created 2014-12-22
Last Updated 2015-02-23
CHANGELOG
2.8.3.0
All versions - fixed color
See TWRP site for other changes
2.8.2.0
T330
v2 - Disabled screen timeout to prevent freeze ups. You may (or may not) still see the setting, but the screen will not timeout.
v1 - Initial release
======================
T331
test1 - Initial test -working
======================
T335
test1 - Initial test -working
======================
T365
test2 - WORKING
test1 - not working
-
Reserved
Other 8 inch Tab 4 variants.
If you want this for your tablet, you must post your stock recovery.img and test for me. It should be easy to make for T331, T335, etc... as long as your bootloader isn't locked.
-
:/
BUG:
When making a backup (Around 42%) The tablet just crashes for a second and shuts down.
Forgot to mention that my screen timeout is disabled....
Rusell said:
BUG:
When making a backup (Around 42%) The tablet just crashes for a second and shuts down.
Forgot to mention that my screen timeout is disabled....
Click to expand...
Click to collapse
I need recovery log.
Sent from my SM-N900V using Tapatalk
Thanks long time ago i seen you haha
gr8nole said:
I need recovery log.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Re-installed recovery now it is working well. However this time i am backing up on my external SD, maybe i didn't have enough space in my internal storage.
---------- Post added at 09:35 AM ---------- Previous post was at 09:31 AM ----------
BUG (Again )
When the screen times out, you can't wake up the device it just deep sleep. I'm going to try to pull out a recovery log.
Rusell said:
Re-installed recovery now it is working well. However this time i am backing up on my external SD, maybe i didn't have enough space in my internal storage.
---------- Post added at 09:35 AM ---------- Previous post was at 09:31 AM ----------
BUG (Again )
When the screen times out, you can't wake up the device it just deep sleep. I'm going to try to pull out a recovery log.
Click to expand...
Click to collapse
New v2 uploaded. http://d-h.st/bpb
I added a flag to disable the screen timeout. Let me know if it works.
gr8nole said:
New v2 uploaded. http://d-h.st/bpb
I added a flag to disable the screen timeout. Let me know if it works.
Click to expand...
Click to collapse
screen timeout is not disabled.but that's the only bug i found.
Who else owns this device other than me?
NVM in the settings it says it is set for 60 seconds but it never times out.
i beg you
can anyone please port a recovery to smt331
anyone i mean that should be custom like my favourite cwm
gr8nole said:
New v2 uploaded. http://d-h.st/bpb
I added a flag to disable the screen timeout. Let me know if it works.
Click to expand...
Click to collapse
gr8nole,
hi, in boardconfig
TW_NO_SCREEN_BLANK := <true or comment line with # or omit for false>
TW_NO_SCREEN_TIMEOUT := <true or comment line with # or omit for false>
to completely slay screen time-out and lock
m
moonbutt74 said:
gr8nole,
hi, in boardconfig
TW_NO_SCREEN_BLANK := <true or comment line with # or omit for false>
TW_NO_SCREEN_TIMEOUT := <true or comment line with # or omit for false>
to completely slay screen time-out and lock
m
Click to expand...
Click to collapse
That's what I used and it did work.
Dewang rocky said:
can anyone please port a recovery to smt331
anyone i mean that should be custom like my favourite cwm
Click to expand...
Click to collapse
If you will send me the T331 boot.img or recovery.img, I will do it. But, you have to test it for me.
Rusell said:
NVM in the settings it says it is set for 60 seconds but it never times out.
Click to expand...
Click to collapse
Ok, the reason you still see the screen timeout settings is because that info was saved in the TWRP settings file. This would only affect you because no-one else has flashed a version that had screen timeout. If you delete the TWRP/.twrps file from your internal storage, then you won't see the timeout settings anymore. That page will only show brightness control. Either way, the timeout is disabled and should cause no more problems. :good:
Thanks for testing!
Flashing TWRP recovery successful on sm-T330nu
I have successfully flashed TWRP recovery on my Tablet, sm-T330nu
using the easy instructions provided by the OP, gr8nole.
I tested this recovery by flashing the supersu 2.40 and did a backup of
the stock rom. This recovery is great and working fine.
I have not face any screen freeze up during this test.
When wiping cache/dalvik, it takes a bit long about 4 mins to finished.
Thank you gr8nole for your hard work and great TWRP.
The stock rom backup using this TWRP recovery
is 2.89gb large. This stock rom had many not needed
apps removed and only a few small games.
Is this backup size normal for a stock rom of
a samsung tablet T330nu ?
Antrobot200 said:
The stock rom backup using this TWRP recovery
is 2.89gb large. This stock rom had many not needed
apps removed and only a few small games.
Is this backup size normal for a stock rom of
a samsung tablet T330nu ?
Click to expand...
Click to collapse
That doesn't seem to be too big. Samsung roms are typically very big. Look into the backup folder and see what the size of the pieces of the backup are. It may be a lot of data.
Edit: On my Tab 3, my backup is about 3 gb with a mildly debloated Samsung rom.
Sent from my SM-T310 using Tapatalk
Thank you for your quick explaination about
the backup rom size. I am glad it is the normal
size for this tablet. This is my first samsung tablet
so I am still learning a lot about using it.
For some reason this won't install for me in odin. I go through the process and when I boot into recovery it takes me into stock recovery. I renamed the file T330.TWRP.2.8.2.0.v2.tar.md5.exe with .tar extension and it flashes but but when I go into recovery its stock recovery.
thanks
I will upload recovery.img and boot.img of my smt331