Database Users

[A70B/IT2 HC][3.2.81 update] Enabling SDE and rooted firmware package

First:
Warning! This is only for A70B/A70IT2 Honeycomb model, It won't work on Froyo model!
Here is a package that enables unofficially SDE menu in recovery and install a rooted stock firmware with busybox and SuperUser.Apk
Pre-Requisite:
- Adb must be enabled on tablet and PC driver+adb command must be working. You can test on pc with "adb shell", it should give you a '$' prompt. If you don't have this, first make it work. There are multiple links around to help if needed.
Instructions:
- Unzip files on your pc in adb.exe directory.
- Launch enable_sde.bat on your pc. It's better to do it in a cmd.exe window, you'll be able to copy-paste log here if anything goes wrong.
- Follow instructions in the cmd window. Basically, script reboots tablet multiple times, you have to press enter when tablet is completely booted each time.
- Congratulation, your device is sde enabled and has a rooted sde firmware. Please read below for more information.
Upgrades:
If you already installed a first version and enabled sde already, here is how to install new rooted firmware:
- Optional: flash updated stock firmware. I always recommend to match stock firmware, it avoids dalvik-cache rebuilds and bootloaders may have been updated in new firmwares.
- Boot rooted firmware. You should be running rooted firmware if you want upgrade script to work. To be sure of that, you should see SuperUser app in your apps menu.
- Unzip files on your pc in adb.exe directory
- Launch upgrade.bat (or upgrade.sh for linux)
- Tablet reboots at the end to rooted firmware and should be upgraded to new version.
SDE information:
1) What is SDE?
SDE (Special Developer Edition) is basically a dual boot mechanism. It allows us to dual boot Archos stock firmware and our custom ones.
2) How does it work ?
I won't give much details on how to use it, I should do a separate topic about this one someday. Until then, here is some basic information:
- At the end of this script, you are booted with sde firmware, superuser should be in your start menu and you should be root with adb or any root app.
- If you reboot or boot, press volume up while booting, it will display the dual boot menu. Select "Developer Edition", it will start the rooted build (check here point 9 to see how it looks).
- If you missed volume key or don't do anything during reboot, you will go back to unrooted stock firmware. You have to press the volume up key during boot to get the boot menu.
- Warning: booting stock firmware is harmless except that you will loose your SuperUser.apk preferences. As it's not part of stock firmware, Android clears it.
- You can boot straight to rooted firmware by deleting the stock firmware kernel in recovery. Check here, do point 4,5, and on screen 6, select "Remove Android Kernel". Make sure that you have properly working SDE firmware before doing that. If you want to re-enable back stock firmware, just flash it from recovery again.
Downloads:
3.2.80 can be downloaded here: Mirror 1 (Mediafire), Mirror 2 (Sendspace).
3.2.81 can be downloaded here: Mirror 1 (SendSpace) (bat fixed)
Sorry, Mediafire no longer let me upload without signup, if you know one good upload location without registration and allowing more than 200 MB, let me know.

*reserved*

Registered just to say thank you!
Worked like a charm, and no problems using the shell script (I run Arch Linux)
Keep up the good work!

Thanks
I mean real thanks
Sent from my ARCHOS 70it2 using xda premium
EDIT:
Beautiful man, beautiful. Works splendidly
Thanks again

LeTama
Have a beer or two on me, 84G89322WT2139701.
Thanks again for your Rom.

Hi mrew42,
Thanks a lot! Much appreciated!

Tomorrow, my 70b return at home
I testing that !
but my 70bit2 is with 3.2.81

Letama, can you may be make the same for 3.2.81?

Yes, it will come soon...

3.2.81 is up and instructions on first post updated if you upgrade.

Great
http://www.jbmm.fr/?p=27601
{
"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"
}

cajl said:
Great
Click to expand...
Click to collapse
Nice job! Thanks for the article on jbmm!

Thanks, will try it out soon.

Thanks letama, this is just what I wanted. Awsome work!
I think there is an error in upgrade.bat and enable_sde.bat for 3.2.81.
The line that reads:
adb push android_32.ext4.update /media/
should read:
adb push android_32.ext4.update /data/media/
Also, upgrade.bat is missing the line that says:
adb shell rm /data/local.prop
Keep up the good work and thanks again.

