Develop Bugs

[TUTORIAL] How to S-OFF your HTC Desire

Hi there !
Many people here want to be S-OFF on their HTC Desire but don't know how to be, this thread is for you !
Credits goes to all AlphaRev developpers.
What is S-OFF ?
(Quotes from original AlphaRev website)
HTC implemented security on their newer generation phones. This flag, called @secuflag, controls whether your phone has
it's NAND or flash unlocked. Most noticeably, S-ON (security on) will read-lock your /system and /recovery partition, to name a few. Also, secuflag controls whether zip files being flashed through recovery or fastboot, are signed by HTC.
The now notorious S-OFF (security off) will disable this NAND security.
Since we are unable to access the Radio NVRAM itself (where secuflag is stored), we turned our attention to HBOOT.
Click to expand...
Click to collapse
For more informations about AlphaRev S-OFF, read the OFFICIAL Thread HERE.
There is many solutions to install S-OFF, this tutorial will show you few methods.
TRY AT YOUR OWN RISK ! I'am not responsible of bricked phone, for more help try the OFFICIAL Thread.
PREREQUISITES :
a ROOTed HTC Desire ROM with debugging option enabled on it.
a computer running Windows XP/Vista/Seven (32 or 64 bits), Linux, or Emulation via WMware etc.
a computer which can boot USB devices (for USB method only)
a branded USB Key 32Mb or more (for USB method) or a CD to burn (for CD method).
EASIEST method so far seems to be now by "Revolutionary" method.
Please check this out before trying solutions below (they are manual and maybe outdated, because I don't have the time keep updated this topic, moreover I don't own anymore a HTC Desire).
STEP-BY-STEP GUIDES :
.: USB METHOD :.
Be sure to Nandroid backup your device from recovery (just in case).
Download the latest Universal USB Installer or UnetBootin.
Download ISO Reflash Utility from AlphaRev website.
Install the software of your choice.
Open it, and select your USB device and your AlphaRev ISO freshly downloaded.
Create your bootable USB key.
Reboot your computer and boot on the USB key you freshly created.
Press any key to accept the disclamer.
Once you are in your ROM, plug your Desire with the USB cable on your computer.
/!\ DON'T TOUCH ANYTHING TILL YOU GET THE FINISH MESSAGE AT STEP 3 /!\
(Some users reports it can take over 1 hour. Passed this time, pull out the battery and reboot your phone).
The USB key method worked 100% for me, I personally installed my S-OFF exactly like that on my Desire.
.: CD METHOD :. (by jshields)
Clic HERE
.: VirtualBox METHOD :. (by Stewge)
Clic HERE
.: VMWare METHOD :. (by -V-O-Y-A-G-E-R-)
Clic HERE
Congratulations ! you are done !
Note : If for some unknown reasons you cannot access your Recovery anymore, it's normal, you must flash your Recovery using "fastboot" (SDK Android Kit must be installed on your running computer).
You have the choice between flashing a custom recovery like ClockWork one or put the original one but I sugger you the custom one which gives you much many more features
How to flash your recovery using ClockWork's image :
Download Clockworkmod 2.5.0.7 recovery image from official AlphaRev thread for bravo.
Move the file into "C:\android-sdk-windows\tools" (default sdk android folder's installation).
Verify MD5 checksum of the image with a freeware like HashCalc or something (IMPORTANT !).
Go to the main menu of your AlphaRev HBOOT (turn on your device with return button pressed).
Go to "FASTBOOT" mode.
Go to your computer and open a new terminal (Administrator privileges required if Windows Vista or 7).
Enter exactly this (without ") : "fastboot flash recovery recovery-clockwork-2.5.0.7-bravo.img".
Now you will have a ClockWork Recovery image installed and working
Note 2 : If your device freeze on boot logo, apply your Nandroid backup that your did before S-OFF.. that should do the trick.
If one day you want to S-ON your phone again, just reflash an original RUU rom !
Need supports ? all kind of questions must be posted on this thread directly. Be sure to read the whole thread (or at least 5 latest pages) before asking any question.
If you enjoy this guide, don't forget to rate it
{
"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"
}
stars, and clicking the
button (right below) is always appreciated to keep this thread maintained
LIKE MY WORK ?
OFFER ME A
!​​

Thank you so much, been waiting for this, will try it out later

nice tut but you can avoid installing anything, You can just use UnetBootin

Or CD version
1.download Alpha Rev.iso
2.burn .iso image to CD using a iso burning software eg. Power ISO
3.boot from CD eg. Hold F12 at boot
4.press the Legendary enter
TIPS connect USB when the CD has booted
Any problems just pm me
Sent from my HTC Desire s-off

Beaverman20 said:
nice tut but you can avoid installing anything, You can just use UnetBootin
Click to expand...
Click to collapse
It's nearly the same, you don't have to install universal usb installer, however, it is Windows-only.
Sent from my HTC Desire using XDA App

Really good work... a simple and clear guide

jshields said:
Or CD version
1.download Alpha Rev.iso
2.burn .iso image to CD using a iso burning software eg. Power ISO
3.boot from CD eg. Hold F12 at boot
4.press the Legendary enter
TIPS connect USB when the CD has booted
Any problems just pm me
Sent from my HTC Desire s-off
Click to expand...
Click to collapse
Yeah, I found it much easier to just burn to a rewrittable CD. F8 on bootup to load up my boot menu, then I selected my CD Rom.

nice tut, simple and very clearly...
oh don't forget to put in the first post for ppl who gets stuck at stage 3 (it happen to me) just to wait for about 30 minutes or more (don't know exactly how long, just for safety), and then pull out the battery and reboot the phone...
many ppl report it work....
Sent from my HTC Desire using Tapatalk

I think I'm done with the flashing of the hboot from alpharev
But now my phone keeps rebooting to the fastboot screen.
I've tried removing the battery and rebooting again, reboot from fastboot, reboot from clockwork recovery... but i still cant boot up my rom.......
Anyone can shed me a light on what went wrong?

All options to apply S-off should be included, this is a 'how to', and this is not THE only way to do it, personally I found virtual box the easiest method for me. I just think that some other options should be made clear to people, maybe people that have used a different method could add their own ' how to' to this thread?
Great idea though to help people.
sent from my HTC Desire, powered by a SuperVillain using XDA App.

Sorry to noob it up here but what are the benefits of S-OFF. im guessing it means security. does this enable us to hack the kernal? as a user who doesnt do programming but likes to mod my phone alot what could i gain out of this?
thankyou in advance

Yeah sorry for newbies here but what is the benefits of this s-off?

eozen81 said:
Yeah sorry for newbies here but what is the benefits of this s-off?
Click to expand...
Click to collapse
Maybe its a good thing to sum up the benefits on the first page, to stop these kind of questions and making it a 500 page topic where you cant find answers...
I know if you read the forum, or use google you can find all the info
Info from the http://alpharev.shadowchild.nl/ site
HTC implemented security on their newer generation phones. This flag, called @secuflag, controls whether your phone has
it's NAND or flash unlocked. Most noticeably, S-ON (security on) will read-lock your /system and /recovery partition, to name a few. Also, secuflag controls whether zip files being flashed through recovery or fastboot, are signed by HTC.
The now notorious S-OFF (security off) will disable this NAND security.

I gonna change a bit the tutorial, and add the other solutions. Will do a link directly of posters with the solution he use, will be easier for me

AndroidGX said:
I gonna change a bit the tutorial, and add the other solutions. Will do a link directly of posters with the solution he use, will be easier for me
Click to expand...
Click to collapse
allrighty then

Ok, many changes on the tutorial, hope you like it
Tried to do as clear as possible, and add some features.
If any method to add please PM me, I will add it with your name directly from your post here.
Thanks!

AndroidGX said:
Ok, many changes on the tutorial, hope you like it
Tried to do as clear as possible, and add some features.
If any method to add please PM me, I will add it with your name directly from your post here.
Thanks!
Click to expand...
Click to collapse
looks great !

I have now read all the information i can find about S-OFF - Only advantage i can find is that you can change bootscreen.. What are the options if i choose to make S-OFF on my phone - What else can i change ? My phone is rooted, and i have flashed roms and kernels with S-ON - So you guys really need to show more advantages to this than what has already been written..

Nobody is trying to sell you anything. Why don't you GTFO?

ionhide said:
I have now read all the information i can find about S-OFF - Only advantage i can find is that you can change bootscreen.. What are the options if i choose to make S-OFF on my phone - What else can i change ? My phone is rooted, and i have flashed roms and kernels with S-ON - So you guys really need to show more advantages to this than what has already been written..
Click to expand...
Click to collapse
You post in the wrong thread, go say that in the original S-OFF thread (gave in first post).
Here is just a help for people who want to install S-OFF feature on their Desire. Nothing else.

[GUIDE] Debranding Bell Desire Z

Ok have just ran through this on irc and its confirmed working on a bell phone debranding to WWE
This will wipe your phone -- So backup all needed data
Although tested and really shouldn’t cause any damage I accept no responsibility for any damage caused by this. By doing this you are accepting all responsibility ​
What you will need
-- micro SD card reader
-- spare microSD or backup all data from your normal SD card
-- a WWE rom i,e THIS ROM
-- HeX editor
-- ADB shell set up and working
Part 1 GoldCard
1) Format the microSD card to FAT32 format (in card reader).
2) Put the microSD card in your device and boot it.
3) Open Up an ADB shell this doesnt need to be ran as root.
4) Enter 'adb shell cat /sys/class/mmc_host/mmc2/mmc2:*/cid' and press enter. You should get a very long number copy it.
5) Visit this page, paste in your number and reverse it.
6) Visit this page, enter your reversed number and create your goldcard image, which will be e-mailed to you.
7) Open the HxD hex editor. If you are using Windows Vista or Windows 7, you must run the application as administrator.
8) Go to the 'Extra' menu and select 'Open Disk'. Under physical disk, select Removable Disk (your microSD card), uncheck 'Open as Readonly' and click OK. Note that you should select physical disk NOT the logical disk. This is important!
9) Go to the 'Extra' menu again and select 'Open Disk Image'. Open the goldcard image that you received by email.
10) You should now have two tabs - one is your removable disk, the other is your goldcard image. Press OK when prompted for 'Sector Size' (selecting 512 (Hard disks/Floppy disks)) and click OK.
11) Click on the goldcard image tab. Go to the 'Edit' menu, choose 'Select All' then select the 'Edit' menu again and select 'Copy'.
12) Click on the 'Removable Disk' tab. Highlight offset (line) 00000000 to offset (line) 00000170 (including the 00000170 line), then click on the 'Edit' menu and select 'Paste Write'.
12) Click on the 'File' menu and select 'Save', accepting the warning.
Part 2 Grabbing Rom From RUU
1) Start the exe and leave it to load
2) once loaded leave it
3) navigate to C:\Users\**username***\AppData\Local\Temp\
4) look for pne of the two newest folders and open
5) within that folder there will be another folder open that
6) find rom.zip and copy to the sdcard
7) rename PC10IMG.zip
8) Put MicroSD card back into phone and boot to android
Part 3 MISC edit to allow downgrade
this part is only needed if you are downgrading i.e from
1.34.666.5 to 1.34.405.5
1) open up "ADB shell" and type SU to get # symbol
2) run
dd if=/dev/block/mmcblk0p17 of=/sdcard/misc.img
Click to expand...
Click to collapse
3) copy misc.img from the root of the sdcard to your computer //Copy So as to preserv a backup of misc.img on the SD card//
4) open the misc.img in the HeX editor
5) now edit the version line from somthing like
1.34.666.5
Click to expand...
Click to collapse
This will be whatever the version you are on currently
to
1.34.405.5
Click to expand...
Click to collapse
This can/will be whatever the version of the rom you are trying to downgrade too
6) now save as miscnew.img
Here is what your minsc.img and miscnew.img should look like in HeX editor
{
"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"
}
7) copy miscnew.img to sdcard
8) unmount usb storage
9) in ADB shell run command
dd if=/sdcard/miscnew.img of=/dev/block/mmcblk0p17
Click to expand...
Click to collapse
Part 4 Flashing the rom
1) power off phone
2) boot into hboot by holding down vol-dwn + power
3) the phone should then scan the .zip file and ask to flash
4) after flash you will be debranded and running a WWE rom
Credits
The Goldcard Guide Was Adapted To Work On The New eMMC Devices From Here mmc0 to mmc2

