Related
hey guys,
once every serveal months i check for updates for my rom, my recovery, and some apps.
yesterday i wanted to update tp the latest recovery (1.52)
now, the phone connected, driver was installed correctly (windows 7 32-bit)
i used the adb commands as posted in the recovery topic.
now it updated it, but after a few minutes using and wiping the phone, the usb-connection will not come to live (in any way, not even a "unknown device") and when the phone booted it gave a message: "SD removed, please place sd-card." while it has a 8 gb on there. luckily i backed up all data i needed from the sd before i flashed. so i used recovery to recreate partitions and wipe sd. but nothing works anymore... when i select ANY option in recovery wich needs SD access it immediatly gives errors.
also tried a nother microsd of 1 gb which did also not work...
about the usb-connection, it also does not work in Recovery.
but in the bootloader, it installs without any problems the well known "My HTC" device. using fastboot to boot to recovery image works, but again: no usb connection
please guys... help me... without sd-card i find my phone completely useless. (because of many documents and pictures for my work.)
I've had this problem and I had to send my Hero for repair, but it could be difficult if you have custom software in there, thry to flash original rom. Not sure though if it can be done through fast boot.
Also if you have to send it back, pretend to be an idiot and say it just went wrong. "I didn't do anything" could work.
Use fastboot to revert to a stock ROM (update.zip)
This sounds very similar to this issue on Modaco - http://android.modaco.com/content-page/299174/no-adb-no-sd/
Still ongoing, as I (pulser) am trying to guide the OP through making the goldcard (need to find another android phone to do this) and then we need to try an RUU somehow???
adwinp said:
Use fastboot to revert to a stock ROM (update.zip)
Click to expand...
Click to collapse
ok, and how?
thanks for reply.
i was thinking of letting it be repaired, but as you all say, unlocked spl, recovery image, custom rom. it does not look so good when they disver that.
but i am a stupid guy, so pretending to be stupid should be easy for me
If you are just interested in getting it back to stock for returning under guarantee to HTC, here is what I would suggest.
(No guarantees, as I haven't had to try this, and won't, for obvious reasons)
Get the stock RUU file from the hero that you have. I would recommend the oldest one that is available for you. (eg. a 1.73 one).
DISCONNECT your phone, and run the exe file(Yes, sounds strange, but bear with me).
Wait till the splash screen for the RUU is up, asking you to accept the EULA etc.
Now browse in my computer to your temp directory (C:\Users\Username\AppData\Temp in Vista/7, C:\Documents And Settings\Username\Application Data\temp in XP)
Sort the folders/files by date modified, and the most recently modified (or one of the most recently modified) folder should contain the RUU stuff. Inside a subfolder is a file called rom.zip. Copy this file to the desktop or another safe place. Once file is copied, close the RUU.
Now get your phone plugged in and booted into fastboot. (hold back + power)
Then use the command
Code:
fastboot flashall C:\Users\Username\Desktop\rom.zip
No guarantees, but it should get you back to the stock recovery, system and boot (NOT HBOOT or SPL, the actual boot.img that android uses to boot the kernel)
can i also flash custom rom with fastboot? to test if something is wrong with the rom?
That would depend on what version of SPL/HBOOT you have. If it is security off, then maybe. Otherwise I doubt it. You usually need an original, HTC signed file to flash using that method.
Feel free to give it a go, but I don't think it would work.
Hey everyone. I know there are already a few threads with boot loop animations, and am having difficulties finding the same situation as what I'm going through. Here is what the phone used to have before it randomly started looping:
Rooted - with Stock rom, using ClockwordMod Recovery 5.5.0.2
Used Go Launcher Theme ( if that even matters )
No additional roms installed or anything, the phone is 3 months old.
Ok here is where I'm stuck. I understand I should reflash somethings like recovery image or something, but I'm stuck with one big problem. My computer and phone don't recognize using the USB mount.
The message I get is called "Unable to open lunfile ( no such file or directory)
Here's what screens I can get to:
1. Hold vol up/down while holding power ( the little android with its belly open, and the options Start - Restart Bootloader - Recovery mode - Power Off )
2. Hold vol down - ODIN mode, with the START option only
I can access WMD recovery and factory reset, Try to install my old backup, nothing works at all in that area, no matter what I do.
Can someone advise me a step by step way of getting my computer to recognize my phone, so that I am able to do fastboot, or reflash, or anything to get my phone working again. I can't access my internal memory at all.
It's even possible that I've read too much, and my frustration is getting in the way, if so I apologize! Some guidance would be greatly appreciated!
Thanks in advance of course! I need my phone for business!
Cheers,
Install the drivers on a computer then use fastboot oem unlock. Or just factory reset it from within recovery.
Sent from my Galaxy Nexus using Tapatalk 2 Beta-4
Try my siggy.
I'm not sure about the exact error:
But the link there will get you the correct drivers.
Also, as stated...try to factory reset.
You'll lose your apps/data that way though =/
Hopefully you can get the driver installed and get your computer to recognize.
If so, follow this to back up your apps:
http://forum.xda-developers.com/showthread.php?t=1420351
Have exactly the same setup as you (rooted/stock/CWM) and had the animation bootloop - animation would just loop until a battery pull.
Only thing that solved it was a factory reset from recovery. Been working fine for the 4 weeks since. No need for any reflashing etc. Titanium recoveries have all worked fine as well. Didn't try my Nandroid backup as I thought that may still have the 'fault' built in.
I had a boot loop for every from I tried to flash...wat fixed it was before flashing u need to wipe system data and wipe the cache in the recovery...ie a clean install...then every rom I tried worked...so I think ur missing that crucial step coz it worked for me
Sent from my Galaxy Nexus using Tapatalk
Hey guys, as stated above I've done numerous factory resets, it still seems to boot. I will for sure try to get the drivers installed so my phone is recongised by the computer, but would need step-by-step assistance when doing fastboot, or whatever the next step is.
Looking for more help though! Keep em coming!
?
Any other ideas?
Thanks!
Ok guys, so here's where I'm at now. I've used Jubakuba's sticky link, located here:
http://forum.xda-developers.com/showthread.php?t=1529058
Everything is able to be recognized up to the point where it says "Put the su.zip on your phone."
Since I cannot access my phone contents, since I keep getting this "Unable to open lunfile ( no such file or directory), it does not allow me to add anything to my phone.
I re-installed CWD as stated in the list of things to do, and all that went well. But I have the same issue, I tried factory resetting all that. erase cache, and still stuck with the same issue.
What's my next step now peeps? Looking for a quick answer as I have time to do it tonight!
Edit***
Just tried this trick: but it says it does not recognize the device?? what is going on! Please help someone! Thanks!
Panic Section! (Something is Wrong)
Q: My phone won't boot!
A: The easiest option is to get into recovery and restore a nandroid using the above guide (pull battery to put phone in an off-state if needed).
However, more advanced options are available if you don't have a nandroid available (You're naughty).
Do you have another rom .zip available on your SD card? If so, simply use the above guide for installing a rom to get you booting again.
If not, you can download one on your PC. Boot into fastboot (the green Android with open chest menu).
Move the .zip to the C:\android-sdk-windows\platform-tools folder.
Open ADB.
Change the NAMEOFZIP.zip below to the correct file name...and perform the action.
Surely your computer recognizes your phone. Otherwise how were you able to unlock the bootloader and flash the recovery?
And I've never seen that error message before. It doesn't even make any sense to me. Where are you seeing it? On your phone or on your computer? And in what context? What are you trying to do when it shows up?
If your phone isn't booting I'm not sure that you can copy any files to it yet. (Maybe you can use adb in clockworkmod? I'm not sure) What I do know you can do is flash the stock ROM and start over.
Download the image from Google here:
http://code.google.com/android/nexus/images.html
Here's a instructions for the GSM version:
http://forum.xda-developers.com/showthread.php?t=1366806
For the Verizon version, I can't find the thread at the moment but you just replace the filenames and also there's 2 radios to flash so:
fastboot flash radio *filename*
fastboot reboot-bootloader
fastboot flash radio-cmda *filename*
"Unable to open lunfile ( no such file or directory) appears on the phone, in CWD mode, when trying to attempt "mount Usb" to be able to access my internal storage .
I am attempting your thoughts right now.
I will post with results
Ok I tried to do this step. This is the outcome I received on the computer after even typing the first step:
'fastboot-windows' is not recognized as aninternal or external command, operable program or batch file.
A thing to stress, I'm not sure how to do step 1: 1) Take a Nandroid Backup if you have CWM installed.
EDIT***
GREAT NEWS!
used this setup!
http://android.modaco.com/topic/348161-01-feb-r4-superboot-rooting-the-gsm-lte-galaxy-nexus/
and it worked!
Thank you everyone! Going to play with my phone and make sure it all works!
Macinshak said:
Ok here is where I'm stuck. I understand I should reflash somethings like recovery image or something, but I'm stuck with one big problem. My computer and phone don't recognize using the USB mount.
The message I get is called "Unable to open lunfile ( no such file or directory)
Click to expand...
Click to collapse
the problem is when that happen?? when ur phone is booted and u plug the usb cable to ur pc? or when u are under recovery and want mount the usb mass storage? the second one doesn't work
Hello All,
I am completely stuck after trying to fix my girlfriend's phone.
S-Off
HBOOT 6.13.1002
Radio 0.99.01.0225_2
eMMC-boot
___________________________
The phone was rooted over a year ago (not by me). I flashed the HTC12-MROM found here:http://forum.xda-developers.com/showthread.php?t=1892450
The ROM was recently updated, so I did a nandroid backup and tried installing the new rom zip. When I tried to format and wipe the system, everything went to hell.
Whenever I tried to format system, wipe data/cache, I got these messages:
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I also got messages saying:
error formatting /cache!
error formatting /data
I tried just rebooting the phone, but got stuck in bootloops.
I pulled the battery, tried to do a factory reset, but still got stuck in bootloops.
My genius idea was to try to unroot and take it to a verizon store. No such luck.
I used this guide to try to unroot. http://theunlockr.com/2011/10/14/how-to-unroot-and-return-the-droid-incredible-2-back-to-stock/ I got through Step 1 and flashed the stock ROM file, but the phone was still bootlooping.
I pulled the battery and tried to get into CWM, but the screen goes to a generic phone with a red triangle and exclamation point. If I try to simply reboot the phone, it says "updating software..." but does not move. It's been in this position for at least a half hour.
Can anyone suggest a fix? I can still get into HBOOT. I want to fix this or get it back to stock so I can bring it to Verizon.
Thanks in advance for your help.
That's one of the oldest RUU (Froyo) file from VZW - you might want to try flashing a newer GingerBread RUU from your computer to the DI2 via micro-usb cable. Boot into Bootloader (HBoot) first - make sure that the PC recognize it in USB (nothing like "unknown" or errors reading device, etc.)
http://www.androidfiles.org/ruu/sec....01.1111_NV_VZW1.92_release_225831_signed.exe
Download & flash it, follow the prompts and it should restore your device to stock unrooted condition, then it's a matter of unrooting it again & pushing CWM (with 'adb")
Let it bootup initially and go thru the setup - most likely, you will need to (Re)Activate it OTA again, download/update PRL's - if you can make outgoing call and receiving incoming call, got working 3G/Evdo data and WiFi - it's good to go. If NOT, you will need to call VZW tech support at #8899 [Send/Call] as they will need to take steps to restore your device's security settings (i.e.. "A" keys, etc.) on their end and have you power cycle the device 2 or3 times, get you to make a successful test call, etc.
As for that continuous bootlooping while it's in bootloading mode, it might be a PG32IMG.zip file on the mSD card, pull the Sim card & use a PC to rename and/or delete it, that should help stop the endless loop and help launch it into bootloader and/or recovery.
Thanks for getting back to me. How exactly do I flash this? I can only get into HBOOT. Should I rename this file PG32IMG.zip and put it on the base of the SD?
EDIT
That was a completely retarded question. I figure I can use a cmd prompt to flash this, however, I don't think I've ever had to do that. Can you walk me through it?
Thanks again!
So I figured out how to flash the .exe (literally just plug into the USB and run as administrator). It installed completely fine, but still bootloops. Gets to the red droid eye then boots back to the white HTC screen. It's still not loading.
Any other ideas?
double zero said:
So I figured out how to flash the .exe (literally just plug into the USB and run as administrator) ... It's still not loading. Any other ideas?
Click to expand...
Click to collapse
Okay, let's try to get it stop the bootlooping first. Pull out the mSD card & VZW's Sim card too, if installed after taking out the battery. Let it sit for a minute + and re-insert battery only. Power on while holding the Volume Down key only to get it into Bootloader mode - press the Power key to confirm and you should be in HBoot, move down to Factory Reset and press it.
Next, try to go into Recovery screen from HBoot menu and see if you can see the HTC/factory recovery menu (if the RUU was installed, your previous CWM or TWRP should be gone)
Reconnect via mUSB cable to the PC, and clean flash the RUU again - do NOT put the mSD card back in the side slot yet. Let's see (and hope) if it will continue to setup all the way to finish (HTC activation screen) without bootloop or freezing at the white HTC screen.
The other option is to manually flash things using ADB tools (factory Images - system.img and recovery.img, etc.) that's probably beyond your skills ?? as the file systems, bootloader, etc. were likely corrupted & damaged. There are details / guides & steps-by-steps on how to do it in the Development sub-section ...
Let's see if these ideas will work for your devices and if not ... unless someone else "cruising" here has further tips, your device is almost fully restored back to stock to bring back to Big Red for help, IF and if ...
I pulled the SD and Sim Card as you suggested and got it into HBOOT. I hit "Factory Reset" and the phone eventually went into the white HTC screen (and did not move).
I pulled the battery, went back into HBOOT and scrolled down to Recovery. However the phone is stuck at the generic phone with red triangle/exclamation point.
Should I try to get into HBOOT and try to flash the RUU again?
double zero said:
... Should I try to get into HBOOT and try to flash the RUU again?
Click to expand...
Click to collapse
At this point, as long as the PC recognize the DI2 when the USB is connected, I would attempt to flash the RUU again - watch the monitor screen for any error messages that popped up, any bypassed or errors, etc.
When it's done - shouldn't take more than 5 to 10 minutes, power it down. This time, let's try to do the initial boot-up and set-up with a freshly reformatted/blank (FAT formatting) mSD card (hopefully, you have a spare one - 4GB should do - make sure that isn't any PG32IMG.zip files on it as it would interfere with the Bootloader. (Leave your original/regular mSD card out/set it aside for later use in restoring, once you get the basic stock Rom running with no further bootlooping) Next, let it start and bootup ... and let's see if it will boot all the way to the Set-up and Welcome screen.
If this doesn't work either, try transfering/loading the earlier factory rom in PG32IMG.ZIP format onto the new mSD card, bring up the Bootloader and it should load and prompt you to push the Vol. UP key to install/flash. And, when it's finished - boot up and hope ... (I doubt that this extra step will make any difference, but it's worth trying in the overall efforts to un-brick it.
Check & look at your Bootloader to see if anything has been changed in the process and whether the Radio ver. info is different also.
Letitride said:
At this point, as long as the PC recognize the DI2 when the USB is connected, I would attempt to flash the RUU again - watch the monitor screen for any error messages that popped up, any bypassed or errors, etc.
When it's done - shouldn't take more than 5 to 10 minutes, power it down. This time, let's try to do the initial boot-up and set-up with a freshly reformatted/blank (FAT formatting) mSD card (hopefully, you have a spare one - 4GB should do - make sure that isn't any PG32IMG.zip files on it as it would interfere with the Bootloader. (Leave your original/regular mSD card out/set it aside for later use in restoring, once you get the basic stock Rom running with no further bootlooping) Next, let it start and bootup ... and let's see if it will boot all the way to the Set-up and Welcome screen.
If this doesn't work either, try transfering/loading the earlier factory rom in PG32IMG.ZIP format onto the new mSD card, bring up the Bootloader and it should load and prompt you to push the Vol. UP key to install/flash. And, when it's finished - boot up and hope ... (I doubt that this extra step will make any difference, but it's worth trying in the overall efforts to un-brick it.
Check & look at your Bootloader to see if anything has been changed in the process and whether the Radio ver. info is different also.
Click to expand...
Click to collapse
Letitride,
I did exactly as you said, installed the RUU again (it said it was successful). I powered down and put into another microSD card I had (FAT formatted and completely blank). No luck. The phone only boots up to the Red Droid Eye, then reboots to White HTC screen, etc.
I also tried using the factory rom in PG32IMG.ZIP format, same thing. The phone is stuck in the same bootloop. I noticed that when updating via this method, the Bootloader get Bypassed when installing. Do you think this could be a problem?
It also does looks like the Radio version is now different on the HBOOT screen:
S-Off
HBOOT 6.13.1002
Radio 0.99.01.1111
eMMC-boot
It there another RUU I can try flashing or a different PG32IMG?
Is there anything else I try? I haven't used adb before, but if there's a walkthrough on how to use it, would there be anything I can try to do with that?
Thanks.
double zero said:
... The phone is stuck in the same bootloop. I noticed that when updating via this method, the Bootloader get Bypassed when installing. Do you think this could be a problem?
It also does looks like the Radio version is now different on the HBOOT screen:
S-Off
HBOOT 6.13.1002
Radio 0.99.01.1111
eMMC-boot
It there another RUU I can try flashing or a different PG32IMG?
Is there anything else I try? I haven't used adb before, but if there's a walkthrough on how to use it, would there be anything I can try to do with that?
Click to expand...
Click to collapse
DD - Here's XDA's Guide to ADB for your reference - http://forum.xda-developers.com/wiki/Flashing_Guide_-_Android
Link to VZW's RUU files (only used the ones on the bottom of the listed directory for VivoW - it's for DI2 http://www.androidfiles.org/ruu/?dir=Vivo_VivoW
The .1111 Radio flashed is different as shown on the Bootloader is different because it is from a different RUU/Rom build, it is one of the correct ones designed for the device - it is fine. Mine is using a .0312 radio and there is a newer radio with .0320 - they all worked in conjunction with the device, results varied depending on the hardware or build date - results varied.
Both of our DI2 are running fine on HBOOT 6.13.1002
Here is a link to one of the thread with a working HBOOT .96.2000 in ZIP format that you can download & flash from Bootloader - it might help reverse/downgrade to this older version from your existing/newer one - it might NOT work, however as yours is newer (post #37) - http://forum.xda-developers.com/showthread.php?t=1064366&page=4
Is it possible that the device was flashed with the leakded/unofficial RUU or IMG zip file released for China / CDMA-GSM and not meant for VZW's CDMA market ?? If so, it likely corrupted the file/root/boot structure ??
Were you able to do a Factory Reset inside the HBOOT menu ??
Also, do you see the HTC Recovery Menu as it should've been flashed onto the device ?
In any event, let's try doing a wipe of the device once you get into "ADB" with the following command prompt, once it's connected via USB
fastboot -w
Then, try running the RUU again (select this one from the list in the link) - without the new blank mSD card, and with the mSD card
Vivo_VivoW/RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_4.08.605.3_Radio_1.09.01.0722_NV_VZW1.92_release_212888_signed.exe
Add'l thoughts for DZ
Playing w N7 but thinking about your issues, with device still S-OFF (unlocked) - if nothing is working but you can still get into Bootloader, why not try (manually, via ADB if necessary) flash Custom Recovery (CWM or TWRP, whichever works) - boot into that - and, load the SuperDuperWipe script written by ChillyBean in a Zip file. That should do the deep cleansing and wiping to hopefully removed all the hidden files & bits/pieces left on the / or /SD directories that possibly contributed to all the issues you are experiencing - I don't believe it can reverse or rollback your HBOOT version to .97 or earlier (never tried it, maybe it will or it won't) At this point, it doesn't hurt to try or you have everything to gain ...
If the custom recovery & superwipe worked, then, try flashing the RUU again and see if it will boot up fully without looping? From there, you will have a good base, backup first and decide to load/restore custom rom, kernel or minor mods/tweaks ...
Meanwhile, hope you are reading up on ADB - it's a bit "scarely" doing it the first time, after a few command prompts & success - you will feel good about it.
Hi all,
I'm in desperate need of help here, I purchased an already modified HTC One M9 (which i wasn't aware of when purchased) and have attempted to flash it back to Stock.
well i've made a real mess of it and I really don't understand what to do now if someone could help it would be greatly appreciated. as the phone currently stands:
I've somehow removed the TWRP and it boots into standard recovery
Its been wiped as a pre-req of a guide i followed to install the stock image so it wont boot at all
I can't get my PC to see it when i boot into Download mode, so ADB and fastboot do not see it.
I'm tearing my hair out and really wondering where i can go from here.
Any help is greatly appreciated.
Many thanks.
Several things that would be helpful to know, if you can:
About your phone
- your phone's carrier variant (AT&T, T-Mobile, developer, et cetera)
- what you can boot into (recovery, bootloader, download)
- are you S-ON or S-OFF (boot into bootloader, see upper left hand corner)
About your computer
- what drivers have you installed on your PC
- whether or not HTC Sync is installed on your PC
Depending on what you can boot into, an RUU is your safest option - you'll need to download the RUU that corresponds to your phone's carrier variant. Barring that, if you can boot into download mode, you should be able to install TWRP - which may open up some other options.
The carrier is a UK model unlocked factory so i'd imagine just the standard EU model.
I can get into Recovery which is the standard Android one, Bootloader and Download mode
S-ON which is what confuses me, alot of these posts are regarding S-OFF devices
UPDATE: I managed to figure out i was running 2.10.401.1 so i downloaded the corresponding file for it. Formatted an SD Card to FAT32 and put the file on named 0PJAIMG.zip
It looked like it was working but failed on System.img, the device rebooted and now its stuck on white HTC screen with the Green HTC logo.
I can't turn it off, its just stuck there, any ideas?
andyobmonkey said:
I can't turn it off, its just stuck there, any ideas?
Click to expand...
Click to collapse
I'm sorry for the late reply. I hope you've had better luck in the meantime. If not, you can force a reboot by pushing and holding the power button & volume up.
If you can reboot, see what you can boot into. From what little research I've attempted on your carrier's software offerings, I'm not seeing an executable RUU (ie, installable from Windows). If there is one, that is by far the most dependable way to restore your phone to stock condition.
If you're intent on using the SD card install method (or it is the only way), you might consider ensuring that it is a reliable card. A read failure in the middle of a firmware update might explain the install issues you're having.
Beyond that, I'm afraid I don't have any further advice; I've reached the end of my experience! But if you still need help, please post an update and let us know what is going on.
Get a fresh SD card and pop TWRP or CWM on it along with the stock image. Automatic recovery and 3 wipe there we go. I only got boot loops when I was using a corrupted SD. Also, try both the ones with the underscores replacing spaces and regular names. One of them seem to be a decoy, as far as I can see.
andyobmonkey said:
UPDATE: I managed to figure out i was running 2.10.401.1 so i downloaded the corresponding file for it. Formatted an SD Card to FAT32 and put the file on named 0PJAIMG.zip
Click to expand...
Click to collapse
That file is corrupted and shouldn't be used. You can try reviving your phone by using this RUU service since there is no working 2.10.401.1 RUU you could use.
Hey everyone,
this is my first forum post on the xda website so I'll try to create an effective post as best I can.
Objective: Attempting to return to out-of-the-box stock android after using a custom ROM, LineageOS. I mainly want to return it to a condition where I would be able to hand it back to the carrier. It's also much more convenient for me to use the phone in stock. From my understanding, this is possible without much difficulty.
Issue: After many days of searching forums and following guides specific to the phone's model, I've put myself in a confusing position. The phone's current state is as follows: Installed OS[None], Bootloader[Relocked], S-ON[True], Boot to Recovery[Unsuccessful], SIM Card[None]. I'm unable to detect the phone on my computer(running Windows 10), and therefore can't utilize adb commands.
If anyone has any advice or guidance I would really appreciate it; and if you need me to provide any more information I would be happy to. I'll also try to respond as quickly as I can. Thanks!
jamcmich said:
Hey everyone,
this is my first forum post on the xda website so I'll try to create an effective post as best I can.
Objective: Attempting to return to out-of-the-box stock android after using a custom ROM, LineageOS. I mainly want to return it to a condition where I would be able to hand it back to the carrier. It's also much more convenient for me to use the phone in stock. From my understanding, this is possible without much difficulty.
Issue: After many days of searching forums and following guides specific to the phone's model, I've put myself in a confusing position. The phone's current state is as follows: Installed OS[None], Bootloader[Relocked], S-ON[True], Boot to Recovery[Unsuccessful], SIM Card[None]. I'm unable to detect the phone on my computer(running Windows 10), and therefore can't utilize adb commands.
If anyone has any advice or guidance I would really appreciate it; and if you need me to provide any more information I would be happy to. I'll also try to respond as quickly as I can. Thanks!
Click to expand...
Click to collapse
What is your CID/MID and software version? Just use an ruu for your device that's at your current firmware version or higher. Put it on the root of your sd card and run from download mode.
Tarima said:
What is your CID/MID and software version? Just use an ruu for your device that's at your current firmware version or higher. Put it on the root of your sd card and run from download mode.
Click to expand...
Click to collapse
I only have access to the CID(TMOBO10) and software version(2.51.531.32).
I've attempted to use an RUU, although after many attempts I couldn't get past the application setup screen. After the progress bar finished installing the RUU, it would close and never prompt me for anything else. I tried it multiple times.
I don't have a SIM/SD to use, unfortunately.
TWRP was installed as my Recovery, although trying to access it returns a boot-loop.
In terms of using adb, my phone will charge if plugged into the computer but it's not being recognized for file transfers.
I'm gathering that the only option left is to use something like a SIM card as you mentioned?
jamcmich said:
I only have access to the CID(TMOBO10) and software version(2.51.531.32).
I've attempted to use an RUU, although after many attempts I couldn't get past the application setup screen. After the progress bar finished installing the RUU, it would close and never prompt me for anything else. I tried it multiple times.
I don't have a SIM/SD to use, unfortunately.
TWRP was installed as my Recovery, although trying to access it returns a boot-loop.
In terms of using adb, my phone will charge if plugged into the computer but it's not being recognized for file transfers.
I'm gathering that the only option left is to use something like a SIM card as you mentioned?
Click to expand...
Click to collapse
You could troubleshoot your RUU issue, it should work if you have a windows computer. Try googling it. Unfortunately I can't help you much there, it's always worked fine on my machine.
Else, yea, the SD card method also works well. Find an ruu zip version first before trying to find an SD card. The ruu.exe you tried using won't work in this method.
Hi.
PC method
As @Tarima has mentioned the RUU is not running because of a Windows/PC issue.
Your best option is to try and run it in another computer or a friend's computer.
You can put your phone to download mode (volume down+power)
And run RUU again. Here is a link just to make sure you have the correct RUU. It is for your CID and its 2.51.531.32
https://androidfilehost.com/?fid=746010030569947237
For microSD card method
Use a friend's microSD card. It will need to be formatted to FAT32. So backup the microSD card data. Hehe!
To create an installable zip for that RUU, you again need a good computer.
Here is how you can get the installable zip from the RUU since it is encrypted you just cant extract it.
Download this decryption tool from here https://forum.xda-developers.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928
Choose 32bit or 64bit as this is vital to its working. Also make sure dotnet framework 3.5 is installed on your machine or else this tool will not run.
Once decryption tool is ready to run, just drag and drop the RUU on top of HTC_Decrypt_Tool.exe
It will give you some options. From these say yes (Y) to get new keyfiles AND to create installable sdcard zip file. you will know it when you see.
All other options such as uploading new keyfiles to community and getting boot.img and system.img is optional.
Once you get the zip rename it to 2PS6IMG.zip if it already isnt renamed.
Transfer to the root of your microSD card (dont put in any folders, just put it direcly on microsdcard)
Put microSD card into the your htc 10.
Enter download mode (volume down+power)
Download mode should detect the zip file. Press volume up to install.
If you need anymore help please post back again
jamcmich said:
I only have access to the CID(TMOBO10) and software version(2.51.531.32).
I've attempted to use an RUU, although after many attempts I couldn't get past the application setup screen. After the progress bar finished installing the RUU, it would close and never prompt me for anything else. I tried it multiple times.
I don't have a SIM/SD to use, unfortunately.
TWRP was installed as my Recovery, although trying to access it returns a boot-loop.
In terms of using adb, my phone will charge if plugged into the computer but it's not being recognized for file transfers.
I'm gathering that the only option left is to use something like a SIM card as you mentioned?
Click to expand...
Click to collapse
ayyu3m said:
Hi.
PC method
As @Tarima has mentioned the RUU is not running because of a Windows/PC issue.
Your best option is to try and run it in another computer or a friend's computer.
You can put your phone to download mode (volume down+power)
And run RUU again. Here is a link just to make sure you have the correct RUU. It is for your CID and its 2.51.531.32
https://androidfilehost.com/?fid=746010030569947237
For microSD card method
Use a friend's microSD card. It will need to be formatted to FAT32. So backup the microSD card data. Hehe!
To create an installable zip for that RUU, you again need a good computer.
Here is how you can get the installable zip from the RUU since it is encrypted you just cant extract it.
Download this decryption tool from here https://forum.xda-developers.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928
Choose 32bit or 64bit as this is vital to its working. Also make sure dotnet framework 3.5 is installed on your machine or else this tool will not run.
Once decryption tool is ready to run, just drag and drop the RUU on top of HTC_Decrypt_Tool.exe
It will give you some options. From these say yes (Y) to get new keyfiles AND to create installable sdcard zip file. you will know it when you see.
All other options such as uploading new keyfiles to community and getting boot.img and system.img is optional.
Once you get the zip rename it to 2PS6IMG.zip if it already isnt renamed.
Transfer to the root of your microSD card (dont put in any folders, just put it direcly on microsdcard)
Put microSD card into the your htc 10.
Enter download mode (volume down+power)
Download mode should detect the zip file. Press volume up to install.
If you need anymore help please post back again
Click to expand...
Click to collapse
Thanks for the helpful information. I'll try everything and give feedback regarding how it goes.