Related
Okay, well the title should be pretty self explanatory I hope, but here's what I'm looking for:
A way to install TWRP and FireFireFire 1.4 on a Kindle Fire using a Mac (OS X 10.7.4 Lion if anyone wants to know).
I know that you should install TWRP only through fastboot then use TWRP to flash FFF and your custom ROM.
I also know there's something about modifying Android SDK drivers to make ADB and fastboot work properly with the Kindle Fire.
I am not looking for any sort of one-click solution. I once jailbroke my iPhone using a simple one-click, it didn't turn out well. Fortunately iPhones are almost always fixed by an iTunes restore. Did it using redsn0w after that, it was better. I manually installed homebrew on my Wii as well, which is more complex than redsn0w and more of an actual manual install. Wii homebrew works beautifully.
Anyways, I'm against one-clicks/simple rooters/jailbreakers because it seems like if even one thing is out of place, they mess things up.
I want to manually do this, and I know there's a way to. I just need to install Android SDK, I can do that. Modify the drivers, this is the thing I need the most assistance with, because I don't know how to do it and I know tools like KFU do it automatically. And of course, I want to manually use pokey9000's fbmode to get into fastboot, then flash TWRP, then get into TWRP, flash FFF and my custom ROM.
Anyone who could help me with this, I'd greatly appreciate it!
Well I see you don't want the easy solution but maybe part of this will help you with the drivers easily http://forum.xda-developers.com/showthread.php?t=1790139 then its just a matter of fastboot flashing twrp.img and fff.bin to your kindle. From that point you enter recovery make a backup. I suggest reboot after this. transfer a ROM zip and gapps zip of your choice to the root of your sdcard. Boot back to recovery- factory reset, -wipe cache, -wipe dalvik,-wipe system,-flash ROM,-flash gapps- select reboot then select system if prompted enjoy
---------- Post added at 03:49 AM ---------- Previous post was at 03:32 AM ----------
Take some time read these to threads since the hard way makes you happy familiarize yourself with what needs to be done and how to do it so you are always in the safe zone http://forum.xda-developers.com/showthread.php?t=1552547 and this http://forum.xda-developers.com/showthread.php?t=1638452 kinfauns took a lot of time to compile these threads to build awareness I believe he as well is on Mac just a guess. Some of this is a little gauged to windows but the concept is relatively the same so I have been told. I'm on windows myself and I understand that on Mac and Linux drivers aren't a problem as they are on windows. Good luck don't be afraid to ask more questions before you leap others out there have more experience with Mac than I
Edit: And note that I said fff.bin is the file you fastboot flash not a zip a zip file will break your bootloader severely unless you flash in recovery then a zip is the desired file type. Research is good prevents mishaps
Thepooch said:
Well I see you don't want the easy solution but maybe part of this will help you with the drivers easily http://forum.xda-developers.com/showthread.php?t=1790139 then its just a matter of fastboot flashing twrp.img and fff.bin to your kindle. From that point you enter recovery make a backup. I suggest reboot after this. transfer a ROM zip and gapps zip of your choice to the root of your sdcard. Boot back to recovery- factory reset, -wipe cache, -wipe dalvik,-wipe system,-flash ROM,-flash gapps- select reboot then select system if prompted enjoy
---------- Post added at 03:49 AM ---------- Previous post was at 03:32 AM ----------
Take some time read these to threads since the hard way makes you happy familiarize yourself with what needs to be done and how to do it so you are always in the safe zone http://forum.xda-developers.com/showthread.php?t=1552547 and this http://forum.xda-developers.com/showthread.php?t=1638452 kinfauns took a lot of time to compile these threads to build awareness I believe he as well is on Mac just a guess. Some of this is a little gauged to windows but the concept is relatively the same so I have been told. I'm on windows myself and I understand that on Mac and Linux drivers aren't a problem as they are on windows. Good luck don't be afraid to ask more questions before you leap others out there have more experience with Mac than I
Edit: And note that I said fff.bin is the file you fastboot flash not a zip a zip file will break your bootloader severely unless you flash in recovery then a zip is the desired file type. Research is good prevents mishaps
Click to expand...
Click to collapse
BreakDroid is one of those "one click" solutions I'm really trying to keep away from. I know that installing a custom bootloader + recovery is just a matter of having your computer properly recognize the Kindle Fire as an ADB interface, which I need to modify drivers for. I need to know how to modify drivers.
After that, it's just that I need to get into fastboot and I've got it from there.
Well, since you want a complex approach, may as well go with Firekit: http://forum.xda-developers.com/showthread.php?t=1430038&highlight=firekit (install_fff_twrp_from_stock)
I simply just said to use breakdroid for the driver install I didn't suggest you use it for anything else but with drivers I'm sure there are plenty of driver setup tutorials for Mac and the kindle fire so Google is your friend. Read the very first sentence of my first post seems you overlooked that
Breakdroid works great though is simple and installs exactly what you need. From there you have twrp and can flash away.
Sent from my MB860 using xda app-developers app
Thepooch said:
I simply just said to use breakdroid for the driver install I didn't suggest you use it for anything else but with drivers I'm sure there are plenty of driver setup tutorials for Mac and the kindle fire so Google is your friend. Read the very first sentence of my first post seems you overlooked that
Click to expand...
Click to collapse
Actually from what I've seen on various tutorials, ones about rooting, they always have instructions for Windows to install drivers but most of them instruct Mac / Linux to skip that step, then Mac / Linux picks back up where you're already issuing ADB and fastboot commands. I feel totally stupid if I've overlooked this, but if it's actually possible to skip this step that'd be so much easier.
Also I did read your first post. But when looking at BreakDroid I saw nothing specific about installing drivers, just that it was supposed to be a simple tool where you go through each step.
blue71 said:
Breakdroid works great though is simple and installs exactly what you need. From there you have twrp and can flash away.
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
All simple tools are meant to work great. Unfortunately, they just don't sometimes.
Is there anyone who has actually rooted a Kindle Fire on Mac or Linux here that can verify you don't need to do anything with drivers? And that just installing the Android SDK is sufficient to proceed?
superriku11 said:
All simple tools are meant to work great. Unfortunately, they just don't sometimes.
Click to expand...
Click to collapse
Very true. The unfortunate part is when users of these tools have no idea how to get themselves out of trouble, but I digress...
superriku11 said:
Is there anyone who has actually rooted a Kindle Fire on Mac or Linux here that can verify you don't need to do anything with drivers? And that just installing the Android SDK is sufficient to proceed?
Click to expand...
Click to collapse
Here's a guide for setting up a Linux environment...
http://forum.xda-developers.com/showthread.php?t=1475740
All you really need for Linux are the binaries (adb/fastboot) and /root/.android/adb_usb.ini with 0x1949 in it. Once you have those, you just need to run the binaries as root. The other things in that guide sets things up so a user without root privileges can access the USB ports and set paths to those binaries. There are no "drivers" in the Windows sense to be installed and you don't need to install the SDK if you can find those binaries elsewhere.
I'm confident the setup will be similar to Mac OS X, but udev is linux specific. I don't know what the Mac OS X equivalents are because I've always used virtual machines with Linux or Windows to interact with the KF. Regardless, you should still be able to use them as root and issue commands to the KF.
Thepooch gave you links to my guides... whichever OS you decide to use, all of the fastboot and adb commands will be the same. You just need to swap out the directory path conventions from Windows to Linux/Mac OS X.
kinfauns said:
Very true. The unfortunate part is when users of these tools have no idea how to get themselves out of trouble, but I digress...
Here's a guide for setting up a Linux environment...
http://forum.xda-developers.com/showthread.php?t=1475740
All you really need for Linux are the binaries (adb/fastboot) and /root/.android/adb_usb.ini with 0x1949 in it. Once you have those, you just need to run the binaries as root. The other things in that guide sets things up so a user without root privileges can access the USB ports and set paths to those binaries. There are no "drivers" in the Windows sense to be installed and you don't need to install the SDK if you can find those binaries elsewhere.
I'm confident the setup will be similar to Mac OS X, but udev is linux specific. I don't know what the Mac OS X equivalents are because I've always used virtual machines with Linux or Windows to interact with the KF. Regardless, you should still be able to use them as root and issue commands to the KF.
Thepooch gave you links to my guides... whichever OS you decide to use, all of the fastboot and adb commands will be the same. You just need to swap out the directory path conventions from Windows to Linux/Mac OS X.
Click to expand...
Click to collapse
Thanks for your help! Thanks for everyone's help actually! You all contributed somehow, and thanks to you I successfully installed FFF 1.4a, TWRP 2.2.0, and Jandycane 7-29 on my Kindle Fire! Awesome so far, thanks guys!
:highfive::good:
So I've tried searching on here, I've tried googling to no success...So time for my first post on this site I guess.
I have an Acer Iconia Tab A100 running stock ICS (rooted) which now stops during its boot sequence.
I've read that when a device is bricked it stops at the Acer logo on boot, mine goes past this but stops before the Android logo appears.
Stuff I did before this happened:
- Friend rooted my device for me using a guide from these forums.
- I tried seeing what I can do with Superuser permissions and got used to the new features.
- Wanted an app that wasn't compatible with my device so I tried using a Device Spoofer to make my device appear as an HTC Thunderbolt.
- Realized it didn't work still so I used the device spoofer to restore back to my default device.
- Device rebooted and I am now stuck between the Acer logo and the Android logo on boot.
Am I bricked and screwed out of a device?
Is there a way to recover my device/restore to factory?
Any help is appreciated. You all most likely know more that I do.
EDIT: The guide that was followed to root: http://forum.xda-developers.com/showthread.php?t=1531646&highlight=root
phracture said:
So I've tried searching on here, I've tried googling to no success...So time for my first post on this site I guess.
I have an Acer Iconia Tab A100 running stock ICS (rooted) which now stops during its boot sequence.
I've read that when a device is bricked it stops at the Acer logo on boot, mine goes past this but stops before the Android logo appears.
Stuff I did before this happened:
- Friend rooted my device for me using a guide from these forums.
- I tried seeing what I can do with Superuser permissions and got used to the new features.
- Wanted an app that wasn't compatible with my device so I tried using a Device Spoofer to make my device appear as an HTC Thunderbolt.
- Realized it didn't work still so I used the device spoofer to restore back to my default device.
- Device rebooted and I am now stuck between the Acer logo and the Android logo on boot.
Am I bricked and screwed out of a device?
Is there a way to recover my device/restore to factory?
Any help is appreciated. You all most likely know more that I do.
Click to expand...
Click to collapse
Is cwm or twrp recovery installed?
Sent via G2x on temasek b135.2 w/ Trinity TD1.58 kernel (testing)
justjackyl said:
Is cwm or twrp recovery installed?
Sent via G2x on temasek b135.2 w/ Trinity TD1.58 kernel (testing)
Click to expand...
Click to collapse
I don't believe either was installed. Is there anyway to fix this problem without those?
phracture said:
I don't believe either was installed. Is there anyway to fix this problem without those?
Click to expand...
Click to collapse
Well for starters what happened was that tool wrecked build.prop which sits in /system. Not a bug issue except it won't be fixed by resetting, you need to replace/repair build.prop or flash a whole new system to it. Did you enable debugging before doing this? If so adb might be used to repair the damage. If not you'll need to flash an official acer ICS ROM by placing it on the root of external SD named update.zip then power on holding the volume key closest to the lock switch.
Tapatalked from my Nexus 7 - Kuroikaze AOSP
pio_masaki said:
Well for starters what happened was that tool wrecked build.prop which sits in /system. Not a bug issue except it won't be fixed by resetting, you need to replace/repair build.prop or flash a whole new system to it. Did you enable debugging before doing this? If so adb might be used to repair the damage. If not you'll need to flash an official acer ICS ROM by placing it on the root of external SD named update.zip then power on holding the volume key closest to the lock switch.
Tapatalked from my Nexus 7 - Kuroikaze AOSP
Click to expand...
Click to collapse
Ahhh okay I think that makes sense to me, and yes I believe I had debugging turned on so I should be able to fix this I guess fairly simply.
Thanks so much will post to say if I've solved or ran into trouble once i get home.
pio_masaki said:
Well for starters what happened was that tool wrecked build.prop which sits in /system. Not a bug issue except it won't be fixed by resetting, you need to replace/repair build.prop or flash a whole new system to it. Did you enable debugging before doing this? If so adb might be used to repair the damage. If not you'll need to flash an official acer ICS ROM by placing it on the root of external SD named update.zip then power on holding the volume key closest to the lock switch.
Tapatalked from my Nexus 7 - Kuroikaze AOSP
Click to expand...
Click to collapse
Could someone be nice enough as to tell me how to access my device to put the build.prop on it?
I have installed adb and downloaded the files for 4.0.3 using android ADK. I see the build.prop file that I need. However when i try to run adb.exe to see how the program works, I just get a window which scrolls through a large amount of text before closing.
EDIT: I am running windows 7 x64. Would this be easier if I tried using adb on my laptop which runs Ubuntu?
phracture said:
Could someone be nice enough as to tell me how to access my device to put the build.prop on it?
I have installed adb and downloaded the files for 4.0.3 using android ADK. I see the build.prop file that I need. However when i try to run adb.exe to see how the program works, I just get a window which scrolls through a large amount of text before closing.
EDIT: I am running windows 7 x64. Would this be easier if I tried using adb on my laptop which runs Ubuntu?
Click to expand...
Click to collapse
First you need to have the acer drivers installed. Second the tab will need to be booted to the recovery to be seen.
Place the build.prop you need to push to the device in the platform tools folder (the one with adb.exe). Make sure the name is properly build.prop
**There are modded ones here in the dev section here that will work, speed up your tab and/or rename it to an A500 to get more apps.
Open a command propt in the platform-tools folder (shift-right click)
type
adb devices
There should be a device listed
type
adb push build.prop /system
Your done, type reboot
It should reboot with the new build.prop
phracture said:
Could someone be nice enough as to tell me how to access my device to put the build.prop on it?
I have installed adb and downloaded the files for 4.0.3 using android ADK. I see the build.prop file that I need. However when i try to run adb.exe to see how the program works, I just get a window which scrolls through a large amount of text before closing.
EDIT: I am running windows 7 x64. Would this be easier if I tried using adb on my laptop which runs Ubuntu?
Click to expand...
Click to collapse
Open a terminal then cd to where you have adb.exe then run it that way, otherwise it just scrolls help and closes like you saw.
Power on and once it gets stuck booting try
adb devices
And see if it shows up, if it does do
adb pull /system/build.prop
This pulls it to where adb.exe is, from there you can check it for errors or even upload it and we can check it out.
Tapatalked from my Galaxy Nexus - CN(A)
Excuse me for butting in but wouldnt it be easer for him to just do the SD card. A lot less confusing at least fo me..
pio_masaki said:
Open a terminal then cd to where you have adb.exe then run it that way, otherwise it just scrolls help and closes like you saw.
Power on and once it gets stuck booting try
adb devices
And see if it shows up, if it does do
adb pull /system/build.prop
This pulls it to where adb.exe is, from there you can check it for errors or even upload it and we can check it out.
Tapatalked from my Galaxy Nexus - CN(A)
Click to expand...
Click to collapse
I'd be fine with uploading it for you guys to check out, but first I need adb to find my device.
I made sure I have the Acer drivers installed, but when I plug it in and run "adb devices" I get no devices listed.
I tried both at the screen where it stops loading as you said and at the recovery screen as Romman0 said.
Romman0 said:
First you need to have the acer drivers installed. Second the tab will need to be booted to the recovery to be seen.
Place the build.prop you need to push to the device in the platform tools folder (the one with adb.exe). Make sure the name is properly build.prop
**There are modded ones here in the dev section here that will work, speed up your tab and/or rename it to an A500 to get more apps.
Open a command propt in the platform-tools folder (shift-right click)
type
adb devices
There should be a device listed
type
adb push build.prop /system
Your done, type reboot
It should reboot with the new build.prop
Click to expand...
Click to collapse
I tried that and no devices are listed as I said above.
Also, the shift+right click blew my mind. That could've been and will be very useful to save me time.
phracture said:
I'd be fine with uploading it for you guys to check out, but first I need adb to find my device.
I made sure I have the Acer drivers installed, but when I plug it in and run "adb devices" I get no devices listed.
I tried both at the screen where it stops loading as you said and at the recovery screen as Romman0 said.
I tried that and no devices are listed as I said above.
Also, the shift+right click blew my mind. That could've been and will be very useful to save me time.
Click to expand...
Click to collapse
So I still haven't gotten my device to be recognized. Should I try to connect using Ubuntu or Mac OS?
As I was told before, there is something i can do where i put the android API in an update.zip and place it on an external SD. By external SD does this mean micro SD card? Could this solve my problem potentially?
phracture said:
So I still haven't gotten my device to be recognized. Should I try to connect using Ubuntu or Mac OS?
As I was told before, there is something i can do where i put the android API in an update.zip and place it on an external SD. By external SD does this mean micro SD card? Could this solve my problem potentially?
Click to expand...
Click to collapse
Yes the microsd. And yes, if you flash the ICS stock ROM http://forum.xda-developers.com/showthread.php?t=1611696
It will fix it to. Rename to update.zip then place it on your microsd card, power off and boot recovery by pressing both the power and volume rocker closest to the corner at the same time until it starts updating.
Romman0 said:
Yes the microsd. And yes, if you flash the ICS stock ROM http://forum.xda-developers.com/showthread.php?t=1611696
It will fix it to. Rename to update.zip then place it on your microsd card, power off and boot recovery by pressing both the power and volume rocker closest to the corner at the same time until it starts updating.
Click to expand...
Click to collapse
Thanks for confirming and giving me that link. Problem is solved. Thanks everyone for helping a noob out.
I have used all drivers and two different tot files, and it works to reboot, then it fails when I try to get past the first welcome screen... Does it make a difference if the sim card is in or out???
It makes it to preactivation and set phone name, then a second or two later goes back into the reboot stage.
I made it to the settings screen and phone info, and all areas were UNKNOWN
pitbull8265 said:
I have used all drivers and two different tot files, and it works to reboot, then it fails when I try to get past the first welcome screen... Does it make a difference if the sim card is in or out???
It makes it to preactivation and set phone name, then a second or two later goes back into the reboot stage.
I made it to the settings screen and phone info, and all areas were UNKNOWN
Click to expand...
Click to collapse
I don't know what went wrong but since you don't have a reply I'll say this... I would start from scratch. Download the tot file AND dll again to a new place on your PC (like desktop). Run LG flash tool again and browse to those 2 files (flash tools likes to remember previous settings). Flash again and let us know the result. Sim card doesn't make a difference.
http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware if you need it, always flashed reliably for me.
...
scottdanpor said:
I don't know what went wrong but since you don't have a reply I'll say this... I would start from scratch. Download the tot file AND dll again to a new place on your PC (like desktop). Run LG flash tool again and browse to those 2 files (flash tools likes to remember previous settings). Flash again and let us know the result. Sim card doesn't make a difference.
http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware if you need it, always flashed reliably for me.
Click to expand...
Click to collapse
Ive done this.. no luck
pitbull8265 said:
Ive done this.. no luck
Click to expand...
Click to collapse
Did you get anywhere with this? Under status, is your IMEI listed as unknown? This seems like your efs partition might be messed up. Did you make a backup of it?
scottdanpor said:
Did you get anywhere with this? Under status, is your IMEI listed as unknown? This seems like your efs partition might be messed up. Did you make a backup of it?
Click to expand...
Click to collapse
I just read elsewhere that if you used ioroot you may have a backup anyways. On the computer in ioroot. You may find a couple files called, modem st1, and modem st2.
Hopefully they will speak of it. Watch this thread..,.
http://forum.xda-developers.com/showthread.php?p=51932057
@scottdanpor for the info and hopefully how to use it.
pitbull8265 said:
Ive done this.. no luck
Click to expand...
Click to collapse
Sent from my Nexus 7 using Tapatalk
secret.animal said:
I just read elsewhere that if you used ioroot you may have a backup anyways. On the computer in ioroot. You may find a couple files called, modem st1, and modem st2.
Hopefully they will speak of it. Watch this thread..,.
http://forum.xda-developers.com/showthread.php?p=51932057
@scottdanpor for the info and hopefully how to use it.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yeah but he has basically access to download mode and fastboot it seems. I haven't found a way to push files without at least recovery
Well, if he has access to stock recovery should be able to push files that way through ADB
NOPE
scottdanpor said:
Yeah but he has basically access to download mode and fastboot it seems. I haven't found a way to push files without at least recovery
Well, if he has access to stock recovery should be able to push files that way through ADB
Click to expand...
Click to collapse
it just hangs and reboots still... cant access fastboot.. tried every file available nothing is working
rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr
scottdanpor said:
Yeah but he has basically access to download mode and fastboot it seems. I haven't found a way to push files without at least recovery
Well, if he has access to stock recovery should be able to push files that way through ADB
Click to expand...
Click to collapse
I have a recovery I made using twrp saved to my pc, and I chose the option to backup my efs, so all of my info is on my pc in the backup file.
HOW can I use adb sideload or ADB to push it to my phone???
HAS TO BE DONE FROM STOCK RECOVERY ADB, as i cant even get into the ui long enough to activate usb debugging
pitbull8265 said:
I have a recovery I made using twrp saved to my pc, and I chose the option to backup my efs, so all of my info is on my pc in the backup file.
HOW can I use adb sideload or ADB to push it to my phone???
HAS TO BE DONE FROM STOCK RECOVERY ADB, as i cant even get into the ui long enough to activate usb debugging
Click to expand...
Click to collapse
It will take a bit of reading but you will learn a lot!
Here's a guide with some commands, you just need to tailor it to your needs/paths, it says Samsung but all you need are the commands.
http://forum.xda-developers.com/showthread.php?t=2141817
If you have ioroot on your computer you have ADB. Plug in your phone in recovery mode and check device manager. It's probably under "unknown" as LG-LS980. You need to right-click and select "update driver", then manually select driver. From the list, you should be able to find something like Android composite ADB device. Select that one and it should then be recognized as ADB.
Hold Shift and right click on the ioroot folder and select "Open command window here", then in cmd type "adb devices". If all is good you will get a serial number as it detects your device. Once you got this you are ready to enter commands, check that guide for the right command to push the file to: /dev/block/platform/msm_sdcc.1/by-name/
as stated by Autoprime here: http://forum.xda-developers.com/showthread.php?t=2451390
I hope that's enough info to get you going. You should type "adb shell" first in ADB so you have access to root.
---------- Post added at 09:12 AM ---------- Previous post was at 09:03 AM ----------
Oh crap... I just re-read that. I don't think this will work if your backup is from TWRP. That needs to be restored from TWRP. Do you not have a backup from ioroot? That contains the img files you need.
---------- Post added at 09:18 AM ---------- Previous post was at 09:12 AM ----------
Ok, I found this...
"Even though all TWRP backup files carry the extension .win, they are either tar archives or filesystem images. System, data, cache and .android_secure are backed up as tar archives or gnu-zipped tar archives if compression is enabled. You can rename those .win files to .tar (.tar.gz if compressed) and extract them like a regular archive. Boot and recovery partitions are backed up as .img files using dd"
from: http://forum.xda-developers.com/showthread.php?t=1694617
I couldn't find out if TWRP backs up EFS to .tar or .img. Once you figure that out you should be able to rename them to modemst1.img and modemst1.img. I just verified on mine that the files are the same size, so I would guess they are actually img files and not compressed. They should be 3MB in size.
There's a lot more info in that thread by Autoprime that should help.
Anyone else get an error when trying to flash system image 63L? Says boota doesn't exist. I know some partitions are doubled but I assume the image should work. Just wondering if it's my PC drivers or an actual issue with the image itself. Not comfortable pulling it apart and flashing the pieces until there is more info on it. Not that I need it. I just like to play:laugh:
Gizmoe said:
Anyone else get an error when trying to flash system image 63L? Says boota doesn't exist. I know some partitions are doubled but I assume the image should work. Just wondering if it's my PC drivers or an actual issue with the image itself. Not comfortable pulling it apart and flashing the pieces until there is more info on it. Not that I need it. I just like to play:laugh:
Edit: Just realized I posted in wrong section. Mods please move to q&a if you see fit.
Click to expand...
Click to collapse
I had to update adb and fastboot
jaythenut said:
I had to update adb and fastboot
Click to expand...
Click to collapse
I updated through SDK and it says it's urrent but maybe my PC drivers are not playing nice. So it works for you though. That's good to know. It's probably my PC then. I should check if I added a static platform tools folder to my path instead of the updated one. Thanks for the reply
I have same problem as OP. Check out this post. I haven't tested, but I think this might solve the problem. http://forum.xda-developers.com/showpost.php?p=69239012&postcount=27
ADB sideload worked for me, but flashing factory images did not.
Golf c said:
ADB sideload worked for me, but flashing factory images did not.
Click to expand...
Click to collapse
Android studio updated the next time I opened it up. SDK tools version 25 is what it updated too and it works fine. Only fails on the first reboot bootloader command but then it flashes the rest no problem.
i just sideloaded with adb.
just open up the factory firmware files downloaded. within the folder there is a file named:flash-all.bat. i just clicked that after unlocking bootloader and it flashed the images. it did gives some slot error, but i haven't have any issues. im on the 63P image now as some claim it improves signal and wifi connectivity
Today, my phone got bricked after I installed Magisk, am i am looking for a way of sorting it out. The phone was running Android 9 DP3 when rooted, and I was following HighOnAndroids root guide on Youtube for reference,
I unlocked my bootloader and successfully installed TWRP. After this, I installed Magisk, which went throuygh perfectly fine. However, after rebooting the phone, I am stuck on the google splash screen, with a small progress bar that stays for the duration of the time on this screen. After about 2 minutes, the phone reboots into TWRP again.
Does anyone know how I could return to stock Android or at least escape this issue?
Many thanks
James
Jameswebb97 said:
Today, my phone got bricked after I installed Magisk, am i am looking for a way of sorting it out. The phone was running Android 9 DP3 when rooted, and I was following HighOnAndroids root guide on Youtube for reference,
I unlocked my bootloader and successfully installed TWRP. After this, I installed Magisk, which went throuygh perfectly fine. However, after rebooting the phone, I am stuck on the google splash screen, with a small progress bar that stays for the duration of the time on this screen. After about 2 minutes, the phone reboots into TWRP again.
Does anyone know how I could return to stock Android or at least escape this issue?
Many thanks
James
Click to expand...
Click to collapse
Use duces script to flash June google factory image.
jlokos said:
Use duces script to flash June google factory image.
Click to expand...
Click to collapse
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."
Jameswebb97 said:
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."
Click to expand...
Click to collapse
You need this information (the stuff I made bold + the hyperlink):
Code:
If you are having issues with this script:
Download the latest fastboot and adb Platform Tools UPDATED Dec. 22, 2017!!! This is the most common problem!!!
Download/Update Google USB Drivers
Video: Force-Installing the Android USB Drivers Fastboot & ADB
[B]Verify you have the [URL="https://wiki.lineageos.org/adb_fastboot_guide.html"]environment variable (path)[/URL] set for adb and fastboot[/B]
Try a different USB port
Try a different cable
Format Userdata in Stock Recovery
Try to boot stock before doing mods like Locking Bootloader / Kernel / TWRP / Magisk
Jameswebb97 said:
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."
Click to expand...
Click to collapse
umph....hate to tell you, but you have a long way to go...
so before going on this "journey", I would suggest you booting into TWRP again, and try installing (not adb sideloading, just in case you're doing that) Magisk again. Also, be sure you are using the latest (might be considered "beta") 16.4 for taimen... I'm thinking your boot.img or dtbo.img simply may have gotten glitchy and repatching (by installing Magisk again) might fix it...
Also, if you want to go a step further, you might want to consider using the official Magisk uninstaller. Since Magisk makes a copy of your stock boot and dtbo image, it may put that back so you can get it in working order to get into the system (although without root), and then figure things out and/or reinstall Magisk (through TWRP is best) while all things Magisk was removed...
Good luck and hope this helps....
Make sure you are trying to open from the correct location, and put .\fastboot
EvilDobe said:
You need this information (the stuff I made bold + the hyperlink):
Code:
If you are having issues with this script:
Download the latest fastboot and adb Platform Tools UPDATED Dec. 22, 2017!!! This is the most common problem!!!
Download/Update Google USB Drivers
Video: Force-Installing the Android USB Drivers Fastboot & ADB
[B]Verify you have the [URL="https://wiki.lineageos.org/adb_fastboot_guide.html"]environment variable (path)[/URL] set for adb and fastboot[/B]
Try a different USB port
Try a different cable
Format Userdata in Stock Recovery
Try to boot stock before doing mods like Locking Bootloader / Kernel / TWRP / Magisk
Click to expand...
Click to collapse
Ive tried all of this now, i got the script working, but now the phne says it is corrupt and i cannot get into recovery. Is this game over do you think?
simplepinoi177 said:
umph....hate to tell you, but you have a long way to go...
so before going on this "journey", I would suggest you booting into TWRP again, and try installing (not adb sideloading, just in case you're doing that) Magisk again. Also, be sure you are using the latest (might be considered "beta") 16.4 for taimen... I'm thinking your boot.img or dtbo.img simply may have gotten glitchy and repatching (by installing Magisk again) might fix it...
Also, if you want to go a step further, you might want to consider using the official Magisk uninstaller. Since Magisk makes a copy of your stock boot and dtbo image, it may put that back so you can get it in working order to get into the system (although without root), and then figure things out and/or reinstall Magisk (through TWRP is best) while all things Magisk was removed...
Good luck and hope this helps....
Click to expand...
Click to collapse
This is good advice, thanks. i have a new problem (ugh), where i got the script working through changing the paths, but now the phone says that it is corrupt and i cannot access TWRP. Game over?
Jameswebb97 said:
Ive tried all of this now, i got the script working, but now the phne says it is corrupt and i cannot get into recovery. Is this game over do you think?
Click to expand...
Click to collapse
With the unlocked bootloader it'll always say the device is corrupt. Manually put the device into the bootloader & flash the DeucesScript. You're basically starting over at this point but it is possible to get up & going again.
Jameswebb97 said:
This is good advice, thanks. i have a new problem (ugh), where i got the script working through changing the paths, but now the phone says that it is corrupt and i cannot access TWRP. Game over?
Click to expand...
Click to collapse
EvilDobe said:
With the unlocked bootloader it'll always say the device is corrupt. Manually put the device into the bootloader & flash the DeucesScript. You're basically starting over at this point but it is possible to get up & going again.
Click to expand...
Click to collapse
EvilDobe might be right...but I have a bit to offer before maybe starting all over...
I doubt you needed to edit the script and "change the paths." Most likely you merely did not have the images (you extracted from the .zip of the Full Factory image you got from the Google Developers site) inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders.
In any case, I suggest you get the TWRP image file [.img] (NOT the installer .zip necessarily), put the .img file "... inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders." (I've seen some users simply cut and paste those 2 .exe files only to the extracted folder -- this is why I state it this way) Then, power down your device. After it's off, hold down the Volume Down button and press & hold the Power button (this is the manual way to get into the Bootloader Mode). Once there, plug your phone into your computer (USB-A to USB-C would be best) and open a command prompt/powershell ("run as administrator" or with administrative priveleges) and direct it to the platform-tools folder (i.e. if I put it on my desktop, it would be "C:\Users\MyName\Desktop\platform-tools"), you can temporarily boot into TWRP via command
Code:
fastboot boot twrp-3.2.1-2-taimen.img
When in TWRP (hopefully), I suggest trying to do what I advised before -- try either Magisk installer to repatch the boot and dtbo image, or Magisk Uninstaller to attempt to replace your boot and dtbo to stock.
*NOTE: Of course, this is assuming you are running Microsoft Windows (if not, you will need to input .\ as @naiku suggested) and also the whole "device is corrupt" is due to "funky" boot image issues. If not, I/we can guide you to flashing the Full Factory back onto the phone (hopefully without losing data and settings)...
Good luck and hope this helps...
simplepinoi177 said:
EvilDobe might be right...but I have a bit to offer before maybe starting all over...
I doubt you needed to edit the script and "change the paths." Most likely you merely did not have the images (you extracted from the .zip of the Full Factory image you got from the Google Developers site) inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders.
In any case, I suggest you get the TWRP image file [.img] (NOT the installer .zip necessarily), put the .img file "... inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders." (I've seen some users simply cut and paste those 2 .exe files only to the extracted folder -- this is why I state it this way) Then, power down your device. After it's off, hold down the Volume Down button and press & hold the Power button (this is the manual way to get into the Bootloader Mode). Once there, plug your phone into your computer (USB-A to USB-C would be best) and open a command prompt/powershell ("run as administrator" or with administrative priveleges) and direct it to the platform-tools folder (i.e. if I put it on my desktop, it would be "C:\Users\MyName\Desktop\platform-tools"), you can temporarily boot into TWRP via command
Code:
fastboot boot twrp-3.2.1-2-taimen.img
When in TWRP (hopefully), I suggest trying to do what I advised before -- try either Magisk installer to repatch the boot and dtbo image, or Magisk Uninstaller to attempt to replace your boot and dtbo to stock.
*NOTE: Of course, this is assuming you are running Microsoft Windows (if not, you will need to input .\ as @naiku suggested) and also the whole "device is corrupt" is due to "funky" boot image issues. If not, I/we can guide you to flashing the Full Factory back onto the phone (hopefully without losing data and settings)...
Good luck and hope this helps...
Click to expand...
Click to collapse
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!
Jameswebb97 said:
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!
Click to expand...
Click to collapse
I wouldn't go that far with staying away. When I come across people IRL that want to start doing this stuff I always tell them to read the instructions, step through them, read the instructions again, ask questions (as you did here) BEFORE you get started, read the instructions again, and only when you're confident start messing with your device. This is a fun, and at times stressful, hobby. It's great when everything goes according to plan but it's an omg omg omg omg omg omg moment when you mess something up.
Start with baby steps. The straight upgrade to P is fairly simple provided your device is unlocked. Get that working & you'll be set. I have root on my DP3 & the only thing I've done so far is delete some apps from system that I know I don't want/need. If your main goal is to just enjoy your phone, test out Android P, and maybe go back... root isn't needed. Once everything is squared away & you're running for a day or so you can always fastboot to recovery, make a backup, and then try to add root. I hope you don't shy away & get deeper into the hobby. It truly starts to get fun when you begin to understand more of what is going on.
Jameswebb97 said:
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!
Click to expand...
Click to collapse
Hey I'm so glad you got it working! Leave me a "Thanks!" would make it up to me ... I'm always happy to help out and get things figured out...yet I don't get the satisfaction of knowing if it does end up helping a lot of the time because a good number don't come back with their experience...so thanks for that! Glad you got it going...
EvilDobe said:
I wouldn't go that far with staying away. When I come across people IRL that want to start doing this stuff I always tell them to read the instructions, step through them, read the instructions again, ask questions (as you did here) BEFORE you get started, read the instructions again, and only when you're confident start messing with your device. This is a fun, and at times stressful, hobby. It's great when everything goes according to plan but it's an omg omg omg omg omg omg moment when you mess something up.
Start with baby steps. The straight upgrade to P is fairly simple provided your device is unlocked. Get that working & you'll be set. I have root on my DP3 & the only thing I've done so far is delete some apps from system that I know I don't want/need. If your main goal is to just enjoy your phone, test out Android P, and maybe go back... root isn't needed. Once everything is squared away & you're running for a day or so you can always fastboot to recovery, make a backup, and then try to add root. I hope you don't shy away & get deeper into the hobby. It truly starts to get fun when you begin to understand more of what is going on.
Click to expand...
Click to collapse
And it's as @EvilDobe means.....
I remember back in the days of the Motorola Droids (OG Droid1, Droid 3, & Droid 4) where you could really mess things up and come out with a big ol' "brick" "paperweight" as there were many instances where you could not come back from (i.e. updating to a certain point, then attempting to downgrade when Google/Motorola/Verizon put blocks that breaks it). But this isn't the case these days. @Jameswebb97, at least with the Pixel 2's, Oreo and/or P(Android OS 9), it's actually more difficult than easy to get that too far gone. The only reason why I can help so many troubleshooting their issues is because I, myself, have wrecked my current device in some serious ways! So I can relate and have experience in helping in the same situations. I've gotten it to where it says "device is corrupt," (which isn't all that uncommon), BUT with the added desperate troubleshooting where I had to wipe/erase, changing partition types, format several partitions, even go about "resizing" the partition to match the "target extraction size" of the Full Factory flash, and even as far as learning to manually flash the various system partitions and that there are two (system_a & system_b) but, in Google's infinite wisdom(?), one flashes to system_a and the other to system_other!!! And I haven't even started on reading others' issues when going after the Slot A and Slot B complications -- I didn't even attempt to touch this in that troubleshooting story.
My point is: I think I've broken my device farther than most people and got it so close to the brink, and yet I was able to bring it back and am still using that same device today (most people would usually, at that point, go and get a RMA replacement). Honestly, as long as you have access to Bootloader Mode (which Google, in their infinite wisdom, seems to have placed it in the main board memory or separate memory rather than storage as to make it always accessible which makes it hard to "lose"), you have a really good (seemingly perfect) "safety net" in which you can always flash back to a working, stock state -- which is why it's the best policy to just make good backups before experimenting so, if anything, you get back to this state and restore all your data. I'm not trying to convince you to root or to try custom ROMs or anything -- even though there are many great reasons and capabilities of rooting -- I am simply appealingl to your sense of curiosity and reassure you so you aren't held back and you don't restrict and limit yourself if you don't want to, but are to fearful to experiment.
I hope you don't take this post as "lecturing" or anything, just some thoughts I hope you consider...
Glad it worked out in the end for you!