Database Develop

Unrooting Rogers HTC Dream

During the process of rooting my phone, I somehow ended up with my provider information saying
Rogers AT&T
Rogers AT&T
I haven't seen anyone else with this issue, and as far as I can tell it's purely cosmetic, but it's annoying and I want to get rid of it. I figured the best route was to unroot to stock, then root again.
Now I've searched and come across multiple ways to unroot, but I'm not quite sure what is what.
My current SPL is 1.33.2005
My current Radio is 2.22.19.261
Now, I've seen 2 ways of doing this.
1. Download the rogersradio and rogersrecovery image files, then run the rogers update.zip.
2. Download the latest software update from rogers and bang, unrooted.
The problem with #1 is that I can't find a rogers update.zip. The problem with #2 is that it sounds too easy.
Any suggestions?

You can find the instructions to go back to stock rogers here. I've been looking for the back up radio for a while so that I can try the G1 radio and other roms and finally found it.
http://forum.xda-developers.com/showthread.php?t=544654&highlight=losemyroot

Yeah, that's the first one I came across...
I was fine until I saw:
and flash the update.zip found somewhere on this forum ;P
Click to expand...
Click to collapse
That seems to be the issue, I can't find the update.zip that corresponds to the rogers version.

http://www.stevebirstok.com/android/losemyroot.zip

That's just the radio and recovery.
From the sounds of it, you need these flashed before you flash the update.zip....
Regardless, heres the original radio (3.22.20.17) and the original recovery (WARNING: UNROOTED) from rogers dream:
losemyroot.zip
Code:
fastboot flash radio rogersradio.img
fastboot flash recovery rogersrecovery.img
fastboot erase system -w
and flash the update.zip found somewhere on this forum ;P
Click to expand...
Click to collapse
My impression is that I need to flash the radio and recovery, then the rogers rom.

yes you are correct

Need a herocimg.zip, tired of looking.

I've been looking through the forum and googleing for a while. I can't seem to find any herocimg.zip's. I need one of these because my HTC Hero will not boot past the HTC screen nor go past the bootloader into recovery. If you have any suggestions on how to fix that problem they would be apprecaited. As of the moment I've only BEEN ABLE TO clear user data from the bootloader.

Agentx002 said:
I've been looking through the forum and googleing for a while. I can't seem to find any herocimg.zip's. I need one of these because my HTC Hero will not boot past the HTC screen nor go past the bootloader into recovery. If you have any suggestions on how to fix that problem they would be apprecaited. As of the moment I've only BEEN ABLE TO clear user data from the bootloader.
Click to expand...
Click to collapse
it's spelled hercimg, maybe that's the issue.
what would you like to be in the hercimg?
you can ruu to 2.31.651.7 with this one http://forum.xda-developers.com/showpost.php?p=9944755&postcount=9

My Hero hangs at the HTC screen, so I figured I'd try another rom. Like I said, the phone won't go into recovery. Just the voldown+power screen.

You need an HERCIMG.zip with a recovery.img inside. It will only work if you're S-OFF.
BTW, HEROIMG.zip is for the GSM Hero, not the Sprint CDMA one. If you're not S-OFF you need to follow aiwetir's link to get back to stock, re-root, and reflash your recovery..

c00ller said:
You need an HERCIMG.zip with a recovery.img inside. It will only work if you're S-OFF.
BTW, HEROIMG.zip is for the GSM Hero, not the Sprint CDMA one. If you're not S-OFF you need to follow aiwetir's link to get back to stock, re-root, and reflash your recovery..
Click to expand...
Click to collapse
or flash a recovery through ADB.

I didn't know you could use adb from hboot. Good to know.

[Q] HBOOT 1.16.0000, known ROMs to work?

So far I've had no luck using custom ROMs as it just stays on the htc boot screen and does not work. I can confirm that 'MiUi' does work on my phone - however it is buggy and I don't like it.
I want cyanogenod or either android revolution HD but none of these work.
I thinkit has something to do with the HBOOT being 1.16.000, and the ROM version i'm after is 2.34.981.1 (virgin or optus branded) - am with virgin though in Australia.
I have a custom bootloader/recovery whatever you call it, I wipe the cache, dalvik cache and factory wipe, before installing all ROM's. I can't update to stock ROM either because there is none for hboot 1.16.000
So right now my phone is pretty much a paper weight until I can get it working again.
I prefer custom ROM's if there is any that work, if not I atleast want the stock ROM to work for now so I can use my phone. If someone can help me through the process to get it working it would be greatly appreciated. Thanks.

