Related
So I've had two incredible's now fall in to a boot loop
(wiped, pulled battery, RUU'd, went back to s-on - nothing worked)
first one I had for about 8 months with no issues until now. they did
send me a replacement XD and it did the same thing!
Now my wifes phone is doing it :\
I'm just verifying - if I RUU/S-on/remove sd card - then it HAS to be a hardware issue right? nothing that I could have done?
[Further info if needed]
All had CWR 3.0.0.5 and were rooted via unrevoked
h0x90 said:
So I've had two incredible's now fall in to a boot loop
(wiped, pulled battery, RUU'd, went back to s-on - nothing worked)
first one I had for about 8 months with no issues until now. they did
send me a replacement XD and it did the same thing!
Now my wifes phone is doing it :\
I'm just verifying - if I RUU/S-on/remove sd card - then it HAS to be a hardware issue right? nothing that I could have done?
[Further info if needed]
All had CWR 3.0.0.5 and were rooted via unrevoked
Click to expand...
Click to collapse
Were you using the same ROM or kernal each time?
It's the new cwm. It uses a different gscript setup. To a restore or flash incredible reengineered 2.3.1
If not that then I don't know. Did it happen after a Rom flash?
Sent from my Incredible using XDA App
well the first one was running Evervolv and had been for about 3 weeks.
it crashed during a phone call and never booted all the way again. (boot loop)
The second (This ones replacement) was running cm7 (Flashed it right as I got it) and worked fine the first day I had it (but I wasn't using it much that day) then it died while using the browser and fell victim to boot loopage.
The third one (my wifes phone) died about an hour later while using the browser but would still boot - but not stay on for very long. Especially if any sort of data was going on (like syncing with gmail). I figured since it was kind of working maybe it was the rom so I flashed s-on went back to stock 2.2 (ruu) where it now dies upon lock screen.
(or before sometimes)
[Ninja edit] Wifes phone had been running evervolv the amount same time as my first phone
all three were running latest CWM and had the default kernel for the rom they had. Also all 3 were flashed ruu and s-on including a clear storage for good measure (Verizon also had me do a factory reset come to think of it - before they would ship replacements)
Ianxcom said:
It's the new cwm. It uses a different gscript setup. To a restore or flash incredible reengineered 2.3.1
If not that then I don't know. Did it happen after a Rom flash?
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
could cwm leave something behind that would continue the boot loop after ruu?
That would suck because I've already sent in one phone would hate for them
to find something like that ><
have you tryed downgrading? i know i was having alot of issues with the new cwm. im running chingys rom and after the downgrade everything is running smooth again. cwm 2.5.1.2 seems to be working better...
HandsomeRob2310 said:
have you tryed downgrading? i know i was having alot of issues with the new cwm. im running chingys rom and after the downgrade everything is running smooth again. cwm 2.5.1.2 seems to be working better...
Click to expand...
Click to collapse
I've went complete stock everything (including recovery) and it didn't fix anything.
Have an update on the situation as well.
Verizon shipped me another 2 phones - both broken out of the box.
The first one just reboots over and over again and can't even enter recovery.
On the second device the speaker is blown -.-
Are you using the same or different SD card(s) amongst these failing devices?
The one you had running for 8 months, was that SD card at end of life?
Asking, as AOSP ROMs interact quite a bit more w/ the SD card than do Sense ROMs, so if your issues are all with AOSP ROMs, I suspect wonky SD card(s).
smtom said:
Are you using the same or different SD card(s) amongst these failing devices?
The one you had running for 8 months, was that SD card at end of life?
Asking, as AOSP ROMs interact quite a bit more w/ the SD card than do Sense ROMs, so if your issues are all with AOSP ROMs, I suspect wonky SD card(s).
Click to expand...
Click to collapse
I got that SD back when I got the phone so I hope its not
at the end of its life span.
I've actually didn't bother putting the SD cards in this last batch
because they were showing issues immediately (without any modding)
Thanks for the info on AOSP roms that could help diagnose future problems
That would explain a lot, actually, as AOSP ROMs call the sd during boot.
Sent from my ADR6300 using XDA App
Hey all! So, a couple weeks back, I flashed a BETA ICS ROM onto my Inspire (Desire HD). Being my normal ignorant, and noob-like self, I completely ignored the fact that the thread said "DEVS ONLY!"
Well, flash forward a couple of weeks, and my Inspire is all but bricked. The ROM did not have mobile data yet, did not have a connection to the micro-SD card, and it was not touchscreen ready yet. I have tried ADB, but to no-avail, my file system knowledge and overall lack of knowledge put me quite a predicament.
I have flashed many ROMs before, but I sincerely messed up big time on this try. So, would any of you be able to help me find a cure for this important issue? Is the fix really simple and easy, and I am just a bonehead?
Thanks!
Not sure what your issue is. You never clearly stated. Does the phone not boot? Stuck in the splash screen? you want to flash a new rom?
marsdta said:
Not sure what your issue is. You never clearly stated. Does the phone not boot? Stuck in the splash screen? you want to flash a new rom?
Click to expand...
Click to collapse
Oops, sorry! My problem is that my phone is stuck on the developer ROM, and I would like to fix it somehow. So, yes, I would like to get another ROM, but I have to remove this one first. The phone itself works great, but with no wi-fi, mobile data, and no touchscreen support, it is hard to live with.
Your nowhere near bricked. Going to ask the basics. Did you make a backup before hand? Did you have another rom on your SD card.?
If you answered yes to either then simply boot into recovery and flash the rom/ backup. You mentioned flashing roms before so I left out the steps.
If you answered no then you have two options. You can mount the SD card from within cwr. So download a rom on your PC. Mount the sd card, then flash away. Or take out SD card and use an adapter/other phone to transfer a new rom.
I was not smart enough to back up onto a computer, but I did back up onto the SD card. The only problem with this is that the ROM, and my computer, will not recognize that there is in fact an SD card inserted into the phone. So, in other words, it's like not having an SD card at all.
CWR will still read the sd card. Trust me. boot into CWR and restore your backup. And you be good as gold
Thanks! But, what exactly does CWR stand for? Haha, I'm not the most knowledgeable on the topic of Android, but is it like Clock Work Mod?
iTookTheByte said:
Thanks! But, what exactly does CWR stand for? Haha, I'm not the most knowledgeable on the topic of Android, but is it like Clock Work Mod?
Click to expand...
Click to collapse
yeah. CWR stands clockworkmod recovery
Okay, in that case, I'm not sure. All of my old files (CM7, CWM, etc.) were on the SD card, and it is unreachable. I have tried to boot into CWR, but it just gives me a black screen. I feel like this thing is just unable to be fixed!
its fixable. just the black screen in CWR is an obstacle. worst case is you have flash an ruu and start over with the whole rooting. i remember reading about the black screen in CWR give me a few minutes to find them to see what to do next
Okay! Thanks a bunch!
Pull the battery and put back in
Press and hold vol-down
Press power and bootloader will start
Select recovery using vol keys and press power
If you have a backup (you really should, and and if you don't consider this experience a learning one), restore it by selecting the backup / restore option
If no backup, goto mounts and select as storage, plug usb into pc and copy your favorite Rom over, then select back and flash from zip, select the zip and you should all be back up
But please, please I'm all for people learning and experimenting, but might be worth reading some of the basics guides and notes on roms before flashing the next one. Oh, and if I forgot to mention.... Do a backup before flashing ANYTHING saves heartache later, the enjoy
Sent from my HTC Desire HD using XDA App
THANK YOU! I remember this now! Thanks everyone
Your welcome, after all, we all have to learn sometime
Sent from my HTC Desire HD using XDA App
ok i couldn't find the specific thread i was looking for. i remember it being stickied but couldnt find it. did find something that might be usefull but it depends on if you have access to an sd card adapter or other phone to transfer the file needed to reflash CWR. If not i would suggest trying to see if flashing an ruu to help.
edit- I'm confused now. thought you said that when you boot into recovery all you get is a black screen?
Hey guys, I have been having a ton of issues with my phone lately and I am at a loss on what to do from here... I am always having lag, random reboots, and on occasion complete data loss and nothing but force closings on every single app.
I have tried numerous roms both AOSP and Sense and several different kernel combos all with the same problems. My ROM install process is as follows...
1) Wipe Everything 3x
2) Transfer files needed for flashing to SD
3) Run VR_SUPERWIPE.zip 3x
4) Flash ROM
5) Flash Kernel
6) Flash GAPPS (if AOSP)
7) Flash dta2sd
8) Reboot
Phone Info:
White EVO HW 004
Recovery: AmonRA 3.11
SD: 8gb PNY Class 10
Battery: Stock
I usually get to the setup screen and I am able to get everything setup such as wifi and such. I let the phone sit for about 5 minutes then I reboot and procede with the rest of my setup process such as app installs, themeing, etc. On my initial reboot I go into recovery and fix permissions. 7 out of 10 times my phone will get borked right here and I can never get back to the system and I just get stuck at the white evo screen... I have tried cache and dalvik-cache wipes with no luck.
I have even unrooted my phone and tried to run everything as stock with the same results. I am pissed and frustrated and I do not know what to do anymore short of taking the phone and smashing it in to the ground and running it over with a truck
I hope someone has some idea of what is going on and I can get my issue resolved and if not tell me how to get a new phone out of Sprint
Thanks in advance!
EDIT: On reboot the phone makes a clicking noise while on the white htc EVO 4G screen...
This is the best thing to do,"Format & Partition Your SD Card"!that is the most important thing to do to not only make the roms run smoother and less lagging,but your phone will have less errors and more memory,go here.... http://forum.xda-developers.com/showthread.php?t=1158993 partition your sd card,then go here.... http://forum.xda-developers.com/showthread.php?t=715938&highlight=Dark+Tremors+A2SD And install this,trust me you will be wondering why you didnt do it sooner.
Edit:Holy crap,i didnt notice it was you bro,whats up nolimits,you might be having issues with the internals.
Diablo67 said:
This is the best thing to do,"Format & Partition Your SD Card"!that is the most important thing to do to not only make the roms run smoother and less lagging,but your phone will have less errors and more memory,go here.... http://forum.xda-developers.com/showthread.php?t=1158993 partition your sd card,then go here.... http://forum.xda-developers.com/showthread.php?t=715938&highlight=Dark+Tremors+A2SD And install this,trust me you will be wondering why you didnt do it sooner.
Edit:Holy crap,i didnt notice it was you bro,whats up nolimits,you might be having issues with the internals.
Click to expand...
Click to collapse
LOL yup it's me
I have tried a different method of flashing by rebooting after flashing one item at a time and it seems to have worked for the most part... My issues all started back when I tried pb15 of Deck's ICS build and all hell broke loose from there.
I really hope my method has resolved it self but if not I am not sure what to do with Sprint about getting a new phone. I have TEP but I don't have $100 due to a work injury and I don't have any income at the moment.
Here is what I am currently running:
CM7.2 APR8 Build
Mason 0.14 G SBC
dtA2SD
SmurfedOut Script 6.6
nolimit06 said:
Hey guys, I have been having a ton of issues with my phone lately and I am at a loss on what to do from here... I am always having lag, random reboots, and on occasion complete data loss and nothing but force closings on every single app.
I have tried numerous roms both AOSP and Sense and several different kernel combos all with the same problems. My ROM install process is as follows...
1) Wipe Everything 3x
2) Transfer files needed for flashing to SD
3) Run VR_SUPERWIPE.zip 3x
4) Flash ROM
5) Flash Kernel
6) Flash GAPPS (if AOSP)
7) Flash dta2sd
8) Reboot
Phone Info:
White EVO HW 004
Recovery: AmonRA 3.11
SD: 8gb PNY Class 10
Battery: Stock
I usually get to the setup screen and I am able to get everything setup such as wifi and such. I let the phone sit for about 5 minutes then I reboot and procede with the rest of my setup process such as app installs, themeing, etc. On my initial reboot I go into recovery and fix permissions. 7 out of 10 times my phone will get borked right here and I can never get back to the system and I just get stuck at the white evo screen... I have tried cache and dalvik-cache wipes with no luck.
I have even unrooted my phone and tried to run everything as stock with the same results. I am pissed and frustrated and I do not know what to do anymore short of taking the phone and smashing it in to the ground and running it over with a truck
I hope someone has some idea of what is going on and I can get my issue resolved and if not tell me how to get a new phone out of Sprint
Thanks in advance!
EDIT: On reboot the phone makes a clicking noise while on the white htc EVO 4G screen...
Click to expand...
Click to collapse
Did you recently upgrade your radios? If so did you go do a profile and prl update immediately after?
I've seen this issue occur after updating radios, and not updating profile.
Just a thought, and if your answer is no to having updated radios, Diablo had the first best bet just above.
Sent from my PC36100 using Tapatalk
Try the same setup with out dta2sd.
Had the same issue a while back and it was a2sd, everything would be fine until a reboot. Not sure what it is but the a2sd was the culprit...
Also, what ext are you using? ext 4 will bork in the same manner, make sure you are on ext 3.
Sent from my PC36100 using xda premium
jamieg71 said:
Did you recently upgrade your radios? If so did you go do a profile and prl update immediately after?
I've seen this issue occur after updating radios, and not updating profile.
Just a thought, and if your answer is no to having updated radios, Diablo had the first best bet just above.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
It's been over a month since I updated the radios and I did update my profile and prl. I was just on Tommy's Classic and did another update so I am pretty sure that was not the culprit.
imheroldman said:
Try the same setup with out dta2sd.
Had the same issue a while back and it was a2sd, everything would be fine until a reboot. Not sure what it is but the a2sd was the culprit...
Also, what ext are you using? ext 4 will bork in the same manner, make sure you are on ext 3.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
I did try ext4 but like you did figure that was part of the problem so I hooked up my card to my pc and did a full format and repartitioned my card to ext3 with no swap. I did try not going with a2sd but it seems that if I flash that at the very end it seems to work. I never had a problem flashing everything at once but I guess my phone is just being a ass now
If you wipe 3x and superwipe 3x that is over kill one wipe each is safe and fine..
Do you have that issue on all roms? Sounds like something isn't playing well on your phone.
nolimit06 said:
It's been over a month since I updated the radios and I did update my profile and prl. I was just on Tommy's Classic and did another update so I am pretty sure that was not the culprit.
I did try ext4 but like you did figure that was part of the problem so I hooked up my card to my pc and did a full format and repartitioned my card to ext3 with no swap. I did try not going with a2sd but it seems that if I flash that at the very end it seems to work. I never had a problem flashing everything at once but I guess my phone is just being a ass now
Click to expand...
Click to collapse
I noticed that you use amon ra 3.11. Have you tried amon ra 2.3?
Sent from my lair.
reaper24 said:
If you wipe 3x and superwipe 3x that is over kill one wipe each is safe and fine..
Do you have that issue on all roms? Sounds like something isn't playing well on your phone.
Click to expand...
Click to collapse
Agreed od's super wipe messed up my phone when I did it to much I had to fully clear out phone SD and all and factory reset via setting in phone not armon, worked fine after
Sent from my PC36100 using xda premium
I have had my G2 for about 18 months and have been running into a lot of issues recently. I've decided to fix those issues by rooting & getting a new ROM installed. I'm a tech savvy guy, but have not done anything on the phone end due to not wanting to break whats working. I've decided to go with the Mimicry 1.3.2 ROM since the install process uses Aroma and is very straight forward. Before I pull the trigger, I just want to make sure I have all the steps clear so that I don't go "Oh sh**" in the middle because I missed a step. There's also a couple of steps that I'm not clear on. Here's what I researched:
-Root phone using HTC's bootloader unlocker
-Format phone's flash memory to EXT4
--What is the best app to do this with? Will my phone work with Gingerbread after I make this change?
-Download Mimicry 1.3.2 and Google Apps put the zip files on my phone (not SD card)
-Power off phone and then push the volume down and power buttons together and choose to install the ROM
-Answer prompts in Aroma (including installing WiFi calling)
-Flash Google apps
--How exactly is that done?
-Restart phone and start setting up apps again.
Does that look correct and is there anything that I'm missing? Thank you in advance for your help.
Well first off I would stay away from HTC official unlocked bootloader, its worthless and will give you headaches in the future
use the wiki to root, either follow the wiki in cyanogen or here on xda, if you even slightly tech savvy it will be easy
following that guide you will have clockwork recovery, but I suggest moving to 4ext recovery, among many reasons is the ability to format to ext4. Otherwise the next easiest way to format would be to flash a super wipe script with ext4 format written to it (just search xda and you'll find it easier)
Now after you are rooted with an engineering s-off hboot consider flash the .19 radio, not super important but many find this to have the best reception and battery life.
Next make sure your SD card is fat32, I also suggest an ext4 partition there as well (easily done through recovery) but skip the swap
Now feel free to flash mimicry, and may I add this is one other best ICS Roms for the vision, and blk_jck is a very helpful Dev as well.
Good luck, if you run into issues there will be answers all over xda, just search a bit, happy flashing!
Sent from my Nexus 7 using xda premium
Thanks
Thanks for the heads up on the HTC bootloader. I'll check out the Wiki on how to PermRoot my phone.
Mimicry, recovery, soft bricks, and new ROM
Agree with demkantor, the step-by-steps so painstakingly described in cyanwiki are your best bet.
Likewise, using 4ext in place of clockwork is also my recommendation, as I've used both now and
find the latter more polished and stable.
I recently rooted and updated for the first time. Got successfully as far as ICS using cyan's instruction,
then decided to use mimicry after reading about the radio updates etc posted by madmaxx. I think the sequence in which i
carried these out was flawed, because after updating the radio instruction sets, I re-flashed mimicry to take advantage of the
updated radio features and to install the wi-fi telephony; that was my downfall. I got caught in a boot-loop. Oh sh*t, indeed.
I could not, for the life of me, get past the HTC white screen. Being a total noob, I had no
idea where to go to next. I searched this website and cyan's a lot, and realised the term for what I now had was a 'soft
brick' or 'semi brick'. Could not get the device to be recognised via ADB, and could not access the sdcard directory.
I scratched my head for a few days (I had bought another phone prior to playing with the old G2), and came up with the
idea of just accessing the sdcard via my laptop, directly. In the midst of this, I turned on the phone (after taking the card
out), and voila, the phone now cycled into engineering hboot !
I subsequently was able to edit the sdcard directly via the laptop (using an micro sd card adapter), and removed the pc10?.img file
that was left over the radio update. Having recovered to this point, I re-flashed mimicry 1.3.1 (via 4ext) and so was able to get a completely
functional phone again.
The point of all of the is this: 1. To all the previous post-ers, both here and at cyanwiki...You guys rock. Can't say that enough. Even more:
2. A 'soft brick' may be anything but...a little bit of not-very-complicated experimentation afterward can pay off big time. Lastly, I tried
mimicry 1.3.2, but kept getting a heap of error messages. Needless to say, I was a bit spooked by the previous stuff-up, so I quickly reverted
to 1.3.1, which appears to be 100% stable (IMHO).
Cheers
1.3.2 adds few framework level changes and no device level changes. Definitely nothing that should cause errors or problems booting anyway.
Sent from my HTC Vision using xda premium
Good Info
timram said:
Agree with demkantor, the step-by-steps so painstakingly described in cyanwiki are your best bet.
Likewise, using 4ext in place of clockwork is also my recommendation, as I've used both now and
find the latter more polished and stable.
I recently rooted and updated for the first time. Got successfully as far as ICS using cyan's instruction,
then decided to use mimicry after reading about the radio updates etc posted by madmaxx. I think the sequence in which i
carried these out was flawed, because after updating the radio instruction sets, I re-flashed mimicry to take advantage of the
updated radio features and to install the wi-fi telephony; that was my downfall. I got caught in a boot-loop. Oh sh*t, indeed.
I could not, for the life of me, get past the HTC white screen. Being a total noob, I had no
idea where to go to next. I searched this website and cyan's a lot, and realised the term for what I now had was a 'soft
brick' or 'semi brick'. Could not get the device to be recognised via ADB, and could not access the sdcard directory.
I scratched my head for a few days (I had bought another phone prior to playing with the old G2), and came up with the
idea of just accessing the sdcard via my laptop, directly. In the midst of this, I turned on the phone (after taking the card
out), and voila, the phone now cycled into engineering hboot !
I subsequently was able to edit the sdcard directly via the laptop (using an micro sd card adapter), and removed the pc10?.img file
that was left over the radio update. Having recovered to this point, I re-flashed mimicry 1.3.1 (via 4ext) and so was able to get a completely
functional phone again.
The point of all of the is this: 1. To all the previous post-ers, both here and at cyanwiki...You guys rock. Can't say that enough. Even more:
2. A 'soft brick' may be anything but...a little bit of not-very-complicated experimentation afterward can pay off big time. Lastly, I tried
mimicry 1.3.2, but kept getting a heap of error messages. Needless to say, I was a bit spooked by the previous stuff-up, so I quickly reverted
to 1.3.1, which appears to be 100% stable (IMHO).
Cheers
Click to expand...
Click to collapse
Thanks for that info. I am taking a look at the Cyanogen Wiki and seeing what I have to do. I'm thinking that I will jump directly to Mimicry 1.3.2 instead of installing Cyanogen 9 first. Hopefully that file doesn't hang out there and causes that boot loop to happen to me (thanks for that explanation, BTW).
So do I have to use that ClockworkMod to load the ROM, or does EXT4 do the same thing (as far as loading the rom goes)?
...where thanks is due
many thx, blk jack, I should have specifically mentioned your awesome contributions as well, and
have remedied with thanks meter as i came/come across it.
Will re-try the 1.3.2 shortly. If I run in to the same glitches, I will try and make note of the specific errors
(or any other bugs, for that matter) and let you know.
Use the following guide, it is incredibly simple yet swift. Contains root methods for both the DesireZ and the T-Mobile G2 :
http://wiki.cyanogenmod.com/wiki/TMobile_G2:_Rooting
Checking it out now
iamnoobie said:
Use the following guide, it is incredibly simple yet swift. Contains root methods for both the DesireZ and the T-Mobile G2 :
Click to expand...
Click to collapse
I'm actually looking at that wiki right now. I just finished backing up all the contents on my SD card. I can't backup the apps on my phone since it's not rooted, and I can't use a backup app unless I'm root. So it looks like that is a catch 22. Personally, I don't mind wiping everything anyways since I'm going to be making the jump to ICS. I guess I'll have to beat all those levels in cut the rope again :crying:
@deadeye
actually, the only important bits are your contacts, sms's, phone logs, etc (if these matter to you), which i think you can backup via gmail. Additionally, any other (or all) files on the SD card, you should be able to just copy directly onto a folder in your laptop or desktop (see the post I made above). HTH.
timram said:
@deadeye
actually, the only important bits are your contacts, sms's, phone logs, etc (if these matter to you), which i think you can backup via gmail. Additionally, any other (or all) files on the SD card, you should be able to just copy directly onto a folder in your laptop or desktop (see the post I made above). HTH.
Click to expand...
Click to collapse
Thanks for that. I've now downloaded the Android SDK and am now trying to test the connection to my G2 using adb. So far, no connection. Grrrr. I'm looking around now to see how to get my phone detected by adb since it doesn't seem to have anything on the cyanogen wiki.
you downloaded adb.exe from within the sdk right? find the folder it is in (usualy platform tools) hold shift right click within the folder and choose open command here
now type adb devices, you should se some letters and numbers that means you good if not need to trouble shoot some more
alternatively you can change the path within enviromental variables so you can open a cmd anywhere
Sent from my HTC Vision using xda premium
HTC Sync
demkantor said:
you downloaded adb.exe from within the sdk right? find the folder it is in (usualy platform tools) hold shift right click within the folder and choose open command here
now type adb devices, you should se some letters and numbers that means you good if not need to trouble shoot some more
alternatively you can change the path within enviromental variables so you can open a cmd anywhere
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I tried the adb devices command and it didn't return any connected devices. Looking in the xda wiki, they are saying that I need to have HTC Sync installed. I'm downloading that right now. They probably should put that in the cyanogenmod wiki also.
I got my phone detected by adb! I did some preliminary checking and I think I should be good to go on rooting. I think I will root my phone tomorrow when I have plenty of time to troubleshoot any issues that my come up.
This is just the thread I was looking for. I'm also an old (60) tech-savvy guy who has never rooted his phone, and was nervous about which set of rooting instructions (cyan-wiki or Setherio/Strawmetal?; the latter is more recently updated, seems a bit more detailed, and has newer versions of some utilities) which recovery, ClockworkMod or ext4, and which ROM, Cm9 unofficial or mimicry or even AOKP...
You all seem to feel cyan-wiki instructions better (right?) ext4 and mimicry... Shall I go for it? Last suggestions?
Thanks,
Dave
Sent from my T-Mobile G2 using xda app-developers app
prairie-dad said:
You all seem to feel cyan-wiki instructions better (right?) ext4 and mimicry... Shall I go for it? Last suggestions?
Click to expand...
Click to collapse
Cyan wiki worked for me! (strawmetal didn't - I blame myself though).
ext4 and mimicry are what I'm running now (after going through CWM, CM 7.2 and CM9 RC1 & RC2) and I'm very happy with both. Mimicry is great!
prairie-dad said:
This is just the thread I was looking for. I'm also an old (60) tech-savvy guy who has never rooted his phone, and was nervous about which set of rooting instructions (cyan-wiki or Setherio/Strawmetal?; the latter is more recently updated, seems a bit more detailed, and has newer versions of some utilities) which recovery, ClockworkMod or ext4, and which ROM, Cm9 unofficial or mimicry or even AOKP...
You all seem to feel cyan-wiki instructions better (right?) ext4 and mimicry... Shall I go for it? Last suggestions?
Thanks,
Dave
Sent from my T-Mobile G2 using xda app-developers app
Click to expand...
Click to collapse
setherios guide is just for the downgrade process
the cyanogen wiki, xda wiki, and strawmetals pdf guide are all more or less the same guide, just writen a tad differently
as for the recovery 4ext is far superior but feel free to switch recoveries later if it complicates thing, very easy to do
as for a rom choice there are many good ones and it will be hard to recommened one so try a few, make nandroid backups, and see where your prefernce lies. if you like ics then my personal opinions are elitemod ics or mimicry, both are great. don't care much for sense so you will have to explore by yourself on those (you will need the dz hboot if you want any sense roms - easily done)
if you want gingerbread try ilwt or elitemod cm7 (this is still the rom I almost always use, even curently)
have fun, read, read some more, search when stuck... this is should all be easy as you say your tech savvy - happy flashing!
Sent from my HTC Vision using xda premium
minor glitches, but rooted and s-off fine
demkantor said:
setherios guide is just for the downgrade process
the cyanogen wiki, xda wiki, and strawmetals pdf guide are all more or less the same guide, just writen a tad differently
as for the recovery 4ext is far superior but feel free to switch recoveries later if it complicates thing, very easy to do
as for a rom choice there are many good ones and it will be hard to recommened one so try a few, make nandroid backups, and see where your prefernce lies. if you like ics then my personal opinions are elitemod ics or mimicry, both are great. don't care much for sense so you will have to explore by yourself on those (you will need the dz hboot if you want any sense roms - easily done)
if you want gingerbread try ilwt or elitemod cm7 (this is still the rom I almost always use, even curently)
have fun, read, read some more, search when stuck... this is should all be easy as you say your tech savvy - happy flashing!
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
all went well till the very, very, very end. I went to reboot into clockwork recovery, and...nothing doing! holding down the trackball, volume down and power...and waiting and waiting...just got me into the bootloader with no option to go to recovery...just reboot, reboot the boot loader, and power down.
So I thought, maybe I somehow failed to get the recovery img where I wanted it...no big deal. I logged onto the old Market (this is 2.2, after all) and purchased 4ext (which is what seems to be everyone's choice) and installed it. Then I said I wanted to reboot with mimicry and gapps, hit "go," and...it rebooted into ClockworkMod Recovery...where it now sits, I assume backing up the existing system. Mimicry 1.3.2 and gapps images were sitting on my sdcard root, btw.
Very odd, and a little perplexing...I will wait it out a while before powering off and up again.
any thoughts? Must I remove clockwork mod manually (I assume that when I installed 4ext it made itselfthe default recovery method...) or does 4ext just sit atop Clockwork Mod...and what I am seeing now is normal...? I've been waiting a few minutes now, and see nothing but the Clockword Mod icon, the top hat.
Sigh...but pretty clearly almost all the way home.
Thanks to all,
dave
I've never used an app to install a recovery, always used fastboot.
But to answer your question 4ext does replace clockwork, it does not sit on top of it. Just downloading the app well... downloads the app. You must then go into the app and choose to download and install the recovery, after this from within the recovery flash your ROM (and gapps etc. If needed)
I have the 4ext app just for the purpose of supporting the Dev as anything that does me good deserves my money but I really have never bothered much with it so off hand I can't tell you the exact steps to do this but I'm sure it s very straight forward.
Good luck and let us know how all turns out
Sent from my Nexus 7 using xda premium
darn ClockWorkMod/4ext clash!
demkantor said:
I've never used an app to install a recovery, always used fastboot.
But to answer your question 4ext does replace clockwork, it does not sit on top of it. Just downloading the app well... downloads the app. You must then go into the app and choose to download and install the recovery, after this from within the recovery flash your ROM (and gapps etc. If needed)
I have the 4ext app just for the purpose of supporting the Dev as anything that does me good deserves my money but I really have never bothered much with it so off hand I can't tell you the exact steps to do this but I'm sure it s very straight forward.
Good luck and let us know how all turns out
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks...I sat and looked at it for a while, then hit power, and up came the ClockworkMod menu...and did nothing. When I asked _it_ to load a zip from the sdcard...it still sat there stupidly...nice menu but no action. so I rebooted with trackball/volume-down and power...and still can't get to the bootloader menu...the only way is to attach via usb, and do adb reboot bootloader...which gives me a bootloader menu showing no recovery app...just the same options as before. ugh. I wonder what the recovery.img is...? I went through the steps of installing 4ext...and it said it had installed itself.
well, I will poke around a tad more...midnight now...at least I have a working phone on 2.2, rooted, S-OFF, etc.
dave
---------- Post added at 07:33 AM ---------- Previous post was at 06:42 AM ----------
prairie-dad said:
Thanks...I sat and looked at it for a while, then hit power, and up came the ClockworkMod menu...and did nothing. When I asked _it_ to load a zip from the sdcard...it still sat there stupidly...nice menu but no action. so I rebooted with trackball/volume-down and power...and still can't get to the bootloader menu...the only way is to attach via usb, and do adb reboot bootloader...which gives me a bootloader menu showing no recovery app...just the same options as before. ugh. I wonder what the recovery.img is...? I went through the steps of installing 4ext...and it said it had installed itself.
well, I will poke around a tad more...midnight now...at least I have a working phone on 2.2, rooted, S-OFF, etc.
dave
Click to expand...
Click to collapse
Mimicry is booting now. All good. I ended up using the clockwork mod version, 3. something, that I installed when following (too slavishly?) the CM wiki's instructions (otherwise excellent!) Then (and now) I have problems booting into the bootloader, and it doesn't show a recovery option... Running 4ext (which I purchased) seems to be great (looks really useful) until rebooting...when CWM comes up instead.
I kept using volume up or down to pick what I wanted, then pushed the power button to select...wrong! It's the trackball you click, which I only hit upon by accident. Once I got that working, I flashed mimicry and Gapps, and I am off to the races again.
Thanks to all, but I want to figure out what is with recovery for the future.
What buttons do I push to get to bootloader...so far all I have gotten to work is via USB cable and "dab reboot boot loader."
dave
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?