yashsingh1/xdaforums huggingface dataset:
[G2 Q&A, Help & Troubleshooting] lokeycmos:
so I got lg support tool to install, but now it doesn't recognize my phone as being plugged in. in the directions it appears that you have to enable usb debugging, but I cant do that cause my phone wont boot past TWRP recovery.i already wiped everything on the phone. is there a way to flash to stock from twrp?

here is a screen shot. my model isn't listed in the available options for a driver.
[G2 Q&A, Help & Troubleshooting] Swakiny:
Put your phone in download mode
[G2 Q&A, Help & Troubleshooting] bender_007:
Navigate to c:\windows\system32\drivers\etc

open hosts in notepad++ or whatever..

maybe you'll notice the lines 127.0.0.1 lg..blabla.., just delete them or put # in front of them (#127.0.0.1 lg.blablabla..)

This is in case you tried the automatic offline kdz installer and the vbs couldn't remove the lines itself.
[Nexus 7 Q&A, Help & Troubleshooting] filking:
Can anyone help me out.

Tablet rebooted for no reason, now stuck at the google boot screen.

Can get into bootloader, and when I try recovery mode I get all the

E:failed to mount /cache (Invalid argument)

E:Can't mount /cache/recovery/log

E:Can't open /cache/recovery/log

E:failed to mount /cache (Invalid argument)

E:Can't mount /cache/recovery/last_log

E:Can't open /cache/recovery/last_log

E:failed to mount /cache (Invalid argument)

E:Can't mount /cache/recovery/last_install

E:Failed closing /dev/block/platform/msm_sdcc.1/by-name/misc (I/O error)

The pc recognises the device and I have the nexus root toolkit.

Any help would be appreciated.
[Nexus 7 Q&A, Help & Troubleshooting] Captain Sweatpants:
It sounds like a corrupted nand partition which would mean a new motherboard have you tried the unroot and back to stock option in NRT?
[Nexus 7 Q&A, Help & Troubleshooting] filking:
Not tried any option on NRT yet, incase i made it worse. Was waiting for advice on correct path.

Should I try that 1st then?
[Nexus 7 Q&A, Help & Troubleshooting] Captain Sweatpants:
[MENTION=4618766]filking[/MENTION] I would try the unroot and back to stock option tick the box for soft bricked and that will flash a new factory image if that fails the you can try manually flashing the tablet
[Nexus 7 Q&A, Help & Troubleshooting] filking:
Ok, tried unroot/back to stock

Result:

sending 'bootloader' (3911 KB)...

OKAY [ 0.133s]

writing 'bootloader'...

FAILED (remote: flash write failure)

finished. total time: 90.702s

rebooting into bootloader...

OKAY [ 0.006s]

finished. total time: 0.006s

archive does not contain 'boot.sig'

archive does not contain 'recovery.sig'

archive does not contain 'system.sig'

--------------------------------------------

Bootloader Version...: FLO-04.02

Baseband Version.....: none

Serial Number........: 0586533c

--------------------------------------------

checking product...

OKAY [ 0.003s]

checking version-bootloader...

OKAY [ 0.004s]

sending 'boot' (7018 KB)...

OKAY [ 0.235s]

writing 'boot'...

FAILED (remote: flash write failure)

finished. total time: 90.136s

Tablet still in bootloader.
[Nexus 7 Q&A, Help & Troubleshooting] filking:
Well,

I followed instructions and set NRT to force write, and repeated the process.

sending 'bootloader' (3911 KB)...

OKAY [ 0.132s]

writing 'bootloader'...

FAILED (remote: flash write failure)

finished. total time: 90.701s

rebooting into bootloader...

OKAY [ 0.008s]

finished. total time: 0.008s

sending 'boot' (7018 KB)...

OKAY [ 0.235s]

writing 'boot'...

FAILED (remote: flash write failure)

finished. total time: 90.136s

rebooting into bootloader...

OKAY [ 0.005s]

finished. total time: 0.006s

erasing 'cache'...