jakeyo said:
So far I've had no luck using custom ROMs as it just stays on the htc boot screen and does not work. I can confirm that 'MiUi' does work on my phone - however it is buggy and I don't like it.
I want cyanogenod or either android revolution HD but none of these work.
I thinkit has something to do with the HBOOT being 1.16.000, and the ROM version i'm after is 2.34.981.1 (virgin or optus branded) - am with virgin though in Australia.
I have a custom bootloader/recovery whatever you call it, I wipe the cache, dalvik cache and factory wipe, before installing all ROM's. I can't update to stock ROM either because there is none for hboot 1.16.000
So right now my phone is pretty much a paper weight until I can get it working again.
I prefer custom ROM's if there is any that work, if not I atleast want the stock ROM to work for now so I can use my phone. If someone can help me through the process to get it working it would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Hyun is looking for you at revolutionary irc channel.
Sent from my HTC Incredible S using Tapatalk

I know.. I have spoken to him.

jakeyo said:
I know.. I have spoken to him.
Click to expand...
Click to collapse
Any luck? still unable to flash anything?

jakeyo said:
So far I've had no luck using custom ROMs as it just stays on the htc boot screen and does not work. I can confirm that 'MiUi' does work on my phone - however it is buggy and I don't like it.
I want cyanogenod or either android revolution HD but none of these work.
I thinkit has something to do with the HBOOT being 1.16.000, and the ROM version i'm after is 2.34.981.1 (virgin or optus branded) - am with virgin though in Australia.
I have a custom bootloader/recovery whatever you call it, I wipe the cache, dalvik cache and factory wipe, before installing all ROM's. I can't update to stock ROM either because there is none for hboot 1.16.000
So right now my phone is pretty much a paper weight until I can get it working again.
I prefer custom ROM's if there is any that work, if not I atleast want the stock ROM to work for now so I can use my phone. If someone can help me through the process to get it working it would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
If you go to the development section of the HTC Incredible 2 forum, attn1 has a script tool that uses the latest Revolutionary/Unreovked exploit to downgrade the ROMand HBOOT to a version that is supported by Revolutionary.
If you look at the script, it is pretty simple. You would just need to use an older Virgin Mobile RUU.zip instead of the Inc2 version. It looks like the 2.12.981.2 would be the one to try.

Hang on a second, how did you S-off the Hboot 1.16?
I thought you need S-off to be able to flash a custom Rom...
How did you install Miui?
Am I missing something here?

Doesnt matter if you need S-ON or S-OFF, as long as you get permissions to access root files.
Someone installed a custom bootloader so I can install custom ROM's, and it just works.... apparently the radios are locked though.
So, another day gone by and my phone is still not working. I can use MiUi, but I ran out of data on my 3g sim and wifi doesnt work, so now I have no internet on it.

katu2006 said:
Hang on a second, how did you S-off the Hboot 1.16?
I thought you need S-off to be able to flash a custom Rom...
How did you install Miui?
Am I missing something here?
Click to expand...
Click to collapse
I'm pretty sure no soff will cause the issues he is experiencing, though he doesn't seem to be listening

no, you're all just noobs.
It was the boot.img, we swapped it with the MiUi then put back the original one, now it boots up on cyanogenmod7.1 and works completely fine.
Can access root files, can take screenshots, everything is normal.
and I have s-on.

jakeyo said:
no, you're all just noobs.
It was the boot.img, we swapped it with the MiUi then put back the original one, now it boots up on cyanogenmod7.1 and works completely fine.
Can access root files, can take screenshots, everything is normal.
and I have s-on.
Click to expand...
Click to collapse
Yes im a noob that has been using android since 2009..
You seem like a supreme douche.
Weren't you the one who was crying about wanting to go back to his iphone lol

jakeyo said:
no, you're all just noobs.
It was the boot.img, we swapped it with the MiUi then put back the original one, now it boots up on cyanogenmod7.1 and works completely fine.
Can access root files, can take screenshots, everything is normal.
and I have s-on.
Click to expand...
Click to collapse
You're calling us noobs, but you don't even know what was done on your phone...
What's the following sentence supposed to say?
"It was the boot.img, we swapped it with the MiUi then put back the original one"
To get a custom Rom, you actually have to INSTALL it...To get the custom Rom installed, you need CWM recovery. But if you have HBoot 1.16.000, you can't have a custom recovery yet.
In less your "friend" did a downgrade of the HBoot to 1.13.000, it's unlikely that you have CWM recovery on your phone. Even so, to my knowledge HBoot 1.16.000 does a version check and won't let you downgrade it.
So, the question remains, how did you get CWM recovery on your phone?

