My Nexus 6 was Running on Blissrom and I tried Magisk to Root it and it works perfectly. But When I rebooted my device it stuck at Ap Fastboot mode So I tried to install stock rom and it giving me (Remote Failure) Failed to flash Partition.
Iam on Latest Bootloader Version.
Please Help me Devs
I’m thinking that your problem is that you are using a platform tool set that is too new. The newer versions were not designed to work well with the N6.
I suggest using minimal ADB & Fastboot. Use an older release to better match the older nature of the N6. try one of the 1.3 versions. Then just follow the install instructions on the factory full OTA images page to sideload the OTA. Or, if you are bootloader unlocked (says so on the screen when booted into the bootloader) you could Fastboot flash using the Google Factory Images page.
The instructions on each page are very accurate. Make sure to note when the say “older device” that includes the N6.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
I Tried 1.3 Mnimal adb version but still get this error remote failure .
ktmom said:
I’m thinking that your problem is that you are using a platform tool set that is too new. The newer versions were not designed to work well with the N6.
I suggest using minimal ADB & Fastboot. Use an older release to better match the older nature of the N6. try one of the 1.3 versions. Then just follow the install instructions on the factory full OTA images page to sideload the OTA. Or, if you are bootloader unlocked (says so on the screen when booted into the bootloader) you could Fastboot flash using the Google Factory Images page.
The instructions on each page are very accurate. Make sure to note when the say “older device” that includes the N6.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
i tried older 1.3 Minimal adb but still get this error . I attached an Image
I'm so not a Windows person, but are you positive the minimal version was actually being run, and not the studio version of Fastboot? The whole slot thing didn't exist way back.
Have you tried sideloading the OTA?
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Post a photo of the phone in bootloader mode - maybe we can spot something unusual.
Can you start recovery from bootloader?
No I Cant Reboot to Recovery
runekock said:
Post a photo of the phone in bootloader mode - maybe we can spot something unusual.
Can you start recovery from bootloader?
Click to expand...
Click to collapse
I can't reboot to recovery but i can temporaily boot twrp using nexus root toolkit
i have attached an image of Ap fastboot mode
I Can't Reboot to Recovery
ktmom said:
I'm so not a Windows person, but are you positive the minimal version was actually being run, and not the studio version of Fastboot? The whole slot thing didn't exist way back.
Have you tried sideloading the OTA?
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
When I try to reboot to recovery from ap fastboot nothing happens. So I try Nexus root toolkit to temporary boot into twrp but in twrp nothing is mounted so I cant do anything.
Please Help ME
Your photo shows nothing unusual.
Honestly, I don't have much hope. My guess is that your flash disk is damaged.
When you have TWRP running, it should be possible to get some diagnostics with adb on the PC. Below are some commands to try, they write the diag to some text files which you can post. Maybe some of it will tell us something, but I warn you that I won't know how to fix it in any case.
adb shell dmesg >dmesg.txt
adb shell cat /proc/partitions >parts.txt
adb shell df >df.txt
adb shell cat /tmp/recovery.log >recover.txt
it showing me access denied
runekock said:
Your photo shows nothing unusual.
Honestly, I don't have much hope. My guess is that your flash disk is damaged.
When you have TWRP running, it should be possible to get some diagnostics with adb on the PC. Below are some commands to try, they write the diag to some text files which you can post. Maybe some of it will tell us something, but I warn you that I won't know how to fix it in any case.
adb shell dmesg >dmesg.txt
adb shell cat /proc/partitions >parts.txt
adb shell df >df.txt
adb shell cat /tmp/recovery.log >recover.txt
Click to expand...
Click to collapse
Showing me Access Denied
Does adb devices work? And show the phone?
Yes it work it shows adb recovery but adb shell is not working when I try adb shell command its shows some variables like '$#
panup310 said:
Yes it work it shows adb recovery but adb shell is not working when I try adb shell command its shows some variables like '$#
Click to expand...
Click to collapse
~# are correct prompts when in the ADB shell. But the commands posted by @runekock should be entered as written without first entering the ADB shell. What willl happen is the ADB shell will execute the command and then dump the information into a text file in the directory where you are working on the PC.
Code:
adb shell dmesg >dmesg.txt
adb shell cat /proc/partitions >parts.txt
adb shell df >df.txt
adb shell cat /tmp/recovery.log >recover.txt
The first command tells ADB to enter a shell then read the dmseg file and output it to a text file "dmesg.txt". Each subsequent line is doing the same type of thing.
You'll want to post the output files of each of those.
If you can boot recovery and use ADB, I would think you should be able to sideload the factory full OTA image (linked in earlier post).
This should be achievable by:
Code:
adb shell twrp sideload
TWRP will switch to a screen "Running Recovery Commands". it should also have a line that says "Starting ADB sideload feature..."
Now flash the OTA using:
Code:
adb sideload NameOfFactoryOTA.zip
panup310 said:
When I try to reboot to recovery from ap fastboot nothing happens. So I try Nexus root toolkit to temporary boot into twrp but in twrp nothing is mounted so I cant do anything.
Please Help ME
Click to expand...
Click to collapse
If I'm understanding correctly. You need the file(s) you're trying to flash or restore & TWRP isn't showing any files.
If so I'd load an USB OTG device loaded with all possible files you might need. Then plug it in to your N6 microUSB & point TWRP to OTG device NOT Internal Storage. Then flash or restore whatever you want.
I Can't use USB OTG because it is not mounted
zapjb said:
If I'm understanding correctly. You need the file(s) you're trying to flash or restore & TWRP isn't showing any files.
If so I'd load an USB OTG device loaded with all possible files you might need. Then plug it in to your N6 microUSB & point TWRP to OTG device NOT Internal Storage. Then flash or restore whatever you want.
Click to expand...
Click to collapse
Its Show Internal Storage (0mb) OTG(0mb)
I tried to flash ota through side load but it failed
ktmom said:
~# are correct prompts when in the ADB shell. But the commands posted by @runekock should be entered as written without first entering the ADB shell. What willl happen is the ADB shell will execute the command and then dump the information into a text file in the directory where you are working on the PC.
Code:
adb shell dmesg >dmesg.txt
adb shell cat /proc/partitions >parts.txt
adb shell df >df.txt
adb shell cat /tmp/recovery.log >recover.txt
The first command tells ADB to enter a shell then read the dmseg file and output it to a text file "dmesg.txt". Each subsequent line is doing the same type of thing.
You'll want to post the output files of each of those.
If you can boot recovery and use ADB, I would think you should be able to sideload the factory full OTA image (linked in earlier post).
This should be achievable by:
Code:
adb shell twrp sideload
TWRP will switch to a screen "Running Recovery Commands". it should also have a line that says "Starting ADB sideload feature..."
Now flash the OTA using:
Code:
adb sideload NameOfFactoryOTA.zip
Click to expand...
Click to collapse
I have attached an Image of Twrp Error
Related
I was trying to install bad seeds sense 6 and sadly did not back up and did not had any old rom as aback up. the rom installed ok but i got this at the end set_metadata_recursive: some changes failed . the phone just keeps rebooting to twrp. i tried to transfer another rom via adb but im not getting my commands right, any other way to add another rom. or way to update my twrp ? please help?
kmacho714 said:
I was trying to install bad seeds sense 6 and sadly did not back up and did not had any old rom as aback up. the rom installed ok but i got this at the end set_metadata_recursive: some changes failed . the phone just keeps rebooting to twrp. i tried to transfer another rom via adb but im not getting my commands right, any other way to add another rom. or way to update my twrp ? please help?
Click to expand...
Click to collapse
Here's what to do (before having to RUU):
boot into TWRP;
connect USB cable;
adb shell into the device;
Code:
adb shell
see if /sdcard is ok (meaning you didn't mistakenly flash entirely the wrong ROM or something):
Code:
ls /sdcard
if the above shows files is a list of tings you recognize (like Downloads, Ringtones, whatever), two things are ok: i) your data area; and ii) your adb is working, then issue these commands (for good measure):
Code:
umount /system
exit
Using TWRP normally (use the touch screen), Wipe the following: system, cache, dalvik-cache, data;
Now, push a ROM file you want, for now I'd suggest one of the Sense 5.5 ROMs -- at least until the Sense 6 ROMs stabilize a bit more and we've had time to settle out all the new idiosynchrasies). Once downloaded, you'll have some zip file, let's call it "myrom.zip" for the purpose of commands (it'll be something different, just use the actual file name instead of myrom.zip below):
Code:
adb push myrom.zip /sdcard
Using the TWRP touch interface, just install the rom from /sdcard/myrom.zip
Just fyi -- the Sense 6 Roms have been exhibiting some oddities for folks in recoveries -- the issue actually is not the ROM, rather in the ext4 file system and some file system metadata bugs when dropping so many files in one shot as the ROM installer zips are doing. I've been debugging this in my TWRP builds and will be putting an option in to cover for the problem (it's deep in the android of ext4, believe it or not -- the kernel is detecting a problem and remounting the file systems read-only and that's what makes the install fail).
Hope this helps.
twrp sideload
tdhite said:
Here's what to do (before having to RUU):
boot into TWRP;
connect USB cable;
adb shell into the device;
Code:
adb shell
see if /sdcard is ok (meaning you didn't mistakenly flash entirely the wrong ROM or something):
Code:
ls /sdcard
if the above shows files is a list of tings you recognize (like Downloads, Ringtones, whatever), two things are ok: i) your data area; and ii) your adb is working, then issue these commands (for good measure):
Code:
umount /system
exit
Using TWRP normally (use the touch screen), Wipe the following: system, cache, dalvik-cache, data;
Now, push a ROM file you want, for now I'd suggest one of the Sense 5.5 ROMs -- at least until the Sense 6 ROMs stabilize a bit more and we've had time to settle out all the new idiosynchrasies). Once downloaded, you'll have some zip file, let's call it "myrom.zip" for the purpose of commands (it'll be something different, just use the actual file name instead of myrom.zip below):
Code:
adb push myrom.zip /sdcard
Using the TWRP touch interface, just install the rom from /sdcard/myrom.zip
Just fyi -- the Sense 6 Roms have been exhibiting some oddities for folks in recoveries -- the issue actually is not the ROM, rather in the ext4 file system and some file system metadata bugs when dropping so many files in one shot as the ROM installer zips are doing. I've been debugging this in my TWRP builds and will be putting an option in to cover for the problem (it's deep in the android of ext4, believe it or not -- the kernel is detecting a problem and remounting the file systems read-only and that's what makes the install fail).
Hope this helps.
Click to expand...
Click to collapse
sorry but i feel so ignorant. i installed the drivers and have the rom ready, but how to i the phone to adb shell. do i go to mount on twrp or on the advance settings adb sideload? when i put adb shell in the command prompt but it says adb not recognized. i would really appreciate your help if you could help me with more detail if possible.
kmacho714 said:
sorry but i feel so ignorant. i installed the drivers and have the rom ready, but how to i the phone to adb shell. do i go to mount on twrp or on the advance settings adb sideload? when i put adb shell in the command prompt but it says adb not recognized. i would really appreciate your help if you could help me with more detail if possible.
Click to expand...
Click to collapse
Goodness -- I thought you were all setup for adb and understood this stuff.
Here's what you need to do *first*, then follow the instructions above after you get adb working. To "adb shell" in to the phone -- you will boot into TWRP, which starts the adb server on the phone. But you use your computer and a "command terminal" window. We have to have this one way or another, so you have to learn. You will plug in your USB cable to the phone and computer, then the commands will work -- yes, they will work with TWRP.
To setup the adb stuff, learn here: http://forum.xda-developers.com/showthread.php?t=2277892 and look for Question 8
adb
tdhite said:
Here's what to do (before having to RUU):
boot into TWRP;
connect USB cable;
adb shell into the device;
Code:
adb shell
see if /sdcard is ok (meaning you didn't mistakenly flash entirely the wrong ROM or something):
Code:
ls /sdcard
if the above shows files is a list of tings you recognize (like Downloads, Ringtones, whatever), two things are ok: i) your data area; and ii) your adb is working, then issue these commands (for good measure):
Code:
umount /system
exit
Using TWRP normally (use the touch screen), Wipe the following: system, cache, dalvik-cache, data;
Now, push a ROM file you want, for now I'd suggest one of the Sense 5.5 ROMs -- at least until the Sense 6 ROMs stabilize a bit more and we've had time to settle out all the new idiosynchrasies). Once downloaded, you'll have some zip file, let's call it "myrom.zip" for the purpose of commands (it'll be something different, just use the actual file name instead of myrom.zip below):
Code:
adb push myrom.zip /sdcard
Using the TWRP touch interface, just install the rom from /sdcard/myrom.zip
Just fyi -- the Sense 6 Roms have been exhibiting some oddities for folks in recoveries -- the issue actually is not the ROM, rather in the ext4 file system and some file system metadata bugs when dropping so many files in one shot as the ROM installer zips are doing. I've been debugging this in my TWRP builds and will be putting an option in to cover for the problem (it's deep in the android of ext4, believe it or not -- the kernel is detecting a problem and remounting the file systems read-only and that's what makes the install fail).
Hope this helps.
Click to expand...
Click to collapse
do i need android sdk? and htc sync? i have the drivers i think? on my device managers it doesnt say adb . just device and on the info it says htc device
thank you
tdhite said:
Goodness -- I thought you were all setup for adb and understood this stuff.
Here's what you need to do *first*, then follow the instructions above after you get adb working. To "adb shell" in to the phone -- you will boot into TWRP, which starts the adb server on the phone. But you use your computer and a "command terminal" window. We have to have this one way or another, so you have to learn. You will plug in your USB cable to the phone and computer, then the commands will work -- yes, they will work with TWRP.
To setup the adb stuff, learn here: http://forum.xda-developers.com/showthread.php?t=2277892 and look for Question 8
Click to expand...
Click to collapse
thanks a lot! those commands work ! just needed to install the drivers . thanks! again
Hey there.
Was playing around with recovery and managed to wipe EVERYTHING (yeah...I know... )
I now have no OS and, obviously, when I reboot I get stuck in a bootloop.
My question is how do I flash a rom onto it, as there is no sdcard slot?
Thanks in advance!
adb sideload
b0gd4n said:
Hey there.
Was playing around with recovery and managed to wipe EVERYTHING (yeah...I know... )
I now have no OS and, obviously, when I reboot I get stuck in a bootloop.
My question is how do I flash a rom onto it, as there is no sdcard slot?
Thanks in advance!
Click to expand...
Click to collapse
you use adb from your adb / fastboot folder
TWRP / Advanced / Sideload
From PC adb /fastboot folder
you use
adb sideload name_of_rom.zip
or
just have TWRP loaded on the first screen and
adb push name_of_rom.zip /sdcard/
both ways the name_of_rom.zip needs to be in the same folder as adb / fastboot
1) Go back into recovery (power on while holding vol-, then select recovery). Plug in to PC and use "adb push <rom>.zip \sdcard\(rom).zip. Flash.
2) ADB Sideload (don't know how to use personally).
3) Go back into recovery and plug in a USB flash stick (either an OTG flash that will plug right in, or a microUSB-to-FemaleUSB cable and any USB flash stick or hdd).
I don't understand why people are so in love with microSD, when hardly anyone spends the cash on a 64gb card so the built in 32gb is just fine. If you need removable media, you have it in a $1.99 otg cable and any flash stick (or even a 3tb usb-hdd).
rpmccormick said:
1) Go back into recovery (power on while holding vol-, then select recovery). Plug in to PC and use "adb push <rom>.zip \sdcard\(rom).zip. Flash.
2) ADB Sideload (don't know how to use personally).
3) Go back into recovery and plug in a USB flash stick (either an OTG flash that will plug right in, or a microUSB-to-FemaleUSB cable and any USB flash stick or hdd).
I don't understand why people are so in love with microSD, when hardly anyone spends the cash on a 64gb card so the built in 32gb is just fine. If you need removable media, you have it in a $1.99 otg cable and any flash stick (or even a 3tb usb-hdd).
Click to expand...
Click to collapse
clsA said:
you use adb from your adb / fastboot folder
TWRP / Advanced / Sideload
From PC adb /fastboot folder
you use
adb sideload name_of_rom.zip
or
just have TWRP loaded on the first screen and
adb push name_of_rom.zip /sdcard/
both ways the name_of_rom.zip needs to be in the same folder as adb / fastboot
Click to expand...
Click to collapse
BenPope said:
adb sideload
Click to expand...
Click to collapse
thank you all!!!
ok, tried using and OTG cable...but it just broke when unplugged a driver from it...oh well.
Then tried booting into recovery, plugged in the the to my pc, started cmd as admin. now I can't find the phone.
adb devices returns an empty list.
Also tried starting adb sideload, but it just gets stuck at Starting ADB sideload feature. left it for up to 30 mins and nothing...
EDIT: also tried updating TWRP recovery. now I have 2.7.0.0 and I still have the same problems...
b0gd4n said:
ok, tried using and OTG cable...but it just broke when unplugged a driver from it...oh well.
Then tried booting into recovery, plugged in the the to my pc, started cmd as admin. now I can't find the phone.
adb devices returns an empty list.
Also tried starting adb sideload, but it just gets stuck at Starting ADB sideload feature. left it for up to 30 mins and nothing...
EDIT: also tried updating TWRP recovery. now I have 2.7.0.0 and I still have the same problems...
Click to expand...
Click to collapse
Yeah adb will not list any devices as USB Debugging needs to be enabled and as you dont have a OS installed you won't be able to enable it. Luckily you have the latest version if twrp install so you can use adb sideload from twrp, I think it's in the advanced tab. Start up adb sideload and make sure your Rom.zip file is in the adb folder on your PC and then type, adb sideload <name of Rom>.zip, and the sideload will copy zip file over abd install for you.
BlockABoots said:
Yeah adb will not list any devices as USB Debugging needs to be enabled and as you dont have a OS installed you won't be able to enable it. Luckily you have the latest version if twrp install so you can use adb sideload from twrp, I think it's in the advanced tab. Start up adb sideload and make sure your Rom.zip file is in the adb folder on your PC and then type, adb sideload <name of Rom>.zip, and the sideload will copy zip file over abd install for you.
Click to expand...
Click to collapse
yeah, I tried that. every time I try to enable it, it gets stuck at "Starting adb sideload". Left if for 30 mins and still nothing...
b0gd4n said:
yeah, I tried that. every time I try to enable it, it gets stuck at "Starting adb sideload". Left if for 30 mins and still nothing...
Click to expand...
Click to collapse
a bit misleading it is, it wont come up with a msg started or something (in other words your waiting for nothing, its already running after the starting msg). Plug your phone in and start the adb sideload in cmd. Of course your system must recognize your phone else your will error out with no device found.
windieboss said:
a bit misleading it is, it wont come up with a msg started or something (in other words your waiting for nothing). Plug your phone in and start the adb sideload in cmd. Of course your system must recognize your phone else your will error out with no device found.
Click to expand...
Click to collapse
aaah, so I don't have to wait for it to "start". OK then, I'll try this.
When I plug in the phone, Windows makes the "New device" sound, so I guess it does recognise it.
so it's adb sideload ....zip ?
b0gd4n said:
aaah, so I don't have to wait for it to "start". OK then, I'll try this.
When I plug in the phone, Windows makes the "New device" sound, so I guess it does recognise it.
so it's adb sideload ....zip ?
Click to expand...
Click to collapse
yup.
BlockABoots said:
Yeah adb will not list any devices as USB Debugging needs to be enabled and as you dont have a OS installed you won't be able to enable it. Luckily you have the latest version if twrp install so you can use adb sideload from twrp, I think it's in the advanced tab. Start up adb sideload and make sure your Rom.zip file is in the adb folder on your PC and then type, adb sideload <name of Rom>.zip, and the sideload will copy zip file over abd install for you.
Click to expand...
Click to collapse
windieboss said:
a bit misleading it is, it wont come up with a msg started or something (in other words your waiting for nothing, its already running after the starting msg). Plug your phone in and start the adb sideload in cmd. Of course your system must recognize your phone else your will error out with no device found.
Click to expand...
Click to collapse
ok, booted to recovery > Advanced > ADB Sideload > now it ways "Starting ADB sideload feature..."
Plugged in the device, started cmd from adb folder. Doing adb devices here returns no devices...
Tried all USB ports, still none...
b0gd4n said:
ok, booted to recovery > Advanced > ADB Sideload > now it ways "Starting ADB sideload feature..."
Plugged in the device, started cmd from adb folder. Doing adb devices here returns no devices...
Tried all USB ports, still none...
Click to expand...
Click to collapse
Same Problem here. No Solution?
b0gd4n said:
ok, booted to recovery > Advanced > ADB Sideload > now it ways "Starting ADB sideload feature..."
Plugged in the device, started cmd from adb folder. Doing adb devices here returns no devices...
Tried all USB ports, still none...
Click to expand...
Click to collapse
After you have started the sideloader server in twrp, just type adb sideload <name of rom>.zip and it will start sending the file. Dont bother trying to search for the device (adb device) as sideloader only understand the above command
BlockABoots said:
After you have started the sideloader server in twrp, just type adb sideload <name of rom>.zip and it will start sending the file. Dont bother trying to search for the device (adb device) as sideloader only understand the above command
Click to expand...
Click to collapse
doing just that:
start in recovery> start adb sideload (saying "starting adb sideload feature...") > plugged in (windows new device sound) > cmd with admin > navigate to sdk/platform-tools/ > and now I do the following command:
Code:
adb sideload filename.zip
and I get:
error: device not found
b0gd4n said:
doing just that:
start in recovery> start adb sideload (saying "starting adb sideload feature...") > plugged in (windows new device sound) > cmd with admin > navigate to sdk/platform-tools/ > and now I do the following command:
Code:
adb sideload filename.zip
and I get:
error: device not found
Click to expand...
Click to collapse
Hmmm, maybe try uninstalling all HTC drivers on the PC and then reinstalling.....
HTCDriver_4.2.0.001.exe
HTC_BMP_USB_Driver_x64_1.0.5375.msi (or x86 version if on win 32)
SyncManager_2.0.61.0.exe
found here, http://forum.xda-developers.com/showthread.php?t=2217396
http://www.mediafire.com/?o10b16j5b3r3o
try the above. If that still fails then give this a go
http://koush.com/post/universal-adb-driver
(after again uninstalling htc drivers)
I deleted os
Hello brother pls help me . I am sorry but i deleted is of htc one. Now can't anything . Here is the details
Twrp - yes
Hboot- unlocked tampered.
S-off
T-mobile htc one 4.4.2
Please help me . Here I saw many many expert so brother pls help me how to solve it & I can use my htc one .
Pls brother........
If someone can mail me in [email protected]
The details what to do. As I am really new & don't know what to do.
So again brother pls help.
windieboss said:
try the above. If that still fails then give this a go
http://koush.com/post/universal-adb-driver
(after again uninstalling htc drivers)
Click to expand...
Click to collapse
Whooo this worked!! Finally!!!
So I uninstalled all HTC stuff I had installed (drivers, sync manager, everything), then installed the stuff in the link.
Plugged in the HTC One in sideload mode and did
Code:
adb sideload filename.zip
and it worked!! Thanks again mate!
Hi guys, I would really appreciate some help. I am able to root my gear and transfer the TWRP via odin. But when I reboot into recovery it just goes back to the stock launcher. I read this in the developer thread:
IF YOU FIND THE RECOVERY IS NOT STICKING & YOUR GEAR WIPES WHEN ATTEMPTING TO ACCESS RECOVERY AFTER FLASHING.
YOU MUST ROOT YOUR GEAR PRIOR TO INSTALLING TWRP AGIAN & RUN THE FOLLOWING COMMANDS IN ADB.
*NOTE* YOU WILL HAVE TO ACCEPT A SUPERUSER REQUEST POPUP WHEN EXECUTING "SU" COMMAND.
*NOTE 2* PROBABLY A GOOD IDEA TO RUN THIS PRIOR TO FIRST INSTALLATION, TO SAVE TIME.
Code:
$ adb shell
$ su
# mount -o rw,remount /dev/block/mmcblk0p20 /system
# rm /system/recovery-from-boot.p
IF YOU DELETE THE "RECOVERY-FROM-BOOT.P" FILE YOU MUST RELFASH TWRP RECOVERY.
I have rooted and installed roms on phone before but working in the developer tools is new to me. Can anyone explain exactly how and when to do this during the TWRP recovery install process? Or possibly just point me to a how to or youtube on basic adb commands? I have searched and it looks super complicated. Just need to know how to run these 3 commands.
THANKS!
i have the exact same issue, is there any answer for this??
Wettpassat said:
Hi guys, I would really appreciate some help. I am able to root my gear and transfer the TWRP via odin. But when I reboot into recovery it just goes back to the stock launcher. I read this in the developer thread:
IF YOU FIND THE RECOVERY IS NOT STICKING & YOUR GEAR WIPES WHEN ATTEMPTING TO ACCESS RECOVERY AFTER FLASHING.
YOU MUST ROOT YOUR GEAR PRIOR TO INSTALLING TWRP AGIAN & RUN THE FOLLOWING COMMANDS IN ADB.
*NOTE* YOU WILL HAVE TO ACCEPT A SUPERUSER REQUEST POPUP WHEN EXECUTING "SU" COMMAND.
*NOTE 2* PROBABLY A GOOD IDEA TO RUN THIS PRIOR TO FIRST INSTALLATION, TO SAVE TIME.
Code:
$ adb shell
$ su
# mount -o rw,remount /dev/block/mmcblk0p20 /system
# rm /system/recovery-from-boot.p
IF YOU DELETE THE "RECOVERY-FROM-BOOT.P" FILE YOU MUST RELFASH TWRP RECOVERY.
I have rooted and installed roms on phone before but working in the developer tools is new to me. Can anyone explain exactly how and when to do this during the TWRP recovery install process? Or possibly just point me to a how to or youtube on basic adb commands? I have searched and it looks super complicated. Just need to know how to run these 3 commands.
THANKS!
Click to expand...
Click to collapse
i have the exact same issue, is there any answer for this??
Well it's been well over a year since I did that but let's see if I can help..... Before I start I'm hoping you've already enabled adb debugging on the gear and downloaded adb onto your computer. I believe you run the commands after you've run cygnia but before you flash twrp. You run the task from a command prompt from your pc. I'm pretty sure you don't include the $ or #. Before you start try the adb command- adb devices from the command prompt on your pc. That'll let you know if the gear is connected. I remember being a bit intimidated by it all as it was different to any other flash I'd done. In reflection it's very easy, type the line in a command prompt, press enter, wait for the cursor to come up again, type the next line. As for guides..... I can't remember which one I used but there's plenty out there.
CONFIRMED
I've looked a bit arround how we could achieve root on the fire without TWRP.
I don't have 5.1.1 installed, but I'm hoping the following is still possible.
(I tested it on a brand-new fire, that never came in touch with TWRP or a custom rom)
If someone could test this please:
Confirmed, working:
- Enable ADB-Debugging in Developer Settings, then:
Code:
adb reboot-bootloader
fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
fastboot continue
adb wait-for-device && adb shell
You should now hopefully have a shell with root-priviledges:
Code:
[email protected]:/ #
Please test and report back.
To Flash SuperSU and make root persistent (thx @pappasmurfsharem):
https://www.androidfilehost.com/?w=files&flid=42700
If you are still inside "adb shell" from the last command above type "exit" first.
Or just skip the "adb shell" command above.
Code:
adb remount
adb push files\libsupol.so /data/local/tmp/
adb push files\root_fire.sh /data/local/tmp/
adb push files\su /data/local/tmp/
adb push files\Superuser.apk /data/local/tmp/
adb push files\supolicy /data/local/tmp/
adb shell chmod 777 /data/local/tmp/root_fire.sh
adb shell /data/local/tmp/root_fire.sh
# This Part reopened fastboot and I just re-ran the cmds from the first post in this thread #
fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
fastboot continue
adb wait-for-device && adb remount
adb shell /system/xbin/su --install
adb reboot
It works, in fact I've used it to remove a couple of apks from Amazon on 5.1.1 but... I can't see firelauncher, for example.
Huge thanks k4y0z!
I have another Fire due to arrive tomorrow, will definitely try it if I get 5.1.1.
Could you give the commands for restoring the old bootloader? Or would we use FlashFire? I presume there is a risk of hard brick. Flashing the bootloader would include the preloader & amazon recovery? I see there is a Boot & a Recovery partition.
Confirmed. This works on 5.1.1
Thanks, it is working on my fire 5.1.1.
now just need to figure out how load TWRP on here
I'll do it... I only have one, but I bought it for $30, so I don't mind helping here!
cococo42 said:
It works, in fact I've used it to remove a couple of apks from Amazon on 5.1.1 but... I can't see firelauncher, for example.
Click to expand...
Click to collapse
Thanks for the feedback
blueberry.sky said:
Huge thanks k4y0z!
I have another Fire due to arrive tomorrow, will definitely try it if I get 5.1.1.
Could you give the commands for restoring the old bootloader? Or would we use FlashFire? I presume there is a risk of hard brick. Flashing the bootloader would include the preloader & amazon recovery? I see there is a Boot & a Recovery partition.
Click to expand...
Click to collapse
I have never used FlashFire.
I believe it should be enough to flash the old fastboot, though I'm unsure about the preloader.
You are correct, the following could potentially WILL brick your Fire, do at your own risk!
Code:
adb push lk.bin /data/local/tmp/
adb push preloader_prod.img /data/local/tmp/
adb shell "dd if=/data/local/tmp/lk.bin of=/dev/block/platform/mtk-msdc.0/by-name/UBOOT"
adb shell "dd if=/data/local/tmp/preloader_prod.img of=/dev/block/platform/mtk-msdc.0/mmcblk0boot0"
adb reboot-bootloader
Now fastboot boot should hopefully work again.
Please test and report back!
Total noob question, I know... I haven't used Android Studio before, but am definitely a computer guy... Very simply, can you show me how to just run a straight up terminal to type these commands without creating a new "app"...
I just have a lack of android coding experience, but if you tell me, I'll understand very quickly...
jbraney said:
Total noob question, I know... I haven't used Android Studio before, but am definitely a computer guy... Very simply, can you show me how to just run a straight up terminal to type these commands without creating a new "app"...
I just have a lack of android coding experience, but if you tell me, I'll understand very quickly...
Click to expand...
Click to collapse
You don't need android studio to do any of this. Do you have ADB and fastboot installed? If you need help PM me.
jbraney said:
Total noob question, I know... I haven't used Android Studio before, but am definitely a computer guy... Very simply, can you show me how to just run a straight up terminal to type these commands without creating a new "app"...
I just have a lack of android coding experience, but if you tell me, I'll understand very quickly...
Click to expand...
Click to collapse
You don't need Android Studio, you just need adb and fastboot, your best bet is to search this forum for these two.
Well this is exciting!
Alright guys... this looks promising!
I'll go ahead and try the bootloader downgrade trick in a few hours, assuming nobody else has done it by that time .
Installed supersu on 5.1.1 ... works perfect ! THX VERY MUCH!!
lordpit said:
Installed supersu on 5.1.1 ... works perfect ! THX VERY MUCH!!
Click to expand...
Click to collapse
Does this mean that the bootloader is unlocked? With root we can now flash CM12.1 and GAPPS?
jbraney said:
Does this mean that the bootloader is unlocked? With root we can now flash CM12.1 and GAPPS?
Click to expand...
Click to collapse
The 5.1.1 bootloader still prevents TWRP recovery/others from being installed. According to post #7, we might be able to downgrade bootloaders.
k4y0z said:
Thanks for the feedback
I have never used FlashFire.
I believe it should be enough to flash the old fastboot, though I'm unsure about the preloader.
You are correct, the following could potentially brick your Fire, do at your own risk!
I have the old fastboot attatched to this post to flash it:
Code:
adb push lk.bin /data/local/tmp/
adb shell "dd if=/data/local/tmp/lk.bin of=/dev/block/platform/mtk-msdc.0/by-name/UBOOT"
adb reboot-bootloader
Now fastboot boot should hopefully work again.
Please test and report back!
Click to expand...
Click to collapse
This bricked my fire on 5.1.1 ... do not do this! Here is what I did to brick it:
Code:
adb reboot-bootloader
fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
fastboot continue
adb push lk.bin /data/local/tmp/
adb shell "dd if=/data/local/tmp/lk.bin of=/dev/block/platform/mtk-msdc.0/by-name/UBOOT"
adb reboot-bootloader
maratd said:
This bricked my fire on 5.1.1 ... do not do this! Here is what I did to brick it:
Code:
adb reboot-bootloader
fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
fastboot continue
adb push lk.bin /data/local/tmp/
adb shell "dd if=/data/local/tmp/lk.bin of=/dev/block/platform/mtk-msdc.0/by-name/UBOOT"
adb reboot-bootloader
Click to expand...
Click to collapse
Damn can you still get into fastboot with VOL-DOWN + Power?
Maybe we also have to flash the older preloader
jbraney said:
Does this mean that the bootloader is unlocked? With root we can now flash CM12.1 and GAPPS?
Click to expand...
Click to collapse
Bootloader is still locked. But if we can downgrade to the 5.0.1 fastboot bootloader then we can return to flashing CM12.1, SlimLP, gapps as we did before (temporarily loading twrp into memory then flashing rom).
k4y0z said:
CONFIRMED
I've looked a bit arround how we could achieve root on the fire without TWRP.
I don't have 5.1.1 installed, but I'm hoping the following is still possible.
(I tested it on a brand-new fire, that never came in touch with TWRP or a custom rom)
If someone could test this please:
- Enable ADB-Debugging in Developer Settings, then:
Code:
adb reboot-bootloader
fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
fastboot continue
adb wait-for-device && adb shell
You should now hopefully have a shell with root-priviledges:
Code:
[email protected]:/ #
Please test and report back.
If it works we can probably restore the old bootloader with "fastboot boot" support.
Click to expand...
Click to collapse
Is this all I habe to do, getting into the root shell or are there any more things to do for a root in my 5.1.1?
Thanks
I was able to install MM using Sideload with MAC.
Procedure is the same as Windows the difference is that you NEED the most recent ADB.
https://developer.android.com/studio/index.html
Check using ./adb version that it is running at least 1.0.32
Davids-MacBook-Air:tools David$ ./adb devices
List of devices attached
XXXXXX sideload
Davids-MacBook-Air:tools David$ ./adb sideload update.zip
Total xfer: 2.07x
abcdavidefg said:
So I try to install sideload using my MAC but no luck.
I made sure the reactivation lock is "off"
I installed the ADB in my MAC.
I test:
./adb devices (and it shows my devices)
./adb reboot (and it reboots my phone)
I'm assuming that the ADB is working.
When I go into recovery mode and the "update ADB" this is what happened
Davids-MacBook-Air:mac David$ ./adb devices
List of devices attached
06157df643132f18 sideload
Davids-MacBook-Air:mac David$ ./adb sideload update.zip
error: protocol fault (no status)
Davids-MacBook-Air:mac David$
Phone wipes everything.
In the screen shows something like installing Hash tree
Hash tree successful
Phone reboots but it turns on regularly with everything wipe but no MM update.
Help!! anyone
Click to expand...
Click to collapse
Does this page help you?
http://forum.xda-developers.com/showthread.php?t=2720846
Jimmyvb98 said:
Does this page help you?
http://forum.xda-developers.com/showthread.php?t=2720846
Click to expand...
Click to collapse
No luck yet.
I try to transfer the file using
./adb push update.zip /sdcard (didn't work).... I'm assuming because I don't have a "/sdcard" directory.
Then I manually created a file called "sdcard" in the root of my memory.
Then copied the file from my computer to the memory of my phone.
Then reboot (power+home+volup) choosed update from external but I get an error saying no .../sdcard (file or directory)
I think the problem is that I can't move the file to the root of the phone. I guess I need root access (which I can't get)
I was able to sideload the file using MAC.
In general is relative the same method. Just make sure you have the most recent version of ADB for MAC.
Most of the "easy" installs of ADB for MAC are old version.
I'll post a more detail explanation. Step by Step if anyone ask for it