Related
Maybe some of you guys have figured this out already but it's probably important to note for people developing custom recovery or boot ROMs.
There is a partition on the internal flash named "bootdata" that stores a files named BCB and BootCnt. The secure bootloader updates BootCnt on every non-sdcard boot and if it gets too high it will automatically boot into the recovery partition instead of the boot partition. So, if you're making any custom ROM to be run from the internal flash then you'll want to reset that file in a boot script somewhere. The shell command "dd if=/dev/zero of=/bootdata/BootCnt bs=1 count=4" would do it (Assuming you've mounted the bootdata partition )
The BCB file is similar in that if the secure bootloader boots into the recovery partition for any reason, it will write to that file and will always boot into the recovery partition until that file is cleared. The shell command to clear that file is "dd if=/dev/zero of=/bootdata/BCB bs=1 count=1088"
The bootdata partition just contains a standard vfat filesystem so you just mount it normally.
And for the love of your god do not delete those files! If you do then booting from internal memory will continue to boot into the recovery partition until they are replaced. You would be able to boot from an SD card to replace them though.
bauwks said:
Maybe some of you guys have figured this out already but it's probably important to note for people developing custom recovery or boot ROMs.
There is a partition on the internal flash named "bootdata" that stores a files named BCB and BootCnt. The secure bootloader updates BootCnt on every non-sdcard boot and if it gets too high it will automatically boot into the recovery partition instead of the boot partition. So, if you're making any custom ROM to be run from the internal flash then you'll want to reset that file in a boot script somewhere. The shell command "dd if=/dev/zero of=/bootdata/BootCnt bs=1 count=4" would do it (Assuming you've mounted the bootdata partition )
The BCB file is similar in that if the secure bootloader boots into the recovery partition for any reason, it will write to that file and will always boot into the recovery partition until that file is cleared. The shell command to clear that file is "dd if=/dev/zero of=/bootdata/BCB bs=1 count=1088"
The bootdata partition just contains a standard vfat filesystem so you just mount it normally.
And for the love of your god do not delete those files! If you do then booting from internal memory will continue to boot into the recovery partition until they are replaced. You would be able to boot from an SD card to replace them though.
Click to expand...
Click to collapse
Yup. On the NookColor these had the same functions. Lived on /rom instead of /bootdata however.
Note: My CWM image doesn't probably handle BCB or bootcnt yet (I do in my CM9 image but that is another thing )
nemith said:
Yup. On the NookColor these had the same functions. Lived on /rom instead of /bootdata however.
Note: My CWM image doesn't probably handle BCB or bootcnt yet (I do in my CM9 image but that is another thing )
Click to expand...
Click to collapse
My Ubuntu image does not mount this partition.
bauwks said:
Maybe some of you guys have figured this out already but it's probably important to note for people developing custom recovery or boot ROMs.
And for the love of your god do not delete those files! If you do then booting from internal memory will continue to boot into the recovery partition until they are replaced. You would be able to boot from an SD card to replace them though.
Click to expand...
Click to collapse
Yep-- this is all taken care of in cm9
Update: I don't think you mentioned, but for completeness, there's also the serial file in /rom at devconf/DeviceId that will trigger a rom reformat if it goes missing. there are also some edge conditions that will trigger recovery/flashing such as the presence of certain update.zip files on SD. Also SD boots are treated differently by default, don't increase the boot count, etc. In short, this is very similar to how NookColor works with the added disadvantage of having to deal with, rather than simply ignore or remove, these various "go to recovery' conditions.
I can verify that Bauwks script works and allows internal booting without a bootloop.
Nemith, if you find the time can you add something like this to your CWM recovery.img? I think just adding the /bootdata mount and dd calls to the init.rc file should work. I was going to build my own CWM .img but figured you already had the source code handy.
I'de like to dabble in a CM7 port soon, while CM9 and Ubuntu ports are in-work
Thanks for all your hard work guys!
CWM recovery bootloop
bauwks said:
And for the love of your god do not delete those files! If you do then booting from internal memory will continue to boot into the recovery partition until they are replaced. You would be able to boot from an SD card to replace them though.
Click to expand...
Click to collapse
I flashed cm9 alpha 0.2 on my nook tablet using the nook tablet recovery apk. It booted into cyanoboot, however it had an error message that said disc majic error. I noticed I had put the wrong boot image on my sd card from the alpha 0.1. I rebooted 8 times and booted into cwm. Now in cwm I flashed a backup of my tablet. I then made the common mistake of clicking reboot recovery. Then trying to fix the bootloop into cwm recovery while unaware of the sevarity of what I was doing I went into mounts and storage and formated each bootdata, cache, data, emmc, rom, and system. I just restored my backup again and now I know what I need to do. My stock Nook recovery was overwriten when I clicked reboot recovery. Also I formated my rom folder and that might have contained my serial number and info.
I basicaly deleted my partions. while stuck in the cwm boot loop. Can you please send me or send me the link to a step by step way that I can get my nook tablet 16gb stuck in the cwm boot loop back to normal.
I tried using fastboot but I dont know the commands to open it. Also I dont know how to use adb either. I have a 2gig, and a 256 mb micro sd. I have a windows pc. Can you show me step by step how to restore those partions, how to do it on adb or fastboot, or the update zip method. I need help as soon as possible. Thanks.
Its similar to this
This seems like the only place folks are looking at bcb in much detail, so I thought I'd post an observation: on the simple touch, if you boot from noogie after issuing an "erase and deregister" command from the OS, the bcb file contains command strings.
I don't know what reads the strings, but after erase and deregister, bcb seems to be used to tell the device to run recovery:
recovery --wipe_data
is an ascii string from bcb on a deregistered and not yet rebooted glowworm - I put the noogie disk in, did the erase and deregister, then dumped the partitions once it came back up.
the command flags available in recovery as of cupcake are documented at
http://www.netmite.com/android/mydroid/cupcake/bootable/recovery/recovery.c
Just wanted to bump this so more people know about it, because I didn't and I reformat my /bootdata.
Can anyone make an image of it for restore purposes?
An image of /factory would be nice as well But less important as we're all (likely) using CM.
edit
Actually disregard this.. I have the nook hd+, but the /bootdata format info will probably be handy for any nook device.
Don't format bootdata or factory!
roustabout said:
This seems like the only place folks are looking at bcb in much detail, so I thought I'd post an observation: on the simple touch, if you boot from noogie after issuing an "erase and deregister" command from the OS, the bcb file contains command strings.
I don't know what reads the strings, but after erase and deregister, bcb seems to be used to tell the device to run recovery:
recovery --wipe_data
is an ascii string from bcb on a deregistered and not yet rebooted glowworm - I put the noogie disk in, did the erase and deregister, then dumped the partitions once it came back up.
the command flags available in recovery as of cupcake are documented at
http://www.netmite.com/android/mydroid/cupcake/bootable/recovery/recovery.c
Click to expand...
Click to collapse
pbassjunk said:
Just wanted to bump this so more people know about it, because I didn't and I reformat my /bootdata.
Can anyone make an image of it for restore purposes?
Click to expand...
Click to collapse
To fix the Recovery Boot Loop caused by invalid/missing BCB and BootCnt in /bootdata, flash Succulent's flashable_fix_bootloop.zip posted at his blog http://iamafanof.wordpress.com/2013...-1-jellybean-sdcard-img-for-nook-tablet-0110/ (see under heading "I am stuck in a recovery boot loop?").
An image of /factory would be nice as well But less important as we're all (likely) using CM.
Click to expand...
Click to collapse
/factory contains a backup copy of stock ROM as well as a backup copy of the device data in /rom partition (romdata.zip), the latter includes data that is unique to each Nook (such as MAC address, security certificate, etc.) and hence is not replaceable with a copy from another Nook.
...
Don't format bootdata or factory!
Click to expand...
Click to collapse
Nor /romdata. See http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for more info.
I created a flashable zip as well, which should reset that partition to a stock (zero-count) state. Hopefully it's not unique per device (I don't think it is, as I've used this successfully on two distinct devices.)
Is a fix being baked into any official roms, CM and the like? I don't mind the workaround via scripting, but the two I bought and modded I gave as gifts, so when they break (they both have) I definitely hear about it and receive the units back again for fixing.
ZIP is attached. Please let me know if it works or doesn't work for you, should you end up using it.
weasel5i2 said:
I created a flashable zip as well, which should reset that partition to a stock (zero-count) state. Hopefully it's not unique per device (I don't think it is, as I've used this successfully on two distinct devices.)
Is a fix being baked into any official roms, CM and the like? I don't mind the workaround via scripting, but the two I bought and modded I gave as gifts, so when they break (they both have) I definitely hear about it and receive the units back again for fixing.
ZIP is attached. Please let me know if it works or doesn't work for you, should you end up using it.
Click to expand...
Click to collapse
Having trouble with the /bootdata/BCB/ and my nook hd+ booting into recovery. Am I just supposed to flash the fix to the SD card boot partition?
tinkering said:
Having trouble with the /bootdata/BCB/ and my nook hd+ booting into recovery. Am I just supposed to flash the fix to the SD card boot partition?
Click to expand...
Click to collapse
You might want to see leapinlar's tip #10 in his post http://forum.xda-developers.com/showpost.php?p=35811322&postcount=1 for the Nook HD/HD+.
digixmax said:
You might want to see leapinlar's tip #10 in his post http://forum.xda-developers.com/showpost.php?p=35811322&postcount=1 for the Nook HD/HD+.
Click to expand...
Click to collapse
Thanks for the link to leapinlar's post. That helps me to understand the problem and fix a bit better. I didn't see the zip that seemed to fit my situation on his post. I did a SD install non-rooted and I see only only emmc fixes on his post. I tried your fix with these steps and I must have done something wrong. Maybe you could point me in the right direction.
DL, unzip, write image to sd using PC(could only write the .img, don't know what to do with the folder) , put SD into nook HD+, try to boot= no boot
Does the device have to be rooted to flash the repair zip? I don't think I am utilizing the fix properly.
tinkering said:
...
DL, unzip, write image to sd using PC(could only write the .img, don't know what to do with the folder) , put SD into nook HD+, try to boot= no boot
Does the device have to be rooted to flash the repair zip? I don't think I am utilizing the fix properly.
Click to expand...
Click to collapse
No, the device does not have to be rooted to get flashed.
If this is your first time trying to boot off SD, it's possible that your HD+ is one of the units that have difficulty booting off SD card -- see http://forum.xda-developers.com/showthread.php?t=2288688.
Is your device still on stock ROM and stock Recovery?
digixmax said:
No, the device does not have to be rooted to get flashed.
If this is your first time trying to boot off SD, it's possible that your HD+ is one of the units that have difficulty booting off SD card -- see http://forum.xda-developers.com/showthread.php?t=2288688.
Is your device still on stock ROM and stock Recovery?
Click to expand...
Click to collapse
Sorry, I probably should have updated my last post. I was attempting to flash the repair incorrectly. Unfortunately, I have a new problem and have moved my question to the "[Q][Panic] HD+ won't boot, can access CWM SD but can't mount sdcard or emmc" thread.
The device would boot from SD. Was running CM10.2 and CWM recovery. The trouble I am having now is that I can't flash anything from the SD in CWM recovery because it wont mount the SD. (See details in thread referenced above.)
Thanks
So my phone is in a bootloop. I flashed CWM recovery via Odin to try to mount the internal storage since i have some things i need to recover before flashing new rom. in CWM under "mounts and storage" i tried everything, but nothing would show up in a computer. Also, mounting system says "Error mounting system" and adb devices doesn't recognize my device now with CWM. it did with stock recovery though, when put in adb mode
edit: flashed original revocery, got adb working, found some adbfileexplorer.jar file from the forums, that shows my device and some files/folders, eg /efs, /preload , cache etc. so they are not the files i'm looking for.
And when writing adb shell in cmd, i get "- exec '/system/bin/sh' failed: No such file or directory (2) -" error
Try philz recovery and aroma file manager to access the data partition.
A sudden boot loop in normal use usually means one or more of the partitions are corrupt, so you may not be able to access data.
boomboomer said:
Try philz recovery and aroma file manager to access the data partition.
A sudden boot loop in normal use usually means one or more of the partitions are corrupt, so you may not be able to access data.
Click to expand...
Click to collapse
Ok well now i got to use adb and via command "adb pull /" i pulled everything there was (This is the right command to do it, right?)
but only two folders, sys and tmp were pulled, none of which contain any relevant data, it would appear
THIS PROCESS WILL ERASE ALL YOUR DATA
I encrypted my HTC ONE MAX last day and because of TWRP error in decrypting my partitions,Like:
Code:
Mount /SYSTEM.error
Mount /DATA error
I decided to decrypte my phone but as I said, TWRP recovery Didn't found any partion on my internal strong.
The solution is simple :
1.Download stock HTC stock recovery :
Stock Recovery Sense 6 - Latest
Stock recovery 3.23.401.1 (Google Drive Download Link) (it's for international version - Find more in other threads)
2.Boot into bootloader -> Fastboot
Use your ADB :
Code:
fastboot flash recovery recovery_t6ul-3.23.401.1.img
3. Go to your Setting -> Backup & Reset and Reset Your device
your device will reboot and recovery will ERASE ALL YOUR DATA
Now You have Non-encrypted Device
4.in final step you could flash TWRP again Like:
Code:
fastboot flash recovery twrp-2.8.7.0-t6ul.img
Another option is using TWRP...
Go into the Wipe settings,
Select Format Data,
Type Yes when prompt
And when is complete, complete a Factory Reset under the Wipe settings.
Don't forget that it will wipe internal storage so you will need to have a copy of the ROM on the external storage to flash..
tapPeD from my haNdhEld cOmpuTeR
andrewjt19 said:
Another option is using TWRP...
Go into the Wipe settings,
Select Format Data,
Type Yes when prompt
And when is complete, complete a Factory Reset under the Wipe settings.
Don't forget that it will wipe internal storage so you will need to have a copy of the ROM on the external storage to flash..
tapPeD from my haNdhEld cOmpuTeR
Click to expand...
Click to collapse
When your device is encrypted, TWRP Can't mount your internal storage!
It should decrypt with stock recovery first...
e12ror said:
When your device is encrypted, TWRP Can't mount your internal storage!
It should decrypt with stock recovery first...
Click to expand...
Click to collapse
It does when you format the data.. I was encrypted and read this technique in a separate HTC forum.
tapPeD from my haNdhEld cOmpuTeR
andrewjt19 said:
It does when you format the data.. I was encrypted and read this technique in a separate HTC forum.
tapPeD from my haNdhEld cOmpuTeR
Click to expand...
Click to collapse
I tried all that ways, even adbshell, but it was the only way!
But thanks for your notice...
please help
I'm in this problem
my device got encrypted
i cannot flash any rom any recovery
i were using nusensesix rom
with CWM 6.0.4.8
MY HBOOT IS 2.49
S-ON
t6u
803e black one max
tampered unlocked
emmc looks alive
device boot to rom but give me message DECRYPT STORAGE
and when it reset phone it goes to cwm recovery and when i try to wipe
it wipes everything except DATA partition
giving me error:
Code:
[HTML]ERROR MOUNTING /DATA
SKIPPING FORMAT
E: UNKNOWN VOLUME FOR PATH [ /SD-EXT]
ERROR MOUNTING /SDCARD/.ANDROID_SECURE!
SKIPPING FORMAT[/HTML]
when flashing stock recovery or twrp it reboots again to cwm recovery
i got mad with all these errors
please try to help me to figure out this problem and solve it .
Hi I by mistake erased the Userdata partition using fastboot and now it is unable to mount /data when ever I try to flash a new ROM or just open TWRP and try to wipe it. Also tried using the repair feature in TWRP but no luck. Help is much needed.
[EDIT]
It was fixed by Changing the File Partition to xFAT or FAT and then back to Ext4.
Hi all, I need a little help, I've unlocked bootloader and installed twrp recovery (that's wiped data on the phone and I've reinstalled apps and accounts).
The guide i was following ask to reboot and boot twrp recovery (working) and to install magisk zip file copied from PC to internal memory
I copied magisk in internal memory (root and download folders) but in TWRP I can't see the storage i get from PC, only different folders.
I tried also adb sideload D:\Android\Magisk-v21.2.zip directly from PC but i get errors on mounted file systems yrying to install files i think, I tried to check and mount file systems in TWRP advanced options but I can't mount them ...
How can I install Magisk ?
Thanks for help
blackalex1 said:
Hi all, I need a little help, I've unlocked bootloader and installed twrp recovery (that's wiped data on the phone and I've reinstalled apps and accounts).
The guide i was following ask to reboot and boot twrp recovery (working) and to install magisk zip file copied from PC to internal memory
I copied magisk in internal memory (root and download folders) but in TWRP I can't see the storage i get from PC, only different folders.
I tried also adb sideload D:\Android\Magisk-v21.2.zip directly from PC but i get errors on mounted file systems yrying to install files i think, I tried to check and mount file systems in TWRP advanced options but I can't mount them ...
How can I install Magisk ?
Thanks for help
Click to expand...
Click to collapse
You must copy files from PC to /temp folder
FSadino said:
You must copy files from PC to /temp folder
Click to expand...
Click to collapse
I don't have a temp folder, only Alarms, Android, DCIM...., Ringtones and Whatsup folders, should I create it ? Then i can see it in twrp ?
By the way upgraded twrp to 3.4.0.2
Tried to create temp but I can't see It obvously in twrp as the rest of the folders, only mounted filesystem is metadata
go in twrp to advanced wipe --> format data partition to ext2 --> wait --> when done format back to ext4 --> wait --> now see if your OS recognizes the USB android device. try usb replugging if not --> now you should see a new partion where you can write in your file explorer on HOST OS.
n3tk1d said:
go in twrp to advanced wipe --> format data partition to ext2 --> wait --> when done format back to ext4 --> wait --> now see if your OS recognizes the USB android device. try usb replugging if not --> now you should see a new partion where you can write in your file explorer on HOST OS.
Click to expand...
Click to collapse
Ok since It is wiping data partition and I'm under mobile connection I'll do this in the next couple of days back home. Just to confirm, I can see internal memory partition from host OS without problems, I can copy files from OS to mobile. The problem is that rebboting in recovery TWRP I can't see FROM MOBILE that partition and folders, so I can't access magisk file I copied ...
With your suggestion do you mean that the new formatted partition is visible both in TWRP and OS ?
blackalex1 said:
Ok since It is wiping data partition and I'm under mobile connection I'll do this in the next couple of days back home. Just to confirm, I can see internal memory partition from host OS without problems, I can copy files from OS to mobile. The problem is that rebboting in recovery TWRP I can't see FROM MOBILE that partition and folders, so I can't access magisk file I copied ...
With your suggestion do you mean that the new formatted partition is visible both in TWRP and OS ?
Click to expand...
Click to collapse
Which guide are you following?
Hw4ng3r said:
Which guide are you following?
Click to expand...
Click to collapse
I found many and they are all similar...
- Unlock boot loader
- Install recovery TWRP
- Reboot in recovery (sometimes from phone other guides from image on PC)
- install magisk copied from OS from twrp recovery
Everything is clear except for I can't access the data partition from TWRP in the last step so I can't see the copied magisk file and I can't mount the partitions in TWRP (i get an error)
A couple of guides:
Root OnePlus 7T Pro (hotdog) and Install TWRP Recovery 3.4.0 (androidweblog.com)
Download Latest Magisk zip 21.2 and Magisk Manager 8.0.4 and Root your phone (getdroidtips.com)
In the second one they use the sdcard partition but I don't have sdcard on 7T Pro ...
You can point me to a different method if available to get magisk installed ...
Thanks for the help
blackalex1 said:
Ok since It is wiping data partition and I'm under mobile connection I'll do this in the next couple of days back home. Just to confirm, I can see internal memory partition from host OS without problems, I can copy files from OS to mobile. The problem is that rebboting in recovery TWRP I can't see FROM MOBILE that partition and folders, so I can't access magisk file I copied ...
With your suggestion do you mean that the new formatted partition is visible both in TWRP and OS ?
Click to expand...
Click to collapse
so when you do as i said you are in twrp cos you booted to it. twrp will read and be able to access your phones storage. you are not wiping the data partion but are formating it to ext2 and then back to ext4 (still do backup as data will be lost). this enables twrp to circumvent the oxygen decryption / format. NOW and only AFTER THAT dont reboot (dont), but now your HOST can copy the desired magisk to the phone that is still in twrp RECOVERY MODE. Thus you can now install it with twrp since twrp can now access and read the recently copied image. anyways i wont do it. i used a patched magisk image. was the only thing that ultimately worked for a clean rooting and it didnt even unlock the /system_boot and /vendor partions but it works. find in the oneplus 7t pro guideds forum topic your corresponding magisk image and flash it to disk with fastboot flash boot magisk-patched.img. that worked pretty well when you use the right android version 10.0.x.etc.
actually, wtf do i know. i just followed this thread:
[Guide] How to Root OnePlus 7T Pro with TWRP
thanks for this detailed root process, I've been looking for this for around 3days. (my OP7t pro is coming today will try this root method)
forum.xda-developers.com
Clearly stated in the TWRP thread, decrypting OOS is not working. And I wouldn't even bother formating data.
In order to flash zip is TWRP you most execute;
"adb push magisk.zip /cache",
then in TWRP go into that folder and flash the file.
Or you can do patched image method, you can find guides in guides section.
Some basic researching would also help.
Lossyx said:
Clearly stated in the TWRP thread, decrypting OOS is not working. And I wouldn't even bother formating data.
In order to flash zip is TWRP you most execute;
"adb push magisk.zip /cache",
then in TWRP go into that folder and flash the file.
Or you can do patched image method, you can find guides in guides section.
Some basic researching would also help.
Click to expand...
Click to collapse
PERFECT thank you very much, got only a couple of warnings at the end:
failed to mount /system_root (permission denied)
failed to mount /vendor (permission denied)
But It seems correct.
I will check for patched image to better understand what is tha advantage compared to the standard one.
blackalex1 said:
PERFECT thank you very much, got only a couple of warnings at the end:
failed to mount /system_root (permission denied)
failed to mount /vendor (permission denied)
But It seems correct.
I will check for patched image to better understand what is tha advantage compared to the standard one.
Click to expand...
Click to collapse
Those errors are nothing to worry about since it's not possible to modify those partitions on stock.
I tried rooting my lenevo tab M10 hd and flashed a incorrect boot img as I am new to rooting and bricked up my device then from some where I got the correct boot img and recovered my device but now I am unable to use its internal storage , its shows some random letters when I open the file manager can you guys help me out resolving this issue.