S-ON can't flash to my Desire S - Desire Q&A, Help & Troubleshooting

Hi I'm new to this, and yes maybe I shouldn't have started messing in the first place, but that's just me I can't help myself.
I was fed up with bloatware and Google so I decided to Root my Desire S using the super one click method.I have Hboot 2.00.0002 so the revolutionary method would n't work, so it worked but I still have S-ON. Everything worked great and I was able to use TiBU to clean my phone of all the junk apps. Unfortunalely I went a bit far, but that wasn't a problem because I'd backed it all up. Not the case when I tried to reinstall apps like HTCcontacts.apk, system apps TiBU just hangs and nothing happens. At a guess Im thinking having S-ON is stopping me from writing to the system folders, although it allows me to uninstal those apps. Hmm I thought OK my phone is wiped anyway I might aswell just flash a new OTA from the HTC website, an official ROM not a custom one, that surely should work. Well to cut a long story short it didn't. It got about a third the way through then failed due to security signatures or something (it flashed up quick so I couldn't read exactly what it said).
Now my phone will only boot to HTC screen and goes no further, I've tried everything but nothings working. I can enter my Bootloader and have managed to flash the ClockworkMod Recovery and have tried to install many different official ROMS from the SD card using the ClockworkMod but it always gets a third through and stops. I've also tried installing from my PC using cmd, which was doing the same but now doesn't even recognise the device.
ITS OK ALL SORTED I WAS JUST DOING THINGS IN THE WRONG ORDER
BIG THANKS TO THIS POST --------> http://forum.xda-developers.com/showthread.php?t=1275632
So having S-ON doesn't seem to matter for flashing new ROMS as there has been some confusion over that in other forums,

Wrong forum mate this is Desire not Desire S
been reported to move to Desire S forum

Related

[Q] clockwork problems

I've just got my first Android phone (an HTC Desire from Telstra - quite a good phone from all reports but hobbled almost to the point of unusability by Telstra). My Android guru (also a member of this forum) has had little success rooting it so it can be made more useful because, although most of the process works, it seems that Clockwork is not going in successfully and doesn't seem to be able to recognise the SD card (8GB, partitoned at 7GB (FAT32) and 1 GB (EXT3)). It claims that it can't find several of the files it needs to work.
The upshot is that, although the screen comes up with the options of things to do (restore etc.), when selected it just hangs with a black screen.
I checked some other similar threads but couldn't come up with anything.
Please pardon any inanity - I'm very new to this.
Any help most gratefully accepted. Thanks
when selected it just hangs with a black screen.
Click to expand...
Click to collapse
When selecting the option use the centre trackpad to select not the power button...
However i'm also new to a Desire (i have a desire hd) and have exactly the same on the Desire i rooted with Unrevoked last night, for example if i try to wipe system or data it just comes up with an error message...
Any ideas thanks...
Just tried to run unrevoked again to see if recovery would install properly this time.
Yesterday it said it was a triumph this time it says failed to get root is the software to new...
Is that because its already rooted or it didn't actually work properly yesterday ?
Thanks
After reading a bit on google and on this forum seems that Unrevoked may be the issue someone else with the same problem got it sorted by using Unrevoked 3.21 rather than the 3.32 that the unrevoked website installs...
Next question anyone know where i can get 3.21 been googling and can't find anything that will actually download..
Again many thanks
wakers said:
After reading a bit on google and on this forum seems that Unrevoked may be the issue someone else with the same problem got it sorted by using Unrevoked 3.21 rather than the 3.32 that the unrevoked website installs...
Next question anyone know where i can get 3.21 been googling and can't find anything that will actually download..
Again many thanks
Click to expand...
Click to collapse
How about PMing the person who sorted the problem out to see if they still have 3.2.1 on their machine? I thought I did but on checking I've got 3.3.2 - sorry!
Hi
I had to use AlphaRev to be able to flash custom firmware. Unrevoked did root the phone but didn't s-off. If you plan to use Unrevoked VirtualBox method get VBox v3.xx, v4.xx has something messed with usb passthrough
Sent from my HTC Desire using Tapatalk
I managed to find a version of the unrevoked that was suggested but it hasn't made any difference...
I've been ages reading and going around in circles
The Hboot is 0.93.0001
The phone appears to be rooted as superuser is on it and appears to be working.
THe phone will boot into recovery but recovery doesn't work
I've tried using a different recovery with rom manager but it makes no difference when i boot into recovery its the same Clockworkmod recovery 2.5.0.7 even though in Rom manager it says its changed...
As it boots into recovery there are a few messages underneath
e:cant find misc:
e:cant mount cache : recovery/command
and a few other lines which i can't remember but similiar
I've tried removing and flashing a different recovery via adb and i get a message saying "remote not allowed"
I've tried flashing recovery with a terminal emulator but can't get it to work either.
Do i need to do the alpharev to get S-Off first before i can sort out recovery ? and if so any info on how to do this, again many thanks and sorry for so many questions.
I've rooted Magic's, Legends, HD2's and my Desire HD but this desire for my missus does have me a bit stumped...
I wonder if fake flash would help in this situation?
Might be a viable way to get recovery functioning...
http://forum.xda-developers.com/showthread.php?t=698403
As it boots into recovery there are a few messages underneath
e:cant find misc:
e:cant mount cache : recovery/command
and a few other lines which i can't remember but similiar
These look like about the same as the ones I get
OK... I don't know why, but this worked for me (and my guru). Instead of pressing the power button as the enter button during the rooting and restore process, we pressed the mouse button and it all worked fine. The errors still showed up but they didn't cause any problems. I think this might have been one of the first suggestions but I seem to have missed it (this is what you get when you stay up 'til stupid-o'clock trying to sort stuff out).
I'm up & running now and I hope this helps some others having the same issues.
Thanks to all those who provided suggestions.
gen_scheisskopf said:
Hi
I had to use AlphaRev to be able to flash custom firmware. Unrevoked did root the phone but didn't s-off. If you plan to use Unrevoked VirtualBox method get VBox v3.xx, v4.xx has something messed with usb passthrough
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Just to clarify this point, Rooting and S-OFF are 2 totally different things.
Root access is to the loaded ROM on the phone. It allows you to gain access to places you normally can't go inside android like \system and \recovery
S-OFF is turning signature verification off in the Bootloader. the bootloader is the lowest system level you can go and as such can do some pretty serious things there.
jimmytheflea said:
Just to clarify this point, Rooting and S-OFF are 2 totally different things.
Click to expand...
Click to collapse
Yes, I know this. S-Off option was selected in Unrevoked menu (and didn't work). AlphaRev 1.8 (LiveCD) didn't work on unrooted phone but after rooting did it's job
Finally success i think sometimes you can read so much info you get confused.
Did alpharev via CD and installed alpharev-cwm recovery option and its all working as it should be, can't believe how simple it turned out to be in the end...
Thanks to all who replied much appreciated...
Hello, i am using oxygen 2.0.3 ROM now. I had been flashing roms with recovery for a few times. But now, it seems like recovery is unable to detect changes to my sdcard.
Whenever i boot into recovery to install zip from sdcard, it will show me the folders and zip files that i had before. Any changes i made to the sdcard was not reflected.
I search through the web and this forum and you seems to have the closest issue that i am experiencing. It would be great if you can advice if your method can solve my problem as well and what are the detail steps you took to solve it. Thanks alot man.
Hi mate the issue i had was that recovery didn't seem to install properly at all and i could see the rom etc on the sdcard and any changes i made but it wouldn't work, i also had issue's with not being able to push commands through adb.
What worked for me was creating the Alpharev ISO image on a CD and running it following the instructions, it was incredibly simple but i had a stock rooted rom on my desire.
The alpharev instructions are here
http://alpharev.nl/
Downloadf the Flash utility then burn the flash utility (still zipped) to a CD shut down your laptop press F12 as it boots choose boot from CD once the laptop screen goes black plug your phone in (i had mine on charge only) you also need to make sure USB debugging is checked...
And follow the instructions for me it S-Off'd the phone and installed the Alpharev-CWM recovery which is working as it should...
Not sure thats going to cure your issue though as it seems you have an issue with your recovery reading the SDcard this wasn't an issue for me...
cheongster said:
Hello, i am using oxygen 2.0.3 ROM now. I had been flashing roms with recovery for a few times. But now, it seems like recovery is unable to detect changes to my sdcard.
Whenever i boot into recovery to install zip from sdcard, it will show me the folders and zip files that i had before. Any changes i made to the sdcard was not reflected.
I search through the web and this forum and you seems to have the closest issue that i am experiencing. It would be great if you can advice if your method can solve my problem as well and what are the detail steps you took to solve it. Thanks alot man.
Click to expand...
Click to collapse
Do you see changes made to sd card when booted rather than in recovery i.e. if you add a zip to SD and reboot to your rom, do you see the SD, then you don't see it if you reboot again to recovery?
stringer7 said:
Do you see changes made to sd card when booted rather than in recovery i.e. if you add a zip to SD and reboot to your rom, do you see the SD, then you don't see it if you reboot again to recovery?
Click to expand...
Click to collapse
Yes. I see the changes made to the SD card in my ROM. But the changes don't get reflected when i am in recovery.
Is your issue occurring after you mount the card in usb mode in recovery and then adding file and then trying to flash that zip? if so, then you can see that file by choosing reboot recovery option
Swyped with my Starburst Classic based Desire with Intelligent Data2sd
I transfer the files while i turn on the usb for data transfer in the rom. Do i have to do the file transfer while i'm in recovery?
I used to be able to do it previously. I am not sure what happened along the way and it stopped working now. I did delete all the files on my SD card before having this issue. Not sure if thats the course and if there is a fix for that.
Thanks!
Well if you were doing it while booted up, sorry I have no idea why it doesn't work then.
Solution is to reflash your recovery
Swyped with my Starburst Classic based Desire with Intelligent Data2sd

[Q] General rooting and ROM questions

Hi guys, I've had a Bell-branded Desire Z (on AT&T's network) for some time now, but I've never gotten around to rooting / flashing a different ROM on it. Since I have some free time this weekend, I figure I'll finally tackle it. Have a few general questions though:
1) Is the method listed in the guide: http://forum.xda-developers.com/showthread.php?t=928160 still the best method for rooting a desire Z? I've heard bad things about visionary, but every rooting method I've read seem to involve it in some way.
2) with S-OFF, am I free to flash any Desire Z / G2 ROM? or will only certain ROMs work with a Bell Desire Z? Any specific recommendation on ROMs? I'm planning on trying out CM7, then going from there
3) What is the best method for backing up my current image + a few other things (mostly contacts and SMS)? Titaniumbackup gets thrown around a lot, but I only have a handful of apps, and really would rather just redownload them then go through the trouble of backing them up
Thanks
http://wiki.cyanogenmod.com/index.php?title=TMobile_G2:_Rooting
that is going to be your safest way to root your vision. eventhough this is longer, there is a lot less chance of bricking your phone. the one you listed is very simple to do, but runs a high risk of turning your phone into a paper weight.
when you do have your phone completely s off, you now have every right to flash kernels, roms, and other things. you can find all of the things i just listed over in the development forum on the g2/desire z. download rom manager from the market. that allows you to back up your current rom, flash the latest recovery and so on. it just allows you to not have to manually install everything. it has the popular g2 roms under the "download rom section".
in terms of backing up everything, there are a few different options. every contact to save is linked to your gmail account, so whatever rom you flash and load youll always have those contacts coming with you. thats the beauty of google and gmail on a android device! but with rom manager, you can back up your current rom and image with that app and save it to your sd card. BEFORE YOU FLASH ANY ROM, OR BEGIN TO START TRYING OUT ROMS, BACK UP YOUR STOCK ROM. whenever i got my g2 when it first came out, i made a nandroid backup of my stock rom and i still have it. when i originally backed it up, i just named it "stock" and havent messed with it since. i just know that i have the stock image(it helps me sleep at night). jk, heh. for your text messages and stuff, download sms backup from the market and you can back everything up through that. all of the apps that you download, including the paid ones of course, travel with you between roms, etc.
i hope i helped ya out, and i wish you luck. if you have any other questions, just shoot me a private message!
Thanks for that;
I actually went ahead and used that method in the guide since upon further research, it seems that visonary was only causing issues when it was use for perm root; temp root, which is what that method uses visionary for seems to work fine.
So did that, reboot into the bootloader, confirmed that I had S-OFF on the first line.
Installed ROM manager from the market
Flashed Clockwork recovery
Booted into recovery and did a system backup to SD card
Rebooted and decided to download the Virtuous ROM from ROM manager
Told it to reboot into recovery and flash that image, wiping all data and settings
Got stuck on an bootup loop (HTC logo + start up sound -> black screen -> HTC logo + startup sound ad infinitum)
Rebooted into recovery, and did a restore from the backup (whew)
Phone seems to be working fine now
Now I'm trying to figure out what went wrong... any ideas?
K, I redownloaded virtuous from XDA, checked the MD5, and tried to flash it again.
Same problem, infinite loop on startup screen.
Do i need to flash the engineering hboot? I was under the impression that that wasn't necessary for using custom ROMs.
Still can't figure out what's wrong.
did you debrand? http://forum.xda-developers.com/showthread.php?t=835777
Have you tried flashing through CWM directly? I really don't like ROM Manager for flashing new ROMs and seems to oversimplify the process to allow green users to get on the flashing wagon.
I would boot into CWM (camera + power i think) and do a complete wipe + flash from in there. I have never had an issue with doing things directly from recovery and I have a Bell DZ as well. It's long since lost it's blue and white colours, but that was it's origin
Have fun!
Im new to this stuff here, and i DO want to learn about it as this stuff is very interesting to me! Technology is something i learn very quickly if im directed in the correct direction
The question i have here is about my Desire Z ( Bell Cannada ).
A few months ago we received a OTA update. So its currently running on Android 2.2.1 : Build - 1.84.666.2 CL322105, and its SUPER slow! Is it still possible to root this version?
I want to install the Gingerbread version on my phone, but i cant find instructions to root this OS version to be able to do so.
Or should i wait till the Official gingerbread Os to come out for our phones?
Ive been searching every where's for this info and everything i find is all back dated to last yr and nothing up-to-date after the OTA.
I hope this question is not TOO n00bish as i tried to search every where for it, and ether i could not find it or i did not enter the correct word search to get a result i needed.
Thanks in advance!
Andrew
Edit: NVM my question here.... i have finally found an update post within the wiki ( April 1 2011 )
Sorry for a useless post!
Thank you all for your efforts in posting in this forum! Very informative!
Athrun88 said:
Have you tried flashing through CWM directly? I really don't like ROM Manager for flashing new ROMs and seems to oversimplify the process to allow green users to get on the flashing wagon.
I would boot into CWM (camera + power i think) and do a complete wipe + flash from in there. I have never had an issue with doing things directly from recovery and I have a Bell DZ as well. It's long since lost it's blue and white colours, but that was it's origin
Have fun!
Click to expand...
Click to collapse
heh. that actually worked. Flashed directly from CWM recovery and it booted up with no issues.
Guess I know not to flash from ROM manager anymore
Thanks.
deaththeorist said:
did you debrand? http://forum.xda-developers.com/showthread.php?t=835777
Click to expand...
Click to collapse
You do not need to debrand to flash custom ROMs to the Bell Canada Desire Z.
makken85 said:
heh. that actually worked. Flashed directly from CWM recovery and it booted up with no issues.
Guess I know not to flash from ROM manager anymore
Thanks.
Click to expand...
Click to collapse
Interesting, I've flashed many ROMs from ROM Manager on my Bell Canada DZ, and never had an issue. That said, flashing from recovery is really not any harder, so if it works, it works.
redpoint73 said:
Interesting, I've flashed many ROMs from ROM Manager on my Bell Canada DZ, and never had an issue. That said, flashing from recovery is really not any harder, so if it works, it works.
Click to expand...
Click to collapse
Yeah, I assumed that flashing from ROM manager just meant that it rebooted to recovery and flashed it from there. I guess there is a difference.
Either way, been playing with Virtuous 1.0.2 for a few days now, really like this ROM, but I'm itching to try out something different now. Man, I can see this is going to develop into a time consuming hobby.
Plus, I'm going to need a bigger SD card to store all of these ROMs + backup =X
Oh, another noob question; I've come across a few zip files that included a system folder and an META-INF folder. How exactly do I install these?
G2 only works with at&t
alright here it is my t-mobile G2 won't connect to the t-mobile network at all, I've went through 3 SIM cards because this thing use to kill the SIM card from working on other t-mobile phones and it works perfectly fine on at&t network. so I've unlocked so it will work on at&t just to see if it would work. so i gave p and bought a MT 4G, but i still want to know if the G2 is fixable because I'm just about ready to throw in the towel this is what I've tried to resolve the problem called t-mobile they ended up saying just return the phone but i can't since i didn't buy it from them. Called them again got the unlock code. I've flashed the radio a few times. I've also just got the leaked 2.3.3 update and nothing has worked. It find t-mobile network but says your SIM card isn't allowed to connect to this network then after trying again it says unable to connect to network please try again later.
Just so frustrating i don't know what to do just about to say forget it. this thread is my last resort.
also i still have S-OFF
i used this method on my G2 just yesterday and put on CM7.0.3. the only issues i came across were because i restored everything (should have just done apps and app data) using Titanium, which put me in a boot loop. I'm dumb, so i did it twice before i figured out what was the problem. the thread has a comment about how Visionary is dangerous, but the OP responded that since it is only used to gain temp root, there should be no problems.

