Disclaimer: I am not responsible for anything that happens to your device.
This requires an unlocked bootloader.
- Stock kernel
- Roots device + installs SuperSU on first boot
- Tested on Rogers Moto X
Download Rogers image: http://d-h.st/cFB
Download ATT image: http://d-h.st/1XI
Rogers kernel version:
3.4.42-xline-gfd1a699-00157-gfb2f8fc
[email protected] #1
Thu Jul 18 20:25:42 CDT 2013
ATT kernel version:
3.4.42-xline-gfd1a699-00158-g8990abb
[email protected] #1
Sat Jul 20 14:29:07 CDT 2013
Install:
reboot to bootloader
fastboot flash boot <image file name>
reboot device
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
rob43 said:
Disclaimer: I am not responsible for anything that happens to your device.
This requires an unlocked bootloader.
- Stock kernel
- Roots device + installs SuperSU on first boot
- Tested on Rogers Moto X
Download: http://d-h.st/btV
Install:
reboot to bootloader
fastboot flash boot ghost-boot.img
reboot device
Click to expand...
Click to collapse
This Is great! Now to apply it to att!
Sent from my MB886 using XDA Premium 4 mobile app
What kernel version is this?
Thanks ! I will wait the version where you don t need to unlock bootloader...
Sent from my XT1058 using XDA Premium 4 mobile app
pixeldrew said:
What kernel version is this?
Click to expand...
Click to collapse
Added to OP
rob43 said:
Added to OP
Click to expand...
Click to collapse
Cheers.
doh... only temporarily booted into the image so it reverted back to secure=1.
All good now.
rob43 said:
Disclaimer: I am not responsible for anything that happens to your device.
This requires an unlocked bootloader.
- Stock kernel
- Roots device + installs SuperSU on first boot
- Tested on Rogers Moto X
Kernel version:
3.4.42-xline-gfd1a699-00157-gfb2f8fc
[email protected] #1
Thu Jul 18 20:25:42 CDT 2013
Download: http://d-h.st/btV
Install:
reboot to bootloader
fastboot flash boot ghost-boot.img
reboot device
Click to expand...
Click to collapse
Correct me if I am wrong, but I thought the Rogers' Moto-X has unlocked bootloader? As in, no unlocking required?
You still have to unlock it via the Motorola website to assert that you voided your warranty.
Sent from my XT1058 using xda app-developers app
pixeldrew said:
You still have to unlock it via the Motorola website to assert that you voided your warranty.
Sent from my XT1058 using xda app-developers app
Click to expand...
Click to collapse
Gotcha. Too bad I went ahead and 'bricked' the device. Fastboot Reason: Flash Failure.
;P
All is well. I had to unlock the bootloader, reflash.
Edit 2: I can't update the SuBinary. It throws a generic error message, stating to contact the developer.
hidea said:
Gotcha. Too bad I went ahead and 'bricked' the device. Fastboot Reason: Flash Failure.
;P
All is well. I had to unlock the bootloader, reflash.
Edit 2: I can't update the SuBinary. It throws a generic error message, stating to contact the developer.
Click to expand...
Click to collapse
I got this as well, you're best off finding the superuser.zip from cyanogenmod's site and installing that by hand via adb.
Code:
[email protected] $ unzip superuser.zip
[email protected] $ adb push superuser/armabi/su /sdcard/
[email protected] $ adb shell
[email protected] $ su
[email protected] # mount -o rw,remount /system
[email protected] # copy /sdcard/su /system/xbin/
pixeldrew said:
You still have to unlock it via the Motorola website to assert that you voided your warranty.
Sent from my XT1058 using xda app-developers app
Click to expand...
Click to collapse
pixeldrew said:
I got this as well, you're best off finding the superuser.zip from cyanogenmod's site and installing that by hand via adb.
Code:
[email protected] $ unzip superuser.zip
[email protected] $ adb push superuser/armabi/su /sdcard/
[email protected] $ adb shell
[email protected] $ su
[email protected] # mount -o rw,remount /system
[email protected] # copy /sdcard/su /system/xbin/
Click to expand...
Click to collapse
Cheers! Any particular Superuser.zip you used?
Cyanogenmod's https://github.com/koush/Superuser
pixeldrew said:
Cyanogenmod's https://github.com/koush/Superuser
Click to expand...
Click to collapse
My wit ends here. I've never used Github. Truth revealed, I'm just a hobbyist!
hidea said:
Cheers! Any particular Superuser.zip you used?
Click to expand...
Click to collapse
The SU binary + Superuser.apk are both from the newest SuperSU (1.51). Where are you seeing the "su requires updating" message? SuperSU is already installed for you.
If you install CM's Superuser, you will get this error. I first tried CM's su + Superuser but the apk was not cooperating.
Nonetheless, you will be able to use su from the terminal and do any update you please. Trying to get CWM recovery working at the moment so this is no longer necessary.
rob43 said:
The SU binary + Superuser.apk are both from the newest SuperSU (1.51). Where are you seeing the "su requires updating" message? SuperSU is already installed for you.
If you install CM's Superuser, you will get this error. I first tried CM's su + Superuser but the apk was not cooperating.
Nonetheless, you will be able to use su from the terminal and do any update you please. Trying to get CWM recovery working at the moment so this is no longer necessary.
Click to expand...
Click to collapse
Cheers, I managed to get Terminal to work. But TIBackup still can't get root access. No popups that I'd normally get with CM/other rooted ROMs.
hidea said:
Cheers, I managed to get Terminal to work. But TIBackup still can't get root access. No popups that I'd normally get with CM/other rooted ROMs.
Click to expand...
Click to collapse
Not sure why that would be. Uninstall CM's Superuser if you downloaded it from the market. Only SuperSU worked for me.
Titanium Backup works without a problem here.
I would suggest deleting both su + Superuser.apk and rebooting, if you modified either in /system. Upon startup, it will reroot your device with the latest SuperSU + su binary.
rob43 said:
Not sure why that would be. Uninstall CM's Superuser if you downloaded it from the market. Only SuperSU worked for me.
Titanium Backup works without a problem here.
Click to expand...
Click to collapse
I never installed CM's Superuser. But I did try installing SuperSU ;P. Do I need to reflash everything again?
hidea said:
I never installed CM's Superuser. But I did try installing SuperSU ;P. Do I need to reflash everything again?
Click to expand...
Click to collapse
Updated my reply above.
rob43 said:
Updated my reply above.
Click to expand...
Click to collapse
Sorry, I'm confused!
After flashing the fastboot image, what do I do? The image came with Superuser pre-installed?
Related
I have create rooting method based on DooMLoRD method [ROOT] Rooting Toolkit for Xperia 2011 ICS [FW:.562]{LOCKED & UNLOCKED BOOTLOADERS} but have different approach.
special thanks to DooMLoRD
REQUIRED ROOTED DEVICE prior to update
How this method work?
1. create file /data/local.prop contain "ro.kernel.qemu=1" to enable root shell (this step must be done on ROOTED DEVICE)
2. update using Update Service/PC Companion/Flashtool without Factory Reset
3. after device updated,we should gained root shell that we use to push su binary and superuser.apk
Download : Xperia-ROOT.rev3.zip
Download : Xperia-ROOT.rev4.zip
Including autoinstall Stericson Busybox 1.20.1 and nAa CWM Recovery 5.0.2.7
extract Xperia-ROOT.rev3.zip to any folder,so you got something like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Another great tutorial made by DragonClawsAreSharp can be found at
[Tutorial]Root.Xperia 4.0.4 ROM | 4.1.B.0.431
STEP :
1. run 01-local-prop.cmd to create /data/local.prop (enable android emulator hack)
2. power off device and update your device WITHOUT FACTORY RESET
Update Service
select Update (recommended)
Flashtool
UNMARK WIPE DATA
after your device updated
on 1st boot your device will reboot once
on 2nd boot it will boot normally
if you got bootloop run 02-push-root-files.cmd right away
until it finished wait for 1 or 2 reboot
if you still got bootloop you need to reflash rootable firmware(zergrush method) then try again
3. run 02-push-root-files.cmd to push su binary and superuser.apk
4. your device will automatically reboot
5. enjoy your new rooted firmware
this method tested on :
1. Arc S ROOTED GB 4.0.2.A.0.42 updated to ICS 4.0.4
2. Ray ROOTED ICS 4.0.3 updated to ICS 4.0.4
3. Active ROOTED GB 4.0.2.A.0.42 updated to GB 4.0.2.A.0.62
tested by user:
1. SK17i ROOTED GB 4.0.2.A.0.58 updated to GB 4.0.2.A.0.62 by Bolussimo
2. Rooted SK17i FW 4.1.B.0.431 by draco_ag
3. LWW WT19i Rooted GB 4.0.2.A.0.58 updated to ICS 4.0.4 by alness1213
4. SK17i ROOTED GB 4.0.2.A.0.42 updated to ICS 4.0.4 by DragonClawsAreSharp
Dis method can only work on non-latest firmware.... lets say am using .62 firmware which is not rooted, dat means i need to downgrade to lower version & ROOT it to use dis!!!
Nice piece of work brov...
whalesplaho said:
Dis method can only work on non-latest firmware.... lets say am using .62 firmware which is not rooted, dat means i need to downgrade to lower version & ROOT it to use dis!!!
Nice piece of work brov...
Click to expand...
Click to collapse
Yup,that's it bro.
As we know zergrush exploit doesn't works on FW starting .62 and above.
we just need any firmware that can be rooted using zergrush method then use this tool before and after upgrade to gain updated and rooted firmware.
I have tested this method on my Xperia Active running on ROOTED FW .42(rooted using zergrush method) use this tool before and after update to gain rooted FW .62
When doing update you MUST NOT do factory reset.
Wipe Data will deleted any add file & make tha phone return to factory reset right....?
whalesplaho said:
Wipe Data will deleted any add file & make tha phone return to factory reset right....?
Click to expand...
Click to collapse
it will clean all data from your phone,all user installed app and setting will gone.
in rooting process DO NOT factory reset.if you wish to factory reset you can do it after running the tool after 1st boot (step 3 - 5 )
And you really did it, bro! I will use your method, root my .62 fw and get ready for my rooted ICS. Thank you again!
Sent from my SK17a using xda premium
A little question...
Just add these line " ro.kernel.qemu=1" to already exist /data/local.prop right???
Or make another /data/local.prop???
Till-Kruspe said:
A little question...
Just add these line " ro.kernel.qemu=1" to already exist /data/local.prop right???
Or make another /data/local.prop???
Click to expand...
Click to collapse
when running 01-local-prop.cmd
it will overwrite /data/local.prop
so /data/local.prop only contain "ro.kernel.qemu=1"
you need to run 01-local-prop.cmd just before you update your device.
puppet13th said:
when running 01-local-prop.cmd
it will overwrite /data/local.prop
so /data/local.prop only contain "ro.kernel.qemu=1"
you need to run 01-local-prop.cmd just before you update your device.
Click to expand...
Click to collapse
I got bootloop...
Till-Kruspe said:
I got bootloop...
Click to expand...
Click to collapse
did you read this?
puppet13th said:
you need to run 01-local-prop.cmd just before you update your device.
Click to expand...
Click to collapse
puppet13th said:
did you read this?
Click to expand...
Click to collapse
yes...I have done all the step...but got bootloop...
Till-Kruspe said:
yes...I have done all the step...but got bootloop...
Click to expand...
Click to collapse
can you tell me what have you done step by step?
edit :
if you have updated your device and run "02-push-root-files.cmd"
it's look like the script failed to remove /data/local.prop
from 02-push-root-files.sh :
Code:
adb shell rm [COLOR="Red"]-f[/COLOR] /data/local.prop
builtin rm command syntax on GB build :
Code:
rm [-rR] <target>
workaround :
open env.cmd
type these command
Code:
adb shell rm /data/local.prop
puppet13th said:
can you tell me what have you done step by step?
edit :
if you have updated your device and run "02-push-root-files.cmd"
it's look like the script failed to remove /data/local.prop
from 02-push-root-files.sh :
Code:
adb shell rm [COLOR="Red"]-f[/COLOR] /data/local.prop
builtin rm command syntax on GB build :
Code:
rm [-rR] <target>
workaround :
open env.cmd
type these command
Code:
adb shell rm /data/local.prop
Click to expand...
Click to collapse
my phone is rooted 2.3.4 with cwm, FW .58, lock bootloader...
First I run 01-local-prop...but on my phone it doesn't ask for superuser permission...in the 01-local-prop it say complete (done replacing new local.prop)...I have checked /data/local.prop (open with text editor) it has this "ro.kernel.qemu=1"
Then I open up PCC and update my phone to FW .62...Bla bla bla...finished...restart phone.....then bootloop...
what to do now...this is my only phone...please help me...
Till-Kruspe said:
my phone is rooted 2.3.4 with cwm, FW .58, lock bootloader...
First I run 01-local-prop...but on my phone it doesn't ask for superuser permission...in the 01-local-prop it say complete (done replacing new local.prop)...I have checked /data/local.prop (open with text editor) it has this "ro.kernel.qemu=1"
Then I open up PCC and update my phone to FW .62...Bla bla bla...finished...restart phone.....then bootloop...
what to do now...this is my only phone...please help me...
Click to expand...
Click to collapse
if you have FW. 58 or erlier ftf flash it with flashtool DO NOT UNMARK wipe data.
then root it using zergrush method.
try again from step 1
edit :
it's look like you got bootloop because your data partition was full.
now i got bootloop downgraded to fw. 42 without factory reset.i only got 50mb free before flashing.
my rom was odexed before,so 50mb was not enought to hold dalvik-cache from framework and system app
updated 1st post
puppet13th said:
updated 1st post
Click to expand...
Click to collapse
Hi puppet,
How come he was not asked by Superuser for root permission?
Is it because he had allowed adb with root rights earlier and had checked "always allow"? (may be).
Or there can be some other reasons?
Thanks,
Rick
Sent from my SK17i using XDA
Till-Kruspe said:
my phone is rooted 2.3.4 with cwm, FW .58, lock bootloader...
First I run 01-local-prop...but on my phone it doesn't ask for superuser permission...in the 01-local-prop it say complete (done replacing new local.prop)...I have checked /data/local.prop (open with text editor) it has this "ro.kernel.qemu=1"
Then I open up PCC and update my phone to FW .62...Bla bla bla...finished...restart phone.....then bootloop...
what to do now...this is my only phone...please help me...
Click to expand...
Click to collapse
now i hit the bull eye
/data/local.prop : ro.kernel.qemu=1 --> cause system instability that cause bootloop if data partition was full
download Xperia-ROOT.rev3.zip from 1st post and run 02-push-root-files.cmd it will wait for device before reboot(bootloop).after /data/local.prop(ro.kernel.qemu=1) gone,it will boot normally
when it reach home screen you need to make more free space on /data partition
DragonClawsAreSharp said:
Hi puppet,
How come he was not asked by Superuser for root permission?
Is it because he had allowed adb with root rights earlier and had checked "always allow"? (may be).
Or there can be some other reasons?
Thanks,
Rick
Sent from my SK17i using XDA
Click to expand...
Click to collapse
it's look like superuser automatically allow su access from adb shell
i just check from superuser app,there is no shell in apps list.
if i remember correctly old superuser doesn't automatically allow su access from adb shell,it will prompt su access and if allowed or denied it will be added to app list as unknown
puppet13th said:
it's look like superuser automatically allow su access from adb shell
i just check from superuser app,there is no shell in apps list.
if i remember correctly old superuser doesn't automatically allow su access from adb shell,it will prompt su access and if allowed or denied it will be added to app list as unknown
Click to expand...
Click to collapse
Okay. Got it.
So if he had connected his dead cell to the pc and run the 2nd bathc file, things would become alright for him right?
Sent from my SK17i using XDA
DragonClawsAreSharp said:
Okay. Got it.
So if he had connected his dead cell to the pc and run the 2nd bathc file, things would become alright for him right?
Sent from my SK17i using XDA
Click to expand...
Click to collapse
02-push-root-files.cmd doesn't run on su access because of /data/local.prop (ro.kernel.qemu=1)
when ro.kernel.qemu=1 in effect we automatically got root shell
so when we start adb shell we got # instead of $
# = root user
$ = normal user
Hi i have rooted my galaxy tab 10.1 wifi only, after i have installed the ClockworkMod Recovery'
and after the rom [ROM][ICS] JellyBeanRom ICS v5 [P7500][P7510][13.08.2012] - xda-developers.
All seems ok i have superuser and superSu .
I have tried to use some apps for root but dont work any such as Titanium backup root explorer etc
I have update superuser and superSu by play and by flash not resolved .
Root Checker done me this:
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - version 0.96 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/xbin/su:
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Standard Location
Check Command: ls -l /system/bin/su:
Result: lrwxrwxrwx root root 2019-08-31 03:30 su -> ../xbin/su
Analysis: File: su is a symbolic link pointing to another file: ../xbin/su
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: root user - ro.secure=0
Results provided on your GT-P7510 device
please can you help me?
Try uninstalling one of the two SU apps...you should only need one to my understanding. Then reboot right after.
If that doesn't work you may have to unroot completely and start over.
Hi dear friend...
I had the same problem(likely) with some APPs in ICS...please do the following:
First if you are running ICS,disable(or uninstall) superuser(supersu is sufficient),then open supersu and look at your list of APPs in the first page,if the # mark in front of some APPs are green,then they have root access.if not, tap on them,in the window that appears,in the root access drop down list choose "Grant"...if even this didn't solve the issue please tell us to send you a working root package...
djmatt604 said:
Try uninstalling one of the two SU apps...you should only need one to my understanding. Then reboot right after.
If that doesn't work you may have to unroot completely and start over.
Click to expand...
Click to collapse
I have tried this but is the same!
arashtarafar said:
Hi dear friend...
I had the same problem(likely) with some APPs in ICS...please do the following:
First if you are running ICS,disable(or uninstall) superuser(supersu is sufficient),then open supersu and look at your list of APPs in the first page,if the # mark in front of some APPs are green,then they have root access.if not, tap on them,in the window that appears,in the root access drop down list choose "Grant"...if even this didn't solve the issue please tell us to send you a working root package...
Click to expand...
Click to collapse
Hi tank you for help me i tried this but superSu dont work : exe SU not present and uperSu cant instal this is a problem!
pls any idea?
skyone75 said:
i tried this but superSu dont work : exe SU not present and uperSu cant instal this is a problem!
pls any idea?
Click to expand...
Click to collapse
Yes...you must get su and supersu.I've put it for you in the attachment...
Note that installing superuser or supersu only doesn't mean rooting...
All the credits of this package go to Max Lee from Zedomax...
arashtarafar said:
Yes...you must get su and supersu.I've put it for you in the attachment...
Note that installing superuser or supersu only doesn't mean rooting...
All the credits of this package go to Max Lee from Zedomax...
Click to expand...
Click to collapse
Tank you i tried to install this file now i have Clocworkmod recovery v 5.8.3.1 and result is :
Installing: /sdcard/GalaxytabHacks.com_superuser.zip
Finding update package...
Opening update package...
Installing update....
Install from sdcard complete
but i have the same problem!
You think is better unroot?
It sounds like you've tried everything else. I would back up stuff you need, unroot with stock firmware and start over with just one option. You may choose to skip manually rooting altogether and just flash a rooted ROM. Good luck!
The first time you flash this you must open supersu,a message says that the su binary is outdated,press OK,after some seconds connected to the internet,you see success message,reboot(just optional) znd execute the app you want to gain root access,if it fails(no prompt appeared)don't get disappointed,close the APP,launch supersu,see the # mark in front of the APP's name,tap on it,from the "root access" select "Grant"...
Edit:if you want to flash a ROM then have a look at Jelly Bean ICS in the dev forum...it's ICS and comes with root+many other goodies...
arashtarafar said:
Yes...you must get su and supersu.I've put it for you in the attachment...
Note that installing superuser or supersu only doesn't mean rooting...
All the credits of this package go to Max Lee from Zedomax...
Click to expand...
Click to collapse
arashtarafar said:
The first time you flash this you must open supersu,a message says that the su binary is outdated,press OK,after some seconds connected to the internet,you see success message,reboot(just optional) znd execute the app you want to gain root access,if it fails(no prompt appeared)don't get disappointed,close the APP,launch supersu,see the # mark in front of the APP's name,tap on it,from the "root access" select "Grant"...
Edit:if you want to flash a ROM then have a look at Jelly Bean ICS in the dev forum...it's ICS and comes with root+many other goodies...
Click to expand...
Click to collapse
Ok i try to unroot , need only flash a firmware samsung in download mode with odin?
wich firmware ? hc 3.2 or ics i have tab 7510 wifi only buy in switzerland with italian language
Is there not an Italian ICS? If not try the UK firmware with IT support.
djmatt604 said:
Is there not an Italian ICS? If not try the UK firmware with IT support.
Click to expand...
Click to collapse
But is better honey com 3.2 or ics for unroot?
Tanks
ICS is faster but lacks flash player...but it doesn't harm too much...
arashtarafar said:
ICS is faster but lacks flash player...but it doesn't harm too much...
Click to expand...
Click to collapse
i have unrooted and now i have installed ROM][ICS] JellyBeanRom ICS v5 [P7500][P7510][03.09.2012] v6
Itink the problem was then i caming by Honeycomb:
Instructions (IMPORTANT!):
1. Coming from stock ICS.
If you don't have any recovery then flash it (for example TWRP). Then boot into recovery, make a full wipe and flash my rom.
2. Coming from Honeycomb or any other custom like CM9/CM10/AOKP etc.
First you have to flash stock ICS, regarding which version of the Tab you have (3G/non 3G). Then you have to flash a custom recovery (for example TWRP), boot into it and make a full wipe. Finally flash my rom.
tanks for help bye .
That makes sense. You can run into problems with some ROMs depending on where you're coming from. I ran into problems with ICS ROMs in the beginning because of a bootloader issue...I flashed stock firmware to change my base and built ROMs from there as you're describing in Step 2.
Enjoy!
I have similar problem...
I own a T-Mobile 10.1 Tab, stock ICS... After flashing the stock ICS (i came from CM9) with odin, i flashed the CWM, and the applyed the "root.zip" file...
Booted and I saw that Superuser has been installed.
But I have no root access... The applications return that the root requisitation timed-out...
Anyone knows why? It shoud be quite simple....
Another thread has just been opened in the General area with someone asking the same question. The answers are there, friend...you just have to look for them Here it is again (assuming you are having the same problem and it sounds like you are) - it's because the version of Superuser the root.zip you're using drops into the system is not friends with ICS. Simply update Superuser to 3.1.3. Go Here , download Super 3.1.3-ARM-Signed.zip, drop it on your tablet's root, flash it from recovery and reboot. You should be good after that.
Tab 10.1 ICS flash player 11
arashtarafar said:
ICS is faster but lacks flash player...but it doesn't harm too much...
Click to expand...
Click to collapse
Since the adobe flash player 11 work for tab 10.1 HC 3.2 P7510, and some ICS early device.
adobe system no more certificate and support for ICS 4.0.x device.
So it SHOULD work for my Tab 10.1 P7510 ICS 4.0.4 too. and Yes. It is.
You no longer fine Flash player in Tablet PLAY store once you upgrade to ICS.
but you can find it in PC version PLAY store, then PUSH install from PC to Tablet P7510.
and YES, it work fine for my P7510 with ICS!
https://play.google.com/store/apps/details?id=com.adobe.flashplayer
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
or try download this APK to your tablet to install:
View attachment adobe.flashplayer11.apk
After install , open Flash player setting in your APPs, and setup options, then yoi are ready for any FLAH web object.
even web flash online games.
Anyone can use this ROM as his base for Custom ROMs without asking for permission as long as they include credits wherever it is posted
DEODEXED Stock Jelly Bean with Sense 4+ build 2.20.401.6 for Desire X
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
neXus PRIME for the JB TWRP Recovery
Chainfire for the SuperSU
doiutzu for testing the updater-script and other tests
And anyone directly / indirectly contribute for this ROM
DEODEXED stock ROM
hTC update build 2.20.401.6 (with Heartbleed fix)
Android Jelly Bean 4.1.1 (JRO03C)
Sense 4+
Kernel: 3.4.0-g2b619a5
rooted with SuperSU
Pre-installed Busybox
init.d support
Unlocked bootloader & Custom Recovery fixed for Jelly Bean
Recommended TWRP Recovery by neXus PRIME (http://forum.xda-developers.com/showpost.php?p=36714573&postcount=2)
For hboot 1.25.0002 (JB hboot)
Put the 2.20.401.6_Dodexed.zip on your sdcard
Make sure you already have the TWRP for JB hboot installed (NOT the stock recovery)
fastboot flash the attached boot.img for S-On DX (which comes with init.d feature)
Reboot to recovery
Make a full wipe is recommended but you can always try a dirty flash if your current ROM is stock (odex or deodexed)
Install the 2.20.401.6_Deodexed.zip as how you normally install a custom ROM
Reboot once completed and you are done
Old version 2.20.401.5_Deodexed.zip
http://sourceforge.net/projects/others/files/DX/2.20.401.5_Deodexed.zip/download
*DELETED*
*DELETED*
I still can't remove apps from system.I think something's wrong with my phone.
CrysiZ said:
I still can't remove apps from system.I think something's wrong with my phone.
Click to expand...
Click to collapse
Use Aroma File Manager. I've removed almost all google aps successfully. Rebooted several times and they do not appear again
CrysiZ said:
I still can't remove apps from system.I think something's wrong with my phone.
Click to expand...
Click to collapse
Which ROM ?
As mentioned before, you need a ROM with a properly installed busybox, root and init.d support.
See Part 1 : http://forum.xda-developers.com/showpost.php?p=40359126&postcount=250
See Part 2 & 3 : http://forum.xda-developers.com/showpost.php?p=40359148&postcount=251
And still can't edit build.prop
secthdaemon said:
And still can't edit build.prop
Click to expand...
Click to collapse
On my Deodexed ROM ?
ckpv5 said:
On my Deodexed ROM ?
Click to expand...
Click to collapse
Yes. Made changes via Build Prop Editor app, allowed changes via SuperSU, rebooted and no changes been applied
secthdaemon said:
Yes. Made changes via Build Prop Editor app, allowed changes via SuperSU, rebooted and no changes been applied
Click to expand...
Click to collapse
Here are the screenshots of build.prop editing that I made on a fresh installed deodexed ROM
I made changes to "ro.config.htc.enableCOTA=1" to "ro.config.htc.enableCOTA=0" with Root Explorer (you can see build.prop.bak is created after saving the changes.
And make a reboot, after reboot the "ro.config.htc.enableCOTA" still show 0 and the build.prop.bak is still there
Init.d seems not to be working
C:\Android>adb reboot recovery
C:\Android>adb push 12_test /system/etc/init.d/12_test
27 KB/s (57 bytes in 0.002s)
C:\Android>adb shell chmod 0755 /system/etc/init.d/12_test
C:\Android>adb reboot
C:\Android>adb shell cat /data/local/tmp/test.log
/system/bin/sh: cat: /data/local/tmp/test.log: No such file or directory
You can try this one.
hm...tried to to make changes with root explorer, rebooted, and all changes are gone and no bak file
secthdaemon said:
Init.d seems not to be working
C:\Android>adb reboot recovery
C:\Android>adb push 12_test /system/etc/init.d/12_test
27 KB/s (57 bytes in 0.002s)
C:\Android>adb shell chmod 0755 /system/etc/init.d/12_test
C:\Android>adb reboot
C:\Android>adb shell cat /data/local/tmp/test.log
/system/bin/sh: cat: /data/local/tmp/test.log: No such file or directory
You can try this one.
Click to expand...
Click to collapse
init.d is working fine... you can find zipalign.log in /data
BTW.. which boot.img that you are using ? the one that you posted ?
I gotta go now... will check later and update post #3 when I'm home.
ckpv5 said:
init.d is working fine... you can find zipalign.log in /data
BTW.. which boot.img that you are using ? the one that you posted ?
I gotta go now... will check later and update post #3 when I'm home.
Click to expand...
Click to collapse
Nope, I'm using your boot.img
secthdaemon said:
Nope, I'm using your boot.img
Click to expand...
Click to collapse
It works for me and others too that helped me.... so no idea why it is not working for you
So.. you don't have zipalign.log in /data folder ?
I'm gonna reflash your rom and boot.img just in case, I'll write about results.
secthdaemon said:
Use Aroma File Manager. I've removed almost all google aps successfully. Rebooted several times and they do not appear again
Click to expand...
Click to collapse
I can remove system apps and edit build.prop with aroma without disabled wp. So what? Why do i need this boot.img?
Sent from my HTC Desire X using xda premium
micu13 said:
I can remove system apps and edit build.prop with aroma without disabled wp. So what? Why do i need this boot.img?
Sent from my HTC Desire X using xda premium
Click to expand...
Click to collapse
You don't have to and you don't need the boot.img when you are comfortable doing all these stuff in recovery
Most people prefer to do things not in recovery as most people use recovery just to do nandroid backup/restore and flashing zips. That is why flar2 comes out with a workaround not only for DX but also on other devices such as
HTC One - http://forum.xda-developers.com/showthread.php?t=2235085 & http://forum.xda-developers.com/showthread.php?t=2233665
secthdaemon said:
I'm gonna reflash your rom and boot.img just in case, I'll write about results.
Click to expand...
Click to collapse
Let us know the result... as I'm afraid it is the JB hboot thing as I can't test it as I'm on ICS hboot.
If yes.. then we may need the kernel source then only Dev like neXusPRIME and atis112 can do their magic.
Ahh... how I wish I am on JB hboot then I can test a lot of things
ckpv5 said:
Which ROM ?
As mentioned before, you need a ROM with a properly installed busybox, root and init.d support.
See Part 1 : http://forum.xda-developers.com/showpost.php?p=40359126&postcount=250
See Part 2 & 3 : http://forum.xda-developers.com/showpost.php?p=40359148&postcount=251
Click to expand...
Click to collapse
Yes,on your deodex rom
This app allows you to use safestrap on certain devices running 4.4.4 and 5.0.
It basically runs
Code:
dd if=kernel.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
I am not responsible for anything that may happen to your device.
Post stack trace/logcat in this thread if it crashes.
If you get errors when updating, uninstall first.
Source code: https://github.com/benwaffle/AT-T-Note-3-Kernel-Flasher
AT&T Note 3 - NC2: this post
AT&T Galaxy S 4 - NC1
AT&T Galaxy S 5 - NCE
If you want to modify for your device, you can edit strings.xml
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What exactly does this do?
Flash the NC2 kernel image without Odin (to access SS). To get back to nj5 or nl1 you still need odin or a flashable zip.
Is there a flashable zip for us? And does that work via safe strap , flashing a kernel?
Installed this but it force closes everyone I open it
---------- Post added at 07:22 PM ---------- Previous post was at 07:22 PM ----------
Everytime*
Can you give me a stack trace? Via 'adb logcat' or if there's a report button, there should be a stack trace section at the very bottom
Never mind it worked somehow
If safestrap doesn't allow you to flash kernels then this is an even worse idea. Use at your own risk.
Almost certain it doesn't but mostly just because we've always been stuck with one and never had this kind of option.. But I'm pretty sure we can't flash any non signed kernels with our locked boot loader.
benwaffle said:
If safestrap doesn't allow you to flash kernels then this is an even worse idea. Use at your own risk.
Click to expand...
Click to collapse
Not safestrap it's bootloader preventing kernel lnstall
carl1961 said:
Not safestrap it's bootloader preventing kernel lnstall
Click to expand...
Click to collapse
no, it's the bootloader preventing custom kernels from actually booting
i can flash them though
benwaffle said:
no, it's the bootloader preventing custom kernels from actually booting
i can flash them though
Click to expand...
Click to collapse
we can flash modems with safestrap this. is your app? It would have been nice to have this to boot safestrap, and safestrap to install NJ5 kernel, then we would not need a computer all the time.
I will try and see if adb will install a kernel, if it fails then I would sat the bootloader is blocking any kernel
carl1961 said:
we can flash modems with safestrap this. is your app? It would have been nice to have this to boot safestrap, and safestrap to install NJ5 kernel, then we would not need a computer all the time.
I will try and see if adb will install a kernel, if it fails then I would sat the bootloader is blocking any kernel
Click to expand...
Click to collapse
I can make the app reboot to safestrap on flashing if you tell me how.
benwaffle said:
I can make the app reboot to safestrap on flashing if you tell me how.
Click to expand...
Click to collapse
@benwaffle you were absolutely right bootloader did not stop kernel install
putting nc2boot.img on internal sdcard then using adb
adb shell
su
dd if=/sdcard/nc2boot.img of=/dev/block/mmcblk0p14
reboot
it installed ns2 kernel and it booted to safestrap
here is the cmd windows readings
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\carl>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/sdcard/nc2boot.img of=/dev/block/mmcblk0p14
dd if=/sdcard/nc2boot.img of=/dev/block/mmcblk0p14
20624+1 records in
20624+1 records out
10559760 bytes transferred in 1.450 secs (7282593 bytes/sec)
[email protected]:/ # reboot
reboot
your NC2Flasher.apk does FC and then Supersu popped so app has root
rebooted phone and app still FC
let me know what I can do to help
carl1961 said:
@benwaffle you were absolutely right bootloader did not stop kernel install
putting nc2boot.img on internal sdcard then using adb
adb shell
su
dd if=/sdcard/nc2boot.img of=/dev/block/mmcblk0p14
reboot
it installed ns2 kernel and it booted to safestrap
here is the cmd windows readings
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\carl>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/sdcard/nc2boot.img of=/dev/block/mmcblk0p14
dd if=/sdcard/nc2boot.img of=/dev/block/mmcblk0p14
20624+1 records in
20624+1 records out
10559760 bytes transferred in 1.450 secs (7282593 bytes/sec)
[email protected]:/ # reboot
reboot
your NC2Flasher.apk does FC and then Supersu popped so app has root
rebooted phone and app still FC
let me know what I can do to help
Click to expand...
Click to collapse
obviously `dd` works, that's what my app does
can you give me a stack trace?
ok how do I grab that "stack trace?"
here is log cat
line 69
01-20 06:53:18.221: V/ApplicationPolicy(1048): isApplicationStateBlocked userId 0 pkgname com.uubmub.nc2flasher
line 208
01-20 06:53:19.461: E/AndroidRuntime(27406): FATAL EXCEPTION: AsyncTask #1
01-20 06:53:19.461: E/AndroidRuntime(27406): Process: com.uubmub.nc2flasher, PID: 27406
01-20 06:53:19.461: E/AndroidRuntime(27406): java.lang.RuntimeException: An error occured while executing doInBackground()
benwaffle said:
obviously `dd` works, that's what my app does
can you give me a stack trace?
Click to expand...
Click to collapse
Got a idea. When you get your app to work I want to try and put nc2 on slot 1 run slot 1 which is nc2 to use your app to install nh1 kernel then hopefully it boots stock slot. If that works then we have a way to do things without odin. I already know that nc2 runs fine on Nl1 firmware except for kernel.
All attempts to install kernel from NC2 running on safestrap failed, and installing NH1 4.4.4 kernel with odin did not ignore safestrap being on slot1, so I had to use safestrap to set phone on stock slot to boot 4.4.4 rom
so even if you did a app to install NH1 successfully ,being in slot1 won't allow 4.4.4 rom to boot
@benwaffle
Awesome app. Thank you so much for creating it for us. One of my biggest problems with 4.4.4 was having to be tied to a computer for anything i wanted to flash. This has made life so much better.
One suggestion I would have is...I wonder if it would be possible to have your reboot method automatically boot into SS instead of having to choose it. I know that @RErick had created an option for the ATTNote 3 that when reboot to recovery was chosen from the Power Options that it automatically went to SS. Maybe you and he can get that together.
I'll be working on that with my update
Should be trivial
It's finally here! Recovery for the Fire TV 2. This is based off of TWRP and the way versions will work is I will increment the last digit in the version as I make updates. So 3.0.0-1 is my first release based off of 3.0.0. The downloads will be numbered starting at v1, and at the bottom of the post it will explain what is contained within each version.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Installing it properly won't brick your Fire TV, but doing stupid things with it might.
Installing this requires root. If you are not rooted, please see my FireTV 2 Recovery Installer page.
Installation
You can copy the files to /sdcard, a USB storage device, or an sdcard. I will be using /sdcard in the instructions, but you can replace it with /storage/usbotg for USB or /storage/sdcard1 for an sdcard.
Copy the zip file to your destination.
Connect adb
Code:
adb connect IPADDRESS
Open an adb shell
Code:
adb shell
Run the zip file (replace vX with the actual version you downloaded). This will automatically run su, so make sure to accept the prompt if necessary.
Code:
sh /sdcard/firetv2_recovery_vX.zip
Reboot
Upgrade
You may repeat this to upgrade to a newer version, or you can install an updated pre-rooted rom, as I will be uploading new versions of those with every version of recovery.
Notes
This includes bootmenu. For everyone that loved the old FireTV 1 bootmenu with Comic Sans, I'm sorry to disappoint you, but the Comic Sans is gone. When the FireTV boots, it will present you with the bootmenu where you can leave it alone and it will boot normally or you can select recovery and it will boot in to recovery. You do need a USB keyboard to interact with the bootmenu. To force it to boot in to Recovery, you can create a file /cache/bootmenu_recovery.
DHCP for Ethernet is enabled, and if there is enough demand I may add in wifi at some point. The IP address should show up in the top left corner.
USB storage, USB keyboard/mice, and sdcards should all work. Hotplugging works, so you should be able to plug and unplug devices as needed.
You can use a USB keyboard, mouse, or the mouse emulator to interact with it. To use a keyboard, you can use the arrow keys to move the cursor and the enter key to select buttons. Sliders don't require sliding, so you can just hit enter/click on them. To use the mouse emulator, use adb shell and then run the program mouse and follow the instructions.
ROMs
Recovery must be included in all ROMs. If you want to develop a ROM, please contact me about including recovery in it.
Kernels
The bootloader is locked and you cannot flash kernels. If you do attempt to flash a kernel, you will brick it.
Installing zips
You can push zips to /sdcard, put it on a USB storage, put it on an sdcard, or use adb sideload. Do note you need adb version 1.0.32 to use adb sideload.
Stuck in a loop?
If you cannot boot normally and keep going back to the bootmenu, wipe Cache from Wipe -> Advanced Wipe.
If that doesn't work, ensure Cache is not mounted from in the 'Mount' menu and run this from an adb shell:
Code:
mke2fs /dev/block/platform/mtk-msdc.0/by-name/cache
Source Code
You can find the source code here:
https://github.com/androidrbox/sloane-2ndinit
https://github.com/androidrbox/android_bootable_recovery
WARNINGS
It is extremely important you never reboot after a failure. This will most likely lead to a brick. If recovery is hung, you can use adb shell to run
Code:
killall recovery
to restart it
It is also extremely important to never reboot after wiping /system.
If you wind up bricking, you must use the Unbrick Image to unbrick.
Finally, thanks to everyone who has donated to me and those that helped to get me my FireTV 2.
Changelog and Downloads:
April 8, 2016 - v6 (md5sum: 79c1a3efbac86618fa2cdbb4901fbd77)
This should prevent auto flashing amazon updates.
This includes 2ndinit version dee776 and TWRP version 3.0.0-5.
February 14, 2016 - v5 (md5sum: 16c957c86f1f61160e14a55819610707)
This should fix the problems certain keyboard were having in recovery.
This includes 2ndinit version dee776 and TWRP version 3.0.0-4.
February 12, 2016 - v4 (md5sum: 15c6d375607839cac4b186a2b68b8b0d)
This includes 2ndinit version 743aa4 and TWRP version 3.0.0-3.
These are just changes related to the unbricking image. No other functional changes.
February 8, 2016 - v3 (md5sum: b39a4dbe0c19080a97f602f37fda63ec)
This includes an updated script. You can now just run the zip instead of needing the zip and the script.
This includes TWRP 3.0.0-2.
Added a reboot recovery option in addition to reboot system. Now reboot system will reboot straight in to Android. Reboot recovery will reboot to the bootmenu.
Fixed restoring backups.
This includes the same version of 2ndinit.
February 7, 2016 - v2 (md5sum: 762621104d158d7ce4010bea725f7181)
This includes an automated script.
This has the same versions of 2ndinit and recovery as v1.
February 6, 2016 - v1 (md5sum: 7be673dd24489080eacdd0ad00feda51)
This comes with 2ndinit version fe3362 and recovery version 3.0.0-1
Awesome work!
Will try immediately! Thanks for posting this on weekend
Thankyou Rbox, i just saw this & its put a smile on my face. Just one question do you need to reblock the updates after recovery & root have been installed? Thanks
deanr1977 said:
Thankyou Rbox, i just saw this & its put a smile on my face. Just one question do you need to reblock the updates after recovery & root have been installed? Thanks
Click to expand...
Click to collapse
As long as you don't wipe data, updates remain blocked.
rbox said:
As long as you don't wipe data, updates remain blocked.
Click to expand...
Click to collapse
I downloaded both the zips from the Github, im already rooted on the previously rooted software & updates are blocked, im not sure if to wait for AFTV News to do a guide or not, im clued up but not to ADB or Terminal savey so i gonna look at the readme & see if i should try it tonight? I rooted with the video guide before & it was a breeze, i know it sounds easy but want to do it right. Can you give me a little more info on connecting the ADB or Terminal please if you arnt busy?
deanr1977 said:
I downloaded both the zips from the Github, im already rooted on the previously rooted software & updates are blocked, im not sure if to wait for AFTV News to do a guide or not, im clued up but not to ADB or Terminal savey so i gonna look at the readme & see if i should try it tonight? I rooted with the video guide before & it was a breeze, i know it sounds easy but want to do it right. Can you give me a little more info on connecting the ADB or Terminal please if you arnt busy?
Click to expand...
Click to collapse
If you don't want to deal with adb, use the installer.
rbox said:
If you don't want to deal with adb, use the installer.
Click to expand...
Click to collapse
Thanks mate, looking at this now. Will it delete any data on the system? Kodi, Amazon apps or External Sd card? Thanks in advance
deanr1977 said:
Thanks mate, looking at this now. Will it delete any data on the system? Kodi, Amazon apps or External Sd card? Thanks in advance
Click to expand...
Click to collapse
Installing recovery and roms does nothing to data.
rbox said:
It's finally here! Recovery for the Fire TV 2. This is based off of TWRP and the way versions will work is I will increment the last digit in the version as I make updates. So 3.0.0-1 is my first release based off of 3.0.0. The downloads will be numbered starting at v1, and at the bottom of the post it will explain what is contained within each version.
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Installing it properly won't brick your Fire TV, but doing stupid things with it might.
Installing this requires root. If you are not rooted, please see my FireTV 2 Recovery Installer page.
Installation
Copy the contents of the zip to /sdcard on your FireTV.
Remount /system as read-write
Code:
mount -o remount,rw /system
Make the /system/recovery directory
Code:
mkdir /system/recovery
Copy 2ndinitstub
Code:
cp /sdcard/2ndinitstub /system/bin/ext4_resize
Copy 2ndinit
Code:
cp /sdcard/2ndinit /system/recovery/
Copy the recovery ramdisk
Code:
cp /sdcard/ramdisk-recovery.cpio /system/recovery/
Remount /system as read-only
Code:
mount -o remount,ro /system
Upgrade
You may repeat this to upgrade, but it is easier to just install a new pre-rooted rom. Every update for recovery I will make a new rom.
Notes
This includes bootmenu. For everyone that loved the old FireTV 1 bootmenu with Comic Sans, I'm sorry to disappoint you, but the Comic Sans is gone. When the FireTV boots, it will present you with the bootmenu where you can leave it alone and it will boot normally or you can select recovery and it will boot in to recovery. You do need a USB keyboard to interact with the bootmenu. To force it to boot in to Recovery, you can create a file /cache/bootmenu_recovery.
DHCP for Ethernet is enabled, and if there is enough demand I may add in wifi at some point. The IP address should show up in the top left corner.
USB storage, USB keyboard/mice, and sdcards should all work. Hotplugging works, so you should be able to plug and unplug devices as needed.
You can use a USB keyboard, mouse, or the mouse emulator to interact with it. To use a keyboard, you can use the arrow keys to move the cursor and the enter key to select buttons. Sliders don't require sliding, so you can just hit enter/click on them. To use the mouse emulator, use adb shell and then run the program mouse and follow the instructions.
ROMs
Recovery must be included in all ROMs. If you want to develop a ROM, please contact me about including recovery in it.
Kernels
The bootloader is locked and you cannot flash kernels. If you do attempt to flash a kernel, you will brick it.
Installing zips
You can push zips to /sdcard, put it on a USB storage, put it on an sdcard, or use adb sideload. Do note you need adb version 1.0.32 to use adb sideload.
Source Code
You can find the source code here:
https://github.com/androidrbox/sloane-2ndinit
https://github.com/androidrbox/android_bootable_recovery
Finally, thanks to everyone who has donated to me and those that helped to get me my FireTV 2.
Changelog and Downloads:
Februrary 6, 2016 - v1 (md5sum: 7be673dd24489080eacdd0ad00feda51)
This comes with 2ndinit version fe3362 and recovery version 3.0.0-1
Click to expand...
Click to collapse
the commands are entered through adb correct......Also, once recovery is installed can I flash either of your pre-rooted roms or do I have to flash the version I'm currently on....i.e. if I'm on 5.0.4 I can only flash 5.0.4
thanks again for your great work!
dk1keith said:
the commands are entered through adb correct......Also, once recovery is installed can I flash either of your pre-rooted roms or do I have to flash the version I'm currently on....i.e. if I'm on 5.0.4 I can only flash 5.0.4
thanks again for your great work!
Click to expand...
Click to collapse
Yes adb shell. You can flash either version.
rbox said:
Yes adb shell. You can flash either version.
Click to expand...
Click to collapse
Awesome thanks rbox
Not working for me. everything is copied over and after reboot there is no menu. Amazon white logo for 5 seconds, than the colored logo and system is booted in less than 15 seconds.
aboshi said:
Not working for me. everything is copied over and after reboot there is no menu. Amazon white logo for 5 seconds, than the colored logo and system is booted in less than 15 seconds.
Click to expand...
Click to collapse
Same here. No boot menu. Reboot to recovery brings up the stock recovery as well.
dk1keith said:
Awesome thanks rbox
Click to expand...
Click to collapse
first command: mount -o remount,rw /system
in adb shell returns a mountermission denied
aboshi said:
Not working for me. everything is copied over and after reboot there is no menu. Amazon white logo for 5 seconds, than the colored logo and system is booted in less than 15 seconds.
Click to expand...
Click to collapse
retyre said:
Same here. No boot menu. Reboot to recovery brings up the stock recovery as well.
Click to expand...
Click to collapse
Both of you please run:
Code:
ls -lZ /system/bin/ext4_resize /system/recovery
dk1keith said:
first command: mount -o remount,rw /system
in adb shell returns a mountermission denied
Click to expand...
Click to collapse
You need to be root...
rbox said:
Both of you please run:
Code:
ls -lZ /system/bin/ext4_resize /system/recovery
You need to be root...
Click to expand...
Click to collapse
you mean by typing su?
dk1keith said:
you mean by typing su?
Click to expand...
Click to collapse
Yes, by typing su.
Code:
-rwxr-xr-x root shell u:object_r:system_file:s0 ext4_resize
-rw------- root root u:object_r:system_file:s0 2ndinit
-rw------- root root u:object_r:system_file:s0 ramdisk-recovery.cpio
aboshi said:
Code:
-rwxr-xr-x root shell u:object_r:system_file:s0 ext4_resize
-rw------- root root u:object_r:system_file:s0 2ndinit
-rw------- root root u:object_r:system_file:s0 ramdisk-recovery.cpio
Click to expand...
Click to collapse
Hrm... can you run
Code:
ls -l /system/bin/ext4_resize /system/recovery
also?