Develop Bugs

I screwed up my device trying Toast's root method, please help me undo the damage!

Thanks for taking an interest in my problem and trying to help.
Here's what I've figured out. I tried doing Toast's root method for linux and the directions weren't idiot proof because I screwed them up. I've explained how far I've gotten in other threads. If that's relevant just ask and I'll explain exactly what I did.
Anyway my phone does the basics. It allows me to make phone calls, text, and look at the internet on the phone so this isn't an emergency but it I am worse off than I was before I tried to root because I can no longer use easytether.
I had no problem with easytether prior to the root attempt, and it still works when I hook it up with my wifes untampered evo. with my phone but with my wife's evo, I've never messed with that one, I have no trouble connecting with easy tether.
Some of the things I've noticed about the device since the attmept...
-I can't update to 2.2 via the OTA or any other method, my device says no updates are available.
-Simple root wasn't so simple, the phone never shut off and rebooted into boot screen like the red screen said it would in step 1.
How do I reset the device to the way it was the day it was purchased. I've got everything I need backed up. I'm ready to reset just tell me how.
Thanks.

Please?
I know it bothers people here when they think someone didn't research anything first but I really did. The problem was I'm on linux so most of the stuff I researched didn't seem to apply, not to mention I'm quite illiterate in the terminal... but working on it. I'd really like to get this phone back to stock so I can try again.
Can anyone help?

what ROM are you running? base on eclair 2.1 or froyo 2.2..
try this http://shipped-roms.com/index.php?category=android&model=Supersonic
They are the Stock Unmodified ROMs for your EVO 4G the first 3 are Eclair (2.1) and the last 2 are Froyo (2.2)
Just know that if you use any of this you will LOSE Root..
Hope it helps..
I recomend you try 1.47.651.1 first ...
Good Luck

hortstu said:
Thanks for taking an interest in my problem and trying to help.
Here's what I've figured out. I tried doing Toast's root method for linux and the directions weren't idiot proof because I screwed them up. I've explained how far I've gotten in other threads. If that's relevant just ask and I'll explain exactly what I did.
Anyway my phone does the basics. It allows me to make phone calls, text, and look at the internet on the phone so this isn't an emergency but it I am worse off than I was before I tried to root because I can no longer use easytether.
I had no problem with easytether prior to the root attempt, and it still works when I hook it up with my wifes untampered evo. with my phone but with my wife's evo, I've never messed with that one, I have no trouble connecting with easy tether.
Some of the things I've noticed about the device since the attmept...
-I can't update to 2.2 via the OTA or any other method, my device says no updates are available.
-Simple root wasn't so simple, the phone never shut off and rebooted into boot screen like the red screen said it would in step 1.
How do I reset the device to the way it was the day it was purchased. I've got everything I need backed up. I'm ready to reset just tell me how.
Thanks.
Click to expand...
Click to collapse
I bet a friend told you about root without giving you all the details, right? Haha. Ok, back to business. Rooting will make it impossible to receive ota updates. This is not a problem, because devs post rooted ota updates that you can flash manually. As far as I know, root is 100% permanent, but you don't know the goods. First of all, search wireless tether root in market it should have a green wifi icon. Second, try some custom roms and themes. I bet you will cry when you see yourself asking to go back to stock....

jadehawk said:
what ROM are you running? base on eclair 2.1 or froyo 2.2..
try this http://shipped-roms.com/index.php?category=android&model=Supersonic
They are the Stock Unmodified ROMs for your EVO 4G the first 3 are Eclair (2.1) and the last 2 are Froyo (2.2)
Just know that if you use any of this you will LOSE Root..
Hope it helps..
I recomend you try 1.47.651.1 first ...
Good Luck
Click to expand...
Click to collapse
I never got to the point where I could flash a ROM or got root. S was never off.
just in case it makes a difference.
firmware= 2.1-update1
baseband version= 1.39.00.04.26
kernel version= 2.6.29-a2443432
build#= 1.32.651.1 CL171253 test-keys
software#= 1.32.651.1
I think the rest is up to date.
I bet a friend told you about root without giving you all the details, right? Haha.
Click to expand...
Click to collapse
Actually I'm a bit of a forum junkie and as soon as I got this phone I found the android forums and have spent a ton of time there trying to maximize the utility of this device. I've done the opposite.
Ok, back to business. Rooting will make it impossible to receive ota updates. This is not a problem, because devs post rooted ota updates that you can flash manually. As far as I know, root is 100% permanent, but you don't know the goods. First of all, search wireless tether root in market it should have a green wifi icon. Second, try some custom roms and themes. I bet you will cry when you see yourself asking to go back to stock....
Click to expand...
Click to collapse
I only want to go back to stock so I can get rooted! I can't root because I can't get 2.2 so I can't use unrevoked 3.21. I can't use simple because of some problem I had with the toast linux method that seems to be screwing up everything since. I appreciate the input I hope I've explained myself better.