Boot Loops, forever.

So, I don't really post on forums because I'm pretty tech-savvy, but I have a big problem that I can't fix, and I can usually fix everything (thanks to you guys!)
This morning, my incredible acted up as I was checking an e-mail and it froze, so I decided to battery pull because restarting my phone didn't work. (Note, my incredible has been running VERY solidly on a CM7.1 nightly). As I tried to boot up the phone again, it would stay on the white HTC Incredible screen. When I rebooted into recovery thru HBOOT, i realized that there was an error mounting something, like recovery_log, or something like that (i didn't mind this because I thought I knew what I was doing), but I tried restoring my old nandroid backup that was working well, but it didn't work. It said it couldn't format /data or something... It ended up staying on the white HTC incredible screen. So, I wiped data/cache like 10 times, and dalvik cache as well and tried re-flashing a clean install of cm7.1 stable, but didn't work again - led me straight to the white Incredible screen. So, installing a fresh rom AND restoring a solid backup didn't work... so...
I found the RUU 2.3 stock rom on the development forums, and tried to install that like I do with the radios (PB31IMG.zip) through HBOOT, but no cigar. It did go PASSED the white screen, but boot loops at the Droid eye.
So, I thought I'd find a different stock img, and found the 2.2 official OTA .zip and installed it the same way, but got the exact same result (boot loops, forever).
Any suggestions? I can't think of anything else.... I feel like my phone is bricked, but I didn't do anything to make that happen.
I feel like something happened that made me not able to format the /data, and stuff. I even formatted my SDcard in case it was the problem.
Any help is appreciated. Thanks!
Load the RUU onto a different fat32 sd card and see if you are able to boot.
Sent from my ADR6300 using XDA Premium App
i'll try that and give an update. thanks for the reply!
*update* no luck. same thing happens. i tried on three different sdcards formatted fat32...
Can you factory reset and flash a ROM from a different sd than the one you were using? Description sounds like bad sd, and AOSP roms interact with the sd on boot. If original (CM 7) sd is toast, it'll never boot, hence different sd card and prefably RUU
Sent from my ADR6300 using XDA Premium App
I had this happen once where no matter what rom i flashed all i got was bootloops. I had to get the stock froyo ruu.exe that you run from your pc and install it that way. Then once installed boot up and go to settings/sd & phone storage and do a factory reset from there. This factory reset is a true reset as it wipes out vzw programing also. After reset folow on screen steps to reactivate your phone, you can skip the rest of the setup. Once thats done your good to go just flash clockwork or amon ra recovery and then flash what ever rom you want. No guarantees but it worked for me.
NOTE: This assumes you are s-off, if your not after flashing the ruu you will have to use unrevoked to regain root and s-off again.
You can also try wiping /system and /boot.
*token post to get my post count high enough to ask for help in the hacking section, dumb rule btw. FAIL*
Mine is now stuck in a continuous boot as well. It's not rooted and have no idea how to fix it.
I see instructions in this thread but they mean nothing to someone who doesn't know what the abbreviations stand for or how to go about the commands required.
sl4m said:
*token post to get my post count high enough to ask for help in the hacking section, dumb rule btw. FAIL*
Mine is now stuck in a continuous boot as well. It's not rooted and have no idea how to fix it.
I see instructions in this thread but they mean nothing to someone who doesn't know what the abbreviations stand for or how to go about the commands required.
Click to expand...
Click to collapse
if you are non root. you will need to download the RUU.exe for 2.2 and install if from you pc.
http://androidforums.com/htc-droid-...mplest-instructions-ever-windows-xp-only.html
follow that and your phone will be back to the day you got it out of the box.
All the recommendations prior to Synisterwolf's post require root.
Some of the "abbreviations" are detailed in the Droid Incredible Development section. If you head over there you can read up on a beginners guide to root terms and helpful links in one of the top four threads namely:
If You're New to Modding/Rooting, Read This First! (Updated 08/05/10)
I will say though:
CM7.1 = CyanogenMod 7.1 (this is a rom)
OTA = Over The Air
2.2 = Froyo (Android software version 2.2)
RUU = basically refers to a file that people use to revert back to the Droid Incredible's pre-root status. Although there are additional steps as well.
SlimSnoopOS said:
All the recommendations prior to Synisterwolf's post require root.
Some of the "abbreviations" are detailed in the Droid Incredible Development section. If you head over there you can read up on a beginners guide to root terms and helpful links in one of the top four threads namely:
If You're New to Modding/Rooting, Read This First! (Updated 08/05/10)
I will say though:
CM7.1 = CyanogenMod 7.1 (this is a rom)
OTA = Over The Air
2.2 = Froyo (Android software version 2.2)
RUU = basically refers to a file that people use to revert back to the Droid Incredible's pre-root status. Although there are additional steps as well.
Click to expand...
Click to collapse
RUU = ROM Update Utility
no luck, I installed the program on my XP machine, but the app can't connect to the phone.
The phone literally keeps rebooting over and over.
sl4m said:
no luck, I installed the program on my XP machine, but the app can't connect to the phone.
The phone literally keeps rebooting over and over.
Click to expand...
Click to collapse
Then its gotta be a hardware failure.
Sent from my sexy assistant. (AMOLED HTC Incredible)
wow... what a bummer. thanks for the help anyway, it's much appreciated.
sl4m said:
no luck, I installed the program on my XP machine, but the app can't connect to the phone.
The phone literally keeps rebooting over and over.
Click to expand...
Click to collapse
Does it give any specific error code when it says it can't connect to the phone?
Someone correct me if I'm wrong but don't you have to have HTC sync installed on your pc to use an ruu.exe? Do you have that installed?
Sent from my ADR6300 using xda premium
I'll try it again to verify the code, I'm pretty sure it was "170"
sl4m said:
*token post to get my post count high enough to ask for help in the hacking section, dumb rule btw. FAIL*
Mine is now stuck in a continuous boot as well. It's not rooted and have no idea how to fix it.
I see instructions in this thread but they mean nothing to someone who doesn't know what the abbreviations stand for or how to go about the commands required.
Click to expand...
Click to collapse
I had this issue the first time i rooted my phone and attempted to put on a ROM, and i resolved it when i found this post to get back to stock. I also used this to fix a problem where my phone had a black screen with a line through it on booting to recovery or attempting to do a nandroid back up:
droidforums.net/forum/droid-incredible-hacks/95406-how-correctly-unroot-incredible.html
All i did was basically use the PB31IMG Method without turning s=on, ( i had stock radio and still have 7.28 )
1) download that PB31IMG.zip and drop it on the root of your sd card ( it has to be named ( PB31IMG.zip ) so make use you have file extensions showing on your PC.
2) boot to hboot and and let see the file and install it
3) used unrevoked ( remove sd card ) to aquire root again.
idk if this helps, but this seems to get me out of the few weird situations i had
sl4m said:
I'll try it again to verify the code, I'm pretty sure it was "170"
Click to expand...
Click to collapse
Check this out to fix your 170 error.
http://androidforums.com/incredible...170-171-solution-windows-7-a.html#post1472468
This low key happened to me and I booted in to HBOOT and went to clear storage and it did its thing and booted up, from there I had to activate it then I was set!
Sent from my ADR6300 using XDA App
=D
Sent from sweet snacks off tapatalk.