katu2006 said:
You're calling us noobs, but you don't even know what was done on your phone...
What's the following sentence supposed to say?
"It was the boot.img, we swapped it with the MiUi then put back the original one"
To get a custom Rom, you actually have to INSTALL it...To get the custom Rom installed, you need CWM recovery. But if you have HBoot 1.16.000, you can't have a custom recovery yet.
In less your "friend" did a downgrade of the HBoot to 1.13.000, it's unlikely that you have CWM recovery on your phone. Even so, to my knowledge HBoot 1.16.000 does a version check and won't let you downgrade it.
So, the question remains, how did you get CWM recovery on your phone?
Click to expand...
Click to collapse
This thread is awesome

no, if I hold down power down and power button I see S-ON and HBOOT 1.16.0000
He typed in commands to give it root permissions, not sure exactly as he remote controlled my computer and typed it in. Then yes, he flashes CWM onto the phone then I installed revolutionary.
Firstly, I went onto the HTC dev site (created an account) and followed the steps to unlock the bootloader. In the end, it was successful, and once it's finished it will wipe the phone (AND WILL STILL SAY s-on)
So then the bootloader is now unlocked, and he did various commands in fastboot. My guess is that he installed CWM from there and it just worked.
at first, cyanogenmod would not boot, so he copied the (boot.img that is working) from MiUi and repled it with cyanogenmod's. The phone booted up and worked. Then he put it back how it was and it now works. Strange, but something must've given it a kick.
I'll repeat myself.
HBOOT 1.16.0000
S-ON
Cyanogenmod &.1 (stable)
Full root access
Need I say more to prove it?
As far as I know, I just cannot flash radios, which actually require the S-OFF....
sorry if I come across as rude, just a long day..

Talk to aftab565 he has the same hboot as you and has arhd running. Sounds like your phone was temp rooted and flashed and I would advise against letting people you don't know take remote access of your pc.

Hopefully it works for him I couldn't help.

Just replied to his thread.
And I know I was aware. I had full control though (could press a certain key to disconnect the connection - and only gave a temporary password) He was only typing in CMD things to do with the phone that I've heard of before
(ADB shell, fastboot recovery etc) and in the end worked well. He said my job is done and disconnect himself, so good guy
Didn't take my eyes off the screen either.

jakeyo said:
Just replied to his thread.
And I know I was aware. I had full control though (could press a certain key to disconnect the connection - and only gave a temporary password) He was only typing in CMD things to do with the phone that I've heard of before
(ADB shell, fastboot recovery etc) and in the end worked well. He said my job is done and disconnect himself, so good guy
Click to expand...
Click to collapse
You gotta give props to these guys for donating their time. Every day there's more talk about h-boot 1.16.0000 so I figure if devs want to keep devin there'll be a rev released eventually.

I really appreciate the amount of work hes done, in total I recon he's spent about 6 hours trying to help me getting it to work.
Never left me by myself, he always helped me through every step and was always there if I needed help. I've now got CM7 thanks to him. If he didn't fix it, I would have a useless phone because I couldn't even put on the stock ROM because of my HBOOT im guessing (I did an OTA update to get 1.16.0000 therefore too new to download)
I think SOME of the custom roms do have support for 1.16.0000 and what you only need is the boot file from them to boot up your non-booting ROM then you're all good.

