Database Develop

[HELP] Revert to 0.33.0012 SPL

Hi all,
I foolishly flashed the Korean FRF91 onto my N1 and now I have SPL 0.35.0017 instead of the normal 0.33.0012 version.
To downgrade, I have tried:
- repacking the 0.33.0012 HBOOT into an update.zip (Looks like it worked, but it didn't)
- Flashing 0.33.0012 through FASTBOOT (Verification failed)
- Applying an older Google update (Main version is older)
Any ideas?
Thanks!

http://android.modaco.com/content/htc-desire-desire-modaco-com/310970/how-to-downgrade-hboot/

OK, I think that worked...
But now my N1 has an HTC logo on the screen for FASTBOOT.

can you explain how do you have made .
i don't understand the tutorial. (i m french :s)
if you can link the file you have apply.
thank's

cursordroid said:
OK, I think that worked...
But now my N1 has an HTC logo on the screen for FASTBOOT.
Click to expand...
Click to collapse
Probably because the link given by baseballkyle is in the "HTC Desire" section of the modaco forum, not nexus one.

Yes,
I would also appreciate an explanation on how you did it.
I tried it but it didn't work for me.
The hboot.img doesn't work. If I try a zip version it seems that the device accepts it and flash it but i keep having the wrong version installed.
Could you explain how you made the mtd0.img (with which numbers) and provide a link to the hboot version that worked for you?

PLs Help Also
Pls tell us also how u did it, thanks..

http://forum.xda-developers.com/showthread.php?t=726258
I have posted instructions here.

Great!!!
The key was applying the hboot file through the PASSIMG.ZIP and not just alone.
Fantastic.
Thanks a lot

nexus Hboot
What happen if I install the korean hboot. Because everybody is complaining about it. They want to return back to stock Hboot.

Though that hboot is newer currently all the signed firmwares (original ones, CM6, and whoever provide signed builds) check that the hboot version installed in the phone is 0.33.2012.
If you don't have that one then you will not be able to install any of this firmwares directly.
With some manual work you can make it happened but forget about OTA updates (stock OTA updates, CM-updater OTA updates, Rom Manager OTA updates).
If you don't care about that then you are fine.

help
i cant install any ota update can someone please help i went to erd 79 hoping that would fix everything

So what is the correct hboot version to use? I currently have 0.33.0012
Sent from my Nexus One using XDA App

[Q] update 2.3.4 help

hey guys,
i have a nexus one 2.3.3 when i try to update to 2.3.4
it says (ERROR status 7) in the bootloader. can anyone help?
thanks.

Have you done anything to the phone's original software? Custom kernel, rooting, custom recovery, etc?
The error 7 basically means that the signature checks don't match and it doesn't upgrade to prevent bricking your phone.

Yes. I rooted and used to have cm7
Does it matter?

If you are already rooted, just flash a rooted version of 2.3.4. It can be found here.
http://forum.xda-developers.com/showthread.php?t=1061648
And yes, when you root the phone, you change the signature of the install, so the upgrade fails. It makes sure the signature matches, otherwise you could end up with a broken phone. (If it didn't check for signatures, it could apply the partial update to a froyo or eclair version, and prevent the phone from booting.)
If you really want the OTA update, you would have to remove everything you did to root the phone and flash the update... and unless you unlocked the bootloader, there currently isn't a way to root 2.3.4.

bassmadrigal said:
If you are already rooted, just flash a rooted version of 2.3.4. It can be found here.
http://forum.xda-developers.com/showthread.php?t=1061648
Click to expand...
Click to collapse
You really should specify that the ROM you are pointing to is not a stock ROM, and any further OTA's will not install on that ROM.
bassmadrigal said:
And yes, when you root the phone, you change the signature of the install, so the upgrade fails.
Click to expand...
Click to collapse
NOT true at all. Rooting has no impact on whether you can receive and install OTA updates.
Here are the main things that will prevent an OTA from installing:
1) a custom kernel;
2) if you remove pre-installed applications from the /system partition
3) if you flash a de-odexed ROM (...that is why the ROM you linked to is not really a stock ROM.)
Rooting makes not difference at all.
bassmadrigal said:
If you really want the OTA update, you would have to remove everything you did to root the phone and flash the update...
Click to expand...
Click to collapse
NOPE.
If you have a stock ROM, all you have to do is make sure you have a stock kernel, and have all the pre-installed applications in your ROM. Nothing else.
If you have a de-odexed "stock" ROM, rooted or not, there is no way you can flash an OTA update (unless you de-odex it, repack it, and then flash it...)

