Database Develop

1.33.0009 on rogers. Can I not root?

The tutorial is for 1.33.00010 but I have 09: http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Rogers_Dream_EBI1_to_CyanogenMod
Am I stuck?

did you try?

bengrulz said:
did you try?
Click to expand...
Click to collapse
If I try and flash an SPL I don't think will work then my device will be bricked.

"In order to replace the SPL on your phone and install CyanogenMod on the system, you will need a customized recovery utility. Ordinarily, fastboot would be the easiest means of installing the utility but Rogers is now distributing phones with v1.33.0010 and higher SPL versions (aka: "Perfect" SPL) which prevent fastboot from flashing image"
it seems to me that youd be okay.
also in the future this is not the correct section for these sorts of questions

bengrulz said:
"In order to replace the SPL on your phone and install CyanogenMod on the system, you will need a customized recovery utility. Ordinarily, fastboot would be the easiest means of installing the utility but Rogers is now distributing phones with v1.33.0010 and higher SPL versions (aka: "Perfect" SPL) which prevent fastboot from flashing image"
it seems to me that youd be okay.
also in the future this is not the correct section for these sorts of questions
Click to expand...
Click to collapse
Apologies, I'm not sure what I'm supposed to do now as to how to root my phone, and if it's going to break because of this

my phone had that for hboot too and i followed that same tutorial and now my phone is bricked. could this be why?

I started with the same SPL as you and just rooted my phone today by following that guide.
That being said, I had to deviate from the guide in order to install an SPL.
The guide tells you to use flashrec from google code, but that older version didn't work on my phone. Write down the URL the old one tries to use, then use it with a new one from here:
http://zenthought.org/content/project/flashrec
And all should work out just fine.

Help needed to downgrade ADP1 1.6!! (Tried many methods that are available)

I need help to downgrade ADP1 1.6!!!
My phone is Singtel HTC Dream
I wanted to flash to Cyanogen mod but accidentally booted with Android 1.6 recovery img.
I've tried using RC29 & RC7 to downgrade but it says "installation aborted".
I also tried using DREAIMG.nbh with bootloader but it says "not allow".
Details...
Model Number : Android Dev Phone 1
Firmware version : 1.6
Baseband version : 62.50S.20.17H_2.22.19.26I
Kernel version : 2.6.29-00479-g3c7df37
[email protected] #19
Build number : dream_devphone-userdebug 1.6 DRC83 14721 test-keys
Thanks!!
I've been stuck with ADP1 1.6 for ages. Thanks a bunch for ANYONE who could help me!!! ><
I've tried searching for methods to solve my problem but all that i've found didn't work.

What SPL do you have installed?
Note: if you have an adp1 build installed, then you HAVE ROOT, so no need to downgrade.

a copule of months ago, i accidentally flashed a stock image on my rooted phone. After that, i also got the "not allow" message when i tried to flash cyanogens rom.
What i had to do in the end was to manufacture a "gold card" (search this forum). You need to download a SW, find the cid of your phone, reverse this string (using the SW) and add a new bootsector of your micro-sd card and use that to boot and flash.
Kind regards
Daniel

I'm a noob at all of these... ><
I do not have root cause i lost it after flashing it to ADP1 1.6.
Thanks Daniel (my05)
But what is SW?
To "reverse this string (using the SW)", is the instructions at the thread of "manufacture a "gold card""?
And to "add a new bootsector of your micro-sd card" is the instructions at that thread too?
If its possible, could you possibly send me the link to that thread or tell me the instructions?
Thanks a bunch!! (waiting for a savior)

As I just said, if you have ADP1.6 on it, then you DEFINITELY HAVE ROOT. Unless for whatever reason, you went OUT OF YOUR WAY to delete the 'su' command.
I can assure you, all ADP1 factory images come with root.
ADP2 factory images do not come with root (but at least the devices come with engineering bootloader, which is just as good).
adb shell
$ su
#
etc.
I GUARANTEE that unless you went out of your way to screw it up, if you still have the ADP1 system image on your phone, then you HAVE ROOT.
DO NOT waste your time with goldcards -- you can screw up your phone with those.
Now please answer the question: WHAT BOOTLOADER do you have installed?

