Develop Bugs

Kin 2 nvidia tegra

So I tried to flash android on to the phone using the tegra 250 images when I realized I need the apx series images for android. The thing about that is I can't find them anywhere. Anyone have any idea where a development site for the tegra apx series is? It seems Nvidia has no support for the old series anymore.

how do you upload android to the phone? what program or steps do you do? is there a debug mode or recovery mode? I believe we have to make are own images.

I was using a program provided by nvidia for programming a tegra based development kit. It is capable of flashing android and windows ce 6. If anybody with more experience would like to take a look at the drivers images and program here are the files.
http://tegradeveloper.nvidia.com/tegra/downloads

Don't the images you are looking for have to have drivers for the hardware interfaces specific to this phone?

stetkas said:
Don't the images you are looking for have to have drivers for the hardware interfaces specific to this phone?
Click to expand...
Click to collapse
I wasn't exactly worried about the hardware working as much as getting android onto the tegra and viewing the os. Creating drivers is the easy part.

dezgrz said:
I wasn't exactly worried about the hardware working as much as getting android onto the tegra and viewing the os. Creating drivers is the easy part.
Click to expand...
Click to collapse
Do you think you could write a driver for this.
APX
USB\VID_0955&PID_7416&REV_0103
USB\VID_0955&PID_7416
This VID supposedly belongs to Nvidia. This is the device that is found by Windows if you plug your phone into the usb when it is turned off and then press the u+s+b+power buttons.

I tried the Recovery Mode, like the person described above me, and it came up with the APX device.. So, if someone makes a driver for that, then we might be able to jailbreak it? (iPod Touches and iPhones jailbreak though Recovery Mode). This doesn't seem much diffirent from an iPhone or an iPod Touch.

I found out a driver that we might be able to modify to give us access. I downloaded both the froyo and c36 downloads available from the tegra site that was mentioned earlier. http://tegradeveloper.nvidia.com/tegra/downloads
These file paths could be different if your hard drive has a different drive letter and perhaps also if you have a 64-bit processer, but I found the drivers in the following directories.
C:\Program Files\NVIDIA Corporation\tegra_froyo_20101105\usbpcdriver\NvidiaUsb.inf
C:\Program Files\NVIDIA Corporation\ce6_tegra_250_5265393\os\usbpcdriver\NvidiaUsb.inf
These drivers have the hardware ID in the inf file and so Windows recognizes it and starts to install the driver and finishes, but says there is an error. I'll keep working on it though.

So, the drivers do actually work; it was my computer that was causing the problems, not the drivers. Now that the drivers are installed I think we can use the SDKs provided by Nvidia on the Tegra download page.
If this works, we now have a serious decision to make. Do we try to get android on the phone or do we stick with the Windows CE based os?

mcdietz said:
So, the drivers do actually work; it was my computer that was causing the problems, not the drivers. Now that the drivers are installed I think we can use the SDKs provided by Nvidia on the Tegra download page.
If this works, we now have a serious decision to make. Do we try to get android on the phone or do we stick with the Windows CE based os?
Click to expand...
Click to collapse
Personally, I would rather stick with current OS. Just because I don't want to brick my phone. Maybe have some additions to the current OS? Enable hidden features or something? Customizations? etc?

First off, I wanted to thank everyone who is working on trying to develop an update to improve on the Kin Two. I currently am interested in getting the TWOm when my contract expires but there is a dealbreaker for me, which is that the phone does not alert you when you have a missed call. I know there are other annoying flaws (pointed out in details at the verizon forums by fisharefriends), but this is the only flaw I cannot deal with.
I do not know what is possible of being changed/edited, but I think mcdietz should focus on implementing basic functions that are currently not on the Kin Two phone, but are on other simple lower spec feature phones.

zero2duo said:
First off, I wanted to thank everyone who is working on trying to develop an update to improve on the Kin Two. I currently am interested in getting the TWOm when my contract expires but there is a dealbreaker for me, which is that the phone does not alert you when you have a missed call. I know there are other annoying flaws (pointed out in details at the verizon forums by fisharefriends), but this is the only flaw I cannot deal with.
I do not know what is possible of being changed/edited, but I think mcdietz should focus on implementing basic functions that are currently not on the Kin Two phone, but are on other simple lower spec feature phones.
Click to expand...
Click to collapse
Implementing missing features.. That's a good start. Also, would It be possible to make it be USB device (so you can go into the phone and let's say.. change the default themes).

@mcdietz
Humm, i installed all those downloads long time ago (i guess when posted or before), but didnt tested the drivers with the APX connection.
It worked with errors in linux connection to the usb (got device errors while reading from the USB device) and didnt worked with virtual machine (though vmware detected it).
On the other hand, it worked ok in a win7 real machine and got the driver installed.
I tried to flash android on the device, using the provided images (heh, tests...) and nvflash. But you always get an error on the first try and then, in further attempts you get a "Starting flash" message loop which does nothing.
Same results if you try to do "nvflash --get-partitions" (stuck at 2nd attempt).
You may thing that it's a non working thing, but if you dont connect the device, nvflash.exe it outputs that there is no USB device connected.
A little weird...
I would want to have android at the kin (as i think that has more future than our wince version, looking @ tegra forums) and anyway, if we can somehow read/write the phone roms, we can made a backup from the current OS.

Installed the same tools on linux (native, no emulation) and the flash option didnt worked here either (normal / root user).
Code:
./nvflash --getpartitiontable test.log
outputs (if no phone connected)
Nvflash started
no usb phone found
Click to expand...
Click to collapse
outputs (if Kin on APX connected)
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
Click to expand...
Click to collapse
in the first attempt. Then if called again, seems to get frozen on "Nvflash started" message.
Maybe the recovery has no way to get that data....

Windows Phone Connector?
has anyone tried using the program WP7 connector for the KIN? it works with the zune hd so why not the KIN?

