Hi!
Quick question,
I was messing around with the bootloader a bit and managed to hex edit it so that it shows "owned by noahvt" when running fastboot oem device-info and it works fine, the phone still works as normal but there is one weird issue:
The fastboot flash command does not work anymore AT ALL, it just hangs forever... commands like fastboot boot still work fine for some reason and I don't know how changing a string could have messed this up. I tried it on different machines and no change. I also dd'd the original bootloader and then it worked fine again!
Any ideas?
Related
Just as a quick intro, hello everyone. I'm new to the forum, but I've been reading from this site for a couple years now. Now that that's out of the way...to the real question.
So, my DNA committed suicide the other day and I received an HTC One M7 from a friend of mine who switched to apple. Yeah...he's stupid. But it's my gain. ANYHOW! It's a sprint HTC One m7 with the 1.57 hboot. I've come across an issue with trying to break this system open. Unlock went great along with TWRP recovery flash and superSU. No issues with any of that. HOWEVER! Somewhere down the line I believe my baseband and IMEI has been lost internally. I only come to this conclusion through research and finding a somewhat similar situation.
Currently, this is what's happening. I can enter bootloader and recovery just fine. The phone boots up just fine. But, once the phone is booted and I unlock the screen, all I get is a white screen with an HTC logo. Touch works, vibration works, it registers everything I do including the pull down (just to display header. it never actually pulls down), usb debugging icon, sounds, screenshot, PC recognizes device and everything. But it stays like this for about a minute or two and then restarts. It does this over and over.
I've been trying to s-off using rumrunner just to see if by chance it'd have success, but the phone won't recognize ADB. It will recognize fastboot commands perfectly, but not ADB. And yes...I use ADB commands in recovery I've tried every driver I could think of and every version of recovery and adb.exe I could find compatible. Because the computer won't recognize the phone in ADB, I can't get anywhere in rumrunner and because I can't access the main screen after unlocking the screen, I can't even use sunshine.
I'm at a total loss and I don't have any money for another phone. I really need some advice to get this fixed so I can flash a baseband and/or RUU and get this thing working with ViperONE. Please halp!
- Charles
You need to flash a stock ruu with fastboot and the imei will restore .
To see if the imei is still in the partition but the software doesn´t recognize it go in fastboot mode and type fastboot getvar all and the imei should be there.
Hi all, first time posting here.
Last night my Nexus 5 turned itself off while charging. Today it won't boot past the white Google logo. I had an unlocked bootloader, but was stock with no root and no custom rom, 5.1.1. I've had the phone for over a year, and bought it from a high street UK phone chain on contract, not from the Play Store.
I've spent the last 6 hours learning, trying, reading, trying again, watching videos, trying not to punch things, but nothing works.
Here's what I know:
I can boot into fastboot mode
bootloader is unlocked
recovery mode is a permanent black screen
"adb devices" cmd in platform-tools does not find the device
I've tried tweaking Windows 7 drivers (driver for fastboot etc.) but to no avail (including using clockwork)
"fastboot devices" returns the serial code for my phone
flashing using fastboot commands gives me "flash write failure" on bootloader-hammerhead xxx .img
even "fastboot erase boot" does not work ("failed to erase partition")
"fastboot reboot-bootloader" simply turns the phone off (does not attempt even a normal reboot)
Unless I'm in some weird driver quandary, I fear my phone may be beyond help as even simple commands do not work. Any help is much appreciated.
I should mention that "flash-all" doesn't work within platform-tools.
The reboot doesn't actually work. When it says "waiting for device" I manually restart the phone into fastboot myself. And then I get write errors, when it's starts pushing the radio file.
imgur . com / eBk4KnX.png
Pete.D said:
Hi all, first time posting here.
Last night my Nexus 5 turned itself off while charging. Today it won't boot past the white Google logo. I had an unlocked bootloader, but was stock with no root and no custom rom, 5.1.1. I've had the phone for over a year, and bought it from a high street UK phone chain on contract, not from the Play Store.
I've spent the last 6 hours learning, trying, reading, trying again, watching videos, trying not to punch things, but nothing works.
Here's what I know:
I can boot into fastboot mode
bootloader is unlocked
recovery mode is a permanent black screen
"adb devices" cmd in platform-tools does not find the device
I've tried tweaking Windows 7 drivers (driver for fastboot etc.) but to no avail (including using clockwork)
"fastboot devices" returns the serial code for my phone
flashing using fastboot commands gives me "flash write failure" on bootloader-hammerhead xxx .img
even "fastboot erase boot" does not work ("failed to erase partition")
"fastboot reboot-bootloader" simply turns the phone off (does not attempt even a normal reboot)
Unless I'm in some weird driver quandary, I fear my phone may be beyond help as even simple commands do not work. Any help is much appreciated.
Click to expand...
Click to collapse
Did you try locking the bootloader, and then unlocking it again?
Oh god , I think you have a hard bricked nexus .
Schoat333 said:
Did you try locking the bootloader, and then unlocking it again?
Click to expand...
Click to collapse
Good idea! Just tried it (which it let me do) but still getting write errors running flash-all.
Given the sudden shutdown and corruption on your phone along with failure to write and to erase sounds like your internal memory has gone bad.
If that's the case you won't be able to to anything. I had the same occur with a Galaxy S3 last year and the nand memory went bad. Unfortunately it does happen, but not often. My guess is you now have a paperweight
I have search XDA, and the net as a whole, and I have found many people with this same problem, and a few that were able to fix it -- however none of the fixes have helped me.
The problem is that once the boot loader is unlocked, I am no longer prompted to allow a connection from ADB so the RSA key doesn't get installed. If I do an adb devices, it shows as unauthorized.
This isn't a huge issue since I can still use any terminal program and execute the same commands on the phone itself, however, that is not ideal. I would really like to be able to use adb and fastboot to pull images, dump files, etc to my PC. As it stands now, I have to use a wireless KB / mouse, execute the commands in a terminal, and then transfer the files to my laptop.
I have tried taking the key that gets generated in %appdata%\.android and copying it to /data/misc/adb/adb_keys, and /adb_keys and /data/adb/adb_keys. I have also tried setting the build.prob variable ro.adb.secure to 0 -- no luck.
If anyone has any other ideas, it would be greatly appreciated. Again, this only happens once I unlock the boot loader (which is needed to root MM). Stock MM gives the prompt on the phone, and I can communicate just fine with adb and fastboot (obviously, need fastboot to unlock the bootloader ).
EDIT: I have an MS631 -- not sure if H631 has this same problem.
-- Brian
So I had a brilliant idea during lunch just now (yea, that is a whole lot of sarcasm).
I figured I would just lock the boot loader back, use adb and then then unlock it. So I boot into fastboot mode, do an oem lock, and then it dawns on me that I kinda need that unlocked bootloader to boot back into the OS. Well, unfortunately my fingers were typing a little faster than my brain was thinking and a fastboot reboot had already happened... LMAO. So, Now I get to sit here and install the LP KDZ, and root / install twrp, then install MM, and root / install TWRP, then restore the backup (that luckily I made right before being a moron) *sigh*. Prime example of why finding a way to boot MM without unlocking the boot loader is so important ....
-- Brian
I have had problem with fastboot earlier mentioned in another post.
The problem is like this: I unlocked a D2302 with flashtool, then relocked with flashtool(drm marlin is lost). However, I coild not unlock persistently anymore afterwards. Any trial with oem unlock first say command did not succeed and then say device is already rooted in the second trial(without rebpoting). If just boot into fastboot and try "fastboot boot", it won't work, but if I first unlock once, it would works to open twrp.
I was too curious to try if wiping an TA with zero could help me and now I am feeling totally regretting( I backed up it in internal sd?).
My phone now no longer goes into either fastboot/flash mode, only a blinking red led is shown when connected to power.
Any help is appreciated. More kudos for methods not involving serial.
My log in terminal
https://pastebin.com/5HCRPdCU
Hi everyone. Thanks for your attention
I have a HTC Mini. Today I wasn't able to connect my phone into the wifi. Then, I restarted and afterwards the phone didn't boot at all. It goes only to the bootloader menu. Last two days I was looking for the solution. In the HBOOT menu when I tried to the factory reset it only jumps into the fastboot menu, same thing for the recovery. When I am in the fastboot menu, if I click on reboot, or reboot bootloader it just reboot and the HBOOT menu comes again.
However, my HBOOT menu is locked and when I wanted to try unlock it. following problem happen :
- when I connect the phone to a Mac, Fastboot Devices detect (but only fastboot, ADB devices return nothing) the phone and I could get the token for unlocking procedure, but when I load the the unlock token which sent to me by mail from HTCDEV, nothing happen. it just say everything was successful on Terminal, but nothing shows up on the phone to Confirm unlocking procedure and sometimes it hangs and if I try pushing the token again (the bin file), I receive an error, fail to splash the screen (something like this). However, I already installed the HTC Sync Manager and every other possible driver I could find on the internet.
When I use windows, after installing HTC Sync and all of the drivers several time, still the command for Fastboot devices or ADB Devices return nothing. I don't care about the phone data or anything. I just want to like Flash the whole operating system and everything . thats fine. But nothing is working properly.
Please guide me if you have any idea about this problem.:crying::crying:
It happened to me too. Same sh1t. Camera didn't worked so i decided to restart the phone...from that time same story like yours.
same here, but i have an idea
when i do fastboot getvar all my baseband says N/A indicating corrupt or missing radio rom
the correct radio should be Radio_1.29.40g on mine based on the RUU i have on hand (used before)
RUU attempts to get into different mode and fails
i have been unable to extract the files from the RUU