yashsingh1/xdaforums huggingface dataset:
[One (M7) Q&A, Help & Troubleshooting] nkk71:
First, keep S-Off :), dont go s-on!!!

Second, the choice is really up to you, you have PN0712000, so you can easily convert to GPE or go with Sense.

1- if you want full GPE, you'll need to change CID to "GOOGL001", then use a GPE ruu.exe or ruu.zip; dont have any links handy so you'll need to google it

2- if you want Sense but not Bell, you can use an ATT ruu, such as: http://www.htc1guru.com/dld/ruu_m7_...20_10-40-1150-04_release_326691_signed_2-exe/

(you'll need to set CID to "CWS__001") i don't know if the ATT version has bloatware.

3- if you want to go back to Bell, you'll have to use the CWM restore method (but I guess that will come with the bloatware)
[One (M7) Q&A, Help & Troubleshooting] Nic2112:
Thank you for your help, I didn't know an AT&T RUU would work.

Do you thing this GPE RUU would work and allow the phone to get OTAs? http://xdaforums.com/show....php?t=2358781
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Yes you can use that. Don't know how much "stock" it is to receive OTAs, there are many guides around, a quick search also found me this: http://htc-one.wonderhowto.com/how-...with-bootloader-recovery-ota-updates-0148068/

your MID is good, just need to change CID.

the RUU will not relock your phone, but you don't need to do it since you are s-off.

keep s-off and all is good.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
looks like it:

i guess it should work, better read through the thread if you want to be sure.

just remember to set CID to GOOGL001.

PS: you can even change your phone into a European unbranded if you want, just takes a few more steps.
[One (M7) Q&A, Help & Troubleshooting] Nic2112:
Thank you very much, I really like that link that you found and I think I'll go with that. If I miss sense too much I will RUU the AT&T version.

GPE should keep me close enough to the latest google goodies without the constant need to flash.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
No problem :)

Enjoy
[One (M7) Q&A, Help & Troubleshooting] Nic2112:
I think I'm in trouble now. I got an "FAILED (command write failed (unknown error)) and the phone went into a weird bootloader menu where the only option was RUU

Well the phone rebooted and it's still sense... PHEW!
[One (M7) Q&A, Help & Troubleshooting] nkk71:
were you flashing a ruu.zip? you need to do it twice in a row. link of what you were flashing please, and stay in bootloader for now
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Good, now take it easy no rushing things :)

what were you trying to flash (link please) and how? also have you downgraded hboot to 1.44 first. trying RUU on 1.55+ usually doesnt work.
[One (M7) Q&A, Help & Troubleshooting] Nic2112:
In the link you sent me, there is a download link for an RUU. It's hard for me to link it because that URL is blocked here at work.

It's basically RUU-HTC_One_GE_2.14.1700.15

I have HBOOT 1.55 though so that is probably the problem. I'll downgrade and try again.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
it's probably because of hboot 1.55, remember that once in RUU mode, you need to issue the "fastboot flash zip filename" TWICE !!! (first one will come back with "failed flush again", the second one should report "success")

NB: this will wipe your entire phone!!!
[One (M7) Q&A, Help & Troubleshooting] Nic2112:
HBOOT Downgraded, now I'm flashing the RUU, the first time it stopped and said flash again so I'm flashing for the second time now.

It failed with the same error so maybe my RUU file is bad.

---------- Post added at 08:31 AM ---------- Previous post was at 08:31 AM ----------

C:\Android>fastboot flash zip RUU-HTC_One_GE-2.14.1700.15.zip

sending 'zip' (467625 KB)...

(bootloader) start check_usb: usb_ep0: type=128, request=6

OKAY [ 34.739s]

writing 'zip'...

(bootloader) zip header checking...

(bootloader) zip info parsing...

(bootloader) checking model ID...

(bootloader) checking custom ID...

(bootloader) start image[hboot] unzipping for pre-update check...

(bootloader) start image[hboot] flushing...

(bootloader) [RUU]WP,hboot,0

(bootloader) [RUU]WP,hboot,100

(bootloader) ...... Successful

FAILED (remote: 90 hboot pre-update! please flush image again immediately)

finished. total time: 36.291s

C:\Android>fastboot flash zip RUU-HTC_One_GE-2.14.1700.15.zip

< waiting for device >

sending 'zip' (467625 KB)...

OKAY [ 35.828s]

writing 'zip'...

FAILED (command write failed (Unknown error))

finished. total time: 35.836s

---------- Post added at 08:34 AM ---------- Previous post was at 08:31 AM ----------

This is the link to the RUU

https://mega.co.nz/#!3cwxzAoR!cNNlvVTqzO1wTnmZLytV2mIHtrtOOFXGMyMQjH-KsIo
[One (M7) Q&A, Help & Troubleshooting] nkk71:
I'm downloading it to check it, gonna take about 30mins on my connection...

did you change CID already? to GOOGL001?
[One (M7) Q&A, Help & Troubleshooting] Nic2112:
C:\Android>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.54.0000

(bootloader) version-baseband: 4A.22.3263.14

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 1.29.401.12

(bootloader) version-misc: PVT SHIP S-OFF

(bootloader) serialno:

(bootloader) imei:

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0712000

(bootloader) cidnum: GOOGL001

(bootloader) battery-status: good

(bootloader) battery-voltage: 4306mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-21fde4b846

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.067s

---------- Post added at 08:46 AM ---------- Previous post was at 08:43 AM ----------

Wait, my HBOOT is back to 1.55... I downgraded it and it was showing 1.44.

---------- Post added at 08:49 AM ---------- Previous post was at 08:46 AM ----------

I kid you not, it was 1.44 because I was the red text saying it's for dev only. I had never seen that before.

---------- Post added at 08:53 AM ---------- Previous post was at 08:49 AM ----------

I'm starting to wonder if it's that RUU that sets the HBOOT to 1.54. It was at 1.44, I flashed the RUU twice, I got the same error, and now my HBOOT is back to 1.55
[One (M7) Q&A, Help & Troubleshooting] nkk71:
yes i know, it's because the first part of the flash zip went through just fine (the hboot), then it comes back with "flush again" (ie after updating hboot), then to flash the rest of the zip.

anyway, hboot 1.54 should still be OK as well. as far as i know "downgrade" was only patched in hboot 1.55.

I'm still downloading, but that error you got doesnt make much sense.
[One (M7) Q&A, Help & Troubleshooting] Nic2112:
I'm going to try this: http://www.htc1guru.com/2013/11/android-4-4-kit-kat-google-edition-3-58-1700-5-ruu-ota-files/

It's a much faster download and it looks more recent
[One (M7) Q&A, Help & Troubleshooting] nkk71:
and my net connection crapped out again.

okay go for it, make sure MD5 is OK
[One (M7) Q&A, Help & Troubleshooting] Nic2112:
Trying the other RUU now and I was getting errors with HBOOT 1.54.

Downgraded to 1.44, flashed the RUU once, no problem. Flashed again and now it seems to be working, it's doing a lot more that it did.

It sounds like I also need to change the recovery in order for OTAs to work, correct? Well maybe not, I saw that the RUU flashed recovery stuff.

The second flash completed with ...successful! And i have 1.54 back.

I thanked all the posts that I could, and I'll say it, thank you for your help today. I think you saved my phone and probably my marriage too because my wife is past angry with all the time I had to spend fixing the phone lately. Now I have GPE with 4.4 and I'm guessing it will OTA to 4.2.2 when there is an HTC one version of it available via OTA
[One (M7) Q&A, Help & Troubleshooting] nkk71:
"Of course an RUU that works helps too!" LOL, indeed.

and the RUU.zip would have flashed everything to stock, including recovery and hboot. so you should be good now. :good:
[Streak 5 Q&A, Help & Troubleshooting] vaz_waseem:
Hello Guys,

I am using Traveller DSC ROM 2.3.10 on my Dell Streak 5 and it is working flawlessly without any issues. However, I have been trying to load a custom boot animation and have been unsuccessful. Here are the error messages I get using different ways to copy/move bootanimation.zip folder to /data/local/ or /system/media/

1. Tried using file manager, already provided in this awesome rom : ERROR: UNABLE TO MOVE/COPY THE FILE

2: Tried Creating a new folder in phone memory: Error: unable to create a folder

3: Tried to give a command to push using ADB: CANNOT COPY THE FILE IN READ ONLY.

Please help me what else can I do to add my custom bootanimation.zip to my mobile.
[Streak 5 Q&A, Help & Troubleshooting] Strephon Alkhalikoi:
The file manager included in the ROM came from CM7 and does not have root support. Use a root-capable file manager such as Astro or ES File Explorer to access /system/media and change the file.
[Streak 5 Q&A, Help & Troubleshooting] vaz_waseem:
Tried with no success

Thank you for your suggestion. However, I tried both Astro and ES File Explorer now and the issue still persists. If I try to copy and replace the existing bootanimation file it says that the file system is read only. Again, I tried creating a new folder, it says OPERATION FAILED.

Everything else works amazingly fast. Please help.

