Linking already compiled FOTA binary working with S8500XPKJ1 bootloaders only.
It needs the same files on User partition as described in tutorial.
Remember that you flash it on your own risk.
It's version 3.0 - may work, or may not.
http://code.google.com/p/badadroid/downloads/detail?name=S8500_XPKJ1_bl_univ_bootv.0.3.zip
Rebellos said:
Linking already compiled FOTA binary working with S8500XPKJ1 bootloaders only.
It needs the same files on User partition as described in tutorial.
Remember that you flash it on your own risk.
http://code.google.com/p/badadroid/downloads/detail?name=S8500XPKJ1_armlinuxboot.zip
Click to expand...
Click to collapse
Thanks! I'll try it tomorrow!
Sorry if it's an idiotic or noobish post, but I just want to make sure:
I have to install S8500XPKJ1 (bada 2.0) then flash this FOTA and I should be able to load Android just like before, right? Thanks!
i flashed the new 2.0 fw with this fota and got no problems. Will install android and report if any issues.
thanks Rebellos
I tried with the above given FOTA file
i had no problems in booting into bada
but while booting ANDROID i get oly white screen--tried about 10 times...
may be cld hav tried wrongly
Anyone else able to boot ANDROID using this fota with mentioned new firmware in phone..
indiamachi said:
I tried with the above given FOTA file
i had no problems in booting into bada
but while booting ANDROID i get oly white screen--tried about 10 times...
may be cld hav tried wrongly
Anyone else able to boot ANDROID using this fota with mentioned new firmware in phone..
Click to expand...
Click to collapse
Whitescreen with any text on it?
What key combination are you using? Ain't sure if it haven't changed.
Recovery mode is Menu+VolUp
Download mode Menu+VolDown (or Menu alone should work too)
Normal kernel boot is CallKey
Otherwise Bada does boot.
Please test it carefully, I couldn't do it by myself yet.
Rebellos said:
Linking already compiled FOTA binary working with S8500XPKJ1 bootloaders only.
It needs the same files on User partition as described in tutorial.
Remember that you flash it on your own risk.
http://code.google.com/p/badadroid/downloads/detail?name=S8500XPKJ1_armlinuxboot.zip
Click to expand...
Click to collapse
which kind of installations ? install on Nand or Memory Card ?
Flashed with S8500XPKJ1
Flashed the fota available in the first post
Copied all the needed files to boot Android.. but what I obtained is the Wave that:
Start Bada regurarly
Start the process to install Android (VolumUp+Menu+EndCall) and show me a screen with some pixels around.
What should be?
Please get me a picture of that screen.
I should have done it before, sorry.
And sorry for the bad quality too.
Here you are a photo just to give you an idea.
http://img507.imageshack.us/img507/5314/dsci0005gd.jpg
@Rebellos
A plain white screen with some pixel dots
I used Vol down+lock+power button for going into download mode
Then used power+menu+vol up button thnkin cld boot into android first time (set up the file system)
Then used power+call key to boot into android
But it dint work
FYI, i used the NAND method...
Regards,
Indiamachi
This is to boot ARM Linux or Android?
I think title may lead to misinterpretation
UP,
android ;]
Android is ARMLinux kernel + Zygote & Dalvik AFAIK.
I'm working on solution.
It really doesn't work. When you try to get into the Recovery Mode or to lauch Android, pixels are displayed like in the bada 1,2 version, but there after these pixels the Galaxy S logo is displayed, and here no reaction.
i tried it... but it doesn't work ! it doesn't even show galaxy logo. And whr can i get the files needed?
AltairBW said:
It really doesn't work. When you try to get into the Recovery Mode or to lauch Android, pixels are displayed like in the bada 1,2 version, but there after these pixels the Galaxy S logo is displayed, and here no reaction.
Click to expand...
Click to collapse
john1995 said:
i tried it... but it doesn't work ! it doesn't even show galaxy logo. And whr can i get the files needed?
Click to expand...
Click to collapse
Answer has given :
Rebellos said:
I'm working on solution.
Click to expand...
Click to collapse
Cannot start Android on Bada 2.0
I am using Modifed S8500XPKJ1. I have loaded the new fota.
I have loaded the android filesystem in memory card and tried to start it but everytime after the flickering the galaxy logo do not appears / android do not start when I press Call+Power button.
I've updated first post with v2.0 - please test it now.
Rebellos said:
I've updated first post with v2.0 - please test it now.
Click to expand...
Click to collapse
Thanks
will try it out after phone battery is full
Related
[Q]Sony BootLoop Solution??
Only post here is somebody get the solution of bootloop problem..
i think that the only think that we can do is wait for someone that posts an update.zip to be flashed via recovery, obviously for the different versione..mine is 16gb 3g (europe sgpt114it)...your is?
I understand that we're all happy we got root, but you gotta be careful running out and deleting/freezing everything without a proper way to restore!
Also, these question threads should all be moved to general.
sorry for posting here, but I can see many people facing this similar boot loop issue & other threads are getting flooded, that is why I posted here..
Lets try to find some way as of now to get rid of this frustrating boot loop !!!
EDIT:
Can anyone tell me, what exactly should be present inside those update.zip?
I am not able to unzip or see the content of signed-nbx03_001XXXXXXXXX.zip, giving some error !!!
it gives errors because the zip is encrypted
what if someone posts a full rom dump and i flash all the files manually via adb?
I tried with another zip and now in Recovery Mode , getting below error:
E:signature verification failed
Installation aborted.
xperiax10.awesome said:
I tried with another zip and now in Recovery Mode , getting below error:
E:signature verification failed
Installation aborted.
Click to expand...
Click to collapse
on that boot loop - do you have access to adb? for a second or two?
br
condi
i had, now it just hangs on the sony logo on the boot..the only hope left is an original update.zip for my model...
condi said:
on that boot loop - do you have access to adb? for a second or two?
br
condi
Click to expand...
Click to collapse
No..
sent via awesome aRc (rooted 2.3.4)
sapphire88 said:
it gives errors because the zip is encrypted
what if someone posts a full rom dump and i flash all the files manually via adb?
Click to expand...
Click to collapse
Since some files are encrypted or contain personal keys, I would think that this would be not advisable. Especially if you have the 3G version (IMSI keys, eyc.)
However, if you can remember what was the last action you performed before the bootloop (for example, uninstalled a particular system app), I would be happy to find the .apk and/or relevant system folder for you so you can install it via ADB (I suppose this would be possible, provided you still have ADB access and root/su).
I was trying to change the fonts using FONT CHANGER, I have not deleted any of the default apps or anything.
Tablet S, 16GB WiFi version (SGPT111SG)
xperiax10.awesome said:
No..
sent via awesome aRc (rooted 2.3.4)
Click to expand...
Click to collapse
****.. thats not good.. you cant even reflash the same version of update..
you could wait for another update from sony, or wait for some hack of recovery, or hm... warranty?
are you able to get into recovery?
I am able to go into Recovery Mode, tried updating thru sdcard but I think we dont have the proper firmware to restore!!!
Its under warranty but donno wanna go there, it needs a solution coz I will again try to change fonts for sure
Did you try looking at condi's post? I am not quite sure what condi managed to achieve, but it sounds at least relevant.
Also, bear in mind I have posted a link to the contents of the (stock) font folder. If we knew exactly what changes are made by this application, it would be possible to revert them. If you can find out, I can find the stock files for you so you can manually reverse this issue.
EDIT: Do NOT try any of the above -- according to sapphire88. You've been warned!
tried both the way, by replacing the fonts with the original ones and by editing the build.prop...the results is that now i'm stucked at the sony logo (no more one time access to the home screen) ...contacted sony to ask them if i could have the original firmware in update.zip format...perhaps (i don't really think that they will give it to me)...
Well, this still makes no sense however. Can we approach the developer of Font Changer and ask the sort of changes the application is performing? I assume that it is not just replacing fonts, but also some system files that point to the fonts that are being used. If we could track all changes and reverse them, surely this would fix the issue.
What about condi's downgrade/upgrade option? (you said it did not work)
Also, do you still have access to ADB (perhaps in recovery)? If you do, then you can still essentially find ways to fix this issue. But for the time being let's black list Font Changer.
i haven't used an app to change the fonts, i've manually replace the three clock fonts (only those three files), and it ended in a bootloop, in recovery adb doesn't work and i can't no more access to the home screen to use adb..
anyone know about Safety Mode?? How to enter into safety mode.
Note: I am NOT talking about Recovery mode..
grcd said:
What about condi's downgrade/upgrade option? (you said it did not work)
Click to expand...
Click to collapse
I think that I found a way to downgrade. Will check it today evening, will post the results.
sapphire88 said:
i haven't used an app to change the fonts, i've manually replace the three clock fonts (only those three files), and it ended in a bootloop, in recovery adb doesn't work and i can't no more access to the home screen to use adb..
Click to expand...
Click to collapse
ADB is available in recovery - just wait a minute or two - it will become available. But its not fully working as in normal boot. Check it, you can 'adb push' some files, maybe you could turn your fonts to stock ones?
xperiax10.awesome said:
anyone know about Safety Mode?? How to enter into safety mode.
Note: I am NOT talking about Recovery mode..
Click to expand...
Click to collapse
Yes, I figured it out some time ago, press power + vol-down, and keep vol-down pressed until tab fully start system.
ohh, so safe mode of no use as we are stuck with boot loop !!!
ATTENTION EVERYONE (For everyone who attempted to install this ROM):
This ROM breaks the Tab splash screen and does harm to the Tablet.
I recommend calling 1-800-SAMSUNG, and ask for a factory re-flash. Do not say anything that you are / were rooted. This should be 100% free, they even pay for shipping. They did mine for free. I recommend doing this ASAP, before more damage might come to the Tablet.
Downloading and testing, do you need anything else? Like the twrp?
edit 1:
Impossible to install, the updater is badly configured, I can not locate the problem, even with normal recovery will not let me install, I will continue to try
edit 2:
Well I found the error, the rom is not well developed, did you do with some automated program? I remember that the tablet 10.1 has another processor and that the compatibility of a direct port without changing the drivers is impossible
jimmy999x said:
Downloading and testing, do you need anything else? Like the twrp?
edit 1:
Impossible to install, the updater is badly configured, I can not locate the problem, even with normal recovery will not let me install, I will continue to try
edit 2:
Well I found the error, the rom is not well developed, did you do with some automated program? I remember that the tablet 10.1 has another processor and that the compatibility of a direct port without changing the drivers is impossible
Click to expand...
Click to collapse
I made it on ES File Explorer, on my Nook, it took me an hour... I had ported it from Acclaim RC5 and Docker 6 Degaswifi, and I changed the updater script to say, "degaswifi", for the device. and I changed the build prop, to be the same cpu, exc... as the tab 4. I used Degaswifi Docker 6 boot.img and recovery folder, and some other important stuff in the system folder. What is the error are you getting?
secretwolf98 said:
I made it on ES File Explorer, on my Nook, it took me an hour... I had ported it from Acclaim RC5 and Docker 6 Degaswifi, and I changed the updater script to say, "degaswifi", for the device. and I changed the build prop, to be the same cpu, exc... as the tab 4. I used Degaswifi Docker 6 boot.img and recovery folder, and some other important stuff in the system folder. What is the error are you getting?
Click to expand...
Click to collapse
Even using other twrp I still can not install, use the recovery and the boot image I found 2 weeks ago, I even deleted the first line and it looked like it would install, but these errors appeared
jimmy999x said:
Even using other twrp I still can not install, use the recovery and the boot image I found 2 weeks ago, I even deleted the first line and it looked like it would install, but these errors appeared
Click to expand...
Click to collapse
Can I see what you had edited?
Only the first line of the updater inside google folder
jimmy999x said:
Only the first line of the updater inside google folder
Click to expand...
Click to collapse
What is in the first line? The new updated one, that you had did?
secretwolf98 said:
What is in the first line? The new updated one, that you had did?
Click to expand...
Click to collapse
this
jimmy999x said:
this
Click to expand...
Click to collapse
strange
I'll look into it later
jimmy999x said:
this
Click to expand...
Click to collapse
Question, after you flashed this rom, did the Splash Screen disappeared on the Samsung?
Because the both versions that I had made, broke my Samsung Splash Screen.
secretwolf98 said:
Question, after you flashed this rom, did the Splash Screen disappeared on the Samsung?
Because the both versions that I had made, broke my Samsung Splash Screen.
Click to expand...
Click to collapse
If, in fact, they stop seeing the logos of samsung when turning on and when entering the download mode, the only way to correct that is to install the official firmware
jimmy999x said:
If, in fact, they stop seeing the logos of samsung when turning on and when entering the download mode, the only way to correct that is to install the official firmware
Click to expand...
Click to collapse
so it did for you, when you flashed official PA1 firmware threw odin? did the screen that broke say, "Samsung Galaxy Tab 4 7.0 SM-T230NU Powered By Android"?
Interested to get this rom running smooth on our tabs
My phone is 10 months old and began bootlooping a few hours ago. I've kept it in a bootloop but it never booted neither system nor recovery.
It's still under warranty but I'll keep it a few days to try a few things. I'm going on vacation next week so I'll be without phone 10 months is just unacceptable from a QA point of view from Huawei and Google. Anyway...
Up to now I get mixed results: I can boot in recovery but can't fully boot. I'll try a few others way (either kernels or parameters) later during the weekend and update this post.
Boot image includes the kernel from O DP3 and recovery image the kernel from twrp 3.1.0.0. Current method is to limit the kernel to use less cores.
If your device is affected by the Boot Loop Of Death, you might try flashing this image to backup your data.
Twrp image:
twrp_3.1.1-bootloop (four cores)
Source code - Local manifest
https://github.com/architek/omnirom-twrp-angler_local-manifest
How to flash:
Reboot into bootloader mode (hold power + volume down)
unzip
fastboot flash recovery omni-7.1-twrp_3.1.1-bootloop.img
Feedback:
Tell me if that works out for you. Thanks.
Update
14th August : Binary link
21th August : Source code link
rchtk said:
My phone is 10 months old and began bootlooping a few hours ago. I've kept it in a bootloop but it never booted neither system nor recovery.
It's still under waranty but I'll keep it a few days to try a few things. I'm going on vacation next week so I'll be without phone 10 months is just unacceptable from a QA point of view from Huawei and Google. Anyway...
Up to now I get mixed results: I can boot in recovery but can't fully boot. I'll try a few others way (either kernels or parameters) later during the weekend and update this post.
Boot image includes the kernel from O DP3 and recovery image the kernel from twrp 3.1.0.0. Current method is limiting the kernel to use 1 cpu.
Urls:
Xtwrp-3.1.0-0-angler.img
Xboot-opp3.170518.006-0bc919b4.img
How to use:
Reboot into bootloader mode (hold power + volume down)
fastboot boot Ximage.img
Will boot you either in recovery or system depending on the image you use.
Feedback:
Tell me if that works out for you. Thanks.
Click to expand...
Click to collapse
The best thing to do is to follow this method at either step 9 or step 10. https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
DEVILOPS 007 said:
The best thing to do is to follow this method at either step 9 or step 10. https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Explain how it is better than what I posted.
rchtk said:
Explain how it is better than what I posted.
Click to expand...
Click to collapse
Because you didn't share what link you were using information from and you didn't say that you tried following everything like flashing the system, boot, recovery, bootloader, vendor etc as that is what needed to fix bigger bricks. Also, you didn't take into account different factors like some things might not work making your method impossible. I'm not saying your method won't work for that certain situation but the link I posted is to one of the biggest people on xda as far as I know with an almost foolproof plan to fix bricks unless it is the blod.
DEVILOPS 007 said:
Because you didn't share what link you were using information from and you didn't say that you tried following everything like flashing the system, boot, recovery, bootloader, vendor etc as that is what needed to fix bigger bricks. Also, you didn't take into account different factors like some things might not work making your method impossible. I'm not saying your method won't work for that certain situation but the link I posted is to one of the biggest people on xda as far as I know with an almost foolproof plan to fix bricks unless it is the blod.
Click to expand...
Click to collapse
Yes, obviously, my post is for people experiencing blod. If you don't then you don't need these images.
The recovery image is not even flashed, its executed in RAM and allowed me to access my filesystem.
The system image goes up to moving dots but doesn't finish booting.
rchtk said:
Yes, obviously, my post is for people experiencing blod. If you don't then you don't need these images.
The recovery image is not even flashed, its executed in RAM and allowed me to access my filesystem.
The system image goes up to moving dots but doesn't finish booting.
Click to expand...
Click to collapse
If it was a blod then your method wouldn't actually work. Your post helps with with something worse than a soft brick but not the infamous proper hard brick blod.
DEVILOPS 007 said:
If it was a blod then your method wouldn't actually work. Your post helps with with something worse than a soft brick but not the infamous proper hard brick blod.
Click to expand...
Click to collapse
The whole post is not about if it works or not. IT DOES WORK to get to recovery on my device which has a BLOD :silly:
Got it?
If you don't need these images, respects others and just don't post in this thread. I'm waiting for feedback on if it works on others too.
rchtk said:
The whole post is not about if it works or not. IT DOES WORK to get to recovery on my device which has a BLOD :silly:
Got it?
If you don't need these images, respects others and just don't post in this thread. I'm waiting for feedback on if it works on others too.
Click to expand...
Click to collapse
I'm just saying that it doesn't work that often lying and the blod doesn't even let you get to recovery anyway but whatever. Believe whatever, believe what you want.
rchtk said:
My phone is 10 months old and began bootlooping a few hours ago. I've kept it in a bootloop but it never booted neither system nor recovery.
It's still under waranty but I'll keep it a few days to try a few things. I'm going on vacation next week so I'll be without phone 10 months is just unacceptable from a QA point of view from Huawei and Google. Anyway...
Up to now I get mixed results: I can boot in recovery but can't fully boot. I'll try a few others way (either kernels or parameters) later during the weekend and update this post.
Boot image includes the kernel from O DP3 and recovery image the kernel from twrp 3.1.0.0. Current method is to limit the kernel to use less cores.
Urls:
Xtwrp-3.1.0-0-2-angler.img
Xboot-opp3.170518.006-0bc919b4.img
How to use:
Reboot into bootloader mode (hold power + volume down)
fastboot boot Ximage.img
Will boot you either in recovery or system depending on the image you use.
Feedback:
Tell me if that works out for you. Thanks.
Click to expand...
Click to collapse
Ok, so I got it booted to the TWRP 3.1.0.0 from your post but I can't see any of my files. I had TWRP 3.0.3.0 installed.
What do I do next?
I haven't tried the other image yet. I'm just excited to see what my battery percentage is so I know if I'm in the 6-9% range as mentioned in the other thread about this problem.
---------- Post added at 06:45 PM ---------- Previous post was at 06:25 PM ----------
Ok, so I just tried the opp file and it's booted up to the Google logo and stops.
outbackpaul said:
Ok, so I got it booted to the TWRP 3.1.0.0 from your post but I can't see any of my files. I had TWRP 3.0.3.0 installed.
What do I do next?
I haven't tried the other image yet. I'm just excited to see what my battery percentage is so I know if I'm in the 6-9% range as mentioned in the other thread about this problem.
Click to expand...
Click to collapse
Glad it also works for you. Well that's weird that you don't see your files under /data .
Can you try to mount /data (and maybe open shell and issue dmesg) ? Were you encrypted?
That looks similar to me. Mine was encrypted and it actually failed to decrypt it. So I formated it in the hope that it would help to boot.
---------- Post added at 06:45 PM ---------- Previous post was at 06:25 PM ----------
Click to expand...
Click to collapse
Ok, so I just tried the opp file and it's booted up to the Google logo and stops.
Click to expand...
Click to collapse
With a modified ramdisk to remove ciphering and dm-verity, mine fails right away. With the boot img I posted, the moving dots show for like 5 minutes (creating cipher metadata?) so most of the partitions are mounted but it cannot fully boot.
I did a simple check of the emmc (dding mmc to /dev/null) which is ok but I actually need to compile a pattern write and read to confirm that.
Unfortunatly, I have no USB to serial device to see eventual kernel logs.
psycho-punk said:
Also, what are the modifications done to this recovery and boot image?
Click to expand...
Click to collapse
"Boot image includes the kernel from O DP3 and recovery image the kernel from twrp 3.1.0.0. Current method is to limit the kernel to use less cores."
I have several kernels with different modifications but the original ones are actually the ones that work better. These are original kernels but called with a maxcpus parameters (isolcpu would fit better but doesn't seem to do the job).
The recovery I posted is 5 cpus IIRC, its fast enough and works from RAM but not always when flashed. Flashing a recovery when cpu is lowered to 1 always works.
Again, on MY device, might not be the same for you.
Edit: links worked with proxy
Click to expand...
Click to collapse
Weird that going through a proxy helps. Whatever.
I'll try a few others things in the next days but I'm sending the device on Thursday at the latest... I'll try to get in touch with some kernel devs. Any idea is welcome!
psycho-punk said:
Tried booting the images. Unfortunately, both of them didn't work for me.
Sent from my XT1092 using Tapatalk
Click to expand...
Click to collapse
You fastboot boot Xrecovery and it didn't boot? fastboot flash followed by rebooting into recovery might not work.
This evening, I'll post one which limits to only one core.
For the system one, it has more requirements. Not sure if there is backward compatiblity (being able to start an old ROM/vendor with a very recent kernel).
I tried so many things. Only not the oven yet
rchtk said:
Glad it also works for you. Well that's weird that you don't see your files under /data .
Can you try to mount /data (and maybe open shell and issue dmesg) ? Were you encrypted?
That looks similar to me. Mine was encrypted and it actually failed to decrypt it. So I formated it in the hope that it would help to boot.
With a modified ramdisk to remove ciphering and dm-verity, mine fails right away. With the boot img I posted, the moving dots show for like 5 minutes (creating cipher metadata?) so most of the partitions are mounted but it cannot fully boot.
I did a simple check of the emmc (dding mmc to /dev/null) which is ok but I actually need to compile a pattern write and read to confirm that.
Unfortunatly, I have no USB to serial device to see eventual kernel logs.
Click to expand...
Click to collapse
I'm pretty sure I was encrypted. I don't have the phone with me at the moment.
So, if it's encrypted am I out of luck?
When it booted to TWRP it asked for a passcode. I just hit cancel. Is that what will let me see my data?
outbackpaul said:
I'm pretty sure I was encrypted. I don't have the phone with me at the moment.
So, if it's encrypted am I out of luck?
When it booted to TWRP it asked for a passcode. I just hit cancel. Is that what will let me see my data?
Click to expand...
Click to collapse
So you're in the same boat as me (hope you had backups like me).
Twrp 3.1 should be able to decrypt /data with the correct password. I guess it first tries with default_password and if a known pattern is not detected it asks for your passcode (pin to boot by default) until it succeeds.
But for me (encrypted with pin to boot), twrp wasn't able to decrypt. In my tests once I format /data, it gets encrypted again and twrp again fails to decrypt the partition.
Can you try with pass "default_password" (without quotes) or your pin to boot if you had set one?
Also do the same after flashing the one core version I just posted and rebooting into it.
psycho-punk said:
Eagerly waiting to try the one core only recovery.
Click to expand...
Click to collapse
http://dl.free.fr/oIkytaKDF
outbackpaul said:
I'm pretty sure I was encrypted. I don't have the phone with me at the moment.
So, if it's encrypted am I out of luck?
When it booted to TWRP it asked for a passcode. I just hit cancel. Is that what will let me see my data?
Click to expand...
Click to collapse
You should also try to *flash* the one core version and see if you're able to decrypt your data with it.
rchtk said:
So you're in the same boat as me (hope you had backups like me).
Twrp 3.1 should be able to decrypt /data with the correct password. I guess it first tries with default_password and if a known pattern is not detected it asks for your passcode (pin to boot by default) until it succeeds.
But for me (encrypted with pin to boot), twrp wasn't able to decrypt. In my tests once I format /data, it gets encrypted again and twrp again fails to decrypt the partition.
Can you try with pass "default_password" (without quotes) or your pin to boot if you had set one?
Also do the same after flashing the one core version I just posted and rebooting into it.
Click to expand...
Click to collapse
I don't even remember putting in a pin but I've tried every one that I remember ever using.
psycho-punk said:
One core version didn't work either. Guess I'm out of options.
Sent from my XT1092 using Tapatalk
Click to expand...
Click to collapse
It would be interesting to start from the same configuration by using the O DP3 factory image script flash-all.sh (removing -w if you want to keep your data).
Progress:
The fact that twrp can't decrypt data with the correct password is not understood. I'm getting a KM_ERROR_KEY_NOT_YET_VALID error message. Which is rather weird.
KM_TAG_ACTIVE_DATETIME requires comparison with a trusted UTC time source. If the current date and time is prior to the tag value, the method must return KM_ERROR_KEY_NOT_YET_VALID.
So I've formated /data, disabled encryption and verify and twrp sees my /data which is populated during system boot.
Regarding boot img, I've tried several things but I still fail to get past the jumping dots. It could be a consequence of the twrp problem about communication error with the keystore which has nothing to do with big cluster disabling (so there may be a general HW failure). I've tried playing a bit with big cluster settings but my attempts fail. Still a lot of things to try but I won't have much time in the next days.
Nexus 6p bootlooping just
Tried both did not work
command used
Fastboot flash boot Xboot-opp3.170518.006-0bc919b4.img
Fastboot flash recovery Xtwrp-3.1.0-0-angler.img
and
Fastboot boot Xtwrp-3.1.0-0-angler.img
not working
RIP
Game is over for me: I've let the phone charge at home and when trying to power it back, I just get a red blinking led. I always managed to power it back but this time not.
Which brings me to the conclusion that it looks power related. Battery, soldering, IC, motherboard (components are more prone to fail stop failures).
In the end, I've mostly changed kernel stuffs (and discovered a few kernel inconsistencies btw) but didn't have time to try a lot of things in userland nor investigate on the decryption failure.
My goal was just to get users to get back their data before throwing/sending back the brick.
So I'd suggest users to decrypt their /data before BLOD happens.
A bit frustrating but was fun anyway. Thanks to @Dees_Troy for the chat on IRC
***UPDATE***
To anyone who comes across this, I fixed the issue by following a guide by @AddictedA1 on this post . Note that your case might be different as in you might be locked out of device and unable to change OEM lock from settings. This was the case with me so I just follwed the FRP/Knox bypass guide, accessed settings, enabled OEM unlocking and the proceeded with the above guide.
If you have any questions then just message me.
***************
So today we were given Samsung Galaxy Tab A7 lites by our state government for promoting technology in the state (elections in a few months go figure).
The issue was that it comes with knox which has government agency as the admin.
I tried rooting by flashing magisk flashed AP following this guide (for samsung galaxy tab A7) but now after startup it asks me to connect to the Internet and, runs a few checks and says "cant create work profile because security policy prevents this on a custom os".
It's just stuck at that message and can't get out of there.
I've never had any Samsung device before so I might be doing something wrong. Any help on how to get out of this is appreciated. Thanks
Well. I faced the same problem. After hours of hit and trail i finally managed to atleast boot back to my previous state i.e Yogi Ji's pic
Solution : I just relocked my bootloader via Download Mode and Flashed latest Firmware ( September Build ) with ODIN Tool. Untill some new development i.e custom ROMs for this device comes i think we are stuck with this lol
alp47470 said:
Well. I faced the same problem. After hours of hit and trail i finally managed to atleast boot back to my previous state i.e Yogi Ji's pic
Solution : I just relocked my bootloader via Download Mode and Flashed latest Firmware ( September Build ) with ODIN Tool. Untill some new development i.e custom ROMs for this device comes i think we are stuck with this lol
Click to expand...
Click to collapse
same here bro yogiji , Knox is inside samsung cant get it out by adb , safemode, cant root magisk . Only option left flash twrp install lineage os.. but cant find exact twrp model tar one gta7lite .. any idea ?
AddictedA1 said:
same here bro yogiji , Knox is inside samsung cant get it out by adb , safemode, cant root magisk . Only option left flash twrp install lineage os.. but cant find exact twrp model tar one gta7lite .. any idea ?
Click to expand...
Click to collapse
Sorry, I couldn't find any TWRP so far. If i do will surely let you knoww.
alp47470 said:
Sorry, I couldn't find any TWRP so far. If i do will surely let you knoww.
Click to expand...
Click to collapse
Im trying to port TWRP , hopefully something will work main thing is configuring fstab right partitions
AddictedA1 said:
Im trying to port TWRP , hopefully something will work main thing is configuring fstab right partitions
Click to expand...
Click to collapse
That's great new. Good Luck ;-)
alp47470 said:
Well. I faced the same problem. After hours of hit and trail i finally managed to atleast boot back to my previous state i.e Yogi Ji's pic
Solution : I just relocked my bootloader via Download Mode and Flashed latest Firmware ( September Build ) with ODIN Tool. Untill some new development i.e custom ROMs for this device comes i think we are stuck with this lol
Click to expand...
Click to collapse
Hey can you share the link to download the firmware please
Insomniac05 said:
Hey can you share the link to download the firmware please
Click to expand...
Click to collapse
samfw site put exact name then select country
AddictedA1 said:
samfw site put exact name then select country
Click to expand...
Click to collapse
thanks man i'll see if i can get it to boot back with the flash
alp47470 said:
Well. I faced the same problem. After hours of hit and trail i finally managed to atleast boot back to my previous state i.e Yogi Ji's pic
Solution : I just relocked my bootloader via Download Mode and Flashed latest Firmware ( September Build ) with ODIN Tool. Untill some new development i.e custom ROMs for this device comes i think we are stuck with this lol
Click to expand...
Click to collapse
didn't work for me unfortunately
still shows the same can't create work profile
o
Insomniac05 said:
didn't work for me unfortunately
still shows the same can't create work profile
Click to expand...
Click to collapse
of course it will not work cause knox app is inside stock samsung os it will connect to internet and get to know
Im trying Magisk method it will work 80% confident by patching os file. will update soon.... building twrp mehod is not working is on hold.
AddictedA1 said:
o
of course it will not work cause knox app in inste stock samsung os it will connect to internet and get to know
Click to expand...
Click to collapse
Yeah I know Knox is a part of the os the dude did say his worked so I gave it a go
AddictedA1 said:
Im trying Magisk method it will work 80% confident by patching os file. will update soon.... building twrp mehod is not working is on hold.
Click to expand...
Click to collapse
U mean patching the ap file??
Insomniac05 said:
U mean patching the ap file??
Click to expand...
Click to collapse
yeh
AddictedA1 said:
yeh
Click to expand...
Click to collapse
Tried doing it that's what tripped knox for me unfortunately
I have tried flashing after patching the AP file with magisk and it still didn't work.
It's knox which is the issue. It'll only work If someone can remove knox successfully and please update here if you do so. Thanks
AddictedA1 said:
o
of course it will not work cause knox app is inside stock samsung os it will connect to internet and get to know
Click to expand...
Click to collapse
Insomniac05 said:
Hey can you share the link to download the firmware please
Click to expand...
Click to collapse
The Knox app only stop booting if it detects that bootloader was unlocked or somtheing of similar nature. You can go back to your old state by relocking and flashing stock fw.
i made a quick guide, hope it helps
FIX - "Can't create work profile because policy prevents custom OS"
Samsung Galaxy Tab A7 Lite was distributed by our state government for promoting technology in the state. (JUST ELECTION THINGS) Anyways, the Tabs are coming with Samsung Knox security which cannot be uninstalled, disabled, debloated with adb...
forum.xda-developers.com
Somebody get help or asked some experience in XDA to make a TWRP port for this device or else forget privacy in this.
LADIES AND GENTLEMEN I HAVE SUCCESSFULLY REMOVED KNOX FROM SAMSUNG OS AND WITH NEW WALLAPER LOOKS HEAVEN )))))
Hello, I'm fairly new here. I've tried flashing TWRP to my Android TV box, but now it's just constantly rebooting over and over again. How do i fix that? How do i access the recovery mode?
TV Box: https://www.androidtv-guide.com/pay-tv-provider/united-group-eon-ott-smart-box/
Fzloop said:
Hello, I'm fairly new here.
Click to expand...
Click to collapse
Fairly? You joined yesterday. You could hardly be fairer.
Fzloop said:
I've tried flashing TWRP to my Android TV box, but now it's just constantly rebooting over and over again.
Click to expand...
Click to collapse
The good news is that since it is bootlooping, the bootloader is probably okay.
For this model device running android 9, neither of the bootable partitions can be modified (while still running the original bootloader), even if the bootloader is unlocked, without causing a signature check failure. Since flashing some twrp version has modified the recovery partition, which is a bootable partition, the signature check is failing.
Fzloop said:
How do i fix that?
Click to expand...
Click to collapse
One way is to flash the original recovery partition back to the device using burn mode.
Fzloop said:
How do i access the recovery mode?
Click to expand...
Click to collapse
By holding the button on the device. You'll need the worldcup drivers and command line "update" burn mode tool (not the GUI burning tool).
If you have a copy of the original recovery partition, you'd just flash that with the update tool and be done.
If you don't have a copy of the original recovery partition, you can use the update tool to dump a different partition, like system, in order to learn which version of the firmware is installed on your box. Report the version here, and maybe some member will have the matching recovery partition that you can flash to your device using the update tool.
goapy said:
Fairly? You joined yesterday. You could hardly be fairer.
The good news is that since it is bootlooping, the bootloader is probably okay.
For this model device running android 9, neither of the bootable partitions can be modified (while still running the original bootloader), even if the bootloader is unlocked, without causing a signature check failure. Since flashing some twrp version has modified the recovery partition, which is a bootable partition, the signature check is failing.
One way is to flash the original recovery partition back to the device using burn mode.
By holding the button on the device. You'll need the worldcup drivers and command line "update" burn mode tool (not the GUI burning tool).
If you have a copy of the original recovery partition, you'd just flash that with the update tool and be done.
If you don't have a copy of the original recovery partition, you can use the update tool to dump a different partition, like system, in order to learn which version of the firmware is installed on your box. Report the version here, and maybe some member will have the matching recovery partition that you can flash to your device using the update tool.
Click to expand...
Click to collapse
I did join yesterday, but I've been using this forum for a while without posting.
I managed to fix the box on my own, turns out all i needed was an SD card and a ROM.
Fzloop said:
I managed to fix the box on my own, turns out all i needed was an SD card and a ROM.
Click to expand...
Click to collapse
An alternative ROM, or the original ROM?
If you installed an alternative ROM, you may have "fixed" your box, but you've also blown away your drm keys forever.
If you're happy with the result, that's all that matters.
Although you could have posted that your issue had been resolved. That would have saved me from wasting my time. I always regret replying to posts about the dv8519. This is the last one for me.
goapy said:
An alternative ROM, or the original ROM?
If you installed an alternative ROM, you may have "fixed" your box, but you've also blown away your drm keys forever.
If you're happy with the result, that's all that matters.
Although you could have posted that your issue had been resolved. That would have saved me from wasting my time. I always regret replying to posts about the dv8519. This is the last one for me.
Click to expand...
Click to collapse
Unfortunately, alternative. I'm still looking for the original.
My apologies for wasting your time. Have a great day.
Fzloop said:
Unfortunately, alternative. I'm still looking for the original.
My apologies for wasting your time. Have a great day.
Click to expand...
Click to collapse
Hi @Fzloop,
can you share the ROM?
xfenixxx said:
Hi @Fzloop,
can you share the ROM?
Click to expand...
Click to collapse
BoskoWifiBT
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Worked fine at first, but after playing with it a bit more the box just wouldn't boot, so be careful.
Fzloop said:
BoskoWifiBT
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Worked fine at first, but after playing with it a bit more the box just wouldn't boot, so be careful.
Click to expand...
Click to collapse
Thank you very much, I'll still give it a try.
Hello, I've tried flashing TWRP to my Android TV box, but now it's just constantly rebooting over and over again. How do i fix that? How do i access the recovery mode?
TV BOX https://www.androidtv-guide.com/pay-tv-provider/dhiraagu-tv-joybox/
box connected AMLOGIC usb burn tool. but error uboot/getresult/Diskinitial error