Hello Team,
I bricked My nothing phone 1 and it's been 3 days now I'm unable to flash stock rom using "Fastboot mode"
The actual error is when I run downloaded.ps1
It gives me a option do you have firmware download (y/n) I selected it as N
Then, Global or Eu I selected it as G and there we go with error
Please team help me to get back to stock rom
I have downloaded update platform tools
1.4.4 sh4 and super 1.4.4
Can you try running the script from a different terminal? Or maybe a computer with different Windows version?
it says wget and all those other commands not supported
You sure you can even trust that script?
Also, since you are running Windows 8.1, even though you REALLY shouldnt be, most scripts these days are designed for Windows 10 at minimum.
wget and tar are only available on Windows 10 and 11 since that is when Windows Subsystem for Linux started (wget and tar in Windows itself was a side effect of it)
There are also no official unbricking tools, if there were, it would be in the form of something like the MSM Tool for OnePlus phones.
Furthermore, you can flash firmware to a device even if the current firmware isnt working, this is a program on the Qualcomm board, not controlled by the manufacturer.
Related
(Moved from development forum, newb root thread)
I recently received my phone back from a HTC repair. I hadn't used it til today as I was waiting for froyd 1.5 to come out before rooting it and setting it up. Today I switched it on and it asked me if I wanted to update the software, I clicked no. Then I followed the steps in the OP but had problems in step 5 : everytime I typed anything (including "su") and hit enter I had a message saying "denied" or words to that effect, despite the UniversalAndroot program giving the "woot rooted" message.
This is the part where I might have done something stupid - I decided to let the phone update itself to the latest software, and then I was planning to run the UniversalAndroot again. I thought that maybe UA had been tested on the latest official HTC stuff but not whatever 2.1 but not fully updated version that mine had come back from repair with. It went to the update screen and the progress bar completed, it tried to reboot but just got stuck on the white boot screen with the green HTC logo. If I pull the battery out and start again it just hangs at the same screen.
I can get the 2.73.405.5 WWE RUU to see the phone when in fastboot, but when I try to update it it eventually gives me error 140 "bootloader version error".
I tried to load it through HBOOT using kazuni's technique in his thread "A way of flashing the RUU rom extract" (sorry, it won't let me paste a link to the actual thread) but it says "main version is older, update fail". Do I need to send it off to HTC again? I just got it back! Will they be able to tell what broke it and refuse to fix it?
Many many thanks
Try the 2.1 downgrade in my sig below.
Please could you explain "The recovery can be flashed via running 'runindos.bat'."? I assume I need to install this adb program that people keep mentioning?
Also what is the goal here? To upgrade my phone to 2.1 (which was already on from the HTC repair, the OTA update just said something about adding g-sensor calibration tool) to then root it or to downgrade my phone to 1.5 to root?
Many thanks!
Ah, just seen adb guide on villain forums. OK, I'll follow the guide to get adb installed, put your recovery files in the /tools folder, but then how exactly do I flash the recovery? Simply by typing runindos.bat in cmd whilst in the correct folder?
Ah, I see, I just run the batch file from your recovery download. Sorry for all the dumb questions! I ran this with my phone on fastboot usb but it said this :
adb server is out of date. killing...
* daemon started successfully *
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
"Files copied and permissions set, rebooting HTC Andriod 2.1"
"Your phone will now reboot into normal mode, then reboot into recovery mode. I
f it does not reboot the second time, wait 10 minutes and manually reboot and be
gin again."
error: device not found
As far as I can tell nothing happened on my phone. I assume my usb drivers are fine as the RUU was able to begin updating before it gave me the 140 version error. Any ideas?
It's the ADB drivers, what OS are you using?
I am using Windows 7. I thought i read that the latest version of htc sync had drivers fully compatible with win 7 and the RUU seems to see it fine once I selected 'my htc' drivers under adb in device manager. I am confused!
HairyBones said:
I am using Windows 7. I thought i read that the latest version of htc sync had drivers fully compatible with win 7 and the RUU seems to see it fine once I selected 'my htc' drivers under adb in device manager. I am confused!
Click to expand...
Click to collapse
You may want to build an XP workstation eitha virtual or physical. Don't be alarmed. Yes, the latest version of HTC Sync does contain the drivers. However, they some what don't work for majority of users. Sorry.
Just did a quick google - will http://www.microsoft.com/windows/virtual-pc/download.aspx work?
HairyBones said:
Just did a quick google - will http://www.microsoft.com/windows/virtual-pc/download.aspx work?
Click to expand...
Click to collapse
virtual box - http://www.virtualbox.org/
vmware player - http://www.vmware.com/products/player
Eek - I need to get an xp install disc and set it up like I was loading it onto an actual PC? The microsoft tool within win 7 definitely wouldn't work?
HairyBones said:
Eek - I need to get an xp install disc and set it up like I was loading it onto an actual PC? The microsoft tool within win 7 definitely wouldn't work?
Click to expand...
Click to collapse
Yeh, to install XP you will need an install disk, unless you download XP Trial version VHD. This is the trial version from Microsoft in virtual machine mode.
http://www.microsoft.com/downloads/...90-958F-4B64-B5F1-73D0A413C8EF&displaylang=en
Windows XP Mode with Windows Virtual PC, available for Windows 7 editions Professional, Enterprise, and Ultimate, provides a licensed virtual Windows XP Professional environment for compatibility with applications not compatible with Windows 7. Windows Virtual PC supports USB attachment, therefor supporting direct connection of USB devices to the virtual Windows XP environment.
For information and to download Windows XP Mode or Windows Virtual PC visit the product page microsoft.com/windows/virtual-pc/default.aspx
Brandon
Windows Outreach Team- IT Pro
I want do do some development for Firefox OS and I have a ZTE Open C to work on. But I can't unlock the device. I've downloaded the Open_C_upgrade_Tool and run it in serveral environments. I only have a Mac and so I installed Bootcamp with Windows XP but the Upgrade Tool just says scanning for device ... and never finds it! Also tried it with XP running under VMware Fusion - the same result the UpgradeTool just searches for the ZTE and never finds it.
Before I pluged the ZTE to the system via USB I took out the SIM-Card and the SD-Card even tried with only SIM-Card out but again no success.
So can anyone here give any help with this. I read on other post that people had the same problem but there is no answer on this matter ...
And without unlocking my device it's no use to start any project.
Thanks for any help in advance!
Hi,
You can follow this guide to flash a the rooted image on your device (I assume you have an EU version) :
(Warning : not sure if it works on US version)
http://builds.firefoxos.mozfr.org/doc/en/devices/zte-open-c-eu
(and optionally update FirefoxOS with the provided -unofficial- builds)
The best would be to use a real Windows computer, I don't know if it works in a virtual machine for sure. But be sure to install the usb drivers (download link provided in the above guide) before trying to flash.
I have done it on my Open C and now I'm currently testing FxOS 2.1 (aurora)
I happen to update platform-tools in the Android SDK from version 23.1 to version 24 on an older PC.
The newest adb.exe included with v24 no longer works on WinXP.
You will get the following error upon startup:
adb.exe - Entry Point Not Found
The procedure entry point WSAPoll could not be located in the dynamic link library WS2_32.dll.
Click to expand...
Click to collapse
In case anyone is curious, I tracked the change down to this one:
https://android-review.googlesource.com/#/c/203387/
ADB
I've attached the v23.1 adb and fastboot to this post in case someone needs the previous version (which works fine with 5x up to at least MTC20F)
Just unzip and you can use adb/fastboot from the resulting platform-tools-v23.1 directory or copy them over to where your normal platform-tools directory is.
USB drivers for 5x
I also included USB drivers that work with 5x. These should work for 32/64-bit for winxp and vista. Win7 is maybe, haven't tested.
They WILL NOT work with win8 and above due to changes in driver enforcement. I am not sure about win8.x but on win10, there is a built-in driver that works with adb. To get bootloader/fastboot driver, just allow win10 to search for drivers. It will load Marshall London Bootloader Interface. This is for a different phone from music company Marshall, but it works fine since it is an Android-based device.
I could never find one official driver from google or lg that would work with adb inside android, adb inside twrp, adb sideload inside stock recovery, and fastboot.
I stopped worrying about why it works for other people and just fixed the problem myself.
Not sure if it matters to that many people these days, but it was confirmed the change in adb is not a bug and will persist going forward, so if you ever need to run adb on a WinXP box or emulator, you'll need to retrieve platform-tools-23.1 or earlier.
WinXP compatible platform-tools also could be downloaded from official repository:
http://dl-ssl.google.com/android/repository/platform-tools_r23.1.0-windows.zip
Thank you so much for this sfhub. This was driving me crazy getting bootloader access with Win 7. Updated to the driver you linked and worked great. I guess most people out there are using Win 8 or 10 now? Minblowing that so few use 7.
Greefus said:
Thank you so much for this sfhub. This was driving me crazy getting bootloader access with Win 7. Updated to the driver you linked and worked great. I guess most people out there are using Win 8 or 10 now? Minblowing that so few use 7.
Click to expand...
Click to collapse
Actually Windows 7 is still installed on nearly half of all desktop and laptop computers: https://www.netmarketshare.com/operating-system-market-share.aspx?qprid=10&qpcustomd=0. Did the most recent SDK drop support for it?
For anyone who wants to use adb on the latest version of Android Studio running on Windows XP use the adb .exe from version 23 and paste it into the platform tool folder. Keep a copy of the new adb.exe just in case you need it. No need to use the entire v23 platform tool folder.
The references in this thread have so far appear to refer to latest adb compatibility, particularly for Windows XP.
Does the latest fastboot still work fine with Windows XP? If not, what was the last known-good or thought to be last known-good version for Windows XP?
Hi
The adb from the v2.3.1 works fine with my win xp, thank you for the file.
Hello,
I am another WinXP user facing the error
"adb.exe - Entry Point Not Found. The procedure entry point WSAPoll could not be located in the dynamic link library WS2_32.dll."
@sfhub & @Sintetix
Thanks for the info and provide the latest version supported by XP ...
Are you aware of any important changes / additions in the future versions to be concerned of?
Regards
---------- Post added at 11:16 ---------- Previous post was at 10:47 ----------
Just to let you know,
C:\v23.1>adb devices
List of devices attached
adb server is out of date. killing...
error: protocol fault (couldn't read status): Invalid argument
error: could not install *smartsocket* listener: cannot bind to 127.0.0.1:5037:
I am trying to connect an Asus Transformer tablet with "MTP file transfer" mode on WinXP Service Pack 3 laptop... cable is fine and the plan is to move from custom ROM (Android 6.0) to Stock (JellyBean) ... Something I already did few years ago having Win10 (I have the receipe used then)
I think I better get a fresh Win7 on my primary Win10 PC and start from there... I never liked W10 anyway ... and since I did mods to [finally &effectively] stop the [annoying, unwanted & plenty of bugs] Win10 updates ... I got funny errors when using dev stuff ... even DotNet ...
And I need to think a better O.S for the XP PC ...
Time to change. Regards
Before jumping to my major O.S actions,
I gave a chance to my Asus Transformer tablet with another cable under the W10 PC and the latest adb (r29.0.2-win) and this second time it worked fine ...
The first time and first cable did not work (reason that drove me to the WinXP PC thinking the cause was Win10)
fastboot devices
was literally returning
???????????? fastboot
But this second time with another cable
fastboot devices
returned
BLAxxIDxxSTRING fastboot
And I was finally able to perform the format and flash series of commands to return my tablet to the stock ROM ...
As I understand this thread is about WinXP, for testing purposes, I hooked my fresh flashed tablet to the WinXP PC with the successful spare cable, and
adb devices
got again
List of devices attached
adb server is out of date. killing...
error: protocol fault (couldn't read status): Invalid argument
error: could not install *smartsocket* listener: cannot bind to 127.0.0.1:5037
Certainly I don't have the explanation of this, but I can tell you is not because a faulty cable or something related to the tablet.
And something scary to add: the first cable looks in good shape and is the one used every day to charge the tablet without any delays or issues ...
Hope someone find this useful and provide more insight. Regards
hi i have a nuvision windows tablet tm800w610l,couple days ago when windows updates installing blue error screen come and i think say(ssd error) after that windows not booted say(bcd error),so i downloaded windows frimware from website and put in bootable flash and connect with otg to tablet(via simple hub for flash and keyboard)now i have a problem with installing new windows,i think usb speed is very very slow,it cant boot windows for installing(take 20-30 minuts just on the windows install loading screen)after that black screen and nothing happening,im tested other bootable iso files but speed is very very slow i cant do any thing.im searched net some people think its on bios setting,some think usb hub is problem(before that i have a another windows tablet and installed windows via same hub)
so i dont know where is the problem,in bios there is very very settings i dont know which setting must changed.
thanks.
had to reload mine from scratch worked fine with a OTG hub, keyboard , mouse and flash drive .
Got touch working?
image
where did you get the image from?
the one on the nuvision website is corrupt.
I tried new and old versions of winrar and it has checksum errors
same with the drivers. what the f***. tried googleing filenames etc and get almost no results.
djmdesign said:
where did you get the image from?
the one on the nuvision website is corrupt.
I tried new and old versions of winrar and it has checksum errors
same with the drivers. what the f***. tried googleing filenames etc and get almost no results.
Click to expand...
Click to collapse
Just an FYI, the version that’s currently on the Nuvision website works.
It’s not an iso, at least it doesn’t download as one. I took that file and created an iso and used a usb bootable maker to create the usb drive.
It recognized it upon restarting in advanced mode. The installer is in another language but it got me up and running again.
Just wanted to put this out there.
You can use the NuVision image if you wish (You just extract the RAR to your USB drive and then boot it in your tablet), or you can create installation media using the Windows Media Creation tool (or UUPtoISO if you want to use Insider Preview downloads from another machine).
As long as you use the correct processor architecture, you don't need the NuVision restore package (It's also out of date and no longer supported by Microsoft as it's version 1511, or maybe it was 1603 either way it's unsupported as of now). Some drivers maybe, but a lot of those are available via WU (I've never had to actually install any drivers doing a clean install from a Windows ISO).
This also applies to the NuVision TM800W560L, any 32-bit image will boot and work properly for installing Windows. If you look into installing 64-bit Linux on the W560L though, it's a little more complicated (yes, you can install 64-bit Linux, but not Windows. This is because the Linux kernel can replace UEFI Runtime Services if it needs to, which booting a 64-bit Kernel with a 32-bit version of GRUB causes UEFI to disable access to Runtime Services, which is why Windows cannot run like this and bugchecks with UNSUPPORTED_PROCESSOR.)
I have a Lumia 950XL prototype I got recently, but it's stuck on version 10586.164
When looking for updates says it is up to date, already tried it (WDRT) even if you messed up the product code
unsuccessfully
Can someone help me? He has the boot unlocked
(WDRT Error) PACKAGE NOT AVAILABLE FOR THIS PHONE With the original product code
Firmware: 01078.00048.16135.36002
Original product code: 059W5J6
PROTO
you tried Interop Unlock and registry change?
https://forum.xda-developers.com/showpost.php?p=71937591&postcount=323
3.Go to the app bar, then choose x50 series unlock. You will receive an error about the acer service not running. That's ok for now. Click step 1 and it will tell you to install the acer system service and copy some files. To install the acer system service, use iutool [rs and newer builds,this version is essential,old versions will probably not work] (can be found here. thanks @Wack0Distractor ).
iutool install https://forum.xda-developers.com/showpost.php?p=68459157&postcount=13
run this command as administrator
iutool -v -p "path to the file acer.service.acersystemservice.spkg"
if you receive error 0x80070490, disconnect your phone from usb, go to control panel on your pc, devices and printers, find your windows phone and remove device. reconnect the usb to your phone,and after it reinstalls the drivers automatically, run iutool command above again.
if you receive error 0x8024a110, your phone should reboot to the gears UI in a minute. if not, run the command again. if it still doesnt auto reboot, manually reboot your phone. It should reboot into the gears UI, then back into the OS. if it still fails and doest show gears, give you phone a rest for 5-10 minutes and retry(usually needed after a new rom flash).
4.When you're back in the phone OS, copy newndtksvc.dll and ndtksvc.dll to your documents folder on your phone through USB
5.Go to the app bar, then choose x50 series unlock. You should no longer receive the error about the acer service. Now click step 2 and follow the rest of the instructions from the app.
6.If you've taken the silent extras/advanced+info update, or updated that app manually, be sure to choose the option "Restore NDTK 950/XL" in the "x50 series unlock" page and reboot to regain access to the elevated features. It basically means if it suddenly stops working, apply this setting.
Click to expand...
Click to collapse
now you only need change registry
older version of Interop Tools for 10586
https://forum.xda-developers.com/showpost.php?p=68982441&postcount=284
hi, can you boot in masstoragemode and dump few partitions?
before update, make full dump via win32diskimager
If you can have your phone recognized by PC in any mode, there's a spark of hope, but be warned that I take no responsibility for any damage that may occur (and it may occur since you are installing a software that's made for final products on a prototype):
I strongly recommend you to perform a full ROM backup if possible to be able to get back to this version if things go horribly wrong. If you can't do this, you may consider enrolling in Windows Insider program (which may allow you to get new builds), or perform a software RM Code change - most recommended- (check here: thewincentral.com/get-windows-10-mobile-redstone-on-older-lumias-using-an-app-now-uses-same-mod/)
You might not find a ROM corresponding exactly to that product code (because it's a prototype) on the internet, but you can download any Lumia 950 XL Firmware you'd like (check this: www . lumiafirmware.com/ser/RM-1085).
Once you've downloaded all firmware files, use the following tool to flash the firmware onto your device: androidmtk.com / use-windows-phone-image-designer-tool
(remove spaces from urls)