I keep trying to flash t.w.r.p via adb but it keeps failing. I try orange and Peter but they don't work and make me get stuck in bootloop. Official 3.3.1 recovery flashes but then when I boot to recovery it only shows the teamwin logo and I have no options to do anything, then on reboot when I trying booting into recovery again it boots into stock recovery like I never even flashed it.
Can someone tell me what I'm doing wrong or tell me correct recovery to flash with this rom? It should be straight forward process to flash t.w.r.p, but I am having trouble for some reason. Thank you.
toyspeed said:
I keep trying to flash t.w.r.p via adb but it keeps failing. I try orange and Peter but they don't work and make me get stuck in bootloop. Official 3.3.1 recovery flashes but then when I boot to recovery it only shows the teamwin logo and I have no options to do anything, then on reboot when I trying booting into recovery again it boots into stock recovery like I never even flashed it.
Can someone tell me what I'm doing wrong or tell me correct recovery to flash with this rom? It should be straight forward process to flash t.w.r.p, but I am having trouble for some reason. Thank you.
Click to expand...
Click to collapse
What's the message that appears in ADB when you flash it?
toyspeed said:
I keep trying to flash t.w.r.p via adb but it keeps failing. I try orange and Peter but they don't work and make me get stuck in bootloop. Official 3.3.1 recovery flashes but then when I boot to recovery it only shows the teamwin logo and I have no options to do anything, then on reboot when I trying booting into recovery again it boots into stock recovery like I never even flashed it.
Can someone tell me what I'm doing wrong or tell me correct recovery to flash with this rom? It should be straight forward process to flash t.w.r.p, but I am having trouble for some reason. Thank you.
Click to expand...
Click to collapse
Did u unlocked the bootloader?
Sent from my Redmi Note 7 Pro using XDA Labs
Naveenthemi said:
What's the message that appears in ADB when you flash it?
Click to expand...
Click to collapse
Just usual message such as:
PS C:\platform-tools> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.112s]
writing 'recovery'...
OKAY [ 0.355s]
finished. total time: 2.474s
I tried with Black Project also, same story. I don't understand this, I just want to root but I can't!
toyspeed said:
Just usual message such as:
PS C:\platform-tools> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.112s]
writing 'recovery'...
OKAY [ 0.355s]
finished. total time: 2.474s
I tried with Black Project also, same story. I don't understand this, I just want to root but I can't!
Click to expand...
Click to collapse
Ok someone else who's facing the same problem fixed this by formatting the data partition.
But idk why don't you try reinstalling MIUI(Flashboot it through MiFlash) and then try again?
Naveenthemi said:
Ok someone else who's facing the same problem fixed this by formatting the data partition.
But idk why don't you try reinstalling MIUI(Flashboot it through MiFlash) and then try again?
Click to expand...
Click to collapse
Ok, thanks for advice I'll try formatting data partition. That's exactly what I've been doing, flashing MIUI through MiFlash everything perfect. Then I run into problems after I try flashing recovery so I can root, very weird but I will keep trying.
toyspeed said:
Ok, thanks for advice I'll try formatting data partition. That's exactly what I've been doing, flashing MIUI through MiFlash everything perfect. Then I run into problems after I try flashing recovery so I can root, very weird but I will keep trying.
Click to expand...
Click to collapse
Did it work?
Naveenthemi said:
Did it work?
Click to expand...
Click to collapse
I actually decided to flash Superior OS instead, loving it so far!
Related
Hi Guys,
Hoping you can help me with this.
I was originally running Slimkat 4.4.4 and had the latest TWRP installed.
I downloaded the file for LPX13D and extracted all of the files right down to the Flash-all.bat and the images for bootloader, radio, and the system.
I ran the Flash-all.bat, and it installed everything successfully. The device booted, and voila, I am on 5.0 now.
The problem now, is that when I reboot into recovery, I am instead met with the little android guy laying on his back, with a red triange/exclamation point in his chest.
No problem, I say to myself. I'll just flash TWRP manually.
So I go to the bootloader, and try the command fastboot flash recovery recovery.img (renamed to make it faster to type.)
It goes through the motions, and says it was successful.
But when I go to recovery, it's the same red triange guy still.
I tried pressing volume up, power+volume up, etc. No dice. After about 30 seconds, it reboots on it's own back to system.
When I connect it to the Nexus Root Toolkit, and click on Flash recovery, and then choose TWRP latest, I get a window that pops up that tells me :
______
File Dependency Download
Status: Stock Kernel: Not Present - Need to download (this is in red)
Then a button that says "Download + Update All File Dependencies"
So what's my best option here? Should I let the NRT update the dependencies?
Try to flash cwm and tell me what happens
Isus <3 said:
Try to flash cwm and tell me what happens
Click to expand...
Click to collapse
D:\DOWNLOADS>fastboot flash recovery cwm.img
target reported max download size of 1073741824 bytes
sending 'recovery' (11312 KB)...
OKAY [ 0.561s]
writing 'recovery'...
OKAY [ 0.930s]
finished. total time: 1.491s
D:\DOWNLOADS>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
I then selected recovery, and lo and behold, it worked! I'm in CWM.
So then i flashed TWRP again, and now it's working properly too.
I don't know why it refused to work the first time, but now it seems to be okay. How strange.
Thanks for your time and help. I appreciate it.
deleted
Stupendousman2012 said:
D:\DOWNLOADS>fastboot flash recovery cwm.img
target reported max download size of 1073741824 bytes
sending 'recovery' (11312 KB)...
OKAY [ 0.561s]
writing 'recovery'...
OKAY [ 0.930s]
finished. total time: 1.491s
D:\DOWNLOADS>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
I then selected recovery, and lo and behold, it worked! I'm in CWM.
So then i flashed TWRP again, and now it's working properly too.
I don't know why it refused to work the first time, but now it seems to be okay. How strange.
Thanks for your time and help. I appreciate it.
Click to expand...
Click to collapse
Twrp is not optimized yet well like cwm is for andorid l
Recovery won't work AT ALL no matter what you do until you reflash a KK userdata.img, which also wipes all data in the process.
Lethargy said:
I flashed the new developer preview for 5 minutes or so then went to revert. Recovery wouldn't boot not matter what I flashed, until I flashed a KK userdata.img. So it seems like the new developer preview changes the internal storage/data partition more then the old one.
Click to expand...
Click to collapse
Don't try getting around it. Nothing to do with anything else.
Isus <3 said:
Twrp is not optimized yet well like cwm is for andorid l
Click to expand...
Click to collapse
What? CWM is outdated.
Lethargy said:
Recovery won't work AT ALL no matter what you do until you reflash a KK userdata.img, which also wipes all data in the process.
Don't try getting around it. Nothing to do with anything else.
What? CWM is outdated.
Click to expand...
Click to collapse
Well, Twrp worked until I rebooted and then tried going back to it. Then bam! back to the error dude with the triangle.
So, I flashed cwm again, and that one seems to be persisting after a reboot, so I guess I'm stuck with cwm for now....
I also flashed the boot.img and the supersu update to get root working, and it seems to be going well now.
Cwm tells me that I may have lost root immediately after flashing the supersu update, but when I reboot, root is actually working. What a weird bunch of crap to go through.
Stupendousman2012 said:
Well, Twrp worked until I rebooted and then tried going back to it. Then bam! back to the error dude with the triangle.
Click to expand...
Click to collapse
Flash userdata.img and your TWRP will work properly.
Stupendousman2012 said:
So, I flashed cwm again, and that one seems to be persisting after a reboot, so I guess I'm stuck with cwm for now....
Click to expand...
Click to collapse
It isn't whether its persisting or not. TWRP just won't boot properly until you reflash a KK userdata.img. I don't know why CWM would even boot up, nor why anyone would want to really use it anyways.
Stupendousman2012 said:
Cwm tells me that I may have lost root immediately after flashing the supersu update, but when I reboot, root is actually working. What a weird bunch of crap to go through.
Click to expand...
Click to collapse
It says that because CWM is outdated.
Lethargy said:
Flash userdata.img and your TWRP will work properly.
It isn't whether its persisting or not. TWRP just won't boot properly until you reflash a KK userdata.img. I don't know why CWM would even boot up, nor why anyone would want to really use it anyways.
It says that because CWM is outdated.
Click to expand...
Click to collapse
Okay:
So I extract the userdata from a 4.4.4 stock image, yes? If not, can you point me in the direction of the correct userdata.img
I assume the correct order and syntax is:
fastboot flash userdata userdata.img
fastboot reboot-bootloader
fastbook flash recovery twrp.img
Fastboot reboot-bootloader
Select recovery
Wipe data/Factory reset, and then and reboot system.
Set up phone as normal.
Have I overlooked anything?
Stupendousman2012 said:
Okay:
So I extract the userdata from a 4.4.4 stock image, yes? If not, can you point me in the direction of the correct userdata.img
I assume the correct order and syntax is:
fastboot flash userdata userdata.img
fastboot reboot-bootloader
fastbook flash recovery twrp.img
Fastboot reboot-bootloader
Select recovery
Wipe data/Factory reset, and then and reboot system.
Set up phone as normal.
Have I overlooked anything?
Click to expand...
Click to collapse
Yeah. Don't need to boot into recovery and wipe data since flashing a .img with fastboot while in bootloader erases it first then flashes. Just make sure you backup your stuff, including internal storage, off to a PC first if you have anything important.
Until L is officially released, we're using the below thread
http://forum.xda-developers.com/show....php?t=2796217
Android "L" Developer Preview Help, Troubleshooting, Q&A
Sent from my Nexus 5 using Tapatalk
Going through some of the threads here got me as far as being able to use fastboot on my bricked Shield.
I would like to ask if anyone can give me some pointers what to try next.
The previous owner tried to flash Lineage OS onto the Tablet using CWM but this failed and he probably wiped some needed partition.
I tried to flash new partitions and this works but I can not start the Shield and it won't boot into CWM. The strange thing is that I tried flashing TWRP and even though that started it did not boot through. And after a simple Shield reboot the CWM logo popped upmagain.....:confused
I was convinced I could fix this but I am beginning to think that this Tablet is a goner...
Any thoughts would ne appreciated.
What happens if you download an original recovery image from Nvidia for your model, and flashboot flash all 5 (recovery, boot, system, userdata, blob)? Do you get any fastboot errors? If the partition structure is corrupted, you'll see some sort of error message.
If the blob is messed up sometimes TWRP won't start. I suggest getting a factory image and trying again, then giving it a long time to boot. Once mine took 20 minutes at the Nvidia screen.
I did try flashing the original image from Nvidia including the other 4 images. One of the first things I tried. I woyld like to get it back to factory default. This went without issues an no errors. I might not have given it enough tine to but but still CWM seems to be on.
Will give it another try and post a screenshot.
Sent from my SM-G935F using Tapatalk
Here is a dump of the flash log. After flashing I reboot and the CWM logo pops up after a few minutes and gets stuck.
D:\Downloads\Shield Fix\Drivers\ADB FastBoot\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 100663296 bytes
sending 'recovery' (9758 KB)...
OKAY [ 0.384s]
writing 'recovery'...
OKAY [ 0.320s]
finished. total time: 0.709s
D:\Downloads\Shield Fix\Drivers\ADB FastBoot\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.394s]
booting...
OKAY [ 0.017s]
finished. total time: 0.417s
Think it is done for, after flashing TWRP numerous times it let me get to the start screen for TWRP it then hangs. When you reboot the Shield and want to go to the recovery again you get the dead android.
PS. I can sometimes get into TWRP but it fails on everything I do. Would there be a terminal solution for this? Like re-creating partitions?
Unlock your bootloader?
Sent from my ZTE A2017U using Tapatalk
It is already unlocked I am afraid.
Sent from my SM-G935F using Tapatalk
sn0r said:
It is already unlocked I am afraid.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Try to flash the attached file. Remember to unzip it first! Flash with:
"fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb"
Flashed the battery file and did another flash of NVIDIA's recovery image and even-tough it says everything is flashed correctly when I reboot I get the CWM logo and nothing more. When I do get into TWRP and try to flash a ROM I get messages errors like attached.
sn0r said:
Flashed the battery file and did another flash of NVIDIA's recovery image and even-tough it says everything is flashed correctly when I reboot I get the CWM logo and nothing more. When I do get into TWRP and try to flash a ROM I get messages errors like attached.
Click to expand...
Click to collapse
Then my guess would be some problems with the internal storage which may not be repairable.
Using fastboot try the following
Fastboot erase cache
Fastboot format cache
Fastboot format userdata
Make sure your tablet is in bootloader mode first though.
Sent from my pa_osprey using Tapatalk
Hello All,
I tried many ROMs but somehow now I am not able to boot in TWRP after flashing it.
Not able to add image here.
Command used is fastboot flash recovery twrp-2.8.6.0-bacon.img
target reported max download size of 536870912 bytes
sending recovery (10180 KB)
OKAY [ 0.368s]
writing recovery
OKAY [ 0.186s]
finished total time 0.554s
I can boot in fastboot mode. Any help would be appreciates. Thanks
Sanjay13 said:
Hello All,
I tried many ROMs but somehow now I am not able to boot in TWRP after flashing it.
Not able to add image here.
Command used is fastboot flash recovery twrp-2.8.6.0-bacon.img
target reported max download size of 536870912 bytes
sending recovery (10180 KB)
OKAY [ 0.368s]
writing recovery
OKAY [ 0.186s]
finished total time 0.554s
I can boot in fastboot mode. Any help would be appreciates. Thanks
Click to expand...
Click to collapse
Boot into twrp just after you flash it.And flash latest twrp this time.
I recommend @kutep0v 's twrp.
Mr.Ak said:
Boot into twrp just after you flash it.And flash latest twrp this time.
I recommend @kutep0v 's twrp.
Click to expand...
Click to collapse
hello,
I am getting a error
booting
Failed ( remote:dtb not found)
Sanjay13 said:
hello,
I am getting a error
booting
Failed ( remote:dtb not found)
Click to expand...
Click to collapse
You mean a error while flashing recovery?
Just after flashing, long press volume down plus power button to restart & get into recovery.
In case problem persists, memory could be corrupted.
You might need to start afresh installing cm13 snapshot. That'll wipe your phone internal memory as well.
kapil_dheer said:
Just after flashing, long press volume down plus power button to restart & get into recovery.
In case problem persists, memory could be corrupted.
You might need to start afresh installing cm13 snapshot. That'll wipe your phone internal memory as well.
Click to expand...
Click to collapse
Thanks Kapil. I could resolve the problem myself. I did a instaal cm13 using the below link.
http://tweakguy.com/return-your-oneplus-one-to-full-stock/
Then flashed TWRP and then had the ROM installed. Guess now I can flash anything for OPO.
Well my due credit to TweakGuy and also to DeadlyIndian for the ROM below having the latest Oxygen and Marshmellow
https://forum.xda-developers.com/oneplus-one/development/rom-oxygenos-3-1-2-t3470907
Thanks once again to all who read this.
I need help with my op6.
I was using LOS (Unlocked+rooted) until now and I accidentally brick my device, now it's stuck at the bootloader screen.
It doesn't matter if I'm trying to get into the system/recovery.
These are the steps that I did to get here (as far as I can remember):
Wipe system, data, and cache.
Flash latest OxygenOS (9.0.4) using TWRP (blu_spark_v9.96).
Flash TWRP.
Reboot to TWRP
This time it didn't ask me to unlock it with my pattern, and I saw that all of my files in the sdcard folder are encrypted.
I pressed the other partition (A) manually and reboot to TWRP.
It got stuck on the recovery screen.
I flashed TWRP via ADB.
Now the A partitions files are encrypted, I tried to manually move to partition B again, but stuck at crash dump after reboot.
I flashed TWRP via ADB, this time to B.
And now it's stuck at the bootloader...
I can't use the MsmDownloadTool because it's the bootloader and not the crashdump screen, the tool doesn't recognize the device in order to unbrick it.
I even tried to use this guide, but it didn't help, the msmtool still don't recognize it.
I tried to flash TWRP via ADB and this is what I got:
Code:
C:\Users\Folio\Downloads>fastboot flash recovery twrp-3.2.3-x_blu_spark_v9.96_op
6.img
target reported max download size of 536870912 bytes
sending 'recovery' (28892 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.625s
I also tried these commands:
Code:
C:\Users\Folio\Downloads>fastboot getvar current-slot
current-slot: b
finished. total time: -0.000s
C:\Users\Folio\Downloads>fastboot flash boot_b twrp-3.2.3-x_blu_spark_v9.96_op6.
img
target reported max download size of 536870912 bytes
sending 'boot_b' (28892 KB)...
OKAY [ 0.617s]
writing 'boot_b'...
OKAY [ 0.140s]
finished. total time: 0.773s
C:\Users\Folio\Downloads>fastboot boot twrp-3.2.3-x_blu_spark_v9.96_op6.img
downloading 'boot.img'...
OKAY [ 0.608s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.640s
But it didn't really do anything...
I'm out of ideas, what should I do next?
just go use the unbrick tool ?
I've been in your situation a lot of times in the beginning when I started to know about A/B partitioning.
Just fastboot the stock rom found here and you will boot easily in OOS.. Although your internal will be formatted every time you do this.
By the way, when you go to OOS from any ROM, you will always have to format internal storage to make OOS boot. (The step you didnt do in mentioned steps)
Fastboot ROM - https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Blunts47 said:
just go use the unbrick tool ?
Click to expand...
Click to collapse
As I mentioned.
Yes, I have tried that already.
Joyarup said:
I've been in your situation a lot of times in the beginning when I started to know about A/B partitioning.
Just fastboot the stock rom found here and you will boot easily in OOS.. Although your internal will be formatted every time you do this.
By the way, when you go to OOS from any ROM, you will always have to format internal storage to make OOS boot. (The step you didnt do in mentioned steps)
Fastboot ROM - https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Click to expand...
Click to collapse
I never saw in any other guide that It's necessary to also wipe the internal storage.
The OP6 imaging prosses is even more agonizing than I thought it is. :crying:
I'll try the guide that you sent me and will update, thanks for that.
lyor said:
As I mentioned.
Yes, I have tried that already.
I never saw in any other guide that It's necessary to also wipe the internal storage.
The OP6 imaging prosses is even more agonizing than I thought it is. :crying:
I'll try the guide that you sent me and will update, thanks for that.
Click to expand...
Click to collapse
I agree with you, the A/B partitioning is just a pain in the back.
Try that guide, just let your phone boot into fastboot, plug in pc and run the batch file in the zip of the rom and let it proceed.
Joyarup said:
I agree with you, the A/B partitioning is just a pain in the back.
Try that guide, just let your phone boot into fastboot, plug in pc and run the batch file in the zip of the rom and let it proceed.
Click to expand...
Click to collapse
WOW, how is this guide is not more popular?
Anyhow, you just saved my as5 man, thank you!
lyor said:
WOW, how is this guide is not more popular?
Anyhow, you just saved my as5 man, thank you!
Click to expand...
Click to collapse
Haha, glad to be useful. I know right, fastbooting ROMs are not popular these days. Everyone just follows the unbrick tool..
Enjoy!!
btw, can I now move freely to any other ROM without touching (flashing) the stock ROM?
lyor said:
btw, can I now move freely to any other ROM without touching (flashing) the stock ROM?
Click to expand...
Click to collapse
Yes, if you are booted to OOS once, you can flash any ROMs now. But remember while flashing back the OOS, you will need to wipe internals.
Joyarup said:
Yes, if you are booted to OOS once, you can flash any ROMs now. But remember while flashing back the OOS, you will need to wipe internals.
Click to expand...
Click to collapse
Oh yes, one last thing.
Will I be able to install them without flashing TWRP every time after them (for both of the A/B slots)?
lyor said:
Oh yes, one last thing.
Will I be able to install them without flashing TWRP every time after them (for both of the A/B slots)?
Click to expand...
Click to collapse
Always flash ROM zip + Twrp
Then reboot to TWRP then flash gapps and magisk(if any).
And never change boot partition through twrp, it will brick you. It's kinda buggy...
Hi All,
I need some help please with (soft?) bricked Note 7 pro. I have the global version and installed e. foundation ROM which is a fork of LineageOS. This was working well until I loaded the latest version last week. Now the phone seems to be softbricked.
I can get into fastboot. I have downloaded TWRP violet and when I run "fastboot flash recovery twrp-3.3.0-0-violet.img" I get:
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.723s]
writing 'recovery'...
OKAY [ 0.370s]
finished. total time: 2.093s
However when I try to boot into that recovery it wont work. (I just see the "Redmi by Xiaomi" screen with the "unlocked" detail at the bottom.
I also tried to run "fastboot boot twrp-3.3.0-0-violet.img" but that leads to a "system has been destroyed" message.
I downloaded the Mi unlock tool and tried to unlock again, just in case, but that tool reported that the phone is unlocked already.
I should point out that I get the same result with twrp-3.3.1-0-violet.img
Does anyone have any suggestions as to what I can try next? I am reluctant to remove the back from the phone.
Thanks
jimmy987654321 said:
Hi All,
I need some help please with (soft?) bricked Note 7 pro. I have the global version and installed e. foundation ROM which is a fork of LineageOS. This was working well until I loaded the latest version last week. Now the phone seems to be softbricked.
I can get into fastboot. I have downloaded TWRP violet and when I run "fastboot flash recovery twrp-3.3.0-0-violet.img" I get:
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.723s]
writing 'recovery'...
OKAY [ 0.370s]
finished. total time: 2.093s
However when I try to boot into that recovery it wont work. (I just see the "Redmi by Xiaomi" screen with the "unlocked" detail at the bottom.
I also tried to run "fastboot boot twrp-3.3.0-0-violet.img" but that leads to a "system has been destroyed" message.
I downloaded the Mi unlock tool and tried to unlock again, just in case, but that tool reported that the phone is unlocked already.
I should point out that I get the same result with twrp-3.3.1-0-violet.img
Does anyone have any suggestions as to what I can try next? I am reluctant to remove the back from the phone.
Thanks
Click to expand...
Click to collapse
Use Peter's twrp or flash fastboot rom with miflash
urstrulynaveen said:
Use Peter's twrp or flash fastboot rom with miflash
Click to expand...
Click to collapse
Thanks. Ive never heard of Peters TWRP so I'll try that next. Cheers.
jimmy987654321 said:
Thanks. Ive never heard of Peters TWRP so I'll try that next. Cheers.
Click to expand...
Click to collapse
Thanks urstrulynaveen, that worked a treat. I'm very grateful. All back up and running now.
jimmy987654321 said:
Thanks urstrulynaveen, that worked a treat. I'm very grateful. All back up and running now.
Click to expand...
Click to collapse
Were you able to lock your bootloader