Related
I recently had to give up my rooted preordered Incredible for a refurb due to heat issues and reboot (loop) issues. For those looking for a guide as to what to do if you have to return your phone to Verizon and want to unroot. I welcome any comments to update/add to this information:
1) Make a NANDROID Backup if you want to simply port it over to your new phone
2) Mount your phone as DISK DRIVE
3) Walk the directories and delete any cached thumbnails of web sites you have visited
4) Copy any pictures you want to keep which were saved on the phone
5) Reboot into ClockWork recovery
6) Wipe the Dalvik Cache
7) Wipe the Data/Factory Reset
8) Go back
9) Wipe Data (main menu)
10) Power Down your phone
11) Remove your SD Card
12) Download one of the RUU's which are hosted around the web:
http://www.shipped-roms.com/shipped/Incredible/
13) Turn on your phone and plug it in to your USB
14) Run the RUU and let it do it's thing. When its done, so are you
15) If you have a screen protector, remember to remove it.
Any additions are welcome!
Yes it will revert everything back to normal, that's called an RUU btw
Cool
Anyone know if this also removes the more hidden data, such as the cached images of the web sites you have visited? In other words, if I run the RUU, is the phone ready to just be handed over?
if i root and uninstall some apps, will this restore my phone to stock and allow me to get all future HTC updates?
jdmba said:
Anyone know if this also removes the more hidden data, such as the cached images of the web sites you have visited? In other words, if I run the RUU, is the phone ready to just be handed over?
Click to expand...
Click to collapse
I don't think so, but it's easy enough to do a wipe and then apply the RUU (and hey, for the hell of it, you could wipe again).
Steps?
[deleted ... first post updated]
I'm pretty sure the RUU will completely wipe your phone. However, you can take giantcrazy's advice and wipe before running the RUU.
One more try
[deleted ... first post updated]
Ok, here is what you want to do.
there would be two things you need to un do before sending them back this phone.
make sure it says S-ON.
and then make sure you have stock recovery.
If you have these two things, your gold bod.
Probably to noob to know any better
After going through a lot of threads this one seems appropriate. I am looking for how to go back to stock DI. After Unrevoked3, ota leak and unofficial froyo leak, my DI wont connect to VZW anymore, all out going calls are busy. Talked to my VZW guys, they are cool with me, tried to help nothin'. Today tried Unrevoked forever and official froyo leak, still no VZW connection. I looked into this a lot before I tried these mods I don't know what went wrong, I would not have been able to do this with out such easy tools as are provided today. "I NEED HELP" to get back to stock, "PLEASE". I have looked into SDK and Adb, as I have been lead to believe there is no way to return to 2.1 and the right radio without these tools. At this moment I have not been able to find clear enough explanations on how to use these tools, this is where I maybe over my head. I assume my radio is fried, I don't care if no "S on", I just need those obvious things; version, kernel, baseband, to be stock. Any help will be appreciated, big thanks for any suggestions
A Lex and Er said:
After going through a lot of threads this one seems appropriate. I am looking for how to go back to stock DI. After Unrevoked3, ota leak and unofficial froyo leak, my DI wont connect to VZW anymore, all out going calls are busy. Talked to my VZW guys, they are cool with me, tried to help nothin'. Today tried Unrevoked forever and official froyo leak, still no VZW connection. I looked into this a lot before I tried these mods I don't know what went wrong, I would not have been able to do this with out such easy tools as are provided today. "I NEED HELP" to get back to stock, "PLEASE". I have looked into SDK and Adb, as I have been lead to believe there is no way to return to 2.1 and the right radio without these tools. At this moment I have not been able to find clear enough explanations on how to use these tools, this is where I maybe over my head. I assume my radio is fried, I don't care if no "S on", I just need those obvious things; version, kernel, baseband, to be stock. Any help will be appreciated, thanks
Click to expand...
Click to collapse
Ok, there is so much here I will do my best.
number one, having s-on is just as important as having a radio thats either 2.15x or 1.x, now that the OTA 2.2 update is sending out, you can send the phone back with 2.2 and 2.15x radio.
what you need to make sure of, is two things, you have s-on,
and you have stock recovery.
ACD168 said:
Ok, there is so much here I will do my best.
number one, having s-on is just as important as having a radio thats either 2.15x or 1.x, now that the OTA 2.2 update is sending out, you can send the phone back with 2.2 and 2.15x radio.
what you need to make sure of, is two things, you have s-on,
and you have stock recovery.
Click to expand...
Click to collapse
Thank you, and really they wont know if the ota was pushed to me? I found the S on tool, I didn't know there was one, I had only read on about S off. I don't know how to find/replace stock recovery, I will start searching though. Much appreciation, my better half is not as thrilled about my learning experience as I am.
I already rooted and unrooted once, will I get stock recovery back after unrooting?
A Lex and Er said:
Thank you, and really they wont know if the ota was pushed to me? I found the S on tool, I didn't know there was one, I had only read on about S off. I don't know how to find/replace stock recovery, I will start searching though. Much appreciation, my better half is as thrilled about my learning experience as I am.
Click to expand...
Click to collapse
Your welcome, I'm happy to see you are learning so quickly. S-on is very helpful for those warranty returns of the phone.
Verizon has no idea whether or not you got the ota, or better yet what version you have or if you are rooted, ect.
If you tell me what your hboot it, radio, software version, s-on or s-off, if rooted or not, and if you have the stock recovery or clockwork and I will try and guide you to where you want to be..
if you need help getting to the stock recovery this must mean you are rooted, and this can be achieved by downgrading the phone by un-rooting, I'd suggest running s-off while you are rooted, then
androidforums.com/incredible-all-things-root/99828-video-howto-unroot-incredible-downgrading.html
sorry can't post links yet,
to help you un-root and get that stock recovery back.
A Lex and Er said:
I already rooted and unrooted once, will I get stock recovery back after unrooting?
Click to expand...
Click to collapse
To find out real fast if you have the stock recovery or clockwork-mod recovery, boot into HBOOT, (power off phone, hold vol down and power til screen turns on) and then vol down to select recovery and push the power button I think to select and then if you get a red triangle that means stock recovery.
Also need to return phone
I just got off with Asurion and they are over nighting a replacement. I had rooted my phone, installed some root only apps like wireless tethering and set cpu, removed some bloat like CityID and Tweet/Peep, and changed the boot animation. No custom ROM or radio update.
Then I wanted to get the OTA update so I applied s-off and flashed back to stock recovery.
So what do I need to do to return this phone. I know I will need to apply s-on. Then should I flash a stock 2.1 or just revert the changes I made to boot animation, restore the bloatware, and remove the root apps? Do I need to remove any other files that go with being root?
Thanks.........MM
ACD168 said:
Your welcome, I'm happy to see you are learning so quickly. S-on is very helpful for those warranty returns of the phone.
Verizon has no idea whether or not you got the ota, or better yet what version you have or if you are rooted, ect.
If you tell me what your hboot it, radio, software version, s-on or s-off, if rooted or not, and if you have the stock recovery or clockwork and I will try and guide you to where you want to be..
if you need help getting to the stock recovery this must mean you are rooted, and this can be achieved by downgrading the phone by un-rooting, I'd suggest running s-off while you are rooted, then
androidforums.com/incredible-all-things-root/99828-video-howto-unroot-incredible-downgrading.html
sorry can't post links yet,
to help you un-root and get that stock recovery back.
Click to expand...
Click to collapse
Hello,
I wanted to thank you again for the help this last weekend. I apologize for not returning for more of the help you offered me. My wife only has every other weekend off and we have an 18mo. old son, both of whom deserved my time more than my DI. I love my DI but it wasn't giving me much love.
Although VZW isn't always the nicest to my pocket book, I have never been taken care of as well by any other provider(s) employees, thank you. As I mentioned in my first post, my VZW guys are cool with me. Yesterday I went into the store and the manager offered to help me. He managed to reconnect my DI to the network but no 3g's. He believes my problem is just a coincidence because he had another customer with a similar problem over the weekend, with no mod's. Still I need to exchange my DI, it doesn't look like 3g's is going to turn on.
My real issue is still getting custom recovery off and stock recovery back on, then unrooting will be a breeze. The videos you lead me to are one of the sources I have been working with, however to reverse the leaked ota, Downgrade leaked ota video, requires SDK and adb knowledge, this is where I am noob. At this time my VZW manager who is in school for programing is attempting to help me (he has a over clocked Palm Pre Plus, 1Ghz), this is very cool of him, well beyond what is expected. (I am in no way encouraging anyone to rely on their VZW employees for this kind of help, this is a unique situation, I have been building a relationship with my VZW guys for two years+, not all VZW employees have a clue about mod's, and mod's technically void the warranty) I am hoping to learn enough about these tools, SDK and adb, to help myself before the next time, and I will hopefully be gaining some of this knowledge from my friends at my VZW store soon. I will also be looking forward to the help I receive from fine people such as yourself and people in this community in future endeavors.
I will stop basically hijacking this thread now
Thanks to all of the people who support these community's, with out whom many of us would never get our foot in the door. Much appreciation to ACD168 for being there to help me.
Take the time and learn to do it right the first time.
A Lex and Er said:
Hello,
I wanted to thank you again for the help this last weekend. I apologize for not returning for more of the help you offered me. My wife only has every other weekend off and we have an 18mo. old son, both of whom deserved my time more than my DI. I love my DI but it wasn't giving me much love.
Although VZW isn't always the nicest to my pocket book, I have never been taken care of as well by any other provider(s) employees, thank you. As I mentioned in my first post, my VZW guys are cool with me. Yesterday I went into the store and the manager offered to help me. He managed to reconnect my DI to the network but no 3g's. He believes my problem is just a coincidence because he had another customer with a similar problem over the weekend, with no mod's. Still I need to exchange my DI, it doesn't look like 3g's is going to turn on.
My real issue is still getting custom recovery off and stock recovery back on, then unrooting will be a breeze. The videos you lead me to are one of the sources I have been working with, however to reverse the leaked ota, Downgrade leaked ota video, requires SDK and adb knowledge, this is where I am noob. At this time my VZW manager who is in school for programing is attempting to help me (he has a over clocked Palm Pre Plus, 1Ghz), this is very cool of him, well beyond what is expected. (I am in no way encouraging anyone to rely on their VZW employees for this kind of help, this is a unique situation, I have been building a relationship with my VZW guys for two years+, not all VZW employees have a clue about mod's, and mod's technically void the warranty) I am hoping to learn enough about these tools, SDK and adb, to help myself before the next time, and I will hopefully be gaining some of this knowledge from my friends at my VZW store soon. I will also be looking forward to the help I receive from fine people such as yourself and people in this community in future endeavors.
I will stop basically hijacking this thread now
Thanks to all of the people who support these community's, with out whom many of us would never get our foot in the door. Much appreciation to ACD168 for being there to help me.
Take the time and learn to do it right the first time.
Click to expand...
Click to collapse
First off, you are very welcome my friend, anything I can do to help do hesitate to ask!, and your not hijacking any thread brother, that's what these threads are for!!!
Thats real cool of the VZW employees!!
adb and sdk isnt that difficult I can help you!!
Read my post about warranty exchange.
I know alot of people are "better safe than sorry" mentality. but I have returned 2 phones that were fully rooted, updated, s-off running custom roms and I had no issues. in fact ive never had an issue using warranty exchange. ive exchanged phones that I broke (like broke.. with pieces coming off). I just call and tell the operator lady my phone doesnt work, i dont know why.. it was just working earlier and now it wont turn on.. they send me a new phone and I send back the broken one and everyone is happy.
They only confirm that the numbers on the phone match your account. Not the reasons you are sending it Back. the warhouse guy that opens your box isnt the same guy you talked to, nor do they have information about your phone call to the tech. They simply open the box, scan the numbers and move on.
dont stress to much about it
Great info here
Thanks to every one of you on this thread. I am finally breaking free from WinMo and getting Dinc after a lot of research. I like Verizon but hate the bloatware they pack onto Androids and all the other phones, so I will be fiddleing with ROMs. If I screw up I am looking here first to see how to get it back to stock so I can get my new one with the insurance coverage.
Everytime I get to serouosly looking around these forums I learn great new stuff. I will donate to the XDA someday soon!
Okay. so im a noob. Just need to ask. What do you guys mean by stock recovery? I just rooted my phone but need to unroot to send it in for work at Verizon. Could you help me out?
Hello everyone,
I have been on this site for sometime, always reading and waiting to be able to take the plunge into all the fun.
I am a Bell subscriber, and have enjoyed my phone till this point, but now I would like to be able to get everything back to normal.
A couple months back, I messed up my Atrix and decided to flash the following sbf file onto it, 4.2.11.MB860.Retail.en.FR.
It has been running good since then.
Now I want to be able to get back to the Bell software and be able to take the OTA updates, and have my car dock working again.
I have read until I am blue in the face, and there is so much jumping around from thread to thread, I am really lost when it comes to start this.
My phone is currently rooted using Gingerbreak 1.20, I have backed up everything, and am willing to do anything to this phone to accomplish this. I am not to worried about it, as I have purchased the extended warranty on it, so I hope I am covered.
My questions are:
Do I need to unlock my phone to proceed to the next step?
if so, I use ihop-bell?
I install CWM, I currently use the one with Rom-Manager
I download the Bell 2.2.2. Gobstopper? Install it?
I have the current version of RSD lite installed on my computer
then I ????? this is where I get lost again.
I know some of you are saying read the steps posted, but it seems they all lead to different pages and I kinda got lost in the process. Would someone point me to a step-by-step that could help me please?
Sorry for inconveniencing any of you, but it is greatly appreciated
Thank you
Fred
Hello, xda-developers,
I have a myTouch 4G that was updated to the 2.3.4 Gingerbread software and wanted to root it. In order to do so, after many research, it states that there is no root for the 2.3.4 Gingerbread software and for it to be rooted you'll have to downgrade it.
The reason why I wanted to root it is because I am having a problem with the WIFI connectivity in my home and was wondering if it will fix it. Same reason why I update it to the 2.3.4 Gingerbread software in the first place. The myTouch 4G that I have will "RARELY" connect to my wireless router in my home but for some reason it doesn't fail me when connected to other wireless routers outside of my home even when having the same router. But this is now not the problem.
As you can read, the title says it all. My problem now is that I just soft bricked my myTouch 4G after a downgrade that I followed here: http://forum.xda-developers.com/showthread.php?t=1178912# Like the noob always say when something goes or went wrong, "Boohoo, I don't know what I did wrong. Someone, please, help me." But I THINK I know what I did or went wrong.
I followed the guide strict and carefully hoping I don't brick it but then I said to myself, "It's a 99.9% chance I won't, I think... what can possibly go wrong?" Everything went well. I did everything it says and once the update bar fills up to the top, BAM! It hits the "T-Mobile myTouch 4G" boot screen. I was happy. Very happy because I felt accomplished and one step closer to excitingly freeing my phone. But my hopes went down when it stayed like that for hours on end. I pulled the battery out and reboot it and nothing was fixed. Although it was stuck, I still can access the bootloader. I pulled out the battery again and boot it to the bootloader and re-updated it again and nothing was fixed. I yanked out the battery one last time and deleted the PD15IMG.zip file from the SD card to keep it from asking to update everytime I boot it to the bootloader so I can factory reset it but, still, that didn't help.
Like I said. I think I know what I did or went wrong. Examine the guide. The "Gaining Temp Root" part I did right. The "Changing Version Number to Allow Downgrade" I did correct and the results on the command prompt came out the way it stated it should come out. THEN! I yanked out the battery to reboot it after that. When I've done so I continued to the next procedure and everything went how it says it should go but, instead of the end results, I got it stuck on the "T-Mobile myTouch 4G" boot screen after the update. I think that's where I messed up. When I yanked out the battery to reboot it after the "Changing Version Number to Allow Downgrade" part. I believe it kicked it out from root. It is a temp root by the way and I read it somewhere that said, "Once you're rooted you CAN downgrade it." Something like that which made me think it wasn't rooted after that reboot and the downgrade wasn't a success. I also have two other guesses in which I think soft bricked the phone. I either have a bad eMMC-boot or the PD15IMG.zip was bad. These are my thoughts in what went wrong. I'm asking for your help. So can you help me find the solution to this problem?
Thank you very much in advance for your time and effort into reading this and helping me out. I really appreciate it.
-Victor​
P.S. Here's the information on the myTouch 4G's bootloader:
GLACIER PVT SHIP S-ON
HBOOT-0.89.0005
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
Apr 14 2011,13:18:22
Again, Thank you.
wow, same thing happened to me.
You could try updating it back up to the 2.3.4 RUU. If that works, nothing lost at least.
You used a wrong PD15IMG, most probably.
If you have used the correct one, your bootloader would be 0.86.0000, but it isn't.
Please re-download the correct PD15IMG and try again. When it works, if it throws any messages - write them here, so someone will be able to help you. If you see "Fail-PU" - your phone is dead.
Your mistake might have been removing the battery instead of typing "adb reboot bootloader". Yanking the battery off a working phone can destroy its eMMC. If that's what happened to you - well, you can replace your phone under warranty and follow the instructions better next time.
It was definitely the part where you yanked out your battery. You lost temp root then. Why you did it, not sure. But it's already been done so Let's not linger.
Have you tried starting over from step one?
Sent from my HTC Glacier using XDA App
You used a wrong Rom to downgrade or it is corrupted during download.
Download the official 2.2.1 rom, put it to the root of your sdcard, and try to update.
The original bootloader is 0.86.0000
You can download it here
Rename it to PD15IMG.zip before updating.
Do what he said
Do what the last guy said and rename the image and flashing.
Here is what has happened, you were probably installing a signed downgrade to a previous version. Either you got the wrong file, your download was corrupt (THANKS TO CHROME), or you didn't clear your cache dalvik needs to be clear if you run a different kernel. The main cause of hanging at the bootscreen is the incorrect cache either regular or dalvik. Thats what I've noticed from threads and just in general.
You don't appear to be running clockworkmod recovery. If you are going to mess with the system, DO IT ALL THE WAY! Don't get confused with this one... if you are planning to write radios, flash updates, or do anything YOU WILL NEED ROOT. This is because something could go wrong and you could be locked out. If you aren't willing to commit to basic root privileges, do not attempt to downgrade. Either go all the way, or don't go at all. That's just some friendly advice cause people will make the misconception if they just downgrade thats fine, but getting root is more dangerous... not true! If you have root, you can actually gain control of the phone and restore even a 'broken' one.
ROOT is mostly gained from within the phone in the operating system. You use an APP to gain root privileges. Once you get root, you need to get SU a program to grant privileges to programs that request them. Then you need to get clockworkmod rom manager so you can flash a recovery (internet and market access is required unless you can install from the .apk and use adb). ONCE YOU HAVE THAT RECOVERY you can downgrade, upgrade, flash, flex, backup, restore all with a simple push of a button, no expertise required!!
You can even revert to stock easier when you have root.
Once you get that recovery installed then look for ways to turn s-off and unlock your sim so you don't have to worrry about stuff.
And remember, they might not honor your replacement phone if you hack or modify it... but if you lose the phone they will replace it for you.
Big Thanks For the Help!
Hello, xda-developers,
Thank you, all, for your help! I've figured out the problem.
It was because of the PD15IMG.zip file. It was a bad one and I figured it out by downloading another one BUT, instead of downloading it from the same site I got it from, I downloaded it from a different site. I've barely figured this out and I could have fixed this problem way earlier if I had checked back my post.
Big thanks, again, to you guys for taking your time and helping me figure out this problem. It has been a month since I've been "Android-less" and now I am going to treasure it more than usual and I can not lie... I miss its awesomeness.
My phone is now back and it is officially perm-rooted! Love this phone more than ever with all the things it can do now. Rocking this phone out now with the Virtuous Unity rom and it blows... me... away!
-Victor​
Well..... at last you figured it out.....Iam happy for you....Try Virtuous Unity 2.39 you will really love it.
By the way, where did you get the PD15IMG.zip file???? Can you post the link, so that it will be easy for others with similar problem.
Thanks! You're right, I am trying out Virtuous Unity 2.39 right now and I love it. I was actually looking for an android "bone-stock" gingerbread rom but I can't seem to find one without the customization. Then I bumped into this one. They say sense 3.0 were only made to work on dual-core phones... they were wrong. I really love this rom and I'm sticking to it. Until I find a stock gingerbread rom that has been perfected for the myTouch 4G. You know, the one without the customization.
Oh! Here's the link where I got the radio (PD15IMG.zip) from: www1240.megaupload.com/files/89ce9e2eeb86bb659eceb64baa356c4b/PD15IMG.zip
Since I'm a new member of the xda-developers forum, I couldn't post a link. So, instead, here's the address.
So have you tried the link in my post? Did it work for you?
The link for the PD15IMG.zip radio? Nope. I went onto googling it and finding one myself. The link for the stock myTouch 4G 2.3.4 rom? Nope. Not a big fan of the myTouch 4G's overlay.
Hi guys,
I'm an idiot.That's nothing new, but here it looks that I'm double one I tried to root my wife's HTC Desire Z, but without success. I tried to use CWM Super-Su v0.96, HTC Quick Root and few others. But I'm not able to do it.
Can you please explain me somebody step-by-step, what I have to download exactly, what to copy where, what to run, to do and so on.... For example HTC Quick Root - after initial reboot to recovery mode I had to run 1st option "phone reboot" or something like that, but before reboot that I received some error message regarding rights to folder structure....So I wasn't able to install Superuser or SuperSU. I also tried to run Superuser.apk but of cousre I have no rights to System/xbin to copy there su file...
Her Android ver is 2.3.3 , HTC Sense ver 2.1 , SW number: 2.42.405.4
PS: During this process I need my data untouched in the phone (pictures, contacts, SMS). I don't want to upgrade Android ver, I just need root access to install Titanium Backup and delete 90% of useless apps.
Thank you very much,
idiot Rado77 :cyclops:
PS: I'm adding answer also here. As you can see below, there are few ways how to do the same thing, but for example in my case worked only this way:
http://wiki.cyanogenmod.com/wiki/HTC_Desire_Z:_Firmware_Downgrade_(Gingerbread)
http://wiki.cyanogenmod.com/wiki/HTC_Desire_Z:_Rooting
Try this guide:
http://forum.xda-developers.com/showthread.php?t=835777
Thank you very much Marquin. I spent appr. 6 hours and read whole internet, but I couldn't root that crazy phone I used almost every type of rooting method, but I allways receive some error message regarding rights, or it repeatedly freezes on some concrete step... I don't underdstand because I sucessfuly rooted my Xperia U and LG P690 during 15 minutes. But this HTC really shocked me. I'm an idiot, I said that...
The only way to truley root your phone will be following the xda wiki, the cyanogen wiki, or strawmetals PDF guide. Don't use any other method or you will have issues, some could brick your phone some could just make things more difficult later.
You will need to downgrade first, yes this will wipe your phone. You can use apps like sms backup + to save call logs and messages, link account to google to store contacts, have pictures on sd so you don't loose them.
Sent from my Desire Z using xda premium
Ahaaaaaa, so it looks that downgrade is necessary part of root process. Thank you very much for info. I think that this could be the right way: http://forum.xda-developers.com/showthread.php?t=905261
When I was rooting my DZ I used that:
http://wiki.cyanogenmod.com/wiki/HTC_Desire_Z:_Firmware_Downgrade_(Gingerbread)
for downgrading...
Finally I used pages on WIKI:
http://wiki.cyanogenmod.com/wiki/HTC_Desire_Z:_Firmware_Downgrade_(Gingerbread)
http://wiki.cyanogenmod.com/wiki/HTC_Desire_Z:_Rooting
and I can say that rooting of this phone was the heaviest what I did :laugh: I had to chat with some guy named GUHL who helps me with whole process step-by-step, he checked outputs wiht error messages in my cmd and as final he gaves me the link with beautifull 2.3 Sense with available root.
Ufffff...that was really interesting way!
PS: I'll never root any HTC phone !!!!
Hey all!
I finally decided to root my phone after having it for about two years or so. I don't know why I never bothered, but decided to do so today. It was a bit of a hassle, even with the instructions that I found (the same ones I found in this thread), but I finally got it to work! I just flashed my first rom (Gen.Y VisionX R2 ) and so far I'm liking it, but I don't really know what's out there in terms of what I can do (customizing options, speed/performance, overclocking, and all that).
But anyways, great links in this thread
without downgrading to 2.2 Froyo, there's no way to Root desire z 2.3.3, if you are already on 2.2 and you can continue rooting procedure. make sure to follow the instructions correctly and (copy past the command do not type it>> IMPORTANT) :cowboy
Ahmedrzvi
Recently got my vision on 2.3.3 and already soff . Now I'm not sure what to do.
Which root method could be the best option now
The rooting page on XDA links to the PDFs that have step by step guides, but the tools that are used/referenced are no longer available for download. This is a step above the Cyan page which is just plain gone.
Can anyone point to currently active steps in rooting the phone? I have it downgraded, I just need to root it.
Abdullah Dot said:
Recently got my vision on 2.3.3 and already soff . Now I'm not sure what to do.
Which root method could be the best option now
Click to expand...
Click to collapse
Im in a similar situation, bought a Desire Z from Ebay, already has bootloader unlocked and s-ff (was like this when I got it). Unfortunately, I upgraded to Gingerbread before I realised this was an issue with rooting.
Have tried a few different guides, but it appears as though the fr3yo file is no longer available.
thank you im rooted
Hi.
I purchase desire z from ebay. From the first time i have some issues with the phone. Touchscreen was pressing by itself etc. I asked for help and told me that was digitizer fault. Before that i thought that may be they didn't flash the ROM corectly so i returned to stock froyo but i don't think i'm rooted.
I gave it for repair and after some days they gave me the phone back and told me that it is ok. To tell you then truth the problem it wasn't so intense so take it from there. I turn it on, played al little and turn it of. I made a charge for 5 hours. After that device turn on, go to menu and after some seconds reboot and reboot and reboot.
I have tried to install CWM with this method but i can't. At first step says "sending file" but after i got message "failed"
I know here are the most experienced guys that will try to suggest me a solution before sell it for parts.
Thank you very much
Antonis
Changing ROM
Hello,
I rooted my DZ a few weeks ago, without any issue; I did everything which was mentioned in the instructions, so I suppose I have S-off, rooting, and whatever. Of course I don't remember anything at all.
Now I'd like to change ROM, mainly because, in spite of using CM 7.2, which is widely recognized as one of the fastest, I am having several issues with performance. I read around that a "superwipe" may be useful, yet I don't remember having done it last time. So, my question is: what are the steps I should perform? I should maybe mention that I have ClockworkMod Recovery 3.0.2.4 installed.
I hope this is a correct 3D to post into, if it isn't please take into account that I am new in this forum :angel:
All links you should need are in here
http://forum.xda-developers.com/showthread.php?p=43195539
Sent from my Nexus 4 using xda premium
So, I've now LITERALLY spent days on this. Don't tell me "read the FAQ/Stickies", because I already did :good:
I'm not a noob when it comes to rooting/installing ROMs on phones. I would estimate that I've done it on about 50 different models...but this one has me up a freakin tree. So, I rooted it and installed 4EXT recovery. I applied the Energy Rom on it, rebooted....just hangs at the MyTouch4g screen. Left it for 20 minutes....nothing.
Tried a different Kernel, same thing.
Tried 4 different roms (GB and ICS) and different Kernels....no dice.
So, I tried taking it back to stock. I downloaded the 2.3.4 update from the "you think you're bricked" thread. Renamed it and loaded it to the SD card. The blue bar progresses all the way through....then it just goes to the HBOOT screen like nothing happened.
I really need to get this thing back up and working (it's a phone from a wholesale lot that I got off ebay) so that I can sell it. It's losing value every day that it sits here
Any help from anyone, please?
Well, without knowing the exact steps you took for rooting it'll not be possible to help you. It's hard for me to understand how someone who "installed ROMs on approx.50 different devices" would require this explained.
Also, the only reason for the "return to stock" PD15IMG.ZIP to be read but not to proceed is the main_version being high. This is why a script (misc_version) is applied to allow downgrading. And if you searched, you'd definitely see the references to it.
A wild guess of mine - you unlocked the bootloader instead of gaining S-OFF, and didn't flash the kernel through fastboot? And/or didn't wipe data?