[Q] Completed Factory Reset (MIUI) and SDCard format and now soft-bricked!

Hey folks,
Thanks for taking the time to read/assist. I don't typically do these kinds of posts and am at my wit's end!
Phone's Previous Setup - MIUI Gingerbread, Rooted (but with S-ON after the fact).
What happened:
My HTC Incredible finally got to the point of being practically unuseable with laggy behavior and random restarts and the like, so I decided to complete a reset to factory settings or wipe.
I completed my backups using Titanium (apps) and ClockworkMod Recovery (full backup). After this, I went ahead and opened up Settings and directed the phone to complete a Reset to Factory Settings. It ran through the process, rebooted, and came up jelly. While no custom apps were installed (expected), my folder settings on my main home page were saved, along with some previous text messages. I was pleasantly surprised.
From here, I wished to wipe the SD Card so as to make sure it was clean of any residual folders/files that might cause conflict down the road (based on advice from others). So, headed to the SD card part of the settings. Had to unmount the SD card to format, proceeded to do so.
Here's where things went wonky: Despite receiving a confirmation that the SD card format had proceeded, nothing else ever happened. I attempted to mount the card again w/o luck (kept getting a msg that it was now unmounted). Eventually, I decided to go ahead and restart the phone and see if that helps. Big mistake.
From this point forward, the phone refuses to fully start up into any Android ROM. Initially, it hung on the white HTC Incredible splash screen (yes, even w/ giving it an hour+ of time). I tried wiping and reflashing different ROMS over the period of the day yesterday to no avail.
Doing a full recovery via ClockworkMod (from my backup that I made before and copied back onto the SD card via USB) leaves me stuck on the HTC Incredible white splash screen.
MIUI - 2.2.10
Hangs on white splash screen
No go w/ or w/o SD card installed
MIUI - 2.2.17
Loads past white and MIUI splash screens
Instead of loading into Android homescreen, immediately loads up "Encryption" error and directs to "reset phone."
Repeated restart and attempts of resetting phone don't work
No go w/ or w/o SD card installed.
MIUI - 1.12.9
Hangs on white splash screen.
No go w/ or w/o SD card installed.
CM - 7.1.0
Hangs/loops on CM splash screen.
No go w/ or w/o SD card installed.
CM - 6.1.0
Hangs/loops on CM splash screen.
No go w/ or w/o SD card installed.
I looked into HBOOT options, getting PB31IMG.ZIP and PG86IMG.ZIP.img thinking maybe I could try reverting to stock at a friend's suggestion. HBOOT sees the files and "checks" them, even briefly showing a small vertical blue loading bar at the top-right corner, but never attempts to run/update them as I am lead to expect from all the instructions/encounters I've found on the net suggest. The screen info flashes by so quickly, I can barely read it, but I confirmed that it said "checking" and not updating or such. x.x
I considered trying to flash an updated copy of ClockworkMod Recovery, but I cannot do that w/o being able to load up the phone into Android.
I cannot run anything desktop-side, like ADB, as they all require the phone started up and put into USB-debugging mode.
I've looked into and tried all this and more, but nothing seems to be working.
My next idea is to try to forcibly downgrade the phone. Reasoning being that I read that the HBOOT will not try to update if it senses that the ROM is newer than its default settings(?). So, I need a good choice of "old" ROM that I can attempt to install via the HBOOT or CWM Recovery, and verify I have the correct files for HBOOT to try updating/running.
Again, this is a speculative attempt, but I'm willing to try whatever might work! Otherwise, I've got a fancy brick and my well-being on the line w/ no $$ to replace the phone. x.x
Thanks again for reading and hopefully offering some wonderful assistance! Sorry it's so long!
Feel free to ask Qs if you need clarification on stuff.
wigmuke said:
Hey folks,
Thanks for taking the time to read/assist. I don't typically do these kinds of posts and am at my wit's end!
Phone's Previous Setup - MIUI Gingerbread, Rooted (but with S-ON after the fact).
What happened:
My HTC Incredible finally got to the point of being practically unuseable with laggy behavior and random restarts and the like, so I decided to complete a reset to factory settings or wipe.
I completed my backups using Titanium (apps) and ClockworkMod Recovery (full backup). After this, I went ahead and opened up Settings and directed the phone to complete a Reset to Factory Settings. It ran through the process, rebooted, and came up jelly. While no custom apps were installed (expected), my folder settings on my main home page were saved, along with some previous text messages. I was pleasantly surprised.
From here, I wished to wipe the SD Card so as to make sure it was clean of any residual folders/files that might cause conflict down the road (based on advice from others). So, headed to the SD card part of the settings. Had to unmount the SD card to format, proceeded to do so.
Here's where things went wonky: Despite receiving a confirmation that the SD card format had proceeded, nothing else ever happened. I attempted to mount the card again w/o luck (kept getting a msg that it was now unmounted). Eventually, I decided to go ahead and restart the phone and see if that helps. Big mistake.
From this point forward, the phone refuses to fully start up into any Android ROM. Initially, it hung on the white HTC Incredible splash screen (yes, even w/ giving it an hour+ of time). I tried wiping and reflashing different ROMS over the period of the day yesterday to no avail.
Doing a full recovery via ClockworkMod (from my backup that I made before and copied back onto the SD card via USB) leaves me stuck on the HTC Incredible white splash screen.
MIUI - 2.2.10
Hangs on white splash screen
No go w/ or w/o SD card installed
MIUI - 2.2.17
Loads past white and MIUI splash screens
Instead of loading into Android homescreen, immediately loads up "Encryption" error and directs to "reset phone."
Repeated restart and attempts of resetting phone don't work
No go w/ or w/o SD card installed.
MIUI - 1.12.9
Hangs on white splash screen.
No go w/ or w/o SD card installed.
CM - 7.1.0
Hangs/loops on CM splash screen.
No go w/ or w/o SD card installed.
CM - 6.1.0
Hangs/loops on CM splash screen.
No go w/ or w/o SD card installed.
I looked into HBOOT options, getting PB31IMG.ZIP and PG86IMG.ZIP.img thinking maybe I could try reverting to stock at a friend's suggestion. HBOOT sees the files and "checks" them, even briefly showing a small vertical blue loading bar at the top-right corner, but never attempts to run/update them as I am lead to expect from all the instructions/encounters I've found on the net suggest. The screen info flashes by so quickly, I can barely read it, but I confirmed that it said "checking" and not updating or such. x.x
I considered trying to flash an updated copy of ClockworkMod Recovery, but I cannot do that w/o being able to load up the phone into Android.
I cannot run anything desktop-side, like ADB, as they all require the phone started up and put into USB-debugging mode.
I've looked into and tried all this and more, but nothing seems to be working.
My next idea is to try to forcibly downgrade the phone. Reasoning being that I read that the HBOOT will not try to update if it senses that the ROM is newer than its default settings(?). So, I need a good choice of "old" ROM that I can attempt to install via the HBOOT or CWM Recovery, and verify I have the correct files for HBOOT to try updating/running.
Again, this is a speculative attempt, but I'm willing to try whatever might work! Otherwise, I've got a fancy brick and my well-being on the line w/ no $$ to replace it. x.x
Thanks again for reading and hopefully offering some wonderful assistance! Sorry it's so long!
Feel free to ask Qs if you need clarification on stuff.
Click to expand...
Click to collapse
You need to gain s-off again before flashing with clockwork. How come you turned it back on?
"In a nutshell, S-OFF means that the NAND portion of the device is unlocked and can be written to. The default setting for HTC’s devices is S-ON, which means that neither can you access certain areas of the system nor can you guarantee a permanent root. Furthermore, signature check for firmware images is also ensured by the S-ON flag."
edit:
gain s=off boot into CMW wipe data, and factory reset. Flash a new rom of your choice and then boot. should get you back to a working phone.
synisterwolf said:
You need to gain s-off again before flashing with clockwork. How come you turned it back on?
"In a nutshell, S-OFF means that the NAND portion of the device is unlocked and can be written to. The default setting for HTC’s devices is S-ON, which means that neither can you access certain areas of the system nor can you guarantee a permanent root. Furthermore, signature check for firmware images is also ensured by the S-ON flag."
edit:
gain s=off boot into CMW wipe data, and factory reset. Flash a new rom of your choice and then boot. should get you back to a working phone.
Click to expand...
Click to collapse
The first time my phone was rooted/flashed, my bf did it for me. He used Unrevoked to root it and install CWM Recovery (v2.5.1.2 presently). I recall conversation being that having S-On would be better security with regards to the cell carrier (e.g., good to leave on, bad if off as they can see you rooted). So I agreed to having it put back to S-On, which I understood he then took care of.
Fast-forward a year and he now tells me he didn't actually end up running the other Unrevoked (Forever) tool to put S-On back in place, but that it simply *was*, so he left it that way. o.o;
Keep in mind, I've flashed 3 different ROMs since he originally rooted and flashed, w/o issues.
I pulled up everything to try re-rooting it again (to gain S-Off), but the instructions required having the phone loaded up and in debugging mode, which I cannot do as I cannot start up the phone past recovery in the first place.
Did I miss something that allows it via recovery? Going to check again in the meantime.
wigmuke said:
The first time my phone was rooted/flashed, my bf did it for me. He used Unrevoked to root it and install CWM Recovery (v2.5.1.2 presently). I recall conversation being that having S-On would be better security with regards to the cell carrier (e.g., good to leave on, bad if off as they can see you rooted). So I agreed to having it put back to S-On, which I understood he then took care of.
Fast-forward a year and he now tells me he didn't actually end up running the other Unrevoked (Forever) tool to put S-On back in place, but that it simply *was*, so he left it that way. o.o;
Keep in mind, I've flashed 3 different ROMs since he originally rooted and flashed, w/o issues.
I pulled up everything to try re-rooting it again (to gain S-Off), but the instructions required having the phone loaded up and in debugging mode, which I cannot do as I cannot start up the phone past recovery in the first place.
Did I miss something that allows it via recovery? Going to check again in the meantime.
Click to expand...
Click to collapse
actually its better to keep it s=off so this type of situation wont happen. Your carrier cant see your hboot from my understanding on how this phone works. They dont care if you have root or not, unless you are trying to exchange the phone for another one from them or for insurance reasons. With root you only void your warranty on the phone and not your contract or anything to do with VZW. S=off is just a NAND lock, meaning you cant add your own custom recover to the phone, and you are limited to builds that come from VZW themselves (ie the security signature check).
If you ever want to take the phone back to them because its defective or call insurance then you need to remove root and S=on. but thats the only time you need to toggle the NAND lock.
ok so you will need to ruu to stock, downgrade then gain s=off over again:
for the ruu for GB:
http://forum.xda-developers.com/showthread.php?t=1227279
a guide to do this all after you ruu:
http://forum.xda-developers.com/showthread.php?t=1306400
OMG I may've gotten it!
So I decided to give things another go with attempting to revert to stock again, as at this point, nothing is going to work other than via HBOOT.
I completed another reformat of the SD Card (Fat32) to be on the overcautious side and copied over ONLY the PB32IMG.zip file and restarted into HBOOT.
(Ah.. new user, so not allowed to post the link of where I got it.)
This time, much like before, it scanned, found the file, and did a parsing/loading. However, THIS TIME it actually prompted me to update! I chose yes (Vol+) and let it do its thing.
At this time, I am happy to announce that it actually is back up stock!
Wooohoo! Now to get it back to how I like it again. XD
If nothing else, hope this information helps someone else later on.
wigmuke said:
OMG I may've gotten it!
So I decided to give things another go with attempting to revert to stock again, as at this point, nothing is going to work other than via HBOOT.
I completed another reformat of the SD Card (Fat32) to be on the overcautious side and copied over ONLY the PB32IMG.zip file and restarted into HBOOT.
(Ah.. new user, so not allowed to post the link of where I got it.)
This time, much like before, it scanned, found the file, and did a parsing/loading. However, THIS TIME it actually prompted me to update! I chose yes (Vol+) and let it do its thing.
At this time, I am happy to announce that it actually is back up stock!
Wooohoo! Now to get it back to how I like it again. XD
If nothing else, hope this information helps someone else later on.
Click to expand...
Click to collapse
You might have lost root if you did the ruu from hboot. to check download the app "super user" from market that will tell you if you still have root or not.
Alright, now that I'm back to stock and runnin' smoothly, I need to figure out what route to take for rooting and flashing. Everyone talks about Unrevoked3, but I've heard there're other newer tools, too.
What would you recommend?
....also, sorry for the weird delay/disjointed/incomplete responses. I keep forgetting that XDA severely limits my posting capabilities. I wanted to say super thanks wolf, for all your help and sticking with me! Your input is appreciated. And yes, I'm pretty sure I lost all root, etc. It is back to "out-of-the-box" stock as far as I can tell.
wigmuke said:
Alright, now that I'm back to stock and runnin' smoothly, I need to figure out what route to take for rooting and flashing. Everyone talks about Unrevoked3, but I've heard there're other newer tools, too.
What would you all recommend?
Click to expand...
Click to collapse
unrevoked3 is the easiest way. but you will need to downgrade to android 2.2 for the security exploit.
http://forum.xda-developers.com/showthread.php?t=1306400
Edit: fixed link
---------- Post added at 10:44 AM ---------- Previous post was at 10:35 AM ----------
wigmuke said:
....also, sorry for the weird delay/disjointed/incomplete responses. I keep forgetting that XDA severely limits my posting capabilities. I wanted to say super thanks wolf, for all your help and sticking with me! Your input is appreciated. And yes, I'm pretty sure I lost all root, etc. It is back to "out-of-the-box" stock as far as I can tell.
Click to expand...
Click to collapse
lol now worries. easiest way to get to the 10 limit is just pad the count in here. ie just say something 10 times and you are good to go.
synisterwolf said:
unrevoked3 is the easiest way. but you will need to downgrade to android 2.2 for the security exploit.
http://forum.xda-developers.com/showthread.php?t=1306400
Edit: fixed link
Click to expand...
Click to collapse
Good news, I'm on 2.2 stock right now (just checked to confirm). So should be able to just go ahead and run Unrevoked3 then.
Also, the most popular recovery I'm aware of is ClockworkMod Recovery. I found that it's up to version 5.0.2.0. Would you recommend anything else or know of a newer version?
Figure if I'm going to do this, might as well do it right.
wigmuke said:
Good news, I'm on 2.2 stock right now (just checked to confirm). So should be able to just go ahead and run Unrevoked3 then.
Also, the most popular recovery I'm aware of is ClockworkMod Recovery. I found that it's up to version 5.0.2.0. Would you recommend anything else or know of a newer version?
Figure if I'm going to do this, might as well do it right.
Click to expand...
Click to collapse
Nope I'm RunNing that one and it works well.
Sent from my sexy assistant. (AMOLED HTC Incredible)

