DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS
Install instructions:
1. Download an arbitrary SM-A127F firmware zip package on SamMobile.com, whose Android version is 11
2. Flash by Heimdall by PIT partitions or by Odin by BL, AP, CP, and CSC tar packages
3. Back to the stock ROM > go to Developments settings > allow OEM unlocking (Developments settings could be enabled by tapping 7~10 times somewhere in About Device)
4. If OEM unlocking is unseen to you, take software updates first
5. Also inside Developments settings, enable USB debugging
6. Download the TWRP image, and unzip.
7. Hold <VolUp>+<VolDn> with device tethered to USB-C with your PC
8. Hold <VolUp> to unlock OEM
9. Hold <VolUp>+<VolDn> again with device not disconnected of USB-C
10. Press <VolUp> without holding to enter Download mode
11. Open ODIN to flash the downloaded TWRP in AP slot with my TWRP image.
12. Hold <VolDn> + <Power> to shut down, then Hold <VolUp> + <Power> to reboot to TWRP
Important: device must boot directly to recovery or stock recovery will be restored if you boot direct to OS.
13. 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"
}
What is working:
Mounting, flashing
What is not working:
Please do let me know.
Device tree: Links removed and thread locked. @edward0181 Check PM.
CHANGELOG:
25-10-2021:
Changed FSTAB issues, Sideload/MTP and ADB issues.
Reserved free space on dynamic partitions to flash GAPPS if needed.
21-10-2021:
Initial post, issues to be expected.
Nice work.
edward0181, thank you for making all this possible! I have a problem though: I want to install LineageOS, I have successfully got TWRP running after repackaging your .img into .tar and flashing it with Odin but I cannot go any further: the SD card contents cannot be read from TWRP and ADB sideloading does not work as well, because the USB device is not detected by the PC when TWRP is working. There is no way to upload any image. Also wiping does not work with lots of "failed to mount" and "block device required" messages. I tried OTG also and it does not work as well. No way to flash the OS.
hoba22 said:
odin not detect file After unzip
Click to expand...
Click to collapse
You have to repackage it into .tar archive.
No further help needed, my phone is bricked. I tried to follow the instructions on how to root it, presuming that was needed to move on in my intention to install Lineage OS. I think now it's completely hopeless: it's stuck on the welcome screen (the one with the warning sign) and not detected as a USB device at all at any stage. It just reboots after several minutes, and that's all. All I can do is force to reboot it by pressing power+vol down. No other key combinations work. So bad I can't get into the download mode without USB connection. Or can I?
OK. I have managed to unbrick it by prying the case open, unscrewing some screws inside to reveal the battery connector and disconnecting the battery. Then I have reconnected it, partially closed the case to make the buttons available, pushed vol up+vol down and connected the USB. Voila: it was in the download mode. I have reset the bootloader and reuploaded the stock OS. Fine, now back to the LineageOS problem.
Question: Is it possible to upload the LineageOS image with Odin so that it will be availabe for flashing with TWRP (USERDATA partition may be)? Or may be it's possible to flash LineageOS directly with Odin, like the stock image?
@uluruman You are not the only one who has ADB sideload issues, DEVI will fix them soon enough... One dude reported his phone wasn't getting detected in SIDELOAD mode but in normal RECOVERY mode was. You probably have same issues, you can try pusshing LinageOs.img file to ROOT directory which isn't encrypted and can safely install Linage then.
Push the file by ADB PUSH
Apache config:
adb push LinageOs.img /root/
After pushing LinageOs Image file you can follow my guide for installing it normaly...
Installing TWRP and LInageOS
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS # knox_bit_warranty:0x1 # # Your warranty is now void # # You have been warned. # # I will laught at you if you...
forum.xda-developers.com
Covering some misleading theories and issues with our A12
This thread will be updated regularly. If you don't agree with something comment and if I was proven wrong I will update the thread. Please don't comment or chat here if it isn't releated with something I said. If you need further help with...
forum.xda-developers.com
deleted
Thanks LAST_krypton! Unfortunately the push method does not work for me either, the filesystem is read-only. I guess the phone must be rooted but this is not possible: the magisk-patched file causes the infinite reboot cycle. I tried it again, in case I did something wrong. I also tried some other methods (sideloading via the fastboot, repackaging the stock firmware) but none of them work for one reason or another. Actually just getting rid of the forcefully installed Russian software (which is included in the prism.img) would be enough for me, but I could not accomplish it either.
As of the LineageOS: may be there is some other dir is available both via adb and TWRP, which does not require rooting?
uluruman said:
Thanks LAST_krypton! Unfortunately the push method does not work for me either, the filesystem is read-only. I guess the phone must be rooted but this is not possible: the magisk-patched file causes the infinite reboot cycle. I tried it again, in case I did something wrong. I also tried some other methods (sideloading via the fastboot, repackaging the stock firmware) but none of them work for one reason or another. Actually just getting rid of the forcefully installed Russian software (which is included in the prism.img) would be enough for me, but I could not accomplish it either.
As of the LineageOS: may be there is some other dir is available both via adb and TWRP, which does not require rooting?
Click to expand...
Click to collapse
Disable READ_ONLY restrictions either by TWRP or ADB. You can follow my guide for rooting, it is for the whole enviorment and you have the patched VBMETA with BOOT image.
Unlocking the bootloader and rooting
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS # knox_bit_warranty:0x1 # # Your warranty is now void # # You have been warned. # # I will laught at you if you...
forum.xda-developers.com
LAST_krypton said:
Disable READ_ONLY restrictions either by TWRP or ADB. You can follow my guide for rooting, it is for the whole enviorment and you have the patched VBMETA with BOOT image.
Unlocking the bootloader and rooting
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS # knox_bit_warranty:0x1 # # Your warranty is now void # # You have been warned. # # I will laught at you if you...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks, I'll try it!
CHANGELOG:
25-10-2021:
Changed FSTAB issues, Sideload/MTP and ADB issues.
Reserved free space on dynamic partitions to flash GAPPS if needed.
Guys, is there another way to reboot into recovery after flashing? I just can't catch the moment when I should press power+vol up, it seems just impossible, it always gets into the red text warning screen, hangs for a while then vibrates and goes on into Android. Strangely enough, I could boot into TWRP with the first release, and can't with this second one. It wasn't easy with the first one but I could do it two or three times. Now I can't do it at all. Strange. Anyway, I'll keep on trying before making conclusions.
uluruman said:
Guys, is there another way to reboot into recovery after flashing? I just can't catch the moment when I should press power+vol up, it seems just impossible, it always gets into the red text warning screen, hangs for a while then vibrates and goes on into Android. Strangely enough, I could boot into TWRP with the first release, and can't with this second one. It wasn't easy with the first one but I could do it two or three times. Now I can't do it at all. Strange. Anyway, I'll keep on trying before making conclusions.
Click to expand...
Click to collapse
Just when you see the warning screen stop pressing vol + and then after goes from warning PBL unlock screen to LOGO hold vol + again. You can try "adb reboot recovery" from download but dout that will work.
Once you get good like me, you can reboot and with your fingers still enter download mode or recovery mode in 5s
LAST_krypton said:
Just when you see the warning screen stop pressing vol + and then after goes from warning PBL unlock screen to LOGO hold vol + again. You can try "adb reboot recovery" from download but dout that will work.
Click to expand...
Click to collapse
OK, I'm trying it this way:
1. Flash TWRP then power off manually (auto reboot is turned off in Odin)
2. Push Vol+, then Power and hold them
3. The first logo screen appears
4. The warning screen appears and immediately disappears because I'm still holding the Power button (no time to release the vol+ button here)
5. The second logo screen with the red text and the yellow warning sign appears
6. It vibrates and the Android boots up (just the single Samsung logo on the screen)
At which stage I should release the Vol+ button? May be I should release the Power button at some point?
P.S.: adb does not work in the Download mode, of course. I tried.
LAST_krypton said:
Once you get good like me, you can reboot and with your fingers still enter download mode or recovery mode in 5s
Click to expand...
Click to collapse
I already know the trick to get into the Download mode with fingers at any point But still no recovery mode.
Well, sorta... I've found a reliable way to get at least into the stock recovery mode:
1. Connect the phone to PC
2. Turn it off
3. The charging screen appears, with the bolt sign
4. Once the bolt sign changes to the percent counting, press and hold Power + Vol up
5. Hold the buttons until it gets into the recovery mode
Works all the time for me. This method does not work after flashing TWRP though, it just hangs on the second logo screen. I suspect it actually tries to run TWRP at this point but can't, and it's the software problem, because once I allow it to go through and restore the original Recovery program, it boots into Recovery just fine following these steps. But never gets to TWRP.
Quite often after that TWRP loading attempt the phone becomes always hanging at this second logo screen on every boot, without holding any buttons, so I have to reflash the AP partition completely to restore it (reflashing recovery.tar.md5 does not help). I don't know what's wrong here.
My phone is SM-A127F with the SER (Russian) v3 firmware.
uluruman said:
Well, sorta... I've found a reliable way to get at least into the stock recovery mode:
1. Connect the phone to PC
2. Turn it off
3. The charging screen appears, with the bolt sign
4. Once the bolt sign changes to the percent counting, press and hold Power + Vol up
5. Hold the buttons until it gets into the recovery mode
Works all the time for me. This method does not work after flashing TWRP though, it just hangs on the second logo screen. I suspect it actually tries to run TWRP at this point but can't, and it's the software problem, because once I allow it to go through and restore the original Recovery program, it boots into Recovery just fine following these steps. But never gets to TWRP.
Quite often after that TWRP loading attempt the phone becomes always hanging at this second logo screen on every boot, without holding any buttons, so I have to reflash the AP partition completely to restore it (reflashing recovery.tar.md5 does not help). I don't know what's wrong here.
My phone is SM-A127F with the SER (Russian) v3 firmware.
Click to expand...
Click to collapse
Are you sure you are flashing the correct TWRP.tar.md5 file, if you are on android10 that could be the reason why, try on latest android 11.
LAST_krypton said:
Are you sure you are flashing the correct TWRP.tar.md5 file, if you are on android10 that could be the reason why, try on latest android 11.
Click to expand...
Click to collapse
No it's Android 11, and the file I downloaded is the latest from this thread, it's recovery.tar.zip (inside of which is recovery.tar.7z, inside of which is recovery.tar.md5). It all seems correct. Anyway I'll leave the attempts for now, because more v3 firmwares have been published today on samfw.com. I have installed the non-Russian one which is pretty clean of suspicious government-pushed apps, it'll do for now. At least for now.
Great thanks to edward0181 for the job!
I am trying to get TWRP on my SM-A127F TWRP SEK, but I am facing some errors:
1. I have successfully unlocked OEM, and am able to enter the download mode
2. I am successfully flashing the provided .tar.md5 archive into AP with Odin 3.14.4 with auto reboot turned off. After getting the success in Odin, I turn the device off by pressing <VolDn> + <Power>, then try to boot into TWRP but stuck on the welcome screen just like uluruman mentioned
3. First, I disconnected and reconnected the battery and was able to get into Download mode once again, but then found a better way: press <VolDn> + <Power> to restart. When the screen gets black I quickly press <VolUp> + <VolDn> and insert the USB before I can see the intro logo to get directly into Download mode (might be helpful for someone).
4. After several attempts I am still not able to boot into TWRP, getting either stuck on the welcome screen or somehow booting into the stock OS.
5. I then tried to root the device (chances are, TWRP might work on a rooted device) following this guide:
Unlocking the bootloader and rooting
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS # knox_bit_warranty:0x1 # # Your warranty is now void # # You have been warned. # # I will laught at you if you...
forum.xda-developers.com
6. After successfully flashing the magisk patched and turning the phone off I can see only the charging screen (the first one, without numbers) and it doesn't get any further before force reboot (<VolDn> + <Power>).
7. Following the same logic as with step 3, I tried to press <VolUp> + <Power> during the reload when the screen is black and it worked, I managed to load the bootloader. However, after the factory data reset and whipping cache partition I get stuck on the welcome screen, as with step 2.
8. Flashing the original firmware works well.
Any ideas of what else should I try to finally install TWRP? The primary goal is to install LineageOS or AOSP.
Related
Hi,
I was trying to flash TWRP, but now I am stuck with flashing TWRP logo after rebooting or powering the phone on.
I am unable to get to the fastboot.
STEPS I did before brick:
1. unlocked OEM via official way
2. flashed TWRP
3. after that my phone was reset however most of the apps was missing, I was trying to do factory reset once again but it failed with the message "Data partition was heavily damaged"
4. I re-locked EOM
5. brick as mentioned above
Please help, I have the phone only two weeks and I have no idea how to fix this without fastboot.
Thank you.
Meiton said:
Hi,
I was trying to flash TWRP, but now I am stuck with flashing TWRP logo after rebooting or powering the phone on.
I am unable to get to the fastboot.
STEPS I did before brick:
1. unlocked OEM via official way
2. flashed TWRP
3. after that my phone was reset however most of the apps was missing, I was trying to do factory reset once again but it failed with the message "Data partition was heavily damaged"
4. I re-locked EOM
5. brick as mentioned above
Please help, I have the phone only two weeks and I have no idea how to fix this without fastboot.
Thank you.
Click to expand...
Click to collapse
Sounds like you flashed the 3030 version of TWRP. Download the 3020 version and put it in your fastboot folder. Plug in the USB to PC
Hold power and volume up untill the phone reboots. While it's still off immediately change to power and volume down and hold till it goes into fastboot (bootloader)
Now fastboot flash recovery TWRP.img
With the 3020 version.
Unplug the USB and hold power and volume up until it says the phone is booting.. let go and TWRP will load.
Go to Wipe / format data / type yes
Reboot to system and your all set
Sent from my Nexus 6P using Tapatalk
clsA said:
Sounds like you flashed the 3030 version of TWRP. Download the 3020 version and put it in your fastboot folder. Plug in the USB to PC
Hold power and volume up untill the phone reboots. While it's still off immediately change to power and volume down and hold till it goes into fastboot (bootloader)
Now fastboot flash recovery TWRP.img
With the 3020 version.
Unplug the USB and hold power and volume up until it says the phone is booting.. let go and TWRP will load.
Go to Wipe / format data / type yes
Reboot to system and your all set
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
So I've tried that but the phone is still booting to recovery (flashing TWRP logo) no matter what.
Basically the phone is always on now because if hold the power button (or any other combination) for a few second it will just reboot back.
I have an access only to ADB, but I am not able to boot to bootloader at all, it seems the bootloader is damaged somehow.
Also that warning about unlocked OEM doesn't have that text saying "hold volume up to boot to recovery" etc. like before brick.
Hi there,
Try using the Huawei Multi Tool with the Unbrick option : https://forum.xda-developers.com/honor-8/development/tool-huawei-multi-tool-team-mt-t3523923
Speaking from experience, this little fellow helped me recover my phone when I bricked it ON DAY ONE after failed root attempt... (Derp)
Let me know if it helped you
(Leave a thanks if it did )
EDIT : This tool is also useful if you want to get lazy whilst rooting. I use it constantly when flashing diffrent bits and pieces
Clearly follow My steps To unbrick and get normal device ::
Step 1 ::
Download the full firmware of your device.
Step 2 :
make sure that your bootloader is in unlocking state
Follow the video blindly ::: https://youtu.be/OMKDnBqbi3U?list=PL...eT9J26lkefvVkK
don't panic of mobile.
Step 3 :: done ..enjoy u did it
--------------------------------------------------------------------------
If you bricked on nougat then follow the below steps
step one :::
download the downgrade package to mm .
then extract the zip and open the update.app using HuaweiUpdateextrator in that select recovery and extract
1.now, boot your device into fastboot and flash the recovery (Optional)(try this if it said incompatible version on recovery)
2. on your sd card and make a folder "dload" . and copy the update.app which we have extracted earlier
3.the switch off the device and press all three buttons you will be reboot into recovery and done . you device will be okey
Meiton said:
So I've tried that but the phone is still booting to recovery (flashing TWRP logo) no matter what.
Basically the phone is always on now because if hold the power button (or any other combination) for a few second it will just reboot back.
I have an access only to ADB, but I am not able to boot to bootloader at all, it seems the bootloader is damaged somehow.
Also that warning about unlocked OEM doesn't have that text saying "hold volume up to boot to recovery" etc. like before brick.
Click to expand...
Click to collapse
Booting to the bootloader is just a timing issue
Phone must be hooked to PC with USB
And volume up and power till it goes black
Then immediately volume down and power and Hold untill the bootloader loads
Keep trying until you get it
Sent from my Nexus 6P using Tapatalk
clsA said:
Booting to the bootloader is just a timing issue
Phone must be hooked to PC with USB
And volume up and power till it goes black
Then immediately volume down and power and Hold untill the bootloader loads
Keep trying until you get it
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I appreciate your help but I've tried it multiple times always with the same result.
I also can use "adb reboot bootloader", but it will reboot again to stuck recovery.
DJ Daemonix said:
Hi there,
Try using the Huawei Multi Tool with the Unbrick option : https://forum.xda-developers.com/honor-8/development/tool-huawei-multi-tool-team-mt-t3523923
Speaking from experience, this little fellow helped me recover my phone when I bricked it ON DAY ONE after failed root attempt... (Derp)
Let me know if it helped you
(Leave a thanks if it did )
EDIT : This tool is also useful if you want to get lazy whilst rooting. I use it constantly when flashing diffrent bits and pieces
Click to expand...
Click to collapse
I've tried that, but I am still stuck as that tool is using fastboot as every other tool to flash .img files.
Thank you for the tip though.
Plug phone into computer with USB, then hold down power + volume down until it eventually boots into bootloader. I had the same scenario as you and that's how I got into the bootloader. You can flash either a good TWRP or the stock recovery, either one will work.
Root your "Barns & Noble Nook 7" BNTV450 using Magisk's Patch Boot Image File option.
BE CAREFUL!
There are always risks involved when you start messing around with a device.
If something goes wrong, you may end up with a non-working "bricked" device.
This is especially true when you start flashing partitions. (In this case boot.)
Disclaimer
I am not responsible for your non-working "bricked" devices.
I have a few of my own.
Requirements
Barns & Noble Nook 7" BNTV450
A computer with working adb and fastboot
USB cable
WiFi connection
Magisk Manager (Link below)
Stock boot image (Link below)
Tested on:
BNTV450-v1.0.2-20161230 Security patch October 5, 2016
BNTV450-v2.0.4-20170927 Security patch August 5, 2017
BNTV450-v2.0.5-20170110 Security patch November 5, 2017 ota update
macOS 10.13.x
Windows 7 Pro
Steps
Unlock bootloader
Boot Magisk patched boot image
Pull stock boot and recovery images from device
Use Magisk to patch pulled stock image
Test and flash new patched boot image
Notes:
Google updates were needed to get everything working correctly.
PlayServices and WebView
Mac users. As with some other devices, I had to unplug and plugin the USB cable between some of the fastboot commands.
fastboot flash boot patched_boot.img and fastboot boot bntv4-recovery.img
Magisk:
There have been a lot of changes in Magisk since I originally used it to root.
Way too many to mention so, just the basics that apply to this device.
Newer versions of Magisk use the Download directory instead of creating and using the MagiskManager directory.
Some apps search for this directory and used it to determine if the device is rooted.
If you previously used Magisk to root and have a MagiskManager directory, you will want to delete it.
To update Magisk Manager.
Use the update option, it will download and install the newest version.
To update Magisk.
The safest way is to patch the boot image again. Test and flash.
The Direct Install option works but, may lead to a non-desirable outcome.
To uninstall Magisk.
Test boot your original boot image to make sure it works.
Check with Magisk Manager, it should say Magisk not installed.
If so, then flash your stock boot image back using fastboot.
If your stock boot image will not boot, then you are stuck with Magisk patched boot images.
Hardware Keys:
Power and Volume Up = Recovery Mode
Power and Volume Down = Factory Mode
It will show on the bottom Left (Sideways on the top left) Detecting boot mode. With bootloader unlocked it flashes this message very fast so you might not see it.
I still can not produce the same results continuously across mine. The newer ones, that came with v2.0.5 seem to work but, the older ones still it's a 50 % chance if I can get it to work. The bricked ones, do not seem to register the key combo on boot.
Files Needed
Magisk
xda Magisk forum. Link
Magisk and MagiskManager Official github downloads. Link
Boot Images
Magisk patched boot image downloads. Link
Stock recovery and boot image downloads. Link
Credits and Thank You:
@topjohnwu - The creator and brilliant mind behind Magisk.
Everyone who has helped me learn through the years.
Last edited 23.Sep.2018
"QUICK" Guide - BNTV450 Nook 7
Unlock Bootloader
THIS WILL VOID YOUR WARRANTY.
Unlocking the bootloader WILL wipe and Factory Reset your device. Make sure to copy, backup and logout of everything before you begin.
Note: adb and fastboot need to be installed and working.
On device
Go to Settings - About and tap on the build number seven times to enable Developer options.
Go to Settings - Developer options and Enable OEM unlocking and USB debugging
Connect to computer and Allow USB debugging?
On computer
Code:
adb reboot bootloader
Wait for device to boot into fastboot mode then.
Code:
fastboot flashing unlock
On device
Follow the prompts on the device.
Unlock bootloader?
If you unlock the bootloader,you will be able to install custom operating system software on this phone.
A custom OS is not subject to the same testing as the original OS, and can cause your phone and installed applications to stop working properly.
To prevent unauthorized access to your personal data,unlocking the bootloader will also delete all personal data from your phone(a "factory data reset").
Press the Volume UP/Down buttons to select Yes or No.
Yes (Volume UP):Unlocking(may void warranty).
No (Volume Down): Do not unlock bootloader.
After it returns to fastboot mode, use the power button to turn off, unplug it from computer and then turn on.
It will reboot a few times, including an Erasing... screen.
Once device reboots, run through the initial setup.
Note: Sometimes mine would get stuck on the nook .... animation screen. Give it a few minutes (I wait at least 5 minuets) then power off and power back on.
Note: You will now have the annoying boot delay and "Orange State" message.
Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
"QUICK" Guide - BNTV450 Nook 7
Root using Magisk.
MagiskManager 6.0.0 Download
Magisk 17.2 patched v2.0.5 Download
Using Magisk Manager and the provided Magisk patched boot image.
Note: When booting an image from "fastboot", you should not see the initial "orange boot" screen.
Make sure to grant permission if and when prompted on device.
Some of the adb and fastboot commands may require input on the device.
On device
Go to Settings - About and tap on the build number seven times to enable Developer options.
Go to Settings - Developer options and Enable USB debugging
Connect to computer and Allow USB debugging?
On computer
Code:
adb reboot bootloader
Wait for device to boot into fastboot mode then.
Code:
fastboot boot m172_v205_boot.img
Wait for device to boot then.
Reminder. Make sure to grant permission if and when prompted on device.
Code:
adb install -r MagiskManager-v6.0.0.apk
adb shell su -c "dd if=/dev/block/mmcblk0p7 of=/sdcard/bntv4-boot.img"
adb shell su -c "dd if=/dev/block/mmcblk0p8 of=/sdcard/bntv4-recovery.img"
adb pull /sdcard/bntv4-boot.img
adb pull /sdcard/bntv4-recovery.img
Test the images you just made.
Code:
adb reboot bootloader
Wait for device to boot into fastboot mode then.
Code:
fastboot boot bntv4-recovery.img
Wait for device to boot into recovery mode then.
On device
In Stock Recovery use the volume down key to highlight Reboot to bootloader and press the power button.
Wait for device to boot into fastboot mode then.
On computer
Code:
fastboot boot bntv4-boot.img
Wait for device to boot then.
On device:
If you haven't setup WiFi, do so now.
Open MagiskManager
Tap on Install
Select Install
Select Patch Boot Image File
Tap on Internal storage
- Note: If Internal storage is not displayed. Tap on the 3-dot menu (upper right corner) and select Show SD card.
Scroll down and tap on bntv4-boot.img
When Magisk is done patching the image file, select CLOSE
You can close MagiskManager as well.
Copy and test your Magisk patched boot image.
On computer
Code:
adb pull /sdcard/download/patched_boot.img
adb reboot bootloader
Wait for device to boot into fastboot mode then.
Code:
fastboot boot patched_boot.img
On device
Open MagiskManager
Note: You should see that Magisk is installed and active.
To do a quick check.
On Computer
Code:
adb shell
[email protected]:/ $su
[email protected]:/ #exit
[email protected]:/ $exit
If it worked, and you are ready to say goodbye to stock Non-root.
Code:
adb reboot bootloader
fastboot flash boot patched_boot.img
fastboot boot bntv4-recovery.img
Once it's booted into Recovery, unplug the device.
On device
In Stock Recovery use the volume down key to highlight Wipe cache partition and press the power button.
-- Wiping /cache...
Formatting /cache...
Cache wipe complete.
Then with Reboot system now highlighted press the power button.
You are now rooted and running Magisk.
Last edited 23.Sep.2018
Links to my shell logs.
Unlock bootloader. Pastbin
Root. Pastbin
volume button does not react
Hi
unlocking does not work
As mentioned in the other discussion, the volume up button does not seem to react and so the unlocking does not work. Also one user suggested using the reset button after pressing the volume up button for the unlock; that also does not work for me
Do u have any other suggestions to unlock ?;
arrmusic said:
Hi
unlocking does not work
As mentioned in the other discussion, the volume up button does not seem to react and so the unlocking does not work. Also one user suggested using the reset button after pressing the volume up button for the unlock; that also does not work for me
Do u have any other suggestions to unlock ?;
Click to expand...
Click to collapse
I never ran into this problem. So short answer - No.
Can you point me to that other discussion?
What do you get if you run fastboot oem lks
fastboot oem unlock is supported on this device. You could give that command a try and see if there is a difference.
Not sure what you have tried.
I would start with "Factory Reset" in stock recovery. Skip through the initial setup and try again.
Note: Developer option menu has a toggle at the top, make sure it is turned On.
Sent from my BNTV450 using XDA Labs
Volume up button not recognised while fastboot unlock
Hi
Here is the discussion thread that I was referring to where people are stuck with unresponsive volume up button for fastboot unlock
https://forum.xda-developers.com/nook-7/help/nook-rootable-t3510289
I didn't do the factory reset. So maybe I will do that and see if it works.
unlock not working
Hi
Just to further update you on your reply; i did a factory reset and tried to unlock the bootloader but i get to the same problem; the volume button does not respond; so stuck with the message 'press the volume up button to unlock the bootloader'
I did the fastboot oem lks and that commands executes well and it gives me a OK output.
Cheers & New year greetings!
Any update on the unlock issue
Hi
Is there any update on the unlock issue i reported some time back? My last update on this was executing the command => 'I did the fastboot oem lks and that commands executes well and it gives me OK output.'
not sure if my last update was interpreted in the right way; it does nothing when i type fastboot oem lks except saying it is OK (which i suppose is the expected output of fastboot oem lks). So i do not know how to get around the volume keys not being recognised to go further in unlocking
I still can not use the volume keys for the unlock as it does not seem to react. just stuck a bit on this
@arrmusic I guessed it it looked more like this.
Code:
fastboot oem lks
...
(bootloader) lks = 1
OKAY [ 0.000s]
finished. total time: 0.000s
lks = 0 would be unlocked.
I am looking for a way to un-brick these. I think that may be the best way to correct the button problem also.
What os version are you running? (BNTV450-vx.x.x-20xxxxx)
What do you get when you run fastboot flashing get_unlock_ability ?
Tested a few things tonight.
I was NOT able to re-lock the bootloader on either of my rooted devices.(BNTV450-v2.0.4)
Found some more inconsistencies with power and volume key boot combinations. (Among other things.)
"FAILED (remote: not support on security)" apparently is not just for unlocked devices.
Sent from my BNTV450 using XDA Labs
not able to unlock yet
Hi
Many thanks for your reply.
I seem to have the software version v1.0.2;
I tried to find by googling v2.0.4 but i am not able to find that security update anywhere to download; do you have the v2.0.4 file? can i have it somehow?
I ran the commands u had mentioned in your previous reply.
fastboot flashing get_unlock_ability
...
(bootloader) unlock_ability = 16777216
OKAY [ 0.012s]
finished. total time: 0.012s
fastboot oem lks
...
(bootloader) lks = 1
OKAY [ 0.004s]
finished. total time: 0.008s
What is the origin of the boot.img?
What is the origin of the boot.img? I'd rather not just flash something without knowing where its come from.
74178951237895321 said:
What is the origin of the boot.img? I'd rather not just flash something without knowing where its come from.
Click to expand...
Click to collapse
v2.0.3 boot came from a supposed "N" rom for this device and was the first boot image I was able to make bootable. It was still API 23 "M" by the way.
I would have to find and unpack the original file to see what I edited to make it bootable.
All others are "dd" copies from my own device(s).
I am working on updating the OP and the "Quick Guide"
Boot Images
Download Magisk 15.3 patched v2.0.5 (Preferred and current boot image.)
Sent from my ford using XDA Labs
Scatter file for Mediatek MT8163, opening the tablet
Can you post the scatter file for the Mediatek MT8163?
I've been trying to make my own image dumps for the Nook 7, but have run into an issue where the device won't stay in a readable mode for SP Flash Tools long enough while the battery is still connected. So, the solution for most phones is to disconnect the battery and have it powered over USB only so that it won't go past the preloader and into the charging mode.
But I can't get the darned thing open! My phone has a similar style housing and I had to use a suction cup on the glass while prying at the edges to gain access. But for the Nook 7 its just not working.
Edit: This started while trying to soft load TWRP to make the image dumps. When I do
Code:
fastboot boot twrp.img
It tells me that the kernel address lies outside of memory. Its possible to supply an address to load it at with the fastboot command which you are supposed to learn from the scatter file. I found what I thought was a valid MT8163 scatter file but using the address found within did not fix the issue.
I forgot you mentioned that you didn't pull the original image from your device yourself. I've been trying to root this without relying on images from others. Your latest guide to pulling and modifying your own boot.img is a decent enough middle ground for me to use. Thanks.
@74178951237895321
Sent from my Nexus 7 (2013) using XDA Labs
I was able to get a successful root by following the steps in this thread in combination with those mentioned in this one. ipdev, just to satisfy my curiosity, where did you find this "N rom" image?
ipdev said:
So we hit a snag using Magisk 15.4+ to patch a stock boot image on this device.
Click to expand...
Click to collapse
So, I was dumb and went through with updating Magisk without checking this thread first, and now my tablet's stuck in a bootloop that I can't seem to get out of. @ipdev, do you have any ideas on how this happened/how to get out of it? The tablet can't get past the "Orange state your device has been unlocked etc. etc." screen, and I can't get it to boot into recovery either (using Power+Volume Down, is the combination something else on this tablet?). fastboot won't discover it either, probably because it reboots within seconds and never gets to a point where it could be recognized. I'm thinking of letting it bleed out until its battery dies (unfortunately, the battery is soldered and glued in, so I can't just disconnect it), and checking on it in the morning to see if it will be cooperative enough to let me flash the modified Magisk image.
@saagarjha
I have a few in the same condition. As you noticed, the battery is soldered in so the best you can do is disconnect the screen. (Connector to the right of battery.)
One of these days, I was going to try sp flashtools to see if I could recover one of mine. (I'm not sure if it works with these.)
Sent from my Nexus 5 using XDA Labs
I let the tablet run out of battery and then plugged it back in again and it immediately got stuck in the same bootloop, so it looks like it's actually bricked rather than just pretending. I think SP Flash Tools is the way to go at this point; we'd have to find a functioning preloader driver and scatter file to do that, however. It might be possible to simulate disconnecting the battery by shorting the battery's leads, but I'm not sure if this would work (or is even safe to do).
I was having trouble with unlocking the boot loader on my v1 launch version of this Nook. Recently I dropped it and got a new one via the replacement plan - this one was marked 'v2', came with a 2.x firmware that I wasn't able to even get on my launch Nook 7.
Anyway, this one unlocked without any problems. Thought this might be helpful to anybody having trouble unlocking the bootloader. Consider the revision of the Nook you have. Maybe the solution here is flashing the v2 firmwares to the v1? Hard to say.
unable to unlock
So I did "adb reboot bootloader" and the tablet rebooted and says "=> FASTBOOT mode..." on the screen.
I then did "fastboot flashing unlock" on the computer. Nothing happened on the device and my computer says "< waiting for device >". Could anyone please let me know what I did wrong? Thank you very much.
Update: Thread outdated. A new and working version of TWRP was posted in another Forum. Thanks.
{
"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"
}
I get this
PS: On instructions for second method you may want to mention you have to rename twrp image to recovery.img
My device is now stuck in the fastboot menu. It says I can navigate the menu using volume up and down but pressing either of those doesn't do anything and I can't seem to power off the device by holding the power button. Any suggestions on how to fix this?
laod said:
My device is now stuck in the fastboot menu. It says I can navigate the menu using volume up and down but pressing either of those doesn't do anything and I can't seem to power off the device by holding the power button. Any suggestions on how to fix this?
Click to expand...
Click to collapse
Some people have reported that touch isn't working and partitions aren't mounting properly. I tried to fix most issues and uploaded a new version. I do not own this device personally - so i can not test the fixes. Please give me feedback for the updated version.
I just got my GPD XD+ today, thanks for the TWRP build but on mine, even with the current build (2018/04/01), I can't perform any actions. Touch still seems not to work for me. I can't get past TWRP asking me "Keep System Read-only?" Let alone see if partitions are loading correctly.
Everything is in portrait mode which is awkward for this device. What about landscape? Shouldn't it be 1280x720 rather than 720x1280?
**Update**
It would appear that my touch controls are inverted... so the fix for others, seems to have inverted my own.
**Update 2***
Well... after realizing the touchscreen was reversed for me, I was able to slide the "Swipe to allow modifications" slider but after that, I chose to reboot out of recovery since the likelyhood of me hitting something by mistake with the controls reversed was high. Being very careful, I was able to tell it to reboot to system and now the system hangs at the GPD logo.. which no longer animates... I can no longer boot into anything but recovery and fastboot.
Any theories as to what has happened? Does anyone have a Clean Stock ROM of the plus model so I can start over using adb?
**Update 3**
PsyOps pointed me towards some stock images at "forum.gpd.hk/t3-the-latest-firmware-of-gpd-game-console" and I'm back in business. Had to flash more than just recovery and boot.. had to flash system as well for some reason.
Goayandi said:
Some people have reported that touch isn't working and partitions aren't mounting properly. I tried to fix most issues and uploaded a new version. I do not own this device personally - so i can not test the fixes. Please give me feedback for the updated version.
Click to expand...
Click to collapse
I have the same situation here.
It happened after unlocked the bootloader, so it's nothing to do with the recovery.
The adb commend return the error: device '(null)' not found.
I can't check the "recovery" box. It doesn't do anything. And the first methode doesn"t work
EDIT : nevermind, I did it but same problem as Busted77
laod said:
My device is now stuck in the fastboot menu. It says I can navigate the menu using volume up and down but pressing either of those doesn't do anything and I can't seem to power off the device by holding the power button. Any suggestions on how to fix this?
Click to expand...
Click to collapse
Same thing here. Now waiting for the battery to empty. What happens after that? Will it work fine and the bootloader be unlocked?
vanzan said:
Same thing here. Now waiting for the battery to empty. What happens after that? Will it work fine and the bootloader be unlocked?
Click to expand...
Click to collapse
I was being dinner and used adb commands instead of fast boot. If you have your device plugged into a computer with fastboot setup you can run "fastboot reboot" and everything should work.
vanzan said:
Same thing here. Now waiting for the battery to empty. What happens after that? Will it work fine and the bootloader be unlocked?
Click to expand...
Click to collapse
Wait for the battery runs out, then recharge, it works fine and the bootloader is unlocked, the first boot will take longer and a few reboot.
And I find that any time you issue fastboot command from you pc, the xd plus will stuck and you have to wait the battery runs out.
I installed the Magisk use fastboot method, stuck again, and need to wait for the battery runs out, recharged, and evertyhing ok then.
There's another root method on Chinese forum (flash supersu pack by recovery), since I rooted by installin Magisk, I didn't try that.
---------- Post added at 11:46 ---------- Previous post was at 11:45 ----------
laod said:
I was being dinner and used adb commands instead of fast boot. If you have your device plugged into a computer with fastboot setup you can run "fastboot reboot" and everything should work.
Click to expand...
Click to collapse
No, when I stuck in the fastboot menu, the adb command return error that no device can find, I have to unplug battery or wait for the battery runs out.
"fastboot reboot" worked perfectly for me!
Fastboot stuck
Same problem here.
I installed the drivers but got the error.
Now my device is in fastboot mode but fastboot reboot etc. don't work.. And I just can't turn it off..
Im really sad.
Windows 10 x64
So.. At least I could fix the problem, I installed the Drivers (had do disable driver signature) and installed your TWRP Mod successfully but the Screen is mirrored! U can use it but its very tricky.. I could open "Install" But if I open it, twrp could not load any data it called "0MB Space" and yeah after reboot, my GPD XD Plus DON'T start..
LeraxGER said:
So.. At least I could fix the problem, I installed the Drivers (had do disable driver signature) and installed your TWRP Mod successfully but the Screen is mirrored! U can use it but its very tricky.. I could open "Install" But if I open it, twrp could not load any data it called "0MB Space" and yeah after reboot, my GPD XD Plus DON'T start..
Click to expand...
Click to collapse
I had the same issue, could use it inverted and mirrored but after running it and not doing anything with it, I could no longer boot into system... Only into recovery. If I tried to boot into system, the boot animation would never animate and the system would hang.
See PsyOps' reply to my question of where to find a stock rom. You can either use the provided tool or you can use adb commands to reflash your system partition... At least for me I had to flash system... Flashing boot and recovery (removing TWRP) didn't work alone...
reddit.com/r/gpdxd/comments/8a50vq/gpd_xd_plus_stock_rom_available/
Busted77 said:
I had the same issue, could use it inverted and mirrored but after running it and not doing anything with it, I could no longer boot into system... Only into recovery. If I tried to boot into system, the boot animation would never animate and the system would hang.
See PsyOps' reply to my question of where to find a stock rom. You can either use the provided tool or you can use adb commands to reflash your system partition... At least for me I had to flash system... Flashing boot and recovery (removing TWRP) didn't work alone...
reddit.com/r/gpdxd/comments/8a50vq/gpd_xd_plus_stock_rom_available/
Click to expand...
Click to collapse
Thanks for the advice, I spoke with him too and he already gave me the guide how to boot into Recovery Mode and then fastboot (Hold VOL+ & On Off Untill Menu apperas, then boot into recovery, then if the android guy appears press On/Off and THEN VOL+, so you're in the normal recovery mode for all the other poor user's )
And I flashed system.img, boot and stock recovery and then it booted up..
The only thing is, that I think that the SD card won't mount correctly anytime and if I plug it to the PC, I dont see the SD card and big files (like the StockROM Update 1.10 abort before its finished).
Greetings
Contact me in discord.
Could you please close the thread and delte the download link? Not even once your TWRP worked, please don't share the file anymore. Other user's will brick their device too.
Hello how to fix a black screen caused by overheating device?i dont know how to use the stock recovery i have thr gpd boot logo but after a black screen and blue led thanks
Hi, i have a start 101 tablet with a Cortex-A9 cpu, a WM8850 chipset and a Mali-400 GPU and i do have root, it has android 4.0.3, im not very good in these things but i wanted to install google apps on this tablet, i already found a site that gives some links to some zip files for every android version, but i don't know how to install them. The site that gave those zip said that you need to boot into the recovery of the device and press install from zip, but the problem is that my recovery doesn't have any menu on it.
So 2 days ago i tried finding a way to boot into the recovery, holding the power button and volume up do not take me to the recovery, they take me to a screen which says "do you want to do system recovery? press power button before 10 seconds to confirm" and if i press the power button the tablet factory resets, if i wait 10 seconds the tablet shuts down, i also tried holding the power and volume down buttons but they just took me to normal android.
Now yesterday i found a way to boot into the recovery by using an adb command or by using an app called "Reboot manager ROOT", but the problem is that when i use abd or this app and reboot to the recovery, an android robot with a red triangle appears without any menu on it, and searching this on the internet i was told to basically press power and volume up / down untill a menu appears but i can't get this menu to show up, and since there is no menu if i hold the power button to reboot im stuck into this boot to recovery loop unless i factory reset which works and takes me back to normal android, so then i was thinking that maybe the recovery in this tablet does not exist but is that possible? im not very experienced with this but i also found out about custom recovery yesterday, so after like 5 hours on the internet i found a cwm recovery for my chipset and i saw a video on youtube that said that if you had a twrp/cwm recovery for the same chipset of your android device you can make a custom recovery for your device, the video i followed is this:
so i made this custom recovery img file now but how can i flash it? or can i just use the recovery that is already into my tablet to install the google apps?
because i searched the internet a bit and it seems that for flashing a recovery you need to go to the bootloader but i can't access this thing for some reason, power + volume down takes me to normal android so then i tried adb reboot bootloader but it also takes me to normal android, then i also tried the same app i used to reboot into recovery (reboot manager root) but pressing the reboot to bootloader buttons also does not work (it asks for root permission, i press allow and then it reboots to normal android) same with the reboot to download mode button, then as a last attemp i downloaded an app called "flashify" which basically allows to flash recovery, zip and etc, so i first tried to flash the recovery but pressing the button choose file made the app freeze, so then i tried the flash zip option to maybe flash google apps without recovey, but after choosing the zip it gets stuck at downloading 92% and the app freezes and it doesn't seem to have installed the google apps, do you know if there is any way to boot into this bootloader to flash this cwm recovery or maybe any way i can get the normal recovery to work?
i also have the tablet model url, here it is: http://www.start-tablet.it/tablet_start10_it.php
you can also get the english page version here: http://www.start-tablet.it/tablet_start10_en.php
also sorry for my bad english and bad explanation,
thanks for the help!
I also found a picture of what the normal recovery shows me, i will attach the jpg.
{
"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"
}
Update: i went to a local store and he said that the tablet doesn't have the bootloader so rip i guess
Every Android device has a bootloader, unless it gets removed by user: without a bootloader Android OS couldn't get started.
jwoegerbauer said:
Every Android device has a bootloader, unless it gets removed by user: without a bootloader Android OS couldn't get started.
Click to expand...
Click to collapse
hi and thanks for the reply, well then do you know any way i can access it? because the guy at the shop said that my tablet was too old that it didn't have one, i tried going into the bootloader with adb using the computer and also using an app on the tablet itself, both of those method don't work and they just boot normal android.
ADB deals with Android OS, whereas FastBoot deals with device's bootloader: totally different softwares.
To operate on its bootloader, device's bootloader must get made accessible, known as get unlocked: this gets enabled within Android -> Settings -> Developer options.
FYI: As with Android, recovery refers to the dedicated, bootable partition that has the recovery console installed from which you can perform specific tasks.
jwoegerbauer said:
ADB deals with Android OS, whereas FastBoot deals with device's bootloader: totally different softwares.
To operate on its bootloader, device's bootloader must get made accessible, known as get unlocked: this gets enabled within Android -> Settings -> Developer options.
FYI: As with Android, recovery refers to the dedicated, bootable partition that has the recovery console installed from which you can perform specific tasks.
Click to expand...
Click to collapse
hi, what i meant is i tried to type adb reboot bootloader into the cmd and it booted to normal android, now im going to turn on the tablet and go into the developer option to check if there is a bootloader thing to enable, so how do i unlock it? i go to the developer option and then what do i need to press?
jwoegerbauer said:
Click to expand...
Click to collapse
hi, unfortunately i didn't find any option that was talking about the OEM or the bootloader in the developer settings, i could try to attach the screenshots of all the developer settings i have, but i was also thinking that maybe the root is causing issues?
If I were you I would completely reset the tablet
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP-FILE>
jwoegerbauer said:
If I were you I would completely reset the tablet
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP-FILE>
Click to expand...
Click to collapse
ok the stockrom is on the site only problem is that well it's 404 not found, but i will try archive.org, also should i unroot first?
jwoegerbauer said:
If I were you I would completely reset the tablet
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP-FILE>
Click to expand...
Click to collapse
hi, uhm the stock firmware isn't archived on wayback machine
http://www.start-tablet.it/ftp/START-LOGO_V1.5.1_20130107.zip
also i never changed the rom, i just rooted the device a long time ago so maybe the un-root will fix stuff? if not how can i find the stock firmware?
Hi, it's me again, i know this is kinda old but since i have the same problem i will say it here, basically i gave up on this device in june of last year but now i want to try again, im still having the same issue (in recovery i see no menu, i only see the android logo with a red triangle, and yes i tried power button + volume down or up and even both, but none of this key combination made the menu show up) so im stuck and i don't know what to do, i unrooted the device to see if maybe it could affect anything but it didn't so i rooted again with kingroot.
I also have the cwm recovery made for this tablet but i can't flash it because i can't access the bootloader, i tried to boot with volume down, adb reboot bootloader, and even one app on android that reboots to bootloader if you have root (which i have), from what i found on the internet my bootloader should be unlocked because i was able to root, i also tried apps like flashify and rashr to flash the cwm recovery but they don't work, after i give them root access i tried to flash with Flashify and when i press the button to select the zip file it just hangs the application,
with Rashr it gives "Failed Execute".
+bump
jonnyprogamer said:
Hi, it's me again, i know this is kinda old but since i have the same problem i will say it here, basically i gave up on this device in june of last year but now i want to try again, im still having the same issue (in recovery i see no menu, i only see the android logo with a red triangle, and yes i tried power button + volume down or up and even both, but none of this key combination made the menu show up) so im stuck and i don't know what to do, i unrooted the device to see if maybe it could affect anything but it didn't so i rooted again with kingroot.
I also have the cwm recovery made for this tablet but i can't flash it because i can't access the bootloader, i tried to boot with volume down, adb reboot bootloader, and even one app on android that reboots to bootloader if you have root (which i have), from what i found on the internet my bootloader should be unlocked because i was able to root, i also tried apps like flashify and rashr to flash the cwm recovery but they don't work, after i give them root access i tried to flash with Flashify and when i press the button to select the zip file it just hangs the application,
with Rashr it gives "Failed Execute".
Click to expand...
Click to collapse
Hello did you try a temp recovery?
notnoelchannel said:
Hello did you try a temp recovery?
Click to expand...
Click to collapse
Hi, thank you very much for replying, no and i don't exactly know what that means, can you explain it to me? Thanks.
I just want to flash the CWM recovery because i want to sideload the Google Apps, but since i can't find a way to go into the bootloader im trying to do it from adb shell, i also tried "flash_image recovery /path/to/recovery/" but it doesn't find the flash image command.
jonnyprogamer said:
Hi, thank you very much for replying, no and i don't exactly know what that means, can you explain it to me? Thanks.
Click to expand...
Click to collapse
Hello, temp recovery is flashable anytime FROM stock recovery but will not keep as your permanent recovery.Do you want a link for it?
jonnyprogamer said:
I just want to flash the CWM recovery because i want to sideload the Google Apps, but since i can't find a way to go into the bootloader im trying to do it from adb shell, i also tried "flash_image recovery /path/to/recovery/" but it doesn't find the flash image command.
Click to expand...
Click to collapse
adb push "/path/recovery.img" "/dev/recoverymount"
can you try it on ur pc? Replace recoverymount with your recoverys partition
notnoelchannel said:
adb push "/path/recovery.img" "/dev/recoverymount"
can you try it on ur pc? Replace recoverymount with your recoverys partition
Click to expand...
Click to collapse
Thanks, how can i find my recovery partitions?
jonnyprogamer said:
Thanks, how can i find my recovery partitions?
Click to expand...
Click to collapse
Can you send me your recovery.img? I'll send your recovery mountpoints and i can port a recovery for you
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS
Code:
# knox_bit_warranty:0x1
#
# Your warranty is now void
#
# You have been warned.
#
# I will laught at you if you point the finger at me.
UNLOCKING BOOTLOADER1. Open settings app
2. Tap on about phone, and then software information
3. Tap the build number until you see a pop up that says developer options enabled
4. Go back and tap on developer options
5. Enable OEM unlocking
6. Reboot your phone
7. After reboot power off the phone
8. Conect the usb cable to your pc and phone, then hold VOL + and VOL - at the same time
9. There should be two options, you want the unlock mode (VOL UP LONG PRESS)
10. After holding VOL UP for 10 seconeds you should get in to the screen that will let you unlock the OEM so now just press VOL UP.
11. Phone will reboot, during setup conect to the internet to avoid perenormal mode
12. Check in developer options if oem unlocking is grayed out, if it isn't factory reset data and wipe chace partiton will have to be done.
ROOTING1. Download the fimware you are currently running https://samfw.com/
2. Copy the AP file to your phone
3. Install magisk canary version, download app-debug.apk and install https://github.com/topjohnwu/magisk_files/tree/canary
4. Open magisk, check for updates
5. Tap install and then tap select and patch a file and find the AP file you transferd from your pc
6. In the download folder of the phone will be a file named magisk_patched-xxxxxxx.tar
7. Transfer it to your pc
8. Boot the phone in to download mode, manualy or from adb shell (adb reboot download)
9. Open odin and go in to options and uncheck auto reboot
10. Click on AP or PDA and select the patched magisk file and click start
11. Reboot the phone manualy after odin does it's thing (VOL - and POWER at the same time for 7 seconeds).
After the phone turns off, amedietly boot in to recovery (Vol + and POWER at the same time)
12. Make a factory data reset and whipe cache partition
13. Reboot in to system
14. Conect to interent during setup
15. Enable dev options by taping on build number 7 time. OEM UNLOCKING must be grayed out.
16. Install the same magisk (app-debug.apk)
17. Ignore the pop up that says magisk needs inital setup and click on update
18. After updateing, go back in to magisk and if you get the pop up for aditional setup, ignore it and go straight to install
19. Click on direct install
20. After flash reboot
21. Check in developer options if oem unlocking is grayed out, if it isn't the instalation process will have to be followed again
THIS IS A OLD METHOD OF INSTALLING TWRP
INSTALLING TWRP, I RECOMEND FOLOWING MY LATEST GUIDE
Installing TWRP and LInageOS
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS # knox_bit_warranty:0x1 # # Your warranty is now void # # You have been warned. # # I will laught at you if you...
forum.xda-developers.com
INSTALLING TWRP OLD METHOD# If you are not on the A125F or A127F you might have to do a crossflashing fimware operation
1. Make sure you are on android 11 and that you pre rooted your phone already
2. Download twrp from here https://forum.xda-developers.com/t/aosp-11-unofficial-samsung-sm-a125f-twrp.4317131/
3. Boot in to download mode
3. Go in to odin and uncheck auto reboot
4. Click on AP or PDA and select the twrp file you have downloaded, click start
5. Manualy reboot (VOL - and POWER for 7 seconeds)
6. Boot in to twrp before booting in to system (VOL + and power) or this process will have to be repeated
7. Swipe allow modifications of system and reboot
Links
Samsung Firmware Download - Lastest official firmware update
Samsung Firmware Download ⭐ Official and fast update ⭐ Lastest and old version ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
GitHub - topjohnwu/magisk_files at canary
(Deprecated) Magisk File Host. Contribute to topjohnwu/magisk_files development by creating an account on GitHub.
github.com
[AOSP-11] [OFFICIAL] Samsung SM-A125F TWRP
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS Install instructions: 1. Download an arbitrary SM-A125F firmware zip package on SamMobile.com, whose Android...
forum.xda-developers.com
Credits
@edward0181 twrp
LAST_krypton said:
Code:
Your warranty is now void
# I'm not responsible for any damage done to your device
# If you point the finger at me, I will laught at you
Click to expand...
Click to collapse
LAST_krypton said:
Code:
# Your warranty is now void
# I'm not responsible for any damage done to your device
# If you point the finger at me, I will laught at you
UNLOCKING BOOTLOADER
Code:
1. Open settings app
2. Tap on about phone, and then software information
3. Tap the build number until you see a pop up that says developer options enabled
4. Go back and tap on developer options
5. Enable OEM unlocking
6. Reboot your phone
7. After reboot power off the phone
8. Conect the usb cable to your pc and phone, then hold VOL + and VOL - at the same time
9. There should be two options, you want the unlock mode (VOL UP LONG PRESS)
10. VOL UP for bootloader unlock
11. Phone will reboot, during setup conect to the internet to avoid perenormal mode
ROOTING
Code:
1. Download the fimware you are currently running https://samfw.com/
2. Copy the AP file to your phone
3. Install magisk canary version, download app-debug.apk and install https://github.com/topjohnwu/magisk_files/tree/canary
4. Open magisk, check for updates
5. Tap install and then tap select and patch a file and find the AP file you transferd from your pc
6. In the download folder of the phone will be a file named magisk_patched-xxxxxxx.tar
7. Transfer it to your pc
8. Boot the phone in to download mode, manualy or from adb shell (adb reboot download)
9. Open odin and go in to options and uncheck auto reboot
10. Click on AP or PDA and select the patched magisk file and click start
11. Reboot the phone manualy after odin does it's thing (VOL - and POWER at the same time for 7 seconeds)
12. After the phone turns of, amedietly boot in to recovery (Vol + and POWER at the same time)
13. Make a factory data reset and whipe cache partition
14. Reboot in to system
15. Conect to interent during setup
16. Install the same magisk (app-debug.apk)
17. Ignore the pop up that says magisk needs inital setup and click on update
18. After updateing go back in to magisk and if you get the pop up for aditional setup, ignore it and go straight to install
19. Click on direct install
19. After setup reboot
INSTALLING TWRP
Code:
If you are not on the A125F model you will have to disable MTK Secure Boot and Secure Download and might also downgrade SW REV and then install A125F fimware
1. Make sure you are on android 11 and that you pre rooted your phone already
2. Download twrp from here https://forum.xda-developers.com/t/aosp-11-unofficial-samsung-sm-a125f-twrp.4317131/
3. Boot in to download mode
3. Go in to odin and uncheck auto reboot
4. Click on AP or PDA and select the twrp file you have downloaded, click start
5. Manualy reboot (VOL - and POWER for 7 seconeds)
6. Boot in to twrp before booting in to system (VOL + and power) or this process will have to be repeated
7. Swipe allow modifications of system and reboot
Links
Samsung Firmware Download - Lastest official firmware update
Samsung Firmware Download ⭐ Official and fast update ⭐ Lastest and old version ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
GitHub - topjohnwu/magisk_files at canary
(Deprecated) Magisk File Host. Contribute to topjohnwu/magisk_files development by creating an account on GitHub.
github.com
[AOSP-11] [OFFICIAL] Samsung SM-A125F TWRP
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS Install instructions: 1. Download an arbitrary SM-A125F firmware zip package on SamMobile.com, whose Android...
forum.xda-developers.com
Credits
@edward0181 twrp
Click to expand...
Click to collapse
Thanks for the wide guide. TWRP build has been updated in my post as well.
All works as it should.
May I ask you to post a guide on howto install Lineage GSI with twrp?
Cheers
edward0181 said:
Thanks for the wide guide. TWRP build has been updated in my post as well.
All works as it should.
May I ask you to post a guide on howto install Lineage GSI with twrp?
Cheers
Click to expand...
Click to collapse
Ok sure, I will do it when I get time.
Cheers
Is it possible to make A125U into A125F? That would be the only way for me i believe. It worked on my A115U when i flashed A115U1 onto it but i cant seem to find it for the A12.
Rularick5 said:
Is it possible to make A125U into A125F? That would be the only way for me i believe. It worked on my A115U when i flashed A115U1 onto it but i cant seem to find it for the A12.
Click to expand...
Click to collapse
It is possible, and it is the only way for you to do what?. To flash A125F fimware on A125U you have to go through a really complicated method to succeeded, you would have to dismantle the phone and force boot it in to the preloader and disable MEDIATEK's and samsung's own security locks to trick the rollback prevantion (RP) and downgrade SW REV so you can flash A125F fimware. And forgot to mention, you have to go trought some litle pain with SBL aswel.
Wow, seems like a lot. i just want root and twrp. I wonder why it was so eqsy on A11. Thank you for the reply.
Rularick5 said:
Wow, seems like a lot. i just want root and twrp. I wonder why it was so eqsy on A11. Thank you for the reply.
Click to expand...
Click to collapse
Thats the way I think it should be done, I don't know other methods. This guide is for every model if you are not following the installing twrp part.
LAST_krypton said:
Thats the way I think it should be done, I don't know other methods. This guide is for every model if you are not following the i gues
Click to expand...
Click to collapse
The issue is i have is with oem unlock missing from developer options. Ive tried the methods above. Plus, as we all know, no oem unlock, no root. Im looking to see if there are working alternatives.
Rularick5 said:
The issue is i have is with oem unlock missing from developer options. Ive tried the methods above. Plus, as we all know, no oem unlock, no root. Im looking to see if there are working alternatives.
Click to expand...
Click to collapse
See here, https://forum.xda-developers.com/t/...ing-theories-and-issues-with-our-a12.4336999/
LAST_krypton said:
Thats the way I think it should be done, I don't know other methods. This guide is for every model if you are not following the installing twrp part.
Click to expand...
Click to collapse
Except this doesnt work for every model as the A125U Model is different. Is there any way you can elaborate on how to "force boot it in to the preloader and disable MEDIATEK's and samsung's own security locks to trick the rollback prevantion (RP) and downgrade SW REV so you can flash A125F fimware." Maybe a separate guide can be made? Because i can get it in download mode but flashing AP using odin fails and i have no idea how to disable mtk secure boot which shows enabled and my sw rev says : B1 NS1 K1 S1
Could you be a little clearer on how to perform these steps?
1. Download the fimware you are currently running https://samfw.com/
do i download the same firmware my phone is running?
2. Copy the AP file to your phone
do i copy the ap file to my phone using odin?
3. Install magisk canary version, download app-debug.apk and install https://github.com/topjohnwu/magisk_files/tree/canary
do i download this to my pc or phone?
4. Open magisk, check for updates
5. Tap install and then tap select and patch a file and find the AP file you transferd from your pc
6. In the download folder of the phone will be a file named magisk_patched-xxxxxxx.tar
7. Transfer it to your pc
8. Boot the phone in to download mode, manualy or from adb shell (adb reboot download)
9. Open odin and go in to options and uncheck auto reboot
10. Click on AP or PDA and select the patched magisk file and click start
wiiddakidd said:
Could you be a little clearer on how to perform these steps?
1. Download the fimware you are currently running https://samfw.com/
do i download the same firmware my phone is running?
2. Copy the AP file to your phone
do i copy the ap file to my phone using odin?
3. Install magisk canary version, download app-debug.apk and install https://github.com/topjohnwu/magisk_files/tree/canary
do i download this to my pc or phone?
4. Open magisk, check for updates
5. Tap install and then tap select and patch a file and find the AP file you transferd from your pc
6. In the download folder of the phone will be a file named magisk_patched-xxxxxxx.tar
7. Transfer it to your pc
8. Boot the phone in to download mode, manualy or from adb shell (adb reboot download)
9. Open odin and go in to options and uncheck auto reboot
10. Click on AP or PDA and select the patched magisk file and click start
Click to expand...
Click to collapse
You donwload the same fimware your phone is running and copy the AP.tar.md5 fimware file to your phone. Install cannary version of magisk and patch the AP.tar.md5. Transfer magisk_patched-xxxxxxx.tar back to your pc and in odin flash it in AP slot.
wiiddakidd said:
Except this doesnt work for every model as the A125U Model is different. Is there any way you can elaborate on how to "force boot it in to the preloader and disable MEDIATEK's and samsung's own security locks to trick the rollback prevantion (RP) and downgrade SW REV so you can flash A125F fimware." Maybe a separate guide can be made? Because i can get it in download mode but flashing AP using odin fails and i have no idea how to disable mtk secure boot which shows enabled and my sw rev says : B1 NS1 K1 S1
Click to expand...
Click to collapse
A guide for that, maybe some other day. It would require phone disasembely to force PRELOADER. And what error do you when flashing AP file?
Hello, long time forum lurker here but never posted anything before. I recently have been having a headache from several different AT&T phones all being restricted to the point where I can't do anything with them. I have an SM-A125U from att that doesn't have an OEM unlock option.
Through my Ubuntu computer I can run some basic adb and fastboot commands but nothing that actually helps me. Still though the fact that I can make the phone go to recovery and fastboot make me wonder if there is really nothing I can do about this. Frija also won't let me get a firmware file for my device.
Not totally sure how it works but somebody said AT&T encrypts the software so you can't access specific functions. I am just wondering is there anything I can do through adb or fastboot to fix this issue in any way, or if my only real option is to just buy a new unlocked phone or something?
I explained it here, if it still doesn't work then comment again here.
Covering some misleading theories and issues with our A12
This thread will be updated regularly. If you don't agree with something comment and if I was proven wrong I will update the thread. Please don't comment or chat here if it isn't releated with something I said. If you need further help with...
forum.xda-developers.com
Thanks I am definitely a few steps closer now. I got the Android 10 installed, and got the OEM unlock option finally. Turning that on and powering off my phone afterward, I started it up with the Vol + - and then the power button. After pressing up it booted into a somewhat different looking download mode where it shows the warranty status and stuff. Just to make sure I'm not doing anything out of order here, what file is it looking for now to unlock the bootloader? The OEM unlock option is still there and activated right now after following the bootloader guide in this post.
so it seems like it's doing something weird I think.
This is the information it gives me on this download screen:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-A125U
CURRENT BINARY: SAMSUNG OFFICIAL
FRP LOCK: OFF
KG STATUS: CHECKING
MTK SECURE BOOT: ENABLE(0)
WARRANTY VOID: 0X0(0X0)
RP SWREV: B2 NS2 K2 S2
SECURE DOWNLOAD: ENABLE
CASS: 0X1
DID : 0E7724BBE578
CARRIER_ID: ATT
drcroc said:
Thanks I am definitely a few steps closer now. I got the Android 10 installed, and got the OEM unlock option finally. Turning that on and powering off my phone afterward, I started it up with the Vol + - and then the power button. After pressing up it booted into a somewhat different looking download mode where it shows the warranty status and stuff. Just to make sure I'm not doing anything out of order here, what file is it looking for now to unlock the bootloader? The OEM unlock option is still there and activated right now after following the bootloader guide in this post.
so it seems like it's doing something weird I think.
This is the information it gives me on this download screen:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-A125U
CURRENT BINARY: SAMSUNG OFFICIAL
FRP LOCK: OFF
KG STATUS: CHECKING
MTK SECURE BOOT: ENABLE(0)
WARRANTY VOID: 0X0(0X0)
RP SWREV: B2 NS2 K2 S2
SECURE DOWNLOAD: ENABLE
CASS: 0X1
DID : 0E7724BBE578
CARRIER_ID: ATT
Click to expand...
Click to collapse
You have to get in to the menue of dowload mode where you can chose where to go. Vol + longpress will send you to the screen for unlocking PBL and Vol + normal will send you to odin protocol mode.
LAST_krypton said:
You have to get in to the menue of dowload mode where you can chose where to go. Vol + longpress will send you to the screen for unlocking PBL and Vol + normal will send you to odin protocol mode.
Click to expand...
Click to collapse
I don't know if I'm just missing something but I can't figure that out so far. This phone isn't reacting to the buttons like the guides suggested. I have the phone powered off to get it to do any of this first, but power and vol + goes to the stock recovery screen. Power and vol + and vol - makes it go to a warning screen about installing a custom OS and asks if I want to continue or not. Long pressing vol+ doesn't do anything from that screen, and only opens odin mode. plugging in the phone to my computer and only holding vol+ and vol- didn't do anything at all, and also just long pressing vol+ didn't work either Is the phone supposed to be powered off already when I long press vol+, or on a different screen from the blue yes or no screen you see before odin mode?
drcroc said:
I don't know if I'm just missing something but I can't figure that out so far. This phone isn't reacting to the buttons like the guides suggested. I have the phone powered off to get it to do any of this first, but power and vol + goes to the stock recovery screen. Power and vol + and vol - makes it go to a warning screen about installing a custom OS and asks if I want to continue or not. Long pressing vol+ doesn't do anything from that screen, and only opens odin mode. plugging in the phone to my computer and only holding vol+ and vol- didn't do anything at all, and also just long pressing vol+ didn't work either Is the phone supposed to be powered off already when I long press vol+, or on a different screen from the blue yes or no screen you see before odin mode?
Click to expand...
Click to collapse
Make sure OEM unlocking and usb debuging have applayed. Boot in to system, reset developer options and then enable them back. After that enable OEM unlocking and usb debuging and restart. After reseting and booting back in to SYSTEM power off the phone and hold VOL + and VOL - at the same time. UNLOCKING MENUE should now be shown and you will be able to get in to it by VOL + longpress.