So this changes a Bell-branded phone so that it can flash HTC ROMs, right ? Because even the "BellMobility" ROMs still seem to have "WWE" in their title.
What happens if you try to flash an HTC ROM to a Bell phone without this ? Would be useful to know, just for info.

I can confirm that I was the test subject on IRC and this unbranding of my Bell Desire Z worked perfectly.
I now have things like HTC Locations, and Car Panel present on my phone, and things like non-uninstallable game demos of Ashphalt, Golf, Uno, Bell PVR, GPS Navigator, Kobo, Zoompass, Tunes & Apps, TV & Radio are all gone.
After unbranding, everything is working as expected.
Thanks a ton to the op for dedicating his time on helping me unbrand my phone!

Will this work on the G2?

steviewevie said:
So this changes a Bell-branded phone so that it can flash HTC ROMs, right ? Because even the "BellMobility" ROMs still seem to have "WWE" in their title.
What happens if you try to flash an HTC ROM to a Bell phone without this ? Would be useful to know, just for info.
Click to expand...
Click to collapse
Humm never noticed the WWE in the bell mobility rom (could be to do with the Z being a WWE phone and the G2 not, but as they are moth the vision), but regardless you should be able to flash any Z to the HTC- WWE "debranded rom"

pixelwix said:
Will this work on the G2?
Click to expand...
Click to collapse
What getting the Z rom on the G2 ?
if so we have tried and get "data too large" errors. but feel free to try (at your own risk as its never been done before)
i havent tried the 1.22.405.1 RUU
:-D

