Related
Im getting this error and force close on one of my Heros when I try installing any of my apps on any of the 2.1 roms. Im coming from Fresh 1.1 and following the same procedure I used on my other Hero on which the market is fully functional. Ive wiped everything over and over and cleared data on anything that looked like it at to do with the market. I also tried fix apk mismatches from recovery. Short of RUU which Id like to avoid if at all possible Ive tried everything else I can think of. In searching I have come across this error code on other android phones, but nothing on the hero and nothing specific to trying to install apps. So has anyone else seen this? And would RUU do anything a full data wipe didnt already?
Reading instructions has its benefits grasshopper...
Download the latest recovery and throw it onto your SD Card, boot into the old version of recovery and flash the new recovery as a .zip update, reboot into recovery again and then wipe your phone again, then install android 2.1, don't reboot yet, make sure your rom either has it's own custom kernal or download one for 2.1 and flash it, open up adb and clear dalvik cache and boot cache, then reboot your phone and you should load without any problems.
Thanks. But I did that from the get go. Aside from flashing a kernal, but Im running Darchtrev2 on the fully functional Hero that I mentioned and thats got a custum kernal built into the rom. So thats what I started with on the second one using the exact same process without success. Does wiping from adb do more than wiping from recovery? Thats one other thing I didnt do after the initial install.... But do understand you correctly that you have seen this specific error before?
Just bumpin the tread in hopes of finding a solution. I dont even mind gettin flamed for asking a stupid question if I could get linked up with a fix! lol I see its getting views, just no ideas I guess... It sucks cuz everything else works fine except the market. I get the list of my downloads, when I tap on one to install I the download button instead of the install button, so Ill tap on it and I get get the progress bar saying its downloading. When it gets to 100% I get the error and force close... Anyone?
I would try wiping again then flashing fresh 1.1 see if that boots and everything works ok then I would redownload the recovery and flash that still running fresh then reboot make sure everyhting is cool, then redownload whatever 2.1 rom you want and wipe and flash.
doing this serves 2 purposes
1. make sure that somewhere along the line none of the files corupted
2. if you still have the same problem then it will let you know where the problem is coming from.
just process of elimination
if you still have problems after that then I would say RUU, yes it is different than just wiping from recovery as it restores a completely stock image and gets rid of everything else. all a data wipe really does is get rid of user data.
just my opinion.
honestley thinnking about it I RUU'd my phone just for giggles then I re-rooted and then flashed DCv1 right from stock and I found that a lot of the little bugs that people where seeing I wasnt so it may not be a bad idea to ruu anyways.
Thanks for the reply and for giving me something different to try. I hadnt thought about trying that. Frustration I guess! It makes sense though. Ill give it shot. Thanks!
Why not see why it fc'd?
Adb with logcat of ...vending....
Find the syntax here: http://developer.android.com/search.html
Just an idea. It may or maynot give you the insight to fix the cause ( like a parameter ...vending... is null fetching on ).
Yeah, Ive been thinking about RUU'n too just to see if making a fresh start would make any difference, but after all the time I spent getting the one Hero working like I want on 2.1 and the troubles Ive had with the second and what Ive read about people bricking trying to RUU or flash recovery Ive been kinda hesitant....
willy900wonka said:
Why not see why it fc'd?
Adb with logcat of ...vending....
Find the syntax here: http://developer.android.com/search.html
Just an idea. It may or maynot give you the insight to fix the cause ( like a parameter ...vending... is null fetching on ).
Click to expand...
Click to collapse
Thanks. I dont know that Im quite that knowledgable though. Im sure I could read a logcat... understanding what the hell I would be reading is something else again. Saving the url though in case I need to dig deeper. Thanks for the reply.
wtphoto said:
honestley thinnking about it I RUU'd my phone just for giggles then I re-rooted and then flashed DCv1 right from stock and I found that a lot of the little bugs that people where seeing I wasnt so it may not be a bad idea to ruu anyways.
Click to expand...
Click to collapse
Sometimes it's just fun to RUU and do everything again
Alright if you're still having problems then just follow these steps:
Boot into recovery and make a nandroid back up just in case something goes wrong.
Download the latest version of your current 2.1 rom and reflash it from Recovery.
Open up adb and mount the /data directory (adb shell, mount /data)
Enter the following two commands in adb: rm -r /data/boot-cache , rm -r /data/dalvik-cache
Go Back to ADB and type the following commands: cd /data/data/com.android.vending , rm -R cache
Fix UID Mismatches using the tool in Recovery and then reboot your phone
regaw_leinad said:
Sometimes it's just fun to RUU and do everything again
Click to expand...
Click to collapse
or NOT!
Thanks again for your help all. I ended up just RUU'in . I'm with fixxer... fun isn't how I'd describe it! Anyway, I got it all working just to find out its got the mms issue now... if its not one thing its another. Oh well, something for me to work on tomorrow! Thanks again for the replies and advice.
HERNANDEZ4LIFE said:
Thanks again for your help all. I ended up just RUU'in . I'm with fixxer... fun isn't how I'd describe it! Anyway, I got it all working just to find out its got the mms issue now... if its not one thing its another. Oh well, something for me to work on tomorrow! Thanks again for the replies and advice.
Click to expand...
Click to collapse
You should have updated to the latest ruu...
wcgbmd said:
You should have updated to the latest ruu...
Click to expand...
Click to collapse
The latest RUU? I used the 1.56..... I did get it working tho. Flashed the mms. fix zip. Just wasn't expecting to have to as I didn't with my other hero. Don't know what the difference is between the two devices. Both are google branded, but the second one fought me every step of the way.
HERNANDEZ4LIFE said:
Thanks again for your help all. I ended up just RUU'in . I'm with fixxer... fun isn't how I'd describe it! Anyway, I got it all working just to find out its got the mms issue now... if its not one thing its another. Oh well, something for me to work on tomorrow! Thanks again for the replies and advice.
Click to expand...
Click to collapse
First, sorry for the bump.
I just started getting this error and wanted to know if you figured out exactly what it was so I didn't have to go through that whole RUUing process. Thanks.
don't know if this is your problem, but i know on sushi rom you have to go to manage applications, market, click on it and then click on uninstall updates.. Then apps. will download and install correctly.
boredmug said:
don't know if this is your problem, but i know on sushi rom you have to go to manage applications, market, click on it and then click on uninstall updates.. Then apps. will download and install correctly.
Click to expand...
Click to collapse
You're the bomb. That worked like a charm.
boredmug said:
don't know if this is your problem, but i know on sushi rom you have to go to manage applications, market, click on it and then click on uninstall updates.. Then apps. will download and install correctly.
Click to expand...
Click to collapse
Cant believe nobody wrote this first
boredmug said:
don't know if this is your problem, but i know on sushi rom you have to go to manage applications, market, click on it and then click on uninstall updates.. Then apps. will download and install correctly.
Click to expand...
Click to collapse
I was having the same problem on DC a couple days ago and that fixed it for me. I was reading this thread wondering why no one had mentioned it yet.
Ok so, i just added the Fresh Toast v1.1, it was working AMAZINGLY. But then i accidentally hit the camera button while tryin to remove it from the home screen, it poped up the camera, Said "Updating PRL", force closed like 4 programs, then rebotted it self. Since then, no service. Contacted sprint (Did'nt tell them it was rooted) but they did a few master resets, troubleshooting here and there. still nothing
note: did wipe/factory reset twice and reinstalled toast, didnt work
note: also wiped, then restored my nanoid back up. also didnt work
anyone know how to help me out? would prefer not to have to go to the sprint store then they find out its rooted >.>
would greatly appreciate the help
Downtime24 said:
Ok so, i just added the Fresh Toast v1.1, it was working AMAZINGLY. But then i accidentally hit the camera button while tryin to remove it from the home screen, it poped up the camera, Said "Updating PRL", force closed like 4 programs, then rebotted it self. Since then, no service. Contacted sprint (Did'nt tell them it was rooted) but they did a few master resets, troubleshooting here and there. still nothing
note: did wipe/factory reset twice and reinstalled toast, didnt work
note: also wiped, then restored my nanoid back up. also didnt work
anyone know how to help me out? would prefer not to have to go to the sprint store then they find out its rooted >.>
would greatly appreciate the help
Click to expand...
Click to collapse
wow... idk man, i actually have no clue really. ive been hitting the camera button for days trying to debug camera and havent ran into some crazy stuff like that. all it does is sit with a black screen on mine.
oh man! and your 1 of the developers lol
my phone is done?
Downtime24 said:
oh man! and your 1 of the developers lol
my phone is done?
Click to expand...
Click to collapse
Nah. Just RUU back to 1.5, that oughta fix it.
smw6180 said:
Nah. Just RUU back to 1.5, that oughta fix it.
Click to expand...
Click to collapse
+1, RUU back will usually fix any crazy abnormalities. This will unroot your phone too, so if you do need to bring it to sprint, it will be back to complete unrooted factory
Yeah man go ahead and ruu. Or flash fresh 2.0d first and see if that fixes it. His Rom includes a pri fix
sounds like a plan lol.
mind providing the link to RUU? I've never done it before
Fresh 2.0d has a PRI fix?!? I've loaded that before and my PRI still says Flipz_01...
SupahDave said:
Fresh 2.0d has a PRI fix?!? I've loaded that before and my PRI still says Flipz_01...
Click to expand...
Click to collapse
That is the PRI fix.... If your PRI is Flipz_01, you're good..
Also, the RUU is here:
http://forum.xda-developers.com/showthread.php?t=608434
did the RUU, but at the end it gives me an error, now my hero aint responding at all O
errors the file open error, re-downloaded about 6 times, still hasnt worked T_T
i would reccomebd unrooting sans sd card.
theres a fix floating around for the ruu error, assuming your getting the same one
good luck!
mountaindont said:
i would reccomebd unrooting sans sd card.
theres a fix floating around for the ruu error, assuming your getting the same one
good luck!
Click to expand...
Click to collapse
Search ruu error 110 fix. This should help fix the problem
Download files and place on SD card:
update-nexusone-FRF50-noradio-signed.zip from Modaco.com (May 24: noradio files added - should work fine for T-Mo & AT&T!)
froyo-rooter-signed.zip from Cyanogen
Titanium Backup -> Backup all user apps
Turn off phone -> Hold Volume Down, then Press Power button
Enter Recovery
Backup/Restore -> Nand backup
Wipe if you have a Sense UI ROM (no wipe needed coming from Cyanogen)
Flash update-nexusone-FRF50-signed.zip
Reboot, you'll get Android-falling-out-of-box
It will reboot into Recovery, select Reboot again
It should boot into 2.2, yay!
You should still have root, but if you want BusyBox (or lost root somehow), Cyanogen has done it again! Go back into Recovery and flash froyo-rooter-signed.zip. Then Titanium Backup will work once again.
Cyanogen for Prez
Paul for vice prez
(no hate on paul... just cant be prez since he wasnt born here )
i'm getting a picture of an Android falling out of a box
joksinjai said:
i'm getting a picture of an Android falling out of a box
Click to expand...
Click to collapse
I got that while the radio was updating, it should boot back into the recovery menu then reboot once more for FroYo
nDrg said:
I got that while the radio was updating, it should boot back into the recovery menu then reboot once more for FroYo
Click to expand...
Click to collapse
It worked! this is my first time doing this, so i got scared of the open box based on Paul's 100% fool proof guide
=)
joksinjai said:
i'm getting a picture of an Android falling out of a box
Click to expand...
Click to collapse
Yep! When it reboots to recovery, reboot again. Updated OP
Thanks Paul And Cyanogen!
As Always...Great work!
iam trying
once your done installing 2.2 get flash
http://www.androidcentral.com/now-we-have-froyo-its-time-feed-flash-android-22
Freaking sweet! I lost root for whatever reason. Glad to see that Paul and Cyanogen pumped this stuff out! And a flashing I will go!
My flash runs like crap unfortunately. I am getting some FCs too on SMSing apps
Does this work on AT&T devices?
AGeleff said:
Does this work on AT&T devices?
Click to expand...
Click to collapse
I think only if you're rooted. I'm not sure.
AT&T users in the Modaco thread have said it worked. Here's one poster who's done it:
http://android.modaco.com/index.php?s=&showtopic=309286&view=findpost&p=1284057
Post #76:
I think you can just not flash the radio, I do have an AT&T frequency too so I am not taking chance, I will remove the radio.img prior to install
Click to expand...
Click to collapse
don't worry about it. Just flash it. You'll get a speed bump. I did. Getting about 1mb faster DL speeds. Its crazy... especially since its mid-day saturday. I'm on ATT 3g in chicago.
Click to expand...
Click to collapse
Though as the previous person said, you may have to remove the radio.img in the zip. I'm totally not sure. Has anyone here done it?
AGeleff said:
Does this work on AT&T devices?
Click to expand...
Click to collapse
It should work on any rooted Nexus handset.
AGeleff said:
Does this work on AT&T devices?
Click to expand...
Click to collapse
People are saying in this thread that it DOES indeed work!
http://forum.xda-developers.com/showpost.php?p=6563603&postcount=255
http://forum.xda-developers.com/showpost.php?p=6563614&postcount=256
so when updating to froyo does rooted nexus one becomes just like the stock one, means do we need to root it again to install custom Rom
Thank you. This is awesome and super easy to execute. Thanks again.
Nice! thanks for the write up.
one thing that confuses me though, i have rooted my phone but have the stock rom (nadroid from cyanogen 506), will i be able to get the OTA when it rolls for the ATT version? Or only manual update for me?
thanks.
Everything works, great post by paul as usual
I followed these steps (was running Cyanogen 5.0.6) and it works perfectly. I have the AT&T/Rogers version. I didn't wipe and all my apps/settings are intact!
OK, congratulate me!! Thanks. I did it on the first try, no issue or hiccups what-so-ever.
Now for the info. I'm not sure that anyone will be interested, but I'm guessing other people in my position at least might be.
I'm very experienced with computers, but not working directly with rooting/unlocking devices. But I would say anyone who reads up a bit and can follow directions properly could pull it off pretty easily.
So I run 2.2.2, and I used superoneclick 1.6.3.
After opening superoneclick, I switched it from psneuter to rageagainsthecage. I had no idea if I was supposed to do this, but I read all about rageagainstthecage, and never heard of psneuter.
I had my phone connected to my PC, and I left my SD in the phone, but I unmounted it in settings. I have used ADB before, so I knew the drivers were installed and working, and I hit the button root.
After reading this site, http://forum.xda-developers.com/showthread.php?t=803682, I started with debugging off, and turned it on as it said. I then turned it off, but didn't get a chance to turn it back on and off and on, so I just turned it back on (debugging) when it got to "Waiting for device" for the second time.
That was it! It asked to test and see if root was in fact accomplished, and it was. I then installed setCPU (which is basically the only reason I wanted to do this) and as far as I can tell it seems to be working fine.
I have been reading a lot about this for the past few days, but the actual procedure only took a couple of minutes. Keeping in mind, of course, that I already had ADB and drivers working.
Nothing was wiped off my phone, which surprisingly was hard to confirm on the web. I did read somewhere that only unlocking wipes data, but still, you never know.
I hope this helps anyone else who is new and unsure of the process, and I'd be happy to answer any other specific questions based on what I have learned of the last week or so. I know that people hesitate to ask questions in case they have already been asked lots of times, but are buried and hard to find (because that's the position I was in ).
Thanks for posting your "rooting" experience. I'm sure there are people that will find it helpful.
I think when I did mine, it was something along the lines of:
fastboot-oem-unlock
fastboot flash recovery <whatever>
reboot into recovery and flash rom
Other than the ability to install custom ROM's I've yet to see a huge deal in rooting my phone. Anyone care to tell me what I can do with a rooted N1 that is a must have? So far I tried to change some fonts, which didn't work, and discovered that I have to install a custom ROM to change the color of the notification bar, and I can't make the default Google music and news widgets slightly transparent. So educate me, what's the huge deal with rooting, aside from a custom ROM?
Set cpu of course like being said. I remember the first time I rooted my phone was universal androot it was a breeze. Then I lost root and use super one click to gain out back. Root really easy as well
Sent from my Nexus One using XDA App
- Backup application, like MyBackup, can backup your app data(including game save...) if your device is rooted.
Hi N1 owners.
I also just root my N1 with superoneclick 1.6.3
After that I flashed CM 6.1.1 and yesterday I tried CM7. Everything has worked fine for me so far, but I have some questions, I hope someone can answer.
1/Can I just flash random roms on top of each other, like i did from cm6 - cm7?
2/ Can I always restore backups, nomatter what rom I come from or to?
3/ when/if official GB come out, can I flash a stock rom and get the OTA update right away?
Sorry, if I ask silly questions ..
Built in trackball colors, call blocker, hide frequently called list in the favorites tab, remove unnecessary apps, tmobile wifi calling, notification bar power toggles, trackball wake and unlock, quiet hours, themes, etc., etc., etc. Just off the top of my head. Oh, and Gingerbread!!!
Sent from my Nexus One using Tapatalk
Some apps want to bypass the home screen "5 second rule" like widget locker, you need root. I setup a widget to reboot (nice!).
brettbellaire said:
...I did read somewhere that only unlocking wipes data, but still, you never know.
Click to expand...
Click to collapse
Unlocking the Bootloader wipes data, rooting does not. This is probably what you read.
offenberg said:
Hi N1 owners.
I also just root my N1 with superoneclick 1.6.3
After that I flashed CM 6.1.1 and yesterday I tried CM7. Everything has worked fine for me so far, but I have some questions, I hope someone can answer.
1/Can I just flash random roms on top of each other, like i did from cm6 - cm7? Yes you can. Often if the ROM is the next version in a series, you can flash without wiping data or cache, but some ROMs require you to do this first.
2/ Can I always restore backups, nomatter what rom I come from or to? A Nandroid backup can be reinstalled from any ROM, or even just from Recovery if there is no ROM.
3/ when/if official GB come out, can I flash a stock rom and get the OTA update right away? Yes. Either restore your stock ROM Nandroid backup or a passimg.zip.
Sorry, if I ask silly questions ..
Click to expand...
Click to collapse
offenberg said:
Hi N1 owners.
I also just root my N1 with superoneclick 1.6.3
After that I flashed CM 6.1.1 and yesterday I tried CM7. Everything has worked fine for me so far, but I have some questions, I hope someone can answer.
1/Can I just flash random roms on top of each other, like i did from cm6 - cm7?
2/ Can I always restore backups, nomatter what rom I come from or to?
3/ when/if official GB come out, can I flash a stock rom and get the OTA update right away?
Sorry, if I ask silly questions ..
Click to expand...
Click to collapse
1. As a rule, if you are going from 1 ROM to another totally different ROM, it's always a good idea to wipe. It only takes a few seconds to sign back in to everything. You can bypass immediate sign in and activate wifi if you need it.
2. Nandroids can be reinstalled anytime. However, a nandroid does not contain your HBOOT and Radio. So if you updated those to use a specific ROM, they would stay in place with the nandroid restore.
3. When GB does finally make it out to our specific device, there is no way you would get an OTA before the ROM devs here had you up and running.
***Also note, the 1-click root tools may or may not work right away with the OTA 2.3. So to anyone that rooted using those tools and unrooted to hurry up and get an OTA, you may be stuck on stock until it gets fixed.
Know-Fear said:
1. As a rule, if you are going from 1 ROM to another totally different ROM, it's always a good idea to wipe. It only takes a few seconds to sign back in to everything. You can bypass immediate sign in and activate wifi if you need it.
Click to expand...
Click to collapse
I agree, do a full wipe if it's a new ROM. Titanium Backup is a great way to get all of your apps and data back after installing the new ROM.
bigmout said:
I agree, do a full wipe if it's a new ROM. Titanium Backup is a great way to get all of your apps and data back after installing the new ROM.
Click to expand...
Click to collapse
So what do you lose (if anything) when flashing a new ROM if you backup and do things the right way?
Another question would be if you just flash a new kernal do you lose any/all data?
brettbellaire said:
So what do you lose (if anything) when flashing a new ROM if you backup and do things the right way?
The only thing you'd lose is the old rom
Another question would be if you just flash a new kernal do you lose any/all data?
Click to expand...
Click to collapse
Nope
Sent from my Nexus One using XDA App
kmiloco49 said:
Nope
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Interesting... Thanks!
@ brettbellaire
I've rooted before, and lost root when ota's came. I've rooted again using superoneclick, and am contemplating cm7. But I feel very cautious about flashing a different rom, I'd cry if I bricked my phone. However, I'm probably going to do it during the next week (unless gingerbread ota arrives).
Andy
Sent from my Nexus One using XDA App
Hmmm, I have been anxious for GB too.... but I'm not sure it's worth it. I don't think it's such a big update. I don't think there's too much of a danger of brinking these days.
I have been contemplating doing what I have to to overclock, see what kind of a difference that makes...
bigmout said:
I agree, do a full wipe if it's a new ROM. Titanium Backup is a great way to get all of your apps and data back after installing the new ROM.
Click to expand...
Click to collapse
I am a newbie to root. Can Titanium Backup restore the paid apps? because some apps require online verification with Google at the first time of use.
Also, Z4root does not work on my N1. I want to use superoneclick but where can I find the driver for my win7? thanks
unroot
is it possible to go back and unroot the phone? i.e. hide the padlock during phone startup ..I am using N1 ForYo 2.2.2..Thanks
zmalach said:
is it possible to go back and unroot the phone? i.e. hide the padlock during phone startup ..I am using N1 ForYo 2.2.2..Thanks
Click to expand...
Click to collapse
If you see the padlock, you've got an unlocked boot-loader. This can't be re-locked.
Sent from my Nexus One using XDA App
Hey guys, about a week or two ago, I went to a T-Mobile store to upgrade to 2.3.4. I have been looking into rooting and loading CM7, but im not sure how to do it and what is the best way. I was thinking about doing it with ADB, but im just too chicken to try it. I can't afford to break this phone, so i have to be really careful. If you have any other better ideas as to how I could root 2.3.4, that would be awesome. Also, if you have found any way to unbrick it if it gets bricked somehow in the process, that would be great too. I am an experienced hacker, and am working on starting to develop apps for Android and Apple. Thanks guys, I really need your help.
There is no root for 2.3.4 yet
Sent from my HTC Glacier using Tapatalk
Please read the Wiki in my signature. It has all the guides you'll need.
Here
http://forum.xda-developers.com/showthread.php?t=1178912
Sent from my HTC Glacier using XDA App
Just want to note that that guide is not the solution for all Gingerglaciers. Some devices (mine included) cannot make it past the first step due to 'permission denied'.
Who else is in the waiting line for rootage?
AwesomeTurtle said:
Just want to note that that guide is not the solution for all Gingerglaciers. Some devices (mine included) cannot make it past the first step due to 'permission denied'.
Who else is in the waiting line for rootage?
Click to expand...
Click to collapse
how are you entering the first step, the reason i ask is because i had to help someone who entered it wrong once he followed what i told him it was smooth sailing
AwesomeTurtle said:
Just want to note that that guide is not the solution for all Gingerglaciers. Some devices (mine included) cannot make it past the first step due to 'permission denied'.
Who else is in the waiting line for rootage?
Click to expand...
Click to collapse
This says nothing about the quality of the solution, but rather means that you're not executing the guide correctly.
agrabren said:
* If you get a permission denied, we don't have enough access rights and can't exploit the device.
Click to expand...
Click to collapse
Just in case you all start getting condescending about people not pulling through successful with Ultimate Guide Deluxe. I am not doing it wrong and chances are I know a tad more about this process than you.
There are always chances. On the other hand, chances often lie. Read this:
http://forum.xda-developers.com/showthread.php?t=1185243&page=7
From post 62 downwards.
Then you can count your chances again, or post here about how you and some others missed the obvious.
AwesomeTurtle said:
Just want to note that that guide is not the solution for all Gingerglaciers. Some devices (mine included) cannot make it past the first step due to 'permission denied'.
Who else is in the waiting line for rootage?
Click to expand...
Click to collapse
I am. I'm not well versed enough to do the downgrade-via-ADB thing. All I want to do is temproot, freeze the bloatware on the stock 2.3.4. I'm not interested in flashing a ROM or having permanent root. From what I understand, this isn't possible without downgrading.
Tom Barrister said:
I am. I'm not well versed enough to do the downgrade-via-ADB thing. All I want to do is temproot, freeze the bloatware on the stock 2.3.4. I'm not interested in flashing a ROM or having permanent root. From what I understand, this isn't possible without downgrading.
Click to expand...
Click to collapse
No, it isn't possible. You have to downgrade and install pre-rooted 2.3.4.
It's not really that hard. You could start by trying to set up ADB, and if you get a working environment - you'll know that you're good to go with the guide.
Sorry to raise a dead thread, but I was just wondering if anyone had come across a 2.3.4 root method. I am trying to root my fiancee's device and seem to be getting nowhere.
Apologies also if this has already been addressed.
Thanks guys =]
The rooting method for 2.3.4 involves downgrading to 2.2.1. That's the way it has been, that's most probably the way it'll stay, for a long time, possibly indefinitely.
how to unbrick t-mobile htc mytouch 4g glacier
guys, i successfully rooted my friend's htc glacier mytouch 4g.i noticed dat the backup failed.then i tried flashing this ROM cm-10.1-20130710-Albinoman887-glacier.zip, it was successfully installed.i now clicked on reboot it just got stock on flash screen.i tried factory reset. but any time i clicked on it it takes me back to recovery mode.please help me.my friend is about to turn me to his enemy.
take out your battery, then out it back in
Hold the volume down button and the power button, select recovery (use the volume keys)
Then when your in there, do a factory reset, wipe cache and dalvik (if your using cwm then go to advanced then wipe dalvik)
Then re-flash the rom.
N_otori0us_ said:
take out your battery, then out it back in
Hold the volume down button and the power button, select recovery (use the volume keys)
Then when your in there, do a factory reset, wipe cache and dalvik (if your using cwm then go to advanced then wipe dalvik)
Then re-flash the rom.[/QUOwhen i click on factory reset, it boots into recovery mode.i have tried two different roms cm10.1 amd a cm7 but not the stock rom. please i need more help
Click to expand...
Click to collapse
daddydizzleman said:
N_otori0us_ said:
take out your battery, then out it back in
Hold the volume down button and the power button, select recovery (use the volume keys)
Then when your in there, do a factory reset, wipe cache and dalvik (if your using cwm then go to advanced then wipe dalvik)
Then re-flash the rom.[/QUOwhen i click on factory reset, it boots into recovery mode.i have tried two different roms cm10.1 amd a cm7 but not the stock rom. please i need more help
Click to expand...
Click to collapse
lol you wanna go back to stock?
Ok then, well look around for the PD15IMG.zip for 2.3.4 then put it on your sd card at the root, and then go into bootloader again.
Click to expand...
Click to collapse
N_otori0us_ said:
daddydizzleman said:
lol you wanna go back to stock?
Ok then, well look around for the PD15IMG.zip for 2.3.4 then put it on your sd card at the root, and then go into bootloader again.
Click to expand...
Click to collapse
aiit thanks.i would try it n get back to u tomorrow.downloading it right away.
Click to expand...
Click to collapse
daddydizzleman said:
N_otori0us_ said:
aiit thanks.i would try it n get back to u tomorrow.downloading it right away.
Click to expand...
Click to collapse
Ok, make sure you get the right one. 2.3.4
Click to expand...
Click to collapse
crazydrummer95 said:
Hey guys, about a week or two ago, I went to a T-Mobile store to upgrade to 2.3.4. I have been looking into rooting and loading CM7, but im not sure how to do it and what is the best way. I was thinking about doing it with ADB, but im just too chicken to try it. I can't afford to break this phone, so i have to be really careful. If you have any other better ideas as to how I could root 2.3.4, that would be awesome. Also, if you have found any way to unbrick it if it gets bricked somehow in the process, that would be great too. I am an experienced hacker, and am working on starting to develop apps for Android and Apple. Thanks guys, I really need your help.
Click to expand...
Click to collapse
Rooting is easy and safe i rooted mine last week and i don't brick my baby... Just take a giant step to follow the information carefully and read the pdf it helped me too.. And adb is easy to use just takes time.
Sent from my myTouch 4G
Perm Rooted
S-OFF
CM 10
using xda app-developers app