Are you sure i still have root?
I tried using applications that uses root but they don't work.
I've lost my nandroid bootloader and i am now using the normal bootloader from ADP1 1.6.
Thanks for the info anyway

It has to be the SHELL user to use the su command, ie, ADB.
It is impossible for any "app" to get root access since that it a hideously disgusting security vulnerability!!!! If an app can get root access, it means that that app can TAKE OVER YOUR PHONE! You don't want that, so it is secured against that. Does NOT mean that YOU can't get root IN THE WAY IT IS DESIGNED!
adb shell
su
#

nootish said:
I've lost my nandroid bootloader and i am now using the normal bootloader from ADP1 1.6.
Click to expand...
Click to collapse
nandroid is not a bootloader. Nandroid is a PROGRAM.
A program runs on an operating system.
The operating system is loaded by a bootloader.
WHAT BOOTLOADER DO YOU HAVE?
Thanks for the info anyway
Click to expand...
Click to collapse
Don't be rolling your eyes at me. If you want help with this, you be polite.

lbcoder said:
Don't be rolling your eyes at me. If you want help with this, you be polite.
Click to expand...
Click to collapse
I don't even see why you're still bothering to try. This entire thread was "fail" from the start.

My bootloader is the Original G1 bootloader.
DREA110 PVT 3VB
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.26I
Sep 2 2008
Serial0
Sorry to have offended you...
Didn't know what that smiley really meant...

nootish said:
My bootloader is the Original G1 bootloader.
DREA110 PVT 3VB
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.26I
Sep 2 2008
Serial0
Sorry to have offended you...
Didn't know what that smiley really meant...
Click to expand...
Click to collapse
Ok, no problem.
Start by upgrading the SPL to the engineering SPL... 0.95.3000.
http://forum.xda-developers.com/showthread.php?t=455860
You can also find a modified recovery image and install that.
Once the SPL is installed, you will have fastboot available. Which means that you can do anything you like whenever you like. DO NOT EVER mess with any NBH files after this!!! And I mean *EVER*.

lbcoder said:
Ok, no problem.
Start by upgrading the SPL to the engineering SPL... 0.95.3000.
http://forum.xda-developers.com/showthread.php?t=455860
You can also find a modified recovery image and install that.
Once the SPL is installed, you will have fastboot available. Which means that you can do anything you like whenever you like. DO NOT EVER mess with any NBH files after this!!! And I mean *EVER*.
Click to expand...
Click to collapse
I need help too!
I've accidentally flash the NBH file, and now the device can only boot into a SPL mode when you turn on, is there any way to fix this?
(Recovery mode only shows the icon, nothing else)
Many thanks!

astate said:
I need help too!
I've accidentally flash the NBH file, and now the device can only boot into a SPL mode when you turn on, is there any way to fix this?
(Recovery mode only shows the icon, nothing else)
Many thanks!
Click to expand...
Click to collapse
This is not your thread.
Start your own.

Omg!
Thanks for the solution!
I'll try it tonight!

I've tried to upgrade the SPL to the engineering SPL but it doesn't work.
Here is what it says:
E:Can't open /cache/recovery/command
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Installation aborted.
When i tried to install it again, it just repeats the same thing over and over again.
Do you still have any other solutions?

What you need might be here:
http://wiki.cyanogenmod.com/index.php/RE-recovery-img
Although it would still be a good idea to get yourself an engineering SPL.
You can do that after you have followed the Wiki procedure to flash the custom recovery back.

Thanks for the link!!
I've tried using the steps but i'm stuck at this part...
Restoring the custom recovery image --> adb root
This is what i did:
C:\Users\Android_Fish> cd C:\android-sdk-windows\tools
C:\android-sdk-windows\tools> adb shell
$ adb root
adb root
adb: permission denied
$ su
su
# adb root
adb: not found
I've tried the "su" method to get the "#" icon to get it right.
But it still doesn't work!
I'm still really inexperienced in this.
So i hope there would be anyone who could help me