I read on a number of sites that people were getting the Status 7 error due to them rooting and only rooting.
The first time I rooted my phone I put CyanogenMod on there, so I never had any experience with trying to get OTA updates.
But thanks for the info, I will store it and remember it for future reference.

bassmadrigal said:
I read on a number of sites that people were getting the Status 7 error due to them rooting and only rooting.
[snip]
Click to expand...
Click to collapse
I suspect it is because they "rooted" by flashing a "stock" ROM like the one to which you linked. Although it looks stock and, for the most part, behaves like a stock ROM, it is not, as it is de-odexed. If someone want to flash a stock Gingerbread ROM, they need to flash one like the first link in this thread: http://forum.xda-developers.com/showthread.php?t=968396
That ROM is not de-odexed. To get root, you just need to flash the superuser zip over top, and you have a rooted-but-otherwise-totally-stock ROM, which will receive and install all OTA updates.

Flash Fail

Good Morning
First please forgive my english if i make some mistakes...
Here is my problem :
i have a RAZR I, I flashed it into a new brazilian rom, , that worked perfectly.http://sbf.droid-developers.org/smi....0R_SCPNMINIIRETBRLA_P024_A031_CFC_fb.xml.zip
... but i cant root with motofailgo.... I tried severy times... then...
I want to back to older version and i give this error in fastboot during the flashing:
i had this failure message :
update gpt_main version failed
preflash validation failed for GPT
When i try to turn it off or on... it doesn't move...
Again I can flash only new version and work perfect...
any ideas to help me fix this !!!
Thanks for taking time to read me and help.!!! :crying:

Hello, if you read this forum, and search a little,you will found that:
-The latest rom are not rootable without unlock the bootloader (i imagine that you have not do it...)
-You could not downgrade a rom.
I imagine that your rom is one of the latest rom?
So if you wan t to root a latest rom, you have to unlock the bootloader and read the post. And you could not roll back to an oldest version.

Burn02 said:
Hello, if you read this forum, and search a little,you will found that:
-The latest rom are not rootable without unlock the bootloader (i imagine that you have not do it...)
-You could not downgrade a rom.
I imagine that your rom is one of the latest rom?
So if you wan t to root a latest rom, you have to unlock the bootloader and read the post. And you could not roll back to an oldest version.
Click to expand...
Click to collapse
Yep is the lastest. I cant back anymore?
I did it when I installing this rom during the flash:
" Unknown fastboot command. (getvar)" I give an error than I removed this line: <step operation="getvar" var="max-download-size" />.
and work perfect but i cant back for old rom. I need root by motofail. :crying: There any problem in future upgrades by OTA?
Thx...

Normally you could not downgrade. but you could flash any rom that are in the same version. So there is no reason that it would be a problem for a future ota update.
As i know and read on xda, there is no other possibility to root on the latest rom, to unlock the bootloader.

Can't Flash most ROM's

OK so,
The phone is rooted. It has relatively new firmware/radios and it has su installed with TWRP
Its a HTC One, Colour = Black, 32GB
UK Vodafone.
Was one of the first black ones that Vodafone rolled out as I had it on pre-order.
Now I've NEVER had a problem flashing CM, however I'm one of those people that loves flashing various ROMS and trying this and that.
I've got a pining for MIUI
If I get the file from here - http://en.miui.com/download-111.html
Or the one that used to be on the forums I get the same error message
*******************
Installing - (path here)
Checking for MD5
Skipping MD5
assert failed: getprop ("ro.product.device") ==
E:Error executing updater binary in zip
Failed
*******************
Its infuriating because I really want to try other ROMs and I spent time downloading them, moving them onto my phone only to find that they don't work.
I thought I had the M7UL but I'm not even sure anymore. I download the m7ul file from Cyanogenmod and it works fine
Can anyone help me?
***
Confirmed Working
***
http://forum.xda-developers.com/showthread.php?t=2279766 - Insert Coin - Installed fine, No issues