Hm... so while I'm sorely tempted to try this, are there any downsides to debranding atm? Will it affect OTA updates in the future?
I'm assuming it'll void warranty, heh. The only real benefits are just to get rid of the Bell only stuff though I'm assuming?
Er, also wanted to ask something else: Where exactly are you guys finding the ROMs for the HTC Desire Z (NA)? All the ones I find are EU or AP.

well any ota you should be able to flash :-D .... also u can always flash the bell RUU if u want or need it back as it shipped

CWolfCW said:
Er, also wanted to ask something else: Where exactly are you guys finding the ROMs for the HTC Desire Z (NA)? All the ones I find are EU or AP.
Click to expand...
Click to collapse
There appears to be one on the first page of this forum, at http://forum.xda-developers.com/showthread.php?t=815253
Given how long it's been there though, I'd be suprised if that's the ROM version that's shipping for Bell.

can't wait to get home and do this so i can get Locations and car panel

I think I'm going to hold off until a more current official NAM version of the HTC Desire Z ROM is available as it seems like only the EU/AP versions are available (unless I'm misunderstanding).
Atm, by disabling packages, I can get close to 'debrand' without having to flash. Only thing is I won't be able to get access to HTC Locations and Car Panel afaik.

Sorry, this may seem obvious, but does doing this require root? I'm pretty new to Android.

