I just wanted to split this discussion from the leaked ROM thread. From what I have gathered and understand, this newest update is the US equivalent of the Europe 2.51 update. I know many of you have already upgraded your devices to this, so users like me who are late/slow to the game, aren't there yet. In my case I still had the stock 3.6.160 up until last night. I know many have had the concern about 2.51 and not being able to go back. Has US TMobile done us a favor by releasing this OTA update? It would seem to me that this is now a sanctioned update, so anything from here on out would be officially supported and updated. It also seems that if the US and Europe version are the same, any thing that works for 2.51, would work for the US version. Like the 3.4.2 Nandroid backups. It should just be a matter of a simple restore and everything should work, correct? Sorry if I seem a little off. Prior to this device all of mine have been HTC devices which didn't have the locked bootloader. So this concept of of firmware/roms is a little off to me. I haven't had a chance to test any of this yet, I just want to know if the theory is correct. If I'm wrong please point me in the right direction. I'd like to be able to contribute to this forum constructively, especially as I am in charge of deploying DEFYs on our corporate network. The nice part of this is my Director is all for rooting our phones. He looks at in the manner that we need to do what needs to be done. If a phone gets bricked in the process, well we will just buy another. Warranty really isn't a concern.I'd like to get playing on it this weekend, especially with Froyo.
runeblade said:
It would seem to me that this is now a sanctioned update, so anything from here on out would be officially supported and updated.
Click to expand...
Click to collapse
Nope.
The only update for the US DEFY is an incremental one (still 2.1) and it has only been released to 500 or so users according to the offical Tmo forums.
They are testing that one now.
The official froyo for DEFY is probably still a couple/few months away from public release, but let us hope they get it out faster.
More info in this thread:
http://forum.xda-developers.com/showthread.php?t=931212
The Incremental has been released to the wild. Both of my Defy's received it OTA. I also know this is not an OS upgrade. Still stuck at 2.1. But my understanding was that the US update changes the boot loader to the same one as the Europe 2.51 update. If this is indeed true it would mean that we should be able to boot any of the 2.2 Roms out there without using the European update. Thats what I'm trying to confirm/Deny.
I registered for the "testing update", and received it this morning. Overall the phone is so much smoother. I'm now using Blur instead of ADW or LP. As a matter of fact all scrolling is smoother. The homescreens, app drawer, lock screen, widgets. Everything. Before the update if I was on Wi-Fi and sent a MMS I would get a delay, and have both icons in the notification bar for Wi-Fi and 3G, but now they send instantly, and I only have the Wi-Fi icon. Battery seems to be lasting longer today too which is one of the included functions. I'm impressed overall with what they did.
I was on of the very first few to get the Official 3.6.360 and while yes some things have improved. I decided to do a wipe after I had installed it. And I notice something interesting. No more root, Z4Root (using 1.3.0 which is what I used the first time I rooted this phone) no longer works, unexpected failure. So yea the have changed something... I run down the ADB route and see what that turns up.
I will have go the ADB route to get back to rootville.
darknetone said:
I was on of the very first few to get the Official 3.6.360 and while yes some things have improved. I decided to do a wipe after I had installed it. And I notice something interesting. No more root, Z4Root (using 1.3.0 which is what I used the first time I rooted this phone) no longer works, unexpected failure. So yea the have changed something... I run down the ADB route and see what that turns up.
I will have go the ADB route to get back to rootville.
Click to expand...
Click to collapse
I noticed the same thing. No more root access after the update. I tried to re-root with z4root, super 1 click to no avail. Not familiar with the ADB process. Kinda nervous to be honest. First Android phone and all. Had it 2 weeks. Hopefully a new 1 click method comes from one smarter than I soon.
That's interesting. I noticed right off the bat that Z4Root no longer worked, so I ran Super1click, and that worked fine for me. The only thing I haven't done is wipe the phone, but at this point it doesn't sound like I'm going too.
runeblade said:
That's interesting. I noticed right off the bat that Z4Root no longer worked, so I ran Super1click, and that worked fine for me. The only thing I haven't done is wipe the phone, but at this point it doesn't sound like I'm going too.
Click to expand...
Click to collapse
Did you need to do anything special with Super1click, or was it as simple as z4root? Can you just run it, and wait for it to finish? I mean I read some stuff that you may need to do the "turn debug off, turn it on, turn it off" thing with it because some phones give a "waiting for device". If you did certain steps other than just clicking root can you share? Thanks.
Nope. Just downloaded it, ran as admin and let it do its magic. Short and simple.
runeblade said:
Nope. Just downloaded it, ran as admin and let it do its magic. Short and simple.
Click to expand...
Click to collapse
How long did it take? I tried it, but it keeps hanging on "waiting for device..."
Mine as well. Just keeps saying waiting. It got further once but stuck in a loop and came back to waiting. I unmount the sd, put it in debug, not sure what usb mode to use or where this admin option is found though. Quite frustrated since the bloatware I froze with Titanium Backup is back and all my root permissions are one. Any help for a newAndroid guy would be awesome.
Make sure when you have it connected to your machine that you are in Portal mode, as well as making sure that your machine is actually picking up the MDB interface. I know with mine it took a couple of plug ins to get it to actually install correctly.
bobbyphoenix said:
How long did it take? I tried it, but it keeps hanging on "waiting for device..."
Click to expand...
Click to collapse
I think your problem might be that you're running it in USB "None" mode (as you would if running ADB). This is a common mistake. With Super1Click, you have to run it in "Portal" mode.
Plug your phone into the computer. You'll get "USB Connection" in your notification bar at the top. Then pull the notification bar down and click "USB connection". Click "Motorola Phone Portal". Then make sure "USB Debugging" is on (in Menu key > Settings > Applications > Development). Now run Super1Click as administrator. Click "Root".
It still takes a while in between steps, especially at the various "Waiting for device" stages. But if you did all the initial steps above, it should work properly. Just BE PATIENT.
cargohook said:
I think your problem might be that you're running it in USB "None" mode (as you would if running ADB). This is a common mistake. With Super1Click, you have to run it in "Portal" mode.
Plug your phone into the computer. You'll get "USB Connection" in your notification bar at the top. Then pull the notification bar down and click "USB connection". Click "Motorola Phone Portal". Then make sure "USB Debugging" is on (in Menu key > Settings > Applications > Development). Now run Super1Click as administrator. Click "Root".
It still takes a while in between steps, especially at the various "Waiting for device" stages. But if you did all the initial steps above, it should work properly. Just BE PATIENT.
Click to expand...
Click to collapse
Everyone keeps saying 'as administrator'. There is no option in S1C for that. Nor on my phone. How do I execute this as admin? Am I just being dumb?
Edit: Does this mean as computer admin? Like head honcho on the pc?
This is based on the assumption you are using windows 7 or vista. You right click on the program and in the drop down menu select Run as Administrator. It will then open up the program.
slipknotfn said:
Everyone keeps saying 'as administrator'. There is no option in S1C for that. Nor on my phone. How do I execute this as admin? Am I just being dumb?
Edit: Does this mean as computer admin? Like head honcho on the pc?
Click to expand...
Click to collapse
Exactly, "Head Honcho of the computer"! Do what runeblade said.
cargohook said:
I think your problem might be that you're running it in USB "None" mode (as you would if running ADB). This is a common mistake. With Super1Click, you have to run it in "Portal" mode.
Plug your phone into the computer. You'll get "USB Connection" in your notification bar at the top. Then pull the notification bar down and click "USB connection". Click "Motorola Phone Portal". Then make sure "USB Debugging" is on (in Menu key > Settings > Applications > Development). Now run Super1Click as administrator. Click "Root".
It still takes a while in between steps, especially at the various "Waiting for device" stages. But if you did all the initial steps above, it should work properly. Just BE PATIENT.
Click to expand...
Click to collapse
Yep. That was my problem. Didn't have it in portal mode. As soon as I did, it went fast. It went through a bunch of steps. I see it says "Running psneuter... ROOTED" It should be almost done. It's on "Reading OS Version properties..." now, and it's been there for like 10 minutes now.
cargohook said:
Exactly, "Head Honcho of the computer"! Do what runeblade said.
Click to expand...
Click to collapse
What if one were running, say, XP? Then head honcho would work? I have no computer here that has 7 or Vista. Just my old, trusty laptop. Thanks for all your help.
And which version of S1C? The one for 2.51 or the 1.63 version?
The 2.51 version.
runeblade said:
The 2.51 version.
Click to expand...
Click to collapse
where is that version? I'm using 1.6.3 and it's still stuck on "reading OS" thing.
Related
I tried the "IDIOT-PROOF Root Guide! NAND Unlock and ADB Update!!".... to no avail.
I had fallowed the instructions to a tee and around step 55 it all went down hill, it was supposed to automatically flash a ROM and it did nothing, and now i have probably screwed it up worse. Phone is still 100% functional but i would like to reset back to factory settings, no root, no nand, no custom rooted ROMS, nothing.
Does anyone know of a way to get my phone back to the way it was when i walked out of Best Buy earlier today?
Thanks for the help and all the great resources here at XDA.
Daugusta.
Search for and run the RUU
Step 55? Thats the idiot proof guide? I followed the original guides and there were like 10 steps max..
Haha, could i snag a link to the guide you used? also, where can i find this RUU?
Thanks.
Daugusta12 said:
Haha, could i snag a link to the guide you used? also, where can i find this RUU?
Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=685835&highlight=RUU
This is not flashed, its an exe so its run while your phone is plugged in. Should go smoothly, but as always know the risks of flashing anything
I've heard toasts method is pretty solid for rooting.
Quick question wouldn't this be in Q & A? Not trying to come off as a jerk. Just my 2 cents
Sent via the Sprint HTC EVO
RUU Is not working, i get it to start, it restarts my phone and then sits their at a black screen that says "HTC" Then the program says "Waiting for boot loader" and counts to like 75 and then errors saying that it cannot connect to the phone. I then tried to start the process, pull the battery, then manually put it into the boot loader and the program never recognizes it.
Anyone else have another idea, or a way to get this working?
Thanks,
Daugusta
I believe you have to use HTC sync when you run it, though I could be mistaken. Search YouTube, there's a video of it somewhere. I wouldn't give up on rooting just yet though.
Trust me im not giving up
Try the 1-click Root Method
I looked at the fifty-five step root method and peed my pants, then I hit up jiqqaman's one-click root method. Stable root, and you can flash the stock (rooted) rom.
[forum.xda-developers.com/showthread.php?t=706411
Diesektor said:
I believe you have to use HTC sync when you run it, though I could be mistaken. Search YouTube, there's a video of it somewhere. I wouldn't give up on rooting just yet though.
Click to expand...
Click to collapse
When I have ran an rru from previous HTC phones I have had to have sync up. But then again its never been at a black screen
Sent via the Sprint HTC EVO
Ya, i had the HTC sync running as well, synced up fine with my comp but the RUU still gave me the same error.
Im running this on Win 7 64 Bit, im guessing the 64 bit may be the problem. ill try it on a different comp and see how it goes.
Just tried it on a 32 bit Windows 7 comp, still same issues.
Sucks man, coming from the iphone world this rooting stuff seems a hell of a lot more complicated. The last jailbreak I did on my 3GS I downloaded 1 program, plugged by phone into the PC, clicked 1 button and bam!
This andriod root stuff is waaaaay more difficult, NAND this, bootloader that, recovery this, RUU that, adb this, zip and flashing all kinds of stuff. Wish there was a simpler method. Im obviously a noob so Im sure it will get easier with time.
Daugusta12 said:
RUU Is not working, i get it to start, it restarts my phone and then sits their at a black screen that says "HTC" Then the program says "Waiting for boot loader" and counts to like 75 and then errors saying that it cannot connect to the phone. I then tried to start the process, pull the battery, then manually put it into the boot loader and the program never recognizes it.
Anyone else have another idea, or a way to get this working?
Thanks,
Daugusta
Click to expand...
Click to collapse
It should work. After the program doesn't recognize it, while your phone is at the HTC logo. Close the program on your pc and start it again.
Daugusta12 said:
Just tried it on a 32 bit Windows 7 comp, still same issues.
Click to expand...
Click to collapse
There shouldn't be any problems caused by 64-bit OS. I used Win7 Ult 64-bit and it worked fine. Do you have the HTC Sync drivers? That may fix the problems you have.
EVO'D_OUT said:
Sucks man, coming from the iphone world this rooting stuff seems a hell of a lot more complicated. The last jailbreak I did on my 3GS I downloaded 1 program, plugged by phone into the PC, clicked 1 button and bam!
This andriod root stuff is waaaaay more difficult, NAND this, bootloader that, recovery this, RUU that, adb this, zip and flashing all kinds of stuff. Wish there was a simpler method. Im obviously a noob so Im sure it will get easier with time.
Click to expand...
Click to collapse
I noted this too, only I didn't have an iPhone, just an iPod Touch. Despite this, I am having a lot more fun with Android and how it works. I.E. *.9.pngs which made made jaw drop when I understood how it works. SO AMAZING.
I don't think I will ever be much of a dev, but who knows. I have been digging through a TON of documentation over the past 2-3 weeks.
Thread moved to Q&A.
well I'm pretty much over this rooting business. Ill wait for the official froyo update from Sprint/HTC and not worry about this crap, no camera, instability, bricking, etc. Guess I'm not much of an android hacker and the phone works pretty well bone stock.
Here are my questions...and please explain this to me like I am mentally retarded haha...
For returning my phone to bone stock, Like Day 1, same as it was when I walked out of Sprint store...
1) download .exe file from post #1 onto my PC
2) plug EVO into USB on PC (run in USB debug mode?)
3) Run .exe file while EVO is in Andriod
4) Select yes, yes, blah, blah and it will do its thing automatically?
Is this correct? Some have mentioned I need to download HTC sync onto PC. Yes - No? Any help would be appreciated. Hopefully someone can comment THAT HAS ACTUALLY DONE THIS and not just guessing/speculation can assist.
EVO'D_OUT said:
well I'm pretty much over this rooting business. Ill wait for the official froyo update from Sprint/HTC and not worry about this crap, no camera, instability, bricking, etc. Guess I'm not much of an android hacker and the phone works pretty well bone stock.
Here are my questions...and please explain this to me like I am mentally retarded haha...
For returning my phone to bone stock, Like Day 1, same as it was when I walked out of Sprint store...
1) download .exe file from post #1 onto my PC
2) plug EVO into USB on PC (run in USB debug mode?)
3) Run .exe file while EVO is in Andriod
4) Select yes, yes, blah, blah and it will do its thing automatically?
Is this correct? Some have mentioned I need to download HTC sync onto PC. Yes - No? Any help would be appreciated. Hopefully someone can comment THAT HAS ACTUALLY DONE THIS and not just guessing/speculation can assist.
Click to expand...
Click to collapse
Great question.. Some of these long winded threads need trimming and a definite answer listed out. Clutter = confusion
I would like to get everyone's opinion, I'm looking at a couple options of how to get rid of Sprint / HTC Junk that runs at startup and continues to startup - Sprint Nav, Sprint Zone, Nascar, all those things. I'd love to hear alternate suggestions as well.
1. Startup Auditor - Seems to do a decent job of keeping things from starting, definitely reduced boot time, but I'm unsure of how it actually operates - is it just another task killer? Or does it actually take things out of a startup list without running in the background? I've been playing with it for close to a day and am still undecided, at times it seems to help, but other times I don't think it really did anything. It seems like having root would make it completely pointless, since you could edit things yourself.
2. Wait for Root - I already did the OTA update so root is not possible, from what I understand. With root access, I'm sure it would be much easier to remove the actual applications, and furthermore install custom roms without the bloat.
3. ?? You tell me please
Thanks guys!
If you're comfortable using adb, you can root here: http://forum.xda-developers.com/showthread.php?t=718889
I rooted my yesterday after the OTA and flashed Fresh 0.5.3. It doesn't have most of the crapware.
gx1400 said:
If you're comfortable using adb, you can root here: http://forum.xda-developers.com/showthread.php?t=718889
I rooted my yesterday after the OTA and flashed Fresh 0.5.3. It doesn't have most of the crapware.
Click to expand...
Click to collapse
Funny I was just reading that. I have zero experience with ADB, but perhaps that is the best route. Can't be too hard to learn, right?
Thanks for posting that. If you have root, it mostly eliminates the need for a program like startup auditor, right?
berardi said:
Funny I was just reading that. I have zero experience with ADB, but perhaps that is the best route. Can't be too hard to learn, right?
Thanks for posting that. If you have root, it mostly eliminates the need for a program like startup auditor, right?
Click to expand...
Click to collapse
Correct. Most ROMs already have the crapware removed, however, once rooted you'll also have the ability to remove and do anything else you want.
If you are uncomfortable with adb, don't be. There are enough tutorials and videos around to walk you through the process. Not only was I a complete noob when I moved to Andriod from the iPhone but I am also using a Mac which means the commands are slightly different. However, with a little trial and error I was able to root via adb the very weekend the phone was released when only adb instructions existed.
And, going forward you'll never have to wait for "Idiot Guides" again. Whenever something new and great comes along you'll have the skills to implement it right away.
okolowicz said:
Correct. Most ROMs already have the crapware removed, however, once rooted you'll also have the ability to remove and do anything else you want.
If you are uncomfortable with adb, don't be. There are enough tutorials and videos around to walk you through the process. Not only was I a complete noob when I moved to Andriod from the iPhone but I am also using a Mac which means the commands are slightly different. However, with a little trial and error I was able to root via adb the very weekend the phone was released when only adb instructions existed.
And, going forward you'll never have to wait for "Idiot Guides" again. Whenever something new and great comes along you'll have the skills to implement it right away.
Click to expand...
Click to collapse
I'm trying to setup ADB right now but I'm stuck here:
http://forum.xda-developers.com/showthread.php?t=694250
3. Enabling ADB support on EVO
If using completely stock EVO, adb will be disabled in recovery and can't be enabled.
Click to expand...
Click to collapse
So if you can't enable ADB on stock EVO, but you need ADB to root - what to do?
EDIT : Nm I think I got it
I want to say that if you plug your phone into your computer and select sync option, that it will install the necessary drivers. Just make sure to turn on usb debugging in your settings menu: menu,settings, applications, development, usb debugging- check the box.
elegantai said:
I want to say that if you plug your phone into your computer and select sync option, that it will install the necessary drivers. Just make sure to turn on usb debugging in your settings menu: menu,settings, applications, development, usb debugging- check the box.
Click to expand...
Click to collapse
Thanks got it..
I'm following these instructions, they seem the most complete. I followed every step successfully and refreshed the pages, and it told me to reboot and run part2. However when I hit
adb reboot
it returns
adb: permission denied
What did I do wrong here?
EDIT: Missed hitting exit. That step wasn't there in original, it is in the recompiled though.
go read up on that thread, do a search for 'permission denied' or the like and I am sure something will come.I saw it a few times while reading that thread
err... Are you sure it didnt just mean reboot your phone?
elegantai said:
go read up on that thread, do a search for 'permission denied' or the like and I am sure something will come.I saw it a few times while reading that thread
err... Are you sure it didnt just mean reboot your phone?
Click to expand...
Click to collapse
haha thanks I was messed up because the original instructions didn't say to exit the adb shell (I probably should have known though) but now I'm past that, now to reboot and hit adb shell /data/local/part2 in time lol this is fun :-D
All done!!! :-D now to flash rom... good times!
Thanks all
my Xperia Play R800i will not turn on anymore after i tried to flash a rom... i dont exactly remember which one it was... i hope its not important
what my phone does is showing the Sony Ericsson logo and just stays there... i had it on the entire day just be sure that i wasnt doing something in the background or anything ...
but i never did it on my phone yet... (maybe better if never did this now i think of it)
but anyway pc companion says "null" and thats all it will say further it cannot detect my phone or do anything with it
i hope flashtool works if anyone is willing to lead me through it.
i dont have warranty anymore.
MausHaxxi said:
my Xperia Play R800i will not turn on anymore after i tried to flash a rom... i dont exactly remember which one it was... i hope its not important
what my phone does is showing the Sony Ericsson logo and just stays there... i had it on the entire day just be sure that i wasnt doing something in the background or anything ...
but i never did it on my phone yet... (maybe better if never did this now i think of it)
but anyway pc companion says "null" and thats all it will say further it cannot detect my phone or do anything with it
i hope flashtool works if anyone is willing to lead me through it.
i dont have warranty anymore.
Click to expand...
Click to collapse
Would you happen to have a custom kernel? Which Sony Ericsson logo is it, the non-moving one or the animated one?
Now, you wouldn't have happened to install a CyanogenMod, Ice Cream Sandwich or Jelly Bean rom, would you? I know you don't remember which rom you installed, just trying to spark a memory. Anyway, if you did so, then all you need to do is flash a compatible kernel. You see, if the Sony Ericsson logo you are seeing is the non-moving one, then you have the stock kernel, the one that's incompatible with the aforementioned roms.
If you don't want to get involved with this kernel business, then I've provided a Flashtool guide, so you can at least get your phone to a working, albeit factory reset, state:
First, install Flashtool.
Go here and find what you think your stock firmware was, download it.
Place the .ftf file in your Flashtool/firmwares directory.
Open Flashtool (as administrator if necessary) and click on the lightning bolt in the Flashtool window. Highlight Flashmode and select OK. A new window shall pop-up.
Select your downloaded firmware. I should read "R800i" in the first box and "4.0.2.A.0.XX" (with the "XX" being the number of the version you downloaded) in the second, the contents of the third box varies, so disregard it. There are many options for what to keep/replace during flashing, but I'd recommend leaving them as they are. Select OK. The window will now close and a new window will pop-up shortly after.
This window will detail the proceeding steps: With your turned-off phone (make sure its battery is intact), hold the back key (the leftmost one) while inserting the usb from your computer to your phone, continue holding the key until the window closes, DO NOT REMOVE THE USB.
The Flashtool window will now begin streaming various lines detailing its progress, all you need to look for is the line detailing a successful flash which with then tell you to disconnect your phone, now you can remove the USB.
Go ahead and close the remaining Flashtool window, your phone should now be back to default, factory reset, everything except your phone's bootloader and SIM unlocked statuses, they should be how you left them before.
thanks!
Toasty Clown said:
Would you happen to have a custom kernel? Which Sony Ericsson logo is it, the non-moving one or the animated one?
Now, you wouldn't have happened to install a CyanogenMod, Ice Cream Sandwich or Jelly Bean rom, would you? I know you don't remember which rom you installed, just trying to spark a memory. Anyway, if you did so, then all you need to do is flash a compatible kernel. You see, if the Sony Ericsson logo you are seeing is the non-moving one, then you have the stock kernel, the one that's incompatible with the aforementioned roms.
If you don't want to get involved with this kernel business, then I've provided a Flashtool guide, so you can at least get your phone to a working, albeit factory reset, state:
First, install Flashtool.
Go here and find what you think your stock firmware was, download it.
Place the .ftf file in your Flashtool/firmwares directory.
Open Flashtool (as administrator if necessary) and click on the lightning bolt in the Flashtool window. Highlight Flashmode and select OK. A new window shall pop-up.
Select your downloaded firmware. I should read "R800i" in the first box and "4.0.2.A.0.XX" (with the "XX" being the number of the version you downloaded) in the second, the contents of the third box varies, so disregard it. There are many options for what to keep/replace during flashing, but I'd recommend leaving them as they are. Select OK. The window will now close and a new window will pop-up shortly after.
This window will detail how the preceding steps: With your turned-off phone (make sure its battery is intact), hold the back key (the leftmost one) while inserting the usb from your computer to your phone, continue holding the key until the window closes, DO NOT REMOVE THE USB.
The Flashtool window will now begin streaming various lines detailing its progress, all you need to look for is the line detailing a successful flash which with then tell you to disconnect your phone, now you can remove the USB.
Go ahead and close the remaining Flashtool window, your phone should now be back to default, factory reset, everything except your phone's bootloader and SIM unlocked statuses, they should be how you left them before.
Click to expand...
Click to collapse
Thanks, i will try this when im home tonight
i will tell you if i got it working again lol (ps. i aint a noob... i never got freezings before... i was just being cautious so i wont break it behond repair LOL)
ALMOST fixed
ok it works again now. but now it asks me to download settings ... which it fails in... my phone tells me that it failed and asks me to retry downloading them.... which eventually will fail again... i got wifi on ofcourse (duh...)
anyway... i dont get it why i am having so much trouble with my phone.... my tablet i can hack without hassle... i just never used flashtool XD
always cmd and such...
anyway im almost there to have it completely fixed
thanks so far
MausHaxxi said:
ok it works again now. but now it asks me to download settings ... which it fails in... my phone tells me that it failed and asks me to retry downloading them.... which eventually will fail again... i got wifi on ofcourse (duh...)
anyway... i dont get it why i am having so much trouble with my phone.... my tablet i can hack without hassle... i just never used flashtool XD
always cmd and such...
anyway im almost there to have it completely fixed
thanks so far
Click to expand...
Click to collapse
Okay, having not used stock in a long time, I've reverted my rom and kernel! Upon doing so, I noticed little wrong. Though I do remember an annoying prompt when I opened the browser, it'd say "Please insert SIM card" and "downloading settings" would pop-up following it.
Aside from that, I can't recreate the problem you're having. Could you go into more detail?
screen photo
Toasty Clown said:
Okay, having not used stock in a long time, I've reverted my rom and kernel! Upon doing so, I noticed little wrong. Though I do remember an annoying prompt when I opened the browser, it'd say "Please insert SIM card" and "downloading settings" would pop-up following it.
Aside from that, I can't recreate the problem you're having. Could you go into more detail?
Click to expand...
Click to collapse
here is the popup that i get all the time.... while i CAN call people and receive calls... my phone refuses to use 3G which i do need...
MausHaxxi said:
here is the popup that i get all the time.... while i CAN call people and receive calls... my phone refuses to use 3G which i do need...
Click to expand...
Click to collapse
Well... That's something I have never seen before...
Searched the Q&A and troubleshooting section, and I'd found a thread detailing such an error upon switching firmware. No offence but perhaps I didn't give you enough detail on which firmware to download, and for that I apologise.
Would you happen to know what branding your phone is, and post what it is and which firmware you installed (you can find said information in that third box I told you to ignore in Flashtool)? AT&T, Verizon, unbranded/no SIM/unlocked? I ask this as you may have installed incompatible firmware.
As an example, my phone was unbranded and came with no SIM, the pre-installed installed firmware (and the only one that I find to be fully compatible) was the R800i 4.0.2.A.0.42 UK Generic. In the context of stock roms, I find that it's best not to stray.
Anyway, you've probably already figured out what to do: find the intended firmware and flash it, using the instructions above. I'd recommend gathering some more outside help, changing the thread's title to reflect the current conundrum should be a good starting point.
will do
Toasty Clown said:
Well... That's something I have never seen before...
Searched the Q&A and troubleshooting section, and I'd found a thread detailing such an error upon switching firmware. No offence but perhaps I didn't give you enough detail on which firmware to download, and for that I apologise.
Would you happen to know what branding your phone is, and post what it is and which firmware you installed (you can find said information in that third box I told you to ignore in Flashtool)? AT&T, Verizon, unbranded/no SIM/unlocked? I ask this as you may have installed incompatible firmware.
As an example, my phone was unbranded and came with no SIM, the pre-installed installed firmware (and the only one that I find to be fully compatible) was the R800i 4.0.2.A.0.42 UK Generic. In the context of stock roms, I find that it's best not to stray.
Anyway, you've probably already figured out what to do: find the intended firmware and flash it, using the instructions above. I'd recommend gathering some more outside help, changing the thread's title to reflect the current conundrum should be a good starting point.
Click to expand...
Click to collapse
if i cant obtain the required info i need i will make a new post regarding this issue...
but thanks to you for getting my phone to a working state
ps. i will post here if i got the 3G back to work or not using the thread you supplied.
fixed
MausHaxxi said:
if i cant obtain the required info i need i will make a new post regarding this issue...
but thanks to you for getting my phone to a working state
ps. i will post here if i got the 3G back to work or not using the thread you supplied.
Click to expand...
Click to collapse
it was simply the APN settings....
how could i know xD never had this error before... anyway it works fine now 3G works smoothly
MausHaxxi said:
it was simply the APN settings....
how could i know xD never had this error before... anyway it works fine now 3G works smoothly
Click to expand...
Click to collapse
Oh, sorry about that. I'd only ever experienced an APN problem when one of the roms I had installed had a broken settings app.
Anyway, it's nice to see that you've fixed your phone yourself, congrats!
I have adb and fastboot installed, and using rumrunner, I am trying to s-off/root my HTC One M7. Is anyone else having issues with it getting stuck on the first pouring <1>... message? Mine has been sitting here for about an hour with no change. I made sure to go in an disable 'verify apps by adb' in the phone's settings, and started again, and yet it still gets stuck on this first pour.
Any ideas?
MReprogle said:
I have adb and fastboot installed, and using rumrunner, I am trying to s-off/root my HTC One M7. Is anyone else having issues with it getting stuck on the first pouring <1>... message? Mine has been sitting here for about an hour with no change. I made sure to go in an disable 'verify apps by adb' in the phone's settings, and started again, and yet it still gets stuck on this first pour.
Any ideas?
Click to expand...
Click to collapse
I had lots of issues what I did by the book is the following...
Flashed stock deodex vzw rom
Flashed stock boot img
Flashed stock recovery
Made sure usb debugging was on
Made sure verifying apps was off
Made sure fastboot was off
Made sure no lock screen was selected
And boom it finally worked. Windows 8 64bit.
Okay so my first question: Is it a VERIZON One?
Second question: Did you properly install the drivers for fastboot on the phone?
1st suggestion: Add an exception in your firewall for soju.exe
2nd suggestion: open a command window in your platform tools folder of your adb installation and type adb devices to see if it comes up
Sent from my One using XDA Premium 4 mobile app
cstrife999 said:
I had lots of issues what I did by the book is the following...
Flashed stock deodex vzw rom
Flashed stock boot img
Flashed stock recovery
Made sure usb debugging was on
Made sure verifying apps was off
Made sure fastboot was off
Made sure no lock screen was selected
And boom it finally worked. Windows 8 64bit.
Click to expand...
Click to collapse
Ok maybe I missed that, where is verifying apps off?
Never mind, found it under developer options.
sanjeeva7 said:
Ok maybe I missed that, where is verifying apps off?
Never mind, found it under developer options.
Click to expand...
Click to collapse
Under security. It's a 4.2 and up thing to prevent malware from being installed on the phone.
Ok still not working.
I am on VZW with stock. Zero mods made to the phone. I just got it a few days ago. I am on the .10 version.
adb works:
C:\miniadb_m7>adb reboot bootloader
C:\miniadb_m7>fastboot devices
FA37K------- fastboot
C:\miniadb_m7>fastboot reboot
rebooting...
finished. total time: 0.044s
C:\miniadb_m7>adb devices
List of devices attached
FA37K------- device
C:\miniadb_m7>
Loaded the HTC only drivers for Windows 7. Run as admin directly from the program, and in DOS which was run as admin. At first I was getting the "WTF" error. I have disabled my antivirus and added the "soju.exe" to allow in my firewall settings. So then I rebooted. I am using the OEM cable and usb 2.0 port.
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (34/120)
Device detected.....................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
Waiting for ADB (36/120)
Waiting for device
Waiting for device
pouring (1)...........
.................................
Waiting for device
pouring (2)...........
.................................
Waiting for device
pouring (3)...........
.................................
Waiting for device
pouring (4)...........
................................
Waiting for device
pouring (5)...........
................................
Waiting for device
pouring (6)...........
................................
Waiting for device
pouring (7)...........
................................
Waiting for device
pouring (8)...........
.................................
Waiting for device
pouring (9)...........
.................................
Waiting for device
pouring (10).....
...
If you're getting the pouring (10) error, run the .08 software. that fixed it for me.
What worked for me was to right click soju.exe and run as administrator. After that it worked like a charm.
Sent from my HTC6500LVW using Tapatalk 4
Wow, 10 pours? With all these random numbers of pours I'm reading (mine was 3), I'm thinking this exploit keeps trying until it works and I imagine theres a bit of timing or trial and error involved?
skiman10 said:
What worked for me was to right click soju.exe and run as administrator. After that it worked like a charm.
Sent from my HTC6500LVW using Tapatalk 4
Click to expand...
Click to collapse
Make sure debugging is check marked every time the phone reboots during the process.
I had to manually mark it the first few times.
Sent from my HTC6500LVW using Tapatalk 2
My suggestion is to use Linux to do the process , I did it first attempt . Just make sure you sudo get adb and fastboot and you are good to go . If you don't have linux I suggest dual booting it will get the job done .
Sent from my HTC6500LVW using Tapatalk now Free
kookahdoo said:
Make sure debugging is check marked every time the phone reboots during the process.
I had to manually mark it the first few times.
Sent from my HTC6500LVW using Tapatalk 2
Click to expand...
Click to collapse
It seems when you turn that fast boot option OFF it kept USB debugging on. At least it did for me.
I'm not sure why it would make any difference, but I wiped adb and fastboot from Windows, then reinstalled both of them. After that, everything went perfectly fine, and now I just have to figure out what ROM to put on this thing.
Any suggestions for the Verizon version?
USB ports
I was having the exact same problem, dumping out to a WTF error on Pouring 1. I tried everything on the planet, but what eventually fixed it for me was switching USB ports.
Ironically, it was a USB 3.0 port that worked for me. But my tower has, easily 10 USB ports on the backside. Try different ports. That's the only change I made, and it went from that exact failure to a first try success.
MReprogle said:
I'm not sure why it would make any difference, but I wiped adb and fastboot from Windows, then reinstalled both of them. After that, everything went perfectly fine, and now I just have to figure out what ROM to put on this thing.
Any suggestions for the Verizon version?
Click to expand...
Click to collapse
I am running VANIR and liking it so far. I'm sure I'll try them all eventually. Never had much luck with PAC on any of my previous devices and Liquid was always good but lacked some features I wanted. CM is always another option as well. Whatever you pick now, you will probably change as now that we have a simple S-Off my guess is we will have a LOT more choices soon. What I'd really love to see is a Team Sourcery ROM but doubt it will happen.
I really like Blinkfeed, so I went with BoneStock.
cstrife999 said:
I had lots of issues what I did by the book is the following...
Flashed stock deodex vzw rom
Flashed stock boot img
Flashed stock recovery
Made sure usb debugging was on
Made sure verifying apps was off
Made sure fastboot was off
Made sure no lock screen was selected
And boom it finally worked. Windows 8 64bit.
Click to expand...
Click to collapse
Where did you get the stock recovery to flash?
Verizon HTC One software version & rumrunner
Prior to implementing any Rumrunner S-OFF mod, I notice that Verizon pushed a "minor" OTA upgrade last week. It might have been .8 prior to the OTA and is now showing a long string for the ID; both revs are being shown.
When I query my software on the phone now, I see: "...1.10.605.10-1.10.605.8_R2". I'm not sure what it showed prior to receiving the OTA push...
Question, which version of the software should be downloaded, at least initially? The .10 or the .8? I assume the .8_R2 implies the tweak to .8 and the .10 means the push is applied... Any recommendations?
Thanks, bj
clivusmul said:
Prior to implementing any Rumrunner S-OFF mod, I notice that Verizon pushed a "minor" OTA upgrade last week. It might have been .8 prior to the OTA and is now showing a long string for the ID; both revs are being shown.
When I query my software on the phone now, I see: "...1.10.605.10-1.10.605.8_R2". I'm not sure what it showed prior to receiving the OTA push...
Question, which version of the software should be downloaded, at least initially? The .10 or the .8? I assume the .8_R2 implies the tweak to .8 and the .10 means the push is applied... Any recommendations?
Thanks, bj
Click to expand...
Click to collapse
if i were you, i'd try .8
Aggies1288 said:
Where did you get the stock recovery to flash?
Click to expand...
Click to collapse
I provided a .zip somewhere
let me find it
http://d-h.st/sdg
use fastboot.
I recently picked up a D851 (TMobile). I rooted it, but did not replace the ROM or install a custom bootloader.
Last weekend, the phone started randomly rebooting. Watching logcat via adb showed me several random apps throwing sig11s, after which the phone would give up and reboot. Cycle repeats.
This looks like a hardware issue, as the apps that crash change on each boot cycle.
I arranged with TMobile to swap the device, but they cautioned me that the phone must be returned to an unrooted state.
I've had a hell of a time with it from here. My first try was to install the LG drivers and the PC Suite under a Windows VM, as I do not run Windows at home. Enabling USB passthrough for the phone to the VM let Windows see the phone, but the LG drivers would invariably fail with 'Device cannot start. Code 10.'. Likewise, the PC Suite couldn't find the phone.
Next step was to throw together some spare hw and install Windows 7 on that (a desparate move, to be certain. ). The LG drivers can now recognize the phone, so that's a definite plus. The LG PC Suite, though, claimed that my phone could not be upgraded. Wonderful.
Next step was to try this tutorial: http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html . I was able to get further with this method, but as it begins to flash SYSTEM, it pauses, and then dies with 'We can't communicate with Phone'. End result - I now have a soft bricked phone. On the phone, I see the port - COM41 - appear, and the usb animation starts to spin ... and after a few seconds, stops. It's at this point that Flashtool throws the Can't Connect error.
I next tried following this tutorial: http://forum.xda-developers.com/showthread.php?t=2785089 to flash a KDZ. The newer LG Flash tool used here can't create a connection to my phone for flashing.
I've run into a wall here. Any ideas on where to go next? I need to reset this phone back to a working stock state so that I can send it back.
http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/
Use this and follow video carefully. Has worked many times. Use all his links not what you have downloaded.
NOTE 4
BACARDILIMON said:
http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/
Use this and follow video carefully. Has worked many times. Use all his links not what you have downloaded.
NOTE 4
Click to expand...
Click to collapse
Also - as silly as it sounds, make certain you're using the USB cable that came with the phone. This has solved problems for a lot of people when trying to revert to stock.
etawful said:
Also - as silly as it sounds, make certain you're using the USB cable that came with the phone. This has solved problems for a lot of people when trying to revert to stock.
Click to expand...
Click to collapse
I wasn't initially, but I did switch to it last night. Still no go.
I suspect it's either the phone itself (see above: re suspected hw failure), or the PC in question (nVidia chipset on this old motherboard, and I've had more than a few problems with adb talking to phones on nVidia motherboards). I'm going to try Bacardilimon's suggestion tonight, on a PC that has *nothing* nVidia-related in it, before I throw in the towel. As it is, the failing phone needs to be back to TMO by the middle of next week, so I'm all but out of time to resolve this.
Drake Maijstral said:
I recently picked up a D851 (TMobile). I rooted it, but did not replace the ROM or install a custom bootloader.
Last weekend, the phone started randomly rebooting. Watching logcat via adb showed me several random apps throwing sig11s, after which the phone would give up and reboot. Cycle repeats.
This looks like a hardware issue, as the apps that crash change on each boot cycle.
I arranged with TMobile to swap the device, but they cautioned me that the phone must be returned to an unrooted state.
I've had a hell of a time with it from here. My first try was to install the LG drivers and the PC Suite under a Windows VM, as I do not run Windows at home. Enabling USB passthrough for the phone to the VM let Windows see the phone, but the LG drivers would invariably fail with 'Device cannot start. Code 10.'. Likewise, the PC Suite couldn't find the phone.
Next step was to throw together some spare hw and install Windows 7 on that (a desparate move, to be certain. ). The LG drivers can now recognize the phone, so that's a definite plus. The LG PC Suite, though, claimed that my phone could not be upgraded. Wonderful.
Next step was to try this tutorial: http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html . I was able to get further with this method, but as it begins to flash SYSTEM, it pauses, and then dies with 'We can't communicate with Phone'. End result - I now have a soft bricked phone. On the phone, I see the port - COM41 - appear, and the usb animation starts to spin ... and after a few seconds, stops. It's at this point that Flashtool throws the Can't Connect error.
I next tried following this tutorial: http://forum.xda-developers.com/showthread.php?t=2785089 to flash a KDZ. The newer LG Flash tool used here can't create a connection to my phone for flashing.
I've run into a wall here. Any ideas on where to go next? I need to reset this phone back to a working stock state so that I can send it back.
Click to expand...
Click to collapse
There is a link in the general thread on how to return to stock including a method using twrp. It's a sticky thread at the top I've never done the twrp method myself but it can more than likely be done without a computer. Twrp can be installed via Playstore if you don't already have it
BACARDILIMON said:
httx://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/
Use this and follow video carefully. Has worked many times. Use all his links not what you have downloaded.
NOTE 4
Click to expand...
Click to collapse
Holy hell. That site's links are absolutely infuriating. Anyone who puts each and every download link for software referenced by a howto behind separate timed appearance links that you have to ALSO enter an annoying captcha to enable should be shot out of a cannon - or, at the very least, have their howto ignored by the rest of the world.
Suffice it to say, the quality of that page doesn't give me much confidence that this will work any better than what I've tried already. Since I've already wasted a crapload of time on this project, and more on following those damned links, I'll give it a try tonight, but I'm not going to hold my breath.
Is the author of that page an XDA member? If so, please let me know who he is, so I can berate him personally. Thanks.
Toneman07 said:
There is a link in the general thread on how to return to stock including a method using twrp. It's a sticky thread at the top I've never done the twrp method myself but it can more than likely be done without a computer. Twrp can be installed via Playstore if you don't already have it
Click to expand...
Click to collapse
I'd consider doing that, except as I mentioned, the G3 in question disconnected during a run of Flashtool, rendering it without a working OS to boot to. The phone now boots straight to download mode. The good news is, it's now officially unrooted. The bad news is, it's also officially bricked until I can get an OS flash to work.
Drake Maijstral said:
Holy hell. That site's links are absolutely infuriating. Anyone who puts each and every download link for software referenced by a howto behind separate timed appearance links that you have to ALSO enter an annoying captcha to enable should be shot out of a cannon - or, at the very least, have their howto ignored by the rest of the world.
Suffice it to say, the quality of that page doesn't give me much confidence that this will work any better than what I've tried already. Since I've already wasted a crapload of time on this project, and more on following those damned links, I'll give it a try tonight, but I'm not going to hold my breath.
Is the author of that page an XDA member? If so, please let me know who he is, so I can berate him personally. Thanks.
Click to expand...
Click to collapse
OK I gonna keep it real with you. You can either enter the captcha and fix the issue or throw the phone away. Yes he is a member and for every phone that is out their he has its own page doing this for us. If you can't fix your phone with his method then it not the method but you. I have used this for many bricks. It works and it works great. Sorry if he making you do a little typing but like I said u can use his method or keep trying the other methods. Good luck
NOTE 4
BACARDILIMON said:
OK I gonna keep it real with you. You can either enter the captcha and fix the issue or throw the phone away. Yes he is a member and for every phone that is out their he has its own page doing this for us. If you can't fix your phone with his method then it not the method but you. I have used this for many bricks. It works and it works great. Sorry if he making you do a little typing but like I said u can use his method or keep trying the other methods. Good luck
NOTE 4
Click to expand...
Click to collapse
After going through the painful process of clicking his links, I found that everything I downloaded is the same thing I already had, except for Flashtool - lgg3root's is actually older. Even the TMO firmware for my phone and the dll are both exactly the same, and I checked by running md5sum on them.
But hey, it must be me. There's clearly no other technology-related cause for this issue. I obviously don't know how to follow a howto, right?
Thanks for 'keeping it real'.
Drake Maijstral said:
After going through the painful process of clicking his links, I found that everything I downloaded is the same thing I already had, except for Flashtool - lgg3root's is actually older. Even the TMO firmware for my phone and the dll are both exactly the same, and I checked by running md5sum on them.
But hey, it must be me. There's clearly no other technology-related cause for this issue. I obviously don't know how to follow a howto, right?
Thanks for 'keeping it real'.
Click to expand...
Click to collapse
See we agree.
NOTE 4
BACARDILIMON said:
See we agree.
NOTE 4
Click to expand...
Click to collapse
Not likely.
In any case, it failed again. The video he did gave me the exact same steps I followed elsewhere, and unsurprisingly, it failed with 'We can't communicate with Phone', after beginning the flash process. There is something else wrong here, though I'm not certain if the failing phone is at fault or the PC in question is causing the issue. To be crystal clear, the flash process starts, and then, at a random point during the flash, it completely stops, and Flashtool eventually gives up and throws the aforementioned error.
Any other ideas? If not, I'm going to have to try another PC to rule that out as the culprit. Sigh.
Mine gave the same error as well as couldn't communicate with server but the flash process continued running and the phone rebooted took about 3 minutes u learned not to touch any of the popups on the screen during flash and sorry I missed the part about no OS I thought you were booting to recovery... Driving while reading not the best idea
Toneman07 said:
Mine gave the same error as well as couldn't communicate with server but the flash process continued running and the phone rebooted took about 3 minutes u learned not to touch any of the popups on the screen during flash and sorry I missed the part about no OS I thought you were booting to recovery... Driving while reading not the best idea
Click to expand...
Click to collapse
Nope, the phone is definitely not doing anything - the usb animation on the G3 completely stops before Flashtool throws the error.
And damnit, quit reading while driving. You can do that later.
Moved the hdd Windows is installed on to another PC with a different chipset. After it updated drivers, I tried again. Flash proceeded partway, then died. Reset phone, Flashtool reststarted flash from scratch, flash died at 15%.
15% is interesting. While I've seen the flash die at various points, 15% is the one that was most often repeated. This tells me the failure follows the phone, not the PC - which makes sense, as the phone has a suspected RAM failure.
At this point, it appears that flashing this phone is impossible due to faulty hw. Hopefully TMO (and eventually, LG) will accept the faulty phone back with no OS, because there's no way an OS is being written to this device ever again.
Thank you for answering
yanowman said:
Thank you for answering
Click to expand...
Click to collapse
No problem. There's nothing I hate more than stumbling across a thread where the OP has the same problem I have, only to find it was never updated with the solution.
Good luck man let us know what tmobile says