Database Users

[WIFI Only] [How-to] GT-P1010 Gingerbread Update

I know a lot of people are going to have problems updating to the latest gingerbread build.
PLEASE NOTE: This update will remove root but you can root again with CF-Root from second post.
ALSO, THIS PROCESS WILL WIPE DEVICE!
1) Put your P1010 into download mode (by holding POWER and VOL-DOWN):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2)I went ahead and used ODIN tool to downgrade/upgrade to the latest FROYO firmware before Gingerbread:
P1010XWKC1_OXX
(OEM Flash Guide here)
You should have the same tick marks and files loaded as in my screenshot. Be sure that the box is yellow on the right and you can initiate the firmware install by clicking 'Start'.
3) (VARIES) From there, after restart some people will experience a force close followed by a reboot loop. You will need to flash this kernel via ODIN:
P1010ZHKF1-kernel
(Flash this the same way as above but UNCHECK Re-Partition and CSC!)
4) You will then be able to boot into Froyo.
5) You will use ODIN again to install the Gingerbread update and flash just the PDA (leave CSC blank and leave Re-partition unchecked this time).
P1010XEUKPG
(Flash this the same way you flashed the Kernel in step #2)
6) After it reboots, you will have 2.3.6
7) (Optional) steps in post #2 to install CWM Recovery and Root.

I recommend installing CWM Recovery and CFRoot in the thread below:
ClockWorkMod Recovery for P1010
After you install CWM Recovery, you can do a nandroid backup and never worry about brick again! (=
Also, you can use ES Explorer to mount root and get rid of the Samsung bloatware (AT YOUR OWN RISK!!!)

For those wanting to remove the bloatware (AT YOUR OWN RISK!!!):
You can remove the bloatware with ES Explorer, there's an option to enable 'Root Explorer'. Download the latest version from the Market.
See below:
screenshots are from my Galaxy Nexus but it's the same for any Android 2.2+.
1) Go to the 'Settings' screen
2) Change home directory to '/'
3) Tick the 2 marks on the bottom
4) Browse to /system/app
5) Delete whichever app you don't want, but do it with caution (I usually move these files to /sdcard and move back if it causes any type of force close)
If you totally borked out the system in such a way that you can't boot, you can always move it back in recovery via ADB (much more complicated process but it's possible).
Also, why not do a nandroid backup before messing with deep system files?

Nice! Great topic.

Updated op! =)

this is the best christmas present so far.
edit: worked, almost. thanks ! rooted flashing Skin1980-CF-ROOT-P1010-BETA.tar .
skype isn't using the front camera. =s

Is this for any p1010? Will this work for us models?
Sent from my HTC Flyer P510e using XDA App

r_3 said:
Is this for any p1010? Will this work for us models?
Sent from my HTC Flyer P510e using XDA App
Click to expand...
Click to collapse
It's THE EU ROM but it works with my US P1010.

No restart issues?

r_3 said:
No restart issues?
Click to expand...
Click to collapse
If you followed those steps, the ROM runs stable without any FC's or reboots. I even have setCPU installed on mine.
Also, it's good to note that I'm running CF-Root kernel from the thread in 2nd post.
Plus, you could always downgrade if you run into issues. Just remember to always BACKUP YOUR DATA!

nice!
wow this is good news! does this modded skype work on this: http://forum.xda-developers.com/showpost.php?p=16889575&postcount=1262
or
http://forum.xda-developers.com/showpost.php?p=20697907&postcount=1640
?
I cant try it now as I'm not home. I hope someone could try as so I won't have to think about it until I get home..

@blue_algae: neither the front or the back camera works. tried v11 and v12. so far no luck

densets said:
@blue_algae: neither the front or the back camera works. tried v11 and v12. so far no luck
Click to expand...
Click to collapse
Could you attach the logcat here? or if you could send it directly to theos0o, that'll be great. he's the modder of the skype apps I pasted above.
could you also try this: http://forum.xda-developers.com/showthread.php?t=1153285 this works for me using froyo.

im getting excited about this.. is it really for the p1010 wifi only device? because from what i can see in this subforum is the devs working on the p1000 only. another thing, please don't tell me this is an official update. i don't think the bad sammy will update this little tab.

