Related
I've had a MT3G for awhile and just upgraded to a Nexus One. I still have my old phone and can use adb with the MT3G without any issues. When I try using adb with the Nexus one i receive an error insufficient permissions on the device. Here's some more info about my setup:
Nexus One:
Clockwork Mod Recovery
CM6.0.0RC1
USB debugging is enabled
Computer:
Ubuntu 10.04
I have the rules set up for adb
I have tried remounting and restarted adb with root permissions and have still receiving the same error. I've tried connecting to another Ubuntu box and a windows xp box with the same error.
Any help?
What response (if any) do you get to the "adb devices" command?
What exact command are you trying to execute when you get that error?
When i run adb devices i receive this:
List of devices attached
???????????? no permissions
adb shell gives this:
error: insufficient permissions for device
I receive the same output running the commands as user or superuser. I've also killed and started the server as user and root. Remember I'm running the udev rules so I can run these commands as user.
Today I went ahead and reflashed my phone. I downloaded cm6 from xda and frf91 from the same post. Checked the md5sum for the update and then wiped and flashed.
Even after the wipe I'm in the same spot.
Can you access the device via fastboot?
When I first got the device I used fastboot to unlock the bootloader.
now the command
Code:
fastboot reboot
hangs at
Code:
< waiting for device >
I can still reboot the device into recovery and fastboot.
another update.
I rebooted into recovery (holding trackball and power) and tried running fastboot devices. It found my phone. While fully loaded it normally displays nothing.
adb devices is still blank but I'm not sure if it's supposed to work while in recovery.
last thoughts, as it's been a while since I've used adb on Ubuntu...
Code:
./adb kill-server
./adb start-server
./adb devices
???
./PROFIT
It seems to be somehow an issue with your local adb set up, not anything phone-related. Could even perhaps be a driver issue.
raim1312 said:
another update.
I rebooted into recovery (holding trackball and power) and tried running fastboot devices. It found my phone. While fully loaded it normally displays nothing.
adb devices is still blank but I'm not sure if it's supposed to work while in recovery.
Click to expand...
Click to collapse
Yeah, should've pointed out that fastboot will only work while in fastboot mode
trackball + power == fastboot, btw.
volume_down + power == hboot, which will let you boot into recovery
trackball + volume_down + power == three-finger salute, the equivalent to CTRL+ALT+DEL
i get the same results after killing and starting adb either as user or root. i'll pull out the drivers and android sdk and reinstall. i'll let you know how it goes once its done
codesplice said:
Yeah, should've pointed out that fastboot will only work while in fastboot mode
trackball + power == fastboot, btw.
volume_down + power == hboot, which will let you boot into recovery
trackball + volume_down + power == three-finger salute, the equivalent to CTRL+ALT+DEL
Click to expand...
Click to collapse
Yeah sorry about that one. i'm still a newb but willing to learn
i just reinstalled the android sdk and removed the udev rules. gave my pc a reboot and killed then started the adb server.
same issue.
to verify adb was working i plugged my gf's mt3g in and adb found it.
i've never need to reinstall usb drivers in anything but windows so honestly I don't know how to do it in ubuntu. can you point me in the right place?
I'm afraid I'm out of ideas then. I've only had very limited experience using adb on my Ubuntu install
well thanks for all the help codesplice.
i'll keep looking and post anything i do here.
raim1312 said:
well thanks for all the help codesplice.
i'll keep looking and post anything i do here.
Click to expand...
Click to collapse
Please do. Everything that I was able to find on google relates to a screwy adb server... but being able to adb on another device complicates things. Very interested to see what you figure out on this.
I installed the rom froyou frf50 with radio from here:
http://android.modaco.com/content/g...ed-update-zip-no-radio-option-online-kitchen/
didn't work.
while looking into returning the phone to stock i received an ota update. so i ran it.
the update failed during a signature check.
i tried to follow the instructions here to return to stock: http://androidspin.com/2010/05/06/guide-unrooting-your-nexus-one-its-like-it-never-happened-almost/
only issue is fastboot will not find my device.
performed a nandroid restore to go back to cm6 frf91.
fastboot still will not find my device.
i'm at a loss here. the device is usable for everything but adb. and adb is the main thing i need. i dont' want to keep whacking at this and cause more issues.
any ideas are welcome. all my data is backed up and the bootloader is already unlocked.
its... working??? i finally got adb to recognize my device.
first i restored the phone back to stock using this: http://forum.xda-developers.com/showthread.php?t=717870
then i replaced the cable i was using for one from a Motorola droid. (since the mt3g has a different usb port i had to use a different cable).
then i ran the adb kill and start server commands as root. and voila. it works.
i remove the cable and go back to the one that came with the phone and it still works. not sure what happened but adt is working as well. so im back up and running. i wish i knew the cause of this frustration but i fear i will never know. anyway thanks for all your help!
Yikes.... take your boat back!!!
Perhaps you ran chmod u+s on adb?
Edit: Yep, that was the problem for me..
I don't know the commands to well, so i just right clicked adb and went to permissions and removed set uid.
seems adb needs started from root, but making the file always run as root doesn't work so well.. I thought it would fix my annoyances with eclipse starting adb with not enough permissions. Perhaps ill chmod u+s eclipse instead.
Oh and btw... nexus one can kiss my a$#. HTC Hero!!
Solution for permission problems:
http://wiki.cyanogenmod.com/index.php?title=Udev
i used this method to boot:http://forum.xda-developers.com/showthread.php?t=920347
first it worked but i powered my nc off and since it didn't boot even if a kept the n button pressed,when i plug it on my computer adb dont detect it and the light is orange in charge and on computer
plz help me
thx
cwr
i boot from cwr and used this method:http://forum.xda-developers.com/showthread.php?t=931720
but still doesn't boot
need help
please someone help me i don't know what to do
Does your NC totally not boot at all? If you followed instruction in this thread - http://forum.xda-developers.com/showthread.php?t=931720 basically you are booting from SD. In this case, it has nothing to do what's on your internal flash. Check whether your SD card is created correctly.
it boots
it only boots from CWR
i had the same problem you have. i booted into CWM using the 1 gig sdimage, put the stock boot.img and system.img (from here - http://forum.xda-developers.com/showthread.php?t=919353) and did the dd commands from adb as shown there and my system booted normally.
i had a problem with the stock B&N usb cable where it didn't detect through adb at all. i had to use a different usb cable and it worked good.
i'll try
thx i'll try it tonight,it 1 pm in france^^,tell you if it worked
i don't have any other cable,i ll try to see at virgin tomorrow ,if you have an easier way let me know
the only other way i can think of doing that is to use nookie froyo and wireless adb. the problem with this method was when i tried doing that, i had no market, so i couldn't get wireless adb. i didn't feel like doing a workaround to getting that apk on there. problem with this method is i didn't know if the partitions would look the same or even show off the nook as i was working off the sdcard for froyo, so i wouldn't be able to say if this would actually work.
using the stock B&N cable, i noticed that the device would show in adb, but not online. so reading around i found out if u used a different usb cable it might work, so i did and it did work lol.
Simply flash my repartition boot file...
Sent from my HTC Desire using XDA App
samuelhalff said:
Simply flash my repartition boot file...
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
i looked at sam's method before as well, but didn't try it since i had luck with my usb cable connection for ADB usage. just dd-ing system and boot seemed to work for me and allowed me to keep it how i had it before (with all my previous apps installed). my partitions are probably still shorter though. flashing the zip looks like it'll restore everything to stock.
i bought a new cable,still don't work with adb ,windows detect it but it says it's two different devices and i cant change the driver,sooner nc booted under nookie froyo i don't know how,i'll try to boot again with 2.2 and work with adb from here
were u able to adb in the first place? i used this link http://forum.xda-developers.com/showthread.php?t=882751 to get it working. i also went through the nookdev site to get adb working. i was assuming it was my cable at least since it was tweaking (connecting/disconnecting) with the stock B&N usb cable.
still no adb even over nookie froyo,i try with your method
i have adb usb ,now i don't know how to do cause i only have a 2gb card so i only can put boot but not system on it,i don't know how to enter the command ,is it in adb shell?
i went through CWM and mounted system, data and sdcard. u use adb shell to get into the shell in the nook. then adb'd and
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
dd if=/sdcard/system.img of=/dev/block/mmcblk0p5
Click to expand...
Click to collapse
did that. i guess u can put one file and then another file after the first file is dd'd. i used adb to push those img files to the sdcard.
i try it,could you make me a kind of how to with steps and stuff plz?
petithor said:
i try it,could you make me a kind of how to with steps and stuff plz?
Click to expand...
Click to collapse
in your situation this is what i would do.
boot into cwm
mount system, boot and sdcard through the menus
without entering the shell (adb shell) type in: adb push <boot.img file location> /sdcard
now enter the nook's shell by type adb shell then enter
so you're in the nook's shell, and type "dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1"
delete the boot.img file so you have enough space on for the system image by typing "rm boot.img" (make sure you're in the root of sdcard)
type exit to exit the nook's shell
now you're going to push the system.img to the sdcard: adb push <system.img file location> /sdcard
enter into the nook's shell again (adb shell)
type in "dd if=/sdcard/system.img of=/dev/block/mmcblk0p5"
once that is done reboot and everything should work just like before you ran that other script.
this is pretty much what i did. i'm on windows 7 x64 so i just dragged and dropped the files into the command prompt to get the file locations.
again: http://forum.xda-developers.com/showthread.php?t=919353 for more reference of what i was doing.
it worked thx very much ,you are a god besides the humans
Hello, I am very new to this forum. I searched everywhere but couldn't find an answer to my problem. I really appreciate it if you can help me as I am a total noob in android.
Previously my power button was a little buggy, it works on and off, and I solved it by wiping the partition cache in stock recovery <e3>.
My power button completely stopped working today for no reason that I know off.
Out of frustration, I tried what I did last time by booting into recovery mode (using quickboot this time) but then to realise that I can't choose anything/ get out of the recovery mode.
Nothing works by removing the battery. When the battery is reinserted, it boots back into recovery.
My phone is rooted, non CWM. Has a bad eMMC chip with a susceptible kernel. (latest update from KiES, no custom ROMs)
I got this phone as a prize, so there's no warranty that comes with it.
What can I do now? I have heard of this ADB thing but I have no idea how it works. Does it help? If so, how?
Thank you.
Edit: Service centre fixed it. Turns out its a pretty complex issue.
Click to expand...
Click to collapse
you could try adb.. you need to first install adb .. its included in the android SDK package. eg http://forum.xda-developers.com/showthread.php?t=1241935
once installed.. boot into recovery... connect phone to pc.. go to the adb folder and run command prompt in there.
then use command
adb devices
<the output should show a device connected> if yes then
adb reboot
nokiamodeln91 said:
you could try adb.. you need to first install adb .. its included in the android SDK package. eg http://forum.xda-developers.com/showthread.php?t=1241935
once installed.. boot into recovery... connect phone to pc.. go to the adb folder and run command prompt in there.
then use command
adb devices
<the output should show a device connected> if yes then
adb reboot
Click to expand...
Click to collapse
Hello, thank YOU very much! I got it to reboot properly and working. And I learnt a lot in the meantime.
Words cannot express my gratitude right now.
I have another question though, is it possible for me to wipe partition cache thru adb?
yes using adb shell, you will get the access to file system.
for this adb should run as root.
adb root
adb shell > this should give a # and not $
mount /cache
ls > this should list the files. check for cache folder
rm -r cache
same way dalvik cache (if you want)
cd data
ls > lists dalvik cache
rm -r dalvik-cache
adb reboot
nokiamodeln91 said:
yes using adb shell, you will get the access to file system.
for this adb should run as root.
adb root
adb shell > this should give a # and not $
mount /cache
ls > this should list the files. check for cache folder
rm -r cache
same way dalvik cache (if you want)
cd data
ls > lists dalvik cache
rm -r dalvik-cache
adb reboot
Click to expand...
Click to collapse
Okay, so I tried to do what you suggested, and got stuck at adb root. This is what I got in return:
"Adbd root cannot run as root in production builds"
So what I did was to skip to the second step,
"adb shell"
This is what I got in return:
[email protected]:/ $
I entered the command "su", granted su access on my phone using supersu (got a pop-up) and got this:
[email protected]:/ #
Moving on, I entered "cache /mount" and it repeatedly failed to mount.
I read up a bit of it and it seems like its because my bootloader is not unlocked.
But given the fact that my power button is malfunctioned, I cannot unlock it by normal means. I gave some thought onto PhilZ safe kernel but then the fact that my phone is susceptible to brick if I unlock the bootloader (there will be a data wipe right?) makes me stuck at where I am now.
What are your recommendations?
Additional info on eMMC:
[email protected]:/sys/class/block/mmcblk0/device # cat cid | cut -b 19,20
gives back: 19 (susceptible)
[email protected]:/sys/class/block/mmcblk0/device # cat name hwrev fwrev manfid oemid date type
gives:
Name: VYL00M
HwRev: 0x0
FwRev: 0x0 (not completely safe)
Manfid: 0x000015
Oemid: 0x0100
Date: 01/2012
Type: MMC
nokiamodeln91 said:
you could try adb.. you need to first install adb .. its included in the android SDK package. eg http://forum.xda-developers.com/showthread.php?t=1241935
once installed.. boot into recovery... connect phone to pc.. go to the adb folder and run command prompt in there.
then use command
adb devices
<the output should show a device connected> if yes then
adb reboot
Click to expand...
Click to collapse
you saved me big time!!
I have almost the same problem
I bootlooped my tab and forgot to turn on debugging option. I used framaroot for rooting. Only way to make my tab go back to normal is by factory resetting through recovery mode but my Power button isnt working help pls?
FluffyBunneh said:
I bootlooped my tab and forgot to turn on debugging option. I used framaroot for rooting. Only way to make my tab go back to normal is by factory resetting through recovery mode but my Power button isnt working help pls?
Click to expand...
Click to collapse
Did you find a solution for this?
My Samsung j7 is stuck in recovery mode and power button is broken...and my USB debugging is also ON but phone is NOT detecting On PC...not even in DEVICE MANAGER...I checked in ADB deveices command but still nothing...help me....
FluffyBunneh said:
I bootlooped my tab and forgot to turn on debugging option. I used framaroot for rooting. Only way to make my tab go back to normal is by factory resetting through recovery mode but my Power button isnt working help pls?
Click to expand...
Click to collapse
I also have the same problem, my phone is now stuck in recovery, and without power button I am not able to bring it out of recovery mode, did you manage to find a fix for this? My phone is not getting listed in "adb devices"!
Phone:SM J200G
After installing stock rom via odin
I enter into recovery mode and forget to on USB debugging. Also my power button dead.
What to do? Now?
nokiamodeln91 said:
you could try adb.. you need to first install adb .. its included in the android SDK package. eg http://forum.xda-developers.com/showthread.php?t=1241935
once installed.. boot into recovery... connect phone to pc.. go to the adb folder and run command prompt in there.
then use command
adb devices
<the output should show a device connected> if yes then
adb reboot
Click to expand...
Click to collapse
hey i got the same problem when i charged my phone after it turn of (low bat). Recovery mode suddenly showed up and i cant choose reboot system now because the lock button is stuck. So i tried the adb and installed it but when i tried to use it . it cant find my device the usb cord is 100% working and idk what to do anymore
I'm having the exact same problem. My power button is broke, I put the phone into Recovery Mode and now I can't get out. ADB can't find my device so I can't use that either. I have no idea what to do.
nokiamodeln91 said:
you could try adb.. you need to first install adb .. its included in the android SDK package. eg http://forum.xda-developers.com/showthread.php?t=1241935
once installed.. boot into recovery... connect phone to pc.. go to the adb folder and run command prompt in there.
then use command
adb devices
<the output should show a device connected> if yes then
adb reboot
Click to expand...
Click to collapse
please help i have the same problem but my device is not recognized
bryll1022 said:
hey i got the same problem when i charged my phone after it turn of (low bat). Recovery mode suddenly showed up and i cant choose reboot system now because the lock button is stuck. So i tried the adb and installed it but when i tried to use it . it cant find my device the usb cord is 100% working and idk what to do anymore
Click to expand...
Click to collapse
please help i have the same problem
MaeButArt said:
I'm having the exact same problem. My power button is broke, I put the phone into Recovery Mode and now I can't get out. ADB can't find my device so I can't use that either. I have no idea what to do.
Click to expand...
Click to collapse
did you find a solution i have the same problem
MaeButArt said:
I'm having the exact same problem. My power button is broke, I put the phone into Recovery Mode and now I can't get out. ADB can't find my device so I can't use that either. I have no idea what to do.
Click to expand...
Click to collapse
same did anyone find solution for this?
nokiamodeln91 said:
yes using adb shell, you will get the access to file system.
for this adb should run as root.
adb root
adb shell > this should give a # and not $
mount /cache
ls > this should list the files. check for cache folder
rm -r cache
same way dalvik cache (if you want)
cd data
ls > lists dalvik cache
rm -r dalvik-cache
adb reboot
Click to expand...
Click to collapse
when i plug my phone to pc its not connecting if i use commang adb reboot its say "error: no devices/emulators found"
Ive encounter that problem with j4 + what i did is just let the battery run out after that be ready to press button for download mode and insert charging cable to phone, hope this will help on your problem
x33eraser said:
Hello, I am very new to this forum. I searched everywhere but couldn't find an answer to my problem. I really appreciate it if you can help me as I am a total noob in android.
Previously my power button was a little buggy, it works on and off, and I solved it by wiping the partition cache in stock recovery <e3>.
My power button completely stopped working today for no reason that I know off.
Out of frustration, I tried what I did last time by booting into recovery mode (using quickboot this time) but then to realise that I can't choose anything/ get out of the recovery mode.
Nothing works by removing the battery. When the battery is reinserted, it boots back into recovery.
My phone is rooted, non CWM. Has a bad eMMC chip with a susceptible kernel. (latest update from KiES, no custom ROMs)
I got this phone as a prize, so there's no warranty that comes with it.
What can I do now? I have heard of this ADB thing but I have no idea how it works. Does it help? If so, how?
Thank you.
Click to expand...
Click to collapse
Sorry i hope i post this right first timer your guide didnt workt but i found a workaround:
usbc to usb adapter i tryed a mouse not working but my cheab truest cxt tastatur ACCEPTED THE ENTER BUTTON
and i came out of this because only repair loking cost 60 bucks .not with me i hope this help others too
i am doing a tiktok video on it(guide) PrestigeWorldWideUS
buy usbc to usb adapter i try your keybords sorry my english
I believe I habe the kfsowi model. it is 11.3.1.0 it is rooted and I am wanting to factory reset it but I dont have a factory cable. just a normal usb cable that I've been using adb to transfer and even instlal some files because through tweaking it, it lead to a missing status bar in which i change the qmenu = to 0 and 1 or whatever in build.prop but no matter what it doesnt keep the status bar active at all times like it should be. it is non existent until i click on an app in apex, adw or any launcher ive tried then it flashes and disappears. during this flash it is not usable no matter how fast i click it.
also a small issue it has is ever reboot, it says kindle is upgrading but it is not upgrading at all because i have tried to click check now in settings to check for updates but every time it says update failed. next after that message it says starting applications for about 20 seconds. long bootup. i have probably messed with tweak i shouldnt have with pimp my rom and also android tweaker 2 and pro before it became 2. so the status bar is non existent. sucks cause cant even get facebook notifications lol.
i did factory reset it by the menu and also by using andromizer app to click recovery mode and do it that way.
(without status bar i been using all in one gestures but now recently i switched to using LMT.
this kindle has a few issues since i made it kinda as minimal as i could and probably uninstalled a couple things i shouldnt of lol like it only installs apps with adb install and adb install -r sometimes as well as through 1mobile market which is awesome. it will not sideload anything now because through uninstalling an extra deal or two i should of, it wont allow me to enable unknown sources installation through menus. if anyone knows a way to do this through terminal of linux that would be great
thanks to any help
or would there be any way to use the water beta without the cable and only using adb or any other steps. which to my understanding is the only rom so far. thanks
If you are rooted You should I think be able to run these commands from a terminal in Linux, if you meant a terminal on your kindle then take off the and shell in the commands I list to run.
Code:
adb shell
su
reboot bootloader
I think if you are rooted it will kick it into fastboot and you can restore without a cable.
Sent from my LG-P769 using Tapatalk
thanks for the quick reply. yeah i am speaking of terminal from debian/ubuntu. I enter those commands you give me and it is recognizing the device. With adb I can even push files to install since it is screwed up and I can't access the menu part for installing from unknown sources. that is the worst part of the few issues I have with it.
after I enter those commands it only reboots normally. it doesn't go into the bootloader. I can get it to go into recovery mode where I am able to just do a normal wipe of the device but that is about it.
just to make sure I understand this. with a fastboot cable and all it is a different method from just a normal "wipe and reset" isn't it? it is using an untouched .img or something to put back to actual FACTORY as if bought from store? cause the normal wipe and factory reset doesn't put back the items I uninstalled of course from system and what not.
also is this safe to do without a factory cable. I just haven't ever needed one before and even if there is an extra step or two I don't mind instead of waiting a week for a cable.
Actually you might not even need the fastboot cable, if I remember correctly the restore method for that device would normally flash a system image that is smaller and incomplete because the system IMG is to big for fastboots 's buffer, then when it was just bootable enough to have adb push a file, it would push a amazon update file and run a command that forces the system partition to update back to stock from the update zip. So you should be able to simply push the update file for your amazon os version or older/newer and force update it. I don't have instructions handy right now for doing this and its late so maybe I post them tomorrow.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
Actually you might not even need the fastboot cable, if I remember correctly the restore method for that device would normally flash a system image that is smaller and incomplete because the system IMG is to big for fastboots 's buffer, then when it was just bootable enough to have adb push a file, it would push a amazon update file and run a command that forces the system partition to update back to stock from the update zip. So you should be able to simply push the update file for your amazon os version or older/newer and force update it. I don't have instructions handy right now for doing this and its late so maybe I post them tomorrow.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
if you could do that that'd be awesome. thanks. I just read up about a locked bootloader but I've seen it's made some progress. I just need to be sure to not turn it into a drink coaster lol.
I finally found a way to do factory reset thanks to gran pc
How to reinstall FireOS
Botched your /system partition beyond recognition? Everything is broken? Dropped your #Kindle in a sea of piss and need to RMA it? Fear not! You can just reinstall FireOS and get it looking just as if we had never touched it!
First of all, you'll have to root your tablet. I'm assuming you know how to do this!
Once that's done, put this file -- https://s3.amazonaws.com/kindle-fire-updates/update-kindle-11.3.1.0_user_310084920.bin -- in /sdcard/ (you can use adb push).
Then run these commands:
jesunoiMac:multidownload granpc$ adb shell
[email protected]:/$ su -
[email protected]:/# cp /sdcard/update-kindle-11.3.1.0_user_310084920.bin /cache/update.zip
[email protected]:/# echo --update_package=/cache/update.zip > /cache/recovery/command
[email protected]:/# exit
[email protected]:/$ exit
jesunoiMac:multidownload granpc$ adb reboot recovery
If everything went well, you should see the 'installing update' screen -- and once you're booted, we're back to stock! We did it!!!!!!
s3.amazonaws.com/kindle-fire-updates/update-kindle-11.3.1.0_user_310084920.bin
funny thing is I rerooted after the clean update and forgot all about OTA's being automatic of course. The damn thing upgraded to 11.3.2.2 which I searched has NO root exploit right now. I am wondering if I can do the same above steps to go back to 11.3.1 but that is a downgrade and I am worried about a brick although amazon new update is like an iphone you can't tell any difference haha
also is the above way how you install ICE or hellfire?
slixz85 said:
I finally found a way to do factory reset thanks to gran pc
How to reinstall FireOS
Botched your /system partition beyond recognition? Everything is broken? Dropped your #Kindle in a sea of piss and need to RMA it? Fear not! You can just reinstall FireOS and get it looking just as if we had never touched it!
First of all, you'll have to root your tablet. I'm assuming you know how to do this!
Once that's done, put this file -- https://s3.amazonaws.com/kindle-fire-updates/update-kindle-11.3.1.0_user_310084920.bin -- in /sdcard/ (you can use adb push).
Then run these commands:
jesunoiMac:multidownload granpc$ adb shell
[email protected]:/$ su -
[email protected]:/# cp /sdcard/update-kindle-11.3.1.0_user_310084920.bin /cache/update.zip
[email protected]:/# echo --update_package=/cache/update.zip > /cache/recovery/command
[email protected]:/# exit
[email protected]:/$ exit
jesunoiMac:multidownload granpc$ adb reboot recovery
If everything went well, you should see the 'installing update' screen -- and once you're booted, we're back to stock! We did it!!!!!!
s3.amazonaws.com/kindle-fire-updates/update-kindle-11.3.1.0_user_310084920.bin
funny thing is I rerooted after the clean update and forgot all about OTA's being automatic of course. The damn thing upgraded to 11.3.2.2 which I searched has NO root exploit right now. I am wondering if I can do the same above steps to go back to 11.3.1 but that is a downgrade and I am worried about a brick although amazon new update is like an iphone you can't tell any difference haha
also is the above way how you install ICE or hellfire?
Click to expand...
Click to collapse
ah good you found it before i could look it up. It will downgrade just fine, but you will probably need a fastboot cable to do it. If ICE or hellfire are roms then no, the 2013 isn't flashable with the exception of kindlewater. Since the bootloader is locked we are limited to using amazon's bootimg(kernel+intram fs).
stunts513 said:
ah good you found it before i could look it up. It will downgrade just fine, but you will probably need a fastboot cable to do it. If ICE or hellfire are roms then no, the 2013 isn't flashable with the exception of kindlewater. Since the bootloader is locked we are limited to using amazon's bootimg(kernel+intram fs).
Click to expand...
Click to collapse
ok sounds like I need to find out if putting water on this without a fastboot cable is possible then
I have ran into a bit of an odd problem due to me messing up a root and then messing my phone up even more while trying to fix it.
my phone is fully bricked and only boots into fastboot mode. i tried to fix it with the one-plus fixer (idk its official name) but i got an error 7. I now need to re flash an older version of TWRP and try a diffrent method but i cant as my phone no longer is recognized in fastboot using the ADB tool. I have the USB driver installed on Windows. On Linux i ran the .sh script as root and it still doesn't work.
I have both Ubuntu and Windows installed on my PC so i can do whatever you suggest me to do regardless of the os.
Thank you to anyone that can help in advanced
Malte
This is not a hardbrick; a hard one wouldn't boot at all and give no sign of life (except when plugged to PC).
Try an unbrick tool to revert to official OOS. On Windows 7+ remember to disable signed driver enforcement.
You mention fastboot and adb. Which one are you using?
Just to make sure: While in the bootloader (fastboot mode), adb does not work. You have to use the fastboot commands. Installing TWRP would be:
Code:
fastboot flash recovery <name-of-img-file>
If that's what you're already trying, just ignore this post.
I want to be able to do that but if i do adb devices it no longer finds my phone
Didgeridoohan said:
You mention fastboot and adb. Which one are you using?
Just to make sure: While in the bootloader (fastboot mode), adb does not work. You have to use the fastboot commands. Installing TWRP would be:
Code:
fastboot flash recovery <name-of-img-file>
If that's what you're already trying, just ignore this post.
Click to expand...
Click to collapse
I want to be able to do that but if i do "adb devices" in the cmd/terminal it no longer finds my phone. so my goal is to be able to execute that command. However, i may be mistaken that it doesnt need to find my phone i can just execute that command
Ive done this but it didnt fix my phone.
przemcio510 said:
This is not a hardbrick; a hard one wouldn't boot at all and give no sign of life (except when plugged to PC).
Try an unbrick tool to revert to official OOS. On Windows 7+ remember to disable signed driver enforcement.
Click to expand...
Click to collapse
I did this last night but it never fixed my phone. it boots and then says "md5 checksum error" so im needing to try a diffrent approach but i cant because i cant flash anything onto it due to adb not finding my device now
Bandella said:
I want to be able to do that but if i do "adb devices" in the cmd/terminal it no longer finds my phone. so my goal is to be able to execute that command. However, i may be mistaken that it doesnt need to find my phone i can just execute that command
Click to expand...
Click to collapse
Like I said, the adb commands won't work while in the booloader (that's why it's called fastboot mode). You need to use fastboot commands... The equivalent command would be:
Code:
fastboot devices
Bandella said:
I did this last night but it never fixed my phone. it boots and then says "md5 checksum error" so im needing to try a diffrent approach but i cant because i cant flash anything onto it due to adb not finding my device now
Click to expand...
Click to collapse
I had the same issues with md5, all you have to do is try a different USB port. I suggest the ones on your motherboard if you're on a PC. Then run the tool as administrator. I hope this helps, good luck!
P.S if it still doesn't work, try a different PC, I'm 100% sure it'll work
Bandella said:
I want to be able to do that but if i do "adb devices" in the cmd/terminal it no longer finds my phone. so my goal is to be able to execute that command. However, i may be mistaken that it doesnt need to find my phone i can just execute that command
Click to expand...
Click to collapse
As Didgeridoohan touched upon, adb and fastboot (while related) are different. They have different requirements and applications.
adb won't work while the device is in fastboot mode. Conversely, when the device is able to use adb, fastboot commands won't work.
adb: only works booted to OS or alternately in TWRP. Debugging must be enabled
fastboot: only works in bootloader-fastboot mode. Debugging is not required to be enabled.
For flashing TWRP, it's fastboot that you need. Well, there is a way to do it with adb, but fastboot is by far the more common way.
When in fastboot mode, adb command won't work, and there fore it is completely expected that "adb devices" yields not response. Try "fastboot devices" (no quotes) and if you get the phone's ID in response, you are in business.
Bandella said:
...
my phone ... only boots into fastboot mode...
Click to expand...
Click to collapse
I've had this happen to me when I've triggered dm-verity. Instead of getting the dm-verity warning display the phone would simply boot straight back to fastboot.
My solution was to:
- flash the latest TWRP using
Code:
fastboot flash recovery <recovery file. img>
- reboot into recovery (use the volume keys on the phone to select recovery and then press the power key)
-flash the full stock image I was using before the problem started
This would clean up any changes made to the boot and system images and allow me to boot the system normally.
Note: because this leaves you with a stock kernel you'll end up with the stock recovery after you boot the system.
Sent from my OnePlus3T using XDA Labs
boot your PC into Ubuntu and install adb/fastboot (tons of guides available off the 'net). then boot your 3t to dl mode and connect it to your PC. as mentioned already "fastboot devices" should list your 3t and you should now be able to flash to your heart's content. no need for drivers, unlike under Windows. i have a bootable linux usb drive primarily for this reason. curious what script you're trying to run though..