yashsingh1/xdaforums huggingface dataset:
[One (M7) Q&A, Help & Troubleshooting] therealdeadlycheese:
Hey, thanks for the tips.

I'm a linux user, so everything is command-line, fastboot or adb. No HTCSync or drivers other than what is in my kernel (3.14.22-100.fc19.x86_64).

I would have been happy to have used TWRP but I couldn't get it to boot all the way, just would hang at the TeamWin logo. Here are the ones I tried:

openrecovery-twrp-2.6.3.3-m7.img

openrecovery-twrp-2.6.3.4-m7ul.img

openrecovery-twrp-2.7.1.1-m7.img

openrecovery-twrp-2.8.0.2-m7.img

openrecovery-twrp-2.8.1.0-evitareul.img

I would be willing to try again, or another one, if you suggest it ... didn't realize that CWM would bork the Android Revolution ROM. I might try 2633 again to see if it works after flashing CWM, somehow.

Hey, thanks for the tips. I fear it is hardware, but I agree, the smart thing is to exhaust firmware flash attempts.
[One (M7) Q&A, Help & Troubleshooting] alray:
Just want to add that this version of ARHD require s-off (GE). use a Sense based rom like arhd 82.

Would also suggest to do a full "format data" (not only a wipe) before pushing and installing the rom, for me, the initial issue sounds like something got corrupted and a format data wouldn't hurt.
[One (M7) Q&A, Help & Troubleshooting] clsA:
lock the bootloader with fastboot

fastboot oem lock

then download and flash this RUU

http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe

For Linux the RUU zip is here

http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3-decrypted-zip/
[One (M7) Q&A, Help & Troubleshooting] therealdeadlycheese:
Sigh. Tried openrecovery-twrp-2.6.3.4-m7ul.img again ... boots to teamwin logo, screen blanks for 2 seconds ... and reboots, hanging at htc logo.
[One (M7) Q&A, Help & Troubleshooting] alray:
do what cisa told above, There a ruu that match your verison it should be the easiest way to restore you phone. relock and run the ruu
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
Good catch ;) :good:

Ahh a Linux user nice. Have you tried killall adb. To fix the protocol error

In your terminal type

killall adb

disconnect your phone for a few seconds then

sudo adb devices

Also worth checking your adb version with

adb version

If you found my posts helpful, Please click thanks :good:

---------- Post added at 02:19 AM ---------- Previous post was at 02:13 AM ----------

Just follow instructions from [MENTION=2895182]clsA[/MENTION] to restore your phone.

But for future reference are you using

fastboot erase cache

after flashing recovery?

If you found my posts helpful, Please click thanks :good:
[One (M7) Q&A, Help & Troubleshooting] majmoz:
Here is full wipe stock firmware 4.18.502.7. It will wipe your data so you will need to copy your files off your phone to your PC. Since you are S-ON, you will need to lock your bootloader prior to flashing this firmware. Download the file and place in your adb/fastboot folder and rename it firmware.zip for ease of typing. Here are the steps for flashing the firmware.

If this firmware didn't flash successfully, then you can execute RUU 3.17.502.3 or the next available RUU 4.18.502.7.

If the firmware flashes successfully, then the only RUU you can run is the 4.18.502.7 one.
[One (M7) Q&A, Help & Troubleshooting] therealdeadlycheese:
OK, I really appreciate all the help. Where I'm at:

- booted clean Windows7 VMware image

- installed adb/fastboot/drivers in Windows7

- verified windows VM access with "fastboot devices" (success)

- ran "fastboot oem lock" ; last line said "FAILED (status read failed (Too many links))", but the phone says "RELOCKED", so I'm guessing it worked

- ran RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2.exe

in windows VM

- phone now shows silver HTC logo, green bar at about 20%, RUU installer shows "Updating Boot...." with 20% in the progress bar .... but it has been that way for about 10 minutes ... and the phone shows a triangle with an exclamation point in it at the end of the progress bar.
[One (M7) Q&A, Help & Troubleshooting] clsA:
forget the VM ..just use the ruu.zip
[One (M7) Q&A, Help & Troubleshooting] therealdeadlycheese:
VM RUU is still stuck on 20% ... reboot and start over with the zip from linux, then?
[One (M7) Q&A, Help & Troubleshooting] clsA:
yes you'll have to force reboot the phone if it's stuck

hold the power and volume down under a bright light for about 15 seconds
[One (M7) Q&A, Help & Troubleshooting] therealdeadlycheese:
heh

rebooting now, will try flashing again from linux.
[One (M7) Q&A, Help & Troubleshooting] therealdeadlycheese:
Well, last night I let it sit at 20% for 45 minutes before giving up and disconnecting the phone. But, when I tried to reboot it, it wouldn't boot, no lights, no sounds, not anything. I let it sit for a bit, tried again, nothing ... hold power button, hold volume buttons, clickety-clickety power and volume buttons, recharging ... still nothing. Went through all the gyrations again this morning ... still dead.

I may get farther under warranty with it in this totally inert state than I would if it booted to a custom recovery image, so maybe I'm better off.

Thanks everyone for the help, though.

Has anyone had any experience with HTC Warranty repair? Any tips or gotchas to share?
[One (M7) Q&A, Help & Troubleshooting] Nikatichi:
I didn't want to start a new thread, since this is very similar to my situation.

I have a sprint htc one m7. I'm pretty sure the phone is hot since my girlfriend bought it for me from some guy she works with for $10. I soon found out that Sprint either hates their customers, or wants to try their hardest to protect their customers from street corner electronics hustlers (probably a bit of both). I want to unluck the sim, but it seems nearly impossible...

I immediately unlocked and rooted my new android phone. When I tried using firewater to unlock the sim, I was told that my kernel had anti-firwater. So I tried flashing a kernel from this site which was compatible to my device, but the device was stuck in boot loop. The arrogant noob that I am started screwing around with the device, and eventually bricked the phone.

Luckily, I was able to find an ruu from this site that didn't require s-off and successfully restored the device.

WHERE I STAND AT THE MOMENT:

before I go on, here are my specs;

Android version 4.4.2

sense 6.0

software 5.05.651.2

rooted with supersu and recovery is TWRP

I tried running firewater again...failed. protected. So, I tried flashing Android_Revolution_HD-One_6.1_GE. It installed perfectly, but when I rebooted, it hung at the htc splash screen. I tried again after doing another restore.

What I don't understand is this: when I reboot after installing this rom (and a viper rom), TWRP tells asks me to install SuperSU because my device "doesn't seem to be rooted". I found that odd since I had previously rooted the phone, so I downloaded a root checker just to make sure. The app congratulated me, ensuring that my device was rooted, but I'm still being asked to install supersu after flashing the rom. I did, of course, but the device just reboots when I "swipe to install"
[One (M7) Q&A, Help & Troubleshooting] alray:
Are you sure you have flashed a sprint compatible kernel? Sprint htc one is not the same as the Htc One, different hardware and different partition layout. Flashing a kernel, a rom or a recovery not explicitly made for sprint htc one will soft brick your phone and will probably corrupt your partitions.

Go back in ARHD 6.1 thread and read the OP:

you should see:

and

Your device is sprint and is not s-off....

I think you don't understand what "rooting" mean. You root the OS aka Android aka System, not the phone itself. If you flash another rom aka system, you have to root it again (except if the rom is pre-rooted).

+

You are probably not using a sprint recovery/sprint rom so the recovery is probably not looking for root files at the correct partition.

and you'll be happy to know that there is a dedicated thread in the sprint htc one "general" forum to help users achieving s-off and sim-unlock on 5.x.651.x version. You might want to try what said there.

http://xdaforums.com/sprint-htc-one/general/sprint-htc-one-s-off-sim-ulock-hboot-1-t2890412

So remember, do not use anything (ruu/rom/recovery/mods/guides) that are not explicitly made for the Sprint htc one variant, which mean basically everything posted in this forum section (Htc One)
[One (M7) Q&A, Help & Troubleshooting] Nikatichi:
ElementalX-m7-Sprint-13.1 is the name of the kernel, and thank you for responding so fast. I've jumped in head first and now have deep respect for developers; especially those that give their own time to help. Thank you. I'm diving into that link you gave me right now.
[Moto G Q&A, Help & Troubleshooting] black_skull:
Hello i have a problem with the wifi the problem is that no connect, I turn on wifi and in a 1 second turns off i search whats the problem and my two unique answers are: first: the modem is dead, second: a folder named PDS is damaged Anyone can help me with your pds folder you can access to that folder with root explorer... Cellphones specifics: Moto g xt1032 Android 4.3 jelly bean NOTE: I try to flash kitkat stock firmware but the sim card don't works

NOTE: SORRY FOR MY ENGLISH
[Moto G Q&A, Help & Troubleshooting] black_skull:
any can send me psd files please if the problem fixes i tell you
[Moto G Q&A, Help & Troubleshooting] black_skull:
any who have the same problem there is the solution http://xdaforums.com/moto-g/orig-development/fix-wifi-issues-t2929398
[Galaxy Note Pro 12.2 Android Development] bonuzzz:
OmniROM for P900 Only

