This is my first post, otherwise I would have posted in the Runnymede AIO dev forum. It actually is two parts.
1. I have searched many threads and still can't find a fix for my problem. I tried to install Runnymede AIO four times yesterday. My phone is S-off, rooted, etc. I have what the installer says is a stock HBOOT, but it has the "Revolutionary" banner on the bootloader screen. Every time I installed and rebooted it would hang on the white "HTC" screen. I wiped the phone every time I reinstalled as well. I have the EXT4 Recovery. I tried the reboot into recovery, then reboot from there trick, and it still got stuck. I really want to use this ROM, but I can't get it to install correctly. Anybody have any suggestions?
2. I tried to change by HBOOT from the Revolutionary HBOOT to the CM7/r2 HBOOT from AlphaRev using Fastboot Commander yesterday. When I did that, it soft bricked my phone so I couldn't see the screen (I am assuming I have a SCLED model). I finally got it fixed and ended up finally just restoring my Nandroid backup. Do I need to use the downgrader before trying to flash a new HBOOT, or would something else cause that?
Well, I found the superb troubleshooting guide from bortak (and thanked as well!) and tried flashing CyanogenMod. It went without a hitch. I tried Runnymede AIO again. Stuck on boot. So, I thought I would try Runny Rom. Same thing. Why would it be that I can get CM to flash but not a Sense ROM?
grillheadxl said:
Well, I found the superb troubleshooting guide from bortak (and thanked as well!) and tried flashing CyanogenMod. It went without a hitch. I tried Runnymede AIO again. Stuck on boot. So, I thought I would try Runny Rom. Same thing. Why would it be that I can get CM to flash but not a Sense ROM?
Click to expand...
Click to collapse
have you tried post#4 from Runnymede AIO thread, the detailed FAQ and installation guides in PDF format?
my immediate guess it that you don't have an ext partition set up on sd card, as i don't think you've mentioned one. CM does not require one to boot, but Runnymede AIO does.
well done for solving one of the problems yourself, many ppl can't find that troubleshooting guide for some reason...
What exactly are you Doing. Don't get clumsy write down step by Step what procedure your followed.
tehTerminator said:
What exactly are you Doing. Don't get clumsy write down step by Step what procedure your followed.
Click to expand...
Click to collapse
For the Runnymede AIO install, I followed the 4EXT Recovery and Runnymede AIO installation sheets to the T. I did every step that was shown in them, including making a 1024mb EXT4 partition on the SD card, which showed when I checked the partition tables. I did a complete install from those sheets at least twice and it still would not move past the white screen. I let it set for 1 1/2 hours and it didn't move on.
For the HBOOT flashes I used Fastboot Commander as well as tried flashing from fastboot in the SDK. I was wanting to flash the CM7/r2 HBOOT so I could get the AD2SDX function.
My guess would be the ext partition of the sd card is acting up. When you format it using 4ext recovery did you pick the option to save your fat32 partition? If that was the case, backup your sd card contents to a computer and use 4ext to format the entire card this time including the fat32 partition. Pnce complete put your files back in the card and flash again.
via xda app
stankyou said:
My guess would be the ext partition of the sd card is acting up. When you format it using 4ext recovery did you pick the option to save your fat32 partition? If that was the case, backup your sd card contents to a computer and use 4ext to format the entire card this time including the fat32 partition. Pnce complete put your files back in the card and flash again.
via xda app
Click to expand...
Click to collapse
The first time I formatted and flashed, I backed up to the computer, formatted the entire sd card, and transferred everything back. After that I have done it both ways when trying to flash again, with the same result.
I don't know if this makes a difference or not, but I thought I'd throw out there that I have a CDMA Desire (US Cellular).
After digging around, I think I have found that the CDMA is most likely what my issue is. I found this post ( http://forum.xda-developers.com/showthread.php?t=1476469 ) that says Runnymede AIO is GSM. If that's what the problem is, that really stinks because that ROM looks awesome! I don't remember the threads about the ROM saying if it was compatible with CDMA or not (in fact I only remember one mentioning it with a patch, and I've read that the patches don't even work). So, is there a list or something that I've missed that tells what works with CDMA?
Runny from seb is pure gsm, have look at runny from coolexe he is/was doing CDMA patch, both have same base
Sent from my HTC Sensation XE with Beats Audio using XDA Premium App
kotag82 said:
Runny from seb is pure gsm, have look at runny from coolexe he is/was doing CDMA patch, both have same base
Sent from my HTC Sensation XE with Beats Audio using XDA Premium App
Click to expand...
Click to collapse
I may give it a try. I think the Sense ROMS look really really nice is the main reason I am trying to hard to get this to work.
grillheadxl said:
I don't know if this makes a difference or not, but I thought I'd throw out there that I have a CDMA Desire (US Cellular).
Click to expand...
Click to collapse
grillheadxl said:
After digging around, I think I have found that the CDMA is most likely what my issue is. I found this post ( http://forum.xda-developers.com/showthread.php?t=1476469 ) that says Runnymede AIO is GSM. If that's what the problem is, that really stinks because that ROM looks awesome! I don't remember the threads about the ROM saying if it was compatible with CDMA or not (in fact I only remember one mentioning it with a patch, and I've read that the patches don't even work). So, is there a list or something that I've missed that tells what works with CDMA?
Click to expand...
Click to collapse
Ahh, yes, you'll often find such minor details left out of your OP to be the ones that are the biggest problem.
Sorry, you cannot use Runnymede with CDMA. There are actually only a very few ROMs made for CDMA devices, but if you search "CDMA" in the Dev section, you will definitely find something you can use.
PS, you may like to know that yes, Runnymede is an awesome ROM!!
Well, I installed Cool3d Runny v7 last night in CDMA mode. Still ended up stuck on the white screen. Guess I'll try Runnymede007 with the patch next...
Did you full wipe before install??
Also, occasionally, you might get a bad download, so might be worth dl'ing again, just to be sure...
Yep, did full wipe. I forget what the error was it showed. I'll try dl'ing it again. I just finished trying to work with RunnymedeMod007. I can't get the script edited for the CDMA patch. Needless to say, I am getting very frustrated.
unfortunately I've found that some of the CDMA patches don't work like they say they do
(in fact I've found one and that was the ics bcm)
make sure you have the right partition sizes that they want for the rom to work
use cMTD to change partition sizes:
http://forum.cyanogenmod.com/topic/23984-guide-to-installing-cmtd/
DONT USE ANOTHER HBOOT
if that didn't work check with the dev and see if the patch actually includes a bravoc kernel. if not it has a very very slim chance of working
if it doesn't work after that i have no answers
if resolved and working please post what you did so others may do the same
I'll see what I can do. For RunnymedeMod007 it says to delete a line from the script. I unzip the file, edit in Wordpad, zip the file, and save to SD. When I try to run it ai get an error. The zip has a root folder inside of it. Any idea what I'm doing wrong, or how else to edit the wcript and see if the patch works?
Edit script with Notepad++
Sent from my HTC Sensation XE with Beats Audio using XDA Premium App
Tried using Notepad++ to edit and it took out the script, but I can't get it to save back into the zip file. Tried zipping the entire file and ended up with the "file-in-file" problem again.
Ok, I redownloaded RunnymedeMod007, verified the MD5, unzipped it, edited out the line as he said to do, zipped the file, signed it with AndroidSigner, moved to SD, and, it failed. Whenever I zip the file, it makes the "Runnymede etc" zip file, then if I open it, there is another file inside with the same name, and if i open it, then all the info is there. I can't get it to zip without that extra folder inside, and I think that's the problem with this installation.
Also, I tried downloading Cool 3D Runny and doing a CDMA install with it again. I got it installed, but it hung at the white HTC screen again. I gave up after it was that way for an hour and did a battery pull.
The HBOOT partitions are all set to stock sizes, EXT4 partition set at 1024mb and aligned.
Related
Please forgive me and understand I have done my best to find a result before asking this question. For two days I have searched and as much as I hate to ask, I NEED HeLP.
I was running cm7 rc3 and looking around to what other roms interested me. I attempted to flash leedroid from clockwork, selected wipe data and wipe cache, and phone went to bootloader(?) and began the initial steps, wiped and formatted, etc... then said it couldnt find sd-ext. Boots to htc white screen with logo, and freezes. Any attempt to get back to bootloader(?) fails, power volume up or down. HTC sync cannot recognize my device and safely remove hardware pops up. I found metatrons patch, alignment-zip. and downloaded it to sd card via sd adapter on computer. Tried reinserting into Inspire and still, its Power on to htc logo screen - freeze. I have read where peeps can attempt fastboot, and find bootloader or recovery, but either I am forgetting something, or have a unique situation, or I am bricked? I feel I havent exhausted all my options yet, but despite fervently searching, and other forums, cannot find a result. this is my first post, and if anyone could help me, I will get my shizzle running and leave the phone mods and everything in between to the pros...
P.S. can I move or should I move alignment-zip. to a different or certain folder within my sd card? I backed all previous settings up first - before any flash or wipe. Ran wipe-.zip before flashing because the thing said to. did that erase my backup? I am so frigging sorry, i know this has got to get old for you all...
You did not provide enough information for troubleshooting.
Is your sd card formated with fat32 plus ext2/3/4? Specify!
What hboot are you using?
Which LeeDroid are you tring to use?
Sent from my HTC Desire using XDA Premium App
Ok. Check it, this is what I remember. I rooted my phone using bubbys method and installed whatever rom was with that link, a cyanogen I know. I flashed cyanogen7 rc4 and have clockwork recovery 3.0.5 card was formstted fat/32 yes. tried the latest leedroid 3.0 I believe, downloaded wipe.zip went to clockwork recovery and it auto matically asked about wiping and flashing new rom - attemted flash over cm7, looked as though everything was working, but never got past htc screen. then I noticed the alignment.zip link I should have downloaded also. I downloaded it, but for all I know it isnt in the proper place on my SD card. bootloader screen says ACE PVT SHIP S_OFF RL ; hboot - 0.85.0019 ; Radio - 26.06.04.06_M ; under that it says eMMC-boot and I am not quite sure which ext. is formatted with fat/32. I knew, but Jesus I have read so much and searched so hard I dont know wtf anymore...
I'm having trouble installing any roms on my girlfriends desire. Installing roms seems to work fine, right up until i try to boot the phone, it just gets stuck at the HTC screen, I've pulled the battery and tried again, but nothing works. I've tried multiple roms, and with every one, the same problem.
The phone is rooted, HBOOT 0.93.0001, S-ON, Baseband 32.54.00.32U_5.14.05.17
Anyone know what's going on? It's been a while since I've played with android phones, so I'm not current with all the lingo. I'm currently a WP7 user
Thanks for the help!
I'm assuming then it would be a2sd Rom?? Your ext3 or 4 setup? ROM manager sucks for this, use gparted or minitools(I've never used this one) and preferably a card reader.
Sent from my HTC Desire
Ya, I tried ROM manager for the partition, I'll give gparted a shot. thanks!
Ok, formatted the sd card, and repartitioned to FAT32, and 512mb of EXT3 and the same thing happens, it just hangs at the HTC screen after installing a rom.
How long are you giving it before pulling the battery? It can take 10 or 15 minutes on first boot. I'm assuming you've tried a couple of different roms.
yes, I have tried a few different ones. I'd say the longest I waited was around 25-30 minutes. In my previous experience flashing hero roms, the most I had ever had to wait for those was about 5 minutes, so I assumed the 30 minutes was long enough, and decided that nothing was going to happen.
A Dustman said:
yes, I have tried a few different ones. I'd say the longest I waited was around 25-30 minutes. In my previous experience flashing hero roms, the most I had ever had to wait for those was about 5 minutes, so I assumed the 30 minutes was long enough, and decided that nothing was going to happen.
Click to expand...
Click to collapse
i'm a previous hero owner, same thing happend to me, desire is different.
on all desire roms the op will tell you what hboot is made for and then to flash the alignement zip even if your sdcard is partioned , you have to otherwise the will never bootup and then you flash the rom plus whatever updates they suggest .
i think your hboot is stock, same as mine, but you need to S-off your phone in order to flash any roms, follow this guide: http://forum.xda-developers.com/showthread.php?t=1016084
try cool sensation or what ever takes your fancy
1-download the alignement zip , the rom and the updates if there are any
2- put all of them on your sd card (mount it or use usb card adapter)
3- go to recovery and flash them in sequence, usually alignement zip first + the rom and then reboot should be about 5 to 10mn any longer you in a bootloop means something wrong.
just have a good read before flashing any rom , and follow what they say.from step 1 till the end.
you'll get there, don't worry it wont brick your phone
I was under the impression that S-Off wasn't necessary for all roms, for example insert coin cm7. I could not get my computer to successfully boot from my flashdrive to perform the s-off with alpharev, so I skipped that step
I also flashed the alignment zip, and still had the same problem.
A Dustman said:
I was under the impression that S-Off wasn't necessary for all roms, for example insert coin cm7. I could not get my computer to successfully boot from my flashdrive to perform the s-off with alpharev, so I skipped that step
I also flashed the alignment zip, and still had the same problem.
Click to expand...
Click to collapse
You don't need s-off to flash roms, I'm not and flashed many. Make sure your installing roms for the stock hboot, cm7 won't work. From what I've seen unless your having problems with your ext the alignment patches can be more trouble than good.
Sent from my HTC Desire
Thanks a lot! I found a rom that works with the stock hboot, and it worked perfectly!
What rom are you using with the stock hboot? I'm having same problem.
Also I'm assuming cm7 is cyanogenmod7, i thought it worked with the stock hboot?
Ok, so I'm having another issue now... The market is not working, I tap it, and it brings up a white loading screen for about half a second then disappears. I tried a reset, and I still have the same problem. Is there something I need to flash in order for it to work? The rom I'm on is cool sensation v6, and I didn't see anything there about anyone having market issues, so I'm not sure what the problem is.
Thanks again
EDIT: I notice that under accounts and sync, it says that sync is currently experiencing problems
EDIT EDIT: I just remembered that with my old hero, I had to first sync over 3g only, tried that, and it solved my problem.
Under Applications, find the market and try clearing the cache
A Dustman said:
I could not get my computer to successfully boot from my flashdrive to perform the s-off with alpharev, so I skipped that step
Click to expand...
Click to collapse
Did you create a bootable usb drive?
firepanda said:
What rom are you using with the stock hboot? I'm having same problem.
Also I'm assuming cm7 is cyanogenmod7, i thought it worked with the stock hboot?
Click to expand...
Click to collapse
It's a bit misleading, cm7 does not refer to cyanogenmod7 but cm7 partion table.
You will usually find 2 different versions of most popular ROMs.
1. A2sd
apps2sd, usually A2sd+. This requires the stock partion table. You do not need to be S-off to flash these ROMs
2. CM7
This refers to the CM7 partion table (custom Hboot). To repartion your nand you need to be S-off. These ROMs are data++ ROMs.
So, no you do not need to be S-off to flash custom ROMs, you do need to be S-off to resize your partion tables. More info in this thread:
This explains Data++ versus A2SD very well:
http://forum.xda-developers.com/showthread.php?p=14615477#post14615477
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.
-I have true s-off, permaroot and superCID
-ENG hboot and CWM work fine
-can successfully load and run ROMs
Device no longer sees a SIM card, yet been testing various ROMs for over 6 months with this handset.
I've taken it apart , and SIM slot looks ok.
I've tried eft wipe, superwipe, all my working nandroids, updated radio (currently running cm9/aokp40) to no avail.
Can anyone point me to how I can determine whether this is a S/W or H/W issue?
I'm leaning towards downgrading to stock/s-on then repeating the unlock to re-set my unlocked status for lack of any other options.
While googling not finding much if anything on radio data, so thanks in advance.
IF this is S/W based and you can help to fix I've a working TP2 in box as a reward/incentive.
If I am not mistaken the newer Roms need a newer SIM card, i.e.: the older ones (I think like 3-5 years old) won't be recognized with say the new radio (*.19)
I'm not sure what the new # is, but mine has 39.01a on the side, and works with the latest radio and CM9, EliteMod ICS, etc.
EDIT: But that might only refer to T-Mobile, not sure how it is with Fido/Rogers.
kbeezie said:
If I am not mistaken the newer Roms need a newer SIM card, i.e.: the older ones (I think like 3-5 years old) won't be recognized with say the new radio (*.19)
I'm not sure what the new # is, but mine has 39.01a on the side, and works with the latest radio and CM9, EliteMod ICS, etc.
EDIT: But that might only refer to T-Mobile, not sure how it is with Fido/Rogers.
Click to expand...
Click to collapse
Food for thought thanks, the SIM stopped being recognized after having flashed the "no service fix" update to this ROM http://forum.xda-developers.com/showthread.php?t=1749445 and have asked in that thread whether anything in the fix file could've set something off on my device.
IT IS an older SIM that I'm using but up to now have used every ROM with it without a hitch. I'll downgrade the radio now as an option.
igor45 said:
Food for thought thanks, the SIM stopped being recognized after having flashed the "no service fix" update to this ROM http://forum.xda-developers.com/showthread.php?t=1749445 and have asked in that thread whether anything in the fix file could've set something off on my device.
IT IS an older SIM that I'm using but up to now have used every ROM with it without a hitch. I'll downgrade the radio now as an option.
Click to expand...
Click to collapse
I noticed that it said "only for 2.7.13", though that seems to be specifically for a version of MUIU.
though when I unpack the fix :
Code:
assert(getprop("ro.product.device") == "vision" || getprop("ro.build.product") == "vision");
mount("ext4", "EMMC", "/dev/block/mmcblk0p25", "/system");
package_extract_dir("system", "/system");
unmount("/system");
Which basically only verifies that the phone is a HTC Vision (as per existing build.prop), mounts the /system partition, then extracts the package's content of /system to your rom
in this case a single file:
/system/framework/framework-res.apk
So from just that, I can't really see the fix having a prolong effect on all your other roms, unless you failed to do a full wipe (factory reset and wipe cache/dalvik cache in recovery before flashing a brand new rom).
This is the only thing I've changed in framework-res.apk:
Code:
<bool name="skip_restoring_network_selection">false</bool>
v1r0x said:
This is the only thing I've changed in framework-res.apk:
Code:
<bool name="skip_restoring_network_selection">false</bool>
Click to expand...
Click to collapse
right but even that change would be completely wiped out if he wiped/changed roms, so would have to be another factor that caused it.
kbeezie said:
right but even that change would be completely wiped out if he wiped/changed roms, so would have to be another factor that caused it.
Click to expand...
Click to collapse
Yes. Maybe it's just coincidence..
But I hope there is a fix for that problem.
Sounding like my SIM slot at this point then. But I didn't just flash the fix on its own. I first flashed the updated zip from later in the thread that included the fix w/the complete ROM. Wonder if anyone else has tried that file?
Sent from my HTC Vision using xda app-developers app
igor45 said:
Sounding like my SIM slot at this point then. But I didn't just flash the fix on its own. I first flashed the updated zip from later in the thread that included the fix w/the complete ROM. Wonder if anyone else has tried that file?
Sent from my HTC Vision using xda app-developers app
Click to expand...
Click to collapse
Maybe nothing to do with this but was using Elitemod/CM9/AOKP before flashing and "su" reported that it needed to close. I'D been experiencing few FCs with that ROM installed.
Didnt thing this would affect it once rebooted to CWM.
igor45 said:
I first flashed the updated zip from later in the thread that included the fix w/the complete ROM. Wonder if anyone else has tried that file?
Click to expand...
Click to collapse
which file do you mean with that?
igor45 said:
Maybe nothing to do with this but was using Elitemod/CM9/AOKP before flashing and "su" reported that it needed to close. I'D been experiencing few FCs with that ROM installed.
Didnt thing this would affect it once rebooted to CWM.
Click to expand...
Click to collapse
Can you be more specific on the EliteMod part, are you simply talking bout the EliteMod ICS rom, or putting EliteKernel on top of a CM9 or AOKP port? (if just the rom, I'm not aware of a 'fix' that was meant for EliteMod).
v1r0x said:
which file do you mean with that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=28906048&postcount=74
... maybe something in yozgats file?
igor45 said:
http://forum.xda-developers.com/showpost.php?p=28906048&postcount=74
though I see it doesn't include the fix... maybe something in yozgats file?
Click to expand...
Click to collapse
Are you saying you used a fix from one rom (light) with another rom (elitemod)? I'm not getting very clear information from you just bits and pieces.
to clarify
kbeezie said:
Are you saying you used a fix from one rom (light) with another rom (elitemod)? I'm not getting very clear information from you just bits and pieces.
Click to expand...
Click to collapse
LOL - bit of a noob here though not that bad, so no I didn't mix fixes/ROMs :highfive:
I was on latest Elitemod/CM9/AOKP
To be clear,
1 - I first flashed the file from post 74 in the thread that included the bugfixes and few enhancements to the original.
(So wondering whether there's something in that file, and yes it does include the fix)
----this is where "no sim inserted" occurs---
2 - when ROM came up good but no SIM, i reverted to my nandroids, trying each one of them.
3 - then tried full wipes with fresh ROM flashes
4 - then tried superwipe/efs wipe AND updated radio and tried each nandroid/fresh installs again
5 - now downgraded radio to what I had (minus the rils) and living with WIFI only connection til I can fix the SIM issue
btw "Elitemod/CM9/AOKP" are three different roms If you just mean EliteMod ICS just say that , helps reduce the confusion. (since some people do separately install AOKP or CM9 by itself, and then flash EliteKernel on top of those).
k, as for #1 when I originally read about the 'fix', that was for a completely different rom than EliteMod and course probably wouldn't work anyways.
Secondly with EliteMod ICS, I've found that I had to be on the .19 radio (note my signature) in order to boot up with it and manage both data and wifi connection, there was no need to 'patch' anything because nik3r already included the proper ril/data for the newest radio in the rom/kernel itself. And it doesn't matter if you're on either the G2 hboot (0.76.0000 I think) or the DZ hboot like I have, since it's not a sense rom or a rom of that size.
If you are on a functional phone right now (outside of the non-Wifi data connection of course), I would recommend upgrading your recovery to 4EXT recovery first (something like the 4EXT Touch Recovery 1.0.0.5 RC5 that can be installed from the app, the app itself is found in google play and can install the recovery for you, there is a free version of the app that I have if you simply want the installer but I Recommend the paid version since you can control most of it's preferences from the app before rebooting into recovery).
From there (assuming you have everything you need backed up to the computer including say any titanium backup files):
Just to knock out a number of possibilities will just act like we're going to do a 'full' setup, assuming that 1) You are already using an ENG S-OFF hboot and 2) have already upgraded the radio to the latest .19 version
1) re-partition the SD card via 4EXT (I recommend a 2GB sd-ext, skipping the sd-ext2 and skipping swap), so that's freshly setup [that and if you chose to use the dataswap mod for EliteMod the 2GB sd-ext is needed to compliment it, never make a sd-ext less than ~1.5GB in size]
2) once you got that re-partitioned toggle the USB storage so you can copy back all the files you need including the rom files etc etc.
3) "Wipe/Format" menu to do
a) Factory Reset/Wipe
b) wipe cache+dalvik
c) Battery stats (cuz why the hell not, it *could* help lol)
4) No need to do an EFS wipe since the EliteMod rom zip does this for you upon installation, so Flashing the EliteMod Rom, then any optionals (Gtalk, google gallery, T-mobile wifi calling, DataSwap mod) on top of that.
PS: if you like to multitask active apps quite a bit (i.e.: background notifications etc), I would recommend the 64MB Dataswap mod at the very least, especially with all that free space you'll have on /data partition from the use of an sd-ext partition.
5) Reboot, once fully booted, reboot again
6) check connectivity for both SIM/Wifi/Etc.
If you're *still* having problems, even after physically pulling the sim out, blowing some dust out, or whatever you can and putting it back in, I'd start to wonder if 1) the sim is too old for whatever reason [ie: with whatever update], 2) the sim got damaged [maybe via some kind of sim update?], or 3) the sim slot is maybe damaged? 4) or the universe just hates you right now.
---------- Post added at 06:27 PM ---------- Previous post was at 06:26 PM ----------
PS: I highly recommend Titanium Backup, it's been very useful in flashing a fresh clean rom, but then being able to restore most of my applications with their settings/data intact.
kbeezie said:
btw "Elitemod/CM9/AOKP" are three different roms If you just mean EliteMod ICS just say that , helps reduce the confusion. (since some people do separately install AOKP or CM9 by itself, and then flash EliteKernel on top of those).
k, as for #1 when I originally read about the 'fix', that was for a completely different rom than EliteMod and course probably wouldn't work anyways.
Secondly with EliteMod ICS, I've found that I had to be on the .19 radio (note my signature) in order to boot up with it and manage both data and wifi connection, there was no need to 'patch' anything because nik3r already included the proper ril/data for the newest radio in the rom/kernel itself. And it doesn't matter if you're on either the G2 hboot (0.76.0000 I think) or the DZ hboot like I have, since it's not a sense rom or a rom of that size.
If you are on a functional phone right now (outside of the non-Wifi data connection of course), I would recommend upgrading your recovery to 4EXT recovery first (something like the 4EXT Touch Recovery 1.0.0.5 RC5 that can be installed from the app, the app itself is found in google play and can install the recovery for you, there is a free version of the app that I have if you simply want the installer but I Recommend the paid version since you can control most of it's preferences from the app before rebooting into recovery).
From there (assuming you have everything you need backed up to the computer including say any titanium backup files):
Just to knock out a number of possibilities will just act like we're going to do a 'full' setup, assuming that 1) You are already using an ENG S-OFF hboot and 2) have already upgraded the radio to the latest .19 version
1) re-partition the SD card via 4EXT (I recommend a 2GB sd-ext, skipping the sd-ext2 and skipping swap), so that's freshly setup [that and if you chose to use the dataswap mod for EliteMod the 2GB sd-ext is needed to compliment it, never make a sd-ext less than ~1.5GB in size]
2) once you got that re-partitioned toggle the USB storage so you can copy back all the files you need including the rom files etc etc.
3) "Wipe/Format" menu to do
a) Factory Reset/Wipe
b) wipe cache+dalvik
c) Battery stats (cuz why the hell not, it *could* help lol)
4) No need to do an EFS wipe since the EliteMod rom zip does this for you upon installation, so Flashing the EliteMod Rom, then any optionals (Gtalk, google gallery, T-mobile wifi calling, DataSwap mod) on top of that.
PS: if you like to multitask active apps quite a bit (i.e.: background notifications etc), I would recommend the 64MB Dataswap mod at the very least, especially with all that free space you'll have on /data partition from the use of an sd-ext partition.
5) Reboot, once fully booted, reboot again
6) check connectivity for both SIM/Wifi/Etc.
If you're *still* having problems, even after physically pulling the sim out, blowing some dust out, or whatever you can and putting it back in, I'd start to wonder if 1) the sim is too old for whatever reason [ie: with whatever update], 2) the sim got damaged [maybe via some kind of sim update?], or 3) the sim slot is maybe damaged? 4) or the universe just hates you right now.
---------- Post added at 06:27 PM ---------- Previous post was at 06:26 PM ----------
PS: I highly recommend Titanium Backup, it's been very useful in flashing a fresh clean rom, but then being able to restore most of my applications with their settings/data intact.
Click to expand...
Click to collapse
Yes understood that the "fix" was a trivial patch and that it pplies only to the MIUI multilang version in question - trust me I would not have mixed those two up. I opted to first flash the version from the later post since it included app/framework enhancements WITH the "no service fix"
Yes I was on Elitemod ICS (AOKP base) with modified CM9 kernel. Sorry for that confusion.
I'd previously used Elitemod AND AOKPs with my old radio with no issues whatsoever. never had to tweak a thing.
FWIW I'm on hboot .84.2000 ENG s-off and yes using clockworkmod recovery
I'd like to try 4ext - looking into it now.
Appreciate the help.
Maybe I'll put this on hold til I get a new sim from FIDO...
igor45 said:
Maybe I'll put this on hold til I get a new sim from FIDO...
Click to expand...
Click to collapse
Yea the issue in general sounds just weird overall, hopefully it'll get resolved one way or another.
kbeezie said:
Yea the issue in general sounds just weird overall, hopefully it'll get resolved one way or another.
Click to expand...
Click to collapse
Indeed - still hoping that there's someone that can offer a method of testing to see whether its a H/W issue. Must be somethng in adb and/or bootlogs? Perhaps in the bootloader for Radio.
well reading over this thread have you tried another sim? your sim in another phone? you can run some very simple tests in the diagnostics menu. go to dialer and type *#*#4636#*#*
go into phone info and play around with turning radio on and off and gsm only etc to see if anything appears ok. the best ways to test software/firmware or hardware faliure you seem to have tried, wipe fully, flash new rom, new radio...
I guess you can always try to unroot? if it still won't work then my guess is hardware
Sent from my HTC Vision using xda premium
demkantor said:
well reading over this thread have you tried another sim? your sim in another phone? you can run some very simple tests in the diagnostics menu. go to dialer and type *#*#4636#*#*
go into phone info and play around with turning radio on and off and gsm only etc to see if anything appears ok. the best ways to test software/firmware or hardware faliure you seem to have tried, wipe fully, flash new rom, new radio...
I guess you can always try to unroot? if it still won't work then my guess is hardware
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
thx for the suggestions
Have my sim working in my backup phone and works in every other phone I've tried. Yes have also tried airplane mode on/off data on/off - etc...
Did try to unroot yesterday but ran out of time, had to run off to work.
Want to do it right so will try again today as I've a bit more time.
playing with diagnostics menu now thanks.
Hello,
sorry if u will find this thread to be repeated, but I was searching so much, and nothing helped me. After all, I think you are my last chance.
So to the problem:
One day I rebooted my Desire Z - rooted, CyanogenMod 7.2.0 RC# ( # is number can't remember which one - 2 or 3). Then I haven't paid attention to it and when I came home I noticed that phone is turned-off. So I turned it on: HTC white screen with green htc logo, CM loading screen and PIN code screen. So i entered PIN everything started loading ( i mean icons in notification bar appeared ) and then it happened: reboot. So again: logo, CM screen, PIN. I was bit slow so I didn't manage to enter PIN code and phone rebooted again. So it appears like it reboots in periods. So I start searching around the internet. I tried some things which I knew how to do, but I always found some problem. For example I can't mount USB storage while in CWM v5.0.2.7.
It appears to be boot loop, but I am not sure because I got to entering PIN code.
Help me, pls... I'm clueless.
P.S.: Sorry for my english, it's not my native language.
helper
YOU HAVE TO REINSTALL HBOOT AND FLASH A NEW ROM I WONT RECOMMEND GOING BACTO YOUR OLD ROM
get the hboot zip from http://www.virtuousrom.com/2011/06/t-mobile-g2-users-migrating-to-desirez.html put the file in the root of your sdcard hboot wiil recognize it and asked if you want to update after this remove the memory card use a card reader and on your pc delete the file put it back and enjoy dont forget to flash a new rom since this will delete every thing (oh use the card reader to put the file in you sd since you cant mount it from cmw
HIT THANKS IF I HELPED:good:
strip419 said:
YOU HAVE TO REINSTALL HBOOT AND FLASH A NEW ROM I WONT RECOMMEND GOING BACTO YOUR OLD ROM
get the hboot zip from http://www.virtuousrom.com/2011/06/t-mobile-g2-users-migrating-to-desirez.html put the file in the root of your sdcard hboot wiil recognize it and asked if you want to update after this remove the memory card use a card reader and on your pc delete the file put it back and enjoy dont forget to flash a new rom since this will delete every thing (oh use the card reader to put the file in you sd since you cant mount it from cmw
HIT THANKS IF I HELPED:good:
Click to expand...
Click to collapse
Umm, don't do that ^^^^^
But it does look like you have some serious issues, try this, boot into recovery and wipe cache and dalvik, now flash cm7 on top of it
If it still is causing issues then you need to do a full wipe (even better if you super wipe or fastboot -w)
Then flash ROM of choice, cm7 is great and there are many good Roms based off of cm7 I would also recommend, elitemod or ilwt for a couple nice options
Sent from my Nexus 7 using xda premium
demkantor said:
Umm, don't do that ^^^^^
But it does look like you have some serious issues, try this, boot into recovery and wipe cache and dalvik, now flash cm7 on top of it
If it still is causing issues then you need to do a full wipe (even better if you super wipe or fastboot -w)
Then flash ROM of choice, cm7 is great and there are many good Roms based off of cm7 I would also recommend, elitemod or ilwt for a couple nice options
Click to expand...
Click to collapse
I am at work right now and I left phone at home, but I can tell you I tried wiping cache. Problem appeared when I showed log of this wiping and there was something like app2s something with partitions or something like. I already formatted my card in PC (FAT32, not quick format, non-USB card reader - normal one). Should I try different card (card is gold card CID-11111111 (i don't know how many ones ))?
And if I will try what strip419 said, could something possibly happen to my phone ( in wrong way)?
Draftur said:
And if I will try what strip419 said, could something possibly happen to my phone ( in wrong way)?
Click to expand...
Click to collapse
I wouldn't bother with reflashing the hboot, I would try more 'non-destructive' solutions first.
Reflashing thé hboot is thé only way to format all partitions do away with any thing that could be doing this of cos you could brick your phone but if you follow rules its gonna be okay if you have adk on your pc then you could use the command tool to clear this but that could do worse damage if you are a noob so its up to you man try or keep looking for a. Solution that will end up like mine any way
Sent from my HTC Desire Z using xda app-developers app
strip419 said:
Reflashing thé hboot is thé only way to format all partitions do away with any thing that could be doing this of cos you could brick your phone but if you follow rules its gonna be okay if you have adk on your pc then you could use the command tool to clear this but that could do worse damage if you are a noob so its up to you man try or keep looking for a. Solution that will end up like mine any way
Sent from my HTC Desire Z using xda app-developers app
Click to expand...
Click to collapse
... No it's not, 4EXT Recovery -> Wipe/Format -> Format all partitions (except SDcard).
And how does hé get that recovery working when hé cant even boot or can hé flash it from cwm recovery?????
TRY
Sent from my HTC Desire Z using xda app-developers app
strip419 said:
And how does hé get that recovery working when hé cant even boot or can hé flash it from cwm recovery?????
TRY
Sent from my HTC Desire Z using xda app-developers app
Click to expand...
Click to collapse
You can flash recovery from fastboot or via PC10IMG.zip the same way doing a hboot reinstall would work, except in this case you don't go to such extremes to do the entire hboot over again, just the recovery and go from there. If it's an ENG hboot can use fastboot directly to flash the recovery.img, otherwise you pack it into a PC10IMG.zip and place it on the SD card.
Worse case scenario, the internal memory is fried, and attempting to do a full hboot reinstall would most likely brick it as opposed to only trying to flash a portion.
I had a repetitive reboot issue when flashing a previous ROM as well.
My noob solution was to put PC10IMG.zip back on the SD card, boot to recovery using ADB and then going through the whole process of reinstalling hboot and putting on a known ROM. Didn't brick mine and I'm new to this...
Could have done with finding this forum earlier.
all should know to be careful doing that method, if it were a stock rom and you simply flashed the pc10img.zip with radio hboot, etc in it you could get a brick easy, especially if you don't have a working rom with adb functionality.
what would happen would be (this is if you have eng s-off as most root users do) your phone would begin by flashing the bootloader, after this it would reboot and attempt to flash flash the radio, only problem is the new hboot would be ship s-on and therefore would get stuck, leving you a soft brick with a little luck it would be possible to fix this but it could be that it is unfixable depending on the exact circumstances
all this is just to say be careful what you do, noob or not, if you aren't 100% sure what you are doing when flashing firmware a brick is easy
Sent from my HTC Vision using xda premium
I have a similar problem but not sure if it's the same one... When I boot up my phone it goes through all the boot images fine, but when it starts it starts sometimes with my background showing and sometimes in a blank screen but both saying Android System at the top then shortly after shut down (usually shows shutting down not just straight up turns off) I have flashed new roms, reflashed backups, even got a jelly bean rom to go through the optimizing apps screen thing then would go to a blank screen with Android System on top again, and shut down.
Any help would be amazing! I've had my G2 since it's release and would hate to think it ran out of hearts :crying:
SoftAndDeep said:
I have a similar problem but not sure if it's the same one... When I boot up my phone it goes through all the boot images fine, but when it starts it starts sometimes with my background showing and sometimes in a blank screen but both saying Android System at the top then shortly after shut down (usually shows shutting down not just straight up turns off) I have flashed new roms, reflashed backups, even got a jelly bean rom to go through the optimizing apps screen thing then would go to a blank screen with Android System on top again, and shut down.
Any help would be amazing! I've had my G2 since it's release and would hate to think it ran out of hearts :crying:
Click to expand...
Click to collapse
You have my exact problem! Have you found a fix for it?
Magnumxxxl said:
You have my exact problem! Have you found a fix for it?
Click to expand...
Click to collapse
I also have the same problem. I attempted to use superwipe g2 to no avail.
I have clockwork recovery installed, and every custom rom I try to use seems to crash 5-10 seconds after finishing to loading screen for say cm7 or cm9.
I do not have a goldcard so am wondering what the best course of action would be. I am reluctant to follow the Hboot advise as the risks mentioned seem great.
everyone having these issues should go to irc freenode #g2root (just google it) and can receive real time help there. there are too many possiblities of what is going wrong and not enough information being given to help here well.
once things are figured out and all is working post back here to explain what the problem/fix was so future people finding this thread may have an easier time
Sent from my HTC Vision using xda premium
demkantor said:
everyone having these issues should go to irc freenode #g2root (just google it) and can receive real time help there. there are too many possiblities of what is going wrong and not enough information being given to help here well.
once things are figured out and all is working post back here to explain what the problem/fix was so future people finding this thread may have an easier time
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
What is the hboot way? What does that do? I'll try it, my G2 is already useless now, anything that will fix it including a dangerous way tell me
well hboot (also known as bootloader or spl) is sorta like bios on a pc. but I don't suggest trying anything rash and can't help much unless I know paticulars of your situation, if you give that I can see what I can do, but like I said before if you would like some realtime help go to freenode.
if you want help here give me details, what exactly is your problem, what have you tried to do to fix it, what method specificaly did you use to obtain root, write down everything on your hboot screen (again you get there by holding volume down while powering on)
Sent from my HTC Vision using xda premium
demkantor said:
well hboot (also known as bootloader or spl) is sorta like bios on a pc. but I don't suggest trying anything rash and can't help much unless I know paticulars of your situation, if you give that I can see what I can do, but like I said before if you would like some realtime help go to freenode.
if you want help here give me details, what exactly is your problem, what have you tried to do to fix it, what method specificaly did you use to obtain root, write down everything on your hboot screen (again you get there by holding volume down while powering on)
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Well I bought this phone at a swapmeet last year for 40 bucks. Everything worked and it was on gingerbread last year. In a week I googled and found a way to root by using the thread here in the forum by using adb and downgrading to froyo which was a pain for a noob using adb I just add lol, I was on elitemod gb for many months, until I was playing music a few days ago it just rebooted itself and it wouldn't boot correctly. Here's how it goes, htc white screen, boot animation, then it says android system on the top left and all black under and it shuts itself off. EVERY rom I have flashed it does that, I wiped completely and use the superwipe g2+ and still no dice. I couldn't find the 4ext recovery, I need it as a flashable zip to try it.
not really you should be able to flash it via fastboot (which is my opinion the prefered way anyhow) just google search for the image.
but I still need to know what is on your hboot screen or I can't help much further
Sent from my HTC Vision using xda premium
demkantor said:
not really you should be able to flash it via fastboot (which is my opinion the prefered way anyhow) just google search for the image.
but I still need to know what is on your hboot screen or I can't help much further
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Do you have twitter so I can show you there with ease?