Random Reboots Problem - please help

I simply have done all i can - and it seems that i cant do it right. Please consider to help me, because im noob.
Before i state my problem i should say that i have googled an crossed xda forum for 4 days and without any improvement.
Problem I have is that, my phone randomly reboots at no particular time or place - but here come the details:
First, for purpose of unlocking phone from SIM lock from carrier, it was S-OFFed and rooted by someone else (previous owner).
Rom was installed - Oxygen 2.3.2. and it worked for few months without bugs.
Then, one day it restarted and stuck in bootloops, but it came up for few seconds, or some time (but not for long), and then again restarted and so on. Eventually it held enough to do a factory reset which generally helped, but with one strange thing - clock couldnt sync and loosed about an hour for 5-6 hours (really strange).
Then i decided to try some other ROM hoping to resolve clock issue.
When I go into HBOOt it says:
--- AlphaRev ---
BRAVO PVT4 SHIP S-OFF
HBOOT-6.93.1002
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Aug 10 2010 17:52:10
Then i went here -> http://forum.xda-developers.com/show...p?t=1315961URL and done REALLY step by step whole procedure.
ROM was installed, along with -> http://forum.xda-developers.com/show....php?t=1408936
It worked flawllessly for about half an hour an then started rebooting on no particular action - sometimes went up for some time few secs to 10-20 mins an then reboot and sometimes it got stuck in endless loop (only pulling the battery helped).
Since it went wrong, i tried to RESTORE previosly made BACKUP of mentioned OXYGEN ROM, but sadly, same thing happened all the time.
I was devasteted, didnt know what to do so I decided to get back to STOCK ROM via RUU. (thought it would solve the problem)
I used RUU_Bravo_Froyo_HTC_WWE_2.29.405.14_Radio_32.49.00 .32U_5.11.05.27_release_224699_signed
Phone stayed S-OFF (obviosly for AlphaRev HBOOT) but have been preety stable comparing what was happening before, in terms: restarted few times for a day and allways rebooted back. Then i inserted other SIM card ant it began again with restarts as soon it went up and been up for 10-20 secs. After few reboots, it stabilised, but had different problem: couldnt add new account, and couldnt remove one I set up at the beginning (message said that i should do FACTORY reset if i want account removed). So I did factory reset - and NOTHING HAPPENED - evrything stayed exactly as it was - with account and everything.
Then i came across BORTAKs Guide ->http://forum.xda-developers.com/showthread.php?t=1275632 and followed step one, although it doesnt exactly match my probs - in terms that my phone boots up most of the time, but restarts randomly...
So I did what I was supposed to do and installed CyanogenMod after following step 10 Amon Ra's Recovery (I have PVT4 device) but same thing continues to happen - reboots, apparently on trying to add account on phone...
SORRY FOR SUCH LONG POST, but Im out of ideas, and new to this so PLEASE< PLEASE HELP me if u somehow can...
Thanks in advice
goxyendzy said:
I simply have done all i can - and it seems that i cant do it right. Please consider to help me, because im noob.
Before i state my problem i should say that i have googled an crossed xda forum for 4 days and without any improvement.
Problem I have is that, my phone randomly reboots at no particular time or place - but here come the details:
First, for purpose of unlocking phone from SIM lock from carrier, it was S-OFFed and rooted by someone else (previous owner).
Rom was installed - Oxygen 2.3.2. and it worked for few months without bugs.
Then, one day it restarted and stuck in bootloops, but it came up for few seconds, or some time (but not for long), and then again restarted and so on. Eventually it held enough to do a factory reset which generally helped, but with one strange thing - clock couldnt sync and loosed about an hour for 5-6 hours (really strange).
Then i decided to try some other ROM hoping to resolve clock issue.
When I go into HBOOt it says:
--- AlphaRev ---
BRAVO PVT4 SHIP S-OFF
HBOOT-6.93.1002
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Aug 10 2010 17:52:10
Then i went here -> http://forum.xda-developers.com/show...p?t=1315961URL and done REALLY step by step whole procedure.
ROM was installed, along with -> http://forum.xda-developers.com/show....php?t=1408936
It worked flawllessly for about half an hour an then started rebooting on no particular action - sometimes went up for some time few secs to 10-20 mins an then reboot and sometimes it got stuck in endless loop (only pulling the battery helped).
Since it went wrong, i tried to RESTORE previosly made BACKUP of mentioned OXYGEN ROM, but sadly, same thing happened all the time.
I was devasteted, didnt know what to do so I decided to get back to STOCK ROM via RUU. (thought it would solve the problem)
I used RUU_Bravo_Froyo_HTC_WWE_2.29.405.14_Radio_32.49.00 .32U_5.11.05.27_release_224699_signed
Phone stayed S-OFF (obviosly for AlphaRev HBOOT) but have been preety stable comparing what was happening before, in terms: restarted few times for a day and allways rebooted back. Then i inserted other SIM card ant it began again with restarts as soon it went up and been up for 10-20 secs. After few reboots, it stabilised, but had different problem: couldnt add new account, and couldnt remove one I set up at the beginning (message said that i should do FACTORY reset if i want account removed). So I did factory reset - and NOTHING HAPPENED - evrything stayed exactly as it was - with account and everything.
Then i came across BORTAKs Guide ->http://forum.xda-developers.com/showthread.php?t=1275632 and followed step one, although it doesnt exactly match my probs - in terms that my phone boots up most of the time, but restarts randomly...
So I did what I was supposed to do and installed CyanogenMod after following step 10 Amon Ra's Recovery (I have PVT4 device) but same thing continues to happen - reboots, apparently on trying to add account on phone...
SORRY FOR SUCH LONG POST, but Im out of ideas, and new to this so PLEASE< PLEASE HELP me if u somehow can...
Thanks in advice
Click to expand...
Click to collapse
Did you try to run RUU after flashing Alpharev downgrade to achieve S-ON gain, or you just ran it over Alpharev stock?
Also did you try to format sd card or to remove it from phone and than to boot it up?
It all seems like it was SIM unlocked by a "fake" code so that are the issues that can happen.
Plus: to gain SIM unlock you don't need S-off and root.
nlooooo said:
Did you try to run RUU after flashing Alpharev downgrade to achieve S-ON gain, or you just ran it over Alpharev stock?
Also did you try to format sd card or to remove it from phone and than to boot it up?
It all seems like it was SIM unlocked by a "fake" code so that are the issues that can happen.
Plus: to gain SIM unlock you don't need S-off and root.
Click to expand...
Click to collapse
I ran it over Alpharev... Im really new to this so i ask for help.
U say that i should:
1) flash AlphaRev downgrade to achieve S-ON gain (HOW exactly? please link to some guide if exists)
2) then run RUU
I tried formatting SD card later, removed it, even change card and latest ROM (Cyanogen) is on other SD card and its all the same...
Thanks for fast reply
goxyendzy said:
I ran it over Alpharev... Im really new to this so i ask for help.
U say that i should:
1) flash AlphaRev downgrade to achieve S-ON gain (HOW exactly? please link to some guide if exists)
2) then run RUU
I tried formatting SD card later, removed it, even change card and latest ROM (Cyanogen) is on other SD card and its all the same...
Thanks for fast reply
Click to expand...
Click to collapse
Yes, both steps. With that you will overwrite both hboot and radio to stock ones, that could be the things that made you problems. You will get S-on after flashing of RUU (I recomend 2.3) when your hboot is overwritten.
This is a good guide how to use ADB and fastboot (you will need fastboot for flashing of hboot):
http://androidforums.com/desire-all...fastboot-windows-updated-1st-june-2011-a.html
But reading your post I think that the problem is with unlocking (SIM). If a guy that sold you the phone said he did it with S-off and root he is laying, as I told you it can't be done with that. The problem can occur when you unlock the phone with a "fake code" that actually removes the part of phone's software used to check for carrier and not replacing critical parts (something like that).
There's a tool:
http://forum.xda-developers.com/showthread.php?t=943726
Try to run it and see what you will get.
nlooooo said:
Yes, both steps. With that you will overwrite both hboot and radio to stock ones, that could be the things that made you problems. You will get S-on after flashing of RUU (I recomend 2.3) when your hboot is overwritten.
This is a good guide how to use ADB and fastboot (you will need fastboot for flashing of hboot):
http://androidforums.com/desire-all...fastboot-windows-updated-1st-june-2011-a.html
But reading your post I think that the problem is with unlocking (SIM). If a guy that sold you the phone said he did it with S-off and root he is laying, as I told you it can't be done with that. The problem can occur when you unlock the phone with a "fake code" that actually removes the part of phone's software used to check for carrier and not replacing critical parts (something like that).
There's a tool:
http://forum.xda-developers.com/showthread.php?t=943726
Try to run it and see what you will get.
Click to expand...
Click to collapse
Thanks in advance, ill try everything when i setup everything properly. Will update on progress! :good:
OK, at fisrt I have removed both SIM and SD cards and then:
1) flashed AlphaRev downgrade to achieve S-ON
2) then run RUU
Inserted only SIM card, and for now without reboots - but this was only 15 mins ago, so ill keep informing about case after testing, in hope not to get another reboot ever.
What I realised is thatr I dont have recovery?
Is this supposed to be? And how will I resolve problem If something unwanted occur?
Thanks a lot for Your help!
goxyendzy said:
OK, at fisrt I have removed both SIM and SD cards and then:
1) flashed AlphaRev downgrade to achieve S-ON
2) then run RUU
Inserted only SIM card, and for now without reboots - but this was only 15 mins ago, so ill keep informing about case after testing, in hope not to get another reboot ever.
What I realised is thatr I dont have recovery?
Is this supposed to be? And how will I resolve problem If something unwanted occur?
Thanks a lot for Your help!
Click to expand...
Click to collapse
You have recovery, but it is stock one (pretty different to custom ones ).
Now after you flashed 2.3 RUU you probably have 1.02 hboot, so go here:
revolutionary.io
Download the tool and follow the process described to achieve s-off and root again (the problem you have have nothing connected with s-off and root but probably with some parts of system software which might be recovered now). During the process you will flash Clockworkmod recovery, from which you will install Superuser.apk. After that reboot the phone and go here:
4ext.net
Download Recovery updater, install it to your phone and flash 4ext recovery. Than from recovery you can restore backup you have from your old rom, but my suggestion is to go here:
http://forum.xda-developers.com/showthread.php?t=809328
and find something for you, cause I think that you have to start from scratch to have a proper software (cause you already had problems with previous one).
If you're up to Oxygen again go here:
http://download.oxygen.im/roms/
but I think that there are a few roms on previous link that are based on Oxygen, but a little bit modified with some extra options.
Well, thanks really, but for now I would like to live things as they are...
I dont mind beeng S-ON and not rooted, if phone doesnt reboot again. I just need it functioning, without advanced options.
Are U suggesting that STOCK ROM is not the way I should go?
goxyendzy said:
Well, thanks really, but for now I would like to live things as they are...
I dont mind beeng S-ON and not rooted, if phone doesnt reboot again. I just need it functioning, without advanced options.
Are U suggesting that STOCK ROM is not the way I should go?
Click to expand...
Click to collapse
It's the way I went for a long time until I started experimenting, mostly because a lack of space. After that I found the thread I posted (All things desire) and wanted to try some advanced roms (Sense 3.0, 3.5) even made some stuff on my own on that way.
http://forum.xda-developers.com/showthread.php?p=23101063#post23101063
My opinion is that stock roms are the best solution foe our device, cause it runs smoothest and I think that Sense is something that brings HTC devices above all other android devices. I've never been a fan of AOSP software but I tried it, just to see how it feels. I even used MIUI rom for some time as the first software option.
Anyway, the story with memory problem stays, but the main point for getting s-off and root again are diagnostic and flashing options cause on s-off device you can flash all crucial partitions that can cause problems (hboot and radio-see attachment) and change partition table layout to gain space (see alpharev.nl)
I hope I helped!
nlooooo said:
It's the way I went for a long time until I started experimenting, mostly because a lack of space. After that I found the thread I posted (All things desire) and wanted to try some advanced roms (Sense 3.0, 3.5) even made some stuff on my own on that way.
http://forum.xda-developers.com/showthread.php?p=23101063#post23101063
My opinion is that stock roms are the best solution foe our device, cause it runs smoothest and I think that Sense is something that brings HTC devices above all other android devices. I've never been a fan of AOSP software but I tried it, just to see how it feels. I even used MIUI rom for some time as the first software option.
Anyway, the story with memory problem stays, but the main point for getting s-off and root again are diagnostic and flashing options cause on s-off device you can flash all crucial partitions that can cause problems (hboot and radio-see attachment) and change partition table layout to gain space (see alpharev.nl)
I hope I helped!
Click to expand...
Click to collapse
Since there are no reboots yet (I really hope its in past) U have been more than helpful! :good:
I still havent inserted sd card, and been consedering of getting a new one (with higher speed).
Also, as I see that U R my countryman (ko ce kome ako ne svoj svome), U have earned a few drinks when U come to my town!
I will be updating how things are regarding of this case.
Cheers :highfive:
goxyendzy said:
Since there are no reboots yet (I really hope its in past) U have been more than helpful! :good:
I still havent inserted sd card, and been consedering of getting a new one (with higher speed).
Also, as I see that U R my countryman (ko ce kome ako ne svoj svome), U have earned a few drinks when U come to my town!
I will be updating how things are regarding of this case.
Cheers :highfive:
Click to expand...
Click to collapse
No problem, I'm holding you for your word!
If you have no reboots try to insert different carriers sim cards and see if it's still unlocked.
reboots again
nlooooo said:
No problem, I'm holding you for your word!
If you have no reboots try to insert different carriers sim cards and see if it's still unlocked.
Click to expand...
Click to collapse
Reboots again...
After half a day of normal usage, I tried inserting another SIM (but from same carrier) and it started again...
Not so often but from time to time it reboots.
So I guess, at the end it seems it is hardware fault.
One strange thing thou (and it makes me wonder): When I try removing account it says I should do Factory Reset if I want to change that basic acc. But afrer performing Factory Reset NOTHING happens? Account is still there, along with other settings and/or installed apps.
Any ideas?
Invitation still holds

Categories

Resources