And it's been like this for about 45 minutes..... ermmmm

Any ideas?
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
Hi, filking...

As Captain Sweatpants suggests, this has some of the hallmarks of bad or corrupt NAND/eMMC... but a couple of points...

First...

Are you sure the bootloader is unlocked with fastboot oem unlock?

And second...

This indicates your Nexus 7 is actually the second generation Nexus 7 (2013) ... so are you sure you're trying to flash the correct factory image for your device... ie.,

NOT

a 'nakasi' or 'nakasig' factory image.. (also known as 'grouper' or 'tilapia' factory images).

------------------------------------

For your Nexus 7(2013) you need either a 'razor'(WiFi) or 'razorg'(mobile) factory image.

Ensure you have the correct factory image for your device from here...

https://developers.google.com/android/nexus/images

Good luck.

Rgrds,

Ged.
[Nexus 7 Q&A, Help & Troubleshooting] filking:
Thanks for reply.

The device was unlocked and rooted before it crashed. So assume the bootloader was unlocked.

And I'm sure i'm on the right image. I'm using razor KOT49H for the wi-fi one.

Anything else I could try?
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
You'll know if the bootloader is unlocked by the presence of an unlocked padlock symbol upon boot.

The factory image you're using sounds about right...

I know this is 'grasping at straws' a little bit... but you could try changing your USB port connection to your PC or your USB cable. I've had some weird situations myself in the past, with my own Nexus 7 when flashing back to factory stock, and this has resolved some problems for me.

Failing that, you should try asking over on the Nexus 7(2013) forum itself...

http://xdaforums.com/nexus-7-2013

The guys over there are probably better qualified to help you, as I have no direct experience of the second gen. Nexus 7.

Rgrds,

Ged.
[Nexus 7 Q&A, Help & Troubleshooting] filking:
That shows my age that my eye sight is going. I could've sworn I was in the N7 (2013) section... Sorry..

And yes it does have the unlock symbol and i'll try a diff usb..

But I'll cut and paste the best bits of this over in the right forum.

Cheers again.
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
You're welcome... and again, good luck.

Rgrds,

Ged.
[Nexus 7 Q&A, Help & Troubleshooting] Captain Sweatpants:
Hope you find a solution I really think we need to rename this forum

Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
[HTC Flyer, EVO View 4G] richych:
Hi,

I'm trying to S-OFF my sister-in-law's HTC Flyer and then put a more recent Android OS on it.

The Flyer is currently running OS 3.2.1, software 3.55.405.1 with the 1.11.0011 HBOOT.

I've been trying to research this for the last few weeks and so far I've:

1. Unlocked the bootloader via HTC Dev

2. Installed Revolutionary CWM v4.0.1.4 recovery

3. Rooted

However, I understand that to upgrade to a more recent OS (e.g. 4.x) I need S-OFF. The device is currently S-ON.

I also understand I need to downgrade to an earlier HBOOT and OS which will allow me to use tools to S-OFF. Once I've done that, then I can put a much more recent CFW on it and thus a newer OS.

However, here's the problem. Running an appropriate RUU doesn't work. It does nothing at all. I've donwloaded one from two different sources and neither do anything. They just say 'sending....' for hours on end, and when I give up a reboot I see RUU failed and then reboot again and device is back to where it was before. Nothing's changed.

If what I understand above is correct, what's my next course of action?

It's a P510e HTC Sense 1.1 (Fastboot getvar cid says HTC_16 so it's a PG4110000) with 3G and Wi-Fi.

Thanks in advance!
[HTC Flyer, EVO View 4G] hantreser:
First try this http://revolutionary.io/

Basicly follow instructions on site.

If it doesnt help, xda forums are full of threads which will help you.
[HTC Flyer, EVO View 4G] richych:
Hi,

Thanks for the reply, but I've already visited that site. Unfortunately, it isn't of any help to me as I'm not running the required HBOOT version. Mine is later (v1.11.0011) and it needs to be downgraded to an earlier version before S-OFF can be achieved via revolutionary.io.

