|
Aroma (as far as I understand) is a kind of boot script thing lots of ROMs use now to make the flashing process really user friendly. HTC One M7 using the ViperOne v.7.0.1 I managed to use TWRP to fix the partitions and reformat ect. Still stuck on 1% every time though...
|
#
?
Nov 6, 2014 18:57
|
|
|
|
| # ? May 25, 2024 17:45 |
|
|
This is definitely not normal. Its been stuck at this step for over 10 minutes now (1%). Edit: got it. Had to use an OLDER version of TWRP! Gozinbulx fucked around with this message at 19:16 on Nov 6, 2014 |
|
#
?
Nov 6, 2014 19:07
|
|
|
Can you just flash it with fastboot instead?
|
|
#
?
Nov 6, 2014 19:16
|
|
|
Just rooted my OnePlus and immediately decreased the DPI. Whoa, now suddenly this phone makes a lot more sense! Definitely recommended for any giant phone owners if you do nothing else with your root access.
|
|
#
?
Nov 6, 2014 21:13
|
|
|
mobby_6kl posted:Just rooted my OnePlus and immediately decreased the DPI. Whoa, now suddenly this phone makes a lot more sense! Definitely recommended for any giant phone owners if you do nothing else with your root access. That's the one that puts more info on the screen, right? Did that to my note and I can confirm it's better.
|
|
#
?
Nov 6, 2014 21:33
|
|
|
So I gave my old samsung galaxy nexus to my father to mess around with over a year ago. I had rooted and loaded some custom rom and I have no idea what it was because I haven't dicked with it since then. It might have been cyanogen or just takujo or whatever the stock rom was at the time. I wanted to get 4.0 on it when I had it because my nexus 7 got it OTA and I don't remember if the galaxy nexus did or not. I figured he was just going to play around with the phone a bit and see how he liked the whole Android experience but he (somewhat?) recently restored to factory defaults with the settings menu. The phone won't boot into the bootloader or anything like that, there's no indicator light that says it's connected to power with/without the battery in. I'm guessing the phone is bricked but figured I'd ask here before I sent it off for recycling. I don't need the phone or really want it, but is there anything I should try before giving it up for ghost? Since it's unresponsive to anything I figure it's a lost cause. Mr Newsman fucked around with this message at 14:40 on Nov 7, 2014 |
|
#
?
Nov 7, 2014 14:37
|
|
|
quote =/ edit
|
|
#
?
Nov 7, 2014 14:39
|
|
|
Mr Newsman posted:So I gave my old samsung galaxy nexus to my father to mess around with over a year ago. I had rooted and loaded some custom rom and I have no idea what it was because I haven't dicked with it since then. It might have been cyanogen or just takujo or whatever the stock rom was at the time. I wanted to get 4.0 on it when I had it because my nexus 7 got it OTA and I don't remember if the galaxy nexus did or not. Well, I'm not sure what variant you have, but here's a post at XDA detailing using odin to reflash a soft bricked phone, and there are similar posts for other versions. Lots of stuff for that phone still out there including 4.4.4 builds of potentially stable roms and official official images up to 4.3 depending on the model.
|
|
#
?
Nov 7, 2014 16:30
|
|
|
Blitter posted:Well, I'm not sure what variant you have, but here's a post at XDA detailing using odin to reflash a soft bricked phone, and there are similar posts for other versions. I guess I should clarify that it won't boot up at all. I have no idea what the man did to the thing but he done hosed it up good.
|
|
#
?
Nov 7, 2014 16:46
|
|
|
Mr Newsman posted:I guess I should clarify that it won't boot up at all. I have no idea what the man did to the thing but he done hosed it up good. Uh so what do you think we can do? The phone won't power on at all? Have you tried putting it in the microwave for an energy transfusion?
|
|
#
?
Nov 7, 2014 17:28
|
|
|
Mr Newsman posted:I guess I should clarify that it won't boot up at all. I have no idea what the man did to the thing but he done hosed it up good. Nothing weird with the USB port, like obviously wiggly or full of cruft? Failing anything that obvious a bit of googling suggested that the Galaxy Nexus had this kind of problem, occasionally solved by the following - remove USB power, remove battery, apply USB power, insert battery, press power button. *shrugs* I mean, you can burn some incense and kill a few chickens for the added voodoo handwaving but it does sound like it might just be failed hardware too.
|
|
#
?
Nov 7, 2014 17:29
|
|
|
So I currently have Rogue ET 1.1.2 on my 4g Epic touch running Unnamed Rom from back in the stone age. It was a great Rom, light weight and light on the battery but I wanted to bump it to something more modern. I notice a lot of Roms mention things with using the latest recovery version. Then other say things about the different types of recovery programs. What's the safest way for me to get to something like this?: http://forum.xda-developers.com/epic-4g-touch/orig-development/rom-dirty-unicorns-4-4-4-v7-8-t2838547
|
|
#
?
Nov 7, 2014 17:30
|
|
|
Blitter posted:Nothing weird with the USB port, like obviously wiggly or full of cruft? Failing anything that obvious a bit of googling suggested that the Galaxy Nexus had this kind of problem, occasionally solved by the following - remove USB power, remove battery, apply USB power, insert battery, press power button. USB port is fine. When searching a bit I found this http://forum.xda-developers.com/galaxy-nexus/general/bricked-gnex-brought-to-life-t1760787 and checked the device manager and turns out it was doing the same thing (omap popping in and out every couple of seconds). Tried it, their .bat file wanted me to turn off the device (which isn't on). I'm not looking to spend a few more hours installing and uninstalling device drivers and trying to catch some two second window bullshit in order to get a phone I don't care much about back to life. Thanks for the help though! It doesn't look like it's bricked but I can't really justify the time spent to get it back to life I don't think.
|
|
#
?
Nov 7, 2014 18:27
|
|
|
maniacripper posted:So I currently have Rogue ET 1.1.2 on my 4g Epic touch running Unnamed Rom from back in the stone age. It was a great Rom, light weight and light on the battery but I wanted to bump it to something more modern. What do you mean by "safe"? If you can't tell what you're flashing, or how to do it, then well, it's not safe, and you shouldn't do it. Why don't you read something on XDA? I mean, I know it's painful, but you could notice that cm11 (which the rom you want is based on) uses cwrm (http://forum.xda-developers.com/showthread.php?t=2652286) or perhaps other things like: SomeDudeBro posted:
.. ah, useful - data comes and goes, randomly!. Might be worth waiting for a better build? Blitter fucked around with this message at 18:47 on Nov 7, 2014 |
|
#
?
Nov 7, 2014 18:40
|
|
|
maniacripper posted:So I currently have Rogue ET 1.1.2 on my 4g Epic touch running Unnamed Rom from back in the stone age. It was a great Rom, light weight and light on the battery but I wanted to bump it to something more modern. Um please call your phone by the correct name: The Samsung Galaxy S II Epic 4g Touch by Sprint: The Now Network
|
|
#
?
Nov 7, 2014 20:46
|
|
|
Blitter posted:What do you mean by "safe"? If you can't tell what you're flashing, or how to do it, then well, it's not safe, and you shouldn't do it. Why don't you read something on XDA? I mean, I know it's painful, but you could notice that cm11 (which the rom you want is based on) uses cwrm (http://forum.xda-developers.com/showthread.php?t=2652286) Hey thanks that's just what I was looking for!
|
|
#
?
Nov 8, 2014 03:03
|
|
|
Anyone out there have some experience with creating keylayouts (.kl files) for usb devices for Android? I think I understand it (vendor_xx_product_xx.Kl) and it even seems trivially easy. In fact, I'm shocked I have yet to find an app that simply created/edits existing keylayouts (don't say tincore, it doesn't do this). There are apps that show you what keyevent each button does, they're apps that show which soft button is triggered by each keyevent, and they're apps that show you vendor and device id of plugged in peripherals. But there Is no app that does all 3 and saves it in a simply formatted text file that is a .kl Yet despite all that, my attempt to create a kl for a generic usb gamepad I have did not work. Yes I know some games let you map the controls for that game but they're are actually many that do not and will only respond to a gamepad that conforms to a standard layout. Any help?
|
|
#
?
Nov 8, 2014 05:36
|
|
|
Cross posting from the Sprint thread. So I bought a supposedly new Note 2 and after setting it up it got an OTA 4.3 update. After it restarted the phone didn't boot. It would flash the white text "galaxy note" then nothing... I went and ODIN flashed to 4.4.2 and I found some troubling things:  WTF does this poo poo mean? Knox is triggered and I know what that is so I guess this phone wasn't new after all?
|
|
#
?
Nov 11, 2014 16:42
|
|
|
Looks like its been rooted/boot loader unlocked. It shouldn't be a problem. Were you able to restore the original factory image via odin? You should refer to XDA for restore solutions. http://forum.xda-developers.com/showthread.php?t=2389426 Also this looks pretty straight forward: Samsung Galaxy Note 2: back to stock, unroot, stock recovery and reset flash counter http://www.andromods.com/unroot-locking/samsung-galaxy-note-ii-restore-stock-no-root-reset-flash-counter.html r0ck0 fucked around with this message at 16:49 on Nov 11, 2014 |
|
#
?
Nov 11, 2014 16:44
|
|
|
Why the gently caress are you giving him a project to do? Dude was sold a used phone as new, take it back. It doesn't matter if he can get it back to normal, he was sold something different than he was told.
|
|
#
?
Nov 11, 2014 16:52
|
|
|
RZA Encryption posted:Why the gently caress are you giving him a project to do? Dude was sold a used phone as new, take it back. It doesn't matter if he can get it back to normal, he was sold something different than he was told. I assumed he bought it on craigslist or the like and uh good luck returning poo poo there. But ya if you bought it from a store why would you even post it here, take it back. Do they even sell new notes 2 anymore?
|
|
#
?
Nov 11, 2014 16:54
|
|
|
I was able to ODIN flash 4.4.2 and everything seems to be fine. And I got it on Swappa, I've been in contact with the seller about it who of course has no idea why it says that since "all his phone are factory new". I guess we'll see how it goes with Swappa since it's his word vs mine at this point. VVVV The only way I know to check is through the ## menu on the phone and it reported the phone as not refurbished maniacripper fucked around with this message at 19:28 on Nov 11, 2014 |
|
#
?
Nov 11, 2014 19:17
|
|
|
Who still has factory new phones that were released 2 years ago? You sure they are not factory refurbished?
|
|
#
?
Nov 11, 2014 19:26
|
|
|
maniacripper posted:I guess we'll see how it goes with Swappa since it's his word vs mine at this point. I had a similar thing happen to me (bought "mint" phone on Swappa that had scuffs on it) and successfully resolved it through Paypal. Definitely file a Paypal claim if the seller won't take it back. Be sure to include details and point them to Swappa's condition criteria FAQ which states that new phones must be unused and never activated. Paypal tends to side with buyers so you will be fine. Also see if you can get the seller to admit to something (like the phone being refurbished) while talking to him on the Swappa sale page. Mine actually apologized for picking the wrong condition (and still refused a refund) so I added that tidbit when filing the claim. Hikaki fucked around with this message at 21:00 on Nov 11, 2014 |
|
#
?
Nov 11, 2014 20:57
|
|
|
Christ, Lollipop made poo poo even more complicated to have a working rooted system. This is an all-night project just to get two devices working. And despite what the thread title says, until the Google cloud's restore function also includes user data such as login sessions, app preferences, etc; Titanium etc is always required IMO. That's just some basic poo poo that never has happened.
|
|
#
?
Nov 13, 2014 05:25
|
|
|
Craptacular! posted:Christ, Lollipop made poo poo even more complicated to have a working rooted system. This is an all-night project just to get two devices working. That's annoying to hear. What devices are you using?
|
|
#
?
Nov 13, 2014 05:33
|
|
|
Nexus 5 and 10. Instead of flashing TWRP and a SuperSU binary, the everyman how has to get a device-specific root utility from Chainfire that runs a script of stuff, including some kind of boot image flash that on the device shows you a picture of a red bugdroid with a piracy eyepatch as text quickly flies by and then tah-dah you're rooted. Apparently this is some kind of kernel patch due to all the SElinux additions that have been made. But it's simply the way things are right now for people who have a low tolerance for technical bullshit. EDIT: So I'm flashing these Chainfire things and SuperSU doesn't appear at all. The more and more I go deeper into this hell, the more I think people will just start downloading pre-rooted OSes from XDA and not bother with patching their stock systems. Craptacular! fucked around with this message at 06:09 on Nov 13, 2014 |
|
#
?
Nov 13, 2014 05:54
|
|
|
Stupid question: Why can't I flash a Nexus 5 system image with TWRP? Why do I have to connect it to a computer and run terminal commands?
|
|
#
?
Nov 13, 2014 06:49
|
|
|
Craptacular! posted:Nexus 5 and 10. Instead of flashing TWRP and a SuperSU binary, the everyman how has to get a device-specific root utility from Chainfire that runs a script of stuff, including some kind of boot image flash that on the device shows you a picture of a red bugdroid with a piracy eyepatch as text quickly flies by and then tah-dah you're rooted. Its really not as difficult as you are making out
|
|
#
?
Nov 13, 2014 10:00
|
|
|
b0nes posted:Stupid question: Why can't I flash a Nexus 5 system image with TWRP? Why do I have to connect it to a computer and run terminal commands? The system image isn't a zip. It contains a stock recovery that will overwrite your TWRP. And on the Nexus 5, there's a new radio. Skarsnik posted:Its really not as difficult as you are making out Craptacular! fucked around with this message at 10:07 on Nov 13, 2014 |
|
#
?
Nov 13, 2014 10:04
|
|
|
Has something changed from the second preview image? Fastboot modded kernel then root as normal. Haven't re-rooted yet but will be doing it today so I'll report back.
|
|
#
?
Nov 13, 2014 10:44
|
|
|
Yeah its the same, but you might as well just use CF Autoroot, as it patches the kernel and installs SuperSU 2.20 in one go Just run the zip from windows or whatever with the phone in fastboot mode There are still a couple of apps that havent been updated properly to use it, es explorer for one (root explorer works fine), and you need the beta version of Titanium Backup
|
|
#
?
Nov 13, 2014 10:58
|
|
|
Tunga posted:Has something changed from the second preview image? Fastboot modded kernel then root as normal. Haven't re-rooted yet but will be doing it today so I'll report back. I'm sure Koush's Superuser hasn't been updated yet either so I guess I have to go back to SuperSU.
|
|
#
?
Nov 13, 2014 11:13
|
|
|
Skarsnik posted:Yeah its the same, but you might as well just use CF Autoroot, as it patches the kernel and installs SuperSU 2.20 in one go I grabbed the CF-Auto-Root package and it's just a shell script which boots to (not flashes) a mysterious kernel image. Presumably that then patches the kernel and installs SuperSU, but it's a little opaque. LastInLine posted:Is there a place I should be grabbing this stuff? I haven't kept up but I know there's a kernel I need to flash but I haven't searched for it yet.
|
|
#
?
Nov 13, 2014 11:57
|
|
|
Tunga posted:I don't really like these "auto root" things. Yeah i'm usually the same, but seeing as otherwise all I'd be doing is installing the modified kernel from chainfire, and then installing supersu from chainfire.. I might as well just let chainfires script do it all in one
|
|
#
?
Nov 13, 2014 12:06
|
|
|
Is there ever going to be a version of gravitybox for L? I'm glad I have to root my device and use extra software to get rid of the 'potential hearing damage' message every time I plug in my headphones. Also the fact that it sets the volume back to half way every loving time  Or does this not happen on L? Anyone in the uk can confirm this?
|
|
#
?
Nov 13, 2014 12:48
|
|
|
track day bro! posted:Is there ever going to be a version of gravitybox for L? I'm glad I have to root my device and use extra software to get rid of the 'potential hearing damage' message every time I plug in my headphones. Also the fact that it sets the volume back to half way every loving time Gravitybox on Lollipop is really all dependent on if the Xposed dev gets it (Xposed) working on ART.
|
|
#
?
Nov 13, 2014 14:21
|
|
|
track day bro! posted:Is there ever going to be a version of gravitybox for L? I'm glad I have to root my device and use extra software to get rid of the 'potential hearing damage' message every time I plug in my headphones. Also the fact that it sets the volume back to half way every loving time I got that message once but never again, it seems to remember over a reboot now. It doesn't reduce the volume when you plug headphones in either. Also when I did get the message I almost missed it, as apparently just pressing volume up again clears it now.
|
|
#
?
Nov 13, 2014 14:31
|
|
|
Skeezy posted:Gravitybox on Lollipop is really all dependent on if the Xposed dev gets it (Xposed) working on ART. The Xposed guy has spent the last 6 months or so whining about ART support so it's probably going to be a while.
|
|
#
?
Nov 13, 2014 14:42
|
|
|
|
| # ? May 25, 2024 17:45 |
|
|
Whizbang posted:The Xposed guy has spent the last 6 months or so whining about ART support so it's probably going to be a while. Honestly I wonder if he's even going to bother doing it.
|
|
#
?
Nov 13, 2014 15:02
|
|