sometimes some recoveries doesn't work with some roms. Have you tried using clockwork mod or flashing the latest TWRP? Also if you phone is SOFF you can change your CID to all #1s. Once you do that you should be able to install any rom as long you follow the OP instructions.

vang2k said:
sometimes some recoveries doesn't work with some roms. Have you tried using clockwork mod or flashing the latest TWRP? Also if you phone is SOFF you can change your CID to all #1s. Once you do that you should be able to install any rom as long you follow the OP instructions.
Click to expand...
Click to collapse
Hi Vang.
Thanks for the update.
A while back I had issues with S-On / S - OFF.
I basically reverted the phone to stock, S-Off'd, changed the CIDS to all 1's and updated to the latest TWRP
That MIUI still wont work for me

Your best bet is to ask in the MIUI forums as they are not really supported here.
The error is saying that the rom file is not for your device. Also as it is a 4.2 rom it may not work well with the updates to the firmware in 4.4. To be honest I am not sure as I avoid MIUI like the plague.

[Q] Problem installing update

Hi today i got the 4.4.2 update and i tried to install it and it failed
My current situation is:
Tempered
Relocked
S-ON
Completely stock (I was rooted, xposed, sense 5 toolkit, htc hand font) by flashing firmware.zip and relocking the bootloader and i created (data/preload/apps) and put every app that comes with the same directory in the OTA and flashing htc stock font back and i've done a factory rest to make sure everything is stock :good:
every time i try to install the update i got ("/system/bin/app_process' has unexpected contents Installation aborted)
by the way my CID is HTC_044 and i'm on 707 region
Anybody have any idea to help please don't hesitate to share it

afmot said:
Hi today i got the 4.4.2 update and i tried to install it and it failed
My current situation is:
Tempered
Relocked
S-ON
Completely stock (I was rooted, xposed, sense 5 toolkit, htc hand font) by flashing firmware.zip and relocking the bootloader and i created (data/preload/apps) and put every app that comes with the same directory in the OTA and flashing htc stock font back and i've done a factory rest to make sure everything is stock :good:
every time i try to install the update i got ("/system/bin/app_process' has unexpected contents Installation aborted)
by the way my CID is HTC_044 and i'm on 707 region
Anybody have any idea to help please don't hesitate to share it
Click to expand...
Click to collapse
Looks like you're not stock after all.
You say you were using Xposed. Xposed replaces /system/bin/app_process with a patched version. By flashing firmware.zip you did not revert your system to stock, only your firmware, that is recovery, kernel, radio, hboot and other firmware partitions, but *not* /system. Which means you still have the Xposed version of app_process on your phone, as well as any other additional mods you installed.
To get to stock, you'll need to restore a backup of the stock system without any mods installed. Neither relocking the bootloader nor S-ON/S-OFF have any effect, you can apply official OTAs with both S-OFF and unlocked bootloader just fine. You don't need factory reset either, the contents of /data don't matter to the OTA at all. What you do need is a stock /system and stock recovery. Of those two requirements, you only fulfilled the second.
If you do not have a clean backup of the stock system, you can either hope that someone else has one and is willing to share it, or you can change your CID to either HTC_622 or a super CID and use the stock ROM I posted over here

All done
koniiiik said:
Looks like you're not stock after all.
You say you were using Xposed. Xposed replaces /system/bin/app_process with a patched version. By flashing firmware.zip you did not revert your system to stock, only your firmware, that is recovery, kernel, radio, hboot and other firmware partitions, but *not* /system. Which means you still have the Xposed version of app_process on your phone, as well as any other additional mods you installed.
To get to stock, you'll need to restore a backup of the stock system without any mods installed. Neither relocking the bootloader nor S-ON/S-OFF have any effect, you can apply official OTAs with both S-OFF and unlocked bootloader just fine. You don't need factory reset either, the contents of /data don't matter to the OTA at all. What you do need is a stock /system and stock recovery. Of those two requirements, you only fulfilled the second.
If you do not have a clean backup of the stock system, you can either hope that someone else has one and is willing to share it, or you can change your CID to either HTC_622 or a super CID and use the stock ROM I posted over here
Click to expand...
Click to collapse
Thank you it went well :victory::victory::victory::victory:
I replaced the app_process with the one from your nandroid backup and the update process was successful :laugh::laugh: