i rooted my tf300 when on stock ics. i used the method that doesnt require bootloader unlocking.
couple of days later the jb ota came along, so installed that, and restored root with voodoo
i want to install a custom rom, but i can't get the recovery working. the tablet boots fine, and the behaviour is the same now im on jb, as it was when on ics
basically, i power on + vol down, then select the rck icon, and it loads to an android with a blue loading animation, then changes to a 'dead' android with a red exclamation just above.
the tablet still boots fine otherwise.
question is, do i have to unlock the bootloader before i can install/run the recovery, or is there a way i can do it without unlocking?
edit: i tried also flashing via fastboot (tried first with terminal, when trying twrp for ics) and this is what it comes back with, same thing for cwm and twrp:
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 flash recovery CWM-Touch.blob
sending 'recovery' (6370 KB)...
OKAY [ 2.646s]
writing 'recovery'...
FAILED (remote: (InvalidState))
finished. total time: 5.901s
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (7304 KB)...
OKAY [ 3.538s]
writing 'recovery'...
FAILED (remote: (InvalidState))
finished. total time: 6.779s
You have to unlock to install a custom rom. Think it over and do some more reading. You could build a house since there is no shortage of bricks. :banghead:
Still Charged Up
do you think there's any chance of being able to do this without unlocking in the future?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Nope. One requires the other. Simply put - ASUS does not want to deal with true user-created bricks. That's why they make it optional.
Still Charged Up
EDIT: Guys it worked. Some weird **** happened first, keyboard wasn't working on stock rom and everything was buggy but after an update with HiSuite and a factory reset everything works fine. Thank you for all your support.
I bricked my Honor 8 (FRD-L09) while trying to go back to stock rom. I can only acces eRecovery and Fastboot, when I try to access normal recovery, the screen just freezes at "Your device is booting now". After reading multiple guides, I tried unbricking with the Huawei Multitool but I always get these errors:
sending 'boot' (15464 KB)...
OKAY [ 0.334s]
writing 'boot'...
OKAY [ 0.371s]
finished. total time: 0.710s
target reported max download size of 471859200 bytes
sending 'cust' (433554 KB)...
OKAY [ 9.343s]
writing 'cust'...
FAILED (remote: partition error)
finished. total time: 9.358s
target reported max download size of 471859200 bytes
sending 'recovery' (36996 KB)...
OKAY [ 0.794s]
writing 'recovery'...
OKAY [ 0.883s]
finished. total time: 1.682s
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (435393 KB)...
OKAY [ 10.280s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 10.327s
I'm desperate and I don't know what to do.
EDIT: I HAVE MANAGED TO INSTALL RR BUT STILL CAN'T GO BACK TO STOCK.
Rommco05 said:
Hi, what about twrp u loos access?
Click to expand...
Click to collapse
I have regained access to twrp. I have installed a custom rom, but still can't install stock rom.
Rommco05 said:
Your hole model number is? U try yo flash stock rom via twrp?
Click to expand...
Click to collapse
FRD-L09. I haven't flashed stock rom via TWRP. I tried the huawei extractor method right now, I'm probably doing something wrong, I'll look more into it . I'm calm now that I managed to install a custom rom.
Rommco05 said:
Ok, so if still without luck try to download full stock fw B360 or B381 (2 zips)
Click to expand...
Click to collapse
Ok.. I will try that. My phone is stuck at "your device is booting up" screen after flashing stock recovery.
Note that there is also recovery2 in first update.zip when you extract it via Huawei Multitool. Thats probably why recovery never boots up, it's not all. Try to send the first basic ones - boot, recovery, recovery2, erecovery, and so on (don't exactly remember which). Then you should be fine to dload or flash the rest through fastboot (if possible). And remember to always use full-ota-mf-pv version of software (like FRD-L09C432B381) with about 2.37 GB total (2 zip files).
Rommco05 said:
You can flash back twrp?
Click to expand...
Click to collapse
Yes, I can.
So, did it work?!
PalakMi said:
So, did it work?!
Click to expand...
Click to collapse
I'm at work now. I'll try after a few hours.
Radu Florin said:
I'm at work now. I'll try after a few hours.
Click to expand...
Click to collapse
Good luck, I hope it works after all
Guys it worked. Some weird **** happened first, keyboard wasn't working on stock rom and everything was buggy but after an update with HiSuite and a factory reset everything works fine. Thank you for all your support.
Radu Florin said:
Guys it worked. Some weird **** happened first, keyboard wasn't working on stock rom and everything was buggy but after an update with HiSuite and a factory reset everything works fine. Thank you for all your support.
Click to expand...
Click to collapse
Great , your device is back :highfive:
Hey everyone!
I'm a long time reader, but never had the occasion to post until now. I have somewhat recently started tinkering with my phones. I'm a programmer by trade so I'm not at all seperated from technology, however, I fear I may have gotten myself into a but of a ?.
So, here's what I broke: I have a Verizon Wireless Pixel 2. A few weeks ago I read that there was a boot loader unlock for it. As such, I rebooted to the boot loader, ran the "fastboot flashing lock_critical" command. After being unlocked I then proceeded to flash TWRP and then Magisk Manager. All was well until my phone had an unrelated warranty issue. As such, I filed a claim, and got my new phone.
Today I was trying to recover my phone to factory and am getting a few errors. I downloaded this Image from Google "8.0.0 (OPD3.170816.023, Nov 2017, Verizon) - https://dl.google.com/dl/android/aosp/walleye-opd3.170816.023-factory-f269631e.zip"). I extracted it, and ran "flash_all.bat". Througout the process I get an error stating that it can't find a recovery.img. I looked in the .zip and found that to be true. I downloaded the standard stock .zip and noticed it doesn't have one either. In addition, when it gets to the part about flashing the system image I get the following error:
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
--------------------------------------------
Bootloader Version...: mw8998-002.0066.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: REMOVED
--------------------------------------------
checking product...
OKAY [ 0.000s]
checking version-bootloader...
OKAY [ 0.001s]
checking version-baseband...
OKAY [ -0.000s]
sending 'boot' (32768 KB)...
OKAY [ 0.744s]
writing 'boot'...
OKAY [ 0.000s]
sending sparse 'system' (524284 KB)...
OKAY [ 12.589s]
writing 'system'...
OKAY [ -0.000s]
sending sparse 'system' (524284 KB)...
FAILED (remote: No such partition.)
finished. total time: 13.631s
Anyone have any idea how to remedy this? I'm simply trying to get it back to stock. In addition, if I can get it returned to stock is relocking the bootloader even possible?
Thanks in advance for any help!
-Sofie
is your phone currently on 8.0.0 or have you been updated to at least 8.1?
you can't flash to a lower version than what you already have. i have verizon and i plan on flashing back to stock and you should be flashing to the 013 version from January.
iridium7777 said:
is your phone currently on 8.0.0 or have you been updated to at least 8.1?
you can't flash to a lower version than what you already have. i have verizon and i plan on flashing back to stock and you should be flashing to the 013 version from January.
Click to expand...
Click to collapse
It was on 8.1. Makes sense, I'll download the latest and try that. I just chose that because it says "VZW" in the name.
iridium7777 said:
is your phone currently on 8.0.0 or have you been updated to at least 8.1?
you can't flash to a lower version than what you already have. i have verizon and i plan on flashing back to stock and you should be flashing to the 013 version from January.
Click to expand...
Click to collapse
SweetSofie said:
It was on 8.1. Makes sense, I'll download the latest and try that. I just chose that because it says "VZW" in the name.
Click to expand...
Click to collapse
Well, that didn't help at all. :crying:
SweetSofie said:
Well, that didn't help at all. :crying:
Click to expand...
Click to collapse
try everything over and start clean:
1) delete all your stuff from your comp (all previous tools and images)
2) download the fresh set of latest adb tools from google
3) download the latest walleye stock image from google
4) put all those things in the same directory and uncompress them there (so flash-all.bat is in the same folder as adb, along with the img and zip files for walleye).
5) adb reboot bootloader
6) flash-all
are those similar to the steps that you did before?
SweetSofie said:
Hey everyone!
I'm a long time reader, but never had the occasion to post until now. I have somewhat recently started tinkering with my phones. I'm a programmer by trade so I'm not at all seperated from technology, however, I fear I may have gotten myself into a but of a ?.
So, here's what I broke: I have a Verizon Wireless Pixel 2. A few weeks ago I read that there was a boot loader unlock for it. As such, I rebooted to the boot loader, ran the "fastboot flashing lock_critical" command. After being unlocked I then proceeded to flash TWRP and then Magisk Manager. All was well until my phone had an unrelated warranty issue. As such, I filed a claim, and got my new phone.
Today I was trying to recover my phone to factory and am getting a few errors. I downloaded this Image from Google "8.0.0 (OPD3.170816.023, Nov 2017, Verizon) - https://dl.google.com/dl/android/aosp/walleye-opd3.170816.023-factory-f269631e.zip"). I extracted it, and ran "flash_all.bat". Througout the process I get an error stating that it can't find a recovery.img. I looked in the .zip and found that to be true. I downloaded the standard stock .zip and noticed it doesn't have one either. In addition, when it gets to the part about flashing the system image I get the following error:
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
--------------------------------------------
Bootloader Version...: mw8998-002.0066.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: REMOVED
--------------------------------------------
checking product...
OKAY [ 0.000s]
checking version-bootloader...
OKAY [ 0.001s]
checking version-baseband...
OKAY [ -0.000s]
sending 'boot' (32768 KB)...
OKAY [ 0.744s]
writing 'boot'...
OKAY [ 0.000s]
sending sparse 'system' (524284 KB)...
OKAY [ 12.589s]
writing 'system'...
OKAY [ -0.000s]
sending sparse 'system' (524284 KB)...
FAILED (remote: No such partition.)
finished. total time: 13.631s
Anyone have any idea how to remedy this? I'm simply trying to get it back to stock. In addition, if I can get it returned to stock is relocking the bootloader even possible?
Thanks in advance for any help!
-Sofie
Click to expand...
Click to collapse
Just so you know, those "archive does not contain" errors are normal. I get them all the time. Always did on the original Pixel too. I'm not sure about the one at the end. Can't say I've ever seen that on either the Pixel 1 or 2.
SweetSofie said:
Well, that didn't help at all. :crying:
Click to expand...
Click to collapse
Were you able to sort out your issue?
If not, I have heard good things about using this tool to install the latest factory image. Just download this script and follow the instructions in that thread.
If that goes well, then you should be able to boot to the latest build and ready to lock the bootloader, which will factory reset the phone as part of the process.
adb reboot bootloader
fastboot flashing lock
If that process makes you feel uncomfortable, I found this post from another thread doing a similar method (but not using the script above)
Good Luck!
robocuff said:
Just so you know, those "archive does not contain" errors are normal. I get them all the time. Always did on the original Pixel too. I'm not sure about the one at the end. Can't say I've ever seen that on either the Pixel 1 or 2.
Click to expand...
Click to collapse
Thanks for the re-assurance. I did notice that the zips literally dont contain a recovery.img. Is that normal for the Pixel 2?
SweetSofie said:
Thanks for the re-assurance. I did notice that the zips literally dont contain a recovery.img. Is that normal for the Pixel 2?
Click to expand...
Click to collapse
Yes. The recovery is in the boot.img now.
Duhman72 said:
Were you able to sort out your issue?
If not, I have heard good things about using this tool to install the latest factory image. Just download this script and follow the instructions in that thread.
If that goes well, then you should be able to boot to the latest build and ready to lock the bootloader, which will factory reset the phone as part of the process.
adb reboot bootloader
fastboot flashing lock
If that process makes you feel uncomfortable, I found this post from another thread doing a similar method (but not using the script above)
Good Luck!
Click to expand...
Click to collapse
I tried this tool and had no luck either. I ultimately just locked the bootloder, as-is, and sent it back. ? Hopefully the think it's just a component level failure since the boot loader is locked. I guess we will see... ?
SweetSofie said:
I tried this tool and had no luck either. I ultimately just locked the bootloder, as-is, and sent it back. ? Hopefully the think it's just a component level failure since the boot loader is locked. I guess we will see... ?
Click to expand...
Click to collapse
They won't even check, they don't care. They will inspect it for physical abuse and water damage. That is all.
TonikJDK said:
They won't even check, they don't care. They will inspect it for physical abuse and water damage. That is all.
Click to expand...
Click to collapse
I think you're right! So far so good. I haven't had any backlash from Verizon so far. Thanks!
Hi. I unlocked bootloader and flashed twrp via fastboot, but when I try to boot into it, the phone gets stuck at "your phone is booting now". The stock recovery no longer works. The phone's never been updated, still on Android 6.0 and EMUI 4.0. I tried several twrp versions with the same effect. What am I doing wrong? Can dm-verity be somehow interfering with twrp? Any ideas? Thanks in advance.
Code:
fastboot flash recovery twrp-3.0.2-0-next.img
target reported max download size of 471859200 bytes
sending 'recovery' (22020 KB)...
OKAY [ 0.701s]
writing 'recovery'...
OKAY [ 0.129s]
finished. total time: 0.830s
Months later I tried the same, also NXT-L29
Endless:
"Your device has been unlocked and can't be trusted....."
Your device is booting now...
Any solution please?
I am trying to install lineageos to my moto g7 power 2021.
I have followed all the instructions here https://wiki.lineageos.org/devices/ocean/install up until
Now reboot into recovery to verify the installation.
Use the menu to navigate to and to select the Recovery option.
under Booting a customer recovery using fastboot.
When I select recovery mode I get an android on its back with an open chest door with a red triangle with an exclamation point. Under that it says "no command."
Does anyone know what's going on and how I can if it?
If it helps, this is the result in got when flashing the recovery:
Sending 'boot_b' (25028 KB) OKAY [ 0.805s]
Writing 'boot_b' OKAY [ 0.109s]
Finished. Total time: 0.961s
I did this a few times and at one point it flashed to boot_a for as well.