Depending on where you are freon yes it its the official ireland uk update and makes massive difference as well
Much better tab.
Sent from my GT-P1010 using Tapatalk

skype is working
@densets, skype is working for both skype mods I posted earlier. you just need to enable 'use valid preview'. for droidrx's version, set the app to 'crop' so your video is centered.

phew.. relieved by this news, nevermind if it is not going to be released here in malaysia, at least i can still skype with my family w/o much trouble into getting the ffc to work.

urra901109 said:
phew.. relieved by this news, nevermind if it is not going to be released here in malaysia, at least i can still skype with my family w/o much trouble into getting the ffc to work.
Click to expand...
Click to collapse
hmm, if you are still in froyo, you can use ffc on skype: http://forum.xda-developers.com/showthread.php?t=1153285
just rotate the camera and try out different settings.

sorry for the newbie question, but what's the password for the 2.3.3 file from sammobile?
edit: already found it, my bad

Interestingly, I've followed the guide exactly as mentioned above (had KC1 and the HK kernel from previous flashing) and flashed the PDA for XEU 2.3 from Sammobile, and I'm now stuck in an eternal bootloop. I like the new samsung boot music though, better than the previous one
Any suggestions?
Edit: I wiped data and cache from recovery, flashed KC1 and the Kernel and it boots fine. Checked Kies to be sure and it's offering me FW upgrade to KM2. Should I accept this FW upgrade or just persevere with flashing the new 2.3 firmware?

Bricked my Kindle "/system/bin/sh failed"

I tried the new partition utility found in this section and I got an error from the sdcard portion, so it moved on to partitioning data but all it did was freeze and eventually I was stuck so I unplugged it. I managed to get back to TWRP and install the 6.2.1 update.zip but after I installed it I am stuck at the notorious "Your Kindle has detected a problem" screen and I can't get past it. I've tried KFU to boot into normal mode or even fastboot but I am stuck with the <waiting for device> message. I looked into it more and found this thread here:
http://forum.xda-developers.com/showthread.php?t=1414832
However, I can't get past the first command because I get this message:
exec '/system/bin/sh' failed: no such file or directory (2)
So I can't get anywhere without an error or waiting for device message, am I screwed or is there a way to fix this? ADB is working from what I can tell because reboot and similar commands work just fine, I think the partition just needs to be fixed. However when I click on Kindle properties in Device Manager I get this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please help me guys, I don't want to have to send this thing back or have to get a factory cable.

I think you're screwed. Same thing happened to me. Had to send it back
Sent from my Galaxy Nexus using XDA App

I had the same issue and got it to boot by repartitioning it by hand and then installing the kindle 6.2.1 update. Now I am back up and running.

Did the same to mine earlier.
I followed the advice of Pokey9000 who referred to his thread.....
http://forum.xda-developers.com/showthread.php?t=1369405
You'll need to reflash at the end of this but it's defintely not bricked.

dnathan13 said:
I had the same issue and got it to boot by repartitioning it by hand and then installing the kindle 6.2.1 update. Now I am back up and running.
Click to expand...
Click to collapse
Can you explain how you did that?
The problem is that I can't get FFF or TWRP installed since I did a fresh install of 6.2.1.

Well nevermind guys I'm not gonna even bother with this. I contacted Amazon and I'm getting a new KF sent here in 2 days.

I also have a similar problem. I used TWRP to wipe everything and reflash the stock 6.2.1. Now I get the "exec '/system/bin/sh' failed: no such file or directory (2)" error. Everything I've found to fix the problem requires the shell and I can't use it. The Kindle never mounts in Windows either.

Those are the exact same issues I'm having. Oh well, I'm getting a new one and won't be messing with partitioning anymore.

The problem here is that you screwed your kindle and instead of doing the work to unscrew yourself you are sending it back to Amazon. All your doing is giving Amazon more reason to lock us out of the Kindle. They don't want to be taking back equipment that you ruined.
It's because of this kind of stuff that we are constantly fighting to get root on our devices. If you root your device and soft brick it you shouldn't send it back to the manufacturer. Do us all a favor and when you get your new KF, do not root it.

