Related
So im got this gnex borked an I am rtying to fix it. So far i have tried every known method(usb jig,toolkit,omap flasher, fastboot) basically everything in the book.
The phone itself will not boot up except by running omap flasher. When running omap flasher I can boot up into fastboot via plugging it in and holding all buttons. In fastboot the volume keys do not work. If I start off by trying to flash a bootloader it gets stuck at writing bootloader. If I try to flash a recovery it will say unknown partition. The jig does not force it into download mode.
Please advise me on what other steps to try.
Thanks in Advance.
just a little update I am able to boot into cwm by using fastboot boot command this allowed me to have a window into adb. I am not able to mount tanything in cwm including sdcard and /sytstem
I checked the partitions to see if they are O.K. and you can see the result in the attached pic
i tried the fastboot boot bl.img and it made it hang at the google screen with padlock
i think you should try ot flash a factory image , if you cant do this via adb , use some toolkit ,,,
khuzema9 said:
i think you should try ot flash a factory image , if you cant do this via adb , use some toolkit ,,,
Click to expand...
Click to collapse
If i do that It gets stuck at writing bootloader.
If you had a backup saved, it would have been easy.
Edit: Sounds like the sys permission might have been changed or something you installed could have altered the bootloader.
yalkowni said:
If i do that It gets stuck at writing bootloader.
Click to expand...
Click to collapse
Try
Code:
fastboot format bootloader
before flashing?
It does look like your partitions are derped. There should be A LOT MORE partitions to show. Hopefully partition info is still there, so you might as well use fastboot to format everything else (recovery, userdata, system).
---------- Post added at 04:15 PM ---------- Previous post was at 04:10 PM ----------
yalkowni said:
i tried the fastboot boot bl.img and it made it hang at the google screen with padlock
Click to expand...
Click to collapse
Code:
fastboot boot
is only for booting kernels, so that obviously doesn't work.
Actually i use fastboot boot to boot clockworkmod... So it works for recoveries too.
And i agree that the partitions do not look right.
Would you fastboot flash bootloader?
Yeah. Get a bootloader from the factory image.
You can use fastboot commands right? Format every partition you can think of, except for bootloader. (system, userdata, recovery, boot)
Then flash a bootloader.
This may screw up further, but I can't think of anything else, so if all else fails, then go crazy and format bootloader? What modes can you get into and how?
I thank you guys a lot for helping me out. I will try your suggestions in an hour and report back here.
formatatitng any partition comes back in error with unknown partition.
formatitng bootloader comes back in
yalkowni said:
formatatitng any partition comes back in error with unknown partition.
formatitng bootloader comes back in
Click to expand...
Click to collapse
Sheesh...you got no partition info, so fastboot can make them.
Your NAND is pretty well fried I guess.
It might be time to get a replacement.
I don't know how it might be possible to repartition with having a partition info table. Mayyybe somehow you can get the partition info and have the whole internal storage mounted on your desktop, but that doesn't seem possible.
gnustomp said:
Sheesh...you got no partition info, so fastboot can make them.
Your NAND is pretty well fried I guess.
It might be time to get a replacement.
I don't know how it might be possible to repartition with having a partition info table. Mayyybe somehow you can get the partition info and have the whole internal storage mounted on your desktop, but that doesn't seem possible.
Click to expand...
Click to collapse
Anyway I can rewrite the partition table somehow ?
yalkowni said:
Anyway I can rewrite the partition table somehow ?
Click to expand...
Click to collapse
if u can go into download mode then see my signature for odin firmware (pit file re-partition table + bootloader)
samersh72 said:
if u can go into download mode then see my signature for odin firmware (pit file re-partition table + bootloader)
Click to expand...
Click to collapse
is there any command via adb or fastboot cammands that corces it into download mode?
I havent found a command, but i believe it is to power up via power+volume down..
yalkowni said:
is there any command via adb or fastboot cammands that corces it into download mode?
Click to expand...
Click to collapse
I don't even know how to get into download mode. Is it even there?
Sent from my Nexus 7 using Tapatalk HD
yalkowni said:
is there any command via adb or fastboot cammands that corces it into download mode?
Click to expand...
Click to collapse
Press and hold volume down + power button . or use a USB jig if u have one. Unfortunately, there is no adb or fastboot command for Odin mode
Sent from my Galaxy Nexus using xda premium
Good time of the day to everyone. I have the problem with my Kindle Fire first gen. Please tell me the solution If someone knows. First was the problem with picture on the screen then I changed the controller of LVDS and then image became normal. But first I thought that this problem is software and though I almost didn't see nothing on the screen I tried to solve the problem in TWRP. When display started to show good picture I did see that tablet do not boot on. So now I can start TWRP recovery but in the log I see that tablet cannot mount sd-card. This is half of the proble. I saw the solution on this forum how to mount by ADB and some command from command line. But the computer also do not see the tablet. The tablet shoes in device manager just from the begining of the booting for about 2 sec. And I cannot do something. Is there any solution in this situation?
Ichigo said:
You can't mount? Take a look at this: http://forum.xda-developers.com/showthread.php?t=1949372
Click to expand...
Click to collapse
Thanks, I will. The problem is that I cannot do any adb which needs that tablet is connected to computer and recognized. My computer see thee tablet only in the time of booting in the begining.
One question, is it possible to write all commands wich I see in instractions for unbricking kindle in native terminal of the TWRP?
Is it possible to solve the problem with "can't mount /sdcard (invalid argument)" from TWRP itself without ADB, I mean computer. Then I could
make some BAT file wich will handle connection with KF in the begining of booting and write update.zip to sdcard on the tablet, then I could
to flash it.
Please help! I can PAY for the real help by PayPal.
toly084 said:
One question, is it possible to write all commands wich I see in instractions for unbricking kindle in native terminal of the TWRP?
Is it possible to solve the problem with "can't mount /sdcard (invalid argument)" from TWRP itself without ADB, I mean computer. Then I could
make some BAT file wich will handle connection with KF in the begining of booting and write update.zip to sdcard on the tablet, then I could
to flash it.
Please help! I can PAY for the real help by PayPal.
Click to expand...
Click to collapse
Here`s your answer http://forum.xda-developers.com/showthread.php?t=1850038 a live usb with soupkit. If you want help and you can catch me online I would be happy to assist and it wont cost you a dime just time.
Thepooch said:
Here`s your answer http://forum.xda-developers.com/showthread.php?t=1850038 a live usb with soupkit. If you want help and you can catch me online I would be happy to assist and it wont cost you a dime just time.
Click to expand...
Click to collapse
Thank you very much. I see that Soupkit is just what I needed. First I need to install Ubuntu, then will try to recover my KF wich I made two of them not working. I hope one will work. I thought I have no luck and only way to reball a flash from another board of KF wich I have as spare.
Thepooch said:
If you want help and you can catch me online I would be happy to assist and it wont cost you a dime just time.
Click to expand...
Click to collapse
Dear Sir. So, I tried SoupKit. The same situation as with ADB in Windows. My KF can be seen just in the begining of the booting.
And this is not enaugh time to do something. Also I wanted to ask that man wich made SoupKit, but for now it is not allowed for me to pos there.
toly084 said:
Dear Sir. So, I tried SoupKit. The same situation as with ADB in Windows. My KF can be seen just in the begining of the booting.
And this is not enaugh time to do something. Also I wanted to ask that man wich made SoupKit, but for now it is not allowed for me to pos there.
Click to expand...
Click to collapse
Boot into recovery and see if your computer will detect it.
soupmagnet said:
Boot into recovery and see if your computer will detect it.
Click to expand...
Click to collapse
Thank you for the answer, I tried to post in your theme but it wasn't allowed.
The computer see my KF only in the begining of the booting 2-3 sec. I also tried your SoupKit in the Ubuntu, the same problem,
I just can flash bootloader, recovery and that's all.
toly084 said:
Thank you for the answer, I tried to post in your theme but it wasn't allowed.
The computer see my KF only in the begining of the booting 2-3 sec. I also tried your SoupKit in the Ubuntu, the same problem,
I just can flash bootloader, recovery and that's all.
Click to expand...
Click to collapse
Okay, boot into Ubuntu, let the device boot up normally and enter the following in the terminal...
Code:
lsusb
Let me know what the output is
soupmagnet said:
Okay, boot into Ubuntu, let the device boot up normally and enter the following in the terminal...
Code:
lsusb
Let me know what the output is
Click to expand...
Click to collapse
I'm sorry, but I can't do this right now. Notebook on wich I installed Ubuntu I left on the work and tablet also. Tomorrow I will try to do so. I will explain what happened. First I had a problem with picture on the screen, I hardly could see what is on the screen. I thought it was the software problem and try in the recovery to solve the problem. But as I couldn't see what I do, I done something what bricked my KF. The problem with picture was solved by reballing the LVDS controller. And now I have a tablet wich cannot mount system, data, sdcard what I saw in log of TWRP. And also tablet can't be seen now by computer as it was and I cannot recover tablet by ADB. I also asked before if is it possible to do something in TWRP in terminal that to solve the problem with mount of partitions.
toly084 said:
I'm sorry, but I can't do this right now. Notebook on wich I installed Ubuntu I left on the work and tablet also. Tomorrow I will try to do so. I will explain what happened. First I had a problem with picture on the screen, I hardly could see what is on the screen. I thought it was the software problem and try in the recovery to solve the problem. But as I couldn't see what I do, I done something what bricked my KF. The problem with picture was solved by reballing the LVDS controller. And now I have a tablet wich cannot mount system, data, sdcard what I saw in log of TWRP. And also tablet can't be seen now by computer as it was and I cannot recover tablet by ADB. I also asked before if is it possible to do something in TWRP in terminal that to solve the problem with mount of partitions.
Click to expand...
Click to collapse
First we need to see if Linux is detecting your device when plugged into USB, hence the 'lsusb' command. We need to get the communication problem resolved before you can fix your mounting issues. As far as using TWRP's command line to fix the partitions, not likely. I've tried it before and it didn't work out.
It's possible, for whatever reason, your device is reporting a different product ID than what is configured in the udev rules, but we probably won't know for sure until we have access to 'lsusb'.
soupmagnet said:
First we need to see if Linux is detecting your device when plugged into USB, hence the 'lsusb' command. We need to get the communication problem resolved before you can fix your mounting issues. As far as using TWRP's command line to fix the partitions, not likely. I've tried it before and it didn't work out.
It's possible, for whatever reason, your device is reporting a different product ID than what is configured in the udev rules, but we probably won't know for sure until we have access to 'lsusb'.
Click to expand...
Click to collapse
Tomorrow I will try "lsusb" and will write an answer.
toly084 said:
Tomorrow I will try "lsusb" and will write an answer.
Click to expand...
Click to collapse
Good time of the day. As I thought computer do not see the device.
But now I can remain in fastboot mode by the comman "fastboot getvar product". And SoupKit see the device in fastboot. Is it possible somehow to transfer the firmware file to the KF?
toly084 said:
Good time of the day. As I thought computer do not see the device.
But now I can remain in fastboot mode by the comman "fastboot getvar product". And SoupKit see the device in fastboot. Is it possible somehow to transfer the firmware file to the KF?
Click to expand...
Click to collapse
If SoupKit sees the device in fastboot as you say, use it to install recovery and boot into it
soupmagnet said:
If SoupKit sees the device in fastboot as you say, use it to install recovery and boot into it
Click to expand...
Click to collapse
I have FFF booty v1.4a installed and TWRP recovery installed.
I think because of the problem of the mounting of sdcard / system / data computer do not see the device.
toly084 said:
I have FFF booty v1.4a installed and TWRP recovery installed.
I think because of the problem of the mounting of sdcard / system / data computer do not see the device.
Click to expand...
Click to collapse
Use fastboot to reinstall TWRP and check 'lsusb' again.
soupmagnet said:
Use fastboot to reinstall TWRP and check 'lsusb' again.
Click to expand...
Click to collapse
By the help of your instructions from the another post about mounting of SYSTEM DATA CACHE and SDCARD,
now all partition can be mounted only SDCARD won't. But computer as it was before do not see device in normal mode,
just in fastboot. All work concirning mounting SYSTEM DATA CACHE was made from the terminal of TWRP.
soupmagnet said:
Okay, boot into Ubuntu, let the device boot up normally and enter the following in the terminal...
Code:
lsusb
Let me know what the output is
Click to expand...
Click to collapse
In the list there is no the device. Only standart wich belongs for notebook hardware. If I could mount sdcard then I could flash update.zip from fastboot, but I can't.
toly084 said:
By the help of your instructions from the another post about mounting of SYSTEM DATA CACHE and SDCARD,
now all partition can be mounted only SDCARD won't. But computer as it was before do not see device in normal mode,
just in fastboot. All work concirning mounting SYSTEM DATA CACHE was made from the terminal of TWRP.
Click to expand...
Click to collapse
Your mounting issues shouldn't have anything to do with whether or not Linux will detect your device. Are you using a LiveUSB, VM, or full Linux boot?
soupmagnet said:
Your mounting issues shouldn't have anything to do with whether or not Linux will detect your device. Are you using a LiveUSB, VM, or full Linux boot?
Click to expand...
Click to collapse
I installed full Ubuntu. I do not know why tablet can't be seen in linux.
Well, Long story short, I flashed Freedom OS on my Oneplus 3 and things went poorly. I set up a passcode and when my device booted, the passcode was somehow changed to one other than what I had put. Not only that, I seem to have no recovery on my device either. Basically I can boot into my lockscreen where I'm basically screwed, and I can mess with fastboot but I'm unable to flash a rom, twrp wont flash either. Please help, will do anything.
bparisi15 said:
Well, Long story short, I flashed Freedom OS on my Oneplus 3 and things went poorly. I set up a passcode and when my device booted, the passcode was somehow changed to one other than what I had put. Not only that, I seem to have no recovery on my device either. Basically I can boot into my lockscreen where I'm basically screwed, and I can mess with fastboot but I'm unable to flash a rom, twrp wont flash either. Please help, will do anything.
Click to expand...
Click to collapse
Did you try the mega unbrick guide ? http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
bparisi15 said:
Well, Long story short, I flashed Freedom OS on my Oneplus 3 and things went poorly. I set up a passcode and when my device booted, the passcode was somehow changed to one other than what I had put. Not only that, I seem to have no recovery on my device either. Basically I can boot into my lockscreen where I'm basically screwed, and I can mess with fastboot but I'm unable to flash a rom, twrp wont flash either. Please help, will do anything.
Click to expand...
Click to collapse
Recovery:
I assume you are on FreedomOS CE, have you flash the recovery who's recommended for the CE version?
If no, read the op: http://forum.xda-developers.com/oneplus-3/development/rom-freedomos-ce-1-7-t3470660
and use this command in fastboot:
Code:
fastboot flash recovery twrp-3.0.2-19-oneplus3.img
Lockscreen / data:
Because you have set a passcode at the booting time (not the basic lockscreen).
You can't restore all your data, because all the partition is now encrypted, the only way to access to that is to use the passcode.
The only way to fix that is to format your data partition in fastboot (not twrp).
Code:
fastboot format userdata
NevaX1 said:
Recovery:
I assume you are on FreedomOS CE, have you flash the recovery who's recommended for the CE version?
If no, read the op: http://forum.xda-developers.com/oneplus-3/development/rom-freedomos-ce-1-7-t3470660
and use this command in fastboot:
Code:
fastboot flash recovery twrp-3.0.2-19-oneplus3.img
Lockscreen / data:
Because you have set a passcode at the booting time (not the basic lockscreen).
You can't restore all your data, because all the partition is now encrypted, the only way to access to that is to use the passcode.
The only way to fix that is to format your data partition in fastboot (not twrp).
Code:
fastboot format userdata
Click to expand...
Click to collapse
THANK YOU SO MUCH! The data format completely fixed it for me, thank you so much!
I have rooted my OP3 and manually updated to 3.2.6 O2 os,but unfortunately device get unrooted and no custom recovery is there.But now i want to root and install custom recovery but Facing problem with ADB Interface Device can't be detected in Fastboot mode????please help me out.
Hi,
i broke my screen complete. All i see are artifacts.
I have TWRP, system start but all i can use is the CLI. How can i delete my phone complete and safe? Is it safe via "find my phone" from Google Website or is there any other command to do this? Is the any Java-All-in-Onetools i can use?
Regards and thanks
if you have twrp installed i assume your bootloader is unlocked, turn on your phone and use volume buttons to boot into fastboot, connect your phone to pc, fire up fastboot/adb type in fastboot format userdata
ach3fck said:
if you have twrp installed i assume your bootloader is unlocked, turn on your phone and use volume buttons to boot into fastboot, connect your phone to pc, fire up fastboot/adb type in fastboot format userdata
Click to expand...
Click to collapse
OK. Sound like a plan.
What if i use the tool seen in the screenshot? There is a point to decrypt and format. Yes, i will search myself - how can i encrypt it again?
On an older phone I used TWRP recovery. That has a brilliant option to create system backups.
How to do that in the LineageOs recovery?
I want to clone one phone to another identical phone. I hope that can be done by creating a backup on phone 1 and install it from recovery on the other. Hopefully including the OS (with all the setting that take hours of fiddling about), apps and data.
Just use twrp..?
PhotonIce said:
Just use twrp..?
Click to expand...
Click to collapse
But fom what I understand the TWRP-backup is only the system, not the apps and data.
In the install instructions for lineageOs, the lineageOs recovery is used. So I followed the instructions exactly. Just surprised there is no backup option.
carsten888 said:
But fom what I understand the TWRP-backup is only the system, not the apps and data.
In the install instructions for lineageOs, the lineageOs recovery is used. So I followed the instructions exactly. Just surprised there is no backup option.
Click to expand...
Click to collapse
Obliviously no, twrp backup include everything. I use twrp and when I have to install new lineage os update I boot lineage recovery from fastboot and keep internal recovery as twrp
carsten888 said:
But fom what I understand the TWRP-backup is only the system, not the apps and data.
In the install instructions for lineageOs, the lineageOs recovery is used. So I followed the instructions exactly. Just surprised there is no backup option.
Click to expand...
Click to collapse
Use twrp backup and select all the partitions. It'll back up everything.
Apps and settings are located in the data partition and other files/data is located in the internal storage partition. boot is the kernel, recovery is the recovery and system in the system image.
If you know what you're doing you could even install a fresh copy of lineage onto another phone and just restore the data and internal storage partitions, and still receive an exact copy of the phone you backup up from while using less space in the backup.
... An additional question. I apologize if my n00b question should be something I already know. However, I briefly had twrp on my device and then I flashed lineageOS and magisk on slot b and of course it switched to boot from slot b. Since then, I have not been able to access twrp as it is located on slot a. When I boot into recovery, it brings me automatically to lineageOS recovery. How would I access twrp once again?
Paul_Neocube said:
... An additional question. I apologize if my n00b question should be something I already know. However, I briefly had twrp on my device and then I flashed lineageOS and magisk on slot b and of course it switched to boot from slot b. Since then, I have not been able to access twrp as it is located on slot a. When I boot into recovery, it brings me automatically to lineageOS recovery. How would I access twrp once again?
Click to expand...
Click to collapse
Not sure what you mean by slot A and B, but just try flashing twrp again, it should override lineage recovery.
PhotonIce said:
Not sure what you mean by slot A and B, but just try flashing twrp again, it should override lineage recovery.
Click to expand...
Click to collapse
On my device there are two slots... A and B. Like two separate partitions that van have software installed to. When I installed my rom I first installed twrp to slot a and then my Tom to slot b which is what runs now when I power on my device. I can't install twrp to the slot my os is on as I would have issues with the os recovery that is on that slot.
Skorpion96 said:
Obliviously no, twrp backup include everything. I use twrp and when I have to install new lineage os update I boot lineage recovery from fastboot and keep internal recovery as twrp
Click to expand...
Click to collapse
Could you please explain (or link to instructions) how did you manage to have two different recoveries (TWRP and LOS) in the same phone? I would've thought that was not possible.
zogoibi said:
Could you please explain (or link to instructions) how did you manage to have two different recoveries (TWRP and LOS) in the same phone? I would've thought that was not possible.
Click to expand...
Click to collapse
It's not. He keeps LineageOS recovery on the phone, and when he wants to use TWRP, he connects the phone to his computer via USB and runs fastboot boot twrp.img from the command line. This reboots the phone and loads TWRP into memory without flashing it to the phone.
@MJPollard Wow!! That's a very intersting trick! thanks a lot. I'll take that down as it seems darn useful. Just one question: the "alternative" recovery .img file should be in my computer, or previously copied to the phone?
zogoibi said:
@MJPollard Wow!! That's a very intersting trick! thanks a lot. I'll take that down as it seems darn useful. Just one question: the "alternative" recovery .img file should be in my computer, or previously copied to the phone?
Click to expand...
Click to collapse
actually i done the reverse, i have twrp installed and when i want to run lineage recovery i boot it with fastboot boot "recovery.img"
Thanks. Yes, I've realized that. Still, my question remains unanswered: In order to boot via fastboot, should the alternative recovery's .img file reside in the computer or in the phone? I presume the former, but I'm not sure.
zogoibi said:
Thanks. Yes, I've realized that. Still, my question remains unanswered: In order to boot via fastboot, should the alternative recovery's .img file reside in the computer or in the phone? I presume the former, but I'm not sure.
Click to expand...
Click to collapse
You ever flashed TWRP via cmd (adb) on a pc? It's the same thing but you use fastboot flash rather than fastboot boot. When you flash twrp on phone, you put the recovery.img file in your adb folder, if I'm not mistaken. The same thing goes for booting an .img file (it goes in the adb directory/folder in your pc).
zogoibi said:
Thanks. Yes, I've realized that. Still, my question remains unanswered: In order to boot via fastboot, should the alternative recovery's .img file reside in the computer or in the phone? I presume the former, but I'm not sure.
Click to expand...
Click to collapse
The alternate recovery should remain on the computer. It can be in the same folder as adb and fastboot for easy access (it doesn't need to be there, it's just easier that way). That way, all you need to do is reboot the device into fastboot mode, connect it to the computer via USB, and run fastboot boot twrp.img (or whatever it's named). The original recovery will remain untouched on the phone while the alternate recovery runs in memory.
MJPollard said:
That way, all you need to do is reboot the device into fastboot mode, connect it to the computer via USB, and run fastboot boot twrp.img (or whatever it's named). The original recovery will remain untouched on the phone while the alternate recovery runs in memory.
Click to expand...
Click to collapse
Thank you. I know this question is a bit off topic, but when I try to run that command (with the phone in fastboot mode), it fails:
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.611s]
booting...
FAILED (remote: Unrecognized command boot)
Do you have an idea of why is that? My device's recovery is LOS's, and the recovery I try to run from the computer is TWRP.
zogoibi said:
Thank you. I know this question is a bit off topic, but when I try to run that command (with the phone in fastboot mode), it fails:
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.611s]
booting...
FAILED (remote: Unrecognized command boot)
Do you have an idea of why is that? My device's recovery is LOS's, and the recovery I try to run from the computer is TWRP.
Click to expand...
Click to collapse
Try fastboot boot recovery twrp.img. I don't normally do this so I might have misremembered it. If it works, I'll edit my post so that others don't get confused.
Nope, it didn't work. The first command you told me is the correct one (I've checked that on the fastboot manual), but it fails on my device. Maybe there is some incompatibility between LOS recovery's fastboot mode and the TWRP I am trying to run. I won't insist, as this is not the thread for such an issue. I will try to find some information somewhere else. Thank you all the same for trying to help!
zogoibi said:
Nope, it didn't work. The first command you told me is the correct one (I've checked that on the fastboot manual), but it fails on my device. Maybe there is some incompatibility between LOS recovery's fastboot mode and the TWRP I am trying to run. I won't insist, as this is not the thread for such an issue. I will try to find some information somewhere else. Thank you all the same for trying to help!
Click to expand...
Click to collapse
have you found a solution for this? I m also having same trouble lineage os 20. I wanna use TWRP to make backup of whole rom.
agamemnonn said:
have you found a solution for this? I m also having same trouble lineage os 20. I wanna use TWRP to make backup of whole rom.
Click to expand...
Click to collapse
I found out that it's not possible. LOS Recovery's fastboot mode has that command disabled.