Great news !!
Thanks for sharing
Let the fun begin
And regarding:
CWolfCW said:
Er, also wanted to ask something else: Where exactly are you guys finding the ROMs for the HTC Desire Z (NA)? All the ones I find are EU or AP.
Click to expand...
Click to collapse
Where ?? from this same forum !!
User football posted some HTC RUU flashers some weeks ago:
[ROM]RUU_Vision_HTC_WWE_1.34.405.3_Radio_12.28b.60.140e _26.03.02.18_M2 (the debranded, world ROM flasher)
[ROM]RUU_Vision_BellMobility_WWE_1.34.666.1_Radio_12.28 b.60.140e_26.03.02.18_M2 (to flash back to Bell branded)
[ROM]RUU_Vision_HTC_WWE_1.22.405.1_Radio_12.26.60.1301_ 26.02.00.24_M2_release (a previous release)
.

i'm assuming this doesn't remove sense?

Stratrix said:
i'm assuming this doesn't remove sense?
Click to expand...
Click to collapse
nope, you will even get MORE SENSE
(since Bell removed some HTC sense apps, and this firmware is the original, "purest" HTC Sense firmware)
but there's another thread you may be interested in:
"[GUIDE] How to remove sense (almost...)"
check it

FireGX said:
Sorry, this may seem obvious, but does doing this require root? I'm pretty new to Android.
Click to expand...
Click to collapse
Download VISIONary from the Android market. You will need this to 'temporarily' root your phone which is required for this process to work.

shubjero said:
Download VISIONary from the Android market. You will need this to 'temporarily' root your phone which is required for this process to work.
Click to expand...
Click to collapse
Rooting with VISIONary is now permanent

gtrab said:
Rooting with VISIONary is now permanent
Click to expand...
Click to collapse
not exactly, it will be tomorrow. there are some extra steps in conjunction w/ VISIONary that are required right now

gtrab said:
Great news !!
[ROM]RUU_Vision_BellMobility_WWE_1.34.666.1_Radio_12.28 b.60.140e_26.03.02.18_M2 [/URL] (to flash back to Bell branded)
.
Click to expand...
Click to collapse
Can anyone confirm that this is the same version that is shipping on the Bell Z? I am showing Build 1.34.666.5 on my Bell Z. I want to be able to get back to unrooted stock Bell firmware if I Desire. Will this unroot if I flash back to this ROM?
Thanks,
Y2J

My Bell Desire Z is also 1.34.666.5. I don't think it's the same as the one posted...
And yea, now that VISIONary is perma-root, is there a way to unroot the device? Do I simply uninstall the program?

[Q] Dinc corrupt primary file system *serious software help needed*

to start off with here is the problem list:
1) any rom, ruu, etc loaded will not boot past htc screen and if they do it boot loops 5 seconds into the animation.
2) clockwork reads error, E: /dev/block/xxxxxxxxxxx and cant mount data or cache partitions.
3) when doing a cat of mounts there are only five items instead of the 20 an unrooted stock phone possesses.
so in short i am asking for ideas maybe i have not tried "be creative here" to recover or reinstall "in my opinion the best fix" the whole main file system. just as if it was merely hardware blank from the factory. maybe push over new /dev, /system, /data, /cache etc etc as i believe the file system is corrupted and missing directories.
thanks for your time and thoughts...
*edit* i have been trouble shooting with the brilliant guys over at incredibleforum as well and thus whats lead me to my question here. so the back story, everything i've tried already, findings, and pictures are already posted here (not to violate TOS just for reference):
incredibleforum . com/forum/htc-incredible-rescue-squad/10812-boot-loop-after-exhausting-ever-possible-fix-my-head-experiance-help.html

Have you tried to ruu to stock froyo, and then do a factory reset thru hboot? Also when you say you ruu'd before did you do the PB31IMG.zip ruu or the ruu exe, or did you try both? Also have you at some point gotten the 5 vibes of death while booting?

i have done the ruu's both in hboot pb31img and via the exe while i booted into hboot. and i've never gotten nor heard of the five vibes. but exploring the file system there are directories missing for some reason. so i'm figuring the ruu's and roms aren't installing certain files due to not having a place to put them.

Sounds bad to me. I know they say if it turns on its not bricked, but if an ruu cant write to the partitions you will probably never be able to find a way to either. Hey im not an expert though by any means. Hope some one can help you figure it out.

the ruu cant write to the partitions because they don't seem to exist or the mounts for those directories. thats why i'm interested in finding a way to rewrite the partitions back to factory. there is a way because the phone wasn't built with this file system on it so there is a way to write /dev /system /cache /data etc.. maybe even a way to pull it off a stock phone and write to this one?? i can adb shell and view all of the files so i know its accessible. and hboot and recovery both work and can flash successfully. come on xda don't let me down i know there are some really brilliant and creative minds out there who think this is an easy fix to them.