Anyone can help???
Really...
Anyone???

how do i go back to frf91 from frg33?

I flashed 33 and my phone is stock. I need paid apps plus this build is bugging out on me alot. Stuff freezes, its just a bad build. How do I undo this without rooting?

Pretty sure you have to root.

If its like FRF91. Then it wont let you downgrade because it sees FRF91 as an "old version."

Download ere27 as passimg.zip. place in your sdcard root. Boot into recovery. Restore. Let it do its work. Put frf91 into sd card. Boot into recovery and load from zip. Ta da. You are on Frf 91
Sent from my Nexus One using Tapatalk

Or, if you want a shorter and more correct route:
Nexus One Wiki, "Restore", PASSIMG.ZIP method, use FRF91 complete stock image found in one of the threads in Q&A from the last day (or Google).
Don't use FRF91 update, since it's only an update - it's not a complete image.

whatever. Just use a passimg.zip to clean out all the crap. its basically the "do-over" method. Think etch-a-sketch flip and shake.

i tried passimg from http://forum.xda-developers.com/showthread.php?t=717870
it said failure because it was an older version. If i find that ere one will it let me do it? i dont mind going way back and working my way back to froyo, but i dont think i can passimg anything since its considered "older"

search the forum for how to downgrade your hboot- it exists just search for the thread

http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=726258

androidjedi said:
http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=726258
Click to expand...
Click to collapse
Thank you. Looks like ill have to root for it which im sure ill find if i search how to root 33 so ill wait for a while to see if something else comes up but at least I know there's a way

There is no other way but to root.
Since you're erasing the system you're rooting anyway, why do you care?
The full guide is now in the Wiki, including reverting HBOOT for those that need it.

Jack_R1 said:
There is no other way but to root.
Since you're erasing the system you're rooting anyway, why do you care?
The full guide is now in the Wiki, including reverting HBOOT for those that need it.
Click to expand...
Click to collapse
i dont know, i did 1 click root a few times but every rom i tried- cyan, eno, modac, whatever were great but there was always some bug or something that was annoying enough that i just wanted stock instead. So i dont know how much i like the idea of permanent root, but theres probably a stock rom i can use so its not the end of the world. SDK/Terminal i did all that crap with my g1, personally i found it to be more of a hassle than it was worth. But not having protected apps is not going to cut it so ill cave soon im sure

Again, maybe this time it'll be understood:
There is no "permanent root". The only "permanent" thing is unlocking the bootloader, which you don't have to do - the guide doesn't require it. The system you root will be erased in the PASSIMG method and replaced with a completely stock system of your choice. So, what's exactly stopping you from rooting?

Jack_R1 said:
Again, maybe this time it'll be understood:
There is no "permanent root". The only "permanent" thing is unlocking the bootloader, which you don't have to do - the guide doesn't require it. The system you root will be erased in the PASSIMG method and replaced with a completely stock system of your choice. So, what's exactly stopping you from rooting?
Click to expand...
Click to collapse
the only way to go back from FRG33 is to unlock the bootloader at this stage, the PASSIMG method does not work

When you revert HBOOT, it should work fine. Just the same as it works with Korean FRF91 version, which also has a new HBOOT. People in the FRG33 thread don't know it?

Why people can't understand?At this moment,if you've flashed stock FRG33 rom,using PASSIMG method,you can't root anymore!The only method to roll back to FRF91 is to unlock your bootloader,which is permanent and can't be un-done!
Cheers

