Related
Describing my problem :
Since yesterday my OPO did some random reboots. I was running Paranoid Android and it worked perfectly...
Yesterdayevening after it rebooted another time, my OPO didn't start at all... It seems that my bootloader won't load the OS.
This morning, I did a complete wipe and I've put the stock ROM from the CM site back on my OPO ( XNPH33R signed boot).
-Fastboot works
-Recovery works
-Bootloader won't load OS. ( only the One Plus logo pops up (not the bootanimation)). After that it reboots over and over...
Update 1 17:30 5/10/2014 :
I'm in a bootloop, I have no ROM. I have the TWRP recovery. And the bootloader is LOCKED.
So I tried to unlock the bootloader with the toolkit for the OnePlus one. ( I tried it also manually with cmd).
----WHAT IT DOES in CMD/ Phone-------
In CMD : " OKAY [0.012 s]
Finished. total time : 0.012 s
OPO : It opens up my TWRP recovery but it does not unlock the bootloader
Update 2 19:52 5/10/2014 :
I've been able to unlock the bootloader...
with the command " fastboot oem device-info" , I received :
Bootloader tampered : True
Bootloader unlocked : False ( because the toolkit only did " fastboot oem unlock " , I did an adb sideload with a zip "OnePlusOne-OnlyBootloaderToggle" from the thread
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912. Now my bootloader is back UNLOCKED.
I hope the bootloop will stop when I do a factory / reset.
10:40 6/10/2014 :
I tried several times to flash stock roms from the official site / from the forum. None of them 'work'.
Can someone please help me?? He still bootloops!!! How frustrating thazt is,I tried everything from threads on the forum. Nobody is ansering my thread. Any reason for that ?
My suggestion is this: grab one of the recovery flashable versions of CM11S from here, boot into your TWRP recovery and use adb to push the ROM zip to your phone, then use the install function in TWRP to flash it.
To push the zip to your phone you first need to put it in your adb/fastboot folder (wherever you have adb.exe and fastboot.exe located on your PC), make sure your phone is booted into TWRP and connected to your PC, open a command prompt from within your adb/fastboot folder (shift + right click anywhere in the folder, then select open command prompt here), and issue this command:
Code:
adb push <name of file.zip> /sdcard/
*Please note the '<' and '>' symbols are not included in the command.
From there just flash the ROM like you would flash any other ROM.
Transmitted via Bacon
Failure with E:
timmaaa said:
My suggestion is this: grab one of the recovery flashable versions of CM11S from here, boot into your TWRP recovery and use adb to push the ROM zip to your phone, then use the install function in TWRP to flash it.
To push the zip to your phone you first need to put it in your adb/fastboot folder (wherever you have adb.exe and fastboot.exe located on your PC), make sure your phone is booted into TWRP and connected to your PC, open a command prompt from within your adb/fastboot folder (shift + right click anywhere in the folder, then select open command prompt here), and issue this command:
Code:
adb push <name of file.zip> /sdcard/
*Please note the '<' and '>' symbols are not included in the command.
Transmitted via Bacon
Click to expand...
Click to collapse
Pushing the zip into sdcard :good:
Installing the zip gives a message about E:
example :
something with E: path
E: unable to wipe
E: error executing updater binary in zip 'sdcard/cm11.0... .zip
Proberly more
Are you sure you're attempting to flash one of the recovery flashable zips? What's the full filename?
Transmitted via Bacon
timmaaa said:
Are you sure you're attempting to flash one of the recovery flashable zips? What's the full filename?
Transmitted via Bacon
Click to expand...
Click to collapse
cm-11.0-XNPH33R-bacon-signed
Links
1. Recovery flashable zips of the complete ROMz:
XNPH22R
XNPH25R
XNPH33R
From your link
EDIT-----
1. I had flashed the stock recovery back.
2. Did a factory reset
3. Wiped cache
4. Wiped media
5. Flashed TWRP back
6. ADB push zip in /sdcard/
7. Flashed the zip SUCCESSFUL after these steps
I still have a bootloop
Have you tried to format your internal sd card and flash your zip. Remember if you format though you will lose everything on your sdcard. Make sure you backup everything first if you want to try this. Also if you do this you will have to push your zip back to the phone
Who can even solve this?...
playya said:
Have you tried to format your internal sd card and flash your zip. Remember if you format though you will lose everything on your sdcard. Make sure you backup everything first if you want to try this. Also if you do this you will have to push your zip back to the phone
Click to expand...
Click to collapse
My internal storage was already formatted. I just have the TWRP and the zip on my phone.
[Q] In the TWRP recovery menu in 'Advanced' what has to be between Copy Log to SD and Terminal Command? There is a blank spot ,there should be button normally?
How is it even possible i have nothing but the recovery and the zip and I still got a bootloop...
Is there somebody that knows something else that i can try?
Is it possible to flash perhaps with odin?
VictorByttebier said:
My internal storage was already formatted. I just have the TWRP and the zip on my phone.
[Q] In the TWRP recovery menu in 'Advanced' what has to be between Copy Log to SD and Terminal Command? There is a blank spot ,there should be button normally?
How is it even possible i have nothing but the recovery and the zip and I still got a bootloop...
Is there somebody that knows something else that i can try?
Is it possible to flash perhaps with odin?
Click to expand...
Click to collapse
definitely not odin thats Samsung my friend. Partition SD Card is whats missing in TWRP for you. I asked about formatting internal because a similar thing happened to my friend. We had to format internal then adb push recovery and rom and all was well again. If you have tried this recently then my bad but if you have not it wont hurt to try it again in that order
format internal
adb push recovery
adb push rom
reboot
Take a look in here as well http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
Bootloop fixed
It finally worked!!! How weird that i already found a zip like on the thread but with XNPH33R and also with the persist and recovery.img and flash-all etc... but it didn't work.
Now i just have to update from the settings
At beginning I was convinced that a bootloop could be fixed with factory/reset would do it. Like it always worked on my previous smartphone.
Thank you playya and timmaaa for the responses!:good: You are awesome! See me sitting here with a
Hello all.
I know there are many threads of this kind but nothing worked for me. So Please help!
I unlocked my bootloader, installed TWRP and flashed SuperSU binaries. Everything was working fine.
Then I wanted to flash cm12 nightly. So i downloaded the zip file and also the Gaaps.zip file. I transfered them to the phone and booted to recovery.
1. Then instead of wiping cache i wiped the whole system i.e factory data reset. So then i tried reboot it says NO OS INSTALLED! do you want to continue? After that "Your phone is not rooted. Install SuperSU? As i don't have the SuperSU files so it just reboots to the bootscreen and stays there. I can go to the recovery and fastboot mode.
2. then i booted to recovery and went to adb sideload. I have the ADB files on my desktop and pasted the ROM.zip file to the folder.
3. Then i tried the command adb sideload ROM.zip with my phone connected. But then a lot of coding appears in the cmd window and phone stays at adb sideload.
4. When i connect my phone to my pc in recovery It comes up as "One" in the disk drives. I open it and it has a folder named TWRP and inside thata file. Nothing else. The good thing is I have a nandroid backup of my device when it had SuperSU binaries.
*the "One disappears when I go to ADB sideload in my phone*
So can I transfer the backup to my phone in a separate folder named "Backups" and install it via restore in TWRP? Or do have to do something else?
Please help! Please! :crying:
You're already getting help for this here:
http://forum.xda-developers.com/showthread.php?t=3044924
Transmitted via Bacon
I accidentally formatted all partition and now only have a TWRP. The TWRP only shows the start screen when i go to recovery.
Adb devices show me the device detected. I did a adb push and moved the stock rom 5.1.11 and my twrp recovery to the sdcard using the command adb push. I am struck here because i cannot get to the twrp screen which gives you option to install/wipe etc.
Can somebody please guide me if there is a way to recover or install the .zip files I have copied to sdcard. Thanks in advance
You need to fastboot flash the default stock rom, and then re root/install TWRP etc etc
Thank you for your response. Will that be adb fastboot flash stock.zip ? I am not sure if this would mess it up hence please confirm. Also, will it work if i use the fastboot to install twrp again and then flash the stock rom using its menu.
SachinGopal said:
Thank you for your response. Will that be adb fastboot flash stock.zip ? I am not sure if this would mess it up hence please confirm. Also, will it work if i use the fastboot to install twrp again and then flash the stock rom using its menu.
Click to expand...
Click to collapse
You need to go to this thread... https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Download the version of OOS you want (5.1.11) and unzip the contents in to a folder and run the flash-all.bat file and let it install to all partitions. Just follow this instructions in the thread and you will be fine.
Thank you so much for your response, but when I run this command I am getting " Waiting for device" option. I am only able to boot into twrp. I see the teamwin loading screen and its struck there. I am able to run adb commands and adb device shows the device details. I was also able to push the stock rom.zip through adb push command to /sdcard.
D:\OnePlus6Oxygen_22_OTA_015_all_1808102118_770880-FASTBOOT>flash-all-partitions-fastboot.bat
Do you want to wipe all the data ( Reccomended )[Y/N]?y
< waiting for any device >
Thank you so much it worked when I tried. Grateful . Will donate the Dev for that bat script.
SachinGopal said:
Thank you so much for your response, but when I run this command I am getting " Waiting for device" option. I am only able to boot into twrp. I see the teamwin loading screen and its struck there. I am able to run adb commands and adb device shows the device details. I was also able to push the stock rom.zip through adb push command to /sdcard.
D:\OnePlus6Oxygen_22_OTA_015_all_1808102118_770880-FASTBOOT>flash-all-partitions-fastboot.bat
Do you want to wipe all the data ( Reccomended )[Y/N]?y
< waiting for any device >
Click to expand...
Click to collapse
You need to be in fastboot mode.
Either adb reboot bootloader from inside android or from a powered off phone, hold Volume Up and power on.
Hello, i want to reactivate my old acer A701 by flashing a newer img or zip.I have the following problems.When I try to do the recovery with a zip file on an sdcard i get the prop error.When i try to flash it by an img i always get i haven set the ANDROID_PRODUCT_OUT even when I do an export ANDROID_PRODUCT_OUT=/home/leopold/platform-tools.
A printenv shows the ANDROID_Product_OUT and the img is in platform-tools.
What is going wrong, what can i do?
You either apply Flash zip from sd from within Android's Recovery menu or you use external ADB Sideload command to flash a properly signed ZIP-file what contains the ROM, or you use external Fastboot Flash command to flash an IMG-file what requires device's bootloader is unlocked.
Hello and thank you,
like i wrote above, i want to flash it.Now i found at another place i have to write:
sudo ANDROID_PRODUCT_OUT="./" fastboot flashall recovery Az.img
when i do that, the flash is starting but then i get the error android-info.txt is missing.
So i guess i have a wrong image.
Does anybody have an image for the A701 with a newer android version.Or can give me a link.
My 4.1.1 does not recognice newer apps.
leopold
Take note that
Code:
fastboot flashall <ROM.IMG>
is to be used to flash a complete ROM, whereas
Code:
fastboot flash recovery <RECOVERY.IMG>
is to be used to flash only a Recovery.
Ok, i understand but i m lost.
I have some imagees and some zip files what should work on my a701.
If I use fastboot with img, i get no android-txt found.
if I work with adb reboot recovery and the zip files I will allways get the partition error prop undefined.
Can I supress the search for the android -txt?
What else can I do?
one of the zip files is from here https://acer.shreps.fr/, it is the said stable kitkat.
If you have access to a Windows computer then make use of a Flash Tool what's suitable to the tablet.
Unfortunately i can not find a flashtool for the nividia tegra3.
I have some zip files what should work on the a701 but all have the error check partition size [-Prop_UNDEFINED-) then the installation will be aborted.
Is there a way to eliminate the partition check.
Or does somebody have a zip or an img with a working update or recovery for a recent Android working on the a701?
was bout to flash pixel experience plus android 12. But i accidentally deleted the internal storage . Now i don't have a OS. I don't have a SD card as well. I tried ADB sideload from TWRP. I still have the TWRP but only TWRP. I installed all the drivers for ADB, Also the qualcomm driver as well. But when i use the adb devices command in cmd without running adb from mobile it shows the device is there but when i start ADB from TWRP it doesn't detect the device in PC> PLEASE HELP
eusz said:
was bout to flash pixel experience plus android 12. But i accidentally deleted the internal storage . Now i don't have a OS. I don't have a SD card as well. I tried ADB sideload from TWRP. I still have the TWRP but only TWRP. I installed all the drivers for ADB, Also the qualcomm driver as well. But when i use the adb devices command in cmd without running adb from mobile it shows the device is there but when i start ADB from TWRP it doesn't detect the device in PC> PLEASE HELP
Click to expand...
Click to collapse
What do you mean with this "without running ADB from mobile"?
ADB must run only in the CMD.
When you do adb devices, device doesn't appear?, try with disabling/enabling MTP.
When the twrp is open and i don't click ADB mode in twrp , it detects the phone . But after i click ADB in the twrp it get's disconnected in the PC and i can't flash the rom.
eusz said:
When the twrp is open and i don't click ADB mode in twrp , it detects the phone . But after i click ADB in the twrp it get's disconnected in the PC and i can't flash the rom.
Click to expand...
Click to collapse
Not sure what you mean with "click" ADB, adb is a command to type through.
Try transferring the file to the internal storage, use, adb push, then flash through TWRP, strange enough so TWRP enables ADB by default, although the ADB sideload can fail.
Try reflashing Newest TWRP , may be a bug or an error, even try to install "Minimal adb and fastboot tool" its more easy to use ...
Enriquecalong said:
Try reflashing Newest TWRP , may be a bug or an error, even try to install "Minimal adb and fastboot tool" its more easy to use ...
Click to expand...
Click to collapse
try ofox recovery, in that recovery always appears ADB SIDELOAD in pc , without error , almost for me...
TWRP RECOVERY(VAYU VERSION)
OFOX RECOVERY (VAYU)
For android 12 roms use ofox... less bugs
If your internal storage doesnt appears only FORMAT DATA and you can copy the rom in your internal storage without using ADB.
SubwayChamp said:
Not sure what you mean with "click" ADB, adb is a command to type through.
Try transferring the file to the internal storage, use, adb push, then flash through TWRP, strange enough so TWRP enables ADB by default, although the ADB sideload can fail.
Click to expand...
Click to collapse
ADB sideload didn't work here.
Enriquecalong said:
try ofox recovery, in that recovery always appears ADB SIDELOAD in pc , without error , almost for me...
TWRP RECOVERY(VAYU VERSION)
OFOX RECOVERY (VAYU)
For android 12 roms use ofox... less bugs
If your internal storage doesnt appears only FORMAT DATA and you can copy the rom in your internal storage without using ADB.
Click to expand...
Click to collapse
This worked thanks man.