Well i own a nook tablet. and i was wondering if i could install a nook color rom without causing any trouble with by device since the nook tablet devs are kind of .....slow. But i should not say anything cuz i probably don't know 1/1000 of the things they know.
but anyway, will it work.
hint:i want to install the regular cyanogen mod but it says nook color. not tablet
also if you could give me a link on how(not mandatory)
thankyou
424aca said:
Well i own a nook tablet. and i was wondering if i could install a nook color rom without causing any trouble with by device since the nook tablet devs are kind of .....slow. But i should not say anything cuz i probably don't know 1/1000 of the things they know.
but anyway, will it work.
hint:i want to install the regular cyanogen mod but it says nook color. not tablet
also if you could give me a link on how(not mandatory)
thankyou
Click to expand...
Click to collapse
I hope you have a good flamesuit.
The devs are not "slow" - this is a different animal. The NT has a locked bootloader whereas the NC does not. If you could install a ROM you would be the first. Feel free to give it a go and post instructions on how you got it to work.
TL;DR: No, you cannot.
As noted, the devs are not slow, even with an unlocked device, building custom ROMs would take time, more than the month or two (at most) that the Nook Tablet has been out.
While the NC and the NT look quite similar, the innards can be vastly different, and require entirely different drivers. This is of course first assuming that there weren't a locked bootloader.
Getting around the bootloader will be a pain in the butt, and may take years upon years to do "properly", as ideally, we would know the private key, and then we could sign our own bootloaders. That being highly unlikely, we have to find a bug in the bootloader (don't worry, there is in all likelihood a bug in there somewhere) and then figure out how to exploit it.
Basically, it's a pain in the butt, and it will take a long time, I wouldn't expect a Cyanogenmod ROM being available for a long time... but until then, we can root the device, and make the best of it.
If you want a custom rom then get a Nook Color. With the right overclocked kernel it will have about the same performance as the Nook Tablet.
The initial JTAG was unsuccessful since they are using Secure JTAG.
They are looking into 2nd INIT and kexec to use the kernel to run another rom for us, but that is still a little ways away.
Related
I did one flash...to TNT version 4xx, and I loved it...but I'm finding I'm getting lots of Google Framework errors and generally just kind of want to start from scratch, over again.....go back to the latest version of the official viewsonic roms.
Sadly I didn't use clockwork or anything so I think my original files are history
I know there are lots of threads, and I tried to follow one about snagging a rom and moving it to the Root and all it does is re-install TNT I think I am "not getting something".
Can someone walk me through this....
The force closes can be fixed by re-partitioning your sd card. Part 1 Step 7 in this tutorial:
http://forum.xda-developers.com/showthread.php?t=865245
But partitioning will erase everything, and is usually done after installing cwm and before flashing a rom.
You really don't want to go back to stock, especially if it's only to gain stability. All the force closes will go away when the tablet is properly formatted.
If your looking to go back to stock, I like nvflash, but there are easier ways.
http://forum.xda-developers.com/showthread.php?t=861950
Force closing is a known issue that can be easily fixed by repartitioning your internal sd card to the right specs. It has nothing to do with your newly flashed rom.
What you need to do is back up all your data on the sdcard and then go into clockworkmod advance and repartition to 2048/0.
Added by edit.
To be honest, your original post tells me the gtab isn't for you. I say a mainstream device like the ipad is more for you. Here is why. In order to use the gtab, you need to do the following things.
(1) Install clockworkmod.
(2) Use clockworkmod to repartition to fix the force closing issue.
(3) Use clockworkmod to flash a new rom.
And you're done. The entire process takes about 10 minutes at most.
Again, steps 1-3 should take you 10 minutes at most and the device is ready for use. If you find yourself frustrated by one of these steps or that you're spending more than 20 minutes, then the gtab is not for you and you need to get a mainstream device.
goodintentions said:
Again, steps 1-3 should take you 10 minutes at most and the device is ready for use. If you find yourself frustrated by one of these steps or that you're spending more than 20 minutes, then the gtab is not for you and you need to get a mainstream device.
Click to expand...
Click to collapse
This recommendation is of course assuming you have no determination whatsoever, and are incapable of learning anything new.
brettdwagner said:
This recommendation is of course assuming you have no determination whatsoever, and are incapable of learning anything new.
Click to expand...
Click to collapse
Look, for most people this device is a toy. I use it at work, and I suspect most people don't do this. Let's admit it. Modding a device isn't for everybody.
I went into modding the gtab as a total android newbie. And yet it took me all of 15 minutes to figure out how to install clockworkmod, repartition, and flash a custom rom. Then a week after I flashed a custom kernel.
You just can't ask everybody to go through the headache of modding a device if they have neither the will nor the time.
I said 15 minutes because that was my first time ever modding an android device. After that first time, it took me about 5 minutes to do my second device.
It's a simple process to go through. If a person gets stuck on any of those 3 steps, then I think it's best that they get a mainstream device. The gtab just isn't for everybody.
HeadRusch1,
I think you can handle modding the gTab. If you understand how a file system works, can extract a zip, and have already flashed a custom ROM then your about 90% of the way to a smooth running gTab. As mentioned above, you simply missed one step.
I understand the "10 minutes or forget it" argument, however I think it's wildly inaccurate when gauging a new user's potential competency with the gTab. If you find yourself frustrated then go read some more, search for a solution, or ask a question. It should take a long time to get comfortable modifying Android devices, there are tons of loosely documented best practices, but don't bail early because it's hard.
PS.
This assumes your looking for a device to tinker with. Goodintentions is right for users who are looking for iPad equivalent. I just assume that users looking for a cheap iPad rarely make it as far as XDA. And if they have, then it's a good opportunity to encourage further exploration.
The reason I gave the 20 minutes advice is because I've seen too many people buying the gtab thinking they got an ipad. The gtab isn't mainstream at all even though it's outsold a lot of the mainstream devices out there (ahem xoom) by several orders of magnitude. Customer support for the gtab is almost non-existent. And don't hold your breath for updates from viewsonic.
I absolutely love my gtab. I am currently running vegan ginger OC to 1.2ghz. The speed on my gtab is absolutely stunning. There's no jerking at all. My touchscreen is incredibly sensitive. Viewing angle has never bothered me. I love the full size usb where I can just put a memory stick in there just like my laptop. The autocad app is extremely helpful for me. In fact, it's been a whole week since I turned on my laptop.
That said, again, this device is not mainstream. Meaning it's not for most people. I am absolutely convinced that most people would be better off with something like the ipad or transformer.
Based on my experience, there are two types of people in the world of gadgets. (1) Those who sees a problem and see the end of the world and (2) those who sees a problem and try to get around it.
An example of #1 is my friend Sarah. She wanted to use my gtab to get a feel for it. She said the touchscreen bothered her and that she was more comfortable with a laptop touchpad more. And then she said "I don't know, I think I'll be better off with an ipad." LOL. Boy is she going to be so surprised to find out the ipad also uses the touchscreen rather than an touchpad.
Anyway, another example is one of my colleagues. After I told him the autocad app doesn't work with 3-D view yet, he acted like it was the end of the world. Me, I just use the side, top, and front views in my demos. Works just fine for me.
Anyway, I'm rambling now. The point is my experiences tell me most people are better off with something like an ipad or transformer. Since those devices are mainstream, people can't say "of course you can't do this, you can't do that". With the gtab, since it is not mainstream, the smallest inconvenience means the end of the world.
HeadRusch1 said:
I did one flash...to TNT version 4xx, and I loved it...but I'm finding I'm getting lots of Google Framework errors and generally just kind of want to start from scratch, over again.....go back to the latest version of the official viewsonic roms.
Sadly I didn't use clockwork or anything so I think my original files are history
I know there are lots of threads, and I tried to follow one about snagging a rom and moving it to the Root and all it does is re-install TNT I think I am "not getting something".
Can someone walk me through this....
Click to expand...
Click to collapse
Plug the gtablet into the computer.
Mount it for file transfer when prompted.
Check for an "update.zip" file at the root of the SD card (That's the tablet's 16gb internal memory). Delete it using your computer. That was causing TNT to be reloaded.
Here's the link to the original 3588 version they shipped with: http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-3588-user.zip Save it to your computer. Rename it "update.zip". Copy it to the root of the gtablet SD. Shut off the tablet. Unplug the USB cord. Restart with power & vol +
It should update.
If anyone notices a mistake, feel free to correct me. I've only flashed from stock 3588 to Vegan Ginger. So a whole 1x.
For what its worth, I tinkered and now I'm good.
Got NVFLASH working, went back to stock. Then went to Clockwork, then went to Vegan 5.1.1, then to CM7, now back to Vegan. I've found some apps that work and I'm liking it more. For the record, I own an Ipad2 as well.
Now, to those who chose to comment: You guys need to understand that many of those links are drowning in "extra information", and that is fine if you don't mind clicking hyperlink to hyperlink to do some trial and error, but now with multiple install path choices and whatnot, it gets confusing and it also means you have some time. I asked for someone, possibly someone in my shoes who has been down the path, to walk me through the steps.
Some of you did, some of you projected some assumptions with the underlying message of "RTFM".
This, too, was my first dip into the Android pool. Thanks for the help.
HeadRusch1 said:
I'm getting lots of Google Framework errors and generally just kind of want to start from scratch, over again.....go back to the latest version of the official viewsonic roms.
Sadly I didn't use clockwork or anything...
Click to expand...
Click to collapse
I had that issue and didn't have clockwork.
Solution:
1: install clockwork
2: boot into clockwork, and select 'fix permissions'.
3: reboot, tablet fixed
Just got this tablet and want to root it and install a custom rom and have some Qs so that I don't brick it.
My Android version is 2.2
Tap UI version is 1.2.4349
Kernel is 2.6.32.9-00001
Build Number is FRF91
I tried to look into the forum for some specifics but could not find them. What ROMs and Recoveries are specific to the above specs? Thanks.
First thing to note is that you are on the 1.2 bootloader. Which means that you will want to start with 1.2 based roms. Most devs indicate in which bootloader their rom works with.
Check out goodintention's howto site. Great tutorials and information.
http://viewsonic-gtablet-for-dummies.webs.com/
As already said 1.2 bootloader roms is going to be the less likely route to lead to a soft brick.
No worries .....I think it is near impossible to brick beyond repair. Search and learn nvflash.
Sent from my HERO200 using Tapatalk
brettdwagner said:
First thing to note is that you are on the 1.2 bootloader. Which means that you will want to start with 1.2 based roms. Most devs indicate in which bootloader their rom works with.
Check out goodintention's howto site. Great tutorials and information.
cool site... I've testing 1.2 ROMs and it's because of theses developers I'm G-taber today
Click to expand...
Click to collapse
here is the nice thing to remember- you don't have to be afraid to mess your device up- i remember flashing my first rom ever a few weeks ago with my heart pounding- and instantly borked my device right off the bat. nv flash is easy to use and in about 5-10 min you can have your tab right back to stock and try over no harm no foul. just follow every step. (not saying its impossible to ruin your gtab but i havent found a way yet)
dexdash said:
here is the nice thing to remember- you don't have to be afraid to mess your device up- i remember flashing my first rom ever a few weeks ago with my heart pounding- and instantly borked my device right off the bat. nv flash is easy to use and in about 5-10 min you can have your tab right back to stock and try over no harm no foul. just follow every step. (not saying its impossible to ruin your gtab but i havent found a way yet)
Click to expand...
Click to collapse
No one has found abway to completely bork their gtab, unlike noto xoom. Over at their forum, some poor ssouls have totally borked their xoom and moto won't repair or replace because warrantee was coided due to modding.
The closest anyone has gotten to soft borking their gtab was using rom manager and put their gtab into permanent apx mode. And even then there is a procedure to unbork it.
Thanks to all of you guys. I was able to follow all the steps and am now running the Vegan 2.3 ROM.
Apart from the occasional bad viewing angle, this thing really flies. A little on the heavier side but I got this for $170 brand new with the docking station so not going to complain.
This maybe a dumb question but the soft keys are not lighted?
Button Savior is your friend. Puts a small icon on the screen that when touched brings up buttons for the things the soft keys do. Its perfect for using the tab in the dark. I use it solely, I even used button remapper to disable the actual buttons.
Okay, this isn't "exactly" a noob question---I've been puttering around these boards and goofing off with my NT since December. And it's not that I "can't" find the answers on my own---my concern is that I'll find what I "think" are answers only to find out I was wrong. So, since flashing to cm7 can SERIOUSLY screw up my NT, I'm gonna go the prudent route and dot all my T's before I take the plunge.
Potentially pertinent info---my NT is currently internally rooted a la Indirect, with a 16gb card in the slot, and build modded to spoof a Nexus S. I have apps/games installed, with ebooks (read through B&N reader) and a few movies on internal memory (moved there via Root Explorer).
1) I understand that prerequisite to loading cm7, I need CWM installed. Anybody got a link to those instructions?
2) When I go to backup my stuff (via Titanium) will it back up ALL my stuff---apps, books, movies, etc---or just the apps?
The rest I can pretty much figure out myself via the pertinent threads. I ain't chicken$#!7 to mod my NT, but this thing is my LIFELINE at work (you have no idea the sheer VALUE of entertainment until you get a job as a security guard!) so I'm very cautious about anything that might have me sitting post, bored to tears because I didn't pay close enough attention or was too proud to ask a noob question
Sent from my rooted Nook Tablet using Tapatalk 8)
To install CWM (you don't necessarily HAVE to install it internally, but it is convenient), instructions are here
I believe you can set TiBU to back up anything you want. Dig around in it, set a new event and select what you want.
Books purchased through B&N will still be available to read through the B&N market app.
Don't forget to cross your i's
As a side note, Celtic is working on putting together an SDCARD version of CM7. I'm not sure exactly what the hold up is, but if you want to wait a minute, you could go that route as well and 'test the waters'
Know-Fear said:
To install CWM (you don't necessarily HAVE to install it internally, but it is convenient), instructions are here
I believe you can set TiBU to back up anything you want. Dig around in it, set a new event and select what you want.
Click to expand...
Click to collapse
Excellent! Thanks large
Books purchased through B&N will still be available to read through the B&N market app.
Click to expand...
Click to collapse
I've actually got the books all saved to my HDD---I just didn't wanna lose my bookmarks if I didn't have to.
Don't forget to cross your i's
Click to expand...
Click to collapse
Roger that
As a side note, Celtic is working on putting together an SDCARD version of CM7. I'm not sure exactly what the hold up is, but if you want to wait a minute, you could go that route as well and 'test the waters'
Click to expand...
Click to collapse
Right, and I've considered that, but when I did cm7 sd card on my wife's NC, it ran kinda sluggish, and I wanted to avoid that with my NT.
Further, when they release cm9 or cm7-Beta, I'd like to know more of what I'm doing so I can be a little less cautious
Sent from my rooted Nook Tablet using Tapatalk 8)
Once you flash cm7 I recommend installing wifi analyzer. If you end up with wifi issues it will allow you to reconnect without having to reboot. Also volume + will unleash those speakers so you can play videos and actually hear then at a reasonable volume.
As to the sdcard cm7 running sluggish, The only one I tried was a test build, and I never felt a difference at all. And I only use a class 4 sdcard (16gb). I think the NC just runs sluggish period.
Thanks a lot, guys
One more question---is ADB included in the CWM link you posted to me? If not, is it prerequisite to installing CWM?
EDIT: In the link you provided, I found another link to a CWM APK, which seems to pretty much take the guess work out of the whole deal. Guess I know what I'll be doing this weekend (gotta give myself enough time to fix this thing if I jack it up LOL)
Sent from my rooted Nook Tablet using Tapatalk 8)
nashdude said:
Thanks a lot, guys
One more question---is ADB included in the CWM link you posted to me? If not, is it prerequisite to installing CWM?
EDIT: In the link you provided, I found another link to a CWM APK, which seems to pretty much take the guess work out of the whole deal. Guess I know what I'll be doing this weekend (gotta give myself enough time to fix this thing if I jack it up LOL)
Sent from my rooted Nook Tablet using Tapatalk 8)
Click to expand...
Click to collapse
To be honest, I don't remember if it is linked there or not. You can find the ADB.exe and the adb_usb.ini needed in the nook&zergy root from Indirect. (should still be stickied in the dev section). It's been a minute, I don't remember how I actually put CWM on my NT. I have it internally installed, as well as running a copy on a CyanoBoot sdcard atm.
Ya know, I'm rooted with Indirect, so I think I may already HAVE ADB.
Cool. One less thing...
Sent from my rooted Nook Tablet using Tapatalk 8)
Hello, just picked up a couple Colors the other day for $125. + tax and my Husband has already got one up and running with CM7 booting via Sandisk SD card for my Son and it's working good however it's seems to be a little slow still. So my question is this: Is it worth paying the extra for a Nook tablet to root via SD card and is it as stable at this point booting via SD on an 8GB tablet. We don't want to take a chance of bricking anything thus the reason for sticking with the SD card method. Most of the post I ran across when searching for comarisons are older and when things were being blocked by B&N with the update. Mainly the tablet will be used for playing apps, movies, and Netflix if that makes a difference and the price difference is around $45.00 tax for the 8 GB tablet.
Also if there are ways of making the Color quicker when booting via SD card it would be very much appreciated if someone can point me in the right direction.
Thanks
Links
Tablet
https://nookdeveloper.barnesandnoble.com/product/nook-tablet-specs.html
Color
https://nookdeveloper.barnesandnoble.com/product/nook-color-specs.html
It is worth buying the tablet
VERY EASY to unbrick with a little knowlege
However:Color Development if farther than Tablet
(but at least we have Cm7 and now Cm9)
Display is the same except for
(16Gb Model) assets directory res/layout-xlarge
(8Gb Model) Assets Directory res/layout-xlarge
TABLET HAS MICROPHONE
MAIN DIFFERENCE IS SYSTEM under the links
Its also easy to not brick it if you actually read everything and ask questions when you're not sure about something instead of just "oh I guess I'll just flash this" or "this seems like a good thing to format."
Returning to stock should you ever need to, if you decide to overwrite the internal operating system or root it, is fairly easy as well.
Thanks for the advice so far. I probably should have worded the bricking part differently in my original post as as my Husband is not afraid at all of bricking it all and has already said he'd like to root it, but I on the other hand, not being very technically inclined, am afraid of bricking it.
Your advice Cubanluke88 brings up another question though. What are the main advantages of rooting either the color or tablet via emmc vs. booting them via SD card?
I'd also love to get some other opinions on the tablet vs color rooted or booted.
Thanks Again
rmnypt said:
Thanks for the advice so far. I probably should have worded the bricking part differently in my original post as as my Husband is not afraid at all of bricking it all and has already said he'd like to root it, but I on the other hand, not being very technically inclined, am afraid of bricking it.
Your advice Cubanluke88 brings up another question though. What are the main advantages of rooting either the color or tablet via emmc vs. booting them via SD card?
I'd also love to get some other opinions on the tablet vs color rooted or booted.
Thanks Again
Click to expand...
Click to collapse
I can vouch from about 6 months of experience of booting from internal now. I personally would say that booting from emmc is much more stable and fast than booting from sd. Also if youre flashing roms quite frequently its nice because the ext_sd card doesnt get wiped so you can carry over music, video and other data instead of wiping your sd every time you change what you flash. Id recommend emmc installs all the way. its super easy and i would recommend it over sd methods any day!
I decided that I'd go ahead and exchange my Nook Color tomorrow and get an 8GB tablet for myself with the idea that my Husband could eventually root it. Then I started researching here on the forum the steps to do so and from what I'm finding it looks like it's not safe to root the 8GB tablet, that rooting it will brick the 8GB but that it is perfectly safe to root the 16GB. I just want to verify this before I trade in my color. I'm a little hesitant to spend another $100 + for the 16GB tablet that will have to be rooted. I didn't mind so much going up another $35-40 for the 8GB talbet if it could be rooted but by the time I pay taxes for the 16GB, even with a Staples coupon, I'm up to the same price as the Samsung Galaxy 2 7", the upcoming google Nexus or the much anticipated, but probably not gonna happen, Asus Memo 370T.
So should I keep the color and root it with CM7 eventually since it was a pretty decent deal or is it worth spending another $100 + on The 16GB Nook tablet (if it's not possible to root the 8GB) with so many other tablets, like the ones mentioned above?
I'd love to get some opinions . . .
Thanks
The first thing we need to do is clear up "rooting."
Rooting does not mean applying a custom rom like CM7 or CM9. In fact, you don't even need to root to put a custom rom on (though rooting first does make it a bit easier."
Rooting is simply the process of gaining "root access", the linux equivalent of "administrative privileges." Applying a custom rom, a custom version of android designed for the device, otherwise referred to as "flashing" completely overwrites the internal operating system (unless you are booting from sdcard). Simply rooting will give you root access which will enable you to do things you otherwise would not be able to, but you would still have the "stock B&N operating system."
Now with that cleared up, the method to root the 8GB nook works just fine. Its flashing roms like CM7 that is a bit more work. However, booting from sdcard for CM7 works just fine on the 8GB nook.
If you look at the "How to install CM9 on the 8GB nook tablet" thread, you can find directions on how to flash CM9 to the 8GB nook. I haven't tested this as I own a 16GB, but I believe the method should work for other roms as well, at least to try them out. So you could grab the CM7 zip file and try to flash it using that method and see if it works. If not, you would just restore the backup you made prior to attempting it.
I know thats a lot of information. Do the necessary reading/ask questions before doing this stuff if its your first time.
rmnypt said:
So should I keep the color and root it with CM7 eventually since it was a pretty decent deal or is it worth spending another $100 + on The 16GB Nook tablet (if it's not possible to root the 8GB) with so many other tablets, like the ones mentioned above?
Click to expand...
Click to collapse
foolish me. . i own several tablets, but the 16GB nook is my favorite because it is zippier ( and the display is the best too )
I have 2 HDX 7". One of them shows a black screen and won't boot. When plugged into my computer (Windows 10 64-bit) it comes up under my Device Manager as Unknown USB Device (Device Descriptor Request Failed). I have tried installing the drivers and everything and anything with this one. I am not having a single solitary luck on getting it to do anything. I have read and read and read until I think my brain will explode! Does ANYONE have any suggestions on what I could do to restore this HDX please, I am getting desperate here.
My other Kindle HDX 7" is a 32GB currently running AOSPExtended. I want to get it back to the Kindle HDX 7" original stock FireOS firmware. Anyone tell me how to go about doing that PLEASE? Again I have read and just haven't found more than people saying keep it the way it is. Problem is I want to sell it and found someone to sell it but they want FireOS on it not Android.
Please ANYONE, I am really needing some help here. Don't mean to sound desperate but I am getting that way. Thanks!
alias4ever said:
I have 2 HDX 7". One of them shows a black screen and won't boot. When plugged into my computer (Windows 10 64-bit) it comes up under my Device Manager as Unknown USB Device (Device Descriptor Request Failed). I have tried installing the drivers and everything and anything with this one. I am not having a single solitary luck on getting it to do anything. I have read and read and read until I think my brain will explode! Does ANYONE have any suggestions on what I could do to restore this HDX please, I am getting desperate here.
My other Kindle HDX 7" is a 32GB currently running AOSPExtended. I want to get it back to the Kindle HDX 7" original stock FireOS firmware. Anyone tell me how to go about doing that PLEASE? Again I have read and just haven't found more than people saying keep it the way it is. Problem is I want to sell it and found someone to sell it but they want FireOS on it not Android.
Please ANYONE, I am really needing some help here. Don't mean to sound desperate but I am getting that way. Thanks!
Click to expand...
Click to collapse
- Unresponsive device may be recoverable but it will take a lot of trial/failure going through the various approaches/solutions mentioned in other unbrick threads. There is no universal 'fix' for these fussy devices when they go belly up. Your only hope is coaxing it into "bulk mode" which is tough w/o a USB connection. I'd set it aside (or sell it) for spare parts should something happen to your primary.
- Restoring FireOS v4 along with essential companion environments (recovery, bootloader) is a rough ride that should not be attempted by the inexperienced. Good chance you'll brick the little fella or end up with a FrankenKindle that does noting well. Convince the buyer AEX (or any of the Nougat based ROMs) is a much better option. Not being a nerd here; I generally prefer/run the stock ROM on all my handheld gizmo's. Amazon devices are the notable exception with 3rd gen HDX being especially hard to restore once unlocked/rooted.
Davey126 said:
- Unresponsive device may be recoverable but it will take a lot of trial/failure going through the various approaches/solutions mentioned in other unbrick threads. There is no universal 'fix' for these fussy devices when they go belly up. Your only hope is coaxing it into "bulk mode" which is tough w/o a USB connection. I'd set it aside (or sell it) for spare parts should something happen to your primary.
- Restoring FireOS v4 along with essential companion environments (recovery, bootloader) is a rough ride that should not be attempted by the inexperienced. Good chance you'll brick the little fella or end up with a FrankenKindle that does noting well. Convince the buyer AEX (or any of the Nougat based ROMs) is a much better option. Not being a nerd here; I generally prefer/run the stock ROM on all my handheld gizmo's. Amazon devices are the notable exception with 3rd gen HDX being especially hard to restore once unlocked/rooted.
Click to expand...
Click to collapse
I get that recovering a bricked HDX is not going to be easy. I have read so much I am on overload. I am a mother of 5 kids (one of them is 3 years old) and I have spent every little extra minute (which has been hard I'll admit) reading as much as I possibly can for the last several weeks. I am not totally stupid when it comes to doing things with a computer and I don't mind trying things over and over again. I am trying to get it fixed for my kids to have something to play with.
I am just hoping SOMEONE can just help me out in what specifically to try or suggestions or where to start. Someone that has had the same problems I've got. [emoji39] I would be so very eternally grateful. Again I know it isn't easy I already knew that and don't need to be told that again and again.
I have always enjoyed xda and all the help I've ever gotten on all my devices so hopefully someone can help me out with this one.
Thanks all.
Sent from my [device_name] using XDA-Developers Legacy app
Anyone help me please? I would really love some help if possible.
alias4ever said:
Anyone help me please? I would really love some help if possible.
Click to expand...
Click to collapse
The brickled kindle just stopped working alone? noone try to do something weird or install some strange app?
If the answer its yes,probably its a hardware issue, there nothing to do with physical hardware to make a diagnostic.
For the other case, you can install a FireOS modded version to run with TWRP
https://forum.xda-developers.com/ki...nt/twrp-flashable-stock-images-t3194914/page8
I hope someone could upload 4.5.5.3, 4.5.5 had some bugs, the keyboard type speed becomes so slow at the end of the day,you need reboot the tablet every day to recover the smoothness of the keyboard, sometimes i got some reboots (4-5 since i installed it), this never happened on lastest version.
Yousucks2 said:
The brickled kindle just stopped working alone? noone try to do something weird or install some strange app?
If the answer its yes,probably its a hardware issue, there nothing to do with physical hardware to make a diagnostic.
For the other case, you can install a FireOS modded version to run with TWRP
https://forum.xda-developers.com/ki...nt/twrp-flashable-stock-images-t3194914/page8
I hope someone could upload 4.5.5.3, 4.5.5 had some bugs, the keyboard type speed becomes so slow at the end of the day,you need reboot the tablet every day to recover the smoothness of the keyboard, sometimes i got some reboots (4-5 since i installed it), this never happened on lastest version.
Click to expand...
Click to collapse
The bricked kindle I am not sure on. I got it from a friend of mine who said all she did was an update and then it just wouldn't boot anymore. I have heard that sometimes Amazon updates have bricked some...I am going to see about taking it apart to make sure everything is plugged in and what not.
As for the FireOS where can I find 4.5.5.3 do you know? I would love it for both the 8.9 and 7" HDX. Thanks so much for all your help I am forever grateful. :good:
alias4ever said:
The bricked kindle I am not sure on. I got it from a friend of mine who said all she did was an update and then it just wouldn't boot anymore. I have heard that sometimes Amazon updates have bricked some...I am going to see about taking it apart to make sure everything is plugged in and what not.
As for the FireOS where can I find 4.5.5.3 do you know? I would love it for both the 8.9 and 7" HDX. Thanks so much for all your help I am forever grateful. :good:
Click to expand...
Click to collapse
Check this thread for FireOS TWRP Flashable Images, you can flash it like other rom's with twrp , you dont worry for OTA updates because its disabled
https://forum.xda-developers.com/kindle-fire-hdx/development/twrp-flashable-stock-images-t3194914
unfortunately the only image available is 4.5.5 ,almost the same as 4.5.5.3 but in my experience , had some minor bugs
For the bricked kindle, its almost impossible to recover without ADB access a.k.a USB Conectivity for run some programs to get access to the file system and procede to repair it (not apply in all cases), sadly Amazon Fire's isnt user friendly for homemade repairs, best choice is replace the motherboard or get another one.
I dont know if amazon keep provide support for our old fire hdx's, in the case she wanna repair( paying for it), ,probably not.