Did you see that?
http://androidforums.com/1533396-post14.html
Or is it the only report? (in that case, the guy probably didn't try to run root).
Anyway, being unable to root makes you unable to flash PASSIMG of anything with bootloader lower than 0.35 - but did anyone try PASSIMG with Korean FRF91? It has the same HBOOT as FRG33, so it shouldn't be reported "older".

Jack_R1 said:
When you revert HBOOT, it should work fine. Just the same as it works with Korean FRF91 version, which also has a new HBOOT. People in the FRG33 thread don't know it?
Click to expand...
Click to collapse
Code:
[HOW-TO] Revert HBOOT 0.35.0017 to 0.33.0012
I CAN'T RELOCK THE BOOTLOADER!!!
This only reverts your SPL/HBOOT back to 0.33.0012 after you've installed the Korean FRF91 files and ended up stuck with 0.35.0017 SPL.
Thanks to the guys in the Desire forums and help from the Nexus Q&A, I have reverted my phone to the original HBOOT so I can apply custom roms again.
First you need to root the Korean FRF91 that's on your phone using Paul's instructions for superboot FRF83.
If you are rooted already, skip this step.
http://android.modaco.com/content/go...the-nexus-one/
Code:
How to use Superboot - Windows, Linux and OSX
- Download the Superboot zip file above and extract to a directory
- Put your device in bootloader mode - Turn off the phone then press and hold the trackball to enter the bootloader
- WINDOWS - double click 'install-superboot-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-mac.sh' followed by './install-superboot-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-linux.sh' followed by './install-superboot-linux.sh'
Note: If you are using a retail Nexus One, you may need to unlock the bootloader first, as detailed here.

Ok, let's make some order:
1) PASSIMG can flash versions with the same or higher HBOOT version - to check: will the same version flash? I believe so.
The official FRF91 has HBOOT 0.33.0012, the Korean FRF91 has 0.35.0017, and I suppose the FRG33 also has 0.35.0017 - correct?
2) Rooting isn't possible on FRG33 yet. 1 report doesn't count.
So, looking at this:
Using PASSIMG with the Korean FRF91 (complete with HBOOT 0.35.0017) will work over FRG33, if the HBOOT is indeed the same version.
Korean FRF91 is rootable.
Rooting Korean FRF91 allows to downgrade HBOOT, which in order allows to use PASSIMG method to flash official FRF91 with older HBOOT.
So, did anyone try PASSIMG with Korean FRF91?

Jack_R1 said:
Did you see that?
http://androidforums.com/1533396-post14.html
Or is it the only report? (in that case, the guy probably didn't try to run root).
Anyway, being unable to root makes you unable to flash PASSIMG of anything with bootloader lower than 0.35 - but did anyone try PASSIMG with Korean FRF91? It has the same HBOOT as FRG33, so it shouldn't be reported "older".
Click to expand...
Click to collapse
Downloading and testing, thanks for the tip, will report back.

flash recovery: signature verify fail

I am trying to install Amon_RA recovery on my N1.
I followed the instructions from the Full Update Guide (wiki.cyanogenmod) and from XDA (recovery RA-passion-v2.2.1 by Amon-RA who does an outstanding dev).
Checked md5sum of recovery-RA-passion-v2.2.1.img : matched
Checked md5sum of recovery-RA-passion-v2.2.1-CM.img: matched
The phone is unlocked. I use fastboot to flash the recovery. I get “Signature verify fail”.
I made a thorough search and I did not find an explanation and an answer other than for rooted phone.
I do not want to root.
I tried disabling the anti virus program. I reset the phone. I checked the installation of SDK. I checked the Environment Variables in “Advanced settings” on Widows Vista and Win7. I even checked my sanity.
I would appreciate any guidance to solve this issue.
Nexus One unlocked
S-ON HBOOT-0.35.0017 RADIO-5.08.00.04
GB 2.3.6 Kernel 2.6.35.7-59465-g42bad32 Build # GRK39F
Device recognised under ADB and Fastboot. Recovery put in android-sdk-windows/platform-tools.

hi, sorry if my english isn't perfect, but i want to try to help u.
If with the command fastboot devices you get a report the fastboot.jpg in attachments you'r ok.
Unlock the bootloader, command prompt do this: fastboot oem unlock
and accept the question on the mobile phone.
now you have phone unloocked so no free assistance if you broke.
Procede to next step, flash the recovery download rar from attachments and then in the fastboot do this: fastboot flash recovery recovery-RA-passion-v2.2.1.img if you get problem repost.
teh in the bootloader go to bootloader (power button) and then recovery (power button) phone will reboot in recovery mode.
If you have problem post another time and forgive my bad english =)

