Here is TWRP 3.2.1 build for Project Tango K1 ATAP.
Download
gdrive: twrp-3.2.1-yellowstone.img
mailru: twrp-3.2.1-yellowstone.img
Sources
device tree: https://github.com/HighwayStar/android_device_google_yellowstone
kernel: https://github.com/HighwayStar/android_kernel_google_yellowstone
How to install
enable USB debugging in stock ROM and run command: adb reboot bootloader
Unlock bootloader using command: fastboot oem unlock (it will wipe all your user data!)
With unlocked bootloader boot into stock rom and enable USB debugging again. Reboot to bootloader: adb reboot bootloader
Flash recovery image: fastboot flash recovery twrp-3.2.1-yellowstone.img
To boot into recovery you could run adb reboot recovery after booting to stock ROM or use Vol+ Vol- Power combo to boot in bootloader menu and select Recovery using volume keys and confirm by pressing Power.
XDA:DevDB Information
[RECOVERY][TWRP] Project Tango K1 ATAP TWRP 3.2.1, Tool/Utility for the Nvidia Shield Tablet
Contributors
highwaystar_ru
Source Code: https://github.com/HighwayStar/android_kernel_google_yellowstone
Version Information
Status: Testing
Created 2019-02-19
Last Updated 2019-02-19
Any ROMs available for yellowstone? I can see one in use on the LineageOS Statistics page (search 14.1-20190208-UNOFFICIAL-yellowstone)
But I can't find it on xda.
I didn't get it to boot, but I was in a hurry and hopefully just forgot something simple. If anyone gets it working please post details. Hopefully this is legit:
Edit: link removed. Per the developer: "please don't use them. They're experimental, and won't be booting for some time... you run the chance of bricking. Definitely stay away until I make some form of announcement otherwise."
@highwaystar_ru gave me this ROM that is working splendidly on my yellowstone: https://cloud.mail.ru/public/Hmco/XryszodXm
From @highwaystar_ru:
It uses binary files from stock yellowstone and has some issues:
cameras doesnt work, video playback sometimes has artifacts, all cpu
cores always up (without it video playback lags), accelerometer sensor
inverted.
Me and couple of lineage devs working hard to port shieldtablet kernel
to yellowstone, it will allow to use shield binary files and resolve
most problems, but progress are really slow (but there is some
progress lately).
Click to expand...
Click to collapse
shiznit1618 said:
@highwaystar_ru gave me this ROM that is working splendidly on my yellowstone: https://cloud.mail.ru/public/Hmco/XryszodXm
From @highwaystar_ru:
Click to expand...
Click to collapse
Thanks! This is working very well so far for the limited testing I've done. I'll have to take it into the field and see how that goes .
Tried out that ROM , it's pretty good outside of issues listed bluetooth is non functional.
Mobile data , text, wifi etc working.
Back to life
Thanks to highwaystar_ru I was able to install twrp and then lineage 14.1 with Open GApps pico.
I hope that somebody will be able to bring this to 15.1
Please keep up your effort, Hurray I can use my tango again , at least some of it, would be great that bluetooth and cameras working and good luck with the shield software i'll be looking for it . Thanks alot
thanks
worked for me. . with all the restrictions added.. but still brought a perfectly fine tablet from no usage to home automation dashboard device
Great work thank you,
Also i tested that Rom in the thread and it works well despite the reversed sensor, bluetooth (and i report USB on dock non fuctional with rom)
has there been any progress on the Rom at all? thanks.
Any progress with this rom?
Also @shiznit1618 and @highwaystar_ru where are you guys collaborating? If this is a telegram, discord, or other chat group. I'd love to get in and talk, maybe help a bit. I'm currently on arcore devs slack chat but there isn't much activity in their #yellowstone channel.
https://arcore.slack.com
ShapeShifter499 said:
Any progress with this rom?
Also @shiznit1618 and @highwaystar_ru where are you guys collaborating? If this is a telegram, discord, or other chat group. I'd love to get in and talk, maybe help a bit. I'm currently on arcore devs slack chat but there isn't much activity in their #yellowstone channel.
https://arcore.slack.com
Click to expand...
Click to collapse
There does seem to be some active development on GitHub (within the last week) and I also found (from same developer on GitHub) a newer rom based on 15.1 although I couldn't get it to boot, seems I need to update TWRP, but trying to update TWRP it tells me the recovery partition exceeded size, so I assume I have to update boot as well (which I didn't do). i'd suggest checking on GitHub and contacting that developer.
https://github.com/TegraDevelopment/android_device_google_yellowstone
Bazathoth said:
There does seem to be some active development on GitHub (within the last week) and I also found (from same developer on GitHub) a newer rom based on 15.1 although I couldn't get it to boot, seems I need to update TWRP, but trying to update TWRP it tells me the recovery partition exceeded size, so I assume I have to update boot as well (which I didn't do). i'd suggest checking on GitHub and contacting that developer.
https://github.com/TegraDevelopment/android_device_google_yellowstone
Click to expand...
Click to collapse
Where did you find the 15.1 build?
ShapeShifter499 said:
Where did you find the 15.1 build?
Click to expand...
Click to collapse
http://updater.ods.ninja/yellowstone
This is the same project I had mentioned in post #3. I took the link down because it wasnt ready at the time and I've been waiting for the dev to let us know when its working. See post #3 for a quote from him...
But... there is a build from Feb 12. Please let us know how it goes if you try it. :good:
xaxxelous said:
http://updater.ods.ninja/yellowstone
This is the same project I had mentioned in post #3. I took the link down because it wasnt ready at the time and I've been waiting for the dev to let us know when its working. See post #3 for a quote from him...
But... there is a build from Feb 12. Please let us know how it goes if you try it. :good:
Click to expand...
Click to collapse
I have a new issue, my tablet is rebooting constantly. It will crash to a "red battery icon" and then boot back up to the lockscreen. I'm not sure if the battery in my unit is bad or if the battery calibration is messed up. Do you have any ideas what to do here?
My device was restored to stock btw.
ShapeShifter499 said:
I have a new issue, my tablet is rebooting constantly. It will crash to a "red battery icon" and then boot back up to the lockscreen. I'm not sure if the battery in my unit is bad or if the battery calibration is messed up. Do you have any ideas what to do here?
My device was restored to stock btw.
Click to expand...
Click to collapse
Will it stay on while plugged into the dock? Or usb even?
xaxxelous said:
Will it stay on while plugged into the dock? Or usb even?
Click to expand...
Click to collapse
I never got a hold of a original dock, I didn't check to see if keeping it on charge helped.
ShapeShifter499 said:
I never got a hold of a original dock, I didn't check to see if keeping it on charge helped.
Click to expand...
Click to collapse
Did you flash that build from Feb 12?
How did you return to stock? A TWRP backup or do you have original firmware?
Does it keep bootlooping by itself without any input from you or will it sit stable at the lockscreen? Can you keep it turned off?
Depending on the answers to those questions, the first thing I would do is turn it off and plug it in. Let it sit until fully charged. It takes a long time via USB, and even longer if it is on. Not that this is a solution, just troubleshooting...
xaxxelous said:
Did you flash that build from Feb 12?
How did you return to stock? A TWRP backup or do you have original firmware?
Does it keep bootlooping by itself without any input from you or will it sit stable at the lockscreen? Can you keep it turned off?
Depending on the answers to those questions, the first thing I would do is turn it off and plug it in. Let it sit until fully charged. It takes a long time via USB, and even longer if it is on. Not that this is a solution, just troubleshooting...
Click to expand...
Click to collapse
It reboots without me touching. The main OS has a full battery icon but the reboot flashes the red battery icon before booting. I flashed using NVFlash a copy of the stock OS I got from the arcore stack. Someone gave me their APX package that NVFlash requires.
That file is here: https://drive.google.com/file/d/1dv5ZPsczOAp6l9WOgVlbCTuBnbW71L8p
Conversation starts here: https://arcore.slack.com/archives/C68HHETL7/p1549401595001100
Main quote of interest from that chat:
Greg Willard (r3pwn) 1:20 PM
Around 3 mins left on the upload
1:24
What I did in the interest of still letting a device turn on if someone didn't get the chance to back up their persist/persistbk, was I took mine, and scrubbed the mac addresses and serial number. So the macs are set to 00:11:22:33:44:55:66, and the serial num is 012345678.
1:25
... aaaand here you go https://drive.google.com/file/d/1dv5ZPsczOAp6l9WOgVlbCTuBnbW71L8p
Click to expand...
Click to collapse
ShapeShifter499 said:
It reboots without me touching. The main OS has a full battery icon but the reboot flashes the red battery icon before booting. I flashed using NVFlash a copy of the stock OS I got from the arcore stack. Someone gave me their APX package that NVFlash requires.
That file is here: https://drive.google.com/file/d/1dv5ZPsczOAp6l9WOgVlbCTuBnbW71L8p
Conversation starts here: https://arcore.slack.com/archives/C68HHETL7/p1549401595001100
Main quote of interest from that chat:
Click to expand...
Click to collapse
I can't see that convo without an account. Have you asked for help there?
Until I get home I can't really look at that apx. Maybe install TWRP and the ROM from post #4 or a TWRP backup? Without knowing what that apx flashed its hard to say. The ROM from highwaystar_ru (mostly) works. Might at least get you out of the bootloop.
And just to be clear, you did not flash that 15.1 build, right? What were you running before flashing the apx?
Unless TWRP and that LOS 14.1 ROM or a TWRP backup help we've gone off topic for this thread...
Related
I have been modifying the Sony kernel sources, and porting our 4.1 kernel to a 4.2 CAF branch to be used with CyanogenMod 10.1 and above. We will eventually receive Android 4.3 direct from Sony, and therefore suitable kernel sources, but if we can beat them to it, why not?
However our Xperia SP has a very temperamental screen, it really needs a perfect frame buffer or it will crap out on you with no apparent way back.
If you flash a kernel with a broken frame buffer (a kernel that does not send the correct signals to the display), you will see nothing on the screen, sometimes random vertical lines, then your device will get into a low level bootloop, (ADB will not be available) and even if you flash a working kernel from a factory image this will not recover the device. Basically, the screen gets stuck in a non-functional state, the device is able to detect this and immediately hard resets, so your device seems hard bricked.
Well... almost.
Fortunately, Sony build into their factory images a special lock that, on first boot, nothing can cause the device to shut down or reboot. Therefore to break this hard brick, you need to do a full wipe with flashtool.
On reboot the screen will still be broken, but it will do a full boot (you will eventually hear touch sounds when pressing the screen). You can now hit the power button to switch off the display, hit it again and your screen should, finally, come back to life.
* * * * * * * * * *
Why does this happen? My guess is that a specific set of commands must be used to control the display. Any deviation from that set and the screen gets stuck in a non-functional state, and the only way to recover is to eventually send the correct off/on sequence to it.
However this can only happen from a working rom, but due to the auto detect of the broken screen and hard reset (forcing the hardware to switch off without sending an off command to the screen), this can only happen after a full wipe to recreate the first boot sequence.
Therefore if you are experimenting with the kernel you need to be aware of this... 'feature' and that luckily there is a way to recover from it.
I have needed to recover my device three times now with this method and I haven't even owned it for a week yet. I have never seen such behaviour on any of the other devices I have worked on, so this is going to make kernel porting a tricky and tedious affair. The fact that the screen 'remembers' your bad kernel even after you flash a good one is pretty disturbing. (I even left my Xperia SP powered off for over an hour to see if the lack of power would reset the screen, but no change)
Thanks for the more detailed info.
Thanks @adfad666 for the info.
I'm currently looking at framebuffer now and it should be fixed pretty soon then all you guys can have a CM and I'll get eagleeyetom to unlock the thread.
Still continuing
uberlaggydarwin said:
Thanks @adfad666 for the info.
I'm currently looking at framebuffer now and it should be fixed pretty soon then all you guys can have a CM and I'll get eagleeyetom to unlock the thread.
Click to expand...
Click to collapse
adfad666 fixed it in THIS POSTpost.
Kernel is now much more stable, no issues of permanently broken displays across flashes. Also we now have logcat:
logcat: http://pastebin.com/A0VyPDh5
kmsg: http://pastebin.com/TNE1awUy
:victory::victory::victory:
adfad666 said:
Kernel is now much more stable, no issues of permanently broken displays across flashes. Also we now have logcat:
logcat: http://pastebin.com/A0VyPDh5
kmsg: http://pastebin.com/TNE1awUy
:victory::victory::victory:
Click to expand...
Click to collapse
At mean that all of us is ready for cm10.2 development on our device??
best regards.
sanzNya
sent from my mind via tapatalk 4
Oh, great information @adfad666 , thanks alot, hopefully I'll have the deivce in 1 or 2 weeks, and I could help u on the development. (I'm not a kernel developer expert, but for sure I'll learn from you) Thanks in advanced for this, it is really helpful for new SP users. Following your github Thanks.
bieltv.3 said:
Oh, great information @adfad666 , thanks alot, hopefully I'll have the deivce in 1 or 2 weeks, and I could help u on the development. (I'm not a kernel developer expert, but for sure I'll learn from you) Thanks in advanced for this, it is really helpful for new SP users. Following your github Thanks.
Click to expand...
Click to collapse
Biel? Oh dear! I followed your development on the 5830i since day one, back when I had that phone! Hope you'll be bringing CM to this phone too
Sent from my C5303 using xda app-developers app
Updated the thread.
adfad666 said:
Kernel is now much more stable, no issues of permanently broken displays across flashes. Also we now have logcat:
logcat: http://pastebin.com/A0VyPDh5
kmsg: http://pastebin.com/TNE1awUy
:victory::victory::victory:
Click to expand...
Click to collapse
Updating this thread with a link to the CM port from @adfad666 & Kali- and myself.
https://plus.google.com/111440315650679525393/posts/PeAj8dgoNHA
You can look at our kernel source to look at frame buffer.
Hello!
I have a Moto E First Generation xt1022 (condor),running Cyanogenmod.
About 2 weeks ago,i saw a notification about a CM system update. So i had the BRILLIANT idea to try to update the phone,with a low battery. I pressed the button to install updates and left my phone unattended.
About 3 hours late i come back,find my phone still displaying CM bootanimaion. I held the power button,it showed a low battery indicator,and now i am here.
My phone has an unlocked bootloader. It is able to boot into the bootloader,it's able to boot into the latest version of TWRP recovery,it is recognized by ADB,it's recognized by Fastboot and Mfastboot,and it also recgonized by RSD Lite,but none of them can flash the phone into a working state.
I'm away from my main computer right now. Tomorrow i will post the logs
Is there any hope for this phone?
Is it bricked? I mean,it shouldn't be,i can everything like fastboot and adb...
If you need more info about the phone,tell me.
Help and suggestions are highly appreciated
Thanks! :good:
Livelm said:
Hello!
I have a Moto E First Generation xt1022 (condor),running Cyanogenmod.
About 2 weeks ago,i saw a notification about a CM system update. So i had the BRILLIANT idea to try to update the phone,with a low battery. I pressed the button to install updates and left my phone unattended.
About 3 hours late i come back,find my phone still displaying CM bootanimaion. I held the power button,it showed a low battery indicator,and now i am here.
My phone has an unlocked bootloader. It is able to boot into the bootloader,it's able to boot into the latest version of TWRP recovery,it is recognized by ADB,it's recognized by Fastboot and Mfastboot,and it also recgonized by RSD Lite,but none of them can flash the phone into a working state.
I'm away from my main computer right now. Tomorrow i will post the logs
Is there any hope for this phone?
Is it bricked? I mean,it shouldn't be,i can everything like fastboot and adb...
If you need more info about the phone,tell me.
Help and suggestions are highly appreciated
Thanks! :good:
Click to expand...
Click to collapse
Flash latest twrp 3.x.x and cm13 Nov 08 build ( do clean flash)
Latest builds are non bootable
Rajendran Rasa said:
Flash latest twrp 3.x.x and cm13 Nov 08 build ( do clean flash)
Latest builds are non bootable
Click to expand...
Click to collapse
I can't do that now. My phone has been stolen.
That's right. When thought it couldn't get worse...
Thanks for you help ,though.
Hi gang!
I have a Moto E 2nd Generation here that was having some issues, browser crashing, slow downs, overheating issues due to multiple apps running, etc. So I decided to log into TWRP and attempt to do a factory reset. After this factory reset was done now I attempt to log into fastboot, which gives me the options of start, restart, factory, etc. I am just receiving a boot loop and nothing more. The steps to get this corrected is a bit jumbled and confusing, I must admit. I have installed ADB on my computer in hopes that this will be straightforward. I have downloaded some system images which I thought would help the process, negative. So if someone could help me this would be greatly appreciated.
- John
CheapStudent
cheapstudent said:
Hi gang!
I have a Moto E 2nd Generation here that was having some issues, browser crashing, slow downs, overheating issues due to multiple apps running, etc. So I decided to log into TWRP and attempt to do a factory reset. After this factory reset was done now I attempt to log into fastboot, which gives me the options of start, restart, factory, etc. I am just receiving a boot loop and nothing more. The steps to get this corrected is a bit jumbled and confusing, I must admit. I have installed ADB on my computer in hopes that this will be straightforward. I have downloaded some system images which I thought would help the process, negative. So if someone could help me this would be greatly appreciated.
- John
CheapStudent
Click to expand...
Click to collapse
Heyo John!
I can try to help since I have managed to overcome my bootloop issue and flash a custom ROM into my phone. Could I ask, are you trying to also install a custom ROM? And what version of TWRP do you have?
I had the bootloop issue because of an outdated TWRP and had to flash the latest one, which thankfully worked!
Let me know! ^_^
testerexp345 said:
Heyo John!
I can try to help since I have managed to overcome my bootloop issue and flash a custom ROM into my phone. Could I ask, are you trying to also install a custom ROM? And what version of TWRP do you have?
I had the bootloop issue because of an outdated TWRP and had to flash the latest one, which thankfully worked!
Let me know! ^_^
Click to expand...
Click to collapse
Hello testerexp345,
Thank you for the reply and the assistance, I am not sure if TWRP is installed anymore as I can't get passed the bootscreen on the phone. I hold down the volume down and power button to get the options of factory reset, shut down, restart, etc. However all these options lead back to the boot screen looping over. The ROM that I had installed on the phone was from an online seller that paired the phone with a SIM card that allowed unlimited data service, which was great for my business since I am out much of the week traveling. Any insight would help, as when it comes to flashing devices and cell phones... let's just say I am a newbie still
John C.
cheapstudent said:
Hello testerexp345,
Thank you for the reply and the assistance, I am not sure if TWRP is installed anymore as I can't get passed the bootscreen on the phone. I hold down the volume down and power button to get the options of factory reset, shut down, restart, etc. However all these options lead back to the boot screen looping over. The ROM that I had installed on the phone was from an online seller that paired the phone with a SIM card that allowed unlimited data service, which was great for my business since I am out much of the week traveling. Any insight would help, as when it comes to flashing devices and cell phones... let's just say I am a newbie still
John C.
Click to expand...
Click to collapse
To boot in bootloader while you stuck on bootlogo
Press and hold power button and volume button , and when screen goes off, quickly release power button only . don't release volume down button . now you will boot in bootloader
hamxa266 said:
To boot in bootloader while you stuck on bootlogo
Press and hold power button and volume button , and when screen goes off, quickly release power button only . don't release volume down button . now you will boot in bootloader
Click to expand...
Click to collapse
Hello hamxa266, okay I was able to get into the bootloader. All the options I choose restart the phone and put it back it back into a bootloop. I am not very familiar when it comes to using ADB.
John C.
cheapstudent said:
Hello hamxa266, okay I was able to get into the bootloader. All the options I choose restart the phone and put it back it back into a bootloop. I am not very familiar when it comes to using ADB.
John C.
Click to expand...
Click to collapse
I guess now you need to flash stock frimware using fastboot. if you are not familiar with then go and get familiar with it . It is not too hard just read few posts and thats it ..
If you need any help i am here!
Hi, I have the same issue, but I can't get it into recovery, but... Can I use "fastboot boot recovery.img"? for go into recovery for a factory reset and solve it, or I need to do something more, I have the same Moto, surnia with the bootloader locked, please I need help
testerexp345 said:
Heyo John!
I can try to help since I have managed to overcome my bootloop issue and flash a custom ROM into my phone. Could I ask, are you trying to also install a custom ROM? And what version of TWRP do you have?
I had the bootloop issue because of an outdated TWRP and had to flash the latest one, which thankfully worked!
Let me know! ^_^
Click to expand...
Click to collapse
Can u provide link for latest TWRP...??
mkranthikmr said:
Can u provide link for latest TWRP...??
Click to expand...
Click to collapse
This is the link for official twrp website
http://twrp.me/motorola/motorolamotoelte.html
Or you could use squid's twrp from here:
https://forum.xda-developers.com/mo.../twrp-squid-twrp-recovery-moto-e-lte-t3137649
shreyas_123 said:
This is the link for official twrp website
http://twrp.me/motorola/motorolamotoelte.html
Or you could use squid's twrp from here:
https://forum.xda-developers.com/mo.../twrp-squid-twrp-recovery-moto-e-lte-t3137649
Click to expand...
Click to collapse
Thank you bro... Got it already...:good:
Hello first of all my phone touch screen not working at all. It can't react to my touch. Even i had to reboot it by long pressing the power button. The phone still can reboot to recovery,fastboot mode. It's like you're touching the person in coma. No reaction.
What i do before it gets into this problem, i flash a kernel (not gonna tell n not blaming dev either). At first 10 minutes it was ok until i reboot again to recovery to flash magisk zip. After it went to recovery mode my phone didn't react to my touch.
What i do is i try to flash stock global rom. The phone boots but still in coma. Just a new dress for a coma person. Any ideas?
I'll post a pic later. A miui startup screen, fastboot and recovery screen.
StormTrooper89 said:
I'll post a pic later. A miui startup screen, fastboot and recovery screen.
Click to expand...
Click to collapse
Does touch work in twrp?
sotosgolf said:
Does touch work in twrp?
Click to expand...
Click to collapse
Not working too. I'm still convinced it's not a hardware problem. But right now I'm out of ideas.
have you tried reflashing miui through mi flashtool in fastboot mode?
If you can fast it to fastboot perhaps flash the original miui. Maybe you flash a 75hz kernel that some pocophone is not compatible I already did that but twrp is sure working for me though.
StormTrooper89 said:
Not working too. I'm still convinced it's not a hardware problem. But right now I'm out of ideas.
Click to expand...
Click to collapse
If you have kept a vendor image backup of after you unlocked the phone, flash it. Differently, your only option is flashing your original miui via fastboot (not an update).
StormTrooper89 said:
Hello first of all my phone touch screen not working at all. It can't react to my touch. Even i had to reboot it by long pressing the power button. The phone still can reboot to recovery,fastboot mode. It's like you're touching the person in coma. No reaction.
What i do before it gets into this problem, i flash a kernel (not gonna tell n not blaming dev either). At first 10 minutes it was ok until i reboot again to recovery to flash magisk zip. After it went to recovery mode my phone didn't react to my touch.
What i do is i try to flash stock global rom. The phone boots but still in coma. Just a new dress for a coma person. Any ideas?
Click to expand...
Click to collapse
Hi. Sorry for heating this.
I know it would make the dev look bad, but could you please mention which kernel you used? So the dev could try and look into it. If it was my kernel, that's strange, we literally never broke and phone. Now we saw a post about NGK breaking a touch, that's why I'm asking you to at least somehow hint at the kernel
D1stRU3T0R said:
Hi. Sorry for heating this.
I know it would make the dev look bad, but could you please mention which kernel you used? So the dev could try and look into it. If it was my kernel, that's strange, we literally never broke and phone. Now we saw a post about NGK breaking a touch, that's why I'm asking you to at least somehow hint at the kernel
Click to expand...
Click to collapse
I flashed Lawrun K. But don't worry I didn't blame him the dev for the cause of my phone.
I already flash stock miui using miui flash tool. Even flash the outdated version in hope that it will back to normal but it's not.
What bad is that in any screen, either home, stock recovery nor twrp the touchscreen won't work. The rest work perfectly. It can boot, can flash via adb, flash tool whatsoever.
Right now i cant replace my screen yet due to covid19 restrictions order to stay at home and all shops closed. If any of you guys have idea please do share. For the dev of Lawrun Kernel, it's not your fault. I already understand the risk of flashing all this tweaks.
I know it may sound odd but have you tried plugging in a mouse from a computer and see if you can get a curser to click on the on screen buttons.....
stinka318 said:
I know it may sound odd but have you tried plugging in a mouse from a computer and see if you can get a curser to click on the on screen buttons.....
Click to expand...
Click to collapse
Lol i already did that too. I figured it before when i use my oppo find 7 with screen crack and that was a long time ago. But no cursor appeared.
StormTrooper89 said:
Lol i already did that too. I figured it before when i use my oppo find 7 with screen crack and that was a long time ago. But no cursor appeared.
Click to expand...
Click to collapse
It is ashame that there not some sort of way to modify Samsung's remote system that you plug it in to your laptop and can control it without the use of the touch screen.......
hi there,
hope someone can help me,
in my samsung tab s3 sm-t820 i installed twrp_3.2.1-1_T820_28518 and lineage-17.1-20201227-UNOFFICIAL-gts210wifi
but when i reboot i am with the boot screen in loop
i've already tried to wipe and reinstall. but nothing.
please let me know i have a chance.
thanks
someone?
Lucauonz said:
someone?
Click to expand...
Click to collapse
Hey
Lucauonz
maybe you have not the right Lineage-Release ... use lineage-17.1-20200211-UNOFFICIAL-gts3lwifi.zip https://drive.google.com/file/d/1D8lY5z9O3oafqiWlDLvtltFDQCEHnZbN/view?usp=sharing
from this thread: https://forum.xda-developers.com/t/...l-lineage-17-1-android-10-q-20200211.3981535/
I wish you success
Edit: At the end of the discussion there is a link to https://drive.google.com/drive/folders/1E5pBRVSkHv-nc9pQ25DtAp4MwfOOgIwy with lineage-17.1-20200829-UNOFFICIAL-gts3lwifi.zip
Frischifrisch said:
Hey
Lucauonz
maybe you have not the right Lineage-Release ... use lineage-17.1-20200211-UNOFFICIAL-gts3lwifi.zip https://drive.google.com/file/d/1D8lY5z9O3oafqiWlDLvtltFDQCEHnZbN/view?usp=sharing
from this thread: https://forum.xda-developers.com/t/...l-lineage-17-1-android-10-q-20200211.3981535/
I wish you success
Edit: At the end of the discussion there is a link to https://drive.google.com/drive/folders/1E5pBRVSkHv-nc9pQ25DtAp4MwfOOgIwy with lineage-17.1-20200829-UNOFFICIAL-gts3lwifi.zip
Click to expand...
Click to collapse
Hi, thank you anyway but i had some error while i tryied to flash rom and gapp as you can see in the attached screeshot:
sorry, I repeated the installation a second time but this time without any kind of error, now I have restarted the system to get it started, I am with the boot screen in loop, I have read that at the first start it takes some time, for now I wait.
he boot screen is in loop for almost an hour, now the istallation was clear,
I have done these steps in sequence:
format and reboot recovery
flash ROM and GAPPS
reboot - system
boot screen is in loop
any advice?
thanks a lot
Sure ... How well do you already know about rooting or the tools for Samsumg devices?
I will sketch a brief instruction, first download:
Odin (https://forum.xda-developers.com/t/...ead-03-sep-20-galaxy-s10-sm-g975f-ds.3908710/ should work ... you can find most of the software in the tools section odf xda)
SamFirm (https://forum.xda-developers.com/t/tool-samfirm-samsung-firmware-downloader-checker.2988647/)
Use SamFirm to download the latest original Samsung Firmware.
(Connect Tablet with PC & start Download-Mode: press Power (only until Vibrate) + Volume down + Home green Screen then Volume Up, voila)
And use Odin to flash Tablet S3 -> good as new, and you can start all over again ;-)
I will attach some Screenshots ...
Many Greetings
STOP
Did you (not forget to) FORMAT DATA before your attempt to Install a Rom???
maybe try to flash https://forum.xda-developers.com/t/rom-sm-t820-tweaked-rom-sm-t820-tweaked.3659433/ first ... in the thread are very detailed instructions.
just to clarify the above, this is done wile in twrp > wipe menu >format data and it requires you type"yes" before it launches the process
@Frischifrisch @Lucauonz
As Samsung has changed servers or what so ever, Samfirm I didn't find working any longer.
Samfirm_reborn did/does it.
GitHub - ivanmeler/SamFirm_Reborn
Contribute to ivanmeler/SamFirm_Reborn development by creating an account on GitHub.
github.com
.
Btw. recommendation of "Format Data" I encourage as well.
Might be neccessary to reboot to recovery afterwards before continuing.
@Lucauonz Which Gapps are you using?
Pico version I've always found best, as everything else can be installed later additionally.
Try just flashing ROM and test if device restarts without anything else to exclude Gapps as the cause for the failure.
Hi guys,
thanks a lot for your help, for now i am still with this problem, i am left with the boot screen in loop,
now i'm looking for a way to go back to an original android version if possible, a version that doesn't slow me down.
i don't know if it's possible not having a backup
thanks verymuch
Luca
Lucauonz said:
Hi guys,
thanks a lot for your help, for now i am still with this problem, i am left with the boot screen in loop,
now i'm looking for a way to go back to an original android version if possible, a version that doesn't slow me down.
i don't know if it's possible not having a backup
thanks verymuch
Luca
Click to expand...
Click to collapse
That's not a problem to go back to stock.
Just follow the post from @Frischifrisch and use samfirm_reborn to get multiple part version.