ok, just to put some closure and sanity on this thread.
Firstly I'm probably bettery know as hyuh on #revolutionary, and it was me who was connected to his PC.
I use teamviewer to connect to people remotely, this allows anyone who doesn't like the look of *anything* I do to diconnect me...The user in front of the PC has full control of my session and I remind them to close teamviewer after we're done.
Secondly to those who think you need to be S-OFF to install a custom ROM or custom recovery, this is simply not true in the case of the 1.16 hboot. If you follow the HTC unlock procedure then you will have sufficient access to the phone to do this, it is not S-OFF just an unlock. Your phone will be in state "S-ON unlocked" This allows certain partitions on the emmc to be written to, and this sufficient for custom ROMs.
Really all that is requird is:
Code:
fastboot flash recovery <recovery.img>
then follow the normal flashing procedures.
In jakeyo's case CM7 would not boot, but MIUI would. When I say it would not boot I do not mean a boot loop here, I mean no boot period. At this point I had expected to need to rebuild a boot image for CM7 for him suspecting that HTC had done something different in the new hboot with paritions or the boot image offset.
The reason for flashing the MIUI boot image on top of CM7 was simple, to get to adb in the boot image. However seeing nothing particularly strange in the boot sequence ( other than the mismatch and resulting bootloop) I decided to reflash the CM7 boot image through fastboot.
The phone booted fully this time without issues.
It appears that the boot image simply did not flash properly from recovery the first time but I don't have a vivo to troubleshoot further.
A couple of things:
1. Don't take the OTA for 1.16 hboot if you haven't already done so.
There is currently no unofficial unlock/S-OFF
There is no RUU to fix the phone if you screw up.
There is nothing in the OTA you can't get in other ways.
2. If you're on 1.16 and want custom ROMs and aren't worried about warranty, go ahead and do unlock from HTC, but bear in mind:
There is no RUU, so you can't go back to stock
You can't flash radios
You can't superCID or similar ( but not needed since there is no RUU )
2a. You don't need any existing root method to exist, there is no exploit involved in any of this, this will work irrespective of the current status of a root expoit existing or not.
2b. The phone does not have to be listed by HTC as being supproted. Any phone with a suitable hboot can be unlocked.
if this:
Code:
fastboot oem get_identifier_token
returns an identifier code then the phone can be ulocked.

globatron said:
ok, just to put some closure and sanity on this thread.
Firstly I'm probably bettery know as hyuh on #revolutionary, and it was me who was connected to his PC.
I use teamviewer to connect to people remotely, this allows anyone who doesn't like the look of *anything* I do to diconnect me...The user in front of the PC has full control of my session and I remind them to close teamviewer after we're done.
Secondly to those who think you need to be S-OFF to install a custom ROM or custom recovery, this is simply not true in the case of the 1.16 hboot. If you follow the HTC unlock procedure then you will have sufficient access to the phone to do this, it is not S-OFF just an unlock. Your phone will be in state "S-ON unlocked" This allows certain partitions on the emmc to be written to, and this sufficient for custom ROMs.
Really all that is requird is:
Code:
fastboot flash recovery <recovery.img>
then follow the normal flashing procedures.
In jakeyo's case CM7 would not boot, but MIUI would. When I say it would not boot I do not mean a boot loop here, I mean no boot period. At this point I had expected to need to rebuild a boot image for CM7 for him suspecting that HTC had done something different in the new hboot with paritions or the boot image offset.
The reason for flashing the MIUI boot image on top of CM7 was simple, to get to adb in the boot image. However seeing nothing particularly strange in the boot sequence ( other than the mismatch and resulting bootloop) I decided to reflash the CM7 boot image through fastboot.
The phone booted fully this time without issues.
It appears that the boot image simply did not flash properly from recovery the first time but I don't have a vivo to troubleshoot further.
A couple of things:
1. Don't take the OTA for 1.16 hboot if you haven't already done so.
There is currently no unofficial unlock/S-OFF
There is no RUU to fix the phone if you screw up.
There is nothing in the OTA you can't get in other ways.
2. If you're on 1.16 and want custom ROMs and aren't worried about warranty, go ahead and do unlock from HTC, but bear in mind:
There is no RUU, so you can't go back to stock
You can't flash radios
You can't superCID or similar ( but not needed since there is no RUU )
Click to expand...
Click to collapse
Get a mod to make a hboot sticky there will be floods of this crap further down the road.

[Q] I hope I have't bricked my Sprint HTC One

