Just noticed that the Chinese site Rerede.com has finally managed to build support for the WiFi card in the Surface Pro in a build of Android-IA.
This build seems to support everything, apart from bluetooth:
Original link: I don't have rights to place URLs in as I haven't posted enough here. If a moderator can add the link here, I would appreciate it.
Original text (from Google Translate):
Code:
All along, only heard Surface Pro can run Ubuntu and Android. But never seen someone real up and running, often took a running Live CD boot to coax interface, now Rerede.com released China's first support for Surface Pro Android system. Support the Android installed on your machine up. And it can coexist with your Windows!
Working conditions:
· Touch
· Keyboard
· Camera
· Gravity sensor · WIFI
· Other
Not supported:
· Bluetooth
Compatibility:
· Support and native dual-boot Windows 8
• The need to disable Secure Boot
Data is priceless! Please make the necessary data backup before installing! We do not assume any responsibility for loss of data!
Unzip password: rerede.com
Copy the code
Preparation:
In a hard disk to free up more than 1G unallocated space, 4GB recommended
Installation:
1, decompress, burn to use UltraISO to live.img U disk
2, disable SecureBoot
3, the use of U disk boot, select the third item, manually install Android4, tips Choose disk to install Android, select the disk you want to install, I chose Surface of SSD (1),
Tips Do you want to preserve Windows and dual boot (if dual boot Windows), press Y
5 Tips Do you want to resize Windows to make more space (whether android resized), press N
6 Tips Install GummiBoot BootLoader (using gummiboot), press Y
7, when prompted Enter boot menu timeout (boot menu wait time), I chose 5
8, press Enter to install, the installation process approximately less than 1 minute.
9 After the installation is complete, unplug the U disk, enter the restart to complete the installation reproduced or quoted, please indicate from the hot community , Rerede.com
Pictures attached
That looks really nice. Hope they figure out the bluetooth as well.
JLIT99 said:
Just noticed that the Chinese site Rerede.com has finally managed to build support for the WiFi card in the Surface Pro in a build of Android-IA.
This build seems to support everything, apart from bluetooth:
Click to expand...
Click to collapse
Thanks for this, it's really working, although far from perfect. Fastest touch response on android =))
Here's the direct link to download: http://rerede.com/surface.android-ia.rerede.com.vPRC2.zip
Could you get the front Cam working?
Turns out that front cam doesn't run by default. I fixed it along with some other things like youtube playback, play store etc. It's almost perfect now
Surface 2 Pro
Has someone tested these instructions on a Surface 2 Pro ? Working ?
Unfortunatly, I have a Surface 1 Pro and encounter the following error:
FATAL: ASERTION FAILED bootable/iago/plugins/gummiboot.c:gummiboot_execute:154 'efibootmgr' encountered an error (status 100)
Gummiboot the EFI bootmgr does not install. Maybe it would be possible to install it manually.
Secure Boot is disabled, and I also tried different USB sticks and the original unmodifed Android-IA image. No success.
Current progress: managed to boot into Android-IA using Refined, which itselfs loads Gummiboot.
However the overall stability of Android-IA on the Surface Pro is not good:
- Wifi most of the time does not work. Turning it on/off does not help. Neither does it help to disable power saving features. Maybe we could try a different driver
- Sometimes when the device is not used for about 2 minutes and goes black, it cannot be turned on again. I have to hold the power button to force a shutdown.
ToniSoft said:
Current progress: managed to boot into Android-IA using Refined, which itselfs loads Gummiboot.
However the overall stability of Android-IA on the Surface Pro is not good:
- Wifi most of the time does not work. Turning it on/off does not help. Neither does it help to disable power saving features. Maybe we could try a different driver
- Sometimes when the device is not used for about 2 minutes and goes black, it cannot be turned on again. I have to hold the power button to force a shutdown.
Click to expand...
Click to collapse
What do you mean by using Refined?
how do you get this installed? When i reach the instructions to press Y if to save dual boot my type keyboard does not work. How did you proceed? Thank you.
zcrugby,
How do you get this installed? When i reach the instructions to press Y if to save dual boot my type keyboard does not work. How did you proceed? Thank you.
Click to expand...
Click to collapse
You need to use a USB hub, so that you can have you USB stick and USB keyboard attached simultaneously. This installation program does not recognize the Surface keyboard, but it does recognize a standard USB keyboard.
I, however am having a different problem. I get (almost) to the end of the whole process, after it says press enter to continue with the installation and does a bunch of stuff, but then give the following error:
FATAL: ASERTION FAILED bootable/iago/plugins/gummiboot.c:gummiboot_execute:154 'efibootmgr' encountered an error (status 100)
It was mentioned earlier in this thread, but no one seemed to shed any light on the subject. In other forums some have suggested that it was just an incompatible memory stick, but I have not tried multiple memory stick by different manufactures...
Others have suggested that you need to disable AHCI and instead run in IDE mode, but with the Surface Pro 2's woefully underwhelming BIOS, I haven't yet figured out how to disable AHCI. There's some that say that simply changing some registry keys will do the trick, but I haven't gotten that to work yet, and I don't have extremely high hope for it when I do.
Does anyone here have any thoughts about this error??? Anyone run into it who has successfully gotten it working after seeing this error? If so, how?
Thanks!
please help: Fatal Asertion Failed... (status 100)
Does anyone have any light to shine on the follow error? Please?
FATAL: ASERTION FAILED bootable/iago/plugins/gummiboot.c:gummiboot_execute:154 'efibootmgr' encountered an error (status 100)
I've detailed some of the (failed) solutions I've found on other boards/threads regarding to how to get around this error on other devices, but none seem to be the trick for getting past this error on the surface. I'm really surprised that there don't seem to be more people trying to install Android on the MS Surface... or perhaps there are, but for most people things go more smoothly. Any help our there, please?
Thinking about returning the surface if I can't get android on it. I'm really interested in a powerful tablet that can dual boot windows/android.
Quixtrike said:
Does anyone have any light to shine on the follow error? Please?
FATAL: ASERTION FAILED bootable/iago/plugins/gummiboot.c:gummiboot_execute:154 'efibootmgr' encountered an error (status 100)
I've detailed some of the (failed) solutions I've found on other boards/threads regarding to how to get around this error on other devices, but none seem to be the trick for getting past this error on the surface. I'm really surprised that there don't seem to be more people trying to install Android on the MS Surface... or perhaps there are, but for most people things go more smoothly. Any help our there, please?
Thinking about returning the surface if I can't get android on it. I'm really interested in a powerful tablet that can dual boot windows/android.
Click to expand...
Click to collapse
When you get this error, it means that efibootmgr is unable to create the boot entry but all the files are in fact in boot partition. I also received this error, but since I also had Ubuntu (well, you kind of also need Ubuntu to access Android partitions easily anyway) I used the efibootmgr in Ubuntu to manually create Android entry. This way, I'm able to select advanced boot options under Windows (created desktop shortcut) and switch to Android really easily. You should leave the Windows as default so that you might never need a keyboard attached for boot menu. If you don't want to install Ubuntu just to solve this error, you *might* get away with a live Ubuntu CD, however I never tried that.
ozkaya said:
When you get this error, it means that efibootmgr is unable to create the boot entry but all the files are in fact in boot partition. I also received this error, but since I also had Ubuntu (well, you kind of also need Ubuntu to access Android partitions easily anyway) I used the efibootmgr in Ubuntu to manually create Android entry. This way, I'm able to select advanced boot options under Windows (created desktop shortcut) and switch to Android really easily. You should leave the Windows as default so that you might never need a keyboard attached for boot menu. If you don't want to install Ubuntu just to solve this error, you *might* get away with a live Ubuntu CD, however I never tried that.
Click to expand...
Click to collapse
Hi ozkaya, this sounds really promising, and I've even kind of gotten it installed, but it was going crazy (constant nonstop scrolling to select a boot mode as if I were holding down the arrow key; ended up being like Russian Roulette booting), so I decided to clean the slate and try again, the only problem is, I keep getting this error again... As a side note, I'm not overtly familiar with Ubuntu though I do have OSX successfully running on the Surface Pro 2, but I'm using a thumb drive to boot into it.
A few follow up questions:
-Are you saying that you use grub to boot into Android rather than gummiboot?
-Would you be willing to described "used the efibootmgr in Ubuntu to manually create Android entry" in more detail?
-How exactly to you select advanced boot options under Windows & create desktop shortcut?
*sorry if any of these questions are super basic. Back in the early XP days I was fairly savvy with dual/triple booting, but windows 8 and the Surface Pro's lackluster BIOS options are completely baffling me.
Quixtrike said:
Hi ozkaya, this sounds really promising, and I've even kind of gotten it installed, but it was going crazy (constant nonstop scrolling to select a boot mode as if I were holding down the arrow key; ended up being like Russian Roulette booting), so I decided to clean the slate and try again, the only problem is, I keep getting this error again... As a side note, I'm not overtly familiar with Ubuntu though I do have OSX successfully running on the Surface Pro 2, but I'm using a thumb drive to boot into it.
A few follow up questions:
-Are you saying that you use grub to boot into Android rather than gummiboot?
-Would you be willing to described "used the efibootmgr in Ubuntu to manually create Android entry" in more detail?
-How exactly to you select advanced boot options under Windows & create desktop shortcut?
*sorry if any of these questions are super basic. Back in the early XP days I was fairly savvy with dual/triple booting, but windows 8 and the Surface Pro's lackluster BIOS options are completely baffling me.
Click to expand...
Click to collapse
1- No I'm not using grub, in fact I also tried to daisy chain grub booting gummiboot booting Android and it doesn't work. I'm using native EFI entry.
2- I don't have it written up somewhere, I did it as I was reading and trying. But basically, you first need to install Ubuntu with dual boot with Windows. Have a look at the /boot partition, you will see the gummiboot files and config files there. Then research command line parameters for efimootmgr program and create the entry for the gummiboot file in /boot partition.
3- Just use google for this one, you can select advanced startup options somewhere from the settings in Windows 8 fancy menu. You can also create desktop shortcut for this. Once you completed Step 2, you will see Windows, Ubuntu and Android entries there. Since, Windows will be default, when you would like to switch to Android, you just double tap the shortcut and select Android. In Android you just power off and next restart will be Windows again. No keyboards, mouse etc needed. I also got the front cam and youtube playback working. Only bluetooth doesn't work.
Surface Pro 2
Anyone got this to work with Surface Pro 2? I am thinking of getting one, and if it could run android, im definitely getting one!
(I don't really see the point of getting Surface 1 when the 2 is out now)
I have followed the instructions and it installed fine, and then booted to android however as soon as I reboot I can no longer run android (or fastboot/recovery) without reinstalling it all over again from USB.
The error I get from gummiboot is:
HandleProtocol (DiskIoProtocol): Unsupported
Failed to start boot image 'Android': Unsupported
I would really appreciate some help from anyone who has a better understanding of this since I couldn't find anyone with a similar problem.
(I am using a 128gb Surface Pro 1/Original)
Thanks
when turning trusted platform module on and off it works sometimes
Jacob.Halsey1 said:
I have followed the instructions and it installed fine, and then booted to android however as soon as I reboot I can no longer run android (or fastboot/recovery) without reinstalling it all over again from USB.
The error I get from gummiboot is:
HandleProtocol (DiskIoProtocol): Unsupported
Failed to start boot image 'Android': Unsupported
I would really appreciate some help from anyone who has a better understanding of this since I couldn't find anyone with a similar problem.
(I am using a 128gb Surface Pro 1/Original)
Thanks
Click to expand...
Click to collapse
I'm having the same problem over and over .. still no luck
Where to begin? Logic would dictate, the beginning.
I'll do my best to be brief with the backstory.
Months ago I ordered a Jide Ultratablet to use as my portable workhorse. At first things were peachy until a rather monumental lag began to manifest every 15-45 seconds. It made the device impossible to utilize in any productive fashion, so I contacted Jide and opened up a support ticket. After months (in no way an exaggeration) of barely responsive correspondence, during which I sent them a video to demonstrate the problem, they finally came back to me with an email containing a link to a compressed folder containing the Remix 2.0 images, and also a link to a rather vague and complicated tutorial on how to flash Remix 1.5 manually to a device. (In fact, I tried to include a link to the tutorial, but I am unable to since I haven't posted to the forum enough. I am happy to PM it or email it to anyone who might like to help) I can only assume I am meant to apply the same logic to the Remix 2.0 files they sent me. Seemed a bit dicey at first glance, but while I'm by no means an expert, I'm no slouch in this arena and I'm a very quick study.
Now, on to the proverbial meat and potatoes:
If you were able to contact me for a link to the tutorial in question, you will have undoubtedly seen that they indicate one should use ADB-Fastboot as a means to flash the recovery image. No real surprises there. I have ADB and Fastboot installed on my PC (Windows 10). I also have the ADB drivers installed and have confirmed the addition to my PATH. (eg: ;C:\ADB) I can also confirm that it is working fine since I am able to pull up a terminal and issue the ADB command and it gives me the usual wall of commands. The problem is that my device (Ultratablet) is not being seen by ADB. I have checked my USB drivers and they are all up to date and installed properly. My PC sees the device no problem and there is no indication of any sort of connection error. I've also tried different cables and ports. Yet, I can't access it via ADB and thus am unable to issue commands to my device such as "adb reboot bootloader" or "fastboot reboot-bootloader".
My next logical approach was to attempt forcing the device into fastboot mode using the hardware button combination, which is not listed specifically for the Ultratablet anywhere, I might add. (Power key + Volume up) It brings me to a boot options menu with the selections "Continue/Fastboot Protocol/Recovery Kernel/Reboot/Poweroff/Forced Recovery". Ateempting to select Fastboot Protocol causes the display to shut off for a moment, the device to vibrate once, and then the display to turn back on back at the same menu full of selections.
So, in summary, I am expected to flash the device using fastboot and yet I can't even get the device into fastboot mode, let alone issue commands from my PC terminal. As I highlighted near the beginning, teh Jide support team is incredibly unresponsive and not overly helpful. I have notified them of this same set of issues, but I don't expect to hear back in any expedient fashion and I thought one of the mighty members here on XDA might be able to help me come up with a next step in the meantime. I'd cerainly love to be able to use my shiny new tablet.
In any case, thank you for your time.
Kind regards.
Shaiden
XDA Visitor said:
Where to begin? Logic would dictate, the beginning.
I'll do my best to be brief with the backstory.
Months ago I ordered a Jide Ultratablet to use as my portable workhorse. At first things were peachy until a rather monumental lag began to manifest every 15-45 seconds. It made the device impossible to utilize in any productive fashion, so I contacted Jide and opened up a support ticket. After months (in no way an exaggeration) of barely responsive correspondence, during which I sent them a video to demonstrate the problem, they finally came back to me with an email containing a link to a compressed folder containing the Remix 2.0 images, and also a link to a rather vague and complicated tutorial on how to flash Remix 1.5 manually to a device. (In fact, I tried to include a link to the tutorial, but I am unable to since I haven't posted to the forum enough. I am happy to PM it or email it to anyone who might like to help) I can only assume I am meant to apply the same logic to the Remix 2.0 files they sent me. Seemed a bit dicey at first glance, but while I'm by no means an expert, I'm no slouch in this arena and I'm a very quick study.
Now, on to the proverbial meat and potatoes:
If you were able to contact me for a link to the tutorial in question, you will have undoubtedly seen that they indicate one should use ADB-Fastboot as a means to flash the recovery image. No real surprises there. I have ADB and Fastboot installed on my PC (Windows 10). I also have the ADB drivers installed and have confirmed the addition to my PATH. (eg: ;C:\ADB) I can also confirm that it is working fine since I am able to pull up a terminal and issue the ADB command and it gives me the usual wall of commands. The problem is that my device (Ultratablet) is not being seen by ADB. I have checked my USB drivers and they are all up to date and installed properly. My PC sees the device no problem and there is no indication of any sort of connection error. I've also tried different cables and ports. Yet, I can't access it via ADB and thus am unable to issue commands to my device such as "adb reboot bootloader" or "fastboot reboot-bootloader".
My next logical approach was to attempt forcing the device into fastboot mode using the hardware button combination, which is not listed specifically for the Ultratablet anywhere, I might add. (Power key + Volume up) It brings me to a boot options menu with the selections "Continue/Fastboot Protocol/Recovery Kernel/Reboot/Poweroff/Forced Recovery". Ateempting to select Fastboot Protocol causes the display to shut off for a moment, the device to vibrate once, and then the display to turn back on back at the same menu full of selections.
So, in summary, I am expected to flash the device using fastboot and yet I can't even get the device into fastboot mode, let alone issue commands from my PC terminal. As I highlighted near the beginning, teh Jide support team is incredibly unresponsive and not overly helpful. I have notified them of this same set of issues, but I don't expect to hear back in any expedient fashion and I thought one of the mighty members here on XDA might be able to help me come up with a next step in the meantime. I'd cerainly love to be able to use my shiny new tablet.
In any case, thank you for your time.
Kind regards.
Shaiden
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist.
First, you'll need to create an account so you can post in the other sections.
After you have done that, you can post your questions and ask the experts here:
http://forum.xda-developers.com/android/help
You're sure to receive quality answers there.
Good luck and welcome to XDA!
I am a PC technician and don't know much about phones. A customer brought me in a mostly dead phone and wants pictures of his kids recovered. I believe this is probably possible given the state. I want to give enough information without overloading anyone looking to help, so I will put it in sections.
What I know about the phone:
I never saw it working and I'm not a phone guy. The back says the model is XT901. This customer is not a tech, so only push updates would have likely been done., if even those were done. It came in roughly 2 weeks ago. That is pretty much the extent of what I know about the phone and its OS.
What the problem is:
When booting normally the Motorola logo comes up with the swirling blue around it. It stays on that screen forever.
What the phone can do:
I can get into a couple different menu systems with different key presses (which I don't exactly remember right now. It's kind of trial and error to get into the one I want). The less helpful menu has a "Recovery" option which just makes the phone boot to the swirling logo again. By retrying with different keypress combinations I can get it to show the android on his back with the exclamation mark. From there I can reboot into a different menu, where I found QC Diag, among other things.
What I need to do:
I need to connect the phone to a Windows 7 Professional 64 bit computer to recover, especially, pictures of his kid that he didn't have backed up.
The problem I ran into:
Four devices do show up in the device manager as "Unknown device". I did manage to get the QC Diag port set up following the instructions here:
googlebought.blogspot.com
/2014/12/motorola-qc-diagnostic-driver.html (separated because I can't post links, but the information might be important)
I used the PID listed on the page since I have no idea what to change it to or even if I need to change it, but it did seem to work for one unknown device. I then right-clicked on each of the 4 "Unknown" devices and browsed to that folder. One was detected and updated, the Motorola QC Diag Port on COM3. This did not make a drive letter show up as I had hoped.
What I have tried:
Downloading a few dozen drivers to get all 4 of these devices detected, starting with the latest standard drivers for the phone, Motorola Device Manager 2.5.4 and Motorola Mobile Drivers Installation 6.4.0. This is how I got to just 4 devices listed as "Unknown". Of course, there are currently only 3 unknown since getting the QC Diag port going.
My technical abilities:
I have been a PC tech for about 15 years and am pretty good at it. I have rooted Android devices before, but frankly that's just "download a program, push a button". I am utterly unskilled in Android, but I can follow even complicated instructions.
I am hoping that there is a mode I can go into (I believe I've tried all I can get into) or a driver I can install which will allow me to browse the directories on the phone. I realize this is more complicated than it sounds because of the difference in file systems. I would imagine that since I can see these devices in certain modes this is probably possible.
Thank you in advance for any help you can offer. I'm sorry it's long-winded, but I wanted to be thorough. Hopefully it's organized enough that you can skip over any information you don't need.
XDA Visitor said:
I am a PC technician and don't know much about phones. A customer brought me in a mostly dead phone and wants pictures of his kids recovered. I believe this is probably possible given the state. I want to give enough information without overloading anyone looking to help, so I will put it in sections.
What I know about the phone:
I never saw it working and I'm not a phone guy. The back says the model is XT901. This customer is not a tech, so only push updates would have likely been done., if even those were done. It came in roughly 2 weeks ago. That is pretty much the extent of what I know about the phone and its OS.
What the problem is:
When booting normally the Motorola logo comes up with the swirling blue around it. It stays on that screen forever.
What the phone can do:
I can get into a couple different menu systems with different key presses (which I don't exactly remember right now. It's kind of trial and error to get into the one I want). The less helpful menu has a "Recovery" option which just makes the phone boot to the swirling logo again. By retrying with different keypress combinations I can get it to show the android on his back with the exclamation mark. From there I can reboot into a different menu, where I found QC Diag, among other things.
What I need to do:
I need to connect the phone to a Windows 7 Professional 64 bit computer to recover, especially, pictures of his kid that he didn't have backed up.
The problem I ran into:
Four devices do show up in the device manager as "Unknown device". I did manage to get the QC Diag port set up following the instructions here:
googlebought.blogspot.com
/2014/12/motorola-qc-diagnostic-driver.html (separated because I can't post links, but the information might be important)
I used the PID listed on the page since I have no idea what to change it to or even if I need to change it, but it did seem to work for one unknown device. I then right-clicked on each of the 4 "Unknown" devices and browsed to that folder. One was detected and updated, the Motorola QC Diag Port on COM3. This did not make a drive letter show up as I had hoped.
What I have tried:
Downloading a few dozen drivers to get all 4 of these devices detected, starting with the latest standard drivers for the phone, Motorola Device Manager 2.5.4 and Motorola Mobile Drivers Installation 6.4.0. This is how I got to just 4 devices listed as "Unknown". Of course, there are currently only 3 unknown since getting the QC Diag port going.
My technical abilities:
I have been a PC tech for about 15 years and am pretty good at it. I have rooted Android devices before, but frankly that's just "download a program, push a button". I am utterly unskilled in Android, but I can follow even complicated instructions.
I am hoping that there is a mode I can go into (I believe I've tried all I can get into) or a driver I can install which will allow me to browse the directories on the phone. I realize this is more complicated than it sounds because of the difference in file systems. I would imagine that since I can see these devices in certain modes this is probably possible.
Thank you in advance for any help you can offer. I'm sorry it's long-winded, but I wanted to be thorough. Hopefully it's organized enough that you can skip over any information you don't need.
Click to expand...
Click to collapse
Hi and welcome to XDA.
Your device has a dedicated forum here but it's very quiet as it isn't the most popular phonein the world.
You can try posting your query there or in: Android Q&A,Help and Troubleshooting.
You'll have to create an account to post in the main forums.
Good luck
My device just got bricked. It was part of the recall and I had removed TegraOTA long ago. Today, after a few weeks of testing out CM13, I decided to go back to stock, remembered to flash the NoMoreOTA zip file but for some reason, it didn't stick. My device started downloading an update which I failed to get suspicious at, then shut down and hasn't come back online since.
This is far more than the frustration of losing a device and its data. It's a scary thought that NVidia has the ability to so utterly control our devices from a distance, with very little that can be done to prevent it if you're an average user. Remember that fuss when Amazon used DRM in their EBooks to remotely delete them from the computers of customers that legally purchased and should've had full rights to the content? This is inexcusable, and we must work to find a fix and pressure NVidia into giving up this disturbing practice.
Here are a basic list of resources I'm researching that have potential, I'll be posting as stream-of-consciousness and these links will also be here for reference when I reboot into Linux for some of the more advanced stuff. I can't make any promises, but stay tuned, this might just work!
Resources
Main XDA discussion RE kill switch
An old method that worked on the first variation of the kill switch (doesn't help anymore, since now the kill switch directly attacks the bootloader)
More discussion on the topic:
https://forum.xda-developers.com/shield-tablet/help/shield-tablet-stuck-apx-mode-black-t3074446
So far:
Bootloader is corrupted. Device is showing as APX.
Step one, therefore: Download APX drivers.
I found these for the Note 7, weren't easy to come across.
Slight issue with signature verification. You need to reboot into advanced settings and disable device driver signature verification.
http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
To use NVFlash, we need the device's SKB. Most forum members seem to agree that's virtually impossible without a leak from NVidia themselves, but those same people also claim the same issue with getting an APX driver for the Shield, so maybe it can be done. A hopeful post on the matter:
[GUIDE] Recovering Recovery/Obtaining SKB
Below link looks promising, need to obtain blob from stock rom. Guy claims he has the blob file, but we still need the SBK:
https://www.reddit.com/r/theNvidiaS...shield_tablet_bricked_at_1114_pm_est/cu2kudk/
This might help:
SBCalc - Generate your SBK (v1.1)
https://forum.xda-developers.com/showthread.php?t=1927818
What is NVFlash and what are SBKs?
http://www.androidroot.mobi/pages/the-inner-workings-of-secure-boot-key-and-nvflash/
More unresolved threads on this topic:
https://forum.xda-developers.com/shield-tablet/help/shield-tablet-stuck-apx-mode-black-t3074446
https://forum.xda-developers.com/shield-tablet/general/recover-y01-battery-shield-tablet-t3199153/
Lives Updates To Come
You cant repair kill switched NST, because tegraOta attack bootloader at low level and btld is pernamently corrupted.
Also Since Nvidia Tegra Note 7 SBK key is not used its an ODM key system. So they are heading into the wrong bush. only Nvidia knows the ODM key. But good luck.
Hey ReckoningForce,
Really hope you find a way, been searching for hours myself.
Driving me mad as i was bloody stupid enough to turn my should have been recalled device one without turning off the WiFi first, so unfortunately in the same boat as yourself.
Please update this thread if you get anything working!
Thanks again mate
hI, I HAVE A SHIELD 2017 with boot unlocked , but after downgrade from 9.1 to 8 (7.2.3) are in permanent loop:
1 message about risk unlock
2 logo nvidia
3 coloured cirlcle of anroid running
After get print on display "android" it loop into nvidia logo and repeat again infinitely those steps: HDMI recognize them as "Shield"
if i put a keyboard on usb port and i try to boot into fastboot/recovery ( A+B+PWRON) dont
do anymore loop but are stucked into run coloured cirvcles on screen : HDMI recognize them as "PB1"
Also un usb service port it recognize it as MTP USB device
does exist any possibility to get recovery or fastboot mode or i need to throw it out?
Over the past 1 year I have purchased a total of 7 Samsung Galaxy A32 5G. One for myself (Development) and one each for my children and wife. They were (are) decent devices for the price. I’m a licensed Android Developer (among a-lot of certs and licenses) and I have tried everything. I explain this so we can skip the basic concepts.
One night one of my device wouldn’t charge properly (no water damage) I turned it off to see if it charges correctly while off.
Instead the device enters a boot loop. I noticed an error on the bottom. Seems like it said “Kernel Dump” or “KDump” but the message was too fast to read. I even attempted taking video and pausing it on that frame but it was so quick it’s blurry. I was able to read it a bit better though and It does look like it says Kernel Dump (kdump) though. I can boot into Download Mode , I cannot boot into recovery or Fastboot however. I have tried many options (Kies , Odin) and while Odin is absolutely 100% completing successfully with no issues the device continues to go into a boot loop and show this Kernal dump. . I know Linux in general has a Kdump which creates a log when the Kernal crashes. Naturally I can’t think of a way to see that log. Is there something I’m missing? Is there a solution that works?
Thank anyone for any suggestions.
Innovatorsww said:
Over the past 1 year I have purchased a total of 7 Samsung Galaxy A32 5G. One for myself (Development) and one each for my children and wife. They were (are) decent devices for the price. I’m a licensed Android Developer (among a-lot of certs and licenses) and I have tried everything. I explain this so we can skip the basic concepts.
One night one of my device wouldn’t charge properly (no water damage) I turned it off to see if it charges correctly while off.
Instead the device enters a boot loop. I noticed an error on the bottom. Seems like it said “Kernel Dump” or “KDump” but the message was too fast to read. I even attempted taking video and pausing it on that frame but it was so quick it’s blurry. I was able to read it a bit better though and It does look like it says Kernel Dump (kdump) though. I can boot into Download Mode , I cannot boot into recovery or Fastboot however. I have tried many options (Kies , Odin) and while Odin is absolutely 100% completing successfully with no issues the device continues to go into a boot loop and show this Kernal dump. . I know Linux in general has a Kdump which creates a log when the Kernal crashes. Naturally I can’t think of a way to see that log. Is there something I’m missing? Is there a solution that works?
Thank anyone for any suggestions.
Click to expand...
Click to collapse
Have you tried booting in to safe-mofe or adb booting an image, a/b slots, etc. Make sure clear data (sucks)
Not much help, I'm sure you've covered all this, and well, the basics. Good luck
I had the same issue with my A32 5G and i found a solution to this. Plug the phone in and make sure it is charging and then power it on and set it aside and let it go into the boot loop. (plugging it in is to ensure it wont die) Eventually, after a few hours, the boot loop will stop and the phone will open android recovery and allow you to facotry reset the phone. After the reset it should boot again. Not sure what the exact cause of this is but this is what worked for me. Good luck!