hortstu said:
Please?
I know it bothers people here when they think someone didn't research anything first but I really did. The problem was I'm on linux so most of the stuff I researched didn't seem to apply, not to mention I'm quite illiterate in the terminal... but working on it. I'd really like to get this phone back to stock so I can try again.
Can anyone help?
Click to expand...
Click to collapse
Use this to go back to stock: http://forum.xda-developers.com/showthread.php?t=780141

grouse130 said:
Use this to go back to stock: http://forum.xda-developers.com/showthread.php?t=780141
Click to expand...
Click to collapse
The problem is I don't think I'm rooted.I flashed pc36img.zip and never made it any further. Am I rooted. Do I need to undo this or can I do a hard reset?

grouse130 said:
Use this to go back to stock: http://forum.xda-developers.com/showthread.php?t=780141
Click to expand...
Click to collapse
OK so here's why I think I'm not rooted, when I follow step one of the detailed directions,
Power off the phone and reboot into the recovery by holding VOL DOWN + POWER until it boots to the white screen. Then select RECOVERY.
Click to expand...
Click to collapse
I get a screen with an evo, a red triangle, and a red exclamation point.
Where do I go from here?
Any direction will be immensely appreciated.

To find out if you're rooted, simply try to run an app that requires root access. Try downloading Titanium back up, and as soon as you install it, hit the "Problem?" button on the lower right and install busybox. One of the first lines on the main screen of the app says:
Root access => OK (Busybox 1.16.0 from app)
If it does not say "root access => OK" and you cannot use the app, then you don't have root.
hortstu said:
OK so here's why I think I'm not rooted, when I follow step one of the detailed directions,
I get a screen with an evo, a red triangle, and a red exclamation point.
Where do I go from here?
Any direction will be immensely appreciated.
Click to expand...
Click to collapse
From this screen, if you hold volume up and press the power key, it will take you to the hboot menu.

Have you flashed a recovery img?
Sent from my PC36100 using XDA App

rugedraw said:
From this screen, if you hold volume up and press the power key, it will take you to the hboot menu.
Click to expand...
Click to collapse
OK so I'm at the "hboot" screen.
Code:
Android system recovery <2e>
Use volume...
click power key...
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
Then in yellow, below the device picture, triangle, and exclamation I have
Code:
E: Can't open /cache/recovery/command
Not sure where you're steering me rugedraw but thanks for the help...

hortstu said:
OK so I'm at the "hboot" screen.
Code:
Android system recovery <2e>
Use volume...
click power key...
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
Then in yellow, below the device picture, triangle, and exclamation I have
Code:
E: Can't open /cache/recovery/command
Not sure where you're steering me rugedraw but thanks for the help...
Click to expand...
Click to collapse
To check if you are rooted. Download "Terminal Emulator" on the market. If it starts up and when it is done booting, you get a # prompt, you are rooted. If you get a $ prompt. You are not rooted.
You also do not have a custom recovery installed on your phone (the recovery screen you have is the stock one). Try finishing up the process by doing Toast part II -- http://forum.xda-developers.com/showthread.php?t=701835&highlight=Part-2

