Hi there
I got a white 32B from German Vodafone.
Code:
SAPPHIRE PVT32B SHIP S-ON G
HBOOT-1.330007 (SAPP10000)
CPLD-10
RADIO 2.22.19.26I
Jul 31 2009.15.49:25
It has 1.2.1 recovery, which is nice, as I can change the ROMs, but...
I have no idea how the guy flashed this recovery. I'm trying with the second phone (exactly the same)
The method with original RUU and downgraiding, fails (wrong RUU for this model).
I can't fastboot boot or fastboot flash on both phones. I get FAILED (remote: not allow) and the SPL is NOT perfect!
The guys here:
http://forum.xda-developers.com/showpost.php?p=4649780&postcount=43
have the same problem.
How can i use fastboot? Guess the perfect method is not for me.
How can I root the second phone? It has 1.6 now and refuses to go back to 1.5...
Ok the method with flashing ENG SPL via update.zip via recovery worked for the 1st phone (http://forum.xda-developers.com/showthread.php?t=529019)
Now it's only how to root the other...
BTW What does RADIO mean (on the fastboot 3-boards white screen) ? I can't find it...
It seems that we have the exact same model
As you saw on my thread, I used the 1 method click to flash the recovery rom, and from that install the ROMS.
As for the flashscreen, I did not find an answer, I guess that the only solution will be to flash a new SPL that allows to flash through fastboot.
On some threads that I created and were blocked since they were in the wrong section(I was stupid, twice...), they have sugested to update to the Engineering SPL 1.33.2005 using the recovery method tool.
I have never tried it since I haven't seen anyone with HBOOT-1.330007 that have changed its SPL... I don't want to risk bricking it... I have been told that there are some risk, but not too big... any way, I still have not tried to flash the SPL.
You said that you have flashed a first phone with a ENG SPL, what was its original SPL and how did you flashed if?
Here are the threads that were closed:
http://forum.xda-developers.com/showthread.php?t=567517
http://forum.xda-developers.com/showthread.php?t=567497
Here is a message that may be important:
http://forum.xda-developers.com/showpost.php?p=4643066&postcount=164
I had this spl inside my Magiic from Voda Germany
HBOOT-1.33.0007 (SAPP10000)
I used "RecoverFlasher" to get another recovery inside.
Then I Booted into recovery mode and flashed
HBOOT-1.33.2004 into the phone.
It is now running perfectly well with AmonRA s rom
and AmonRa 1.23 recovery inside
Eurocrypt said:
I had this spl inside my Magiic from Voda Germany
HBOOT-1.33.0007 (SAPP10000)
I used "RecoverFlasher" to get another recovery inside.
Then I Booted into recovery mode and flashed
HBOOT-1.33.2004 into the phone.
It is now running perfectly well with AmonRA s rom
and AmonRa 1.23 recovery inside
Click to expand...
Click to collapse
Humm, thats excellent news, finally someone with an HBOOT-1.33.0007 that had changed its SPL
Thanx
Did you use the "Engineering SPL 1.33.2004 - MD5 : 1B49F0A53E147171E7C51F08510CF95F" from http://forum.xda-developers.com/showthread.php?t=529019?
Well for now I've got
1. white 32B with an eng SPL (Engineering SPL 1.33.2010 - MD5 : 865020FBDFBD9C08950076A701A8A003) changed from 0007 (http://forum.xda-developers.com/showthread.php?t=529019). recovery 1.2.1 -> select zip file -> reboot and it worked. then i flashed my boot screen with fastboot, as in the tutorials.
i'm doing everything using the recovery and the 'update.zip' position in the menu. right now having cyanogenmod 4.2.2 with my native Polish keyboard installed as an app from the market. Works great.
2. black 32b with Donut 1.6 which refuses to do fastboot and adb flash. What's more HTC Sync doesn't recognize the phone and the RUU (from the 1 click method) says there's an error with the files (and shows strange ROM version installed on my phone)
skhell:
Thats the one I used
Altembas said:
Well for now I've got
1. white 32B with an eng SPL (Engineering SPL 1.33.2010 - MD5 : 865020FBDFBD9C08950076A701A8A003) changed from 0007 (http://forum.xda-developers.com/showthread.php?t=529019). recovery 1.2.1 -> select zip file -> reboot and it worked. then i flashed my boot screen with fastboot, as in the tutorials.
i'm doing everything using the recovery and the 'update.zip' position in the menu. right now having cyanogenmod 4.2.2 with my native Polish keyboard installed as an app from the market. Works great.
Click to expand...
Click to collapse
I am starting to like this thread, I see that I can flash two SPLs on my phone with no problem
2. black 32b with Donut 1.6 which refuses to do fastboot and adb flash. What's more HTC Sync doesn't recognize the phone and the RUU (from the 1 click method) says there's an error with the files (and shows strange ROM version installed on my phone)
Click to expand...
Click to collapse
I guess that your only option will be to use the "Gold card" method, but I really don't know how that works, there are quite a posts over the forum with info on that, a quick search will tell you how.
I keep getting this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and later err 155...
seriously wt*?
Have you tried the "Gold card" thing?
nope, i don't feel like buying and then destroying an SD card I'm not that desperate... yet!
I'm concerned about that RUU which shows vfpioneer-user instead of the ROM version...
Altembas said:
nope, i don't feel like buying and then destroying an SD card I'm not that desperate... yet!
I'm concerned about that RUU which shows vfpioneer-user instead of the ROM version...
Click to expand...
Click to collapse
I don't know how the goldcard method works, but how will it destroy your SD card?
I've found in some tutorials that when you write bytes to the card it stops working as a normal card. Probably because you write from sector 0, and i guess there is some important data stored.
If personally find it VERY odd. If you can use (under linux) dd to write to the card, then you can use it to read from it it's original bytes and restore them later. That is ofcourse if the card (after turning to goldcard) will be recognized as a SD card...
Altembas said:
I've found in some tutorials that when you write bytes to the card it stops working as a normal card. Probably because you write from sector 0, and i guess there is some important data stored.
If personally find it VERY odd. If you can use (under linux) dd to write to the card, then you can use it to read from it it's original bytes and restore them later. That is ofcourse if the card (after turning to goldcard) will be recognized as a SD card...
Click to expand...
Click to collapse
I do believe if that happens, if you make a copy with dd, you can safely restore it. Just to be sure, you can also make a backup of the partition table of the sdcard.
Oh, the dd tool is also available to windows, but I guess this kind of things should be done on linux
I don't mind using linux. Actually I use both everyday. And it seems easier to use dd than some fancy hex editor under windows.
Anyway, my only concern is that, I may overwrite the bytes which identificate the card as a SD card (and not as a MMC for instance) and then the usb reader and linux woun't be able to use it... So there will be no way to use dd to restore backup...
On the other hand, I'm pretty sure I'm exaggerating and the only problem some ppl had was with the Windows Hex editor editing to much. I see no reason why the 'dd method' shouldn't work...
Ahhhhhhhh!
Finally some progress, little but still. RUU finds my phone (and version number) only if my magic is in fastboot mode! Then it actually works, until it starts to check the CID number...
rom.zip contains android-info.txt which has a different cid number (i'm talking about the 1click method).
The question which arises is why can't i edit rom.zip and put there recovery flash, eng SPL, modified ROM and force an update by changing CID in .txt?
And an answer:
because CID check is done between the phone and the .img files, the txt is only supplementary. So preparing another .zip file doesn't work
Back, to where I was 3 days ago
Related
Hello everyone, i've got the interest of joining everyone and try come up with a solution in orther to sort the part of After rooting , suddently become S ON. I know problably you made a mistake, but the intention of this post is to try undone that mistake, or achive a new solution to it.
I would request everyone to post exacly what you have done to become S ON. Try remember every detail, such as after you turned on the phone, wich bottons you touched, options selected, if you used recover, fastboot HBoot .
Lets hope we may achive a solution to everyone
Issues underinvestigation: http://forum.xda-developers.com/showthread.php?t=665349
Recomended method if you want to flash radio or Hboot, the use fastboot its the safest way.
Regards
I have my phone rooted and it says S-ON. Not sure what it was before rooting. But what exactly is S-ON and S-OFF. What are the difference?
ayush20m said:
I have my phone rooted and it says S-ON. Not sure what it was before rooting. But what exactly is S-ON and S-OFF. What are the difference?
Click to expand...
Click to collapse
The diference is that S-ON means singature verification On, in other words your phone is not rooted now. If you try install another rom, it wont install. Could you please Copy the details wich are on Fastboot?
PLease try remember the last modifications wich you've made on your phone before become S-ON after you rooted.
A well rooted phone is something similer as:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sapphire PVT 32 B Ship S-ON G
HBOOT 1.33.0006 (SAPP 30000)
CPLD 10
RADIO 2.22.19.26I
I did not do anything since I rooted it about 3 weeks ago. At that time I was able to install a new ROM.
jgcaap said:
in other words your phone is not rooted now. If you try install another rom, it wont install
Click to expand...
Click to collapse
I still have root access. I can use the su command in terminal emulator. Does S-ON just prevent from installing another ROM?
hmm interesting. You are a 32B i need to study those (I only understand of 32A But since we are a community surely someone with a 32 B should know the awser but i'll also study those) . But according to theory you cant flash new rom. Could you provide the instructions you followed please?
Superuser app installed, i'm not sure at wich point it should work completly with Sign ON.
Please test by going to the adb and enter in su mode then type cd /data/app-private if it works than the ROM is rooted.
But the Singature verification is ON so i supposed the protection again rom flashing is on also.
S-ON prevents you from using fastboot commands. It does not mean you're not rooted.. You can definitely flash another rom with S-ON
KAwAtA said:
S-ON prevents you from using fastboot commands. It does not mean you're not rooted.. You can definitely flash another rom with S-ON
Click to expand...
Click to collapse
Thanks Kawata. I lost my heart beat for a second there but now it is back.
So how do I turn S-OFF. I followed the unlockr method for rooting my phone. It did not mention anything about S-ON or OFF
Flash an ENG spl via recovery. And then never again touch your radio/spl using recovery. Do it from fastboot
anyoneelse having issues post here Thanks kAwAtA
KAwAtA said:
Flash an ENG spl via recovery. And then never again touch your radio/spl using recovery. Do it from fastboot
Click to expand...
Click to collapse
i know this is probably rezing this post, but i actually cant do this, because my SD card just isn't recognized anymore. i can't mount it, i cant access it from Recovery, i've tried all kinds of solutions regarding the fixing the SD card slot, but alas, i think i may have backed myself into a corner.
hay guys pls help me out
i am having LEO asia version
yeterday i flashed it with (biggest mistake of my life)
RUU_Leo_1_5_TMOUS_2.13.531.1_Radio_15.39.50.07U_2. 10.50.26_Signed_LEO_Ship
using sd card(another big blunder)
its orignal rom was
RUU_Leo_HTC_WWE_1.66.405.2_Radio_Signed_15.30.50.07U_2.06.51.07_Ship.exe
now it is stuck on this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i tried hspl2 gives this
i tried hspl it gives me this
hspl1024
http://i39.tinypic.com/21cyp9i.jpg
when trying to format with official rom
just shows loading....... and hangs out
pls somebody help out i bough this phone collecting my 6 months salary
common guys any body there
Should have read the stickies bro....
Anyways, try flashing an older stock version from SD...but I think you are stuck because now phone has new SPL 2.10 on it and no HSPL out there for it yet.
You could however try flashing the new stock ROM from PC instead of SD and it should atleast give you a working phone
there is no spl for 2.10 yet... not sure you can flash a stock ROM vis PC to get it working. try flashing your stock ROM via SD.
pongster's
i tried flashing stock rom via sd also stuck on loading..........
rahul_sharma1982 said:
pongster's
i tried flashing stock rom via sd also stuck on loading..........
Click to expand...
Click to collapse
that means only one thing... I'm afraid you'll need to wait for HSPL3 or something to get HSPL for 2.10.
Bepe and Cotulla and their team are the geniuses that will be able to help you out.
you're phone still has hope... you'll have to wait though... there were those who flashed the 2.10 shipped ROM before Hspl2 came out and were stuck as well. A new Hspl for 2.10 Spl looks like your only chance.
Hopefully, I'm wrong...
Sorry to hear that Bro..
Your Leo stucked on SPL 2.10 while the most currrent HSPL is HSPL 2.08.
What I understand, original SPL can be upgraded but not downgraded.
I suggest you to bring it to HTC service center. They will definitely know that the warranty is void, but you still can ask them to repair it but you will be charged for that (but its better to try it unless the cost is more than the price of your Leo)
Flash the 2.13 rom again.
Apart from gold card its the only thing you can do until a 2.10 hardspl is released.
Reflash 2.13 with Goldcard is ur only solution.
Probably you have to change the first 2 digit from 00 to 11 in ur goldcard.
It's funny, there shipping LEO 1.5 PB81120 in whole of Asia.
hello xmoo
u suggested for gold card but i searched in this forum and found gold cards are no longer available. if u know the method pl tell me thanks
rahul_sharma1982 said:
hello xmoo
u suggested for gold card but i searched in this forum and found gold cards are no longer available. if u know the method pl tell me thanks
Click to expand...
Click to collapse
PM ur SD-Card serial nr and i'll fix you a correct goldcard!
pkoper
i tried to flash 2.13 again but error is coming .
That is sad....
Reflashing your leo 2.13 is the only option left i think.. give it a try.. or wait for the newer version of hspl.. current version of hspl2 support till only 2.08 and by flashing via sd card u have upgraded your hspl to 2.10 ..
Wait or try 2.13.. that is all you can do for now.. rest ask Bepe and cotulla for the help.. if they can do anything for you..
xmoo
thanx xmoo i will post my sd card serial nr tonight as i am in office u r my last hope man
how about flashing the 2.10
Code:
tmous rom from sd card? yes it will fail, but will it not flash the spl 2.08 before it fails?
just a thought.
samsamuel's
no i tried that also its going to 1% and phone restarts
only solutions i know about for this are the following:
1: turn your phone off, put it in the microwave for 2-3 seconds, this will destroy all data held on all chips in the HD2, essentially causing a complete failure, then return it, when they ask what happened tell them this:
I was sending an sms, the screen went all static and the device locked up, so i pulled the batter and tryed a soft reset, but the device didnt load and now it does this....
(this wil also stp them from being able to tell if you have tried to flash at all!!)
2: wait for new SPL
(it all depends on your insurance really)
MG
good suggestion i will go for 2nd one:
MysticGenius said:
only solutions i know about for this are the following:
1: turn your phone off, put it in the microwave for 2-3 seconds, this will destroy all data held on all chips in the HD2, essentially causing a complete failure, then return it, when they ask what happened tell them this:
I was sending an sms, the screen went all static and the device locked up, so i pulled the batter and tryed a soft reset, but the device didnt load and now it does this....
(this wil also stp them from being able to tell if you have tried to flash at all!!)
2: wait for new SPL
(it all depends on your insurance really)
MG
Click to expand...
Click to collapse
Number 1. works great for me...THX...
Hi,my phone is having the same problem.However,my SPL version is 2.08.I want to flash back to a stock rom but it just stucks at the white 'loading...' screen.Here's a picture of it.
Hey everybody,
I'm opening this thread as a support tool for AplhaRev X.
I'm going to go first with my problem.
Phone gets detected, Beta key accepted and then I get to aquiring root.....
And that seems to be as far as I can get. I just seem to get stuck there.
Firstly I did it using Windows 7, which tells you to wait up to 15 mins and I went over this period. I did a factory reset on phone and tried again with the same result
I've just tried the Linux version on Ubuntu, again with the same result.
I've been connected as charge only, usb debugging turned on.
Currently running eclair 1.37 WWE but with hboot 1.01.0002 after several downgrades/upgrades attempting to root my phone. I am also using a goldcard and a modded misc image.
Why am I getting stuck at this point? Do I need to flash 2.2 first? Do I need to format sdcard or something?
Thanks
Im kind of new to android and I would love to try this, but could some1 please first post or link me a guide wich tells me what to do after this alpharev X's s-off, if i would like to install cyanogenmod (and i guess clockwordmod recovery needs to be installed too)?
When i Run It
It Says That
Rebooting to fastboot (again)...
Waiting for fastboot...
FAILED - Go have some lemonade!
Press (almost) any key to exit.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Helllllllllllllllllllllp
Problem Solved
Sorted,
Upgraded to Froyo which downgraded Hboot from 1.01.0002 to 1.01.0001,
redownloaded for hboot 1.01.0001 ran it and instant success.
Well done AlphaRev, its fantastic what you have achieved.
Theres a donation coming your way (not till payday though)
dannyjmcguinness said:
Hey everybody,
I'm opening this thread as a support tool for AplhaRev X.
I'm going to go first with my problem.
Phone gets detected, Beta key accepted and then I get to aquiring root.....
And that seems to be as far as I can get. I just seem to get stuck there.
Firstly I did it using Windows 7, which tells you to wait up to 15 mins and I went over this period. I did a factory reset on phone and tried again with the same result
I've just tried the Linux version on Ubuntu, again with the same result.
I've been connected as charge only, usb debugging turned on.
Currently running eclair 1.37 WWE but with hboot 1.01.0002 after several downgrades/upgrades attempting to root my phone. I am also using a goldcard and a modded misc image.
Why am I getting stuck at this point? Do I need to flash 2.2 first? Do I need to format sdcard or something?
Thanks
Click to expand...
Click to collapse
Is there anything else that I need beside AlphaRev X software? Because I run the software and connect the phone and it says "Waiting for device...". I left it for ten minutes and it still didn't detect my phone. Also, I have enabled USB debugging and selected "Charge only" mode when connected to PC. Am I doing something wrong?
Also note that I don't know a lot about flashing.
Thanks in advance
You need:
Unrevoked hboot drivers: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
ADB:
Download Android SDK
@dannyjmcguinness
good to see it solved. Issue maybe due to gingerbreak supporting froyo.
----------------------------------------------------------------------------------------------------------------------------------------------
@Hooda_mask
What is ur os version. Have u downgraded to eclair without downgrading hboot (there is a process actually).
Maybe u also need the unrevoked hboot drivers. Uninstall htc sync if present.
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Alternatively, irrespective of process, try to connect phone to pc in fastboot mode and check the command fastboot reboot from command prompt "tools folder" of android sdk (where fastboot.exe lies) and see whether phone reboots or not.
nejc121 said:
You need:
Unrevoked hboot drivers: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
ADB:
Download Android SDK
Click to expand...
Click to collapse
It is probably worth mentioning that these drivers are only required if you are using Windows. If you use the Linux version no additional drivers are needed.
Sent from my HTC Wildfire using XDA App
Well I don't know I'm lost ... been trying for several hours now ... with no success.
I'm running the UK Vodafone RRU.
Phone is detected AlphaRevX runs fine ... i.e.
This is a beta release and requires a beta release key.
Please visit: http://alpharev.nl/x/beta for more information.
Enter beta key [serial: xxxxxxxxxxx]: xxxxxxxxxxxxxxxx
Beta key accepted - thank you for participating!
Acquiring root (method 1)...
Sending in Caroline...
Cleaning up...
Rebooting to fastboot...
Waiting for fastboot...
When life gives you lemons, don't make lemonade. Make life take the lemons back!
Rebooting to fastboot (again)...
Waiting for fastboot...
FAILED - Go have some lemonade!
Running HBOOT 1.01.0002
Tried patching a WWE RRU but get a "HBOOT versions wrong error".
Perhaps I need a downgrade or other solution.....
Anyone got any ideas? Or is this Vodafone ROM is dead duck?
Not tried with Linux yet .....
Thanks in advance.
Mipery said:
Im kind of new to android and I would love to try this, but could some1 please first post or link me a guide wich tells me what to do after this alpharev X's s-off, if i would like to install cyanogenmod (and i guess clockwordmod recovery needs to be installed too)?
Click to expand...
Click to collapse
Here you go. I followed this.
chbiz said:
Well I don't know I'm lost ... been trying for several hours now ... with no success.
I'm running the UK Vodafone RRU.
Phone is detected AlphaRevX runs fine ... i.e.
This is a beta release and requires a beta release key.
Please visit: http://alpharev.nl/x/beta for more information.
Enter beta key [serial: xxxxxxxxxxx]: xxxxxxxxxxxxxxxx
Beta key accepted - thank you for participating!
Acquiring root (method 1)...
Sending in Caroline...
Cleaning up...
Rebooting to fastboot...
Waiting for fastboot...
When life gives you lemons, don't make lemonade. Make life take the lemons back!
Rebooting to fastboot (again)...
Waiting for fastboot...
FAILED - Go have some lemonade!
Running HBOOT 1.01.0002
Tried patching a WWE RRU but get a "HBOOT versions wrong error".
Perhaps I need a downgrade or other solution.....
Anyone got any ideas? Or is this Vodafone ROM is dead duck?
Not tried with Linux yet .....
Thanks in advance.
Click to expand...
Click to collapse
Sent from my HTC Wildfire using XDA App
Have you tried a factory reset first?
I've done 2 devices but I got another one 1 to do.
1 of them was on Vodafone 2.2. That one was successful.
There was another update for Vodafone after Froyo, which was installed on the one I'm having problems with, resulting in same error.
Are you fully OTA updated?
1.01.0002 to 1.01.0001
[Deleted]
If Anyone having problem with doing S-OFF then verify this before proceeding:
1. Make sure you have Froyo (Official) WWE ROM installed. So that you will have version 2.2.1
2. Make sure you have WWE ROM installed so that your hboot version will be 1.01.0001 as there's some problem with others like 1.01.0002 or so..
3. Make sure HTC Sync is uninstalled as it may interrupt the normal operation of the tool. DON'T UNINSTALL DRIVERS.
4. Make sure you are in Charge Only mode and Debugging Mode Option selected. If not goto Settings > Applications > Development > USB Debugging - Check this option.
5. Make sure your phone is connected with turned on in normal mode not in hboot or recovery or fastboot mode.
6. If you have Eclair ROM upgrade it to FROYO and if you have Regional ROM which has hboot different from 1.01.0001 then downgrade it to WWE ROM by using below method provided by dannyjmcguinness:
Code:
1. Started out with hboot 1.01.0002 and Froyo 2.2.1 preinstalled when I bought it new.
2. Achieved shell root using the psneuter hack (newbies, you may find it easier using SuperOneClick 1.65 or 1.7 for this). You should now have root #.
3. Run command "adb shell cat /dev/mtd/mtd0 > /sdcard/mtd0.img". This creates an image of mtd0 on sdcard. There are other tutorials with theses kind of steps and you may find it referred to as misc.img as opposed to mtd0.img. This doesn't really matter as long as the final command includes the correct file name. This command will fail if connected as disk drive, you must be charge only.
4. Reconnect as disk drive allowing computer gui access to sdcard. Using a hex editor (I used HxD, which is freeware) open disk image mtd0 on sdcard. On line 6 you should find a version number and it will look something like 2.22.405.1. This needs to altered to correspond to the RUU you intend to flash. If you are on hboot 1.01.002 you need an WWE RUU first that contains hboot 1.01.001 so you are still looking at reinstalling Froyo. Those allready on hboot 1.01.001 may choose any WWE RUU. I'm not absolultley sure, but it may be possible for those on those on hboot 1.01.002 to skip to another RUU but I think you would more than likely get a "customer ID" error.
5. I used the goldcard method to flash my RUU. There are many tutorials, but some seem to sequence different steps. To get mine working I used the goldcard tool available on these forums, but found it wouldn't work. It does, however do a good job of getting your CID and reversing it for you, so copy that and use the page provided with the tool to get your goldcard via email.
6. Make sure you are connected as disk drive and open HxD again. Open the goldcard image as read-only. Also open the sdcard (after using windows to full format it, fat32). Oh yeah, dont forget it needs to be a primary partition (do this before format) there is a handy free tool called "MiniTool Partition Wizard Home Edition", which is so easy to use. Make sure physical sd disk is opened and read-only is unchecked.
7. Copy the goldcard using HxD (select all, or 0 - 17F) and overwrite the same blocks on sdcard. Save it.
8. Disconnect phone from PC and allow phone to mount, reconnect as disk drive. If phone or PC asks for format keep repeating sequence until normal operation can be maintained.
9. Download "flash_image" a file with no extension. Push it to sdcard. You need to have flash_image and your modified mtd0.img on your sdcard (It may be useful to ceate goldcard before creating mtd0.img, unless you back it up to PC before goldcard creation).
10. Run command (connected charge only, as root) "cat /sdcard/flash_image > /data/flash_image
11. Run command "chmod 0755 /data/flash_image" On a seperate note I've been using permission set 67676 as I've noticed the permission set seems to be more then 4 digits, there seems to be 5, poosibly even 6 digits. This particular permission changes some of the permissions to capital characters. What use this is, i dont know I'm looking into it though
12. run command "/data/./flash_image misc /sdcard/mtdo.img"
13. You should now be able to flash RUU or pull rom.zip from temp files when running RUU and rename PC49IMG.zip
14. PC49IMG.zip should be pushed to root of sdcard if using goldcard (I don't know if RUU can be flashed normally without goldcard, but i think so, i dont think RUU pushes rom.zip to sdcard but it may be necessary as a CID thing).
15. Its now successfully downgraded to 1.01.0001 (WWE FROYO ROM)
Or check here too for downgrading:
http://forum.xda-developers.com/showthread.php?t=1132028&highlight=1.01.0002+to+1.01.0001
Hope after this checks you can S-OFF successfully.
Quick question, anyone got any patched hboot partition tables? Ordo i have to do it myself?
SORRY had enough I JUST WONT HAVE IT DONT NO WHAT I AM DOING JUST KEEPS FAILING ALL THE TIME S-OFF YES I AM NEED HELP BIG TIME
Good lord, it's working!
This is kinda weird...
I ran the tool.
It ended by saying everything went smooth but when I try to boot into recovery or run any app that needs root access it just tells me that I'm not rooted...
The 'funny' thing is that when I boot into HBOOT at the top of the screen it says:
---AlphaRev ---
BUZZ PVT SHIP S-OFF
HBOOT-6.01.1002
.
.
.
So it says S-OFF but apparently not.
When I try to run AlphaRevX again I'm told that my phone is not supported...
Any one?
nicolaibvm said:
I ran the tool.
It ended by saying everything went smooth but when I try to boot into recovery or run any app that needs root access it just tells me that I'm not rooted...
The 'funny' thing is that when I boot into HBOOT at the top of the screen it says:
---AlphaRev ---
BUZZ PVT SHIP S-OFF
HBOOT-6.01.1002
.
.
.
So it says S-OFF but apparently not.
When I try to run AlphaRevX again I'm told that my phone is not supported...
Any one?
Click to expand...
Click to collapse
It just gave you S-OFF. Not a Custom Recovery like ClockworkMod, and not the Superuser binary which gives you root access. These are additional processes which you all have to perform after getting S-OFF. Refer this guide:
http://forum.xda-developers.com/showthread.php?t=1130044
Sorry, thanks and it worked...
I misunderstood. I thought it also rooted. Followed your link and it worked like a charm. thank you VERY much!
faz1511 said:
SORRY had enough I JUST WONT HAVE IT DONT NO WHAT I AM DOING JUST KEEPS FAILING ALL THE TIME S-OFF YES I AM NEED HELP BIG TIME
Click to expand...
Click to collapse
Sure.
Hello.
Please.
Thank you.
Hello,
I recently got a Nexus One to replace my old G1. Now that the Nexus One is my daily driver phone, I want to get my hands dirty and play around with my G1. Even though I had my G1 for nearly a year, I never went ahead and installed any custom ROMs on the thing fearing that I'd somehow brick the phone or mess it up in some way, so I stuck with the official Donut update (it's been hard using Android 1.x while everyone has been using >2.x for the past year or so).
Anyway, I've wiped the G1 back to factory settings and then downgraded it to RC29 (using this guide) so I could activate it over WiFi (I don't have an active SIM in the phone). So right now, I'm on stock Android 1.0.
I think I want to try a Sense ROM on my G1 (Sense is my favorite custom Android UI and I think it looks pretty darned good, too). Are there any decent Sense ROMs for the G1 that are fast and stable? Preferably, I'd like them to be based on Android 2.0 or higher for better app compatibility (and maybe multi-touch).
I won't be using the G1 as a phone (or at least I don't plan to). I intend on using it mainly to browse the internet over WiFi.
Since I've never done any rooting or custom ROM installations on my phone, I'm a bit of a noob at the entire rooting/flashing process. Are there any special precautions that I'd need to take on a phone running stock Android 1.0?
Thanks.
beanboy89 said:
Hello,
I recently got a Nexus One to replace my old G1. Now that the Nexus One is my daily driver phone, I want to get my hands dirty and play around with my G1. Even though I had my G1 for nearly a year, I never went ahead and installed any custom ROMs on the thing fearing that I'd somehow brick the phone or mess it up in some way, so I stuck with the official Donut update (it's been hard using Android 1.x while everyone has been using >2.x for the past year or so).
Anyway, I've wiped the G1 back to factory settings and then downgraded it to RC29 (using this guide) so I could activate it over WiFi (I don't have an active SIM in the phone). So right now, I'm on stock Android 1.0.
I think I want to try a Sense ROM on my G1 (Sense is my favorite custom Android UI and I think it looks pretty darned good, too). Are there any decent Sense ROMs for the G1 that are fast and stable? Preferably, I'd like them to be based on Android 2.0 or higher for better app compatibility (and maybe multi-touch).
I won't be using the G1 as a phone (or at least I don't plan to). I intend on using it mainly to browse the internet over WiFi.
Since I've never done any rooting or custom ROM installations on my phone, I'm a bit of a noob at the entire rooting/flashing process. Are there any special precautions that I'd need to take on a phone running stock Android 1.0?
Thanks.
Click to expand...
Click to collapse
hey,
here's a good sense rom:http://forum.xda-developers.com/showthread.php?t=1116154 it's android 2.1 Eclair.
to flash that rom, your going to have to root and upgrade your radio/spl here's a good guide for that:http://forum.xda-developers.com/showthread.php?t=1098899
Just follow that guide and you should be good.
and your also going to have to partiton your sd card with swap and ext 4 partitions so just follow my instructions:
Ok, so heres what your going to do.
We are going to partition through recovery:
boot into recovery
go to the partition sd card option
click partition sd card
use these sizes:ext 2: 512 mb, linux swap : 96mb, and the rest is for the fat 32 partition
then once that is done, click ; SD:ext2 to ext3 :: Convert ext2 to ext3
then once that is done, click : SD:ext3 to ext4 :: Convert ext3 to ext4
and u now have ext 4!
and there ur done.
Click to expand...
Click to collapse
these are instructions for amon ra recovery so make sure u have that recovery when doing these instructions
Good luck and have fun flashing!
Thanks...
Before I do anything, should I upgrade to Android 1.5 or 1.6 or will it be easier for me to do this process on 1.0/RC29 (which I believe can be easily rooted).
Here's what I currently have on the phone:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Upgrade to android 1.5 it'll make things easier.
Sent from my Gingerbread on Dream using XDA App
yeah i believe you need 1.5 to gain root access on device
@maximo thanks for reccomending my ROM & rooting guide
@beanboy if you have any further questions maximo and myself are usually available so dont be shy to ask questions!!! there is nooooo stupid question out there when it comes to rooting your device! nobody wants a brick in there pocket
Easiest way to root would be upgrade to 1.6
Run universal androot
Install rom manager and flash recovery of choice through there.
Then you should upgrade to the 0013d spl and 27.08 it 28.25 radio.
Then flash rom.
(For sense I recommend senselx. (Yes I'm recommending a rom I kinda helped develop )
Otherwise I recommend ezgingerbread.)
I got 1.5 installed, but when I try to update to 1.6 from the SD card, I get this error:
http://i.imgur.com/NuEvT.jpg
I guess I'll have to wait for the OTA update?
beanboy89 said:
I got 1.5 installed, but when I try to update to 1.6 from the SD card, I get this error:
http://i.imgur.com/NuEvT.jpg
I guess I'll have to wait for the OTA update?
Click to expand...
Click to collapse
I think ldrifta's guide is for 1.5
I've never used 1.5 and I only used 1.6 long enough to root and flash cm.
Universal androot might work on 1.5. Try it and see what happens. If it works then find a flash_image binary and a recovery image and flash it manually
Manual flash instructions via adb:
adb push flash_image /data/local
adb push recovery.img /sdcard
adb shell
$ su
# chmod +x /data/local/flash_image
# /data/local/flash_image recovery /sdcard/recovery.img
Flashing from the phone works the same way, just with everything run in a terminal and changed appropriately
Or if you have an eng spl you can use fastboot and 3 commands to get the latest radio and spl and custom recovery. Look for ezterry's 14mb ram thread
I think something is up with my G1's hardware. Before I completely wiped everything, I had been having problems with the SD card not being detected most of the time. I tried different cards, and none of them seemed to improve the situation. So, I followed ldrifta's guide since I was already on Android 1.5. I was got through step 1 (installing OI File Manager, installing flashrec from the SD card, and then flashed the backup recovery. I rebooted into recovery mode (I guess it was just the new recovery that I had just flashed). I then wiped the device and when I went to flash the .zip file, it wouldn't let me do so, giving some errors about not being able to read the SD card or something. So I rebooted back into normal Android 1.5 (I think) and now I'm stuck not being able to activate the phone because there's no data. I guess I'll have to go back to RC29 to reactivate. This is beginning to seem like way too much trouble. Ugh.
I had issue with class 2 sdcards in my device. They randomly wouldn't work. Maybe you are having the same problem. Try a class 4 or faster card.
Or if you got to the point of having an eng spl, the only thing the sdcard is needed for us flashing roms. How far did you get into ldrifta's guide?
I got through step 1 and had just started step 2 where I went to wipe the device. The installing update .zip didn't seem to work. I went ahead and reflashed back to RC29 and now I'm back with Android 1.0.
I've tried two SD cards: A 1 GB Transcend (no class because it's not an SDHC card) and two different 4 GB SanDisks (each class 2).
Try to follow his guide up to getting an eng spl if you don't already have one. If you have one then flash the new radio and spl and a recovery via fastboot. Then try to get a class 4 sdcard and see if it helps
tvall said:
Try to follow his guide up to getting an eng spl if you don't already have one. If you have one then flash the new radio and spl and a recovery via fastboot. Then try to get a class 4 sdcard and see if it helps
Click to expand...
Click to collapse
I assume I still have the default SPL installed. I don't think I was able to flash any other SPLs. I'll go through and try to upgrade Android again to 1.5 or 1.6. And speaking of that, do I need to install 1.5 before installing 1.6? I see that the .zip for 1.5 is much bigger than 1.6's. Are the updates incremental, meaning I have to have 1.5 installed first and then upgrade to 1.6?
Okay, I got 1.6 installed. I installed 1.5 CRB43, and then 1.5 CRC1, and finally 1.6 DRC83. Apparently you can't update directly from CRB43 to DRC83. I guess I'm now set to start rooting, flashing recoveries, flashing radios, and installing custom ROMs...
I'd suggest Ginger Yoshi 1.2.1
I'm still a bit confused on the process that I'd follow, however. I see guides that say that I need to have a certain radio, installed, a certain recovery, etc. I'm still not exactly sure of what I need or what I need to do it. I know that I can't just flash a custom ROM from the stock recovery and expect it to work. For example, how do I check my radio version and recovery (I think I have the stock recovery)?
beanboy89 said:
I'm still a bit confused on the process that I'd follow, however. I see guides that say that I need to have a certain radio, installed, a certain recovery, etc. I'm still not exactly sure of what I need or what I need to do it. I know that I can't just flash a custom ROM from the stock recovery and expect it to work. For example, how do I check my radio version and recovery (I think I have the stock recovery)?
Click to expand...
Click to collapse
Can you boot to fastboot mode?
power off phone - hold back button down then press power button.
jeff72k said:
Can you boot to fastboot mode?
power off phone - hold back button down then press power button.
Click to expand...
Click to collapse
Yeah. Here's what I'm getting:
Code:
DREA100 PVT 32B
HBOOT-0.95.000
CLPD-4
RADIO-2.22.19.26I
Sep 2 2008
Serial0
beanboy89 said:
Yeah. Here's what I'm getting:
Code:
DREA100 PVT 32B
HBOOT-0.95.000
CLPD-4
RADIO-2.22.19.26I
Sep 2 2008
Serial0
Click to expand...
Click to collapse
Does it say s-off? Or eng ?
hi,
i try to figure why , buy when i start the device he boot regular to adnroid but after 3 sec the screen fade to black and not responding.
the device worked good.
i decide to back to wm 6.5 and then all this mess start.
use hspl 2.08 , radio 2.15.50.14 , leo t8585 , magldr 1.13 .
any idea?
thanks.
Need more info ...
What ROM were you using?
What was the last thing you had done before this problem started?
Are you on NativeSD, SD or NAND? if NAND, which recovery?
We can't help you if you don't help us help you.
thanks for your help.
last thing i did is downloaded wm stock : RUU_Leo_S_HTC_WWE_3.14.405.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship
but after installed this stock , phone was stuck on htc white screen with some letters in red in the left corner.
after i saw that i cant install this wm so i tried to back to the old nanndroid.
installed hspl 2.08
magldr 1.13
recovery 150M
clockwork mode 3.0.0.5
with this i installed once :
typhoon rom and hyperdroid
after that i used recovery with 400M and coredroid rom.
maybe its importent to tell that in the recovery and in the boot animation and pics there is no problam.
same same with all this
thanks again.
I wonder why people flash back to stock, and when they get problems they flash back to android.
Okay, use the HD2 Toolkit (google it) to repartition your NAND and install a later recovery. Choose a bigger partition than 150, like say 180. After that, install Typhoon or Hyperdroid and see if it works.
I am telling you this because I can't see anything wrong in your steps.
Luckycookies said:
thanks for your help.
last thing i did is downloaded wm stock : RUU_Leo_S_HTC_WWE_3.14.405.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship
but after installed this stock , phone was stuck on htc white screen with some letters in red in the left corner.
after i saw that i cant install this wm so i tried to back to the old
Click to expand...
Click to collapse
Did you switch HSPL back before flashing WinMo??
Luckycookies said:
installed hspl 2.08
magldr 1.13
recovery 150M
clockwork mode 3.0.0.5
after that i used recovery with 400M and coredroid rom.
maybe its importent to tell that in the recovery and in the boot animation and pics there is no problam.
Click to expand...
Click to collapse
I hope that 150 MB for recovery is wrong! Your recovery partition should only be 7-10 MB!
Further you said 400 MB - is that the system partition? Are you planning to use DataOnEXT?
Make sure you set partition sizes correctly for the ROM being installed. If you have the space make the system partition 20-100 MB larger than minimum recommended in case you have bad blocks.
Hanging at boot animation can be a sign of insufficient free space in system or data partition or corrupt binaries.
This is one of the few times I might recommend a Task 29 to start clean.
---
Don't walk behind me; I may not lead. Don't walk in front of me; I may not follow. Just walk beside me and be my friend. (via Tapatalk)
hi,
i already use the task29 to delete all.
i used recovery 400 because i use ext partition with coredroid rom that use sens3.5.
after flashed wm from the start, i return to spl 2.08.
i preffer to back to wm , so if someone can help with that it will be the best.
the phone stuck after flash with the htc white screen
r 2.15.50.14
g 15.42.50.1 1u
d 3.14.04666
mayb this will help you to help me
I think you're confusing the /system partition and the recovery partition. You should change the /system partition to whatever is needed by the ROM but leave the recovery partition the same. The easiest thing to do is follow what both of the above posts say and flash a slightly larger than needed partition to account for any bad blocks by using the HD2 toolkit.
If you want to flash back to WinMo then just flash the Stock RUU from the bootloader. You shouldn't need HSPL to do this (AFAIK) but I'd flash HSPL2.08 just in case. As Marvlesz said, I also don't see anything wrong with your steps. If that doesn't work, try flashing a stock ROM from the SD card (google it).
ny_limited said:
I hope that 150 MB for recovery is wrong! Your recovery partition should only be 7-10 MB!
Further you said 400 MB - is that the system partition? Are you planning to use DataOnEXT?
Click to expand...
Click to collapse
Nigeldg said:
I think you're confusing the /system partition and the recovery partition. You should change the /system partition to whatever is needed by the ROM but leave the recovery partition the same
Click to expand...
Click to collapse
He's probably referring to the old recovery packages. The 150mb, 250mb and 400mb. Hence the old recovery version(?)
Marvlesz said:
He's probably referring to the old recovery packages. The 150mb, 250mb and 400mb. Hence the old recovery version(?)
Click to expand...
Click to collapse
Yeah I think ny_limited is pointing out the fact that he said 'recovery partition' when he meant 'system partition'. The old recovery version shouldn't matter, I still use the old packages and edit the flash.cfg and all ROMs I try work fine for me.
Luckycookies said:
i preffer to back to wm , so if someone can help with that it will be the best.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Depending on what you have used (HSPL 2 or 4) make sure you are set on either 1.66.000 SPL (HSPL2 file) or 2.08.000 (HSPL4 file).
Make sure you have the original Stock ROM/SPL for your appropriate HD2 - there probably are others but these are the ones I can find quickly at the moment:
T-Mobile Stock ROM/SPL
ELL HTC HD2 Stock ROM/SPL
French HTC HD2 Stock ROM/SPL
NLD HTC HD2 Stock ROM/SPL​
Extract the .zip file the ROM comes in (if it comes in one).
Plug your phone in via USB.
Sync it with ActiveSync or Windows Device Center 6.1 and wait for it to finish.
Double click the .exe file inside the folder we extracted earlier.
Follow the prompts and wait for it to finish flashing.
Once it is done, click ok, close the program, and reboot the phone.
If all goes well that should bring you back to Windows Mobile...
already flashed a lot of roms in the last 48 hour with any method.
sd, treecolor bootloader, android, wp7.
wp7 work, android stuck when it finish loading system, winmo stuck when it in the htc screen with red letters in the left corner.
i did try with nativesd and same same.
all installs finish sucessfully.
hspl 2.08, 3.03, 1.66 everything :|
full wipe before.
wp7 works well so its not a hardware problem.
full phone details:
SKU,HTC,English-WWE,GBR,RigidGray,w/oSIM Lock,LEO-C9#EMEA
UNITED KINGDOM
vergin phone
i am desperate
someone ? :\
Luckycookies said:
already flashed a lot of roms in the last 48 hour with any method.
sd, treecolor bootloader, android, wp7.
Click to expand...
Click to collapse
Any ROM is flashed through the "treecolor bootloader", and if you can't flash your original WinMo through SD, there might be a "big" problem.
Luckycookies said:
wp7 work, android stuck when it finish loading system, winmo stuck when it in the htc screen with red letters in the left corner.
Click to expand...
Click to collapse
Explain further, what do you mean byt "android stuck when it finish loading system"? You mean you can see the setup wizard/lock screen but then your screen becomes unresponsive? Or you get bootloops? Or Everything force closes? What is "stuck" exactly?
Luckycookies said:
i did try with nativesd and same same.
all installs finish sucessfully.
hspl 2.08, 3.03, 1.66 everything :|
Click to expand...
Click to collapse
Did you REALLY try nativeSD or you're just adding it to your thread without knowing what it is? Because NativeSD should have worked unless your device has a hardware issue or your setup was incorrect
You don't need HSPL to flash windows mobile, and MAGLDR doesn't work on other than 2.08.HSPL, so why flash 3.03 and 1.66? Just flash the 2.08 and stick to it.
Luckycookies said:
full wipe before.
wp7 works well so its not a hardware problem.
Click to expand...
Click to collapse
Not necessarily, but if it's not, then you must be doing something wrong you're not telling us about .
Luckycookies said:
full phone details:
SKU,HTC,English-WWE,GBR,RigidGray,w/oSIM Lock,LEO-C9#EMEA
UNITED KINGDOM
vergin phone
i am desperate
Click to expand...
Click to collapse
You can try this method: http://forum.xda-developers.com/showthread.php?t=1633243
Even though you don't have fatal hit, you can't flash anything (as you say)
I still can't understand how you can flash MAGLDR, CWM and WP7 yet you can't install Windows Mobile.
Are you sure that everything installs successfully?
yes im sure that everything install successfully...
ill try it later today thanks
hi,
this method not work to.
any other ideas? :\
when i flash android with magldr its complete. when i start config the screen fade to a blank.
computer still recognize the hd2 , charge led display and buttons led 2.