This is why company's hate root. If you cant take the time to fix your kindle after you f*** something up then don't root it.
edit: haha same post above me

I like how you guys say that when there is no real solution to solve this problem.
I got my new KF a day early. I sure won't be messing with partitioning again.

how do you partition by hand

There is a way, people have come back from completely wiping out the partition table on their kindle, I just can't find the post on how they did it. If you look in the custom kernel thread awhile back, the kernel had a glitch and caused some kindles to wipe out all partitions. So you can come back from it, just it hasn't happened to many people.
Edit: I believe you could have made it back using some form of this guide. http://forum.xda-developers.com/showthread.php?t=1388996&highlight=partition , but I'm not well versed enough in doing all this crap.
Edit again: If theres no real solution then you should be SOL, its not amazons fault you messed something up so badly on your kindle its unrecoverable. So yes, I will say that even if there is no solution.

Matt V said:
Well nevermind guys I'm not gonna even bother with this. I contacted Amazon and I'm getting a new KF sent here in 2 days.
Click to expand...
Click to collapse
Wow, you suck at life. Thanks for being part of the reason people want to stop us rooting. You have no idea what you are doing so you send it back and make amazon eat it. You didn't even try to fix it.

Video TUTORIAL: How to Root your Galaxy Tab 8.9 and Install Clockwork Recovery

Hi Guys,
I made a small video tutorial on how to root the galaxy tab 8.9 (GT-P7310/P7300 ONLY) and how to install clockworkrecovery on it based on some tutorials that I came across here.
The video might be helpful to someone.
Credit to mramirezusa and alterbridge86.
ROOT:
http://www.youtube.com/watch?v=gh9KVGUBm6o
CWM:
http://www.youtube.com/watch?v=FZzNY9lFGQM
Thanks for watchin.
Cursed4Eva

Thanks good video's i will root my tab now
Sent from my HTC Desire HD A9191 using XDA App

fase said:
Thanks good video's i will root my tab now
Sent from my HTC Desire HD A9191 using XDA App
Click to expand...
Click to collapse
Glad to help bro Let me know how it goes

ashwin123 said:
Hi Guys,
I made a small video tutorial on how to root the galaxy tab 8.9 (GT-P7310/P7300 ONLY) and how to install clockworkrecovery on it based on some tutorials that I came across here.
Cursed4Eva
Click to expand...
Click to collapse
Thanks for video, it is clear and I am now more comfortable to root.
However, I have one question. Is it really necessary to install Samsung Kies? I have installed the Kies software but failed to connect to Tab. I called Samsung service center and still cannot resolve the fail connect issue (I had tried connect to different USB ports). From the video, the purpose of the kies is seems to allow to copy the root.zip file to tab. Am I right? Thanks.

yongck7 said:
Thanks for video, it is clear and I am now more comfortable to root.
However, I have one question. Is it really necessary to install Samsung Kies? I have installed the Kies software but failed to connect to Tab. I called Samsung service center and still cannot resolve the fail connect issue (I had tried connect to different USB ports). From the video, the purpose of the kies is seems to allow to copy the root.zip file to tab. Am I right? Thanks.
Click to expand...
Click to collapse
Glad to help bro.
As for kies, no it is required so that odin is able to detect the phone, kies installs the required drivers to send out the commands to the device so that the firmware can get flashed, it is mandatory to install it
Hope I helped

ashwin123 said:
Glad to help bro.
As for kies, no it is required so that odin is able to detect the phone, kies installs the required drivers to send out the commands to the device so that the firmware can get flashed, it is mandatory to install it
Hope I helped
Click to expand...
Click to collapse
Thanks. So we have to ensure Kies work properly (able to connect Tab) in order to successfully root, else there is potential soft brick, right?

yongck7 said:
Thanks. So we have to ensure Kies work properly (able to connect Tab) in order to successfully root, else there is potential soft brick, right?
Click to expand...
Click to collapse
Without kies installing the drivers, odin will not detect your device... this is as per knowledge, someone please correct me if am wrong

