All the guides I've found thus far that have described how to root your phone and flash to a new ROM have required using a modified ROM. Is it possible to turn a G1 into a Dev Phone 1 without the use of a hacked ROM?
If I understand the guides correctly, you need to flash back to RC29 to gain a root console, then you need to replace your recovery partition with one that will take ROMs signed with different keys, then you need to replace the bootloader, and finally you neeed to flash from a modified ROM.
Would it be possible to instead replace the bootloader, recovery partition, and ROM with their stock Dev Phone counterparts, thus essentially turning my G1 into a stock Dev Phone 1? The Dev Phone 1 has root access enabled, so wouldn't I enjoy all the benefits of the hacked ROMs?
Sorry if this has been answered elsewhere, but the guides seem to focus on modified ROMs and a search revealed nothing.
You can downgrade and root, after that install official ADP 1.5 and eSPL but this doesn't really make sense, grab JF's Cupcake ADP 1.5, hSPL and you will have more fun.
The recovery system > original recovery, more options, real backup. So is hSPL > eSPL.
In this thread it says I have to replace the recovery partition with a modified one so that the phone will accept images that have been signed with different keys.
Will the recovery partition already on my phone accept ADP images, allowing me to skip this step and only deal with the SPL and an ADP image?
hSPL only gives you the ability to write non-matching NBH files. With eSPL or hSPL, you won't be using NBH files anyways, so this doesn't matter. Might as well use the stock eSPL. And yes, you can certainly write the ADP1 image once the eSPL is installed, or you can write any of the custom images... I wouldn't use the word "hacked", since those based on the official ADP1 1.5 image really aren't hacked, they're just customized. And of course, once the eSPL is written, you can switch between system images at will without any kind of crazy hacking procedure to do so -- that's what eSPL is made for.
Alright, let's take this a step further...
I am trying to identify the exact set of files that determine ADP1 vs. G1. I flashed the JF ADP1.5 and ADPCP2.0. The later was identifying itself on the phone as T-Mobile G1, despite the file name. I returned to JF, but used the boot from ADPCP2.0 and did manage to get a lot of the speed in it, as it is much faster. I still want the whole file system, though, but I need to be on an ADP version. Before you go on about su and root and stuff... I have it. But programs such as Spotter remain free if you are ADP branded. So the question is what do I need to keep to keep ADP?
Thats easy. The file that identifies to the OS if its a G1 or ADP1 is /system/build.prop. Note that you can customize this file however you wish.
The main *real* difference between the ADP1 and the G1 that gives the ADP1 infinitely more power than the G1 is the bootloader. With the engineering bootloader, you can do anything.
Related
Hi
similar to an other thread here if tried to change my SPL
and never recovered.
I can still get the blue led going using TrackBall + EndCall buttons.
The orange led lights up when I connect the usb cable.
But I cannot see it from the pc in any way (adb/fastboot).
there is some life in it but not a lot, have not seen the screen light
up at all.
Would it be possible to get a new bootloader/spl on it? Perhaps using
some kind of automatic update mechanism that is build in using an
update.zip file on the sd card?
Any help is more than welcome.
abe
*bump*
hmm, post needs al least 10 chars... should be enough now...
Has everyone also drawn a blank on this?
abe
Try downloading the ruu from your phone's official reseller.
T-Mobile USA standard OS.
Assuming that you backed up using Nandroid or something to SAVE and STORE your originally packaged Android 1.5 (Cupcake) version from T-Mobile...you NEED to restore that properly using a recovery image. Amon_RA has a great one, so does Cyanogen, obviously by now I'm sure you're aware. But keep in mind, to get back to that state...you must be careful not to alter any necessary files on that standard OS.
Do some Google searching and try to track down a Cupcake 1.5 download from one of those sites that leaked it or something. That's your best bet. Right now you don't need to be worried about continuing on from where you are. You need to backtrack and begin anew.
Sorry to hear that. I was thinking of installing Haykuro Apps to SD ROM and it needs to change the SPL. But I think not worth taking a risk.
Can you tell a little bit more which ROM were you planning to install?
Which SPL did you update to?
Which ROM did you have at the time of SPL update?
Which thread or instructions did you follow if any?
Hi
@mrjunix
I have a google ion, and therefore cannot return it unfortunately to the
carrier, as there was none. I went to the Google IO conference but
I am back in Europe and there is not support here.
btw what do you mean by RRU??
@Reignzone
I do have a nandroid backup but I cannot get back into recovery mode,
or fastboot mode or anything... the pc does not recognize it either.
@technicolor
I installed the Cyanogen recovery image and was able to install
one of his rom's. It worked fine but then I wanted to install
a Hero rom and I wanted to update the SPL.
Used the cyanogen recovery to update the spl using an update.zip
file. the phone restarted the "android" update screen came on
briefly and it never came back on...
changing the recovery rom should not be an issue,
and normally I think you do not need to flash your spl at all any more.
you can do a lot with the fastboot mode and one of the recovery roms
mentioned by Reignzone
abe
Reignzone said:
Assuming that you backed up using Nandroid or something to SAVE and STORE your originally packaged Android 1.5 (Cupcake) version from T-Mobile...you NEED to restore that properly using a recovery image. Amon_RA has a great one, so does Cyanogen, obviously by now I'm sure you're aware. But keep in mind, to get back to that state...you must be careful not to alter any necessary files on that standard OS.
Do some Google searching and try to track down a Cupcake 1.5 download from one of those sites that leaked it or something. That's your best bet. Right now you don't need to be worried about continuing on from where you are. You need to backtrack and begin anew.
Click to expand...
Click to collapse
This is the same advise you gave me yesterday on my bricked MT3G, but if you can't enter recovery mode, a nandroid backup ain't gonna help much, is it?
Also, any cupcake downloads are not going to help either, if you can't fastboot or enter recovery.
I appreciate you trying to help, but if you pay attention to the OP (and my own post), you'll see that your advise isn't going to solve anything.
For starters:
My advice to have those of you who are in need to take an approach that allows you to backtrack you work. Perhaps you left out various details of your issue or process taken in order to end up where you're at.
Your bitterness isn't appreciated for my having misread the problem.
YOU are the one with the F***** device, not me.
Anyway, all that aside; you might try to read-up on various threads that could be of some help. Google search, HTC support, ADB, etc.
There's always something to be done.
Good luck.
abeman said:
Hi
@mrjunix
I have a google ion, and therefore cannot return it unfortunately to the
carrier, as there was none. I went to the Google IO conference but
I am back in Europe and there is not support here.
btw what do you mean by RRU??
Click to expand...
Click to collapse
forum puffering aside, RUU is ROM Upgrade Utility
Prepackaged programs that bypass the phone's software altogether to reflash the rom
My carrier is Rogers of Canada and I have their "HTC Magic" phone
Be warned that Rogers is intentionally altering their hboot to disable system changes, you may not be able to cook your os after using this rom update.
Their updates page
https://your.rogers.com/web_auth/techsupport.asp
has the update
http://downloads.rogers.com/wireless/products/htc/magic/RUU_Sapphire_Rogers_WWE_2.17.631.2_release_signed_NoDriver.exe
Hi, I've recently bought a HTC Magic and since then I've been reading into how to root my phone. Before I start I would like to know if it's possible on my phone.
Details:
HTC Magic Vodafone Uk (32B)
Hboot: 1.33.0007
Firmware version: 1.5
Build: CRC24
I've read from a thread in another section of this forum
that it would be impossible because of 1.33.0007 being a perfect spl BUT my phone is running the firmware version 1.5, with a CRC24 build. Would this mean I will be able to root my phone or not?
Also I've been reading up on how you either have cupcake or donut. My version is 1.5 so would that mean I have cupcake?
I'm worried that I might brick my phone so would prefer to use the one click tutorial at theunlockr (would add link but I can't) which is for htc magic running on cupcake.
Would it work?
Sorry for all my questions and I probably will end up asking more
Thanks if anyone can answer these for me!
You should be able to root using the relentless rooter or by following the guide on the unlockr. You are lucky you are running cupcake and don't need to downgrade
I think you are only really at risk when you flash radio and spl. Using the unlockr's stuff shouldn't be too bad. But read eveerything a bajillion times incase
same boat
Hey bunnybag
Was in the same boat as you until yesterday.
Also had a perfect SPL (0010) on a 32A.
I was also reading up a lot wrt getting a new ROM on my phone, and was also afraid of bricking it...
The gold-card method seemed quite involved, and that QMAT application doesn't exist anymore, and the newer version of it, does not run in XP or Vista...
Yesterday, I used the one click method from theunlockr, and after a few mistakes, it worked! Now I have a shiny CyanogenMod running with a 1.6 donut
It seems with the one click method -that you do not need to change the radio or SPL (which I guess are the most dangerous flashes to attempt)
Quicky summary of what I did, and where I deviated:
1) Read the one click method from theunlocker, and some of the comments at the bottom. Also - very importantly - watch the YouTube video at the top of the one click method page a few times!!
2) Downloaded the FlashRec apk (follow link on the one click method's page)
3) Installed FlashRec (the latest version of FlashRec looks slightly different to the one in the YouTube video but functions the same)
4) Did a backup of the existing recovery image via FlashRec. After the backup, you can copy the backed up .img to your PC...
5) Copied the latest Amon RA recovery image (v1.5.2) onto the SD card. Make sure you get the right one... there is a different one for 32A/32B... [Deviation from the one click method- which uses an older version of the RA recovery image]
6) Attempted to flash the new RA recovery via FlashRec. Here is where I struck a problem - the thing just stalled - for a good 10mins - and said 'do not interrupt' :|
I hooked up the USB cable, and from the command prompt ran: adb catlog
From here, scrolling up, I could see that FlashRec gave some message of invalid recovery image... Bit of a bummer - I checked the CRCs of the recovery image after copying it to the SD, and also tripple-checked the filename I typed into FlashRec! In the one click method page, they also warn about inadvertently adding spaces to the end of the filename when you type it in. I also checked for that.
I attempted it once more as follows:
-Rebooted phone
-Deleted the RA recovery .img from the SD
-Re-copied it onto the SD, and this time renamed it to something easy: ra.img
-Checked the CRC
-Ran FlashRec, and specified the path as: sdcard/ra.img
-Flash succeeded! maybe FlashRec can't handle very long file names?
7) After the recovery was flashed, I booted into recovery mode (HOME & POWER). Seems like the Amon RA recovery image takes slightly longer to boot that the stock recovery... so - don't crap yourself if it takes a few seconds. This is also a good point to stop, and watch the second video from theunclockr on how to load a new ROM...
8) After verifying that the new recovery image was working I booted back into Android, and I copied my ROM's files onto the SD. I used the Cyanogen Mod. The Cyanogen wiki has a page on how to load it for a 32A and also 32B.
Basically, you need the latest stable cyanogen mod, an Android 1.6 "defanged" ROM (link available on the Cyanogen wiki), and a new kernel. The kernel is 32A/32B specific, so get the right one.
9) With the 3 files on the SD, I booted back into the new RA recovery I just flashed.
10) Did a Nandroid backup
11) Did a wipe/factory reset [Deviation from theunlockr method: I did not format my SD card, or partition it into Ext & Swap. I prefer not to have a Swap partition on the SD, nor do I think I'll need to swap any apps out to the SD card... I think the 32A has enough space... you can read further about it in the xda-developers wiki, under page: HTC_Sapphire_Hacking_2]
12) Still in RA recovery, I applied (in order) a) the defanged 1.6 ROM, b) the Cyanogen mod, c) the new 32A kernel
13) Flashing it takes a while - there is a progress bar...
14) Reboot after all 3 were flashed. The first reboot takes a looong time... couple of minutes... don't worry, or try to reboot again... just give it time.
15) Once inside - tested everything: GPS, Wifi, Phone, Market, G-sensor, Gtalk, Gmail.
16) It might be worth while to note that once the phone is booted, and you've entered your SIM PIN, and the Android desktop is displayed, it can still take a few seconds - 4 or 5 I guess, before you are able to interact (swipe desktop left/right). Give it time to settle down, and all is well
//TODO: still need to flash a new splash-image...
Good luck - post back here with your results!
How to root Magic (32A) with Europe ROM ROM Version:3.05.401.3 with Sense?
Have somebody any idea, how to root Magic (32A) with Europe ROM Version:3.05.401.3 with Sense? Thanks!
bogo_mips said:
Hey bunnybag
-Re-copied it onto the SD, and this time renamed it to something easy: ra.img
-Checked the CRC
-Ran FlashRec, and specified the path as: sdcard/ra.img
Good luck - post back here with your results!
Click to expand...
Click to collapse
Ah, I tried using the unlockr's method and failed at flashrec. The unlockr kept saying that the reason was because I was already on Donuts but that is not true. I ended up using the relentless rooter software (looking back, his method is basically an automation of the original method).
Maybe you should post this also in the unlockr so that people who have "backup failed" messages know what to do?
Thanks for the info. It will be very helpful for other members trying to use the unlockr method.
Thanks for the post guys.
@bogo_mips: Great advice and I'll more than likely use this along with the unlockr one click tutorial.
Oh and there's one thing I'm worried about. My phone has somehow automatically downloaded the 1.6 upgrade and it keeps asking me to install it. Anyone know of a way to delete it so that it won't upgrade?
I'm worried that it might install if I turn my phone off.
@bunnybag: that 1.6 download sounds like a problem... if it takes, you'll no longer be able to do to the one-click method...
Check around the forum for advice. I'd guess - since the download would have had to happen in user-space, that the downloaded file might be sitting on the SD card or possibly the phone's flash. Get that Linda Filemanager app from the market and poke around... I guess if you could find the file, and delete / rename it - you could avert an install?
Alternativley, I'm guessing that if you can attempt the one-click method, that you'll have a new recovery image before you power down your phone, so - I think that will keep you safe...
@visitador02: according to the FlashRec page, there are 1.5 cupcakes out there which have been patched, so - FlashRec can't work on them... maybe that is what happened to you...
Hi all,
I just updated my Magic (Hutchison/3, Australia) (32A) to the latest official HTC firmware with sense ui (I had cyanogen on there before but it was too buggy for my liking). However, it seems that this firmware has the "perfect" spl (HBOOT-1.76.0008, Radio 6.35.08.29). I was planning to root the phone without flashing a different rom but i of course need write access to /system. My plan was to boot amon-ra's recovery to do this, however when i try and boot it with "fastboot boot recovery-RA-sapphire-v1.6.2H.img", i get told "FAILED (remote: not allow)" (same deal for the hero version).
My idea is to download an old sappimg.nbh and start up the SPL on the phone, which displays some messages about looking for that file when it starts up. I assume this will flash an older SPL; then, i install the system part of the new ROM but not the radio/SPL somehow (is this possible?) then follow my initial plan for rooting the phone
However, from what i've read it seems messing with the SPL is pretty much the only way to brick the phone. Is what i suggest safe/will it work?
Thanks guys
greeklegend said:
Hi all,
I just updated my Magic (Hutchison/3, Australia) (32A) to the latest official HTC firmware with sense ui (I had cyanogen on there before but it was too buggy for my liking). However, it seems that this firmware has the "perfect" spl (HBOOT-1.76.0008, Radio 6.35.08.29). I was planning to root the phone without flashing a different rom but i of course need write access to /system. My plan was to boot amon-ra's recovery to do this, however when i try and boot it with "fastboot boot recovery-RA-sapphire-v1.6.2H.img", i get told "FAILED (remote: not allow)" (same deal for the hero version).
My idea is to download an old sappimg.nbh and start up the SPL on the phone, which displays some messages about looking for that file when it starts up. I assume this will flash an older SPL; then, i install the system part of the new ROM but not the radio/SPL somehow (is this possible?) then follow my initial plan for rooting the phone
However, from what i've read it seems messing with the SPL is pretty much the only way to brick the phone. Is what i suggest safe/will it work?
Thanks guys
Click to expand...
Click to collapse
unfortunately wont work... it wont allow you to flash an older spl...probably will have to wait till an official 2.1 update comes out and hope that it might be rootable..
And THAT will teach me to look before I leap! I guess I can live with this update because its actually a HUGE improvement over what I was using before (radio reception is much better, text correction in the browser,sense is win in general and its much snappier) and I can still do usb tethering. But still, WHY DID YOU DO THIS TO US HTC!!!
EDIT:
I tried taking the rom image from the RUU and using fastboot to boot the boot.img from that but not even that works! I was thinking to do something like init=/system/bin/sh... I don't suppose theres another way to supply cmdline parameters to the kernel?
Mods can we make this a sticky to stop further irrelevant threads
Please categorize your question accordingly, Anaylize which forum to post it
Development forum is only for development of phone OS related stuff
Q- My phone is stuck and the android loading or the second screen
A- your ROM flash went wrong or some system files are missing
Remedy- Flash the ROM again or try flashing some other ROM, check your SD card if its inserted properly(If you have Linux-swap or apps 2 sd activated)
Q- I cant go past the first splash screen and i cant move into recovery or bootloader
A- Say goodbye to your phone, it is bricked.
Remedy- PM me maybe i can help you get a new phone (already got a new phone after bricking)
Q- I cant go past the first screen but can enter recovery or SPL
A- Your ROM is not flashed properly or check your SDCARD maybe its not inserted (SDCARD step only if you have apps 2 sd , linux-swap or data 2 sd)
Remedy- flash a new ROM, use nandroid and and try reformatting the ext partition
Q- My phone is slow
A- Your phone is overloaded
Remedy- Try wiping, removing some apps and increase linux swap
Q- Home screen reloads after quitting Application
A- Your RAM is not enough, phone quits Launcher or Rosie to make some RAM free
Remedy- Use or increase linux swap or try increasing swappiness
Q- Sdcard says update.zip not found
A- maybe you renamed the update.zip as update.zip.zip .If you have enabled show file extensions for know file types then rename it as update.zip and if not then rename it as update
Q- Which ROM is best for me/ Which ROM is the best for 32A/B?
A- Take some time on the forums, look at the ROMs available for your device and individually assess what works for you by reading the various issues affecting them and make a decision. If that still doesn't work out for you, hey, that's what makes XDA great, try a different one and so on, till you find one that YOU'RE happy with. It's very subjective since what my needs are could be totally different from what yours are.
Q-What will/is released, When will be released, New is released
A- Post is General Forum, leave this forum for Phone Development by Developers
Any other questions or suggestions welcome
Q- Which ROM is best for me/ Which ROM is the best for 32A/B?
A- Take some time on the forums, look at the ROMs available for your device and individually assess what works for you by reading the various issues affecting them and make a decision. If that still doesn't work out for you, hey, that's what makes XDA great, try a different one and so on, till you find one that YOU'RE happy with. It's very subjective since what my needs are could be totally different from what yours are.
Q- ADB doesn't find or see my device?
A- I suggest reading the Sapphire Wiki as it contains a lot of information about troubleshooting when you're stuck
Q- I have no data/ 3G connection
A-Check under settings ->wireless controls->mobile networks->access point names, If you have no APN set then add your carrier APN settings from this list here
anybody with a new no thread start wiki
charnsingh_online said:
...
Q- I cant go past the first splash screen and i cant move into recovery or bootloader
A- Say goodbye to your phone, it is bricked.
Remedy- PM me maybe i can help you get a new phone (already got a new phone after bricking)
...
Click to expand...
Click to collapse
Not 100% correct: if you can still load in fastboot mode (vol DOWN+POWER) you can still boot a recovery image and flash it on the device:
1. fastboot mode
2. fastboot boot myrecovery.img
3. (in the recovery) adb shell mount /sdcard
4. adb push myrecovery.img /sdcard/recovery.img
5. adb shell flash_image recovery /sdcard/recovery.img
myrecovery.img: whatever the file is called.
Bootloader is same as fastboot mode
Hey...
How do I know if I have a 32a/32b phone?
I've got a myTouch 3g and I just got it a month ago.
Is rooting illegal? I know it voids your warranty but do you get apps for free and stuff?
juiceaccts said:
How do I know if I have a 32a/32b phone?
Click to expand...
Click to collapse
Boot your phone into fastboot mode:
Power phone off
Hold Back key and power phone on
It will bring up a screen which either says
SAPPHIRE PVT 32B SHIP S-ON G
or
SAPPHIRE PVT 32A SHIP S-ON H
There will be instructions on the screen to power the phone off so you can boot as per normal.
elegos said:
Not 100% correct: if you can still load in fastboot mode (vol DOWN+POWER) you can still boot a recovery image and flash it on the device:
1. fastboot mode
2. fastboot boot myrecovery.img
3. (in the recovery) adb shell mount /sdcard
4. adb push myrecovery.img /sdcard/recovery.img
5. adb shell flash_image recovery /sdcard/recovery.img
myrecovery.img: whatever the file is called.
Click to expand...
Click to collapse
Yeah but charnsingh says, if we CAN'T go into recovery.. You're assuming we can
The post is a bit misleading, cos we don't expect physical damage to the device (in which case, you get to the first splash, but can't reach recovery.. i.e. your Back/Vol. down buttons don't work)
Q: What's Goldcard? and how to make a Goldcard
minhzc said:
Q: What's Goldcard? and how to make a Goldcard[/QUOTE
damm - i understand all, but what is a goldcard and how to create?
Click to expand...
Click to collapse
Goldcard, a special sd card that ur phone spl accepts, search the dream forum
Whenever I flash a new ROM I backup my data and apps using either Backup To Root or MyBackup Pro. When I reinstall my apps it never puts the apps back into the Market under my Downloads so that if the app developers update their apps it shows that there is an update. IN fac the only apps shown are the ones I've purchased.
What do I need to do, besides reinstalling each one individually, in order to have the Market get all my apps in the Downloads the way I want them?
Thanks
can someone explain what SPL refers to?
and then i hear terms like perfected SPL, eng SPL....
ive flashed some ROMs earlier...without worrying too mmuch about this SPL business, and now with a mandatory rogers update out, people are talking about SPLs (see rogers thread)
cheers
So what is an SPL anyway? What does it do?
The SPL, or Second Program Loader, is essentially the Android bootloader. It's job is more than just loading the Android OS - it also offers several other boot options, including Recovery mode, Fastboot, and HBOOT modes, and ultimately it's the SPL that allows manipulation of the flash nand on your device. Part of the SPL's job is to ensure that the data flashed to the device is correct. Most of the current shipping SPLs (apart from the "Perfect SPL's) let us flash a complete ROM image, but don't let us flash a recovery rom or boot image as it checks the verification signature. Haykuro has modified the SPL's available to remove this check and this is what the Engineering SPL's available offer. As the SPL is so crucial to the handset though, you have to be very careful when flashing it as if it's updated incorrectly then you may be incapable of restoring it without specialised hardware and knowledge. You essentially have a very expensive brick
Click to expand...
Click to collapse
From the xda HTC sapphire wiki
remap "search" button on MyTouch
I have searched the forum and only found results for the G1 or remapping the soft keyboard...
Can the search button (magnifying glass) be ramapped as hard key to the camera?
If this has been discussed and i missed it, links are appreciated.
If it's a kernel-level issue, i'm on enomther's TheOfficial 2.5.1 AOSP.
Thanks in advance
[Sorry mods if this isnt the right place to ask this, tired, at work and pretty much I was asleep at the wheel. Please move this to the appropriate subforum if need be. ]
if i download a rom using my phone can i rename it and apply it or do i need a computer. im already rooted and ive got the requirements for the rom already on my phone. i just want to know if its possible or not.
it will work without computer
ROM Development
Hi, I have been Googleing for a while now and cant find any info on how to remove my current Android keyboard from my current ROM and replace it with the Hero keyboard – does anyone have any links relating to ROM modification. I a have come across how to download the Hero keyboard and load it into your current setup but I kept on getting FCs plus I want to learn how to modify any part of a ROM not just the keyboard.
Thanks.
Does my new mytouch with the more ram and 3.5mm jack have an actuall name?
Hello, I recently purchased my first smartphone. The mytouch3g with 288 ram and 3.5mm jack. For two weeks now I have been researching about rooting and roms. Most of the info that i am reading/viewing is on the oringinal mytouch3g...does this stuff still apply to mine? Will installing a custom rom give me more ram? Obviously I am completely new to all this but I am finding all this stuff to be quite fascinating...Any help would be greatly appreciated.
Thanks
As a solution to the brick issue and not getting past the bootscreen or not beeing able to load fastboot or recovery here's a solution which I had tried on my magic after I lost all hope and it worked ..Thanks to God and google
while on the bootlogo screen stuck, insert your datacable. it will show fastboot in red color on top corner.
run the android sdk cmd from dos prompt and enter "fastboot boot recovery_image_name.img" provided you can find the appropriate recovery image for your phone.
after updating, it will restart and you will bt good to go
Its only going to be a matter of time before people will need to send phones back under warranty for whatever reasons so a guide for unrooting will be needed.
Any takers?
G2 already has one, but obviously we will need different rom/hboot etc to go back to our stock.
Not just unrooting, but going completely back to stock, i.e. S-ON and stock ROM.
As you say, we should be able to base it on this - http://forum.xda-developers.com/showthread.php?t=835971
Although we have several different stock ROMs, e.g. European, Asian, Vodafone UK, etc.
this is already covered in the FAQ (easy tutorial @ dev forum)
http://forum.xda-developers.com/showpost.php?p=9143411&postcount=2
gtrab said:
this is already covered in the FAQ (easy tutorial @ dev forum)
http://forum.xda-developers.com/showpost.php?p=9143411&postcount=2
Click to expand...
Click to collapse
That just says to use Visionary to turn off rooting. Or did I miss something ?
As I said, I think we need to cover how to return a phone completely to stock, and I don't think it includes all that you'd really need to do, or if you didn't use Visionary in the first place, e.g. the kind of stuff in the G2 post that I linked.
steviewevie said:
That just says to use Visionary to turn off rooting. Or did I miss something ?
As I said, I think we need to cover how to return a phone completely to stock, and I don't think it includes all that you'd really need to do, or if you didn't use Visionary in the first place, e.g. the kind of stuff in the G2 post that I linked.
Click to expand...
Click to collapse
It does say to flash an RUU to S-ON which in the past I would have said would work, but seeing how the G2 forums are not suggesting that its that simple my guess would be that its not that simple.
I had to flash the PC10img thing taken from the stock ROM to restore root and s-on. But no idea how to extract that PC10img thing, not that I have looked into it either.
That info was from one of the guides in the dev section I'm sure.
Sent from my HTC Vision using XDA App
What might work now will probably not work once an OTA update comes out for the DZ though, as per the problem on the G2 they've had which has led to quite a few semi-bricks (possibly full bricks in some cases ?).
Done some research, it would seem that flashing an RUU would work fine for those of us already rooted, if an OTA were to come out those who rooted after the OTA would have issues unless an RUU for the same OTA was released as well. (this is basically because the RUU's currently available will be older than the software the phone is on so the RUU would fail leaving you with a semi-bricked phone as described above, basically it would flash stock hboot and recovery then fail to flash the /system so you would be left with no root or recovery and no rom.
Flashing the ruu would give rise to accepting the OTA too, if you really wanted to do that, but it might block root.
you just need the RUU for your correct original phone version
OR use a gold card
eg. I have debranded mine from bell NAM 1.34.666.5 to euro generic 1.34.405.5
To go back to stock, I can:
1.- grab the bell 1.34.666.1 RUU (its slightly previous, but is the correct original version for my phone)
OR
2.- run the euro generic 1.34.405.5 with a golcard inserted
gtrab said:
you just need the RUU for your correct original phone version
Click to expand...
Click to collapse
Isn't that dangerous though once we get any OTAs, and could lead to this ?
http://forum.xda-developers.com/showthread.php?t=838484
Or am I missing something ?
steviewevie said:
Isn't that dangerous though once we get any OTAs, and could lead to this ?
http://forum.xda-developers.com/showthread.php?t=838484
Or am I missing something ?
Click to expand...
Click to collapse
Yes thats what I was getting at in my post above, any RUU you flash needs to be of the same or newer version of what your previously flashing. You cannot GoldCard to flash an RUU to S-ON or you get left with the semi-brick where you have stock recovery and hboot, but no rom installed.
So if an OTA comes out, you can't accept it, s-off then use an older RUU to s-on again. You would have to flash an RUU of that OTA version (if one is released).
Basically its best to not accept any OTA if you can avoid it and just wait for a custom rom of the same, that way we can always use the older RUU's to s-on if we need it.
I successfully downgraded my rooted/S-OFF'd phone to an earlier ROM last night. I simply followed this method - http://forum.xda-developers.com/showthread.php?t=832503
I'm of the firm belief that this is the onyl way to do it if you are at S-OFF. If you have S-OFF, then flashing an older RUU will probably brick your phone.
Well yesterday I perm root and s-off my european Desire Z with World/Euro generic 1.34.405.5. Somehow everything went bad after flashing recovery mode, so I decided to unroot it and bring it back to original settings.
I found there are 2 methods, one is to run the original ruu, and the other one was to copy the exact World/Euro generic 1.34.405.5 PC10img.zip to the root of my sd card.
Then entered to bootloader, and the phone recognize the archive, I simply apply it, and now I am back again to original stock.
However now I tried again and I am happily root, and S-Off following the amazing gtrab guide (http://forum.xda-developers.com/showthread.php?t=835777)
buzmay said:
I found there are 2 methods, one is to run the original ruu, and the other one was to copy the exact World/Euro generic 1.34.405.5 PC10img.zip to the root of my sd card.
Click to expand...
Click to collapse
That's the thing I keep saying though, flashing the original RUU worked for you because you weren't trying to downgrade the ROM, it was the same version that you already had on (just S-OFF etc). If you had a later version on your phone (e.g. via an OTA update) and were trying to flash to an earlier one, you would have bricked it trying the straight RUU method.
So what should be done is download and install an RUU - say 1.234.987, so you're on 1.234.987 - then root / S-OFF / custom ROM the phone. If anything goes wrong, reinstall the 1.234.987 RUU.
By the way - that's a fake RUU
DanWilson said:
So what should be done is download and install an RUU - say 1.234.987, so you're on 1.234.987 - then root / S-OFF / custom ROM the phone. If anything goes wrong, reinstall the 1.234.987 RUU.
Click to expand...
Click to collapse
During that process, if the stock HBOOT/recovery that is installed by that RUU decides that what you're trying to flash is "older" than your custom ROM, you're screwed though. That's why the "debranding" guide has extra steps in it, i.e. gold card and editing the misc partition.
steviewevie said:
During that process, if the stock HBOOT/recovery that is installed by that RUU decides that what you're trying to flash is "older" than your custom ROM, you're screwed though. That's why the "debranding" guide has extra steps in it, i.e. gold card and editing the misc partition.
Click to expand...
Click to collapse
I hate HTC.
Love the phones, love the Sense, hate the security.
Why not give us a command like the N1? WHY!?
So you should backup the system partition before S-OFF and so on? Like so a dd? (Following on from previous post)
DanWilson said:
So you should backup the system partition before S-OFF and so on? Like so a dd? (Following on from previous post)
Click to expand...
Click to collapse
The system partition isn't changed in S-OFF, that's the boot partition (just allows writing to the system partition).
The gold card and editing of the misc partition should work fine, as per this thread - http://forum.xda-developers.com/showthread.php?t=832503
It worked for me last night to flash to an older stock ROM (which also gave me S-ON again, removing my S-OFF).
steviewevie said:
The system partition isn't changed in S-OFF, that's the boot partition (just allows writing to the system partition).
The gold card and editing of the misc partition should work fine, as per this thread - http://forum.xda-developers.com/showthread.php?t=832503
It worked for me last night to flash to an older stock ROM (which also gave me S-ON again, removing my S-OFF).
Click to expand...
Click to collapse
Cool. Confused. I believe you though.
But you are saying just to make a gold card, and edit the misc partition?
Nice
DanWilson said:
Cool. Confused. I believe you though.
But you are saying just to make a gold card, and edit the misc partition?
Click to expand...
Click to collapse
Following that guide that I linked worked for me. Yes, I turned my SD card into a gold card and edited the misc partition. Then it is fooled into thinking you're restoring a ROM of the same version that it already is running, so it lets you do it.
Actually, I do wonder whether both steps are necessary (i.e. gold card *and* editing misc), because I thought the whole point of the gold card was that it avoided those checks, so perhaps you can do one or the other ? I am only thinking out loud here, and may well be missing something, so I don't suggest trying it other than as in that guide.