Related
I have sucessfully rooted my nook and I can load apks from dropbox, installers or via adb so I am a happy camper, all is good....
But I got greedy. The ComicViewer doesn't work well without menu keys so I decided to install softkeys.apk and that is where the trouble started, something is amiss.
I am not an expert here, just a novice, so forgive my patchwork explanation.
Here's what I know and what I did, maybe someone can spot my error?
I can fully access adb.
I remember installing SuperUser and SU using the commands:
# adb shell
# cd /system/bin
# mount -o remount,rw /dev/block/mmcblk0p5 /system
# cat /data/local/su > su
# chmod 6755 su
# ls -l su
And all was fine, SuperUser shows up in the drawer. Then I tried installing SoftKeys and it never showed up or worked.
So I figured I fubared the SuperUser install somehow or have an old version of SU or SuperUser. So I downloaded the most recent versions and went to uninstall the original with uninstall utilities and it's not listed in any of them, so I tried using adb (adb shell ls /data/app) and it's still not in the list.
I even reset the Nook to factory and rooted again with nooter and when I tried to install SuperUser again (downloaded the latest version here on the forum) it said "Install Failed already exists!"
So I cannot uninstall the SuperUser or overwrite it with a newer version, and a factory reset doesn't fix it??
I cannot use any root utilities like SuperUser or z4root, SuperUser has all blank screens and I cannot update it and 4zroot just doesn't seem to do anything but reboot the nook.
Titanium Backup says I don't have root access and other utilities say the same thing,
I can mount system partition as read-write
> adb shell
# mount -o remount rw /system
# exit
That works...
So I tried the commands again to install SuperUser and SU and when I try to install SU
# cd /system/bin
# mount -o remount,rw /dev/block/mmcblk0p5 /system
are OK but when I do:
# cat /data/local/su > su
I get:
Cannot create su: remote access failed
I have also tried a few other things that seem to be available to root users and all come back with write or access errors.
What could I be doing wrong?
Note: I also tried to do a full wipe by using that Power and Volume Down and nothing happens...
Power the nook on and off immediately 8 times until it does a full factory reset. When I've done the Power+VolUp+Nook button reset it doesn't always seem to do a FULL reset. When the nook fails to boot 8 times it does a different reset that takes a good deal longer and (at least in my experience) seems to be the real deal.
z4root will work and install superuser for you.
mhoepfin said:
z4root will work and install superuser for you.
Click to expand...
Click to collapse
I have already mentioned that that did not work, but thanks for the suggestion anyway.
Ok, something VERY weird is going on.
I have reset it to factory twice
Each time I did it by powering on and off 8 times in a row
The first time after it indicated it was updating th software, it went into a stuck at NookColor Logo boot loop again.
The second time I left in the nooter microSD card and it booted properly.
But it booted to a "clean" system with all my programs.
All my settings and data was gone, but all my apks were still installed.
So what exactly did it reset? Just data?
I tried to get it to flash both ways, the quick (power/home/volume) and now twice with the 8 power cycles. Neither reset the Nook entirely.
Am I screwed?
I want to go back to factory to fix this thing
EDIT:
Looks like I am locked out of the system entirely, none of my apps work, some of them come back and say no write access.
I cannot do an app listing like:
adb shell ls /data/app
I get:
opendir failed, Permission denied
I can't do a simple mount
mount -o remount rw /system
I get:
mount: operation not permitted
This should help you with what type of reset you want to do. I think you should do another 8 power on/off reset followed by a power-up-home reset to get it fully reset.
axe2 said:
This should help you with what type of reset you want to do. I think you should do another 8 power on/off reset followed by a power-up-home reset to get it fully reset.
Click to expand...
Click to collapse
I tried that...
Now it's completely dead.
Won't power up at all.
It had plenty of battery life left and plugging it in will not boot it either...
gormly said:
I tried that...
Now it's completely dead.
Won't power up at all.
It had plenty of battery life left and plugging it in will not boot it either...
Click to expand...
Click to collapse
Well that's a bummer! Maybe something went wrong in one of the resets. Did they seem to complete? If it's not a hardware problem you should still be able to revive it via nooter. I would suggest PMing pokey9000 and see if he can walk you through a recovery. You might be the first near brick that requires running some of the recovery commands by hand. I think Pokey9000 knows the most about that.
axe2 said:
Well that's a bummer! Maybe something went wrong in one of the resets. Did they seem to complete? If it's not a hardware problem you should still be able to revive it via nooter. .
Click to expand...
Click to collapse
Yea, but it won't respond to anything, it won't boot meaning no power at all.
It's just completely black screen.
Nothing I do does anything.
gormly said:
Yea, but it won't respond to anything, it won't boot meaning no power at all.
It's just completely black screen.
Nothing I do does anything.
Click to expand...
Click to collapse
Whatever you do make sure the battery is getting charged somehow.. Try to leave it plugged into the wall or in a usb. Does the computer see the device when plugged in? HAve you tried to remove the SD card from the NC while powering up?
norkoastal said:
Whatever you do make sure the battery is getting charged somehow.. Try to leave it plugged into the wall or in a usb. Does the computer see the device when plugged in? HAve you tried to remove the SD card from the NC while powering up?
Click to expand...
Click to collapse
Yep tried all those things...very frustrating afternoon so far
However...I did get it to boot.. here is how:
Press and hold the power button while inserting the USB charger connected to a computer, continue to hold (I think it was 10 seconds or so).
I remember doing this to reset a device a long time ago, not sure what.
But it worked, not only that but I was able to do a pwer/up/home rest and this time it completely wiped the nook. It looks like I am back to factory!
YES!!
Thanks for alll the help and suggestions guys. Hopefully this struggle will help someone else in the future.
gormly said:
But it worked, not only that but I was able to do a pwer/up/home rest and this time it completely wiped the nook. It looks like I am back to factory!
YES!!
Thanks for alll the help and suggestions guys. Hopefully this struggle will help someone else in the future.
Click to expand...
Click to collapse
OK. This time around, do this:
(1) nooter
(2) use ADB to enable Non-Market Apps
(3) use ADB to enable multitouch
(4) Use ADB to push z4root over to the NC
(5) Run z4root and do a full-root (whatever is NOT the "temp" option)
(6) Use ADB to install Astro
(7) Use ADB or Astro to install a market
(8) Install the rest of your apps however you choose.
johnopsec said:
OK. This time around, do this:
(1) nooter
(2) use ADB to enable Non-Market Apps
(3) use ADB to enable multitouch
(4) Use ADB to push z4root over to the NC
(5) Run z4root and do a full-root (whatever is NOT the "temp" option)
(6) Use ADB to install Astro
(7) Use ADB or Astro to install a market
(8) Install the rest of your apps however you choose.
Click to expand...
Click to collapse
I did 1,2,3,6,7,8 and in place of 4/5 I used the most recent version of SU and SuperUser and all is good on my Nook! Not sure what happened before but it must have been a bad version of su or superuser. In any case, all seems fine, only Titanium doesn't work, all the rest of the root requesting apps work fine.
Thanks!
i used this method to boot:http://forum.xda-developers.com/showthread.php?t=920347
first it worked but i powered my nc off and since it didn't boot even if a kept the n button pressed,when i plug it on my computer adb dont detect it and the light is orange in charge and on computer
plz help me
thx
cwr
i boot from cwr and used this method:http://forum.xda-developers.com/showthread.php?t=931720
but still doesn't boot
need help
please someone help me i don't know what to do
Does your NC totally not boot at all? If you followed instruction in this thread - http://forum.xda-developers.com/showthread.php?t=931720 basically you are booting from SD. In this case, it has nothing to do what's on your internal flash. Check whether your SD card is created correctly.
it boots
it only boots from CWR
i had the same problem you have. i booted into CWM using the 1 gig sdimage, put the stock boot.img and system.img (from here - http://forum.xda-developers.com/showthread.php?t=919353) and did the dd commands from adb as shown there and my system booted normally.
i had a problem with the stock B&N usb cable where it didn't detect through adb at all. i had to use a different usb cable and it worked good.
i'll try
thx i'll try it tonight,it 1 pm in france^^,tell you if it worked
i don't have any other cable,i ll try to see at virgin tomorrow ,if you have an easier way let me know
the only other way i can think of doing that is to use nookie froyo and wireless adb. the problem with this method was when i tried doing that, i had no market, so i couldn't get wireless adb. i didn't feel like doing a workaround to getting that apk on there. problem with this method is i didn't know if the partitions would look the same or even show off the nook as i was working off the sdcard for froyo, so i wouldn't be able to say if this would actually work.
using the stock B&N cable, i noticed that the device would show in adb, but not online. so reading around i found out if u used a different usb cable it might work, so i did and it did work lol.
Simply flash my repartition boot file...
Sent from my HTC Desire using XDA App
samuelhalff said:
Simply flash my repartition boot file...
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
i looked at sam's method before as well, but didn't try it since i had luck with my usb cable connection for ADB usage. just dd-ing system and boot seemed to work for me and allowed me to keep it how i had it before (with all my previous apps installed). my partitions are probably still shorter though. flashing the zip looks like it'll restore everything to stock.
i bought a new cable,still don't work with adb ,windows detect it but it says it's two different devices and i cant change the driver,sooner nc booted under nookie froyo i don't know how,i'll try to boot again with 2.2 and work with adb from here
were u able to adb in the first place? i used this link http://forum.xda-developers.com/showthread.php?t=882751 to get it working. i also went through the nookdev site to get adb working. i was assuming it was my cable at least since it was tweaking (connecting/disconnecting) with the stock B&N usb cable.
still no adb even over nookie froyo,i try with your method
i have adb usb ,now i don't know how to do cause i only have a 2gb card so i only can put boot but not system on it,i don't know how to enter the command ,is it in adb shell?
i went through CWM and mounted system, data and sdcard. u use adb shell to get into the shell in the nook. then adb'd and
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
dd if=/sdcard/system.img of=/dev/block/mmcblk0p5
Click to expand...
Click to collapse
did that. i guess u can put one file and then another file after the first file is dd'd. i used adb to push those img files to the sdcard.
i try it,could you make me a kind of how to with steps and stuff plz?
petithor said:
i try it,could you make me a kind of how to with steps and stuff plz?
Click to expand...
Click to collapse
in your situation this is what i would do.
boot into cwm
mount system, boot and sdcard through the menus
without entering the shell (adb shell) type in: adb push <boot.img file location> /sdcard
now enter the nook's shell by type adb shell then enter
so you're in the nook's shell, and type "dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1"
delete the boot.img file so you have enough space on for the system image by typing "rm boot.img" (make sure you're in the root of sdcard)
type exit to exit the nook's shell
now you're going to push the system.img to the sdcard: adb push <system.img file location> /sdcard
enter into the nook's shell again (adb shell)
type in "dd if=/sdcard/system.img of=/dev/block/mmcblk0p5"
once that is done reboot and everything should work just like before you ran that other script.
this is pretty much what i did. i'm on windows 7 x64 so i just dragged and dropped the files into the command prompt to get the file locations.
again: http://forum.xda-developers.com/showthread.php?t=919353 for more reference of what i was doing.
it worked thx very much ,you are a god besides the humans
not sure if anyone has seen this but i found it posted in another forum dated june 8 (retail launch date) and no one has commented. i dont know enough to try this out my self but looks promising.
Galaxy Tab Rooting Instructions - ADB Method
These instructions provided me with a permanent root workaround when SuperOneClick, run within Windows 7, repeatedly hung "waiting for device". SuperOneClick elegantly automates the ADB method, but for some reason the ADB command "adb devices" fails to recognize an attached Galaxy Tab when run from within Windows 7. The larger problem seems to be that in some situations like mine, ADB simply does not run correctly from within Windows 7, even when one right-clicks on SuperOneClick.exe and runs it as Administrator. Perhaps SuperOneClick would work OK on Windows XP, but I have no idea.
The procedure below uses components from SuperOneClick but runs the ADB server and commands from within Linux. In this environment the ADB command "adb devices" correctly reports the attached Galaxy Tab, and other ADB commands work correctly as well. To obtain the needed SuperOneClick components, download SuperOneClickv1.9.1.zip to Linux and unzip it there. The SuperOneClick.exe (which is a Windows executable) will be ignored, but other files (see below) will be pushed to the Galaxy Tab during the rooting process.
I'm indebted to authors at http://pastebin.com/i234U96k and http://rootingdroid.com/ for the hack below. Note that there is a modification to require no dependence on a "cp" command at the ADB shell prompt. For some reason "cp" is missing in /system/bin on my Galaxy Tab.
As always, attempt using this procedure at your own risk. Be specifically aware that you may not be able to "unroot" your Galaxy Tab after using this procedure--ever! This procedure doesn't back anything up from the unrooted device, so if "unrooting" it requires restoring something from such a backup, I'm (and you're) stuck with a permanently rooted device. This condition may interfere with your receiving certain updates or downloading DRM content in the future.
1) Download and install TitaniumBackup and SuperUser onto your Galaxy Tab from the Android Market. Note that SuperUser may not be necessary since there are sources for this app below. I'm including it at this step because I had previously installed it prior to the steps below.
2) Download and unzip SuperOneClickv1.9.1 into some Linux folder of your choice. You can get it at http://shortfuse.org/?page_id=2 near the bottom of the page.
3) Install Android SDK for Linux x86 into your home directory on your Linux box. You can get it at http://developer.and.../sdk/index.html The ADB server will be located in ~/android-sdk-linux_x86/platform-tools.
4) For convenience, copy from the SuperOneClickv1.9.1 folder above the files Superuser.apk, psneuter, su-v2 as su, and busybox into ~/android-sdk-linux_x86/platform-tools. Note that SuperOneClick seems to provide three different versions of su (su-v1, su-v2, su-v3). The su-v2 version worked for me. Performing this copy simplifies entering the "adb" commands below.
Note that there is an alternative source for Superuser.apk and su at http://www.rootingdroid.com at the "Download" link in Step 2.
5) Enter the Linux directory containing the ADB server with the command
cd ~/android-sdk-linux_x86/platform-tools
6) Plug in the Galaxy Tab to the computer, with USB debugging turned on.
7) Test ADB recognition of the Galaxy Tab with the command
./adb devices
You should see messages indicating the ADB server is starting, and then a message similar to
List of devices attached
100020497aab device
If no device is listed, begin investigating by ensuring that USB debugging is turned on. In my experience, when the "adb devices" command is entered from within Windows 7, no device is listed. Again, I think this is related to the "waiting for device" hang when SuperOneClick is run in Windows 7.
8) Push psneuter to the Galaxy Tab with the command
./adb push psneuter /data/local/tmp
9) Make psneuter executable with the command
./adb shell chmod 777 /data/local/tmp/psneuter
10) Run the psneuter exploit with the command
./adb shell /data/local/tmp/psneuter
The message "property service neutered." should appear indicating success.
11) Test for successful rooting with the command
./adb shell
The # prompt should result.
12) Remount the /system volume rw (by default it's ro), so that files can be pushed to /system, with the command
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
13) Return to the Linux computer command line with the command
exit
14) Push Superuser.apk, su and busybox to the /system volume with the commands
./adb push Superuser.apk /system/app/Superuser.apk
./adb push su /system/bin/su
./adb push busybox /system/bin/busybox
15) Make su executable with the command
chmod 4755 /system/bin/su
16) Remount the /system volume as ro with the command
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
17) Verify that su works with the command
su
You should see the # prompt; type the command
exit
and you should see the # prompt again.
18) Power the Tab down and then power it back up. Run TitaniumBackup, which will ask for root privileges that (hopefully) will be granted. It's a good idea to backup your Galaxy Tab before using your new root privileges!
i take no credit for this. all credit to feral urchin for which ever device this works for retail or I/0 but something tells me its for retail because I/o has had an easier way to root for a while..
I am running windows vista ultimate. Should I try this and see if I have the same bug that has been reported for Windows 7?
I have a new Tab 10.1 Retail picked up today.
give it a try let us know the results please
dsh897 said:
but for some reason the ADB command "adb devices" fails to recognize an attached Galaxy Tab when run from within Windows 7. The larger problem seems to be that in some situations like mine, ADB simply does not run correctly from within Windows 7, even when one right-clicks on SuperOneClick.exe and runs it as Administrator. Perhaps SuperOneClick would work OK on Windows XP, but I have no idea.
Click to expand...
Click to collapse
This might work. I am running Vista Ultimate x64 and my adb does recognize my retail Tab 10.1. See image below.
Now when I execute the command on step 10 I receive this error. . .
"Failed to set prot mask <Inappropriate ioctl for device>"
Suggestions?
4) For convenience, copy from the SuperOneClickv1.9.1 folder above the files Superuser.apk, psneuter, su-v2 as su, and busybox into ~/android-sdk-linux_x86/platform-tools. Note that SuperOneClick seems to provide three different versions of su (su-v1, su-v2, su-v3). The su-v2 version worked for me. Performing this copy simplifies entering the "adb" commands below.
did you put everything in the right directory?
where are you a firefighter? im a medic finishing up fire academy in 2 weeks in sofla
im attempting another angle right now..
i got odin working with my galaxy very quickly i backing up now. but i have a funny idea that i can flash the i/o unlocked bootloader with odin 3 unlock it then gain root and then update everything and then flash clock work.
dsh897 said:
4) For convenience, copy from the SuperOneClickv1.9.1 folder above the files Superuser.apk, psneuter, su-v2 as su, and busybox into ~/android-sdk-linux_x86/platform-tools. Note that SuperOneClick seems to provide three different versions of su (su-v1, su-v2, su-v3). The su-v2 version worked for me. Performing this copy simplifies entering the "adb" commands below.
did you put everything in the right directory?
where are you a firefighter? im a medic finishing up fire academy in 2 weeks in sofla
Click to expand...
Click to collapse
Yes I copied all those files to the correct directory. Only on my windows machine the it is /android-sdk/platform-tools/
I am a firefighter in the Charlotte, NC area. Just got off tour this morning.
Google searching that error as I type. I'll let you know the progress.
dsh897 said:
im attempting another angle right now..
i got odin working with my galaxy very quickly i backing up now. but i have a funny idea that i can flash the i/o unlocked bootloader with odin 3 unlock it then gain root and then update everything and then flash clock work.
Click to expand...
Click to collapse
I would like a backup image to odin if needed as well. How do I do this. I have a slight idea but i don't know the directories to pull?
i just disconnected my odin during dump im screwed at the mobile phone and computer! dunno how to get out
trying both volume rockers now. days downloading and flashing android box
just hold the power button for 10 seconds or just goto recovery mode and select reboot
that should get you back to honeycomb.
yea i got it with the power up then the recovery mode thx
How did you get adb to dump. i am running all sorts of commands and nothing works. some help would be greatly appreciated.
i was using odin3 to dump but it doesnt seem to be working correctly i think because its still locked. my next step is to flash the I/0 bootloader / system but im nervous now after it not correctly dumping (failure to write) it just creates a dummy file.
I am at work i will have to play with at home more. and have more resources
I am at an standstill as well. I don't know much more then what I have done thus far. I admittedly know nothing about Linux user privileges so I was never a help to begin with. The image below speaks for itself.
have you been able to flash anything with odin? i think if we can flash the stock i/o bootloader were set
Nope. Dont you think thats a little balzy without a retail dump to fall back on? Although, i could just exchange the device with best buy if something happens...
Sent from my GT-P7510 using XDA Premium App
haha why i havent done it yet. i cant see to get adb to recognize my tablet anymore i was making progress until now
is this method working ok to root a new retail SGT 10.1? thanks
i tried it and this what i got
"Failed to set prot mask (Inappropriate ioctl for device)"
any suggestions, thanks
neonflx said:
is this method working ok to root a new retail SGT 10.1? thanks
Click to expand...
Click to collapse
Nope. I am stuck. He is stuck. We are stuck.
any other methods to root a retail SGT, i took my XOOM back to Cotsco already
This is a step-by-step protocol (not necessarily a how-to, you still need to read the threads and be careful and kind of know what you do) for transforming a stock (with an activated account though) Kindle Fire HD 7" that came with 7.4.0 to a tablet with Hashcode's CyanogenMod 10.1 in the version of 07/26. No factory cable needed (you will need one, if you do anything wrong, though!). I used Windows 8.1 Pro Review.
I do not guarantee for anything!
If anybody wants to format this wall of unattractive text, they may do so
on your pc, download and install android sdk and follow https://www.youtube.com/watch?v=oaNM-lt_aHw
on your kindle, update to 7.4.3 by hitting SYNC on the menu on the top (it may take a while for the update to load, be patient, use wifi)
on your kindle, enable ADB in the settings
charge to 100% (I did only 80%, but try not to)
on your pc:
download the four files from STEP 2 from here http://forum.xda-developers.com/showthread.php?t=2128848
download and use http://www.winmd5.com/ to verify MD5 checksums, re-download files, if corrupted!
download Root_with_Restore_by_Bin4ry_v30 (not v31!) from the interwebs
download QemuRoot_v1.0.zip and the ADB_Drivers from here http://forum.xda-developers.com/showthread.php?t=1893838
/*
download KFFirstAide.zip from here http://forum.xda-developers.com/showthread.php?t=2096888
*/
for the adb drivers, under windows 8.1 Beta, follow https://www.youtube.com/watch?v=_srAqx5y2xE (two hints: the restart button is under recovery. press 7, when asked what to choose, to disable driver signature enforcement)
then, install and confirm that it is an unsigned driver
connect your kindle to a USB 2.0 port (not 3.0)
open the device manager on windows. check that there is an entry "Kindle Fire" with "Android Composite ADB Interface" below it
disconnect your kindle
follow https://www.youtube.com/watch?feature=player_embedded&v=CYDBoTtdvcE#at=127 from 2 minutes on (download the superuser-3.1.3-arm-signed.zip from the description)
once you get the permission denied, stop (when doing echo 'ro.kernel.qemu=1' > /data/local.prop). for a list of the commands, see here http://forum.xda-developers.com/showthread.php?t=1891939
run root-with-restore-v30 (RunMe.bat), use normal mode (1)
you may have to try two or three times, till it works. once it worked for me, the background and other pics were missing on the kindle (not displayed). this seems indicative of root access via the adb shell. the kindle turned extremely slow
then continue with the video. make sure that the shell shows a #, not a $. otherwise do root-with-restore again
when you get to the last step (adb install Superuser.apk) and fail, repeat root-with-restore. then, do not reboot, but instead immediately do "adb install Superuser.apk ". for me, it threw an error that it was already installed, so it may have worked the first time, but im not sure about that.
if your kindle, after rebooting, remains slow, repeat these steps:
adb shell mount -o remount,rw /system
adb push su /system/xbin/su
adb shell
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
rm /data/local.prop
exit
adb reboot
it should work then.
install ES File Explorer from the amazon store (it's for free). start, hit the button on the top left and click on 'root explorer'. if you do have root access, it will ask you to grant it to the app (and you should do so).
copy kfhd7-twrp-2.6.0.0-recovery.img and kfhd7-freedom-boot-7.4.3.img to the directory you're in with the windows command line. then do
adb push kfhd7-twrp-2.6.0.0-recovery.img /sdcard/kfhd7-twrp-2.6.0.0-recovery.img
adb push kfhd7-freedom-boot-7.4.3.img /sdcard/kfhd7-freedom-boot-7.4.3.img
to copy them to the /sdcard folder on your kindle
execute the commands from STEP 2 from here http://forum.xda-developers.com/showthread.php?t=2271909 (the 4th will take 1-2 minutes)
modify the last 3 commands before executing them. remove the '/' after '.img', also remove the '[' and the ']' around the backup path. again, the very last command (adb pull /sdcard/stock-system.img C:\KFHD7Backup) may take a while (for me, it was 3,5 min).
download fireflash11.apk from here http://forum.xda-developers.com/showthread.php?t=2168512
push (=copy) it to the /sdcard folder of your kindle (be sure it's in the folder your command shell is in):
adb push fireflash11.apk /sdcard/fireflash11.apk
on your kindle, open ES file explorer.
choose to analyze the sdcard. open fireflash11.apk. if an error occurs (blocked b/c it's not from the official amazon store), click on settings and allow installation of other apps (it's probably labeled differently, you get the idea). go back and click on the file again. install it. open it, click 'allow'.
next to the red warning, check 'flash [...].bin'!!!
for the boot partition (not flashed), choose the freedom-boot.img.
check 'apply stack override' below it.
for the recovery partition (not flashed), choose the twrp-recovery.img.
check 'disable recovery auto update'.
be sure that all of these are correct, unplug your kindle from your pc, then click on 'flash, install script'.
once it's done, turn your kindle off.
when you turn it on again, immediately hold down the volume up button (the leftmost button) and release it 3 seconds after the logo turns blue. you should now see TWRP. simply hit reboot and power off and then turn your kindle on normally.
download the unofficial cyanogenMod from here http://forum.xda-developers.com/showthread.php?t=2245335 (i used the version from 07/26, so I'll also explain how to setup the cam-fix2.zip).
download CAM-FIX2.ZIP from there as well, if you want to use 07/26.
be sure to check both md5 check sums!
(you may want to create a backup from within TWRP at this point. i missed it, but would have done so, had I thought of it beforehand. it's your call to make)
turn off your kindle. enter TWRP. hit 'wipe'. swipe to factory reset.
connect your kindle (while it's in twrp). copy the cm-[...].zip to /sdcard:
adb push cm-10.1-20130726-UNOFFICIAL-tate.zip /sdcard/cm-10.1-20130726-UNOFFICIAL-tate.zip
(this took 45 sec for me)
then, hit 'install' in the twrp menu, select the cm-[...].zip, swipe to confirm flash.
wipe cache/dalvik. swipe to wipe. back. reboot system. wait for 5 minutes (during that time, I only hit the power button once or twice to wake the kindle up, though that was likely unnecessary). reboot again afterwards.
turn your device off. reboot into twrp. push the cam-fix onto your kindle:
adb push cam-fix2.zip /sdcard/cam-fix2.zip
hit 'install'. select the cam-fix2.zip. swipe to confirm flash. reboot system (don't wipe). turn your kindle off.
download GApps (Play Store, Maps, etc.) from here http://goo.im/gapps (linked to by http://forum.xda-developers.com/showthread.php?t=2245335). choose the link in the CyanogenMod 10.1.x and Android 4.2.2 row.
boot your kindle into TWRP (holding the volume up button) again. push gapps to /sdcard:
adb push gapps-jb-20130301-signed.zip /sdcard/gapps-jb-20130301-signed.zip
(this took half a minute)
hit 'install'. select gapps.zip. swipe to confirm flash. reboot system.
unplug your device and enjoy CM10.1 on your Kindle Fire HD 7"! And don't forget to install the Kindle app!
Tabs I had open during the process and that may be helpful:
http://forum.xda-developers.com/showthread.php?t=2245335
http://forum.xda-developers.com/showthread.php?t=2271909
http://forum.xda-developers.com/showthread.php?t=2128848
http://forum.xda-developers.com/showthread.php?t=2168512
http://forum.xda-developers.com/showthread.php?t=1886460
http://forum.xda-developers.com/showthread.php?t=2096888
http://forum.xda-developers.com/showthread.php?t=1893838
http://forum.xda-developers.com/showthread.php?t=1891939
https://www.youtube.com/watch?feature=player_embedded&v=CYDBoTtdvcE#at=127
https://developer.android.com/tools/help/adb.html
[SOLVED]
Solution = effing about with various linux machines and usb cables until a combination allows ADB sideloading - then carry out steps 15 onward of the root thread to get back to a working state. #rootlife # tuxlife
------------------------- the below is now academic -----------------------------------------
Morning all,
In summary: I'm having 2 issues resolving a boot-loop (see heading "what I did that was stupid" below) issue with my fire 7 - full details of these are in the lists under the heading "What I have tried to fix it:" further below:
I can't get TWRP to reliably mount my SD card (internally or via USB OTG); and
I'm having trouble getting ADB to pick up the device in TWRP for an ADB sideload.
What I did that was stupid: I Rooted my F7 a while ago, got it all working nice (Play store, Bloat disabled, but alexa working etc) - however in the meantime I forgot the important instruction from the fire-7-2019-mustang-unbrick-downgrade etc thread not to update Magisk from within Magisk manager.
I did update Magisk via Magisk Manager and now I have a boot loop.
What I have tried to fix it: I figured all I would need to do is reflash the previous version of Magisk, and "finalise.zip" via, given in the above thread, via TWRP and I'd be good to go. However:
Does anyone know why TWRP is being really finicky about USB OTG USB adaptors and SD cards - they are not always there to mount in the mount menu - is there something I am missing? I am somewhat stuck having done the following:
I mounted a random SD card via a USBOTG adaptor. It didn't show up at first in the "mount" section of TWRP, but after a few secionds arrived when I pressed "select storage" - I then flashed the Magisk.zip - it threw an error about a corrupted zip file.
To attempt to rule out a dodgy SD card, I then flashed "finalise.zip" - which worked fine.
I re-downloaded the Magisk zip file, loaded it to the SD card , and now I can't get TWRP to see the USB OTG reader, or the SD card (in the device's SD slot).
As I am having the above difficulties I decided to try ADB sideload - using the same Ubuntu box I did the rooting on (some of it via ADB) - I have disabled modem manager:
I fire up ADB on my linux box and
Code:
$ sudo killall ModemManager
.
Whether my device is plugged in before, or after I start the ADB server I get no devices listed when I run
Code:
$ adb devices
.
I'm at a loss here as this was the same Ubuntu box i did the rooting on (via ADB) and it found the device fine.
Does anyone have any insight into what I may be doing wrong, or any fixes /workarounds I can try?