So, I guess I firstly need to find a way to downgrade from 1.11.0011 to an earlier HBOOT before I can then S-OFF and add a custom ROM running a later Android OS.
[HTC Flyer, EVO View 4G] htcflyerhc:
downgrade from here http://xdaforums.com/showthread.php?t=1307759

Sent from my HTC Flyer P510e
[HTC Flyer, EVO View 4G] richych:
Hi,

For some reason, the RUU approach isn't working for me.

If I try using the util itself, it never sends the file to the Flyer. I've sourced the RUU from two different locations on the 'net, with the same result. I discovered that the ROM.ZIP in both wasn't a valid ZIP file so I couldn't try the misc_version method (*and* worryingly Kaspersky 2014 detects the misc_version file as Malware and deletes it so I'm concerned about that method anyway).

I've rooted and CFW'd three devices in the past (a G2 Touch, an SII and a TF301T) but this HTC Flyer is a pain in comparison (and I have a Desire HD to do next!).
[HTC Flyer, EVO View 4G] htcflyerhc:
did you unlocked the flyer via htc dev?

Sent from my HTC Flyer P510e

---------- Post added at 07:10 PM ---------- Previous post was at 07:04 PM ----------

or try this http://xdaforums.com/showthread.php?t=1428104

Sent from my HTC Flyer P510e
[HTC Flyer, EVO View 4G] richych:
Yes, unlocked via HTC Dev then rooted by adding the Revolutionary CWM v4.0.1.4 recovery image.
[HTC Flyer, EVO View 4G] htcflyerhc:
there is no malware on misc file you can use it and open the ruu wizard wait for couple seconds the take the rom.zip, be sure that you have at least 700 mb free memory on your pc before starting the ruu wizard.

Sent from my HTC Flyer P510e
[HTC Flyer, EVO View 4G] richych:
Okay, I've followed the misc_version instructions (temporarily turned off Kaspersky so it wouldn't complain) and even though I have now relocked the bootloader etc. the RUU *still* doesn't do anything. It reboots the Flyer, but afterwards it just sits there and says it's sending but never does! There was an error that flashed up sometime during the 'adb' or 'adb shell' stuff - mentioning too many links - so maybe there's another issue somewhere? :(
[HTC Flyer, EVO View 4G] htcflyerhc:
if you do all the steps from the links above it must work i dont know why you cant downgrade try puting the rom.zip on your sdcard and reboot to bootloader be sure that rom.zip is not corrupted and rename the rom.zip to PG41IMG.zip.

Sent from my HTC Flyer P510e
[HTC Flyer, EVO View 4G] richych:
I'd downloaded RUUs from different sites on the 'net and Windows reported the rom.zip they contained was duff. However, just tried testing one with 7zip and that reported the zip was fine (and I extracted it as a test), so for some reason my Windows 7 is unable to read the zip file correctly, which might explain why RUU was failing to work?

Anyway, I copied the RUUs resulting rom.zip file to the SD card and renamed it as suggested.

I ran misc_version via adb and set it with the correct RUU version (2.00.405.3) and then exited back to the command line, and told adb to reboot to bootloader. Bootloader loaded and checked the PG41IMG.zip file, and it then reports "Main Version is older! Update Fail!", which I expected misc_version to avoid?

