My story, used Fire off ebay, sweet deal,w/ 3.5.0. os. Used d630 Dell, Vista,clean install. Both same week.
Downloaded........... 4.6.1---3.5.0---4.6.3--,4.6.6,adbfastboot 15 sec 1.3/1.4.3,safestrap,kingroot,esfile,
1st attempt...root and safestrap said recovery installed but "go to recovery" button went to black screen, reboot only went to Amazon,lost recovery and os.
2nd attempt.... waited 3 days went back to the phone, vol up/power/plugged into laptop at the same time, boom I had os(?), tried again 3x to recovery through safestap,still no recovery but system was back. I upgraded ota to 3.5.1, restored recovery, kept root.
Now everything is good except the "cannot read update.bin". I noticed in properties ,4.6.1 is actually is a .zip but renamed .bin. If i convert it using some kind of freeware, will the result be a brick or "can read update.bin"?
Why does every place i read, 4.6.6 is the latest update but mine doesn't see beyond 3.5.1?
Do I still have to download to 3.5.0 from 3.5.1 to do 4.6.1, to install cm?
Why doesnt safestap install recovery on 3.5.0?
I haven't tried safestap on 3.5.1, not until I can adb or push/fastboot????
Related
Ok long story short, im borderline ripping my hair out.
I followed a YT video as to how to put TWRP on my KF. Followed it and installed and extracted the utility tool, the latest verison. I got the "run" screen to come up and the red lettering came up I pressed 5 to install TWRP I accidentally hit the other button which I think installed CWM recovery.
I went back in and tried to put TWRP. Now its giving me an Oops message when I tried to put TWRP in.
Nowwww I installed a different version of the utility tool it was like the 3rd to newest version. I sucsessfully installed the TWRP it said it was "ALL DONE!" but I cant get any other screen but the blue and white kindle fire screen. The only recovery I can get into is the red text looking CM screen. I even tried to do a normal flash I DL'd the rom I wanted put it on my KF and did apply update form sd.. flashed it.. NOTHING loads. GRRR!!
Anyway,
I cant seem to get to the TWRP screen I need to get to, the one with the gray buttons?
ANY help would be appreciated. Thanks.
Try Smirkit
http://forum.xda-developers.com/showthread.php?t=1836005 but smirkit is the way to go...
Hi everyone. I have an old firetv that I haven't updated ever since I rooted it.
TL;DR: I would like to update the firmware to either the latest rbox custom rom or the latest official to get external USB disk functionality.
Unfortunately, I can't get past the white fire tv logo screen no matter which method I use (both bootleg rom and the official amazon update process).
adb reboot recovery => white logo. There are no USB devices attached to the firetv fyi while I'm booting.
I rooted my device using the adbfire tool and I distinctly remember I never got the clockworkmod and the bootloader unlock steps to work. I figured I don't really need that anyway, so I've been using the device just fine with Kodi. BTW, the device is not bricked. I just have to replug the power when it gets stuck on the white logo screen for it to go back to normal.
I think I somehow corrupted the recovery partition (if that makes any sense?).
Because I wasn't going anywhere with the unlock->bootleg rom process, I decided I don't care about root anymore.
I reenabled updates (pm enable com.amazon.dcp) and let the device download the latest rom though the amazon system menu. I saw the progress bar go 100% and the device rebooted... alas white logo screen. I gave it half hour then hard boot it. I'm back to my old rom... still works just fine but I need this external usb function for my vacation...
Regarding the boot unlock, the "partial unlock" steps work for me. i.e. I get "Attempting to unlock… All done!". However, the full unlock binary doesn't seem to have any affect after the autoreboot. aftv-full-unlock gives me the long random string as expected before it goes rebooting, but after it reboots and I 'adb shell', it gives me the [email protected] instead of root[email protected] (meaning the unlock didn't work).
How can I recover my recovery?
Just an update, I managed to fix this.
In my case, the aftv full unlock did not give me the root prompt (#) on adb shell. I was running 51.1.0.1.
On a whim, I decided to install the stock recovery (because I couldn't get into cwm) and try upgrading to 51.1.0.2 manually using these instructions http://forum.xda-developers.com/showthread.php?t=2796067
As soon as the system update finished and the firetv booted, I adb shell'd in and voila... root shell. I didn't even have to run aftv full unlock again. Apparently it was already fully unlocked, and I just had to upgrade from 51.1.0.1.
From there, I installed the latest ClockworkMod, upgraded to 51.1.4.0, installed the boot menu, then finally upgraded to the pre-rooted 51.1.6.3!
I have no idea how to root or anything like that, I bought this oneplus 3 and had a update a week later.. so when I did the software update it took me into teamwin recovery mode and now I don't know how to get back into my phone please help....
Did you buy the phone second hand or did you try to flash TWRP yourself? It shouldn't have TWRP installed by default.
Regardless, you can use TWRP to flash the latest update.
Given that you have TWRP, I'm assuming that you have an unlocked bootloader. Did you notice a warning pop up everytime you reboot your phone before? It should say something along the lines of "your device has been unlocked and can't be trusted". If not, you'll have to unlock it (it wipes your phone in the process).
If the bootloader is unlocked, you can simply download and flash the latest zip for OOS 4.0.3 in TWRP. This will update you phone and replace TWRP with the stock recovery (so you don't run into this problem again in the future when installing an OTA). If you don't intend to modify your phone in any way, then this is all you need to do, your phone should be functional.
There are plenty of threads with detailed guides on how to do all of this.
I'm also stuck on TWRP after stupidly downloading the latest OTA and I don't know what to do!
Phone won't boot normal, just goes off.
Situation:
- Bootloader, Fastboot and TWRP wil load.
- Device seen by windows
- Zip install in TWRP gets stuck at 'patching zip unconditiontally'
- Another zip flashes, but gets stuck at the end, no reboot option (manually but that's not the way)
Can someone please point me in the right direction? I don't care if I lose data, just want my phone back!
not helping:
Saying i'm a dipsh-t I know, I know, I will do better in the future, for now, help a brother out please
sndr1384 said:
I'm also stuck on TWRP after stupidly downloading the latest OTA and I don't know what to do!
Phone won't boot normal, just goes off.
Situation:
- Bootloader, Fastboot and TWRP wil load.
- Device seen by windows
- Zip install in TWRP gets stuck at 'patching zip unconditiontally'
- Another zip flashes, but gets stuck at the end, no reboot option (manually but that's not the way)
Can someone please point me in the right direction? I don't care if I lose data, just want my phone back!
not helping:
Saying i'm a dipsh-t I know, I know, I will do better in the future, for now, help a brother out please
Click to expand...
Click to collapse
Simple, check the OnePlus D/L sites for this one http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img and flash it by TWRP or fastboot to RECOVERY. Boot once with the official Recovery and all ist fine again.
This is issue of using a faulty twrp so for that when ur phone us booting up go to fastboot and flash twrp 3.0.4-1 and everything will work
emuandco said:
Simple, check the OnePlus D/L sites for this one http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img and flash it by TWRP or fastboot to RECOVERY. Boot once with the official Recovery and all ist fine again.
Click to expand...
Click to collapse
Similar Problem here:
just wanted to flash latest OOS 4.0.3, so I flashed back stock recovery with flashify and rebooted into recovery mode to flash the already downloaded OOS 4.0.3. zip. That's when it began to go poop! After rebooting it just went dark with no Chance to power it on again! No dice with power button, Volume up/down + power button, nothing! Not even the LED's are blinking when plugged in. So this one seems to be basically dead!
I got it once booting again after randomly pushing the buttons (after x minutes!?), but everytime I reboot the phone it just shuts off without beeing able to power it on again. At the Moment it's dead!
Any ideas what might happened? If I get it on again, should I immediately reset it to factory Settings?
I am kinda lost here! Any help/ideas would be much appreciated!
Flashify? Never used it and never trusted apps which flash stuff on a running system. Use fastboot and reflash the recovery partition. Link to recovery is in my former post.
fastboot flash recovery PATHTOIMGFILE
Thank you for your advice! Still a lot to learn! Got it up again, will try as you suggested!
It appeared that my stock recovery file was corrupted , but all is fine again! Thank you very much!
Mannycolon85 said:
I have no idea how to root or anything like that, I bought this oneplus 3 and had a update a week later.. so when I did the software update it took me into teamwin recovery mode and now I don't know how to get back into my phone please help....
Click to expand...
Click to collapse
I may have been the person you traded with to get the OnePlus 3, but I took the phone back and after 5 hours I got it up and running.
The phone would boot to TWRP, but even after wiping the entire system and dragging a ROM zip to the internal storage, reinstalling did nothing. It just kept booting back to recovery.
The solution entailed the following.
Download stock recovery IMG. Flashed through TWRP. Rebooted recovery and now was back to stock recovery.
Download the official OxygenOS ROM zip from the OnePlus website and changed the name to update.zip
Next I downloaded Android studio for access to ADB. I had never used ADB before, but I knew this was needed to push a file to the phone.
Needless to say, ADB kept freezing my computer when I would type in the commands to side load.
I deleted Android studio and installed a minimal ADB/Fastboot I found online. I opened my command prompt, typed the command for sideloading, and immediately got my installation starting. It took about 10 minutes to fully install. When it was finished, I rebooted and had a fully functioning OnePlus 3
Sent from my ONEPLUS A3000 using Tapatalk
On my AFTV2 I had flashed sloane pre-rooted 5.2.4.0 and TWRP Recovery V3. I decided I wanted to rollback to 5.0.5 because of FireStarter not working. I checked all the boxes under the Advanced Wipe section of TWRP and got the "Warning no OS installed..." error. I rebooted and I am stuck on the white Amazon logo with a slow flashing white LED. Through several attempts to use rbox's unbrick method, I never get past the "Waiting for preloader" stage. My computer detects the fire box but comes up with an error when installing the drivers. I don't know how to go about any repairs if I can't even get connected to it. I see others out there with issues similar to this but never quite find a solution for the lack of usb connectivity to make repairs.
From what I've read, you never wipe /system and then reboot.
It's a shame you did not read the red bold print on the AFTV2 ROMs page here: https://forum.xda-developers.com/fire-tv/development/firetv-2-sloane-prerooted-stock-images-t3309783
It says: WARNING: DO NOT FLASH 5.0.5.1 OR EARLIER IF YOU STARTED WITH VERSION 5.2.1.0 OR LATER
Everything I've read says if you do this you now have a paperweight.
You are indeed correct on all fronts... Thing is I never got to the rollback point. I never even attempted to install the old version over the new one. I got stuck right after the wipe not being able to do anything else. I would gladly take back what I already installed at this point.
WARNINGS
•It is extremely important you never reboot after a failure. This will most likely lead to a brick. If recovery is hung, you can use adb shell to run
Code:
killall recovery
to restart it
•It is also extremely important to never reboot after wiping /system.
Lesson learned. I thought it would reboot back into TWRP... I guess not.
I think I may be in this same boat. For some reason, my USB keyboard may have wigged out and ticked System, too.
Ugh
So is there really no solution at all, if you reboot after system wipe in TWRP?
Hello, I had the same issue. Wiped system and had to restart, at least I tought I had to.
So there is no solution than to get the fire tv alive again?
My Zenfone 2 (ZE551ML 4GB) dilemma:
*•*I unlocked the bootloader with the official bootloader app
*•*I flashed the latest TWRP via adb. In the recovery screen, I saw an android showing error. That's when the panic started.
*•*I Then I rooted my phone with the one click Zenfone root application (available in XDA)
*•*I installed the official TWRP manager from the playstore and flashed with it. That also didn't solve my problem. Actually, a new problem set in. The phone started bootlooping IN RECOVERY.
*•*I rebooted the phone and then flashed an old version of TWRP for my phone. That solved the problem.
*•*Now, I wanted to flash Lineage OS in my phone. According to a YouTube tutorial, I copied my required files (the custom ROM and OpenGAPPS) to my Micro SD and then from twrp's advanced wipe, deleted everything except for Micro SD. I know that was an extremely stupid move but please bear with me.
*•*Deleting everything made things hundred times worse. It seemed impossible to get the phone into recovery mode again. But after a long time, I did.
*•*Now onto flashing the new ROM. I did a factory reset with twrp and then flashed the ROM and immediately got Error 7. By googling a bit, I found that the only way to solve this problem was by deleting the assert lines from the updater-script in meta/com/google/android inside the ROM.
*•* When I reflashed it, the process completed but it showed an error: (E:unknown command [log])
*•* Then I overlooked it again as a quick google said it didn't matter. Then I successfully flashed OpenGAPPS. I rebooted my phone and it kept bootlooping until it was back in the recovery screen. Weird right?
*•*I didn't seem to find any workaround so I decided to restore stock ROM. I downloaded it and flashed it. It succeeded. I rebooted my phone. And. .
*•*My phone now vibrates when I power on the phone and then it shows a black screen. It reboots automatically. I know it does as the phone vibrated periodically after the reboot
*•* I also can't go into the bootloader menu. My phone seems dead but I really need to revive it. I can't afford a new phone. Could you guys help me out please?
LethalHoe said:
My Zenfone 2 (ZE551ML 4GB) dilemma:
*•*I unlocked the bootloader with the official bootloader app
*•*I flashed the latest TWRP via adb. In the recovery screen, I saw an android showing error. That's when the panic started.
*•*I Then I rooted my phone with the one click Zenfone root application (available in XDA)
*•*I installed the official TWRP manager from the playstore and flashed with it. That also didn't solve my problem. Actually, a new problem set in. The phone started bootlooping IN RECOVERY.
*•*I rebooted the phone and then flashed an old version of TWRP for my phone. That solved the problem.
*•*Now, I wanted to flash Lineage OS in my phone. According to a YouTube tutorial, I copied my required files (the custom ROM and OpenGAPPS) to my Micro SD and then from twrp's advanced wipe, deleted everything except for Micro SD. I know that was an extremely stupid move but please bear with me.
*•*Deleting everything made things hundred times worse. It seemed impossible to get the phone into recovery mode again. But after a long time, I did.
*•*Now onto flashing the new ROM. I did a factory reset with twrp and then flashed the ROM and immediately got Error 7. By googling a bit, I found that the only way to solve this problem was by deleting the assert lines from the updater-script in meta/com/google/android inside the ROM.
*•* When I reflashed it, the process completed but it showed an error: (E:unknown command [log])
*•* Then I overlooked it again as a quick google said it didn't matter. Then I successfully flashed OpenGAPPS. I rebooted my phone and it kept bootlooping until it was back in the recovery screen. Weird right?
*•*I didn't seem to find any workaround so I decided to restore stock ROM. I downloaded it and flashed it. It succeeded. I rebooted my phone. And. .
*•*My phone now vibrates when I power on the phone and then it shows a black screen. It reboots automatically. I know it does as the phone vibrated periodically after the reboot
*•* I also can't go into the bootloader menu. My phone seems dead but I really need to revive it. I can't afford a new phone. Could you guys help me out please?
Click to expand...
Click to collapse
Did you flash the MM bootloader compatible TWRP mentioned in the OP for LineageOS? That solves error 7.
Ragarianok said:
Did you flash the MM bootloader compatible TWRP mentioned in the OP for LineageOS? That solves error 7.
Click to expand...
Click to collapse
I did not do that. I remembered all the steps but forgot that. That is the primary cause of my problem. Anyway to solve it?
LethalHoe said:
My Zenfone 2 (ZE551ML 4GB) dilemma:
*•*I unlocked the bootloader with the official bootloader app
*•*I flashed the latest TWRP via adb. In the recovery screen, I saw an android showing error. That's when the panic started.
*•*I Then I rooted my phone with the one click Zenfone root application (available in XDA)
*•*I installed the official TWRP manager from the playstore and flashed with it. That also didn't solve my problem. Actually, a new problem set in. The phone started bootlooping IN RECOVERY.
*•*I rebooted the phone and then flashed an old version of TWRP for my phone. That solved the problem.
*•*Now, I wanted to flash Lineage OS in my phone. According to a YouTube tutorial, I copied my required files (the custom ROM and OpenGAPPS) to my Micro SD and then from twrp's advanced wipe, deleted everything except for Micro SD. I know that was an extremely stupid move but please bear with me.
*•*Deleting everything made things hundred times worse. It seemed impossible to get the phone into recovery mode again. But after a long time, I did.
*•*Now onto flashing the new ROM. I did a factory reset with twrp and then flashed the ROM and immediately got Error 7. By googling a bit, I found that the only way to solve this problem was by deleting the assert lines from the updater-script in meta/com/google/android inside the ROM.
*•* When I reflashed it, the process completed but it showed an error: (E:unknown command [log])
*•* Then I overlooked it again as a quick google said it didn't matter. Then I successfully flashed OpenGAPPS. I rebooted my phone and it kept bootlooping until it was back in the recovery screen. Weird right?
*•*I didn't seem to find any workaround so I decided to restore stock ROM. I downloaded it and flashed it. It succeeded. I rebooted my phone. And. .
*•*My phone now vibrates when I power on the phone and then it shows a black screen. It reboots automatically. I know it does as the phone vibrated periodically after the reboot
*•* I also can't go into the bootloader menu. My phone seems dead but I really need to revive it. I can't afford a new phone. Could you guys help me out please?
Click to expand...
Click to collapse
xfstk is the only way. go to following thread and do as suggested. one advice when you get into bootloader. flash raw without AFT. that is best.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785