ColinTaylor said:
I think there is an error in upgrade.bat and enable_sde.bat for 3.2.81.
The line that reads:
adb push android_32.ext4.update /media/
should read:
adb push android_32.ext4.update /data/media/
Click to expand...
Click to collapse
Ah! Right! Thanks for pointing it, I'll fix that and re-upload when I find time to do it.
Also, upgrade.bat is missing the line that says:
adb shell rm /data/local.prop
Click to expand...
Click to collapse
Yes, this is normal, this one is only needed when enabling sde first time. local.prop is coming from temp root and won't be there anymore.

I finally had time to try it out tonight, all seemed to be installed fine, but I don't see the Superuser in the apps list... I can boot into developers fw menu though. Did I miss something or should I just try to reinstall the SDE again by running that bat file again?

No, as ColinTaylor said, there is a typo in script, you just need to push the ext4.update at root of storage.
Just type this command in the directory you unzipped the files:
Code:
adb push android_32.ext4.update /data/media/
then boot sde.

Hello
As i have read your post about how to root 3.2.81, the instructions seems to confuse me, but what do you mean by adb? im sorry im kinda new at this ,please let me know thanks!

hello, first of all thanks for your work.
I am having some problems with the upgrade file.
it says that it cannot stat 'zImage':no such file or directory
and secondly it cannot open the kernel file (no such file or directory) mkf lashimage failed.
could you please provide some help with this?
thanks!

lozano.markp said:
Hello
As i have read your post about how to root 3.2.81, the instructions seems to confuse me, but what do you mean by adb? im sorry im kinda new at this ,please let me know thanks!
Click to expand...
Click to collapse
adb is a developer tool from android sdk that let you execute commands on your tablet from your PC. You have to install android sdk to get it, you need to enable it on the tablet and have a proper driver.

Can't get my official status back

I have a Rogers variant, i rooted and changed to supersu, now my status is custom and i cant get it back to official. I tried what seemed to work for many, i used es file explorer to delete the SU folder and try to re-root again and i'm still on custom status. Does anybody have any suggestions on how to change back to Official so i can apply OTAs? I tried looking around in forum but wasnt able to find any solutions.
Thanks

delete

it doesnt work, as soon as i temp unroot and hit the OTA update it tells me my device is modified.

Clear Dalvik cache and reboot
using ADB:
Code:
adb shell
su
cd /data/dalvik-cache
rm *
exit
adb reboot

dew.man said:
using ADB:
Code:
adb shell
su
cd /data/dalvik-cache
rm *
exit
adb reboot
Click to expand...
Click to collapse
i'll try that when i get home tonight...thanks

Or you can use odin to install the new firmware from here, then just root again...
http://forum.xda-developers.com/showthread.php?t=2269304
Sent from my SGH-I337M using xda app-developers app

Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

dew.man said:
using ADB:
Code:
adb shell
su
cd /data/dalvik-cache
rm *
exit
adb reboot
Click to expand...
Click to collapse
That rm * part i dont get, whats the *? i know rm removes files but what is the * for?
{
"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"
}

it means... all of them.

well it doesn't work as you can see.

polish_pat said:
well it doesn't work as you can see.
Click to expand...
Click to collapse
And what makes you say that?

because when i sent command rm * it did nothing, when i sent command rm, it responded. In any case, i keep getting a "device not found" message when i abd reboot.
I'm trying to do odin methond but again, i'm running into hiccups.
I'm desperate and stuck in a loophole i cant get out of -_-
No matter what i do, it blocks at setupconnection

correct me if I am wrong here...if you root..status is going to stay custom...

TheAxman said:
correct me if I am wrong here...if you root..status is going to stay custom...
Click to expand...
Click to collapse
You're wrong There are a couple of threads on how to remove.
And OP - rm * shouldn't return anything, when you reboot it should rebuild the dalvik cache.
And if you're having Odin trouble (you really shouldn't need it) then make sure your Odin version is up to date (I think 3.0.7 works on the S4) and that you have updated Samsung drivers (see if Kies can see the phone).
EDIT: when your Odin screenshot says "GS3", you might want to look around for an updated version