installation:

install custom recovery TWRP: http://xdaforums.com/showthread.php?t=2706982

install omnirom with recovery

install gapps (optional): http://xdaforums.com/showthread.php?t=2397942

for root flash zip file with recovery: http://download.chainfire.eu/589/SuperSU/

Changelog:

R2:

-improve overal stability

-bug fixes

known issues:

camera is not working

buttons backlight is not working

download links:

R2:

P900 https://yadi.sk/d/SUn2aByFcaEAM

XDA:DevDB Information

OmniROM, ROM for the Samsung Galaxy Note Pro 12.2

Contributors

bonuzzz, Valera1978, arcadia2uk

ROM OS Version: 4.4.x KitKat

ROM Kernel: Linux 3.4.x

Based On: AOSP

Version Information

Status: Testing

Created 2014-11-04

Last Updated 2014-11-20
[Galaxy Note Pro 12.2 Android Development] bonuzzz:
Reserved
[Galaxy Note Pro 12.2 Android Development] Stevethegreat:
To anyone who flashed this, can you do the following immediately after installation?

1) Let the rom be installed and after setting up everything that it may be required from you (your google account?), wait for a while and then reboot the tablet.

2) Once the reboot is completed go to Settings-> Apps and from there navigate to the "Running" TAB. Once there please report the "USED" amount (it would be like "700MB used", or sth like this).

Thanks.
[Galaxy Note Pro 12.2 Android Development] arcadia2uk:
1.1Gb RAM used, but I'm running MultiROM, besides that I had only installed SuperSU and Pico gapps, I have exactly the same usage displayed with cm11.
[Galaxy Note Pro 12.2 Android Development] bonuzzz:
IR port is working. Tested with smart ir

flip cover is working also

I dont understand issue with screen rotation
[Galaxy Note Pro 12.2 Android Development] arcadia2uk:
The screen doesn't automatically rotate when turning the device, although I have automatic rotation enabled in System/Display/ with values 0/90/180/270. However, with some apps a forced rotation arrive that turn the screen from landscape to portrait, after this the screen stay in portrait until another app trigger a turn to landscape. Anyway, blocking the screen in landscape, or in portrait with the apps I mentioned in my post works perfectly well, but it's a forced rotation, not automatic. It could be device specific? - note issue only concern T-900, not P900/901

I retested IR and Lid and they worked when flashing the ROM with TWRP 8.2.1.1. This was either a glitch, or the fact that I flashed in MultiROM.
[Galaxy Note Pro 12.2 Android Development] bonuzzz:
download please z-device test https://play.google.com/store/apps/details?id=zausan.zdevicetest and send me screenshot of his report

multirom in current state uses kernel from primary rom in additional roms. Concerning screen rotation, I think it is specific for t900 and I'll solve it in next release.
[Galaxy Note Pro 12.2 Android Development] arcadia2uk:
That kernel use can explain some of the oddities I've experienced.

On the T-900 I had the screen rotation issues as well, along with other users, so I believe it's a T900 issue. It works with stock ROM though. Also, I just forwarded some screen shots.
[Galaxy Note Pro 12.2 Android Development] brock28:
Hey guys thanks for yet an other custom rom you sure have been working hard! I did some reading about this omnirom and i conclude imo it is prefereable to cyan, is valeria working only on omni now i noticed she released a new cm. Thanks again looking forward to next release.
[Galaxy Note Pro 12.2 Android Development] nsiti:
Hi friends, I wanted to thank you for bringing OmniRom to the Note Pro 12.2.

I will be sure to install it this coming weekend when I have some time

I'm currently on CM and it's very nice, but I like the idea of Omni being truly open source.

Your efforts are greatly appreciated.
[Galaxy Note Pro 12.2 Android Development] rkirmeier:
Ok I was excited when OmniROM was originally announced but honestly that was mostly because of the multi window stuff the is now available via Xposed. How is Omni better than CM? I have to say I have the CM build on my tablet and it's exceptional, can't believe it's this good when the Note 12.2 just recently become supported. Is Omni really noticeably faster/smoother?
[Galaxy Note Pro 12.2 Android Development] arcadia2uk:
My experience running the beta release that even at this stage it is already faster and smoother than cm-11. Try it and and you can tell directly by the screen transitions, and this is just the beginning. But the reason for OmniROM is more flexibility, it's a true AOSP ROM, meaning there's a lot more flexibility in deploying the code, than under cm that start loosing its freedom in development under a corporate flag. Besides, Omni is already better prepared for this, you can see this in it's deployment of the OmniSwitch as well as other features, eg. under the performance tab, where OC, undervoltage and other settings, and there is more...

