Related
Q&A for [Pure Edition][Root] Superboot style root for MotoX 2014 Pure Edition
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
MotoX Pure - UnRoot To Update Firmware
I used the Jcase method (fastboot boot pure2014sb.img) to root my new MotoX Pure. Worked great. However, the next day I received a notification on the phone that a firmware update is available: "New FIrmware Available" "Update to get the lastest Motorola Sensor. . ."
Because this method uses fastboot boot vs fastboot flash, I don't understand how I can go back to stock in order to update firmware.
Wondering if someone could school me on what the heck it actually means to fastboot boot vs fastboot flash. Basically looking for a way to be able to un-root, apply firmware update, and then re-root.
A
You need a factory image to flash using Motorola's mfastboot to get back to stock. Motorola has not posted a factory image yet, but they said they would.
Sent from my Nexus 10 using Tapatalk
tyea said:
You need a factory image to flash using Motorola's mfastboot to get back to stock. Motorola has not posted a factory image yet, but they said they would.
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
if they said they would, then i'm glad. getting worried here lol
root moto x 2014 followed by ota lollipop update
The moto x is delivered with KitKat initially and then updated via ota later once powered up etc. If I follow your method as soon as I get the phone and then later accept the ota update to lollipop, will it cause problems or lose root?
bootloop
i tried to root my phone and i followed every step but now i am stuck in a bootloop. what do i do? please help
---------- Post added at 06:27 AM ---------- Previous post was at 05:53 AM ----------
I tried to root my moto with this method and now i am stuck in a bootloop. i followed every step including the fastboot boot. please help me
deelv said:
i tried to root my phone and i followed every step but now i am stuck in a bootloop. what do i do? please help
---------- Post added at 06:27 AM ---------- Previous post was at 05:53 AM ----------
I tried to root my moto with this method and now i am stuck in a bootloop. i followed every step including the fastboot boot. please help me
Click to expand...
Click to collapse
The same thing happened to me but I've gotten out of the boot loop by getting to fastboot (hold down the power button till the screen turns off and then you have to guess and hold the power and volume down button for about 5 seconds and then release the power button but hold down the volume button until you see the fastboot. If it doesn't get to fastboot try it again.)
When you're at the fastboot, connect to a computer and cmd a command "fastboot erase userdata" and then "fastboot erase cache" to pretty much factory reset and get you out of the boot loop. Then it should boot and tell you to set up the device.
I would recommend looking for the root boot image from chainfire them self, they recently released it. Just look for your model # (e.g. xt1095) and "fastboot boot (insert boot image)"
My Moto x 2014 is currently rooted with chainfire's boot image. It works like a charm.
XT1092 bootloop after OTA
Hi,
Got my XT1092 and unlocked the bootloader and gained root using this method a while back, no problem there.
Downloaded and installed the OTA update to lollipop and went about reinstating the root access using this method. Subsequently have been stuck in a bootloop and have been unable to find a stock image to repair this with.
Does anyone have a suggestion on how to fix this?
When I have tried using
fastboot boot *whatever stock image I have found*
I get a little droid with a red exclamation mark with 'NO COMMAND' underneath.
Any suggestions of how to fix this/what I can boot/flash that can fix this?
Cheers
HamRack said:
Hi,
Got my XT1092 and unlocked the bootloader and gained root using this method a while back, no problem there.
Downloaded and installed the OTA update to lollipop and went about reinstating the root access using this method. Subsequently have been stuck in a bootloop and have been unable to find a stock image to repair this with.
Does anyone have a suggestion on how to fix this?
When I have tried using
fastboot boot *whatever stock image I have found*
I get a little droid with a red exclamation mark with 'NO COMMAND' underneath.
Any suggestions of how to fix this/what I can boot/flash that can fix this?
Cheers
Click to expand...
Click to collapse
Boot this boot.img : http://forum.xda-developers.com/moto-x-2014/general/lollipop-root-achieved-t2937154
Its for xt1095 but some have confirmed working on xt1092
Sent from my Moto X 2014 Pure Edition
does it work on Android 5.0?
Yes, I'm currently running Android 5.0 Lollipop.
Sent from my Moto X 2014 Pure Edition
Bootloop
Stuck in a bootloop. Followed all your instructions carefully. :/ Not able to boot into bootloader.
Formatted Telus Moto X (2014) SD card and all data ... recovered.
I might make a tutorial video on how to recover from a mistake like mine, and I may not have done it correctly, but the phone is back operational.
What I did to screw it up :
1) Unlocked the bootloader and installed TWRP without doing research about development for the phone
2) The phone is already almost stock android and that's one of it's selling points so I don't know why I wanted to unlock and root
3) Got frustrated and wiped / formatted internal SD ... since I use to flash ROM's on my older Huawei this way ... it must be the same right ... smh.
4) Freaked the eff out, had thoughts of just running it over with the car because that qualifies under my 2-year warranty, since I voided it by unlocking.
5) Thought I knew it all when I really don't understand most of the lingo still
What I did to 'TRY' to fix it :
1) Scoured the internet for ROMS / Zips.
2) I was in 'Android Studio' ... unnecessary.
3) Tried flashing .zips in TWRP by draggin and dropping .zips ... contanst 'FAILED' signs.
4) Tried sideloading as I was grasping at straws by this point. 'FAILED'
5) Considered buying an OTG cable.
6) Spent hours going in circles
What I did to fix it :
1) Downloaded the SDK ... 'adt-bundle-windows-x86_64-20140702'
2) Installed the 'Google USB drivers' as I checked 'Device Manager' and there was an exclamation ... this is why when I went typed 'ADB devices' nothing showed up. I 'manually' installed the drivers. VOILA, first step.
3) Found a .ZIP file I believe was the correct one ... ;RETCA_XT1097_4.4.4_KXE21.187-42_cid14_CFC.xml.zip' (From this website I believe)
4) Watched a few youtube tutorials on how to flash from within 'SDK' > 'Platform-Tools'
5) Extracted the .ZIP file into 'Platform-Tools'
6) Had phone booted into fastboot mode
7) Opened the CMD from within 'Platform-Tools' with that .ZIP file within that folder, held 'SHIFT' 'Right-click" > 'Run CMD'
8) This is where I didn't do it properly, but the phone is booted for now and working ... with these Commands
- fastboot flash boot boot.img;
- fastboot.exe flash system system.img_sparsechunk.0
- fastboot.exe flash system system.img_sparsechunk.1
- fastboot.exe flash system system.img_sparsechunk.2
- fastboot.exe flash system system.img_sparsechunk.3
- fastboot.exe flash system system.img_sparsechunk.4
Got that nice Motorola earth screen and booted to the welcome screen. Froze. I reset. Froze. Walked away from phone, came back and tried to see if I could press 'OK' and it worked.
All-in-All , not worth it for the average consumer and not worth it for someone such as myself who was stupid and just wanted to 'play around' with a brand new 2-year warrantied $500 phone.
I just got my motorola yesterday. I did quite a few things like unlocking it and rooting it..After my first initial root it worked fine but earlier today i decided to install lollipop. I was using the twrp version 2.7 to install the rom but i realised it wasnt working till i tried a few more time and it finally it. I tried back up my stock 4.4.4 room before i installed my new rom but it failed several times because i think the recovery was faulty to say the least. Anyways my lollipop worked very fine but i notice anytime i restarted the phone it took a long freaking time to restart but it was working normal as usual until i restarted my phone another time and realised i couldn't go past the bootanimation.It takes forever but i never get past it. I then decided to flash the twrp 2.8.0.1. After flashing i realised I could do a backup but it was too late. I tried a few tricks I've always used to get past the bootanimation like mounting the storage but it never shows up on my pc. I also tried side loading the rom using the adb sideload command but it never workedd.it always shows up saying "error: device not found" but when i go back to the bootloader and use the fastbootdevices command it shows up my device. IS there any recovery that will allow me to sucessfully mount my storage or sideload my rom without all this hussle?Even my the the bootloader unlock warning reboots several times before getting to the never ending bootanimation
rom:TitanPrimeROMv1.3-XT1068-69_RC1
XT1068
Rooted
TWRP 2.0.8.1
Window 8.1 64bit
I already have my mini sdk files
There's a number of guides in this subforum that goes through flashing the stock firmware for your phone. The reason you're getting bootloops is because there's currently no stable way to get root access on Lollipop for this phone, but it is being worked on.
ADB can be a bit finicky, so it'd probably be easier to have your ROM on the phone itself, whether in the data/media/ folder in Internal Storage, or on an SD card, since neither are wiped whenever you factory reset or clean your phone. TWRP 2.8.2.0 and above allows you to enable MTP mode so you can move your files straight onto or off your phone.
Actaully i managed to root my phone using chainfare's auto rode for the moto G.I just also installed twrp 2.8.0.3. Unfortunately,I dont have any rom on my phone which is bummer. Yh I do get to MTP enable my device in recovery but it never shows up on my pc.I have had issues like this before and I got it done in minutes without no problem..This is my first motorola device and I'm regretting my choice in buying this phone
sleekykenny said:
Actaully i managed to root my phone using chainfare's auto rode for the moto G.I just also installed twrp 2.8.0.3. Unfortunately,I dont have any rom on my phone which is bummer. Yh I do get to MTP enable my device in recovery but it never shows up on my pc.I have had issues like this before and I got it done in minutes without no problem..This is my first motorola device and I'm regretting my choice in buying this phone
Click to expand...
Click to collapse
Did you try manually selecting the driver is device manager?
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657 This thread is your best friend. The other thing is that you'll probably need to uninstall the drivers for your phone from Hardware Manager on your OS, unplug your phone, then plug it back in when you're in recovery, and your OS should pull the right drivers to get ADB working. Still, you've got fastboot so the best option for you at the moment is to just restore your phone to stock and go from there.
As I said, though, root doesn't work on Lollipop for our phone yet, and AFAIK we don't have the kernel sources yet for Chainfire (the developer of SuperSU amongst other things) to get root access working without causing bootloops.
Traediras said:
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657 This thread is your best friend. The other thing is that you'll probably need to uninstall the drivers for your phone from Hardware Manager on your OS, unplug your phone, then plug it back in when you're in recovery, and your OS should pull the right drivers to get ADB working. Still, you've got fastboot so the best option for you at the moment is to just restore your phone to stock and go from there.
As I said, though, root doesn't work on Lollipop for our phone yet, and AFAIK we don't have the kernel sources yet for Chainfire (the developer of SuperSU amongst other things) to get root access working without causing bootloops.
Click to expand...
Click to collapse
I tried this thread but the problem is that the required mfastboot-v2 file link is not working for me.Anytime i try downloading it i get the message "Sorry, this file is infected with a virus,Only the owner is allowed to download infected files."
sleekykenny said:
I tried this thread but the problem is that the required mfastboot-v2 file link is not working for me.Anytime i try downloading it i get the message "Sorry, this file is infected with a virus,Only the owner is allowed to download infected files."
Click to expand...
Click to collapse
Huh.
http://forum.xda-developers.com/showpost.php?p=47820707 This contains just the mfastboot.exe file for each OS, it /should/ work since it's essentially the same file. Just put the files in that .zip into your folder with adb and fastboot in it, and you should be good to go.
Traediras said:
Huh.
http://forum.xda-developers.com/showpost.php?p=47820707 This contains just the mfastboot.exe file for each OS, it /should/ work since it's essentially the same file. Just put the files in that .zip into your folder with adb and fastboot in it, and you should be good to go.
Click to expand...
Click to collapse
Thanks Dude, After your last message I rechecked the mfastboot-v2 folder on the thread and realised the only new file in there was the mfastboot.exe file so i quickly googled it and saw another thread in which i found the file.I downloaded it and then executed all the commands. Goshh I finally saw my phone boot up in a long time which brought a huge smile to my face.
I would like Thank all of you guys who took the time out to visit this thread and give me suggestions. THANK YOU BROS
I really appreaciate it. Happy new year
Glad to hear everything worked out for you. Happy New Year to you too.
Duplicate thread created by OP
Original is here
Please do not create multiple threads again.
Thread closed
I recently formatted everything on my nexus 6 and I mean everything, the OS too. And I can't fix it, there was nothing on the forums or threads about this and how to fix it. Could you please help me?
Boot into the boatloader and flash the fastboot image.
Sent from my DROID Turbo 2
I have Ben an apple guy for 5 years just bought the nexus, I know how to get in to the boot loader but how do I flash the image? I tried downloading the image from the Google developers website but it said it failed ins
talling it!
Big-Blunt said:
I have Ben an apple guy for 5 years just bought the nexus, I know how to get in to the boot loader but how do I flash the image? I tried downloading the image from the Google developers website but it said it failed ins
talling it!
Click to expand...
Click to collapse
you cant use the flash-all, you need to flash each part separately. ynzip the file, then flash each .img file sepately. btw, ive deleted the whole os before. if you already have twrp installed, it wouls be a much easier fix using twrp instead.
How do I unzip the file in the boot loader?
Big-Blunt said:
How do I unzip the file in the boot loader?
Click to expand...
Click to collapse
i dont remember the program i used on my laptop, maybe 7zip.
The file downloaded from Google has a second zip inside. Unzip twice with 7 zip. The system image is inside the embedded zip file.
I assume you have the SDK from Google... Place all image files in the platform tools folder. I rename the images boot, radio, system, etc. to simplify typing the commands when actually flashing the images. DO NOT add the, " .IMG" when renaming.
Then:
Fastboot flash bootloader bootloader.IMG
Fastboot reboot-boitloader
Then same for system, radio, data and cache with out the reboot line.
When all files are flashed then fastboot reboot and enjoy
My brains are exploding rn, idk what or how to do anything, maybe u will think I'm dumb but I don't know what u guys are saying, could anyone post full instructions on how I would do it
The ONLY thing that you need to revive your device is alive bootloader. Every OS has its bootloader, and it determines what to load before system loaded.
I guess you did that foolish things on recovery. Then it won't kill itself of bootloader for sure.
Then there's always a chance. Try to boot into bootloader and switch it to fastboot mode.
Just flash stock rom image provided by google as described above.
You need to do some googling about fastboot and/or look for the beginners guide posted in the forums. You could use wugsfresh toolkit as well. I'm not being a douche not linking them,I'm to stoned
Google anything you don't understand
Sent from my Nexus 6 using Tapatalk
Do you know if your bootloader is unlocked?
You say you're an Apple guy - are you using a Mac? If you have access to a Windows machine I suggest you install Wugfresh's Nexus Root Toolkit and use the "Install & test drivers" button to set up the required drivers to connect your Nexus 6 to the computer. The walkthrough is comprehensive and extraordinarily simple - brilliant piece of programming. There is no Mac version.
Download the factory image (https://developers.google.com/android/nexus/images?hl=en#shamu image MMB29K).
Find the Fastboot/ADB programs on the web (I may have used the Minimal ADB & Fastboot tool, I can't remember exactly) and create a directory containing both programs plus their associated bits and pieces. I recommend making the path as simple as possible - e.g. C:\ADB for ease of navigation ( see below).
(While reading up on this, I came across this, which you may find useful - http://www.android.gs/install-set-up-adb-mac-os-x-linux/).
Unzip everything in the factory image, including the zip inside the zip as Larzzzz82 said, then copy the unzipped *.img files into the ADB Fastboot directory.
Boot your N6 into bootloader.
Open a CMD window and navigate to the ADB directory.
To check that you're connected, type (you don't need caps, this is just to make it clearer) FASTBOOT DEVICES. You should see something like "djdgkdjhgkdfj device" in response; if it's blank you're not connected - go through the driver setup again to see what you've missed.
Once you're successfully connected, you can install your new image following the instructions in this thread:
http://forum.xda-developers.com/google-nexus-5/help/stuck-launching-flashstock-bat-t3244470
I did ask for an expert to run a more experienced eye over them to correct any errors or to remove any pointless reboot commands, but nobody did either, so I guess they're ok. It's what I did and it worked for me. I've just noticed that it includes a line "fastboot flash recovery twrp.img" which you can ignore for the moment - though you may want to do this later when you have a working device.
Come back if you want any clarifications.
Happy new year (and, I hope, device...)
I tried I guess flashing the image through the recovery mode in the mount section but it said it failed,
Big-Blunt said:
I tried I guess flashing the image through the recovery mode in the mount section but it said it failed,
Click to expand...
Click to collapse
No no no you do not flash images through the recovery
Use Wugfresh's Nexus root and toolkit to restore it. Pretty easy.
@wolfen69 - duck and take cover...
I was going to suggest exactly that, since I'm a big fan of Wugfresh's NRT, but recommending it doesn't half bring down the flak... that's why I recommended using it initially at least to get the PC set up properly to connect and then get on with learning how to do it manually.
Personally in this situation using the NRT is exactly what I'd do myself. But now I'm retiring to my bunker for a while.
dahawthorne said:
@wolfen69 - duck and take cover...
I was going to suggest exactly that, since I'm a big fan of Wugfresh's NRT, but recommending it doesn't half bring down the flak... that's why I recommended using it initially at least to get the PC set up properly to connect and then get on with learning how to do it manually.
Personally in this situation using the NRT is exactly what I'd do myself. But now I'm retiring to my bunker for a while.
Click to expand...
Click to collapse
That's OK if people disagree with my recommendation. People are entitled to their opinions.
I tried for hours to do it the manual way and could never get it to work. And I'm a person who is VERY tech savvy. I had a computer repair business and have written advanced linux tutorials. I gave up and started using wugfresh. Has worked great for me. Others are free to do what works for them.
If you dont flash the images through the recovery mode then how do you flash it? I cant flash through command because the phone dosent have usb debugging enabled and its not in developer mode. I tried the nexus root toolkit as well and that didnt work either. Plz i need help!
So how much of my instruction did you follow? What exactly have you tried? Step by step. If you're vague then we can't help you. Error messages?
How did you delete the OS if your phone isn't unlocked?
Sent from my DROID Turbo 2
So i put it in recovery mode and when i tried resetting to factory i accidentally clicked advanced wipe and deleted everything so now its stuck in the boot loop. What i have tried was i downloaded the img file 6.0 shamu from googles site and drag and dropped on internal memory with my pc. Then in recovery mode i went mount and selected the img and it said error.
I nearly bricked my Razr i XT when downgrading from a Kitkat update to JB 4.1.2 but thanks to the great work here I am making some progress but cannot get Recovery or Root. the unlocking of bootloader via the Motorola website went fine and thanks to this post
http://forum.xda-developers.com/showthread.php?t=2239706 I got the rom I wanted, and it's fine.
I have read many other tutorials on installing a recovery and have downloaded and tried 6 or 7 CWM and TWRP images
but it never completes - fastboot says it has, but the phone stubbornly hangs at the flashing.
I have no problems getting into fastboot, but failed many times, and in desperation have tried with USB debugging on and off
and with and without sim and sdcard inserted.
attached are some photos to show where I am stuck at, and I would greatly appreciate some help
carkev said:
I nearly bricked my Razr i XT when downgrading from a Kitkat update to JB 4.1.2 but thanks to the great work here I am making some progress but cannot get Recovery or Root. the unlocking of bootloader via the Motorola website went fine and thanks to this post
http://forum.xda-developers.com/showthread.php?t=2239706 I got the rom I wanted, and it's fine.
I have read many other tutorials on installing a recovery and have downloaded and tried 6 or 7 CWM and TWRP images
but it never completes - fastboot says it has, but the phone stubbornly hangs at the flashing.
I have no problems getting into fastboot, but failed many times, and in desperation have tried with USB debugging on and off
and with and without sim and sdcard inserted.
attached are some photos to show where I am stuck at, and I would greatly appreciate some help
Click to expand...
Click to collapse
U said fastboot hangs at flashing the recovery, but on the command lines on your PC it says finished. Have u tried booting into recovery?
What recovery did u use and where did u get it?
USB debugging, simcard and sdcard don't have anything to do with fastboot. But it is likely that u didn't know that
thanks for looking at this.
I did try booting into recovery from my PC by after rebooting it and then taking the recovery option, but the phone hung at the Motorola bootloader unlocked warning screen.
this link was typical of the various tutorials I used: http://androidteen.com/motorola-razr-i-how-to-root-and-install-clockworkmod-cwm-recovery-on-android-4-1-2-jelly-bean-firmware/
to be fair I cannot recall where I got all the recovery images from - I have that many, and had to rename them recovery.img, so cannot remember the original download names
update:
I have just tried an app from the google play named Root Android, which advised trying other apps - Kingroot, Framaroot & Towelroot,
but they all failed .
what did catch my eye yesterday was the yellow text when in fastboot that says 'dismatched partition entry'
I ignored it as the img files I was trying to flash are all much smaller than the 100mb stated,
but today I am beginning to think that perhaps my recovery partition is corrupt and look for ways to repair it.
does that make any sense?
carkev said:
update:
I have just tried an app from the google play named Root Android, which advised trying other apps - Kingroot, Framaroot & Towelroot,
but they all failed .
what did catch my eye yesterday was the yellow text when in fastboot that says 'dismatched partition entry'
I ignored it as the img files I was trying to flash are all much smaller than the 100mb stated,
but today I am beginning to think that perhaps my recovery partition is corrupt and look for ways to repair it.
does that make any sense?
Click to expand...
Click to collapse
That could be it. Try flashing a rsd lite package from JB. Than go to the recovery and see if u have stock back.
Hazou said:
That could be it. Try flashing a rsd lite package from JB. Than go to the recovery and see if u have stock back.
Click to expand...
Click to collapse
thanks HazouPH, I'll give that a go
I have solved my problem with CWM:victory:
whilst I am not 100% certain I am pretty much sure it was a driver problem - for those who this may benefit, here is what I did.
1. I did not reflash my phone, but stayed with the one in my original post.
2. remember that the main problem was that Fastboot said I had succeeded in flashing a Recovery image, but that the phone 'hung'
at flash as in my photo. and then from my phone I could not get to recovery from the fastboot menu .
3. I stumbled across a posting (on XDA, but I cannot remember where) that said the Motorola drivers were not as good as they should be and that the Motohelper one's would be fine - so I downloaded them, and have attached the zip below.
4. I then decided to tidy up my PC and uninstalled all mobile phone drivers, plus any redundant USB Device drivers
5 for the USB tidying up I tend to use USBdview, which is superb and can be found here
6 when all this was done I simply tried the reflash of CWM - and got the same situation I had been having all along
but amazingly, when I selected 'recovery' it went in CWM - I nearly fainted with surprise!
from all this I can only assume it was a driver problem as I had changed nothing else.
perhaps it was Motohelper drivers- perhaps it was USBdview that did it for me - I will never really know, nor care!
I now have CWM v6.0.1.9 - it is touchscreen and permanent, plus I use the cute Reboot by app by Petrus to control my phone.
happy days!
It's exactly as the title mentions...
Basically I had this tablet for two years, and I love this tablet, we've been through a lot when it came to flashing ROMs and other stuff, the journey so far has been awesome and I don't want it to end here and I won't give up on this tablet!
So here goes... basically I have installed the Magisk Manager app and in the app I chose to install Magisk V14.0 (I chose the recommended option) and once it has finished downloading and installing I then decided to reboot it. Upon rebooting i noticed that the kindle kept rebooting every 3 seconds, so I knew at that point I seriously screwed up!
I'm on the resurrection remix (marshmallow) and when it was installing the Magisk file it said it was updating the boot.img, I think that's the reason why my kindle is acting up. I don't know really know how to fix this issue as I've tried to go into recovery but it simply will not allow me to because it keeps rebooting and doesn't even give me a chance (which is giving me a headache). I looked on similar posts and users have said that a fastboot cable is needed, but I don't have one and I was wondering if using a normal USB cable would do the trick with ADB commands... if possible. If this requires me to purchase (or make) a fastboot cable then I will gladly order (or make) one.
And if ADB method does work, please tell me specific commands to use, and so. Also I have tried getting my laptop (windows 10) to recognise my device, but even when attached and the tablet is on my device isn't showing in device manger, I have downloaded the SDK tools (not manager) and even then I can't use ADB commands in CMD. I typed "ADB shell" (without commas) and even then it won't allow me to access ADB (so please guide me on this area as well).
If you're a user who is interested in helping others and likes to face a challenge, then please step right up and help me as I need all the help at this point! Thank you!
Stone. Cold said:
It's exactly as the title mentions...
Basically I had this tablet for two years, and I love this tablet, we've been through a lot when it came to flashing ROMs and other stuff, the journey so far has been awesome and I don't want it to end here and I won't give up on this tablet!
So here goes... basically I have installed the Magisk Manager app and in the app I chose to install Magisk V14.0 (I chose the recommended option) and once it has finished downloading and installing I then decided to reboot it. Upon rebooting i noticed that the kindle kept rebooting every 3 seconds, so I knew at that point I seriously screwed up!
I'm on the resurrection remix (marshmallow) and when it was installing the Magisk file it said it was updating the boot.img, I think that's the reason why my kindle is acting up. I don't know really know how to fix this issue as I've tried to go into recovery but it simply will not allow me to because it keeps rebooting and doesn't even give me a chance (which is giving me a headache). I looked on similar posts and users have said that a fastboot cable is needed, but I don't have one and I was wondering if using a normal USB cable would do the trick with ADB commands... if possible. If this requires me to purchase (or make) a fastboot cable then I will gladly order (or make) one.
And if ADB method does work, please tell me specific commands to use, and so. Also I have tried getting my laptop (windows 10) to recognise my device, but even when attached and the tablet is on my device isn't showing in device manger, I have downloaded the SDK tools (not manager) and even then I can't use ADB commands in CMD. I typed "ADB shell" (without commas) and even then it won't allow me to access ADB (so please guide me on this area as well).
If you're a user who is interested in helping others and likes to face a challenge, then please step right up and help me as I need all the help at this point! Thank you!
Click to expand...
Click to collapse
Yes, you are going to need a fastboot cable. You can pick one up on Amazon for cheap or you can make your own by using some tutorial online. After you get the fastboot cable, use the Kindle Fire restore tool that I will link down below. Download it (it will take a while) and run it. Please read the directions because I didn't at first and I boot looped my Kindle by installing older recovery and boot image. After this is complete your Kindle will work again. I wouldn't recommend installing Magisk again because it modifies the boot loader. Sorry.
KFHD Restore tool (that tool that I mentioned): https://forum.xda-developers.com/showthread.php?t=1951254
Thank you for this, will. I will follow your instructions once I have received my fastboot cable
Again, thank you. I have left my tablet on my shelf for quite some time now and didn't really have time to fix it due to college work, and so. But I will definitely let you know the results :fingers-crossed:
I made pretty mutch the same error like you and flashed Magisk 12. I used the fastboot cable, entered fastboot and used the recovery tool to restore recovery and stock Rom with supersu and apex launcher. After following exectly the steps in 2. Bootloader and twrp. The problem I am facing is the same I faced before. After flashing linearOS 14 with twrp. I reboot from recovery. At first it showes the orange logo and the the blue. And it stays at blue logo for hours.
I don't know what to do. The strange thing is. I can boot in the recovered Amazonfire OS. But I can't flash any costum Rom.
I have no idea what I made wrong during the process. I followed all steps and repeated the procedure 3 times.
Always ending in blue logo.
Even without flashing any rom. Only following the steps to flash twrp with all the other stuff I am stuck on blue screen.
Please I need advice. Help me