Database Info

[Q] Nexus S 4G won't boot past Google Screen!!

I tried rooting my phone, but when I flashed CWM my Nexus S stopped booting... it freezes on the Google screen in the intro. I can boot into Fastboot, and cwm, but I cant connect the Internal memory to the computer without it booting like it is supposed to. Does anybody know of anything I can do to fix my phone and bring it back to stock??

There are guides for returning to stock stickied in the Nexus S 4G Android Development forum.
Before you do that though, try flashing a different recovery, like the one linked to here or here.
Btw, which guide did you use? You're not the first person to have this problem, and it's really bugging me (though probably not as much as it's bugging you :-o).

Maximilian Mary: I tried to post the link, but since I'm a new member I have to wait 8 posts before I can post a URL.... :/
I will try a different recovery, but how would I flash a rom if I can connect my phone via usb mount?

deadzunehd said:
Maximilian Mary: I tried to post the link, but since I'm a new member I have to wait 8 posts before I can post a URL.... :/
Click to expand...
Click to collapse
What's the title of the thread?
.
I will try a different recovery, but how would I flash a rom if I can connect my phone via usb mount?
Click to expand...
Click to collapse
I'm a little out of my depth here, but I think it's
fastboot flash system system.img.
You don't need to put the rom image on the sdcard. Just put it in the same folder as fastboot.

It was titled "How to Root Nexus S!"
And I will try to flash recovery and try that rom command, thank you )

deadzunehd said:
It was titled "How to Root Nexus S!"
And I will try to flash recovery and try that rom command, thank you )
Click to expand...
Click to collapse
Hmmm. I can't find that exact title. Could you pm me the link?

deadzunehd said:
thank you )
Click to expand...
Click to collapse
There's a button for that.

I got the link. Thanks. I looks like you flashed a boot image that is incompatible with your phone. That guide was for the T-Mobile Nexus S. (Why they're screwing with the boot.img to begin with, I really don't understand.)
Download the attached file, and unzip it to the same folder as fastboot. The md5 sum is d4a9508f9321eb25df3383f00f571e8b. Then
Code:
fastboot flash boot boot.img
You'll probably also want to use one of the recoveries listed above to
Code:
fastboot flash recovery recovery.img
, but leave system alone for now. Flash that only as a last resort.

deadzunehd said:
I tried rooting my phone, but when I flashed CWM my Nexus S stopped booting... it freezes on the Google screen in the intro. I can boot into Fastboot, and cwm, but I cant connect the Internal memory to the computer without it booting like it is supposed to. Does anybody know of anything I can do to fix my phone and bring it back to stock??
Click to expand...
Click to collapse
I had this problem after flashing the wrong ROM onto my phone. I got the phone back to stock using ODIN.
My thread can be found here
http://forum.xda-developers.com/showthread.php?p=14172335#post14172335
hope it helps

Acnescar said:
I had this problem after flashing the wrong ROM onto my phone. I got the phone back to stock using ODIN.
My thread can be found here
http://forum.xda-developers.com/showthread.php?p=14172335#post14172335
hope it helps
Click to expand...
Click to collapse
OMG!! im having the same issue. could you please post the link for ODIN so i can return to stock and take it from there please? I rely on my phone so much and i need it asap thank you.

same problem with me.
but in my case, the phone not only freeze after the google logo before boot. I tried several times to pull the battery and start the phone again, it took several times until the phone can boot normally again.
After that, my nexus s can work as usual. but it only takes 3-4 hour until it freeze/hangs or reboot automatically and show image of green robot lay down with red alert triangle...
sometimes I noticed all application force closed like gmail, gtalk, etc. (its a basic apps instead of 3rd party app)
History :
- root GB 2.37 using superoneclick
- upgrade OTA to ICS 4.04
- problem happens
- root using guide : nexusshacks.com
- unroot using guide : nexusshacks.com
- back to factory setting on GB 2.34
- upgrade OTA to ICS 4.04
- Still got that problem.....
I'm using Nexus S 4G Sprint, pls help me guys...