gunner1937 said:
I am trying to install Amon_RA recovery on my N1.
I followed the instructions from the Full Update Guide (wiki.cyanogenmod) and from XDA (recovery RA-passion-v2.2.1 by Amon-RA who does an outstanding dev).
Checked md5sum of recovery-RA-passion-v2.2.1.img : matched
Checked md5sum of recovery-RA-passion-v2.2.1-CM.img: matched
The phone is unlocked. I use fastboot to flash the recovery. I get “Signature verify fail”.
I made a thorough search and I did not find an explanation and an answer other than for rooted phone.
I do not want to root.
I tried disabling the anti virus program. I reset the phone. I checked the installation of SDK. I checked the Environment Variables in “Advanced settings” on Widows Vista and Win7. I even checked my sanity.
I would appreciate any guidance to solve this issue.
Nexus One unlocked
S-ON HBOOT-0.35.0017 RADIO-5.08.00.04
GB 2.3.6 Kernel 2.6.35.7-59465-g42bad32 Build # GRK39F
Device recognised under ADB and Fastboot. Recovery put in android-sdk-windows/platform-tools.
Click to expand...
Click to collapse
You said "I do not want root" so why do you want to install custom recovery? The purpose of installing custom ROM or recovery is to gain root access but you don't want to root your phone so don't flash custom ROM or recovery. And you should post in Q&A not both places.

Molto grazie.Your English is far better than my Italian.
As I said the phone is unlocked and, yes, I get fastboot (if not I could not go to the point where I am, I believe)
Forza italia ma nontroppo against Russia

Yes, you're right, but i'm agree with Taodan, why you should have to flash recovery if you don't want root ? it isn't very useful XD maybe you want root in order to backup a stock rom, but if you want a stock rom of android 2.3.4 i can upload one for you XD anbd thanks for say my engolish isn't bad and yes Forza Italia XD but I want to get live in the UK or USA !!!

taodan said:
You said "I do not want root" so why do you want to install custom recovery? The purpose of installing custom ROM or recovery is to gain root access but you don't want to root your phone so don't flash custom ROM or recovery. And you should post in Q&A not both places.
Click to expand...
Click to collapse
I owe you an apology for not knowing that I have to justify the purpose of my question.
I was naive enough to consider that flashing a recovery was obviously to help install a Cyanogen ROM. My naivete even brought me to believe that installing a Recovery without flashing a ROM will bring me back to the stock recovery.
Going further I should have added "for the moment" to my decision of not rooting.
And my final answer, regarding the wrong thread, is that I tried to edit my post in order to move to the right thread when I discovered my mistake.
Thank you for your reply. It will help me re-check my sanity.
That said are you ready to offer me a solution which could be posted on the other thread?

Ivan93tm said:
Yes, you're right, but i'm agree with Taodan, why you should have to flash recovery if you don't want root ? it isn't very useful XD maybe you want root in order to backup a stock rom, but if you want a stock rom of android 2.3.4 i can upload one for you XD anbd thanks for say my engolish isn't bad and yes Forza Italia XD but I want to get live in the UK or USA !!!
Click to expand...
Click to collapse
My main concern is not to root or not to root.
Re-read my post and you will discover that my question specifically asks for a solution regarding a flash recovery.
Anyway, I do appreciate your contribution. Prego

this belong to help Q&A thread not dev thread...

P00r said:
this belong to help Q&A thread not dev thread...
Click to expand...
Click to collapse
Please, read Post# 6 and the last sentence of the 1st paragraph. It should make you happy

[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