Hello,
For some reason that is not relevant, i made a factory reset on my rooted ouya console. When i finished the set-up, the system installed Chupacabra R1 (1.2.1084_r1).
When i try to install "Root My Ouya" from sdcard using FilePwn app, i got "App Not Installed" as result.
NOTE: I don't remember if i had 1.2.995_r1 installed before factory reset (again, when i had root).
UPDATE: I did another factory reset. Ouya is now rooted.
Testing
Second test
Related
I rooted my device yesterday and installed clockworkmod, then i was going to install a new rom on my device. But i decided to this the next day, but i still deleted
cache and did a factory reset, When i booted up i didnt find superuser and i downloaded titanium backup and the programe said i was not rooted.
So i installed visionary r12 and it said im rooted. what Now?
Now i uninstalled r12, and unstalled r14, and got everything to work,
now i want to take a backup but in rom manager when i press backup rom, it tells me
E:cant open /cache/recovery/comand
Have you turned Security Off (S-OFF)?
Yes i installed s-off before factory reset, shuld i try to do it again
In ROM Manager try to flash ClockworkMod Recovery again. Most users note that it doesn't work first time.
I find more assuring to make a backup from within CWM Recovery. Six and 2 Threes I know.
It worked to reflash clockwork. Thank you<3
No problem.
Being a total noob, I am happy to report that my KF1 is now running CM10 (Android 4.1.2):
http://forum.xda-developers.com/showthread.php?t=1778010
[ROM] CM10/SGT7 for the Kindle Fire [20121224] [Linaro]
Some problems I ran into:
1) Installed Kindle Fire Utility (KFU) and drivers. KFU could not find Kindle Fire.
SOLUTION: Make sure Kindle Fire is disconnected from computer before installing drivers. If necessary, completely uninstall drivers, restart system, then re-install. Afterwards, you can connect your Kindle and it will should up on KFU.
2) Installed a custom rom using TWRP. Upon reboot, rom was stuck at loading screen.
SOLUTION: I didn't do a factory reset. In the Wipe menu on TWRP, make sure you do a Factory Reset, Cache Wipe, Davlik Cache Wipe, and System Wipe.
3) AOSS Keyboard kept force closing.
SOLUTION: Make sure you're running the correct version of Google Apps (GAPPS). I was installing GAPPS 4.2.x. It should have been 4.1.x for this particular rom.
I also recommend not restoring system data from titanium backup when changing roms. I did that when downgrading from a cm10.1 rom to a cm10 rom and it just got stuck at the cm splash screen until I did a factory reset.
Sent from my Amazon Kindle Fire using Tapatalk HD
Robb Flynn said:
Being a total noob, I am happy to report that my KF1 is now running CM10 (Android 4.1.2):
http://forum.xda-developers.com/showthread.php?t=1778010
[ROM] CM10/SGT7 for the Kindle Fire [20121224] [Linaro]
Some problems I ran into:
1) Installed Kindle Fire Utility (KFU) and drivers. KFU could not find Kindle Fire.
SOLUTION: Make sure Kindle Fire is disconnected from computer before installing drivers. If necessary, completely uninstall drivers, restart system, then re-install. Afterwards, you can connect your Kindle and it will should up on KFU.
2) Installed a custom rom using TWRP. Upon reboot, rom was stuck at loading screen.
SOLUTION: I didn't do a factory reset. In the Wipe menu on TWRP, make sure you do a Factory Reset, Cache Wipe, Davlik Cache Wipe, and System Wipe.
3) AOSS Keyboard kept force closing.
SOLUTION: Make sure you're running the correct version of Google Apps (GAPPS). I was installing GAPPS 4.2.x. It should have been 4.1.x for this particular rom.
Click to expand...
Click to collapse
Good job. Glad it worked out for you.
A note about solution #1:
The problem in this case isn't so much the drivers, as many (including I) had once believed. The problem is the stock bootloader itself. From what I understand, fastboot shouldn't require drivers to work properly anyway. I'm guessing, the stock bootloader (Kindle Fire logo) isn't the same bootloader the device had in it's infancy and this is causing some very confusing problems for a lot of new users.
For one, the command "fastboot devices" will never show a device connected in fastboot mode. And, when you send any other fastboot command, you'll see it hang at "<waiting for device>", indefinitely. * The solution for this, is to send the command with the device shut down completely and then turn the device back on (this is why it worked in your case). Then, as the device boots up again, fastboot will detect the device and continue with whatever process was waiting for the device. KFU uses the same fastboot commands to check if a device is connected (fastboot devices) and install FFF and TWRP (fastboot flash...), therefore the solution is still the same.
That's not to say the bootloader is always the problem. The stock boot animation can easily be confused with the stock bootloader splash screen, but that's another subject altogether.
I hope this helps to clear up some confusion as to what is actually happening when fastboot doesn't seem to be working properly.
Once you've installed your apps and got your KF running smoothly with your new ROM, reboot into TWRP and do a backup. I usually backup Data only. I keep the ROM and the GAPPS on my KF's SDcard so if I ever need to reinstall, I can do a clean wipe (the caches, factory reset, system), install the ROM and GAPPS, and restore my Data from backup.
I also recommend backing up Data regularly and testing your Data backups.
I strongly recommend twa_priv's CM10.1 rom. I use it 2 Kindle Fire's that my kids have.
Today he added hashcode's new Kernal tweaks, and the battery drain in standby (deep sleep) is unbelievable now! My daughter's Fire is getting about -15 drain when sleeping now, it was getting about -35 before todays update, and honestly I thought that was pretty good. Now ita amazing.
(I use battery monitor widget from 3c to check battery drain)
I searched for my particular issue and haven't found a solution that works yet so here goes. any help with this issue would be greatly appreciated.
I've painted myself into corners before tinkering with this phone and always found a way out but this time I'm stumped.
HOW I BROKE MY PHONE:
1) had latest CM 11 nightly installed but wanted to try the OTA.
2) In TWRP I restored a back up of my stock rooted software.
3) Unfroze bloat in titanium back up.
4) Checked on phone for OTA, received notification, and began download
5) On completion of download I initiated the update.
6) It booted to recovery (TWRP) and every time I rebooted, or started the phone from powered down it always goes into TWRP.
7) I attempted a factory reset and restoration of my stock back up- same result. It booted straight into recovery.
8) I factory reset and installed cm11 fresh from the SD card- same result
9) Here's my real screw up: since neither installing a fresh ROM or restoring my stock recovery weren't working I went for the nuclear option, I decided to format everything and use the LG Flash tool to get this puppy back up and running.
10) Only to discover I can't get into Download mode and while the G2 is "seen" by my PC it's listed under "other devices."
Dear kind and wise individual who's read my tale of woe. What might my next step be? I've considered attempting to sideload a ROM with TWRP in sideload mode, but I'm afraid I'd just have the same result as when I tried reinstalling CM11 from the SD card.
this
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
Many thanks! I'll give this a try.
Hi, I came from 4.2.2 stock rooted. I was updating to 4.4.2 (D80220a-ESA-XX) via LG Support Tool and make it go back to stock unrooted again. Next I rooted using ioroot25. After a fresh flash, I performed encrypt phone but the process was too fast, I was amazed until I checked that the disk wasn't actually encrypted.
I did again, but this time I was using factory reset via Backup and Reset and performed encrypt phone, but same result. The device just rebooted and blank, no android logo with encrypting process shown thus the encryption process failed.
Is this a bug? Anybody here face the same problem?
Any help will be appreciated :good::good:
I finally went back to stock, the encryption was working out. Here is what i've done:
Run make_ext4 /dev/block/mmcblk0p35, reboot again and apply encrypt phone (failed)
Back to stock using offline mode and re-apply encryption (success)
Root, Install TWRP and reboot (failed, TWRP 2.7.0.0 didn't prompt password for encrypted partition)
Install PAC ROM and CM 11 via TWRP sideload (success), BUT both of ROMs can't open the encrypted storage (failed)
Back to stock again, root, install TWRP, install PAC ROM, boot into PAC and apply encryption (failed, the PAC ROM can't perform encryption, it's just back to boot normally). This applied to CM as well.
My conclusion, LG has performed their owned encryption method instead of using AOSP method. I can't understand why PAC and CM failed performed their encryption method while using AOSP encryption method.
For now, I'll stick to stock since I need the encryption.
Hi Guys,
i lately got on old Samsung Tab 9.7 with an official Android 7 Nougar running on it.
I decided to flash twrp_3.1.0-1_sm-t550_13317 with Odin3_v3.10.7. I followed the steps ashyx described in his thread. So far so good..
Afterwards I installed SR5-SuperSU-v2.82-SR5-20171001224502 from SDCard and it prompted to reboot... now there is the problem.. It won't reboot. It says "Check failed" and I have to factory reset it. When pressing the button it boots into twrp and I can only spot red lines until it reboots with kernel binary and I'm back at the same point.
Any ideas what to do?
btw. are there any new version of twrp , SuperSu or Magisk I can use? Couldn't find any newer versions. I also search for any ROM which has the most up-to-date status (if there are any xD)
Thanks guys
Not my type of tablet but when the SM-T585 had those issues it was a wrong version of TWRP, so maybe look into that.
And SuperSU, really? That's been dead for years, use Magisk instead. It has a whole subforum here on XDA.
/edit: I managed somehow to install latest twrp and lineageOS.. but on first boot it brings up an encryption error.
"encryption was interrupted and can't complete..."
I need to factory reset the tablet... but with that i run again into a bootloop. I can't wipe "data" via twrp Error 8 was it, i think at least ^^
/edit2: I'd go with magisk... but I only find the .apk .. what do I have to flash in twrp?
/edit3:
Managed to reinstall twrp with latest verion twrp-3.5.2_9-0-gt510wifi.img. wiped all data ... Installed Magisk-v23.0 afterwards lineage-18.1-20211108-UNOFFICIAL-gt510wifi . But again.. encryption error on Lineage boot.
Problem solved.
reverted to complete stock, afterwards flashed twrp, installed magisk + lineage 18.1 + OGapps 11.0.
Now it's running.