Related
OK so I might have screwed up my prime. I've done command line stuff and had custom ROMs on everything I own. But I am by no means an expert so please bear with me. I will explain my series of events to the best of my ability.
Starts off with a buggy ROM, i loaded it some time ago and have been dealing with it since. It was cm10 dated sometime in the middle of 2012. Did some searching and found that all the new ROMs were saying something about needing to nvflash to get blobs or something. No prob. Right?
Got everything prepared based off of these instructions:
androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
Downloaded recovery_tf201.img, fastboot, nvflash, and the drivers. The very first step went ok. It showed moving the .img and then flashing the file. When done the little blue bar went across the screen like it should have.
Here's were it all went bad. I ran the reboot command in fastboot, device rebooted, loaded android. I held power a sec and chose "reboot recovery". I can now get the device to do one of three things:
1. Asus splash screen showing device unlocked when powered normally. That's it.
2. Hold vol down gets asus screen with 4 lines: this device is unlocked, android cardhu-user bootloader 2.10 e, checking for ota recovery, and booting recovery kernal image. Stops there.
3. Volume up gets black screen apx mode
Also tried running battery dead. Still same thing.
Is there any hope for my prime?
Where did I go wrong? Was it by pressing "reboot recovery" from the os?
Arggg please help. Otherwise a guide to replace the main board would be great.
Anything else please ask.
Thanks all,
Nick
Username5.2 said:
OK so I might have screwed up my prime. I've done command line stuff and had custom ROMs on everything I own. But I am by no means an expert so please bear with me. I will explain my series of events to the best of my ability.
Starts off with a buggy ROM, i loaded it some time ago and have been dealing with it since. It was cm10 dated sometime in the middle of 2012. Did some searching and found that all the new ROMs were saying something about needing to nvflash to get blobs or something. No prob. Right?
Got everything prepared based off of these instructions:
androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
Downloaded recovery_tf201.img, fastboot, nvflash, and the drivers. The very first step went ok. It showed moving the .img and then flashing the file. When done the little blue bar went across the screen like it should have.
Here's were it all went bad. I ran the reboot command in fastboot, device rebooted, loaded android. I held power a sec and chose "reboot recovery". I can now get the device to do one of three things:
1. Asus splash screen showing device unlocked when powered normally. That's it.
2. Hold vol down gets asus screen with 4 lines: this device is unlocked, android cardhu-user bootloader 2.10 e, checking for ota recovery, and booting recovery kernal image. Stops there.
3. Volume up gets black screen apx mode
Also tried running battery dead. Still same thing.
Is there any hope for my prime?
Where did I go wrong? Was it by pressing "reboot recovery" from the os?
Arggg please help. Otherwise a guide to replace the main board would be great.
Anything else please ask.
Thanks all,
Nick
Click to expand...
Click to collapse
2. Hold vol down gets asus screen with 4 lines: this device is unlocked, android cardhu-user bootloader 2.10 e, checking for ota recovery, and booting recovery kernal image. Stops there.
Can you post a screen-shot of this ?
Thx Josh
See if this works.
Username5.2 said:
See if this works.
Click to expand...
Click to collapse
When on that screen does the PC see it as anything in device manager ?
So you do have your nvflash files backed up ?
Thx Josh
No it is not picked up by the PC at all.
And no I had just flashed the custom recovery with fastboot. Had not done anything else. Next step was to run wheelie. Didn't get that far.
Username5.2 said:
No it is not picked up by the PC at all.
And no I had just flashed the custom recovery with fastboot. Had not done anything else. Next step was to run wheelie. Didn't get that far.
Click to expand...
Click to collapse
Well, with no fastboot or adb an no nvflash a motherboard is the only way ...
Sorry for the crappy news ....
Thx Josh
lj50036 said:
Well, with no fastboot or adb an no nvflash a motherboard is the only way ...
Sorry for the crappy news ....
Thx Josh
Click to expand...
Click to collapse
Probably; but: screenshots show, that it is a tf101 (Eee Pad Transformer). I thought that I read in the forums some workaround, because it has no encrypted bootloader. Can be wrong, I'm no expert. Search!
edit:
Found it:
lilstevie said:
There is no concept of locked or unlocked in the tf101 bootloader, in the most general sense it is unlocked as it allows booting of unsigned kernels, and flashing of unsigned blobs.
the leaked key allows lower level communication (bootrom) with the device and can recover from bootloader errors.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=22408864&postcount=3
Josh, thanks. And no problem on the crappy news. I kinda figured this was the case.
OK well after searching eBay and forums, I'm going to just get another prime. $80 for the logic board or $100 for a whole working tablet. So I will let this one sit awaiting a fix or a cheap logic board.
In the mean time can someone tell me where I screwed up?
I hate stock ROMs, and the sound of an "unbrickable tablet" by flashing new recovery is appealing. For that I will be attempting to back up these nvflash files on my new prime but I don't want another expensive paperweight.
So 2 questions.
Where did it all go wrong?
Am I following the set of instructions you all would recommend? I did get the link from this forum.
Thanks again.
das chaos said:
Probably; but: screenshots show, that it is a tf101 (Eee Pad Transformer). I thought that I read in the forums some workaround, because it has no encrypted bootloader. Can be wrong, I'm no expert. Search!
Click to expand...
Click to collapse
It is def. A tf201. All that writing in the screenshot is new except "the device is unlocked" since I flashed the recovery image from the link.
das chaos said:
Probably; but: screenshots show, that it is a tf101 (Eee Pad Transformer). I thought that I read in the forums some workaround, because it has no encrypted bootloader. Can be wrong, I'm no expert. Search!
edit:
Found it:
http://forum.xda-developers.com/showpost.php?p=22408864&postcount=3
Click to expand...
Click to collapse
Its a really old bootloader, that is the way they use to look....
Thx Josh
Username5.2 said:
Josh, thanks. And no problem on the crappy news. I kinda figured this was the case.
OK well after searching eBay and forums, I'm going to just get another prime. $80 for the logic board or $100 for a whole working tablet. So I will let this one sit awaiting a fix or a cheap logic board.
In the mean time can someone tell me where I screwed up?
I hate stock ROMs, and the sound of an "unbrickable tablet" by flashing new recovery is appealing. For that I will be attempting to back up these nvflash files on my new prime but I don't want another expensive paperweight.
So 2 questions.
Where did it all go wrong?
Am I following the set of instructions you all would recommend? I did get the link from this forum.
Thanks again.
Click to expand...
Click to collapse
The bootloader is to old to flash that recovery, that is where you went wrong ....
Thx Josh
Username5.2 said:
OK so I might have screwed up my prime. I've done command line stuff and had custom ROMs on everything I own. But I am by no means an expert so please bear with me. I will explain my series of events to the best of my ability.
Starts off with a buggy ROM, i loaded it some time ago and have been dealing with it since. It was cm10 dated sometime in the middle of 2012. Did some searching and found that all the new ROMs were saying something about needing to nvflash to get blobs or something. No prob. Right?
Got everything prepared based off of these instructions:
androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
Downloaded recovery_tf201.img, fastboot, nvflash, and the drivers. The very first step went ok. It showed moving the .img and then flashing the file. When done the little blue bar went across the screen like it should have.
Here's were it all went bad. I ran the reboot command in fastboot, device rebooted, loaded android. I held power a sec and chose "reboot recovery". I can now get the device to do one of three things:
1. Asus splash screen showing device unlocked when powered normally. That's it.
2. Hold vol down gets asus screen with 4 lines: this device is unlocked, android cardhu-user bootloader 2.10 e, checking for ota recovery, and booting recovery kernal image. Stops there.
3. Volume up gets black screen apx mode
Also tried running battery dead. Still same thing.
Is there any hope for my prime?
Where did I go wrong? Was it by pressing "reboot recovery" from the os?
Arggg please help. Otherwise a guide to replace the main board would be great.
Anything else please ask.
Thanks all,
Nick
Click to expand...
Click to collapse
Username5.2 - We are sorry to hear about this issue you are having and we are more than happy to assist you. Please email us at [email protected] with your serial number and this post attached for assistance.
If you have any further questions, comments, or concerns please do not hesitate to let us know. We will be more than happy to assist you. Once again, thank you for choosing ASUS products and services.
Thank you,
-In Search of Incredible-
Technical Support Department
http://www.asus.com :: http://service.asus.com/
lj50036 said:
Its a really old bootloader, that is the way they use to look....
Thx Josh
The bootloader is to old to flash that recovery, that is where you went wrong ....
Thx Josh
Click to expand...
Click to collapse
Dang. I followed a link from this forum @
http://forum.xda-developers.com/showthread.php?t=1774352
That led me to this link I posted above:
androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
So that guide had me download an incorrect file? The files were downloaded right from that page. Check it out.
Username5.2 said:
Dang. I followed a link from this forum @
http://forum.xda-developers.com/showthread.php?t=1774352
That led me to this link I posted above:
androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
So that guide had me download an incorrect file? The files were downloaded right from that page. Check it out.
Click to expand...
Click to collapse
Your firmware version is 9.4.2.21 which is Android version 4.0.3 'ICE CREAM SANDWICH'
The guide is for 'JELLYBEAN' bootloaders....
That is why flashing said file was the wrong thing to do...
Sorry for the bad new... :crying:
Thx Josh
Hello guys,
I am searching for help, my elephone g6 does not start, rebooted it yesterday and it did not started ever again, not even in recovery mode, i tryed to flash stock rom but can't get him recognised by my computer, the omputer is always playing the sound connect->disconnect->connect->disconnect, within 30 seconds space more or less. i have no idea what to do more, anyone knws the problem and a possible solution?
cheers
thanks in advance.
Try looking up some recovery software from the manufacturer like HTC does. Otherwise is a little to vague.
scottbear said:
Try looking up some recovery software from the manufacturer like HTC does. Otherwise is a little to vague.
Click to expand...
Click to collapse
So, i got my phone to connect to the computer, but the SP flash tools goes to 100% red bar and doesn't do anything more, i am doing everything correctly but it just gets stuck 100% red bar and don't move it has ben like 30+ minutes and nothing, any tip on that?
cheers
n3las said:
So, i got my phone to connect to the computer, but the SP flash tools goes to 100% red bar and doesn't do anything more, i am doing everything correctly but it just gets stuck 100% red bar and don't move it has ben like 30+ minutes and nothing, any tip on that?
cheers
Click to expand...
Click to collapse
No clue. Have you tried flashing a recovery?
scottbear said:
No clue. Have you tried flashing a recovery?
Click to expand...
Click to collapse
hello again, yes i tryed and that's my problem, my SPflashtools just get stuck with a 100% progreress red bar and does not move on, i have done everything correctly, exact stock rom, drivers and so.
n3las said:
Hello guys,
I am searching for help, my elephone g6 does not start, rebooted it yesterday and it did not started ever again, not even in recovery mode, i tryed to flash stock rom but can't get him recognised by my computer, the omputer is always playing the sound connect->disconnect->connect->disconnect, within 30 seconds space more or less. i have no idea what to do more, anyone knws the problem and a possible solution?
cheers
thanks in advance.
Click to expand...
Click to collapse
I have the same problem :crying:
Does someone know what to do?
I have downloaded REMIX OS beta version today and when I was installing it I was getting this error " failed to find cpu0 device node" after it it's get stuck at boot nothing happens after it!!
So please members help to do it....
i got the error too but it booted and installed. no other issues. saw the same error on Liliputing's video for beta. so most likely something else is causing the freeze
kantelia parth said:
I have downloaded REMIX OS beta version today and when I was installing it I was getting this error " failed to find cpu0 device node" after it it's get stuck at boot nothing happens after it!!
So please members help to do it....
Click to expand...
Click to collapse
I have same bug... anyone can help?
Yes this error line show when booting, don't known what's it mean
But my remix was booted and running fine no issue
Maromi said:
i got the error too but it booted and installed. no other issues. saw the same error on Liliputing's video for beta. so most likely something else is causing the freeze
Click to expand...
Click to collapse
Which bit is your PC??
I mean 32bit or 64bit???
And you have installed with PENDERIVE or hard drive ??
kantelia parth said:
I have downloaded REMIX OS beta version today and when I was installing it I was getting this error " failed to find cpu0 device node" after it it's get stuck at boot nothing happens after it!!
So please members help to do it....
Click to expand...
Click to collapse
it's not an error, it's a warning that can be ignored
https://bugzilla.redhat.com/show_bug.cgi?id=1254210
When I was installing it got to around 45% and then my screen went black and was getting no video signal for about 8 minutes. I just let it keep running and it came back on and finished and booted. Maybe that's what is happening?
fgdn17 said:
it's not an error, it's a warning that can be ignored
https://bugzilla.redhat.com/show_bug.cgi?id=1254210
Click to expand...
Click to collapse
So what will be the problem while installing REMIX OS BETA version ..!! According to u???
rcgamer said:
When I was installing it got to around 45% and then my screen went black and was getting no video signal for about 8 minutes. I just let it keep running and it came back on and finished and booted. Maybe that's what is happening?
Click to expand...
Click to collapse
I think that was the screen going to sleep. I toutched my kepboard and it came back on again. (mouse won't do anything as it's still command line)
kantelia parth said:
So what will be the problem while installing REMIX OS BETA version ..!! According to u???
Click to expand...
Click to collapse
I wouldn't know, and you can keep guessing forever BUT if you learn how to read the error logs like
logcat / dmesg / bugreport you may get some indication of why it's not working for you yet working
for many others.
fgdn17 said:
I wouldn't know, and you can keep guessing forever BUT if you learn how to read the error logs like
logcat / dmesg / bugreport you may get some indication of why it's not working for you yet working
for many others.
Click to expand...
Click to collapse
Can u find in favour of us!!!?
kantelia parth said:
I have downloaded REMIX OS beta version today and when I was installing it I was getting this error " failed to find cpu0 device node" after it it's get stuck at boot nothing happens after it!!
So please members help to do it....
Click to expand...
Click to collapse
I got that error on every device i've put remix on, all of them boot and install just fine. You may want to try the install again.
I had the same error. I had not disabled secure boot. After I did that it worked fine. On first boot it did take about 10 minutes. Not sure if it was checking the disk or formatting it. Anyway, make sure you disable secure boot. (hold down F2 then press power on for my lenovo Y410p which was totally obliterated and made useless by Windows 10)
fsuinnc said:
I had the same error. I had not disabled secure boot. After I did that it worked fine. On first boot it did take about 10 minutes. Not sure if it was checking the disk or formatting it. Anyway, make sure you disable secure boot. (hold down F2 then press power on for my lenovo Y410p which was totally obliterated and made useless by Windows 10)
Click to expand...
Click to collapse
How do I do it please help me bro!!!
✌✌✌
kantelia parth said:
I have downloaded REMIX OS beta version today and when I was installing it I was getting this error " failed to find cpu0 device node" after it it's get stuck at boot nothing happens after it!!
So please members help to do it....
Click to expand...
Click to collapse
Try to switch display port to onboard may be it doesn't support the gpu
For Legacy only: put nouveau.modeset=1 i915.modeset=0 in the grub if you have a Nvidia GPU
kantelia parth said:
How do I do it please help me bro!!!
Click to expand...
Click to collapse
It depends on what kind of system you have. Google search how to get to the boot menu for your particular system. Usually you shut down the system then press and hold down a particular button while you turn on the power. Usually you hold esc or F1 or F2 but different systems use different buttons. When you get to the boot menu it looks very old school. use left and right arrows to get to boot tab. arrow down to Secure boot and (I think) F5 or F6 to switch from enabled to disabled. follow instructions on screen to exit and save.
AmoraRei said:
For Legacy only: put nouveau.modeset=1 i915.modeset=0 in the grub if you have a Nvidia GPU
Click to expand...
Click to collapse
Where should I put this ????
fsuinnc said:
It depends on what kind of system you have. Google search how to get to the boot menu for your particular system. Usually you shut down the system then press and hold down a particular button while you turn on the power. Usually you hold esc or F1 or F2 but different systems use different buttons. When you get to the boot menu it looks very old school. use left and right arrows to get to boot tab. arrow down to Secure boot and (I think) F5 or F6 to switch from enabled to disabled. follow instructions on screen to exit and save.
Click to expand...
Click to collapse
OK !!
I will try this ..
Same Problem
Stuck black screen on PC1 (32bit) and similar on new PC2 (64bit UEFI)... This OS just doesn't work at all.
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...
Here was a Guide. Someone said people don't care about Me or My Work so...
I followed the steps, but I can't get into bootloader mode. please help. When I reboot to bootloader, the screen is blank and doesn't respond to fast boot commands.
Noob here Never posted but I've lurked quite alot.
Installing magisk works fine, but not any GSI
I'm just getting bootloops, reboots every few seconds or stuck at the splash screen.
Restoring with EMMA works, so It's not bricked.
I've been struggling with this for over two days and I can't understand what's going wrong
RP1408 said:
I followed the steps, but I can't get into bootloader mode. please help. When I reboot to bootloader, the screen is blank and doesn't respond to fast boot commands.
Click to expand...
Click to collapse
Is Your LED Blue if you attech to USB? If yes, are your drivers not correctly installed...
strandplask said:
Noob here Never posted but I've lurked quite alot.
Installing magisk works fine, but not any GSI
I'm just getting bootloops, reboots every few seconds or stuck at the splash screen.
Restoring with EMMA works, so It's not bricked.
I've been struggling with this for over two days and I can't understand what's going wrong
Click to expand...
Click to collapse
Well, you can try:
fastboot flash super GSI.img (in fastbootd)
That may work... Let me know!
Hi.
I'm having problems unlocking my bootloader and accessing fastboot. I even installed Ubuntu because I thought the problem was my Windows drivers. No luck. It recognizes fastbootd thingie (adb reboot fastboot) and ADB commands, but button up and usb plug-in doesn't work, no matter the platform. Device info says it's unlockable, model is XQ-CT54, software version is 64.1.A.0.857. what I'm supposed to do? I can give more info if needed. Haven't tried flashing stock yet.
edit. Never mind, I got it, and on Windows! I just have to pick manually those Sony drivers from the list and feed them for device manager every time I use fastboot. Acceptable.
Ok I know this thread is for the 1 IV, but since this is basically a copy-paste of the previous tutorials for 1 III etc.: Is this procedure android 13 approved, for the IV series as well as for the III series? I myself have the 5 III but just recently a colleague asked me if there's a way to root their 5 IV which is why I stumbled over this thread in the first place.
Both of the phones are running on Android 13 since the end of December.
Retenor said:
Ok I know this thread is for the 1 IV, but since this is basically a copy-paste of the previous tutorials for 1 III etc.: Is this procedure android 13 approved, for the IV series as well as for the III series? I myself have the 5 III but just recently a colleague asked me if there's a way to root their 5 IV which is why I stumbled over this thread in the first place.
Both of the phones are running on Android 13 since the end of December.
Click to expand...
Click to collapse
If they have international version yes they can if they have US version no they can't
raven213 said:
If they have international version yes they can if they have US version no they can't
Click to expand...
Click to collapse
And this goes for III series as well as with Android 13 for either of the two? Once again sorry for asking this here but neither of us can afford a brick and I wouldn't get an answer in the 5 III thread anymore after someone seemed to have had issues there with A13
I
Retenor said:
And this goes for III series as well as with Android 13 for either of the two? Once again sorry for asking this here but neither of us can afford a brick and I wouldn't get an answer in the 5 III thread anymore after someone seemed to have had issues there with A13
Click to expand...
Click to collapse
I think with the III you should be able to root I know they just started blocking bootloader on the IV
raven213 said:
I
I think with the III you should be able to root I know they just started blocking bootloader on the IV
Click to expand...
Click to collapse
Both of us are located in europe so I'm guessing the bootloader block doesn't affect us in this case, guess I'll just have to try as soon as I find the time to do it
Has anyone tried flashing GSIs? I need help flashing lineage OS. After rebooting from fastboot I'm stuck at boot animation (waited ~20 minutes). AOSP GSI from android website works and boots in seconds but not lineage os, please help.
Miustone said:
You will be fine with it somehow!
All the Best for the future,
Miu
Click to expand...
Click to collapse
Duudddeee... Nooo...!
MOD EDIT: civil words
K. You know google caches pretty much the entire internet though right?
ParkourPaul said:
K. You know google caches pretty much the entire internet though right?
Click to expand...
Click to collapse
Most people will never do that and just jump off here. The point was to revert my contributions on the Xperia Forums and to take My Work aside from the Guides offline. There are still forks around and there might be cached copies of my Threads. But my personal support ends here and I won't continue my work for Xperias starting today. Please respect that and have a great time with your Device anyways!
Thread has been closed as OP @Miustone removed the content of the opening post.
Regards
Oswald Boelcke
Senior Moderator