(If I try 'adb reboot bootloader' from the # su prompt rather than exiting first, adb shell reports that it can't find the device. Is that relevant at all? I assumed you had to exit back to the Windows cmd prompt before doing 'adb reboot bootloader' (which works) but could that be where I'm going wrong?)

Just in case it's at all relevant, 'fastboot getvar all' tells me:

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.11.0011

(bootloader) version-baseband: 3822.10.08.07_M

(bootloader) version-cpld: None

(bootloader) version-microp: 0950

(bootloader) version-main: 3.55.405.1

...

(bootloader) product: flyer

(bootloader) platform: HBOOT-7230

(bootloader) modelid: PG4110000

(bootloader) cidnum: HTC__016

(bootloader) battery-status: good

(bootloader) battery-voltage: 4191mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: f0e1145e

(bootloader) hbootpreupdate: 12

(bootloader) gencheckpt: 0

I'm using RUU_Flyer_HTC_WWE_2.00.405.3_R_Radio_20.3501.30.089BU_3809.05.04.10_M_release_194964_signed, which I am guessing would be the correct version as I think I need 405.3 to be able to then get S-OFF and upgrade to a newer OS.

The flyer is 3G and Wi-Fi, HBOOT 1.11.0011, running 3.55.405.1. It's on Talk Mobile (via Vodafone) for 3G data and the device seems to originate from South Africa rather than the UK, but I'm assuming WWE is going to be okay?
[HTC Flyer, EVO View 4G] htcflyerhc:
did you installed recovery and su before trying to use the misc file?

Sent from my HTC Flyer P510e
[HTC Flyer, EVO View 4G] richych:
Yes. The phone was unlocked, new recovery and rooted before I tried misc_version.
[HTC Flyer, EVO View 4G] htcflyerhc:
i really dont know whats the problem

Sent from my HTC Flyer P510e
[HTC Flyer, EVO View 4G] richych:
It's okay, you've been really helpful - and patient - so I'm really grateful for your suggestions. I thought I was getting close up until I got the old version problem!

I'll try again (and again) and see what happens.

Thanks anyway!
[HTC Flyer, EVO View 4G] htcflyerhc:
Your welcome, i really want to help you but i cant figure out what is causing the problem.

Sent from my HTC Flyer P510e
[HTC Flyer, EVO View 4G] richych:
Bricked?

Unfortunately, something very odd has now happened to the HTC Flyer. It was left plugged in to my PC, slowly charging via USB.

We went out for part of the day, came back and the device is now caught in a perpetual loop. Screen goes off for about 7 seconds, then comes back on, stuck in FASTBOOT USB (if I'm connected via USB) or FASTBOOT AC (if I'm using a plug) for about 3 seconds before going off and then repeating the cycle. The power button flashes orange on/off throughout this loop.

I have noticed that apart from the usual info (e.g. S-ON, etc.), it also has one important addition underneath *** RELOCKED ***, which is:

*** Security Warning ***

The options I have are:

BOOTLOADER

REBOOT

REBOOT BOOTLOADER

POWER DOWN

As I only have 3 seconds, I don't have the time to select anything other than BOOTLOADER and the instant the HBOOT screen appears, the device starts the cycle again and I'm back to the beginning.

Any suggestions before I have to inform my sister-in-law that her flyer is now a brick? :(
[HTC Flyer, EVO View 4G] htcflyerhc:
put the honeycomb rom on your sdcard and reinstall it.

Sent from my HTC Flyer P510e
[HTC Flyer, EVO View 4G] richych:
Hi,

Sorry to be a bit slow, but I need a few more details?

I've got a backup of my system (via Revolutionary recovery mode) from a few weeks ago. That presumably includes the Honeycomb ROM (the flyer was running 3.2.1), but how do I reinstall it when the Flyer is stuck in this loop?

The backup contains: boot.img, cache.img, data.img, nandroid.md5, recovery.img, system.img

The system.img file will be the ROM as it's 768MB.

I don't see how to get the Flyer to do anything whilst it's stuck like this. It doesn't switch on at all if it isn't plugged in (USB or AC) and it's in this loop if it is plugged in. I don't think it's charging the battery at all whilst it's in this loop, and the battery doesn't seem to have any charge if it's not plugged in!
[HTC Flyer, EVO View 4G] htcflyerhc:
download the hc rom take the rom.zip and put in on the sdcard

Sent from my HTC Flyer P510e
[HTC Flyer, EVO View 4G] richych:
Sadly, nothing is making any difference. It's in a perpetual 7 second loop. However, I looked over a few things and noticed something that might be relevant:

Here's what fastboot getvar all told me a week ago:

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.11.0011

(bootloader) version-baseband: 3822.10.08.07_M

(bootloader) version-cpld: None

(bootloader) version-microp: 0950

(bootloader) version-main: 3.55.405.1

...

(bootloader) product: flyer

(bootloader) platform: HBOOT-7230

(bootloader) modelid: PG4110000

(bootloader) cidnum: HTC__016

(bootloader) battery-status: good

(bootloader) battery-voltage: 4191mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: f0e1145e

(bootloader) hbootpreupdate: 12

(bootloader) gencheckpt: 0

Here's what the same command told me just a short while before the device went wrong:

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.11.0011

(bootloader) version-baseband: 3822.10.08.07_M

(bootloader) version-cpld: None

(bootloader) version-microp: 0950

(bootloader) version-main: 2.00.405.3

...

(bootloader) product: flyer

(bootloader) platform: HBOOT-7230

(bootloader) modelid: PG4110000

(bootloader) cidnum: HTC__016

(bootloader) battery-status: good

(bootloader) battery-voltage: 4082mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: f0e1145e

(bootloader) hbootpreupdate: 12

(bootloader) gencheckpt: 0

(bootloader) hbootpreupdate: 12

(bootloader) gencheckpt: 0

The difference is that version-main is now the older 2.00.405.3 which is what I was trying to get misc_version to do, but it never seemed to work!

I really don't know what to do. It won't boot up without power, and when you do it's stuck in a quick reboot cycle I don't seem to be able to interrupt no matter what I try!
[HTC Flyer, EVO View 4G] htcflyerhc:
you are on gb now thats why your version is changed so try instaling gb rom again maybe your rom is not instaled propertly and if your flyer cant power on with presing the on tab key it looks like your battery is empty try charging the battery without turning on the flyer.

Sent from my HTC Flyer P510e
[HTC Flyer, EVO View 4G] richych:
Hi,

I think I know what's happened. The Flyer was left in a mode where the battery doesn't charge (probably in Fastboot?), then the battery drained completely. Unfortunately, the moment you plug the device into USB or AC, it turns on in FASTBOOT mode then realises it has no battery power, switches off, detects USB or AC power then boots up again and the cycle repeats.

The device isn't on GB yet, I've never been able to downgrade the ROM. I think it's just thst setting misc_version finally worked. Running an RUU or doing it manually would have been my next step, if this hadn't happened.

So, I think I need to get the battery out and find a way to charge externally?
[HTC Flyer, EVO View 4G] htcflyerhc:
http://xdaforums.com/showthread.php?t=2490641

Sent from my HTC Flyer P510e
[HTC Flyer, EVO View 4G] richych:
Okay. I took out the battery but found trying to do a DIY job on charging it outside of the Flyer beyond my clumsy capabilities. Instead I took the plunge and ordered a replacement battery. It turned up, and after thinking I'd completely broken the Flyer I got all the fiddly cables and screws back into the device and it booted back into the Android OS. Phew!

The only negative is that the pen icon in the bottom-right corner of the device is red all the time. In fact, I hadn't noticed it before (it wasn't on at all before things went awry two weeks ago).

Anyway, lesson learned. Never leave a device on in FASTBOOT and then let the battery drain!

So, back to the task in hand ...
[HTC Flyer, EVO View 4G] htcflyerhc:
nice your flyer is working now:p
[HTC Flyer, EVO View 4G] beboptheory:
Hello,

I'm by no means an expert.. but I spent the last 3 days troubleshooting, trying to get my

View

rooted and finally finished successfully today!

Regarding your problems running the RUU, make sure your bootloader is relocked when you run it (command: fastboot oem lock).

Also, make sure you're in fastboot when you run the RUU (I didn't see this written anywhere, but saw it in a youtube video).