alacrify said:
You're wrong There are a couple of threads on how to remove.
And OP - rm * shouldn't return anything, when you reboot it should rebuild the dalvik cache.
And if you're having Odin trouble (you really shouldn't need it) then make sure your Odin version is up to date (I think 3.0.7 works on the S4) and that you have updated Samsung drivers (see if Kies can see the phone).
EDIT: when your Odin screenshot says "GS3", you might want to look around for an updated version
Click to expand...
Click to collapse
Thanks for the tip but 3.07 was the latest i found, please correct me if i'm wrong but i've look everywhere and it was the latest. If rm * doesnt return anything in that case it all went well and that method didn't work. I realized that it deleted dalvik cache so i tried to boot into stock recovery but unlike on the S3, when deleting cache partition it just gave me an error. In any case, when i tried that method, when i booted back into android it did update apps, so i guess the method work, just not to restore my official status

polish_pat said:
Thanks for the tip but 3.07 was the latest i found, please correct me if i'm wrong but i've look everywhere and it was the latest. If rm * doesnt return anything in that case it all went well and that method didn't work. I realized that it deleted dalvik cache so i tried to boot into stock recovery but unlike on the S3, when deleting cache partition it just gave me an error. In any case, when i tried that method, when i booted back into android it did update apps, so i guess the method work, just not to restore my official status
Click to expand...
Click to collapse
Try this thread: http://forum.xda-developers.com/showthread.php?t=2252248 - either in this one or the djrbliss Motochopper thread, someone should have an answer for you. Make sure Samsung drivers are at v1.5.14, and that ADB works. And the one that held me up longest - make sure your USB cable is ok (use the one from the S4 to be sure) and make sure you're plugged in to a "real" USB port - i.e. front or back of the computer. That one took me over an hour to sort out.

alacrify said:
Try this thread: http://forum.xda-developers.com/showthread.php?t=2252248 - either in this one or the djrbliss Motochopper thread, someone should have an answer for you. Make sure Samsung drivers are at v1.5.14, and that ADB works. And the one that held me up longest - make sure your USB cable is ok (use the one from the S4 to be sure) and make sure you're plugged in to a "real" USB port - i.e. front or back of the computer. That one took me over an hour to sort out.
Click to expand...
Click to collapse
adb works, usb cable is the 3rd i'm using, usb ports are on laptop, i've tried them all. drivers are up to date I'll try another computer and report back
EDIT: i've just tried on a new computer i got 3 days ago, same problem, odin fails at setupconnection, i'm guessing this might be a problem with odin but i can't find a new version

delete

wttisme said:
Attached is the Odin that I just used with my S4 to do a factory restore. Pretty sure it's the same thing you've been using, but maybe it'll work.
Also, make sure Kies isn't running. If I remember right, when I had my S3 it prevented Odin from properly making a connection. I would go into task manager to kill the process.
One last thing, try to disable USB debugging and re-enable it.
Click to expand...
Click to collapse
Its the exact same thing to the byte. Kies has been uninstalled, this was the second thing i did after changing USB ports. And for debug, i've thought about that too but no success... -_-
I've started a new thread here in the hopes of attracting more poeple to help me with odin: http://forum.xda-developers.com/showthread.php?p=41314525#post41314525

polish_pat said:
Its the exact same thing to the byte. Kies has been uninstalled, this was the second thing i did after changing USB ports. And for debug, i've thought about that too but no success... -_-
I've started a new thread here in the hopes of attracting more poeple to help me with odin: http://forum.xda-developers.com/showthread.php?p=41314525#post41314525
Click to expand...
Click to collapse
I had this problem. its your drivers. I'm 100% certain it is. Try and find some new drivers.

{CONFIRMED} NEW Root on 9.30.1 on HD/M/Maxx

