Related
I'm having problems when sending sms messages and calls. Only 2 out of 5 messages that I send ever get to the other person's phone. Also, when I make a call I hear noises.
What I have done:
1-Try Updating my Radio (I'm in 2.15.00.07.28 and tried installing 2.15.00.09.xx. I did it using hboot, putting the .img on the sdcard and letting hboot do the rest but I'm still in 2.15.00.07.28 THE UPDATE DIDNT WORK)
2-Different ROMs.
3-Doing *228 several times.
Nothing has fixed the problems, please help me.
Phsyckr said:
I'm having problems when sending sms messages and calls. Only 2 out of 5 messages that I send ever get to the other person's phone. Also, when I make a call I hear noises.
What I have done:
1-Try Updating my Radio (I'm in 2.15.00.07.28 and tried installing 2.15.00.09.xx. I did it using hboot, putting the .img on the sdcard and letting hboot do the rest but I'm still in 2.15.00.07.28 THE UPDATE DIDNT WORK)
2-Different ROMs.
3-Doing *228 several times.
Nothing has fixed the problems, please help me.
Click to expand...
Click to collapse
Be very careful flashing radios. Section 3 of Dadicus' guide will tell you how. Couple of key points. Be sure to read thoroughly to avoid mistakes, make sure your sd card is FAT32, and don't rename the file. Leave it as default, which should be PB31IMG.zip. Of course, leave it on the root of the sd card, and update through HBOOT. Again, be careful.
Official Radio Thread
Thanks!
But I that's what I did trying to update the Radio and I want to try again (i know you arent suppoused to install the same radio twice, I wont I figured that it didnt update the first time I did beacuse the link on the Guide wasnt the last version but the same I already had before updating) Do you think updating the Radio would help me?
I'm at my wit's end here. I've tried searching around (I rarely, if ever, post) and I can't find a solution to my problem so I'm gonna try here.
First thing's first, Device Specs (HTC Evo 4G):
SUPERSONIC EVT2-3 ENG S-OFF
HBOOT-0.76.2000 (PC3610000)
MICROP-041f
TOUCH PANEL-ATMELC03-16ac
RADIO-2.15.00.11.19
Mar 30 2010,11:24:04
Rooted with unrevoked3
Second, what I was running:
Cyanogenmod 7.0 happily running for about a week
What I was doing (at time of crash): Getting coffee... I left my phone on top of my computer (installed Go SMS Pro about 10 minutes prior), came back and it was boot looping from htc evo 4g screen to htc evo 4g screen to etc...
I have tried everything to get this thing running. All I have is fastboot and the bootloader, I can flash recovery using fastboot but they will not load up... I have tried the 3.7 RUU annd it will only detect my device while in fastboot, it runs through the update and acts like it was successful but it goes back to boot looping. I have also tried to do a nandroid restore using fastboot and I can flash every partition (system, userdata, recovery, cache) EXCEPT boot, where I get a FAILED (remote: image update error) message.
Also, I have tried using the eng-pc36img.zip file and the normal PC36img.zip file and, something interesting, it will update all of the files , radio v2, bootloader, system etc.. etc.., but when it gets to "boot" it will immediately shut off, boot back into the bootloader, reload the zip file and continue where it left off... Is it supposed to do that?
Anyways, that is my plight. I hope I've been descriptive enough. Please help and thanks you!
n00barmy said:
I'm at my wit's end here. I've tried searching around (I rarely, if ever, post) and I can't find a solution to my problem so I'm gonna try here.
First thing's first, Device Specs (HTC Evo 4G):
SUPERSONIC EVT2-3 ENG S-OFF
HBOOT-0.76.2000 (PC3610000)
MICROP-041f
TOUCH PANEL-ATMELC03-16ac
RADIO-2.15.00.11.19
Mar 30 2010,11:24:04
Rooted with unrevoked3
Second, what I was running:
Cyanogenmod 7.0 happily running for about a week
What I was doing (at time of crash): Getting coffee... I left my phone on top of my computer (installed Go SMS Pro about 10 minutes prior), came back and it was boot looping from htc evo 4g screen to htc evo 4g screen to etc...
I have tried everything to get this thing running. All I have is fastboot and the bootloader, I can flash recovery using fastboot but they will not load up... I have tried the 3.7 RUU annd it will only detect my device while in fastboot, it runs through the update and acts like it was successful but it goes back to boot looping. I have also tried to do a nandroid restore using fastboot and I can flash every partition (system, userdata, recovery, cache) EXCEPT boot, where I get a FAILED (remote: image update error) message.
Also, I have tried using the eng-pc36img.zip file and the normal PC36img.zip file and, something interesting, it will update all of the files , radio v2, bootloader, system etc.. etc.., but when it gets to "boot" it will immediately shut off, boot back into the bootloader, reload the zip file and continue where it left off... Is it supposed to do that?
Anyways, that is my plight. I hope I've been descriptive enough. Please help and thanks you!
Click to expand...
Click to collapse
Well that certainly sounds no good man. It kind of sounds like your boot partition may be corrupted, so it's unable to write to that partition. You have already tried everything I would have suggested (RUU, RUU from fastboot, RUU from PC36IMG, tried reflashing recovery, etc). Your situation sounds identical to what people were experiencing in this thread, http://forum.xda-developers.com/showthread.php?t=1009672, and unfortunately no one ever found a solution, other than replacing the phone. I wish you luck, and hope you're able to recover with one of the available RUU's or PC36IMG.
Oh well...
k2buckley said:
Well that certainly sounds no good man. It kind of sounds like your boot partition may be corrupted, so it's unable to write to that partition. You have already tried everything I would have suggested (RUU, RUU from fastboot, RUU from PC36IMG, tried reflashing recovery, etc). Your situation sounds identical to what people were experiencing in this thread, http://forum.xda-developers.com/showthread.php?t=1009672, and unfortunately no one ever found a solution, other than replacing the phone. I wish you luck, and hope you're able to recover with one of the available RUU's or PC36IMG.
Click to expand...
Click to collapse
Well, shucks . I really wanted to be able to figure this out. I've tried and tried and tried and nothing seems to work. Oh, well thanks for putting my mind at ease. Sprint is already replacing it tomorrow. I just wanted to see if I could get this fixed now and be able to pass the information on to others who might be in the same situation. At least I was able to figure out how to downgrade from 2.10 to 0.76!
You don't know of any way of zeroing out the phone's partitions do you? Sorry if that is an odd request but I'm just brainstorming.
n00barmy said:
Well, shucks . I really wanted to be able to figure this out. I've tried and tried and tried and nothing seems to work. Oh, well thanks for putting my mind at ease. Sprint is already replacing it tomorrow. I just wanted to see if I could get this fixed now and be able to pass the information on to others who might be in the same situation. At least I was able to figure out how to downgrade from 2.10 to 0.76!
You don't know of any way of zeroing out the phone's partitions do you? Sorry if that is an odd request but I'm just brainstorming.
Click to expand...
Click to collapse
I apologize for the sour news, and wish there was a way for you to recover (maybe there is, but I'm just not aware of it). As far as zeroing out, or erasing all of the partitions, I'm not positive. I know you can do that using fastboot commands ( i beleve), but I don't have a ton of experience with fastboot, other than running an RUU. I'm sure someone else will chime in here and give you the fastboot commands to do that. It would be something like 'fastboot erase recovery', for example if you wanted to erase your recovery partition. I would google up on that a little bit, and see what all you can erase by using fastboot.
k2buckley said:
I apologize for the sour news, and wish there was a way for you to recover (maybe there is, but I'm just not aware of it). As far as zeroing out, or erasing all of the partitions, I'm not positive. I know you can do that using fastboot commands ( i beleve), but I don't have a ton of experience with fastboot, other than running an RUU. I'm sure someone else will chime in here and give you the fastboot commands to do that. It would be something like 'fastboot erase recovery', for example if you wanted to erase your recovery partition. I would google up on that a little bit, and see what all you can erase by using fastboot.
Click to expand...
Click to collapse
It's all good. Like I said, they're replacing it anyways, just more for my curiosity. Thanks for showing me that thread. Out of all the threads I looked at I, somehow, missed that one. I see y'all have been at this for a while and I will certainly be watching it even after I get my replacement. I guess I'll have to pull my battery doing a radio install...
Sucks to hear about your phone For my curiosity could you please answer a question or two. A lot of people are chalking this up as a "user error" while others are thinking its CM7 (i dont). Then there is the logical one, to much flashing. I see you do not post often, but you know what to do to get out of a jam, most anyway. Did you flash your phone often, like every time a new rom comes out you would try it? Or more of a moderate flasher, stick to a main rom and flash updates, not counting nightlies. Nightlies would be extreme flashing, lol. Thats all, I am just curious on flashing habits, you did say up downgraded Hboot. I am assuming you did this after the bootloops to gain fastboot access, correct? Downgrading Hboot with the new larger partitions will brick a Evo real quick! Personally I am thinking the reason for the new partitions is related to this problem starting to emerge. If there is a way to "erase" everything and write new partitions via fastboot, those of us with older partitions can avoid this sudden death loop, and fix them for those who catch it...
Just a thought
Thanks
n00barmy said:
Well, shucks . I really wanted to be able to figure this out. I've tried and tried and tried and nothing seems to work. Oh, well thanks for putting my mind at ease. Sprint is already replacing it tomorrow. I just wanted to see if I could get this fixed now and be able to pass the information on to others who might be in the same situation. At least I was able to figure out how to downgrade from 2.10 to 0.76!
You don't know of any way of zeroing out the phone's partitions do you? Sorry if that is an odd request but I'm just brainstorming.
Click to expand...
Click to collapse
When did your problem begin? Was it after you downgraded from hboot 2.10? That is a tricky and dangerous feat in and if itself. Can you get to the bootloader screen?
UPDATE: If you can get to the bootloader, try reflashing amon RA v2.3. If you're successful, I would then reflash all of the radios including hboot 2.10 and then a rom...in that order.
posting & replying via the XDA Premium app.
dougjamal said:
When did your problem begin? Was it after you downgraded from hboot 2.10? That is a tricky and dangerous feat in and if itself. Can you get to the bootloader screen?
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
My problem began last friday and no, I only tried the downgrading bit after it started looping. I wanted to be able to use the fastboot commands. Oddly enough, though. I just tried to run the eng-pc36img.zip again and now it did not immediately reset when trying to update "boot" but rather went through the whole thing... It still loops though...
Woah!
Now able to write to boot using fastboot flash boot boot.img...
n00barmy said:
Now able to write to boot using fastboot flash boot boot.img...
Click to expand...
Click to collapse
Forward progress is good. So you were able to do that after the last RUU ran? You said it didn't skip over writing the boot.img that time?? However it still loops? Where is it looping at? THe splash screen, correct?
k2buckley said:
Forward progress is good. So you were able to do that after the last RUU ran? You said it didn't skip over writing the boot.img that time?? However it still loops? Where is it looping at? THe splash screen, correct?
Click to expand...
Click to collapse
Yes, at the splash screen. It seems I can only manually write this one boot.img in my tools folder. Everything else gets a image update error in fastboot. I was not able to do that after the RUU because it changed my hboot to 2.10 (I think, don't quote me on that).
sucks
Damn im sorry to hear about this..i hope that as mentioned above it isnt from too much flashing!! Cause i am what i would call an extreme flasher..lol i flash just about every new rom that drops to try it out
n00barmy said:
Yes, at the splash screen. It seems I can only manually write this one boot.img in my tools folder. Everything else gets a image update error in fastboot. I was not able to do that after the RUU because it changed my hboot to 2.10 (I think, don't quote me on that).
Click to expand...
Click to collapse
I see. And yes, running the most recent RUU would indeed 'upgrade' your bootloader to 2.10.
k2buckley said:
I see. And yes, running the most recent RUU would indeed 'upgrade' your bootloader to 2.10.
Click to expand...
Click to collapse
I have a little more info. It seems that the only boot.img that flashes successfully through fastboot is the one located in the eng-pc36img.zip file. I cannot flash any from my nandroid backups from rom manager pro. I have not tried any other boot.img files from any other actual pc36img.zip files. I have another but that will set my hboot to 0.97.
Also, I doubt it is from too many writes. I am still fresh to rooting and I am not flash happy by any means...
n00barmy said:
I have a little more info. It seems that the only boot.img that flashes successfully through fastboot is the one located in the eng-pc36img.zip file. I cannot flash any from my nandroid backups from rom manager pro. I have not tried any other boot.img files from any other actual pc36img.zip files. I have another but that will set my hboot to 0.97.
Also, I doubt it is from too many writes. I am still fresh to rooting and I am not flash happy by any means...
Click to expand...
Click to collapse
I also doubt it's from writes. That would be a very hard sell on me. I have flashed hundreds of things I'm sure, between roms, kernels, mods, themes, etc. Probably more than hundreds, lol. I just dont see that causing it.
Keep in mind, that whatever hboot you were on when you created a nandroid backup, is the one you'd also need to be on when restoring it. Therefore, if you're using a boot.img from a nandroiid backup, then I'm fairly certain that you'd need to be on the same hboot as when you created the nandroid backup. I discovered this a few weeks ago, lol. Every nandroid backup I had made was created on .93 hboot. I then downgraded to the ENG. 76 hboot, and got careless and tried to restore a backup from when I was on .93 hboot. That did not go well, and resulted in me only being able to get to fastboot. Fortunately I still had recovery, so I had no problem recovering from that.
Anyways, I'm not sure what to suggest next, unfortunately. I will continue trying to come up with suggestions for ya, but for now I think it's pretty much trial and error for ya. I guess if you already have a new phone coming, you don't have much to lose by messing around with that one. I'm just not sure where to take it from there. I've been down that road, and I failed, lol. I just have no idea what prevents the RUU from running successful. Or even if it appears to be successful, it still yields boot loops. So I'm at a loss on what the actual cause of that may be.
k2buckley said:
I also doubt it's from writes. That would be a very hard sell on me. I have flashed hundreds of things I'm sure, between roms, kernels, mods, themes, etc. Probably more than hundreds, lol. I just dont see that causing it.
Keep in mind, that whatever hboot you were on when you created a nandroid backup, is the one you'd also need to be on when restoring it. Therefore, if you're using a boot.img from a nandroiid backup, then I'm fairly certain that you'd need to be on the same hboot as when you created the nandroid backup. I discovered this a few weeks ago, lol. Every nandroid backup I had made was created on .93 hboot. I then downgraded to the ENG. 76 hboot, and got careless and tried to restore a backup from when I was on .93 hboot. That did not go well, and resulted in me only being able to get to fastboot. Fortunately I still had recovery, so I had no problem recovering from that.
Anyways, I'm not sure what to suggest next, unfortunately. I will continue trying to come up with suggestions for ya, but for now I think it's pretty much trial and error for ya. I guess if you already have a new phone coming, you don't have much to lose by messing around with that one. I'm just not sure where to take it from there. I've been down that road, and I failed, lol. I just have no idea what prevents the RUU from running successful. Or even if it appears to be successful, it still yields boot loops. So I'm at a loss on what the actual cause of that may be.
Click to expand...
Click to collapse
Yeah, It's getting replaced so if you have any suggestions, go ahead. I'll try anything, I've got nothing to lose at this point. Maybe we can find a solution before I have to turn it in (hopefully). Thanks for the info on the hboot versions, I didn't know that. It makes sense though. I wonder if I can just switch the hboot from .97 to .76 in that one PC36img file I have and maybe it will run... Don't know but anyways...
Oh, I forgot to mention. I flashed an AmonRA v1.8 recovery earlier and while it didn't load it got farther than ANY other recovery I flashed. After the device shut down it said AmonRA v1.8 at the bottom of the black screen, for a split second, before it would go back into the HTC splash loop. It's not much farther but it worked "better" none the less... Anyways, just some food for thought
n00barmy said:
Yeah, It's getting replaced so if you have any suggestions, go ahead. I'll try anything, I've got nothing to lose at this point. Maybe we can find a solution before I have to turn it in (hopefully). Thanks for the info on the hboot versions, I didn't know that. It makes sense though. I wonder if I can just switch the hboot from .97 to .76 in that one PC36img file I have and maybe it will run... Don't know but anyways...
Oh, I forgot to mention. I flashed an AmonRA v1.8 recovery earlier and while it didn't load it got farther than ANY other recovery I flashed. After the device shut down it said AmonRA v1.8 at the bottom of the black screen, for a split second, before it would go back into the HTC splash loop. It's not much farther but it worked "better" none the less... Anyways, just some food for thought
Click to expand...
Click to collapse
That is very interesting that you saw the RA recovery 1.8 at the bottom of the screen for a second. What hardware version is your phone? I believe 1.8.0 is only for phones with the older erase block size, which is hardware 002, and some 003. Some of the later 003 models were the new erase block size, which is 0040000. The old size is 0020000. If you're 0040000, 1.8.0 wouldn't work anyways.
As far as changing hboots go, if you're on 2.02 or 2.10 currently, you can't easily downgrade. If you're on something other than those, you should be able to switch hboots easily.
Sent from my PC36100 using XDA App
irishgreen said:
Damn im sorry to hear about this..i hope that as mentioned above it isnt from too much flashing!! Cause i am what i would call an extreme flasher..lol i flash just about every new rom that drops to try it out
Click to expand...
Click to collapse
Same here. Sorry for asking in here but does anyone know is there limit?.... and if yes how many time you can flash it, or may just go randomly?
k2buckley said:
That is very interesting that you saw the RA recovery 1.8 at the bottom of the screen for a second. What hardware version is your phone? I believe 1.8.0 is only for phones with the older erase block size, which is hardware 002, and some 003. Some of the later 003 models were the new erase block size, which is 0040000. The old size is 0020000. If you're 0040000, 1.8.0 wouldn't work anyways.
As far as changing hboots go, if you're on 2.02 or 2.10 currently, you can't easily downgrade. If you're on something other than those, you should be able to switch hboots easily.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I'm actually not sure how to check that . But, As for the hboots, I have successfully downgraded from 2.10 to .076 three times as of right now. I have a few things I'm going to try in succession and I'll post the results .
n00barmy said:
I'm actually not sure how to check that . But, As for the hboots, I have successfully downgraded from 2.10 to .076 three times as of right now. I have a few things I'm going to try in succession and I'll post the results .
Click to expand...
Click to collapse
The only way to check that (that I know of) is issuing a command from a shell. it would be something like cat /proc/mtd.
Is this the method you've been using to downgrade hboot?? http://forum.xda-developers.com/showthread.php?t=883548&highlight=downgrade+hboot ? Otherwise, I'm not sure... As far as I always understood, if you had the newer erase block size (some 003 and all 004 hardware) then downgrading from 2.02/2.10 hboot was not even possible (without making a brick). If you had hboot 2.02/2.10 on the older erase block size then you would be able to successfully downgrade. Anyhow, good luck with your efforts and please post your results.
Hello everyone, I'm having a problem with my Data connection on my Tmobile-G2 after flashing new custom rom from stock.
My internet connection seems fine but even after a fresh flash I still cannot use my data. It seems to be a problem with a setting of some sort seeing as on 3 different ROMs this is happening. On the top i see my full H perfectly stable, and even in settings showing working data. But when opening apps I see "error - connection timed out)
(Could someone direct me with exactly how to flash a new radio, PC10IMG.zip on SD card and going into bootloader doesn't work, it simply says image/file not found. I have put the "PC10IMG.zip" into the root of my SD but on bootloader it does not recognize it. I've put both the .img file and zip filed renamed to "PC10IMG.zip" and "PC10IMG" and none of those variations work)
Current Radio : -12.28b.60.140eU_26.03.02.26_M-
Currently on Virtuous Sense v2.0.0 (MD5:b11fa8b0aaf14221f259a88efcfef978)
which is the best radio for TMOUS g2? I haven't gotten a chance to try.
Cheers, any help greatly appreciated.
If you poke around in the development forum for the G2, you can find guides for all of those things you are asking about! I'd post a few links I know where to find instantly, but alas I am on my phone.
Did you do a complete wipe of your phone through recovery before flashing that custom rom from stock? That may be your only problem there. Hopefully you did a nandroid backup - if so, revert to it in CWM and check that everything works.
Sent from my T-Mobile G2 using XDA Premium App
Everything works correctly now, reflashed everything from scratch and went to the store to get a new sim card. I just wished someone helped me with my radio flashing problem. Oh well, thanks for the post.
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
So 2 days ago a friend bought an HTC Desire HD. It was working fine, but since it was second hand he wanted to hard reset it, and so he did. After he did that it started doing what I am showing in the video below(but it was with an older version, gingerbread I think). It was also going in CWM 10 sec after it was put into a charger. After I tried installing custom roms and roots, I installed what is said to be a stock ruu:
RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed
Click to expand...
Click to collapse
It is obviously(visually) a newer version of the software the phone uses, than the one it had when he first gave the phone to me.
Nothing seems to have worked at this point, I'm desperate. After that 4th option of the setup(scheduled sync) it just goes black screen with a status bar and nothing. When he first gave it to me it used to display an error that said something like setup couldn't load, and with options to close it, wait for it, or tell HTC about it. It CAN receive SMS and calls, but there just isn't any GUI(menu, or whatever it's called).
I'm also providing a picture of the bootloader below.
I don't need the phone to be rooted or with any particular ROM or version, I just need it working normally.
Any help/assistance will be welcome! Thanks in advance
VIDEO:
youtube.com/watch?v=aNI1t4KjY-0&feature=youtu.be
youtube.com/watch?v=aNI1t4KjY-0&feature=youtu.be
Just makes it easier to click on it. :beer:
Edit: Try booting without the sd card, but aside from that, no idea.
You can also try flashing a stable gb rom see if you get the same issue.
Sent from a dream.
<-------- new user here. cant post links thanks
iLoveAlkohola said:
<-------- new user here. cant post links thanks
Click to expand...
Click to collapse
If you already have s-off and cwm, why not just flash rooted stock rom? It should work fine if the rom can be flashed successfully.
If it is not, it is most probably hardware issues, although i am not so sure myself.
yumm91 said:
If you already have s-off and cwm, why not just flash rooted stock rom? It should work fine if the rom can be flashed successfully.
If it is not, it is most probably hardware issues, although i am not so sure myself.
Click to expand...
Click to collapse
As I said, before installing the newest stock ruu(with which I lost cwm and can''t seem to get it back), I installed some custom roms, all of them with the same effect. But thanks for the suggestion.
iLoveAlkohola said:
As I said, before installing the newest stock ruu(with which I lost cwm and can''t seem to get it back), I installed some custom roms, all of them with the same effect. But thanks for the suggestion.
Click to expand...
Click to collapse
Make a full wipe before flashing the Ruu. Flash a custom recovery in fastboot, do a full wipe, then flash a ROM (stock or custom) To see what happens
Already did all that. When I first got the phone I used the full wipe function of cwm(and of the stock recovery) a couple of times, but every time it was stuck at that point of the initial setup with the error showing up.
Is there a file SPECIFICALLY for the initial setup that I can flash to the phone, because I flashed different recoveries, roms, boots and even radios manually before installing the stock ruu. I haven't set up a phone before, so I'm not sure, but as I can see there are still 2 or 3 options left to select ,after that scheduled sync option, before the phone could run the main menu(gui or whatever).
Oh, and btw, when I updated it with that ruu, the setup visually changed and by that I figure out it gets flashed as part of the ruu, but still with the same problem. Can it be some kind of hardware problem of the internal memory? No matter how much I searched and where I looked I never found someone with a problem even close to this one.
Teichopsia said:
Edit: Try booting without the sd card, but aside from that, no idea.
You can also try flashing a stable gb rom see if you get the same issue.
Sent from a dream.
Click to expand...
Click to collapse
Whatever I was doing to the phone it didn't usually have an sdcard in it and was booting without an sd card, tried with and without, no changes.
After I installed that sense ruu i can't seem to get back to gb, any ideas how to do it? I also can't get cwm to work now, even though it flashes without any error or problem I can only ge the htcdev root(already did) with this ruu, I think but I don't get any changes except that there is a watermark on the first line of bootloader.