However, the best way is to try it out and judge for your self.

On the other hand, if you really want to read up about it, check out this article
[Galaxy Note Pro 12.2 Android Development] notspike:
Where is the multi-window support as shown in this vid?

https://www.youtube.com/watch?v=f5bcccyBPsU
[Galaxy Note Pro 12.2 Android Development] rkirmeier:
Thanks for the info and that is an interesting read. I'll probably give OmniROM a try...
[Galaxy Note Pro 12.2 Android Development] arcadia2uk:
I don't believe it is implemented. But, the split view feature in the video exist as the xposed module: XMultiWindow. This was Omin's first release of the multi-window feature, and the development is still ongoing for a more feature packed floating window solution. See for example this concept idea.
[Galaxy Note Pro 12.2 Android Development] bonuzzz:
multiwindow had been removed from omnirom in spring 2014.
[Galaxy Note Pro 12.2 Android Development] bonuzzz:
published first release for P901. I dont have this tab, so I cant testing. I hope mobile part is working here. Write your feedback please
[Galaxy Note Pro 12.2 Android Development] francesco totti:
can't download it !! when i press the download button nothing happens!! does camera work in this build ?? Thanks.
[Galaxy Note Pro 12.2 Android Development] bonuzzz:
https://yadi.sk/d/xTQ0HUhocaBpC

no. camera is not working yet
[Galaxy Note Pro 12.2 Android Development] Stevethegreat:
I remember back in the day when cm tried to add multiwindow and got stopped by Google. I understand it's a hard undertaking, but honestly without it tablets are toys to me, overblown phones which is why samsung is the only game in town concerning tablets. It's not the best possible implementation and not fast by any stretch of the imagination. But going back to a nexus 9 even seems like a severe handicap to my usage patterns. It just does significantly less than what a tablet ought to do as I m using them.

Having said that tw roms tend to be slow and greedy in resources which was why I always hoped for an aosp derived multitasking and I was disappointed to see omni team dropping it. Aosp roms are reverted back to novelty items to me, unsuitable for serious use. Still I may flash them every now and then for specialized uses (for example VT based linux).

Anyhow, [MENTION=242033]bonuzzz[/MENTION] thanks for your continuing support of this device...
[Galaxy Note Pro 12.2 Android Development] arcadia2uk:
OmniROM Now Booting on Android 5.0 Lollipop

from xda article

OmniROM has officially become the first large-scale custom ROM distribution to merge and successfully boot Android 5.0 Lollipop. The initial boot was performed with the Nexus 7-2013

More details in main Omni Lollipop thread.
[Galaxy Note Pro 12.2 Android Development] bonuzzz:
I've already compiled lollipop for note12.2 today. It needs a lot of work to bug fixes. Maybe somebody else decide to deal with lollipop now, but I''ll contunue to work with kitkat next months
[Galaxy Note Pro 12.2 Android Development] nsiti:
I'm using OmniRom now, it seems speedier than CM. Thanks for your efforts.

Edit, lots of little bugs to stomp out though. CM is much more stable than Omni.

I experienced problems entering data into user password dialog boxes, as well as mini crashes at the main page and when adjusting certain settings.
[Galaxy Note Pro 12.2 Android Development] bonuzzz:
where is it?
[Galaxy Note Pro 12.2 Android Development] arcadia2uk:
It would be very appreciated to have some specifics, in order to recreate the issue while trying to fix it.

Did you perform a complete re-install, wiping factory reset and advanced wipe checking cache, dalvik and system before flashing the ROM? In what apps did you have issues to enter password? What settings was adjusted leading to mini crashes? What do you mean by mini-crashes, softwares that announces a close? which ones? etc.

The developers need your input in order to improve the ROM's and not only for Omni, but w/o specifics it is very difficult to fix things.

Even better, logs...
[Galaxy Note Pro 12.2 Android Development] nsiti:
Hi, yes, I performed a factory reset before installing OmniRom.

The problem I experienced was when logging into the Wall Street Journal app, i could not switch from the username to the password boxes, I had to close and restart, then it worked. One mini crash was when changing the auto-brightness screen setting within options. Another was when running a program, don't remember which one, sorry.

I will continue to report any bugs I experience.

Thanks for your efforts with this ROM.
[Galaxy Note Pro 12.2 Android Development] arcadia2uk:
Thanks for the input nsiti.