Just about tried everything to root this and found this.
I tried this method on 9.30.1 and it worked for me
This root method was made for the Samsung Galaxy S4, But the OP says may work on others too
Has been confirmed to work on the Razr HD, Razr HD Maxx and the Razr M here and over at my post @ droidrzr.com
You do not need to install the samsung drivers.
Just the Moto drivers and make sure adb is working.
http://forum.xda-developers.com/showthread.php?t=2565758
Enjoy

All 3 msm8960 phones [xt907, xt925/6 & mb866] have always used the same low level exploits & this SHOULD be no different. Works on one, works on all.
BTW I never knew how to interpret the BL codes:
Device is LOCKED. Status Code: 0
Device is UNLOCKED. Status Code: 1
Device is LOCKED. Status Code: 2
Device is UNLOCKED. Status Code: 3

Root pics
{
"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"
}

KC, if this works, you'll be the man .....
I am FXZ'ing my M tester to give it a whirl as well. Will keep you posted.

Delete

aviwdoowks said:
Status 0 means no root!
I think the root check app is in error.
Have you created a folder in the root of the phone? Or used a root browser in /cache?
Click to expand...
Click to collapse
yes I have also loaded blurry rom on safestrap

So you did the process just as posted for the galaxy s4?

aviwdoowks said:
So you did the process just as posted for the galaxy s4?
Click to expand...
Click to collapse
yes

Confirmed to work on the M version 98.30.1 as well. Added a test folder to system to confirm as well.

livinginkaos said:
Confirmed to work on the M version 98.30.1 as well. Added a test folder to system to confirm as well.
Click to expand...
Click to collapse
Awesome

http://forum.xda-developers.com/showthread.php?p=49257686#post49257686

Are any timid?
http://forum.xda-developers.com/showthread.php?t=2602657

Rooted 98.18.94 XT907
kc6wke said:
Just about tried everything to root this and found this.
I tried this method on 9.30.1 and it worked for me
Try at your own risk
http://forum.xda-developers.com/showthread.php?t=2565758
Click to expand...
Click to collapse
I have been trying to root my phone since September 2013. I had given up and was reading some info on the possibility of using an AT&T sim in my Verizon phone on Droidrazr.com when I came across a post from yesterday that said "and just like that". Root is confirmed 100%. Thanks very much for the help. These two sites are invaluable.
P.S. I did not have to install the Samsung Drivers.

kc6wke said:
Just about tried everything to root this and found this.
I tried this method on 9.30.1 and it worked for me
Try at your own risk
http://forum.xda-developers.com/showthread.php?t=2565758
Click to expand...
Click to collapse
The referenced thread seems to be talking about Samsung devices. Are you saying this root method for Samsung works on a Motorola RAZR HD (xt926)?
I have a razr hd with unlocked bootloader and recently flashed the 9.30.1 update and lost root. I read somewhere that you can somehow copy the su binary back to the phone in one of the directories in the path using fastboot but I have no idea how to do that. I do have an unlocked bootloader if that helps. I also have a copy of the su and Superuser.apk files on my PC in my original motochopper folder.

chuckh1958 said:
The referenced thread seems to be talking about Samsung devices. Are you saying this root method for Samsung works on a Motorola RAZR HD (xt926)?
I have a razr hd with unlocked bootloader and recently flashed the 9.30.1 update and lost root. I read somewhere that you can somehow copy the su binary back to the phone in one of the directories in the path using fastboot but I have no idea how to do that. I do have an unlocked bootloader if that helps. I also have a copy of the su and Superuser.apk files on my PC in my original motochopper folder.
Click to expand...
Click to collapse
The op will update soon but it works as is on xt926 & 907.
http://forum.xda-developers.com/showpost.php?p=49288923&postcount=22

Ok. So after verifying adb works, I just unzip the saferoot.zip file, cd to the directory where I extracted it, and run install.bat? That simple?
Should I remove the old Superuser app (that no longer works) before running this?

chuckh1958 said:
Ok. So after verifying adb works, I just unzip the saferoot.zip file, cd to the directory where I extracted it, and run install.bat? That simple?
Should I remove the old Superuser app (that no longer works) before running this?
Click to expand...
Click to collapse
Shoot I missed u unlocked!
No need for this exploit. Flash su & you are done.
But now that you did it, yea delete the old su.
See my stickys for the su/root zip-flash from cwmr via matt's util.

