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
Related
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.
Hi all,
Two weeks ago, I download Gingerbread Official version for DHD Here
After that my device is Unroot and HBoot S-ON
I have try to use GingerBreak appli, but unsuccessfully.
After I try to use a Ruu 1.32, but the result is the same.
Then I follow this thread: How to Downgrade 1.7x/1.8x/2.x to 1.32.405.6
I have that:
{
"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 put the PD98IMG.zip on my SDcard.
I reboot on bootloader, but nothing happened. My screen stay on bootloader menu or fastboot menu.
I can read:
ACE PVT SHIP S-ON RL
HBOOT-0.85-0024
MICROP-0438
RADIO-26.09.04.11_M2
eMMC-boot
Apr 12 2011,00:55:45
Click to expand...
Click to collapse
So my Device is not S-OFF that's why I can't use PD98IMG.
Does anyone have a clue for me for:
- How to Root my phone
Then I can turn on HBoot S-OFF and change my Rom
Thanks for all, and sorry, I am French
I followed the very same guide just a few days back to root my DHD. Your adb terminal seems to be fine.
You got "#" in the shell, that says temproot was fine (according to the guide).
Make sure you put the PD98IMG.zip file in the "root of your SD", not inside any other folder.
Reboot into bootloader, and it should automatically recognize the rom image and ask you to update. Say yes, and you are ready to root and S-OFF your device.
in the root folder?
that is where I put it:
no, By using the downgrade method in the Thread, you dont need S-OFF
you do S-OFF after you have downgraded.
The reason why nothing happens is your sd card. Get some other sd card and try.
The same thing happened to me, on one sd card it wouldnt read, but i got another one and it did. So try it with a different sd card
I try with 2 sdCard :/
But with the other I have CID error :/
EDIT: With one I have format on fat32 and nothing happen, I try to take pictures about that
EDIT2:
From my n°1SD:
From my n°2SD:
Thanks for your answer
yea, if you have a CID incorrect error, then you need a GoldCard. Google how to make a GoldCard.
Remember to use the mmc2 ID and reverse it, make sure its mmc2 and reversed!
If you dont know what im talking about, just google GoldCard, and you will find options about mmc (mmc0, mmc1, mmc2, ...) choose mmc2.
There are many tutorials about making goldcards
i used this link when i was making my goldcard : GOLDCARD-LINK
I edit my last message!
Uhm, My n°1SD is a goldcard, but mmc0, I don't find mmc2
Thanks for your link.
What is reversed?
I try your link.
EDIT: Do you have the GoldCardHelper apk?
because I am in Norway, so I don't have data access from my phone, and there is no available Wifi xD
that's maybe okay, I use the internet continu connexion from my computer.
I try to connect to internet
wait, i didnt get you .. you want me to upload the goldcardhelper?
Ok, so I have that:
I follow the tuto
No that's okay, I have found it on internet
Thanks
EDIT:
I use 00b400...
your welcome!, just remember to press the thanks button!...and yes
use the 1st reverse ID (00b400...)
yes I have to press thanks in few minutes!
But I can't paste write with HXD :/
Okay That's great I success, because I select Read Only
So know What does I have to do?
Direct use PD98IMG? or I have to do the thread about how to downgrade to 1.32?
(2 thanks for you )
you do the commands on your phone - that was written on the downgrade thread.
Then you copy the .zip file onto your GoldCard
Then you go into bootLoader!
okay I try immediatly
thanks again
your welcome,
... Is that correct?
ummm...you're suppose to get the same screen as you did before.
Try again, but do it carefully. - make sure you restart you're phone before you try again
Yes I am supposed...
I will try again xD
Again the same :/
I don't format my µSD To Fat32 because it's ever format in Fat32
do you think I need to format an other time?
can anyone please help???
My friend failed at rooting the desire and now...
No mather what i do my phone always turns on in hboot mode. this is a problem, because volume up and down don't work, neither does the powerbutton.
i tried to lunch the RUU exe on ma computer to instal androind anew but it always says that the battery is under 30%
i also tried to put a rar file with the name PB99IMG_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed
on my sd card... it should install this update automaticly but it does nothing
i red a lot of forums and tried a lot but nothing worked
Any ideas?? please help
Did you rename it to PB99IMG.zip? Because that you must do
Sent from my HTC Desire using xda premium
do i have to have a goldcard that this metod works??
i tried to rename it, didn't work : /
Did you get any errors?
Did you rename with windows? If yes, make sure it's not PB99IMG.zip.zip, because windows hides known file extensions.
Did you get your phone from a carrier or an independent store like amazon?
rename with windows? what do you mean?
i renamed it like every other map or ikon
no errors, it doesn't do anything
ok... i'm cinda confused now. what should i rename into PB99IMG.zip. a shipped rom right?
I mean, with witch OS (windows, linux, android itself) did you rename the downloaded file?
You should download and rename this file:
PB99IMG_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.zip
After downloading, rename it to "PB99IMG.zip". When done, copy it to the root of your SD card (so not in any folder).
Now reboot into HBoot (start phone with pressed volume back and power button) and the file should be recognized.
no, you need to extract rom.zip from the RUU (EDIT: unless you already downloaded the PB99IMG version of it which I can see you did so never mind what I said)
go to my guide and find the right section for you there's a tutorial on how to do it
bortak said:
no, you need to extract rom.zip from the RUU (unless you already downloaded the PB99IMG version of it which I can see you did so never mind what I said)
go to my guide and find the right section for you there's a tutorial on how to do it
Click to expand...
Click to collapse
IMHO its's much easier to download a "prepared" PB99IMG-file directly.
tnx very much guys!!!
i hope it works
if it doesnt... is there anything else i can try??
jann32 said:
if it doesnt... is there anything else i can try??
Click to expand...
Click to collapse
Let's first see if it works. Always take one thing at a time.
it doesn't recognize it.... it does nothing
it isn't rooted... perhaps that is the problem?
do you have another suggestion??
Are you really in Hboot mode (HBOOT in blue highlighted letters)?
Try what bortak said.
it doesnt work
it doesnt do anything
mybe because it isnt rooted??
do you have another suggestion??
Please answer based on my questions instead of repeating what you just wrote, otherwise it's nearly impossbile to help you.
yes i am in hboot.... white screen... blue highlights
do i need a goldcard for the file to be recognized?
No it just must be spelled correctly. PB99IMG.zip
Not zip.zip and also not lower case like pb99img.zip
If you can give us a screen shot of the file name in windows to confirm it is correct please
Sent from my HTC Desire using xda premium
i spelled correctly
mybe it did't work cause i put in on a different sd card and than switch it with the original one
i did it so, because i can't put anything on the broken desire, cause its broken. so i took a different phone and then i put on the sd card that file. then i switch sd cards.
could that be the reason?
{
"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"
}
Where on the SD card are you putting it?
If its not reading SD card, you need to follow the usb brick tutorials such as
http://androidforums.com/desire-tips-tricks/365476-guide-usb-brick-fix.html
Sent from my HTC Desire using xda premium
hm... mybe you're right!
i'll try that, tnx!
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
With all the splash screen discussion and threads popping up, I decided it was time to make a tool which could help users create and flash their own splash screens.
Verizon HTC One Splash Image Creator
This simple Windows command-line tool allows the creation of splash images, which are automatically converted to zip files and placed in the 'flash' folder, ready to be flashed, which can be flashed by the second option. It also allows the backing-up of your current splash image, as well as extracting the image from custom '.img' files.
Instructions:
S-OFF is required for this to function!
Everything needed is included aside from the image you want to be a splash screen, and the on-screen directions are quite straight-forward.
Unzip it to a location you can easily find and run 'splash.bat'. If necessary, run it as Administrator.
Make sure you maintain the folder structure as it is in the zip.
DISCLAIMER:
This tool consists of several files, most of which I didn't create. Specifically, it includes the most up-to-date ADB and Fastboot files, along with the FFMPEG free software licensed under GPL, as well as 7-Zip, also licensed under GPL. I am not making money from this tool, therefore everything should be copacetic. All I'm doing is collecting them in one place, making it significantly easier to perform its specific function.
I can not be held responsible for your use of this tool. Flashing custom images generally can't brick your device, but if it does, the fault lies with you, the user. I am not liable. Use this tool at your own risk. This is for the Verizon HTC One only!
Screenshots:
{
"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"
}
Known Issues:
When creating a splash image, sometimes it asks you to specify whether the destination is a file or directory. It's a directory. I have overwrite and quiet mode on, so it shouldn't pop up and ask that. It only does it about 2 out of 30 times.
When flashing the splash zip, it sometimes tells me that fastboot flash isn't a valid command, despite it working without changing anything since the last time I ran it. I also tested it about 30 times, and it also only gave me that error twice. It immediately reboots and works again right after that without any modification.
Potential Limitations:
I have only been able to test this on the 1.10.605.8 software release. I don't know if you need to change the text in the android-info.txt file in the '/tools/' folder to the updated version or not. I would appreciate it if someone would test that for me who is currently on the new update.
Changelog:
Code:
v1.01 - Bux fix regarding folder structure.
v1.0 - Initial release.
Download:
http://d-h.st/OTD
Please let me know if you discover any bugs, or if you think you know why I have the two I have now. Also, let me know if it works on the .10 software update.
RESERVED
This isn't working for me. Its saying that '/tools/adb.exe' does not exist.
sebastianraven said:
This isn't working for me. Its saying that '/tools/adb.exe' does not exist.
Click to expand...
Click to collapse
Are you maintaining the folder structure as it is in the zip?
EDIT:
I did leave a bug in there regarding folder structure. I was operating from C:\ during testing, and left "C:" in there as part of the test for whether the needed files existed. If you were operating on a drive letter besides C:, it would throw that error. I removed that drive letter requirement. Please download version 1.01 and try it again from any drive letter you like.
IceDragon59 said:
Are you maintaining the folder structure as it is in the zip?
EDIT:
I did leave a bug in there regarding folder structure. I was operating from C:\ during testing, and left "C:" in there as part of the test for whether the needed files existed. If you were operating on a drive letter besides C:, it would throw that error. I removed that drive letter requirement. Please download version 1.01 and try it again from any drive letter you like.
Click to expand...
Click to collapse
Ok. Here's what I did:
Redownloaded the zip.
Unzipped and moved it to my C: drive to make this as simple as possible.
Ran as Administrator
Selected #2.
Got the same error.
sebastianraven said:
Ok. Here's what I did:
Redownloaded the zip.
Unzipped and moved it to my C: drive to make this as simple as possible.
Ran as Administrator
Selected #2.
Got the same error.
Click to expand...
Click to collapse
That's very odd. Are you placing a picture in the 'image' folder, using option #1 and converting it to the flashable zip, then trying to flash it? If there's no zip to flash, it throws an error, even though that's the wrong error.
ak074 said:
if this creates the .img to be flashed via hboot, then the android-info.txt will need to be changed to reflect the current version of the phone.
Click to expand...
Click to collapse
I know there is a way to fix it but yea it's better to be safe than sorry
on rezound I accidentally flashed a leaked one, so i couldn't flash any of these, we eventually figured out a way to fix it thankfully but it was a lesson learned
Good job man!
Worked great for me.
Thanks!
I would like to start using this tool, but I am using santods modded no-text hboot from the latest OTA...
What should the android-info.txt file have? do i just change the mainver?
peteschlabar said:
I would like to start using this tool, but I am using santods modded no-text hboot from the latest OTA...
What should the android-info.txt file have? do i just change the mainver?
Click to expand...
Click to collapse
I've used this with multiple ROMs and HBOOT versions, including the newest one, without altering anything in this program, and all worked without a problem. While I can't guarantee that that will always be the case, I haven't come across any problems as of yet. Flashing a splash image generally can't screw your phone up, but there are always exceptions. I really should update this tool with more specific instructions. Maybe I'll do that while I'm off over the holidays. To be specific in what I've tested it with, I've listed everything that I recall testing it with. I haven't seen it fail yet, and I haven't updated it since the original version.
ROMs tested with:
1.08.605.8
1.08.605.10
1.08.605.15
2.10.605.1
CM 10.2
HBOOTs tested with:
1.08.605.8 HBOOT 1.54.0000
1.08.605.10 HBOOT 1.54.0000
1.08.605.15 HBOOT 1.54.0000
2.10.605.1 HBOOT 1.55.0000
Santod's modded HBOOT 1.54.0000
RegawMOD Bootloader Customizer HBOOT 1.54.0000
Thanks! Worked great on 1.55hboot ViperOne 4.2.1 rom. Great work.