Related
Hello guys,
i got a serious and frustrating problem here.
A few days ago my xoom was stuck on the M screen, so I used a thread in the forum and recovered it.
It solved myh problem back then, but since I had 3.2 before this and the solution injected me with Android 3.01 my problems started to show themselves.
the first one is that
<b> Through Fastboot, RecoveryMod, ADB </b> and any other way you can Imagine to install a new ROM or even remove or create a file,
All of them show success message but when I check them out I see no changes.
i tried fastboot and Recovery to install nearly every ROM,Recovery and bootimage in this site but so far it was wild goose chase.
so I want to ask if I'm doing anything wrong or if you need any more information here, but please help me with this
wow I cant believe it, All these masterminds here and no answer to my distress signal??
Guys I am so in trouble and this is the only place I hoped to get answered.
I can provide you with more info if you need, but please dont say I'm on my own here.
all these years this forum was the last hope for me.
i know I'll get my answer here one day
You are not being very clear about what you have done,, but I'm assuming that you reinstalled the stock image that got you back to HC 3.01. Can you see if you are able to get OTA updates to get you back to at least 3.1, or 3.2 if possible?
If that's my problem forgive me please, Ive written that post in 3:00AM
for the sake of clearity I should add some info:
1. I even tried stock ROMs but you see I cant even flash them (Not from Recovery nor Fastboot) the steps seem successful : it opens the package,it installs them and it says everything was a success. But when I restart the device I see nothing has changed.
2. OTA updates are the same, they keep downloading and when the sysem reboots to recovery to install them it cant find them.
3. You dont believe it if I say even files and programs that I remove from device by my hand(Android OS) are back after the first restart.
And you see it's dark magic! everything from a file to a partition are back by one reboot. I dont know what should I call it but I havent seen anything like it on the whole Internet.
So seems like I should make a competition for the xda experts here
Can you publish it so all of them can see it?
Mohfath said:
If that's my problem forgive me please, Ive written that post in 3:00AM
for the sake of clearity I should add some info:
1. I even tried stock ROMs but you see I cant even flash them (Not from Recovery nor Fastboot) the steps seem successful : it opens the package,it installs them and it says everything was a success. But when I restart the device I see nothing has changed.
2. OTA updates are the same, they keep downloading and when the sysem reboots to recovery to install them it cant find them.
3. You dont believe it if I say even files and programs that I remove from device by my hand(Android OS) are back after the first restart.
And you see it's dark magic! everything from a file to a partition are back by one reboot. I dont know what should I call it but I havent seen anything like it on the whole Internet.
So seems like I should make a competition for the xda experts here
Can you publish it so all of them can see it?
Click to expand...
Click to collapse
Actually, I have seen someone with the same problem here on this forum, but I can't recall exactly what the solution was.
Can you describe, step by step what you are doing, what cable you are connecting to your pc with, etc?
okantomi said:
Actually, I have seen someone with the same problem here on this forum, but I can't recall exactly what the solution was.
Can you describe, step by step what you are doing, what cable you are connecting to your pc with, etc?
Click to expand...
Click to collapse
That would be relief to know this could be solvable.
I will look more too.
As for your post I must say:
1. I plug the Xoom to the PC using the included cable
2. I start the xoom and start fastboot
3. on the PC system has the drivers and completely knows it
4. I start with SDK:
I. Fastboot oem unlock (Completing onscreen instructions and reboot device)
II. Fastboot mode again I use Fastboot flash boot boot.img
III. Continuing with Recovery,System
IV. Rebooting the device anything is the same.
My ROM is unchanged by the process and keeeeeeeeps giving the damn error of System process error please submit
5. And with ClockworkrecoveryMod I have the stock ROM on my sd card.
I. I choose install zip from sd card.
II.Choose the correct zip file and start flashing.
III. Choosing Wipe Data/Factory reset will take the device into a complete hang. unless I first use the mount page to mount the System/Data
IV. I reboot the device and ..... you know nothing changed.
so thats my story.
Still hope to find something about it.
Thanks...that was helpful. But now I want to know the following:
Were you rooted before the trouble started?
What did you do to recover?
If rooted, what version of CWM recovery did you have installed? Did you do a nanadroid backup? (I guess the answer is no, because you could have just restored with that).
What recovery are you accessing when trying to flash a zip file?
If you can answer these questions I will continue to wrack my brain trying to recall where I saw that thread.
Edit: please check out this thread http://forum.xda-developers.com/showthread.php?t=1370312
Some of what I said to him may help you .
okantomi said:
Were you rooted before the trouble started?
What did you do to recover?
If rooted, what version of CWM recovery did you have installed? Did you do a nanadroid backup? (I guess the answer is no, because you could have just restored with that).
What recovery are you accessing when trying to flash a zip file?
If you can answer these questions I will continue to wrack my brain trying to recall where I saw that thread.
Edit: please check out this thread http://forum.xda-developers.com/showthread.php?t=1370312
Some of what I said to him may help you .
Click to expand...
Click to collapse
Being rooted? -> Yes, The world is more beautiful with root!
to recover -> I followed this: http://forum.xda-developers.com/showthread.php?t=1097997 Shame it was Android 3.0
I use ClockworkRecovery 3.0.0.28 and I cant upgrade it cause of ... you know
And for your help I must say you are definitely the most caring person I know...
I'm off to check the provided link now
I was thinking of something that might be a reason.
I have this tiny problem:
When I go to CWM and choose Erase userData/Factory Reset Device Hangs
Click to expand...
Click to collapse
I was thinking of may be the userdata partition is corrupted and I gotta find a way to flash it completely.
Somehow I used Fastboot utility to do this and after saying Success, Nothing changed again.
Do you know any other way to physically do this job?
Hey everyone,
I'm having trouble getting my Nexus 7 to update to 4.2.2. My device is rooted, I recently performed a factory reset.
The update has never appeared in my "System updates" menu, so I looked around and saw that if you force stop "Google Services Framework" and clear its data, the update will appear in "System updates."
It did, but when it finishes downloading, it says "Verification failed."
I tried another factory reset, and I had to again force stop and clear data on "Google Services Framework" to get the update to appear, but again it downloads and say "Verification failed."
I'm stumped now. Do I have to unroot and reroot? Do I have to keep waiting for this update? Do anything with the bootloader? (I really hope not...)
Thanks everyone!
If some files in your system got changed for whatever reason, then you wont be able to update. You can flash the 4.2.1 stock rom and try ota update again.
Leonhan said:
If some files in your system got changed for whatever reason, then you wont be able to update. You can flash the 4.2.1 stock rom and try ota update again.
Click to expand...
Click to collapse
Is flashing the stock 4.2.1 rom the same thing as doing a factory reset to 4.2.1?
If it isn't, would flashing the 4.2.1 rom wipe my tablet?
Leonhan said:
If some files in your system got changed for whatever reason, then you wont be able to update. You can flash the 4.2.1 stock rom and try ota update again.
Click to expand...
Click to collapse
If he is trying to do an OTA to 4.2.2, would it not be more straightforward to just flash the 4.2.2 factory image? The OP has already done a factory reset, so it doesn't look like he/she is particularly attached to his current setup.
Also - the language he used was vague - it sort of sounded like the OP observed "verification failed" in the main OS rather than in the recovery. Not sure.
But it doesn't matter - newbs should not be trying to use OTAs on modified /system images or tabs with altered boot images. It's just too detailed a process to describe compactly.
@Horadrius
Before you do anything further, you should back up everything on the "SD Card" to your PC. Yes, all of it. You can throw it away later if you find you didn't need it. But if you follow the instructions for the Google (factory) images install, everything gets wiped off of /data including your pseudo - SD card.
At a minimum, that will allow you to follow the SBS instructions for installing the 4.2.2 factory images, or - you can simply install a 4.2.2 Stock ROM from over in the dev forum.
Whatever you do, start getting in the habit of making backups - and at least occasionally also getting copies of those off of the tablet.
Oh boy, lot of information to digest here....and a lot of questions
it sort of sounded like the OP observed "verification failed" in the main OS rather than in the recovery. Not sure.
Click to expand...
Click to collapse
Yes, it was the main OS - Settings -> About Tablet -> System Update.
After force stopping Google Services Framework, the update showed up there, and when the download bar reached 100%, it said "verification failed." I did a factory reset, and now when I go to System Update it simply says that my system is up to date.
This makes me think I'm not "supposed" to have the update yet, and that it will arrive, eventually. Yes?
newbs should not be trying to use OTAs on modified /system images or tabs with altered boot images.
Click to expand...
Click to collapse
So, no updating the device from System Menu because I'm rooted/unlocked bootloader? I'll have to flash everything as it comes out?
@Horadrius
Before you do anything further, you should back up everything on the "SD Card" to your PC.
Click to expand...
Click to collapse
Would Titanium Backup held in this regard? Or simply copy/paste the sdcard folder to my PC?
This whole process has been very frustrating. Is this the price you pay for rooting your device? Making simple system updates into a maze?
Horadrius said:
Oh boy, lot of information to digest here....and a lot of questions
Yes, it was the main OS - Settings -> About Tablet -> System Update.
After force stopping Google Services Framework, the update showed up there, and when the download bar reached 100%, it said "verification failed." I did a factory reset, and now when I go to System Update it simply says that my system is up to date.
This makes me think I'm not "supposed" to have the update yet, and that it will arrive, eventually. Yes?
So, no updating the device from System Menu because I'm rooted/unlocked bootloader? I'll have to flash everything as it comes out?
Would Titanium Backup held in this regard? Or simply copy/paste the sdcard folder to my PC?
This whole process has been very frustrating. Is this the price you pay for rooting your device? Making simple system updates into a maze?
Click to expand...
Click to collapse
Sounds like your download is bad if it fails at this stage. I believe it is saying the checksum of the download file doesn't match whatever is downloaded.
PS. not related to N7, why XDA use the re-captcha which I need to refresh several times to get something I can read
Horadrius said:
Yes, it was the main OS - Settings -> About Tablet -> System Update.
After force stopping Google Services Framework, the update showed up there, and when the download bar reached 100%, it said "verification failed." I did a factory reset, and now when I go to System Update it simply says that my system is up to date.
This makes me think I'm not "supposed" to have the update yet, and that it will arrive, eventually. Yes?
Click to expand...
Click to collapse
No. It means that for some strange reason, running a checksum program on the downloaded OTA file failed to produce the expected checksum. The most likely way this can happen is that the file is truncated - the download stopped short of the full file. Don't know why this is happening, but there you go. There could be other failure causes that are more rare, but it doesn't mean you are not "supposed" to have the OTA. It means that the download process is failing.
The *stock* recovery does a number of even more sophisticated checking than this; but it appears from your description that the recovery never even gets booted.
Horadrius said:
So, no updating the device from System Menu because I'm rooted/unlocked bootloader?
Click to expand...
Click to collapse
Yes and No. An unlocked bootloader causes no problems at all. ANY of the following CAN or WILL cause problems:
- attempting to run an OTA with a custom recovery installed instead of the stock recovery.
- having a modified boot partition (e.g. non-stock kernel, or slightly modified boot partition)
- having altered (or removed!) files in the /system partition that are targeted for patching.
- permissions changes performed by the installer script can cause root functionality to disappear
Horadrius said:
I'll have to flash everything as it comes out?
Click to expand...
Click to collapse
Not sure what you are asking here, but the basic answer is that if you stay on stock you can certainly apply OTAs easily. If you start altering things, you might or might not be able to apply an OTA; there are simply no guarantees.
[size=+1]OTAs are meant for stock installations - including a stock recovery. PERIOD. While it is possible that an OTA could succeed, it is unreasonable to have the expectation that it will do so.[/size]
Horadrius said:
Would Titanium Backup held in this regard? Or simply copy/paste the sdcard folder to my PC?
Click to expand...
Click to collapse
I presume you are talking about the future here, as you said that you already did a factory reset at least twice. If you have subsequently added stuff back in, then I suppose you might be talking about the present tense.
But, yes - either TiBu or the Carbon app can be used along with a strategy where you simply back up the apps & data you are interested in, (plus any "flashable zips" that you used to customize your device in the first place), and you simply start from scratch with a factory install followed by re-rooting, and then restore your apps & data (using TiBu or Carbon).
One other thing you can do which is EASY is this: simply wait until a developer/ROM cook publishes a "Stock" flashable ROM based on the release that the OTA is upgrading to. Don't worry about the OTA, just wait a little bit. (These ROMs are already out for the WiFi-only model, BTW).
1) Take a backup as the first thing you do. It's easy and gives you some insurance.
2) Don't wipe (no "factory reset") - just install the Stock ROM over the top of your existing ROM.
that's it. If you were using a custom kernel, re-install it.
Horadrius said:
This whole process has been very frustrating. Is this the price you pay for rooting your device? Making simple system updates into a maze?
Click to expand...
Click to collapse
[size=+1]OTAs are meant for stock installations - including a stock recovery. PERIOD.[/size]
Interpret that as you desire. It is unreasonable for you to expect that you can diddle with your phone any way you please, and a patch install upgrade methodology will be robust in the faces of arbitrary changes on your part. You are the person creating the maze, not Google.
Moreover, it is your choice to take an upgrade - it's not mandatory. My guess is your tablet was quite pleasing to you before any OTAs started rolling out. Nobody is forcing you to do anything.
OK, one last thing. It is still possible that a manual OTA can succeed on your phone if it is lightly rooted - but there are no guarantees. The procedure does not require you to wait around until an OTA arrives on your phone, but it is not for the faint-hearted:
1) Download the appropriate Stock OTA File.
2) Re-install the stock recovery onto your tablet. You will have to dig it out of the Google full factory image for the version of the OS you are currently running. (available here)
Code:
fastboot flash recovery factory-4.2.1-recovery.img
3) Soft-boot into a custom recovery, e.g.
Code:
fastboot boot openrecovery-twrp-2.4.1.0-grouper.img
5) Using the command line and adb to communicate with the soft-booted recovery, create a recovery command file:
Code:
C:\myPCsux> adb push 6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip /cache/update.zip
C:\myPCsux> adb shell
# cd /cache/recovery
# cat > command
--update_package=/cache/update.zip
^D # ( that is a Control-D character )
# sync
# reboot recovery
This will either succeed or fail. Based on your comments though, you might just want to overflash a Stock-derived ROM over the top of your existing ROM (a "no-wipe" install).
[ROM][Factory Image][4.2.2] Nakasi -::- Odex, Deodex, Rooted -::- teshxx (02/14/13) <-- NOTE for WiFi (nakasi/grouper) ONLY
good luck with your tab.
Someone once said "Rooting is a lifestyle". There's some truth to that; it eats up your time. Perhaps it is not for you.
Thanks, bftb0.
Looking through your list of reasons for why my OTA might not work, none of them applied to me.
I didn't install any custom recovery (didn't install Clockwork Mod recovery specifically to avoid dealing with flashing roms) or kernels or modify any partitions, nor to my knowledge changed any files in the /system section.
I think I'm going to give this update a week or so to pop up on my update menu before I start tinkering again.
Don't get me wrong - I enjoy this kind of tinkering, and all the perks of rooting, but my knowledge is extremely limited, which is what makes it frustrating trying to find information. The only thing I've done before this is install Cyanogen on my HP Touchpad.
Anyway, do I need to install CWM recovery to flash (overflash?) that 4.2.2 rom you linked?
if you haven't done anything other than rooting(i.e. copying a file su to it), OTA would go through. Your problem is about the download process. It can go wrong for many reasons from the download is bad to what saved to the temp area(where the download is) is bad(rare but still possible).
chimpanzeexda said:
if you haven't done anything other than rooting(i.e. copying a file su to it), OTA would go through. Your problem is about the download process. It can go wrong for many reasons from the download is bad to what saved to the temp area(where the download is) is bad(rare but still possible).
Click to expand...
Click to collapse
That's all I've done, root and unlock bootloader. The download only showed up when I cleared data and force stopped the "Google Services Framework" process. I reboot the system, and check for the update and nothing is there.
well, sounds like you have to flash it manually using fastboot then.
That said, I myself have no intention of doing the update any time soon as I don't find any specific problem with 4.2.1 and there isn't any specific feature i want in 4.2.2
Horadrius said:
Anyway, do I need to install CWM recovery to flash (overflash?) that 4.2.2 rom you linked?
Click to expand...
Click to collapse
TL;DR Yes and No.
People that use toolkits seem to use hard-flashed installs of custom recoveries, as they don't really understand what goes on under the hood, even if the toolkit offers them a means to soft-boot any image the toolkit operator downloads. (I assume that the toolkits probably allow this; as I don't use them I don't know for sure.)
What I am saying is that the answer depends on your knowledge. So long as you have an unlocked bootloader, you can soft-boot any boot image you like - including custom recoveries.. (This also pre-supposes correctly-functioning device drivers, but that is a Windows/user training issue, it has nothing to do with Android).
When I say soft-boot, I mean that the image is transferred to the tablet, which then hands over control and starts executing that image - but it is not "flashed" to Flash memory, so the next time a boot occurs, the same boot images are still stored in either "boot" or "recovery".
In this configuration, the phone should be much more likely to complete an OTA as it will have the stock recovery present most of the time, and only temporarily present when you attach to your PC and kick things off with a custom recovery.
The OTA could still fail, but it probably would succeed for a very lightly rooted stock configuration (other than problems with losing root).
The only downside to this arrangement is that you can't be flashing roms or making nandroid backups or other forms of rooter activities when you are away from the PC.
For the IT-OCD or obsessive ROM hopper, that could be a good thing.
good luck... the rest is up to you.
Ok, I installed Clockwork Mod from a toolkit because going into fastboot and choosing "Recovery mode" led me to a picture of the Android guy with a red triangle on his back saying "No Command."
I'm just going to install 4.2.2 myself now. Question regarding that link - odex/deodexed - I looked up the difference but can't tell which one is appropriate for me - I'm guessing it's odex because that seems to be closer to stock.
Edit: It worked! Thanks for your assistance, everyone!
IMO, google should not ship odex image now that we have fast enough hardware. odex is just a form of 'pre-compilation' which only benefit first time load(or when the cache is cleared). Too little gain for such a complicated setup.
Everything I found on this says volume + and power, which kicks me into download mode, not fastboot.
I've gone into adb and typed adb reboot bootloader, but that just restarts the phone and turns in on like normal.
I google the how to enter fastboot mode on LG G2 and can find plenty of post about being stuck in fastboot, but nothing on how to get into fastboot in the first place.
Found a tutorial here about setting up and using fastboot and thought I was set until I got to the part about "and using fastback", where it just says:
Make sure you have android debugging turned on in your phone (not really needed for fastboot but you do need for ADB), plug it into your computer and boot into fastboot mode...
I felt like watching "Much ado about nothing" when Denzel says; "The learned constable is too cunning to be understood"
Any direction is appreciated.
Hmm, I may have written that guide... Just checked and yeah should have been more clear I'll change that up. It should have read the USB debugging was needed for adb (not for fastboot) so when you can issue
adb reboot bootloader
But after that I did mention to check device specific forum for answers on how to get into fastboot/bootloader and being I've never held an lg g2 I took a quick look around.
Unfortunately the only way that I found that people said works every time is to wipe recovery to get into bootloader mode as the recovery you guys currently have disables something due to a patch getting custom recoveries to work
So yeah, I would advice to speak with someone knowledgeable about your specific device before you just wipe recovery
Out of curiosity, is there something specific you need to do with fastboot or are you just curious about your phone?
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
Out of curiosity, is there something specific you need to do with fastboot or are you just curious about your phone?
Click to expand...
Click to collapse
the current thing I've been trying to straighten out is that despite being rooted and installing TWRP, I can't install ROMS. I tried CM 11 and Hellfire so that I could put kitkat on, but gave the following:
Error executing updater binary zip.
One of the answers I found said that I had to go back to TWRP 2.3 (I'm using 2.6) and I believe that's where the whole bootloader thing came into play, because it was the way to 'downgrade' -
So then I found Philz touch 6 (as I understand it a mode of CM 11), but here he talked about fastboot and lokifying items. Here's the link:
http://forum.xda-developers.com/showthread.php?t=2554053
In the end it still comes back to the "can't load ROMs" issue. Just want a completely stripped down Kitkat that I can add the stuff I want without the bloatware.
Thanks in advance.(and the thanks button was hit on your reply)
For KitKat you should need a newer recovery with SELinux support which I believe is 2.6.x and newer for twrp, 2.3 I doubt would work if there even is one for your phone
But yes fastboot is often the best way to change recoveries but not the only way.
If there is a flashable.zip you could install new recovery from old
If your current ROM supports the flash image binary you can use a terminal emulator
You can use adb to install
Or even apps from the market
I would look for the latest recovery for your device, twrp, cwm, shouldn't matter so long as its new and then find what way works best changing for your phone.
The update-binary issue is often a sign that you need to change recoveries
Unfortunately without having your device I don't know if I can give you the best answers but feel free to ask
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Unfortunately without having your device I don't know if I can give you the best answers but feel free to ask
Best of luck!
Click to expand...
Click to collapse
Thanks again. I have adb and the script for loading TWRP 2.6.xx. I unrooted and rerooted the phone, because I wasn't sure how to replace the recovery... Now I think I realize that I could just find another recovery image and place it in the same file as the loki flash and that will flash it (At least that's what I understand at present).
If that's the case, then downloading the Philz touch 6 would work... but not wanting to brick it, I'm still asking and reading.
Hello Guys.
I am having a similar issue. I have a new ROM that will not run because of a faulty lg set up wizard that always force closes and I can not get passed it and a nandroid that for some reason is corrupted. So. This fastboot seems to be a dead end it looks like a quick learning curve of ADB is the only viable answer. I have installed all SDK Manager with ADB Tools and also the required Jarva JDK and LG drivers. The phone is turned on (at the beginning of the faulty setup wizard) In CMD my device is found when typing in 'adb devices' So. I am already to push a new ROM over to the phone.
Do either of you guys know the adb command?
Help would be appreciated.
Thanks
You can't actually flash a new ROM with adb, but you can either push it phone with adb and then flash in recovery. Or if your recovery has an option for adb sideload then use this.
Also setup wizard crashing is usually the fault of wrong gapps or not wiping before flashing a rom
Sent from my Nexus 4 using XDA Premium 4 mobile app
I found that the best way was to load flashify, that did the trick so I could start trying out ROMs... so no on to the next step - finding a 4.4.2 stripped down stock and the LG stuff I actually like.... thanks again.
demkantor said:
You can't actually flash a new ROM with adb, but you can either push it phone with adb and then flash in recovery. Or if your recovery has an option for adb sideload then use this.
Also setup wizard crashing is usually the fault of wrong gapps or not wiping before flashing a rom
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the reply!
I know it's not possible to flash a ROM via ADB. I have everything set up, ADB etc, etc. My phone is turned on and adb is seeing it but I can not work out the command to push. Every time I try to push I just get a long list of ADB instructions (I think they are) but nothing gets pushed. I have read lots of instructions on how to make the command but I still must be doing something wrong.
Here are my parameters;-
adb push/C:\Users\dene\Desktop/cm-11-20140210-SNAPSHOT-M3-d802.zip/sdcard
Am I missing some spaces I am not aware of? Are all my slashes the right way round and in the right places? Is my 'sdcard' destination designation correct seeing as there is only internal storage on the G2?
Another problem I am having is that ADB has no problem seeing my sevice EXCEPT when I boot in to recovery (TWRP). When in recovery I lose coms between my device and pc. Hence I can no do TWRP ADB side load (I have tried). I have all the correct LG drivers loaded. Except MTP keeps failing to install? Any ideas?
Not to be mardy about it or hassle you but I am fairly house bound and live out in the country and really require my mobile phone. I have spent many hours trying to figure this out. Any help with the above would be much appreciated?
PS. I did a very thorough wipe, I always do. The gapps are built in to this ROM!
Thanks
dodge3003 said:
Thanks for the reply!
I know it's not possible to flash a ROM via ADB. I have everything set up, ADB etc, etc. My phone is turned on and adb is seeing it but I can not work out the command to push. Every time I try to push I just get a long list of ADB instructions (I think they are) but nothing gets pushed. I have read lots of instructions on how to make the command but I still must be doing something wrong.
Here are my parameters;-
adb push/C:\Users\dene\Desktop/cm-11-20140210-SNAPSHOT-M3-d802.zip/sdcard
Am I missing some spaces I am not aware of? Are all my slashes the right way round and in the right places? Is my 'sdcard' destination designation correct seeing as there is only internal storage on the G2?
Another problem I am having is that ADB has no problem seeing my sevice EXCEPT when I boot in to recovery (TWRP). When in recovery I lose coms between my device and pc. Hence I can no do TWRP ADB side load (I have tried). I have all the correct LG drivers loaded. Except MTP keeps failing to install? Any ideas?
Not to be mardy about it or hassle you but I am fairly house bound and live out in the country and really require my mobile phone. I have spent many hours trying to figure this out. Any help with the above would be much appreciated?
PS. I did a very thorough wipe, I always do. The gapps are built in to this ROM!
Thanks
Click to expand...
Click to collapse
I HAVE SOLVED THE ISSUE! Thanks for your assistance mate but in the end I just went back to stock using this amazing thread:-
http://forum.xda-developers.com/showthread.php?t=2432476
in conjunction with this amazing video;-
http://www.youtube.com/watch?v=IixQjo_hyz8
So! I am now un rooted and back to stock. Time to start the rooting ana ROMing all over again.lol
Thanks
Glad to here!
You need a space after push
But it usually easier not to enter the location of a file while pushing so cd to the directory first like
cd C:\Users.....
Then once there adb push /nameoffile /locationonphone
But if you don't want to cd, I see you have widows, depending on version you can just right click in the folder your file is located and choose open cmd here
Sent from my Nexus 7 using XDA Premium 4 mobile app
Need Help
As I thought I bought LG G2 D-802, but it was D-800 and I accidentally install the lollipop of D802 and now it's in bootlap.... I can only get into fastboot and whenever I try to flash .img of D-800 or D-802 it just stuck at "writing .img"
What to do to unbrick the phone and bring it back to live. I tired the adb and fastboot cmd method on windows 10 and windows 7 but no success. It's just stuck at writing .img file.
My tmobile LG k20 plus phone has a boot loop and will not start, this happened when I copied a file to the main directory of my phone, instead of merging the files it deleted the system folder, I tried to fix it by reinstalling twrp and it worked, after flashed twrp I installed a fresh SuperSU ROM and when I did the boot loop did not go away and in addition to this my computer will no longer find my phone through ADB or fastboot, if you can help I will be amazed and quite happy, I'm new here so any help is appreciated
bump:fingers-crossed:
megamind994 said:
My tmobile LG k20 plus phone has a boot loop and will not start, this happened when I copied a file to the main directory of my phone, instead of merging the files it deleted the system folder, I tried to fix it by reinstalling twrp and it worked, after flashed twrp I installed a fresh SuperSU ROM and when I did the boot loop did not go away and in addition to this my computer will no longer find my phone through ADB or fastboot, if you can help I will be amazed and quite happy, I'm new here so any help is appreciated
Click to expand...
Click to collapse
did u ever get it figured out? i am in the same boat grr
I found a program called lgup which was able to fix the phone, it's capable of flashing a new rom onto a soft bricked phone. Sadly I don't recall any specifics but on a quick search for "lgup lg k20 plus" you should be able to find what you're looking for with relative ease. Also, you may want to consider making your own thread on the future... It has been 3 years
megamind994 said:
I found a program called lgup which was able to fix the phone, it's capable of flashing a new rom onto a soft bricked phone. Sadly I don't recall any specifics but on a quick search for "lgup lg k20 plus" you should be able to find what you're looking for with relative ease. Also, you may want to consider making your own thread on the future... It has been 3 years
Click to expand...
Click to collapse
thanks
Yeah. Sorry for the late reply given you guys found the fix by now, but yes, generally with the sort of severe mishaps from editing or accidental deletion of certain system files or directories, sometimes a dirty flash or even a totally clean flash after performing data ave system partition wipes, will just not fix or restore the device.
You would then need to do a complete stock image reflash either using LGUP or the official LG software recovery tool. If you know what you're doing, you could skip over reflashing stock in its entirety, if say you know the problem has only to do with a particular protected partition like modem, EFS, etc. But generally good practice to just recover all the stock partitions, refresh the device software to factory conditions, reflash your bootloader and recovery images, root STOCK or install custom ROM, so on and so forth.
If you're a frequently curious tinkerer, making backups will be crucial to your sanity.
Hi. I'm just gonna say this first: I didn't know entirely what I was doing when beginning this operation. I was just trying to do something fun and new, and it didn't pan out. I fully acknowledge that I am an idiot.
Now, the story. I was attempting to root my LGV20 with this guide: https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500 .
I have read over this thread more times than countable and thought I was doing everything correctly. I got to the "STEP3.BAT" portion of the guide and long story short, my phone crashed during it and somehow got foobarred.
It *kinda* works (as in it will boot for around a minute) and then blue/black screen into a reboot.
Is there any way I can save this phone? Hard resets, going into software, more dumb computer stuff, anything. I don't *need* to get this phone working again but it would be really preferable.
Simultaneously I fully accept the responsibility in failing the operations. I know that somewhere I must have messed up. If no-one wants/ can help me, tell me so. Just means new phone time.
If any more detail on what happened is needed, tell me.
First off: that guide is ONLY for the H910 (AT&T) variant, so make sure with your model
and also, when you said a "blue or black screen" it also has very small writings too, right? If so, then you may have faced a kernel/bootloader panic
Technically your phone is *still* alive, and your best method is to start over again, assuming if you read the whole guide carefully then you have backed up your firmware and can still access download mode.
Flash your stock firmware back (or use the H915 firmware provided by the guide), wipe and setup your phone again, then root the phone again.
I also suggest replacing the TWRP recovery inside the provided Dirtysanta folder cuz that's what i did when i faced the kernel panic
MEMO#22 said:
First off: that guide is ONLY for the H910 (AT&T) variant, so make sure with your model
and also, when you said a "blue or black screen" it also has very small writings too, right? If so, then you may have faced a kernel/bootloader panic
Technically your phone is *still* alive, and your best method is to start over again, assuming if you read the whole guide carefully then you have backed up your firmware and can still access download mode.
Flash your stock firmware back (or use the H915 firmware provided by the guide), wipe and setup your phone again, then root the phone again.
I also suggest replacing the TWRP recovery inside the provided Dirtysanta folder cuz that's what i did when i faced the kernel panic
Click to expand...
Click to collapse
Thanks so much. Freaked out over this for a good bit. Came back, did what you said and we're back at that step fully working. Life saver.
Now my first guess as to why step3 failed is that i didn't have the latest version of TWRP. How can I set that up?
Inside the root package folder you can see an .img file named twrp 3.0.2-1- us996.img
What i did was downloaded a later version
(not latest cuz my phone won't boot at the latest version for some reason), copied the name of the original twrp and renamed it, paste it to the folder, overwrite the old one, and try to root it again
MEMO#22 said:
Inside the root package folder you can see an .img file named twrp 3.0.2-1- us996.img
What i did was downloaded a later version
(not latest cuz my phone won't boot at the latest version for some reason), copied the name of the original twrp and renamed it, paste it to the folder, overwrite the old one, and try to root it again
Click to expand...
Click to collapse
Alright, i've done that now too. Thanks. Is there anything else i should/need to keep in mind to ensure failure is not going to happen? I want to make 100% sure I get everything right this time.
reptarien said:
Alright, i've done that now too. Thanks. Is there anything else i should/need to keep in mind to ensure failure is not going to happen? I want to make 100% sure I get everything right this time.
Click to expand...
Click to collapse
No i don't think there is more things to do, the guide you're following is pretty much straightforward already.
100% guarantee is always a stretch here in XDA. But if you're still facing problems you can ask for help on that guide's thread.
MEMO#22 said:
No i don't think there is more things to do, the guide you're following is pretty much straightforward already.
100% guarantee is always a stretch here in XDA. But if you're still facing problems you can ask for help on that guide's thread.
Click to expand...
Click to collapse
I really want to give up on this. This time I successfully made it through all Step 3, but I also noticed that my screen was kind of glitched and not rendering properly at that stage. After it rebooted, I unplugged my micro usb cable and it gave me an angry green warning message I will attach here.
If you/someone can tell me what to do with this message from here or instruct me on how to flash stock H910 10 q back onto the phone without doing TWRP (since i'm evidently incapable of installing it) I would be most appreciative.
Slightly better picture without anything cut off.
reptarien said:
I really want to give up on this. This time I successfully made it through all Step 3, but I also noticed that my screen was kind of glitched and not rendering properly at that stage. After it rebooted, I unplugged my micro usb cable and it gave me an angry green warning message I will attach here.
If you/someone can tell me what to do with this message from here or instruct me on how to flash stock H910 10 q back onto the phone without doing TWRP (since i'm evidently incapable of installing it) I would be most appreciative.
Click to expand...
Click to collapse
The screen glitching is normal, the green text after boot however is somehow not.
Sad to hear that it still didn't work, there something seems to be interrupting the process of rooting your phone. I dunno if it has something to do with ARB (anti rollback) preventing you to root
If you want to go back to your stock firmware that you backed up, you can:
-Carefully flash each file of your backed up firmware through adb and fastboot mode
-build a zip file of your firmware and flash through TWRP (since it didn't succeed tho)
MEMO#22 said:
The screen glitching is normal, the green text after boot however is somehow not.
Sad to hear that it still didn't work, there something seems to be interrupting the process of rooting your phone. I dunno if it has something to do with ARB (anti rollback) preventing you to root
If you want to go back to your stock firmware that you backed up, you can:
-Carefully flash each file of your backed up firmware through adb and fastboot mode
-build a zip file of your firmware and flash through TWRP (since it didn't succeed tho)
Click to expand...
Click to collapse
Could you reply with any links with a tutorial on how to do the first thing? Or describe it. Sorry for being so dumb i'm a total newbie lol
reptarien said:
Could you reply with any links with a tutorial on how to do the first thing? Or describe it. Sorry for being so dumb i'm a total newbie lol
Click to expand...
Click to collapse
Unfortunately i can't find any guides when it comes to flashing the back up.
I did read something back then on turning it into a zip file, but even if you can build one you still need TWRP, in which case you haven't successfully installed, so that's no option
Flashing the backup files requires specific commands, especially to the part on what partition should it be flashed to
When LGUP backs up your phone's firmware, you can see a vast number of files(i can't remember how were they named, I'll look up a reddit post about it)
The files where named based on what partition it came fom (H910_modemxx_COM12, H910_system_COM12 or something like that)
These are image files, what i did as far as i can remember was rename these files by adding an IMG extension for ADB to recognize
Flash them according to it's partition name:
"Fastboot flash system H910_system_COM12.img"
"Fastboot flash recovery H910_recovery_COM12.img'
Etc.
To go to fastboot, turn off your phone and hold the volume down button , then plug your phone to the PC.
But i really cannot guarantee this, because for all i know, in order to flash this you need fastboot, and to get fastboot you need to root your phone, because only the engineering bootloader has it (i'm sorry if it's wrong tho), and flashing these files to fastboot might be a bit dangerous because it will not verify the files, there may be chances that you might flash a corrupted file. so flashing via LGUP is the safest option so far if you don't know what you're doing