I just tried this on a Razr HD XT926 running 9.18.94, android 4.1.2
Confirmed WORKING, at least for me. Got my root back yay!
Thanks for this OP

Worked
Amazing worked on Razr HD 9.30.1
Thought I'd never be able to get this phone rooter.

You have made my day!

[INFO/steps] Cydia Impactor Root (easy root method/confirmed working on R800X)

(MODS - Please Close this thread)
Hi Everyone,
The Cydia Impactor root method (discussed in this thread) appears to be a really easy and quick way to root our Xperia Play phones. I have searched the Xperia Play threads and couldn't find any other posts discussing this root method for our phones, so I'm starting this thread to share information about it with my fellow Xperia Play users. (Since I can only test it on the R800x, it would be great if others could test it to confirm that it works for other versions of the Xperia Play...but I believe it should. I have 2 Xperia Play phones (one with a locked and one with unlocked bootloader. I tested this method on both phones running 2.3.3 & 2.3.4 Gingerbread and it worked as expected in each test).
:good:
CREDITS:
I take no credit for this root method. All credit and thanks should go to saurik for creating the Cydia Impactor, and to Chainfire for SuperSU. Also, thank you to karandpr for starting the other Xperia thread, where I first learned about this method. (If I've forgotten anyone, please PM me and I'll add you).
DISCLAIMER:
If you choose to download and install any of the linked files to your computer or phone, then you are choosing to take full responsibility for any risks or potential consequences that come with rooting and tinkering with your phone. Neither I, nor anyone else in the linked threads will be liable for anything that you choose to do with your phone or computer. Please don't proceed with this root method if you don't agree.
Prerequisites: For the below method to work, you must have the Xperia Play drivers installed on your computer to allow your phone and computer to communicate with each other.
~~~~~~~~~~~~~~~~~~~~~~~~
STEPS:
1. Download the Cydia Impactor zip file: (FOUND HERE) to your computer and unzip it. (On my computer, I created a folder called "Cydia Impactor Root Method," and then used 7zip to unzip it into that folder).
2. Enable USB debugging on your phone and connect the phone to your computer with a USB cable
3. On your computer, navigate to where you unzipped the contents of the Impactor zip file. Right click on the Impactor application and open it with Administrator rights.
4. Click Start and let the root exploit do its thing.
5. On your phone, go to the Google Play Store and install Chainfire's SuperSU (Link), then open SuperSU and update the SU binary. (I chose the "Normal" option to update the SU binary and it worked).
That's it! Your phone should now be rooted with SuperSU installed. This worked great for me and I'm hoping that others will find this information helpful.
PS: This root method doesn't install Busybox, so you'll need to do that if you plan to stay stock rooted. Here's a good app to help you install it if you're not familiar with Busybox: Link
---------------------------------
---------------------------------
Sreenshot of the Cydia Impactor program after opening it on the computer:
{
"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"
}
Screenshot after Cydia Impactor rooted the phone & placed SU binary into system/xbin:
Screenshot of SuperSU asking if you want to update binary with "Normal" or Custom Recovery method:
Screenshot of SuperSU confirming successful installation of SU binary update:

reply
i cant do it in my mob the computer said no device founed

davi.beckham said:
i cant do it in my mob the computer said no device founed
Click to expand...
Click to collapse
I am assuming that you have not installed the Xperia Play drivers onto your computer to let your phone and computer communicate properly. I apologize, but I guess that I assumed people would have known to have done that before trying the above root method. I will update the original post to include these additional steps.
There are numerous ways to install the drivers on your computer, but installing Sony's PC Companion from this link: ( http://support.sonymobile.com/us/tools/pc-companion/ ) will probably be easiest if you are totally new with this stuff. PC Companion takes up a lot of space on the computer's hard drive--so it's not my first choice, but it is a very easy way to get the proper drivers installed.
1. just install the PC Companion on your computer, then enable USB Debugging on your phone by going into Settings/Applications /Development/ then Enable USB Debugging. (I don't think it's necessary... but you might also want to enable Unknown Sources too).
2. Connect your phone with your computer with the USB data transfer cable and this should let your Windows computer install the correct drivers automatically. (You might want to reboot the computer after installing the drivers, but probably not necessary).
After doing these 2 additional steps, retry the rest of the steps in the above rooting method and I believe that it should work.

Thread closed at OPs request

kingroot infected?

Hello all,
I recently started to get lots of popads on my device, so I ran my usual scan with Malwarebytes and it came up with KingRoot being heavily infected with malware. I cant uninstall, since its what i used to root and its also a system app. Any help?

loganwaffle8 said:
Hello all,
I recently started to get lots of popads on my device, so I ran my usual scan with Malwarebytes and it came up with KingRoot being heavily infected with malware. I cant uninstall, since its what i used to root and its also a system app. Any help?
Click to expand...
Click to collapse
see rootjunky's supersume video
https://www.youtube.com/watch?v=3O3DcpeS_Ic
or manually install supersu with a terminal emulator
http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html

Ill try the rootjunky method in a few hours, I tried the terminal emulator installed and it just forceclosed all apps and rebooted.
Sent from my KFTBWI using XDA Labs

So I got a bit impatient, and decided to retry the w0lfdroid method. The same thing happened from last time (apps wouldnt open) and so I decided to reboot.
As the device began to shutdown, SuperSU appeared for a few seconds, then my device switched off. I believe I have bricked my device as it has been stuck on the 'fire' logo for the past 10 minutes. Congrats to me ._.

I tried to install adb and its drivers, however drivers wouldnt install saying 'windows couldnt find any driver software for you device' when i point it to the drivers. Any idea why?

loganwaffle8 said:
I tried to install adb and its drivers, however drivers wouldnt install saying 'windows couldnt find any driver software for you device' when i point it to the drivers. Any idea why?
Click to expand...
Click to collapse
Download kindle_fire_usb_driver.zip from Amazon site
Connecting Your Fire Tablet for Testing or XDA
extract files
run KindleDrivers.exe
Then manually select drivers
Open device manager Settings>Devices>Device Manager
Connect Kindle Fire
Enable USB debugging
(If Kindle is not listed as Android>Android Composite ADB interface)
select Other Devices>Fire
Right Click>Update Driver Software
Browse my computer for Driver Software
Let me pick from a list of drivers on my computer
select Android or Android Phone (or ADB Interface or Android Device)
Select Android Composite ADB interface for Stock rom or recovery/adb sideload
Select Android ADB interface for Fastboot mode
or Android Composite ADB interface
next
you may have to reboot pc
{
"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 KFFOWI using XDA Labs

Thanks
Have I done it right? I hope I've done everything. Also when I open ADB a load of text flashes down the cmd box for about a second then it closes. Ran as administrator and everything. Hoping I can get this fixed by the weekend...

Ok, I think I got it.
Doing adb devices gives me G000HH0454340LB9, I beleive this is the correct device?
Anyways, plan is:
Boot into recovery on device and select apply update from adb
Get the 5.1.1 update (firmware it originally had) and place it in the folder adb installed in.
Do adb sideload (file name)
Wait (maybe grab a cup of coffee?)
Hopefully success, back to stock firmware!
Afterwards ill root with kingroot and then remove using rootjunky supertool.

Ok, this is getting kinda annoying.
Placed the update-kindle-32.5.4.1_user_541112720 .bin file in the same folder I have adb installed.
Booted devices into recovery mode, selected apply update from adb
Open adb, do adb sideload update-kindle-32.5.4.1_user_541112720
Get error message 'cannot read update-kindle-32.5.4.1_user_541112720'
Have ALL correct drivers and stuff installed @sd_shadow

Can anyone help? I really need this fixing...

loganwaffle8 said:
Can anyone help? I really need this fixing...
Click to expand...
Click to collapse
try downloading the firmware again, or try a different version like 5.1.2
which version is on it now?
Sent from my KFFOWI using XDA Labs

The version on my device before it was bricked is 5.1.1. I'm staying on that version since its the easiest to root.