It all started when I rebooted my phone one day. My phone loaded up the lock screen with google voice. I could say the pin but could never get my phone unlocked. The keyboard button didn't work. So rather than just bootloader/factory resetting my phone, i decided i might as well unlock it and give myself root and flash a rom and try it out. I am an experienced EVO 4G user and have flashed many a rom. I did not have any problems unlocking the phone, flashing the TWRP recovery, applying su, or flashing the rom. I flashed the rootbox rom. It worked just fine. I then decided I was going to try a different rom out. I was not aware that there were roms that would cause problems... the non-sprint roms. I then tried to flash several non-sprint roms. None of the worked and eventually my phone would only boot up into the bootloader. I was able to successfully fastboot flash the TWRP recovery back onto my phone. I tried then to load in a sprint rom. Apparently I had messed up my radios, file structure and possibly other stuff, as no rom would work at that point. After much research, I found I needed to apply the RUU to get my phone back into "sprint" mode with the correct radios and file structure. I have been trying for hours now to do just that. I have tried all the methods listed on xda. The current condition of my phone: Will boot only into bootloader, will not boot into recovery although i think the TWRP recovery is still on my phone. I have the tampered, relocked, and security warning messages at the top of my phone. I am still s-on. I cannot get s-off as I have no accessible os on the phone to use the adb commands. I do have fastboot access. I have tried to fastboot flash the ruu and I get failed messages either <remote: 12 signature verify fail> or <remote: 43 main version check fail>
Any/All advice recommendations are welcome. If there is a thread about fixing bricked phones or tools to load RUU, I have tried them to no avail.
Thanks

Have you tried running the RUU from your PC? It would also help to know if you are on 1.29 or 1.31.

MrFixit007 said:
It all started when I rebooted my phone one day. My phone loaded up the lock screen with google voice. I could say the pin but could never get my phone unlocked. The keyboard button didn't work. So rather than just bootloader/factory resetting my phone, i decided i might as well unlock it and give myself root and flash a rom and try it out. I am an experienced EVO 4G user and have flashed many a rom. I did not have any problems unlocking the phone, flashing the TWRP recovery, applying su, or flashing the rom. I flashed the rootbox rom. It worked just fine. I then decided I was going to try a different rom out. I was not aware that there were roms that would cause problems... the non-sprint roms. I then tried to flash several non-sprint roms. None of the worked and eventually my phone would only boot up into the bootloader. I was able to successfully fastboot flash the TWRP recovery back onto my phone. I tried then to load in a sprint rom. Apparently I had messed up my radios, file structure and possibly other stuff, as no rom would work at that point. After much research, I found I needed to apply the RUU to get my phone back into "sprint" mode with the correct radios and file structure. I have been trying for hours now to do just that. I have tried all the methods listed on xda. The current condition of my phone: Will boot only into bootloader, will not boot into recovery although i think the TWRP recovery is still on my phone. I have the tampered, relocked, and security warning messages at the top of my phone. I am still s-on. I cannot get s-off as I have no accessible os on the phone to use the adb commands. I do have fastboot access. I have tried to fastboot flash the ruu and I get failed messages either <remote: 12 signature verify fail> or <remote: 43 main version check fail>
Any/All advice recommendations are welcome. If there is a thread about fixing bricked phones or tools to load RUU, I have tried them to no avail.
Thanks
Click to expand...
Click to collapse
Pm me your teamviewer information and I'll help you out.

bigdaddy619 said:
Have you tried running the RUU from your PC? It would also help to know if you are on 1.29 or 1.31.
Click to expand...
Click to collapse
I am on 1.31. I have tried running the RUU from my PC and I got error 140. I tried looking that up and could not find any solutions to that. I figured it was because I am on 1.31 and not 1.29 and I still had s-on. That is when I tried to get s-off so that I could apply the 1.29. Is it possible to open a fastboot shell? I was going to try to push the revone files to the phone via fastboot and then run the commands via fastboot, but didn't get around to trying that out last night.

Indirect said:
Pm me your teamviewer information and I'll help you out.
Click to expand...
Click to collapse
Thanks a bunch! I have sent you a PM. I'll send you another one when I get home from work.

MrFixit007 said:
Thanks a bunch! I have sent you a PM. I'll send you another one when I get home from work.
Click to expand...
Click to collapse
OK!! Awesome! Indirect showed me the error of my ways!! So now I have TWRP recovery back on my phone and I was able to get RUU to be successful.
What are the recommended next steps?

MrFixit007 said:
OK!! Awesome! Indirect showed me the error of my ways!! So now I have TWRP recovery back on my phone and I was able to get RUU to be successful.
What are the recommended next steps?
Click to expand...
Click to collapse
What do you want to know?
Sent from?

MrFixit007 said:
OK!! Awesome! Indirect showed me the error of my ways!! So now I have TWRP recovery back on my phone and I was able to get RUU to be successful.
What are the recommended next steps?
Click to expand...
Click to collapse
Congrats on getting phone back up. I recommend you stay away from flashing Roms that are not for Sprint but I think you learned that part first hand already.