By the way, thank you so much for your ROM. You are awesome.
[Streak 5 Q&A, Help & Troubleshooting] Strephon Alkhalikoi:
Did you make sure to enable root for ES File Explorer or Astro in their respective settings when you ran them? If you did that and it still doesn't work, then you somehow lost root when SuperSU upgraded to 1.75 last week.
[Streak 5 Q&A, Help & Troubleshooting] vaz_waseem:
Thank you

Thank you. It was my bad, I was trying to copy the bootanimation.zip to /system/media/ where the file was a read only and it was not replacing to a different file. I just copied it to /data/local/ and it worked just fine :good::D
[Android Q&A, Help & Troubleshooting] nghiado70:
i need recovery motorola droid bionic (recovery.img) because my phone can't boot

thanks alot.
[Optimus L3, L5, L7 Q&A, Help & Troubleshooting] GustavoAngelo:
Hello,

Suddenly, my phone turned off and won't turn on back. I didn't tried anything, just happened. Few weeks ago, it was with a problem of don't charge correctly, i connected the cable, but instead increase the battery power, decreased. 2 hours charging, decreased 10 %. Then, i removed the battery and put back, until get back to normal.

I tried Vol Down + Button power, Vol Up + power button, Vol Up + Vol Down + Power Button. Don't respond.

What can be? I'm waiting the worse. haha.
[Optimus L3, L5, L7 Q&A, Help & Troubleshooting] Torres00:
is your phone rooted? any recoveries installed??? else try emergency mode!
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] Cundis:
Anyone heard of this, or even tried it? It seems to cover a lot of devices, our i9305 included. Pretty strange i've never heard of it before!

http://www.emccann.net/nuclearmistake/VanirAOSPRelease/
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] Raistlin1158:
See here:

http://youtu.be/Z4e0hL2y4eQ
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] Cundis:
Looks interesting! I tried to flash it but it was without gapps and it wouldn't boot. With some ROMs you don't have to flash gapps, but this one obviously requires it.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] Christian1981:
You could try to wipe cache partition and dalvik after install... In many 4.3 Roms i saw the info to wipe them after install too.... But looks interesting

Heavy Metal.. I guess i give it a try. Thanks for publishing!

Sorry bout my english! Greets from the snowy Austria :D
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] Cundis:
Hehe yeah this guys are Heavy Metal Vikings!

Didn't try to wipe dalvik and cache after the install, but thanx for the tip!
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] Cundis:
Maintaining

If someone with the skills and a i9305 are interested in creating and maintaining a thread here on XDA for this ROM i know they (Vanir) would be interested.

Here is a link to their community on Google+.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] Cundis:
I have been in contact with Dave Kessler from Team Vanir, and he says if anyone is interested they can contact him directly if interested in maintaing this ROM for i9305.

His requirements for the person who will eventually do this is:

1. They must have the device

2. Be able to compile to test and have the necessary skills to use at least github. We (Team Vanir) use gerrit but it's not far off﻿ and I can show them how if they meet the other requirements

(Dave Kessler qoute from Google+)
[G2 Q&A, Help & Troubleshooting] fegar:
Hi all,

As the title suggests, I have a bricked phone.

A little background, I rooted the phone then installed CWM. After that I installed CM10.2 but didn't care for it so decided to use Scotts stock rooted rom. To install that you have to have TWRP so installed that using Loki/adb. TWRP booted fine but when I went to do a wipe it hung at formatting cache. I rebooted and tried it again with the same results. I decided to try to install the rom anyway (dumb I know) and now all I have is a blank screen. No LG logo or anything. When I connect it to my pc windows recognizes like 10 different drives. I can't get it into download mode or recovery.

Am I screwed and need to see if ATT will replace it or is there a work around for this?

Thanks!
[G2 Q&A, Help & Troubleshooting] tdevaughn:
Wiping takes a long time. let it run and finish... could take 10 minutes or more.

how are you trying to get into recovery?
[G2 Q&A, Help & Troubleshooting] fegar:
Yeah I let it run for about 15 minutes which is considerably longer than it usually takes on any other phone I've done (many).

Tring to get to recovery using the power key method.

The thing is that it never gets to the LG logo. Nothing shows up on sceen at all but it is on.
[G2 Q&A, Help & Troubleshooting] mazer4455:
I'm in the same boat except I never installed a custom recovery or rom. Have you tried fastboot?

