i spent 3 days trying to fix my kindle but i couldn't
first i rooted my kindle ,then by mistake i wiped OS,so the kindle stuck on logo.then i login recovery mode and installed the new version 6.3.2
but now i lost the root and it still stuck.
i tried many times with many ways but i almost lot the hope.
adeeb101 said:
i spent 3 days trying to fix my kindle but i couldn't
first i rooted my kindle ,then by mistake i wiped OS,so the kindle stuck on logo.then i login recovery mode and installed the new version 6.3.2
but now i lost the root and it still stuck.
i tried many times with many ways but i almost lot the hope.
Click to expand...
Click to collapse
You need a factory cable.
soupmagnet said:
You need a factory cable.
Click to expand...
Click to collapse
the problem is i''m not in USA ,its not available here
is there another way to fix it?
adeeb101 said:
the problem is i''m not in USA ,its not available here
is there another way to fix it?
Click to expand...
Click to collapse
You can make one yourself with a little skill and/or ingenuity, or you can check with @SkOrPn (I believe he ships to all over the world).
soupmagnet said:
You can make one yourself with a little skill and/or ingenuity, or you can check with @SkOrPn (I believe he ships to all over the world).
Click to expand...
Click to collapse
thank you i'll see what i can do
wait a minute, I rooted mine with a stock micro-USB cable
adeeb101 said:
thank you i'll see what i can do
Click to expand...
Click to collapse
Since I already see this coming, I'll go ahead tell you where you went wrong and how to avoid it in the future.
First off, there's really no need to "root" your Kindle Fire. The steps required to root the Kindle Fire involve installing custom recovery (TWRP in this case) to gain temporary root permissions so you can push Superuser.apk and the SU binary. However, all custom ROMs come pre-rooted, so rooting beforehand is unnecessarily redundant. Even if you wanted to keep the stock OS, there is a stock based ROM called MoDaCo that will give you what you want while saving you pretty much all the work of having to do whatever you wanted to do with a rooted stock device anyway.
Second, with custom recovery already installed, the only reason to install the 6.3.x software update from Amazon, is to revert the device to 100% stock (i.e. no root, no recovery, no custom bootloader). Where you failed is in attempting to install the update.zip without first doing a factory reset in recovery. The resulting problem will leave you with a device that has no working shell, and therefore no ability to change bootmodes or install custom recovery again.
The factory cable (mentioned earlier) puts the device in fastboot mode where you can reinstall custom recovery, custom bootloader, and change bootmodes using fastboot commands (or some script based utility), then you can use custom recovery to properly install a ROM of your choice (remembering to factory reset). It should also be noted, that you should never wipe anything in custom recovery until you have successfully used it to create a backup. Be sure to save your system partition at the very minimum, and you can always go back to delete it afterwards.
Related
first timer here,
so I had my fire tv for a week it was rootable so I had it rooted and running on 51.1.4.1_514013920
fixed, for some reason i decide to install boot menu, so I could just update once the 51.1.4.2 comes out
and now it would not boot kernel. every time i try it just loops back I could still boot in to recovery
but i already have the rom removed from the device
I just wanna ask if there's anyway i could load the rom back into the firetv with recovery mode
and install it from there? Or could i remove the boot menu in anyway?
thank you so much for your help
gk83916 said:
first timer here,
so I had my fire tv for a week it was rootable so I had it rooted and running on 51.1.4.1_514013920
fixed, for some reason i decide to install boot menu, so I could just update once the 51.1.4.2 comes out
and now it would not boot kernel. every time i try it just loops back I could still boot in to recovery
but i already have the rom removed from the device
I just wanna ask if there's anyway i could load the rom back into the firetv with recovery mode
and install it from there? Or could i remove the boot menu in anyway?
thank you so much for your help
Click to expand...
Click to collapse
If you can boot in recovery install 51.1.4.0_514006420-rooted+updated, this is the last firmware that does not required a boot menu. As far as I know 51.1.4.1 requires it so not sure how did you manage to run this rev without the boot menu. Let me guess, did you try installing boot menu using Firetv Utility s/w? After reverting back to 51.1.4.0 follow the guide from AFTnews and install boot menu manual sending one commend at the time.
Thank you for the reply
But how do I install the frimware in recovery?
Because u had it deleted from the firetv
Is there any way I could load it back in the within recovery?
gk83916 said:
Thank you for the reply
But how do I install the frimware in recovery?
Because u had it deleted from the firetv
Is there any way I could load it back in the within recovery?
Click to expand...
Click to collapse
I've always used adb push but if that's not an option (because you can't connect) I'm pretty sure you can copy the update to a usb drive then insert in aftv and get it from there. Actually I've read that's the preferred method for lots of people.
But it doesn't hurt to re-read Rbox's threads and/or aftvnews guides.
KLit75 said:
I've always used adb push but if that's not an option (because you can't connect) I'm pretty sure you can copy the update to a usb drive then insert in aftv and get it from there. Actually I've read that's the preferred method for lots of people.
But it doesn't hurt to re-read Rbox's threads and/or aftvnews guides.
Click to expand...
Click to collapse
So I could just plug a USB drive in there and it would work?!
Thank you so much I will give it a try tonight
alright this is what happened I finial took care of this boot loop thing
the reason is i install boot menu twice so once the first boot menu try
to boot into kernel it goes to the second boot menu and that's how the
boot loop started
luckily i could still get into recovery so from there I tried everything
finally i find the think called advanced putty
from there I was able to load 5140 and removed both menus
reroot busybox did everything and now got a fire tv fully working
rooted and all good
Thank everybody for helping out
good luck
HI Guys,
I need some help, i cant peform a factory reset or boot into CWM, i was not able to reboot into CWM after the first installation. I rooted my AFTV these are the steps.
1) block updates on router.
2) fire tv running stock version 51.1.0.1
3) rooted fire tv (installed towelroot, supersu and busybox)
4) disable updates via adb on the fire tv
5) partially unlock boot loader
6) install CWM 6.0.5.1.4a (yes i granted su permission)
At this point fire tv rebooted but it did not bring CWM instead it went to straight to normal amazon boot. I tried alt+printscn approach but didn't work. When i try to get into cwm via adb command "adb reboot recovery" it will reboot and for a split sec i see blue screen and but then it boots up in normal amazon menu.
So i decided to do factory rest and start over.....problem is it is not really resetting the box, it takes me to the initial amazon sign in screen, i enter my login info and bang into main menu and all my apps that was there before are still installed.
Good news is i can still adb to the box and have root access.
any suggestion who to fix this?
I am still running on stock version 51.1.0.1 and i have not installed rbox boot menu. Also, i have done rooted 6 boxes so i am fairly familiar with the process and steps to follow.
Thank you
Try this.....
http://www.aftvnews.com/how-to-revert-an-amazon-fire-tv-back-to-stock-recovery-and-stock-software/
bula1ca said:
Try this.....
http://www.aftvnews.com/how-to-revert-an-amazon-fire-tv-back-to-stock-recovery-and-stock-software/
Click to expand...
Click to collapse
I also tried to upgraded but after the zip file was adb to the box fire tv did reboot but didn't go thru the installation process.
Any other suggestion guys please? I hate to return this box since it has root since it is getting harder and harder to find AFTV which has root able firmware?
I have been trying to get into CWM via "Alt+print Scrn + i" for few days now but without any luck i have tried this with wired and wireless keyboard, I hold these 3 keys simultaneously as soon as i see the white amazon logo and again when i see the colorful amazon log. Am i doing something?
However, when i do manage it get into CWM. What should i do? Should i select wipe data/Factory reset option? Will this take my AFTV to the way it came from amazon? I am still running amazon stock version 51.1.0.1 and fully rooted with Super su and busybox installed.
Thank you
ashsha7877 said:
I also tried to upgraded but after the zip file was adb to the box fire tv did reboot but didn't go thru the installation process.
Any other suggestion guys please? I hate to return this box since it has root since it is getting harder and harder to find AFTV which has root able firmware?
I have been trying to get into CWM via "Alt+print Scrn + i" for few days now but without any luck i have tried this with wired and wireless keyboard, I hold these 3 keys simultaneously as soon as i see the white amazon logo and again when i see the colorful amazon log. Am i doing something?
However, when i do manage it get into CWM. What should i do? Should i select wipe data/Factory reset option? Will this take my AFTV to the way it came from amazon? I am still running amazon stock version 51.1.0.1 and fully rooted with Super su and busybox installed.
Thank you
Click to expand...
Click to collapse
You need to get in CWM to upgrade to a pre-rooted image.
Have you tried to downgrade (reverse) to factory as per above link? That should work without no issues, should bring your box back to stock and you can start from zero again. I done it numerous times however you need to read carefully and follow the guide step by step sending all the commands one by one in ADB
bula1ca said:
You need to get in CWM to upgrade to a pre-rooted image.
Have you tried to downgrade (reverse) to factory as per above link? That should work without no issues, should bring your box back to stock and you can start from zero again. I done it numerous times however you need to read carefully and follow the guide step by step sending all the commands one by one in ADB
Click to expand...
Click to collapse
I tried to revert it back to stock following aftvnews guide step by step, read it over and over before actually doing it but on the final steps, AFTV will reboot but does not install the actual files.
i also rooted another box last night and everything went fine so i am not sure whats up with this box.
Thanks
hello i recently rooted and installed cm11 on my FP, i just did a clean system partition flash, then flashed pa_gapps. now screen is stuck at black screen with amazon logo. what should i do? i did get the phone to connect to the pc, i got it working using the stock usb cord phone came with. now the phone not connecting to pc anymore.
what can i do to return the phone to factory setting? or at least to get the cm11 running.
azheng said:
hello i recently rooted and installed cm11 on my FP, i just did a clean system partition flash, then flashed pa_gapps. now screen is stuck at black screen with amazon logo. what should i do? i did get the phone to connect to the pc, i got it working using the stock usb cord phone came with. now the phone not connecting to pc anymore.
what can i do to return the phone to factory setting? or at least to get the cm11 running.
Click to expand...
Click to collapse
You mentioned clean partition flash and pa gapps but you didn't say you flash the cm11 zip. I assume you did? If not there's no os. Twrp will notify if the os isn't there but not sure about safestrap. I'd assume you need to flash it in fastboot now unless there's a button combo that can be utilized.
I'd take this to the cm11 thread. ggow might be able to assist.
KLit75 said:
You mentioned clean partition flash and pa gapps but you didn't say you flash the cm11 zip. I assume you did? If not there's no os. Twrp will notify if the os isn't there but not sure about safestrap. I'd assume you need to flash it in fastboot now unless there's a button combo that can be utilized.
I'd take this to the cm11 thread. ggow might be able to assist.
Click to expand...
Click to collapse
well problem is i cant even get into safestrap recovery right now. when i hard reset the phone, try to boot it. its stuck at amazon screen. good thing right now is when i plug the phone in the pc, it makes connection. maybe i can sideload a os using the pc?
azheng said:
well problem is i cant even get into safestrap recovery right now. when i hard reset the phone, try to boot it. its stuck at amazon screen. good thing right now is when i plug the phone in the pc, it makes connection. maybe i can sideload a os using the pc?
Click to expand...
Click to collapse
That probably IS a good thing. But if there's no OS installed I'd think it would automatically boot to recovery? I've only owned this phone a short time and before last week never used safestrap. Normally I'd either try to boot recovery with a button combo (haven't needed to on this phone.) Or connect via adb and use the command "adb reboot recovery".
I'd say you have a better chance or at least a quicker response if you head over to ggow's thread. Good luck
KLit75 said:
That probably IS a good thing. But if there's no OS installed I'd think it would automatically boot to recovery? I've only owned this phone a short time and before last week never used safestrap. Normally I'd either try to boot recovery with a button combo (haven't needed to on this phone.) Or connect via adb and use the command "adb reboot recovery".
I'd say you have a better chance or at least a quicker response if you head over to ggow's thread. Good luck
Click to expand...
Click to collapse
thanks for the help, i think recovery went bye bye along with the OS lol
Hi,
any update on this thread? I've been stuck also. I had safestrap. I supposed to flash a cleamsystempartion but I accidentally restart it without flashing new rom and now i am stuck in Fire Phone Logo. I still can access the stock recovery tho. Please help :crying::crying::crying:
try to flash your phone back to stock rom
any solution to this problem? I am stuck with same problem.
siddharth_bhal said:
any solution to this problem? I am stuck with same problem.
Click to expand...
Click to collapse
same problem here: can't start safe stripe and stuck at Amazon. tried to start the phone pressing volume up and power button, see if you can get into the build-in recovery. if it works, you can wipe the data and then use ADB sideload to flash in official rom (should be a bin file, i tried 4.6.1 version) and bring back your phone .
fire phone keep rebooting
my fire phone is keep rebooting with amazon logo up to 5 minutes and suddenly turned of i want to know the problem and how to fix it so please help me.
Have any of you guys tried the instructions in this thread: https://forum.xda-developers.com/fire-phone/general/reverting-fire-phone-to-stock-t3288890
I have bricked Fire phone quite a few times and everytime I followed his instructions and the lifehacker instructions that he linked to install adb and ADB sideloaded 4.6.6.1. without any problems.
My fire keeps rebooting and gets stuck with the amazon logo on it pls i need ur help urgently
Bahdtyga said:
My fire keeps rebooting and gets stuck with the amazon logo on it pls i need ur help urgently
Click to expand...
Click to collapse
U need a new fire phone, talk with amazon from your country or region or the seller from where you got fire phone!
So, I have this Kindle Fire 1st Gen (2011), and lately I got this urge to customize it and install some further version of Android. Though, with ups and downs I managed, I was pretty much not satisfied with the stability of the customs ROMs.
It was then that I thought the stock firmware was the only best choice for an outdated device like the Kindle fire. So I made my mind to revert back to Stock, wherein I screwed up real bad, left no stone unturned, yet I'm stuck in the rut.
Need Your Help
Let Me Walk you through it all so you'd get a hint where and how I screwed up
1. Rooted the Kindle Fire 1, and installed TWRP 2.2.2.1
2. Tried Installing Custom ROMs, but there was nothing much available for the Stock Bootloader.
3. So opted for the OtterX Bootloader, as they had a variety of ROMs, for which a newer version of TWRP is required, 2.7.X.X, I believe.
TECHNICALLY, EVERYTHING WAS FINE UP TILL HERE
This is where I screwed up while trying to do a roll back..
1. While I was supposed to replace the OtterX Bootloader with the Stock one, I accidentally flashed TWRP 2.2.2.1, first.
2. Clearly, I couldn't boot up into recovery since then, cuz the 2.2.2.1 might be specifically designed for the AMAZON STOCK BOOTLOADER.
3. Before all of that I had wiped away the OS from the device, so I'm stuck here with no OS n no recovery, either.
4. Thought ADB and Fastboot could help, but I kinda remember I screwed up with that too (don't remember exactly what I did).
So this is the current situation
1. NO OS
2. NO RECOVERY
3. I can only setup the fastboot mode, but windows says, it doesn't recognize the device (probably something to do with the drivers, but I've literally rubbed my ass off finding the particular drivers, but to no good)
IF ONLY I COULD SOMEHOW GET FASTBOOT TO WORK, I'D BE GOOD BY MYSELF, I'LL TAKE CARE OF IT ALL, BUT CAN'T, JUST CAN'T
JayZ996 said:
So, I have this Kindle Fire 1st Gen (2011), and lately I got this urge to customize it and install some further version of Android. Though, with ups and downs I managed, I was pretty much not satisfied with the stability of the customs ROMs.
It was then that I thought the stock firmware was the only best choice for an outdated device like the Kindle fire. So I made my mind to revert back to Stock, wherein I screwed up real bad, left no stone unturned, yet I'm stuck in the rut.
Need Your Help
Let Me Walk you through it all so you'd get a hint where and how I screwed up
1. Rooted the Kindle Fire 1, and installed TWRP 2.2.2.1
2. Tried Installing Custom ROMs, but there was nothing much available for the Stock Bootloader.
3. So opted for the OtterX Bootloader, as they had a variety of ROMs, for which a newer version of TWRP is required, 2.7.X.X, I believe.
TECHNICALLY, EVERYTHING WAS FINE UP TILL HERE
This is where I screwed up while trying to do a roll back..
1. While I was supposed to replace the OtterX Bootloader with the Stock one, I accidentally flashed TWRP 2.2.2.1, first.
2. Clearly, I couldn't boot up into recovery since then, cuz the 2.2.2.1 might be specifically designed for the AMAZON STOCK BOOTLOADER.
3. Before all of that I had wiped away the OS from the device, so I'm stuck here with no OS n no recovery, either.
4. Thought ADB and Fastboot could help, but I kinda remember I screwed up with that too (don't remember exactly what I did).
So this is the current situation
1. NO OS
2. NO RECOVERY
3. I can only setup the fastboot mode, but windows says, it doesn't recognize the device (probably something to do with the drivers, but I've literally rubbed my ass off finding the particular drivers, but to no good)
IF ONLY I COULD SOMEHOW GET FASTBOOT TO WORK, I'D BE GOOD BY MYSELF, I'LL TAKE CARE OF IT ALL, BUT CAN'T, JUST CAN'T
Click to expand...
Click to collapse
have you looked at my thread
Started a Thread [How To] Fix OtterX Install Errors, Partition sizes, Unable to Mount System... with some possible fixes for those having issues since converting to OtterX, with pushing files, failure to mount system errors when installing Lollipop Roms...
Sent from my XT1096 using Tapatalk
I have been trying for a while now to root my phone with magisk. Everytime I go to root it at the end I go into a boot loop and can't go to recovery then I have to reinstall the version of Android 13 I'm using but still never rooted when I do so.
Samuel1307 said:
I have been trying for a while now to root my phone with magisk. Everytime I go to root it at the end I go into a boot loop and can't go to recovery then I have to reinstall the version of Android 13 I'm using but still never rooted when I do so.
Click to expand...
Click to collapse
Do you have TWRP installed?
webhook said:
Do you have TWRP installed?
Click to expand...
Click to collapse
No
Samuel1307 said:
I have been trying for a while now to root my phone with magisk. Everytime I go to root it at the end I go into a boot loop and can't go to recovery then I have to reinstall the version of Android 13 I'm using but still never rooted when I do so.
Click to expand...
Click to collapse
Rooting pixel phones are pretty straight forward and not much difficulties. Two different approaches:
1. If you are an experienced user and 100% sure what you are doing, then go back to your rooting process step by step to make sure you didn't miss anything.
2. If you are not sure that you have done everything correctly, then I would suggest you that you follow the steps which describe in this thread, believe it still the most detail explanation for rooting the pixel phones even today. https://forum.xda-developers.com/t/...ootloader-update-root-pass-safetynet.4356231/
Also posting your question on this thread could get you quicker response.
If after your trying of everything you still couldn't get it done, then describe your entire process when you ask for help without people have to guess what could went wrong.
PS: The only information which you shouldn't follow with that thread is "NOT" to use the latest platform tool, stay with version 33.0.3, version 34.0.1 has problem.
Samuel1307 said:
I have been trying for a while now to root my phone with magisk. Everytime I go to root it at the end I go into a boot loop and can't go to recovery then I have to reinstall the version of Android 13 I'm using but still never rooted when I do so.
Click to expand...
Click to collapse
I had the same issue. Right after flashing when booting for the first time it got stuck in a boot loop. Factory reset fixed it.
Stupid question also could be the wire your using and usb port
If you guys are bootlooping after flashing Magisk patched image...
You should use the Google's official Android Flash Tool to reset your device to a working state...
Then you should use badabing2003's PixelFlasher to root; it automates most of what's needed to root, and it has checks and protocols to make sure files are correct, versions are correct, and the right procedure happens in the right order -- taking out a lot of guesswork or mis-steps that might be happening that is causing bootloops.
Many/You would be surprised how many times PixelFlasher succeeds where many have failed; almost miraculously and/or inexplicably! It's why it's become rather famous tool for Pixels...
Samuel1307 said:
I have been trying for a while now to root my phone with magisk. Everytime I go to root it at the end I go into a boot loop and can't go to recovery then I have to reinstall the version of Android 13 I'm using but still never rooted when I do so.
Click to expand...
Click to collapse
fluxfield said:
I had the same issue. Right after flashing when booting for the first time it got stuck in a boot loop. Factory reset fixed it.
Click to expand...
Click to collapse
Previously rooted with Magisk modules?
Incompatibility with newer updates is more often than not the cause of bootloops.
Rebooting into safe mode will disable them.
Press and hold volume down when the bootloader unlocked warning screen appears. Then let go as soon as you feel a vibration.
You will boot into safe mode and modules will be disabled.
Then reboot normally and go into Magisk and re-enable only safe modules such as USNF.
Test the others one by one until you find the culprit. Usually it will be a font changing module or an AOSP mod .
It's pretty straightforward provided you have an unlocked bootloader, USB debugging and platform tools, The latest works for root alone btw.
In terminal
Code:
adb devices
Authorise adb in the popup window
Code:
adb reboot bootloader
If fastboot isn't recognising your phone install the USB driver
You may find it easier to install the driver in fastboot.
Code:
fastboot flash boot <path_to_magiskboot.img>
Code:
fastboot reboot
Profit.
Assuming you've patched the right boot.img file from the .zip within the factory image zip file and you're using magisk from github.
fil3s said:
You may find it easier to install the driver in fastboot.
Code:
fastboot flash boot <path_to_magiskboot.img>
Click to expand...
Click to collapse
Accidental mistake.... "image" was meant, not "driver".
...don't want OP chasing down an issue because of a miscommunication or confusion...
PixelFlasher is truly the easiest & most straightforward, honestly....
simplepinoi177 said:
Accidental mistake.... "image" was meant, not "driver".
...don't want OP chasing down an issue because of a miscommunication or confusion...
PixelFlasher is truly the easiest & most straightforward, honestly....
Click to expand...
Click to collapse
I meant that sometimes the google USB driver is easier to install in fastboot. Regards
fil3s said:
I meant that sometimes the google USB driver is easier to install in fastboot. Regards
Click to expand...
Click to collapse
aaahh...i see now...
sorry, i just made that assumption because you put the fastboot command to installing/flashing the image right after the sentence -- i made the mistake of connecting the two...
i should've known better as i was already initially confused as you don't install the driver AS a fastboot command...!