Hi XDA,
I've been trying to find a solution for this particular problem, have tried several solutions presented in various threads, but none of them have actually helped me solve the issue. In short, I'm running the LGE988 and can't seem to flash another ROM. I can however always access the recovery and it doesn't matter which one (CWM, TWRP, PhilZ). From the recovery I can install .zip files, but no rom would actually get installed. It just reboots back into recovery and if I look on the internal sdcard it would show nothing new.
I've tried using LG Flash Tool to go back to the original ROM, which worked before, but now I'm getting the low battery notification. I've tried all the solutions presented in the threads to work around it, but no luck so far.
ADB sideload is not functional on any of the recoverys either.
Any suggestions?
Thanks!
Related
I lov using my phone explorer app, Everything works great except I used to be able to control my phone using my PC keyboard n mouse in the phone view.
I've upgraded my my phone to CM7 and it give an option to select My phone explorer as an external keyboard.
I cant get it working without selecting the option of external text in the appropriate input on my phone which sort of defeats the whole remote angle.
Can anyone help please ....
Bootloop solved
I read this thread trying to figure out why my phone (marvelc A510c virgin mobile) went into bootoop after trying to installing simonsense3.5 rom, and thought I'd share my success story. This is actually my first post. I want to hopefully save someone like me HOURS of heartache over a stupid solution.
Background (roughly):
Unlocked bootloader via htcdev, worked great.
Used Simonsimon34's htc utility and it worked okay. I still had to use the htc supertool to get root.
Got cwm 5.0.2.8 installed and made a backup rom
Downloaded simonsense3.5 rom and attempted to flash it, but phone hanged in recovery. After that, I was stuck in a bootloop. Could still get into recovery, but cwm would hang ALL the time doing things like wiping and I couldn't get it passed "Opening Update Package" when flashing new roms. I read forum after forum, reformatted my sd, wiped partitions, got a second sd, tried 3 or 4 roms people swore would work, did it all over again. Nothing! I found a thread that said to back cwm down to 5.0.2.6, but that didn't work. This went on for two days and I was getting desperate.
SOLUTION:
I finally found a thread (http://forum.xda-developers.com/showthread.php?t=1213229) that posted cwm 4.0.xx (the "previous version" link) and at my wits end flashed that, and wouldn't you know it, success! CWM was the problem the whole freaking time! I used the cwm partition creator to make a fresh 1024b partition on a fresh sd, wiped everything, put the rom on, and installed simonsense3.5 on the first damn try. The rom works okay, but I'm having some bugs... but that is another forum.
Good luck!
Good Morning,
I've searched through the forums and so far haven't had any luck. I apologize if this is a topic that's been covered to death, which it likely has, but I haven't found a solution to my particular problem.
Galaxy Tab Pro 10.1.
I was having problems with TouchWiz crashing, usually 2 to 3 times per day. Sometimes it would lock up the unit, requiring me to reboot. Sometimes it would just come back after 5 or so minutes. Whatever the case, I decided, since I was already interested, that I would try to root the device, clear up some memory, maybe even flash a new ROM to take care of the issue.
First, I successfully rooted the device, no problem. Surprisingly easy, actually, following steps from this website.
I loaded SuperSU, Titanium Backup, Greenify - but still had (more rare) instances of TouchWiz crashing, and even the entire unit rebooting itself occasionally. So, I decided to take a stab at Cyanogenmod 11.
After attempting to load Cyanogenmod using Heimdall and Odin, and having issues I'll add, I finally realized that (theoretically) I could just use ROM Manager to load the file. Cool! So I loaded the zip file for CM11 onto the top level of my SD Card, created a recovery, and attempted to load the new ROM. The first problem I had was that the unit wouldn't just load the ROM like I expected, but it put me into recovery mode. I suspect that's not right, but I attempted to go ahead and use the menu picks to load the ROM anyway. I wiped data/factory reset, them wiped cache partition. Then, I selected "apply update from external storage". I selected the zip file for CM11, which was right where I left it, hit select, and had the following problem.
I got the following errors, two times, in red text (with other yellow text messages surrounding);
E:footer is wrong
E:signature verification failed
So...what do I need to do here, folks? Worst case scenario, obviously, I just keep using TouchWiz, as I haven't managed to brick my device yet, and I would still be able to utilize root access apps. But I have to be close, aren't I? Does anyone have the patience to help out a guy who only knows enough to be dangerous?
You need to use custom recovery to flash custom ROMs. It sounds like you are trying to use stock recovery.
redpoint73 said:
You need to use custom recovery to flash custom ROMs. It sounds like you are trying to use stock recovery.
Click to expand...
Click to collapse
Thanks for the reply. I'm not sure what I did wrong, but I decided to give TWRP recovery a shot, and was getting an error on the CM11 zip file. I re-copied over the zip file, tried again, and that did the trick. I guess I either had a bad zip file, the wrong recovery, or both.
Thanks!
Robb
Sometimes I had problems flashing zips from external storage, appeared as corrupted, never a problem when zip was in internal storage . Did you try that?
thdervenis said:
Sometimes I had problems flashing zips from external storage, appeared as corrupted, never a problem when zip was in internal storage . Did you try that?
Click to expand...
Click to collapse
No, I did not try that, as simply recopying the zip file onto the SD card did the trick.
I spent all evening playing with the settings, trying out themes, setting up my apps - and my unit didn't crash one time. Pretty slick!
Now I just need to learn how to use Titanium Backup to store settings so I can play with different ROM's.
I am a frequent experience Android user and have been flashing Roms since like forever.
Owning gs4 been nice installing Roms all the time however recently when I went to install new gpe ROM (new kernel seemed prime to have) coming from HDrom rls20 I downloaded currupt zip. When I tried installing currupt zip (not knowing yet it was currupt) it gave me red errors not allowing me to proceed.. Then, I turned off device got fresh dload and made sure md5 sum was legit and it was tried again of course first factory data reset with advanced system wipe the ROM proceeded to aroma installer this time.. Attempting to install I chose all my settings and it went to progress bar to install and skipped any system extraction and went straight to Apks.. Batch completed and I hadn't a ROM installed for it took it 5seconds.. I have had this problem in the past before and I sold it they returned it (didn't like condition) and bingo I was able to install Roms again (this was way back in the day with this same gs4) I'm assuming system partition not mounting because also when I tried installing that currupt file it was saying in red unable to mount system and stuff. Luckily I downloaded NK2 firmware (took 8hs) and am fine on stock but I'm hoping someone has a clue to point me in right direction.. I saw forum of somebody with similar issue their fix was pushing zip via computer adb commands then installing. I'll have to give it a try but sticking to stock for a bit. BTW this happens with every ROM just skips system files in fact cyanogenmod just hhung at installation wouldn't fail or complete. I used TWRP LATEST. Please help developers I'm sure this ones a no brainer for y'all. Except seems like issue only I've encountered for this isn't a popular thing at all on google.
SOLVED
Thanks to somebody in gs3 forums all i had to do was push adb the rom and wow it worked installed system YAY IM HAAPPPYY
Stoowyguy said:
Thanks to somebody in gs3 forums all i had to do was push adb the rom and wow it worked installed system YAY IM HAAPPPYY
Click to expand...
Click to collapse
What does it mean to "push adb" a phone's rom? Doesn't Odin automatically flash the selected rom?
My SM-T210 (Galaxy Tab 3 7.0 Wifi) XSP region which was running fine for over a year starting giving me the Kernel Panic Upload Mode errors in the last few days.
It is absolutely stock - still running Android 4.1.2, never rooted, etc.
From previous threads on this error, it seems that doing a factory reset in recovery ought to fix this. However, I can't quite seem to do the factory reset. Doing it from Android settings just seems to go into recovery. And from recovery, after telling it to do the data wipe/reset and rebooting, I'm back into Android with all of my apps and settings still in place.
So I'm a newbie and don't know what to do from here. Any suggestions please?
Ok, I've tried to flash the TWRP recovery by following the instructions at http://forum.xda-developers.com/showthread.php?t=2437219. But even after getting "RES OK", I did the reboot into recovery, and went straight back into the stock recovery. wtf... it seems as though writes to the internal storage are accepted but ignored.
Still hoping for some pointers, please...
I'm guessing that the problem is that the writes appear to succeed but actually did not take place at all. To test this, I've booted up, used ES File Explorer to create a "test" file and rebooted. Upon rebooting, the file has disappeared even though the kernel did not panic during this process.
Has anyone seen such symptoms before? My search-fu is lacking, and I can't find appropriate search results.
webbrowser said:
Still hoping for some pointers, please...
I'm guessing that the problem is that the writes appear to succeed but actually did not take place at all. To test this, I've booted up, used ES File Explorer to create a "test" file and rebooted. Upon rebooting, the file has disappeared even though the kernel did not panic during this process.
Has anyone seen such symptoms before? My search-fu is lacking, and I can't find appropriate search results.
Click to expand...
Click to collapse
I have heard many stories before about kernel panic upload mode. I believe it might be a kernel issue in which changing it would be a good idea or some sort. That's all I know ?
-DUHA
DUHAsianSKILLZ said:
I have heard many stories before about kernel panic upload mode. I believe it might be a kernel issue in which changing it would be a good idea or some sort. That's all I know
-DUHA
Click to expand...
Click to collapse
Roger. I've tried to flash the TWRP recovery via ODIN, but the writes did not seem to work despite "RES OK". Flashing recovering is required before I can change the kernel right?
For what it's worth, my symptoms seem to match the "emmc brickbug".
I've found what appears to be instructions on how to fix this after the brickbug has occured here (these are for different devices, but I suppose it oughta work):
http://forum.xda-developers.com/showthread.php?t=1823918
http://forum.xda-developers.com/showthread.php?t=1667886
Unfortunately, I can't seem to run the zips from my stock recovery, as signature verification fails. And I don't think I can install a custom recovery at this point now, since all writes seem to fail. So I'm still stumped, and I think I have a brick :crying:
I was needing a new phone and saw a Linus Tech Tips video where he took an LG G3 and put LineageOS on it. So I thought I'd try it out for myself following his guidelines at https://linustechtips.com/main/topic/1058206-lg-g3-lineageos-tutorial/
I bought an LG G3 D851 (T-Mobile version) off EBay for this. It's my first Android phone (yes, experimenting on my first Android Phone), I've always used Windows phones. This is what I've done to the LG G3 so far:
I reverted back to KitKat. Everything seemed to have gone just fine.
Then I downloaded the the Full Purple Drake Root and ran that after I figured out that .gz files are a compressed file and that can be decompressed. Everything seemed to have worked fine.
Then I downloaded the TWRP app on the phone and tried to backup the recovery via the TWRP app, which I'm not sure if it worked correctly. But anyhow.
Now that I'm writing this I see I missed this step:
number seven: Select the TWRP file we copied over earlier in the app, flash it to recovery, and then reboot to recovery
Click to expand...
Click to collapse
I guess I just didn't understand what was meant by flashing it over and has just copied it to the phone's memory which I later wiped.
Well then I went into TWRP recovery and tried to do a recovery backup, which it seemed to do just fine. I rebooted and tried copying it over to the computer, which seems to not have worked. I just have an empty folder on my computer as we speak.
Then back in the TWRP recovery, I selected Wipe>Advanced Wipe, and select Dalvik, Cache, Data, Internal Storage, and System – then swipe to wipe.
Then I downloaded the latest version and nightly of LineageOS zip file and the Opengapps zip file but then had a hard time figuring how to get them to the phone.
I figured out that I could stick them on an SD card and slip it into the LG G3 that I'm working on and could see the files from the TWRP recovery menu.
So I tried to install the LIneageOS zip file several times and it didn't work. I'm guessing it's because I forgot to flash a certain file to TWRP recovery and am not sure how to do that, especially now with the phone only booting into recovery mode with the TWRP menu since it's wiped clean and will just display the LG logo and turn the LED different colors if I try to normal boot the phone.
Well I still want to try to fix the phone and go for LineageOS. I spent nearly all night working on it so I may give it a rest for a few days. But any help or pointers would be greatly appreciated.
Now that I think about it, I didn't do what I mentioned ok #4 above about flashing the TWRP recovery because TWRP recovery was installed with the full Purple Drake root. However, the Linus Tech Tips instructions point to them rooting the phone with the lite version of Purple Drake (root only) and then flashing the newest version of TWRP recovery. So I wonder if my problem has to do with my having the latest version of TWRP recovery on my phone.
Ok. So I think I'm making progress, although that's just a feeling I have since I'm not suite what I'm really doing.
Anyhow the error code was something like "Unknown Error, Error Executing Updater Binary in Zip, Zip is for LG G3 D851, this phone is...(blank)". So I found an article in DroidThunder.com talking about this very problem. It suggested unzipping the rom on my computer and looking for the updater-script file and erasing some lines that apparently only have to do with verification. Then re-zip and retry.
Now I'm getting a "No MD5 file" message followed by an "Error flashing zip" message.
Edit: After reading this I take it I have an older version of TWRP, that is, v2.7.1.0, whereas the newet versio (for this phone?) is apparently 3.3.1-0. That seems to have an effect on this. I wonder if it's possibly to flash a newer version of TWRP onto this bricked phone. Anyhow, I'll have to look into that later. It's time to call it a day.
So recently I've been focusing on these two threads:
[GUIDE] LG G3 D851 Unbrick Qualcomm 9008 Fully Working... Unbrickable D851! by Omar-Avelar
And:
[GUIDE][FIX][DISCUSSION] LG G3 Hard Brick Recovery by l33tlinuxh4x0r
But I can't get either of them to work. I guess the only other thing would be to try to find a ROM, preferably the original KitKat that came with the phone, and hope and pray that I can get TWRP recovery v2.7 to install it.
I have the original as a tot file. But as far as I understand, I need a zip file that's set up for TWRP recovery.
Anyhow, trying to get this phone running hasn't been easy and has made other problems. Now every time I turn on my Surface 3 I have to go through BitLocker authentication. Hopefully turning bcd Test Signing off will stop that. But I'm getting to the point that I'm feeling like giving up.
Well that's it. Last night I found a zip file for the original Marshmallow ROM for my G3. I got it onto the SD card, went into TWRP recovery, saw it install, restarted and...
Now it's hard bricked. I cannot even get into TWRP recovery. The screen won't show a thing. I tried several times to get it into any mode possible, normal boot, TWRP recovery boot, download mode, and that jumping the pins trick, and I can't get it to where I can do something with the phone.
So I'm giving up on all this rooting, custom recoveries and custom ROM stuff. It all seems like a good idea, and I'd love to be a part of it all. But I take it this isn't for me. So I give up.
Thanks to all who have worked on this and have made the helpful forums about these phones! Maybe if I were more competent I would have figured it out.
Well, I said I was giving up. But maybe not. I did give up trying to recover the phone from being bricked and sent it out to a JTAG shop. For about $40 the phone is supposedly fixed and on it's way back.
But when it's back, do I just leave it alone this time, or should I try to get Lineage OS back on it again? Well, this is something that I haven't made my mind up yet. I see where I had made several mistakes when I first tried to get LineageOS on it. Maybe I know enough now that it won't happen again. But at the same time there's no guarantee that I won't me it up again, and have to pay some $40 again to have it unbricked.
SUCCESS!!!
So I got my phone back with stock Marshmallow working. Then I carefully went through every step on the Linus Tech Tips site, including installing the latest version of TWRP, and the next thing I know I'm running LineageOS 16 on my phone!
This is great! It's my first Android Phone and I've got it setup just about perfect! The only thing I kind of miss is Wi-Fi calling. But that didn't work so well on the Alcatel Window's phones I had anyway. But I got all the apps and most of the music I need installed and am ready to go! I also have two batteries, and the original isn't too bad, so I might carry that around as a backup until I'm sure how much battery I'll be using.
I'll be coming back and thanking all the ones who's posts and work have helped me individually. But if you read this and are one of those who have worked on TWRP, LineageOS and anything else that has helped me, Thank You!