im0rtalz said:
Congrats on getting phone back up. I recommend you stay away from flashing Roms that are not for Sprint but I think you learned that part first hand already.
Click to expand...
Click to collapse
bigdaddy619 said:
What do you want to know?
Sent from?
Click to expand...
Click to collapse
Yeah, I sure did. Coming from an OG EVO 4G that was a little bit of a nasty surprise. Wel my phone is sitting on the fastboot screen after the successful ruu. The only message at the top is **relocked***
Can i boot like normal now? Should i flash a rom at this point? i'm kinda still wearing the kid gloves...

MrFixit007 said:
Yeah, I sure did. Coming from an OG EVO 4G that was a little bit of a nasty surprise. Wel my phone is sitting on the fastboot screen after the successful ruu. The only message at the top is **relocked***
Can i boot like normal now? Should i flash a rom at this point? i'm kinda still wearing the kid gloves...
Click to expand...
Click to collapse
Did Indirect get you S-OFF? If not you need to unlock your bootloader again then re-flash TWRP or CWM then you can flash a rom. Any questions shoot me a PM

bigdaddy619 said:
Did Indirect get you S-OFF? If not you need to unlock your bootloader again then re-flash TWRP or CWM then you can flash a rom. Any questions shoot me a PM
Click to expand...
Click to collapse
We did not get to s-off. I am still s-on. the way I understand it is that basically I am back at square one... only I can use the fastboot command to unlock the bootloader, I don't need to go to the HTC website. and once i put a recovery on i can load any SPRINT ROM i want.
i'll do my best to be good this time

MrFixit007 said:
We did not get to s-off. I am still s-on. the way I understand it is that basically I am back at square one... only I can use the fastboot command to unlock the bootloader, I don't need to go to the HTC website. and once i put a recovery on i can load any SPRINT ROM i want.
i'll do my best to be good this time
Click to expand...
Click to collapse
Check PM

MrFixit007 said:
OK!! Awesome! Indirect showed me the error of my ways!! So now I have TWRP recovery back on my phone and I was able to get RUU to be successful.
What are the recommended next steps?
Click to expand...
Click to collapse
Indirect helps so many people on herr. We are lucky to have the folks in this forum.
Sent from my (M7WLS) HTC ONE.

theotrman said:
Indirect helps so many people on herr. We are lucky to have the folks in this forum.
Sent from my (M7WLS) HTC ONE.
Click to expand...
Click to collapse
Indirect is a beast

bigdaddy619 said:
Indirect is a beast
Click to expand...
Click to collapse
yep! Indirect and bigdaddy are both beasts!

theotrman said:
Indirect helps so many people on herr. We are lucky to have the folks in this forum.
Sent from my (M7WLS) HTC ONE.
Click to expand...
Click to collapse
Indirect and bigdaddy have both helped me out bunches tonight!!! I am completely back in action!!

What in the world did Indirect do that worked to well?
I'm in a similar situation right now and I'm still stuck.

NotSneakyNinja said:
What in the world did Indirect do that worked to well?
I'm in a similar situation right now and I'm still stuck.
Click to expand...
Click to collapse
Probably downgraded him from 1.31 to 1.29 so he could RUU
Sent from?

NotSneakyNinja said:
What in the world did Indirect do that worked to well?
I'm in a similar situation right now and I'm still stuck.
Click to expand...
Click to collapse
The key is knowing what fastboot commands to use and in which order. I had gotten stuck and gotten some of them out of order. I'd be willing to help you out like indirect did for me. If you PM me your teamviewer information i can help you out.

MrFixit007 said:
The key is knowing what fastboot commands to use and in which order. I had gotten stuck and gotten some of them out of order. I'd be willing to help you out like indirect did for me. If you PM me your teamviewer information i can help you out.
Click to expand...
Click to collapse
I got him fixed up

[q] help!a crazy problem!

(I'm a Chinese middle school student,I'm not very good at English,there may be some problems in the passage,sorry)
There is something wrong with my HTC G1.The device is given by my uncle,I don't know what he has done,but when I want to update it
to hboot-1.33.0013d/radio-2.22.28.25,I can't do it.When I connect it to my computer,it still worked,but when I flashed the recovery 1.7.0,the fastboot didn't react any more.When I checked the hboot in my G1,it showed me it is s-off,but I can't use the fastboot to update the device.Now,I'm still using the Android 1.6 rom and the 1.42.2000 spl and the 2.22.16.19 radio.And I can't receive help in any Chinese forum,so I post in xda-developers.What can I do?If person who helps me need more things about my G1,please ask me.
If someone can help me,THANK YOU VERY MUCH!