If it boots directly to a black screen (no lg splash), i'm sure ATT won't have any issues taking it back as they won't be able to see that it's rooted.
[G2 Q&A, Help & Troubleshooting] 4rsenal:
http://www.lg-phones.org/how-to-flash-unbrick-lg-g2-back-to-stock.html Here's a way to unbrick g2
[G2 Q&A, Help & Troubleshooting] fegar:
Yeah I tried the flash tool too. No luck as I couldn't get into download or recovery.

I wound up taking it back to ATT and they gave me a new one no questions asked.
[Asus Transformer TF701] Ikkerens:
Hi there,

I've been searching around to find a specific firmware zip for my new tablet, the SKU: WW, Version: 10.26.1.7.

It appears that asus has pulled this file and was wondering if anyone still has this file available somehow.

I soft-bricked my tablet and am not capable of flashing any other (earlier) firmware zip.

Any help would be greatly appreciated.

Yours sincerely,

Rens "Ikkerens" Rikkerink
[Asus Transformer TF701] schmeggy929:
Why can't you download an earlier firmware?
[Asus Transformer TF701] Ikkerens:
I can, but it always ends up with some kind of error.

I basically tried following the steps you did:

But on when trying to flash the ***-user.zip, I get this error message:

$ fastboot -i 0x0B05 flash system UL-K00C-WW-10.14.1.47-user.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi

Edit: My bootloader version shows: WW_epad-10.26.1.7-20131108
[Asus Transformer TF701] schmeggy929:
you are going to get that along with a few more errors. Wait until it is done. It will take like 10 mins and finish.

when it is done reboot in bootloader and you should see the version change.
[Asus Transformer TF701] Ikkerens:
You're getting this wrong, it does not do anything. The process immediately quits.
[Asus Transformer TF701] schmeggy929:
Ok when you get that message do you get a blinking curser?
[Asus Transformer TF701] lpdunwell:
did you make any backup with cwm recovery?

try this:

unpack blob from 47 update

fastboot flash staging blob
fastboot flash recovery recovery.img
fastboot reboot-bootloader

load recovery, restore your backup

if you have not made any backup with cwm recovery, tell me.

btw fastboot flash system... is not needed here
[Asus Transformer TF701] Ikkerens:
I have not made a backup using cwm because there was no CWM available for my version.

My tablet was already updated to 4.3 and I (apparently) could not boot the cwm in the development section.

If I would be able to flash a usable recovery, I wouldn't be in this situation anyway as the asus update (.47) is flashable (found an updater-script in the zip).
[Asus Transformer TF701] lpdunwell:
forget what I wrote here. I opened a thread with unbricking instructions. Good luck
[Asus Transformer TF701] Ikkerens:
Won't do me any good at the moment, I already managed to brick it even further (couldn't even get into fastboot mode anymore), so I RMA'd it.
[Asus Transformer TF701] lpdunwell:
oh crap. sorry about that. I know there's the nvflash, too, but I have no idea how to use that so far...:rolleyes:

would you mind telling what exactly happened?
[Asus Transformer TF701] Ikkerens:
Nvflash is inaccessible at the moment, it requires some preparation (you have to prepare it BEFORE you brick it)

Anyway, basically, I bought the tablet a few hours earlier.

Wanted to root it to remove some bloatware and restore some titanium backup thingies.

So I unlocked, rooted, basic stuff.

Went into TB, removed bloatware such as Amazon Kindle and some other irrelevant titles.

That action however, somehow caused it to be unbootable.

So I went into some basic repair stuff, as usual.

Tried to flash a recovery, only to find out, there is no working recovery. Only CWM, which required an earlier version of my bootloader.

So, what next. Restore stock? Downloaded the firmware, found out it was the earlier version of my device, because Asus removed the 4.3-EU version from their website.

So, I downloaded the .47-EU version, opened it. Saw there were no images, merely plain files meant for /system and an updater-script.

I ended up attempting to package my own system.img after that. Created an ext4 image on my computer, moved the files there. Followed the instructions in updater-script, which were mostly symlinks and stuff.

In the end of the updater-script they flashed blob to /staging and boot.img to /boot.

So, I flashed my custom system.img to /system.

Flashed boot

Flashed the blob

And beyond that point, I ended up in a bootloop of my bootloader. I could not hold down volume to enter fastboot or anything. All I could do was watch the asus logo as it constantly rebooted. (And ofcourse, no way to turn it off other than waiting for the battery to die)
[Asus Transformer TF701] Snah001:
Since you are unlocked, you can try to flash the recovery (extract it first) of the US version 1.7, should be the same as wwe. Or just even try to flash the whole us update manually. And later change back to the wwe version when it comes available. The 47 update was only a minor ota for 4.2 so no image of recovery or bootloader there.
[Asus Transformer TF701] pelago:
Sad story. What would have been the safe thing to do, if others wish to root their devices?
[Asus Transformer TF701] Ikkerens:
I still had the original recovery flashed, I never overwrote it actually. I needed a custom recovery (such as CWM, TWRP).