tophkr said:
the ruu cant write to the partitions because they don't seem to exist or the mounts for those directories. thats why i'm interested in finding a way to rewrite the partitions back to factory. there is a way because the phone wasn't built with this file system on it so there is a way to write /dev /system /cache /data etc.. maybe even a way to pull it off a stock phone and write to this one?? i can adb shell and view all of the files so i know its accessible. and hboot and recovery both work and can flash successfully. come on xda don't let me down i know there are some really brilliant and creative minds out there who think this is an easy fix to them.
Click to expand...
Click to collapse
which hBOOT do you have? have you tried to reinstall the hBOOT?
http://pvillecomp.com/?page_id=4
after you reinstall hBOOT then try to ruu with the .exe

synisterwolf said:
which hBOOT do you have? have you tried to reinstall the hBOOT?
http://pvillecomp.com/?page_id=4
after you reinstall hBOOT then try to ruu with the .exe
Click to expand...
Click to collapse
+1 for reflashing hboot.
An ruu is ment to program the phone as if it were strait off the line never touched. It should create the file structure and partitions if they dont exist. What bothers me about your problem is that flashing roms or dooing ruu's compleet sucessfully without error. If the ruu cant write to these partitions it should stop and give an error, not just continue as if everything is ok. So to me it seems its writing to them fine but then for some reason cant read from them. Same for flashing a rom if it cant mount the partitions it should halt and give an error.

cmlusco said:
+1 for reflashing hboot.
An ruu is ment to program the phone as if it were strait off the line never touched. It should create the file structure and partitions if they dont exist. What bothers me about your problem is that flashing roms or dooing ruu's compleet sucessfully without error. If the ruu cant write to these partitions it should stop and give an error, not just continue as if everything is ok. So to me it seems its writing to them fine but then for some reason cant read from them. Same for flashing a rom if it cant mount the partitions it should halt and give an error.
Click to expand...
Click to collapse
well you have have a partition that has blocked write access so when RUU reads it, it works but when it try's to write it skips it.

