Related
Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.
Same here on my Nex5.
It seems, that some custom zips changed my stock (rooted) rom in this way that I am not able to install the 4.4.2 update.
I got similar issue on my Nex4 in the past, I could help me out by flashing full rom (rooted) deodexed, but where can I find the full rom of 4.4.2 for my Nex5 now?
Anybody can give me a clue?
Thank u very much.
Greetz from Germany.. Fred
Lexus One said:
Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.
Click to expand...
Click to collapse
amplifier1980 said:
Same here on my Nex5.
It seems, that some custom zips changed my stock (rooted) rom in this way that I am not able to install the 4.4.2 update.
I got similar issue on my Nex4 in the past, I could help me out by flashing full rom (rooted) deodexed, but where can I find the full rom of 4.4.2 for my Nex5 now?
Anybody can give me a clue?
Thank u very much.
Greetz from Germany.. Fred
Click to expand...
Click to collapse
Hi Fred, and greetz from Ohio. I'm not aware of anything in the 4.4.2 flavor right now for the Nex10. I'm not sure about the Nex5. I think we're just going to have to wait. But I'd like to have the same thing. A lean & clean deodexed stock rooted 4.4.2 rom with a few performance tweaks. Like the old "Cleanrom" by scrosler. As for right now, did you try an ADB Sideload update to 4.4.2 using Wug's Toolkit? http://www.wugfresh.com/faqs/how-to-update-ota-not-working/
Lexus One said:
Hi Fred, and greetz from Ohio. I'm not aware of anything in the 4.4.2 flavor right now for the Nex10. I'm not sure about the Nex5. I think we're just going to have to wait. But I'd like to have the same thing. A lean & clean deodexed stock rooted 4.4.2 rom with a few performance tweaks. Like the old "Cleanrom" by scrosler. As for right now, did you try an ADB Sideload update to 4.4.2 using Wug's Toolkit?
Click to expand...
Click to collapse
Hi. Meanwhile i found a thread in nexus5 Android development area which contains both deodexed and odexed stock rooted full rom . so i just flashed odexed Version over my 4.4... Now i am on 4.4.2 finally... And still rooted..
Thank u anyway..
Greetz, fred
Lexus One said:
Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.
Click to expand...
Click to collapse
Hi,
You can try performing a full unroot in the SuperSU app if it still doesn't work... I had to adb sideload mine to work, don't know how it works with toolkit, but you have to first set your tablet to receive it. As you are on TWRP you simply go to advanced and select adb sideload, then try using the tool, or following the instructions on it to do so .
You cannot install a OTA zip like a Custom ROM zip, they are a little bit different hehe.
Hope this helps,
~Lord
PS.: This will work for N5 too.
I somehow got the idea that rooted Nexus devices with a custom recovery could handle OTA's without trashing the recovery. I guess I expected that I would lose root. I think I'm just going to wait for someone to put together a "CleanROM" based on 4.4.2 or newer. I've been waiting for a rom like this since I bought my Nex10 anyway. I don't think I'll suffer too much running on 4.4 until then.
Thanks to those who contributed, I'll remember your suggestions. Especially if I end up waiting a long time for a 4.4.2 based Cleanrom.
Update: Thanks to Wug's toolkit. I'm now running 4.4.2..
I should ask for a sticky for this but these instruction will work EVERY TIME if you are running either custom recovery or Root.
You will need the latest adb/fastboot from google, you can either install the SDK or download any of the many smaller adb/fastboot and libs for your os
You will need STOCK 4.4/4.3/4.2 recovery depending on what version of android you are currently on. Download the factory image from here. Open the zip within the package and pull out recovery.img and rename it stockrecovery.img
Copy your custom recovery to the adb folder name it twrp.zip or short name for whatever you are using I am using twrp.
You will need the correct OTA you are seeking to apply - rename it to something short simple and obvious - for this example I will use otaupdate.zip
If you wish to root get the latest patch (I believe its up to 1.75 now) and copy it to the adb/fastboot folder.
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
If you are already Rooted:
If you are using SuperSU - go to the application options and completely unroot and reboot if needed
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
If not rooted start here:
I am assuming most of you are Windows users. Open your file explorer and open the ADB folder.
On the left hand folder where ADB is located press shift and right click the ADB folder and select "Open command window from here". This will open a command prompt window for you to run all your adb/fastboot commands from. This is the same folder where you copied your recoveries and updates to.
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
Copy your custom recovery and stock recovery to your adb folder
Copy and rename the OTA to the adb folder
Copy your root.zip patch to the /sdcard downloads folder (if you wish root)
>adb reboot bootloader
>fastboot flash recovery stockrecovery.img
>fastboot reboot-bootloader
Go into recovery and wait till dead droid appears
Press power and Volume Up at same time to go into the stock recovery menu
Using the volume buttons move and down the blue list of options and select: Apply update from ADB
You will now have orange text at the bottom of the screen - follow the instructions to side load by typing >adb sideload otaupdate.zip in your command prompt window
Wait and watch the progress, at this point you should see the ota processing steps of which there a few and will vary depending on the package. When its complete there will be a "install complete" or similar message
Reboot and let the update complete the system optimizations and go in validate your device is working and the version is what you wanted
>adb reboot bootloader
>fastboot flash twrp.zip
>fastboot reboot-recovery
Using your newly installed custom recovery you can now apply zips/root etc
Reboot as needed and update root if using older .zip to current binaries and enjoy your updated device.
And yes you only need to backup once prior to starting but many people skip that step -DON'T BE ONE OF THOSE PEOPLE.
Hopefully I've not missed a bit.
You can also use these same instructions if you're stuck in boot loop or applied a patch without first replacing stock or unrooting - just boot to bootloader using fastboot and replace recovery and apply the patches. This will usually work just fine and prevent much heart ache on your part.
How to root Lenovo TAB A7-40 A3500-FL?
[Solved] See the guide below!
Device info:
Model number: Lenovo A3500-FL
Android version: 4.4.2
Kernel version: 3.4.67
Build number: A3500FL_A442_01_25_140823_SE
BB Chip: MT6582
MS Board. A3500FL
Bar code: this was my device's serial number
SW Ver.: ALPS.KK1.MP1.V2.10
Custom Build Verno.: 1408775889
Managed to get cwm and root with this guide: http://forum.xda-developers.com/and...vo-a3500-h-t2879208/post55491817#post55491817
Modified the guide for Lenovo A3500-FL!
EDIT: Also some users have reported that this guide doesn't do the trick or is out-dated, so copypasted the guide from this post here.
Guide
1. Download attachment cwmRecovery.zip and download latest Flash_tool (version 5.1352.0) can be downloaded from here)
1.1. Enable USB-debugging. (How to do this)
2. Manually install the drivers from the attachment a7_40_drivers.zip for the LenovoTablet before plugin it to computer (win7 dirvers work for win8 too).
2.1. To install unsigned/uncertified drivers on Windows 7: http://en.kioskea.net/faq/3914-windows-7-how-to-install-unsigned-drivers
2.2. To install unsigned/uncertified drivers on Windows 8: http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
2.3. After you have disabled the driver signature verification, you can install the drivers like this: Right click My computer, Manage, Device Manager, right click your computer at the top, Add Legacy hardware, next, Install plapla manually, next, Show all Devices, Have a Disk.., Browse to the driver folder where you unzip them, choose example windows7 and the 64 version (win7 drivers work for win8.x too), install every device. Then follow the guide.
(Note: Otherwise Windows only installs the normal automatic drivers and its more difficult to install the other drivers.)
2.4. Plug your device to PC.
3. Download the latest supersu zip file (version 2.46) from attachments or from https://download.chainfire.eu/696/SuperSU/
3.1. Move the zip.-file to the Sdcard.
4. Turn off your device.
5. Unpack cwmRecovery.zip
6. Run Flash_tool.exe with Admin Rights.
7. Chose Scatter-Loading and choose MT6582_Android_scatter.txt (in Recovery folder).
7.1. Now you will see checekd only one checkbox - recovery, if not click on it and choose recovery.img
7.2. Press Download.
7.3. Connect your device.
7.4. Wait few seconds.
8. Have CWM on your device .
9. Unplug your device.
10. . Boot to cmw recovery by turning off your device. Then press and hold VOL DOWN + VOL UP and then also press and hold POWER for about 7 seconds.
10.1. Choose " Install zip from sdcard." (To confrim always use the Power Button)
10.2. Choose "zip from sdcard".
10.3. Select SuperSU-v2.46.zip from sdcard and apply.
10.4. Have a rooted tablet.
It might be necessary to always flash the CWM with the Flashtool directly before you startup the device. Otherwise it will start the original AndroidRecovery again.
It might also be necessary to use different drivers from here.
If the supersu zip doesn't install, try toggling the signature verification to disabled from cwm->install zip from sdcard->toggle signature verification.
Tested and working on Levono A7-40 3500-FL with kitkat update, build number A3500FL_A442_01_25_140823_SE, from ota. Attached screenshot for proof. Also other people have reported that this works for later updates too, for example A3500FL_A442_01_27_141127_SE.
You can update to the latest OTA firmware by first going back to stock recovery. See the second post for the guide.
Thanks and credits go to: @Koli96 and @bobais
How to go back to stock rom/recovery and update to latest Lenovo OTA firmware update
So, it's pretty simple, you take the stock_recovery.zip from the first post, extract it, and replace recovery.img in the recovery folder with the stock one.
Then :
Quote:
4. Turn off your device.
6. Run Flash_tool.exe with Admin Rights
7. Chose Scatter-Loading and choose MT6582_Android_scatter.txt (in Recovery folder)
7.1. Now you will see checekd only one checkbox - recovery, if not click on it and choose recovery.img
7.2.. Press Download
7.3. Connect your device
7.4. Wait few seconds.
And that's it !
On a side note, if it seems stuck on a black screen with a loading circle after factory reset, you have to put the tablet in landscape mode and restart (the shutdown menu appears without any problem) - this issue doesn't seem related to recovery, but a bug within lenovo firmware and the first configuration screen.
Side note 2: The first boot after flashing new update might take 15mins.
Side note 3: After updating to the latest OTA you can go back to cwm recovery with the guide from the first post.
Credits @tenuis
I got the same tablet and I also am looking for a root. :/
Another waiting for rooting lenovo owner.
Same here, i was looking for a root guide and i couldn't find anything.
Does anyone else has a problem with long charging times?
Well it charges long and the charge stays long, so no issue here.
Seems that not that many lenovos root easily, but of course this is a pretty new device(?).
leripe said:
Well it charges long and the charge stays long, so no issue here.
Seems that not that many lenovos root easily, but of course this is a pretty new device(?).
Click to expand...
Click to collapse
OK let's try this
Install mtk drivers
Install USB and adb drivers
Install v root 1.7.8
Now tick adb debugging and connect your device to PC run v root and click root button after device get connected to v root
Let me know if you have any issues
All the best ?
Sent from my x604 using Tapatalk
The-Immortal said:
OK let's try this
Install mtk drivers
Install USB and adb drivers
Install v root 1.7.8
Now tick adb debugging and connect your device to PC run v root and click root button after device get connected to v root
Let me know if you have any issues
All the best ?
Sent from my x604 using Tapatalk
Click to expand...
Click to collapse
Can you link all the drivers?
Edit: Vroot link here: http://vrootdownload.info/vroot1.7.8/
leripe said:
Can you link all the drivers?
Edit: Vroot link here: http://vrootdownload.info/vroot1.7.8/
Click to expand...
Click to collapse
If you have win7 or win8/8.1 USB drivers will automatically installed when you connect device
Adb driver I hope this will work
http://adbdriver.com/downloads/
If it fails make a google search am sure you will find it
Sent from my x604 using Tapatalk
The-Immortal said:
If you have win7 or win8/8.1 USB drivers will automatically installed when you connect device
Adb driver I hope this will work
http://adbdriver.com/downloads/
If it fails make a google search am sure you will find it
Sent from my x604 using Tapatalk
Click to expand...
Click to collapse
Installed everything and tried vroot once again (I have tried it before).
Still not rooted. And btw that vroot at least tries to install bunch of bloatware crap on the pc.
Edit:
I would suggest for anyone who installed Vroot to your pc to scan the whole pc after you uninstall the vroot.
Here are the scanning tools:
Malwarebytes
adwcleaner
superantispyware
hitmanpro
leripe said:
Installed everything and tried vroot once again (I have tried it before).
Still not rooted. And btw that vroot at least tries to install bunch of bloatware crap on the pc.
Edit:
I would suggest for anyone who installed Vroot to your pc to scan the whole pc after you uninstall the vroot.
Here are the scanning tools:
Malwarebytes
adwcleaner
superantispyware
hitmanpro
Click to expand...
Click to collapse
I got a successful root by flashing Recovery.rar from lenovo-forums.ru, (it's easy to google, I'm not allowed to post links) with the included SPFlash Tool and afterwards flashing the needed SU binaryies and apk. However, this will mess up the OTA updates, and I can't find the stock recovery again.
Therefore, I really beg anyone having the stock recovery to post it, enabling us to switch between them, whenever we want to apply any OTAs.
Thanks a lot!
nkr said:
I got a successful root by flashing Recovery.rar from lenovo-forums.ru, (it's easy to google, I'm not allowed to post links) with the included SPFlash Tool and afterwards flashing the needed SU binaryies and apk. However, this will mess up the OTA updates, and I can't find the stock recovery again.
Therefore, I really beg anyone having the stock recovery to post it, enabling us to switch between them, whenever we want to apply any OTAs.
Thanks a lot!
Click to expand...
Click to collapse
Well I very highly doubt that there will be any more updates for a device with this price range. And since the next android version is the L version, which requires more work than before.
Edit2: http://forum.xda-developers.com/android/development/guide-lenovo-a3500-h-t2879208 found this. Tested and it works. Will edit it to the first post.
The same as me
i cant flash update.zip from cwm recovery and need to restore the stock recovery ...
I think flashing the stock rom can solve the problem..
.by using the sp flash tool we can select to flash recovery only ....unticking the others except recovery.img ....you just try to download the stock rom and flash the recovery
Same problem
Heya guys!
I have the same problem here.. I can't run the .zip file from the SD card, it get interrupted every time. Any ideas?
drabuaiad said:
The same as me
i cant flash update.zip from cwm recovery and need to restore the stock recovery ...
I think flashing the stock rom can solve the problem..
.by using the sp flash tool we can select to flash recovery only ....unticking the others except recovery.img ....you just try to download the stock rom and flash the recovery
Click to expand...
Click to collapse
I dont know what you two are trying to do but this thread is about rooting the lenovo A3500-FL not about lenovo stock rom.
Rooting..
Yes indeed, that's what I'm trying to do. Rooting the A3500-FL. According to the instructions you need to install the SuperSU from a zip on your SD card. When I try do that it gets interrupted every time. Installing recovery went well. So I'm not getting what I do wrong? Any ideas?
leripe said:
I dont know what you two are trying to do but this thread is about rooting the lenovo A3500-FL not about lenovo stock rom.
Click to expand...
Click to collapse
Mrosenho said:
Yes indeed, that's what I'm trying to do. Rooting the A3500-FL. According to the instructions you need to install the SuperSU from a zip on your SD card. When I try do that it gets interrupted every time. Installing recovery went well. So I'm not getting what I do wrong? Any ideas?
Click to expand...
Click to collapse
http://download.chainfire.eu/452/SuperSU/UPDATE-SuperSU-v2.02.zip and y ou mean this when you talk about update.zip?
And I hope you are using the install zip from sdcard option and the choose zip from sdcard option?
Boot to cmw.
Install zip from sdcard.
Choose zip from sdcard.
browse to your supersu zip and apply.
Now I also update the first post's guide, so you can check that out too.
Thanks for the help so far. But now I'm starting to doubt that the CWM install went successfully. Let me show you a picture of my screen after a failed install of the UPDATE-SuperSU-v2.02.zip -file. (ht_tps://ww_w.dropb_ox.com/s/1wrnatzjk2gn42h/2014-10-09%2008.50.40.png?dl=0) (slightly modified link because of forum rules, just take out the _) I'm using the "apply update from sdcard" option, then I browse to the SuperSU.zip -file and apply it. Then it starts installation, but aborts it in a few seconds. So am I booting to just a normal recovery mode and not CWM? (Sorry if all this seems totally ignorant, I have only flashed roms before, never rooted a new device)
leripe said:
UPDATE-SuperSU-v2.02.zip and you mean this when you talk about update.zip?
And I hope you are using the install zip from sdcard option and the choose zip from sdcard option?
Boot to cmw.
Install zip from sdcard.
Choose zip from sdcard.
browse to your supersu zip and apply.
Now I also update the first post's guide, so you can check that out too.
Click to expand...
Click to collapse
Yup.. This is the problem. The recovery runs fine from Flash Tool and claims it installs it. (Download ok) But I still don't seem to have CWM on the device. It's just normal recovery mode. So any ideas about the CWM-installation? What could possibly go wrong? I get no error messages. Cheers.
//Mike
Mrosenho said:
Thanks for the help so far. But now I'm starting to doubt that the CWM install went successfully. Let me show you a picture of my screen after a failed install of the UPDATE-SuperSU-v2.02.zip -file. (ht_tps://ww_w.dropb_ox.com/s/1wrnatzjk2gn42h/2014-10-09%2008.50.40.png?dl=0) (slightly modified link because of forum rules, just take out the _) I'm using the "apply update from sdcard" option, then I browse to the SuperSU.zip -file and apply it. Then it starts installation, but aborts it in a few seconds. So am I booting to just a normal recovery mode and not CWM? (Sorry if all this seems totally ignorant, I have only flashed roms before, never rooted a new device)
Click to expand...
Click to collapse
thanks ...
It is work fine for me on a3500 fl with 4.4.2 ver a442_01_26_140911_se
Mrosenho said:
Yup.. This is the problem. The recovery runs fine from Flash Tool and claims it installs it. (Download ok) But I still don't seem to have CWM on the device. It's just normal recovery mode. So any ideas about the CWM-installation? What could possibly go wrong? I get no error messages. Cheers.
//Mike
Click to expand...
Click to collapse
Same for me, what about this @leripe ?
EDIT// Oh, It's working now, tried to flash it one more time, then I held a power button until Lenovo logo appeared and then I pressed Vol UP and Vol DOWN and the CWM came in, thank you! Now my tablet is finally rooted
If so, how? Thanks!
magicmanfk said:
If so, how? Thanks!
Click to expand...
Click to collapse
This was totally bugging me too but after a whole day of trying I've finally managed it.
1) Go to this thread here
2) Boot into fastboot and flash the boot.img and system.img as suggested in the thread
3) Also flash the original recovery using "fastboot flash recovery recovery.img"
4) Go to the official asus support site here and download the update files you need, the last two
5) Download Version V11.41.87.2 and place the file in the internal storage of your sd card, once you pull the cable out your phone the phone should detect a update file and ask if you want to install it. Click OK.
6) The phone will unpack the update and reboot and install it
7) Delete this update file and then add the latest Nougat update file (Version V20.31.49.2)
8) Do the same again and install it and there you have it... the key is that you have to install each incremental update rather than go straight to the latest.
Oh and I don't know if it makes any difference, but I decided to turn off adb debugging once I'd flashed the various boot, system and recovery images before I started to update using the Asus method.
Also I have successfully re-flashed TWRP through fastboot on Nougat.
Hope this helps.
worked for me perfectly
pjcarrmole said:
This was totally bugging me too but after a whole day of trying I've finally managed it.
1) Go to this thread here
2) Boot into fastboot and flash the boot.img and system.img as suggested in the thread
3) Also flash the original recovery using "fastboot flash recovery recovery.img"
4) Go to the official asus support site here and download the update files you need, the last two
5) Download Version V11.41.87.2 and place the file in the internal storage of your sd card, once you pull the cable out your phone the phone should detect a update file and ask if you want to install it. Click OK.
6) The phone will unpack the update and reboot and install it
7) Delete this update file and then add the latest Nougat update file (Version V20.31.49.2)
8) Do the same again and install it and there you have it... the key is that you have to install each incremental update rather than go straight to the latest.
Oh and I don't know if it makes any difference, but I decided to turn off adb debugging once I'd flashed the various boot, system and recovery images before I started to update using the Asus method.
Also I have successfully re-flashed TWRP through fastboot on Nougat.
Hope this helps.
Click to expand...
Click to collapse
Thanks for the instructions; worked for me. Were you able to re-root? I tried to by following this guide: https://www.reddit.com/r/zenfone/comments/6gqha5/zenfone_3_ze553kl_z01hd_root/
But on step 8 of the supersu website, my phone gets stuck on "starting adb sideload feature." I had already tried installing supersu via twrp, but still no root.
Devalorize said:
Thanks for the instructions; worked for me. Were you able to re-root? I tried to by following this guide: https://www.reddit.com/r/zenfone/comments/6gqha5/zenfone_3_ze553kl_z01hd_root/
But on step 8 of the supersu website, my phone gets stuck on "starting adb sideload feature." I had already tried installing supersu via twrp, but still no root.
Click to expand...
Click to collapse
I flashed TWRP from one of the other threads on here filename twrp-3.1.0-0-Z01H-20170408.img to be precise.
I then flashed the latest version of magisk the zip found here
Then selecting core files only and magisk hide options I have root that passes the latest safetynet checks. No problem.
pjcarrmole said:
I flashed TWRP from one of the other threads on here filename twrp-3.1.0-0-Z01H-20170408.img to be precise.
I then flashed the latest version of magisk the zip found here
Then selecting core files only and magisk hide options I have root that passes the latest safetynet checks. No problem.
Click to expand...
Click to collapse
This worked for me, thanks. It's too bad Xposed doesn't support Nougat yet. Missing my Xposed modules.
Devalorize said:
This worked for me, thanks. It's too bad Xposed doesn't support Nougat yet. Missing my Xposed modules.
Click to expand...
Click to collapse
Magisk has a few modules for it but nothing like Xposed.
I'm going to do a full back up and then see how well ZenUI plays with Substratum as most of the ZenUI Themes are pretty poor and I want an all black theme. I'll let people know how it goes if anyone is interested in using substratum.
---------- Post added at 10:28 AM ---------- Previous post was at 09:32 AM ----------
pjcarrmole said:
I flashed TWRP from one of the other threads on here filename twrp-3.1.0-0-Z01H-20170408.img to be precise.
I then flashed the latest version of magisk the zip found here
Then selecting core files only and magisk hide options I have root that passes the latest safetynet checks. No problem.
Click to expand...
Click to collapse
Oh, if you're having trouble getting TWRP to stick don't reboot the system but reboot back into Recovery, by holding the Vol - & Power together and using the Volume buttons to select Recovery.
After this you can then reboot normally.
Disclaimer: If you go through with this and encounter issues, I (or the others here) will try to help you, but the risk is all yours.
I see a few posts mentioning TWRP for the AFTV3, so here it is for the pendant (needle): link. Extract twrp.img from the archive, copy it to /sdcard, and flash as follows:
Code:
adb shell
su
dd if=/sdcard/twrp.img of=/dev/block/recovery
Note: You will need a Y (OTG) cable to connect a mouse and/or a keyboard.
I have tested this on the pendant (needle), but it should also work for the cube (stark).
You can also boot or flash this from fastboot (reboot bootloader or run from aml_reboot in the root thread) if you so desire.
To enter recovery from a terminal running on the AFTV3:
Code:
reboot recovery
To enter recovery from ADB:
Code:
adb reboot recovery
For those interested, here's what I did:
-- Rather than build from scratch, I used an existing TWRP for Amlogic's S905X as the base. Quite a few of them are here.
-- You can't just use a random TWRP and expect it to work on the AFTV3 (due to hardware and partition mismatch). I first replaced (and repacked) the ramdisk with that from needle's boot image (using magiskboot).
-- While TWRP booted up, USB OTG was absent. Without OTG, TWRP is not of much use (w/o OTG, I used openrecoveryscript as a workaround). Turns out the random TWRP images lack the correct USB modules. I extracted the correct modules from the AFTV3, copied them to the TWRP image, and everything works.
If something doesn't work, please post here.
Great job, i flashed it from fastboot.
adb reboot bootloader (or install a app that will reboot into bootloader)
fastboot flash recovery C:\(this TWRP version)
Seems to be functional.
the old Firestick 1's you could control the mouse from a adb shell. I dont know how to make that functional for those without a OTG.
Confirmed, it works on the cube (stark) as well...
That's really a great job. As stated here: https://forum.xda-developers.com/showpost.php?p=78958467&postcount=165 I (hopefully soft) bricked my pendant trying to install Google services. Now it just reboot at the white amazon logo. Ordered a OTG cable to test TWRP but was trying random versions. Now this confirmed woirking version is a life saver to me. Now I just have to find a way to remove the offending google service apk.
Thanks again.
Sorry to bother again.
I still have my pendant in bootloop (bad google service installation).
Tried OTG cable but using it doesnt let me go in fastboot mode and I dont know how to navigate in recovery without it.
Since now the pendant is rooted and can recover OTA files maybe my next attempt could be to try to find a .bin rom file and flash it using fastboot?
If so does anyone know if there is such a file yet (pre rooted version should be great)?
Thanks.
Does anyone know where to get the updated firetv3 roms? with TWRP now i would like to attempt updates.
Michajin said:
Does anyone know where to get the updated firetv3 roms? with TWRP now i would like to attempt updates.
Click to expand...
Click to collapse
None available yet, but there are a couple of methods by which we may obtain them.
The first one has some risk involved. you would have to re-enable OTA updates and allow the device the check for and download the current version
and then again disable the OTA update apps. Then pull a copy of the update from the device before clearing the cache.
I have noticed that as long as the device is busy, say running a sideloaded app, it will not initiate a downloaded update.
The second is dependent upon if the individual will help us. There is a member on this forum who has modified the DeviceSoftwareOTA.apk for OS 5
that allowed update check and download to stay enabled because the installation procedure was removed from the APK. So you could simply pull the
update from the cache at any time. I will pull a copy from OS 6 and post it today and see if he would be willing to assist.
I'm with you, I'd like to update mine as well after seeing some of the changes that have been posted.
2WhlWzrd said:
None available yet, but there are a couple of methods by which we may obtain them.
The first one has some risk involved. you would have to re-enable OTA updates and allow the device the check for and download the current version
and then again disable the OTA update apps. Then pull a copy of the update from the device before clearing the cache.
I have noticed that as long as the device is busy, say running a sideloaded app, it will not initiate a downloaded update.
The second is dependent upon if the individual will help us. There is a member on this forum who has modified the DeviceSoftwareOTA.apk for OS 5
that allowed update check and download to stay enabled because the installation procedure was removed from the APK. So you could simply pull the
update from the cache at any time. I will pull a copy from OS 6 and post it today and see if he would be willing to assist.
I'm with you, I'd like to update mine as well after seeing some of the changes that have been posted.
Click to expand...
Click to collapse
Would the update fail anyway if I replaced Amazon recovery with TWRP?
Michajin said:
Would the update fail anyway if I replaced Amazon recovery with TWRP?
Click to expand...
Click to collapse
No, TWRP would be over written by an OTA update.
2WhlWzrd said:
No, TWRP would be over written by an OTA update.
Click to expand...
Click to collapse
you sure about that? i just screwed up and was rooting my "tanks" and forgot to update one. Then i took the update, it ran the amazon update though open recovery TWRP and updated. Booted without issues, i know its a firestick2, but almost thinking i should test on a pendant...
Michajin said:
you sure about that? i just screwed up and was rooting my "tanks" and forgot to update one. Then i took the update, it ran the amazon update though open recovery TWRP and updated. Booted without issues, i know its a firestick2, but almost thinking i should test on a pendant...
Click to expand...
Click to collapse
There is a difference between writing outside of TWRP and with TWRP, it's hard to overwrite something that's doing the writing.
If you read in the first post of the tank rooting thread, the author explicitly states: "Only ever flash boot/recovery images using TWRP",
anything outside of that will not be root aware. Better to be safe, than sorry.
How may I get the "su". It said, I don't have permision.
eSephiroth said:
How may I get the "su". It said, I don't have permision.
Click to expand...
Click to collapse
Open Magisk Manager, Select the Menu in the top left corner.
In the sidebar navigate to "Superuser", you should see "com.android.shell".
Toggle the switch to right to enable it.
2WhlWzrd said:
Open Magisk Manager, Select the Menu in the top left corner.
In the sidebar navigate to "Superuser", you should see "com.android.shell".
Toggle the switch to right to enable it.
Click to expand...
Click to collapse
If you didn't root the device, how can you have superuser?
eSephiroth said:
If you didn't root the device, how can you have superuser?
Click to expand...
Click to collapse
I assumed you were already rooted. Since you are not, start here:
[ROOT] Rooting the FireTV Cube and Pendant with FireFU
Anything from firmware 6.2.5.8 and up, the exploit has been patched.
This is the most complicated root method I have ever seen. Mine is 6.2.8. too bad.
eSephiroth said:
This is the most complicated root method I have ever seen. Mine is 6.2.8. too bad.
Click to expand...
Click to collapse
This isn't the root thread. But yeah, it's the only thing we've got for these devices, so we make it work
Hi,
I was able to recover my Pendant using a finally working OTG cable and using mouse with your TWRP and finally delete the offending google.gsm app so thanks a lot for that.
The only thing I noticed is that adb doesn't work for me once booted into TWRP (I wanted to use adb backup to backup bigger partitions directly to my PC). Is that just my issue or it's happening for everyone?
Thanks.
Pino.
moving it to the right place.
anyone have interest in the update files? If i turn on my update, download the update, but before rebooting copy the .bin file to a different folder, delete from the cache folder then disable updates again. I can share the file if anyone wants it to see if we can modify to keep root and update? I am thinking i might download it, move it and change it to a .zip, then reboot into TWRP. Flash the update and flash magisk before a reboot. Anyone have thoughts about risk of a BRICK?
Hi guys,
I have been reading similar threads and trying to find a solution but could not find what could help and ran into other issues. Hope someone can help me fix this.
I was trying to flash a custom ROM. had the device unlocked and installed twrp using adb.
It was a mistake to not back up. I tried to flash the firmware + extendedUI rom + magisk. Only magisk gave some error.
tried to reboot and got stuck in bootloop. Entered Twrp tried to do it again so wiped data,system,cache and then realised my folder with the rom disapeared. So now no OS and not sure what to do.
I was trying to use adb sideload to push the new zips on the device but the sideload just disconnects at 8% Understood that might drivers might be at fault. . Been trying to find and update drivers and might have done some mistakes there, as chose to update unknown device automatically with device manager and now it disappeared as well.
I read about recovering with Miflashtool but got confused whether thats the right way.
I would prefer to install a custom rom like the ExtendedUI or AOSPextended.
FuzzEdgar said:
Hi guys,
I have been reading similar threads and trying to find a solution but could not find what could help and ran into other issues. Hope someone can help me fix this.
I was trying to flash a custom ROM. had the device unlocked and installed twrp using adb.
It was a mistake to not back up. I tried to flash the firmware + extendedUI rom + magisk. Only magisk gave some error.
tried to reboot and got stuck in bootloop. Entered Twrp tried to do it again so wiped data,system,cache and then realised my folder with the rom disapeared. So now no OS and not sure what to do.
I was trying to use adb sideload to push the new zips on the device but the sideload just disconnects at 8% Understood that might drivers might be at fault. . Been trying to find and update drivers and might have done some mistakes there, as chose to update unknown device automatically with device manager and now it disappeared as well.
I read about recovering with Miflashtool but got confused whether thats the right way.
I would prefer to install a custom rom like the ExtendedUI or AOSPextended.
Click to expand...
Click to collapse
The zip files are to big to push them through adb sideload.
Just connect the cellphone to the pc while in twrp and mount otg