ashwin123 said:
Without kies installing the drivers, odin will not detect your device... this is as per knowledge, someone please correct me if am wrong
Click to expand...
Click to collapse
No Kies needed for drivers, just go here and download the drivers (tried them myself and they're in my guide too, no complaints so far).

nirogu325 said:
No Kies needed for drivers, just go here and download the drivers (tried them myself and they're in my guide too, no complaints so far).
Click to expand...
Click to collapse
Okay thanks, kies does the same thing too right? (but its larger.... i understand)

ashwin123 said:
Okay thanks, kies does the same thing too right? (but its larger.... i understand)
Click to expand...
Click to collapse
That and sometimes brick devices. Me and a lot of people don't trust that thing.

nirogu325 said:
That and sometimes brick devices. Me and a lot of people don't trust that thing.
Click to expand...
Click to collapse
Okie dokie, future vids will have this instead of kies... R.I.P Kies

Hope this thread isn't abandoned, I rooted by the video, everything went smoothly, went to play store & installed superuser. Installed fine, opened it, seemed normal. Then I figured I'd test it out by installing adfree. The popup box for permission never popped up & I get the force close or report box for superuser. Have not installed cwm recovery yet. Please help, & thank you
Sent from my PC36100 using Xparent Blue Tapatalk 2

aheeejd said:
Hope this thread isn't abandoned, I rooted by the video, everything went smoothly, went to play store & installed superuser. Installed fine, opened it, seemed normal. Then I figured I'd test it out by installing adfree. The popup box for permission never popped up & I get the force close or report box for superuser. Have not installed cwm recovery yet. Please help, & thank you
Sent from my PC36100 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Reboot the device, install titanium backup, get busybox, let me know what happens bro

Thanks for getting back man. Well I put basically the same post in like 3 threads. So anyway, I ended up basically rerooting it with the tool package from one of the other threads, without using keis. It worked fine, flashed cwm recovery & already on my 3rd rom. First I flashed cm9. But am so used to that on my HTC Evo 4g. Second, flashed the aokp & galaxian soup one. This morning flashed just galaxian soup. Thanks again man.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my PC36100 using Xparent Blue Tapatalk 2

Tab does not go n recovery mode. Black screen instead
I have read the instructions about rooting en installing CWM carefully. The movies are very clear to me.
But....when I restart the Tab with Power and volume - I get the Box with the little Android symbol and the big Android with Downloading Symbol.
I select with volume - the box with little Android and select this with the volume +
The result is that the Tab shuts off instead of going in recovery mode. What am I doing wrong. I have seen this question in some other topics of this forum but never find a good solution.
I already did a factory reset, but that did not help. I am on ANDROID 3.2
Who is willing to help. Thanks

Does this method work if i upgraded to ics via kies?

I wanted to do this with my gf's p7300 but when i choose the recovery the screen stays blank.
Why is that.?
I haven't done anything else with the tab yet only update samsung to 3.2.
Verstuurd van mijn Transformer Prime TF201

No SD card option
Hi,
I just wanted to root my Galaxy Tab 8.9 but don't have the option of SD card in the Android menu. See attached files with screenshots.
On a high note... I tried to flash a custom ROM on Sunday and kinda softbricked the device. After getting it back today from the store I don't want to screw it up again...
Any ideas what I need to do?
Thank you!

sobits said:
Hi,
I just wanted to root my Galaxy Tab 8.9 but don't have the option of SD card in the Android menu. See attached files with screenshots.
On a high note... I tried to flash a custom ROM on Sunday and kinda softbricked the device. After getting it back today from the store I don't want to screw it up again...
Any ideas what I need to do?
Thank you!
Click to expand...
Click to collapse
Seems that you have official 4.0.4 now. You need to install CWM/TWRP before installing root zip.

DemonGloom said:
Seems that you have official 4.0.4 now. You need to install CWM/TWRP before installing root zip.
Click to expand...
Click to collapse
Hi. Thanks for the reply. But how to Flash CWM in the original bootloader when the SD is inaccessible as in the pic? Is there a possibility to flash CWM safely through Odin? Sorry for so many newb questions ; after the softbrick I am overly cautious.
Sent from my GT-P7300 using xda app-developers app

Unable to install 4.2.2 upodate

I have clockworkmod recovery installed and when I install the update it fails. Cannot remember the error sorry. Why is this happening. Here is a screenshot my about phone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 7 using xda app-developers app

Here is the error I am getting.
sent from my nexus 4 using google mind control

The OTA installer checks every single file it intends to patch before anything happens.
If a single file that is checked has been changed by even one byte, not one patch operation will occur.
The message you are getting means you did something to change or remove that file compared to how it was in the stock ROM.
Note that the installer halts on the first error of this type; there could be zero or many more of these errors awaiting you.
In short, OTAs are not meant for patching random non-Stock ROMs.

I installed beats from play store. Gutted. Just backing up all my data and gonna factory reset and try again
sent from my nexus 4 using google mind control

R: Unable to install 4.2.2 upodate
I had error 7 with TWRP recovery. Then I installed clockworkmod and it worked.
Nexus 7 3G - Tapatalk

Androll79 said:
I have clockworkmod recovery installed and when I install the update it fails. Cannot remember the error sorry. Why is this happening. Here is a screenshot my about phoneView attachment 1728828
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
i have the same problem.but i flash stock recovery with WugFresh toolkit and wait until OTA update notification.and you will get your android running 4.2.2 version.

Odp: Unable to install 4.2.2 upodate
Guys, guys, guys. You need STOCK recovery for official updates.
Sent from my BMW E34 using XDA App

I searched many threads when I rooted and unlocked my Nexus 7 3g, to avoid this "status 7" problem.
I chose Wug´s nexus toolkit, unlocked and rooted my device. After that, I installed, via toolkit, the TWRP recovery.
When I received the system update notification, my device asked me to reboot, then a screen of TWRP appeared to me. I just rebooted the system and now, without update, I don´t even get the message again.
I assume that the Wug´s toolkit flashed a grouper version of TWRP. What I have to do now ? I would like to do the things manually. Maybe flash a factory image from here with this method.
I´m very noob with this kind of thing, because I still have a old milestone 2 with a locked bootloader. The method to flash ROM in milestone 2 is quite different...
Anybody can help me ?

There is modified OTA floating somewhere that skips check, worked for me since it reported that GoogleCalendar.apk was different than it should be....

Folks,
You need to stare at the actual error message.
If the failed assert() is complaining about a file (e.g. see the OP's 2nd image attachment) then THAT FILE IS THE PROBLEM. It means that it was altered or removed by a root-privileged operator from the way it was in the stock ROM.
If the failed assert is complaining about a build number, then it is possible that using a different recovery will allow the OTA to succeed.
So you have a couple of choices:
A) Go and find the stock version of the file and put it back into your ROM (with the correct file ownership and permission modes) and repeat the OTA install. Seems like a dumb idea though, as the installer stops on the first error encountered - you will need to keep repeating this process until you have restored all changed files. Could be only one file, could be a few, could be many. Note also that this applies to the boot image, too. Got a custom kernel? You'll need to put the stock boot image back in place, too.
B) Back up your apps using TiB or Carbon. While you are at it, take a nandroid backup too. Install the Factory 4.2.2 ROM, reinstall your fave custom recovery, and root the factory ROM. Boot it up, enter your Google creds, restore your apps & data (Carbon or TiB). Yep, you are gonna have to redo your homescreens. Big deal; that's something you would do anyway when hopping between ROMs (unless you have this covered already by using a non-stock Home/Launcher app which has its' own backup/restore capability)
C) Just wait a little bit - your ROM Dev will probably release a version based on 4.2.2. At that time you can do some stupid thing like overflashing the replacement ROM without wiping.
Unless you know exactly what you are doing, running a modified OTA with *all checks* suppressed is a seriously brain-dead idea. (Removing only the build version check should allow alternate recovery use - but for goodness sake, the OTA nukes the recovery anyway, so what's the big deal about putting the 4.2.1 stock recovery back in place ahead of the OTA?)
Look, running the Stock OTA is going to remove your recovery and very likely disable your root. You are going to need to put your recovery back and re-root anyway. Doing things the right way is barely more effort than what you are going to need to do the crufty way.
good luck

finally ROOTED Fire 5th Generation 5.3.3.0 ( NO BRICKING ) easy and simple

Hey, i figured a simple way to root the fire tablet. All you have to do is flash the super su zip. That's it. Ladies and Gentlemen. :good::good::good: just rooted mine and few others people tablet and having the time of our life.
Horridhenry said:
I fully understand the confusion that my thread created. And also I am sorry for the little amount of information given by me on first place.
-- My tablet was running on the latest update, however after bricking it while ago I had to reset my tablet using the cmd.
And when it booted, i never connected to the wifi.
I took Super-Su.zip and converted into .tar ( i decided to take a bit risk, if it went wrong, just reset it again.)
Turned the tablet off and used the volume down and power at same time.
---- oh yeah, I used Motorola unlocked bootloader method and applied/modified to fire os. ----
After, Odin just recognized my tablet as a different device or something else - ID:COM53
Flashed the super-su.tar and surprisingly it work. It's like changing .apk to .doc so you can send on whatsapp but change .doc to .apk and it becomes .apk aging. Do you understand that. You Can Try Out With Your Whatsapp.
That's it. Hope it help you,
Also shout out to @DragonFire1024 and Davey126
for their optimistic and confident about the future of bringing back root to the very amazing Fire 5th Generation.
Click to expand...
Click to collapse

Horridhenry said:
Hey, i figured a simple way to root the fire tablet. All you have to do is flash the super su zip. That's it. Ladies and Gentlemen. :good::good::good: just rooted mine and few others people tablet and having the time of our life.
Click to expand...
Click to collapse
How exactly do you accomplish this without a custom recovery? Last I knew FlashFire will not run on an unrooted device. Are you able to boot TWRP from fastboot w/FireOS 5.3.3.0?

Davey126 said:
How exactly do you accomplish this without a custom recovery? Last I knew FlashFire will not run on an unrooted device. Are you able to boot TWRP from fastboot w/FireOS 5.3.3.0?
Click to expand...
Click to collapse
No, i press volume down and power button sametime to go download mode

Horridhenry said:
No, i press volume down and power button sametime to go download mode
Click to expand...
Click to collapse
Whoa! If this operation is independently confirmed it represents a serious vulnerability that Amazon will almost certainly patch.
Assuming device is running 5.3.3.x bootloader (you would know it if not).

Davey126 said:
Whoa! If this operation is independently confirmed it represents a serious vulnerability that Amazon will almost certainly patch.
Assuming device is running 5.3.3.x bootloader (you would know it if not).
Click to expand...
Click to collapse
it has nothing to do with bootloader or anything. just simple - go to download mode like you would on any device, connect odin and flash. that's it my g

Horridhenry said:
it has nothing to do with bootloader or anything. just simple - go to download mode like you would on any device, connect odin and flash. that's it my g
Click to expand...
Click to collapse
Cautiously optimistic. Still waiting for independent confirmation (all of my devices have a vulnerable bootloader so are non-representative of the community). Which SuperSU build? May not matter aside from matching your bench config.
Many locked Amazon devices do not offer a 'standard' download mode...either crippled or not accessible. That's what makes your finding so curious and possibly bootloader version dependent.

Did you use an app like Activity Launcher? I couldn't find the download mode in there. And it lists pretty much every setting whether you have root or not. Doesn't mean you can access them or change them. I am on a fire HD 8 at the moment with 5.3.3.0

Horridhenry said:
Hey, i figured a simple way to root the fire tablet. All you have to do is flash the super su zip. That's it. Ladies and Gentlemen. :good::good::good: just rooted mine and few others people tablet and having the time of our life.
Click to expand...
Click to collapse
It cannot be that simple.
Any proves?

DragonFire1024 said:
Did you use an app like Activity Launcher? I couldn't find the download mode in there. And it lists pretty much every setting whether you have root or not. Doesn't mean you can access them or change them. I am on a fire HD 8 at the moment with 5.3.3.0
Click to expand...
Click to collapse
On most Android devices so called 'download mode' is invoked via <power>+<vol+down> from a cold start. Has nothing to do with ROM functionality.

Davey126 said:
On most Android devices so called 'download mode' is invoked via <power>+<vol+down> from a cold start. Has nothing to do with ROM functionality.
Click to expand...
Click to collapse
Was a dumb question. I just found that out. With that said, I thought you couldn't flash anything, even with root? I thought If the bootloader is locked, flash is not possible?

tonibm19 said:
It cannot be that simple.
Any proves?
Click to expand...
Click to collapse
OP claims to have used Odin (leaked Samsung utility; not ChainFire's Mobile Odin) to flash SuperSU on a 5th gen device in download mode. This is quite plausible and a remarkable security oversight by Amazon if independently confirmed. Has significant ramifications aside from rooting FireOS 5.3.3.0.
Not sure it would work on a HD8; depends if bootloader vulnerability exists there to.

Davey126 said:
On most Android devices so called 'download mode' is invoked via <power>+<vol+down> from a cold start. Has nothing to do with ROM functionality.
Click to expand...
Click to collapse
When powered off, volume down + power does nothing. Volume up + power puts me into Amazon System recovery.

DragonFire1024 said:
When powered off, volume down + power does nothing. Volume up + power puts me into Amazon System recovery.
Click to expand...
Click to collapse
Yes - this is the typical scenario on a 'locked down' Amazon device. OP may have an alternative method for entering download mode. Or it may work differently on 5th gen fire devices (as I recall you have a 6th gen HD8). Waiting for independent confirmation.
As previously noted all of my 5th gen devices have a vulnerable bootloader and happily drop into download/fastboot mode...hence I can not validate OP's claims.

Davey126 said:
Yes - this is the typical scenario on a 'locked down' Amazon device. OP may have an alternative method for entering download mode. Or it may work differently on 5th gen fire devices (as I recall you have a 6th gen HD8). Waiting for independent confirmation.
As previously noted all of my 5th gen devices have a vulnerable bootloader and happily drop into download/fastboot mode...hence I can not validate OP's claims.
Click to expand...
Click to collapse
I've downloaded Odin onto my PC and installed Samsung drivers. However I can't get Odin to recognize my device.

Willing to give this a shot here. However I still can't get Odin to recognize my tablet. Lets say I do, according to everything I am reading, in order to root through Odin, you need to download the proper CF-Auto-root file. What one did the OP use?

DragonFire1024 said:
Willing to give this a shot here. However I still can't get Odin to recognize my tablet. Lets say I do, according to everything I am reading, in order to root through Odin, you need to download the proper CF-Auto-root file. What one did the OP use?
Click to expand...
Click to collapse
I agree there is a big lack of instructions here.

Maybe this is nothing, but I just noticed the 1st generation Fires were named 'otter.' My fire HD 8 is also an otter. Not sure if that's at all significant.
EDIT: There is a There is a TWRP file for the 1st generation Fire...named otter.

DragonFire1024 said:
Maybe this is nothing, but I just noticed the 1st generation Fires were named 'otter.' My fire HD 8 is also an otter. Not sure if that's at all significant.
EDIT: There is a There is a TWRP file for the 1st generation Fire...named otter.
Click to expand...
Click to collapse
- 5th gen HD 8 codename = Memphis
- 6th gen HD 8 codename = Gi
- TTBOMK Amazon codenames are not reused (never see it)

Davey126 said:
- 5th gen HD 8 codename = Memphis
- 6th gen HD 8 codename = Gi
- TTBOMK Amazon codenames are not reused (never see it)
Click to expand...
Click to collapse
I've never seen it either. I just happened to see an activity with 'otter.' Third from the bottom in the below image:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also...who or what is amazon.jackson19?
(I can't figure out how to resize a picture for here. Please see second screen shot below)

DragonFire1024 said:
I've never seen it either. I just happened to see an activity with 'otter.' Third from the bottom in the below image:
Also...who or what is amazon.jackson19?
Click to expand...
Click to collapse
Unknown; lots of little mysteries with FireOS.