Related
This is becoming the hardest way to root apparently -_-
I`m trying to get z4root on to my Galaxy S Captivate from Rogers (SGH-I896) running 2.2
I`ve downloaded the apk file and placed it on my desktop, when trying to copy the file to my phone I get this error message.
(I tried to post a picture here but apparently I need to post 8 times?*fail)
It says an unexpected error is preventing the operation.
Error 0x80070057: The parameter is incorrect.
clicking try again just prompts the message again.
Phone is connected in USB mass storage mode.
USB debugging is on.
It appears the app is no longer available in the market so is this the only way to get it on my phone?
I've literally tried downloading the apk 5 different times from different places and they all give the same message when I try to copy, also tried copying the file pretty much everywhere possible on the phone. any help would be greatly appreciated.
1. make sure you turn on the debugging mode;
2. connect your phone using usb cable;
3. i used one click root to root the captivate, search that one in the forums;
4. follow the instruction of that root app;
Hey
I spent all night reading . . . . well pretty much every page on this forum. I am stuck - I am sure that if I had a normal Kindle Fire it would be rooted by now. I found the tutorial really easy to follow.
This demo unit automatically fires up in demo mode every time. A few notes that may help before I get into what I done. When using the swipe down menu, I only have a couple of options and cant get the the security settings (Im sure at this moment that ADB connectivity is disabled). I am unable to check which software this unit is running. If I try to get into the more option nothing happens, if you try to turn of parental controls the unit stated "this feature isnt availble in demostration mode". When connected in via USB - unit states its connected as media device, is listed as kindle under portable devices in device managers, and in my computer shows as a portable media player, with no contents if clicked on. If you check in the properties your can see a firmware version and a serial number but thats it.
This model has a Demo screen saver which kicks in if the unit is left idle for a few minutes, when it does is disconnects from th system then reconnects and is recognised again. If trying all this and ensuring the screensaver doesnt start still have no effect.
following this thread - http://forum.xda-developers.com/showthread.php?t=2069117
I have completed the windows 7 bug fix as here - http://forum.xda-developers.com/showthread.php?p=36373627
and attempting to install the kindle fire abd drivers or the USB_drivers the PC always states that I am currently using the correct drivers and the kindle is listed as "kindle" under portable devices.
I have also tried with the SDK package with the notes here - https://developer.amazon.com/sdk/fire/connect-adb.html
I have completed the actions in this videos also - http://www.youtube.com/watch?v=Khrxo0-NieM&feature=youtu.be
I have uninstalled the devices from my system numerours times but not matter which driver I try to install / force an update with. My system states that I am using the most upto date driver (MTP USB Device). I can uninstall the device from the system but I cant find any option to delete the drivers it auto assigns (wpdMTPdr.dll, winusb.sys, wudfrd.sys, wpdmtp.dll, wpdwtpus.dll). I would delted them manually but thought I would post here first - incase firther problems could arise.
Can anyone help with this issue, someone in this thread - http://forum.xda-developers.com/showthread.php?t=1828335&page=2
said they managed to do it, but didnt supply any info. I believe I have a driver and/or ADB connectivty issue.
At the moment I would just like to revert this Demo to a normal rooted kindle fire with the google play mod. If this isnt possible I would still like to root the device and just put an OS on there (jellybean seems to be the one of choice).
Thanks for reading this - and I look forward to the replies.
PS - The simple nood guide is by far the most informative and easy to follow guide that I have come accross. Had no problemn following the steps etc - like i said at the begging if this wasnt a demo model I am sure it would have been rooted by now. BIG BIG props to you guys especailly after seeing the lenght you go to helping people who didnt understand the guide! keep up the awesome work
So you have adb installed correctly and you're able to connect to the device USB and read it in your device manager.... correct?
Check under device manager for Kindle Fire. Click and check if it says android adb interface.
Sent from my KFHD7 using xda premium
Yes I believe that the ADB drivers are installed on my system. I tried the ones from the "kindle fire abd drivers", "USB_drivers" and the SDK package when following the Amazon guide. But when I connect my kindle to the PC it Auto installs and picks a driver which I found is labeled an MTP driver. The kindle is only list as "kindle" (in lower case) under portable devices in the device manager.
I have tried to update the driver and point the device manager to look at the Kindle fire ADB drivers, USB_drivers or point it to the drivers in the SDK folders.
I have also tried uninstalling the device each time, installing each drivers and reconnecting the device (i have also just uninstalled the device, left it connected and tried to install the drivers that way but no difference) - however it still installs the MTP driver which is automattically assigned. If the devices is connected with each driver and attempting the "ADB Devices" list in CMD prompt the list of devices is empty.
I am unable to access the security options in the kindle as it is a demo unit, if you touch more nothin happenes.
SO in short yes the drivers are on my system but I am unable to force the kindle to use them. I think this is probably to do with the fact that I cant access the security menu (I think ADB is disabled).
The only thing I can think of at the moment is to get a normal Kindle Fire, connect it and install the correct drivers- Unfortunatly I do not have access to another Kindle Fire to attempt this.
Just now The kindle fire stopped responding when booting up, with a pop up stating Demo mode has stopped responding - with options to wait or close demo mode. I choose close demo mode, but after struggling to boot it fired up in demo mode again.
Anyone know how to force a crash on a kindle fire - this may open access to the security menu.
Hello again - Just an update in case any of this is useful
if I follow this guide http://forum.xda-developers.com/showthread.php?t=1923010
with this page which is linked there www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
The unit still installs as an MTP device. The best luck I have had was running the Install_drivers.bat file from the KFU utility which gives me an unsigned driver pop-up warning. when completed the system says it installes the google, INC, (winUSB)androidUSBdeviceclass (12/06/2010 4.0.0000.00000). However in device manager its still listed under portable devices as a kindle using the MTP driver. If I attempt to update and point the unit to the SDK altered files (using above guide) or the KFU drivers, it is still the same.
I am ready to pull my hair out LOL. But I am still pretty sure that the problem lies with not being able to access the security menu on the kindle.
Hey all another update with a bit of progress but I am stuck
I followed this guide - http://forum.xda-developers.com/showthread.php?t=1830108
and managed to get the Kindle recognised as a Android device after I had installed the google USB drivers
I then updated the drivers in the same way (The only driver it would accept was the one from the Qmenu folders).
Now the device is recognised as a kindle fire - when the window is expanded it states its a Android ADB interface.
I tried the advice in this thread http://forum.xda-developers.com/showthread.php?t=1927710 Bujt I cannot get the device to be recognised as an android ADB composit device.
(still shows as offline or does not appear under the ADB devices command, even though shown in device manager)
When updating the drivers as described in the guide, when I pick let me pick from list of device drivers I do have a "%compositADBinterface%, but no matter what I try once installed the device still reads as a kindle fire => Android ADB Interface. If I attempt the process again the "%compositADBinterface%" is still there.
Any ideas people?
I'm curious as to how you ended up with a demo version.
Open cmd... navigate to sdk\platform-tools\
type adb devices
Does it list a serial number?
Under Device Manager in windows, you should see it listed as Kindle Fire. When you expand that, it should show "Android ADB Interface"
If you see that then adb is installed. You may not be able to do anything without a factory cable. These guys on here should be able help you install a non-demo version on to your device.
Good luck!
Sent from my KFHD7 using xda premium
Hello again - thanks for the reply.
My friend worked in one of the stores that was recently a victim of the recession. I asked him how much they were selling the ex-demo stuff, the same evening he dropped by and handed it to me - He says his manager said he could take it .
Yes in Device Manager now the device is seen as a Kindle Fire and when expanded it states its an Android ADB Interface. I am a noob but from what Ive read so far this means the driver isnt correctly installed. As it should read "android ADB composit device"
Using the ADB devices command , it is blank under the list of devices.
Not sure if this helps, but if I right click the kindle in my computer and look at the properties, I can view the serial number there.
Looking into the factory cable options now
Again thanks for the help
stirky said:
Hey
I spent all night reading . . . . well pretty much every page on this forum. I am stuck - I am sure that if I had a normal Kindle Fire it would be rooted by now. I found the tutorial really easy to follow.
This demo unit automatically fires up in demo mode every time. A few notes that may help before I get into what I done. When using the swipe down menu, I only have a couple of options and cant get the the security settings (Im sure at this moment that ADB connectivity is disabled). I am unable to check which software this unit is running. If I try to get into the more option nothing happens, if you try to turn of parental controls the unit stated "this feature isnt availble in demostration mode". When connected in via USB - unit states its connected as media device, is listed as kindle under portable devices in device managers, and in my computer shows as a portable media player, with no contents if clicked on. If you check in the properties your can see a firmware version and a serial number but thats it.
This model has a Demo screen saver which kicks in if the unit is left idle for a few minutes, when it does is disconnects from th system then reconnects and is recognised again. If trying all this and ensuring the screensaver doesnt start still have no effect.
following this thread - http://forum.xda-developers.com/showthread.php?t=2069117
I have completed the windows 7 bug fix as here - http://forum.xda-developers.com/showthread.php?p=36373627
and attempting to install the kindle fire abd drivers or the USB_drivers the PC always states that I am currently using the correct drivers and the kindle is listed as "kindle" under portable devices.
I have also tried with the SDK package with the notes here - https://developer.amazon.com/sdk/fire/connect-adb.html
I have completed the actions in this videos also - http://www.youtube.com/watch?v=Khrxo0-NieM&feature=youtu.be
I have uninstalled the devices from my system numerours times but not matter which driver I try to install / force an update with. My system states that I am using the most upto date driver (MTP USB Device). I can uninstall the device from the system but I cant find any option to delete the drivers it auto assigns (wpdMTPdr.dll, winusb.sys, wudfrd.sys, wpdmtp.dll, wpdwtpus.dll). I would delted them manually but thought I would post here first - incase firther problems could arise.
Can anyone help with this issue, someone in this thread - http://forum.xda-developers.com/showthread.php?t=1828335&page=2
said they managed to do it, but didnt supply any info. I believe I have a driver and/or ADB connectivty issue.
At the moment I would just like to revert this Demo to a normal rooted kindle fire with the google play mod. If this isnt possible I would still like to root the device and just put an OS on there (jellybean seems to be the one of choice).
Thanks for reading this - and I look forward to the replies.
PS - The simple nood guide is by far the most informative and easy to follow guide that I have come accross. Had no problemn following the steps etc - like i said at the begging if this wasnt a demo model I am sure it would have been rooted by now. BIG BIG props to you guys especailly after seeing the lenght you go to helping people who didnt understand the guide! keep up the awesome work
Click to expand...
Click to collapse
stirky,
First, let me apologize for the delay in getting to your issue, we have been working on a new package for the Kindle
which can be viewed here: http://forum.xda-developers.com/showthread.php?t=2096888
Let us know what you think. Now to your problem. We have worked with the demo Kindles, they have security software
to eliminate program installation, even if you allow or turn on "Allow Installation of Programs". I do not understand how
someone what able to breakthrough the block since it is done at the OS Level. Maybe they hacked the Kernel? Anyways,
the task is not easy. What I would do is Fast a new system.img, boot.img and recovery.img using this software:
http://forum.xda-developers.com/showthread.php?t=2096888
If we need to flash the Kernel I will add that functionality too. What this will do is completely remove the Demo and
control/security software and turn the demo Kindle into a regular Kindle. We can ship the required Factory USB Cable
tomorrow. Read the post and send us a PM.
No worries about the delay in getting back to me! I was quite proud I finanlly managed to get it recognised on my system after trail and error.
First Question - I am now assuming that anything I need to do to this unit requires a Factory Cable? Am I correct?
. Now a note - Not sure if this helps. While playing around I did notice this little quirk.
After I had edited the google USB driver as mentioned in the above post, My system first recognised the device as an Adroid ADB interface under abndroid device. While checking back though my edit I noticed that I mistyped Composite. Rectified this and then re-installed as before. Now the devices is rocognised under Andoid Device as an Android ADB Composite interface. I then proceeded to up date the drivers agains from the Qmenu Drivers Folder. This makes the system list the device as a Kindle Fire and under this is states its now just an android ADB Interface.
I then had a brainwave and made an edit of this file and inserted the same edit as the google USB driver. This all installs fine. But still only recognised as an android ADB Interface under Kindle fire.
Does is have to be recognised as a composite device? or is a Andoird ADB Interface suffcient?
I assume I need a factory cable and will get one ASAP if thats the case.
Root and Google Play for Amazon 7" Kindle Fire HD Demo
stirky said:
No worries about the delay in getting back to me! I was quite proud I finanlly managed to get it recognised on my system after trail and error.
First Question - I am now assuming that anything I need to do to this unit requires a Factory Cable? Am I correct?
. Now a note - Not sure if this helps. While playing around I did notice this little quirk.
After I had edited the google USB driver as mentioned in the above post, My system first recognised the device as an Adroid ADB interface under abndroid device. While checking back though my edit I noticed that I mistyped Composite. Rectified this and then re-installed as before. Now the devices is rocognised under Andoid Device as an Android ADB Composite interface. I then proceeded to up date the drivers agains from the Qmenu Drivers Folder. This makes the system list the device as a Kindle Fire and under this is states its now just an android ADB Interface.
I then had a brainwave and made an edit of this file and inserted the same edit as the google USB driver. This all installs fine. But still only recognised as an android ADB Interface under Kindle fire.
Does is have to be recognised as a composite device? or is a Andoird ADB Interface suffcient?
I assume I need a factory cable and will get one ASAP if thats the case.
Click to expand...
Click to collapse
stirky,
That is perfect Android ADB Interface is sufficient.
Yes, you will need a Factory USB Cable. we do sell them and we are shipping a bunch tomorrow. I would ship it
to you Priority at no additional charge, just PM me your name, address, city, state, zip, phone and email.
You would get the cable in about 3 days. We sell the cables at our direct cost to all XDA Developer Members.
great thread... I just picked up the KF HD 8.9 demo unit myself... I have yet to install the SDK, but please let us know of any developments...
thanks...
Obtain a factory cable. Fastboot flash the system.img,recovery.img and boot.img. Then give me results. Use kindle fire first aid program.
Sent from my KFTT using xda premium
wukster said:
great thread... I just picked up the KF HD 8.9 demo unit myself... I have yet to install the SDK, but please let us know of any developments...
thanks...
Click to expand...
Click to collapse
wukster,
The Kindle Fire 8.9" does not need the Factory USB Cable, just use Option 10 in the interface. There is a known Bug in the Kindle Fire 8.9" Bootloader, if you get stuck in Fastboot, let us know, we have the fix.
Please wait until we do some updates on the software and then download it anytime after Monday 8:00am - we are doing critical updates for Kindle Fire 8.9" models.
---------- Post added at 01:09 AM ---------- Previous post was at 01:07 AM ----------
KindleFireGuy said:
Obtain a factory cable. Fastboot flash the system.img,recovery.img and boot.img. Then give me results. Use kindle fire first aid program.
Sent from my KFTT using xda premium
Click to expand...
Click to collapse
KindleFireGuy,
Thank you for the support, for new users here is a link to the Kindle Fire First Aide software:
http://forum.xda-developers.com/showthread.php?t=2096888
Hi I dont want to hijack your thread or anything but i was wondering if you could possibly help me root my demo unit as well. This one is actually from my store but we dont keep the demos on display and would like to have it for personal use when its just 1 person in the store. (we are located in a mall so we often have just one person in the morning). I would really appreciate it if you could maybe walk me through the steps to get it recognized on adb. I have a KFHD 7". Any help or advice would be greatly appreciated.
Edit: Got it to read as "Android Composite ADB Interface" which I believe was the first step to making it work. I need a Factory Cable which from what I understand requires rewiring the B side (or the Micro USB side) of the cable so that the wire is connected to both Pin 4 and Pin 1. If so then I made a make shift one at work today and just need to solder it. Please advise if I have done anything incorrectly. I would also be interested in purchasing a factory cable from you, Prokennexusa, just in case I need it in the future or if I mess up on making mine.
Demo Kindle - Please Help
Hi
Please excuse ,my ignorance but I am struggling to get my kindle fire to work with the software I downloaded. I followed every step in the instructions and all seemed to be going well until I actually attempted to do anything with it.
I got the demo kindle from a shop clearance but cannot get the demo mode removed. I have a factory cable and the kindle goes into 'fastboot' mode with the cable but doesn't seem to behave any differently after the software states it is complete.
I have included some screen dumps of the messages I received, I apologise if I am just being dumb but I am lost?
I would be quite happy to just have a working kindle...I don't need android on it if this makes it more difficult......please help
Thanks in advance
Below is the message I received when I tried option 9 Display Fastboot status
************************************************
* OK Here We Go, We Are Beginning The Process! *
************************************************
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
*********************************
*Looks Like Fastboot is Enabled *
*********************************
Press any key to continue . . .
This when I tried option 12 Install Amazon ADB Driver
************************************************
* OK Here We Go, We Are Beginning The Process! *
* Please Make Sure The Kindle Is Disconnected *
* From USB During The Driver Installation. *
************************************************
Press any key to continue . . .
****************************************
*The Kindle ADB Driver Will Now Launch *
*Please Make Sure You Are Running This *
*Software As An Administrator Otherwise*
* This Process May Fail! *
****************************************
The system cannot find the path specified.
******************************************
*The Driver Install Was A Success! Please*
* Plug The Kindle Into USB Using The *
* Original USB Cable That Was Included *
* With The Kindle. This Is The Same USB *
* Cable You Use To Charge The Kindle *
******************************************
Press any key to continue . . .
stirky said:
Hey
I spent all night reading . . . . well pretty much every page on this forum. I am stuck - I am sure that if I had a normal Kindle Fire it would be rooted by now. I found the tutorial really easy to follow.
This demo unit automatically fires up in demo mode every time. A few notes that may help before I get into what I done. When using the swipe down menu, I only have a couple of options and cant get the the security settings (Im sure at this moment that ADB connectivity is disabled). I am unable to check which software this unit is running. If I try to get into the more option nothing happens, if you try to turn of parental controls the unit stated "this feature isnt availble in demostration mode". When connected in via USB - unit states its connected as media device, is listed as kindle under portable devices in device managers, and in my computer shows as a portable media player, with no contents if clicked on. If you check in the properties your can see a firmware version and a serial number but thats it.
This model has a Demo screen saver which kicks in if the unit is left idle for a few minutes, when it does is disconnects from th system then reconnects and is recognised again. If trying all this and ensuring the screensaver doesnt start still have no effect.
following this thread - http://forum.xda-developers.com/showthread.php?t=2069117
I have completed the windows 7 bug fix as here - http://forum.xda-developers.com/showthread.php?p=36373627
and attempting to install the kindle fire abd drivers or the USB_drivers the PC always states that I am currently using the correct drivers and the kindle is listed as "kindle" under portable devices.
I have also tried with the SDK package with the notes here - https://developer.amazon.com/sdk/fire/connect-adb.html
I have completed the actions in this videos also - http://www.youtube.com/watch?v=Khrxo0-NieM&feature=youtu.be
I have uninstalled the devices from my system numerours times but not matter which driver I try to install / force an update with. My system states that I am using the most upto date driver (MTP USB Device). I can uninstall the device from the system but I cant find any option to delete the drivers it auto assigns (wpdMTPdr.dll, winusb.sys, wudfrd.sys, wpdmtp.dll, wpdwtpus.dll). I would delted them manually but thought I would post here first - incase firther problems could arise.
Can anyone help with this issue, someone in this thread - http://forum.xda-developers.com/showthread.php?t=1828335&page=2
said they managed to do it, but didnt supply any info. I believe I have a driver and/or ADB connectivty issue.
At the moment I would just like to revert this Demo to a normal rooted kindle fire with the google play mod. If this isnt possible I would still like to root the device and just put an OS on there (jellybean seems to be the one of choice).
Thanks for reading this - and I look forward to the replies.
PS - The simple nood guide is by far the most informative and easy to follow guide that I have come accross. Had no problemn following the steps etc - like i said at the begging if this wasnt a demo model I am sure it would have been rooted by now. BIG BIG props to you guys especailly after seeing the lenght you go to helping people who didnt understand the guide! keep up the awesome work
Click to expand...
Click to collapse
stirky said:
Hey
This is My first post and im allittle nervous so......
My girlfriend was cheated out of some money when she bought a Fire Hd 8.9 from some girl. it turned out to be the Demo version.
I was able to remove the demo by going to the app store, it asked to set up wifi so i did that, loading file manager then going online downloading 1market app apk. they asked for permission to allow non market apk to be installed so i granted that.
then i went to amazon downloaded newest version of fire 8.9 placed it on update folder from my file manager.
then i downloaded adw launcher apk from 1market store.
This launcher allowed me to access device from settings and from there i updated my kindle fire. it removed the demo version and now running latest version and no demo.
I did all this after rooting the device but i see no way that this method wont work on non rooted devices.
Only difference is that there is no lock screen on the kindle. but besides that works great......
This answering questions thing is hard please dont ever make me do this again....
Click to expand...
Click to collapse
Root or reload KFHD 8.9
wukster said:
great thread... I just picked up the KF HD 8.9 demo unit myself... I have yet to install the SDK, but please let us know of any developments...
thanks...
Click to expand...
Click to collapse
Were you able to root or reload the DEMO unit to a regular tablet?
I have just purchased an 8.9 unit myself and have not seen anyplace for sure if these units can be reworked since ADB is not enabled.
Regards Jery
KindleFireGuy said:
Obtain a factory cable. Fastboot flash the system.img,recovery.img and boot.img. Then give me results. Use kindle fire first aid program.
Sent from my KFTT using xda premium
Click to expand...
Click to collapse
I have a kindle hd 8.9 demo, I do not know if this tool will help
lkmgfy said:
I have a kindle hd 8.9 demo, I do not know if this tool will help
Click to expand...
Click to collapse
I was able to get the demo 8.9 loaded with the regular Kindle software but, with a slightly different method.
I used Soupmagnet's restore image LINUX script that flashes a pre-rooted 8.9 Kindle version 8.1.4 image to the kindle using fastboot.
http://www.adrive.com/public/xvZeWC/KFHD8.9.restore.zip
While the rest of the demo unit is shut down, fastboot will work if the script is executed prior to plugging in the tablet.
The script will set waiting to see fastboot (waiting for device).
When the tablet is booted up, it passes briefly thorough a fastboot cycle and the script will catch it and keep the tablet in fastboot (pretty much as the KF 1 does). The script then loaded version 8.4.1 and success. You can then download the latest Kindle OS and loose root and be back to a stock configuration or continue and push 2nd bootloader, twrp,etc. and or new ROM.
Success of course depends on having the USB and ADB drivers loaded on LINUX (Using Soupmagnet's soupkit will do that for you).
You will have to try the soupkit again package and see if it will work for you. This package is intended for all kindles I believe.
I had all the drivers loaded using the first soupkit package and the drivers worked to see and communicate with the 8.9 tablet.
Original Soupkit:
http://forum.xda-developers.com/showthread.php?t=1850038
New "Soupkit Again"
http://forum.xda-developers.com/showthread.php?t=2162986
However, I installed the new "Soupkit Again" package over the first Soupkit package and while the drivers still work, I lost all access to the Soupkit utility itself (which is not used to restore the 8.1.4 image to the Kindle 8.9). A little off topic, but, I would like to know how to get my Soupkit utility back working. (The soupkit.sh script is missing after installing the new "Soupkit Again" over the original Soupkit).
Hi friends, I got my Nook HD+ today(India). The first time I turn it on, it prompted to install a critical update. I connected it to my wifi network and it downloaded and updated fine. After updating, at the registration process it again checked for critical updates and from this time onwards it keep saying that
" Network Problem: A network-related error occurred. You may have lost connectivity to the local wireless network. Press continue and we'll try to test your connection"
When I press continue it shows " Checking connection" and then detect my wifi fine (Signal strength shows excellent). Then again when I click "continue with setup", this whole procedure is repeating. My Galaxy tab 2 and Laptop are working fine with the same wifi network.
Please, some experts help me about what to do. I'm clueless about what to do next.
There is a known issue with the latest stock Nook firmware moaning about loss of wireless.
Are you able to skip these steps for the time being?
Otherwise I would suggest just flashing one of the Cyanogenmod firmwares instead.
Thanks for the reply artesea. No, I can't skip those steps. All it does is booting to the same procedure again and there is no option to skip. Is it worth waiting for this problem to get fixed by B&N? I really wanna experience the stock OS.
From what others are saying it looks like B&N might have a server down, once it's back up it should just start to work. However if the latest firmware is pointing in the completely wrong direction (IP or domain they don't own) then it might require a firmware patch. Not sure if the device will update if you aren't getting past the reg screens. But a flashable file should be available either direct from them, or someone on these forums.
Keep an eye on this thread where it was first reported
http://forum.xda-developers.com/showthread.php?t=2431280
Thanks artesea. One more question. Does doing the factory reset and turning off the wifi will allow me to use the device without registering?
mashac said:
Thanks artesea. One more question. Does doing the factory reset and turning off the wifi will allow me to use the device without registering?
Click to expand...
Click to collapse
There is a way to skip registration. Look at my HD/HD+ Tips thread linked in my signature and look for the item about skipping OOBE.
Sent from my Nook HD+ running CM10.1 on emmc.
Thanks artesea and leapinlar for the help. My Nook HD+ detected my wifi again out of nowhere and after another update I successfully registered my device. Thanks again guys.
Mine is doing the same thing on February 13, 2018. Really making me mad. Any help is appreciated.
Mine is doing the same thing and it was working fine until then I thought I had to do something with the nook itself so I factory reset it. Now it will not connect to my wifi at all I have even tried my hotspot on my phone but it didn't work. My nook has worked fine up until this point and I have had it for over 5 years. I know it has nothing to do with my battery because I just replaced it at the beginning of this year. It just makes me mad that it will not connect to my wifi.
Can't get past the 'Network Problem' error
I seem to have the same problem as the OP of this thread. I cannot get past a prompt on the stock ROM setup of my Nook HD+ where it says a network-related error has occurred. I'm connected to my home wi-fi just fine but setup will not go past this error. From what I've read it's caused by a security patch needing to be installed on the Nook. In the past, it updated automatically from an OTA update released by B&N but that is not happening any more. Have had it plugged in for days with no update occurring.
Have downloaded the patch file from B&N's website but I can't manually install it because Windows cannot recognize the Nook as a USB device. Have tried updating drivers, uninstalling/reinstalling the device in Windows but nothing works. If I could get that to work, apparently I can just drag & drop the file onto the Nook in Windows and it will install and update the Nook.
So, if anyone can offer a solution to my problem, it would be GREATLY appreciated. I went back to stock ROM because after trying Cyanogen & Lineage the Nook was just too slow to run either one successfully.
Solved: Right after I posted this, I found what is apparently a newer version of the stock ROM than I had previously installed. In case anyone needs this stock ROM it's in the [Stock][Android 4.0.4 ICS] Nook HD/Nook HD+ [Hummingbird/Ovation] 2.2.1 [2018 Update] thread. After installing it, setup went flawlessly and I'm back to full stock ROM. Thanks to secretwolf98 for posting this!
techfandan said:
I seem to have the same problem as the OP of this thread. I cannot get past a prompt on the stock ROM setup of my Nook HD+ where it says a network-related error has occurred. I'm connected to my home wi-fi just fine but setup will not go past this error. From what I've read it's caused by a security patch needing to be installed on the Nook.
Solved: Right after I posted this, I found what is apparently a newer version of the stock ROM than I had previously installed. In case anyone needs this stock ROM it's in the [Stock][Android 4.0.4 ICS] Nook HD/Nook HD+ [Hummingbird/Ovation] 2.2.1 [2018 Update] thread. After installing it, setup went flawlessly and I'm back to full stock ROM. Thanks to secretwolf98 for posting this!
Click to expand...
Click to collapse
I just got a secondhand Nook tablet 7" HD BNTV400 that the vendor has factory reset, and I'm stuck in the same loop:
"Select network/continue with setup/a network error has occurred/we'll test your connection/continue with setup/a network error has occurred" etc etc.
Can anyone point to the security patch that needs installing, based on the previous post and its solution? This tablet is factory reset, so no funky ROMs needed or anything. Thanks for any help or suggestions.
link to update barnes&nobles site
sumbodyelse said:
I just got a secondhand Nook tablet 7" HD BNTV400 that the vendor has factory reset, and I'm stuck in the same loop:
"Select network/continue with setup/a network error has occurred/we'll test your connection/continue with setup/a network error has occurred" etc etc.
Can anyone point to the security patch that needs installing, based on the previous post and its solution? This tablet is factory reset, so no funky ROMs needed or anything. Thanks for any help or suggestions.
Click to expand...
Click to collapse
http s: // help.barnesandnoble.com/app/answers/detail/a_id/1139/~/nook-hd%2Fhd%2B---software-version-2.2.1
(you'll need to put that url back together I don't have sufficient number of posts to insert links....)
the current download is 2.2.1 - you'll need to download to a computer I use an old windows xp laptop,cause it doesn't have problems recognizing
the usb connection when the nook is plugged into the computer. after the file is downladed from barnes&nobles,
you'll need to hookup to computer with your charging (usb) cable and copy the file
over to the root directory of the nook
as the instructions state, don't rename the file... it won't work..
NOOK HD/HD+ version 2.2.1 update is available as an automatic download to registered NOOK HD/NOOK HD+ devices connected to Wi-Fi (Wi-Fi should be turned ON and connected to a hotspot, and the device should be left in sleep mode).
To get the software update right now, be sure you are connected to a Wi-Fi hotspot, tap the Settings icon in the Status bar at the top of your screen, tap on All Settings, then tap on Device Information, and check to see that your Software version matches the number at the top of this page. If it does not, tap on Software version and then tap on the Check for updates button. Follow any on-screen instructions. Do not turn off your device while it is downloading or installing a software update.
To get the update manually, you can download the software update to your computer at any time and then copy it onto your NOOK HD. Simply follow the steps below.
The process will take about 15 minutes for a manual download (depending on the Internet connection for your computer). You should NOT turn your NOOK off while the new software is being downloaded.
Manual Download Instructions
1. From your computer, click here for the software update file. Select Save and select Desktop as the location.
Do NOT modify or change the downloaded file's name in any way. Do NOT try to open the file.
2. Tap the Settings icon in the Status bar at the top of your screen. Tap on All Settings, then tap on Device Information and make sure your NOOK battery charge is at 20% or more.
3. a) For Windows users: Connect your NOOK to your computer using the USB cable that came with your device. A new drive, named MyNOOK or BNTV400, should show up in My Computer. Open this drive and then open the Internal Storage folder within the drive.
From your computer, drag and drop the downloaded file onto the main directory of the Internal Storage folder. Do NOT open or unzip the file. You should not create a new folder on the NOOK drive or add the file to any other existing folder within Internal Storage.
b) For Mac users: Connect your NOOK to your computer using the USB cable that came with your device. A new, removable drive, named MyNOOK should appear on the desktop or in devices. Open the drive MyNOOK.
From your computer, drag and drop the downloaded file onto the top level of the MyNOOK drive. Do NOT open or unzip the file. You should not create a new folder on the MyNOOK drive or add the file to any other existing folder within the MyNOOK drive.
4. Eject or Safely Remove the NOOK drive after the file transfer is complete, and then disconnect your NOOK from your computer.
5. Your NOOK will automatically recognize the file after a few minutes when it goes into sleep mode, and proceed to install the updates.
6. Please do not turn off your NOOK during the installation process.
7. Once the installation is completed, your NOOK will automatically restart and go to the unlock screen.
8. Tap on the small "n" NOOK symbol that appears in the Status bar for additional information. The software has been successfully updated.
Your NOOK must remain turned on while the update is being installed. Once the software is installed, your NOOK will automatically restart. To verify you have the latest update, tap the Settings icon in the Status bar at the top of your screen, tap on All Settings, then tap on Device Information, and check to see that your Software version number matches the number at the top of this page.
Once the software update is completed, your NOOK will automatically restart. The software update will preserve your personal settings, including your registered account information, content, display settings, and Wi-Fi settings.
worked for me anyhow.....
sumbodyelse said:
I'm stuck in the same loop:
"Select network/continue with setup/a network error has occurred/we'll test your connection/continue with setup/a network error has occurred" etc..
Click to expand...
Click to collapse
I have the same issue but a slightly different end result. I'm in the same setup loop. The B&N help page says it needs the updated TLS info for security online. I can successfully download the proper file for my nook HD, but the help page says that it should connect as MyNOOK and that you only copy the file to that directory. My nook connects as BNTV400 and then shows a sub-directory of 'internal storage' like a camera would show up. Nowhere in the sub-directories is there a file or folder I can find called MyNOOK and that's not the name of the device when connected to my Win7 desktop or laptop. I spent a couple of hours exchanging messages with B&N via text chat last night and they finally gave up. I can't believe that mine is the only unit doing this.
So, in short, my nook successfully syncs with my computer(s) and I have successfully downloaded the needed TLS update file, I just don't know where to put it without potentially bricking the unit. Thanks in advance for any thoughts.
------- Edited to add -------
After posting the above message, I checked a few more places and ran across someone with the exact problem I had - the nook was recognized but showed the name as BNTV400, not MyNOOK. He just copied the file over anyway and it worked, so I decided to try that too. In Windows Explorer, I copied the "sideload_2_2_update.npk" file over to the top directory, shown as internal storage. I set the nook aside and, a few minutes later, I noticed it was rebooting. It then went though several onscreen updates to apps then let me move beyond the place where it was previously stuck and I was able to connect to the internet and complete setup. I wanted to post this for future searchers...
The Barnes and Noble Nook first generation e-reader is officially discontinued today. Customers are now unable to purchase new content, register with a BN.com account, or sign in using a NOOK account. Users will still have access to their purchased content and are able to continue sideloading ebooks. If you log out of your B&N account or perform a factory reset, you will lose everything.
Barnes and Noble decided to discontinue this device for two reasons. Firstly the original Nook came out in 2009 and many users have switched to a different e-reader. The second is primarily due to B&N implementing new security standards, known as Transport Layer Security (TLS). TLS Versions below 1.2 are being phased out, and devices accessing the Internet that are not updated to utilize the required TLS Version will not be able to perform many functions related to Internet connectivity. This is why the bookseller issued a new firmware update for all of their e-readers and tablets.
Hi,
I was give a KF 1st gen to fix. When turned on it says "The application JellyBean 4.2 (process.android.process.acore) had stopped unexpectedly. Please try again.). After clicking Force close the message comes right back up. It appears stuck in an endloess loop.
I have done some reading on here and apparently an incompatible OS version was installed on this thing and I need to bring it back to Factory settings.
I downloaded KFU 0.99 and tried that but run into the following issues:
- executing the install_driver.bat file fails with a message "Cannot complete the Device Driver Installation Wizar". This is on Windows 10. The KF appears to connect OK to the PC though.
- when executing the run.bat file I see the following:
Resetting ADB and Launching KF Utility...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
- the ADB Status says Online, but the Boot Status says Unknown;
- When activating Fastboot, I get a message "couldn't write bp1, panic!"
- When installing FFF it just sits there with a message ...waiting for device...
- For some options, it attempts to download files from random.kennocha.com (108.61.31.89), and that site appears to be down.
I was able to download the Amazon Kindle Fire 6.3.2 stock update.zip file, and copied it to the root of the kindle. I then reset it but that didn't do anything.
Any help appreciated,
Thanks,
Jozef
JozefVdM said:
Hi,
I was give a KF 1st gen to fix. When turned on it says "The application JellyBean 4.2 (process.android.process.acore) had stopped unexpectedly. Please try again.). After clicking Force close the message comes right back up. It appears stuck in an endloess loop.
I have done some reading on here and apparently an incompatible OS version was installed on this thing and I need to bring it back to Factory settings.
I downloaded KFU 0.99 and tried that but run into the following issues:
- executing the install_driver.bat file fails with a message "Cannot complete the Device Driver Installation Wizar". This is on Windows 10. The KF appears to connect OK to the PC though.
- when executing the run.bat file I see the following:
Resetting ADB and Launching KF Utility...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
- the ADB Status says Online, but the Boot Status says Unknown;
- When activating Fastboot, I get a message "couldn't write bp1, panic!"
- When installing FFF it just sits there with a message ...waiting for device...
- For some options, it attempts to download files from random.kennocha.com (108.61.31.89), and that site appears to be down.
I was able to download the Amazon Kindle Fire 6.3.2 stock update.zip file, and copied it to the root of the kindle. I then reset it but that didn't do anything.
Any help appreciated,
Thanks,
Jozef
Click to expand...
Click to collapse
this is the 5th gen forum
please ask here
http://forum.xda-developers.com/kindle-fire
see
[INDEX] Kindle Fire Development
Sent from my KFFOWI using XDA Labs
sd_shadow said:
this is the 5th gen forum
please ask here
http://forum.xda-developers.com/kindle-fire
see
[INDEX] Kindle Fire Development
Sent from my KFFOWI using XDA Labs
Click to expand...
Click to collapse
Sorry 'bout that! I reposted it. Feel free to delete this thread. Thanks!
I received a Fire 5th gen running stock Fire OS v5.1.3. I have only turned it on so far. I have not connected it to WIFI, I have not installed anything, I have not altered it from the factory default state in any way. I am brand new to customizing Android. I've spent the better part of 3 days digging through threads and watching videos, and as of right now my head is spinning. Information is fragmented and I am not sure how to put it all together.
I would greatly appreciate any help that will set me in the right direction.
Firstly, do I have a KFFOWI | Ford device? I have searched the settings and options and all I can find is "Device Model - Fire (5th Generation)". Based on THIS it would seem that all current Fire 7 models are "KFFOWI", but wanted to ask the experts of XDA before proceeding.
I want to flash the unofficial CM 12.1 ROM. I have heard good things about CM but if another ROM is recommended, please do not hesitate to let me know about it. My goal is to get away from Fire OS, but beyond that I am a simple user who won't do a lot of heavy app toying. After reading about how to Flash CM, I have become rather confused. The instructions say that on Fire OS >= 5.1.1 to use FlashFire 0.5.0. I Googled that and found the FlashFire app in the Playstore. The app says it requires Root access. Am I correct to assume that I can go no further without gaining Root? If that is so then I must downgrade from 5.1.3 to 5.1.2 using THIS information?
If this is correct, after downgrading what is the best way to gain Root (THIS tool?) After gaining Root access, how do I proceed with the CM install? I do apologize, but I find the unofficial CM 12.1 instructions (linked above) are written for someone who has done this before. I have not and am perhaps seeking a simpler guide with basic steps. I just feel overwhelmed and a bit fearful, I want to make sure I do this right and that the process is fun! For example, how do I install FlashFire without having the Playstore installed? I found a video for installing the Playstore (Root Junkies) but it seems to include tools based on Fire OS 5.1.1.
I hope this wasn't too long of a post. To summarize, I am assuming I need to do the following but am unsure exactly how to proceed.
1. Downgrade from 5.1.3 to 5.1.2
2. Gain Root
3. Install the Playstore to install FlashFire, then use FlashFire to flash files from an external mSD to install CM 12.1
What else am I missing? Please help me to connect the dots!
Thank you for reading!
Blastyrant said:
I received a Fire 5th gen running stock Fire OS v5.1.3. I have only turned it on so far. I have not connected it to WIFI, I have not installed anything, I have not altered it from the factory default state in any way. I am brand new to customizing Android. I've spent the better part of 3 days digging through threads and watching videos, and as of right now my head is spinning. Information is fragmented and I am not sure how to put it all together.
I would greatly appreciate any help that will set me in the right direction.
Firstly, do I have a KFFOWI | Ford device? I have searched the settings and options and all I can find is "Device Model - Fire (5th Generation)". Based on THIS it would seem that all current Fire 7 models are "KFFOWI", but wanted to ask the experts of XDA before proceeding.
I want to flash the unofficial CM 12.1 ROM. I have heard good things about CM but if another ROM is recommended, please do not hesitate to let me know about it. My goal is to get away from Fire OS, but beyond that I am a simple user who won't do a lot of heavy app toying. After reading about how to Flash CM, I have become rather confused. The instructions say that on Fire OS >= 5.1.1 to use FlashFire 0.5.0. I Googled that and found the FlashFire app in the Playstore. The app says it requires Root access. Am I correct to assume that I can go no further without gaining Root? If that is so then I must downgrade from 5.1.3 to 5.1.2 using THIS information?
If this is correct, after downgrading what is the best way to gain Root (THIS tool?) After gaining Root access, how do I proceed with the CM install? I do apologize, but I find the unofficial CM 12.1 instructions (linked above) are written for someone who has done this before. I have not and am perhaps seeking a simpler guide with basic steps. I just feel overwhelmed and a bit fearful, I want to make sure I do this right and that the process is fun! For example, how do I install FlashFire without having the Playstore installed? I found a video for installing the Playstore (Root Junkies) but it seems to include tools based on Fire OS 5.1.1.
I hope this wasn't too long of a post. To summarize, I am assuming I need to do the following but am unsure exactly how to proceed.
1. Downgrade from 5.1.3 to 5.1.2
2. Gain Root
3. Install the Playstore to install FlashFire, then use FlashFire to flash files from an external mSD to install CM 12.1
What else am I missing? Please help me to connect the dots!
Thank you for reading!
Click to expand...
Click to collapse
FlashFire can be sideloaded; no need to install the Play Store or any other Google components before/after rooting.
http://www.apkmirror.com/apk/chainfire/flashfire/
I can not get any driver installs to take. I have not been able to start the 5.1.2 downgrade to attempt rooting. This has become rather frustrating.
Installed the Kindle Fire USB Drivers and the device becomes recognized. When I plug it in an "auto run" pop-up appears. But I am unable to connect via ADB to begin to downgrade. I have USB debugging turned on and followed the instructions in the Root Junky video guide. After that I restored my system. I tried to associate the driver via Device Manager but am always unable. My Win7 machine is unable to find them when I search as per the many instructions I've read thus far. From what I've read and seen, I should have an option in the "let me pick from a list of device drivers on my computer" button that says "Android devices" or "mobile" and those (or anything even remotely like them) are never in the list.
I then ran the 15 sec ADB Installer v1.4.3. This copys 0 files, when in THIS video guide it shows it copying 4 files. When asked to "install the USB drivers" the program gives me an error log that says "Invalid command or parameter", which has something to do with DPInst_x64.exe. I do not have the permissions to post in the discussion thread for this tool to ask what I am doing wrong.
After that I tried THIS method. When I browse the extracted folder I get a message that "Windows was unable to install your Fire" and "Windows could not find driver software for your device".
WARNING Do not downgrade below 5.1.2. It has been confirmed to brick the device.
Here is a status update for anyone who is attempting to do the same thing and has been running into obstacles.
I uninstalled all of the drivers. I did this with a system restore. But you could just as easily do this manually. I've also seen some "wipe" tools online that claim to rip out all Android drivers, maybe try one of those if needed? Once they were gone I turned the Fire 7 ADB debug mode on. I then installed the Kindle drivers from Amazon. Then I plugged in the Fire 7 via USB and let it "install drivers". I checked Device manager and this time ADB was showing up. I then shut down the Fire, held volume down+power to boot into Recovery Mode. I had to then manually point the Fire in Device Manager to the correct drivers. Then I sideloaded the 5.1.2 firmware and it has flashed successfully. Next is Root and then CM12.1.
Here is what I did:
To start, it was running 5.1.3 out of the box. I never connected it to WIFI, never altered it, never updated it, etc. It was a stock Fire 7 Gen 5.
1. Delete all previous Amazon driver installations (if required)
2. Install THESE drivers (I'm on Win7)
3. Enable ADB debugging on your Fire tablet (Info can be found here)
4. Download and extract THESE ADB Fast Boot Files from Root Junkys.
5. Download the v5.1.2 OS build from HERE and then verify the SHA1 and MD5 checksums with THIS free online tool.
SHA1: 66B5423725B79CEB0D5866FA32FF414A99A4B50A
MD5: 5B0DCC957DEF3ACCFF58BF33794D6D88
6. Connect your powered-off (turned off, in the off state, etc) Fire 7 5th Gen tablet via USB and then hold volume down+power to boot into Recovery Mode.
7. (perhaps optional) If Fire is not listed as a usable device in Device Manager when in Recovery Mode (or has that warning icon next to it), you'll need to manually point it to the drivers you installed.
.....Select Other Devices > Fire and then Right Click it and choose Update Driver
.....Click the button to let you pick from a list of drivers on your computer. Find the Amazon device (Fire Device) in the list and then choose "from disk".
.....Navigate to the default driver install folder (C:\Program Files (x86)\Amazon.com\Kindle Fire\Drivers)
.....Select Android Composite ADB interface (this is for Stock ROM, recovery/adb sideload)
More info for step 7 can be found HERE under "Connecting Your Tablet to Your Computer"
8. Hold Select and Right Click anywhere in the extracted ADB Fast Boot Files folder and choose "Open Command Window Here" from the context menu.
9. In the command window type "adb sideload <path to the v5.1.2 firmware>"
.....IE: C:\Users\MyPC\Desktop\Amazon Fire\ADB FASTBOOT FILES WINDOWS>adb sideload "C:\Users\MYPC\Desktop\Amazon Fire\update-kindle-global-37.5.4.2_user_542168620.bin"
.....You can make this easier on yourself by typing "adb sideload " and then drag-drop the v5.1.2 file into the command widow and the correct path will be automatically populated for you.
.....Click Enter, and allow the process to run its course
You should now be running v5.1.2 stock firmware, which is fully rootable. Next up is rooting and then installing CM 12.1.
I'll start reading up on rooting from THIS thread. I'll make a post with what I did after I have it working.
Rooting...
I watched THIS Root Junkys tutorial video for gaining root access. The Super Tool successfully installed KingRoot, but that application is unable to root this device. So what I did was grab the most recent (as of today: v4.9.5) from THIS thread. I renamed that file to Kingroot.apk and replaced the old version found in the Super Tool "apps" directory. I then went through the normal installation procedure and have gained root. To verify this I blocked OTB updates and disabled lock-screen advertisements.
Next up is installing CM 12.1.
Installing Unofficial Cyanogenmod v12.1 (7/10/2016):
I used Root Junkys Super Tool to install Google Play. The tool does eveything for you so there is no need to type out the steps. You can get that tool HERE
Once Google Play was installed, I linked an account and downloaded/installed the current version of FlashFire.
To install CM 12.1 I followed the instructions in THIS thread.
Next up is tweaking CM to my liking and getting the Play store installed.
I apparently picked the wrong GApps package so it did not install. Now I am trying to sideload the nano or pico package but they fail to verify the file signature. Any suggestions?
Blastyrant said:
I apparently picked the wrong GApps package so it did not install. Now I am trying to sideload the nano or pico package but they fail to verify the file signature. Any suggestions?
Click to expand...
Click to collapse
Likely an incompatible package. Verify ARM/5.1/nano. You can check the file integrity in advance by downloading and opening the MD5 checksum file (available for every package) in a text editor. Then use a third party tool like ES File Explorer to see if the signatures match.
Davey126 said:
Likely an incompatible package. Verify ARM/5.1/nano. You can check the file integrity in advance by downloading and opening the MD5 checksum file (available for every package) in a text editor. Then use a third party tool like ES File Explorer to see if the signatures match.
Click to expand...
Click to collapse
Thank you for the reply. I re-downloaded the file again and made sure I had ARM/5.1/nano. I grabbed the MD5 checksum file and verified that the signatures match. The adb sideload continues to fail at 46% with the error "failed to verify whole-file signature" and "signature verification failed".
I also tried to sideload FlashFire v0.52 and received an error "Footer is wrong" and "Signature verification failed". I also verified the MD5 checksum.
I'm going to dig a bit and hopefully uncover a solution through research. Any additional information or suggestions would be greatly appreciated, as I would rather fix this without reverting to stock o/s and then redoing the entire process.
I gave in and re-did the whole process. I got CM installed and Google Play running w/o issue this time. =)
With CM installed, is there a safe way to get rid of the "Amazon" text that shows on before each boot?
Blastyrant said:
Thank you for the reply. I re-downloaded the file again and made sure I had ARM/5.1/nano. I grabbed the MD5 checksum file and verified that the signatures match. The adb sideload continues to fail at 46% with the error "failed to verify whole-file signature" and "signature verification failed".
I also tried to sideload FlashFire v0.52 and received an error "Footer is wrong" and "Signature verification failed". I also verified the MD5 checksum.
I'm going to dig a bit and hopefully uncover a solution through research. Any additional information or suggestions would be greatly appreciated, as I would rather fix this without reverting to stock o/s and then redoing the entire process.
Click to expand...
Click to collapse
Blastyrant said:
I gave in and re-did the whole process. I got CM installed and Google Play running w/o issue this time. =)
With CM installed, is there a safe way to get rid of the "Amazon" text that shows on before each boot?
Click to expand...
Click to collapse
Wait - you are trying to sideload GAaps (and apparently FlashFire) via the stock recovery menu? Can't do that on this device. GAaps zips and other items targeting the system partition get installed via FlashFire which can be obtained from apkmirror or other trustworthy download site if running on a device that lacks Play store access.
Amazon spash screen originates from locked bootloader and can not be replaced.
I just completed the same process for a 5.1.1 Fire 7 5th Gen. Instead of messing with the 5.1.1 rooting, which was not the exact same process as 5.1.2, I simply upgraded to 5.1.2 (using the same methods I used to downgrade from 5.1.3) and then completed the exact same steps.
CM 12.1 is working great on both devices. =)
Davey126 said:
Wait - you are trying to sideload GAaps (and apparently FlashFire) via the stock recovery menu? Can't do that on this device. GAaps zips and other items targeting the system partition get installed via FlashFire which can be obtained from apkmirror or other trustworthy download site if running on a device that lacks Play store access.
Amazon spash screen originates from locked bootloader and can not be replaced.
Click to expand...
Click to collapse
This is my first time ever trying to hack an Android device. I had chosen the wrong GApps package the 1st time and thought I could sideload the correct one to get it to install. Again, I am very new to this so I do not know what works, what doesn't, or why. As I am faltering I am taking the time to research a bit in an effort to educate myself so that my next Android experiment is that much more fun!
Thank you for the information!
Blastyrant said:
I just completed the same process for a 5.1.1 Fire 7 5th Gen. Instead of messing with the 5.1.1 rooting, which was not the exact same process as 5.1.2, I simply upgraded to 5.1.2 (using the same methods I used to downgrade from 5.1.3) and then completed the exact same steps.
CM 12.1 is working great on both devices. =)
Click to expand...
Click to collapse
Blastyrant said:
This is my first time ever trying to hack an Android device. I had chosen the wrong GApps package the 1st time and thought I could sideload the correct one to get it to install. Again, I am very new to this so I do not know what works, what doesn't, or why. As I am faltering I am taking the time to research a bit in an effort to educate myself so that my next Android experiment is that much more fun!
Thank you for the information!
Click to expand...
Click to collapse
Glad to hear all is well on both devices and that you are taking time to research and understand the 'why' behind the 'what' & 'how'. Makes the experience much more enjoyable IMO. Not to mention less error prone.
BTW - root procedures are identical for 5.1.1/5.1.2 but it's easy to think they are different reading through the hundreds of contributor posts, some with conflicting information.
I want to use Titanium Backup to backup/restore when it comes time to update CM 12.1. I downloaded it but it says "Root access: Failed". I then downloaded and installed Root Checker by Super User and it says I am rooted. It reports SU Found (/system/bin/su/system/xbin/su) and Busy Box is installed (/sbin, vendor/bin, /system/sbin, /system/bin, /system/xbin). I also ticked on Root access for apps in the Developer options of CM 12.1. I am assuming that I need SuperSU to provide root access to applications?
I installed SuperSU and on launch it asks to update the binary. This always fails. The link it provides takes me to http://supersu.com/insteadbinaryfile.html. It is here that I am getting confused.
Method 2: replace system/ Xbin with SU file, Steps : <-- Where to I obtain the SU file?
Step 1: Install Root.Explorer APK. <-- Is this the app by by Speed Software that cost $3.99?
Step 2: Rename Su to .SU
Step 3: Copy .SU to system/xbin
Step 4: Authorize Su (chmod 0777 .su) <-- I am unsure how to do this.
Step 5: delete the other SU files, such as ksu, etc. <-- etc means what exactly? What are the files I would need to delete?
Step 6: Rename.SU to SU
Step 7: Go back to the desktop to delete the other authorization apps <-- Which other authorization apps?
I feel like I am making something easy into something much harder. Any help would be greatly appreciated!
I uninstalled Titanium Backup and SuperSU. I then ticked off root for apps in developer settings, ticked it back on, and rebooted the device. Then I reinstalled SuperSU and this time clicked the "expert" button on first start. It installed and is working. Then I installed Titanium backup and that is also working. So looks like it was just an order of operations needed to solve my problem.
Revisiting this old thread. I am going to upgrade to the Fire Nexus ROM and post my steps.
https://forum.xda-developers.com/amazon-fire/orig-development/rom-fire-nexus-rom-lmy49f-t3300714