nexus s won't boot
I had the same problem and read elsewhere that heating the phone with a hairdryer solves the problem.
I must say, indeed it did.
I removed the battery and the SIM card, then heated up the phone (so it really feels warm) put back the battery and sim and simsalebim the phone started again. and is still working since (now already a few day's)
It seems that a component in the phone is heat sensitive, the question in my mind is when will this show again and do I need to consider buying a new phone.
But sofar it works
PS I also tried hard reset factory reset the lot, but in the end only heating up helped.
Good luck, David

I fixed this problem! but I had to wipe all user data by rooting it using nexusrootICS. It finally boots up and the phone works now... that's all I need.

[Q] Stuck in a bootloop, dev ed, root, OTA

I'm new to Motorola in the smartphone world, but just upgraded to a Droid Maxx Developer Edition. The bootloader is unlocked and it has root, but with the stock ROM. Well since yesterday it has been VERY annoyingly insisting on installing an OTA device update every few hours. After postponing it and postponing it I accidentally selected install. Now it's constantly rebooting into recovery (I assume) to install the update, but TWRP loads instead of the stock recovery so nothing happens. Then when I reboot into Android (4.2 19.5.3), within 2 minutes it reboots again to attempt installing the update.
Now, I'm ready to get away from stock (played with it stock for about a month, ready to move on), so I downloaded CM for it. But it won't stay booted into Android long enough for me to copy the .zip over to the phone to flash in TWRP. Also, I've never done anything in adb or fastboot. However, I did install adb (Windows 7 64-bit) and have been playing with that. When my phone is in android, I can usually see it listed as "TA4310BUAV unauthorized" when I run adb devices. After googling, this is because I've not authorized my computer on my phone. However, even after selecting 'revoke all authorizations' or whatever in developer settings, I still get no notification to authorize. And then when I'm booted into TWRP I can't see the phone at all.
Basically, I'm stuck in a bootloop and just want to copy the CM zip file to the phone so I can flash it in TWRP, but I'm at a loss as to how to do this. Can anyone provide me with some advice on how to proceed? It would be greatly appreciated!!

carmike692000 said:
I'm new to Motorola in the smartphone world, but just upgraded to a Droid Maxx Developer Edition. The bootloader is unlocked and it has root, but with the stock ROM. Well since yesterday it has been VERY annoyingly insisting on installing an OTA device update every few hours. After postponing it and postponing it I accidentally selected install. Now it's constantly rebooting into recovery (I assume) to install the update, but TWRP loads instead of the stock recovery so nothing happens. Then when I reboot into Android (4.2 19.5.3), within 2 minutes it reboots again to attempt installing the update.
Now, I'm ready to get away from stock (played with it stock for about a month, ready to move on), so I downloaded CM for it. But it won't stay booted into Android long enough for me to copy the .zip over to the phone to flash in TWRP. Also, I've never done anything in adb or fastboot. However, I did install adb (Windows 7 64-bit) and have been playing with that. When my phone is in android, I can usually see it listed as "TA4310BUAV unauthorized" when I run adb devices. After googling, this is because I've not authorized my computer on my phone. However, even after selecting 'revoke all authorizations' or whatever in developer settings, I still get no notification to authorize. And then when I'm booted into TWRP I can't see the phone at all.
Basically, I'm stuck in a bootloop and just want to copy the CM zip file to the phone so I can flash it in TWRP, but I'm at a loss as to how to do this. Can anyone provide me with some advice on how to proceed? It would be greatly appreciated!!
Click to expand...
Click to collapse
In TWRP try wiping your cache. That should delete the OTA. Then when you boot back into the OS use titanium backup to freeze the app "MotorolaOTA." That should do it.
Sent From Droid Ultra

Caseyk621 said:
In TWRP try wiping your cache. That should delete the OTA. Then when you boot back into the OS use titanium backup to freeze the app "MotorolaOTA." That should do it.
Sent From Droid Ultra
Click to expand...
Click to collapse
Thank you so much! I will try this immediately. I just figured out how to get into fastbook, and my computer recognizes the phone in that mode. Is that a good method for pushing the CM.zip to the phone (just for future reference if the above doesn't work)?

carmike692000 said:
Thank you so much! I will try this immediately. I just figured out how to get into fastbook, and my computer recognizes the phone in that mode. Is that a good method for pushing the CM.zip to the phone (just for future reference if the above doesn't work)?
Click to expand...
Click to collapse
May be wrong but I don't think you can push files in that way via fastboot. If my first method didn't work let me know. There are a few other things to try.
Sent From Droid Ultra

Caseyk621 said:
May be wrong but I don't think you can push files in that way via fastboot. If my first method didn't work let me know. There are a few other things to try.
Sent From Droid Ultra
Click to expand...
Click to collapse
I erased the cache like you said (though I did it through fastboot since I already had it up and it's 'new and exciting' and all), and rebooted. Seems to have worked so far. I could go ahead and d/l TiB and freeze that service like you said, but since I'm going to flash CM anyways, I don't see as that's necessary at the moment. However, I can't get W7 to see the phone to be able to transfer the .zip to the phone, whether by Windows Explorer or adb, because I still don't have the option on the phone to authorize my laptop.
EDIT - I'm sure one problem with the computer not listing the phone as a device is it cannot find the device driver to install for it, and I've not been successful googling for it. So in the Windows Device Manager list, my XT1080 has a yellow exclamation mark by it. Also, just installed TiB and froze "Motorola OTA" since I had to wait five minutes to post this edit anyways.

carmike692000 said:
I erased the cache like you said (though I did it through fastboot since I already had it up and it's 'new and exciting' and all), and rebooted. Seems to have worked so far. I could go ahead and d/l TiB and freeze that service like you said, but since I'm going to flash CM anyways, I don't see as that's necessary at the moment. However, I can't get W7 to see the phone to be able to transfer the .zip to the phone, whether by Windows Explorer or adb, because I still don't have the option on the phone to authorize my laptop.
Click to expand...
Click to collapse
Ok i just like to disable the OTA app to avoid accidentally upgrading and bootlooping. Plus I'm assuming that you'll be making a back up of your stock system to go back to should you not care for CM. Do you have USB debugging enabled on your phone?
Sent From Droid Ultra

Caseyk621 said:
Ok i just like to disable the OTA app to avoid accidentally upgrading and bootlooping. Plus I'm assuming that you'll be making a back up of your stock system to go back to should you not care for CM. Do you have USB debugging enabled on your phone?
Sent From Droid Ultra
Click to expand...
Click to collapse
As per my edit above, I have now frozen "Motorola OTA". That is a great point regarding the backup.
Yes, I do have USB debugging enabled on my phone. Also, per my edit above, not having the proper driver installed for my phone may be the limiting factor here. Though having never used adb before, maybe it's a slew of other things, I'm not sure.

carmike692000 said:
As per my edit above, I have now frozen "Motorola OTA". That is a great point regarding the backup.
Yes, I do have USB debugging enabled on my phone. Also, per my edit above, not having the proper driver installed for my phone may be the limiting factor here. Though having never used adb before, maybe it's a slew of other things, I'm not sure.
Click to expand...
Click to collapse
Maybe here
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Sent From Droid Ultra

Caseyk621 said:
Maybe here
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Sent From Droid Ultra
Click to expand...
Click to collapse
Finally we're getting somewhere. I had installed that earlier, but never had any success with it. However, after just aimlessly disabling and reenabling things (USB debugging, PTP media sharing, revoking authorizations), and unplugging/replugging, it finally installed the driver. And now adb recognizes it, I was able to authorize my laptop, and I just copy and pasted the cm .zip to my phone.
It seems everything is going to work out just fine! I'm going to back up a few things with TiB and then flash CM.
Thank you so much for your input! I'd still be dead in the water if it weren't for your help!

carmike692000 said:
Finally we're getting somewhere. I had installed that earlier, but never had any success with it. However, after just aimlessly disabling and reenabling things (USB debugging, PTP media sharing, revoking authorizations), and unplugging/replugging, it finally installed the driver. And now adb recognizes it, I was able to authorize my laptop, and I just copy and pasted the cm .zip to my phone.
It seems everything is going to work out just fine! I'm going to back up a few things with TiB and then flash CM.
Thank you so much for your input! I'd still be dead in the water if it weren't for your help!
Click to expand...
Click to collapse
Glad I could help! Don't forget to make a backup in TWRP! You may find yourself wanting to go back to stock sooner than you think! I keep trying ROMs but always end up missing active notifications and touch less as well as some others!
Sent From Droid Ultra

I am wanting to take and install the latest Ota update. I'm rooted and unlocked (via Chinese method). My question is how do I actually install the downloaded update considering that I have twrp for a recovery?.... Thank you in advance

nubia11 said:
I am wanting to take and install the latest Ota update. I'm rooted and unlocked (via Chinese method). My question is how do I actually install the downloaded update considering that I have twrp for a recovery?.... Thank you in advance
Click to expand...
Click to collapse
Flash the stock recovery with fastboot. I forget if you need to also unroot or not. Also make sure you have any apps that were disabled or frozen enabled/defrosted

[Q] How to root this device without deleting any data?

Is it possible to root one plus one, without deleting any data and apps from it? I just want root access but don't want any custom rom.

yes, of course..
root doesn't delete any of your data

senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
Thanks for that. How can I do that?
#newtorooting

senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.
---------- Post added at 08:13 PM ---------- Previous post was at 08:10 PM ----------
sourabhkejriwal said:
Thanks for that. How can I do that?
#newtorooting
Click to expand...
Click to collapse
Sorry you got your hopes up, but the other poster isn't right. As per my reply to him you need to unlock your bootloader first, which is going to wipe your device. I'd suggest backing up any files that you have that are important to you. As for your apps and settings, you'll have to set them up again afterwards. Go to my guide thread here:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
You need to follow (in order) sections 1, 2, 3, and 4. This will give you root access on your stock ROM. You should also follow section 10, it's very important that you make a backup of your EFS partition.

timmaaa said:
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.[
Click to expand...
Click to collapse
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
Step-7: If you want to root the phone without installing TWRP recovery, type the following command
fastboot boot twrp.img
Click to expand...
Click to collapse
I guess the real question being, why would you need a custom recovery?

pdhx said:
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
I guess the real question being, why would you need a custom recovery?
Click to expand...
Click to collapse
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Transmitted via Bacon

The default recovery will only flash cm signed zip, which is another reason for needing a custom recovery. That method you mention at ibtimes meant that it would allow you to, for one boot cycle, do a "live boot" of twrp
Sent From Lollipopified Bacon Goodness!

But how is anything going to be written to the system partition if it is locked ?

timmaaa said:
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Click to expand...
Click to collapse
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?

pdhx said:
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?
Click to expand...
Click to collapse
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
what do get when you type fastboot devices ?

bombadier said:
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
Click to expand...
Click to collapse
Which seems to be somewhat limiting for such an otherwise developer friendly device?
bombadier said:
what do get when you type fastboot devices ?
Click to expand...
Click to collapse
Nada, nothing, nil. however, "adb devices" works fine... WTF?

pdhx said:
Which seems to be somewhat limiting for such an otherwise developer friendly device?
Nada, nothing, nil. however, "adb devices" works fine... WTF?
Click to expand...
Click to collapse
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help

bombadier said:
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help
Click to expand...
Click to collapse
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?

pdhx said:
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?
Click to expand...
Click to collapse
They're "forcing" you to unlock the bootloader in order to root the device because that's the universally accepted standard (unlock bootloader, install custom recovery, flash root). Some devices have super secure bootloaders and that's why you end up needing to use hacks to get those devices rooted, but that isn't the normal way to go about it. Anyway, there's no advantage to leaving the bootloader at all. There's also no disadvantage to unlocking the bootloader at all. You might say that the fact that the device is wiped during the unlocking process is a disadvantage, but that fact is very well documented both here, on the OnePlus forums, and pretty much any other reputable tech site that mentions unlocking the bootloader on this phone. The point to that last sentence? It pays to research a device thoroughly before buying it, or before using it, the wiping of the device is no issue at all if you do it when you receive the phone (prior to using it), like many people have. But in your situation you're just going to have to backup any important media from the phone prior to unlocking.
Anyway, on to your fastboot issue. Exactly which drivers do you have installed on your PC? Do you have any other phone drivers or software installed on the PC? And do you have access to another PC in case the one you're using is the source of the issue?

Got it, 27th try (give or take) is the charm.... Had to use USBdeview and uninstall the Google and the Qualcomm drivers. Reinstalled the Google drivers (after a reboot) and got it to work. Guess I could have figured that out from dev manager by watching what drivers got activated while fastboot was active but nothing ever jumped out at me as an obvious culprit.
Interesting to note that TWRP now automatically prompts you to install SuperSU if you reboot after installing it. Maybe it found the zip but either way, nice touch!
Now to go and decide what ROM to install....
Thanks for your help!

I would suggest temasek unofficial cm12 ROM. Been using it pretty much as a daily driver since version 1.something of the ROM and no problems. At this point it's been almost a month of not having to boot into my cm11s ROM lol. I use it with AK kernel, seems like a good match cuz both devs are working together looks like. Flash AK ukm special edition after flashing his kernel and install synapse from play store if you want to play around with settings of the kernel
Sent From Lollipopified Bacon Goodness!

zenix23456 said:
I have been using AnyRooter for months and it is quite good to root OnePlus phones.
Click to expand...
Click to collapse
Except the Oneplus One.

[Q] D80110G OTA phone working but NO download mode No recovery

Hello everyone,
Started from D80110C (stock using download mode), rooted, took all the OTAs till D80110G. Then, on top of that, I received another OTA for 300Mb to D80120G . I wasn't sure what it was. I finally decided to takr it. BIG MISTAKE!!! root was gone.
Tried Towelroot and Root25 and Root10, now all failing with D80120G .
So I said, easy, lets go back to stock D80110C. Surprise: download mode is gone. Every time I follow volume key sequence (tried the all) phone shows charging icon instead of download mode.
And recovery mode? only shows Factory Reset (which I already tried...)
I read that some people were able to use the LG Maintenance tool and choose "Update Recovery". Tried that: to me shows "Nothing to fix".
In other words, I'm stuck. Phone works fine (which is great), but I'm afraid I will never be able to do any upgrade since both download method and recovery method seems to be gone. Question is: will the next OTA work?
Any ideas? I read about the Linux method of overwriting the images. Pretty scary, since the phone still works I'd think something else should be available.
It could be worse, the phone is working, still I hate being without options...
Any help would be greatly appreciated. Thank you in advance!

I used stump root today to root my girlfriends g2 with d80120g. link here ----> http://forum.xda-developers.com/lg-g3/orig-development/root-stump-root-lg-g3-sprint-verizon-t2850906

Swagg422 said:
I used stump root today to root my girlfriends g2 with d80120g. link here ----> http://forum.xda-developers.com/lg-g3/orig-development/root-stump-root-lg-g3-sprint-verizon-t2850906
Click to expand...
Click to collapse
Jswagg thanks for the reply.if I use stump,even after a factory reset, I immediately get a rooted message when in reality I'm not rooted. I read that I'm supposed to use the brute force method.how? Again,it says rooted and I see no options....
Thanks again.

franksrental said:
Jswagg thanks for the reply.if I use stump,even after a factory reset, I immediately get a rooted message when in reality I'm not rooted. I read that I'm supposed to use the brute force method.how? Again,it says rooted and I see no options....
Thanks again.
Click to expand...
Click to collapse
After you run stump and it tells you to reboot. After the reboot go to the playstore and install supersu after that you should be all good.
Sent from my Oneplus one using XDA Free mobile app

Swagg422 said:
After you run stump and it tells you to reboot. After the reboot go to the playstore and install supersu after that you should be all good.
Sent from my Oneplus one using XDA Free mobile app
Click to expand...
Click to collapse
No unfortunately stump doesn't say to reboot. It just says rooted. Then I checked with root checker and I'm not rooted.
I believe its a broken root scenario. Anyone knows what to do? Thank you in advance.

Hello I have custom recovery but unrooted on 4.2.2 JB and have ant OTA to KK can I take it or do I need stock recovery?

franksrental said:
Hello everyone,
Started from D80110C (stock using download mode), rooted, took all the OTAs till D80110G. Then, on top of that, I received another OTA for 300Mb to D80120G . I wasn't sure what it was. I finally decided to takr it. BIG MISTAKE!!! root was gone.
Tried Towelroot and Root25 and Root10, now all failing with D80120G .
So I said, easy, lets go back to stock D80110C. Surprise: download mode is gone. Every time I follow volume key sequence (tried the all) phone shows charging icon instead of download mode.
And recovery mode? only shows Factory Reset (which I already tried...)
I read that some people were able to use the LG Maintenance tool and choose "Update Recovery". Tried that: to me shows "Nothing to fix".
In other words, I'm stuck. Phone works fine (which is great), but I'm afraid I will never be able to do any upgrade since both download method and recovery method seems to be gone. Question is: will the next OTA work?
Any ideas? I read about the Linux method of overwriting the images. Pretty scary, since the phone still works I'd think something else should be available.
It could be worse, the phone is working, still I hate being without options...
Any help would be greatly appreciated. Thank you in advance!
Click to expand...
Click to collapse
Time to reply to my thread? A new one click root method for the g3 actually works with any recently otaed g2. Magically able to go in download mode with adb without forcing with volume up and power button (that is not working anymore).#short short long I'm rooted and I did see download mode forced by the bat file....glta

More info
franksrental said:
Time to reply to my thread? A new one click root method for the g3 actually works with any recently otaed g2. Magically able to go in download mode with adb without forcing with volume up and power button (that is not working anymore).#short short long I'm rooted and I did see download mode forced by the bat file....glta
Click to expand...
Click to collapse
It would be great if you replied with more information for those of us still having this problem.

More info
scottjk said:
It would be great if you replied with more information for those of us still having this problem.
Click to expand...
Click to collapse
Yep, I'm currently having the same problem...

Anyway to return to stock? or Install TWRP/ Rom

I haven't turned this phone on in years.
I unlocked the bootloader and flashed roms years ago and i remember trying to get it back to stock and trying to relock it but i couldn't fully do it.
I tried to install TWRP and put a rom on it but it wont work so i thought trying to get it back to stock as much as i can might help. then i can start again
1. the phone doesn't work by USB if plugged in while it's on. I have to leave it plugged in and then restart it for it to work
2. ADB works while phone is on (doing 1)
3. Fastboot does not and i have no idea why. I can't install TWRP

Passportpowell said:
I haven't turned this phone on in years.
I unlocked the bootloader and flashed roms years ago and i remember trying to get it back to stock and trying to relock it but i couldn't fully do it.
I tried to install TWRP and put a rom on it but it wont work so i thought trying to get it back to stock as much as i can might help. then i can start again
1. the phone doesn't work by USB if plugged in while it's on. I have to leave it plugged in and then restart it for it to work
2. ADB works while phone is on (doing 1)
3. Fastboot does not and i have no idea why. I can't install TWRP
Click to expand...
Click to collapse
do you have usb debugging enabled, are your sdk tools up to date?

Yes to both.
When doing the adb fastboot part it restarts into one of the screen I attached to my post.
My computer makes a noise like a USB had been connected but nothing comes up.
fastboot devices command shows nothing and when I check device manager it just says android with a yellow! If that helps.

Passportpowell said:
Yes to both.
When doing the adb fastboot part it restarts into one of the screen I attached to my post.
My computer makes a noise like a USB had been connected but nothing comes up.
fastboot devices command shows nothing and when I check device manager it just says android with a yellow! If that helps.
Click to expand...
Click to collapse
then you need to update your htc drivers.

here you go.

Aldo101t said:
do you have usb debugging enabled, are your sdk tools up to date?
Click to expand...
Click to collapse
Aldo101t said:
here you go.
Click to expand...
Click to collapse
Super star
I now have another issue though. I can't sideload and it's asking for a password for twrp to mount decrypt data. If you don't mind trying to help me here too
I've done a format data on twrp and it won't ask for a password anymore but I still can't sideload anything. Going to try to copy the rom to the storage and see what happens there
I've only could see a twrp folder on my phone when I connect it to my pc while still in twrp so I copied a rom there and went into install zip, data, media, twrp. My file was there.
Installing rom now I'll update if it worked.

Passportpowell said:
Super star
I now have another issue though. I can't sideload and it's asking for a password for twrp to mount decrypt data. If you don't mind trying to help me here too
View attachment 5087597
View attachment 5087599
Click to expand...
Click to collapse
you may have to format data, then flash magisk after then reboot, why are you trying to side load the rom just put it on your ex-sdcard, and flash it in twrp. twrp won't decrypt your data, what version of twrp you using, the latest is 3.4.0-0
try hitting cancel when it asks for a password, then see if it works.

here is magisk

if you are on pie that viper rom is based on oreo. just so you know.

Aldo101t said:
you may have to format data, then flash magisk after then reboot, why are you trying to side load the rom just put it on your ex-sdcard, and flash it in twrp. twrp won't decrypt your data, what version of twrp you using, the latest is 3.4.0-0
try hitting cancel when it asks for a password, then see if it works.
Click to expand...
Click to collapse
Yeah i sorted that bit. it confused me because there were no files and didn't know how to get to anything i copied over but that's how i got the rom on
Aldo101t said:
if you are on pie that viper rom is based on oreo. just so you know.
Click to expand...
Click to collapse
Yeah i realised after you said it. I believe i was on pie because i was on build no. 3.34.401.1 and now i'm on 2.33.401.19 after installing the rom. I shouldn't be trying to do this at almost 12:30 at night haha.
Is that bad that its gone through and, so far, worked? What would you recommend I do/ what would you do if you were in my position currently?
I was originally going to to try to get back to stock but im not even sure what RUU to use as i think the one that i had used a few years ago might not have been the original.
you've been an amazing help so far so thank you

Passportpowell said:
Yeah i sorted that bit. it confused me because there were no files and didn't know how to get to anything i copied over but that's how i got the rom on
Yeah i realised after you said it. I believe i was on pie because i was on build no. 3.34.401.1 and now i'm on 2.33.401.19 after installing the rom. I shouldn't be trying to do this at almost 12:30 at night haha.
Is that bad that its gone through and, so far, worked? What would you recommend I do/ what would you do if you were in my position currently?
I was originally going to to try to get back to stock but im not even sure what RUU to use as i think the one that i had used a few years ago might not have been the original.
you've been an amazing help so far so thank you
Click to expand...
Click to collapse
well, see how it goes, if you start to have issues go back to stock, if you made a backup of stock just restore it.
use the ruu for 401 make sure it's 3.34.401.x
that software number doesn't mean you are on 2.33 firmware you'll still be on pie firmware, 3.34

Aldo101t said:
well, see how it goes, if you start to have issues go back to stock, if you made a backup of stock just restore it.
use the ruu for 401 make sure it's 3.34.401.x
that software number doesn't mean you are on 2.33 firmware you'll still be on pie firmware, 3.34
Click to expand...
Click to collapse
I can't seem to find a RUU for 401 3.34.401.x that isn't dual sim version. Could you point me in the right direction please in case I do ever want to attempt stock again?
Edit: I've found it. Also why this one instead of 3.37.617.1?
Edit: im guessing because 3.37.617.1 is for NA and the one you mentioned is for EU which is where i am
Also I think im getting an idea about why it won't charge or connect until I restart.
I've installed lineage room 17.1 and it's constricted showing as "charging connected device via usb" even when it's nothing is plugged in. I'm guessing it's a hardware issue?

Passportpowell said:
I can't seem to find a RUU for 401 3.34.401.x that isn't dual sim version. Could you point me in the right direction please in case I do ever want to attempt stock again?
Edit: I've found it. Also why this one instead of 3.37.617.1?
Edit: im guessing because 3.37.617.1 is for NA and the one you mentioned is for EU which is where i am
Also I think im getting an idea about why it won't charge or connect until I restart.
I've installed lineage room 17.1 and it's constricted showing as "charging connected device via usb" even when it's nothing is plugged in. I'm guessing it's a hardware issue?
Click to expand...
Click to collapse
3.37.617.1 is for the us-unlocked

Hello to everyone...I just got from my older brother his HTC U11 4gb 64gb phone. And it has locked bootloader and does not have root. So please what should I have to do so I can install custom rom. Stock rom is old full of bloatrware. There is so many information that I am confused.
Thx so much !