Related
Xposed framework
Hi guys, was wondering if anybody got xposed up and running on the z4t? I know the tablet has been rooted, but I haven't heard much in the way of a custom recovery.
I stumbled on this thread: http://forum.xda-developers.com/g4/themes-apps/guide-installing-xposed-locked-t3181593
Apparently the LG G4 guys got xposed to work without a custom recovery. Does anybody think this will work for the z4t?
mickifree said:
Hi guys, was wondering if anybody got xposed up and running on the z4t? I know the tablet has been rooted, but I haven't heard much in the way of a custom recovery.
I stumbled on this thread: http://forum.xda-developers.com/g4/themes-apps/guide-installing-xposed-locked-t3181593
Apparently the LG G4 guys got xposed to work without a custom recovery. Does anybody think this will work for the z4t?
Click to expand...
Click to collapse
I have a G4 and used that method to get xposed on it successfully but when I tried it for the Z4 Tablet it didn't work. Got FC's after flashing and the apk refused to install.
Also, I only flashed the official framework since romracer's version is only for 5.1.
Charsher47 said:
I have a G4 and used that method to get xposed on it successfully but when I tried it for the Z4 Tablet it didn't work. Got FC's after flashing and the apk refused to install.
Also, I only flashed the official framework since romracer's version is only for 5.1.
Click to expand...
Click to collapse
xposed-v71-sdk21-arm64.zip
Is the correct zip.
Also IIRC it's possible to "flash" though adb too...
Today we are on Android 5.02 and have a 64bit processor
I have not tried it myself.
The referenced zip:
You must be on Android 5.1. It will NOT work on Android 5.0 (too many changes to ART)
Click to expand...
Click to collapse
http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979
The master of it all:
No, this ZIP doesn't support arm64/x86 processors yet.
Click to expand...
Click to collapse
I find an elf file for 32bit arm in rovo89's installer.
http://forum.xda-developers.com/showpost.php?p=60368383&postcount=8
Flashfire works on my Tablet Z4. I tried it with SuperSU. It will not magically get you a recovery partition though ...
EDIT Steve is right! Flash with Flashfire could work. via adb: not available for our xperia
Stevethegreat said:
xposed-v71-sdk21-arm64.zip
Is the correct zip.
Also IIRC it's possible to "flash" though adb too...
Click to expand...
Click to collapse
That's the zip I flashed, it didn't work. Had to wipe back to stock afterwards.
I actually got this to work. After you flash it you have to clear your dalvik-cache.
I did this through adb:
Code:
adb root
adb shell rm -r /data/dalvik-cache
So far I've tested Gravitybox, YouTube AdAway, and OBB on SD and they all work
Charsher47 said:
I actually got this to work. After you flash it you have to clear your dalvik-cache.
I did this through adb:
Code:
adb root
adb shell rm -r /data/dalvik-cache
So far I've tested Gravitybox, YouTube AdAway, and OBB on SD and they all work
Click to expand...
Click to collapse
It works. Just tried it. Used flashfire to flash xposed-v73-sdk21-arm64.zip. After it rebooted, just cleared the dalvik cache and everything seems fine. Xposed modules all seem to be working.
mickifree said:
It works. Just tried it. Used flashfire to flash xposed-v73-sdk21-arm64.zip. After it rebooted, just cleared the dalvik cache and everything seems fine. Xposed modules all seem to be working.
Click to expand...
Click to collapse
Assuming you're rooted to do this yeah?
Sent from my C6603 using Tapatalk
zippy01 said:
Assuming you're rooted to do this yeah?
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Yes. I followed this guide:
https://androplus.org/Entry/626/
After you obtain root, follow this guide:
http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Make sure you flash the zip for Android 5.0
Then after you flash the zip, clear the dalvik cache and you should be good to go.
Thank you but my bootloader is locked thanks anyway
Sent from my SGP771 using Tapatalk
This is a step by step guide for those who want root privileges on their watches. First of all, thanks to @rbox for the modified recovery image, and thanks to @Chainfire for the rooting files. Great developers.
I´ve used the latest superSU beta (systemless rooting), only deleting from the script the superuser.apk.
I´m not responsible for any damage. Do it knowing what you´re doing and at your own risk.
1- You must be in android wear 6.0.1 version. Download and unpack the rooting_files.rar (3 parts, xda format restrictions) and press shift button while right mouse click on a blank space on the folder. In the menu, select open command window here.
2- Reboot your watch in fastboot mode (power off the watch and power on sliding your finger from left top corner to right down corner) (or use adb command "adb reboot bootloader"). Connect it in the charging craddle to pc. If yout bootloader is locked, run "fastboot oem unlock" (It will factory reset your watch). If not, continue.
3- [optional] Flash through adb the twrp287 base image with the command "fastboot flash recovery twrp287.img"
4- Flash the modified twrp with "fastboot flash recovery twrp300modif.img"
5- Select recovery mode from fastboot menu and enter in twrp.
6- Push the wearSU267.zip into the internal memory with command "adb push wearSU267.zip /sdcard"
7- In TWRP select Install option and flash the wearSU267.zip. You may see some errors, ignore them.
8- Reboot your watch
You should have root now! Try it with a su command in terminal or any app.
I´ve included the original TWRP 3.0.0 image if anyone want to flash it after all.
Due to the new /system partition format, we cannot mount it in writable mode, so we cannot make changes inside at the moment, maybe someone can find a solution...
EXTRA: If you want change DPI, run this command: "adb shell wm density 180" (180 or whatever you want). The original value is 240 dpi.
Reserved
Nice tutorial! Currently flashing, I'll see if it works in a few minutes
Update: NICE! Worked like a charm!
Seeing as Busybox is used by almost all android wear apps would you not add it to the files? Also why are you flashing an old recovery and then the proper working one? Just flash the working one
Funciona de lujo, grax!
Xmaster24 said:
Seeing as Busybox is used by almost all android wear apps would you not add it to the files? Also why are you flashing an old recovery and then the proper working one? Just flash the working one
Click to expand...
Click to collapse
In the TWRP page it says the 3.0.0 image is an update, and must be flashed over an old version:
"TWRP Install (Requires TWRP 2.8.4 or higher already installed)"
https://twrp.me/devices/lggwatch.html
Anyway, it does not have effect, it is a precaution.
I´ve installed busybox after all through apk, but it´s not necessary for get root commands working
prototovsky said:
In the TWRP page it says the 3.0.0 image is an update, and must be flashed over an old version:
"TWRP Install (Requires TWRP 2.8.4 or higher already installed)"
https://twrp.me/devices/lggwatch.html
Click to expand...
Click to collapse
Em that's if your updating via recovery through fastboot your completely overwriting the recovery partition if you know how flashing works therefore the old version just disappears after flashing new version
Xmaster24 said:
Em that's if your updating via recovery through fastboot your completely overwriting the recovery partition if you know how flashing works therefore the old version just disappears after flashing new version
Click to expand...
Click to collapse
Then I´ll mark it as optional.
Knowledge is always collaborative
prototovsky said:
Then I�?�´ll mark it as optional.
Knowledge is always collaborative
Click to expand...
Click to collapse
Here's a link to my root method: Only 4 Steps you can take what you like from it http://forum.xda-developers.com/apps/supersu/android-wear-6-0-1-root-squashfs-t3319097/
Also thanks for info on dpi hate having 240 dpi even though it's the watches true dpi lol
Ok, so my watch is rooted now. Thanks! Now what?
jwinstonsf said:
Ok, so my watch is rooted now. Thanks! Now what?
Click to expand...
Click to collapse
Well I use kernel audiotor 4 wear, advanced settings(playstore) commandr, es file explorer (installed onto watch via adb) and minium wear
Xmaster24 said:
Well I use kernel audiotor 4 wear, advanced settings(playstore) commandr, es file explorer (installed onto watch via adb) and minium wear
Click to expand...
Click to collapse
my watch starts now only in twrp - the whole time - what can i do???
finrod2007 said:
my watch starts now only in twrp - the whole time - what can i do???
Click to expand...
Click to collapse
Try a factory reset in TWRP, if this does not work, reflash the rom
prototovsky said:
Try a factory reset in TWRP, if this does not work, reflash the rom
Click to expand...
Click to collapse
unable to mount ....system, data ....
finrod2007 said:
unable to mount ....system, data ....
Click to expand...
Click to collapse
Then reflash all (stock) through adb using this: http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863
prototovsky said:
Then reflash all (stock) through adb using this: http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863
Click to expand...
Click to collapse
thx, i think this will work out, i dont know what it is with twrp flashing supersu...
finrod2007 said:
thx, i think this will work out, i dont know what it is with twrp flashing supersu...
Click to expand...
Click to collapse
after point 5 of the tool - i stuck on bootlogo...made point 6 to restore the watch from stock but now it starts, starting the apps and do the same again and again, its going worser than better^^
finrod2007 said:
after point 5 of the tool - i stuck on bootlogo...made point 6 to restore the watch from stock but now it starts, starting the apps and do the same again and again, its going worser than better^^
Click to expand...
Click to collapse
Just use my method only 4 Steps and have debugged it completely so there should be no problems http://forum.xda-developers.com/g-watch/development/guide-how-to-root-lg-g-watch-6-0-1-t3320512
Xmaster24 said:
Just use my method only 4 Steps and have debugged it completely so there should be no problems http://forum.xda-developers.com/g-watch/development/guide-how-to-root-lg-g-watch-6-0-1-t3320512
Click to expand...
Click to collapse
yes of course I had known it before i had not done it, because everything was good, because then after point 6 i have android 5.1.1 on my watch, not android 6 any more, and its equal what i do nothing is changing when i start the watch, android is starting is finishing, watch starting again, doing this as again and again. i have done step 4 again, it does not change anything...
---------- Post added at 04:08 PM ---------- Previous post was at 04:07 PM ----------
finrod2007 said:
yes of course I had known it before i had not done it, because everything was good, because then after point 6 i have android 5.1.1 on my watch, not android 6 any more, and its equal what i do nothing is changing when i start the watch, android is starting is finishing, watch starting again, doing this as again and again. i have done step 4 again, it does not change anything...
Click to expand...
Click to collapse
but i will do your method now, maybe need a fresh stock rom which i can flash with a .bat file or something like that. are there any links???
finrod2007 said:
yes of course I had known it before i had not done it, because everything was good, because then after point 6 i have android 5.1.1 on my watch, not android 6 any more, and its equal what i do nothing is changing when i start the watch, android is starting is finishing, watch starting again, doing this as again and again. i have done step 4 again, it does not change anything...
---------- Post added at 04:08 PM ---------- Previous post was at 04:07 PM ----------
but i will do your method now, maybe need a fresh stock rom which i can flash with a .bat file or something like that. are there any links???
Click to expand...
Click to collapse
Will send you stock system.img, and you can use invisiblek's kernel or stock boot.img cause they are both working fine just format the others (/data and /cache)
Hello,
Recently I achieved root on my Fire via KingRoot on Fire OS 5.0.1. I disabled the Fire Launcher, and then I stupidly decided to remove KingUser and replace it with SuperSU with SuperSU-Me. Long story short, I rebooted the device when SuperSU finished updating the binaries, and I was greeted with a bricked Fire that would stay on the Fire screen but would not dim and do much else. I can get ADB access, but my Windows PC says that the device is unauthorized and my Linux box says that the device is offline. Any help? I am kind of lost as to what I can do. Thank you in advance
HyperNyan said:
Hello,
Recently I achieved root on my Fire via KingRoot on Fire OS 5.0.1. I disabled the Fire Launcher, and then I stupidly decided to remove KingUser and replace it with SuperSU with SuperSU-Me. Long story short, I rebooted the device when SuperSU finished updating the binaries, and I was greeted with a bricked Fire that would stay on the Fire screen but would not dim and do much else. I can get ADB access, but my Windows PC says that the device is unauthorized and my Linux box says that the device is offline. Any help? I am kind of lost as to what I can do. Thank you in advance
Click to expand...
Click to collapse
Can you get into recovery by holding Power and Volume-Up?
DoLooper said:
Can you get into recovery by holding Power and Volume-Up?
Click to expand...
Click to collapse
Yes, I indeed can get into recovery mode! There might be some hope for my tablet
HyperNyan said:
Yes, I indeed can get into recovery mode! There might be some hope for my tablet
Click to expand...
Click to collapse
Yes, indeed! You can sideload the latest Amazon update. It's 5.1.1. (AFAIK, the November 5.0.1 is not available.) Get the update here: http://kindle-fire-updates.s3.amazo...aZE/update-kindle-20.5.4.1_user_541113320.bin
In recovery, highlight the adb sideload option and press power to get into sideload mode. I don't know linux, but if using Windows install adb drivers. Now, from CMD window, type:
adb sideload <name of the update file>
The update will install and you should be able to boot. You can root with kingroot. After rooting, read/use @bibikalka's guide to reinstall 5.1.1 with SuperSU (to kill Kingroot) and to install Gapps.
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
DoLooper said:
Yes, indeed! You can sideload the latest Amazon update. It's 5.1.1. (AFAIK, the November 5.0.1 is not available.) Get the update here: http://kindle-fire-updates.s3.amazo...aZE/update-kindle-20.5.4.1_user_541113320.bin
In recovery, highlight the adb sideload option and press power to get into sideload mode. I don't know linux, but if using Windows install adb drivers. Now, from CMD window, type:
adb sideload <name of the update file>
The update will install and you should be able to boot. You can root with kingroot. After rooting, read/use @bibikalka's guide to reinstall 5.1.1 with SuperSU (to kill Kingroot) and to install Gapps.
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Click to expand...
Click to collapse
Thank you! My Fire tablet is now able to boot and can run normally, but with root access this time Thank you for helping me through this issue
Update:
I tried to install TWRP without reading that it would not work on the newer Fire OS bootloader, and now I am stuck with no recovery. Attempting to boot into TWRP results in a black screen after the Amazon logo and then it reboots into the OS. I do have access to Android, but I cannot flash the stock recovery as I am currently without a recovery. Any pointers as to how I can possibly get the stock recovery again so then I can redo the whole process of attempting to install CM11?
You may be able to dd the recovery partition. Someone else will have to help with that.
HyperNyan said:
Update:
I tried to install TWRP without reading that it would not work on the newer Fire OS bootloader, and now I am stuck with no recovery. Attempting to boot into TWRP results in a black screen after the Amazon logo and then it reboots into the OS. I do have access to Android, but I cannot flash the stock recovery as I am currently without a recovery. Any pointers as to how I can possibly get the stock recovery again so then I can redo the whole process of attempting to install CM11?
Click to expand...
Click to collapse
Just do this, run the script provided :
http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
I'll get you TWRP and 4.5.3 bootloaders. Then flash 5.4.1 stuff from TWRP.
DoLooper said:
Yes, indeed! You can sideload the latest Amazon update. It's 5.1.1. (AFAIK, the November 5.0.1 is not available.) Get the update here: http://kindle-fire-updates.s3.amazo...aZE/update-kindle-20.5.4.1_user_541113320.bin
In recovery, highlight the adb sideload option and press power to get into sideload mode. I don't know linux, but if using Windows install adb drivers. Now, from CMD window, type:
adb sideload <name of the update file>
The update will install and you should be able to boot. You can root with kingroot. After rooting, read/use @bibikalka's guide to reinstall 5.1.1 with SuperSU (to kill Kingroot) and to install Gapps.
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Click to expand...
Click to collapse
THANK YOU SO EFFING MUCH! I thought my HD6 was done. I was beginning to panic. I went through a LOT of guides to fix it and nothing worked except what you posted.
I know this thread is pretty old, but I haven't fixed the recovery issue yet due to being scared of bricking my tablet. So, just asking, which script do I run? Thanks!
HyperNyan said:
I know this thread is pretty old, but I haven't fixed the recovery issue yet due to being scared of bricking my tablet. So, just asking, which script do I run? Thanks!
Click to expand...
Click to collapse
The recommendations have not changed since the last time you asked Either install stock recovery via Flashify (dig out the recovery image from this zip : 5.2.0_stock_recovery_only.zip , here : http://forum.xda-developers.com/showpost.php?p=62011272 ), or run the script in post #2, and from TWRP, re-install 5.4.1 bootloaders :
http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
Thank you! My tablet is now working great, TWRP successfully installed. Just about a few minutes ago I had a panic attack when it started boot-looping, but then I shut it off for a while, and booted it into TWRP, and it was fine. Go figure I will now attempt to install cm11! Thank you for all of your help!
This thread was originally for Pixel-specific rooting instructions, but by now the SuperSU ZIP and TWRP are fully supported:
- Fastboot boot TWRP
- Install latest SuperSU ZIP (v2.79-SR3 at the time of writing)
Note that at this time I recommend against fastboot flashing TWRP. With the Pixel's new partition layout, the recovery files are inside the boot partition, and so is SuperSU. If you flash both, SuperSU's internal boot image backup will not be of the original boot image, but of TWRP. This means that neither the 'full unroot' option in SuperSU, nor incremental OTA update through FlashFire, will work as expected.
OR
- Use CF-Auto-Root for Pixel (not released at the time of writing, but should be released soon)
Nice work!
Hell Yeah!!! Thanks @Chainfire, your time as well as others that have made this and the bootloader unlock happen is appreciated very much.
Sent from my Pixel XL using Tapatalk
can we flash another kernel such as elementalX on top of this?
diabl0w said:
can we flash another kernel such as elementalX on top of this?
Click to expand...
Click to collapse
How does this relate?
Ker~Man said:
How does this relate?
Click to expand...
Click to collapse
because I attempted to not really thinking about that its systemless and wasnt sure if root would persist. after attempting to flash boot elementalX's kernel my device just powered off so i immediately reflashed root and all is okay now
diabl0w said:
can we flash another kernel such as elementalX on top of this?
Click to expand...
Click to collapse
Lol if you read chainfires instructions you would have e your answer,but it short no, not until they add it
I did read the readme.. so not sure what your getting at
cwalker0906 said:
Lol if you read chainfires instructions you would have e your answer,but it short no, not until they add it
Click to expand...
Click to collapse
chainfire said:
- If you want to use a custom kernel, simply 'fastboot boot' the root image again after flashing the custom kernel. This has been tested with a few custom kernels and found to work well so far.
Click to expand...
Click to collapse
It was a valid question since this flashing method is different than what we are used to due to the difference in partitions and the file system.
lexcyn said:
It was a valid question since this flashing method is different than what we are used to due to the difference in partitions and the file system.
Click to expand...
Click to collapse
okay thanks, so i guess the answer is actually yes
Thanks @Chainfire - booted and working well!
thanks..emoji..root explorer.. viper.. naptime.. titanium.. yes..
if new kernel must boot boot to root again..
Seems I cannot remount /system_root as rw (to copy Emoji font over).
marlin://system_root/system/fonts # mount -o remount,rw /system_root
mount: '/dev/block/bootdevice/by-name/system_a'->'/system_root': Device or resource busy
Edit: Nevermind, used Solid Explorer and granted it SuperUser and seemed to work. Strange.
Does anyone have the stock boot.img for the pixel xl? I don't have the data to download the full factory image.
Life is good!
Thanks to all involved, especially Chainfire.
You Rock!
Worked like a charm. Thanks @Chainfire!
Can't thank you enough. Works perfectly.
can someonone please post the exact steps they are using?
I just unlocked my bootloader. then tried flashing the root-boot img file, it did the reboots, but when i complete android setup, theres no SuperSU and if i install the .apk, it still does not detect root...
just reflashed stock boot.img, locked and unlocked bootloader. waiting for instrustion.
thanks!
spunks3 said:
can someonone please post the exact steps they are using?
I just unlocked my bootloader. then tried flashing the root-boot img file, it did the reboots, but when i complete android setup, theres no SuperSU and if i install the .apk, it still does not detect root...
just reflashed stock boot.img, locked and unlocked bootloader. waiting for instrustion.
thanks!
Click to expand...
Click to collapse
fastboot boot boot-to-root.img
lexcyn said:
fastboot boot boot-to-root.img
Click to expand...
Click to collapse
what about superSU?
I downgraded my Fire HD 6 to 4.5.3, rooted it using Kingroot and installed TWRP using Flashify (couldn't flash TWRP because the bootloader/fastboot was locked ("Failed:...locked hw")) . After rooting, I blocked OTA using the adb command lines.
Then I updated to the latest Fire OS using http://forum.xda-developers.com/fire-hd/general/upgrade-to-4-5-5-root-t3174449. After step 2A (flash the respective Amazon ROM 4.5.x update (the latest one? [so I tried 5.5.4)), I thought I was home free. But upon rebooting, I found root was gone. Not sure what I missed and when I missed it but that's not the point now. [Upon much reflection, it was probably not issuing the block OTA commands again, duh.]
Now, I have no recovery; TWRP is gone. Stock recovery is gone. I can't flash TWRP using fastboot because bootloader is still locked. Flashify needs root to work. Help greatly appreciated.
I tried to unbrick (even though it's not bricked but I'm at a loss as to how to get a recovery back on it) using Imma Wake's Linux but it just hangs on ./reader.sh . I'm really at a loss but it's not for not trying. I've got to reroot this thing cuz I hate hate hate amazon. Can't do it without a recovery. Well, really, is there no one who can help me?
bleak93 said:
I tried to unbrick (even though it's not bricked but I'm at a loss as to how to get a recovery back on it) using Imma Wake's Linux but it just hangs on ./reader.sh . I'm really at a loss but it's not for not trying. I've got to reroot this thing cuz I hate hate hate amazon. Can't do it without a recovery. Well, really, is there no one who can help me?
Click to expand...
Click to collapse
Why don't you try unlocking the bootloader so you can flash TWRP, bleak?
bleak93 said:
Why don't you try unlocking the bootloader so you can flash TWRP, bleak?
Click to expand...
Click to collapse
Well, that's a damn good idea, bleak. I wish I thought of it.
So I tried using the python/cublock.py method. I'm on Windows 7 so I installed Python. I get the two codes, run cublock.py [XXX] [SSS] and I get a file called "unlock.img" but after that, it hangs when I run adb reboot bootloader / fastboot -i 0x1949 flash unlock unlock.signed. I tried fastboot -i 0x1949 flash unlock unlock.img cuz that's what the file is called but it just says "[WAITING FOR A DEVICE]" or something like that after both of those commands. I think it doesn't reboot into the bootloader after adb reboot bootloader ; it shuts down because there are no signs of it in the device manager.
bleak93 said:
Well, that's a damn good idea, bleak. I wish I thought of it.
So I tried using the python/cublock.py method. I'm on Windows 7 so I installed Python. I get the two codes, run cublock.py [XXX] [SSS] and I get a file called "unlock.img" but after that, it hangs when I run adb reboot bootloader / fastboot -i 0x1949 flash unlock unlock.signed. I tried fastboot -i 0x1949 flash unlock unlock.img cuz that's what the file is called but it just says "[WAITING FOR A DEVICE]" or something like that after both of those commands. I think it doesn't reboot into the bootloader after adb reboot bootloader ; it shuts down because there are no signs of it in the device manager.
Click to expand...
Click to collapse
Did you just reply to yourself? ???
I'm stuck in the same crappy situation
I'm in this situation too...
I'm no expert, but I think I know what happened. For whatever reason, TWRP doesn't play nice with 5.x bootloaders. 4.x is fine but 5.x is a no-go. I'm assuming that when you flashed TWRP you overwrote your stock recovery. This would have been fine, but the wording in the tutorial you were following is a bit misleading. When he said flash the 4.5.x update (the latest one) he meant the latest 4.5.x (eg 4.5.3, 4.5.4, etc) but not anything above 4.5.whatever. When you flashed 5.5.4 you updated the bootloaders to 5.x so TWRP no longer works and you've lost your stock recovery. Not sure what happened to your root though. It's possible it's still there and there's just not a manager app installed? Try installing Kingroot again and using its root check function to see. If it really is gone, then I have no idea how to fix it.
@bibikalka any help please?
---------- Post added at 11:55 PM ---------- Previous post was at 11:49 PM ----------
Killa8;72047553 [user=6680544 said:
@bibikalka[/user] any help please?
Click to expand...
Click to collapse
@powerpoint45
similar situation
I havea fire hd 6 (4th generation) running 5.3.1.0 no recovery but I do have root via kingroot so I have flashify and rashr. I have tried flashing TWRP using flashify and rashr, and no error but it wont boot to twrp. Any way to flash stock recovery or is there another option for 5.3.1.0 as far as recover??
bleak93 said:
I downgraded my Fire HD 6 to 4.5.3, rooted it using Kingroot and installed TWRP using Flashify (couldn't flash TWRP because the bootloader/fastboot was locked ("Failed:...locked hw")) . After rooting, I blocked OTA using the adb command lines.
Then I updated to the latest Fire OS using http://forum.xda-developers.com/fire-hd/general/upgrade-to-4-5-5-root-t3174449. After step 2A (flash the respective Amazon ROM 4.5.x update (the latest one? [so I tried 5.5.4)), I thought I was home free. But upon rebooting, I found root was gone. Not sure what I missed and when I missed it but that's not the point now. [Upon much reflection, it was probably not issuing the block OTA commands again, duh.]
Now, I have no recovery; TWRP is gone. Stock recovery is gone. I can't flash TWRP using fastboot because bootloader is still locked. Flashify needs root to work. Help greatly appreciated.
Click to expand...
Click to collapse
Hi I am having the same exact problem and I would just like to know if you have found a fix for this problem yet. I'm stuck on cm11 rom which has a bunch of bugs and I would like to go back to fire os but I have no root and can boot into fast boot or recovery. Any help would be appreciated. Thanks.
---------- Post added at 02:10 AM ---------- Previous post was at 02:08 AM ----------
Killa8 said:
I'm stuck in the same crappy situation
Click to expand...
Click to collapse
Hi have you found a fix for this situation yet I'm stuck in it too. Tried to re flash the device using powerpoints tutorial but gets stuck on reader.sh. Any help would be appreciated thanks.
---------- Post added at 02:11 AM ---------- Previous post was at 02:10 AM ----------
Killa8 said:
I'm stuck in the same crappy situation
Click to expand...
Click to collapse
Hi have you found a fix for this situation yet I'm stuck in it too. Tried to re flash the device using powerpoints tutorial but gets stuck on reader.sh. Any help would be appreciated thanks.
kyle12345109876 said:
Hi I am having the same exact problem and I would just like to know if you have found a fix for this problem yet. I'm stuck on cm11 rom which has a bunch of bugs and I would like to go back to fire os but I have no root and can boot into fast boot or recovery. Any help would be appreciated. Thanks.
---------- Post added at 02:10 AM ---------- Previous post was at 02:08 AM ----------
Hi have you found a fix for this situation yet I'm stuck in it too. Tried to re flash the device using powerpoints tutorial but gets stuck on reader.sh. Any help would be appreciated thanks.
---------- Post added at 02:11 AM ---------- Previous post was at 02:10 AM ----------
Hi have you found a fix for this situation yet I'm stuck in it too. Tried to re flash the device using powerpoints tutorial but gets stuck on reader.sh. Any help would be appreciated thanks.
Click to expand...
Click to collapse
Just so I have a clear understanding: you're running cm11 but you have lost root and recovery. Can you get into fastboot? I think you wrote you can boot into fastboot and recovery.
Kindle fire no twrp
Drunkpilot said:
Just so I have a clear understanding: you're running cm11 but you have lost root and recovery. Can you get into fastboot? I think you wrote you can boot into fastboot and recovery.
Click to expand...
Click to collapse
Ok so yes I am on cm 11 and i cannot boot into recovery but I can boot into fast boot using the adb commands so does this mean I can flash twrp using fast boot?
Also I have used kingo root and have now gained root access.
kyle12345109876 said:
Ok so yes I am on cm 11 and i cannot boot into recovery but I can boot into fast boot using the adb commands so does this mean I can flash twrp using fast boot?
Also I have used kingo root and have now gained root access.
Click to expand...
Click to collapse
Good deal on the root. Yes, you should be able to flash TWRP using fastboot. You need to have the fastboot drivers installed and rename the recovery image to recovery.img. I believe the command is: fastboot flash recovery recovery.img. now that you are rooted though, you can use Flashify to flash TWRP. Flashify would be the easiest and quickest solution. Flashfire might be another option, but I don't know if it would recognize the Kingo root.
Drunkpilot said:
Good deal on the root. Yes, you should be able to flash TWRP using fastboot. You need to have the fastboot drivers installed and rename the recovery image to recovery.img. I believe the command is: fastboot flash recovery recovery.img. now that you are rooted though, you can use Flashify to flash TWRP. Flashify would be the easiest and quickest solution. Flashfire might be another option, but I don't know if it would recognize the Kingo root.
Click to expand...
Click to collapse
Thanks I tried flash fire and it didn't regonize the kingo root, also tried flashify and it just rebooted the tablet and didn't work. So I will try with the fast boot.
---------- Post added at 06:17 PM ---------- Previous post was at 05:47 PM ----------
Drunkpilot said:
Good deal on the root. Yes, you should be able to flash TWRP using fastboot. You need to have the fastboot drivers installed and rename the recovery image to recovery.img. I believe the command is: fastboot flash recovery recovery.img. now that you are rooted though, you can use Flashify to flash TWRP. Flashify would be the easiest and quickest solution. Flashfire might be another option, but I don't know if it would recognize the Kingo root.
Click to expand...
Click to collapse
Right now I remember I tried to flash twrp using fast boot and it gave me an error saying :FAILED (remote: flashing not allowed for locked hw).
Does this mean my bootloader is somehow locked? If so how do I unlock it?
kyle12345109876 said:
Thanks I tried flash fire and it didn't regonize the kingo root, also tried flashify and it just rebooted the tablet and didn't work. So I will try with the fast boot.
Click to expand...
Click to collapse
Maybe try flashing a chainfire SuperSU.zip through flashing so that you can replace the kingo SU, then use the SuperSU app to clean up some of the kingo root remnants and have something recognizable when flashing TWRP. I have been doing a lot of Fire flashing work lately as I just used my warranty for a brick I replaced. Then, within a couple hours bricked the replacement due to me not turning off the OTA sufficiently while running 4.5.2 and used the Powerpoint45 technique (which worked brilliantly on the new Fire) and then stupidly lost root and had to revert back to 4.5.3. Needless to say, I have been reading and executing a lot of different actions. Currently, I'm on 4.5.3 with TWRP and finally getting the Google Play store to work.
Drunkpilot said:
Good deal on the root. Yes, you should be able to flash TWRP using fastboot. You need to have the fastboot drivers installed and rename the recovery image to recovery.img. I believe the command is: fastboot flash recovery recovery.img. now that you are rooted though, you can use Flashify to flash TWRP. Flashify would be the easiest and quickest solution. Flashfire might be another option, but I don't know if it would recognize the Kingo root.
Click to expand...
Click to collapse
Does it help if I say before all this happened I had installed fire os 5 from twrp but i didn't boot it right after I cleared cache and dalvik and then flashed cm11. When I then booted the cm11 the twrp dissapered. Does this mean that I would have to flash the fire os 4 bootloader or something since fire os 5 can't doesn't work with twrp cause I'm sooo lost right now and would just love to get to any stable fire os.
kyle12345109876 said:
Does it help if I say before all this happened I had installed fire os 5 from twrp but i didn't boot it right after I cleared cache and dalvik and then flashed cm11. When I then booted the cm11 the twrp dissapered. Does this mean that I would have to flash the fire os 4 bootloader or something since fire os 5 can't doesn't work with twrp cause I'm sooo lost right now and would just love to get to any stable fire os.
Click to expand...
Click to collapse
Look at the TWRP thread for our Fire. I think it has the dd commands to install the recovery now that you are rooted once again. It sounds like you didn't install the 5.x.x uboot and recovery zip along with the update and lost recovery. I think you said you used the unbrick method and you just hung on the reading.sh. that method would give you TWRP and nothing else, but from there you could them flash the 5.x files in the thread. I used Flashify to get TWRP yesterday, and I think I had kingroot at the time. I know the is a zip only containing the 4.5.3 bootloader's, but I can't remember where I saw it right now, and if it would work or not. I'm still in learning more as well.
Drunkpilot said:
Look at the TWRP thread for our Fire. I think it has the dd commands to install the recovery now that you are rooted once again. It sounds like you didn't install the 5.x.x uboot and recovery zip along with the update and lost recovery. I think you said you used the unbrick method and you just hung on the reading.sh. that method would give you TWRP and nothing else, but from there you could them flash the 5.x files in the thread. I used Flashify to get TWRP yesterday, and I think I had kingroot at the time. I know the is a zip only containing the 4.5.3 bootloader's, but I can't remember where I saw it right now, and if it would work or not. I'm still in learning more as well.
Click to expand...
Click to collapse
Hi thanks for the help turns out I managed to brick the device once again so I just used powerpoints video to unbrick and now I have twrp again. Question though I tried to install fire os 4.5.3 in twrp but it give me an error sayingI have the Omni Ariel not the full Ariel so I can't flash the file. Anyone know how to fix it?
kyle12345109876 said:
Does it help if I say before all this happened I had installed fire os 5 from twrp but i didn't boot it right after I cleared cache and dalvik and then flashed cm11. When I then booted the cm11 the twrp dissapered. Does this mean that I would have to flash the fire os 4 bootloader or something since fire os 5 can't doesn't work with twrp cause I'm sooo lost right now and would just love to get to any stable fire os.
Click to expand...
Click to collapse
Hi the process should be fairly simple. Use the tutorial from the unbricking thread to get your device back to normal. It will be long but it works unless you have fire os 5(like me). Otherwise there's literally no other option you can use
---------- Post added at 05:57 PM ---------- Previous post was at 05:56 PM ----------
kyle12345109876 said:
Hi thanks for the help turns out I managed to brick the device once again so I just used powerpoints video to unbrick and now I have twrp again. Question though I tried to install fire os 4.5.3 in twrp but it give me an error sayingI have the Omni Ariel not the full Ariel so I can't flash the file. Anyone know how to fix it?
Click to expand...
Click to collapse
Did you download the correct file? Check again