Database Develop

[Q] Unable to downgrade or flash recovery with... weird G1?

Hello all,
So I've read all threads I could, I googled everything I could, but still no deal. When I try to downgrade to DREAIMG.nbh I get Model ID Incorrect!
And when I try to flash recovery directly, I get:
Code:
$ sudo ./fastboot flash recovery recovery.img
sending 'recovery' (4602 KB)...
OKAY [ 1.729s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 3.111s
My question is: is there a way to downgrade with fastboot? What if I try fastboot update DREAIMG.nbh?
I had it rooted already, but the speaker broke, took it somewhere to be fixed, but they ended up changing "all the insides". I don't remember it was this difficult to root it the last time, but it was a couple of years ago. This is the current phone booting in fastboot:
Code:
DREAM PVT 32B Ship S-on
HBoot-1.38.0000 (DREA20000)
CPLD-4
RADIO-2.22.16.19
Feb 28 2009, 18:40:30
And this is the about phone:
Code:
Build number
1.58.901.3 PLAT-1.0_gms-141395 CL#15959 release-keys
Firmware version:
1.1
Baseband version:
62.41s.20. 13u_2.22.16.19
Kernel version:
2.6.25-deb9915c
Herbert2and18-2 #11
Build number:
1.58.901.3 plat-1.0_gms-141395 CL#15959 release-keys
What else can I try? I'm comfortable with fastboot and would prefer to do everything in there. Do I really need to downgrade to install a new recovery? Is there another recovery I could try with this model?

Its not hard, and if your speaker broke they didn't need to change anything but the speaker. It looks like they gave you either a new phone or changed out the motherboard. Is this a rogers g1 by chance? Or who is it branded to on the splash screen?
Sent from my HTC Vision using xda premium

It's an Italian TIM branded. It was TIM branded on the splashscreen before and so is this "new" version. Yeah, it should be just replace the speakers, but it took them a lifetime, it came not working and they had to fix it again. So they seem to have changed the motherboard. That was in Italy.
One thing I don't understand. If I do
Code:
fastboot boot recovery.img
it loads up the recovery. But I can't do
Code:
fastboot flash recovery recovery.img
and it gives me that signature failure. Why?
BTW, I also tried the goldcard thing without success...
Anything else I could try?

Well you have s-on right, I don't believe you can flash anything in fastbbot. Hboot should load and flash the .nbh files, a signature fail probably means you have a bad copy. Check the md5 sums or download and flash another one. Maybe even try orange.nbh
Sent from my HTC Vision using xda premium

The S-On is your weakness in this, try to search in the threads to solve this, and try matching your Radio/HBOOT with Orange/Rogers dream, and I think you still have the standard Radio/HBOOT.

So I suppose I can't go wrong with the .nbh file, right?
I can try the orange one, or the rc29, and if it's the wrong version it will simply fail, without bricking the device?
(The G1 is old, but I still love this keyboard).

Ok, done!
The trick was to get a recovery installed. I had to use that flashrec app. Once that was done everything else was easy. I can't paste links yet, so here's some quick notes for any future visitors:
get Flashrec.apk. search the forums or google
get latest amon_ra recovery
Put them both on the sd card. Run the app on the phone (from some file browser app). Put /sdcard/amon_ra_recovery_filename_whatever.img instead of the webaddress it may have as default. Flash.
Once the custom recovery is in place you can proceed with DangerSPL on the wiki as normal, as with newer radios and SPL's.

Yeah, you're right. Another option is to flash it from Terminal Emulator - It's just like Command Prompt, but for your phone. Nice work finding it out for yourself!

[Q] Freezing while Flashing or just about anything.

Just going to start by saying I'm an absolute noob with Android, so I'm sorry for the burden.
Ok, Randomly my phone decided it wouldn't proceed past the HTC Splash screen. So obviously I searched for a problem and found this: http://forum.xda-developers.com/showthread.php?t=1337105
Now before anything is said on this I'm going to say being nooby and all I wasn't sure whether I should post on ^^ That or make a new thread about specifically this topic.
Back to topic, I managed to unlock the phone, but whenever I try to flash the recovery it does nothing and I get this on my command:
c:\Android>fastboot flash recovery recovery-clockwork-5.0.2.0-vivo.img
sending 'recovery' (3726 KB)...
OKAY [ 1.173s]
writing 'recovery'...
And the phone completely freezes. Also might be worth mentioning that when I unlocked it it did not go back to the HBOOT menu and I had to remove the battery.
I tried this multiple times with the same outcome.
Currently on the HBOOT menu the details are:
*** UNLOCKED ***
VIVO PVT SHIP S-ON RL
HBOOT-2.00.0000
RADIO-3822.10.08.28_M
eMMC-boot
Nov 1 2011, 20:33:03
My phone carrier is Optus (AUS) not sure if that helps with anything though.
I've searched all night for a solution but found nothing.

[Q] Have I now botched my M7 beyond repair?

And I thought this would be a simple update from T-mobile Stock Rom to GPe Rom. The good news is I have another idential virgin HTC T-mobile M7 (bought two), and could happily make backups from that one if doing so would help here.
I have a T-mobile HTC One M7.
Here's what I did:
-installed twrp sucessfully
-unlocked bootloader sucessfully
-installed this rom vita twerp: http://forum.xda-developers.com/showthread.php?t=2341395
Then the problems, which I no doubt made worse with my efforts to fix them:
-experienced a bootloop after the ROM was sucessfully loaded
-tried to fix said bootloop by flashing the Guru Reset file ( http://www.htc1guru.com/downloads/stock-rom-downloads/ ) corresponding to my model, namely http://www.htc1guru.com/dld/guru_reset_m7_1-27-531-11-zip/ .
-Realized too late that this file wouldn't work with the touchscreen on my M7 because the firmware was newer than the rom. So now the touchscreen is completely non responsive.
That would be fine, except somehow in the process I broke both twep recovery (I can't load into recovery anymore), and the usb connection to my PC. (The bootloader screen says "fastboot usb" when the cable is connected, as I gather it should. But I can't find the device via adb.
Interestingly to me, I *can* still write from PC to my internal storage when I do a regular boot. So USB debugging is still enabled (indeed I can't disable it, because of the crippled touchscreen problem).
Here is my current info in the bootloader, line by line:
***TAMPERED***
***UNLOCKED***
M7_UL PUT SHIP S-ON RH
HBOOT-1.55.0000
RADIO 4A.17.3250.20
Open DSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Oct 14 2013, 17:31:32.0
I am now lost, after 4+ hours of work. Right after flashing a nook HD+ to CM 11 with no issues...maybe gave me a false sense of confidence?
Anyway, would *very much* appreciate any guidance you all can offer. TIA!

polphi said:
And I thought this would be a simple update from T-mobile Stock Rom to GPe Rom. The good news is I have another idential virgin HTC T-mobile M7 (bought two), and could happily make backups from that one if doing so would help here.
I have a T-mobile HTC One M7.
Here's what I did:
-installed twrp sucessfully
-unlocked bootloader sucessfully
-installed this rom vita twerp: http://forum.xda-developers.com/showthread.php?t=2341395
Then the problems, which I no doubt made worse with my efforts to fix them:
-experienced a bootloop after the ROM was sucessfully loaded
-tried to fix said bootloop by flashing the Guru Reset file ( http://www.htc1guru.com/downloads/stock-rom-downloads/ ) corresponding to my model, namely http://www.htc1guru.com/dld/guru_reset_m7_1-27-531-11-zip/ .
-Realized too late that this file wouldn't work with the touchscreen on my M7 because the firmware was newer than the rom. So now the touchscreen is completely non responsive.
That would be fine, except somehow in the process I broke both twep recovery (I can't load into recovery anymore), and the usb connection to my PC. (The bootloader screen says "fastboot usb" when the cable is connected, as I gather it should. But I can't find the device via adb.
Interestingly to me, I *can* still write from PC to my internal storage when I do a regular boot. So USB debugging is still enabled (indeed I can't disable it, because of the crippled touchscreen problem).
Here is my current info in the bootloader, line by line:
***TAMPERED***
***UNLOCKED***
M7_UL PUT SHIP S-ON RH
HBOOT-1.55.0000
RADIO 4A.17.3250.20
Open DSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Oct 14 2013, 17:31:32.0
I am now lost, after 4+ hours of work. Right after flashing a nook HD+ to CM 11 with no issues...maybe gave me a false sense of confidence?
Anyway, would *very much* appreciate any guidance you all can offer. TIA!
Click to expand...
Click to collapse
Looks like your OS is gone. Did you try and reflash twrp?
---------- Post added at 08:25 AM ---------- Previous post was at 07:55 AM ----------
24.531
polphi said:
And I thought this would be a simple update from T-mobile Stock Rom to GPe Rom. The good news is I have another idential virgin HTC T-mobile M7 (bought two), and could happily make backups from that one if doing so would help here.
I have a T-mobile HTC One M7.
Here's what I did:
-installed twrp sucessfully
-unlocked bootloader sucessfully
-installed this rom vita twerp: http://forum.xda-developers.com/showthread.php?t=2341395
Then the problems, which I no doubt made worse with my efforts to fix them:
-experienced a bootloop after the ROM was sucessfully loaded
-tried to fix said bootloop by flashing the Guru Reset file ( http://www.htc1guru.com/downloads/stock-rom-downloads/ ) corresponding to my model, namely http://www.htc1guru.com/dld/guru_reset_m7_1-27-531-11-zip/ .
-Realized too late that this file wouldn't work with the touchscreen on my M7 because the firmware was newer than the rom. So now the touchscreen is completely non responsive.
That would be fine, except somehow in the process I broke both twep recovery (I can't load into recovery anymore), and the usb connection to my PC. (The bootloader screen says "fastboot usb" when the cable is connected, as I gather it should. But I can't find the device via adb.
Interestingly to me, I *can* still write from PC to my internal storage when I do a regular boot. So USB debugging is still enabled (indeed I can't disable it, because of the crippled touchscreen problem).
Here is my current info in the bootloader, line by line:
***TAMPERED***
***UNLOCKED***
M7_UL PUT SHIP S-ON RH
HBOOT-1.55.0000
RADIO 4A.17.3250.20
Open DSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Oct 14 2013, 17:31:32.0
I am now lost, after 4+ hours of work. Right after flashing a nook HD+ to CM 11 with no issues...maybe gave me a false sense of confidence?
Anyway, would *very much* appreciate any guidance you all can offer. TIA!
Click to expand...
Click to collapse
Try running this 3.24.531.3 ruu, instructions on page.
http://forum.xda-developers.com/showthread.php?t=2375223

Thanks very much folks. Somehow, I was able to reflash twrp. From there, I realized that one mistake I made was overlooking that I needed s-off activated before flashing the ROM. (I think that was the beginning of my difficulties.)
Before reflashing twrp, I tried the RUU suggestion (TY!), but that needed bootloader turned back on, which in turn needed s-off...quite a procedure.
Anyway, With s-off done (thanks to the very persistent rumrunner_HTC_0.5.0.zip !), a second flash attempt of the rom at http://forum.xda-developers.com/showthread.php?t=2341395 worked seemingly perfectly. I now just trying to figure out whether I can get wifi calling working reliably (should be able to in theory, and at least one poster in that thread says he's done so).
Getting the HTC one properly modded is not a simple process relative to my prior experiences. I'm grateful for the help!

All of that work in the beginning was not needed. All you had to do was unlock bootloader, S-Off, change CID to 11111111, and run the GPE RUU from HTC. That's it. I had an ATT version that saw every different incarnation of software and it was that easy every time. Went from ATT to GPE, to T-Mobile, to Dev Edition and back without a problem. Well, red triangles of death be damned, but it never slowed me down, and the only time I got those was when I mis-matched the recovery img, or tried an update with a HBoot higher that 1.44, those are the only thinga to watch for. Make sure your ducks are in a row and update away. Stock recovery and lower Hboot worked awesome. I probably should put together a master file of everything I have for DL because I have it all and would make life so easy if someone hasn't done it already.

[Q] VZW/S-On/Can't Flash Roms/Can't Get S-Off/ADB and Fastboot Work

Here's what my bootloader says:
*** TAMPERED ***
*** UNLOCKED ***
M7_WLV PVT SHIP S-ON RH
HBOOT-1.54 0000
Radio-1.12.42.1104
OpenDSP-v3.1.120.274.0617
OS-1.10.605.15
eMMC-boot 2048
Nov 8 2013, 00:54:21.23263
The other day I tried flashing a Rom in TWRP and it failed mid-way saying that it couldn't mount the System Partition (that's from my memory, I don't remember the exact message). I looked it up and someone said it may be a problem with my recovery, so after painstakingly booting up a Windows 7 Virtual Machine (I'm running Windows 8.1), I finally flashed Philz CWM. However, the same dumb error happened. Since the ROM failed halfway, I can't get into Android. I've tried factory resetting obviously, but that didn't work. My next thought was to flash an RUU, but since my device is S-ON I cannot. I then tried pushing REVONE (which appeared to be the only one you don't need a ROM to do), but I kept getting errors when Preparing it to S-OFF (I'm assuming because there's no OS?).
So long story short, I can't Flash Roms because my system partition isn't mountable, I can't flash an RUU because I'm not S-OFF and I can't S-OFF because I can't boot into Android.
If anyone has any idea on how to save my phone, get S-OFF, or fix the system partition please help!
Thanks in advanced.

aidendudewow said:
Here's what my bootloader says:
*** TAMPERED ***
*** UNLOCKED ***
M7_WLV PVT SHIP S-ON RH
HBOOT-1.54 0000
Radio-1.12.42.1104
OpenDSP-v3.1.120.274.0617
OS-1.10.605.15
eMMC-boot 2048
Nov 8 2013, 00:54:21.23263
The other day I tried flashing a Rom in TWRP and it failed mid-way saying that it couldn't mount the System Partition (that's from my memory, I don't remember the exact message). I looked it up and someone said it may be a problem with my recovery, so after painstakingly booting up a Windows 7 Virtual Machine (I'm running Windows 8.1), I finally flashed Philz CWM. However, the same dumb error happened. Since the ROM failed halfway, I can't get into Android. I've tried factory resetting obviously, but that didn't work. My next thought was to flash an RUU, but since my device is S-ON I cannot. I then tried pushing REVONE (which appeared to be the only one you don't need a ROM to do), but I kept getting errors when Preparing it to S-OFF (I'm assuming because there's no OS?).
So long story short, I can't Flash Roms because my system partition isn't mountable, I can't flash an RUU because I'm not S-OFF and I can't S-OFF because I can't boot into Android.
If anyone has any idea on how to save my phone, get S-OFF, or fix the system partition please help!
Thanks in advanced.
Click to expand...
Click to collapse
well your phone was s-off at some point because you can't unlock the bootloader otherwise. why is it back to s-on ?
you'll have to try and format data in twrp and sideload a rom to the phone with adb

I'm actually not sure... I ordered the phone off of Ebay rooted and it was S-ON (the device was running CM 10 when I ordered it around a year ago.) I'll flash TWRP and format, and hopefully that will do the trick. Sideloading on CWM doesn't work at the moment. Thanks

clsA said:
well your phone was s-off at some point because you can't unlock the bootloader otherwise. why is it back to s-on ?
you'll have to try and format data in twrp and sideload a rom to the phone with adb
Click to expand...
Click to collapse
I wiped all of the data in TWRP and tried sideloading but got an error. I then tried pushing the zip onto it and got another error (some protocol errors or something), but then after restarting and trying like 10 different times I finally got it to push the zip, and then after like 10 more tries I got it to install. Phew. Thanks for the help

Soft Bricked when resetting to stock

Hey all. Been browsing the forum to try to figure this out on my own, but I honestly don't understand this stuff enough to decipher what I need to do next (my experience is with x64-based PC systems).
So let's start off with the background as to what happened. Went back to using my Sprint HTC One as my Samsung S6 Edge decided to go for a dip in some water (yeah, I know). Anyway, I hadn't used the One in almost 2 years so as you can imagine, it was extremely out of date. I had forgotten that I had rooted the device and was running Cyanogenmod on it as well (with TWRP), so I attempted to reset everything to stock (stock ROM and recovery) in order to get OTA software and firmware updates.
After browsing the forum a bit, I decided to use the GuruReset with Aroma installer to reset everything to stock (running the tool through the TWRP recovery on the device itself). It seemed like it worked just fine, but upon reboot, it now just sits at the bootloader and none of the options really do anything (just reboots it back to the bootloader again). I will list a readout of what I see on my screen and hopefully you guys can help out a fellow nerd (and admitted Android noob) figure out this issue.
Btw, I have already attempted to use the HTC One Toolkit v3.3.0 (EoL) to no avail (whenever I try to use one of the options in the toolkit, the program crashes). Running Windows 10 on my PC.
---------------------------------------------------------------------------------------------------------
***TAMPERED***
***UNLOCKED***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.57.0000
OpenDSP-v32.120.274.0909
OS-5.05.651.2
eMMC-boot 2048MB
Sep 24 2014, 16:58:42.0

Nothing?
530+ views and no one has any ideas to throw around?

Have you tried pushing a custom rom on it and flashing it trough TWRP , that may work

Corbarum said:
Have you tried pushing a custom rom on it and flashing it trough TWRP , that may work
Click to expand...
Click to collapse
That's basically what I did to cause the problem in the first place. Had TWRP installed with Cyanogenmod from a couple years ago. Went to reset it to stock ROM and stock recovery. Now it just sits at the bootloader without doing anything. Doesn't even seem like there's a recovery on it at all.... Basically, the flash to stock failed from what I can tell and now there's nothing on it to load.

Try reFlashing TWRP on it, and look for the original rom
I still have no idea why you want the original recovery. but well, your choice
Also the thing is you might have just deleted the whole recovery , from what I know when you flash a custom recovery you overwrite the original recovery, so when you removed it completely
sorry , I am a newbie as well , I barely managed to fix my own m7 but now it works fine with cyanogenmod 13

DComm said:
Now it just sits at the bootloader without doing anything. Doesn't even seem like there's a recovery on it at all.... Basically, the flash to stock failed from what I can tell and now there's nothing on it to load.
Click to expand...
Click to collapse
Can you please post the output of "fastboot getvar all" (remove your imei, meid and serialno before posting)
What version of Guru reset rom did you flashed exactly (link) ?
I think it would be better to flash a RUU and have everything back to stock (wating for your getvar)
Btw twrp got overwritten by the stock recovery when flashing the Guru reset rom, that why twrp isn't there anymore.