I'm a nooobie. I tried rooting my phone using the Evo Universal Root, and i didn't read the instructions. I went right to the video and did the same thing the video told me to do. But my phone ended up getting semi bricked. I can access the bootloader, but i don't know what to do from there. I think my SD is also messed up. Someone Please Help!!!!!! What should I do?
If you can still access bootloader, try to get back to stock. Here's an unroot thread with a PC36IMG.zip.
http://forum.xda-developers.com/showthread.php?t=780141&highlight=Unroot
The first time I tried to root my phone, it corrupted my sdcard and I had to get a new one. Try testing it in another device and see if it can still be read (ideally you have a microsd to sd adapter and a sd port on your computer). If it can be read on a different device, you might just have to reformat it (this erases all the data on the card, so save the data elsewhere if possible/if you care). If it can't be read by multiple devices, it's probably corrupted and you'll have to get a new one.
After you unroot it, if you still want to root your phone, you might want to try the unrevoked method (unrevoked.com). It's super easy and works really well (it's what I used after the first root method I tried failed). They don't provide instructions on the website, but you can find them here. Read the instructions first this time, there are a couple of things you have to do before you begin.
You didnt read the instructions? it took me a week of reading before i was even comfortable enough to try it. i reccomend you read as much as possible on the subject, I mean you see what can happen if you dont!
You'll need to install the version of htc sync that is in the instructions and then restart the script from the screen with the red triangle. It should be able to finish once you do that.
Sent from my PC36100 using XDA Premium App
Related
I was trying to redo Toast's part 1 method for root and when I flashed the PC36IMG.zip, it suddenly stopped, the screen flashed, it showed the status again, but then failed. Now whenever I try to flash a PC36IMG.zip, it loads fine, but then shows "Checking PC36IMG.zip..." After that, it takes me back to the menu, without giving me the option to flash. This is really frustrating, and I can't seem to fix it. I tried running the RUU but got a bootloader incompatible error. Please help!
What version do you have 1.3xxx or 1.47. xxx? If you have 1.47 you wil need the newer ones to root then run toast method.
Sent from my PC36100 using XDA App
Just a little heads up, ask the MOD to move this to Q & A so you don't get flamed.
does it flash the "checking sdcard for PC36...." and then go back to the bootloader? If so, you may want to assure PC36IMG.zip is on your SDCard and that it's formatted as fat32.
Sorry, wasn't sure if this should be a development or Q&A question. Mods please move. Thanks afflaq, that is the problem I'm having. I'll try reformatting the sd card and see if that helps. I just can't figure it out. Its almost like something broke in the bootloader. Anyways, I'll try to reformat and try again.
Tried a different SD card and formatted it. Still has the exact same problem. I think my HBoot is messed up. Does anyone know how I can fix it without using the PC36IMG.zip method?
Is it actually named pc36img.zip or just pc36img? If you have the .zip it won't read it. Not sure if this is your problem but troubleshooting here.
Huoter is a flame
churchwin88 said:
Is it actually named pc36img.zip or just pc36img? If you have the .zip it won't read it. Not sure if this is your problem but troubleshooting here.
Click to expand...
Click to collapse
Its pc36img.zip. I can check and make sure its not zip.zip, but I'm pretty sure it isn't. It loads, so it must have the right name, but then it says checking and after a few seconds just stops. My phone is having some major issues lately, and since I can't seem to use the PC36IMG method, does anyone know where I can pick up the latest RUU? The older one won't work, so I need the newest one even though I'll lose root. This is a freaking nightmare!
Ok, I tried the latest RUU and everything went through. I'll go follow the instructions to root it again and hopefully I'll be able to get everything working again.
Ok, I used quickroot and everything seems fine. Even loads the PC36IMG.zip's correctly now. Thanks for everyone's help. Hopefully this thread will help someone else who gets a bad bootloader.
So I've googled around for the answers, but I still haven't found anything yet.
So, here it goes.
Recently, without me making any major changes to my MyTouch3G Slide, it turned off, then turned back on and wouldn't move forward from the white T-Mobile Mytouch 3G Slide boot screen.
I was rooted using the latest SlideMeRoot image. I've booted into the bootloader and tried restoring a "clean" image, but no luck there. I can't boot into recovery.
I also tried trying to find some spot where I could use ADB to see what's going on, but I knew that was a long shot to begin with :/
Any help guys?
Probably should start off with more details on what exactly you have done to your phone firstly .... Overclocked kernel? Firerat patch? etc?
What was the last thing you did to the phone before it rebooted or attempted to.
Nextly your leaving yourself wide open asking a question or even stating your problem in the developer section.. Shoulda asked it in the Q&A section...
I would simply try putting the phone back to stock/unrooted status using the stock ESPRIMG thread floating around here somewhere...
Did not overclock kernel, nor apply the firerat patch.
The last thing I did on it... was move a video onto the SD card.
Yeah, I thought I put it in the Q&A forum, but I guess not. Forgive me, I'm working on about an hour of sleep.
If any Mods see this, feel free to move it.
I've tried applying three different ESPRIMG.zips (they all had different file sizes) and all of them have the exact same problem. To unroot, I think I need to push some stuff to the phone, which I can't do right now. Any more suggestions?
Thanks in advance.
Wonder if that video corrupted your sdcard..
Did you have a2sd setup?
[UNROOT] (ROM) Factory Rom..Champion build Used for Unrooting If you need to at any Point!! - eugene_373 - http://forum.xda-developers.com/showthread.php?t=713507
SD card is fine, threw it in my old G1 and it took without a hitch.
Yeah, I had A2SD setup.
I can't do that unroot method, can't access adb.
Unless you can somehow get to it from fastboot?
Dunno...
Anything else?
Do you have amon RA recovery or clockwork? Try the one you don't have and see if that one works
Sent from my T-Mobile myTouch 3G Slide using XDA App
newsoundwave said:
SD card is fine, threw it in my old G1 and it took without a hitch.
Yeah, I had A2SD setup.
I can't do that unroot method, can't access adb.
Unless you can somehow get to it from fastboot?
Dunno...
Anything else?
Click to expand...
Click to collapse
Try putting the ESPRIMG onto the SD via the G1 when it is connected?
Moved to Q&A. Please don't post question threads in Development.
acejoker: can't access recovery either way. to get to recovery, you gotta go through the splash screen, which still isn't working
fermunkey: did that. That's how I got I was able to try three different recovery images. None of them worked.
rolfd: hehe, thanks.
Anyone got some last resort ideas?
I have heard of the advantages of S-OFF and would like to do it. However i have also heard of the risks of bricking my phone permanently. Anyone has any ideas how big is the risk? As in percentage?
I have no idea how accurate this is, but I saw someone mention a figure of about 0.4% failure rate.
Just a reminder - no idea how accurate this is - don't come looking me up if yours does happen to go bad.
Anyway, is there a particular reason you want to S-OFF? Perhaps you don't actually need to which avoids the risk in the first place.
Anyone else than the AlphaRev team giving failure rates is just guessing. And i doubt that even AlphaRev knows. I believe failure rate of the process is next to nothing, but the incapability from the user is what causes bricks. If you know what you are getting in to and follow the procedure without doing stupid things there is no realistic risk.
However there is just the bad luck, which at least once happened, where someone's computer crashed during the procedure.
Still keep in mind: You are the only one responsible for your phone, no one else.
what he said ^
User errors like loose usb cable that gets knocked durring the process
or pc crash. Ive S-OFF'd 2 desires and done similar stuff to a HD2 and
never had any problems. Been worried sick each time but everything went
smooth.
Just make sure the usb cable fits tight if youre going to do it. Both mine and
my friends HTC cable slip out by just brushing past it. I use a samsung cable.
Besides what @TheGhost1233 and @esk02k said, you should pay attention to the file you are downloading and use an MD5 tool to check the sum of your downloaded file against the one specified in the thread / site (you don't want to be flashing a corrupted file). And only do a flash after you have fully charged your battery
Hi all
Aplha Rev S-off, Amon Ra recovery Htc Desire 2.2
I just installed miui rom update over miui.19 r1 and my phone stopped working and it is showing sim card error, I tried 3-4 different sims and non of them are working. another problem is it stopped recognising the sd card same i tried 2 others but no luck
please can you help me as i have back up the sd card so can not restore as well as its not recognising my card.
any tips or tricks please, as i can not go to htc customcare as i have already voided my warrenty.
i tried using different sd card when i tried to do nand backup on new card just to check if its appear on system then it showed to start backing up then
Error: Run @[email protected] via adb
and if i tried to upload backup file flash zip from sd card in recovery then it is saying E: can’t mount /sdcard
I have backups of past around 3 different backups , but they are on my cards and my phone is unable to detect sd card so can not go further.
Is there any other way to do restore on phone using backup files, if its not detecting sd card
2) I checked my sim problem as well, sometimes it shows me the arial symbol for network , but when i try to call it shows me the error ” Mobile network not available”
really annoyed as this is my primary phone.
if you/anyone else got an idea, most welcome
Is there any way I can install the latest update without sd card????
please help me and do reply, i know its not nice to see problems n no one is happy to sortout, but i will really appreciate it.
thanks
Raj
rajverma3135 said:
thanks
Raj
Click to expand...
Click to collapse
No idea how you got the idea to post this here but whatever.
Sound like a USB brick. If you are still rooted try this and skip step 1 else this thread might have some useful info for you.
If you have more question do it in another thread since it's completely off topic here.
Lol I just wanna change stuff like splash screen and such.
Sent from my HTC Desire using XDA App
go for it, just make sure you have a good pooter, usb lead and charge your battery up full, im glad i took the plunge, my desire now runs a rom from a desire HD and i have 2gb internal memory lol
So, I don't really post on forums because I'm pretty tech-savvy, but I have a big problem that I can't fix, and I can usually fix everything (thanks to you guys!)
This morning, my incredible acted up as I was checking an e-mail and it froze, so I decided to battery pull because restarting my phone didn't work. (Note, my incredible has been running VERY solidly on a CM7.1 nightly). As I tried to boot up the phone again, it would stay on the white HTC Incredible screen. When I rebooted into recovery thru HBOOT, i realized that there was an error mounting something, like recovery_log, or something like that (i didn't mind this because I thought I knew what I was doing), but I tried restoring my old nandroid backup that was working well, but it didn't work. It said it couldn't format /data or something... It ended up staying on the white HTC incredible screen. So, I wiped data/cache like 10 times, and dalvik cache as well and tried re-flashing a clean install of cm7.1 stable, but didn't work again - led me straight to the white Incredible screen. So, installing a fresh rom AND restoring a solid backup didn't work... so...
I found the RUU 2.3 stock rom on the development forums, and tried to install that like I do with the radios (PB31IMG.zip) through HBOOT, but no cigar. It did go PASSED the white screen, but boot loops at the Droid eye.
So, I thought I'd find a different stock img, and found the 2.2 official OTA .zip and installed it the same way, but got the exact same result (boot loops, forever).
Any suggestions? I can't think of anything else.... I feel like my phone is bricked, but I didn't do anything to make that happen.
I feel like something happened that made me not able to format the /data, and stuff. I even formatted my SDcard in case it was the problem.
Any help is appreciated. Thanks!
Load the RUU onto a different fat32 sd card and see if you are able to boot.
Sent from my ADR6300 using XDA Premium App
i'll try that and give an update. thanks for the reply!
*update* no luck. same thing happens. i tried on three different sdcards formatted fat32...
Can you factory reset and flash a ROM from a different sd than the one you were using? Description sounds like bad sd, and AOSP roms interact with the sd on boot. If original (CM 7) sd is toast, it'll never boot, hence different sd card and prefably RUU
Sent from my ADR6300 using XDA Premium App
I had this happen once where no matter what rom i flashed all i got was bootloops. I had to get the stock froyo ruu.exe that you run from your pc and install it that way. Then once installed boot up and go to settings/sd & phone storage and do a factory reset from there. This factory reset is a true reset as it wipes out vzw programing also. After reset folow on screen steps to reactivate your phone, you can skip the rest of the setup. Once thats done your good to go just flash clockwork or amon ra recovery and then flash what ever rom you want. No guarantees but it worked for me.
NOTE: This assumes you are s-off, if your not after flashing the ruu you will have to use unrevoked to regain root and s-off again.
You can also try wiping /system and /boot.
*token post to get my post count high enough to ask for help in the hacking section, dumb rule btw. FAIL*
Mine is now stuck in a continuous boot as well. It's not rooted and have no idea how to fix it.
I see instructions in this thread but they mean nothing to someone who doesn't know what the abbreviations stand for or how to go about the commands required.
sl4m said:
*token post to get my post count high enough to ask for help in the hacking section, dumb rule btw. FAIL*
Mine is now stuck in a continuous boot as well. It's not rooted and have no idea how to fix it.
I see instructions in this thread but they mean nothing to someone who doesn't know what the abbreviations stand for or how to go about the commands required.
Click to expand...
Click to collapse
if you are non root. you will need to download the RUU.exe for 2.2 and install if from you pc.
http://androidforums.com/htc-droid-...mplest-instructions-ever-windows-xp-only.html
follow that and your phone will be back to the day you got it out of the box.
All the recommendations prior to Synisterwolf's post require root.
Some of the "abbreviations" are detailed in the Droid Incredible Development section. If you head over there you can read up on a beginners guide to root terms and helpful links in one of the top four threads namely:
If You're New to Modding/Rooting, Read This First! (Updated 08/05/10)
I will say though:
CM7.1 = CyanogenMod 7.1 (this is a rom)
OTA = Over The Air
2.2 = Froyo (Android software version 2.2)
RUU = basically refers to a file that people use to revert back to the Droid Incredible's pre-root status. Although there are additional steps as well.
SlimSnoopOS said:
All the recommendations prior to Synisterwolf's post require root.
Some of the "abbreviations" are detailed in the Droid Incredible Development section. If you head over there you can read up on a beginners guide to root terms and helpful links in one of the top four threads namely:
If You're New to Modding/Rooting, Read This First! (Updated 08/05/10)
I will say though:
CM7.1 = CyanogenMod 7.1 (this is a rom)
OTA = Over The Air
2.2 = Froyo (Android software version 2.2)
RUU = basically refers to a file that people use to revert back to the Droid Incredible's pre-root status. Although there are additional steps as well.
Click to expand...
Click to collapse
RUU = ROM Update Utility
no luck, I installed the program on my XP machine, but the app can't connect to the phone.
The phone literally keeps rebooting over and over.
sl4m said:
no luck, I installed the program on my XP machine, but the app can't connect to the phone.
The phone literally keeps rebooting over and over.
Click to expand...
Click to collapse
Then its gotta be a hardware failure.
Sent from my sexy assistant. (AMOLED HTC Incredible)
wow... what a bummer. thanks for the help anyway, it's much appreciated.
sl4m said:
no luck, I installed the program on my XP machine, but the app can't connect to the phone.
The phone literally keeps rebooting over and over.
Click to expand...
Click to collapse
Does it give any specific error code when it says it can't connect to the phone?
Someone correct me if I'm wrong but don't you have to have HTC sync installed on your pc to use an ruu.exe? Do you have that installed?
Sent from my ADR6300 using xda premium
I'll try it again to verify the code, I'm pretty sure it was "170"
sl4m said:
*token post to get my post count high enough to ask for help in the hacking section, dumb rule btw. FAIL*
Mine is now stuck in a continuous boot as well. It's not rooted and have no idea how to fix it.
I see instructions in this thread but they mean nothing to someone who doesn't know what the abbreviations stand for or how to go about the commands required.
Click to expand...
Click to collapse
I had this issue the first time i rooted my phone and attempted to put on a ROM, and i resolved it when i found this post to get back to stock. I also used this to fix a problem where my phone had a black screen with a line through it on booting to recovery or attempting to do a nandroid back up:
droidforums.net/forum/droid-incredible-hacks/95406-how-correctly-unroot-incredible.html
All i did was basically use the PB31IMG Method without turning s=on, ( i had stock radio and still have 7.28 )
1) download that PB31IMG.zip and drop it on the root of your sd card ( it has to be named ( PB31IMG.zip ) so make use you have file extensions showing on your PC.
2) boot to hboot and and let see the file and install it
3) used unrevoked ( remove sd card ) to aquire root again.
idk if this helps, but this seems to get me out of the few weird situations i had
sl4m said:
I'll try it again to verify the code, I'm pretty sure it was "170"
Click to expand...
Click to collapse
Check this out to fix your 170 error.
http://androidforums.com/incredible...170-171-solution-windows-7-a.html#post1472468
This low key happened to me and I booted in to HBOOT and went to clear storage and it did its thing and booted up, from there I had to activate it then I was set!
Sent from my ADR6300 using XDA App
=D
Sent from sweet snacks off tapatalk.
Not sure how to start this...
first off, i'm pretty sure my phone now has a fried eMMC chip, but in reality, i don't really know...
the reason i say i think it's fried is because no matter what method i try to flash anything to my phone with...it simply won't do it...most fastboot commands will not work anymore, my computer won't load the devise anymore so no adb commands, bootloader fails everything when trying to flash a stock rom and gets hung up updating the radio_v2....i've tried running official RUU's but it keeps telling me my phone has less then 30% battery life, wich is simply false. and i can't get into my recovery without it crashing the phone and not letting me turn it back on (till battery pull).
i went onto the #g2root and #xda-devs channels on the freenode server in mIRC, and had talked to a couple people there who also think i probably fried the eMMC chip (making it impossible to write or read anything from the phone), but again...i'm really going on word of mouth rather then first hand knowledge here.
but again today, i ran into yet another possible solution and i just want to know if i should bother trying or if i have a chance.
http://forum.xda-developers.com/showthread.php?t=1314629 is the thread, but i think this is for a desire s, so i suppose my question would be...would this method still work if i just used the right files or, again, am i screwed?
i have an HTC Desire Z that i got from Bell in Canada. it has gotten an OTA firmware update, and does not have root or s-off
if i remember right, everything is still stock, completely. minus the now possibly fried eMMC chip lol
thank you in advance and i will try to edit this post as neccessary so as to update any needed info.
please ask me questions as to what i have done and i will try my best to let you know. i know i had followed probably too many guides for rooting with too many methods lol next time, xda-dev's wiki guide, and that's it!
[edit:] i just found this too...lemme know if this helps..... http://forum.xda-developers.com/showthread.php?t=1284196
[edit:] i do know that when i go into my recovery, it does say those things (e: can't mount cache, blah blah) but it crash's out and doesn't actually get me into the recovery console. if so i would be able to envoke some adb commands and just finish this, but that's adding to the issue really...not being able to get into my recovery.
i feel with you.
it happend for me just today morning.
got my desire z on thursday, installed usual apps.
it started to freeze in random app installations. the last softreset threw it into a boot loop with the same problems you stated above.
you can get pre formated desire z emmc's for around 30 - 40 euro i think. but soldering them on your own requires some skill and tools since their contacs are below and not on the side.
this accident threw me back to my old htc touch diamond (with windows mobile 6.1 D: )