Related
Wow, it doesn't seem like I've only been a member for just over 3 months because I've learned so much since I first joined back in July...
XperiaX10iUser said:
Hi.
I've just bought an Xperia X10i, which was a T-Mobile handset and had firmware version R1FA014. I took to the net as soon as I got it home with the aim of debranding it, and followed this guide - forums.se-nse.net/topic/49076-sony-ericsson-xperia-x10-debranding-tutorial/? to step 5.
So I ran the "repair" option which went fine, but when that had completed and I tried steps 6 to 13, the first problem I encountered was the files in my db folder were totally different to the screen shot in the guide. I put them in size order anyway and renamed the two files and copied and replaced them, and tried running the update again, but it came up with an error about my internet connection (even though it was fine), so wouldn't run again.
Having checked the phone I noticed it had updated to firmware version R2BA023, so thought the debranding had been successful, until I was laid in bed setting the alarm to discover I still had T-Mobile tones and a T-Mobile homepage.
So after googling tonight, I've discovered "rooting", if someone could please explain what that actually is it would be much appreciated, as googling only leads me to guides on how to do it, but not what it actually is, and I have a couple of questions I hope someone can answer for me about the guide in this thread...
1. Are the files in the first post all I require or are there newer ones I should download?
2. I have downloaded SEUS, but I deleted the db folder for SEPCC whilst attempting to get the the steps in the first guide to work, should I uninstall and reinstall SEPPC before attempting the steps in this guide?
3. Is the "market fix" actually required after following this guide?
4. Some people have mentioned they have had issues trying the steps in this guide, is that mainly due to user error or is there a chance that it doesn't always work the first time?
I apologise for the long post, but any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
...and thought I would mark my thousandth post to show what a newb I was when I first joined. I still learn new stuff pretty much everyday just by coming and reading threads posted here and other sections of XDA, although the X10 boards is where I spend most of my time.
So thanks to all that have, and continue to contribute to XDA.
XperiaX10iUser
Smart man lol
Here was my situation: when trying to boot the phone, it would go to the splash screen for a few seconds, then go to a black screen and vibrate 5 times. Had to pull the battery to escape. However, when booting after a battery pull with the charger in it booted just fine, but with no sd card recognition or usb/adb functionality. A factory reset and both htc's and verizon's tech support didn't fix it at all. I had this problem and there seemed to be no good guide on how to fix it so I decided to gather all the right sources in one place.
The reason it's messed up comes from the usb problem, which is why plugging it in lets it boot sometimes. So, contrary to all of tech support, fixing the usb is all you need to do to get it working same as usual again. I've outlined the steps below in the way I think makes the most sense, but read all of what I wrote to understand what you're doing before you start. The links are the specific instructions for each piece written by people smarter than me. I only take credit for figuring out what I needed to do and bringing all of their minds together in one place.
The Process
First thing is to see if you can get it booted. Best bet is to take out the battery and charger, hold down the power button for 10 seconds, then connect the charger and battery and boot. If you can't do that then your only option would be to try some fastboot adb trickery (which is over my head) or flash the stock rom in hboot from http://www.droidforums.net/forum/droid-incredible-hacks/95406-how-correctly-unroot-incredible.html. Note which radio you have (listed in settings -> about phone somewhere or on top of hboot) to get the right file. If you can get it booted then move to the next step.
To fix the sd card and usb go to http://forum.xda-developers.com/showthread.php?t=695243.
Fastboot is in the tools folder of the android sdk, not platform-tools like adb. To get the drivers working go to http://www.flexjunk.com/2010/05/01/installing-htc-incredible-android-sd-drivers/
UPDATE: To clarify: fastboot is a completely separate (although closely related) piece of software from adb. If you do not have "fastboot.exe", download it from http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/ and follow the instructions there. Or, you can just download the full sdk from google which should include adb and fastboot. I recommend the second option, but my hard drive can take the hit. (thanks BonzTM)
UPDATE: If you get an error saying "The Program can't start because AdbWinApi.dll is missing from your computer" you need to copy that file from platform-tools to tools, then it should work (thanks Jester1614).
If you had to reflash and lost root download z4root from http://forum.xda-developers.com/showthread.php?t=833953 and do a temporary root to be able to run the commands to fix the usb.
Once the sd card and usb are fixed then it should reboot with or without the charger plugged in. Now your phone is stable and will work with unrevoked again and you should be good to go!
Disclaimer
Note: This is what I experienced with my amoled incredible; in no way do I take responsibility for anything you do. If you try to blame me for bricking your phone I will enjoy a hearty laugh while salting my soup with your tears.
Worked great for me and saved me from the hassle of needing a new phone.
THANK YOU!
goblue13579 said:
here was my situation: When trying to boot the phone, it would go to the splash screen for a few seconds, then go to a black screen and vibrate 5 times. Had to pull the battery to escape. However, when booting after a battery pull with the charger in it booted just fine, but with no sd card recognition or usb/adb functionality. A factory reset and both htc's and verizon's tech support didn't fix it at all. I had this problem and there seemed to be no good guide on how to fix it so i decided to gather all the right sources in one place.
The reason it's messed up comes from the usb problem, which is why plugging it in lets it boot sometimes. So, contrary to all of tech support, fixing the usb is all you need to do to get it working same as usual again. I've outlined the steps below in the way i think makes the most sense, but read all of what i wrote to understand what you're doing before you start. The links are the specific instructions for each piece written by people smarter than me. I only take credit for figuring out what i needed to do and bringing all of their minds together in one place.
the process
first thing is to see if you can get it booted. Best bet is to take out the battery and charger, hold down the power button for 10 seconds, then connect the charger and battery and boot. If you can't do that then your only option would be to try some fastboot adb trickery (which is over my head) or flash the stock rom in hboot from http://www.droidforums.net/forum/droid-incredible-hacks/95406-how-correctly-unroot-incredible.html. Note which radio you have (listed in settings -> about phone somewhere or on top of hboot) to get the right file. If you can get it booted then move to the next step.
To fix the sd card and usb go to http://forum.xda-developers.com/showthread.php?t=695243.
Fastboot is in the tools folder of the android sdk, not platform-tools like adb. To get the drivers working go to http://www.flexjunk.com/2010/05/01/installing-htc-incredible-android-sd-drivers/
if you had to reflash and lost root download z4root from http://forum.xda-developers.com/showthread.php?t=833953 and do a temporary root to be able to run the commands to fix the usb.
Once the sd card and usb are fixed then it should reboot with or without the charger plugged in. Now your phone is stable and will work with unrevoked again and you should be good to go!
disclaimer
note: This is what i experienced with my amoled incredible; in no way do i take responsibility for anything you do. If you try to blame me for bricking your phone i will enjoy a hearty laugh while salting my soup with your tears.
Click to expand...
Click to collapse
u saved my life/phone i love u son
Perfect Solution!
Thanks Thanks Thanks +1
So...question: Does this mean if you had to reflash and are currently unrooted, that you have to wait for z4root to show up in the market. Because it seems there is no way to root aside from that, and without root no usb, and no usb no adb
sofocused715 said:
So...question: Does this mean if you had to reflash and are currently unrooted, that you have to wait for z4root to show up in the market. Because it seems there is no way to root aside from that, and without root no usb, and no usb no adb
Click to expand...
Click to collapse
Actually you can download it from the link I provided in my post to the xda page for it (http://forum.xda-developers.com/showthread.php?t=833953). Scroll to the bottom of the first post and in the attached files there is a version that works. That's what I did, and then you can run the usb fixing commands. Then it's just reboot, re-root, and restore.
Hope this helps.
This thread needs more attention.
This needs to be stickied(sp?) and maybe added to the Development section where it would most likely be looked for first.
If I've helped you, hit the thanks button!
As you can see by my post count I can't put anything anywhere, so if someone wants to move it feel free.
goblue13579 said:
As you can see by my post count I can't put anything anywhere, so if someone wants to move it feel free.
Click to expand...
Click to collapse
I re-worded your OP and posted it on another forum. I did credit you though. You are now famous.
Cool, thanks!
I wish I would have known this back in March when this happened to me! But then again my phone was S-ON and to get the USB fix to work you said you need root so I might have still been SOL.
brando56894 said:
I wish I would have known this back in March when this happened to me! But then again my phone was S-ON and to get the USB fix to work you said you need root so I might have still been SOL.
Click to expand...
Click to collapse
That is what the z4 root is for. You dont need s-off, just root. The things are going to s-on by themselves when something is trying to write to the misc, thus the misc brick. PITA brick if ya ask me.
doug piston said:
That is what the z4 root is for. You dont need s-off, just root. The things are going to s-on by themselves when something is trying to write to the misc, thus the misc brick. PITA brick if ya ask me.
Click to expand...
Click to collapse
Glad yall were able to make something of this. This is gonna save some people since warranties are finally running out. Hey Doug, I seen your thread over on AF. You did a very good job of writing that up.
Oh and thanks for the tiny little peace of credit, heh. Glad I could help 'point' the late and great dougpiston in the right direction on something, lol
wildstang83 said:
Glad yall were able to make something of this. This is gonna save some people since warranties are finally running out. Hey Doug, I seen your thread over on AF. You did a very good job of writing that up.
Oh and thanks for the tiny little peace of credit, heh. Glad I could help 'point' the late and great dougpiston in the right direction on something, lol
Click to expand...
Click to collapse
Late and great is an over statement. I am just a user like most here. I appreciate you taking the time to reply to my PM. I have been out of the Inc game for some time now so a little direction was very helpful.
Like I said I knew what had to be done but ADB kept ****ting itself, as soon as I read the OP and to use a terminal emulator I slammed my head on my desk.
So simple, I was spending all my time trying to get ADB to run that the idea of the usb being borked hadn't even crossed my mine.
This thread really does deserve more credit and to OP good on ya son. Well done.
Thank you goblue13579, wildstang83 and Doug Piston! My phone is totally functional once again.
Odd timing how the problem happened only 2 days ago on my phone, and coincidentally, a fix was hashed out in the same time period after all this time of it being unfixable.
I owe you all a beer! Thanks again!
doug piston said:
Late and great is an over statement. I am just a user like most here. I appreciate you taking the time to reply to my PM. I have been out of the Inc game for some time now so a little direction was very helpful.
Like I said I knew what had to be done but ADB kept ****ting itself, as soon as I read the OP and to use a terminal emulator I slammed my head on my desk.
So simple, I was spending all my time trying to get ADB to run that the idea of the usb being borked hadn't even crossed my mine.
This thread really does deserve more credit and to OP good on ya son. Well done.
Click to expand...
Click to collapse
Yea bud, even I use adb so much that I keep forgetting that there's emulators to use. Its just one of those things we never think about.
Even though it was really more dumb luck and excessive googling that got me to this solution, thanks! I'm glad my compilation has helped so many people. And honestly, it's the least I can do for all the help and goodies I've gotten from these forums and developers.
Happy modding!
What if the devise isn't rooted?
Let the phone sit for an hour with the battery out. Put the battery in after that, should be good
Sent from my 2.3.5 Incredible Obsession
Evening all,
I have a DHD that is stuck in HBOOT/FASTBOOT, or at least that and the stock recovery program is all I can get to.
I tried an AAHK, and it basically tried to do a downgrade and has left the phone with no data, still at s-on, and I can't find an operator RUU(three uk) to flash it back to a useable state.
Is there a three RUU available?
I'm running around in circles as I can't make a gold card, due to not having another DHD available to retrieve the MMC2. All I need is a goldcard and then I can flash a WWE, but I cant find anywhere to make one without the phone or a similar one.
I dont think it turned the microsd properly into a gc, before it tried to downgrade. Is their anyway I can test to see if the memory card has been successfully goldcarded?
Any help would be greatly appreciated.
Thanks
James
This might help
http://forum.xda-developers.com/showthread.php?p=29203392
Sent from a dream.
Teichopsia said:
This might help
http://forum.xda-developers.com/showthread.php?p=29203392
Sent from a dream.
Click to expand...
Click to collapse
Mine has a lot of those symptoms to be honest. If I vol down/power to get to Hboot, it sits there with no keys being able to be pressed, just highlighted blue FASTBOOT and not even checking for files on memory card
If I just turn it on, it sits at the three splash screen, which i assume is the equivalent of the HTC one for branded phones.
I have now turned it on and left it on as per those linked threads, in the hopes the sd is a proper gold card and it is just slow. Fingers crossed.
Thanks for the pointer
James
There are many threads for your problem, do a search, check what it might be. I believe in the second page of that link has another link, check it out. Find out what is wrong before trying anything. If you have any questions, let us know what are the symptoms, what you have done and so on.
Sent from a dream.
Teichopsia said:
There are many threads for your problem, do a search, check what it might be. I believe in the second page of that link has another link, check it out. Find out what is wrong before trying anything. If you have any questions, let us know what are the symptoms, what you have done and so on.
Sent from a dream.
Click to expand...
Click to collapse
Well what I did, was follow the AAHK instructions, cleaned up my environment etc, went through the install. When it asked to do the downgrade, I said yes, then it asked about wiping and was I sure, so I said yes. It then rebooted the phone and it is now as it is. I pulled the battery and tried vol-down/power, which brings up HBOOT, but it doesnt let me do anything, vol keys and power do not work and it doesnt start looking for image files.
From that thread, it was mentioned it just could be going very slow, and people have just left it overnight. This is what I have done now, and will see if it has accessed the files on the memory card and downgraded properly in the morning.
Thanks
James
Have you tried looking for the RUU here?
Last I remember when aahk downgrades, you will be asked to reboot to basic recovery twice
Panic over, thankfully! Not my phone, you see!
It was so easy to root my S2 and the X10 before that, and the iP3G before that(and custom winmo, and nokia etc etc), I said give it to me, i'll sort you out with some ICS rom action.
Then it all went wrong as explained in my previous posts.
2 days later, i finally found the H3G RUU I needed to get an system on it. Silly branded phones. Took 4 hours to download as it was on a throttled download service(my 100MB leased line usually eats 300MB in seconds, but not this time)
So long story short, into FASTBOOT USB, ran the RUU and it completed and put froyo on the phone, and as a happy coincidence it was at a level that didn't need a downgrade, so AAHK ran through like a trooper, busybox installed and hey presto, ENG S-OFF. IceColdSandwich installed through cwm and one happy mate, who then proceeded to ring his wife and tell her to rent a film, as he would be tinkering with the phone all night lol
It was getting to the point I was going to have to give him my S2, and as I've just taken possession of a Sony SmartWatch, I didn't want to do that!!
Thank for everyone's help and pointers, not sure what went wrong the first time(probably a memory card/incompatibility/goldcard problem), but all sorted now.
James
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 had jwr66v rooted with superSU twrp cmw 6.035 or whast ever.
now i have updated to ******y and i tried to flash a ROM in in CWM but it did nothing. at all. i rebooted into recovery only to get a droid on his back with a red ! coming out his belly. um problem here. i opened super Su and it said i need to reroot because i have installed 4.3
how can i reroot if i can't access recovery.
tried using toolkit to reroot (un root to stock first) but it froze now having this problem: post #455
http://forum.xda-developers.com/showthread.php?p=45162727&posted=1#post45162727
anyone?
Just flash recovery from cmd/terminal using fastboot.
Sent from my Nexus 7 using xda app-developers app
never used it. details would be nice.
Want details? There are stickies and tutorials for a reason. Lemme guess, you used a toolkit to root it the first time?
Sent from my Galaxy Nexus
sure I'll follow one of your tutorials. most of the time written as if we know every detail about android development jargon. oh and most tuts have missing details that usually means moderate technical knowledge people have to make assumptions when following those instructions. another issue I'm funding with following "stickies" is because there are so many different ways to update and so many different versions of root tools made by many different clever developers. sometimes they don't all work together. most of the time i will follow some developers half thrown together set of instructions only to have to redo the instructions 3 of 4 times because of the reasons all mentioned above.
short response to your reply. i followed a simple tutorial put up by a developer and most likely used a tool kit. now i have issues. rather then spend countless hours hunting for else who has had the same problem and actually posted it, i decided to ask the question so someone like yourself that enjoys spending hours each night balls deep in code can give me a simple link or basic set of instructions so i can have some relief.
Adb and fastboot. Those are the only tools you need to use.
If I had been in your shoes, I would have done a bit of googling on the term 'fastboot recovery'
I don't know why some people make this so hard. This is a developer site, if you don't want to learn, you shouldn't be here. Considering all this **** is literally spelled out for you with step by step documentation, it doesn't make any sense to click that 'new thread' button when this issue is so common.
Sent from my Galaxy Nexus
yeah googling more is what got me following half arse instructions and wading hours of my day. so which part of your detailed instructions would have led you ( if in my shoes) to Google fast boot recovery?
well I have now downloaded the latest tool kit so i can un root. then I'm going to hunt through countless posts and try find which is the best way to root and install cm10.x hopefully next time their is an update i won't have to reroot just to get all my little root access apps back.
ps this is the trouble shoot q&a section not the developers only section. hence why i posted here.
Welcome to xda-DEVELOPERS.com.
Maybe you missed that part. The domain name isn't xda-hold-lazy-asses-hand-and-make-their-device-cool.com
You are expected to read, comprehend, and take initiative to learn. Asking for a hand holding session is not the way.
If you would bother reading the stickies, you would see how easy it is to flash recovery. There is a tutorial in the damn stickies that literally walks you through the process.
Hint: every goddamn nexus gets rooted and recovery flash the same way regardless of what version of android you are on
I don't know how much more plain and simple we could be here.
Fastboot flash recovery name of recovery.IMG
I mean wtf how could you NOT find that?
Sent from my Galaxy Nexus
since you are being so lazy, and i have obviously had enough to drink tonight:
http://forum.xda-developers.com/showthread.php?t=1907796
http://forum.xda-developers.com/showthread.php?t=2150661
http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro
http://forum.xda-developers.com/showthread.php?t=2072732
http://forum.xda-developers.com/showthread.php?t=2175086
READ!
heres another hint. you need a recovery made SPECIFICALLY for your device 'tilapia'
so..... thanks for the pointless rant, after re read many guides and how tos, also wasting a saturday. still cant get the bootloader to update from version 4.13 (read post 1 again) not even using fastboot. Also read post #455 http://forum.xda-developers.com/showthread.php?p=45162727&posted=1#post45162727
aza510 said:
so..... thanks for the pointless rant, after re read many guides and how tos, also wasting a saturday. still cant get the bootloader to update from version 4.13 (read post 1 again) not even using fastboot. Also read post #455 http://forum.xda-developers.com/showthread.php?p=45162727&posted=1#post45162727
Click to expand...
Click to collapse
Use stock images for Android 4.2 and not 4.3 to avoid that error.
But i'm not sure why you want to flash anything else than recovery? Do you want to get it back to pure stock?