Search for orange.nbh
Flash this in bootloader than you will need to flash new recovery then radio then SPL in fastboot
Now boot to recovery and flash rom of choice
Sent from my Nexus 4 using XDA Premium 4 mobile app

hope this will help
htc g1 said:
(I'm a Chinese middle school student,I'm not very good at English,there may be some problems in the passage,sorry)
There is something wrong with my HTC G1.The device is given by my uncle,I don't know what he has done,but when I want to update it
to hboot-1.33.0013d/radio-2.22.28.25,I can't do it.When I connect it to my computer,it still worked,but when I flashed the recovery 1.7.0,the fastboot didn't react any more.When I checked the hboot in my G1,it showed me it is s-off,but I can't use the fastboot to update the device.Now,I'm still using the Android 1.6 rom and the 1.42.2000 spl and the 2.22.16.19 radio.And I can't receive help in any Chinese forum,so I post in xda-developers.What can I do?If person who helps me need more things about my G1,please ask me.
If someone can help me,THANK YOU VERY MUCH!
Click to expand...
Click to collapse
Hey bro, wazzup, I suggest that you flash the recovery via terminal emulator here's how you do it, copy first the recovery file on the root of your SDcard, not on any folders, alright, and rename it as recovery.img for you to easily remember it later. then open the terminal emulator(if you don't have it, download it on the market) type the following commands(one at a time, be careful on spelling and spaces)
first type SU and press enter key, after that you will see a "#" sign. now proceed to the next command
flash_image recovery /sdcard/recovery.img press the enter key, after that if you see again a "#" it means your good to go. exit the emulator and turn-off your phone and boot to recovery to check whether you change your recovery or not. I hope that it will help you, if not let me know and I'll find a way to help you out.
Click to expand...
Click to collapse

nico1228 said:
Hey bro, wazzup, I suggest that you flash the recovery via terminal emulator here's how you do it, copy first the recovery file on the root of your SDcard, not on any folders, alright, and rename it as recovery.img for you to easily remember it later. then open the terminal emulator(if you don't have it, download it on the market) type the following commands(one at a time, be careful on spelling and spaces)
Click to expand...
Click to collapse
i think there may be something wrong when it unlocked,because i have flashed it to 1.33.0013d successfully once,at that time i found it turned into s-on,but i can still flash the rom.last month,i want to use the android 1.6 again,so i flashed the dreaIMG.nbh,which includes the 1.42.2000spl,2.22.19.16radio and the official recovery and android1.1rom.then i wanted to flash the recovery,i found i couldn't do it.at last i tried to use a program for flashing phone(it is designed for the beginning flasher in China.)i don't know how it did but it really flashed a ClockworkMod recovery v2.5.0.7,and i flashed the 1.6rom on my phone successfully.but i still can't flash anything through the fastboot.i want to check the official unlock code but i failed whatever it was 1.33.0013d s-on or 1.42.2000 s-off.now my ram is too small to use the 2.3rom and my wifi can't work.recently,the condition of my device is getting worse and worse.i think it is caused by the unlock problem.what can i do?now i have a new idea,i can flash the .nbh file that is on the g1when it was sold out,it may make the g1 relock completely and then i use the official unlock,can't i?if it doesn't work what can i do?there may be more clues for working out the problem which i forget to say,please ask me.i'm looking forward to receiving the helpful reply all the time,thank you.

demkantor said:
Search for orange.nbh
Flash this in bootloader than you will need to flash new recovery then radio then SPL in fastboot
Now boot to recovery and flash rom of choice
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
please read my new reply that will tell you more about my strange problem,thanks.(if my words are not polite,don't mind,i just know how to express my idea and i don't know how to express politely because i'm just a Chinese middle school student,i'm not very good at English.)