To find out if you're rooted, simply try to run an app that requires root access. Try downloading Titanium back up, and as soon as you install it, hit the "Problem?" button on the lower right and install busybox. One of the first lines on the main screen of the app says:
Root access => OK (Busybox 1.16.0 from app)
If it does not say "root access => OK" and you cannot use the app, then you don't have root.
Click to expand...
Click to collapse
Finally went back and checked on the titanium backup download. When I first opened it I got the message that it didn't have root access. So I clicked on "problems?" and installed busy box. Now it says,
Root access v=> OK (BusyBox 1.16.0 from app
Click to expand...
Click to collapse
Plus some other stuff... so I guess I have root but not S-off.
hecklbrg said:
To check if you are rooted. Download "Terminal Emulator" on the market. If it starts up and when it is done booting, you get a # prompt, you are rooted. If you get a $ prompt. You are not rooted.
Click to expand...
Click to collapse
Should I still do this or is the info from titanium backup enough?
You also do not have a custom recovery installed on your phone (the recovery screen you have is the stock one). Try finishing up the process by doing Toast part II -- http://forum.xda-developers.com/showthread.php?t=701835&highlight=Part-2
Click to expand...
Click to collapse
Yes I tried doing that but like I said I'm on a linux computer and had some trouble with the steps. What I'd really like to do is just go back to stock and try rooting with unrevoked 3.21.
My concern is that selecting factory reset from the hboot screen won't take me back there. If it did I could probably get the 2.2 update over the air, I suppose now I have to worry about getting this other update that everyone is talking about at the same time. Can I get 2.2 and avoid the update that came out last night? How.
Will a factory reset get me back to stock? I've already got everything backed up that matters.
Thanks for all the help.

OK...I think this should work for you:
go here and download the file on the page:
WRONG FILE>>>WILL FIND THE CORRECT ONE.
rename it update.zip and put it on the root of your SD card.
Boot into HBOOT then into recovery and go to apply update.zip -- choose the file you put on there.
let it run and you should have the stock non-rooted version of the 1st software release from sprint. from there you can update it as far as you want to root it the method of your choice.

hecklbrg said:
OK...I think this should work for you:
go here and download the file on the page:
WRONG FILE>>>WILL FIND THE CORRECT ONE.
rename it update.zip and put it on the root of your SD card.
Boot into HBOOT then into recovery and go to apply update.zip -- choose the file you put on there.
let it run and you should have the stock non-rooted version of the 1st software release from sprint. from there you can update it as far as you want to root it the method of your choice.
Click to expand...
Click to collapse
Thanks hecklbrg,
I assume since I'm half rooted a factory reset won't get me there?
I'll wait for the link to that file...

if you put this on your card and run it from HBOOT...you will get a rooted version of the latest sprint OTA with a custom recovery and the latest radios.
http://forum.xda-developers.com/showthread.php?t=791019
I'm still looking for a non-rooted version to run...but I would think this would work for you to get you the latest OTA in a rooted form.
Second thing is that I don't think you really screwed up your root process. You have only done part of the process and haven't installed a custom recovery. If this works for you, it will give you a custom recovery and you will have a fully rooted phone.

Hecklberg is right. I don't think you even need to rename it update.zip. If its a
pc36img.zip your hboot will automatically scan for it, find it and run it when you put it on your SD card and open hboot.
Also consider, I rooted my phone without any computer, all done from my Evo, using fastRX8 thread in here about how to root for newbies. It involves putting the files on your SD card, then installing terminal emulator from the market and typing a few commands to install flash_image, then custom recovery. You are root, just don't have flash image, custom recovery, and superuser yet. Basically toast part 2, it can be done with no computer, but same files.
Read real quick Whitslack thread on rooting, and fastrx8 thread, even just the 1st post, and it will make sense to you where you're at and what's left to do. You'll see how close you are.
Once root, and superuser installed, you won't need easy tether, Android wired tether is what I use (doesn't require installing any software on the host pc)
(Actually, if you use the threads I mentioned method, don't use the recovery amonra1.7.0.2, there's a newer one to download, its at 1.8 now, just Chang the recovery file name you type in terminal app accordingly-don't worry, it won't go thru if you do it wrong, but won't 'break' anything)
Hope any of this helps, but yeah, hecklberg is right too, just different methods. One requires no computer.
And yeah, with the devs around here, you don't need any Sprint OTAs, most of the time, they seem to have em available before Sprint releases them. These guys are good.

scottspa74 and hecklbrg,
Thanks for the help. I havent had time to look at this or act on it over the last 24 hours but I will try to get to it tonight and let you know how it works. Sounds like you've gotten me out of the woods.
Thanks again.

I think it is $ if you are rooted and# if you aren't because I know I'm rooted and it shows money signs, unless terminal emulator is messed up,i have nvr used it.
hecklbrg said:
To check if you are rooted. Download "Terminal Emulator" on the market. If it starts up and when it is done booting, you get a # prompt, you are rooted. If you get a $ prompt. You are not rooted.
You also do not have a custom recovery installed on your phone (the recovery screen you have is the stock one). Try finishing up the process by doing Toast part II -- http://forum.xda-developers.com/showthread.php?t=701835&highlight=Part-2
Click to expand...
Click to collapse
Sent from my netarchy_toast, froyo beast of a machine evo!

evohack99 said:
I think it is $ if you are rooted and# if you aren't because I know I'm rooted and it shows money signs, unless terminal emulator is messed up,i have nvr used it.
Sent from my netarchy_toast, froyo beast of a machine evo!
Click to expand...
Click to collapse
Nope you are incorrect my friend.. try typing " su " on the terminal emulator see if you get the "#" ... # ==> Root and $ ===> User(I Think) But I know for sure "#" is root access

[GUIDE] Forcing update 2.2.1 and re-rooting after downgrading

Force update + Re-Root Instructions!
Disclaimer: This is aimed at those of us who used travisjames' method of downgrading to stock. brian6685 confirmed this WILL work with a new phone running stock. I am not responsible for you bricking your phone, but there have been no reports of any bricking with this that I am aware of.
I don't know if many of you are running a software number starting with 1.13, but if you are before you follow these instructions you MUST first follow the "downgrade" instructions (actually an upgrade for you)
The downgrade post can be found here.
First: Forcing the Update
1. download this file save this as PD15IMG.zip
* This is not the same file as in the downgrading instructions!
2. reboot into bootloader and flash this update
* for me Wi-Fi stopped working at this point and my 3g/4g was acting funky
3. This is going to appear as if no updates were made when you reboot, but you will now be able to follow the root instructions in this thread perma root guide to get S-OFF
4. download Clockwork Mod, and The OTA
5. install the clockwork recovery (to do this because my 3g/4g was acting up I dialed *#*#INFO#*#* and in the phone info settings I set it to GSM only) then flash the update and you will have 2.2.1 and full working WIFI... also at this point if you did set it to GSM Only go back in and change it back to WCDMA preferred
**The big problem is wifi will not work after step 2 which is why I included the web downloads for clockwork rom... I used ADB to install them, but if you have astro or something similar you can get them installed that way too... Another way to fix this is to download the broadcom kernel module and insmod it... the reason for this is when you do the update off of the img it's just loading the system files and not running the patches against them. ie kernel gets updated but modules aren't applied
-----------------------------------------------------------------------------
Second: Re-Rooting
This was solved by following Grankin's instructions for fixing root and su after a flash... This requires uninstalling superuser and visionary then following thise steps. The referenced file is here and the original post about this is here
1. Using Explorer navigate to the root of your sdk. Hold shift and right mouse click on the tools folder. Select "Open command window here".
2. Type "adbbat" + enter. Wait till the batch file finishes.
3. Disconnect your phone from the PC.
4. Open terminal emulator on the phone and type "/data/local/rage" + enter. Wait for "Forked XXXXXXXX children" to appear and then close the terminal.
**Just ran through this again... the program you should use is "Android Terminal Emulator" the one labeled just "Terminal Emulator" repeatedly force closes...
5. Start terminal back up. It should force close.
6. Start terminal back up, again. This time it should stay open and you should have a "#" prompt instead of a "$" prompt. Then type "/data/local/temp.sh.
7. When the script finishes run /data/local/rage again and sit tight. The phone should start acting weird and do a soft reboot. Then right after everything loads it should do a hard reboot. After the hard reboot reboot and check S.(If it doesn't do the two reboots just reboot into hboot yourself after rage finishes with the "forked xxxxxxxx children" message.
-----------------------------------------------------------------------------
**When I did this on step 4 I had to go into settings>applications>manage applications>Terminal Emulator and Force Stop because it was not force closing, but when I did I had the "#" prompt when I reopened terminal then it worked as advertised
**If you experience force closes of sense after updating to 2.2.1 run the fix permissions from clockwork recovery and it should fix it. If it is still happening do a factory reset and continue from there.
**For you linux folks here's a little script to replace the adbbat.bat file. adbbat.sh I tested this and it moves all the files and chmods properly.
Credit goes to travisjames for figuring out how to downgrade to stock and grankin01's post about using rage to root when visionary is having issues.

Great find man! Hopefully this will work on all the pre-OTA devices and everyone can have root utopia!
My MyGlacier 4G MINE!!!

I'd love to try this, but I don't see where the OTA plays a part here? May give it a shot when I get off work tonight.

grankin01 said:
Great find man! Hopefully this will work on all the pre-OTA devices and everyone can have root utopia!
My MyGlacier 4G MINE!!!
Click to expand...
Click to collapse
Thanks man, I'm here to help if anyone has questions... I spent about a week waiting for someone smarter than me to figure it out... I have a little linux experience (I run a few servers for fun), but didn't think I would be able to figure this out... turned out it really wasn't too hard... I was about to try the rage thing when I came home today, but someone beat me to it and posted a link to your post, and that was the last piece of the puzzle.
I'd love to try this, but I don't see where the OTA plays a part here? May give it a shot when I get off work tonight.
Click to expand...
Click to collapse
the first file you're downloading is actually the image files from the OTA, this updates some files but doesn't do a full system patch. The thing it does update is the kernel, which allows you to use the original S-OFF method. Once you're S-Off you can install clockwork and flash the actual OTApkg.zip through clockwork's recovery. Then you have to reroot using rage because for some reason visionary thinks it's already rooted and su won't work...

Thanks alot man! I have a pre-ota device and im gonna give it a shot in a few minutes to see if it works. Ill let you know soon!

I am on a pre-ota device, i followed the instructions, and now I am s-off wow thanks alot man! Im gonna do the rest and get clockwork installed and install the update

Okay so everything went successfully. Wifi working again and everything works. I am on the second part now to re-root. I am using linux..... that adbbat is for windows...... any suggestions?

brian6685 said:
Okay so everything went successfully. Wifi working again and everything works. I am on the second part now to re-root. I am using linux..... that adbbat is for windows...... any suggestions?
Click to expand...
Click to collapse
VirtualBox? ... I kid I kid . Just open up adbbat in a text editor and run the commands by hand I'd say.

brian6685 said:
Okay so everything went successfully. Wifi working again and everything works. I am on the second part now to re-root. I am using linux..... that adbbat is for windows...... any suggestions?
Click to expand...
Click to collapse
I can either wip up a script or you can "edit" the batch file and use the commands inside it manually in your shell.
Edit: Genocaust beat me to it.
My MyGlacier 4G MINE!!!

grankin01 said:
I can either wip up a script or you can "edit" the batch file and use the commands inside it manually in your shell.
Edit: Genocaust beat me to it.
My MyGlacier 4G MINE!!!
Click to expand...
Click to collapse
Oh, i see Ill do it thanks lol

Okay, everything is done and everything works s-off and superuser working correctly. Man ive been waiting for this lol. Thanks alot guys this was a huge help! You can put in the OP that it works for phones pre-ota, because i can confirm

brian6685 said:
Okay so everything went successfully. Wifi working again and everything works. I am on the second part now to re-root. I am using linux..... that adbbat is for windows...... any suggestions?
Click to expand...
Click to collapse
the syntax should be the same... just add #!/bin/bash to the top and I bet it will work

stupid question but how do you flash through bootloader?

PolishDude said:
stupid question but how do you flash through bootloader?
Click to expand...
Click to collapse
The first file you download which is called manualota.zip you need to rename it PD15IMG.zip and place it on your sdcard. When bootloader starts it will automatically look for a file with this name and flash from it.

HTC Sense
Hey guys dumb question, im new to android. I like adroid so far, but is flashig the same as Windows Phone? Hold down (Power) Button + Vol Down to enter flash mode. Oh and this phone is cool, but how can i get the actual HTC Sense i dont like My sense, its to girlee.
Thanks in advance.

Is their a way I can force 2.2.1 update without rooting?
Sent from my HTC Glacier using XDA App

hopefully we now have a way for ppl without the ota to update and root maybe we will now get some rom devolopment !!!!!!!!!! thank u for this cant wait for a vanilla android rom.shouldnt be to long now everyone can have root access

cdw9800 said:
Is their a way I can force 2.2.1 update without rooting?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
you won't have root if you follow the force update method and not the re-rooting instructions, but if you do decide to root later visonary won't work you will have to use the rage method

Working on pre-OTA
Just would like to say thank you very much for this guide and confirm that it is working on pre-OTA.
Thank you!

Ok stupid question, after this step:
"3. This is going to appear as if no updates were made when you reboot, but you will now be able to follow the root instructions in this thread perma root guide to get S-OFF"
Should we just have S-OFF, and therefore need to use temproot to install clockwork and such, or should we have S-OFF and permaroot
edit: Nvm, the answer to the above is you should have S-OFF and Permaroot at this step, also I'm a complete dink...you shouldn't even need root to install clockwork, it's just a regular apk. It appears you CANNOT use VISIONary R12 for this, you have to use R11.

how to fix The dead android bot with error when enter recovery?

hello
i have rooted the device using the "1 CLICK ROOT TOOL" and now i have the dead android bot with error when i enter recovery.
i have tried the "fastboot erase cache" command at fastboot mode but it did not help
is their a way to fix it?

Try pressing Volume + key and Power. Don't hold just press. It might take a few goes to get it right. I had the same problem. That means that the update you have downloaded (saved on your system) fails to install.

hello and thanks
i can enter recovery by pressing the keys. this is not the issue
its just that i want to completely solve the problem

koby058 said:
hello and thanks
i can enter recovery by pressing the keys. this is not the issue
its just that i want to completely solve the problem
Click to expand...
Click to collapse
Awh sorry, I thought you can't get into recovery.
Try sideloading the stock Firmware. Go to official ASUS website and download it from there. It's about 1 GB. On this website you can find instructions on how to do it. http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596 Section 3.2)
After that you can download OTA updates and install them using method described here http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835, "Steps to Apply OTA manually".
OTA can be downloaded from there (look at the later posts for newer OTA) http://forum.xda-developers.com/zenfone2/general/ota-links-stock-rom-t3093999
I had a very similar problem few days ago. That solved it. Had a similar problem a few days ago coz I messed up my build.prop

hello
i have already did a "adb siedeload" for the stock rom downloaded from the asus web site but the issue remain.
also i downloaded the latest ota, and "adb sideloaded" them as well. it worked flawlessly .
but the small thing with the recovery is annoying.
i thinking about looking inside tmp directory and delete something called "last update"
what do you say?

koby058 said:
hello
i have already did a "adb siedeload" for the stock rom downloaded from the asus web site but the issue remain.
also i downloaded the latest ota, and "adb sideloaded" them as well. it worked flawlessly .
but the small thing with the recovery is annoying.
i thinking about looking inside tmp directory and delete something called "last update"
what do you say?
Click to expand...
Click to collapse
You're not understanding because the information he gave you is slightly wrong. When you try to enter stock recovery it will ALWAYS say installing update and pop up an error Android bot. It's not about having some update data somewhere that fails to install properly. It will ALWAYS do that. That's normal.

rlaw said:
You're not understanding because the information he gave you is slightly wrong. When you try to enter stock recovery it will ALWAYS say installing update and pop up an error Android bot. It's not about having some update data somewhere that fails to install properly. It will ALWAYS do that. That's normal.
Click to expand...
Click to collapse
Owh, this is embarrassing. I was playing with it a lot and I was kind of sure that if you have a working installed update, which is the same as a zip of an OTA update you have on an SD card it will skip installing the update and go to recovery without an error, but I was very very wrong. I'm very sorry for missleading you, and I've learned something new. Thank you.

NiKiToS-04 said:
Owh, this is embarrassing. I was playing with it a lot and I was kind of sure that if you have a working installed update, which is the same as a zip of an OTA update you have on an SD card it will skip installing the update and go to recovery without an error, but I was very very wrong. I'm very sorry for missleading you, and I've learned something new. Thank you.
Click to expand...
Click to collapse
No worries, I've made the same mistake before. We've all been there, still learning new things about this phone after months of using it!

ok let me tell why i begin asking about it.
when i just got the phone i update all of the ota updates and after that i rooted it with "1 CLICK ROOT TOOL" .
two days ago i receive tha 2.20.40.58 ota . i downloaded and install but the instalation failed .
so i unroot it with "1 CLICK ROOT TOOL" and then i checked for update . but there was no update.
so i assumed the problem is because of the recovery issue.
the qustion is why i cannot install ota automatically ?

koby058 said:
ok let me tell why i begin asking about it.
when i just got the phone i update all of the ota updates and after that i rooted it with "1 CLICK ROOT TOOL" .
two days ago i receive tha 2.20.40.58 ota . i downloaded and install but the instalation failed .
so i unroot it with "1 CLICK ROOT TOOL" and then i checked for update . but there was no update.
so i assumed the problem is because of the recovery issue.
the qustion is why i cannot install ota automatically ?
Click to expand...
Click to collapse
The 2.20.40.58 OTA was bugged and pulled from release. Just flash the full stock 2.20.40.59 firmware available from ASUS site and stop modifying your phone if you want to remain trouble-free with OTA updates. Or if you choose to continue to root and tinker with your phone accept that some things might get broken.

IIIIII'm stuck!

Long story short - Bought an LG D851 off Swappe. It came with CM13. I've been sticking nightlies on it. Currently on 2/14. I tried to put 2/18 and found that TWRP wasn't working - it hangs on TWRP Splace. Then I noticed SuperSU wasn't on the phone. So I installed it. Can't update the binaries. Looks like I don't have root.
Used LG Flash tool and flashed D85120E_00.kdz. Part way through, I get an error that the software cannot communicate with the server and it asks if I want to abort. I let it continue.
The phone reboots, I get the "Android is updating 1/196", etc. After which, it reboots, I get the boot jingle, and then it holds on the T-Mobile screen. I've tried flashing the KDZ a few times with the same result.
So now, I humbly, yet again, ask for help.
The endgoal here, is to have a working ROM with BT and WiFi working. I really don't care what it is at this point. Marshmallow is nice. Lollipop is okay. Whatever. I just need a working phone.
Thanks in advance, as always.

mdphoenix said:
Long story short - Bought an LG D851 off Swappe. It came with CM13. I've been sticking nightlies on it. Currently on 2/14. I tried to put 2/18 and found that TWRP wasn't working - it hangs on TWRP Splace. Then I noticed SuperSU wasn't on the phone. So I installed it. Can't update the binaries. Looks like I don't have root.
Used LG Flash tool and flashed D85120E_00.kdz. Part way through, I get an error that the software cannot communicate with the server and it asks if I want to abort. I let it continue.
The phone reboots, I get the "Android is updating 1/196", etc. After which, it reboots, I get the boot jingle, and then it holds on the T-Mobile screen. I've tried flashing the KDZ a few times with the same result.
So now, I humbly, yet again, ask for help.
The endgoal here, is to have a working ROM with BT and WiFi working. I really don't care what it is at this point. Marshmallow is nice. Lollipop is okay. Whatever. I just need a working phone.
Thanks in advance, as always.
Click to expand...
Click to collapse
Ouch!!! Read my CM13 post...you don't need SuperSU anymore (CM13 has root built in)--I had the same problem a while back--fixed it by flashing the old factory version on the phone & then used Purple Drake to root it & then installed CM13...Was a HARD lesson for me.
Upshot---No SuperSU needed--No BusyBox needed on CM13. If you are used to the old way of doing things--you'll get B0rked big time.
Luck to you!!!!

debianmain1 said:
Ouch!!! Read my CM13 post...you don't need SuperSU anymore (CM13 has root built in)--I had the same problem a while back--fixed it by flashing the old factory version on the phone & then used Purple Drake to root it & then installed CM13...Was a HARD lesson for me.
Upshot---No SuperSU needed--No BusyBox needed on CM13. If you are used to the old way of doing things--you'll get B0rked big time.
Luck to you!!!!
Click to expand...
Click to collapse
I guess trying to push the SuperSU binaries is what effed up TWRP?
I'll check out your CM13 post. But the issue I have is that I can't flash a factory version with LG Flash Utility. I mean, it does, but now it just sits on the Tmobile splash.
Hopefully your post will show me something I missing.
@debianmain1 is this the post you're talking about? http://forum.xda-developers.com/showpost.php?p=65432245&postcount=158
I tried that DD command to no avail last night. I tried everything I could find before reaching out to everyone for help.

mdphoenix said:
I guess trying to push the SuperSU binaries is what effed up TWRP?
I'll check out your CM13 post. But the issue I have is that I can't flash a factory version with LG Flash Utility. I mean, it does, but now it just sits on the Tmobile splash.
Hopefully your post will show me something I missing.
@debianmain1 is this the post you're talking about? http://forum.xda-developers.com/showpost.php?p=65432245&postcount=158
I tried that DD command to no avail last night. I tried everything I could find before reaching out to everyone for help.
Click to expand...
Click to collapse
Yes--the SuperSU binaries B0rked my install real good ( as I understand it--2 different types of SU installed B0rks everything )..... And with CM13, you have to allow ADB & apps to have root. I've been modding phones for years now & CM13 threw me under the bus until I learned what to do... I use to ALWAYS root, install BusyBox & SuperSU---not with CM13
Ya--that won't help you I'd look up fastboot commands & try to flash it that way--sounds like you are stuck in a startup bootloop. I did see some info online about starting the G3 in fastboot--I had a very hard time getting my G3 fixed. Do you have a Linux computer to use? It's easier to work with some of the diag stuff with Linux.

debianmain1 said:
Yes--the SuperSU binaries B0rked my install real good ( as I understand it--2 different types of SU installed B0rks everything )..... And with CM13, you have to allow ADB & apps to have root. I've been modding phones for years now & CM13 threw me under the bus until I learned what to do... I use to ALWAYS root, install BusyBox & SuperSU---not with CM13
Ya--that won't help you I'd look up fastboot commands & try to flash it that way--sounds like you are stuck in a startup bootloop. I did see some info online about starting the G3 in fastboot--I had a very hard time getting my G3 fixed. Do you have a Linux computer to use? It's easier to work with some of the diag stuff with Linux.
Click to expand...
Click to collapse
I can always fire up an Ubuntu flash drive if necessary. I'll get working on Fastboot.
Thanks again!
@debianmain1 Hmmm, Fastboot doesn't seem to be functional. I've got download mode. Can I push something to it that way?

I managed to get somewhere yesterday. I tried flashing D85120e_00.kdz and it failed again. I got the "cannot communicate with server" error, then it rebooted and tried running initial setup and failed.
So I tried flashing D85110C_00.kdz. Much to my surprise, it worked! So I ran through initial setup and got the phone working to make sure all was well. I rebooted and got the Red 2. So now here I am. Guides show that I should be able to put it in download mode and reload factory firmware again. But all I get is the "Download Mode" graphic. It never switches over to the updating mode with the circular arrows. I fear the worst at this point, but I really don't know enough about the LGs to diagnose my own doom just yet.

Someone on Reddit pointed me in the direction of Board Diag. Unfortunately it doesn't appear to work on D851. Running out of options. Looks like it'll end up being an expensive learning experience.

T-Mobile LG G3 D851 30D Marshmallow 6.x is Here!

Finally :good:
D851 30D KDZ + Flashable ZIPs + All IMGs (Marshmallow!!)
discuss...

Thanks

Has this been tested? I'm about to download it but I want to be safe first.

Stupid question how do you flash a kdz?

I will wait for the the Zip files... I have never used KDZ before and I don't wanna lose TWRP.
Enviado desde mi LG-D851 mediante Tapatalk

tjsooley said:
Stupid question how do you flash a kdz?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2785089
imrock666 said:
I will wait for the the Zip files... I have never used KDZ before and I don't wanna lose TWRP.
Enviado desde mi LG-D851 mediante Tapatalk
Click to expand...
Click to collapse
You'll for sure loose TWRP and root. However, I think other models have root available for them, they should work with this too.
I'm going to go ahead and flash... I'll report anything I see on it.
Also, @autoprime, how the hell do you even find these anymore? I haven't been able to get them ever since the LG Firmware Twitter account was taken down

mjoecarroll said:
You'll for sure loose TWRP and root. However, I think other models have root available for them, they should work with this too.
I'm going to go ahead and flash... I'll report anything I see on it.
Click to expand...
Click to collapse
@mjoecarroll
Please let us know how flashing D85130d_00_0404.kdz went for you?
Also.. was root was easily regained?
Thanks!

AndroidUzer said:
@mjoecarroll
Please let us know how flashing D85130d_00_0404.kdz went for you?
Also.. was root was easily regained?
Thanks!
Click to expand...
Click to collapse
I'm having the same issues I always have with flashing from PC... At least for me, if you let Windows install different drivers (or you installed different LG drivers) it won't work right. I'm trying to uninstall drivers until I can figure out which one to use.
Maybe figured it out from following this, but I need to figure out which driver I am supposed to install... There's so many of them it's hard to know which one is the right one.
At first it couldn't even find the device. Now it gives me an error that it can't connect to server and stops. People are saying to let it keep going when it says that but even that doesn't work for me... Hmmm...

Can I root it? I don't want T-Mo junk on my phone

There's a good chance I may need to go back to stock first before I flash it. If anyone else on Fulmics (4.1 if it matters) can get it to flash in either LGUP or LG Flash Tool, reply to this and tag me please.
I'll keep trying... I'm free till about 1.

nice, someone can give md5 or sha1 of 30d, thanks xD

Hashes
josegalre said:
nice, someone can give md5 or sha1 of 30d, thanks xD
Click to expand...
Click to collapse
Here's what came down the pipe for me...
D85130d_00_0404.kdz
1.11GB
CRC32: C505EA89
MD5: A3D04DF6FA1E964BD10B5E2AE59041AE
SHA-1: 864B7721F730970DF198D12D15A6CEB3FBEDBA2D

Just flashed and has booted up. Will tell if I have any issues or if I can root it/install TWRP.
You must use LGUP if you are on MM. Install the LG drivers from this post.
Next, click here. Download the files. Install the 8974 driver first. Then install LGUP.
Make sure you have ADB enabled and plug your phone into your computer. Do a quick ADB Devices check. If it comes back with nothing, you need to install the ADB drivers. If it says unauthorized, check your phone for an ADB message. If there's nothing there, run adb version. If it does not report back that it is version 1.0.32 (or newer), you need to upgrade it.
Run LGUP. On most ROMs, you should see your device pop up along with the model number there. If not, follow the instructions at the bottom here.
Assuming you got this far, click the device. Press the UPGRADE button then click under File Path next to BIN File. Press the ... button and locate your KDZ. After it is selected, DO NOT PRESS START. Instead, exit out of LGUP and restart it. After clicking your device again, the KDZ file should still be listed under the file path. Great. Now, click REFURBISH instead of UPGRADE. Then you can press start.
IF YOU'RE DEVICE SHOWS UP AS UNKNOWN:
Download Root Browser. Run it andallow it to download the utilities. Grant it root access. Go to /system and click on build.prop and choose RB Editor or whatever it is called to edit it.
Somewhere in that file near the bottom, you will find this:
Code:
ro.lge.swversion_arb=
change it to
Code:
ro.lge.swversion_arb=D851XXX
Change XXX to whatever your SW version is (on Fulmics it is 30c). I do not know if every ROM has this, but at least Fulmics does.
Next, look for this farther down:
Code:
ro.lge.swversion=
ro.lge.swversion_short=
Whatever is after each = on that line, delete it. Change it to the following:
Code:
ro.lgeswversion=D851XXX
ro.lge.swversion_short=VXXX
Once again, XXX is your current SW version. Save the file and reboot. Run LGUP again and the device should show up as D851. Go back up and follow the instructions above.
Edit:
Also, the Prox sensor is working perfectly too - no more problems with bad sensor like on Fulmics.

AndroidUzer said:
Here's what came down the pipe for me...
D85130d_00_0404.kdz
1.11GB
CRC32: C505EA89
MD5: A3D04DF6FA1E964BD10B5E2AE59041AE
SHA-1: 864B7721F730970DF198D12D15A6CEB3FBEDBA2D
Click to expand...
Click to collapse
same for me, thanks by confirming the sums xD

can someone pull and post the modem / baseband?

updated BUT ...
hi i have done updating to marshmallow, its super fast and bugles, but sadly i lost root and twrp
i request to please is there any way to get back the root and twrp for marshmallow?

MM Installation
shariq3598 said:
hi i have done updating to marshmallow, its super fast and bugles, but sadly i lost root and twrp
i request to please is there any way to get back the root and twrp for marshmallow?
Click to expand...
Click to collapse
How did you installed it ? (Steps) Thnks

Single bug: I don't know what caused it, but system froze at one point. Screen was unresponsive but touches were being seen. It drained a bit of my battery (even while plugged into a QC charger).
HOW TO INSTALL TWRP AND (TEMP) ROOT:
On your device, download Kingroot, TWRP, and finally SuperSU. (SuperSU is not really needed now but will be once perma-root is found).
Install Kingroot. Run it and the app will say that it cannot confirm if you can be rooted. Tell it to try anyway and it will be successful.
Next, connect your phone to your PC, go to ADB, and type the following commands:
Code:
adb shell
$su
#dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
#reboot recovery
TWRP should boot up. At this point, install the SuperSU zip just for safe measures.
I don't know why Kingroot won't permaroot. I'm working to see different ways to get it.

mjoecarroll said:
Single bug: I don't know what caused it, but system froze at one point. Screen was unresponsive but touches were being seen. It drained a bit of my battery (even while plugged into a QC charger).
HOW TO INSTALL TWRP AND (TEMP) ROOT:
On your device, download Kingroot, TWRP, and finally SuperSU. (SuperSU is not really needed now but will be once perma-root is found).
Install Kingroot. Run it and the app will say that it cannot confirm if you can be rooted. Tell it to try anyway and it will be successful.
Next, connect your phone to your PC, go to ADB, and type the following commands:
Code:
adb shell
$su
#dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
#reboot recovery
TWRP should boot up. At this point, install the SuperSU zip just for safe measures.
I don't know why Kingroot won't permaroot. I'm working to see different ways to get it.
Click to expand...
Click to collapse
Quick question... if my only intention of rooting is to enable the adoptable storage option as per this guide:
http://forum.xda-developers.com/lg-g3/general/mod-adoptable-storage-function-d85530b-t3293039
Would the temp root work fine for that?
Thanks!

rubejb said:
Quick question... if my only intention of rooting is to enable the adoptable storage option as per this guide:
http://forum.xda-developers.com/lg-g3/general/mod-adoptable-storage-function-d85530b-t3293039
Would the temp root work fine for that?
Thanks!
Click to expand...
Click to collapse
Nope. The system would fix itself on boot.
Alternatively, Autoprime just posted flashable zips to get full root.
http://forum.xda-developers.com/tmo...ock-d851-30d-kdz-flashable-zips-imgs-t3367371