{
"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 currently have .92 installed but i've gone back as far as .77 due to it being the development copy with full fastboot and adb capabilities. but i will try to reflash hboot .92 and then run ruu from computer while still in hboot.. worth a shot

You could try this. Sounds like your issue. Post 3.
http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/page__st__20

tried that and i'm guessing the correct partitions are no longer there because i recieve this:
Error: /dev/block/mmcblk0: unrecognised disk label
and get that with every partition in the mmcblk catagory

ok so i have a question based on a possible cause to this problem.. if the prebious owner had flashed a droid incredible 2 rom insted of a DINC rom.. i know that can cause issues flashing the wrong roms.. how would you go about fixing that?

tophkr said:
ok so i have a question based on a possible cause to this problem.. if the prebious owner had flashed a droid incredible 2 rom insted of a DINC rom.. i know that can cause issues flashing the wrong roms.. how would you go about fixing that?
Click to expand...
Click to collapse
Did you try the link on the last page?
Sent from my sexy assistant. (AMOLED HTC Incredible)

synisterwolf said:
Did you try the link on the last page?
Sent from my sexy assistant. (AMOLED HTC Incredible)
Click to expand...
Click to collapse
the link to using parted to fix the partition format.. yes but those folders do not exist. when i show a list of my mounted partitions cache, data, system and a few others don't show up in the list at all. so because they don't exist anymore i don't know what partitions to remake or what folders need to go in them, which to mount etc.

So when you run the RUU's and PBIMG's they complete successfully without error?
also on a kind of related note, have you looked into booting a rom from your SD card or internal storage? Its not a fix or anything just merely might give you the satisfaction that your phone can boot a rom lol though it might not be by the traditional or standard means

nope i've never looked into how to boot a rom from internal storage. could you supply a link to instructions as this might be a temp fix while i continue to try and fix this.
and yes when i run them they compleate with no errors. only errors appear when looking in recovery.

tophkr said:
nope i've never looked into how to boot a rom from internal storage. could you supply a link to instructions as this might be a temp fix while i continue to try and fix this.
and yes when i run them they compleate with no errors. only errors appear when looking in recovery.
Click to expand...
Click to collapse
I would try a Google or XDA search because I've never tried it myself. Last I remember punk.kaos did it back when I had an Eris and I think more recently conap did it with the Incredible. Sorry I couldn't be of more help :/

i'm going to look into it but i've never heard of it being done except on the hd2 and hd7 using ram loading. but thanks for the ideas

[Q] Gaining S-ON Again

Hi
Recently was experimenting with RevolutionN Data ++ but something went wrong and market access was lost, no signal and the phone was not functioning (happened with many different ROMs actaully too).
Anyway tried flashing RUU but got an error 152, successfully reflashed the stock hboot through fastboot and then reflashed RUU which worked (thank god).
I though this would completely revert the phone back to stock however when I enter hboot it still says AlphaRev S-OFF.
Please help

geenius said:
Hi
Recently was experimenting with RevolutionN Data ++ but something went wrong and market access was lost, no signal and the phone was not functioning (happened with many different ROMs actaully too).
Anyway tried flashing RUU but got an error 152, successfully reflashed the stock hboot through fastboot and then reflashed RUU which worked (thank god).
I though this would completely revert the phone back to stock however when I enter hboot it still says AlphaRev S-OFF.
Please help
Click to expand...
Click to collapse
look at the sticky, 1st post in the Q&A thread...

It's not a design element, it really works:
{
"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"
}

MatDrOiD said:
It's not a design element, it really works:
Click to expand...
Click to collapse
I've an idea... the mods should build in a feature, that if you have under 15 posts, the search button is lit up like a Christmas tree, and is 10x larger, or plastered everywhere on the screen.. so that you simply CAN'T miss it... or, before someone signs up, they are MADE to watch an entire video explaining to them how to search, or read a long document detailing how to do so... think my idea would really save us lots of time and wasted thread space...

don't you think I've tried that...which is why I was looking for another solution

Okay, so you searched, and yet you didn't find my guide which is a sticky right on top of the Q&A section which addresses your issue directly.... *sigh*
Troubleshooting Guide said:
[8]STILL S-OFF AFTER RUU
"I want to return my phone for warranty, I used a RUU but I'm still S-OFF"
Cause:
- Alpharev's Hboots are write protected, so that they can not be overwritten by a RUU
HOW TO S-ON
METHOD 1#
[STEP1]- Visit Alpharev and download the "Downgrader"
[STEP2]- Flash the downgrader over fastboot. This can be done with Android Flasher, cmd, or fastboot commander (Note: android flasher is the only program that does not require third party software such as Android SDK or Java JDK)
[STEP3]- You should now notice the title on the bootloader screen is "Alpharev Unlock", run the RUU again and you will have S-ON'd your device.
#METHOD 2#
[STEP1]- Instead of running the RUU again, and putting your phone at risk once more, you can simply upgrade just the bootloader manually, with the PB99IMG.zip method.
[PHASE1]- we need to extract rom.zip from the RUU.
[P1/STEP1]- Run the RUU (BUT DO NOT PLUG IN YOUR PHONE OR CONTINUE), move it to the side as it cannot be minimised.
[P1/STEP2]- go to start menu, and use the "run" feature. Type in %temp%
[P1/STEP3]- select "date modified" to "today" (to make it easier to find). There are should now be 2 folders with long names of random characters.
[P1/STEP4]- search the folders for rom.zip and extract it to the desktop.
[P1/STEP5]- delete everything EXCEPT "hboot_8x50_0.93.0001_20100810.nb0" and "android-info.txt"
[P1/STEP6]- rename the zip to PB99IMG.zip (make sure it is not PB99IMG.zip.zip)
[PHASE2]- now we need to update the bootloader
[P2/STEP1]- put the file in the ROOT of your sd-card (not in any file or folder) and boot into bootloader (poweroff, hold VOLUME DOWN and POWER). After a few seconds, you will be prompted to update bootloader. Select Yes. DO NOT INTERRUPT THE PROCESS, OR YOU WILL BRICK YOUR PHONE.
[P2/STEP2]- Once the process is finished, you will now be S-ON.
Click to expand...
Click to collapse

bortak said:
I've an idea... the mods should build in a feature, that if you have under 15 posts, the search button is lit up like a Christmas tree, and is 10x larger, or plastered everywhere on the screen.. so that you simply CAN'T miss it... or, before someone signs up, they are MADE to watch an entire video explaining to them how to search, or read a long document detailing how to do so... think my idea would really save us lots of time and wasted thread space...
Click to expand...
Click to collapse
I like your idea and I totally agree. My suggestion for the video is this one:

MatDrOiD said:
I like your idea and I totally agree. My suggestion for the video is this one:
Click to expand...
Click to collapse
That would work!
over at bit-tech they have a system that if you've under 10 posts, each post (up to 10) has to be approved by a forum moderator... Imagine how many useless posts that would save

bortak said:
That would work!
over at bit-tech they have a system that if you've under 10 posts, each post (up to 10) has to be approved by a forum moderator... Imagine how many useless posts that would save
Click to expand...
Click to collapse
Would be a nice christmas present by XDA.

Bloody bell some people just don't understand. Only just seen the replies and cheers for the useless help.
Turns out my phone was genuinely ****ed so had to buy a new one!!!
Sent from my HTC Desire using xda premium

Unlock bootloader on GT-I9250 without wipe and without root

Hi! After latest OTA update I was left with an unbootable Galaxy Nexus (zygote couldn't start) and I lost root (su needed activitymanager up). So I needed to unlock to revive the phone, but I really didn't want to lose my data. After some exploration I could come up with a way to unlock bootloader without wipe and without root. I have seen several questions about this here and this was deemed impossible, so I decided to share my findings and expect they might help someone. Should work with GSM tuna phones.
Components for success:
— unlocking without wipe via putting a byte in param partition (needs root):
[1] http://forum.xda-developers.com/showthread.php?t=1650830&page=15
— OMAPFlash, a low-level utility for manipulating and flashing chipset (usually used to unbrick phones)
[2] http://forum.gsmhosting.com/vbb/f63...9250-galaxy-nexus-gt-i9100g-gt-i9300-1465412/
Take the two of them and you have a solution. I could successfully flash unlock byte to param partition using OMAPFlash.
A sketch of a guide:
1. Boot windows xp, download OMAPFlash (http://d-h.st/XNv), connect a turned off phone without battery, install drivers for omap device. (Mod edit: I've updated the download link.)
2. Dump a part of param partition. You don't need to dump the whole partition, but I think it is safer if you dump a sector-aligned area (512*n). I used 4KB (8 sectors).
Code:
OMAPFlash -omap 4 -2 -p OMAP4460_TUNA_8G_HS_PRO -t 36000 chip_upload [email protected] 1000 param.img
chip_upload is for downloading data from device memory
[email protected] is the start of params partition (check /sys/block/mmcblk0/mmcblk0p4/start, multiply by sector size 512 and convert to hex)
1000 is to copy 4KB.
Sometimes the process stalls (esp if you try to download larger dumps), just reconnect and retry.
3. Verify that the content is similar to first 4 KB of the dumps of param partitions attached in the thread [2]. For me they matched entirely.
4. Change the byte at offset 124 (0x7C) from 01 to 00.
Code:
echo -ne "\x00" | dd obs=1 count=1 seek=124 of=param.img conv=notrunc
5. Flash it back to the device.
Code:
OMAPFlash -omap 4 -2 -p OMAP4460_TUNA_8G_HS_PRO -t 36000 chip_download [email protected] param.img
Reboot, you are unlocked.
Additional links:
[3] http://forum.gsmhosting.com/vbb/f634/gt-i9250-pinout-enjoooy-1463061/ GT-I9250 JTAG pinout. Not directly releavant to the guide, but I found it while searching for solution, thought that can help someone in future.

Additional reading
The dangers of OTA when you have root, or why I was stuck with an unbootable phone at all
I learned the hard way that OTA may cause unpleasant results if you are trying to preserve root and mess with filesystem.
I was trying to preserve root in a way similar to one used by rootkeeper apps: put a copy of su somewhere in /system and make it immutable. So I went and put my su to /tts (thought that it's unprobable that OTA will do something there), and made it immutable.
And then the update came. As part of the the update process it copied a new version of /system/usr/share/zoneinfo/zoneinfo.version file and the file got 660 perms (package_extract_dir("system", "/system") in the update_script). Then it went on to recursively fix permissions so that the mentioned file would be made readable (set_perm_recursive(0, 0, 0755, 0644, "/system")). But the set_perm_recursive was met by immutable su in tts directory, chmod returned error and the recursive process was stopped before it got to zoneinfo.version file. So the latter file remained unreadable.
Unfortunately during startup zygote preloadsClasses, static constructor in some sqlite class needs DateFormat, and DateFormat reads zoneinfo. And fails cause it's unreadable. Exception, System.exit. Phone boot stuck.
To work my copy of su needs to send a message to ActivityManager service using binder. I wrote a dirty mock for AM but servicemanager didn't accept my fraud, it checked uid. I tried to bypass preloadClasses with overflowing system file descriptors count to prevent zygote from reading preload class list, but somehow it didn't succeed. Thus the only option I had was unlocking bootloader.
So it may end bad if you mess with /system on a stock rom with locked bootloader and want to receive OTA. It may seem natural, but sometimes the changes seem irrelevant, and then a chain of small failures leads you to loss of everything: boot, root, and data.

This is great work! Kudos to you for figuring it out.
By the way, where did you find the syntax for OMAPFlash commands?

efrant said:
This is great work! Kudos to you for figuring it out.
By the way, where did you find the syntax for OMAPFlash commands?
Click to expand...
Click to collapse
There are some docs in OMAPFlash_tuna.zip package. The most interesting is OMAPFlash.txt that lists options and commands and has some examples.
Also I was lucky that there is a complete example for unbricking GT-I9250 in Targets/Projects/tuna. This is where I took the options specific for this device.

nichtverstehen said:
There are some docs in OMAPFlash_tuna.zip package. The most interesting is OMAPFlash.txt that lists options and commands and has some examples.
Also I was lucky that there is a complete example for unbricking GT-I9250 in Targets/Projects/tuna. This is where I took the options specific for this device.
Click to expand...
Click to collapse
Exactly. I haven't needed this yet, but i had looked in those board files, cross examining with omap 4460 manual that can be found on the web. Thanks for sharing.
I was not aware that JTAG method had been found. Great news.
Sent from my i9250

Works!
Awesome - this worked for me! Unlocked, unrooted, TAKJU Galaxy Nexus w/JB 4.2.2. I used OMAPFlash_tuna.zip (download link).
I had issues when the downloaded param.img file was long, so I replaced 1000 with 200 in the commands. Regardless, it still took me probably 5-10 tries on each command to get it working (unplugging and replugging the phone in between), and sometimes it would freeze up and I'd have to restart Windows. If it takes longer than 5 seconds, you should press Ctrl+C and restart that step.
My problem was that one of my volume buttons is messed up, and as a result the fastboot screen doesn't work - Windows doesn't detect a fastboot device, and none of the hardware buttons or the touchscreen works either. As a result I needed to unlock the bootloader without using fastboot (oem unlock), and this did the trick!
Also, on Windows, I downloaded a hex editor (i.e., HxD) to do the editing. My modified param.img (only 512 bytes) is attached as well.
{
"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"
}

Thank you!!! It worked for me too!
The volume buttons on my Galaxy Nexus didn't work and I can't recharge the battery via USB. The USB works only as data connection. Despite all these issues on my phone, it worked for me too!!
I replaced the size in the commands from 1000 to 400 (1024 bytes = 2*512), and I had to put the battery on the phone.

Sweet jesus I cannot express enough gratitude for this post. While I was a little worried about bricking my device, it would up working perfectly.
A couple of confusing points for anyone out there trying to do this:
- The dump / reflash should only take a few seconds each. If it hangs, cancel and re-start the process.
- Install the drivers with the device OFF but plugged in. You will have an OMAP device without a driver in your device manager. Update the device driver and you're good to go.
- I didn't know how to get the dd command to work on windows, so I also went the Hex editor route it it worked flawlessly
- The only snag I ran into was that it did not boot into my flashed CWM after doing an "adb reboot recovery" from the stock rom. It went back to the stock android recovery. From there I did "fastboot boot cwmrecovery.img" and installed my rom and gapps. After that initial boot, it rebooted into recovery just fine! It seems like a weird glitch (maybe just a one-off).
Cheers

techobrien said:
- Install the drivers with the device OFF but plugged in. You will have an OMAP device without a driver in your device manager. Update the device driver and you're good to go.
Click to expand...
Click to collapse
This is a critical step right here. This thread either should be linked on the 101 FAQ if it's not already or stickied.
a maguro wrote this.

techobrien said:
- The only snag I ran into was that it did not boot into my flashed CWM after doing an "adb reboot recovery" from the stock rom. It went back to the stock android recovery. From there I did "fastboot boot cwmrecovery.img" and installed my rom and gapps. After that initial boot, it rebooted into recovery just fine! It seems like a weird glitch (maybe just a one-off).
Cheers
Click to expand...
Click to collapse
Sounds like you are getting hit with the /system/recovery-from-boot.p file. When you boot into Android, this file checks to see if you have stock recovery...if not, it replaces it with stock recovery. You can rename, move, delete the file safely. It shouldn't exist in custom ROMs, which would explain why after installing a ROM and Gapps you were fine.
This is pretty cool. Nice find OP.

cupfulloflol said:
Sounds like you are getting hit with the /system/recovery-from-boot.p file. When you boot into Android, this file checks to see if you have stock recovery...if not, it replaces it with stock recovery. You can rename, move, delete the file safely. It shouldn't exist in custom ROMs, which would explain why after installing a ROM and Gapps you were fine.
This is pretty cool. Nice find OP.
Click to expand...
Click to collapse
This post thread have not been getting the attention it deserves..
Beamed from my Maguro.

cupfulloflol said:
Sounds like you are getting hit with the /system/recovery-from-boot.p file. When you boot into Android, this file checks to see if you have stock recovery...if not, it replaces it with stock recovery. You can rename, move, delete the file safely.
Click to expand...
Click to collapse
Good to know for next time round. The flimsy headphone ribbon cable is the bane of my existence and it seems like a somewhat common problem. I didn't think that the custom rom would touch the bootloader so I was confused, but /system/ makes sense. Thanks for the tip.

Just in case anybody was wondering, this method also worked for my Verizon GNex LTE. I also used a HEX editor.

Hi,
i'm thinking to use this method to unlock my Nexus' bootloader, in order to gain root privileges without wiping the memory.
This because i need to try and undelete files i have lost on my phone, to do this i need the root but i can't use the normal procedure that would wipe forever all the data i need to restore.
As i am new to this kind of operations, i never even rooted my Android phones, i wanted to ask if this procedure can fit my situation, and if there are any risks....
Thank you very much
EDIT: It worked perfectly!!
Thank you very much!!

Did anybody try it on MAGURO device? Does it require any change in the procedure?

Um... The op (and others) did it on a maguro? After all, the title says "on GT-I9250".

Isn't a i9250 a Maguro?
Beamed from my Grouper

Mod edit: removed quote of the OP.
Is WinXP really required for this process or will it work on newer versions of Windows ie Win8?

mielli1 said:
Is WinXP really required for this process or will it work on newer versions of Windows ie Win8?
Click to expand...
Click to collapse
Please do not quote the first post of threads when you reply.
As for your question, if you can get the driver to install on Windows 8, the program will work fine. The driver installs fine in Windows 7 by the way.
Don't forget to disable driver signature verification if you are trying to install drivers in Windows 8.

Windows 8 - stuck at installing drivers
beekay201 said:
This is a critical step right here. This thread either should be linked on the 101 FAQ if it's not already or stickied.
a maguro wrote this.
Click to expand...
Click to collapse
I have a Nexus with a broken volume up button, so am trying this method as a way of unlocking the bootloader and rooting my device.
When I plug the powered off device into the usb port, constantly get the sounds of a device being inserted, and then unplugged (two different beeps.) This continues until I unplug the phone.
Is this the step where I should get a "found new hardware" notification? It is not happening for me, and I'm wondering if this is Windows 8 related.
FYI - I have already disabled driver signature verification.