While installing ARHD 10.2 in CWM recovery Everything flashed fine and when i clicked reboot device I was promted to fix root. I clicked yes and then my device went into a bootloop. Is there a way to fix this without a computer so i can get back into recovery or do i have to use computer? I wont have access to my computer for several hours and the computer im on i cannot use for anything more than internet browsing. Also, if i do have to use a computer to correct this issue, what is the easiest way. I am using a mac.
try to reflash without fixing root and make sure your wiping cache and davlik
skinsfanbdh said:
try to reflash without fixing root and make sure your wiping cache and davlik
Click to expand...
Click to collapse
I would, but I can't access recovery. When I try the CWM symbol flashes and then phone enters bootloop. This is the problem. If I could access recovery then I'd be fine and could either restore Nandroid or reflash ARHD.
I also see an option for 'Reboot Bootloader' in the fastboot menu. What does this do?
Pure+ said:
I would, but I can't access recovery. When I try the CWM symbol flashes and then phone enters bootloop. This is the problem. If I could access recovery then I'd be fine and could either restore Nandroid or reflash ARHD.
I also see an option for 'Reboot Bootloader' in the fastboot menu. What does this do?
Click to expand...
Click to collapse
just reboots to where you are now. you need a computer to open a cmd. type fastboot erase cache
skinsfanbdh said:
just reboots to where you are now. you need a computer to open a cmd. type fastboot erase cache
Click to expand...
Click to collapse
Alright. Do I need to use my computer that has the Fastboot and adb files or can I use any computer and simply type that into a command prompt?
Pure+ said:
Alright. Do I need to use my computer that has the Fastboot and adb files or can I use any computer and simply type that into a command prompt?
Click to expand...
Click to collapse
when you plug your phone in it installs the drivers but you might need your computer
skinsfanbdh said:
when you plug your phone in it installs the drivers but you might need your computer
Click to expand...
Click to collapse
Alright. Thanks for all the help.
I'm sorry I know you're having trouble but please don't make 3-4 threads try to keep it to one maybe 2 if absolutely necessary
Sent from my HTC One using Tapatalk 4 Beta
Nick281051 said:
I'm sorry I know you're having trouble but please don't make 3-4 threads try to keep it to one maybe 2 if absolutely necessary
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
I'm sorry... What?
I have only made 3 threads recently and all were for very different reasons. And I only made them after extensively searching for the answers else where. If you would prefer not to help because you feel I'm some how doing something wrong then that is perfectly fine.
Sent from the Pure Ninja Black HTC One running ARHD 10.2
Pure+ said:
I'm sorry... What?
I have only made 3 threads recently and all were for very different reasons. And I only made them after extensively searching for the answers else where. If you would prefer not to help because you feel I'm some how doing something wrong then that is perfectly fine.
Sent from the Pure Ninja Black HTC One running ARHD 10.2
Click to expand...
Click to collapse
Except the rule is one thread, because then it clutters up the rest of the forum is all
Sent from my HTC One using Tapatalk 4 Beta
Nick281051 said:
Except the rule is one thread, because then it clutters up the rest of the forum is all
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
Actually the rule is-
5. Post a message only once.
As a large forum we don't need unnecessary clutter, You're free to edit your message as you like, so if you do not receive an answer revisit your message and see if you can describe your problem better. Not everyone is online at the same time, it might take a while before you receive an answer.
Click to expand...
Click to collapse
as in only one thread per question/issue. I had 3 separate question/issues and only made 1 thread for each. I have never made a duplicate thread and never intend to. I don't know if you simply interpreted the rule in a different way, but I am very positive that I am not breaking any rules here. I do thank you for your concern, however next time maybe you could voice it differently or simply send me a PM.
Pure+ said:
Actually the rule is- as in only one thread per question/issue. I had 3 separate question/issues and only made 1 thread for each. I have never made a duplicate thread and never intend to. I don't know if you simply interpreted the rule in a different way, but I am very positive that I am not breaking any rules here. I do thank you for your concern, however next time maybe you could voice it differently or simply send me a PM.
Click to expand...
Click to collapse
No it is generally accepted around here that you don't need to make three separate threads. And I don't see how I should voice it differently considering nothing I said was hostile in any form
Sent from my HTC One using Tapatalk 4 Beta
Nick281051 said:
No it is generally accepted around here that you don't need to make three separate threads. And I don't see how I should voice it differently considering nothing I said was hostile in any form
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
I never claimed that you said or did anything hostile. I simply said that you could have voiced it differently and then I continued to say next time you could simply send me a quick PM saying something like "Hey, I know your new here and having a little trouble with rooting and flashing, however we prefer that you only make one thread in which you can ask all your questions and issues that way it stays easy to navigate through the forums" I can tell you from personal experience that would have worked much better. All I'm asking now is that you realize this entire situation could been handled differently and gone in a different direction. I understand what your saying and next time I will try to remember your suggestion. Now if you could try to understand what I'm saying that would be awesome. Then we can forget this entire thing happened and continue to enjoy these forums and the purpose they serve.
Related
Now I want to start from scratch again. I would like to root and use a cleanrom.
I know how to do all this. However, what exactly do I need to delete from my computer? I still have all the files on here from the last time I rooted my rezound. But I want to start completely from scratch.
Thanks is advance
first, go to htc dev.com and unlock the device.
then download amon ra recovery and install
through cmd or cleanflash 1.0 tool from scott.
after installing, get su from advanced menu in recovery.
now you've been unlocked and rooted.
download the rom and kernel you want to install
then install using recovery.
Disagree. First test the speaker and telephone call quality. Then do some downloading or program updates and make sure the phone does not get too hot. Once you are sure you didn't get a lemon, then decide if you want to void the warranty.
Sent from my ADR6425LVW using xda premium
jdmba said:
Disagree. First test the speaker and telephone call quality. Then do some downloading or program updates and make sure the phone does not get too hot. Once you are sure you didn't get a lemon, then decide if you want to void the warranty.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
yeah i'm on my 2nd replacement so far. i make sure to give phones at least a week of standard usage before i decide to unlock/root.
I found that alot of the phones have poor speakers/overheat or have dead pixels :x.
jdmba said:
Disagree. First test the speaker and telephone call quality. Then do some downloading or program updates and make sure the phone does not get too hot. Once you are sure you didn't get a lemon, then decide if you want to void the warranty.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
the question was how to get cleanrom on the phone..
read before writing..
don't you think testing the phone has been done already?
qudwis said:
the question was how to get cleanrom on the phone..
read before writing..
don't you think testing the phone has been done already?
Click to expand...
Click to collapse
Verizon doesn't really check their phones. There are a ton of POS phones sent out as refurbs/CLNR.
qudwis said:
the question was how to get cleanrom on the phone..
read before writing..
don't you think testing the phone has been done already?
Click to expand...
Click to collapse
Nope, he didn't say you were wrong by the way. Just trying to make sure someone who might be excited about the new phone tests out the phone first. Great logic, so don't get offended.
KORM via the beast known as the Rezound.
putney1477 said:
Now I want to start from scratch again. I would like to root and use a cleanrom.
I know how to do all this. However, what exactly do I need to delete from my computer? I still have all the files on here from the last time I rooted my rezound. But I want to start completely from scratch.
Thanks is advance
Click to expand...
Click to collapse
qudwis said:
the question was how to get cleanrom on the phone..
read before writing..
Click to expand...
Click to collapse
No, that was not the question. Take your own "advice". I quoted the original question as well to make it easy for you.
txkorm said:
Nope, he didn't say you were wrong by the way.
Click to expand...
Click to collapse
Even though s/he was wrong. But I said it so we're covered. lol.
Back to the question, which was ...what exactly do I need to delete from my computer?
I would probably not use the nands from your old set up on your new phone. I don't know if there's a way to access files in them other than from restoring them, but if there isn't I'd say get rid of them.
Also, you don't want to restore data from a Titanium backup if it's to a different ROM, don't know if it matters if it's to a different phone. So you can definitely use them to restore apps but might want to not restore data in case it causes any issues.
You'll need to get a new unlock code so you can delete that unlock_code.bin file you got last time.
Not sure what else you would have on there that you are wondering about. The folder you set up for using fastboot/adb can stay and be used again.
feralicious said:
No, that was not the question. Take your own "advice". I quoted the original question as well to make it easy for you.
Even though s/he was wrong. But I said it so we're covered. lol.
Back to the question, which was ...what exactly do I need to delete from my computer?
I would probably not use the nands from your old set up on your new phone. I don't know if there's a way to access files in them other than from restoring them, but if there isn't I'd say get rid of them.
Also, you don't want to restore data from a Titanium backup if it's to a different ROM, don't know if it matters if it's to a different phone. So you can definitely use them to restore apps but might want to not restore data in case it causes any issues.
You'll need to get a new unlock code so you can delete that unlock_code.bin file you got last time.
Not sure what else you would have on there that you are wondering about. The folder you set up for using fastboot/adb can stay and be used again.
Click to expand...
Click to collapse
Thank you all for your help. I have tested the phone for a week now. Seems to be ok.
that was my question, about the adb and fasboot etc that's already on my computer.
I have no idea on my computer where my old unlock code is haha. Im.sure I will find it.
I can use the same drivers correct?
Thanks afaik for everyone's help. I appreciate it.
Sent from my ADR6425LVW using Tapatalk
You do realize that even if you "void" your warranty, its easy to still return it for a replacement. Just put in the stock ROM and stock recovery and re-lock and you're good to go. You don't even need to re-lock, Verizon doesn't check.
engsoccerfan said:
You do realize that even if you "void" your warranty, its easy to still return it for a replacement. Just put in the stock ROM and stock recovery and re-lock and you're good to go. You don't even need to re-lock, Verizon doesn't check.
Click to expand...
Click to collapse
She's already done that, believe me... we went through it together. lol.
putney... you can keep all the drivers and the whole fastboot/adb folder you have set up. That's just for your computer and not phone specific. Well, the drivers are HTC but you got the same phone so you're set.
No big deal on the Unlock_code.bin. If you end up with the old one and it doesn't work you can always generate a new one any time from what I've heard. I just keep mine in the fastboot/adb folder so it's always available. I also do that with Amon Ra. Then I don't have to go looking for them.
feralicious said:
She's already done that, believe me... we went through it together. lol.
putney... you can keep all the drivers and the whole fastboot/adb folder you have set up. That's just for your computer and not phone specific. Well, the drivers are HTC but you got the same phone so you're set.
No big deal on the Unlock_code.bin. If you end up with the old one and it doesn't work you can always generate a new one any time from what I've heard. I just keep mine in the fastboot/adb folder so it's always available. I also do that with Amon Ra. Then I don't have to go looking for them.
Click to expand...
Click to collapse
Thanks so much, again lol. You are awesome!
Sent from my Kindle Fire using Tapatalk
How do I reverse encryption on gtab10.1 lte vzw. I know it said you can't go back but is there like a root privelaged way?
OK I'm serious about the question.. can anyone help plz.
Sent from my Galaxy SII T-mobile using xda premium
I think the reason for encryption is that you cannot simply reverse it
Well, encryption exists so you can't get in, and since it's a mobile device, there's a reason to /not/ add a "backdoor" or "root override" to it.
Sorry bud. I might be mistaken (and I hope I am) but I don't think there's a way to "go around it"
Can't you just wipe the device?
Sent from my GT-N7000 using Tapatalk 2
RavenY2K3 said:
Can't you just wipe the device?
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I tried to wipe it. Just booted right back up. Even tried through recovery and cannot mount sd
Maybe you are able to wipe it with ODIN - I remember I have read something similar before, one guy claimed he regained access when he wiped it that way.
What about flashing replacement firmware if it's available? http://www.sammobile.com/firmware/
ultratek said:
How do I reverse encryption on gtab10.1 lte vzw. I know it said you can't go back but is there like a root privelaged way?
Click to expand...
Click to collapse
You can reverse this by performing a factory reset through the settings (settings>security>backup and reset)...It is stated clearly at the time you perform the encryption - don't you guys read before doing anything to your tabs? Anyway if you try to reset though recovery then I think the tab hangs. So odin is the only way. In the following thread someone claims he fixed it.
http://forum.xda-developers.com/showthread.php?t=1152623
Good luck!
Sent from my amazing 10.1 galaxy tab
What? Me worry?
Panos_dm said:
It is stated clearly at the time you perform the encryption - don't you guys read before doing anything to your tabs?
Click to expand...
Click to collapse
You mean -gasp- reading manuals? And BEFORE switching the thing on? Nah.
RTFM is only a last-resort-measure...
Part of the fun is reading the manual before first switching the thing on. You should have all the time while the first charge completes anyhow... But then again, this is a general flaw in humanity nowadays. Lacking Common Sense...
Ah well, flames all around now for speaking out in Jest...
Just_Another_N00b said:
You mean -gasp- reading manuals? And BEFORE switching the thing on? Nah.
RTFM is only a last-resort-measure...
Part of the fun is reading the manual before first switching the thing on. You should have all the time while the first charge completes anyhow... But then again, this is a general flaw in humanity nowadays. Lacking Common Sense...
Ah well, flames all around now for speaking out in Jest...
Click to expand...
Click to collapse
Yeah...that's one thing I'm saying....I like reading the manual and I believe that - either printed or in electronic form - a good and sufficient documentation is always critical and needed.
But in this case what I mean is that at the moment you choose the encryption option IN the settings, you get a warning message. Samsung wants to make sure that when you encrypt the device you have knowledge of all the risks involved.
Sent from my amazing 10.1 galaxy tab
Panos_dm said:
But in this case what I mean is that at the moment you choose the encryption option IN the settings, you get a warning message. Samsung wants to make sure that when you encrypt the device you have knowledge of all the risks involved.
Click to expand...
Click to collapse
Not only in the settings and in the manual do you get bold lettering warnings, most of the fora handling this subject warn clearly on the issue.
On the other hand, it is good to encrypt your device, just making it one-directional is kinda non-logic, compared to all other options/settings/behaviour of Android and tablets.
Therefore it would be simple to misinterpret or ignore the big bold-letter warnings.
Again: Common Sense is slowly going down the drain in humanity.
Just_Another_N00b said:
Not only in the settings and in the manual do you get bold lettering warnings, most of the fora handling this subject warn clearly on the issue.
On the other hand, it is good to encrypt your device, just making it one-directional is kinda non-logic, compared to all other options/settings/behaviour of Android and tablets.
Therefore it would be simple to misinterpret or ignore the big bold-letter warnings.
Again: Common Sense is slowly going down the drain in humanity.
Click to expand...
Click to collapse
I'm not sure what you mean by one-directional. The whole point of encrypting your device is to make it secure from third party people, correct? So in order to reverse it you have to ended a pin code. If the encryption was removed by recovery wipe it wouldn't be so "secure". Thus the decryption is possible only if you wipe from the settings, and it requires the code in order to do so. Now yes, it is possible apparently to remove it by odin flash but few people know that (yes, xdaers are "few" to the majority of users).
And, finally, I totally agree with you. Common Sense is not so "common"
Sent from my amazing 10.1 galaxy tab
You guys got a manual with yours? I bought mine refurbished and I didn't receive a manual
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
Panos_dm said:
You can reverse this by performing a factory reset through the settings (settings>security>backup and reset)...It is stated clearly at the time you perform the encryption - don't you guys read before doing anything to your tabs? Anyway if you try to reset though recovery then I think the tab hangs. So odin is the only way. In the following thread someone claims he fixed it.
http://forum.xda-developers.com/showthread.php?t=1152623
Good luck!
Sent from my amazing 10.1 galaxy tab
Click to expand...
Click to collapse
This did not work on my tab at all. The system reboots, appears to be installing something, but then goes to the password prompt and boots as if nothing had happened. Would appreciate it if anyone could provide some suggestions.
So after my battery ran out today I realized that Clockworkmod does not allow charging while the phone is off... This left me in a tricky situation where I could not charge my phone at all. I had seen others mention using another battery but I did not have one on hand. Here's how I replaced Clockworkmod with Amon-Ra to fix it (this also works for all recovery images that I know):
REQUIREMENTS:
-Computer with ADB
-Rezound with Clockworkmod or other faulty recovery
-Amon-Ra's recovery image (attached)
1) Unplug USB and remove battery
2) Put battery in
3) Plug USB into computer (with ADB installed)
4) Enter "adb devices" until you see your Rezound show up as recovery. During this time, the orange LED may either blink shortly first or be solid for a few seconds and then turn off. Once it turns off, it should be accessible over ADB.
5) Grab your amonra recovery img and use adb to copy to phone.
Example: adb push amon-ra-3.15.img /tmp/amon-ra-3.15.img
6) Flash the image to recovery.
Example: adb shell flash_image recovery /tmp/amon-ra-3.15.img
7) Reboot your phone (adb reboot) and repeat steps 1-3 (but this time using wall outlet)
8) Sit back and let Amon-Ra save your Rezound. Once your orange LED has been solid for over a minute, you should be good
Nice guide
Koush really needs to fix that problem or discontinue it for our phone
Sent from my Galaxy Nexus using Tapatalk 2
superchilpil said:
Nice guide
Koush really needs to fix that problem or discontinue it for our phone
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
It is discontinued. I don't even really know where to get it anymore lol.
Granted, I don't use CWM, but nice job.
con247 said:
It is discontinued. I don't even really know where to get it anymore lol.
Click to expand...
Click to collapse
Rom manager. Also he offers touch for pay (which is what I mistakenly purchased thinking it could mount the internal sd. Either way though I agree, it is not safe for the average root user even to have a recovery that doesn't allow charging even through a wall outlet. It should only list Amon-Ra's under alternate recovery.
Chyrux said:
Granted, I don't use CWM, but nice job.
Click to expand...
Click to collapse
Thanks, I know the average user is using Amon-Ra or TWRP but figured I'd put this here so we have a clear guide for getting out of this situation where some users may end up returning their phone to HTC (possibly getting charged after the fact)
con247 said:
It is discontinued. I don't even really know where to get it anymore lol.
Click to expand...
Click to collapse
Its odd, those same people who can't search to find out how to fix the problem, can find CWM
Sent from my Galaxy Nexus using Tapatalk 2
I'm fairly new to the Rezound. Came from the Nexus side because I wanted a more multimedia-friendly device (better external speaker/camera/same res). I bought mine pre-rooted and flashed to Clean, which was pretty nice - until I ran into this issue. I bought another battery from Verizon and hooked the other one up to an external charger. I figure it won't hurt to have two batteries anyway.
I know a ton of people have bad things to say about CWM but is this really the only issue? It flashes just fine, right? I ran a nandroid on what I have now and tried to install the latest leak, but I got a ton of reboots. Eventually reverted back to Clean. Either way, thanks for the writeup. Would have saved me a ton of stress over the weekend, hahaha.
Nice work djh816. this was the thing i have always feared lol. matter of fact, this is a HUGE weight lifted out of my mind. Thanks so much for this. keep up the good work
nice guide but i dont think anyone uses cwm anymore. still, thanks
I do. Haven't had issues. I just, if you can believe it, charge my battery before I do anything.
Sent from my ADR6425LVW using Tapatalk 2
Btw, I would change, just to be safe, but haven't seen instructions for doing so, and don't really want the drama that USUALLY comes from asking a question (can't always find what you are searching for).
Sent from my ADR6425LVW using Tapatalk 2
RED ZMAN said:
Btw, I would change, just to be safe, but haven't seen instructions for doing so, and don't really want the drama that USUALLY comes from asking a question (can't always find what you are searching for).
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
The OP of this thread are the instructions... Just do Steps 2-6.
Edit: or use hasoon2000's first AIO toolkit, which has AmonRa as a flash option (also another lingering source of CWM):
http://forum.xda-developers.com/showthread.php?p=22696442
RED ZMAN said:
Btw, I would change, just to be safe, but haven't seen instructions for doing so, and don't really want the drama that USUALLY comes from asking a question (can't always find what you are searching for).
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Haha I was fine as well with Clockworkmod Touch and had no clue it even had that problem until my battery finally drained all the way. Then I was SOL. But yea as he said, following those instructions simply replaces the recovery image. All your data will still be in tact (aside from your clockworkmod backups if you have them but Amon-Ra can read those too I think)
Yeah, I figured those instructions would work. You should advertise this as a how to swap between them also. There are others using CWM, and just not talking about it.
Thanks.
Sent from my ADR6425LVW using Tapatalk 2
I have an easier solution, while phone has been dead for 5-10 minutes, hold power button and as soon as screen flashes plug in the device. Works every time. I also have 3 batteries, 1 original, 2nd from my replacement from warranty, 3rd is extended. I don't ever even change batteries though.
Funny that people are still having/talking about this issue.
I remember when the issue first popped up on the Rezound and people were clueless. All kinds of theories as to the cause and solution.
I knew of the cause from a few phones back... CWM has a history of issues with charging while powered off. I learned of it from an initial release of CWM for a different phone would that when trying to charge with it powered off, would turn on the screen.
Easiest way is to run the command
adb reboot download
boom phone restarts...
I have had this modded version of CWM touch by someone else (I will let him say who he is just in case he does not want to take credit).
It is a modded version of CWM 5.8.1.4-Touch that solves the charging when off problem.
I can not support it but can assure you it works since I have been using it since the beginning of April. I do switch between this and AmonRa for testing my ROM but all my backups are with this.
Still need to copy the .hidenandroidprogress file from internal to external clockworkmod folder to solve the freeze problem when backing up or restoring.
Just install it just like any other recovery.
NOTE: If anyone want to take this and start another thread with it that is fine by me. I just don't have time which is why I never posted it before.
I ended up doing it through fastboot, as I'm a bit more familiar with that, but thanks for the notes and link. I'm now on Amon Ra.
Anything I need to know as a CWM user since, oh, the G1?
And do I need to worry about moving that file so backups work, like you did in CWM?
Thanks again.
Thanks man, this this is totally pimp, sent you a donation - get yourself some good beer!
Please help. Did the RegawMOD root (that thread should be removed, it could cause so much damage).
Got an error at very end of process. Accessed bootloader, it's Tampered and Unlocked. The phone is also worthless.
It cannot access the Sprint network, nor can it access data. When roaming on VZW's network, it shows nonsense processes in small text on the home screen, scrolling and appearing as procesess start.
It it destroyed or can it be repaired? Lectures about rooting after an OTA will be ignored, please keep this thread only filled with good stuff. Thanks wise people.
Did you try to run the ruu.you will lose root but its better than having a paper weight
Well your unlocked and have a custom recovery, so flash a Rom and find out
Sent from my EVO using Tapatalk 2
You probably should post this on the regawMOD root thread because it's a higher chance that the OP of the thread and author of the tool will reply to you.
atlgator said:
(that thread should be removed, it could cause so much damage).
Click to expand...
Click to collapse
No it shouldn't. It works, if you didn't read and did something you shouldn't then that's on you. I have personally used that method when I first got my phone with no issues. Did you take the OTA and THEN try to root? If so:
regaw_leinad said:
Successful in rooting all builds up to 1.13.651.1.
Click to expand...
Click to collapse
You should read the whole thread (or at least the first and last two pages) before you attempt something like that. Anyway, more info is needed to try and help you better. What error did you get? What small text does it display on the home screen?
atlgator said:
Please help. Did the RegawMOD root (that thread should be removed, it could cause so much damage).
Got an error at very end of process. Accessed bootloader, it's Tampered and Unlocked. The phone is also worthless.
It cannot access the Sprint network, nor can it access data. When roaming on VZW's network, it shows nonsense processes in small text on the home screen, scrolling and appearing as procesess start.
It it destroyed or can it be repaired? Lectures about rooting after an OTA will be ignored, please keep this thread only filled with good stuff. Thanks wise people.
Click to expand...
Click to collapse
yea it can cause damage if u dont have any idea what your doing... lol..
Racer Of All said:
You probably should post this on the regawMOD root thread because it's a higher chance that the OP of the thread and author of the tool will reply to you.
No it shouldn't. It works, if you didn't read and did something you shouldn't then that's on you. I have personally used that method when I first got my phone with no issues. Did you take the OTA and THEN try to root? If so:
You should read the whole thread (or at least the first and last two pages) before you attempt something like that. Anyway, more info is needed to try and help you better. What error did you get? What small text does it display on the home screen?
Click to expand...
Click to collapse
Read as much of the over 60 page thread as I could, I made a mistake. Forget the error, something about RW. The small text is process stuff life system_server, surfacefinger, com.android.phone, etc, scrolling on right side of screen, as the process starts/stops, I guess.
atlgator said:
Read as much of the over 60 page thread as I could, I made a mistake. Forget the error, something about RW. The small text is process stuff life system_server, surfacefinger, com.android.phone, etc, scrolling on right side of screen, as the process starts/stops, I guess.
Click to expand...
Click to collapse
The main question though, did you try to do this root after you did the OTA update?
Try and run the stock ruu from fastboot it should flash back to stock if u get er message download the PG... ZIP if all fails unlock boot loader from htcdev.com use commands to flash recovery and new radio then install Rom of your choice
Sent from my EVO using xda app-developers app
meezy2400 said:
Try and run the stock ruu from fastboot it should flash back to stock if u get er message download the PG... ZIP if all fails unlock boot loader from htcdev.com use commands to flash recovery and new radio then install Rom of your choice
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
When I connect the phone to my PC, the PC doesn't recognize it. How can I get a new ROM on it if the PC won't see it? And the phone can't download anything, data isn't working.
All HTC drivers are installed. Oy.
evo401 said:
yea it can cause damage if u dont have any idea what your doing... lol..
Click to expand...
Click to collapse
+10000000
Bwahahahaha
I have lost count of the threads that has emphasized that if you take the ota DO NOT try to root.
Take the SD card out. Use adapter for SD card in your PC to put a rom on it. Go into recovery and flash. (I'm assuming you have the adapter of course) Hope you get it working. Good luck
atlgator said:
When I connect the phone to my PC, the PC doesn't recognize it. How can I get a new ROM on it if the PC won't see it? And the phone can't download anything, data isn't working.
All HTC drivers are installed. Oy.
Click to expand...
Click to collapse
No, u shouldn't need to ruu, go to >settings>developer options and just untick the "show CPU usage" option........gone
My EVO Ways
Thanks Chris. And ignoring the posts that aren't answers, provided by obvious children who don't have answers themselves.
Sent from my DROID4 using Tapatalk 2
I think most people decided to open attack on you because you said that the thread should be closed when it is apparent that the only reason it caused you harm is due to your lack of understanding of what that thread was for. No offense, but that's why people were sorta harsh.
Sent from my EVO using xda app-developers app
This is a q and a forum. Not an individual attack forum. I appreciate the answers, and the attacks are again ignored. I challenge the know -it-alls to provide a solution.
Sent from my DROID4 using Tapatalk 2
atlgator said:
This is a q and a forum. Not an individual attack forum. I appreciate the answers, and the attacks are again ignored. I challenge the know -it-alls to provide a solution.
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
You basically started it by stating that the thread should be closed on something that is obviously user error.
I hope you get it up and running though.
Sent from my evoLTE
Thanks. It's running again but truly thanks to nobody on this thread with the exception of those fine people I thanked.
Sent from my DROID4 using Tapatalk 2
OP just doesn't get it.
I get it. Don't come here for real help or discussion. But if you want to alert the world that Olathe has LTE for six seconds, boy you're in the right place!
Sent from my DROID4 using Tapatalk 2
that CASUAL does not work. Oh wait, let me guess, I don't have the right (1 of how many different ones suggested) usb driver, right? And I'm not in ADB, right? And I haven't tried different cables, and ports, and CADI on its own, and zadig, and usbdeview, and pulling the battery when it stalls in download mode (when CASUAL was still recognizing the phone, now neither CASUAL nor ODIN connect to it)? Sorry for the sarcasm, but I'm incredibly frustrated here. How does "one click" turn into a week of trying and trying and trying, and not only not making progress, but seemingly moving backwards where now I can't even get programs to connect? Is there something less messy, contradictory (seriously, the dev thread says "stock anything" but when trying the battery pull and reboot it goes off on me: OMFG WHAT THE HELL ARE YOU DOING? I WARNED YOU! YOU NEED TO ROOT FIRST.) way to unlock? Or a more concise thread of troubleshooting CASUAL (And please, I don't need a link to the same dev thread I just referenced, again.)?
Well I guess the rest of us that followed Adam's thread and were easily unlocked and loading ROMs daily are magicians or something?
Try a different USB port and a different computer. I could not get it to work at all on one PC in Windows or Linux, but it worked first try as soon as I tried it on my laptop.
Yes you caught us it was all a huge conspiracy to get you to brick your phone. The hundreds of people that have said they used the program where all in on it.
Sent from my SCH-I605 using xda app-developers app
dmonger11b said:
Yes you caught us it was all a huge conspiracy to get you to brick your phone. The hundreds of people that have said they used the program where all in on it.
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Dude, you weren't supposed to tell him!
Honestly if you can't run casual at this point, you shouldn't be doing it at all. I say this because when a "real" problem comes up you won't be equipped to handle it. Then you really will be SOL.
Sent from my SCH-I605 using xda app-developers app
nosympathy said:
Honestly if you can't run casual at this point, you shouldn't be doing it at all. I say this because when a "real" problem comes up you won't be equipped to handle it. Then you really will be SOL.
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
BINGO!!
Yea maybe try a different computer. I tried my laptop multiple times and it didn't work but once I did it on my surface pro it worked right away
definitely having the same problem, my solution: going to reinstall Windows 7 and see if that fixes my problems. if that doesn't then I'll just install a Linux distro on my computer and install java and see if i can get it to run that way. if anything I'll try it on another laptop running Windows xp or another till i get this **** to work. it honestly can't be that hard to unlock the note 2. maybe I'll try to root first and then try to unlock.. idk but i have faith in Adam and the other devs who've helped him and tested for him. I'll get it to work or die trying, because Verizon deserves that middle finger, big time.
anyway good luck on your journey!
ztotherad said:
definitely having the same problem, my solution: going to reinstall Windows 7 and see if that fixes my problems. if that doesn't then I'll just install a Linux distro on my computer and install java and see if i can get it to run that way. if anything I'll try it on another laptop running Windows xp or another till i get this **** to work. it honestly can't be that hard to unlock the note 2. maybe I'll try to root first and then try to unlock.. idk but i have faith in Adam and the other devs who've helped him and tested for him. I'll get it to work or die trying, because Verizon deserves that middle finger, big time.
anyway good luck on your journey!
Click to expand...
Click to collapse
It'd be easier to get a Linux boot able CD or make one than do all that...
Sent from my SCH-I605 using xda app-developers app
nosympathy said:
It'd be easier to get a Linux boot able CD or make one than do all that...
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
yup definitely thought about that as well actually. in which i may just end up doing. is java 7 good to use with casual?
ztotherad said:
yup definitely thought about that as well actually. in which i may just end up doing. is java 7 good to use with casual?
Click to expand...
Click to collapse
That's what I have on my machine. I had no issues with casual, although that was several months ago.
It's not fair to be pissed at people who make the tools. You root at your own risk. Every post and every user will tell you that.
Sent from my SPH-L710 using xda app-developers app
WindroidApps said:
It's not fair to be pissed at people who make the tools. You root at your own risk. Every post and every user will tell you that.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
this is so true! you do all this crap at your own risk. and I'm willing to take this risk, and not blame the awesome devs for your problems
5w3d15h said:
that CASUAL does not work. Oh wait, let me guess, I don't have the right (1 of how many different ones suggested) usb driver, right? And I'm not in ADB, right? And I haven't tried different cables, and ports, and CADI on its own, and zadig, and usbdeview, and pulling the battery when it stalls in download mode (when CASUAL was still recognizing the phone, now neither CASUAL nor ODIN connect to it)? Sorry for the sarcasm, but I'm incredibly frustrated here. How does "one click" turn into a week of trying and trying and trying, and not only not making progress, but seemingly moving backwards where now I can't even get programs to connect? Is there something less messy, contradictory (seriously, the dev thread says "stock anything" but when trying the battery pull and reboot it goes off on me: OMFG WHAT THE HELL ARE YOU DOING? I WARNED YOU! YOU NEED TO ROOT FIRST.) way to unlock? Or a more concise thread of troubleshooting CASUAL (And please, I don't need a link to the same dev thread I just referenced, again.)?
Click to expand...
Click to collapse
I hear apple calling for thier long lost customer :good:
droidstyle said:
I hear apple calling for thier long lost customer :good:
Click to expand...
Click to collapse
that's the best line I've heard today.
If you go the Linux route, just be sure to update the lib files, as stated in the casual thread. Linux worked perfectly for me, and I am a complete noob at this stuff.
Sent from my SCH-I605 using Tapatalk 2
ztotherad said:
that's the best line I've heard today.
Click to expand...
Click to collapse
Haha sup man? Glad to see ya made the jump up to the note 2!
mcp2009 said:
Yea maybe try a different computer. I tried my laptop multiple times and it didn't work but once I did it on my surface pro it worked right away
Click to expand...
Click to collapse
ztotherad said:
definitely having the same problem, my solution: going to reinstall Windows 7 and see if that fixes my problems. if that doesn't then I'll just install a Linux distro on my computer and install java and see if i can get it to run that way. if anything I'll try it on another laptop running Windows xp or another till i get this **** to work. it honestly can't be that hard to unlock the note 2. maybe I'll try to root first and then try to unlock.. idk but i have faith in Adam and the other devs who've helped him and tested for him. I'll get it to work or die trying, because Verizon deserves that middle finger, big time.
anyway good luck on your journey!
Click to expand...
Click to collapse
Yep ive been through this to and finnally got it to work on my moms laptop. Our desktop is the only one I can use odin on and my moms laptop is the only one I can use casual on. When I have some spare time (or feel like it lol) im gonna try loading up a fresh install on windows 7 on 1 of my spare hard drives and see what happens from there. But for now im not really woried about it, just gonna roll with the flow.
Sent from my SCH-I605 using Tapatalk 2
5w3d15h said:
that CASUAL does not work. Oh wait, let me guess, I don't have the right (1 of how many different ones suggested) usb driver, right? And I'm not in ADB, right? And I haven't tried different cables, and ports, and CADI on its own, and zadig, and usbdeview, and pulling the battery when it stalls in download mode (when CASUAL was still recognizing the phone, now neither CASUAL nor ODIN connect to it)? Sorry for the sarcasm, but I'm incredibly frustrated here. How does "one click" turn into a week of trying and trying and trying, and not only not making progress, but seemingly moving backwards where now I can't even get programs to connect? Is there something less messy, contradictory (seriously, the dev thread says "stock anything" but when trying the battery pull and reboot it goes off on me: OMFG WHAT THE HELL ARE YOU DOING? I WARNED YOU! YOU NEED TO ROOT FIRST.) way to unlock? Or a more concise thread of troubleshooting CASUAL (And please, I don't need a link to the same dev thread I just referenced, again.)?
Click to expand...
Click to collapse
I feel your pain but hang in there and keep trying. It took me 3 days and several hours to find the right combination that finally worked. If you follow the dev thread for a few days, you'll see that most everyone having problems eventually gets it to work through a combination of trial and error and support from the devs.
If you haven't already, try the driver suggestions in the last several pages of the dev thread. This seems to be helping quite a few others. Another thing to try is running the Casual jar file from an admin command prompt instead of double clicking the file. This worked for me.