However, factory reset is often just not good enough switching from one ROM to another, as it doesn't reset the dalvik, or so I believe. I always do an advanced wipe after factory reset, where I check-mark: cache, dalvik and system, and so far I have not experienced any issues. The mini crashes often seem to occur when dalvik wipe is not performed, or when re-installing an app with titanium backup along with the data. If a specific app gives you trouble, go into settings/apps and reset data for that app.

From my own experience, I have not had a single issue (once I learned that MultiROM uses a default kernel, but once installed on its own I have not seen a single issue), except for the ones reported as non-working in the OP.
[Galaxy Note Pro 12.2 Android Development] nsiti:
Hi, please note that as per TWRP (http://teamw.in/whattowipe) a factory reset wipes data and cache (which includes dalvik cache). A factory reset will also wipe sd-ext and android_secure if your device has those items. 99% of the time, this is all that you need to wipe and you only need to do it once, not three times as some people would lead you to believe.

This is what I did and I manually installed all apps (didn't use Titanium as I know it can cause problems). It's time consuming but worth it when changing Roms, in my opinion.

I don't want to give the wrong impression, I like Omni and look forward to future improvements, and would encourage others to try it too.

I briefly used the tablet yesterday and didn't experience any problems in normal use: web browsing on Firefox, email (K-9, Inbox, Touchdown), twitter, facebook, news apps, etc.

Regards,
[Galaxy Note Pro 12.2 Android Development] rkirmeier:
I loaded up OmniRom (did full factory reset) and it didn't seem any faster them CM11. I also was getting some strange popups that would disappear almost instantly. That and not multi window support I just restored my CM11 backup.
[Galaxy Note Pro 12.2 Android Development] arcadia2uk:
Theoretically yes, but TWRP disabled "secure discard" in version 2.8.x., in order to make things faster in comparison with 2.7.x, why the job of wiping the data...
[Galaxy Note Pro 12.2 Android Development] canezila:
900 didn't install. Will re-download to try again
[Galaxy Note Pro 12.2 Android Development] arcadia2uk:
It takes a while before the update kicks in using TWRP, sometimes up to 3 min., just be patient. It might also take some time at first boot.
[Galaxy Note Pro 12.2 Android Development] canezila:
It reports that I am trying to install a wrong version. Then it exits. Sorry to not have the exact error message. I left it at work. I will try again now and report.

---------- Post added at 12:53 AM ---------- Previous post was at 12:25 AM ----------

Ok. I tried both just to make sure. Using the 900 version I get "this package is for v1awifi" devices this is a "v1a3gxx""...... But I have a p900.... Bummer
[Galaxy Note Pro 12.2 Android Development] arcadia2uk:
Apparently you have installed TWRP for the SM-P901 (v1a3gxx). if you download [URL="http://techerrata.com/browse/twrp2/v1awifi"]SM-P900 (v1awifi)[/URL] it should work. I suggest using version 2.8.1.1 in .tar format and then flash it with Odin.
[Galaxy Note Pro 12.2 Android Development] canezila:
Oh really? Thanks for the help. I will fix it
[Galaxy Note Pro 12.2 Android Development] bonuzzz:
if you have p900 model you need to download and install p900 version. if you have 3g model, so install p901 version
[Galaxy Note Pro 12.2 Android Development] notspike:
Hi bonuzzz, any updates coming to Omnirom or CyanogenMod soon?
[Galaxy Note Pro 12.2 Android Development] bonuzzz:
Good question...

I have two problems: I'm very busy at work and I've lost all work about omni. I'm trying to restore, but very slow. It's difficult to talk about any eta, but I will publish asap.
[Galaxy Note Pro 12.2 Android Development] Sterist:
camera not working is a permission goof, hadtg same problem with the acer iconia a700

[MENTION=2633638]Ziyan[/MENTION]
[MENTION=242033]bonuzzz[/MENTION]
[Galaxy Note Pro 12.2 Android Development] bonuzzz:
Has anyone tried P901 version? Is it working?

I haven't received any feedback about that release and I dont have p901 model, so if any feedback doesn't received, I'll stop support it.
[Galaxy Note Pro 12.2 Android Development] francesco totti:
I downloadet it but it didn't have time to test it !! I will try to test it tommorow! ! after all thanks for the efforts! !
[Galaxy Note Pro 12.2 Android Development] Aurondios:
I have a problem :(

I use this tablet to take notes at university, In samsung stock while u write with the spen, the physical buttons are off, but in this rom, when i write with spen the physical buttons works, so i always close the app, or go to recents...

It is possible to deactivate it?

Sorry for my bad english, have a nice day ;)