please tell me your settings
htc g1 said:
i think there may be something wrong when it unlocked,because i have flashed it to 1.33.0013d successfully once,at that time i found it turned into s-on,but i can still flash the rom.last month,i want to use the android 1.6 again,so i flashed the dreaIMG.nbh,which includes the 1.42.2000spl,2.22.19.16radio and the official recovery and android1.1rom.then i wanted to flash the recovery,i found i couldn't do it.at last i tried to use a program for flashing phone(it is designed for the beginning flasher in China.)i don't know how it did but it really flashed a ClockworkMod recovery v2.5.0.7,and i flashed the 1.6rom on my phone successfully.but i still can't flash anything through the fastboot.i want to check the official unlock code but i failed whatever it was 1.33.0013d s-on or 1.42.2000 s-off.now my ram is too small to use the 2.3rom and my wifi can't work.recently,the condition of my device is getting worse and worse.i think it is caused by the unlock problem.what can i do?now i have a new idea,i can flash the .nbh file that is on the g1when it was sold out,it may make the g1 relock completely and then i use the official unlock,can't i?if it doesn't work what can i do?there may be more clues for working out the problem which i forget to say,please ask me.i'm looking forward to receiving the helpful reply all the time,thank you.
Click to expand...
Click to collapse
hey bro, basically t-mobile G1 is only sold in the country with of course T-mobile carriers, so I don't think that it is available on china, I guess that your phone is ported with unlocked bootloader already just like mine because we don't have t-mobile carrier here in my country, it is much better for you to know if where thus that phone came from is it from the U.S.A or U.K after then you can flash the appropriate DREAIMG.nbh file. It will downgrade your G1 to android 1.0 but your phone are still unlocked just like mine, but from there you can then start all over again rooting your G1 and flash the files you want, but if you want I can give you links on where you can download those files. Just tell me if you want it.

Both of you two need to flash the orange.nbh to your phones through bootloader (just like the dreaimg.nbh)
The .13d will not allow for most fastboot commands as radio flags are still present, the orange.nbh will give you a compatible radio and engineering SPL that will allow for all fastboot flashing as it is s-off (although not true radio s-off)
Once you flash this you will need to go to bootloader and flash a new recovery via fastboot and then ROM of choice
And if you guys want to move to the .13d SPL again let me know and I'll help

demkantor said:
Both of you two need to flash the orange.nbh to your phones through bootloader (just like the dreaimg.nbh)
The .13d will not allow for most fastboot commands as radio flags are still present, the orange.nbh will give you a compatible radio and engineering SPL that will allow for all fastboot flashing as it is s-off (although not true radio s-off)
Once you flash this you will need to go to bootloader and flash a new recovery via fastboot and then ROM of choice
And if you guys want to move to the .13d SPL again let me know and I'll help
Click to expand...
Click to collapse
I can't flash recovery via fastboot now and I must know that if I flash the orange.nbh whether I can flash the recovery via fastboot.Now,my information of my device isREAM PVT 32B ENG S-OFF HBOOT-1.42.2000 CPID-4 RADIO-2.22.16.19,RECOVERY-ClockworkMod(It was flashed by one of the flashing programs in China),Android 1.6.And what the orange.nbh include?If I flash it ,can I use the fastboot normally?By the way,I sometimes can't charge unless I take the battery out of the phone(I can't express my idea more directly),is there something wrong with my battery?Please answer me,thank you very much.

orange.nbh - check md5sums this will change bootloader to one that will allow for fastboot commands
as for the battery i cant say for sure what your issue is, it is hard to diagnose hardware problems over the internet

demkantor said:
this will change bootloader to one that will allow for fastboot commands
as for the battery i cant say for sure what your issue is, it is hard to diagnose hardware problems over the internet
Click to expand...
Click to collapse
I have solved the problem by myself,but I still thank you.And now I have a new problem,that is my wi-fi can't work normally.When I start the wifi at the first time I flashed the 1.33.0013d and the android 2.3.5,it worked normally for a while---just a while.About 2 minutes later,my device restarted automatically.And then I could restart the wifi again,but it would restart soon.So I think that there aren't any problems with my wifi hardware.But what can I do?You can imagine what is like if an android phone can't connect the wifi.And now in the hboot mode,it shows that DREAM PVT 32B SHIP S-ON,but I can install any roms.And I can't unlock it by official unlocking.If I enter the command of official unlocking,the fastboot shows that [INFO] Command Error!!!.What causes the problem?Please continue helping me.Thank you.

Well you don't want to unlock it you want to flash the orange.nbh, but do what you please
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
Well you don't want to unlock it you want to flash the orange.nbh, but do what you please
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
what do you mean?I'm a Chinese and I'm not very good at English so please tell me more clearly,thanks and I found that the orange.nbh is the same as the dreaimg.nbh.now I just want to fix up my wifi,what should I do?

Write down ever word from bootloader screen here just as its laid out
Sent from my Nexus 4 using XDA Premium 4 mobile app