Mmm just to inform....
This is what (physically) happens when the Kin is on the nvflash attempts. Phone must be just booted (not previous nvflash attempt in this boot).
Code:
PC <- Kin: 80 30 18 16 B9 E8 00 00
PC -> Kin: [1028 bytes of data]
Pc <- Kin: 04 00 00 00
PC -> Kin: [39252 bytes of data]
Seems like the response we get (rcm 0x04000000), and the next writing is done with the device autolocked, so last PC -> Kin fails.
Further attempts do not try the same procedure but directly send the last 39252 packet again, failing and getting stuck.
Using some selfmade software (cause no other works so far), i repeated the same procedure, changing the first "byte pack" to send a lame pack, and this is the output:
Code:
# ./kingateway
Opening the controller
Checking for kernel attaching
Claiming the interface
Reading from the Kin.
Received data. 8 bytes. Content:
80 30 18 16 B9 E8 00 00
Writing [02 01 00 00] to the Kin.
Reading Kin response.
Received data. 4 bytes. Content:
08 00 00 00
Writing again to the Kin
KinGATEWAY:: Error while writing to the KIN. Error Code is -9 EXITING.
So in short, fails again (haha, expected...really), but the second response from the kin is not "0400...00" but "08 00 ... 00" meaning a rcm 0x0800..000 or whatever that means.
The above error ("autolock"), tagged as Error code "9" on the program, is a integrity-defense method from the kin, not for the flashing issue but from the "command sent" over usb, which is wrong or unknown on how to operate, and is called "Endpoint Stall". Is a way to express "You'r doing it wrong and i wont hear you again".
One of my ideas is that this version of nvflash is not what was used to operate with the kin and all we get are not errors or devil's corporation actions but uncompatibility protections.
What we need, from my point of view is the Tegra SDK and/or a document where the responses from an APX device are listed (like 0x04000 is "wrong certificate" and 0x08000 is "certificate too short", etc), so we know what it's telling to us. Maybe it's easier to contact nVidia for "old" SDKs than roms...

i hate to be a party crasher but i think this thread needs to be a bumped? why did this thread randomly die? maybe i'm missing something.