One more thing: I had the same problem as you, where it says it's sending but never does.. For me it was a Windows driver issue. What fixed it for me was a mixture of unplugging/replugging the USB and restarting the tablet and the PC. Sorry, it was all so frustrating I don't remember exactly what worked. But keeping your Device Manager open in Windows and watching for the tablet to pop in and out of that window as it reboots may give you some awareness on whether the drivers are the problem. I know for sure when running Revolutionary, simply unplugging the USB and plugging it back in fixed it.

I hope this is helpful and isn't out of line, as I'm not as knowledgeable as most on these forums!
[HTC Flyer, EVO View 4G] richych:
Hi,

Thanks for taking time to post. The tablet was successfully rooted (in OS 3.x) before everything went horribly wrong, but my problem remains getting the device downgraded to an earlier OS version (2.x) so that I can change S-ON to S-OFF before upgrading to a later OS (4.x).

So, I'm currently rooted but have come to a haltl getting the OS upgraded (or downgraded!). The file misc_version seems to have worked its magic according to 'fastboot getvar al'l, but just updating via a zipped ROM on the SD card still reports it's an older version (whilst going through the checks in FASTBOOT mode) and aborts the process.

The flyer is indeed relocked (as per the command you mentioned) but I might just try the RUU again and see what happens, trying your suggestion re. USB and the drivers, etc.

