Develop Bugs

[Q] Error switching to Cyanogen

I have a G2. I decided to root it using the guides on Lifehacker and Cyanogens wiki. I got a temproot using Visionary, and permaroot using terminal. Everything went swimmingly. I only used download links that I found on Lifehacker and on Cyanogen's site (the same places I got the guides to root my phone) I attempted to root my phone and put CM7 on it. I backed up everything with Titanium Backup. I downloaded Rom Manager, flashed ClockworkMod Recovery to get the latest version, downloaded CM7 through Rom Manager, and attempted to install it as well as backup existing ROM and wiping data and cache. My G2 returns to the HTC startup screen and just stops.
I tried to do a factory reset, it just stops at the same area. I tried doing a factory reset from the startup options (power and down volume), nada. I tried reflashing ClockworkMod Recovery, zilch. I restored my backup from Titanium, nothing.
The phone works, I'm able to do everything I would normally do on it, but I just can't get this to work and I don't know where I went wrong or how to fix it. I have experience with UNIX based systems so I know how to work a command line to an extent and I know that part went off without a problem. I just can't figure out what's going on with it.

can you connect to your phone using adb? if you can access the shell you might be able to figure out why it's hanging.

ADB
I'm not sure I've tried ADB, any tips?
Are you talking about hooking it up to my computer as an alternative method to flash it? I had a bit of trouble with that because my computer is currently down (I just moved and don't have the room to set it up yet). I think I need a copy of the original ROM for my phone as well, if I get that I believe I can restart the whole process and do it right this time. Any ideas where to get it?

yes hook it up to the PC, even if it's in a bootloop you might be able to access the phone's system to do repairs using adb to enter the shell.
check this thread: http://forum.xda-developers.com/showthread.php?t=865685
it also explains how to use it
http://developer.android.com/guide/developing/tools/adb.html
this one got all the adb commands.
I'm not sure about the log command, but there's a way to call on the system log to see where it fails.
it's not recommended to flash an original image again, you can try to restore the backup of the original ROM (nandroid backup) if you made one...
hope this can help you.

Sounds like there is a problem with your recovery, try to manually flash recovery using flash_image instead of ROM Manager.
Use this thread for a guide: http://forum.xda-developers.com/showthread.php?t=902493
You can get the latest version of CWM (currently 3.0.2.4) here: http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html just scroll down to the link that says "HTC G2"
After you flash try to manually go into recovery by shutting down the phone and powering it up while holding the volume button down, this should bring you into the bootloader menu and allow you to launch recovery.

Thanks!
I'll give that a try as soon as I can, thanks for the assistance!

Stuck in a boot-loop

Hello everyone!
First of all, I would like to apologize, as these kind of issues have probably been talked about and solved a gazillion of times before, but the thing is, I'm having a hard time grasping the start and the end of this issue myself, as the phone that is stuck in a boot-loop isn't mine - it belongs to a friend of mine who somehow managed to get the whole thing bricked.
Anyhow, I'll start off with what I know;
His goal was to flash a new ROM (http://forum.xda-developers.com/showthread.php?t=1601543). He unlocked the bootloader and rooted the phone using these instructions; http://onexroot.com/one-x-root/how-to-root-one-x/). He succeeded in doing so and decided to move onto flashing the rom.
But the problems started when he read that he's first supposed to flash "Android Fastboot kit 2.1" onto the device, prior to flashing the device. And so he did. Or well, tried - what he told me was that he booted the phone into fastboot mode, then ran the "Install Boot.img" bat file inside the Fastboot Kit folder he downloaded and after that, the phone got bricked.
Now, my knowledge in this area isn't too great either, but I've flashed a few ROMs in my life before, so, I decided I'd do my best to help. But I have no clue on what steps he should take from here on.
To my understanding, he was running the official 1.29 version and he is still able to access the boot-loader as well as Clockwork Recovery mod. To my understanding, he didn't create a back-up of his previously working ROM and the phone won't show up in Windows Explorer while connected via USB either.
To my limited understanding, I should now try and install the rom onto his phone and once done, the whole thing should work - the only problem with that is the fact I can't get the ROM zip onto the SD Card right now, as explorer won't recognize it. So far, I tried using ADB to push the ROM file onto the phone, but every time I use the command "adb shell mount /sdcard" I get a "Device not foound" error. So, I'm kinda stuck here right now. If this even is the right way to solve the issue, that is.
So, like I said, I'm having a hard time grasping the start and the end of this issue myself, and if there is any additional information needed, I'll do my best to find out more about it - I do have the phone in my possession at the moment as well.
Thanks a lot to anyone who'll offer any kind of help!

Atraeh said:
Hello everyone!
First of all, I would like to apologize, as these kind of issues have probably been talked about and solved a gazillion of times before, but the thing is, I'm having a hard time grasping the start and the end of this issue myself, as the phone that is stuck in a boot-loop isn't mine - it belongs to a friend of mine who somehow managed to get the whole thing bricked.
Anyhow, I'll start off with what I know;
His goal was to flash a new ROM (http://forum.xda-developers.com/showthread.php?t=1601543). He unlocked the bootloader and rooted the phone using these instructions; http://onexroot.com/one-x-root/how-to-root-one-x/). He succeeded in doing so and decided to move onto flashing the rom.
But the problems started when he read that he's first supposed to flash "Android Fastboot kit 2.1" onto the device, prior to flashing the device. And so he did. Or well, tried - what he told me was that he booted the phone into fastboot mode, then ran the "Install Boot.img" bat file inside the Fastboot Kit folder he downloaded and after that, the phone got bricked.
Now, my knowledge in this area isn't too great either, but I've flashed a few ROMs in my life before, so, I decided I'd do my best to help. But I have no clue on what steps he should take from here on.
To my understanding, he was running the official 1.29 version and he is still able to access the boot-loader as well as Clockwork Recovery mod. To my understanding, he didn't create a back-up of his previously working ROM and the phone won't show up in Windows Explorer while connected via USB either.
To my limited understanding, I should now try and install the rom onto his phone and once done, the whole thing should work - the only problem with that is the fact I can't get the ROM zip onto the SD Card right now, as explorer won't recognize it. So far, I tried using ADB to push the ROM file onto the phone, but every time I use the command "adb shell mount /sdcard" I get a "Device not foound" error. So, I'm kinda stuck here right now. If this even is the right way to solve the issue, that is.
So, like I said, I'm having a hard time grasping the start and the end of this issue myself, and if there is any additional information needed, I'll do my best to find out more about it - I do have the phone in my possession at the moment as well.
Thanks a lot to anyone who'll offer any kind of help!
Click to expand...
Click to collapse
The latest Clockwork jobby will allow you to mount the sdcard as USB drive.
Other than that, you seem to be on the right track.

^ he's right
What you want to do is first download the 5.8.4.0 version of the endeavoru CWM recovery.
reboot to your bootloader, make sure you're in fastboot and flash the new recovery img.
After you have successfully flashed the new recovery, well... go to the recovery
On the recovery, tap mounts and storage, then tap Mount USB. VOILA!!!!!

Yeah, I forgot to mention that I've already tried mounting the SD Card via Clockwork Recovery - I get an error saying "Unable to open ums lunfile (No such file or directory exists). So that doesn't seem to be an option either, unless you have an idea on how to counter this?
EDIT: Ah, I see - he's using an older version. I'll get the latest one on board and give it a go. Will have to wait a bit for the phone to charge up first it seems though. Not enough battery to do it right now .
Thanks!

And voila! The phone is operational.
Thanks a lot for the help and, I just hope I never manage to half-brick my own HOX .

[Q] Nexus 7 won't connect to Windows, can't root, can't flash - stuck?!

So I rooted my Nexus 7 (2013) a while back, and it was working fine. I have TWRP recovery installed, bootloader unlocked, and I thought it was rooted. Then (don't kill me, I can't remember what I did, it was so long ago - I think maybe I installed the official KitKat update, although I am pretty sure I sideloaded a rooted version of the stock KK ROM), root just stopped working. Root Checker says I'm not rooted, even though I have the SU app installed. So, I thought, I'll just flash the SU.zip from recovery. So I flash it. And literally nothing happens. It says it flashed successfully, but when I reboot, no root.
In fact, any time I flash anything, it appears to work, but doesn't actually do anything. I tried flashing a different ROM and no dice. I tried accepting the official 4.4.2 update and again, looked like it flashed, but was still 4.4 when I rebooted.
So I thought I'll just plug it into my PC and re-root and maybe flash everything if need be. Except, when I plug it in, it 1) isn't recognized by my computer at all, no matter how many times I uninstall and reinstall drivers, and 2) the ADB connected icon doesn't show up, even when I enable it in Developer Settings.
So basically I'm dead in the water: I can't do anything via recovery, and if recovery is messed up, I can't do anything because it won't connect to my computer (Windows 7, SP1, 64 bit). I have a Mac running OS X Mavericks, if anyone knows some Terminal tricks for stuff.
So…advice?

darnocs1 said:
So I rooted my Nexus 7 (2013) a while back, and it was working fine. I have TWRP recovery installed, bootloader unlocked, and I thought it was rooted. Then (don't kill me, I can't remember what I did, it was so long ago - I think maybe I installed the official KitKat update, although I am pretty sure I sideloaded a rooted version of the stock KK ROM), root just stopped working. Root Checker says I'm not rooted, even though I have the SU app installed. So, I thought, I'll just flash the SU.zip from recovery. So I flash it. And literally nothing happens. It says it flashed successfully, but when I reboot, no root.
In fact, any time I flash anything, it appears to work, but doesn't actually do anything. I tried flashing a different ROM and no dice. I tried accepting the official 4.4.2 update and again, looked like it flashed, but was still 4.4 when I rebooted.
So I thought I'll just plug it into my PC and re-root and maybe flash everything if need be. Except, when I plug it in, it 1) isn't recognized by my computer at all, no matter how many times I uninstall and reinstall drivers, and 2) the ADB connected icon doesn't show up, even when I enable it in Developer Settings.
So basically I'm dead in the water: I can't do anything via recovery, and if recovery is messed up, I can't do anything because it won't connect to my computer (Windows 7, SP1, 64 bit). I have a Mac running OS X Mavericks, if anyone knows some Terminal tricks for stuff.
So…advice?
Click to expand...
Click to collapse
Does it recognize your device when it's booted into the bootloader (aka fastboot mode)?

charesa39 said:
Does it recognize your device when it's booted into the bootloader (aka fastboot mode)?
Click to expand...
Click to collapse
It didn't, but I found I was using a bad USB cable. Swapped out, and now it works (yay). However, root still wouldn't work after I ran several rooting methods from the computer.
Finally, I went to the Play Store, downloaded Superuser from Clockworkmod, followed their link in that description to download the flashable zip, flashed that, and FINALLY got root working. So happy.

darnocs1 said:
It didn't, but I found I was using a bad USB cable. Swapped out, and now it works (yay). However, root still wouldn't work after I ran several rooting methods from the computer.
Finally, I went to the Play Store, downloaded Superuser from Clockworkmod, followed their link in that description to download the flashable zip, flashed that, and FINALLY got root working. So happy.
Click to expand...
Click to collapse
Cool. Glad it worked out for you. :good:

[SOLVED!] Problem getting ANYTHING onto the E980

Well, as usual, I've managed to mess things up and here I am again. Somehow, I installed something or other that required rebooting. When I did, I kept getting an error that the systemui was messed up. So I decided to try to flash a custom ROM since it appeared this thing was already FUBAR and that's where the fun began. It WAS running stock 4.4.2. I wiped everything in preparation to flash the stock .tot file. Went to flash a zip from the external sdcard, and it refused telling me it couldn't mount the card! The only hopeful thing is that it powers up, I can get into download/recovery, and it's recognized by the PC through LGFT and ADB.
I can't flash anything, can't push or install through ADB, can't sideload anything. LG flash tools gets to about 38 seconds and then fails. It's like the devices permission were all changed to read only. The device is rooted and has CWM recovery. Is there a way to completely slick this thing (except for recovery - I'd do that too if need be) to reset permissions.
Any/all suggestions gladly accepted.

gjtoth said:
Well, as usual, I've managed to mess things up and here I am again. Somehow, I installed something or other that required rebooting. When I did, I kept getting an error that the systemui was messed up. So I decided to try to flash a custom ROM since it appeared this thing was already FUBAR and that's where the fun began. It WAS running stock 4.4.2. I wiped everything in preparation to flash the stock .tot file. Went to flash a zip from the external sdcard, and it refused telling me it couldn't mount the card! The only hopeful thing is that it powers up, I can get into download/recovery, and it's recognized by the PC through LGFT and ADB.
I can't flash anything, can't push or install through ADB, can't sideload anything. LG flash tools gets to about 38 seconds and then fails. It's like the devices permission were all changed to read only. The device is rooted and has CWM recovery. Is there a way to completely slick this thing (except for recovery - I'd do that too if need be) to reset permissions.
Any/all suggestions gladly accepted.
Click to expand...
Click to collapse
Surprisingly, there was nothing wrong with the phone nor the software nor the PC. After screwing around with this for a couple of days, I had a thought to try a different USB cable. So, I popped it on and, lo & behold, I'm able to flash to stock! Lesson learned: Don't use cheap cables and try changing cables when you're have weird problems like this. :good:

[Q] Bricked Gpad 8.3 - stock rom via LG Flash Tool not working

So. Recently, I got CyanogenMod 13 on my Gpad. Everything was just fine. Then I installed the Magisk Manager, which, for some reason, disabled the root access on the device. When I uninstalled it, my recovery (TWRP) asked me, if I want to install SuperSU. I selected yes. And that's the moment when everything fcked up. After SuperSU installation, my tablet went into bootloop, and I wasnt't even able to enter recovery via button combination. I tried to flash the stock rom via LG Flash Tool, but failed miserably. I tried multiple stock roms, but the result is till the same: I can't access the Factory Reset via buttons, the system keeps rebooting, and even if it boots for few seconds, the touchscreen isn't responding. I even tried connecting mouse via USB otg, but no success. Is my tablet dead? Is there any chance of repairing it?
Thank you for your help.
EDIT: It's v500 European version.

Czechball said:
So. Recently, I got CyanogenMod 13 on my Gpad. Everything was just fine. Then I installed the Magisk Manager, which, for some reason, disabled the root access on the device. When I uninstalled it, my recovery (TWRP) asked me, if I want to install SuperSU. I selected yes. And that's the moment when everything fcked up. After SuperSU installation, my tablet went into bootloop, and I wasnt't even able to enter recovery via button combination. I tried to flash the stock rom via LG Flash Tool, but failed miserably. I tried multiple stock roms, but the result is till the same: I can't access the Factory Reset via buttons, the system keeps rebooting, and even if it boots for few seconds, the touchscreen isn't responding. I even tried connecting mouse via USB otg, but no success. Is my tablet dead? Is there any chance of repairing it?
Thank you for your help.
EDIT: It's v500 European version.
Click to expand...
Click to collapse
nope, it's not death (yet)... The buttoncombo to enter might be a problem, but keep trying. If really nothing goes, try connecting to your PC and open a commandline. Type : adb reboot recovery (preferably from a linuxbox). However, make sure you got a ROM, GApps and SU system 2.78 or 2.79 ready on the SD. Personally I recommend @adrianom AOSP 7.1.1, OpenGApps micro and SU 2.79 SR2'systemmode.
Cheers

dirlan2001 said:
nope, it's not death (yet)... The buttoncombo to enter might be a problem, but keep trying. If really nothing goes, try connecting to your PC and open a commandline. Type : adb reboot recovery (preferably from a linuxbox). However, make sure you got a ROM, GApps and SU system 2.78 or 2.79 ready on the SD. Personally I recommend @adrianom AOSP 7.1.1, OpenGApps micro and SU 2.79 SR2'systemmode.
Cheers
Click to expand...
Click to collapse
Thank you for your reply.
However:
I am not able to stay in the system.
I am not able to enter the recovery. (because of the brick)
I am not able to enter ADB, because there's just no way how. I have USB debugging disabled by default (because I tried to reset the system using LG Flash Tool) and I can't use ADB in the download mode.
Actually, download mode is the only thing that hasn't broke yet. I still hope that someone that has experienced similar problems help me.
But again, thanks for your (and the only) reply.

Czechball said:
Thank you for your reply.
However:
I am not able to stay in the system.
I am not able to enter the recovery. (because of the brick)
I am not able to enter ADB, because there's just no way how. I have USB debugging disabled by default (because I tried to reset the system using LG Flash Tool) and I can't use ADB in the download mode.
Actually, download mode is the only thing that hasn't broke yet. I still hope that someone that has experienced similar problems help me.
But again, thanks for your (and the only) reply.
Click to expand...
Click to collapse
If you can get into download, you could connect to a PC and start the LG-tools.Use that to restore to the original ROM and start allover again with latedt software (TWRP, ROM, SU)
Cheers