Related
Sorry to be a hassle, but I just can't figure this out!!
I've rooted my phone with the "new clarified method" thread, gotten to the clockwork mod and everything, but once I've done that I just cannot get the Unrevoked 2 to work. I've tried it on Windows 7, xp, and osx, and nothing seems to work! The main issue I'm getting is that it'll do the whole process, and then I think it says "reboot to recovery" and then I just get that old phone with a red triangle error. What could I possibly be doing wrong??? It can't be driver issues, because doesn't OSX do that automatically?
I had a similar issue on windows 7 and a simple pc reboot seemed to work for me.
Nope, still no luck. Am I supposed to put these Reflash files on the phone somewhere? I just feel like I'm missing some big step or something. Why is there no good tutorial on this process yet?
Oh my god I think I'm going to go insane! Please someone, point me in the right direction! I have done this hundreds of times now, I'm gonna die. All I can get is "Done!" and then my phone is showing me a big dumb red exclamation point triangle thingy. What am I doing wrong??????
Was I supposed to do something once I first reached the clockwork on my initial root? Cuz all I did was reboot to OS. I don't know if anybody can tell, but I'm kinda desperate. hah
Did you make sure that the phone is recongized in the device manager once plugged in? Need to help us out tell me what you have done so far? Did you install the SDK USB Drivers?
when at the command prompt, did you type adb devices? Does your device show up as connected?
larry996 said:
Did you make sure that the phone is recongized in the device manager once plugged in? Need to help us out tell me what you have done so far? Did you install the SDK USB Drivers?
when at the command prompt, did you type adb devices? Does your device show up as connected?
Click to expand...
Click to collapse
I was having the same problem also until I ran reflash.exe and the command prompt both as admin. I also reran Android SDK installing all of the updates. After plugging in the phone, the SDK picked up two more updates, one of which was USB drivers. Once I did that, things seemed to have worked.
Use attn1's method. The clarified method didnt work for me properly.
I assume you never flashed a rooted rom after reaching clockwork mod. If not the phone is not yet rooted. You have to get back to clockwork recovery and flash a rooted rom (either attn1's liberated one or his stock rooted rom). Both found in his liberated thread. Then set up all the drivers for unrevoked and run it. It should work then.
When my phone is just sitting in bootloader, it is not recognized by adb devices.
You have to go through the whole loop process again booting your phone into recovery and connecting the usb cable.
gdeadfan said:
When my phone is just sitting in bootloader, it is not recognized by adb devices.
Click to expand...
Click to collapse
Thats not good, try reformatting your sd card on your pc with an external reader not with your phone and try again. I'm almost certain it needs to be recognized by adb devices when in bootloader.
Just managed to install the Liberated beta ROM, but now unrevoked can't even get past superuser privelages. it's not popping up anymore
Nevermind, it gets past superuser now, but now it just says "waiting for reboot" and completely reboots the phone to the point at which i can use it regularly
Have you installed the hboot drivers?
Re-ran unrevoked?
Edit: Does it reach "done!"?
Yes, yes, and yes. And my phone just keeps getting to the red triangle. doesn't make any sense to me! And at this point, I'm positive I have no drivers getting in the way like Sync etc., and I'm sure HBoot is installed correctly.
Go to the android market and download titanium backup. It requires root so if it installs we know that you are at least rooted.
Try this, because I had the same problem. Go into device manager with Revoked2 says waiting for reboot. Look under devices above my computer or below cant remember and right click uninstall and remove the android device. reboot your computer then see if it installs are does it automatically, if not don't do anything just plug the phone in and get to hboot/ red triangle screen, then try revoked2 again. This finally got loop to read my device then when I got to clockwork I loaded "liberated rom"
Screw revoked2, just get to clockwork recovery and have liberated rom on your SD card ready to go. Then after install I ran revoked2 for clockwork mod.
Good Luck
Please avoid creating new threads for existing topics. Before creating a new post or thread, you should read all available information in the many Aria rooting threads.
Thank you for your understanding and cooperation as we work to organize the Aria forums.
someone please tell me what does ADB stand for????????
i hate myself for being such a noob but what can i do?!?!?! whats adb pleaseeee...
and why is it that everytime i go into command prompt to try and do stuff with the phone it never finds "androidsdk"
ahh!!!!!
Frenzifun said:
someone please tell me what does ADB stand for????????
i hate myself for being such a noob but what can i do?!?!?! whats adb pleaseeee...
and why is it that everytime i go into command prompt to try and do stuff with the phone it never finds "androidsdk"
ahh!!!!!
Click to expand...
Click to collapse
How about you tell everyone what you are trying to do, and what you are typing in command prompt.
Android Debug Bridge....
Do you have Samsung drivers installed/setup?
Take a nice deep breath and do one learning step at a time. Android has a lot to teach. I would also encourage learning the phone use basics, reading up on things before attempting any mods. Welcome to android family.
Here is a good thread to start in.... http://forum.xda-developers.com/showthread.php?t=790004
tats_06 said:
Android Debug Bridge....
Do you have Samsung drivers installed/setup?
Take a nice deep breath and do one learning step at a time. Android has a lot to teach. I would also encourage learning the phone use basics, reading up on things before attempting any mods. Welcome to android family.
Click to expand...
Click to collapse
lol ... well i already opened another thread about how to put hebrew fonts on the phone to support hebrew instead of seing empty boxes on facebooks and websites and what not... my phone Was rooted, Was voodooed but there was force closing on things and market stopped working so i completely stocked the phone, only thing that doesnt work now is my phone memory which is on 0.00 which i read and you apparently have to root the phone all over again
so right now... the phone memory is my only issue, i guess i can live without hebrew if its too much of a hassle to install while rooted::
http://forum.xda-developers.com/showthread.php?t=480964
i have no idea how to work this^^^
i have the drivers installed like i said, i was able to odin, root, and voodoo, clockwork as well ofcourse. now phone is completely stock except for that memory issue.
http://forum.xda-developers.com/showthread.php?t=804457&highlight=phone+memory
completely got lost in this thread... so yeah, those are my problems with the phone at the moment. i wont mention the obvious of gps etc.
another awesome issue, everytime my phone is turned off and back on, it starts that set up process all over again... language; facebook; google... etc... why?
Once you install adb on your computer you have to go to change the path on your computer to point to that folder. Or you can change your directory to the one that holds the adb file from within the command prompt. This should allow you to run the commands.
The issue you are having with the memory on your phone is because voodoo did not completely uninstall. You can fix this by running the steps in this forum to uninstall voodoo. Don't try the one step zip, you are going to have to do the three step manual method to make this work. Don't forget the final step to wipe data.
Once this is done voodoo will be gone, memory should be back, and phone should stop resetting on every boot.
Obviously you aren't the only one to ever have these issues. But you can recover.
Good luck.
Sent from my SCH-I500 using XDA App
No intro
Here is what I did:
Wanted to flash new ROM, [ROM] Super Clean DI01 + AOSP apps, (Thanks to everyone who worked on it AND everyone on this forum cause Ive spent the past week reading the threads and felt confident enough in the info and the support to try).
BUT
when trying to download with ODIN (not certain if this was the right method, too late now) found that it did not work, couldnt see file when looking in the PDA browse.
STUPIDLY disconnected phone from computer while in DOWNLOAD MODE. You know, when the screen says "DONT DISCONNECT FROM TARGET". Apparently, the rebus string for "you dun f*cked up" is a phone symbol... a yellow triangle w/!...computer symbol.
What do I do to get back to fun?
Tried reboot, tried CWR reboot, tried Nandroid restore w/reboot still the YDFU symbol
*EDIT* I continued searching while awaiting a response and found this thread: Stuck on connection warning screen. This got me out of the YDFU screen into a nice force loop. Since I am not a -complete noob- I pulled a nandroid backup outta my hat and ...tada back to good, now to the fun!
I deleted a folder in /data that had some installed software in it. Once I deleted it, the N7 immediately began spitting FCs at me, Aldiko keystore, the WinnIME app, some .pngs, all FCs.
I rebooted and it hangs on the Google screen. I can get into the bootloader by holding volume down, but the menu usually navigated by volume buttons stays on Start and the power/enter button does nothing. No recovery, obviously.
Most depressing, fastboot and adb do NOT work. The closest analogs to this problem I have found through this search is people who accidentally erased their bootloader. It looks like mine may be corrupted, which could end up being no better.
I am out of town and away from my primary Android computer. The one I have with me is Windows, with an Ubuntu VM that has the SDK and confirmed working ADB and fastboot usually. No dice now, like I said.
When I plug in the tablet through USB, the Windows host attempts to install MTP drivers and fails. I would try and install the Windows SDK and try to get a connection through some of the Windows drivers, but the internet where I am cannot take it.
Any ideas? I am thinking the device is toast, but since I would be the first I have heard of to be able to get into the bootloader and still brick, I thought I would open it up to the community.
Details: I HAD CWM, no more. Stock, rooted only.
is there no nv flash for this device.. this is what you need. to boot into nv flash and flash the boot-loader.. .. I think this is the only way. There is another thread that talks about this.. Not sure if they managed it or not but they were very close i think..
erica_renee said:
is there no nv flash for this device.. this is what you need. to boot into nv flash and flash the boot-loader.. .. I think this is the only way. There is another thread that talks about this.. Not sure if they managed it or not but they were very close i think..
Click to expand...
Click to collapse
Yeah. I used NVflash on the wife's transformer 101. I saw that thread, but i think the resolution was that they finally got close enough to find out they didn't know what they were talking about.
That sounds worse than I intended it. I mean that they simply weren't very experienced NVflash users and so they didn't know what they were missing until they worked at it. Seems a while away, if ever.
I have a second Nexus 7, i am wondering if i can do something with the hardware, maybe. Is all of the storage in one chip? I have the 16 gig, i seem to remember the 8 gig has n actual emmc.
I am going to try and stay away from devices with virtual sdcards from now on. This was just a folder in storage, WTF? I am not even sure how this is possible. Hardlink mayhem, presumably. The device had only ran stock.
mateorod said:
Yeah. I used NVflash on the wife's transformer 101. I saw that thread, but i think the resolution was that they finally got close enough to find out they didn't know what they were talking about.
That sounds worse than I intended it. I mean that they simply weren't very experienced NVflash users and so they didn't know what they were missing until they worked at it. Seems a while away, if ever.
I have a second Nexus 7, i am wondering if i can do something with the hardware, maybe. Is all of the storage in one chip? I have the 16 gig, i seem to remember the 8 gig has n actual emmc.
I am going to try and stay away from devices with virtual sdcards from now on. This was just a folder in storage, WTF? I am not even sure how this is possible. Hardlink mayhem, presumably. The device had only ran stock.
Click to expand...
Click to collapse
yea there is only one storage device inside the nexus.. its all symlinked
If you could get the driver going, send a adb reboot-bootloader command, the bootloader should work then.
Will the next nexus have a longer screen?
Same problem here.
mateorod said:
I deleted a folder in /data that had some installed software in it. Once I deleted it, the N7 immediately began spitting FCs at me, Aldiko keystore, the WinnIME app, some .pngs, all FCs.
I rebooted and it hangs on the Google screen. I can get into the bootloader by holding volume down, but the menu usually navigated by volume buttons stays on Start and the power/enter button does nothing. No recovery, obviously.
Most depressing, fastboot and adb do NOT work. The closest analogs to this problem I have found through this search is people who accidentally erased their bootloader. It looks like mine may be corrupted, which could end up being no better.
I am out of town and away from my primary Android computer. The one I have with me is Windows, with an Ubuntu VM that has the SDK and confirmed working ADB and fastboot usually. No dice now, like I said.
When I plug in the tablet through USB, the Windows host attempts to install MTP drivers and fails. I would try and install the Windows SDK and try to get a connection through some of the Windows drivers, but the internet where I am cannot take it.
Any ideas? I am thinking the device is toast, but since I would be the first I have heard of to be able to get into the bootloader and still brick, I thought I would open it up to the community.
Details: I HAD CWM, no more. Stock, rooted only.
Click to expand...
Click to collapse
Hi, everyone!
I've got the same problem with my Motorola Razr D3 (XT920). After a system update, something bad happen while the system tried to install the last patch realeased by Motorola. I still can access the bootloader but nothing is working.
So I wonder if any of you guys have figured out how to reinstall the bootloader.
Hi all,
Long story short, I accidentally bought a Kindle Fire HD 7. I was hoping to root it but I've had nothing but difficulty. Can anyone help me with the things below? ** Please don't reply if you can't - the disorder and unmoderation of this forum is part of the confusion problem **
- The apps that are given on this site mostly don't work for 7.2.3. Is this an issue with the version?
- I kept getting permission denied errors. Nothing that pushes over, pushes successfully - yet it says it does
- When I finally got something "rooted", my status bar and home bar (at the bottom) are all gone. I can pretty much do nothing with it
- I can't figure out how to restore. I can get into FastBoot mode fairly easily, but when I try to do anything I get "waiting on device" errors. Any ideas?
- I'm a Mac guy, but running Windows 7 to do this. I've tried various versions of drivers posted on the board, but W7 is just a PITA to work with. When it goes into Fastboot, it comes up as an "unrecognized device" in Device Manager. Would this be part of the problem? I've tried to associate drivers with the unknown device, but it keeps saying the driver it has is the best (even though I've removed it).
And while I admit, an emotional rant after spending way too long having to do the above..:
- This forum is a complete mess.. can people with KF HD 8.9's get out of the forum and quit replying or giving advice on the wrong device? Mods, please shut down or move KFHD 8.9 posts. For people trying to find out info, it's seriously a mess.
lordmuggins said:
Hi all,
Long story short, I accidentally bought a Kindle Fire HD 7. I was hoping to root it but I've had nothing but difficulty. Can anyone help me with the things below? ** Please don't reply if you can't - the disorder and unmoderation of this forum is part of the confusion problem **
- The apps that are given on this site mostly don't work for 7.2.3. Is this an issue with the version?
- I kept getting permission denied errors. Nothing that pushes over, pushes successfully - yet it says it does
- When I finally got something "rooted", my status bar and home bar (at the bottom) are all gone. I can pretty much do nothing with it
- I can't figure out how to restore. I can get into FastBoot mode fairly easily, but when I try to do anything I get "waiting on device" errors. Any ideas?
- I'm a Mac guy, but running Windows 7 to do this. I've tried various versions of drivers posted on the board, but W7 is just a PITA to work with. When it goes into Fastboot, it comes up as an "unrecognized device" in Device Manager. Would this be part of the problem? I've tried to associate drivers with the unknown device, but it keeps saying the driver it has is the best (even though I've removed it).
And while I admit, an emotional rant after spending way too long having to do the above..:
- This forum is a complete mess.. can people with KF HD 8.9's get out of the forum and quit replying or giving advice on the wrong device? Mods, please shut down or move KFHD 8.9 posts. For people trying to find out info, it's seriously a mess.
Click to expand...
Click to collapse
Ok what is the state of your KFHD? 7"? I would try to use this toolhttp://forum.xda-developers.com/showthread.php?t=1951254 to restore your kindle and getting back to a working state. If you have any questions post them in here or that forum and I will try to guide you through anything. You should not try to use an automated root tool if it isn't for your specified version(7" 7.2.3) and using a automated tool, I think personally, is just not good in general. What does the device manager specifically say when you are in fastboot? It shoulde look like this:
Thanks for getting back to me. I have indeed also tried that, but I encounter the Fastboot problem mentioned above. I can get it into FB mode fine, but when I go to do anything, it gets stuck at "waiting for device". I'm wondering what I'm doing wrong?
I'm using Windows 7 (gah)... just for the purpose of this. Believe me, it reminds me why I've left Windows looonngg ago
PS All automated tools were specific to my model and version #.. i wouldn't do otherwise.
And I forgot to say, it shows the yellow triangle warning signs.
I have however installed all the right drivers that I got on various places on the forums. Any ideas why it's doing that? (USB debugging/ADB is enabled of course)
lordmuggins said:
And I forgot to say, it shows the yellow triangle warning signs.
I have however installed all the right drivers that I got on various places on the forums. Any ideas why it's doing that? (USB debugging/ADB is enabled of course)
Click to expand...
Click to collapse
Try to reinstall the appropriate drivers.. first uninstall the ones you have now then reinstall.. if you have the yellow triangle in device manager the drivers are not installed correctly
I've tried that.. not sure what I need to do now. (I hate Windows)
The drivers appear fine when not in Fastboot (ie regular ADB) just not when in Fastboot
lordmuggins said:
I've tried that.. not sure what I need to do now. (I hate Windows)
The drivers appear fine when not in Fastboot (ie regular ADB) just not when in Fastboot
Click to expand...
Click to collapse
You do know that ADB and Fastboot are different.. Correct? They are two different cmd lines to execite comds to your kindle..does your kindle boot? What is its state? what are you seeing or does it even run at all>
I thought I made this clear in other posts, sorry
My Kindle boots fine normally, but in my attempts to root it, it's screwed something up (my menubar doesn't appear). I wished to restore it using the tool above.
I can get it into Fastboot, but I can't actually perform any actions due to it saying "waiting for device". Most ADB functionality works fine, i.e. to push apps. But I also can't get it rooted.
My issue is that when it is in Fastboot...not when it's not. That is what I'm trying to figure out.
lordmuggins said:
I thought I made this clear in other posts, sorry
My Kindle boots fine normally, but in my attempts to root it, it's screwed something up (my menubar doesn't appear). I wished to restore it using the tool above.
I can get it into Fastboot, but I can't actually perform any actions due to it saying "waiting for device". Most ADB functionality works fine, i.e. to push apps. But I also can't get it rooted.
My issue is that when it is in Fastboot...not when it's not. That is what I'm trying to figure out.
Click to expand...
Click to collapse
Have you tried Kindle Fire First Aide tool and the restore option of you version?
Yes, I have.
And my issue remains - when in Fastboot mode, it also gets stuck on "waiting for device".
When normal boot, ADB functions are fine. It communicates.. things happen
When in fastboot (I have a WordArt looking 'fastboot' logo on the screen) then nothing appears to communicate, and my Device Manager claims it has an "Unknown Device" that it wont let me manually install drivers for.
Windows 7 is x64 if that makes a difference
lordmuggins said:
Yes, I have.
And my issue remains - when in Fastboot mode, it also gets stuck on "waiting for device".
When normal boot, ADB functions are fine. It communicates.. things happen
When in fastboot (I have a WordArt looking 'fastboot' logo on the screen) then nothing appears to communicate, and my Device Manager claims it has an "Unknown Device" that it wont let me manually install drivers for.
Windows 7 is x64 if that makes a difference
Click to expand...
Click to collapse
Try a factory reset on the device and if that doesn't work go to Chris's thread, KFFirstAide and post your problems that you having with the software. He will help you figure out if something is wrong with your device or its the software. I would think its user related, in the nicest way possible. A lot of times we get are selves all worked up over this stuff and forget to specific steps, I am guilty as well. Maybe take a step back for a few hours and then give it another shot.. Sorry I couldnt help more but I currently don't have my KFHD bc I just got a new one shipped to me and still waiting for it to arrive.. If i had my device in front of me I would probably be able to find you a solution.. Its been three weeks since I have seen a Kindle and my memory is vanishing
How do you propose I do a factory reset?
lordmuggins said:
How do you propose I do a factory reset?
Click to expand...
Click to collapse
right.. menubar is gone.. how the F did that happen.. I don't get all these people having so much problem with rooting their devices and $hit disappearing.. Can you download soft keys? I don't remember if you need to be rooted or not too..
If I knew the answer to that question, I wouldn't be here. I do not see how I can download soft keys.. unless they're in the Amazon store?
lordmuggins said:
If I knew the answer to that question, I wouldn't be here. I do not see how I can download soft keys.. unless they're in the Amazon store?
Click to expand...
Click to collapse
Hey man just trying to help you.. I'm not the one with the problem, although I am making my problem bc I am trying to help. Go over to either thread KFFirstAide or KFHD system.img resotre tool and post your problem.. good luck
So I got it restored; I had to execute the app open in adb to get into Settings. Still can't figure out how to get the Win 7 to recognize it in Fastboot mode.. I just get "waiting for device"
lordmuggins said:
So I got it restored; I had to execute the app open in adb to get into Settings. Still can't figure out how to get the Win 7 to recognize it in Fastboot mode.. I just get "waiting for device"
Click to expand...
Click to collapse
Do you mean you get that when you select the option to reboot into fastboot mode, or that you are already on the fastboot screen but nothing is happening?
I had the exact same issue with missing status bar and softkeys, cazy annoying. So hopefully I can remember exactly what I did, depending on your answer to my question though
In regular mode, I had missing status bar and softkeys. I restored factory settings (by using adb to get into the settings screen). They are now back.
Now, I have it rooted (well, I have Superuser loaded at least and it appears to be working)... but that is all. It still feels half-done to me.
With the FirstAide tool I'm getting into Fastboot and then I was going to use it to restore it using the Restore Tool here: http://forum.xda-developers.com/showthread.php?t=1951254
But it doesn't work.. I can load into the Fastboot screen (wordart logo) but it doesn't connect to the device... I just get "waiting for device" and that's where it stops. The WIndows 7 PC I'm using just says that an unknown device has connected and leaves it there.
Ideally, I wish to load Google Play etc, but I can't do that using the First Aide tool. It throws a lot of permission denied errors at me.. reboots several times, says it has been successful but none of the apps are there.
Ideas? I feel like I'm getting closer... perhaps..!
Have you tried running a app that needs root and seeing if the "grant permission" window pops up when you run it. There is a root checker app that you could install from the Noobs Guide to rooting, which should do the trick. SUChecker.apk http://forum.xda-developers.com/showthread.php?t=2069117
If you have managed to get the UI bars back, how come you want to use the restore tool to reset the whole kindle?
If you root is working fine, and you want to install google play then follow the Alternative Manual Install from here http://forum.xda-developers.com/showthread.php?t=2069329 instead of using the first aide tool, which seems to be giving a few issues at the moment.
Another random solution is make sure you are using a usb2 port instead of a usb3 port(if you have one)
A lot of these I'm sure are general but since the HTC 10 is what I have and I'm using firmware and ROMs from within this subforum I thought this would be the most appropriate place to post. I have rooted/unlocked all of my (non-Nexus) phones over the years and like to think I have a moderate amount of experience with the process, but this is driving me up the wall and my searches for similar problems are turning up nothing but unrelated issues. My HTC 10 is unlocked and S-Off. I was running the ROM from this thread (the 6.0.1 version) for quite some time but stopped using the phone due to unrelated issues (screen is too big, can't get over the polarized screen and not being able to use the phone with sunglasses on). I'm now trying to sell it and therefore trying to get current firmware and a stock ROM onto it so potential buyers are not freaked out about modifications to the phone. I'd like to leave it unlocked and S-Off though.
I am able to successfully flash the firmware (from this thread), and have been going back and forth between the full stock ones and the ones with TWRP built in. As of right now the phone has no bootable ROM and I have been unable to load one. I can successfully get into Download, Recovery, and Fastboot modes. I see that I have three main paths to potentially flashing a stock ROM:
- Repair/Upgrade via HTC Sync with the phone in download mode
- Load the ROM onto the phone's SD card and use TWRP to flash
- Use ADB to sideload the ROM directly from Windows
My problems with these three options are thus:
- HTC Sync does recognize the device when put in Download mode. It even successfully downloads the update it perceives the phone needs. But at 20%, it claims the phone has too low of battery (it doesn't, it's locked at 100% and has been plugged in the whole time) and quits. It does this regardless of whether I select Upgrade or Repair. Tried multiple times, with both stock recovery and TWRP. I found one other case of this, and the only response was the OP saying he just sent his phone back to HTC. I don't think this is an option for me because it has sat unused basically since I bought it over six months ago.
- The phone does not read the SD card. Other devices read it just fine, but I don't have any SD card reader that can directly talk to my computer to do the file transfer through. I have not found any guides that allow me to mount the SD card without having a bootable ROM. Maybe this is where I simply don't know enough about ADB/TWRP and someone can point out a simple solution? I'm hopeful.
- I can get the phone into Recovery and then into "Sideload" mode. But trying to run "adb devices" or "adb sideload 2PS6IMG.zip" returns some variation of the following (the 31 and 39 are always there, sometimes it had more detail and sometimes it has less):
>adb server version (31) doesn't match this client (39); killing...
>error: could not install *smartsocket* listener: cannot bind to 127.0.0.1:5037: Only one usage of each socket address (protocol/network address/port) is normally permitted. (10048)
>This application has requested the Runtime to terminate it in an unusual way.
>Please contact the application's support team for more information.
I can't find anyone having these errors in this combination, but from what I can gather it's somehow tied to not having an up-to-date version of ADB... but I keep going and downloading the absolute most recent one (either from one of the threads here or Android Studio) and it just doesn't work. If I use one of the HTC_fastboot packages instead to try running the commands I just get "cannot read 'sideload'". I assume there is some kind of package or library missing from those directories.
Really I will take advice on troubleshooting any of these three angles, or one I have not though of. I'm sure all of the problems are stemming from one very annoying source but I just don't know what else to try. Thanks for any help you can offer.
I managed to get some ROMs onto a different micro SD card and the phone seems to at least recognize them. With stock recovery predictably I got "not signed" errors so I flashed the recovery that includes TWRP 3.1.1 from here, but it is giving me "corrupt file" errors for every single RUU .zip I have tried. They are all Verizon RUUs from here. Does not feel like I have actually made progress.
Valdair0 said:
I managed to get some ROMs onto a different micro SD card and the phone seems to at least recognize them. With stock recovery predictably I got "not signed" errors so I flashed the recovery that includes TWRP 3.1.1 from here, but it is giving me "corrupt file" errors for every single RUU .zip I have tried. They are all Verizon RUUs from here. Does not feel like I have actually made progress.
Click to expand...
Click to collapse
RUUs are to be flashed from download mode, not from twrp. Put your ruu in the root of your sd card and boot into download mode.
Tarima said:
RUUs are to be flashed from download mode, not from twrp. Put your ruu in the root of your sd card and boot into download mode.
Click to expand...
Click to collapse
Make sure it's named 2PS6IMG.zip
Thanks guys, it seems to be working okay now. It was upgrading to 7.0 when I left the house this morning. I'm going to flash stock recovery one last time tonight and hopefully it will be set.