Thanks,
[Xperia Arc Android Development] afi1982:
not working:

Bluetooth

stock browser not 100% working

credit :

LexacyXperia for cm11 base
[Xperia Arc Android Development] giannhs_n:
seems nice,but you say no buggs on top page ,camera works? ion/poem based release?
[Xperia Arc Android Development] afi1982:
Bluetooth fixed.
[Xperia Arc Android Development] afi1982:
for now it's pmem based , camera works fine .
[Xperia Arc Android Development] sympi:
Wow, new ROM! I really appreciate you work. I would love to test this ROM.
[Xperia Arc Android Development] afi1982:
est it and tell me what you think ;)
[Xperia Arc Android Development] sympi:
Does it work with Dark Kernel (from Dark Raven)? Or you recommend to flash kernel provided in zip?
[Xperia Arc Android Development] afi1982:
yeah it is
[Xperia Arc Android Development] dejavu18:
its always good to see a new rom..
[Xperia Arc Android Development] :
is it for unlocked bootloaders only? im a noob :P
[Xperia Arc Android Development] afi1982:
Yes :-? ;)
[Xperia Arc Android Development] afi1982:
new build today.

BeanStalk-4.4.285-20140508
[Xperia Arc Android Development] afi1982:
new build

http://yairpatch.com/blog/2014/05/beanstalk-4-4-285-20140508-anzu/
[Xperia Arc Android Development] dejavu18:
your rom include any file manager?
[Xperia Arc Android Development] afi1982:
no but you can download and install it .
[Xperia Arc Android Development] ahmed1994:
where is download link its broken in first post

---------- Post added at 05:52 PM ---------- Previous post was at 05:52 PM ----------

add this to first post

thanks in advance
[Xperia Arc Android Development] afi1982:
new build

http://yairpatch.com/blog/2014/08/romkitkatbeanstalk-v4-4-4001oc-4-4-4110814/
[Xperia Arc Android Development] jeetlebuice:
is video recording working in the newest build
[Xperia Arc Android Development] jeetlebuice:
480 works great,720 doesnt work with default cam app but does with google camera
[Xperia Arc Android Development] dropsy1234:
is moving apps to sd working?
[Xperia Arc Android Development] jeetlebuice:
no,and using link2sd doesnt work either,Damn it!
[Xperia Arc Android Development] dropsy1234:
Hi yair [MENTION=1945569]afi1982[/MENTION]

first, thank you for bringing great ROMs for xperia arc :) :good:

I have a question about moving apps to SD, why is it disabled in some ROMs like beanstalk and slim ?

is it possible to fix this?

thank you!! :)
[Xperia Arc Android Development] osx_cm7:
Working with Mounts2SD.
[Xperia Arc Android Development] jeetlebuice:
Not for me
[Samsung Gear 2] chon12:
Can u root a galaxy gear 2
[Samsung Gear 2] Breach:
No. Once you can, it will be all over the internet. It's not an android device and there are less devs. Give it some time.