I am poking around the latest official OTA update (get it here).
I am trying to see if there is anything useful for aftermarket roms. I will post
here my findings, if any, and all the questions that pop to my mind. Hopefully
someone in the community will have answers.
The updating script does the following:
1) several checks on bootloader/recovery/cid/device version
2) copy fotaBoot to /data/system/fotaBoot to trigger some changes at reboot
3) checks on files to be patched
4) delete several files from /data (notably adio_checksum, DxDr,
SuplRootCert_injected)
5) delete lots of files form /system
6) apply patches
7) copy files into /system
8) set permissions
9) flash firmware.zip via
Code:
write_firmware_image("PACKAGE:firmware.zip", "zip");
Among the files being modified there are a couple of firmwares (yamato_pfp.fw
yamato_pm4.fw). I do not have them on my system (I run CM7) and I have no idea
which piece of hardware they refer to. There is also an app whose purpose I
ignore (HTC-DPM-GB-2.3-48637-11.1.apk) and a mysterious recovery.img in /system
(more on this later).
Does anyone know the exact procedure by which firmware.zip is flashed? Will any
check be performed on it? Its content is the following:
* android-info.txt: ASCII file with some version numbers.
* boot.img: should be the new kernel+ramdisk; I tried booting it with few
expectations and indeed it wont boot with a non-sense /system
* hboot_8x60_DOT_1.45.0013_20111121_signedbyaa.nb0: the new bootloader; I see no
reason to flash this unless it provides some new features.
* radio.img: fat image with radio files (should be safe to flash)
* rcdata.img: ???
* recovery.img: this won't boot; may it require the above mentioned recovery.img?
Anyway this is completely useless
* rpm.img: ???
* sbl1.img: ???
* sbl2.img: ???
* sbl3.img: ???
* tz.img: ???
Anyone has ideas on what the other files are? I assume that if we avoid flashing
hboot we will always have fastboot available to us and S-OFF to flash anything
we would like to, correct? Revolutionary team can you please explain how you
make the phone S-OFF once your exploit gives you the right privileges? Will any
of those files affect it? Has anyone here any idea of which partitions should
they be flashed to?
As I said I tried to boot both recovery.img and boot.img to get a config.gz and
kernel version with scarce success. I'd like to see whether they made some modifications to the
kernel which improved battery life. I think I will repack the new kernel with
CWM recovery and get the info from there.
Ideas of things to poke at? Comments? Helpful insights?
Related info: here .
sbl*.img might be the boot loader. (secured/secondary boot loader???) but why in 3 separate chunks?
More info: here
rcdata.img is text; it should be the configuration of the radio but if I check the content of the corresponding partition (mmcblk0p18) on my phone there is a lot of binary junk together with the small amount of text. The options are the same except for one (AGPSNVSetting) that is missing in the updated rcdata.img
Code:
# cat /dev/block/mmcblk0p18 | strings | tail -n 9
QCT_UMTS_RADIO_VER=1
DisH=2
AGPSNVSetting=1
EnDTM=0
MSCMode=10
HSDPACat=10
HSUPACat=6
GEA3=0
QCT_UMTS_RADIO_END=1
I know probably the biggest request from the community is to figure out how to root the update; it seems that the Rev. team has been notified that the exploit they used before seems to have been patched in this update.
Also very profitable would probably be zips for the new kernel and radio, if possible. Early reports have indeed been of better battery life, and also higher quadrant scores.
Anyway, many thanks for this thread, and for looking at the update
Etn40ff said:
Among the files being modified there are a couple of firmwares (yamato_pfp.fw
yamato_pm4.fw).
Click to expand...
Click to collapse
Just a shot in the dark, but Yamato is refered to here:
http://code.google.com/p/synergy-ki.../system/etc/adreno_config.txt?spec=svn41&r=41
It seems to have something to do with the adreno chipset...
There's a Pre Rooted Version of the OTA Update on Rootzwiki. I would imagine those on XDA would be rooted all ready. I understand trying to find a way to Root the OTA Update for those who had it before they could root. But wouldn't a simple Temp Root, then Downgrade work? That's what I had to do with my G2 and G1.
Sent from my MyTouch_4G_Slide using xda premium
Litesorrows said:
There's a Pre Rooted Version of the OTA Update on Rootzwiki. I would imagine those on XDA would be rooted all ready. I understand trying to find a way to Root the OTA Update for those who had it before they could root. But wouldn't a simple Temp Root, then Downgrade work? That's what I had to do with my G2 and G1.
Sent from my MyTouch_4G_Slide using xda premium
Click to expand...
Click to collapse
the version on Rootzwiki isn't the newest update, the one that just came out 3 days ago. and the newest update has proven impervious even to temp-root so far. the only way to downgrade is if you were S-OFF before updating. there is a thread on this in the general section.....
If you updated, please view this thread.
http://forum.xda-developers.com/showthread.php?t=1405859
I had pulled the new google talk app and made it flashable on request, here's the link:
Gtalk update
There are a couple others if anyone wants them - deskclock, wifi calling, t-mo mall and carbon backup, netflix, and two logging utilities.
The rest is all small updates to a lot - what I wanted to look into first were the GPS updates to make sure my patch stays as current as possible.
You can either pull apart the package directly, or flash the update and do an adb pull to grab new stuff - backup guide in my sig tells you all about using the adb pull command.
Now that we know you can rewind the changes and get root back after the update, either should be fine. I've been going through the download zip, but haven't had much time at my workstation.
I have a couple emergency shifts to work, kept me offline yesterday & today, I'll check back on a break later and see if I have anything else to add.
Sent from my Bulletproof_Doubleshot using xda premium
Blue6IX said:
I had pulled the new google talk app and made it flashable on request, here's the link:
Gtalk update
There are a couple others if anyone wants them - deskclock, wifi calling, t-mo mall and carbon backup, netflix, and two logging utilities.
The rest is all small updates to a lot - what I wanted to look into first were the GPS updates to make sure my patch stays as current as possible.
You can either pull apart the package directly, or flash the update and do an adb pull to grab new stuff - backup guide in my sig tells you all about using the adb pull command.
Now that we know you can rewind the changes and get root back after the update, either should be fine. I've been going through the download zip, but haven't had much time at my workstation.
I have a couple emergency shifts to work, kept me offline yesterday & today, I'll check back on a break later and see if I have anything else to add.
Sent from my Bulletproof_Doubleshot using xda premium
Click to expand...
Click to collapse
could i get deskclock, wifi calling, and netflix
Yamato is gpu proprietary files. U would use them in a compile against source code for the improvements. I would say kernel fixes would be the main thing if reports are better quadrant and battery life
Sent from my MB525 using XDA App
I flashed the t-mobile signed stock rom PP59IMG.zip through the bootloader then proceeded to download the OTA's. After that I placed the new recovery image in the appropriate place and rebooted bootloader to prepare pushing the recovery through fastboot. What I noticed is that even after installing the OTA in a unrooted totally stock rom, S-off remains, however where "revolutionary" once was written now displays "**Locked**" , so apparently HTC has managed to relock the bootloader even though it shows S-off. It's not totally locked, as I had to reflash the PP59IMG.zip to downgrade hboot again so that I could reuse the revolutionary tool to flash the 4.0.0.8 recovery, then install CWM to update the recovery. As long as "Locked" was sitting where "revolutionary" normally is, I found it impossible to use fastboot, so my guess is security remains off but fastboot is locked. Just my guess anyway.
Where did you get the stock/signed T-Mo PP59IMG.zip? Can't find it anywhere here. Thanks.
monakh said:
Where did you get the stock/signed T-Mo PP59IMG.zip? Can't find it anywhere here. Thanks.
Click to expand...
Click to collapse
Link in quote below:
yogi2010 said:
sure Blue, it is pretty much the usual...
To undo the update/restore the stock firmware that came with the phone:
(Note: this will only work if you are still S-OFF even tho you have the new HBOOT version. If you are S-ON with the new HBOOT, then at this time there is no known way to revert... hopefully we can get the devs. of Revolutionary, etc, to update the root methods. Also, if you want to update just to check it out, make sure to turn S-OFF first if you'd like to give yourself the option to revert later.)
1. Download the stock firmware package from here: http://forum.xda-developers.com/showthread.php?t=1178082
2. Rename it PG59IMG.zip and put it on the root of your sdcard.
3. Boot into the bootloader('adb reboot bootloader' or power down the phone then hold volume down + power), let it read the update package, and press 'volume up' to update when prompted.
4. At the end it will prompt you to press Power to reboot. It scared me because when i pressed Power, the screen went off and seemed to not come back on, so i pressed power once again, and it booted into the system.
That's it! Just remember that if you do this, it will of course erase all your data... your phone will be like it was out of the box.
Click to expand...
Click to collapse
I'm not sure if this helps anyone, but here is the boot.img taken from my nandroid of the newest OTA ROM:
http://db.tt/GHfzWNIj
come to think of it, looks like you might already have this in the OTA zip... although this one is a bigger file...
Two questions:
1. How do you flash this update? When I click the HTC Update, it gave me the ~5MB update, however not the ~40MB one. So is there a way to manually flash it?
2. Is there a way to doing so without loosing the recovery and root?
Sinfamy said:
Two questions:
1. How do you flash this update? When I click the HTC Update, it gave me the ~5MB update, however not the ~40MB one. So is there a way to manually flash it?
2. Is there a way to doing so without loosing the recovery and root?
Click to expand...
Click to collapse
You can download the update and run it manually. I can't remember if I renamed it update.zip and flashed it through stock recovery or used the bootloader.
If it was the bootloader, rename the downloaded zip to PG59IMG.zip, put it on the root of your sdcard and boot into the bootloader. The device's screen should prompt you with install instructions.
As for keeping root and recovery, no. As long as you are S-OFF *before* doing this, however, you can re-flash a custom recovery and re-root using these instructions: http://forum.xda-developers.com/showthread.php?t=1433805
Yeah, the update flashed nicely thru the stock recovery. I learned once you get to the recovery screen, you press volume up + power to get the options to show up.
Related
All,
This rom is a rebuilt version of the latest Telstra AU ROM with GPS fix ( RUU_Bravo_Telstra_WWE_1.16.841.1_Radio_32.30.00.28U_4.05.00.11_release_126124_signed ).
I have removed all of the Telstra crap and added some useful apps. I have deployed it to my unbranded phone and it is working fine.
Changes from the standard ROM include:
- Removed all of the Telstra apps (except whereis... maybe next version )
- Added root access, of course
- Apps2SD included but not functional (you can get it to work by issuing adb commands)
- WiFi Tethering included. Will probably remove from the next version as it's a bit flaky.
- Changed the boot animation to the Nexus One anim
- Some additional apps such as:
3D Gallery
Car Home
Navigator
Voice Dialer
Others I inevitably forgot
To do:
- Figure out how to add APNs to the ROM
- Fix A2SD
Download link is in the next post.
Credit to:
Cyanogen for the Kitchen
Paul OBrien from MoDaCo for making the kitchen available
FeaRThiS for hosting the ROM
Enjoy!
IMPORTANT: READ FIRST
Flashing ROMs in general is a risky business. If you've never flashed a non-standard ROM before, I suggest you read about and understand the method before you even consider downloading this. I take no responsibility for any issues that may be caused by this ROM. Use it at your own risk.
I also suggest you read here and note any known issues and changes for new versions.
You must have a rooted handset to be able to flash this ROM. Head over to MoDaCo, or search XDA for guides on how to root your phone.
To flash this ROM to a rooted handset, follow these instructions:
BEFORE YOU START
Copy the zip file to the root of your SD card.
Method A:
1a) Power on your phone, holding the VOLUME-DOWN button until you see the HBOOT menu
2a) Use the VOLUME buttons to navigate to the "Recovery" option and select it using the POWER button
....continue from step 3 below.
Method B (quicker but requires SDK)
1b) Boot up your phone and connect it to your PC via Micro-USB cable
2b) Execute 'adb reboot recovery' form the tools directory of the Android SDK
....continue from step 3 below.
3) Once you see the red triangle (of death ) connect your phone to your PC using the micro-USB cable
4) Go to the 'pushfiles' folder that came with the root-kit from MoDaCo.
5) Execute ./recovery-linux.sh (Linux), ./recovery-mac.sh (OSX) or recovery-windows.bat (Windows) and wait for the recovery menu to load.
6) Use the TRACKBALL to navigate to the Wipe option. Select Wipe by clicking the optical trackball. Do a System wipe, followed by a cache wilpe and finally a dalvik-cache wipe (each of the first three options). Once complete, press the VOL-DOWN button to return to the main menu.
7) From the main menu select FLASH ZIP FROM SDCARD, select the ROM zip file, confirm flash.
8) Once flashing is complete, select REBOOT from the menu.
9) Enjoy your uncluttered handset
DOWNLOAD HERE:
http://79.170.44.128/r3volutionary....ra-free-skitzandroid-signed_050610_214824.zip
Thanks to FeaRThiS for hosting!
Alternative downloads:
http://uploading.com/files/631d4617/hellstra-free-skitzandroid-signed_050610_214824.zip/
Thanks to lucus30
http://www.deswong.com/android/
Thanks to deswong
Changelog
=======================
Issues:
=======================
- Titanium Backup not working. Its not included in the ROM but just thought I'd mention it It complains about not being able to get root access whereas every other app that requires root access works fine so far. Downloading busybox through TB causes a FC.
- Some people are getting the A2SD infinite boot loop issue (next version will definitely not include A2SD as you can add it yourself if you want it).
You can get out of the loop by doing:
Code:
adb reboot recovery
from the SDK tools folder on your PC to get back to the recovery menu.
You can also do 'adb shell' and then issue the command 'a2sd' from the shell but I wouldn't advise it. It will boot up 'normally' but it's not a permanent fix.
==================
reserved for changelog
Uploading link
http://uploading.com/files/631d4617/hellstra-free-skitzandroid-signed_050610_214824.zip/
Nice one!!
I'm yet to root my phone and WILL get to it in good time.
When I do, I'll give this one a flash.
Thanks for your work.
Death to all the Hellstra visual bloatware scum that crapped up the original ROM (stupid splash screen Tel$tra ding noise especially)
new Link and I have PM'd you all of your FTP details
FeaRThiS said:
new Link and I have PM'd you all of your FTP details
Click to expand...
Click to collapse
Thanks FeaRThiS. Much appreciated!
I've also thrown it on my www as well.
http://www.deswong.com/android/
Hey guys,
Correct me if I'm wrong but for anyone with a Telstra set the problem is 2 fold?
1) we need to be able to Root the phone, Paul's latest 0800 root method will hopefully fix this
2) we need a ROM that incorporates the Telstra GPS fix whilst debloating the phone.
Does that mean that if we want to use GPS we are restricted to ROMs cooked with the GPS fix? or will any generic ROM do the trick (i.e. those from MoDOCO?
I am experiencing the pink AMOLED problem at low brightness and may have to replace the phone with another one. If I root the phone and flash this ROM, can I flash back the original ROM that I downloaded recently from HTC to restore it to the state it was when I bought it?
qubit76 said:
I am experiencing the pink AMBLED problem at low brightness and may have to replace the phone with another one. If I root the phone and flash this ROM, can I flash back the original ROM that I downloaded recently from HTC to restore it to the state it was when I bought it?
Click to expand...
Click to collapse
I dont think so. You could flash the original Telstra one back again but the recovery partition is wiped/messed around with as part of the rooting process. Have a look around Modaco and you'll find your answer - you're definitely not the first to ask.
negatron said:
Hey guys,
Correct me if I'm wrong but for anyone with a Telstra set the problem is 2 fold?
1) we need to be able to Root the phone, Paul's latest 0800 root method will hopefully fix this
2) we need a ROM that incorporates the Telstra GPS fix whilst debloating the phone.
Does that mean that if we want to use GPS we are restricted to ROMs cooked with the GPS fix? or will any generic ROM do the trick (i.e. those from MoDOCO?
Click to expand...
Click to collapse
The GPS issue was a software related bug from the shipped ROM, I read somewhere on here someone mentioning that they flashed the generic ROM and had GPS working before HTC/Telstra released the update
mwong1980 said:
The GPS issue was a software related bug from the shipped ROM, I read somewhere on here someone mentioning that they flashed the generic ROM and had GPS working before HTC/Telstra released the update
Click to expand...
Click to collapse
yeah the new Telstra ROM had the exact same GPS config as my unbranded one so the prolem was caused by Telstra meddling with things.... surprise surprise!
bcmobile said:
I dont think so. You could flash the original Telstra one back again but the recovery partition is wiped/messed around with as part of the rooting process. Have a look around Modaco and you'll find your answer - you're definitely not the first to ask.
Click to expand...
Click to collapse
Cheers bcmobile. So in your opinion am I correct in saying that it's better I wait until the screen problem is worked out (to return under warranty to Telstra from whom I bought it outright) before I go rooting the device?
well tried yrs BC
and now it boots to the htc logo ..and stays there
i've tried twice now.
i can get to recovery mode tho, something wrong with yr image maybe?
note in recovery mode ..down the bottom, it says " Build: not set"
note that i tried yrs after succesffulyy rooting via the latest method from paul, and, applying the radio update. neither got my gps working so i've tried yrs ..
http://android.modaco.com/content-p...h-hboot-0-80-and-os-to-1-21-support/page/340/
qubit76 said:
Cheers bcmobile. So in your opinion am I correct in saying that it's better I wait until the screen problem is worked out (to return under warranty to Telstra from whom I bought it outright) before I go rooting the device?
Click to expand...
Click to collapse
I've used three Desires and they all show the pink on low brightness so returning it under warranty won't help you.
ok, my phones working again, rerooted with pauls method.
but have no gps and i can't flash back to the telstra rom thanks to the radio updating my hboot to .80
same here guys. I rooted using Paul's latest method but gps stopped working. and when flashing this Rom it hangs at the white HTC screen. now back to Paul's rooted Rom. hope we fix the gps issue soon!
mitchello said:
I've used three Desires and they all show the pink on low brightness so returning it under warranty won't help you.
Click to expand...
Click to collapse
Thanks for your feed back. At the risk of hijacking this thread and double posting - My post on the AMOLED sticky.
In summary if you don't want to read my above post, I saw 2 phones 'in store' that did not have the pink issue.
[GUIDE] Root, flash a custom recovery and/or S-OFF your Desire HD the "easy" way!
PLEASE DO NOT HOST MY FILES ELSEWHERE ALSO REPORT ERRORS ABOUT IT HERE AND NOT IN ANY OTHER THREADS!
UPDATE: Uploaded a new version with a temporary fix for if not working properly on the latest OTA?
!!!WARNING!!!
ONLY flash the bootloader (HBOOT) aka "S-OFF" if you understand what it is, what it does, what it can do and how it can brick your phone if flashing it fails.
I can not be held responsible if your phone bricks, makes nukes drop from the sky and/or makes your wife pregnant.
Assuming you have the Android SDK (adb) in working order, some basic knowledge of how to use it and experience using the console for those cases something does go tits up.
=====
Requirements: Android Terminal Emulator (from market), the archive attached to this post and a way to extract it to your SD card (file manager, PC, etc).
VISIONairy+ r12 (or higher) is as of v0.5 ONLY needed for rooting your phone, if you already have root you can skip this!
Download and extract the archive to the root of your SD card and read the included instructions (RTFM.txt).
If the first and second MD5 sums match, HBOOT is flashed correctly.
If the first and third MD5 sums match, HBOOT is not flashed at all and your phone still works like nothing happened.
If the first does not match second or third, something went wrong and you should NOT reboot your phone but seek help on the forums here!
In the last case, you could first try the hboot script again if that doesn't work something went awfully wrong and you should report back here ASAP but whatever you do ... DO NOT TURN OFF YOUR PHONE
=====
Credits goto all who made this possible: Scotty, tmzt (eMMC write), Paul (MoDaCo) (VISIONairy+ root) and adwinp (first working S-OFF post).
(If I left some person out of it just sent me a message and I will correct it)
CHANGELOG (new to old):
Revised scripts.
Failproof way of making kernel module.
Added check to see if the kernel module actually loaded correctly.
Reworked the scripts, more fail and fool proof
Updated the check script to check the kernel module first.
Added scripts to flash/restore recovery.
Got rid of not found errors for good?
Reflected the error message from loading the module is actually ok, polished the first post and RTFM.
Changed the way md5sum is invoked, now trough busybox and this should work for people who had problems with "md5sum: not found".
Fixed a major typo.
Updated with versioning, corrected some textual output and added some extra info to RTFM.
Cleaned up the first post.
Changed hboot script to reflect the original MD5 sum.
Removed recovery, get it yourself.
Revised scripts to be more fail proof.
TODO:
Polish textual output properly.
Proper check to see if kernel module loaded or is loaded already.
Good morning
What recovery.img are you flashing in the process btw?! care to let us know?
since you take a backup of the original bootloader, maybe it would be handy to create a "revert" script also, where you flash back the original recovery and original bootloader in the event that we may need to you know...
the script would then go like this
Code:
dd if=/sdcard/DHD/hboot_orig.bin of=/dev/block/mmcblk0p18
dd if=/dev/block/mmcblk0p18 of=/sdcard/DHD/hboot_check.nb0
dd if=/sdcard/DHD/recovery_orig.bin of=/dev/block/mmcblk0p21
md5sum /sdcard/DHD/hboot_orig.bin
md5sum /sdcard/DHD/hboot_check.nb0
at least thats what i think... unless the file .nb0 and .bin matters in the if=-- of--- command
EDIT**
Read and check everything at least 4 times, ask before you reboot your DHD if unsure about absolutely anything. This process worked for me after some stupidity on my part.
Again, this works but CHECK everything step of the way.
afrcom15 said:
FFS guys, read this carefully and double check everything you do B4 you reboot.
I've ended up with a 450 quid paperweight.
Dunno what I can do, probably nothing
Click to expand...
Click to collapse
did that happen using this guys script? or another way?
im holding off flashing hboot till things are a bit more settled. its hard to resist though.
i have modified the script used by sfjuocekr (so that it doesnt flash the recovery, as I see no point in that at the moment) and would rather flash from fastboot
and the script works and I can confirm s-off success
I think it's safer doing it via the VISIONary method. That's how I.did mine, and zero issues. I don't like how this says don't reboot if the checksums don't match. That's just asking for trouble.
Sent from my Desire HD using XDA App
afrcom15 said:
FFS guys, read this carefully and double check everything you do B4 you reboot.
I've ended up with a 450 quid paperweight.
Dunno what I can do, probably nothing
Click to expand...
Click to collapse
Yeah too many people rush into dangerous stuff like flashing to hboot without understanding the risks properly. I was one of those people. I am very lucky that my flash went smoothly. Feel for you.
madindehead said:
I think it's safer doing it via the VISIONary method. That's how I.did mine, and zero issues. I don't like how this says don't reboot if the checksums don't match. That's just asking for trouble.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
actually, thats BS, excuse my french.
The checksum is an extra security measure implemented to verify that the data flashed and the data that should have been flashed remain integrity. this way, you can verify in 2 steps:
1. The file you downloaded is not currupted in any way
2. The file (bootloader) flashed has flashed correctly, prior to reboot.
so actually, it is something ON TOP of the usual scripts seen here to ensure you dont brick. I need to side with the creator here.
afrcom15 said:
FFS guys, read this carefully and double check everything you do B4 you reboot.
I've ended up with a 450 quid paperweight.
Dunno what I can do, probably nothing
Click to expand...
Click to collapse
Take it back to the shop saying it died and get a replacement :3?
Well I used this method and the checksums returned were both "not found" and everything started force closing, I started to accept the fact that my phone could be bricked, but on reboot I was fine!
Sent from my Desire HD using XDA App
does this work as reliably as the first method?
i modified the scripts and included 2 more tests as well as deleted the flash of the recovery.
I can confirm the pricinple works fine, but i didnt see the point of flashing the recovery i must say. as I will fastboot flash the recovery when we have a "proper" one
I've done the permaroot and deleted visionary, so when my phone boots up now it is rooted and i have access to setcpu and such and i can change it, like the sliders, i can also use other rooted programs too.
What benefits do i stand to receive if i perform this s - off root? please.
And from what i've said am i set to do this?
Thanks.
S-Off is needed for a custom recovery image and custom roms. Essentially it turns off the MMC write protection and signature checking permanently.
Sent from my Desire HD using Tapatalk
Thyrus said:
i modified the scripts and included 2 more tests as well as deleted the flash of the recovery.
I can confirm the pricinple works fine, but i didnt see the point of flashing the recovery i must say. as I will fastboot flash the recovery when we have a "proper" one
Click to expand...
Click to collapse
Where can the modified script be found?
There seems to be little take up on this so far, I guess because it's so risky still?
Andy,
I have composed a comprehensive how-to in german for my "home-forum" after testing it.... so not sure how useful it would be for you non-german speaking ppl. but here is the link for convenience
http://www.android-hilfe.de/root-hacking-modding-fuer-htc-desire-hd/53959-guide-permant-root-mit-austauschen-des-bootloaders-visionary.html
you can manually edit the script from the creator here and delete THIS line
Code:
dd if=/sdcard/DHD/recovery.img of=/dev/block/mmcblk0p21
to avoid flashing the recovery
Here's an update on my sorry situation
CPW say send it direct to HTC, there gonna know aren't they. Phone is completely dead, no options left I'm afraid.
afrcom15 said:
Here's an update on my sorry situation
CPW say send it direct to HTC, there gonna know aren't they. Phone is completely dead, no options left I'm afraid.
Click to expand...
Click to collapse
a) Send it to HTC, they fix it for free
b) Send it to HTC, they fix it and charge you
c) Send it to HTC, they say they won't fix it
afrcom15 said:
Here's an update on my sorry situation
CPW say send it direct to HTC, there gonna know aren't they. Phone is completely dead, no options left I'm afraid.
Click to expand...
Click to collapse
Statutory consumer rights may come into play here my boy. I know that you broke it, but if you're comfortable with lying to them then I suggest you bring this up:
The retailer’s obligations
If there is an obvious fault with the item at any time within the first 6 months and it has not been caused by wear and tear or misuse, your first port of call must be the shop you bought it from. They have the responsibility to put the matter right, and should not evade this responsibility by referring you to the manufacturer in the context of a guarantee or warranty.
EDIT: This is one of the main reasons I take out insurance on my phones. If it breaks, tell them you lost it. Technically still lying but I'm paying for the privilege of that lie, and I have never had to lie to them.
Well I switched to S-OFF to get a new splash screen and now I can no longer install OTA updates for my Hero. I get a signature failure every time I try to install. Does anyone know how to switch this back on? I didn't realize this would kill the ability to do updates as the forums I have read before switching didn't have any mention of it.
Sorry if this has been previously posted and I missed it in the forums.
Any help would be greatly appreciated.
awnorwood said:
Well I switched to S-OFF to get a new splash screen and now I can no longer install OTA updates for my Hero. I get a signature failure every time I try to install. Does anyone know how to switch this back on? I didn't realize this would kill the ability to do updates as the forums I have read before switching didn't have any mention of it.
Sorry if this has been previously posted and I missed it in the forums.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
The signature failure isn't from s-off it's from the custom recovery. What you need to do is to resign the zip.
awnorwood said:
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Just an added note, as far as I know, you can't switch back to S-ON on this
device, at least, not at the moment.. If they get S-ON to work on these phones,
good, but if not, I'm not overly concerned.
http://forum.xda-developers.com/showthread.php?t=759955
and
http://unrevoked.com/rootwiki/doku.php/public/forever
for details..
Asadullah said:
The signature failure isn't from s-off it's from the custom recovery. What you need to do is to resign the zip.
Click to expand...
Click to collapse
Not sure I'm understanding the question. But, if he means receiving updates directly from Sprint then they don't come as zip files. So, how would signing anything help him?
Not sure why you would want to download something from Sprint directly anyway. Whenever an update comes out, they're usually packaged and ready for you to flash via custom recovery by the end of the day if not sooner.
mercado79 said:
Not sure I'm understanding the question. But, if he means receiving updates directly from Sprint then they don't come as zip files. So, how would signing anything help him?
Not sure why you would want to download something from Sprint directly anyway. Whenever an update comes out, they're usually packaged and ready for you to flash via custom recovery by the end of the day if not sooner.
Click to expand...
Click to collapse
The ota (over the air) updates that sprint pushes out and you download are stored in an update zip in /cache then when you choose to install them they are flashed through the stock recovery... but if you don't have the stock recovery you will have to pull the update from your device resign it and then flash it through custom recovery. Also they won't work on anything but a stock or close to stock rom because of the checks it does in the update scripts and most of everything inside is .p files (patch).
I should know because I took the second to last sprint update rooted it and posted it on here. You can actually test this theory by running the ruu rooting it and then when you get an update download it but don't install it right away. You'll find it in /cache (I believe forgotten exactly) or just take my word for it.
If you do do it like that I suggest the original 2.1 ruu just because you'll get your original radio back in the process
Asadullah said:
The ota (over the air) updates that sprint pushes out and you download are stored in an update zip in /cache then when you choose to install them they are flashed through the stock recovery... but if you don't have the stock recovery you will have to pull the update from your device resign it and then flash it through custom recovery. Also they won't work on anything but a stock or close to stock rom because of the checks it does in the update scripts and most of everything inside is .p files (patch).
I should know because I took the second to last sprint update rooted it and posted it on here. You can actually test this theory by running the ruu rooting it and then when you get an update download it but don't install it right away. You'll find it in /cache (I believe forgotten exactly) or just take my word for it.
If you do do it like that I suggest the original 2.1 ruu just because you'll get your original radio back in the process
Click to expand...
Click to collapse
Good information to know. Thanks Asadullah.
OUT OF DATE USE THE ONE CLICK 1.85 ROOT TOOL IN THE FORUMS
As the ROM chefs go to work, we want to be sure that we are ready to flash the ROMs when they come to be available! This guide will help you set up your phone so that you can flash custom ROMs.
After this process you will have a phone on the latest firmware (1.85 at the moment) with bootloader unlock, rooted, and busybox installed.
This guide assumes you are on a root friendly firmware (as of now, it is firmwares 1.82.502.3 and below).
This is really going to be done in a four step process. First we need to root the device in order to access the place where the CID is stored so that we can change it and get unlocked. After changing the CID, we can unlock via htcdev.com. Then we can go on to installing a custom recovery and finally rooting!
From there I will give you some tips on installing ROMs.
NOTE: THIS PROCESS IS EXTREMELY DANGEROUS. IT MAY BE A BIT CONFUSING. READ OVER THE STEPS BEFORE STARTING. IF YOU DO NOT THINK YOU WANT TO RISK YOUR DEVICE BECOMING A BRICK THEN DO NOT ATTEMPT THIS. THIS VERY EASILY COULD RUIN YOUR DEVICE.
BACKUP EVERYTHING BEFORE STARTING AS EVERYTHING ON YOUR DEVICE WILL PROBABLY BE WIPED.
I, XDA, AND THE ORIGINAL TOOL CREATORS DO NOT TAKE RESPONSIBILITY FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. IT IS SOLELY YOUR RESPONSIBILITY FOR WHAT YOU DO TO YOUR DEVICE.
Click to expand...
Click to collapse
Your warranty will be void if you unlock the bootloader. If you just root though then you can return to 100% stock by running the RUU.
This guide is for Windows only at the moment though I will try to post Mac and Linux guides at some point.
ORIGINAL TOOL THREADS:
One Click Root for 1.82 and below: http://forum.xda-developers.com/showthread.php?t=1644167
Spoof CID Script: http://forum.xda-developers.com/showthread.php?t=1672284
I will try to keep this as up to date as possible! Taking a visit to the index of the development forums (http://forum.xda-developers.com/showthread.php?t=1671237) is also a good idea!
Last Updated: 5/28/12
0. Getting the prerequisites:
Download the package at the bottom of the first post to get started.
Extract the package somewhere you will remember (like on your desktop).
Connect your device via USB and make sure you have USB Debugging enabled under settings.
Click to expand...
Click to collapse
1. Root your device
1. Open the folder you downloaded and navigate to the "root" directory.
2. Double click on the root-windows.bat file
3. Let the root run and do not touch your device. It will reboot several times- do not touch it or you may brick your device. Just let it do its thing and eventually after around 3 minutes you will have a rooted device in your hand.
Click to expand...
Click to collapse
2. Get the unlock token
In order to unlock the bootloader we will need to change a value called the CID. This will allow the htcdev.com site to unlock our phones.
1. Go to the downloaded folder and go to the "change_cid" folder.
2. Click on the "Spoof-CID.bat" file. Follow the instructions. Your CID will change from CWS__001 (stock AT&T CID) to 11111111 (called "SuperCID," will allow you to flash anything)
3. Log in to htcdev and go here: http://www.htcdev.com/bootloader/unlock-instructions (NOTE: This skips the agreements you need to click through as some of the buttons on their website are wonky. Doing this assumes you agree to their policies that are listed there)
4. Follow the instructions very carefully (they are written very well) untill the point where you get the file "Unlock_code.bin" via email. Stop there.
5. You should now have the file for bootloader unlock. MAKE SURE TO SAVE THAT FILE "Unlock_code.bin" TO THE "generic" FOLDER IN THE PACKAGE YOU DOWNLOADED! YOU WILL NEED IT LATER.
Click to expand...
Click to collapse
3. Run the RUU to update to latest firmware
1. Download the latest RUU from the xda forums (should be an .exe file)
Currently it is version 1.85.502.3 and you can download it here:
http://briefmobile.com/download-htc-one-x-att-1-85-update
2. Follow its instructions very carefully. It will take approximately 20 minutes to complete. BE PATIENT. IF YOU UNPLUG YOUR PHONE HERE YOU WILL GET A BRICK.
3. Let your phone reboot and go through initial setup again
Click to expand...
Click to collapse
4. Unlock your bootloader using Unlock Token
1. Navigate to the "generic" folder in cmd (you should have added the Unlock_code.bin file to this folder already) and plug your phone in in fastboot mode. To do this, first shut off your phone. Wait for it to turn off. Then hold the volume down button. Press the power button for 3 seconds while still holding the volume down key. Let go of the power button but keep holding the volume down button untill you see a white screen with a bunch of small text on it. Use the volume up and down keys and the power button to select the FASTBOOT option. Plug your phone into your computer. Then wait for the FASTBOOT text to turn into FASTBOOT USB.
2. Type the following into cmd on your computer:
fastboot flash unlocktoken Unlock_code.bin
NOTE: This step might take quite a few tries. For some it works on the first time. For others, it may take around 20 times. Just keep typing in the command until you get a sucessful flash. We aren't sure why it does this at the moment but just keep trying and don't give up.
3. Use the volume keys to say that you do want to unlock your bootloader and wait for reboot
4. Bootloader should be unlocked! Congrats, most of the grunt work is done! Go to Settings - Developer Options - Enable USB Debugging. This will allow us to continue
5. Re-set up phone and enable USB debugging again
Click to expand...
Click to collapse
5. Install a custom recovery so that we can gain root access
1. Currently there are two recovery options: ClockWorkMod Touch and TWRP (TeamWinRecoveryProject). Both are pretty much the same as they both use touch input but TWRP does have some other nice features like a built in file browser and more. It is also more touch optimized. ClockWorkMod is more "old school" and I personally feel more comfortable using it, but using TWRP is fine as well. It doesn't really matter which recovery your choose, both are good choices. Download whichever one you want below:
CWM Touch: http://forum.xda-developers.com/showthread.php?t=1677304
TWRP: http://forum.xda-developers.com/showthread.php?t=1677447
2. Drag the .img recovery file you just downloaded into the "generic" folder
3. Connect your phone via fastboot
4. Type the following:
fastboot flash recovery <insert name of recovery .img file here>
Replace the stuff between the <> with the name of the file you just downloaded
5. Wait for your device to reboot. Then type into cmd which is cd'ed to the "generic" folder:
adb reboot recovery
6. Make sure your recovery works as soon as it is done loading and then press "reboot system"
7. Follow its instructions
Click to expand...
Click to collapse
6. Root your system
1. Connect your phone as a "Disk Drive" and drag the "root.zip" file in the "root" folder to your phone's memory
2. Reboot into recovery with the adb command (adb reboot recovery)
3. Go to install zip from sdcard and navigate to the zip file you downloaded. Say "yes" and watch it flash
4. Reboot system now
5. Go to the play store and download any app that has "Busybox installer" in its name (the one by JRummy16 works good I believe)
Click to expand...
Click to collapse
If all goes well, you should be sitting at an AT&T HTC One X which is on the latest RUU leaked firmware (1.85.502.3 at this moment), rooted, busyboxed, and unlocked.
Congrats!
If you want to flash any ROMs, download the .zip file of the ROM, place it on your phones memory, and then install the zip like you did to the root.zip file.
Enjoy your AT&T HTC One X!
CREDITS:
kennethpenn: For initial root, getting all the RUUs from the "source" and for giving the HTC One X's situation prime press appearance on his website, BriefMobile.com
grankin01: For finding out how to edit the CID originally
designgears: For creating the One Click Super CID tool for bootloader unlock
paulobrien: For porting CWM Touch to our device
sk08: For leading the way in terms of MODs and organizing an S-OFF thread to get this thing fully ours
JSLEnterprises: For initially being there to help organize a bootloader unlock
Team Nocturnal: For their awesome ROM
Click to expand...
Click to collapse
If you want to thank or donate to someone, please do not do so to me. The people above are the ones that deserve the thanks and the donations to encourage them to keep doing the fantastic work they have been doing! I'm just a high school student
Some common terminology:
Deoxdexed: OEMs package their apps with .odex files because they are more optimized for your device. However, this makes the file uneditable by developers and things like mods cannot be used with odexed ROMs. A ROM with "deodexed" as a feature means it is easier to use mods with that ROM
Busybox: A collection of linux tools that are helpful for flashing ROMs and doing other basic Android tasks
RUU: ROM Update Utility, made by HTC, completely reflashes device firmware, useful if you get bricks. Only for Windows.
Root: Allows you to edit system level files
S-OFF: (currently unattainable) Security-OFF, it is a "feature" in HTC phones that allows us to modify almost any part of your system.
Unlocked Bootloader: Allows us to flash custom images to the device.
Click to expand...
Click to collapse
As I understand and appreciate the work put in this thread, do we need another how to? Using the index sticky alone anyone should be able to root/unlock/flash their device. There's already scripts for everything and virtually no ADB required for nubs.
I would assume with the other info already in this section if someone can't figure out how to flash their phone, then they don't need to flash at all.
HydroSkillet said:
As I understand and appreciate the work put in this thread, do we need another how to? Using the index sticky alone anyone should be able to root/unlock/flash their device. There's already scripts for everything and virtually no ADB required for nubs.
I would assume with the other info already in this section if someone can't figure out how to flash their phone, then they don't need to flash at all.
Click to expand...
Click to collapse
Wasnt sure, there are still a few people asking how to do it since it is a bit complicated with the 1.85 update breaking root so I just compiled everything into a master one.
And yeah, I use a lot of the scripts in the package I put for download.
Anyway, mods do what you think with this thread! And this might be in the wrong section, wasnt sure if it goes in general or development.
Please keep this up. As it is the most aggregated list of instructions, I'm sure it will help many who have just gotten their phone. Great work by the way.
HydroSkillet said:
As I understand and appreciate the work put in this thread, do we need another how to? Using the index sticky alone anyone should be able to root/unlock/flash their device. There's already scripts for everything and virtually no ADB required for nubs.
I would assume with the other info already in this section if someone can't figure out how to flash their phone, then they don't need to flash at all.
Click to expand...
Click to collapse
As I agree with you, a "one stop shop" that can be pointed out to for the noobs who got their mommy's to buy them their cool phone should at least keep the redundant questions to a minimum.
you cant ruu WITH a UNLOCKED bootloader these directions are wrong there would need to be a relock step added in.
ALSO THE CWM STEP NEED A ROOT FOR IT TO WORK LOOK AT THE PAGES
READ UP ON THE STUFF BEFORE YOU MAKE A GUIDE BECAUSE THIS IS WRONG
squishy5 said:
you cant ruu WITH a UNLOCKED bootloader these directions are wrong there would need to be a relock step added in.
ALSO THE CWM STEP NEED A ROOT FOR IT TO WORK LOOK AT THE PAGES
READ UP ON THE STUFF BEFORE YOU MAKE A GUIDE BECAUSE THIS IS WRONG
Click to expand...
Click to collapse
Locked boot loader yes.
Root for cwm no.
Sent from my HTC One X using xda premium
squishy5 said:
you cant ruu WITH a UNLOCKED bootloader these directions are wrong there would need to be a relock step added in.
ALSO THE CWM STEP NEED A ROOT FOR IT TO WORK LOOK AT THE PAGES
READ UP ON THE STUFF BEFORE YOU MAKE A GUIDE BECAUSE THIS IS WRONG
Click to expand...
Click to collapse
Why don't you read before you comment on things like this?
I never "Unlock the bootloader"
I simply get the Unlock token from HTC.
So stop acting like you know everything, because you dont
Don't ever use caps with me and expect me to come back with a nice response. I put this out for the community, not for some kid who thinks he knows it all to come back and say that I did it wrong when he didn't even read the post properly.
And you don't need root to install CWM, just an unlocked bootloader.
Stop calling my stuff wrong if you yourself don't even know what is right
rohan32 said:
Why don't you read before you comment on things like this?
I never "Unlock the bootloader"
I simply get the Unlock token from HTC.
So stop acting like you know everything, because you dont
Don't ever use caps with me and expect me to come back with a nice response. I put this out for the community, not for some kid who thinks he knows it all to come back and say that I did it wrong when he didn't even read the post properly.
And you don't need root to install CWM, just an unlocked bootloader.
Stop calling my stuff wrong if you yourself don't even know what is right
Click to expand...
Click to collapse
He put his foot in his mouth, apology should be coming oh and Good job man, Good job. Thanks for the work, this should be a sticky.
This is a great write up and would have been extremely helpful last night. I will admit I have done a lot of reading before I unlocked the bootloader and updated to 1.85, but it was still very confusing at some points. The htcdev site actually gave me the most trouble because I didn't realize most of the steps were completed and I could skip all the way to entering the token and the site was simply used for entering the token and getting the unlock file.
And yes, I almost said the same thing about the relock step. I had to read it twice to realize you didn't unlock yet. That's another thing that confused me last night was unlocking/relocking immediately.
I think this should be a sticky and all the other tutorials and such should be deleted. This is a perfect summary IMO and will use it when I unlock my friends one x
Sent from my HTC One X
My problem with this is that you packaged it all up while the individual threads for each thing are updating and you are severing up potentially outdated scripts.
designgears said:
My problem with this is that you packaged it all up while the individual threads for each thing are updating and you are severing up potentially outdated scripts.
Click to expand...
Click to collapse
I agree. While it is nice to have a all-in-one, you should be linking to the threads since they are updating them on a daily basis instead of linking to their scripts. Ive already had to change JeepFreaks script this morning as he updated it. It would make your world a lot easier if you did it that way, and also not risk giving some new user outdated scripts.
I think this should go in the General section as the first few pages should redirect to the original threads anyway.
Red5 said:
I agree. While it is nice to have a all-in-one, you should be linking to the threads since they are updating them on a daily basis instead of linking to their scripts. Ive already had to change JeepFreaks script this morning as he updated it. It would make your world a lot easier if you did it that way, and also not risk giving some new user outdated scripts.
I think this should go in the General section as the first few pages should redirect to the original threads anyway.
Click to expand...
Click to collapse
Sure thing, I will add to the original post for the links.
Also I will try to keep this updated, but yeah I might not catch all the updates
Thank you so much Rohan! Really appreciate it! Took me about 4 hours to get this done but it was worth it. Now to install cleanrom. Thanks again. This is my first time doing something like this.
Duse ijuat saw this and I'm going to do this and flash clean from when I get home and I read through this I honestly love you for doing this it helps more than you think thanks a lot
Deffinitlet should be stickied
Sent from my HTC One X using XDA
These are the best instructions! Wish i had them when all this shenanigans started. Thx
ethantarheels123 said:
Please keep this up. As it is the most aggregated list of instructions, I'm sure it will help many who have just gotten their phone. Great work by the way.
Click to expand...
Click to collapse
I agree. This guide is very helpful for me. I consider myself to be fairly computer literate and have flashed ROMs on previous phones, but I am a complete n00b to android and linux. Looking around some of the other threads -- it appears to me that there are many people who could have much confusion resolved by reading this. Thanks for the thread.
-- Jon
Not quite sure what's going on with my update...
I'm using the exe that updates the RUU and it gets stuck on the "sending to phone" step. Reboots the bootloader once, gets stuck again (as far as I can tell , nothing is ever sent) and then gives me an error telling me "The ROM Update Utility cannot update your Android Phone. Please get the correct ROM Update Utility and try again"
i've got the correct drivers installed (was having some trouble related to that a couple days ago but have since figured it all out ) would it be better to just do the update manually? (On my evo you just change the update file to Update.zip and it automatically installs it for you when you boot into bootloader)
maybe I'll have to look into it further, but just curious if anyone's run into this issue or figured out how to get past it as of yet...
Edit: Just an update- I'm betting its because I forgot to relock my bootloader before updating. So anyone who's already completed SOME of the steps in the second post here, make sure you relock your bootloader if you haven't already done so.
Edit1.5: This assumption was correct and the bootloader is now unlocked.
Edit 2- Almost done here... Busybox wont install. Tried two different apps, neither one worked. No indication as to why (got very vague error messages to the effect of "busybox was not installed")
Edit 3- FIXED- Ok, figured it out. As far as I can tell, the process should be Root first, THEN install busybox. It doesn't work without root privelages (at least that was my experience here)
Hello XDA,
I am making a new thread because after browsing the web for 6 hours I feel dull and just want to have my own thread about it since none of the others describes my problem.
Preliminary details:
HTC Sensation XE RUU 4.0.3
Software number: 3.33.401.106
S-ON
Rooted
HTC Dev unlocked
ext4 recovery
Things tried:
- Remove SIM
- Delete wpa_supplicant.conf (could not do this.)
- Remove battery, boot into recovery, delete cache, start up, turn on airplane mode and then turn it off.
- Changing around settings. Pretty much any setting.
A few days ago there was an update from HTC. It was 68 MB. It was downloaded over wifi. I installed it, of course. I didn't have enough battery power so I put it in the charger and waited for a while until it did. By the time it did I wanted to install it. The phone rebooted and started up in ext4 recovery. Ext4 started working with the usual update animation and stuff like that. No errors as far as I could tell. It would reboot and start up. System update window appeared again right after I unlocked the SIM card. Same update, same question if I wanted to install it. I figured something must've gone wrong so I complied and let it do the update again. This went on for 5 times until I had enough and told it I don't want it to install the update. It deleted the update and I have never heard from it again. I tried to check for updates but none are found.
Then it struck me. There was no wifi... I checked the settings and all it says is Error. http://imgur.com/JTYSd
Turning it on will immediately switch it back to off. It never changes its state to anything else.
I am absolutely clueless as to why this is happening. None of the fixes posted on the web do anything.
Help, please?
P.S.: I like making my own threads for my problems because my problems tend to be different from the standard. This way a seperate specialized thread appears for a slightly different problem. I always document my steps and solutions. This way the internet will have another problem solved with decent documentation. This is to help future generations.
Datastreamx said:
Hello XDA,
I am making a new thread because after browsing the web for 6 hours I feel dull and just want to have my own thread about it since none of the others describes my problem.
Preliminary details:
HTC Sensation XE RUU 4.0.3
Software number: 3.33.401.106
S-ON
Rooted
HTC Dev unlocked
ext4 recovery
Things tried:
- Remove SIM
- Delete wpa_supplicant.conf (could not do this.)
- Remove battery, boot into recovery, delete cache, start up, turn on airplane mode and then turn it off.
- Changing around settings. Pretty much any setting.
A few days ago there was an update from HTC. It was 68 MB. It was downloaded over wifi. I installed it, of course. I didn't have enough battery power so I put it in the charger and waited for a while until it did. By the time it did I wanted to install it. The phone rebooted and started up in ext4 recovery. Ext4 started working with the usual update animation and stuff like that. No errors as far as I could tell. It would reboot and start up. System update window appeared again right after I unlocked the SIM card. Same update, same question if I wanted to install it. I figured something must've gone wrong so I complied and let it do the update again. This went on for 5 times until I had enough and told it I don't want it to install the update. It deleted the update and I have never heard from it again. I tried to check for updates but none are found.
Then it struck me. There was no wifi... I checked the settings and all it says is Error. http://imgur.com/JTYSd
Turning it on will immediately switch it back to off. It never changes its state to anything else.
I am absolutely clueless as to why this is happening. None of the fixes posted on the web do anything.
Help, please?
Click to expand...
Click to collapse
I remember reading in a thread that you need stock recovery (not 4ext) to do OTA updates. Maybe that's the issue.
That could indeed be the case. Would have to revert to it then... And somehow get the update back because it doesn't show up anymore when I check for it.
Would I need to need to rollback a backup to an older version?
Is there a recovery manager like Ext4 but one that can do OTA updates?
if you have the firmware update extract the boot.img and place it in the file of where is your adb
then do the commands from this thread in extra 1
http://forum.xda-developers.com/showthread.php?t=1631861
it might help you
i had the same issue as yours with my firmware update and i solved it using the extra 1 part of this thread
best wishes to you:good:
rzr86 said:
if you have the firmware update extract the boot.img and place it in the file of where is your adb
then do the commands from this thread in extra 1
http://forum.xda-developers.com/showthread.php?t=1631861
it might help you
i had the same issue as yours with my firmware update and i solved it using the extra 1 part of this thread
best wishes to you:good:
Click to expand...
Click to collapse
Where would I find the update on my phone? And IIRC the phone deleted the update. Could I just get a ROM image with the same version number and get the boot.img from that?
Datastreamx said:
Where would I find the update on my phone? And IIRC the phone deleted the update. Could I just get a ROM image with the same version number and get the boot.img from that?
Click to expand...
Click to collapse
download your firmware.zip,extract the boot.img from it and do the rest(place in the file with the adb is and do the commands)
i suppose it will work
edit:http://forum.xda-developers.com/showthread.php?t=1749789
rzr86 said:
download your firmware.zip,extract the boot.img from it and do the rest(place in the file with the adb is and do the commands)
i suppose it will work
edit:http://forum.xda-developers.com/showthread.php?t=1749789
Click to expand...
Click to collapse
I downloaded PG58IMG.zip from that post but it doesn't contain boot.img. :/ Is it in the ROM zip?
Edit: Been screwing around in terminal emulator trying to find out what I can. In the getprop I saw that my radio was out of date as well. IMO I should just flash the entire firmware.
Edit2: The ROM zip has a boot.img in it. Should I just flash that AND the firmware or just the boot.img?
Edit3: I downloaded the OTA update and it had firmware.zip in it with EVERYTHING. I'm just going to flash that. See what happens. How do I flash that? Ext 4 Recovery says it's a bad zip and can't open it.
Edit4: I noticed that firmware.zip contains a recovery.img. But I already have ext4 recovery. So do not want. I'll just only flash boot.img.
Edit5: Still can't get adb to recognize my device. I installed universal usb, checked development mode, checked unknown sources, restarted adb server, rebooted phone, mount unmount sd card, did the usb hardware id thing in adb_usb.ini. So strange. Again no solution on any thread.
Edit6: I applied the OTA manually by putting it on the SD card and then have it applied by zip through ext4 recovery touch. It gave a success message at the end so I'll let you know the results.
Edit7: No change. Applying it manually did nothing. At all. The version numbers didn't change and wifi still doesn't work.
i see the rom.zip has the boot.img
follow these steps
Put the"boot.img" in your "C:\Android" (or wherever your adb and fastboot are located)
Shift + right click in the white space on that folder
Select "Open command window here
Type in: adb
adb reboot-bootloader
Your phone will reboot, wait until you see a white screen which says "FASTBOOT USB"
Type in: "fastboot flash boot boot.img"
Wait until it's done flashing
Type in: "fastboot reboot"
if you have the same issue again see this
http://forum.xda-developers.com/showthread.php?p=21406675
best wishes to you!
rzr86 said:
i see the rom.zip has the boot.img
follow these steps
Put the"boot.img" in your "C:\Android" (or wherever your adb and fastboot are located)
Shift + right click in the white space on that folder
Select "Open command window here
Type in: adb
adb reboot-bootloader
Your phone will reboot, wait until you see a white screen which says "FASTBOOT USB"
Type in: "fastboot flash boot boot.img"
Wait until it's done flashing
Type in: "fastboot reboot"
if you have the same issue again see this
http://forum.xda-developers.com/showthread.php?p=21406675
best wishes to you!
Click to expand...
Click to collapse
ADB doesn't work for me right now so I'll try that when it does. Also that apk fix I've heard about before and is the permanent solution to removing the SIM card for wifi. So you don't have to remove the SIM everytime you want wifi. It was all about country codes for the wifi and sim doing something fudgy. Which mostly happens in India.
I live in Holland and when I tried that anyway as expected it did nothing.
I flashed boot.img from the rom and the problem persists. Nothing has changed.
Datastreamx said:
I flashed boot.img from the rom and the problem persists. Nothing has changed.
Click to expand...
Click to collapse
see then this thread,i don't know what else to think
http://forum.xda-developers.com/showthread.php?t=1469428
I'm back and I went screw it, I'm gonna fix this ****.
I did a factory reset and it didn't resolve it. So I just installed Cyanogenmod 9 stable. Wifi works now. So theoratically a RUU reinstall of the stock ROM would also work.