I believe it died because johnkussack doesn't have a working kin right now and I don't believe anyone else here wants to try things that may "brick" their phone (I'm one of them). I'm currently trying to buy another kin two (or, uh two), then I'll definitely be digging deeper into those. I may try a hardware route on one and a software route on the other.
This is definitely the most exciting thread the kin two section of xda!

It's been a while but I now have a working KIN device and can continue my efforts. Using the resume mode command to try and force nvflash to write to the kin it displayed a message that said "writing" and then displayed "Failed to perform the following commands: create". It's been a PITA but I feel I will get something written to the device soon.

dezgrz said:
It's been a while but I now have a working KIN device and can continue my efforts. Using the resume mode command to try and force nvflash to write to the kin it displayed a message that said "writing" and then displayed "Failed to perform the following commands: create". It's been a PITA but I feel I will get something written to the device soon.
Click to expand...
Click to collapse
before doing what i lastly underlined, considering what i underlined first... i suggest that you do the reading part, relating to the partition listing.
Just a safe way to find out if the experiments work. Then you can write... with a bit of safety on your side. I mean... you know that testing things writing could not be the best idea on the brikings

Freezing

Ever since I updated to 6.01 I've been having some extremely bad freezing issues. The whole device will freeze up at times and wont except any input from the touch screen. The buttons still work but the screen won't work at all, even if its rebooted or put into twrp. If I force a reboot while that is happening then the google splash that is displayed before the device starts booting often hangs there for a long period of time before continuing to boot. The only way that I've found to get out of it is to wait for a varying amount of time.
The other problem is that the orientation will occasionally freeze and won't change unless I reboot. After that it returns to normal.
Thank you for your time

As it freezes also in TWRP I'd suspect a hardware issue. Check internal connections and consider a new touch digitizer.

k23m said:
As it freezes also in TWRP I'd suspect a hardware issue. Check internal connections and consider a new touch digitizer.
Click to expand...
Click to collapse
But the strange part is that it comes back just by waiting a few minutes. If it was completely a hardware issue than wouldn't that not have happened?

I still vote for hardware issue but if you have any doubts then go back to v5.1.1 and let us know.
Wait, didn't you make a v5.1.1 TWRP backup? Just restore it.

Thanks, I'll take a look at the hardware side. I don't have a backup for 5.1.1 sadly. I've been on 6.01 and just dealing with the issues for the last few months. I'm pretty sure I deleted my old backups already but I'll try flashing 5.1.1 stock to see if it makes a difference.

I have the same issue as yours. My Nexus 7 2013 32GB WiFi freezing at bootup screen as attcahed. Even I flash it with NRT 2.1.4 from ktu84p, lmy48t & mmb29q, it still freezing at bootup screen with the unlock icon. And I tried to flash the TWRP recovery, it is no response with any touch action.....
I can boot it into bootloader mode with the PWR and VOL- key.
How can I know is it the touch digitizer (that mean the hardware) problem? Thanks a lot!

mikengcm said:
I have the same issue as yours. My Nexus 7 2013 32GB WiFi freezing at bootup screen as attcahed. Even I flash it with NRT 2.1.4 from ktu84p, lmy48t & mmb29q, it still freezing at bootup screen with the unlock icon. And I tried to flash the TWRP recovery, it is no response with any touch action.....
I can boot it into bootloader mode with the PWR and VOL- key.
How can I know is it the touch digitizer (that mean the hardware) problem? Thanks a lot!
Click to expand...
Click to collapse
Please clarify - can you boot TWRP and see the graphic TWRP screen?

k23m said:
Please clarify - can you boot TWRP and see the graphic TWRP screen?
Click to expand...
Click to collapse
Normally, I can't bootup to recovery (TWRP/CWM).
When I use the NRT to flash stock rom & unroot it, it running all the command without any error. But it can't bootup and freezing in the Google with lock screen in the previous message. Then I boot it into bootloader mode, and run 'Root and also flash Custom Recovery' in the NRT as attached jpg. It will boot into the TWRP, but it is no response for any touch action on screen as attached jpg2.
Thanks a lot!

Before we condemn the touch digitizer please run TWRP with a mouse on OTG adaptor. Note the attached picture. TWRP is fully controlled by a mouse, you can see the cursor.

mikengcm said:
Normally, I can't bootup to recovery (TWRP/CWM).
When I use the NRT to flash stock rom & unroot it, it running all the command without any error. But it can't bootup and freezing in the Google with lock screen in the previous message. Then I boot it into bootloader mode, and run 'Root and also flash Custom Recovery' in the NRT as attached jpg. It will boot into the TWRP, but it is no response for any touch action on screen as attached jpg2.
Thanks a lot!
Click to expand...
Click to collapse
Once in TWRP you can just use a wireless mouse (the receiver might need an adapter -OTG cable). It happened once to me that the internal storage kept some residual files that messed up all flashing. But to wipe and format everything requires your touch to work since afterwards you'll need fimware on the OTG flash (internal storage completed erased).
If you use fastboot, check to see if it connects to your PC first. If it does, then you can wipe and format everything twice within TWRP; reboot to bootloader page; and flash by command lines, or use Nexus Tookit (skipsoft) to flash a stock or custom rom. Once done, boot it up and see if touch works again.
Failing that, you can tackle the hardware. Remove the back cover; disconnect the battery FIRST; remove and reseat the silver cable making it snug-fits at both ends. Then remove and reseat the two-pronged amber cable coming out of the touchscreen and connected to the lower board. Be gentle as the lock tabs might break. Use something flat to lift the locks slowly. Re-attach the battery LAST.
That's all you can do. If it still doesn't work, then we can discuss further. Touchscreens have been known to fail on their own in this model, but very rarely.

graphdarnell said:
Once in TWRP you can just use a wireless mouse (the receiver might need an adapter -OTG cable). It happened once to me that the internal storage kept some residual files that messed up all flashing. But to wipe and format everything requires your touch to work since afterwards you'll need fimware on the OTG flash (internal storage completed erased).
If you use fastboot, check to see if it connects to your PC first. If it does, then you can wipe and format everything twice within TWRP; reboot to bootloader page; and flash by command lines, or use Nexus Tookit (skipsoft) to flash a stock or custom rom. Once done, boot it up and see if touch works again.
Failing that, you can tackle the hardware. Remove the back cover; disconnect the battery FIRST; remove and reseat the silver cable making it snug-fits at both ends. Then remove and reseat the two-pronged amber cable coming out of the touchscreen and connected to the lower board. Be gentle as the lock tabs might break. Use something flat to lift the locks slowly. Re-attach the battery LAST.
That's all you can do. If it still doesn't work, then we can discuss further. Touchscreens have been known to fail on their own in this model, but very rarely.
Click to expand...
Click to collapse
Thanks for your help! Sorry for my bad english!
I follow your 1st method, I can use the mouse to control in TWRP 2.8.7.0. I tried to factory reset my N7, it show 02 error......Then I wipe twice the all the options in 'Advanced Wipe' (see 04) and 'Format Data' twice time (see 06) successful respectively. And then I follow your 2nd method (using Skipsoft toolkit) to flash the kk4.4 stock rom.... my N7 still freeze on bootup screen (see 08).
And then I use the NRT to flash the TWRP 2.8.7.0 against, and I copy the TWRP 3.0.0.0.img into my N7. I boot to TWRP 2.8.7.0 recovery and flash the TWRP 3.0.0.0.img file into it and reboot to TWRP 3.0.0.0 recovery and once I tried to 'Format Data'... it show the 07 error on screen....
'flash_image /dev/block/platform/msm_sdcc.1/by-name/ metadata /dev/zero process ended with ERROR:255'
I can't goolge this error meaning.......And my N7's touch function still not working!!!
Finally, thanks for your help again very very much......

mikengcm said:
Thanks for your help! Sorry for my bad english!
I follow your 1st method, I can use the mouse to control in TWRP 2.8.7.0. I tried to factory reset my N7, it show 02 error......Then I wipe twice the all the options in 'Advanced Wipe' (see 04) and 'Format Data' twice time (see 06) successful respectively. And then I follow your 2nd method (using Skipsoft toolkit) to flash the kk4.4 stock rom.... my N7 still freeze on bootup screen (see 08).
And then I use the NRT to flash the TWRP 2.8.7.0 against, and I copy the TWRP 3.0.0.0.img into my N7. I boot to TWRP 2.8.7.0 recovery and flash the TWRP 3.0.0.0.img file into it and reboot to TWRP 3.0.0.0 recovery and once I tried to 'Format Data'... it show the 07 error on screen....
'flash_image /dev/block/platform/msm_sdcc.1/by-name/ metadata /dev/zero process ended with ERROR:255'
I can't goolge this error meaning.......And my N7's touch function still not working!!!
Finally, thanks for your help again very very much......
Click to expand...
Click to collapse
Your freezing differs from the OP. He talked about touches being not registered, while yours is the tablet would not boot up past the initial Google Screen. Am I right? If this is the case, you need to be careful. Before you do anything, I'd suggest you go back to KitKat custom rom first because a lot have bricked their tablet trying to upgrade to Lollipop and newer official roms. Go back to older Bootloader if necessary before installing KK.
I have the feeling you're not familiar with the mechanics of what's being discussed. I apologize if I'm wrong but if not, it behooves to read this thread to get an idea. You don't need to wipe and format again with 3000 as it serves no purpose. 2870 had already done that. Remember that if you're not comfortable with fastboot uses, you're treading treacherous territory here, and the probability of inadvertently bricking the tablet is more than good. Once whatever software blocks writing to the internal storage, you're toast.
If you want to flash a custom rom to find out if anything in the software caused the freezing, you need to sideload as detailed in the above thread. Since you don't currently have an OS installed, you need to trick NRT to take you to TWRP (2.7.1.1) before you can sideload. Thereafter, it's automated.
Once you can boot again into Android, you can test touches. If the problem persists, the cause lies elsewhere. If it stops, you can upgrade back to TWRP 2870 or 3000.

Both Doctorimpossible & mikengcm explicitly reported no touch control in TWRP so let's see what the touch controller says.
boot TWRP
connect PC
run: adb shell dmesg > dmesg.txt
Copy dmesg here.

Thank you for attempting to help me but strangely I haven't had that problem again since I posted. I used to have that problem daily when I was on 6.01 but when I somehow managed to get it to connect during flashboot and update it to the latest February update + flash the new Franko kernel + new exposed and root I haven't had that problem since.

k23m said:
Both Doctorimpossible & mikengcm explicitly reported no touch control in TWRP so let's see what the touch controller says.
boot TWRP
connect PC
run: adb shell dmesg > dmesg.txt
Copy dmesg here.
Click to expand...
Click to collapse
I am very sorry if I post in wrong area/forum!
I tried to paste the dmesg.txt into Pastebin.com, I don't know I pasted it or not..
And I attached dmesg.txt also.
Thank you so so much!!

mikengcm said:
I attached dmesg.txt also. Thank you so so much!!
Click to expand...
Click to collapse
Your dmesg is SCREAMING about touch control errors: elan_ktf3k_ts_recv_data: i2c_master_recv error?!
ELAN is the touch controller IC.​
For start, reattach the silver cable on both ends.
If this does not help, then reattach cables going to TPCON1 and TPCON2 (the red chip is your ELAN).
Disconnect the black battery plug before doing anything.
---------- Post added at 10:07 ---------- Previous post was at 09:53 ----------
Doctorimpossible said:
Thank you for attempting to help me but strangely I haven't had that problem again since I posted.
Click to expand...
Click to collapse
I wouldn't celebrate just yet, it was an intermittent issue, also confirmed by TWRP. If/when it happens again, grab a dmesg log and share it here.

k23m said:
Your dmesg is SCREAMING about touch control errors: elan_ktf3k_ts_recv_data: i2c_master_recv error?!
ELAN is the touch controller IC.​
For start, reattach the silver cable on both ends.
If this does not help, then reattach cables going to TPCON1 and TPCON2 (the red chip is your ELAN).
Disconnect the black battery plug before doing anything.
---------- Post added at 10:07 ---------- Previous post was at 09:53 ----------
I wouldn't celebrate just yet, it was an intermittent issue, also confirmed by TWRP. If/when it happens again, grab a dmesg log and share it here.
Click to expand...
Click to collapse
I don't know that the touchscreen mechanics function independently of the OS. The guy's tab has no OS right now. Where would it get the necessary firmware?

graphdarnell said:
I don't know that the touchscreen mechanics function independently of the OS. The guy's tab has no OS right now. Where would it get the necessary firmware?
Click to expand...
Click to collapse
No worries, TWRP is his OS right now, with user interface and all necessary firmware.

Ok so I did start celebrating too early. I left the house 3 hours ago and just came back to find it completely frozen. There was a sort of warning sign a few hours before where the screen would refuse to rotate like it did before. I grabbed the log http://pastebin.com/8hdhctin

But after rebooting everything was OK, right? So is the dmesg log.
The problem is intermittent and we need a log from TWRP when the touch screen does not respond.
Btw you have a Kingston
I see these in your dmesg
Code:
<7>[ 9.451599] EXT4-fs (mmcblk0p30): ext4_orphan_cleanup: deleting unreferenced inode 120188
<7>[ 9.457580] EXT4-fs (mmcblk0p30): ext4_orphan_cleanup: deleting unreferenced inode 358667
<7>[ 9.462524] EXT4-fs (mmcblk0p30): ext4_orphan_cleanup: deleting unreferenced inode 223937
<7>[ 9.463195] EXT4-fs (mmcblk0p30): ext4_orphan_cleanup: deleting unreferenced inode 223936
<7>[ 9.463348] EXT4-fs (mmcblk0p30): ext4_orphan_cleanup: deleting unreferenced inode 223935
<7>[ 9.463470] EXT4-fs (mmcblk0p30): ext4_orphan_cleanup: deleting unreferenced inode 223934
<7>[ 9.463592] EXT4-fs (mmcblk0p30): ext4_orphan_cleanup: deleting unreferenced inode 223923
<7>[ 9.465148] EXT4-fs (mmcblk0p30): ext4_orphan_cleanup: deleting unreferenced inode 390919
<7>[ 9.471221] EXT4-fs (mmcblk0p30): ext4_orphan_cleanup: deleting unreferenced inode 366605
<7>[ 9.472015] EXT4-fs (mmcblk0p30): ext4_orphan_cleanup: deleting unreferenced inode 390918
<7>[ 9.476715] EXT4-fs (mmcblk0p30): ext4_orphan_cleanup: deleting unreferenced inode 138802
Probably an after-freeze mess.

Soft Bricked - Unable to Sideload OTA

Hi all,
My Nexus 5x (16gb - all stock.) went and soft bricked today. Not sure why - just seemed to start wanting to constantly restart - never making it past the white google text part of the boot process. Not sure if it's an update or hardware. No trauma or dropping of the phone - which makes me think s/w rather than h/w.
I have attempted to install a rescue OTA update (instructions I followed are from technobill - don't have enough posts to add a link). However, when running "adb sideload <file>" I get a "failed to read command" error. Have tired multiple cables/ports however to no avail.
(Recovery screen shows the following build details: 7.0/NBD90W/3239497)
Any ideas?
Thanks.
Somewhat Irked

SomewhatIrked said:
Hi all,
My Nexus 5x (16gb - all stock.) went and soft bricked today. Not sure why - just seemed to start wanting to constantly restart - never making it past the white google text part of the boot process. Not sure if it's an update or hardware. No trauma or dropping of the phone - which makes me think s/w rather than h/w.
I have attempted to install a rescue OTA update (instructions I followed are from technobill - don't have enough posts to add a link). However, when running "adb sideload <file>" I get a "failed to read command" error. Have tired multiple cables/ports however to no avail.
(Recovery screen shows the following build details: 7.0/NBD90W/3239497)
Any ideas?
Thanks.
Somewhat Irked
Click to expand...
Click to collapse
Did your phone just reboot in the middle of doing something innocuous then start bootlooping? Were/Are you on total stock with bootloader locked? If both yes, it is probably hardware issue you are encountering.
Regarding sideloading, did you place your Android recovery in sideload mode?
Did you verify adb can "see" your device using "adb devices"?

SomewhatIrked said:
Hi all,
My Nexus 5x (16gb - all stock.) went and soft bricked today. Not sure why - just seemed to start wanting to constantly restart - never making it past the white google text part of the boot process. Not sure if it's an update or hardware. No trauma or dropping of the phone - which makes me think s/w rather than h/w.
I have attempted to install a rescue OTA update (instructions I followed are from technobill - don't have enough posts to add a link). However, when running "adb sideload <file>" I get a "failed to read command" error. Have tired multiple cables/ports however to no avail.
(Recovery screen shows the following build details: 7.0/NBD90W/3239497)
Any ideas?
Thanks.
Somewhat Irked
Click to expand...
Click to collapse
Well luckily I made this post today.

The more this goes on, the more I believe it to be hardware ...
@sfhub - reasonably innocuous. Had just opened one or 2 apps that morning. Not sure what had updated overnight app/os wise. Not anything interesting as far as I can tell. Once I managed to get it into recovery "adb devices" was returning the phone.
@bardhi92 - I saw that once I got in. However, I couldn't get it to see my phone.
Updated things I have tried and why I've all but thrown in the towel:
After the OTA rescue sideload failed I started trying a few different things. It stopped taking me into recovery mode more frequently, at least it seemed that way - it would just keep bootlooping. My main issue is that I has a locked bootloader, which stopped me whacking TWRP on and loading on a custom rom - just to see if that worked.
I thought it might let me sideload on a factory default img file. Turns out nope.
However I used NRT to "Flash Stock + Unroot" (with "Soft Brick/Bootloop" checked) which for some reason, then allowed me to get back into recovery mode. I had also removed the sim card/tray at this point. May have been either or neither of those that allowed me to get into recovery mode. Can't say for certain.
I cleared /cache and /data and then attempted the OTA rescue update again. This time it failed at 45% (according to my cmd prmpt) with the error: "* failed to read command: No error". I'm not sure text was on the phone at the time. But it did manage to boot into Android. I quickly stepped through the various intro steps (putting in the sim, adding my mail google account details).
I went to get a beer. Only to find it boot looping again.
Not to be deterred, I vowed to try again. Same steps as before (remove sim, nrt voodoo). This time however the OTA rescue worked and fully completed. I went through the intro steps again. This time I quickly turned on dev options, enabled usb debugging and sorted out the OEM bootloader. I thought this would be smart, just in case it hapened again. Once I chose to unlock ("fastboot reboot", selected yes), it decided to start boot looping again.
The main annoyance is: I don't think I have any proof of purchase, even though it's in warranty. That, and I now live in Dubai - so shipping back to the UK where I brought it is going to be killer. But I think it's the path of least resistance at the moment.

SomewhatIrked said:
The more this goes on, the more I believe it to be hardware ...
@sfhub - reasonably innocuous. Had just opened one or 2 apps that morning. Not sure what had updated overnight app/os wise. Not anything interesting as far as I can tell. Once I managed to get it into recovery "adb devices" was returning the phone.
@bardhi92 - I saw that once I got in. However, I couldn't get it to see my phone.
Updated things I have tried and why I've all but thrown in the towel:
After the OTA rescue sideload failed I started trying a few different things. It stopped taking me into recovery mode more frequently, at least it seemed that way - it would just keep bootlooping. My main issue is that I has a locked bootloader, which stopped me whacking TWRP on and loading on a custom rom - just to see if that worked.
I thought it might let me sideload on a factory default img file. Turns out nope.
However I used NRT to "Flash Stock + Unroot" (with "Soft Brick/Bootloop" checked) which for some reason, then allowed me to get back into recovery mode. I had also removed the sim card/tray at this point. May have been either or neither of those that allowed me to get into recovery mode. Can't say for certain.
I cleared /cache and /data and then attempted the OTA rescue update again. This time it failed at 45% (according to my cmd prmpt) with the error: "* failed to read command: No error". I'm not sure text was on the phone at the time. But it did manage to boot into Android. I quickly stepped through the various intro steps (putting in the sim, adding my mail google account details).
I went to get a beer. Only to find it boot looping again.
Not to be deterred, I vowed to try again. Same steps as before (remove sim, nrt voodoo). This time however the OTA rescue worked and fully completed. I went through the intro steps again. This time I quickly turned on dev options, enabled usb debugging and sorted out the OEM bootloader. I thought this would be smart, just in case it hapened again. Once I chose to unlock ("fastboot reboot", selected yes), it decided to start boot looping again.
The main annoyance is: I don't think I have any proof of purchase, even though it's in warranty. That, and I now live in Dubai - so shipping back to the UK where I brought it is going to be killer. But I think it's the path of least resistance at the moment.
Click to expand...
Click to collapse
So, you flashed the .TOT file, sideloaded the given OTA within the stock recovery bootloader that comes with the .TOT file, and cleared cache/factory reset?
Please condense it. If you managed to start up the phone, that's a huge success for people who have not been able to yet.

bardhi92 said:
So, you flashed the .TOT file, sideloaded the given OTA within the stock recovery bootloader that comes with the .TOT file, and cleared cache/factory reset?
Please condense it. If you managed to start up the phone, that's a huge success for people who have not been able to yet.
Click to expand...
Click to collapse
In short:
OTA rescue failed during adb sideload,
Tried bullhead-nbd90w-factory-d2f11c5f.zip & removed sim tray - seemed to allow access to recovery mode,
OTA rescue claims to have failed at 47% during adb sideload- still booted into android. However briefly. Went back to bootloop,
Tried bullhead-nbd90w-factory-d2f11c5f.zip & removed sim tray - seemed to allow access to recovery mode,
OTA rescue completed via adb sideload,
Turned on dev options (usb debug, oem unlock),
Booted to fastboot - unlocked bootloader. Now back to bootlooping
@bardhi92 - I could not get the LG utility to detect my phone. Will attempt again tomorrow.

SomewhatIrked said:
@bardhi92 - I could not get the LG utility to detect my phone. Will attempt again tomorrow.
Click to expand...
Click to collapse
IMO you shouldn't flash the TOT file. If you end up bootlooping again, your phone will be stuck in bootloader locked mode with no ability to unlock it.
If you were able to get your phone to boot into android once, there is really nothing the TOT file will do for you that you can't do from TWRP or bootloader, whereas once it locks your bootloader, there are problems you can no longer fix like EFS corruption (which likely isn't your problem).
In the end, you probably do have eMMC that is slowly starting to fail. There is usually error correction on the eMMC that can lock out bad blocks but if it gets to serious, it'll fail. This is why reflashing stuff over and over sometimes works.

Please help me to unbrick my Surface RT

I used bitlocker for my surface RT. I forget the password and the recovery key then I try to reset my device using recovery USB it failed at 2%
so I check my disk using diskpart. There is no partition on Disk 0. I can't do anything to the disk. it's just showing the capacity.
When I try to covert the disk to gpt (convert gpt) I got this error message
Virtual Disk Service error:
The object is not found.
Sorry for my bad English
Thank you.

surface tab RT
nesan95 said:
I used bitlocker for my surface RT. I forget the password and the recovery key then I try to reset my device using recovery USB it failed at 2%
so I check my disk using diskpart. There is no partition on Disk 0. I can't do anything to the disk. it's just showing the capacity.
When I try to covert the disk to gpt (convert gpt) I got this error message
Virtual Disk Service error:
The object is not found.
Sorry for my bad English
Thank you.
Click to expand...
Click to collapse
Did you ever find out how to un-brick your RT surface?

xm8 said:
Did you ever find out how to un-brick your RT surface?
Click to expand...
Click to collapse
No

Same issue - today I decided I wanted to do a full reset and followed what MS' site said to do (click "Skip this drive"). Looks like all that does is brick the device, great.
Mine's a Surface 2. I've done resets on this Surface 2 before, but I'd not click "Skip this drive" and instead put in the bitlocker key (which I would retrieve from the URL specified on that page).
I can barely even find any information about the diskpart error... but I guess all this means is that this Surface 2 (or at least its eMMC drive) is toast, which randomly had its touchscreen stop working a couple years ago (around the time of this post, huh). I'd like to believe it's due to some sort of security on the Surface 2 though... maybe.
Edit: Found one other thread out there on the internet of a user encountering the same issue when attempting to create partitions with diskpart on Surface 2: https://www.computing.net/answers/hardware/diskpart-cant-create-new-partition/94440.html Now I wonder if there's anyone who's _succeeded_ in doing diskpart operations on a Surface 2...

Diskpart works fine on these devices, Surface RT / 2 are quite hard to brick. Can you get to the command prompt using a USB recovery drive?
Do the following:
Diskpart
sel dis 0
clean
exit
This will fully clear the drive - then run recovery as normal.
https://support.microsoft.com/surfacerecoveryimage

jwa4 said:
Diskpart works fine on these devices, Surface RT / 2 are quite hard to brick. Can you get to the command prompt using a USB recovery drive?
Do the following:
Diskpart
sel dis 0
clean
exit
This will fully clear the drive - then run recovery as normal.
https://support.microsoft.com/surfacerecoveryimage
Click to expand...
Click to collapse
Yes, can run those commands (even did a clean /all), but restarting the recovery process fails at the same point (2%). Can't recall where but there's a script in the recovery zip that shows the diskpart commands it runs to clean, convert disk to GPT, create partitions etc. and fails for presumably the same reason.
I know it's attempting to run diskpart commands at this point: Since my touchscreen is broken (firmware probably, randomly stopped working and no amount of resets have fixed it) and its type cover is broken, I at first tried resetting by swapping a USB keyboard and the USB stick while going through the steps. It failed after a few seconds without any indication of progress. When I checked out the partitions with diskpart at this time, all 4 partitions were there and disk was marked as being GPT. When I finally decided to just use a type cover from another Surface (thus avoiding the USB swapping I was doing), this time I also received a "repartition drives?" prompt and selected yes. (Apparently, swapping out the recovery USB drive seems to dismiss the ask to repartition drives.) Recovery failed at 2%. Checked diskpart, and saw the drive with 0 partitions and not GPT - as if it did a `clean` with diskpart.
May be useful to note that ever since the touchscreen randomly stopped working back in at least 2018, my Surface 2 has had problems that appear to be symptoms of disk-related issues. I can't recall them all, but things like dism always reported issues with integrity, disk usage always pegged around 100%, and the last issue I tried to perform a reset for was the settings app just refusing to open (consistent app crash after splash screen). Other issues were that it would not wake from sleep (leading me to set it to never sleep). I can't recall if I ran any chkdsks or other stuff; I'll see if I can find any logs I may have exported. I had used the device quite often for years leading up to that, though of course ever since end of 2018 it's been just sitting around off or plugged in.

Locked bootloader, cannot OEM Unlock or access USB Debugging

Short version of question: How can I unbrick my ONEPLUS 3 (A3000) if I cannot boot to Android and OEM Unlock AND USB Debugging both have not been enabled?
Long version: Phone was recently purchased second hand from a third-party market (Kijiji, kind of like craigslist for Canadians). Person I bought it from claimed in the ad that the device was in a bootloop and couldn't access the OS. I had in the past successfully saved a ONEPLUS 1 from bricked status, so I didn't feel a simple bootloop would pose much of an issue. That, and at the price he was selling I really couldn't turn it down.
I tried various different methods of restoring the phone's partitions, OS, and firmware to stock/custom, but had no real luck with any (I will list below what I have attempted). If there was a root cause of this, I believe it's due to the fact that some part of the phone's storage partition (boot or system if I had to guess) had become corrupted at some point. Given the volume of threads I've seen here and elsewhere online, I wouldn't rule out a bad OTA flash, but doesn't really matter. What does matter, however, is that the Android OS is inaccessible despite my best efforts, and the bootloader is set to locked and ADB Debugging remains off.
Generally speaking, is there a way to access Developer Options to correct both these issues through terminal or a tool? I'm confident that I can get my device working again if I could access this menu, but as of yet I have had no luck.
Methods used to restore/info worth mentioning
While I don't doubt their effectiveness at large, for whatever reason I have yet to find a tool/guide that yields the anticipated results upon completion. MSM Download Tool (V3 and V4) have both been downloaded, executed, and completed numerous times, but will still not boot past the loading screen upon completion.
According to Unified Android Toolkit, my device build is being detected as "OnePlus3 7.0 NRD90M" and All-in-One Toolkit is showing that Android 6.0.1 is installed.
Drivers are all installed correctly, as proven both via tools downloaded and through Windows CMD terminal (adb devices, fastboot devices, adb get-state, etc)
Stock recovery and bootloader modes can both be reached through both hardware keys and software commands. I will note that it seems to take longer than I'd expect to boot to either of these modes using hardware keys.
I have utilized multiple USB ports, Type-C cables, different OS' on two laptops (MS Windows 10 and 7, FWUL Linux). I usually have no problem with the device being detected by the system. When I have, it usually involved one pesky USB cord.
common commands used and their effects:
fastboot OEM unlock: fails, cannot be done remotely
fastboot flash x: fails, remote: flashing partitions not allowed
ADB push: fails. cannot access partition
ADB devices: device is seen by system with serial and state
fastboot devices: device is seen by system with serial
ADB sideload: varying results. Some will fail at 0% citing "total xfer: 0.00x", some will reach 47% and fail (always exactly 47% oddly). Generally if the sideload operation passes 47% it will complete.
fastboot format/erase x: fails, partition formatting/erasing not allowed
fastboot continue: executes, but does not help with android bootloop issue as I had hoped
While I searched for an answer online, I did come across an infosec whitepaper regarding ONEPLUS 3 vulnerabilities, though it was over a year old. To my surprise, the command they had been entering works on my device, but I'm not sure how to properly use it effectively. The command used was fastboot OEM boot_mode [rf/wlan/ftm/normal]. Now, I was unable to determine what each of the triggers does, but what I did discover is that with boot_mode set to rf, my device would display chinese/korean lettering in lieu of the usual ONEPLUS logo with "powered by Android" below. This is also how I managed to have my device show up in CMD terminal for ADB commands to be issued. To the best of my knowledge though, there doesn't seem to be much point to it as I couldn't push/pull any files. Does anybody know where I could find more info on this command, as I'd like to know what the other triggers accomplish.
I've just about exhausted every available resource looking for an answer, but im still coming up short. I've gone as far as contacting ONEPLUS directly, but without proof of purchase they can't (more accurately won't) help me. And while it's not a business practice I would personally support, I can understand why they have it implemented. I've contacted a few phone shops in the area, but none have been able to assist me further than I've already gotten in this process.
I apologize again for creating a new thread about this, but I felt my circumstances warranted a new thread due to the bulk of the others having either an unlocked bootloader or TWRP installed, neither of which I do.
So, can anybody offer their help or suggest something I haven't already tried? Or should I be on EBAY looking for motherboards? Thanks in advance.

Calgary84 said:
Short version of question: How can I unbrick my ONEPLUS 3 (A3000) if I cannot boot to Android and OEM Unlock AND USB Debugging both have not been enabled?
Long version: Phone was recently purchased second hand from a third-party market (Kijiji, kind of like craigslist for Canadians). Person I bought it from claimed in the ad that the device was in a bootloop and couldn't access the OS. I had in the past successfully saved a ONEPLUS 1 from bricked status, so I didn't feel a simple bootloop would pose much of an issue. That, and at the price he was selling I really couldn't turn it down.
I tried various different methods of restoring the phone's partitions, OS, and firmware to stock/custom, but had no real luck with any (I will list below what I have attempted). If there was a root cause of this, I believe it's due to the fact that some part of the phone's storage partition (boot or system if I had to guess) had become corrupted at some point. Given the volume of threads I've seen here and elsewhere online, I wouldn't rule out a bad OTA flash, but doesn't really matter. What does matter, however, is that the Android OS is inaccessible despite my best efforts, and the bootloader is set to locked and ADB Debugging remains off.
Generally speaking, is there a way to access Developer Options to correct both these issues through terminal or a tool? I'm confident that I can get my device working again if I could access this menu, but as of yet I have had no luck.
Methods used to restore/info worth mentioning
While I don't doubt their effectiveness at large, for whatever reason I have yet to find a tool/guide that yields the anticipated results upon completion. MSM Download Tool (V3 and V4) have both been downloaded, executed, and completed numerous times, but will still not boot past the loading screen upon completion.
According to Unified Android Toolkit, my device build is being detected as "OnePlus3 7.0 NRD90M" and All-in-One Toolkit is showing that Android 6.0.1 is installed.
Drivers are all installed correctly, as proven both via tools downloaded and through Windows CMD terminal (adb devices, fastboot devices, adb get-state, etc)
Stock recovery and bootloader modes can both be reached through both hardware keys and software commands. I will note that it seems to take longer than I'd expect to boot to either of these modes using hardware keys.
I have utilized multiple USB ports, Type-C cables, different OS' on two laptops (MS Windows 10 and 7, FWUL Linux). I usually have no problem with the device being detected by the system. When I have, it usually involved one pesky USB cord.
common commands used and their effects:
fastboot OEM unlock: fails, cannot be done remotely
fastboot flash x: fails, remote: flashing partitions not allowed
ADB push: fails. cannot access partition
ADB devices: device is seen by system with serial and state
fastboot devices: device is seen by system with serial
ADB sideload: varying results. Some will fail at 0% citing "total xfer: 0.00x", some will reach 47% and fail (always exactly 47% oddly). Generally if the sideload operation passes 47% it will complete.
fastboot format/erase x: fails, partition formatting/erasing not allowed
fastboot continue: executes, but does not help with android bootloop issue as I had hoped
While I searched for an answer online, I did come across an infosec whitepaper regarding ONEPLUS 3 vulnerabilities, though it was over a year old. To my surprise, the command they had been entering works on my device, but I'm not sure how to properly use it effectively. The command used was fastboot OEM boot_mode [rf/wlan/ftm/normal]. Now, I was unable to determine what each of the triggers does, but what I did discover is that with boot_mode set to rf, my device would display chinese/korean lettering in lieu of the usual ONEPLUS logo with "powered by Android" below. This is also how I managed to have my device show up in CMD terminal for ADB commands to be issued. To the best of my knowledge though, there doesn't seem to be much point to it as I couldn't push/pull any files. Does anybody know where I could find more info on this command, as I'd like to know what the other triggers accomplish.
I've just about exhausted every available resource looking for an answer, but im still coming up short. I've gone as far as contacting ONEPLUS directly, but without proof of purchase they can't (more accurately won't) help me. And while it's not a business practice I would personally support, I can understand why they have it implemented. I've contacted a few phone shops in the area, but none have been able to assist me further than I've already gotten in this process.
I apologize again for creating a new thread about this, but I felt my circumstances warranted a new thread due to the bulk of the others having either an unlocked bootloader or TWRP installed, neither of which I do.
So, can anybody offer their help or suggest something I haven't already tried? Or should I be on EBAY looking for motherboards? Thanks in advance.
Click to expand...
Click to collapse
Thanks for the exhaustive description. You seem to have covered every known method. If the MSM Tool also fails, I think that it is a hardware issue and you are better off searching for a new motherboard instead of wasting further time on trouble-shooting.
Best of luck!

tnsmani said:
Thanks for the exhaustive description. You seem to have covered every known method. If the MSM Tool also fails, I think that it is a hardware issue and you are better off searching for a new motherboard instead of wasting further time on trouble-shooting.
Best of luck!
Click to expand...
Click to collapse
I was afraid of that..... is there a way to test a given hardware component?

Have you tried the unbrick tool FULL updated: https://mega.nz/#!NmhhgZyB!CM7Fw8VjECiMIhh4gRXUx24QVCiE599_ZFAPDf08AiM

acetone802000 said:
Have you tried the unbrick tool FULL updated: https://mega.nz/#!NmhhgZyB!CM7Fw8VjECiMIhh4gRXUx24QVCiE599_ZFAPDf08AiM
Click to expand...
Click to collapse
Indeed I have, dozens of times between the full and mini versions. I've even gone as far as running the toolkits featuring MSMDownloadTool v4.0 to see if it achieved different results (it did not). The mini tool would finish doing its thing (turned the text green upon completion),but I would face varying partitions not being flashed correctly. The full version completes and does not have these varying partitions missing, but the device would then be either stuck in a bootloop where it will eventually reboot itself, or would hang indefinitely on the "swirling dots" loading screen. I tried the remedy of deleting cache in recovery, but this did not help.

deleted

***UPDATE*** - As I mentioned in this thread earlier, I noticed a discrepancy between the variant type listed on my actual device and the variant type returned when queried via fastboot. This got me thinking, and to make a long story somewhat shorter, I found that while most stock Oxygen images I attempt to sideload onto the device fail (at precisely 47%, oddly), I was able to sideload two different Hydrogen images without any resistance at all. I'm guessing something to do with the eMMC vs UFS file storage systems and how each OS uses them.
So I got Hydrogen flashed onto my my device. Smooth sailing, right? Afraid not. Despite fastboot's output clearly stating it was a successful transfer, and the stock recovery on the device echoing this, I still cannot get the OS to load. Now i' stuck with the loading screen hanging indefinitely prior to animation occurring, so basically the static ONEPLUS logo. Factory resets and cache wipes have done nothing to help the situation along. Conventional wisdom from the threads here seem to say using the MSMTool is the right answer..... and thus the circle of frustration is complete with me arriving back where I started. Does anybody have another suggestion I can try out? Still can't flash/boot to TWRP, unlock bootloader, or access Android to activate USB Debug/OEM Unlock either btw.

Have you tried flashing just the firmware, i havent flashed in years but i would assume you could sideload the firmware as well?

voodooline said:
Have you tried flashing just the firmware, i havent flashed in years but i would assume you could sideload the firmware as well?
Click to expand...
Click to collapse
Guess who didn't read? And after a year without flashing + a lack of reading skills, you still think you could solve this case? That's a spirit.
===
You better do pm some devs in dev section and point them to this thread and see if they can help, if you are still curious.
My guess is dead emmc, it can be replaced without buying the whole board.

150208 said:
Guess who didn't read? And after a year without flashing + a lack of reading skills, you still think you could solve this case? That's a spirit.
===
You better do pm some devs in dev section and point them to this thread and see if they can help, if you are still curious.
My guess is dead emmc, it can be replaced without buying the whole board.
Click to expand...
Click to collapse
I did read it, its funny always someone who has to be a **** about things. I should have been more specific. He was able to flash h2os. So he could try to flash the firmware for h2os to see if that gets it to boot.

voodooline said:
I did read it, its funny always someone who has to be a **** about things. I should have been more specific. He was able to flash h2os. So he could try to flash the firmware for h2os to see if that gets it to boot.
Click to expand...
Click to collapse
Magnificent, bro.
You're a truly genius.