Flashing an US update is not possible alltogether, there are some minor differences with hardware compitability and such.

Problem is, I could've downloaded the .47 update, but I had already updated to 4.3 (BL 10.26.1.7)
[Asus Transformer TF701] Snah001:
I don't know if it isn't possible. On the TF700 it was only a line in the build.prop file that made the difference.

I would try it because now you have nothing and when it works you have the us version yes, but at least it works.
[Asus Transformer TF701] Ikkerens:
This guide worked fine for me; http://xdaforums.com/showthread.php?t=2516215

It's only about what you do with the root ^^

Already too late, it has been RMA'd, and then, I had nothing to flash it with.
[Asus Transformer TF701] pelago:
Well I meant, what should a root user do to try and protect themselves against bricking their device like you did? Is it a matter of making sure that CWM or TWRP is on the device as a recovery partition? And are those available on TF701T yet?
[Asus Transformer TF701] lpdunwell:
Oh dear. That's a lot gone wrong.

Cwm is available and that works.

It's made by drgravy. I use it in my unbrick tut.

All i can say is, root --> cwm --> backup.
[Asus Transformer TF701] Ikkerens:
That CWM wouldn't boot for me :/
[Asus Transformer TF701] lpdunwell:
Yes. Because of the bootloader difference.

You'd need to flash the old bootloader and image first
[Asus Transformer TF701] Ikkerens:
An image I did not have.
[Asus Transformer TF701] lpdunwell:
Boot.img from the update zip provided by asus. I' gonna upload what i have as soon as i'm home anyway.

---------- Post added at 05:04 PM ---------- Previous post was at 05:03 PM ----------

Actually blob is all you need

---------- Post added at 05:09 PM ---------- Previous post was at 05:04 PM ----------

I should stop posting while eating.

To get the current drgravy recovery working, even with the 7 update installed, you need to fastboot flash staging blob (of update 47) and fastboot flash recovery recovery.img

To then get back to a booting update 7 android, you need to fastboot flash staging blob (of update 7)

Update 7 is the new one
[Asus Transformer TF701] Snah001:
Sorry to hear that.

Us firmware is still offered as download on Asus website but it is too late i guess.

Will it be covered by warranty by the way?

Sent from my superfast Asus Infinity TF701with Dock
[Asus Transformer TF701] Ikkerens:
I doubt it'll be covered. It's an unlocked device and its bricked as a result of that.

I have hope, but I very much doubt it
[Asus Transformer TF701] Snah001:
When they not grant warranty take it back as it is and use the helpfrom here to get it up and running again i would say.
[Asus Transformer TF701] Ikkerens:
Then I'd still have to pay their processing and transportation fees.

And considering I cannot even get to fastboot anymore, I doubt remote help from XDA would do. I spent an entire day on TWRP IRC to get people to help me, they all helped really well but none really succeeded on it.

I'd personally do not want to take the risk, and let Asus do it. I'l re-consider rooting and perhaps installing a ROM later, when I have played enough with my tablet. (I bricked it after a mere 3 hours)
[Asus Transformer TF701] lpdunwell:
Let's hope for the best, until then: any news about nvflash? I haven't tried yet because I'm a bit behind schedule, as I ran into some trouble installing my build platform as real system (virtual was too slow) on my main machine.
[Asus Transformer TF701] Snah001:
Maybe you are lucky and they just repair it without comments, I hope that for you!
[Asus Transformer TF701] Ikkerens:
I'm hoping the same.

Anyway, for the sake of being ontopic, I have already received this image from someone through PM. Albeit a little late for me to use.
[Asus Transformer TF701] Ikkerens:
Okay, I just received an invoice from Asus.

After a long time of not hearing anything from them, I decided to give 'm a call. I received the email directly after that.

Apparently they're replacing the whole mainboard and facturating me €250,-

I am confident in the fact that this is merely a software issue, yet they decide to take such drastic action.

Replied with a complaint hoping that they can actually repair it instead of simply replacing it.
[Samsung Galaxy Gio GT-S5660] badagila:
hi! can some make a guide how to make our gio stock rom transparent? thanks a lot
[JAM, MDA Compact, S100 Software Upgrading] alexweb:
There is someone that can and want help me?

My MDA is Sim-unlocked.

Thanks before.

Alex