Hello all
I have installed the paranoid android 3+ rom but now I cannot access TWRP or the bootloader screen. Android boots normally and the tablet is perfectly functional. When the tablet is off, there is no way to get to TWRP using the keys (power on with Vol- pressed etc. I have used all possible combinations). Also, there is no option to boot into recovery mode from the menu in "Backup & reset". Also, when I try to boot into recovery through a terminal emulator it again boots into andoid normally as if I just did a normal reboot. The "reboot recovery" command issued from the terminal emulator does not boot into TWRP. Trying to boot into recovery mode from within Phoenix Suite again boots the machine normally rather than in recovery mode. It's driving me nuts. Could it be a corrupt/locked bootloader? Is it something else? It seems to me that the only possible path for the bootloader is to load Android.
Is there any way to blind flash the bootloader again? It seems that this is the culprit since I can copy TWRP to nandg through the terminal emulator ("cat /extsd/recovery.img > /dev/block/nandg; sync; sync ;sync" but then again rebooting goes into android rather than recovery mode. Could there be a similar solution like "cat /extsd/boot.img > /dev/block/nanda" for example?).
The tablet connects normally through USB to my PC and adb sees it properly.
Any ideas?
Thanks in advance
Nobody?
Try it via adb.
Command: adb reboot bootloader
It works for me.
Sent from my PC36100
merden765 said:
Try it via adb.
Command: adb reboot bootloader
It works for me.
Sent from my PC36100
Click to expand...
Click to collapse
Whatever I tried it does not boot into the bootloader, be it adb, Phoenix suite, or the terminal emulator. Is there any way to write the original booloader raw to the respective nand partition? And where can I get the original bootloader?
tzoykas said:
Whatever I tried it does not boot into the bootloader, be it adb, Phoenix suite, or the terminal emulator. Is there any way to write the original booloader raw to the respective nand partition? And where can I get the original bootloader?
Click to expand...
Click to collapse
I have same your problem and now i use goomanager this app can bring you to recovery mode or install in to your tablet.
Related
I have a cell phone which name is Huawei Ascend P1. Now I have a problem, that is the devices can not bootup into Android's home and I can not write anything into flash, even using fastboot.
When booting, the screen stays on the welcome logo, and stay there forever, and adb could connect to linux shell on the phone. I can see all file on the phone, and I can save files after "mount -o remount / /", but after reboot, the file is gone.
If I use fastboot to flash a recovery into my phone, by follow command:
fastboot flash recovery recovery.img
The command line prompt says OK, but when it reboots, it still reboot into the previous recovery.
Who hnows why this happens? And how can I resolve this problem?
Is there anyone who can help me?
mikewootc said:
I have a cell phone which name is Huawei Ascend P1. Now I have a problem, that is the devices can not bootup into Android's home and I can not write anything into flash, even using fastboot.
When booting, the screen stays on the welcome logo, and stay there forever, and adb could connect to linux shell on the phone. I can see all file on the phone, and I can save files after "mount -o remount / /", but after reboot, the file is gone.
If I use fastboot to flash a recovery into my phone, by follow command:
fastboot flash recovery recovery.img
The command line prompt says OK, but when it reboots, it still reboot into the previous recovery.
Who hnows why this happens? And how can I resolve this problem?
Click to expand...
Click to collapse
Is there anyone who can help me?
I had try to upgrade firmware with my pc
Solo1977 said:
Dear sir, you should try to connect pc with you phone and upgrade firmware
Also you can modify phone settings, swap positions for flash memory and external sd card
Click to expand...
Click to collapse
First of all,
I have tried to connect pc with my phone by fastboot. And I have tried to flash the original version of recovery by using command:
fastboot flash recovery recovery.img
And it says success, but when I reboot the phone, it still boot into the old version recovery(which is 3rd party version).
Secendly,
I have tried to upgrade firmware from SD card, and it tell me success and no effect when reboot.
Is there anything I can do else?
Hello I am going in circles trying to get my phone back up and running. It can only load into twrp or recovery and i have a custom rom i am trying to flash because accidentally erased the whole phone alongside the operating system. Now no matter what i do i try to run adb devices in the command prompt and shows device not found....unsure what to do at this point fasboot devices clearly shows it...any ideaS?
Tommyboy77 said:
Hello I am going in circles trying to get my phone back up and running. It can only load into twrp or recovery and i have a custom rom i am trying to flash because accidentally erased the whole phone alongside the operating system. Now no matter what i do i try to run adb devices in the command prompt and shows device not found....unsure what to do at this point fasboot devices clearly shows it...any ideaS?
Click to expand...
Click to collapse
If you can do "fastboot devices" then that means you are either in bootloader or fastboot mode. If that is the case, then "adb devices" would not find your device because it's not in the correct mode to be able to do so. You can access your phone with adb when it's either booted or most recoveries, but fastboot/bootloader mode is only for fastboot commands. Without knowing what phone you have and what update it is / was on, I can't really provide any more direct help. But typically there is a way to reload the OS via fastboot on most devices such as HTCs, Motorolas, and Nexus devices, to name a few.
es0tericcha0s said:
If you can do "fastboot devices" then that means you are either in bootloader or fastboot mode. If that is the case, then "adb devices" would not find your device because it's not in the correct mode to be able to do so. You can access your phone with adb when it's either booted or most recoveries, but fastboot/bootloader mode is only for fastboot commands. Without knowing what phone you have and what update it is / was on, I can't really provide any more direct help. But typically there is a way to reload the OS via fastboot on most devices such as HTCs, Motorolas, and Nexus devices, to name a few.
Click to expand...
Click to collapse
adb devces does not work in clockwork mod either.....what is the easiest way to get this custom rom sent to my internal sd card if the phone wont boot up and os is wiped off the phone? it is an htc one...
adb should work in CWM... You might have to manually load the driver. Even if every driver works when the phone is booted and all, Windows can still have issues finding the right one in recovery. Check in your device manager. If that doesn't work, then you'll have to see if your recovery supports USB OTG and see if you can load like that. If none of that works, you'll have to reload the OS via RUU and start over with root/recovery/etc.
Mount USB and copy it from your PC to the phone or do sideload.
Sent from my GT-I9505G using xda app-developers app
C13v3r0n3 said:
Mount USB and copy it from your PC to the phone or do sideload.
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
Neither of those things are options for the OP. He can't boot, so he can't mount USB (mounting USB in recovery hasn't worked for most phones since JB where most phones don't support USB mount - only MTP) and he can't sideload because he hasn't been able to get ADB working.
His options now are:
Find out why the adb driver isn't loading so he can just adb commands to push the file or sideload
USB OTG
Return to stock via RUU
So recently, I downgraded to 13.3.1.0, and installed Safestrap (not the one for later versions). However, after restarting and adding a ROM slot, it wouldn't let me do anything with stock.
I restored stock, but still nothing.
The odd thing is, whenever I press the power button, it will still make noise.
I can access fastboot, Safestrap, and the default recovery.
What do I do?
Bump, need help ASAP
Alex311360 said:
So recently, I downgraded to 13.3.1.0, and installed Safestrap (not the one for later versions). However, after restarting and adding a ROM slot, it wouldn't let me do anything with stock.
I restored stock, but still nothing.
The odd thing is, whenever I press the power button, it will still make noise.
I can access fastboot, Safestrap, and the default recovery.
What do I do?
Click to expand...
Click to collapse
If you can enter safestrap recovery, check if you can establish adb access:
so enter safestrap and connect kindle to your pc or laptop. Then start cmd window or terminal if you using linux, and try:
adb devices
it should return:
list of devices attached
xxxxxxxxx recovery
if you can achieve that your kindle in safestrap recovery is recognized by win/linux, you can try this:
1. Download this 13.3.1.0 (Kindle HDX 7") update - pure amazon FireOS so OTA updates enabled - do not connect to wifi/register your kindle if you want root and use of custom recovery after flashing this
A. Now, since I am not expert for adb installing pushing repairing etc., read this thread [HOWTO] Unbrick your device
B. If that for whatever reason wont work, you can try sideload update-kindle-13.3.1.0_user_310079820.bin (rename .bin to .zip before sideloading) through safestrap recovery, but because Safestrap is only TWRP "based", I cant guarantee that this will work either (it should, but this is one way ticket, your working safestrap recovery will be destroyed in the process of update and if things dont go as they should, your kindle is bricked for good):
0. connect kindle to pc/laptop
1. enter Safestrap, tap Advanced -> ADB Sideload -> Swipe slider to start Sideload
2. on pc/laptop open cmd/terminal, type adb devices, you should see:
List of devices attached
XXXXXXXXXXXXXXXX sideload
3. type adb sideload update-kindle-13.3.1.0_user_310079820.zip
4. You will see a progress bar in the command prompt indicating that the Zip file is being copied to the device. Once the file is transferred, the Zip is automatically installed on your device.
OK fingers crossed, I hope something will work, but things can go wrong, so it is up to you if you try this or not ...
On a scale of 1 to worse, what happens if ADB sideload refuses to work? It just freezes at starting and does nothing afterwards, and I have to cancel.
Alex311360 said:
On a scale of 1 to worse, what happens if ADB sideload refuses to work? It just freezes at starting and does nothing afterwards, and I have to cancel.
Click to expand...
Click to collapse
You can also try to unlock your bootloader (since you have compatible FW) and proceed to flash cuber signed recovery (TWRP 2.8.5.0) through fastboot and then from TWRP you can do necessary steps to recover your kindle quite easily - if you are familiar with TWRP flashing...
Regarding sideloading I honestly dont know how it will react - never try it - it was developed exactly for quick system recovery, but you must be flashing 100% working rom ...
Personaly I would go for bootloader unlock and then flash TWRP 2.8.5.0 from which sideloading feature (If you want use that) must working... :good:
Do you require a factory fastboot cable for that?
Alex311360 said:
Do you require a factory fastboot cable for that?
Click to expand...
Click to collapse
No, standart USB cable is enough.
Can you give me a link on how to do this? I know I'm sounding very noobish, but I'm a tad new to this.
Alex311360 said:
Can you give me a link on how to do this? I know I'm sounding very noobish, but I'm a tad new to this.
Click to expand...
Click to collapse
Sure, here is original post from dpeddi.
... and here is how to for windows ... :good:
Hey, sorry it's taken me so long to reply. Was busy with school.
For some reason it won't connect to the device in fastboot, it just says "waiting for device", even the Kindle says "Ready." and does nothing.
What do I do?
Alex311360 said:
Hey, sorry it's taken me so long to reply. Was busy with school.
For some reason it won't connect to the device in fastboot, it just says "waiting for device", even the Kindle says "Ready." and does nothing.
What do I do?
Click to expand...
Click to collapse
If your OS is Windows 7, you can try install these drivers and then try again.
jeryll said:
If your OS is Windows 7, you can try install these drivers and then try again.
Click to expand...
Click to collapse
Still no dice. Doing fastboot devices or adb devices brings up nothing.
Please note I have done the following things:
- did a kindle fire system restore with safestrap restore still installed
- adb sideload doesn't work in safestrap
- fastboot drivers used installed does nothing
Still stuck.
Alex311360 said:
Still no dice. Doing fastboot devices or adb devices brings up nothing.
Please note I have done the following things:
- did a kindle fire system restore with safestrap restore still installed
- adb sideload doesn't work in safestrap
- fastboot drivers used installed does nothing
Still stuck.
Click to expand...
Click to collapse
On which FW you were before downgrading to 13.3.1.0?
Weird thing with windows and these drivers is it sometimes command fastboot -i 0x1949 devices does nothing, while actually direct commands like
fastboot -i 0x1949 getvar product
fastboot -i 0x1949 getvar version
fastboot -i 0x1949 getvar kernel
works as expected...
Anyway to restore system on your kindle you need working connection between kindle and PC/laptop, so you can use adb commands to restore your system, or after bootloader unlock, you can use fastboot commands to flash required/missing components. I have tested while in safestrap kindle is recognizable by adb devices, if you can achieve that, you can continue with how to unbrick thread I posted before.
You can also learn how to install/use Linux, where adb and fastboot device recognition/commands works 100%...
I must leave for work now ...
So, some kind of miracle happened, and I found the source of the problem.
Upon trying to update to 13.3.2.4, it reboots the phone instead of installing it. I try booting into Safestrap, and it does Open Recovery Script, causing it to boot to a black screen upon booting to the actual thing.
I don't know how to fix Open Recovery Script doing that, but all I had to do to get it back to normal was reflash the 13.3.1.0 amazon OS onto stock.
I have the XT1022 Moto E model. I recently upgraded from Kitkat 4.4.4 to Lollipop 5.0.2 using an Indian retail version of the stock ROM (Condor retail version) and the adb sideload method on Ubuntu 14.04. The Lollipop update is working in excellent condition. However, I wanted to try the Paranoid Android ROM and tried to enter into the recovery mode for trying out the adb sideload method. However, what I found was that I cannot enter the recovery mode. I was able to do so for a few times after I installed the Lollipop update, but then I suddenly stopped being able to do so. The method I had been following was Power+Volume Down for 5 sec to enter the bootloader, select the recovery option, and press volume up for 15-20 sec and press and release the power key while holding down the volume up button.
I though that I might have wiped the stock recovery during the upgrade, so I wanted to unlock bootloader and install a TWRP custom recovery. However, I was unable to unlock the bootloader, as I am unable to connect fastboot mode in Ubuntu when the phone is in the bootloader/fastboot mode ($ fastboot devices command in Ubuntu terminal window showed no devices. When phone is on, $ adb devices shows that my phone is connected. Also, USB debugging is on).
Can anyone help me with this issue?
rajiiv00 said:
I have the XT1022 Moto E model. I recently upgraded from Kitkat 4.4.4 to Lollipop 5.0.2 using an Indian retail version of the stock ROM (Condor retail version) and the adb sideload method on Ubuntu 14.04. The Lollipop update is working in excellent condition. However, I wanted to try the Paranoid Android ROM and tried to enter into the recovery mode for trying out the adb sideload method. However, what I found was that I cannot enter the recovery mode. I was able to do so for a few times after I installed the Lollipop update, but then I suddenly stopped being able to do so. The method I had been following was Power+Volume Down for 5 sec to enter the bootloader, select the recovery option, and press volume up for 15-20 sec and press and release the power key while holding down the volume up button.
I though that I might have wiped the stock recovery during the upgrade, so I wanted to unlock bootloader and install a TWRP custom recovery. However, I was unable to unlock the bootloader, as I am unable to connect fastboot mode in Ubuntu when the phone is in the bootloader/fastboot mode ($ fastboot devices command in Ubuntu terminal window showed no devices. When phone is on, $ adb devices shows that my phone is connected. Also, USB debugging is on).
Can anyone help me with this issue?
Click to expand...
Click to collapse
Have you tried running the fastboot commands as root to rule out this being caused by a permission issue?
AWildColin said:
Have you tried running the fastboot commands as root to rule out this being caused by a permission issue?
Click to expand...
Click to collapse
Thanks for that. That was mighty stupid of me not to try that. I tried the sudo command in Ubuntu and it did work. I have root
Hi all, I wonder if anybody can help with this.
my volume buttons are not working (hardware issue) and I was trying to install TWRP and a custom rom but, after installing TWRP the phone now always boots in recovery mode (at least this is what adb tells me) but TWRP does not really start, I keep seeing only "honor, powered by android" black screen.
adb is working but not fastboot. I tried to reboot to bootloader but it always go to recovery instead. I have no su, and I am stuck just with adb in recovery.
any idea?
If you have full adb access maybe you can restore your backup directly from it
Thanks Rayan
how? what do you mean by "full adb access"?
I tried to run adb sideload but it does not work (it says "closed" shortly after without doing anything)
I don't really understand what the issue is, do you have access to TWRP menu or not at all? And when you say that you can use adb, is the device recognized when you type adb devices ? And what happens when you try to boot in bootloader and use fastboot? Can you try to the command "adb reboot bootloader"?
Rayan19997 said:
I don't really understand what the issue is, do you have access to TWRP menu or not at all? And when you say that you can use adb, is the device recognized when you type adb devices ? And what happens when you try to boot in bootloader and use fastboot? Can you try to the command "adb reboot bootloader"?
Click to expand...
Click to collapse
Thanks Rayan, I finally solved replacing the volume buttons (found cheap ones). However adb was working but no matter which command I was sending (adb reboot bootloader) the phone was always rebooting in recovery mode but TWRP was not starting properly (could not see anything)
with volume buttons I managed to enter into bootloader, reflash TWRP and do everything I needed
Thanks